Hello XDA Devs,
I have seen a ****load of posts about this, but I haven't found a solution yet.
Thing is, I can get to the screen where it says that the bootloader is locked, the one where you get to choose to boot in recovery mode etc.
I can get a bit further, a screen with the red triangle android on it's back. When I hold the power button and press Vol+ I get text that the cache can't be loaded. Tried wiping and factory reset, same error.
Now the solutions that I've found are all "flash the ROM" etc. etc.
But my bootloader is locked. Every single guide says that you need to enable dev mode and then unlock it, but since my tab won't turn on, I can't enable it. Any suggestions as to what I should do? The tab was bought in the USA, and I live in Lithuania at the moment, pretty sure the warranty has ended ages ago and the shipping would be ridic anyway. It's the earlier version of the N7.
HALP GUISE
Related
I rooted my N10 using CF-Auto-Root without unlocking the bootloade (on purpose). The N10 has been working fine and I loaded 10G of personal files. Then I sideloaded an old version of the LBE privacy guard. It installed, but then when I returned to the homescreen I got bootlooped.
I turn it off and back on, and I got the dreadful android-with-red-triangle saying "no command".
I could get into the recovery mod using power+volume up/down. "Restart bootloader" got me back to the recovery manual; "recovery mode" or "start" got back to the red triangle. I was able to turn it off. The battery is at 80%.
Is there a way I can wipe my N10 and do a factory reset? I did not unlock my bootloader; is that why I can flash a factory image?
Since I can't boot up the N10, at this point I probably can't use adb to remove the bad apk?
I'd prefer not to unlock the device, in case I need to RMA back... And I'd rather not return it at all, since I just uploaded lots of personal info...
Your help is **most** appreciated.
I think that if you press power, volume up and volume down at the red triangle screen it will get you to the stock recovery. You should read the stickies in the two development sections lots of people needing to do factory resets after unlocking.
Sent from my Nexus 10 using xda app-developers app
Sounds like you are getting into fastboot mode fine, so worse comes to worse, you can unlock it, flash a factory image and re-lock it ..
Of course doing that you are going to loose all your data ..
Check out the tut's for flashing factory from fastboot, or you could use mskip's toolkit ..
Hey guys,
I recently went to power on my Nexus 7 (2013) after a weekend of having it off, and it got stuck on the white Google start up screen with no further responses. Holding power the devices still turns off, and I am able to get into Bootloader and Recovery. From bootloader "start" just sends it back to the Google start up screen. I'm able to enter Recovery but the Android logo with the red warning triangle doesn't have the No Command script below it, Power and Vol. Up gets me into the Recovery menu. Entering recovery I get errors of : Can't open, failed to mount, can't mount etc which continues as I try to clear the cache, and wide the partition (I'd post pictures but I can't as a new poster). Moving on I tried some of the guides to flashing a new factory image with fastboot or Adb. Since I don't have normal access to the device I'm sure sure is USB debugging was enabled or not, but in bootloader that shouldn't matter correct? Anyways here is where I hit my snag, my device is still in LOCKED bootloader, and the fastboot oem unlock command gets me to the unlock bootloader screen, but after I select and confirm the option the device freezes and no progress is made. From that screen I am still able to turn it off by holding the power button down, so I'm somewhat confused about it becoming unresponsive to the unlock bootloader command. All of the other fastboot commands like fastboot erase cache come back with "Failed: Too many Links". From my knowledge I've checked through everything I can do software wise, and I was curious if you guys had any input before attributing this all to a hardware failure? I've got some experience rooting and flashing custom ROMS on my phone so I have somewhat of an understand of all this but its by no means vast. Thanks for the help, and I tried to provide you with as much info as possible but I'll attempt to answer additional questions to the best of my ability.
Stock Nexus 7 2013
Version : KTU84P
Bootloader: Locked, FLO-04.02
scbikep2 said:
Hey guys,
I recently went to power on my Nexus 7 (2013) after a weekend of having it off, and it got stuck on the white Google start up screen with no further responses. Holding power the devices still turns off, and I am able to get into Bootloader and Recovery. From bootloader "start" just sends it back to the Google start up screen. I'm able to enter Recovery but the Android logo with the red warning triangle doesn't have the No Command script below it, Power and Vol. Up gets me into the Recovery menu. Entering recovery I get errors of : Can't open, failed to mount, can't mount etc which continues as I try to clear the cache, and wide the partition (I'd post pictures but I can't as a new poster). Moving on I tried some of the guides to flashing a new factory image with fastboot or Adb. Since I don't have normal access to the device I'm sure sure is USB debugging was enabled or not, but in bootloader that shouldn't matter correct? Anyways here is where I hit my snag, my device is still in LOCKED bootloader, and the fastboot oem unlock command gets me to the unlock bootloader screen, but after I select and confirm the option the device freezes and no progress is made. From that screen I am still able to turn it off by holding the power button down, so I'm somewhat confused about it becoming unresponsive to the unlock bootloader command. All of the other fastboot commands like fastboot erase cache come back with "Failed: Too many Links". From my knowledge I've checked through everything I can do software wise, and I was curious if you guys had any input before attributing this all to a hardware failure? I've got some experience rooting and flashing custom ROMS on my phone so I have somewhat of an understand of all this but its by no means vast. Thanks for the help, and I tried to provide you with as much info as possible but I'll attempt to answer additional questions to the best of my ability.
Stock Nexus 7 2013
Version : KTU84P
Bootloader: Locked, FLO-04.02
Click to expand...
Click to collapse
A clear explanation of the problem alone with everything that you have tried will do for reporting hardware/software issues and also help others help you.
Sent from my Nexus 5 using Tapatalk
Hi,
My Nexus 4 is stuck in the Bootloop (where the Colored Dots fly around that should form the Logo) and I don´t know hat to do anymore. I´ve read dozens of threads but not a single Solution could be found...
I tried several Factory Resets and Cash Wipes with the Recovery Mode and Flashing Stock Android on it. I also just let it try to boot up over night, but after 8hours it was still stuck in the same Bootloop.
I´ve never Rooted my Nexus or something like that it was Stock Android all the time (haven´t used it since like half a year, when the Bootloop appeared first, but now i broke the Screen of my Galaxy Alpha which is too expensive for me to let it fix...).
One Thing thats different from many other People that get stuck in Bootloop is the fact, that after Holding the power button to power it down, i can enter the bootloader (where i can find recovery mode) if i only push the volume down button, not the power button. I also have to go into bootloader and select "power down", if i don´t want it to try and boot up again without me doing anything.
I apologize for my bad English (if it is, i´m not sure) and i´m thankful for every hint on what i could do, since Walking aroung without a Smartphone feels weird as f*ck
Greetz,
Slix
Slix37 said:
Hi,
My Nexus 4 is stuck in the Bootloop (where the Colored Dots fly around that should form the Logo) and I don´t know hat to do anymore. I´ve read dozens of threads but not a single Solution could be found...
I tried several Factory Resets and Cash Wipes with the Recovery Mode and Flashing Stock Android on it. I also just let it try to boot up over night, but after 8hours it was still stuck in the same Bootloop.
I´ve never Rooted my Nexus or something like that it was Stock Android all the time (haven´t used it since like half a year, when the Bootloop appeared first, but now i broke the Screen of my Galaxy Alpha which is too expensive for me to let it fix...).
One Thing thats different from many other People that get stuck in Bootloop is the fact, that after Holding the power button to power it down, i can enter the bootloader (where i can find recovery mode) if i only push the volume down button, not the power button. I also have to go into bootloader and select "power down", if i don´t want it to try and boot up again without me doing anything.
I apologize for my bad English (if it is, i´m not sure) and i´m thankful for every hint on what i could do, since Walking aroung without a Smartphone feels weird as f*ck
Greetz,
Slix
Click to expand...
Click to collapse
Is your bootloader unlocked? When you said you flashed stock do you mean you flashed a zip in recovery, or flashed it via fastboot?
I unlocked my bootloader and used the wugfresh toolkit to flash stock 5.1.1. in my nexus.
After hours of online search i finally found out how to "solve" my Problem. Apparently my power button was stuck (wrote sth. like that in my 1st post but wasn't sure yet), so i just slammed it on the desk with the side where the powerbutton is located and it worked!!
I think thats something you should tell everyone who is stuck in a bootloop an not even reflashing stock Android helps
Now i got the Problem that i can't fit my nano sim in the micro sim slot of the nrxus , wouls be nice if someone got an advice in this, but maybe i should just go and get an Adapter tomorrow
Greetings, Slix
If you do not have any data on it, you can reflash the whole device by downloading the nexus 4 factory image here https://dl.google.com/dl/android/aosp/occam-lmy47v-factory-b0c4eb3d.tgz
You will need adb and fastboot which you can get here http://forum.xda-developers.com/showthread.php?t=2588979 (if the latest version does not work use version 1.3)
Then simply unzip the factory image with 7zip and run
Code:
flash-all.bat
as admin
Hi all,
Apologies if this has been posted before elsewhere in the forum, I've done some searching but I'm having a real hard time in getting this fixed.
My friend recently bought a Huawei P10 Plus off Facebook, second hand. He went to the guy's house, bought it and then didn't realise until he got home that it was a demo unit and on the back it says "NOT FOR SALE"
He went back to the house and the guy was nowhere to be seen and now they deny all knowledge of selling it.
So, unable to use it without a 15 second timeout going to a demo video - he gave it to me. I've got some experience of unlocking bootloaders, rooting etc. and I thought that I'd give this a bash.
The Vendor Country Info was locked to Country: Demo - so no firmware upgrades would work.
I got the bootloader unlocked (thanks Huawei Israel - no telephone verification) and then installed TWRP. I then proceeded to modify the oeminfo to set the correct country. This restarted the phone and now it's effectively bricked.
When I power it on, I get two options: eRecovery mode (which is useless) or hold down Vol Up, Vol Down + Power to get the EMUI manual updater.
No firmware files are working with the manual updater and the eRecovery doesn't find any packages to install.
Fastboot doesn't work - hold Vol Down + plug in USB cable just goes to the charging icon on screen. Tried with Power + Vol Down - straight to eRecovery.
Vol Up + Power goes to eRecovery, no standard recovery or TWRP recovery option.
I'm at a complete loss now, I'd be happy to get the demo firmware back on so that I can at least give it back and say "I tried", but I can't seem to get ANY firmware to install.
For information, I'm in the UK - so I'd need VKY-L09C440 firmware.
Any help is appreciated and once again, sorry if I'm reposting stuff - but it's a very particular case.
Anyone have any ideas on this?
Looking to get this resolved ASAP, but just at a real dead end with it all.
Hi there, does anyone have any ideas for this? Tried looking around the site, but can't seem to find any ideas anywhere
Hi, just bought a phone for my son secondhand, it's going to be sold again if I can't fix this! The phone was sold cheap as it had software issues (of course) so I figured I could fix these and get it going (install custom recovery, ROM etc). I'm slightly stumped at the moment, so maybe you can help me.
The phone's defaulting to the bootloader screen, lots of info on this but the key thing I noticed was that it says 'the device is locked status code: 2'.
Clicking 'start' takes me a 'warning unlocked bootloader screen' then it runs through the 'hello moto' startup screen and back to bootloader
Clicking 'recovery' - there is definitely no working recovery on it, I just a get the dead robot with 'no command' underneath.
Clicking 'Factory Mode' allows me so far through the startup (after the bootloader unlocked warning), and you can get so far through setting it up, but because the battery is so low (it's permanently on with the bootloader when plugged in) it never seems to charge up enough, and either way the screen freezes at or around the final setup steps and then it reverts back to bootloader. I thought if I got into developer options and security, I could enable the USB debugging, OEM unlock etc, but no go there.
I've installed Motorola USB drivers but it doesn't seem to be registering on the PC (Windows 10).
There is some suggestion on other forums (less reputable!) that the locked status code may mean the bootloader has been relocked, but this seems contrary to what the phone is telling me.
Any ideas welcome, thanks - it's a lovely phone, just not much use at the moment.
GitManMatt said:
Hi, just bought a phone for my son secondhand, it's going to be sold again if I can't fix this! The phone was sold cheap as it had software issues (of course) so I figured I could fix these and get it going (install custom recovery, ROM etc). I'm slightly stumped at the moment, so maybe you can help me.
The phone's defaulting to the bootloader screen, lots of info on this but the key thing I noticed was that it says 'the device is locked status code: 2'.
Clicking 'start' takes me a 'warning unlocked bootloader screen' then it runs through the 'hello moto' startup screen and back to bootloader
Clicking 'recovery' - there is definitely no working recovery on it, I just a get the dead robot with 'no command' underneath.
Clicking 'Factory Mode' allows me so far through the startup (after the bootloader unlocked warning), and you can get so far through setting it up, but because the battery is so low (it's permanently on with the bootloader when plugged in) it never seems to charge up enough, and either way the screen freezes at or around the final setup steps and then it reverts back to bootloader. I thought if I got into developer options and security, I could enable the USB debugging, OEM unlock etc, but no go there.
I've installed Motorola USB drivers but it doesn't seem to be registering on the PC (Windows 10).
There is some suggestion on other forums (less reputable!) that the locked status code may mean the bootloader has been relocked, but this seems contrary to what the phone is telling me.
Any ideas welcome, thanks - it's a lovely phone, just not much use at the moment.
Click to expand...
Click to collapse
OK, some progress, I have now unlocked the bootloader, so have the UNLOCKED Status Code:3 which is good, unfortunately has not yet helped with my issues. I can't use ADB, but MFastboot tool is working, so can run commands from that (hence me getting to that stage). Tried reinstalling firmware, may try and do this again now bootloader unlocked....
slightly further along...
GitManMatt said:
OK, some progress, I have now unlocked the bootloader, so have the UNLOCKED Status Code:3 which is good, unfortunately has not yet helped with my issues. I can't use ADB, but MFastboot tool is working, so can run commands from that (hence me getting to that stage). Tried reinstalling firmware, may try and do this again now bootloader unlocked....
Click to expand...
Click to collapse
I have now managed to flash stock firmwares using Mfastboot tool, but hasn't unfortunately fixed the boot up issues. However, I have now worked out how to access the recovery, by reading other posts on different Motorola phones:
boot to bootloader, power+vol down
in bootloader select recovery using the volume up/down buttons, press power button to select
phone boots into 'recovery,' showing the dead android with no command
at this point hold down the power and volume up, then release volume up but keep power held down
phones boots, by magic, into android recovery, where you can factory reset, wipe cache adb sideload and install from SD card
I now need to try and get a flashable recovery to sideload, as the attempts to flash it don't work for me. The OS I seem to be on is reteu 7.1.1, so I will try and go for a lower version, and see if that allows me to flash the custom recovery I desperately need.
But....things are improving slowly....:laugh:
GitManMatt said:
I have now managed to flash stock firmwares using Mfastboot tool, but hasn't unfortunately fixed the boot up issues. However, I have now worked out how to access the recovery, by reading other posts on different Motorola phones:
boot to bootloader, power+vol down
in bootloader select recovery using the volume up/down buttons, press power button to select
phone boots into 'recovery,' showing the dead android with no command
at this point hold down the power and volume up, then release volume up but keep power held down
phones boots, by magic, into android recovery, where you can factory reset, wipe cache adb sideload and install from SD card
I now need to try and get a flashable recovery to sideload, as the attempts to flash it don't work for me. The OS I seem to be on is reteu 7.1.1, so I will try and go for a lower version, and see if that allows me to flash the custom recovery I desperately need.
But....things are improving slowly....:laugh:
Click to expand...
Click to collapse
Never try to downgrade using stock firmware.
tyamamoto said:
Never try to downgrade using stock firmware.
Click to expand...
Click to collapse
OK thanks, I read that, but didn't realise it was a thing....should I be able to sideload a custom rom using ADB?