Database Users

Nexus 10 stuck in boot loop.. please help!!!

So, I was using Zedomax's how to root N10 tutorial (http://www.youtube.com/watch?feature=player_embedded&v=wVlI-gWppCA#at=261)... I had everything working fine up until about 4:15 in the video when his restarts mine just gets stuck in boot loop and displays the nexus bootloader for an unlimited amount of time. My device does however show that it is unlocked because when I go back through the process it says it is already unlocked as you can see in the pictures. the first is the cmd I used and the second is what the N10 shows after "fastboot oem unlock"... I am completely lost and have tried over and over to find the problem... I have tried to unroot and restore but I cant even find a working file that isnt malicious... ANY AND ALL HELP OR SUGGESTIONS WOULD BE APPRECIATED...

Andrololol said:
So, I was using Zedomax's how to root N10 tutorial (http://www.youtube.com/watch?feature=player_embedded&v=wVlI-gWppCA#at=261)... I had everything working fine up until about 4:15 in the video when his restarts mine just gets stuck in boot loop and displays the nexus bootloader for an unlimited amount of time. My device does however show that it is unlocked because when I go back through the process it says it is already unlocked as you can see in the pictures. the first is the cmd I used and the second is what the N10 shows after "fastboot oem unlock"... I am completely lost and have tried over and over to find the problem... I have tried to unroot and restore but I cant even find a working file that isnt malicious... ANY AND ALL HELP OR SUGGESTIONS WOULD BE APPRECIATED...
Click to expand...
Click to collapse
I can help you get back to stock, that should fix everything. You will erase everything and have to start whatever you were working on again. So back it up before hand if you can.
So first you need to be sure you have TODAYS latest updates to the fastboot.exe program, do this by installing the SDK from Google, then launching the update manager and doing all updates. See this post:
http://forum.xda-developers.com/showpost.php?p=38961605&postcount=5
Then you need to do what styckx says. Be sure to click 'Thanks' under his posts. The only thing that you may find is hard to understand is, if you download that from Google and it end up as .tar you have to rename it to .tgz to have it extract correclty. See this post:
http://forum.xda-developers.com/showpost.php?p=38091931&postcount=210
EDIT - If you did oem unlock and were stuck at the X bootlogo then there is an easier fix than what I describe. You state you are stuck at bootloader. Just FYI
Good luck!

bigmatty said:
I can help you get back to stock, that should fix everything. You will erase everything and have to start whatever you were working on again. So back it up before hand if you can.
So first you need to be sure you have TODAYS latest updates to the fastboot.exe program, do this by installing the SDK from Google, then launching the update manager and doing all updates. See this post:
http://forum.xda-developers.com/showpost.php?p=38961605&postcount=5
Then you need to do what styckx says. Be sure to click 'Thanks' under his posts. The only thing that you may find is hard to understand is, if you download that from Google and it end up as .tar you have to rename it to .tgz to have it extract correclty. See this post:
http://forum.xda-developers.com/showpost.php?p=38091931&postcount=210
EDIT - If you did oem unlock and were stuck at the X bootlogo then there is an easier fix than what I describe. You state you are stuck at bootloader. Just FYI
Good luck!
Click to expand...
Click to collapse
yes, it is stuck at nexus symbol "X" loading screen.. you say there is an easier fix for that?

Andrololol said:
yes, it is stuck at nexus symbol "X" loading screen.. you say there is an easier fix for that?
Click to expand...
Click to collapse
yes. that is common w/ these after oem unlock. on that fastboot screen you posted, the one you get to by holding the certain key sequence at boot - use the volume keys to select Recovery, then use the start button to boot to that mode. This confuses people because at that point it looks broken - all you see is a triangle with an error X in it (or something like that.) BUT from that screen you access another menu, do this by briefly pressing power volume up and volume down in little spurts. it sounds wierd, but you do that for up to 20 seconds and you'll finally get it. its just hard to enter so you have to do it like that otherwise you go crazy trying. once you've accessed that menu you will know because its all text. using the navigation choose 'factory wipe' and wipe it. after that your N10 will boot like normal. be aware - navigation on that text only menu is tricky.

Nexus 7 no command bootloop

Hi,
I am trying to fix a friends Asus Nexus 7 WiFi tablet, the issue being that they tried to do an update, and now it doesn't boot, it just shows the google logo, then goes to "no command" for a second, then reboots. I have decent knowledge when it comes to fixing this type of thing as I have rooted and customised pretty much every device I have, however I cannot get into bootloader mode/menu and cannot access recovery, is there anythihng I can try or this unit completely dead? I am not sure which update they were trying to do but at this point I do not think there is any ROM on the device itself.
Any advice would be appreciated.
Many thanks,
EDIT: Can get to bootloader, but when selecting reboot to recovery gives me the "boot failed.." error. Cannot unlock bootloader either, it just stick on "unlocking bootloader..." for a while then stays saying locked, even if I reboot

