can't flash any ROM's - SD card problem - Transformer TF300T General

Can anyone extend some help to a TF300T n00b?
I flashed the unofficial CM10 Jellybean ROM to my tf300t, and since the storage isn't working I can't move another ROM or even the stock firmware file to my SD card to flash. So, basically I'm stuck on the unofficial CM10 for now...
posted here because I can't post in the actual developement thread

just connect the tablet to a pc and copy the rom to the tablet. I dont rember if windows sees the internal storage. If it dosent linux should or you can install adb and push the file to /sdcard from your computer.

go here and dl the prog:
http://www.google.de/url?sa=t&rct=j...sg=AFQjCNG5sMnAkUGOfTZHgHJLFBARtdiyPg&cad=rja
extract it
boot into tecovery.
open the prog
choose the rom you like and push it to your tablet.
It is not possible to do it when you are in system, cause you cant write anything to the internal space.

mikaole said:
go here and dl the prog:
http://www.google.de/url?sa=t&rct=j...sg=AFQjCNG5sMnAkUGOfTZHgHJLFBARtdiyPg&cad=rja
extract it
boot into tecovery.
open the prog
choose the rom you like and push it to your tablet.
It is not possible to do it when you are in system, cause you cant write anything to the internal space.
Click to expand...
Click to collapse
I couldn't get the fast ADB pusher to work, nor the actual ADB. Fast pusher said it succeeded a few times but I couldn't find the new ROM on my SD card in CWM.

http://forum.xda-developers.com/showthread.php?t=1680570
Check here it has instructions on how to setup and use adb

MegaNoob said:
http://forum.xda-developers.com/showthread.php?t=1680570
Check here it has instructions on how to setup and use adb
Click to expand...
Click to collapse
looks promising. I hadn't been attempting to push the files while the tablet was in recovery because adb wouldnt recognize the tab when it was in recovery. I don't have my tablet cable, but I will try tomorrow morning. Thanks again.

ljungberg3 said:
looks promising. I hadn't been attempting to push the files while the tablet was in recovery because adb wouldn't recognize the tab when it was in recovery. I don't have my tablet cable, but I will try tomorrow morning. Thanks again.
Click to expand...
Click to collapse
if adb doesn't recognize the pad when it's in recovery, the drivers may not be installed correctly

paedz718 said:
if adb doesn't recognize the pad when it's in recovery, the drivers may not be installed correctly
Click to expand...
Click to collapse
I installed the drivers exactly as the guide directed, then tried using regular ADB, which didnt work. So I tried to use the ADB fast push and it didn't work either, under the "information" tab on the fast adb program it says
"Failed to mount as R/W"
is this a problem?

I got files to push via ADB, installation was aborted on the stock rom
I will try to find another stock rom to flash and update you guys. thanks for all the help so far

Can you still get to fastboot mode?
---------- Post added at 10:53 PM ---------- Previous post was at 10:44 PM ----------
If yes, dl the latest. Asus. STOCK, extract the blob, put it in the Fastboot Folder and. Open cmd
cd to the fastboot directory and write
fastboot -i 0x0B05 flash system blob
This will flash stock.
Don't give up, when it's not working. Just rewrite and try again and again.
A, user in the German Forum needed 20 times till it finally run through.

mikaole said:
Can you still get to fastboot mode?
---------- Post added at 10:53 PM ---------- Previous post was at 10:44 PM ----------
If yes, dl the latest. Asus. STOCK, extract the blob, put it in the Fastboot Folder and. Open cmd
cd to the fastboot directory and write
fastboot -i 0x0B05 flash system blob
This will flash stock.
Don't give up, when it's not working. Just rewrite and try again and again.
A, user in the German Forum needed 20 times till it finally run through.
Click to expand...
Click to collapse
I was able to push and flash a stock firmware! thank god! haha, and thank you guys for all the help!

ljungberg3 said:
I was able to push and flash a stock firmware! thank god! haha, and thank you guys for all the help!
Click to expand...
Click to collapse
Np

So, much of the stuff in this and other threads has been a tremendous help. I did pretty much exactly what OP did in this thread http://forum.xda-developers.com/showthread.php?t=1779080.
That thread lead me to this one, as I was having trouble getting my computer to recognize the usb drivers. I was able to finally get ADB to see the tablet, however, when I go to push the stock rom, I get an error message of "Protocol Failure" in cmd.
Any ideas?
http://s12.postimage.org/unt8ag1vh/adbcmd.jpg
Created new thread as OP solved his problem.

Related

Wiped everything in TWRP. Need Help!

