First time in flashing my TF 701... so I succesfully unlocked my tabled with the Asus unocker tool (now the screen always show "The Device is Unlocked" message).
After keeping the vol- + power button pressed, the Rkc/Android/Wipe data trio appears, but when I proceed with the RCK option, after a couple seconds the "dead droid with red triangle" picture appears.
Like this: https://forums.androidcentral.com/a...94921t-cwm-not-working-androidredtriangle.jpg
Tried the wipe data option, but it made no difference (apart from properly wiping the device ) - The device working fine otherwise (still with the regular Asus Android 4.4.2)
So any advice, how could I flash my device to have a custom ROM (this one I planned to install - https://forum.xda-developers.com/transformer-tf701/orig-development/rom-t3496994 )
Sorry don't have time for details but you have the stock recovery installed and that is the correct default behavoiur.
You need to install a custom recovery like ClockworkMod or TWRP and go from there.
I suggest you do lots of reading to make sure that you don't get into any issues.
Thanks for the reply, based on your initial guidance it I took a look on some guides on the CWM and managed to install it (but only with the help of ADB), and could update the device after it.
Related
Hey y'all.
Please help me. My P990 is stuck right after the LG logo on bootup.
First of all, this is what ive done:
1. Rooting the phone - succesful
2. Following the guide to install CyanogenMod 7.1.0 (stable) ROM - succesfull
- Nandroid backup
- Wipe all data + cache
- Can't remember it all really lol, but i had cyanogenmod working succesfully!
3. I wanted "voodoo sound", therefor i was told i had to flash a new kernel, which was working to cyanogenmod - thats why i chosed this kernel: vorkKernel-OC/UV Kernel for CM[20111105] which can be found here on xda, sorry i cant link yet - so what i did was downloading the .apk file, and in there, i could choose some things to get with it, and then download the .zip to flash from recovery mode. So i downloaded, flashed it from Clockworkmod recovery and it finished succesfully. So i rebooted my phone, it came with the "LG", then the logo (without animation) and then just black screen.
I feel like i cant do anything. As always when i try to open recoverymode (power + vol. down) it comes with: "S/W Update" (while flashing and nandroid backuping ive used ROM Manager's function "Boot to recovery".)
Ive tried to press any buttons.
Ive tried to plug my phone to the computer, no effekt.
Im really lost! Please help me
Thanks.
curzey said:
Hey y'all.
Please help me. My P990 is stuck right after the LG logo on bootup.
First of all, this is what ive done:
1. Rooting the phone - succesful
2. Following the guide to install CyanogenMod 7.1.0 (stable) ROM - succesfull
- Nandroid backup
- Wipe all data + cache
- Can't remember it all really lol, but i had cyanogenmod working succesfully!
3. I wanted "voodoo sound", therefor i was told i had to flash a new kernel, which was working to cyanogenmod - thats why i chosed this kernel: vorkKernel-OC/UV Kernel for CM[20111105] which can be found here on xda, sorry i cant link yet - so what i did was downloading the .apk file, and in there, i could choose some things to get with it, and then download the .zip to flash from recovery mode. So i downloaded, flashed it from Clockworkmod recovery and it finished succesfully. So i rebooted my phone, it came with the "LG", then the logo (without animation) and then just black screen.
I feel like i cant do anything. As always when i try to open recoverymode (power + vol. down) it comes with: "S/W Update" (while flashing and nandroid backuping ive used ROM Manager's function "Boot to recovery".)
Ive tried to press any buttons.
Ive tried to plug my phone to the computer, no effekt.
Im really lost! Please help me
Thanks.
Click to expand...
Click to collapse
Sounds like a boot loop. Check filesystem compatibility of the kernel you flashed. Might not be compatible with the one previously used by CM.
you should wipe cache and wipe dalvik cache if you want to flash the kernel. and in order to get work your phone again, you should nvflash cause your phone can't do anything
You're trying to enter recovery wrong. Hold both power and vol- for around 10secs. If you're getting S/W Update, you're only holding volume down.
vokkernal, how to make it work?
Hi, even I tried that, I got the same error... Can anyone suggest a way to make it work, or if any step is missing?
By the way, I used the latest Version on Cynogenmod (stable) (update-cm-7.1.0-Optimus2X-signed.zip), vokkernal app.
Thanks
Very sorry for slow answer!
Anyone can link a guide for a working NVFlash ? ive tried but it comes up with an "uid read fail" ind the cmd box, after the "Nvflash started" ???
here you are
http://forum.xda-developers.com/showthread.php?t=1007825
Click to expand...
Click to collapse
hmm, I had the same problem trying to enter recovery, You have to press vol down and then power. If you do it at the same time sometimes doesnt work. So try pressing it before power and keep them pressed until you see the LG Logo (but the one with a bit of blue light) then you can't unpress them.
Download smartflash and download stock rom along with baseband and flash it using smartflash by pulling out battery from phone press volumedown and insert usb cable and soon check procedure in xda forum.i garuntee you it will work as i faced same issue
Sent from my LG-P990 using XDA App
I just recently got my TF701T. I unlocked the boot loader with the Asus unlock tool and then attempted to upgrade to version 11.4.1.17 so that I could install Cromi-X 7 on it. I placed the file UL-K00C-US-11.4.1.17-user.zip on the root of the tablet and rebooted. Once the OS booted back up I was alerted that an update file had been found and I clicked it to begin installing.
The tablet rebooted and appeared to be upgrading but now all I see is a robot on his back with a red exclamation point. After a while the tablet will reboot and again show the Asus splash screen and then the upgrading robot then immediately go to the robot on its back.
I can get to fastboot by pressing power and volume down. I see "the device is unlocked" at the top of the Asus splash screen then I see a screen with the following. Android macallan-user bootloader (1.00 e) released by "US_epad-10.14.1.47-20131022" Choosing RCK, Android or Wipe Data do nothing to help the situation.
I thought I had found a solution in this thread http://forum.xda-developers.com/showpost.php?p=47933481&postcount=1 but the link for drgravy's recovery.img is not working.
I would appreciate any help recovering this tablet. Thank you.
jggrnaut said:
I just recently got my TF701T. I unlocked the boot loader with the Asus unlock tool and then attempted to upgrade to version 11.4.1.17 so that I could install Cromi-X 7 on it. I placed the file UL-K00C-US-11.4.1.17-user.zip on the root of the tablet and rebooted. Once the OS booted back up I was alerted that an update file had been found and I clicked it to begin installing.
The tablet rebooted and appeared to be upgrading but now all I see is a robot on his back with a red exclamation point. After a while the tablet will reboot and again show the Asus splash screen and then the upgrading robot then immediately go to the robot on its back.
I can get to fastboot by pressing power and volume down. I see "the device is unlocked" at the top of the Asus splash screen then I see a screen with the following. Android macallan-user bootloader (1.00 e) released by "US_epad-10.14.1.47-20131022" Choosing RCK, Android or Wipe Data do nothing to help the situation.
I thought I had found a solution in this thread http://forum.xda-developers.com/showpost.php?p=47933481&postcount=1 but the link for drgravy's recovery.img is not working.
I would appreciate any help recovering this tablet. Thank you.
Click to expand...
Click to collapse
Do you have the Asus drivers and adb/fastboot installed on your PC?
If you have fastboot access, it would be as easy as:
Download CWM 6.0.4.7 from here http://droidbasement.com/db-blog/?p=3207
I know it says you have to be on 10.26.1.18 for this, but since you will use it only to flash the latest bootloader, you should be fine.
Put the recovery.img into your fastboot folder and flash it (if you need help here, let me know).
Then fastboot reboot
Your tablet should boot up normally now
Part 2:
Head here http://forum.xda-developers.com/transformer-tf701/development/rom-nov-24-t2951032 and grab the 11.4.1.27 bootloader/CWM 6.0.5.1 package
Flash it in your existing CWM
Reboot
Part 3:
Boot to recovery
Make a nandroid of your stock rom
Go back to home
Wipe data, cache and Dalvik
Flash the rom (which you have loaded onto your microSD)
All done.
Don't forget to delete the (probably corrupted) firmware file
EDIT: BTW, when you reboot to system from CWM you will always get the question if you want to fix root. Choose NO - it's a bug....
berndblb said:
Do you have the Asus drivers and adb/fastboot installed on your PC?
If you have fastboot access, it would be as easy as:
Download CWM 6.0.4.7 from here http://droidbasement.com/db-blog/?p=3207
I know it says you have to be on 10.26.1.18 for this, but since you will use it only to flash the latest bootloader, you should be fine.
Put the recovery.img into your fastboot folder and flash it (if you need help here, let me know).
Then fastboot reboot
Your tablet should boot up normally now
Part 2:
Head here http://forum.xda-developers.com/transformer-tf701/development/rom-nov-24-t2951032 and grab the 11.4.1.27 bootloader/CWM 6.0.5.1 package
Flash it in your existing CWM
Reboot
Part 3:
Boot to recovery
Make a nandroid of your stock rom
Go back to home
Wipe data, cache and Dalvik
Flash the rom (which you have loaded onto your microSD)
All done.
Don't forget to delete the (probably corrupted) firmware file
EDIT: BTW, when you reboot to system from CWM you will always get the question if you want to fix root. Choose NO - it's a bug....
Click to expand...
Click to collapse
Thanks for the reply. I do have the drivers and adb/fastboot setup on PC.
After I could not find anywhere to download the version of CWM that was supposed to be for my firmware version I was afraid to proceed.
When I get home I will try the steps you have listed above and report back how it turned out.
One question, In part one after I flash recovery CWM 6.0.4.7 do I reboot to recovery or let the tablet reboot to the OS?
jggrnaut said:
Thanks for the reply. I do have the drivers and adb/fastboot setup on PC.
After I could not find anywhere to download the version of CWM that was supposed to be for my firmware version I was afraid to proceed.
When I get home I will try the steps you have listed above and report back how it turned out.
One question, In part one after I flash recovery CWM 6.0.4.7 do I reboot to recovery or let the tablet reboot to the OS?
Click to expand...
Click to collapse
Shouldn't matter. When you flash recovery or bootloader, you flash it to the staging partition. The actual installation happens during the next boot - you'll see a brief blue progress bar under the Asus logo.
Booting a recovery for the first time I always reboot to system after the flash, then power down and enter the new recovery from the bootloader. Probably booting straight to recovery or bootloader is ok, but I have not tested it.
berndblb said:
Shouldn't matter. When you flash recovery or bootloader, you flash it to the staging partition. The actual installation happens during the next boot - you'll see a brief blue progress bar under the Asus logo.
Booting a recovery for the first time I always reboot to system after the flash, then power down and enter the new recovery from the bootloader. Probably booting straight to recovery or bootloader is ok, but I have not tested it.
Click to expand...
Click to collapse
Well it has gotten worse and I think I have lost fastboot now. I downloaded the CWM from part 1 above and flashed it in fastboot. I typed fastboot reboot and now I am stuck in a bootloop still. It says "The device is unlocked" at top of Asus splash screen for about 15 seconds, screen turns black and the goes back to Asus splash screen.
I tried holding power and volume key to get back to fastboot but no luck. Any ideas?
Wow! You are really having some bad luck there!!
First the failed firmware update and now this.... Please post the commands you used to flash CWM.
I have no explanantion for this since you did not even boot into CWM.......
Unless..... the bad firmware flash left a command behind calling the stock recovery to do something (which in your case did not work anyway since it just looped) and now the bootloader tries to execute the command which is not "understood" by CWM. But that still does not explain why you cannot boot into the BL anymore......
Can you turn it off by long pressing power? Try every which way to get into fastboot. Without it there is not much you can do I'm afraid.
Try the restart pin hole (I believe it's on the left side of the tablet near the top) in conjunction with Volume Down, try leaving it alone for a while, try timing the button press somewhat differently - anything to get you into the BL again...
I feel very sorry for you, mate!!
Thanks for helping even if it didnt turn out great.
I typed fastboot flash recovery recovery.img after I had downloaded 6.0.4.5 and put it in my fastboot folder. I got confirmation that it transferred successfully.
Then fastboot reboot The tablet rebooted but still would not boot into OS. It still boot looped but did not show the dead android icon anymore.
I got back into fastboot and selected RCK but it would not boot into recovery. Finally I got back into fastboot and selected wipe data and that is what got me to current situation. Now the only thing I get is when I long press power and volume up my PC picks up an unknown device that says apx.
jggrnaut said:
Thanks for helping even if it didnt turn out great.
I typed fastboot flash recovery recovery.img after I had downloaded 6.0.4.5 and put it in my fastboot folder. I got confirmation that it transferred successfully.
Then fastboot reboot The tablet rebooted but still would not boot into OS. It still boot looped but did not show the dead android icon anymore.
I got back into fastboot and selected RCK but it would not boot into recovery. Finally I got back into fastboot and selected wipe data and that is what got me to current situation. Now the only thing I get is when I long press power and volume up my PC picks up an unknown device that says apx.
Click to expand...
Click to collapse
I don't know what happened before - maybe you were doomed since the bad firmware flash - but that last step sealed the coffin.
Using Wipe Data from the bootloader with a custom recovery installed is asking for trouble. Never ever do that.... Sorry, it's a brick. [emoji24]
I unlocked the bootloader and rooted my device but then recovery mode wouldn't load; it just gave me the exclamation mark android and wouldn't go into recovery. So, I downloaded TWRP to have a recovery that would load. I then attempted to let the system update itself to 5.1 and it went into TWRP recovery and didn't update. I decided to download the shamu 5.1 from google dev and flash it from the bootloader. I kept getting the error "could not allocate ######### bytes" so I thought I must need to erase all the partitions and load them back one by one. I flashed boot, cache, recovery, and user data, but got the same error on the system partition. I tried to enter recovery to attempt to wipe the data and just got the exclamation mark android so I thought I should lock and unlock the bootloader to force it to clear its data. I locked the bootloader but it will not unlock now; it says "Check 'Allow OEM Unlock' in Developer Options" but the phone will not boot past the google logo. Any advise?
Jesus, error after error there. You should have stopped and asked advice before carrying on.
Well if you haven't got TWRP anymore, you're screwed. You'll have to send it back to moto/google for repair. There's no way out if you haven't got TWRP.
In regards to the mistakes...
- standard recovery gives exclamation mark. Press volume up and power to get to the menu
- you cannot update officially OTA if you are modified at all, including custom recovery
- the error about system was because your fastboot is out of date
- once you lock the boot loader, you can not unlock without a booting OS.
- if you have a broken OS and stock recovery, you can not fix the OS.
Ouch. Yes, this is pretty much a prime example of what not to do in each situation.
As @cam30era always notes, to enter stock recovery, when dead Android appears with red exclamation point, HOLD power and press volume up once.
Sorry you lost your device but if you had read a little before jumping into bad decisions, this could have been avoided. Hope you get a working device soon and next time, ask for help.
ouch..
yea, time to try and RMA it.
So, after wiping cm12.1 system,data and cache files (dalvik too), I tried to flash the cm 13.0 nightly i downloaded from the cm website. The install went well until it crashed halfway during the flashing and rebooted into the "Unlocked bootloader" warning screen. No animated logo appeared. Pressing [power] + [volume down] did make the phone reboot to TWRP, and this time i tried to restore the nandroid backup I made earlier. It reached about 240 megabytes of restoring only to crash and reboot into unlocked bootloader message again. I do not know what to do now, as i have little experience beyond the most basic things of flashing ROMs et cetera. Also I tried to use the ADB bridge to flash the cm13 zip, but oem devices just shows my phone as unauthorized and when using the commands given at cm wiki it just says <waiting for device>. I suspect this being due to the fact ther no longer is an OS installed? I'd really like to reinstall android in some way so i don't have to send it back for the guarantee (which I hope they'll still accept after unlocking bootloader).
Thanks for the help,
Julz_
Recently I tried out the Nougat preview on my EVA-L09C636. It was ok but seeing as there was a problem with fonts and I'd lost root access, I began thinking about going back to MM.
To prepare for downgrade I tried using srktool to bring TWRP back (and I think this is my big mistake as srktool uses a TWRP made for MM, not N, is that right?). After I tried to restore TWRP I noticed "not recognised" errors when I connected my phone to PC again.
System recovery using hajuuk's Firmware Updater and HiSuite looked like it would complete but near the end of the process (the restoring system part) HiSuite aborted itself saying my device wasn't supported. This has left my P9 is in an unusable state where the only thing I can access is fastboot. Also I can't turn off my phone - holding down power simply makes it reboot then get stuck at the "Your device ... can't be trusted / Your device is booting now" screen.
Reading around a bit I attempted to unbrick it without any luck:
1. downloaded EVA-L09C636B152 update.zip from http://forum.xda-developers.com/p9/development/rom-stock-rom-eva-l19c636b168-t3419586 and installed Snoop05's 15 seconds ADB Installer.
2. extracted images from update.zip using Huawei Update Extractor and did
Code:
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash cust cust.img
then tried rebooting holding volume up + power several times (but never got past untrusted device boot screen).
3. extracted contents of update.zip to folder 'dload' on a blank sd card, trying to force update several times by rebooting and holding down power + volume up + volume down (still never get past the screen saying my device is booting).
At this point I'd be happy to get anything happening on my phone - Marshmallow, Nougat or even some other ROM so I can use my device again.
Any ideas? I'm on EVA-L09 C636.
i2ectcf said:
Recently I tried out the Nougat preview on my EVA-L09C636. It was ok but seeing as there was a problem with fonts and I'd lost root access, I began thinking about going back to MM.
To prepare for downgrade I tried using srktool to bring TWRP back (and I think this is my big mistake as srktool uses a TWRP made for MM, not N, is that right?). After I tried to restore TWRP I noticed "not recognised" errors when I connected my phone to PC again.
System recovery using hajuuk's Firmware Updater and HiSuite looked like it would complete but near the end of the process (the restoring system part) HiSuite aborted itself saying my device wasn't supported. This has left my P9 is in an unusable state where the only thing I can access is fastboot. Also I can't turn off my phone - holding down power simply makes it reboot then get stuck at the "Your device ... can't be trusted / Your device is booting now" screen.
Reading around a bit I attempted to unbrick it without any luck:
1. downloaded EVA-L09C636B152 update.zip from http://forum.xda-developers.com/p9/development/rom-stock-rom-eva-l19c636b168-t3419586 and installed Snoop05's 15 seconds ADB Installer.
2. extracted images from update.zip using Huawei Update Extractor and did then tried rebooting holding volume up + power several times (but never got past untrusted device boot screen).
3. extracted contents of update.zip to folder 'dload' on a blank sd card, trying to force update several times by rebooting and holding down power + volume up + volume down (still never get past the screen saying my device is booting).
At this point I'd be happy to get anything happening on my phone - Marshmallow, Nougat or even some other ROM so I can use my device again.
Any ideas? I'm on EVA-L09 C636.
Click to expand...
Click to collapse
did you wiped data, cache, dalvik?
snapdesign said:
did you wiped data, cache, dalvik?
Click to expand...
Click to collapse
Hi! I'm not sure how to wipe data, cache or dalvik, because when I upgraded to Nougat this apparently removed TWRP.
Also I'm wondering if trying to use srktool to reinstall TWRP for 6.0 might have corrupted my 7.0 phone?
Is there any way to wipe data, cache, and/or dalvik now? Or are there other things I could try to unbrick?
Although my phone was in a pretty bizarre state - it would get hot and sit on the booting now screen until battery died - I was able to use DC Phoenix to make it boot up again. At that point it had no themes and only KitKat-esque icons. A reset and upgrade later icons and themes work and I'm back on stock Marshmallow. Here's an outline:
1. Google "Huawei Bricked phone repair guide with DC Phoenix", go to the first result and look at the instructions (I can't post URLs yet).
I used Method 1. But note! The newer versions of DC Phoenix are missing a feature that the instructions make clear you have to use. To get the original version used in their guide, you have to download the latest version of DC Phoenix, open it on your PC, then click "Enter Support Area" which logs you in to a download section. Find "DC Unlocker Softwares", "DC_Phoenix", then download DC_Phoenix_v14.rar and run that instead. Whether it's Method 1 or 2 make sure you complete it - i.e. the fastboot flash step AND a step they call "flashing in upgrade mode."
(Also note that for DC Phoenix you want to feed it the oldest version of firmware available for your phone, in my case b152. This is because themes and icons won't be fixed until it receives the next version of firmware as an update.)
2. Once I did the fastboot and upgrade flash, I did a system reset from the Settings app trying to get themes and current icons again. (This didn't work but doesn't do any harm or might have helped somehow further down the line).
3. I used hajuuk's Firmware Updater and HiSuite to upgrade to the next version of firmware available (in my case b168).
3. All fine and your phone is back to stock - icons look nice again and local themes are back. To get the original icons layout, go to Recents, hold down on the Trash Icon, show system apps, and Clear Data for Huawei Home.
i2ectcf said:
Although my phone was in a pretty bizarre state - it would get hot and sit on the booting now screen until battery died - I was able to use DC Phoenix to make it boot up again. At that point it had no themes and only KitKat-esque icons. A reset and upgrade later icons and themes work and I'm back on stock Marshmallow.
Click to expand...
Click to collapse
Thanks for sharing! You saved me!