Mega Bricked 7X - Calling out all Senior/Pros for HELP!!

HI, I will get right to the point. My phone is Honor 7x (BND-AL10C675 INDIAN) I screwed it up.
Now, the fastboot or recovery or E recovery nothing works!!
There is only one screen which keeps coming in a loop rebooting with a vibration
It says " ERROR MODE"
ATTENTION!
PLEASE UPDATE SYSTEM AGAIN
ERROR! FUNC NO : 8 (HIFI IMAGE)
ERROR NO : 1 (SECURITY VERIFY FAILED)
It keeps rebooting and the phone doesn't even turn off. I tried the download mode (Volume UP & Down Power button, SAME SCREEN comes up)
Let me know if you want me to write a detailed version of how I got here or ask any specific questions.
Now, all I need is at least FASTBOOT so I can do something about it. Is there anyone who can help? I hope SOME PRO OR A GEEK is able to solve this issue magically. I just can't tell you what I'm going through.
UPDATE:
As Christo31 requested and maybe it's useful for other people to help me out. Here is what I did. It's a real long story!!
I have Honor 7x (BND-AL10C675 INDIAN) I had unlocked bootloader and twrp and I was on emui 8 beta which I flashed manually using one of the tutorials here on the forum. One day, I decided to get back to stock as I was stuck in emui 8 beta and no OTA updates so I downloaded the emui 8 stable rom from firmware finder and put it in sd card "dload" folder. Now, for this method to work, we need to relock bootloader and flash stock recovery which I did and it completely wiped everything out.
Now, the "dload" method fails at 5% every time. I tried different roms for this very model but no it doesn't work. (Also, my build no. was stuck at B141 for a long time no matter what rom I changed : Yes, this is stupid, I should have fixed it first) Maybe that's why the "dload" method doesn't work.
So, in this forum I saw some with similar issue but somewhat different " Frp locked & bootloader unlocked" and I was told that the DC phoenix software might fix this and I bought some credits and used the software. Here's what I discovered
My observations with the software:
* I put the phone in fastboot and downloaded the update.app full Ota (same one emui stable) and tried to flash. The software flash well ok as it says "the software is written" but the phone doesn't boot and goes directly into the recovery mode and again the bootloader and frp are locked.
*Here, I noticed that it shows something like "opening backdoor" and then the Bootloader status goes to red and says "UNLOCKED" it means it was definitely doing something so the next I repeated the same process but as soon as the phone was "UNLOCKED", I pulled the usb cable out and I kept my command ready and tried "fastboot flash recovery_ramdisk recovery.img" and guess what it flashed that twrp file and I could see in the command line that it went "okay" so I immediately booted to recovery but again the stock recovery comes up. Also, I tried system.img also it flashes fine but phone doesn't boot. Same recovery.
REMEMBER: THE ABOVE STEPS MAY WORK FOR PEOPLE WHO HAVE UNLOCKED BOOTLOADER BUT FRP LOCKED. IN MY CASE BOTH ARE LOCKED SO THAT'S THE DIFFERENCE.
* I tried another update.app I guess it's BNDL22.ZIP or something and this time the software was trying to flash in "upgrade mode" and somehow the recovery was broke. There was some "ERROR MODE" basically the recovery was broke. I didn't care much. Although flashing another update.app would have fixed it.
* The next step I tried after a lot of trial & error for about 1.5 days. This time I did the same when the bootloader was unlocked, I pulled the cable and tried the command "fastboot oem unlock unlock code" ( I should have got this idea before, I mean it's a mess guys, I didn't sleep for too long) and I was shocked to see that it showed the options "Unlocked bootloader yes or no" and I clicked "yes" and I jumped hoping that it's over but... I ended up with 'ERROR MODE' which I described above.
* I feel, because the recovery was broken, it ended up in error mode. Just imagine if my recovery was fine and then I tried this command then it would have erased everything and maybe I might have been presented with fastboot screen with both "frp & bootloader Unlcock" or at least 'bootloader unlock" in either way, I could have flashed a 'system.img' and get into settings and BEATH THE HELL OUT OF THAT "ENABLE OEM UNLOCK' in settings. The rest you know.
I wrote this not just because someone might help me but because a lot of posts on this forum really helped me a lot and posts like these can help a lot of people down the road.
Now, my phone is still in the same loop. Reboot, Honor logo, Error mode...REPEAT
I heard that once the phone drains down completely, we may get back fastboot. Fingers crossed. Sadly, I have Mac so I borrowed windows laptop for this purpose from a friend. This is the last day and I guess I'm going to put it on sale and sell it as a scrap or something for display and stuff.
How much does motherboard cost? anyone any ideas? if it's below 4K or about 80$ then I might go for the repair if nothing works!!
I'm going to update on this very soon. Le'ts hope for a miracle. Either way my HONOR 7X IS A LEGEND.
UPDATE :
After waiting for hours, my phone got discharged and I curiously plugged in the phone pressing "volume down" button OR power + volume and all other types of combinations but the phone just goes to the same "ERROR MODE' and keeps going in the same loop.
So, I really hate Huawei for not providing stock firmware or some type of recovery for people like me to get back to stock. For example : Xiaomi has that fastboot ROMS which you can easily flash in EDL mode no matter what happens to you and of course some other ways to recovery the bricked phones.
The Huawei E recovery?? What the **** is it? Does it ever work? It's some kind of a joke. The hisuite is again **** It says 'My model is not supported" and it only showed me two very older and ancient models that are supported for recovery.
I'm not expecting warranty but at least they should give the service for the customer. Did I tell you that this phone was in Service centre for three days when it had FASTBOOT, RECOVERY, E RECOVERY working. They could n't fix it in 3 days so I rushed them to get my phone back hoping that I would recover it with the above method.
Now, I got the Redmi Note 5 Pro and my 7X is a dead brick and I'll try selling it as scrap for display etc...
Finally, I really love the XDA forums and the friendly members who are very helping and so empathetic. Thanks guys, you are the best
I'm not leaving. I'll see you on the other side. I mean, the Redmi Note 5 pro development. Keep hustling