I wiped/formatted everything in TWRP. Now of course, there's no recovery or backups and when I do a factory reset, it boots and gets stuck with the LG logo.
HELP!
centro714 said:
I wiped/formatted everything in TWRP. Now of course, there's no recovery or backups and when I do a factory reset, it boots and gets stuck with the LG logo.
HELP!
Click to expand...
Click to collapse
can you get into download mode? (turn phone off, hold vol up, and plug phone into computer)
centro714 said:
I wiped/formatted everything in TWRP. Now of course, there's no recovery or backups and when I do a factory reset, it boots and gets stuck with the LG logo.
HELP!
Click to expand...
Click to collapse
Push a ROM via adb sideload and flash.
Support your Devs......
iOSh8er said:
Push a ROM via adb sideload and flash.
Support your Devs......
Click to expand...
Click to collapse
How do I do that exactly? Is there software on the computer side I have to install?
Install adb on your PC (Google on how to install if need be). Then push your file from PC to phone as instructed here http://teamw.in/ADBSideload
Support your Devs......
---------- Post added at 09:11 PM ---------- Previous post was at 09:07 PM ----------
Or do what @mazer4455 said & get into download mode to restore to stock. See instructions here http://forum.xda-developers.com/showthread.php?t=2432476
Support your Devs......
[QUOTE3]Or do what @mazer4455 said & get into download mode to restore to stock. See instructions here http://forum.xda-developers.com/show....php?t=2432476)[/QUOTE]
Doesn't look like the instructions include the LS980 Sprint version.
I'm trying to read up on installing ADB on my PC put a bit tougher than simply installing.
I've installed Android SDK onto my computer, running cmd from platform-tools, and did a "adb devices" and it cannot find my device.
any tips at this point?
centro714 said:
I've installed Android SDK onto my computer, running cmd from platform-tools, and did a "adb devices" and it cannot find my device.
any tips at this point?
Click to expand...
Click to collapse
wow, can't believe I found out!! turns out downloading the LG drivers DID NOT work but downloading PDA Net did!!
I was then able to sideload the rom and gapps file and now phone is back online! only took about 4 hours
centro714 said:
wow, can't believe I found out!! turns out downloading the LG drivers DID NOT work but downloading PDA Net did!!
I was then able to sideload the rom and gapps file and now phone is back online! only took about 4 hours
Click to expand...
Click to collapse
I did the same thing you did. Can you offer any help. I am extremely lost.
fisheric1 said:
I did the same thing you did. Can you offer any help. I am extremely lost.
Click to expand...
Click to collapse
I will get you some details instructions if you can wait till tomorrow.
Or, read this thread and YouTube how to do an adb side load. In short, you will need to download android sdk to your PC, download the rom zip file, plug your phone in and enter twrp's adb side load, open command prompt, and enter adb side load command.
Sent from my LG-G2 using xda app-developers app
centro714 said:
I will get you some details instructions if you can wait till tomorrow.
Or, read this thread and YouTube how to do an adb side load. In short, you will need to download android sdk to your PC, download the rom zip file, plug your phone in and enter twrp's adb side load, open command prompt, and enter adb side load command.
Sent from my LG-G2 using xda app-developers app
Click to expand...
Click to collapse
Thanks. That is what I figured I would have to do. ADB just isn't find the device though. I can boot into TWRP.
ADB Sideload instructions
fisheric1 said:
Thanks. That is what I figured I would have to do. ADB just isn't find the device though. I can boot into TWRP.
Click to expand...
Click to collapse
Ok, so here's what I did to install a ROM in TWRP when I wiped all the data using adroid SDK tools and TWRP ADB side load:
- Go here to download Android SDK https://developer.android.com/sdk/index.html (remember where you save/install it)
- Download your ROM and Gapps file (For Sprint, I think we only have Carbon ROM so use this link http://forum.xda-developers.com/showthread.php?t=2502789)
- Once you've downloaded the ROM and Gapps zip files, save the zip file into "your drive:\androidSDK\sdk\platform-tools" (this just makes it easier to find when doing the adb side load)
- Now plug your phone into your PC. Go into TWRP and start up ADB Side load. I think it's in Advanced button.
- Now open up the "your drive:\androidSDK\sdk\platform-tools" folder. In that folder, do a Shift-Right-Click and click "Open Command Window Here" to open cmd w/ that destination already mapped out.
- From here, all you have to do is type in "adb sideload [enter zip file name here]" and it should start installing over to your phone.
**** One important thing to note, if for some reason, in the command prompt your device is not visible, download PDA net for Android http://pdanet.co/ (this was actually my case and PDA net worked like a charm)

[Q] How to flash a ROM through twrp adb sideload?

I flashed 1.2.5 Malladus on 12B OTA rooted for Verizon using twrp 2.6.3.3. When I booted the LG logo appears for a second and the screen turns black. Reading from a previous post Malladus wont boot if you're on 12B OTA. I can't boot my phone flashing this rom. I would like to adb sideload through twrp. I don't want to mess phone up to brick I'm a noob I don't have adb tools on my computer I wouldn't know where to place them.
Please help me with a step by step.
Thank you
atticustcx said:
I flashed 1.2.5 Malladus on 12B OTA rooted for Verizon using twrp 2.6.3.3. When I booted the LG logo appears for a second and the screen turns black. Reading from a previous post Malladus wont boot if you're on 12B OTA. I can't boot my phone flashing this rom. I would like to adb sideload through twrp. I don't want to mess phone up to brick I'm a noob I don't have adb tools on my computer I wouldn't know where to place them.
Please help me with a step by step.
Thank you
Click to expand...
Click to collapse
Hey man here's a link;
http://teamw.in/ADBSideload
If you need more help let me know..
.make sure that your enviromentals are set too so your PC can understand commands
RubbleTea said:
Hey man here's a link;
http://teamw.in/ADBSideload
If you need more help let me know..
.make sure that your enviromentals are set too so your PC can understand commands
Click to expand...
Click to collapse
I'm having trouble installing adb i'm following this guy I installed adb but when I open device manager I don't see adb.exe or fastboot in C:\Windows
atticustcx said:
I'm having trouble installing adb i'm following this guy I installed adb but when I open device manager I don't see adb.exe or fastboot in C:\Windows
Click to expand...
Click to collapse
OK hey so you have adb all set up and set in enviromentals right? And you have a ROM ready? And drivers installed? For ease of doing things rename the ROM "ROM" so it should be ROM.zip
---------- Post added at 12:10 PM ---------- Previous post was at 12:00 PM ----------
Once you have that done place the rom into the same folder as your adb.exe is.......now plug in your phone to PC a and have recovery open.....then go to advanced the click sideload ROM....then swipe....
..now open a command prompt...then type adb devices to heck if your device is shown....if it is go ahead and type" adb sideload ROM.zip" ...then wait til it finishes...then unplug from PC and flash the ROM.......if your driver won't show your device try koush universal drivers....sorry man I'm at work now
I had a similar issue and I was able to flash clean rom but I still reboot to twrp. Do I need to flash a boot image or something.?
from my Note Thrizzle
RubbleTea said:
OK hey so you have adb all set up and set in enviromentals right? And you have a ROM ready? And drivers installed? For ease of doing things rename the ROM "ROM" so it should be ROM.zip
---------- Post added at 12:10 PM ---------- Previous post was at 12:00 PM ----------
Once you have that done place the rom into the same folder as your adb.exe is.......now plug in your phone to PC a and have recovery open.....then go to advanced the click sideload ROM....then swipe....
..now open a command prompt...then type adb devices to heck if your device is shown....if it is go ahead and type" adb sideload ROM.zip" ...then wait til it finishes...then unplug from PC and flash the ROM.......if your driver won't show your device try koush universal drivers....sorry man I'm at work now
Click to expand...
Click to collapse
I don't have adb installed and environmentals. I don't have a ROM ready because I'm not sure which one is safe to flash over 12B OTA.
I only have LG drivers 2.11.1.0 installed. Every time I connect my phone it says to install drivers but it can't find VS980 drivers and says unsuccessful install
atticustcx said:
I don't have adb installed and environmentals. I don't have a ROM ready because I'm not sure which one is safe to flash over 12B OTA.
I only have LG drivers 2.11.1.0 installed. Every time I connect my phone it says to install drivers but it can't find VS980 drivers and says unsuccessful install
Click to expand...
Click to collapse
Try downloading a stock ROM with the ota should be one, and download koush universal drivers anyway.....for adb android SDK will have it and have instructions to setup....Google will help.....environment settings will make it so your computer understands adb commands...
---------- Post added at 01:39 PM ---------- Previous post was at 01:37 PM ----------
rawb123456 said:
I had a similar issue and I was able to flash clean rom but I still reboot to twrp. Do I need to flash a boot image or something.?
from my Note Thrizzle
Click to expand...
Click to collapse
So you flash a ROM and it goes to twrp, did you accept the ota with a custom recovery? For you might have to flash to stock image(there's a thread in general forum) but first try another rom
RubbleTea said:
Try downloading a stock ROM with the ota should be one, and download koush universal drivers anyway.....for adb android SDK will have it and have instructions to setup....Google will help.....environment settings will make it so your computer understands adb commands...
---------- Post added at 01:39 PM ---------- Previous post was at 01:37 PM ----------
So you flash a ROM and it goes to twrp, did you accept the ota with a custom recovery? For you might have to flash to stock image(there's a thread in general forum) but first try another rom
Click to expand...
Click to collapse
After trying for hours to get my drivers installed so my phone can be read by computer I gave up. I followed this http://forum.xda-developers.com/showthread.php?t=2448960 took my phone back to stock on 11A.

ASUS ME176C/CX- Unlock Bootloader & Install TWRP

Please note: the information in this thread is out of date. I recommend installing me176c-boot instead, found in https://forum.xda-developers.com/me...tloader-me176c-boot-asus-memo-pad-7-t3780225.
DISCLAIMER: I am NOT responsible for anything that goes wrong with your device. This tablet's very resilient and theoretically unbrickable, but it can still happen.
@social-design-concepts is working on a bootloader "unlock" for all Intel Bay Trail devices running Lollipop. It's working fine on our tablet, so he's given me permission to release the unlock for this device, as well as a TWRP image.
Download the images from here:
https://www.androidfilehost.com/?fid=312978532265362065
UPDATED! TWRP is now version 3.0.2!
MAKE A BACKUP OF ESP AND RECOVERY IN CASE ANYTHING GOES WRONG. YOU'VE BEEN WARNED.
These images aren't in a Nandroid or anything, you'll have to flash them manually via dd.
REQUIREMENTS
ASUS ME176C or ASUS ME176CX with root (duh )
and either-
Terminal Emulator must be installed on the tablet, and given root access
or
Access to a computer w/ ADB installed
INSTALLATION
Download the linked file from above, then unzip them to somewhere on your tablet. This directory will be noted as /path/to/unzipped/zip in this tutorial.
Open up a command prompt and plug in your tablet (if you're on PC) or just launch Terminal Emulator on your tablet.
This first command can be skipped if you're installing this without a computer, but if you're using ADB, then first run
Code:
adb shell
The next steps are universal for both Terminal Emulator and the PC command prompt or terminal.
While we could use tethered TWRP to back up these partitions, it cannot properly back up the ESP, so we'll be backing up the partitions manually. To do so, run the following to get root permission and back up the original recovery and ESP.
Code:
su
dd if=/dev/block/by-name/ESP of=/path/to/unzipped/zip/stock_ESP.img
dd if=/dev/block/by-name/recovery of=/path/to/unzipped/zip/stock_recovery.img
Then, to install:
Code:
dd if=/path/to/unzipped/zip/ESP.img of=/dev/block/by-name/ESP
dd if=/path/to/unzipped/zip/recovery.img of=/dev/block/by-name/recovery
Finally, reboot the tablet to make sure it worked. The ASUS screen should be replaced with an Intel one.
Volume Down + Power will give you an option of either fastboot or recovery, instead of just booting to fastboot like the stock bootloader.
do we still get otas? what happends if the ota contains a uefi update will it become locked again?
Ruben Craveiro said:
do we still get otas? what happends if the ota contains a uefi update will it become locked again?
Click to expand...
Click to collapse
Becouse the firmware update is for unknown reason always included in the esp.img, then the answer is yes no matter how unlogical it is.
P.S anybody still having 16GB whole emmc dd backup? Some guy from my country who doesn't speak English contacted me on PM, he tried to run some KK to LP update from 4pda.ru while already on lollipop. Now he is stuck in Aptio Setup Utlility (lying to him saying it's BIOS ) and so far this seems to be the only option to help him.
P.P.S I have finaly ordered a Y OTG cable from ebay so next month when I get it I can start debugging my debirf-xkiosk running on kali kernel to find out what's the problem.
*EDIT ilogical maybe?
---------- Post added at 09:05 PM ---------- Previous post was at 09:03 PM ----------
Why your tutorial can be in general and mine was moved to Q&A? It's unfair :'(
I got this 'Read only file system' message when I tried the first backup.. this shouldn't be happening, right? Presumably the backup failed?
C:\Program Files (x86)\Minimal ADB and Fastboot>adb shell
adb server is out of date. killing...
* daemon started successfully *
[email protected]_1:/ $ su
su
[email protected]_1:/ # dd if=/dev/block/by-name/ESP of=/recoverystuff/stock_ESP.img
dd if=/dev/block/by-name/ESP of=/recoverystuff/stock_ESP.img
dd: /recoverystuff/stock_ESP.img: Read-only file system
1|[email protected]_1:/ #
Worked perfectly with your instructions. Used Terminal Emulator on the tablet.
Sent from my K013 using Tapatalk
seamo123 said:
I got this 'Read only file system' message when I tried the first backup.. this shouldn't be happening, right? Presumably the backup failed?
C:\Program Files (x86)\Minimal ADB and Fastboot>adb shell
adb server is out of date. killing...
* daemon started successfully *
[email protected]_1:/ $ su
su
[email protected]_1:/ # dd if=/dev/block/by-name/ESP of=/recoverystuff/stock_ESP.img
dd if=/dev/block/by-name/ESP of=/recoverystuff/stock_ESP.img
dd: /recoverystuff/stock_ESP.img: Read-only file system
1|[email protected]_1:/ #
Click to expand...
Click to collapse
Try doing it through Terminal Emulator, see if that helps.
jerbear294 said:
Try doing it through Terminal Emulator, see if that helps.
Click to expand...
Click to collapse
Nah, same result using terminal emulator.. what's wrong I wonder?
seamo123 said:
Nah, same result using terminal emulator.. what's wrong I wonder?
Click to expand...
Click to collapse
Android in it's natire has no real rootfs so writing backup to /customdir/ rather than /sdcard/customdir is not gonnw work. If you "remounted" rootfs rw (not sure if you can remount ramdisk) it would still be all in ram.
---------- Post added at 09:26 PM ---------- Previous post was at 09:25 PM ----------
Mis012 said:
Android in it's natire has no real rootfs so writing backup to /customdir/ rather than /sdcard/customdir is not gonnw work. If you "remounted" rootfs rw (not sure if you can remount ramdisk) it would still be all in ram.
Click to expand...
Click to collapse
I wonder why people use ADB for shell when they don't have to
Mis012 said:
Android in it's natire has no real rootfs so writing backup to /customdir/ rather than /sdcard/customdir is not gonnw work. If you "remounted" rootfs rw (not sure if you can remount ramdisk) it would still be all in ram.
Click to expand...
Click to collapse
Oh ok, I'll just move the folder to the sdcard and give it a try..
seamo123 said:
Oh ok, I'll just move the folder to the sdcard and give it a try..
Click to expand...
Click to collapse
@Mis012 is right, either move it to a micro SD and make the path /Removable/MicroSD/recoverystuff or put it on the internal storage and make the path /storage/emulated/0/recoverystuff
jerbear294 said:
@Mis012 is right, either move it to a micro SD and make the path /Removable/MicroSD/recoverystuff or put it on the internal storage and make the path /storage/emulated/0/recoverystuff
Click to expand...
Click to collapse
Seemed to work fine, thanks! Boots up perfectly with the 'Intel' image. How does one get into recovery though? The volume up/down press/let go power button shenanigans for this pad always drove me totally up the wall. Anytime I ever got into stock recovery it was always by accident!
What's the key combo?
seamo123 said:
Seemed to work fine, thanks! Boots up perfectly with the 'Intel' image. How does one get into recovery though? The volume up/down press/let go power button shenanigans for this pad always drove me totally up the wall. Anytime I ever got into stock recovery it was always by accident!
What's the key combo?
Click to expand...
Click to collapse
Volume Down + Power, just like on the stock bootloader.
When you see the Intel screen release Power but keep holding Volume Down. You'll see a screen with a generic warning, then options to go to either fastboot or recovery.
Mis012 said:
Becouse the firmware update is for unknown reason always included in the esp.img, then the answer is yes no matter how unlogical it is.
P.S anybody still having 16GB whole emmc dd backup? Some guy from my country who doesn't speak English contacted me on PM, he tried to run some KK to LP update from 4pda.ru while already on lollipop. Now he is stuck in Aptio Setup Utlility (lying to him saying it's BIOS ) and so far this seems to be the only option to help him.
P.P.S I have finaly ordered a Y OTG cable from ebay so next month when I get it I can start debugging my debirf-xkiosk running on kali kernel to find out what's the problem.
*EDIT ilogical maybe?
---------- Post added at 09:05 PM ---------- Previous post was at 09:03 PM ----------
Why your tutorial can be in general and mine was moved to Q&A? It's unfair :'(
Click to expand...
Click to collapse
why just not simply go to dnx mode? then from there make fastboot flash osloader efilinux.efi and then fastboot boot droidboot.img from there it should boot to droidboot and allow to load temp recovery and flash .36(ive already been stuck in uefi for at least 2 times and this method helped me... yesterday i was stuck and its working again)
jerbear294 said:
Volume Down + Power, just like on the stock bootloader.
When you see the Intel screen release Power but keep holding Volume Down. You'll see a screen with a generic warning, then options to go to either fastboot or recovery.
Click to expand...
Click to collapse
That's great, thanks! So does this mean that we're all ready to install a custom ROM when one comes along? Running CM or AOSP on this device would be brilliant, I can finally forget all about that piercing white ASUS ui for a start
seamo123 said:
That's great, thanks! So does this mean that we're all ready to install a custom ROM when one comes along? Running CM or AOSP on this device would be brilliant, I can finally forget all about that piercing white ASUS ui for a start
Click to expand...
Click to collapse
Precisely. A custom ROM is possible with this bootloader.
Ruben Craveiro said:
why just not simply go to dnx mode? then from there make fastboot flash osloader efilinux.efi and then fastboot boot droidboot.img from there it should boot to droidboot and allow to load temp recovery and flash .36(ive already been stuck in uefi for at least 2 times and this method helped me... yesterday i was stuck and its working again)
Click to expand...
Click to collapse
He tried, it complained about some partitions not existing.
Mis012 said:
He tried, it complained about some partitions not existing.
Click to expand...
Click to collapse
he needs to repartition the tablet :
Code:
fastboot oem start_partitioning
fastboot oem partition /system/etc/partition.tbl
fastboot oem format factory
fastboot oem format cache
fastboot oem format system
fastboot oem format config
fastboot oem format logs
fastboot oem format misc
fastboot oem format data
fastboot oem stop_partitioning
Does it work with Build .36?
Hello,
i updated my me176c to the build number WW_V12.10.1.36_20151230 can i use your unlocked bootloader ?
intNERD said:
Hello,
i updated my me176c to the build number WW_V12.10.1.36_20151230 can i use your unlocked bootloader ?
Click to expand...
Click to collapse
you can use the unlocked bootloader on any lollipop version
Ruben Craveiro said:
you can use the unlocked bootloader on any lollipop version
Click to expand...
Click to collapse
Thank You! Great work! Cant wait for a custom rom!

Error updating via OTA

Hi everyone,
I was trying to update via OTA to the latest version, but after downloading the update the tablet started updating itself and returned the Android dead droid error. It is important to highlight that I was rooted with KingRoot and removed it to apply OTA update. Any help would be appreciated
regular_ said:
Hi everyone,
I was trying to update via OTA to the latest version, but after downloading the update the tablet started updating itself and returned the Android dead droid error. It is important to highlight that I was rooted with KingRoot and removed it to apply OTA update. Any help would be appreciated
Click to expand...
Click to collapse
Am in the same situation. Waiting to hear back from Cameron Yan.
Looks like you might need to flash the 1.5 version via fastboot and go through each update iteration.
Yeah u might have to flash 1.5
Your Jide Ambassador is here!!!
---------- Post added at 12:45 PM ---------- Previous post was at 12:35 PM ----------
U can't just remove the rooting and think the update will be applied. Each updated is like a layered cake placed on its foundation. When you rooted you messed with pliers of stability for future layered updates and the updates check where they are suppose to be place. If something is missing or out of place you are going to get an error.
Your Jide Ambassador is here!!!
regular_ said:
Hi everyone,
I was trying to update via OTA to the latest version, but after downloading the update the tablet started updating itself and returned the Android dead droid error. It is important to highlight that I was rooted with KingRoot and removed it to apply OTA update. Any help would be appreciated
Click to expand...
Click to collapse
I had the same experience and ended up flashing 1.5 and then going through the automatic updates. Took a little while, but the update installed and I am back to stock for the time being.
regular_ said:
Hi everyone,
I was trying to update via OTA to the latest version, but after downloading the update the tablet started updating itself and returned the Android dead droid error. It is important to highlight that I was rooted with KingRoot and removed it to apply OTA update. Any help would be appreciated
Click to expand...
Click to collapse
Same issue for me I am scared about the root by King root : not the cleaner tool ...
iceheart3131 said:
Same issue for me I am scared about the root by King root : not the cleaner tool ...
Click to expand...
Click to collapse
If you have rooted, the only way to get OTA that I have found is to reflash version 1.5 and then have the normal updates be applied.
I have done this and then rerooted after I have applied the current update.
tomlogan1 said:
If you have rooted, the only way to get OTA that I have found is to reflash version 1.5 and then have the normal updates be applied.
I have done this and then rerooted after I have applied the current update.
Click to expand...
Click to collapse
Ok , but where can I found this 1.5 version please ? there is no Download section on Jide webpage ...
Ok 1.5 version and toutos available on JIDE webpage
I have an issue with fastboot : adb devices found the tablet but fastboot devices found nothing ... My fastboot is functionnal with my edge 7, nexus 5x and android TV ... So it must be something specific to do on Utra Tablet ... But I don't know what
iceheart3131 said:
I have an issue with fastboot : adb devices found the tablet but fastboot devices found nothing ... My fastboot is functionnal with my edge 7, nexus 5x and android TV ... So it must be something specific to do on Utra Tablet ... But I don't know what
Click to expand...
Click to collapse
Probably obvious, but to you have USB debugging enabled?
tomlogan1 said:
Probably obvious, but to you have USB debugging enabled?
Click to expand...
Click to collapse
Yes i have... I have try to connecter other Devices to be sure but the issue is only with Ultra Tablet
iceheart3131 said:
Yes i have... I have try to connecter other Devices to be sure but the issue is only with Ultra Tablet
Click to expand...
Click to collapse
Try connecting via USB and then run a command like adb devices and then unplug the tablet and plug it back in. I remember a security (RSA?) prompt that you have to accept in order for this to work. Worth a try.
tomlogan1 said:
Probably obvious, but to you have USB debugging enabled?
Click to expand...
Click to collapse
Sorry for the long delay (Holydays !!)... Yes USB debug is enabled .
---------- Post added at 05:15 PM ---------- Previous post was at 05:02 PM ----------
tomlogan1 said:
Try connecting via USB and then run a command like adb devices and then unplug the tablet and plug it back in. I remember a security (RSA?) prompt that you have to accept in
Still not available with fastboot
Click to expand...
Click to collapse
iceheart3131 said:
Sorry for the long delay (Holydays !!)... Yes USB debug is enabled .
---------- Post added at 05:15 PM ---------- Previous post was at 05:02 PM ----------
tomlogan1 said:
Try connecting via USB and then run a command like adb devices and then unplug the tablet and plug it back in. I remember a security (RSA?) prompt that you have to accept in
Still not available with fastboot
Click to expand...
Click to collapse
When I use adb I get the device SN. When I use fastboot devices I get nothing. If I then adb reboot bootloader I get the attached response.
Click to expand...
Click to collapse
I follow this tuto (How to flash Remix OS 1.5 from Jide) :
To flash the ROM, please download the file from the following link and follow the below instructions.
https://drive.google.com/open?id=0B...1FVVR3RkRya29sakQ3SEdVbXU5cUg0YTIzUnNfUTRWMTA
Installing image files using fastboot
1. Make sure your Remix has working fastboot (http://wiki.cyanogenmod.org/w/Fastboot) and adb (http://wiki.cyanogenmod.org/w/Adb).
2. Download images
The information of the image zip file:
Images Zip File Name: SK1WG.zip
md5: f993e49ff5f0bfac169dcb62b2e820e8
sha1: 6f9b364f46680ff1294ff2eb9e3fe9aba6592d5a
3. Unzip the downloaded zip file ( SK1WG.zip ) and go to the folder
4. Connect the Remix to the computer via USB.
5. Make sure the fastboot binary is in your PATH (http://wiki.cyanogenmod.org/w/Doc:_paths) or that you place the recovery image in the same directory as fastboot.
6. Open a terminal on your PC and reboot the device into fastboot mode by typing adb reboot bootloader or by using the hardware key combination for your device while it is powered off.
7. Once the device is in fastboot mode, verify your PC sees the device by typing fastboot devices
-If you don't see your device serial number, and instead see "", fastboot is not configured properly on your machine. See fastboot (http://wiki.cyanogenmod.org/w/Doc:_fastboot_intro) documentation for more info.
-If you see "no permissions fastboot", make sure your UDEV (http://wiki.cyanogenmod.org/w/UDEV) rules are setup correctly.
8. Clean the existing data by entering the following command: fastboot -w
9. Flash images onto your device by entering the following three commands:
-fastboot flash system system.img
-fastboot flash recovery recovery.img
-fastboot flash boot boot.img
10. Once the flash completes successfully, run the following command to reboot the device into recovery to verify the installation.
-fastboot reboot
Click to expand...
Click to collapse
I can reboot with adb command
Code:
adb reboot bootloader
my tablet reboot and this menu is available :
but fasboot command seems still without effect , i have try to launch fastboot protocol in the menu : no effect . fastboot devices doens't return any ID . I have try to install complete suite android studio to have ALL tools ( and fastboot ) but it seems the same isssue .
iceheart3131 said:
I follow this tuto (How to flash Remix OS 1.5 from Jide) :
I can reboot with adb command
Code:
adb reboot bootloader
my tablet reboot and this menu is available :
but fasboot command seems still without effect , i have try to launch fastboot protocol in the menu : no effect . fastboot devices doens't return any ID . I have try to install complete suite android studio to have ALL tools ( and fastboot ) but it seems the same isssue .
Click to expand...
Click to collapse
Maybe a driver from previous devices? I'm using the Android naked drivers and they work with the tablet as well as my Android phone.
Victory !!!! until now i have tried with Windows 10 and it doesn't works . With a friend we have follow the sme process on Ubuntu and it works perfectly ! Thanks tomlogan1 for your patience and your support , I appreciate
iceheart3131 said:
Victory !!!! until now i have tried with Windows 10 and it doesn't works . With a friend we have follow the sme process on Ubuntu and it works perfectly ! Thanks tomlogan1 for your patience and your support , I appreciate
Click to expand...
Click to collapse
Congratulations! Now you can be ready when custom ROMs become available. Your presistance paid off.

sideloading adb firmware

So I am really stuck and don't know what to do. Unlocked the bootloader, installed twrp just fine and rooted. then I went to install a custom rom after I made sure it was working and then it kicks me back to the normal recovery. twrp is gone and I can't fastboot the firmware cause I wiped it to flash a rom. Now when I go to adb sideload I keep getting error 21 footer is wrong and signature verification has failed. Can someone please point me in the right direction to fix my phone? thanks
Download stock firmware and flash it via fastboot,all the instructions included in the link https://www.essential.com/developer/current-builds
gm007 said:
Download stock firmware and flash it via fastboot,all the instructions included in the link https://www.essential.com/developer/current-builds
Click to expand...
Click to collapse
Fastboot isn't enabled cause I wiped to flash a rom. and every time I try to sideload it with adb it fails.
tommyjames1992 said:
Fastboot isn't enabled cause I wiped to flash a rom. and every time I try to sideload it with adb it fails.
Click to expand...
Click to collapse
To use fastboot u need to boot ur phone to bootloader mode not to recovery,just follow the information in the link i gave you to know how to flash the firmware.
gm007 said:
To use fastboot u need to boot ur phone to bootloader mode not to recovery,just follow the information in the link i gave you to know how to flash the firmware.
Click to expand...
Click to collapse
Nothing pops up when I type in the command fastboot devices. My phone doesn't show.
tommyjames1992 said:
Nothing pops up when I type in the command fastboot devices. My phone doesn't show.
Click to expand...
Click to collapse
This phone is tricky to get recognized,try changing the usb cable, different usb port and make sure you have the correct drivers installed,and the latest adb fastboot files.
gm007 said:
This phone is tricky to get recognized,try changing the usb cable, different usb port and make sure you have the correct drivers installed,and the latest adb fastboot files.
Click to expand...
Click to collapse
weird thing is I can get it to show when I type fastboot -i 0x2e17 but I am not sure how to use that to flash the firmware. I believe I have all the lastest drivers since I unlocked my bootloader yesterday.
tommyjames1992 said:
weird thing is I can get it to show when I type fastboot -i 0x2e17 but I am not sure how to use that to flash the firmware. I believe I have all the lastest drivers since I unlocked my bootloader yesterday.
Click to expand...
Click to collapse
I had my phone for a week now and happened the same for me ,my pc wasn't recognizing the phone.
All I did is searched for drivers and new adb fastboot files and that did the trick.
Try to remove the phone from device managers on ur pc and install the drivers manually.
Good luck.
---------- Post added at 07:35 PM ---------- Previous post was at 07:15 PM ----------
Try this adb fastboot files,but remove the older one first
https://androidfilehost.com/?fid=3700668719832240948
gm007 said:
I had my phone for a week now and happened the same for me ,my pc wasn't recognizing the phone.
All I did is searched for drivers and new adb fastboot files and that did the trick.
Try to remove the phone from device managers on ur pc and install the drivers manually.
Good luck.
---------- Post added at 07:35 PM ---------- Previous post was at 07:15 PM ----------
Try this adb fastboot files,but remove the older one first
https://androidfilehost.com/?fid=3700668719832240948
Click to expand...
Click to collapse
So I am still got getting fastboot working to flash stock firmware but I managed to reflash twrp and install AICP custom rom. So at least I can use the device. I will figure out the fastboot stuff later I guess lol.

Categories

Resources