Related
Okay, I've seen a lot of "I bricked my Nook Touch" posts around, and floating everywhere but none of their solutions worked. I used the TouchNooter step by step, got the checksum right, did everything right.
Loaded the SD card, restart the nook, BAM! Got stuck on the dreaded "Rooted Forever" screen.
Here's what I've tried so far:
redoing the process
booting without sd card
booting again WITH sd card
8 failed boots
factory reset (bottom left and right and the power button)
30 seconds power button hold, 10 seconds without, 10 seconds holding it down
I think that's about it. i'm just about ready to throw this thing out, seriously. Any other ideas?
I think I'll keep on trying to do the 8 failed boots thing
wajanus said:
Okay, I've seen a lot of "I bricked my Nook Touch" posts around, and floating everywhere but none of their solutions worked. I used the TouchNooter step by step, got the checksum right, did everything right.
Loaded the SD card, restart the nook, BAM! Got stuck on the dreaded "Rooted Forever" screen.
Click to expand...
Click to collapse
As you're able to power down and reboot your Nook I wouldn't even call it bricked. Bricked is when your hardware fails or you manage to screw up your bootloader
I always get stuck on the "Rooted Forever" screen or boot animation when using either Noogie or TouchNooter image, but the process still works, so this doesn't really indicate that something went terribly wrong.
wajanus said:
Here's what I've tried so far:
redoing the process
booting without sd card
booting again WITH sd card
8 failed boots
factory reset (bottom left and right and the power button)
30 seconds power button hold, 10 seconds without, 10 seconds holding it down
I think that's about it. i'm just about ready to throw this thing out, seriously. Any other ideas?
I think I'll keep on trying to do the 8 failed boots thing
Click to expand...
Click to collapse
1,2,3: Unless a simple reboot without the SD card helped this ain't gonna do much good.
4: This usually helps if you can mange to trigger it, it will properly replace both boot and system.
5: This is completely useless. As far as I've seen all it does is clean your /data/app folder and not much more.
6: Never heard of this, can't imagine what it's supposed to do.
One thing you can try the original NookDevs rooting process , see if that kicks your boot into working order again. This is my preffered rooting method.
Your best bet is trying to trigger the 8-failed boot recovery. I've done this a few times on my N2 and it can be a little tricky.
May I ask what version you're running? 1.0.0 or 1.0.1 ?
Thanks.
As far as 6 goes, I saw it on a few forums on the 'net and it was said to break the boot cycle.
I suppose it's not "completely bricked" but I've spent so long with it, trying to get it to work that I'm really, about to ready to throw it away.
I'll try the original guide, hopefully that will trigger it.
It's a 1.0.0, I got it a week after it came out (and it's been bricked since the first TouchNooter came out).
Also, how should I try to do the 8 failed boot recovery? Half the time, it's hard to tell if it's booting, or if it's turned off o.o the only difference I saw is when the Nook is plugged in. Any ideas?
wajanus said:
Thanks.
Also, how should I try to do the 8 failed boot recovery? Half the time, it's hard to tell if it's booting, or if it's turned off o.o the only difference I saw is when the Nook is plugged in. Any ideas?
Click to expand...
Click to collapse
First you need to check whether long pressing power will reboot or just power down you Nook. From my experience a unit that "hangs" on boot will power down when the power button is pressed for at least 10 seconds, while a successfully booted unit will simply reboot.
The following is based on my experience with "hung" units:
Prereqs:
- No USB cable attached (not even charger!)
- No SD Card inserted
Steps:
1: 12 second press (to be sure) for power down
- most likely you'll see no change in the screen!
2: Wait 5 seconds for Nook to settle
3: Press power for 4 seconds to turn it back on
4: Goto step 1 as soon as you see the screen flicker!
- Do not wait for boot animation, a simple flicker is enough!
Repeat 8 times
Also, see this thread for a factory restore image
I wonder, if desperate, whether JTAG could be used.
It is REALLY too bad that some people are so impatient.
When it says "rooted forever", that does NOT mean that the process has completed. It means that the process has ONLY STARTED. Give it some time.
WAIT.
Wait 20 minutes.
It will complete.
Be patient.
If you have to, pull out the battery from the thing.
Then put in the special sdcard.
Plug the battery back in, plug the charge plug in.
Turn on.
WALK AWAY AND COME BACK TOMORROW.
Sorry, but I wouldn't call myself impatient. I pre-charged my nook to full charge before attempting rooting. I left the Nook alone without restarting it until I realized it may need charging again. It was THEN that I tried to restart it.
"WALK AWAY AND COME BACK TOMORROW" <- Yeah, I did that.
However, I do admit, I was expecting a quicker root/rom flash I'm used to my Samsung Vibrant
ros87 said:
First you need to check whether long pressing power will reboot or just power down you Nook. From my experience a unit that "hangs" on boot will power down when the power button is pressed for at least 10 seconds, while a successfully booted unit will simply reboot.
The following is based on my experience with "hung" units:
Prereqs:
- No USB cable attached (not even charger!)
- No SD Card inserted
Steps:
1: 12 second press (to be sure) for power down
- most likely you'll see no change in the screen!
2: Wait 5 seconds for Nook to settle
3: Press power for 4 seconds to turn it back on
4: Goto step 1 as soon as you see the screen flicker!
- Do not wait for boot animation, a simple flicker is enough!
Repeat 8 times
Click to expand...
Click to collapse
Will try. Currently, my nook doesn't even turn on -.-
wajanus said:
Will try. Currently, my nook doesn't even turn on -.-
Click to expand...
Click to collapse
If you can't get it to work, try nookRestore. It basically tricks the nook into thinking you've restarted eight times already.
wajanus said:
Will try. Currently, my nook doesn't even turn on -.-
Click to expand...
Click to collapse
How do you know it's not turning on?
Thread moved. Development goes in the development section, questions in the general section. Thanks.
okay, fast forward a few months forward. I did figure out that the nook DOES turn on but it's probably stuck on an infinite loop. I was successful in booting several different "recoveries". There was a tool a few months back that removed root. The "recovery" booted but didn't help.
Since then I tried the new CWR and it booted! I was so excited. I did the whole "factory reset" and deleted all of the caches. Didn't help, the screen still showed "Rooted Forever". I tried to use the "Touch Formatter", unfortunately, that didn't help either. I used the TouchNooter again but again, nothing happened.
Any suggestions? I haven't seen a "stock" image or anything like that to boot into anywhere.
If your partitions are still intact and you haven't overwritten your rom-partition by writing a touchnooter or cwm img-file directly to the nook you could try the following:
-Create a sd-card with cwm,
-download nook_1_1_update_cwm.zip from http://code.google.com/p/nst-recovery/downloads/list and copy it to the sd
-boot into cwm
-use the install zip from sd-card function to apply the update.
The nook_1_1_update_cwm.zip contains the original update to 1.1, it is just repacked to be usable with cwm. That means, if you want root, you have to root afterwards.
The nook_1_1_update.zip that you get directly from Barnes & Noble is a standard zip file with with a signature attached to the beginning. You can strip off the first 0x1A8 (424) bytes and open it with any unzipper.
Renate NST said:
The nook_1_1_update.zip that you get directly from Barnes & Noble is a standard zip file with with a signature attached to the beginning. You can strip off the first 0x1A8 (424) bytes and open it with any unzipper.
Click to expand...
Click to collapse
I actually found 7-zip can open it without having to do anything to the zip first.
you guys are AMAZING! I couldn't find the 1.1 anywhere. I'm downloading it and installing it later on today. Will update on progress
Steps work
ros87 said:
The following is based on my experience with "hung" units:
Prereqs:
- No USB cable attached (not even charger!)
- No SD Card inserted
Steps:
1: 12 second press (to be sure) for power down
- most likely you'll see no change in the screen!
2: Wait 5 seconds for Nook to settle
3: Press power for 4 seconds to turn it back on
4: Goto step 1 as soon as you see the screen flicker!
- Do not wait for boot animation, a simple flicker is enough!
Repeat 8 times
Click to expand...
Click to collapse
Steps 1-4 solved an infinite loop loading problem with Nook Simple Touch (firmware 1.1).
okay, that seems to have helped some. The Nook boots into a "Read Forever" with a "starting up" thing on the bottom (basically the way stock looks) instead of "Rooted Forever" but it seems like it's in a bootloop, stays on the same screen and never progresses. I'm going to try the n2T to trigger a factory reset. Hopefully, that'll work :/
n2t did not work. Not sure what to do next.
Hi All, as the title states, I'm currently stuck in a CWM bootloop after trying to applying the new OTA update on my rooted transformer.
I know it was kinda stupid of it.
I tried following the steps posted here, but i can't seem to get adb to push the file through.
I must admit that I'm not very good with using command prompts and i have no idea if I'm doing it right.
Steps I'm sure i'm doing right so far.
I opened up my cmd and cd C:\android-sdk\platform-tools
When typing adb devices, my transformer is successfully recognized as 0123456789ABCDEF OFFLINE
However, the next part got me slightly confused.
I had typed in C:\android-sdk\platform-tools>adb push C:\cwm_recovery-5027_rogue_rburrow-tf101-r1.zip /sdcard/download.
However, i kept encountering the error that the device is offline.
I had also set up a marco to press the up arrow+enter key with a 10ms pause in between followed by a 1 second pause before repeating.
However, the file was still unable to be pushed to the device despite countless tries.
I'm not sure if it's because the line i had entered was wrong or was it due to some other factor.
Would someone be kind enough to help me take a look and see if i had done something wrong?
Thank you very much for your help!
lunzi88 said:
Hi All, as the title states, I'm currently stuck in a CWM bootloop after trying to applying the new OTA update on my rooted transformer.
I know it was kinda stupid of it.
I tried following the steps posted here, but i can't seem to get adb to push the file through.
I must admit that I'm not very good with using command prompts and i have no idea if I'm doing it right.
Steps I'm sure i'm doing right so far.
I opened up my cmd and cd C:\android-sdk\platform-tools
When typing adb devices, my transformer is successfully recognized as 0123456789ABCDEF OFFLINE
However, the next part got me slightly confused.
I had typed in C:\android-sdk\platform-tools>adb push C:\cwm_recovery-5027_rogue_rburrow-tf101-r1.zip /sdcard/download.
However, i kept encountering the error that the device is offline.
I had also set up a marco to press the up arrow+enter key with a 10ms pause in between followed by a 1 second pause before repeating.
However, the file was still unable to be pushed to the device despite countless tries.
I'm not sure if it's because the line i had entered was wrong or was it due to some other factor.
Would someone be kind enough to help me take a look and see if i had done something wrong?
Thank you very much for your help!
Click to expand...
Click to collapse
Damn man sorry to hear that. Def should have flashed stock recovery before applying the OTA. Im sure one of these guys can help you out though good luck!
Sent from my Transformer TF101 using xda premium
pierrekid said:
Damn man sorry to hear that. Def should have flashed stock recovery before applying the OTA. Im sure one of these guys can help you out though good luck!
Sent from my Transformer TF101 using xda premium
Click to expand...
Click to collapse
yeah dude, i realised that after i googled for a fix.
prior to this my experience with OTA updates on rooted+CWM phones had never encounter such problem.
The most that had happened previously was that the update failed to be installed.
I had no idea it could get stuck in a loop i couldnt get out of.
when you're doing adb devices, is your tablet in recovery or off?
try this,
push and hold vol down plus power button
when you see words at top left corner, wait a while till you see options to wipe data or cold boot.
Select cold boot to see ifnyou can boot into OS
baseballfanz said:
when you're doing adb devices, is your tablet in recovery or off?
try this,
push and hold vol down plus power button
when you see words at top left corner, wait a while till you see options to wipe data or cold boot.
Select cold boot to see ifnyou can boot into OS
Click to expand...
Click to collapse
thanks for the tip.
I can't try it right now as I left the tablet at home when I left for work today.
I'll update once I get back home to try it.
baseballfanz said:
when you're doing adb devices, is your tablet in recovery or off?
try this,
push and hold vol down plus power button
when you see words at top left corner, wait a while till you see options to wipe data or cold boot.
Select cold boot to see ifnyou can boot into OS
Click to expand...
Click to collapse
The words are not even popping up for me, it just shows the asus logo and then goes straight into recovery. I go into adb devices and it shows OFFLINE aswell.
:S
baseballfanz said:
when you're doing adb devices, is your tablet in recovery or off?
try this,
push and hold vol down plus power button
when you see words at top left corner, wait a while till you see options to wipe data or cold boot.
Select cold boot to see ifnyou can boot into OS
Click to expand...
Click to collapse
That's what I did when it happened to me. Worked like a charm.
I did the same thing and I'm stuck too.
Sent from my Kindle Fire using xda premium
Same problem here for the same reason...flash ota update on my root tablet....I'm always on cwm recovery when reboot. I'm able to cold boot it when holding.vol down and power but I do I get around this cwm ecovwry bootloop? Thanks
Envoyé depuis mon HTC Glacier avec Tapatalk
lamaqc said:
Same problem here for the same reason...flash ota update on my root tablet....I'm always on cwm recovery when reboot. I'm able to cold boot it when holding.vol down and power but I do I get around this cwm ecovwry bootloop? Thanks
Envoyé depuis mon HTC Glacier avec Tapatalk
Click to expand...
Click to collapse
Same here. The only way I can boot now is VolDown + Power. Another thread recommended flashing some stock-like ROM, but I'd rather not.
Has someone found out how to boot normally?
I have to cold boot everytime my device reboots or it shuts off, which is quite often.
The cold boot method is becoming really annoying.
Thanks!
Found a way!
Hi guys! This is my first post helping somebody
So I found a way to make it boot normally...
What you need to do is to cold boot your device.
Then download from the store Android Terminal Emulator.
Open it up and type in:
Code:
su
Allow SuperUser if prompted.
If you get # then you are good to go!
Now you need to type in:
Code:
echo boot | dd of=/dev/block/mmcblk0p3 bs=1 seek=0
Once it's done, reboot your tablet and you should see a progress bar.
Let it load and once it's done, you have your tablet back!
Hope it works!
Hi guys I'm in trouble!! I have continuos bootloops in recovery. I tryed to flash a rom as usual but always bootlooping adn when I tryed to make a cold boot it remain in the same " colod booting linux ".. I can't restore my backup cause I move it on my memory card and cant restore it! Can I do something? I can't boot anymore... Any suggestions? I can only install the rom I have put in the internal memory..
This was my very first android device and I loved it until I tried rooting it. I did some research and got going. Upon getting into clockwork I flashed my system I thought this was what I was supposed to do...I was very...very wrong. I've been trying to follow this video <not allowed to post it> It's called "Tutorials:Root & Unlock Nexus7 Using Mac"
My problem is now, I'm stuck at the recovery screen and no matter what I do I cannot get out. It won't even show up in adb anymore. I'm really angry at myself right now and I really need help. Please help me before I smash my hands with the Nexus 7.
You can get into adb by using the boot loader. Reboot the device by holding down all 3 buttons and it will go into boot loader
Sent from my Nexus 7 using Tapatalk 2
re;
redundant409 said:
You can get into adb by using the boot loader. Reboot the device by holding down all 3 buttons and it will go into boot loader
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
Once I'm in here though, how can I get back to a Android OS...
No matter what I do..it's recovery. I need help man!
--------
UPDATE: Made it into Clockwork at least. Upon doing so I tried doing a factory reset. Still just recovery. God I am such an idiot! I feel like this isn't even fixable and I just wasted all $250 on this device.
UPDATE #2: I fixed it!!! I'm so proud of myself. I kind of hacked it up to do it. If anyone falls into my hole here's what I've done:
Upon entering clockwork I noticed I had the option to restore from /sdcard/update.zip
This "update" does not exist however. So, I then downloaded Cyanogenmod10 rom. I then ran:
./adb push cm-10-20120727-EXPERIMENTAL-grouper-nemith.zip /data/media
Which pushed the Cyanogenmod10 to /sdcard/
Then I opened adb shell and ran:
cd sdcard
mv cm-10-20120727-EXPERIMENTAL-grouper-nemith.zip update.zip
Then restored on clockwork from /sdcard/update.zip.
I then proceeded to do a standard reset from within ROM manager. I'm back to stock android. I'm saved! Thanks to all who have came to help but didn't know how to fix my stupid problems or have helped.
Sorry but you could still go into fastboot by holding the 3 buttons until you reach fastboot. What you probably did is to hold the button until it reboots instead of holding it a little longer to get in fastboot
Sent from my Nexus 7 using Tapatalk 2
Hey Guys,
I've been on android since the G1. I've troubleshooted all problems I've had since flashing cyanogenmod when he was first on xda. With this Nexus 7, however, I've kept it completely stock.
I've had it for a month and it's been great. Yesterday I downloaded a homeland torrent and watched it. Put it down, came back two hours later and it was on a black screen (it was charged when I left at least to 50% after d/l and watching the video). I pressed the power button and it wouldn't start. I finally held it down for about 30 seconds and then it went to the "Google" screen all in white letters. It stayed there. I tried holding power for 10, 20, 30, 40, 50, 60 seconds and it would just reboot to the google screen. I finally tried to enter fastboot, i was able to, and got excited at being at a functional screen that I went into "recovery" and then the google screen just popped back up. Now I can't even get into fastboot.
I've tried the nexus toolkits but they both need either abd in android or the fastboot screen. I can't get into them. I finally called google play devices support and they said they will email me within two days to replace my nexus 7. However, I'd like to get my stored images, music, videos, etc off of there at the very least (although, I'd much rather fix it and keep it).
Can you guys suggest anything?
tl;dr : Stuck on google screen, can't enter fastboot. Is there anything I can do to make it boot? Option 2: how can I at least take my (emulated /virtual) sd card data out of it?
THANKS!
You are rebooting each time you try fastboot, correct?
Sent from my Nexus 7 using Tapatalk HD
Correct. It goes black for about three seconds then back to Google screen indefinitely
Sent from my HTC VLE_U using xda app-developers app
Bump?
Wow, I see criticism every time someone mentions they're "Bricked." Now that someone finally is bricked--or at least it seems like--no one is saying anything...
What happens if you hold all 3 keys for ~30-40 seconds, it should, at that point, reboot to the bootloader.
If you are in fastboot again (if this would work one time) you can do
Code:
adb pull /sdcard
Because I guess when it's at the google screen
Code:
adb devices
won't give any output?
But I guess it's a hardware problem, otherwise it wouln't just have turned off...
Sent from my SK17i running Android 4.1.2
mihahn said:
If you are in fastboot again (if this would work one time) you can do
Code:
adb pull /sdcard
Because I guess when it's at the google screen
Code:
adb devices
won't give any output?
But I guess it's a hardware problem, otherwise it wouln't just have turned off...
Sent from my SK17i running Android 4.1.2
Click to expand...
Click to collapse
ADB doesn't work in the bootloader.... ADB is Android Debug Bridge, and Android is not booted while in the bootloader.
Op, this seems like one of those weird things where you will just have to keep messing with it and it will hopefully work eventually. Mess with charging, different timing etc.
Sent from my Nexus 7 using Tapatalk HD
Thanks guys!
korockinout13 said:
ADB doesn't work in the bootloader.... ADB is Android Debug Bridge, and Android is not booted while in the bootloader.
Op, this seems like one of those weird things where you will just have to keep messing with it and it will hopefully work eventually. Mess with charging, different timing etc.
Sent from my Nexus 7 using Tapatalk HD
Click to expand...
Click to collapse
Yeah, holding all three, holding power and volume up, holding power and volume down doesn't work. I've tried holding power until it restarts and then doing power and volume down, up, and both. Nada.
I appreciate your input guys. I'll just return the product to google... hopefully they don't fix it without a full wipe and get ahold of my files! Yeek!
AW: [Q] Stuck on Google Screen- Cannot enter fastboot
korockinout13 said:
ADB doesn't work in the bootloader.... ADB is Android Debug Bridge, and Android is not booted while in the bootloader.
Op, this seems like one of those weird things where you will just have to keep messing with it and it will hopefully work eventually. Mess with charging, different timing etc.
Sent from my Nexus 7 using Tapatalk HD
Click to expand...
Click to collapse
On my sony device I can do adb pull when I'm in recovery. And if he would be able to enter fastboot and then the recovery, I thought it could work
But I guess the best is to replace it
Sent from my SK17i running Android 4.1.2
mihahn said:
On my sony device I can do adb pull when I'm in recovery. And if he would be able to enter fastboot and then the recovery, I thought it could work
Click to expand...
Click to collapse
He said he was 100% stock.
The stock recovery doesn't start up the adbd daemon. That's typical for stock recoveries.
Proves the point that even if you stay with stock on the N7, you should unlock the bootloader as soon as you get the device. Then the option of soft-booting a different recovery (fastboot boot recovery.img) would be available for rescue situations - even if the ROM stays completely stock and unrooted.
Don't know exactly where you are......
If you OEM unlocked your device, rooted and flashed a custom recovery....I can assist.
Again going with the notion you did...
When your device is on and showing Google
Press and hold the Power key till the screen goes black
Once black, press and hold the volume down key
This will take you to fastboot
Press volume key up twice then power key to select
Device should now be in recovery mode
If you wiped the OS, use Wugs Toolkit to recover from soft brick in advanced options
If you want to push files to your device and try to recover, use MSKIP's Toolkit
Hope this helps....good luck
Sent from my Nexus 7 using XDA Premium HD app
dwny said:
Don't know exactly where you are......
If you OEM unlocked your device, rooted and flashed a custom recovery....I can assist.
Again going with the notion you did...
Click to expand...
Click to collapse
Nope, not unlocked, rooted or have a custom recovery.
Back story and Issue
Soo when I first got my Axon 7, I've first rooted my phone and got TWRP (but it was stuck with a password) and later on around 1-2 weeks later, a new update came out (Build 29) just not too long today so what I did was try to install it but failed and I couldn't back it up anyways due to a password issue that people were having so later, I saw this post thinking it could removing the password issue by flashing the image with TWRP in the "Install" and press "Install Images" or something like that and and it ask where to install it, I installed it in recovery and proceed to install it. Later on, my phone booted into Android and I decided to go back to TWRP to see if it worked and when I turned off my phone and press Up Volume + Power, it goes to the ZTE boot logo for 1 sec and black screened with a red light or 1 sec and turned off immediately which scared me a lot because I think I just my recovery. So what I did was going back to the original post on where I installed my original TWRP and root and being following the steps by going to adb reboot edl and first enter this command axon7backup.exe -p 4 -d and later use the recovery from Unjustified Dev's post (TWRP 3.0.2-2) and used that for the recovery and typed in axon7root.exe -p 4 -r and when I try to boot my phone, the logo shows up for 1 sec and turns off and when I try the Up Volume and power, same thing and when I try Down and Power, same thing, nothing. Doing adb devices doesn't do anything BUT my Qualcomm Drivers and still see COM5 so when I unplugged my phone and plug it back in, my desktop literally froze up in the worst possible situation I've ever seen and I had to replug my desktop and once I booted my computer, I tried again with axon7root.exe -p 5 -b ( or was it -r.. I forgot) and somehow fixed my phone and my phone was able to boot but the recovery problem still persist. someone help
https://www.youtube.com/watch?v=e9sjILIiFFU
xDaDeevellopar said:
Back story and Issue
Soo when I first got my Axon 7, I've first rooted my phone and got TWRP (but it was stuck with a password) and later on around 1-2 weeks later, a new update came out (Build 29) just not too long today so what I did was try to install it but failed and I couldn't back it up anyways due to a password issue that people were having so later, I saw this post thinking it could removing the password issue by flashing the image with TWRP in the "Install" and press "Install Images" or something like that and and it ask where to install it, I installed it in recovery and proceed to install it. Later on, my phone booted into Android and I decided to go back to TWRP to see if it worked and when I turned off my phone and press Up Volume + Power, it goes to the ZTE boot logo for 1 sec and black screened with a red light or 1 sec and turned off immediately which scared me a lot because I think I just my recovery. So what I did was going back to the original post on where I installed my original TWRP and root and being following the steps by going to adb reboot edl and first enter this command axon7backup.exe -p 4 -d and later use the recovery from Unjustified Dev's post (TWRP 3.0.2-2) and used that for the recovery and typed in axon7root.exe -p 4 -r and when I try to boot my phone, the logo shows up for 1 sec and turns off and when I try the Up Volume and power, same thing and when I try Down and Power, same thing, nothing. Doing adb devices doesn't do anything BUT my Qualcomm Drivers and still see COM5 so when I unplugged my phone and plug it back in, my desktop literally froze up in the worst possible situation I've ever seen and I had to replug my desktop and once I booted my computer, I tried again with axon7root.exe -p 5 -b ( or was it -r.. I forgot) and somehow fixed my phone and my phone was able to boot but the recovery problem still persist. someone help
Click to expand...
Click to collapse
ok what is the problem? if it is TWRP asking for that password I only got away from that by unlocking the phone
tabletalker7 said:
ok what is the problem? if it is TWRP asking for that password I only got away from that by unlocking the phone
Click to expand...
Click to collapse
Well, I can't boot into recovery as it would boot into the ZTE logo for 1 second and turn off but when I boot it up to system or android, it works. Added a YouTube link in the post.
xDaDeevellopar said:
Well, I can't boot into recovery as it would boot into the ZTE logo for 1 second and turn off but when I boot it up to system or android, it works. Added a YouTube link in the post.
Click to expand...
Click to collapse
Mine did that when I tried to re-lock my bootloader (don't ask). I used the goodies in here http://forum.xda-developers.com/axon-7/development/wip-axon-7-root-bootloader-unlokced-t3441204 to install TWRP and then used TWRP to do a factory reset.
tabletalker7 said:
Mine did that when I tried to re-lock my bootloader (don't ask). I used the goodies in here http://forum.xda-developers.com/axon-7/development/wip-axon-7-root-bootloader-unlokced-t3441204 to install TWRP and then used TWRP to do a factory reset.
Click to expand...
Click to collapse
Can you tell me the exact steps? I'm not too good at doing stuff like this though I do have a basic understanding.
nevermind, I fixed it lol but I still have the password issue in TWRP help?
xDaDeevellopar said:
Can you tell me the exact steps? I'm not too good at doing stuff like this though I do have a basic understanding.
nevermind, I fixed it lol but I still have the password issue in TWRP help?
Click to expand...
Click to collapse
I noticed that password on TWRP - it is caused by the factory encryption. I wanted to unlock my bootloader and when I did the unlock, it did away with that problem. http://forum.xda-developers.com/axon-7/how-to/guide-how-to-unlock-bootloader-stay-t3461165 just go slow, the directions are pretty straight forward (if you want to unlock)
tabletalker7 said:
I noticed that password on TWRP - it is caused by the factory encryption. I wanted to unlock my bootloader and when I did the unlock, it did away with that problem. http://forum.xda-developers.com/axon-7/how-to/guide-how-to-unlock-bootloader-stay-t3461165 just go slow, the directions are pretty straight forward (if you want to unlock)
Click to expand...
Click to collapse
What does it mean by "navigate to your adb location."?
Damn, just encounter another problem... wifi...
It's ain't turning on and when I go to the Wifi settings in Settings, all it show is it is turned off with no networks and doesn't say anything beside the 3 dots, Wifi, back button, and the off button for wifi. help?
xDaDeevellopar said:
Damn, just encounter another problem... wifi...
It's ain't turning on and when I go to the Wifi settings in Settings, all it show is it is turned off with no networks and doesn't say anything beside the 3 dots, Wifi, back button, and the off button for wifi. help?
Click to expand...
Click to collapse
Do yourself a huge favor - there is a giant box in the top left of the screen as you read this. It is called a search bar. Everything (and I mean EVERY SINGLE THING) you have asked about thus far has been gone over to COMPLETE EXHAUSTION many times over. I am trying to be nice and help you through this whole process but wow, come on already. http://forum.xda-developers.com/axon-7/how-to/please-check-wifi-flashing-bootloops-t3451544 read this post from front to back, then back to front, and then if you still have questions the people over there odds are have your solution
xDaDeevellopar said:
Back story and Issue
Soo when I first got my Axon 7, I've first rooted my phone and got TWRP (but it was stuck with a password) and later on around 1-2 weeks later, a new update came out (Build 29) just not too long today so what I did was try to install it but failed and I couldn't back it up anyways due to a password issue that people were having so later, I saw this post thinking it could removing the password issue by flashing the image with TWRP in the "Install" and press "Install Images" or something like that and and it ask where to install it, I installed it in recovery and proceed to install it. Later on, my phone booted into Android and I decided to go back to TWRP to see if it worked and when I turned off my phone and press Up Volume + Power, it goes to the ZTE boot logo for 1 sec and black screened with a red light or 1 sec and turned off immediately which scared me a lot because I think I just my recovery. So what I did was going back to the original post on where I installed my original TWRP and root and being following the steps by going to adb reboot edl and first enter this command axon7backup.exe -p 4 -d and later use the recovery from Unjustified Dev's post (TWRP 3.0.2-2) and used that for the recovery and typed in axon7root.exe -p 4 -r and when I try to boot my phone, the logo shows up for 1 sec and turns off and when I try the Up Volume and power, same thing and when I try Down and Power, same thing, nothing. Doing adb devices doesn't do anything BUT my Qualcomm Drivers and still see COM5 so when I unplugged my phone and plug it back in, my desktop literally froze up in the worst possible situation I've ever seen and I had to replug my desktop and once I booted my computer, I tried again with axon7root.exe -p 5 -b ( or was it -r.. I forgot) and somehow fixed my phone and my phone was able to boot but the recovery problem still persist. someone help
https://www.youtube.com/watch?v=e9sjILIiFFU
Click to expand...
Click to collapse
hey, could u please tell me how u managed to boot up ur device again... i've also bricked my a2017g to a point where i can't even boot into edl mode...
i submitted this post - https://forum.xda-developers.com/axon-7/help/a2017g-totally-bricked-t3537990#post70561874