You need to tell us what you did exactly first for any help

Thetpcguy said:
ERROR! FUNC NO : 8 (HIFI IMAGE)
ERROR NO : 1 (SECURITY VERIFY FAILED)
Click to expand...
Click to collapse
when you are in this situation
- Keep press "volume down" + "power button" for about 10 seconds, the phone will reboot
- When the phone reboot, release the "power button" but keep "volume down" and in the same time plug the micro usb cable ( you have to be ready and quick )
the phone will boot in FASTBOOT&RESCUE MODE ( hope you have unlocked bootloader and frp unlocked )

azerty11 said:
when you are in this situation
- Keep press "volume down" + "power button" for about 10 seconds, the phone will reboot
- When the phone reboot, release the "power button" but keep "volume down" and in the same time plug the micro usb cable ( you have to be ready and quick )
the phone will boot in FASTBOOT&RESCUE MODE ( hope you have unlocked bootloader and frp unlocked )
Click to expand...
Click to collapse
Hi, thanks for your help but the phone doesn't turn off. it just keeps rebooting and there is honor logo and then error mode and then phone reboots and the same cycle. I tried what you said also with other possible things but I guess I need to let the battery drain out completely as some people said it worked for them. It's almost 9 hours and it's still not drained (it was on full charge) anyway Fingers Crossed!!

christo31 said:
You need to tell us what you did exactly first for any help
Click to expand...
Click to collapse
HI, I Updated the post in full details. I hope my phone is rescued.

Let the battery drain, and then try to get into fastboot using key combinations. Let me know if you can do this, from there on you can proceed normally.

vaasu_g_wills said:
Let the battery drain, and then try to get into fastboot using key combinations. Let me know if you can do this, from there on you can proceed normally.
Click to expand...
Click to collapse
It didn't work out. It only boots in error mode and keeps going in a loop.

Thetpcguy said:
It didn't work out. It only boots in error mode and keeps going in a loop.
Click to expand...
Click to collapse
Did you try huawie suite system recovery??

vaasu_g_wills said:
Did you try huawie suite system recovery??
Click to expand...
Click to collapse
I never heard of it I'm googling it now and please throw some light on this but strangely your message got my hopes up.
UPDATE: Oh, I guess you are talking about Huawei Hisuite. I did try that and it didn't work and I included that in my post above as well. I still have my phone with me completely discharged.

Thetpcguy said:
I never heard of it I'm googling it now and please throw some light on this but strangely your message got my hopes up.
UPDATE: Oh, I guess you are talking about Huawei Hisuite. I did try that and it didn't work and I included that in my post above as well. I still have my phone with me completely discharged.
Click to expand...
Click to collapse
and with phone , off, totaly discharged, holding volume down, and plugging in the usb cable , just gives you same error mode?

