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.
Related
I just got and m8 from Cl, it was cheap and I was told the phone had a software issues so I took the plunge.
The phone seems normal, its pack o apps and you can play with it, then I decided to do a factory restore, but it failed (after the reboot it goes to a error screen showing a phone with and exclamation mark)
I tried the same from hboot, same result..
Tried to unlock bootloader, it appears to work but after boot the phone I still the same (loked and with all the user info intact )
Tried to erase the user accounts, it works, I can do a new setup of the Google account, but after restart the phone goes back to the initial state (user accounts are back)
I am not sure what's going on, but it looks like if the memory was protected and after every reboot it goes back to the original state.
Any suggestions of what to do? I am starting to see of there is any way to get warranty thru htc,
Thanks in advance.
The phone is in 4.4.2, can't take updated (it reboots itself on the process)
The phone with the exclamation point indicates the stock Android system recovery is installed. You could try and install TWRP recovery, at which time you could install a custom ROM. My only other thought is to run the RUU for the latest system update. If that doesn't straighten out your issues, something else is going on. Hit the link below and follow the instructions for the manual system update. This is the non-HK RUU. If you need the RUU for the HK version I can post it, also.
http://www.htc.com/us/support/htc-one-m8-sprint/news/
Thanks, I tried to install twrp but it fails, the bootloader is still locked and won't unlock, is there a way to install twrp without unlocking bootloader?
Will give it a try with the RUU, when tried to update thru fastboot it fails, it starts to do all the file checks and it just send you to the "press the power button message" , but no update was perform.
You might give this a try to get your bootloader unlocked and TWRP installed. There is no way around it. You have to unlock the bootloader first before you install TWRP.
http://forum.xda-developers.com/showthread.php?t=2727900
Thanks a lot for the help, nothing has work so far, the phone keeps having random reboots and every time it comes back its like it load an old backup, havent been able to do a firmwware upgrade (from android over wifi, fastboot, or windowsPC).
Is there an utility to test hardware? (possibly memory)
thanks
At the end I contacted HTC support and after some test I was told my phone was still under warranty and I got and RMA (great service)....
Thanks a lot for the help...
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]
Good evening, everyone.
Few hours ago, my N6 randomly shut down and not booting up to the system. I tried to re-install the factory image for 5.0.1 but I got stuck at bootloader screen. I tried every options available from bootloader screen(Start, Recovery mode, Restart bootloader etc.) but it performed nothing but coming back to the bootloader screen. When I tried to use 'Nexus Root Toolkit' to install new system and whenever the process was trying to initiate the process, it is giving me same error message 'FAILED <remote failure>'
What can I do from here?
I appreciate your attention.
chg911225 said:
Good evening, everyone.
Few hours ago, my N6 randomly shut down and not booting up to the system. I tried to re-install the factory image for 5.0.1 but I got stuck at bootloader screen. I tried every options available from bootloader screen(Start, Recovery mode, Restart bootloader etc.) but it performed nothing but coming back to the bootloader screen. When I tried to use 'Nexus Root Toolkit' to install new system and whenever the process was trying to initiate the process, it is giving me same error message 'FAILED <remote failure>'
What can I do from here?
I appreciate your attention.
Click to expand...
Click to collapse
If your bootloader is unlocked, you should be able to either flash the stock factory image, or re-flash each partition separately through the tool-kit. Since you're getting remote errors with the toolkit, double check that you have the right drivers installed, the tookit and a search on the forum should help with that.
did you already try :
http://forum.xda-developers.com/nexus-6/general/guide-flash-factory-images-nexus-6shamu-t2954008
Don't want to raise any alarms already but I shut mine down on Sunday night (Unlocked/ Rooted/ custom kernel & rom) in order to boot in Recovery and flash a new kernel version and:
1) The sdcard looked empty, it read ~ 26 GB free (I had no more than 20 gb free before reboot) and no folders whatsoever.
2) The phone was stuck at the Google logo heating up but going nowhere.
As I said don't want to start assuming things but the phone randomly going "nuts" and losing all data is scary... I had to spent my entire day yesterday flashing stock 5.0.1 back and re-setting up everything. I followed the guide posted above (http://forum.xda-developers.com/nexus-6/general/guide-flash-factory-images-nexus-6shamu-t2954008 oh, go with Method 2 and it will work fine).
Out of curiosity how does your SD look like from recovery? Oh, but then you say you can't even boot to Recovery. Which recovery do you have? (I had/have TWRP 2.8.3.1 ). Anyway to repair it you only need to be able to boot into Bootloader properly I guess.
I was following instructions on rootjunky.com for unlocking and rooting. I successfully unlocked bootloader with sunshine app. Then I flashed TWRP and got it running. But TWRP didn't have the swipe to allow changes to system partition on startup, so I thought I needed to flash system image per the rootjunky video. I figured it couldn't hurt even if it wasn't needed. so I flashed the 10 parts of system image per video and then tried to get to recovery but just saw little dead android flash on screen every few seconds. I have tried holding all combinations of buttons but after unlocked bootloader warning comes up I get lying down android that says "No command" that flashes briefly every few seconds. Am I totally screwed?
All the messages in the command prompt window while flashing all 10 of the system chunks looked nominal ("sending system ... OK ... writing system ... OK", and my batch file looked just like the one in the video.
Any help is appreciated.
Wait. I gave up too soon. Looks like I can get back to fastboot. Somehow TWRP got messed up. I just reflashed TWRP. Whew! Looks like system flash was bad. I'll try flashing system again.
No joy. I have TWRP now, but still can't get system running. When I try to reboot to system from TWRP it comes back to TWRP. I had verified md5sum of system before flashing, so I know that file downloaded ok. Also, adb doesn't see phone when in recovery. I'll keep trying stuff.
Update: I double checked the mda5sum on the system image zip and it was (still) good. Then I re-extracted the ten image chuncks and re-flashed. Now I can boot to system from bootloader and all is as it was before this misadventure. Almost. If I power down phone and then power up I get the dead android with the "No command" message. It just comes on and stays on rather than flashing, so that's an improvement. From there I can get back to the bootloader and then select "Start" to boot up the phone. I can live with that, but it's an annoyance. If anyone has any suggestions to how to make it boot up by itself from power on I'd love to hear them.
Reflash your phone with Verizon Software Update http://www.verizonwireless.com/support/knowledge-base-116673/ and then flash TWRP (fastboot flash recovery twrp.img)
It does't affect your unlocked bootloader.
Thanks, Aptahar, but I have a new theory. I started a new thread here http://forum.xda-developers.com/droid-turbo/help/device-encryption-question-issue-t3283333.
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_