---------- Post added at 10:59 PM ---------- Previous post was at 10:27 PM ----------
[/COLOR]Follow this steps.
1. Just flash with Dc phoenix
3 extract two update. App with huwai firmware extractor.
4. Check the log of dc phoix. Check which files are not flashed. By comparing with extracted files You will observe some files are not flashed. (some files are not in log of dc phoinix) Like Vendor.img product.img cust.img etc.. Note down which imgs are not flashed..
5. Now use multitool and go to unbrick option. There will be option of flashing around 5 img. Flash the 5 imgs. You will get this 5 img from extracting Update.app
6.then your phone will be working but not perfectly. Flash TWRP with fastboot.
7. Aftee flashing TWRP flash all other imgs which were not flashed by dc phoenix.
Then boot. Your phone must be good.
And again if you want then re flash with HWOTA tool. Your phone will be running now.

mrmazak said:
and with phone , off, totaly discharged, holding volume down, and plugging in the usb cable , just gives you same error mode?
Click to expand...
Click to collapse
Yes, even after that it give the error mode and goes on the same loop. Honor log, Error Mode, Reboot...REPEATED LOOP
I Already gave up on this phone but only a miracle can save this phone now.

Thetpcguy said:
Yes, even after that it give the error mode and goes on the same loop. Honor log, Error Mode, Reboot...REPEATED LOOP
I Already gave up on this phone but only a miracle can save this phone now.
Click to expand...
Click to collapse
i more question for you. Please . Does the three button combo from power off attempt to show update screen. I know for everyone the dload method is failing at 5%, but still need to know if yours is attempting this or not even try.
There might be dload method that works, according to posts on 4pda.ru

mrmazak said:
i more question for you. Please . Does the three button combo from power off attempt to show update screen. I know for everyone the dload method is failing at 5%, but still need to know if yours is attempting this or not even try.
There might be dload method that works, according to posts on 4pda.ru
Click to expand...
Click to collapse
I tried that also. Power+Volume UP+Volume Down to get into download mode but it just goes into that "ERROR MODE'
Normally, it should but maybe because I broke my stock recovery also and then tried to unlock the bootloader when the frp was locked with the DC phoenix trick (Pulling out the plug) that it's really screwed up beyond all this. Let me know if you want me to post pics or maybe if the clips canoe uploaded here, I will make short clip with what's happening. I guess I need some factory or manufacturer level stuff or I need to replace the motherboard. BTW the local guy told me it costs 8K INR which is around 125-130 USD which I'm not willing to spend. I got Redmi Note 5 Pro and I'll probably never ever buy Huawei phones ever.
ANYONE HERE WHO CAN DONATE THE MOTHERBOARD, PLEASE PM ME:laugh:

zte axon7 2017G two phases boot

Hi all, thanks to developers for their good job.
I have a zte axon 7 2017G with an official lineageOS 15.1 and I'm experiencing a weird and annoying boot process each time I reboot the device:
1.- First I see a screen saying push any button before 5 secs
2.- Despite push or not any button, I see a pretty similar screen saying that I have 30 sec to push any button to continue boot process.
If no key is pressed, the boot process start again and again and the device never start up.
Only the volume down button works and I can see more boot options, but even it move the options in wrong direction (from bottom to up), the volume up button doesn't work at all.
I've tried different bootstacks, but the boot process doesn't change.
Is there any bootstack, or aboot image or some "magical" process that I could do to change the boot process into a more working one?
Thanks in advance for the help

Are you serious dude,there are dozen of threads and mentions about this.
On the second screen you press the power button to proceed booting(pinguin logo is normal).just like the bootscreen is saying.
if you dont want this you can use other bootstack

Predatorhaze said:
Are you serious dude,there are dozen of threads and mentions about this.
On the second screen you press the power button to proceed booting(pinguin logo is normal).just like the bootscreen is saying.
if you dont want this you can use other bootstack
Click to expand...
Click to collapse
Hi predartorhaze, thanks for your info. Yes I'm serious, I'm know how to manage to boot my device, but what I want is to change this behavior for a lot of reason, one of them is if the device reboot itself, it will keep booting until exhaust the battery or a human being push buttons.
Please, could you share a link with a bootstack to change this behaviour. As I said, I've tried some, and all of them have the same behaviour.

starvoid said:
Hi predartorhaze, thanks for your info. Yes I'm serious, I'm know how to manage to boot my device, but what I want is to change this behavior for a lot of reason, one of them is if the device reboot itself, it will keep booting until exhaust the battery or a human being push buttons.
Please, could you share a link with a bootstack to change this behaviour. As I said, I've tried some, and all of them have the same behaviour.
Click to expand...
Click to collapse
go here https://forum.xda-developers.com/axon-7/how-to/guide-axon-7-path-to-havocos-2-0-pie-t3869732
and try B20 Bootstack by DrakenFX - Modified by Verequies (Splash or NoSplash)
Read the faq for the difference with splash or no splash

Predatorhaze said:
go here https://forum.xda-developers.com/axon-7/how-to/guide-axon-7-path-to-havocos-2-0-pie-t3869732
and try B20 Bootstack by DrakenFX - Modified by Verequies (Splash or NoSplash)
Read the faq for the difference with splash or no splash
Click to expand...
Click to collapse
Thanks predatorhaze, it works as I expected. I tried the splash version, in order to not to loose EDL mode, just in case. Only one 5 second warning screen shows up and if no one button is pressed, the boot process finish completely instead reboot again.
Only one warning just in case anyone would try it. The pin to unlock the phone is lost, and you would not be able to unlock it.

starvoid said:
Thanks predatorhaze, it works as I expected. I tried the splash version, in order to not to loose EDL mode, just in case. Only one 5 second warning screen shows up and if no one button is pressed, the boot process finish completely instead reboot again.
Only one warning just in case anyone would try it. The pin to unlock the phone is lost, and you would not be able to unlock it.
Click to expand...
Click to collapse
You can unlock pin in twrp.B20 splash does not have warning screen for me,i use it too

VNS-L31 Soft Bricked?

Hello
So the problem - unlocked bootloader, flashed TWRP recovery and here is the catch - flashed the wrong one, for my other phone, Motorola G2.
When i wrote command to the abd to reboot into bootloader my phone become "bricked" - it just goes to show the "your device is booting now... " screen and does not load further.
Is there a way to either
1. flash the correct TWRP recovery? But how to do that if cant get computer to detect a phone....
2. Cancel the last order I have to phone -to reboot into bootloader. I know the first time i wrote it wrong (adb reboot boAtloader) and nothing happend, phone just restarted even when it had flashed wrong TWRP. So Im guessing if I somehow canceled my last order, phone would restart and I would be able to flash the correct TWRP.
As is stands now the phone is displaying the "your device is booting now... " message. If i press any of the known key combinations phone just restarts and go the the same position.
So, how to do anything if I cant get anywhere?
Tnx

windpowah said:
Hello
So the problem - unlocked bootloader, flashed TWRP recovery and here is the catch - flashed the wrong one, for my other phone, Motorola G2.
When i wrote command to the abd to reboot into bootloader my phone become "bricked" - it just goes to show the "your device is booting now... " screen and does not load further.
Is there a way to either
1. flash the correct TWRP recovery? But how to do that if cant get computer to detect a phone....
2. Cancel the last order I have to phone -to reboot into bootloader. I know the first time i wrote it wrong (adb reboot boAtloader) and nothing happend, phone just restarted even when it had flashed wrong TWRP. So Im guessing if I somehow canceled my last order, phone would restart and I would be able to flash the correct TWRP.
As is stands now the phone is displaying the "your device is booting now... " message. If i press any of the known key combinations phone just restarts and go the the same position.
So, how to do anything if I cant get anywhere?
Tnx
Click to expand...
Click to collapse
Hello dude,
you may have missed the opportunity to do
a rollback / reflash, depending on the version of the current system.
This will re-lock the bootloader ...
(no problem to re-unlock if you still have the unlock code )
Informations can be found in main thread
Guides, News and Discussions
> UNIFIED HELP THREAD, post number # 6.
It's just a tip to use as a last resort
before taking it to a service center or...
using it like paperweight ... lol
Cheers

Dadditz said:
Hello dude,
you may have missed the opportunity to do
a rollback / reflash, depending on the version of the current system.
This will re-lock the bootloader ...
(no problem to re-unlock if you still have the unlock code )
Informations can be found in main thread
Guides, News and Discussions
> UNIFIED HELP THREAD, post number # 6.
It's just a tip to use as a last resort
before taking it to a service center or...
using it like paperweight ... lol
Cheers
Click to expand...
Click to collapse
Thank you, worked like a charm .
Now my paper weight is back to being operational. Now I hope I will flash the correct recovery onto it

windpowah said:
Thank you, worked like a charm .
Now my paper weight is back to being operational. Now I hope I will flash the correct recovery onto it
Click to expand...
Click to collapse
Glad your device works again ! :highfive: