Hi all,
I am experiencing a boot loop (Amazon logo loping) after flashing an img file of TWRP via Flashify. I have tried factory resetting and tried to enter recovery mode but nothing works, connecting to my computer just causes the device to loop. Please help, any suggestions are welcome.
majinken said:
Hi all,
I am experiencing a boot loop (Amazon logo loping) after flashing an img file of TWRP via Flashify. I have tried factory resetting and tried to enter recovery mode but nothing works, connecting to my computer just causes the device to loop. Please help, any suggestions are welcome.
Click to expand...
Click to collapse
What was the last bootloader that you had in there? Which version, 4.5.3, or something else?
bibikalka said:
What was the last bootloader that you had in there? Which version, 4.5.3, or something else?
Click to expand...
Click to collapse
it was 4.5.3. I believe I had 4.5.4 initially and read I had to upgrade to 5.0 and downgrade to 4.5.3 to root, which I did.
majinken said:
it was 4.5.3. I believe I had 4.5.4 initially and read I had to upgrade to 5.0 and downgrade to 4.5.3 to root, which I did.
Click to expand...
Click to collapse
OK, so when you hold "Power" and "Vol+" during boot, TWRP does not come up? Did you flash the right version of TWRP ?
bibikalka said:
OK, so when you hold "Power" and "Vol+" during boot, TWRP does not come up? Did you flash the right version of TWRP ?
Click to expand...
Click to collapse
unfortunately, it goes into the fire system recovery mode
i used the img form this tread: http://forum.xda-developers.com/fire-hd/general/root-v2-0-fireos-4-5-4-gapps-t3150613
is my only option at this time to talk to amazon customer service? thanks for your help.
majinken said:
unfortunately, it goes into the fire system recovery mode
i used the img form this tread: http://forum.xda-developers.com/fire-hd/general/root-v2-0-fireos-4-5-4-gapps-t3150613
is my only option at this time to talk to amazon customer service? thanks for your help.
Click to expand...
Click to collapse
OK, it looks you flashed TWRP into your boot partition instead of recovery! Your only attempt now is to try to sideload 4.5.4 or even 5.2.0 via the stock Amazon recovery. See if it works (use the directions from the 5.2.0 to 4.5.3 downgrade), and supply it with the standard Amazon's bin file. You will lose root, but if this works, you could downgrade via 5.2.0
@bibikalka, do you know how this would happen? Would flashify cause or allow this? thx
DoLooper said:
@bibikalka, do you know how this would happen? Would flashify cause or allow this? thx
Click to expand...
Click to collapse
Yep, I recall that Flashify gives you 2 possible places to put the image, either boot or recovery. Choose the wrong one, and you are in trouble !
Thanks! Finally posted the guide and totally overlooked this. Time to edit! (EDIT: Whew, it's fine. My brain is fried.)
bibikalka said:
OK, it looks you flashed TWRP into your boot partition instead of recovery! Your only attempt now is to try to sideload 4.5.4 or even 5.2.0 via the stock Amazon recovery. See if it works (use the directions from the 5.2.0 to 4.5.3 downgrade), and supply it with the standard Amazon's bin file. You will lose root, but if this works, you could downgrade via 5.2.0
Click to expand...
Click to collapse
the recovery mode has only 2 options: factory reset or reboot. Noob question, how do i sideload another ver. on? my computer does not detect the kindle while it's in boot loop or in recovery mode.
thanks in adv.
majinken said:
the recovery mode has only 2 options: factory reset or reboot. Noob question, how do i sideload another ver. on? my computer does not detect the kindle while it's in boot loop or in recovery mode.
thanks in adv.
Click to expand...
Click to collapse
OK, indeed. It's 5.2.0 recovery that offered ADB sideload option. 4.5.3 does not have it.
At this stage you only have 1 path forward, which is warranty replacement.
bibikalka said:
OK, indeed. It's 5.2.0 recovery that offered ADB sideload option. 4.5.3 does not have it.
At this stage you only have 1 path forward, which is warranty replacement.
Click to expand...
Click to collapse
ah, ok, thanks for your help again.
My Fire HD7 is boot looping and I can't not boot into TWRP recovery mode manually. I always used adb reboot recovery. Can someone tell me how to boot into recovery mode step by step? Thanks in advance!
I doubt this "proper method" will work while in boot loop, but here's it is: Hold down power button until Power Off? prompt appears and say yes. When device is off, press and hold power and volume up buttons at the same time until you see Amazon logo, then let go. If you can't power off, try holding down power and volume+. That may work. And if it doesn't, try holding down all three buttons together.
EDIT: @tacoda, this was for you. (Think I hit quick reply to OP, not to you.)
DoLooper said:
I doubt this "proper method" will work while in boot loop, but here's it is: Hold down power button until Power Off? prompt appears and say yes. When device is off, press and hold power and volume up buttons at the same time until you see Amazon logo, then let go. If you can't power off, try holding down power and volume+. That may work. And if it doesn't, try holding down all three buttons together.
EDIT: @tacoda, this was for you. (Think I hit quick reply to OP, not to you.)
Click to expand...
Click to collapse
Press hold Power + Vol up and release after Amazon sign didn't work nor holding all three buttons.
tacoda said:
Press hold Power + Vol up and release after Amazon sign didn't work nor holding all three buttons.
Click to expand...
Click to collapse
Did you try powering off first? (Sorry, never had bootloop. Can you power off? probably not. Edit: Of course not. I already said ^^ that wouldn't work.)
DoLooper said:
Did you try powering off first? (Sorry, never had bootloop. Can you power off? probably not. Edit: Of course not. I already said ^^ that wouldn't work.)
Click to expand...
Click to collapse
I did power off the device by holding down the power button for 10+ sec. And then I did try to boot into recovery by holding Vol up + Power/Vol down + Power/holding all three buttons non of em works
crap. I just did the same thing with 3! kindle fires hd6 fortunately I got twrp on 2 of them (on recovery) before I rebooted but all three of them I flashed the recovery to the boot.img. anyone have the original boot image I can flash via TWRP?
AlexanderJohn said:
crap. I just did the same thing with 3! kindle fires hd6 fortunately I got twrp on 2 of them (on recovery) before I rebooted but all three of them I flashed the recovery to the boot.img. anyone have the original boot image I can flash via TWRP?
Click to expand...
Click to collapse
So I unpacked the boot.IMG from my 4.5.3 and flashed the two with twrp and they work now. But since I have no option for fastboot or recovery I can't get the device to accept commands. Any help with this?
Sent from my HTC6435LVW using Tapatalk
Related
I bought a used HTC DNA that is S-ON, and does not say UNLOCKED or TAMPERED, but I have not been able to boot into recovery. When i hold volume down and power I just get blinking soft buttons and then the phone reboots. Is there away to flash the stock recovery back on the phone without having to unlock bootloader?
I can adb into hboot via the cli, but i have no options to get into recovery mode. This all started because i wanted to wipe cache.
Thanks.
have you tried "adb reboot recovery"? That should boot you straight into it.
drumz0rz said:
have you tried "adb reboot recovery"? That should boot you straight into it.
Click to expand...
Click to collapse
Edit: figured it out.
Phreak66 said:
Edit: figured it out.
Click to expand...
Click to collapse
If you still need help, download an app called "flash gui" on the market. Download a recovery image, click img on the one of two options, and flash it. Then hold down the volume down and power and it should work.
I wanted to upgrade my Nabi with the latest OTA. I had TWRP 2.2.2.1. I used it to revert to an old backup. After the restore, I tried to apply the OTA updates. After it rebooted and started the install I got an "!" Android logo.
I power cycled and I was able to boot back in. I noticed I still had the Play Store app (which will not work, error about connecting to services) and suspect the "stockunrooted" restore I used may not have been completely "stock". I did lose root and TWRP though.
I tried to reinstall TWRP again, but it appears that Fastboot no longer works since the restore. The tablet just hangs on the Nabi logo indefinitely. When I press Vol - & + with PWR, and select Recovery Mode, I just get another "!" Android logo (is this stock recovery?).
ADB works, it sees the tablet and I'm able to push, access shell etc.
I used motochopper to root the Nabi again. I tried installing flash_image to manually flash a new TWRP recovery.img, but running the command I get an error about "error scanning partitions".
I'm not sure what else I can do to get Fastboot working or a recovery system installed again. OTA upgrade will not apply, and I'm stuck on 1.9.37 at this point.
Does anyone have a suggestion how I can get Fastboot fixed and the Nabi back to "normal" / upgradeable.
Thanks for your help
kaijan said:
I wanted to upgrade my Nabi with the latest OTA. I had TWRP 2.2.2.1. I used it to revert to an old backup. After the restore, I tried to apply the OTA updates. After it rebooted and started the install I got an "!" Android logo.
Click to expand...
Click to collapse
What software rev did you get to when doing the OTA's?
I power cycled and I was able to boot back in. I noticed I still had the Play Store app (which will not work, error about connecting to services) and suspect the "stockunrooted" restore I used may not have been completely "stock". I did lose root and TWRP though.
Click to expand...
Click to collapse
That is usually a sign that various Google services are removed from the system partition. So in that case it is returned to stock, but there is still information of the Play install on the data partition.
I tried to reinstall TWRP again, but it appears that Fastboot no longer works since the restore. The tablet just hangs on the Nabi logo indefinitely. When I press Vol - & + with PWR, and select Recovery Mode, I just get another "!" Android logo (is this stock recovery?).
ADB works, it sees the tablet and I'm able to push, access shell etc.
I used motochopper to root the Nabi again. I tried installing flash_image to manually flash a new TWRP recovery.img, but running the command I get an error about "error scanning partitions".
I'm not sure what else I can do to get Fastboot working or a recovery system installed again. OTA upgrade will not apply, and I'm stuck on 1.9.37 at this point.
Click to expand...
Click to collapse
Usually when it hangs at the Nabi logo it means you don't have the USB cable plugged in or that the fastboot driver is not installed.(Check device manager and see if fastboot driver is installed/no exclimation point). If that's not the issue then it's the bootloader which I have only seen one person have that issue. Depending on which OTA's you have ran there was an update to a Jellybean bootloader so it's possible. That can be fixed with nvflash or placing the bootloader blob in the staging partition.
Also you can always get recovery back without fastboot in Android by dd'ing the recovery over.
For example if the recovery image is on the internal SD
dd if=/data/media/recovery.img of=/dev/block/platform/sdhci-tegra.3/by-name/SOS
aicjofs said:
What software rev did you get to when doing the OTA's?
That is usually a sign that various Google services are removed from the system partition. So in that case it is returned to stock, but there is still information of the Play install on the data partition.
Usually when it hangs at the Nabi logo it means you don't have the USB cable plugged in or that the fastboot driver is not installed.(Check device manager and see if fastboot driver is installed/no exclimation point). If that's not the issue then it's the bootloader which I have only seen one person have that issue. Depending on which OTA's you have ran there was an update to a Jellybean bootloader so it's possible. That can be fixed with nvflash or placing the bootloader blob in the staging partition.
Also you can always get recovery back without fastboot in Android by dd'ing the recovery over.
For example if the recovery image is on the internal SD
dd if=/data/media/recovery.img of=/dev/block/platform/sdhci-tegra.3/by-name/SOS
Click to expand...
Click to collapse
OTA is trying to install 2.1.27
You were correct about the fastboot driver issue. I was using Windows 8.1 and it it wasn't working properly. I switched to Ubuntu and now have no problems.
I was able to flash TWRP 2.3.3 and tried another restore to stock. Did OTA again, but still get the "!" Android shortly after it reboots and starts installing. I can't seem to get rid of gapps either. Play Store is still installed. I've tried wiping /data/media, cache's etc and it still remains.
I'm not sure why the OTA upgrade keeps failing. Do you think it's due to the gapps still being on the device?
Any other ideas on how I can get the OTAs to work?
Update:
I booted up stock recovery and tried the update from cache
Verifying current system...
assert failed: apply_patch_check("/system/app/Gallery2.apk", "4cadedee1defcdc28afc99ea968ebb1e631e7b9", "ee310bfc0d0ad2fe11356b97f8cb6e754aa43f2b")
E: Error in /tmp/sideload/package.zip
(Status 7)
Installation aborted.
Click to expand...
Click to collapse
kaijan said:
OTA is trying to install 2.1.27
You were correct about the fastboot driver issue. I was using Windows 8.1 and it it wasn't working properly. I switched to Ubuntu and now have no problems.
I was able to flash TWRP 2.3.3 and tried another restore to stock. Did OTA again, but still get the "!" Android shortly after it reboots and starts installing. I can't seem to get rid of gapps either. Play Store is still installed. I've tried wiping /data/media, cache's etc and it still remains.
I'm not sure why the OTA upgrade keeps failing. Do you think it's due to the gapps still being on the device?
Any other ideas on how I can get the OTAs to work?
Update:
I booted up stock recovery and tried the update from cache
Click to expand...
Click to collapse
Hmm that is it weird. It does look like gapps is still installed .As gapps removes gallery2.apk and why it's failing, I don't understand if it's stock how that is happening. Use these updates yet? http://forum.xda-developers.com/wiki/Fuhu_nabi_2
This thread died out....I hate to bump it back to the top...But I have a NABI2-NV7A that I rooted along time ago....and i booted it up and was gonna do some upgrades and everything went kaboom!!
I have TWRP 2.2.2.1 installed.
I can get into TWRP but not fast-boot mode
I'm on a laptop with windows 10 installed...I don't think it's driver related....as i can send commands via adb while TWRP is up....and the NABI responds to those commands
But i never get past the logo screen....and I'm not sure what to to do with NVflash.
I'm experienced...but rooted this thing and installed GAPPS like 2 years ago and the kids dug this thing up and the play store wouldn't work any longer....i read about the OTA....so i was trying to go back to stock and get those OTA's.
Any suggestions or advice?? Anyone...hello....bueller....bueller
hotspace said:
This thread died out....I hate to bump it back to the top...But I have a NABI2-NV7A that I rooted along time ago....and i booted it up and was gonna do some upgrades and everything went kaboom!!
I have TWRP 2.2.2.1 installed.
I can get into TWRP but not fast-boot mode
I'm on a laptop with windows 10 installed...I don't think it's driver related....as i can send commands via adb while TWRP is up....and the NABI responds to those commands
But i never get past the logo screen....and I'm not sure what to to do with NVflash.
I'm experienced...but rooted this thing and installed GAPPS like 2 years ago and the kids dug this thing up and the play store wouldn't work any longer....i read about the OTA....so i was trying to go back to stock and get those OTA's.
Any suggestions or advice?? Anyone...hello....bueller....bueller
Click to expand...
Click to collapse
Have you tried using "adb reboot-bootloader"
There are some things to try before breaking out nvflash. The easiest would be to flash the boot loader and a new TWRP in one recovery session.
Boot twrp2.2.21, Install KK boot loader zip and then install TWRP KK287 zip
Then restore the 3.0.13 ROM
Files and directions here
http://forum.xda-developers.com/nabi-2/general/nabi-information-t3229119
aicjofs said:
Have you tried using "adb reboot-bootloader"
There are some things to try before breaking out nvflash. The easiest would be to flash the boot loader and a new TWRP in one recovery session.
Boot twrp2.2.21, Install KK boot loader zip and then install TWRP KK287 zip
Then restore the 3.0.13 ROM
Files and directions here
http://forum.xda-developers.com/nabi-2/general/nabi-information-t3229119
Click to expand...
Click to collapse
I did try ADB REBOOT-BOOTLOADER all that happens is the NABI2 restarts and sits at the logo screen.
I'm able to push via ADB, so I will download the suggested files and take your advice. I'll report back. And, thanks for the reply.
Update...
I was able to push all of the needed files and I verified I pushed them completely by using "adb push -p xxxxxx /sdcard"
I then rebooted back into TWRP
I flashed KK3013bootloader.zip, then flashed twrp-recovery-NV7AUS-287.zip
Rebooted and I can't get back into TWRP. And, now I can't establish a connection for adb commands.
Any advice? tips...pointers? Could this truly be my first bricked device??
hotspace said:
Update...
I was able to push all of the needed files and I verified I pushed them completely by using "adb push -p xxxxxx /sdcard"
I then rebooted back into TWRP
I flashed KK3013bootloader.zip, then flashed twrp-recovery-NV7AUS-287.zip
Rebooted and I can't get back into TWRP. And, now I can't establish a connection for adb commands.
Any advice? tips...pointers? Could this truly be my first bricked device??
Click to expand...
Click to collapse
Nah Nabi2 is practically impossible to brick.
So do you get the command list in the top left when you press the vol and power buttons? i.e the selection continue, fastboot, recovery kernel, forced recovery? or when you select recovery kernel it just doesn't boot TWRP?
I wont type a lot of stuff until I get you answer but if we need to go the nvflash route this is some good reading. You will need to get in to APX mode, install the driver and issue some commands.
Read this post and next few pages after it
http://forum.xda-developers.com/showpost.php?p=46579190&postcount=1687
General idea of commands
http://forum.xda-developers.com/showpost.php?p=48683262&postcount=124
Might be some work, but we should be able to get the device back, I'll let you know which is the best way after I see your reply.
Yup, no boot options. And, I can't get back into TWRP. I hold power button to shut it down. Then vol+ power and typically I'd get the boot options, but nothing, just the logo. Then hold power button to shut down. Continue...repeat...
I appreciate you sticking in for the long haul on this.
Sent from my SM-N920P using Tapatalk
hotspace said:
Yup, no boot options. And, I can't get back into TWRP. I hold power button to shut it down. Then vol+ power and typically I'd get the boot options, but nothing, just the logo. Then hold power button to shut down. Continue...repeat...
I appreciate you sticking in for the long haul on this.
Sent from my SM-N920P using Tapatalk
Click to expand...
Click to collapse
Damn. It IS going to be a long haul, but you will know the tablet well when its done. I don't have the tablet to test anymore, so I have to work from memory(and that's been a long time)
Well the bad news is this is going to require opening the tablet. See this post http://forum.xda-developers.com/showpost.php?p=46694284&postcount=1701
You are going to have to short those pins to get it in to APX mode and use nvflash
-You will need the APX driver as well.
-The nvflash package
http://forum.xda-developers.com/nabi-2/general/nabi-information-t3229119
I will type more later.
aicjofs said:
Damn. It IS going to be a long haul, but you will know the tablet well when its done. I don't have the tablet to test anymore, so I have to work from memory(and that's been a long time)
Well the bad news is this is going to require opening the tablet. See this post http://forum.xda-developers.com/showpost.php?p=46694284&postcount=1701
You are going to have to short those pins to get it in to APX mode and use nvflash
-You will need the APX driver as well.
-The nvflash package
http://forum.xda-developers.com/nabi-2/general/nabi-information-t3229119
I will type more later.
Click to expand...
Click to collapse
Sweet! Looking forward to this.
Sent from my SM-N920P using Tapatalk
hotspace said:
Sweet! Looking forward to this.
Sent from my SM-N920P using Tapatalk
Click to expand...
Click to collapse
Get the nvflash package from the Nabi General Info thread I linked above
Unzip in to a directory of your choosing and open a command prompt in that folder
The Nabi will be broken open and connected by USB to computer
So once you get those pins shorted and press the power button the screen should come on and be completely black(you can tell the backlight is on though)
Check in device manager for a new device(it will be auto detected or you will have to manually install APX driver)
Once the driver is installed you can issue nvflash commands
nvflash --bl bootloader.bin --download 4 bootloader.bin
Before pressing enter for the below command get ready to press and hold the vol+ key.
nvflash --resume --go
Right on. I'll dig into this in the morning
Sent from my SM-N920P using Tapatalk
@aicjofs, I still haven't begun breaking the Nabi down. I'm working from home today and should be able to squeeze the disassemble in sometime today.
I scanned through the comments you've left since finding out I wasn't able to get to the boot menu...I'll post back once I get it torn apart.
Hi, I did the update here - http://forum.xda-developers.com/showpost.php?p=50341726&postcount=85
And removed twrp. Obviously with my lack of knowledge I
made a mistake. Now I have stock recovery and the nabi freezes on the boot logo.
Any chance someone could help with getting it booting again or getting twrp back on.
gavjbrown said:
Hi, I did the update here -http://forum.xda-developers.com/showpost.php?p=50341726&postcount=85
And removed twrp. Obviously with my lack of knowledge I
made a mistake. Now I have stock recovery and the nabi freezes on the boot logo.
Any chance someone could help with getting it booting again or getting twrp back on.
Click to expand...
Click to collapse
If Jellybean is installed, then I think this is what you need to install TWRP for JB onto the Nabi:
http://forum.xda-developers.com/showpost.php?p=48987089&postcount=2088
Once TWRP is on, your options for recovery are much wider.
gavjbrown said:
Hi, I did the update here -http://forum.xda-developers.com/showpost.php?p=50341726&postcount=85
And removed twrp. Obviously with my lack of knowledge I
made a mistake. Now I have stock recovery and the nabi freezes on the boot logo.
Any chance someone could help with getting it booting again or getting twrp back on.
Click to expand...
Click to collapse
Did you do everything else in thread or just that post? i.e. Did you update the bootloader too? http://forum.xda-developers.com/showpost.php?p=50356162&postcount=91
You will need TWRP one way or another. Use the ICS version if you didn't update the bootloader, and JB if you did.
Thanks for the help guys. I didn't realises until after that I needed to update the bootloader too, I'm guessing that's where my troubles start.
Just going to have a look at your links now, I know I could get twrp back on when it doest boot.
Thanks again.
Tried nabilab for ics and jb and both are no longer detecting my nabi.
When the nabi tries to boot the circle around the logo isnt even moving.
Still stuck with the Nabi, if anyone could help I'd really appreciate it. All I can do with it at the moment is boot to stock recovery.
gavjbrown said:
Still stuck with the Nabi, if anyone could help I'd really appreciate it. All I can do with it at the moment is boot to stock recovery.
Click to expand...
Click to collapse
So you installed the 2.2 ROM, but didn't update the bootloader. You have the stock recovery on it right now.
Can you get TWRP back on it?
Can you get into fastboot mode by pressing power and vol down?
aicjofs said:
So you installed the 2.2 ROM, but didn't update the bootloader. You have the stock recovery on it right now.
Can you get TWRP back on it?
Can you get into fastboot mode by pressing power and vol down?
Click to expand...
Click to collapse
Edited -
Yes put 2.2 on it but didn't update the boot loader. Tried to get twrp back on using nabilab buts the tablets no longer being detected .
Yes, I only have stock recovery. When I select fastboot protocol, I then get bootloader, continue, reboot-bootloader, reboot and power off.
gavjbrown said:
Edited -
Yes put 2.2 on it but didn't update the boot loader. Tried to get twrp back on using nabilab buts the tablets no longer being detected .
Yes, I only have stock recovery. When I select fastboot protocol, I then get bootloader, continue, reboot-bootloader, reboot and power off.
Click to expand...
Click to collapse
OK now you need to put TWRP back on it with fastboot when it's in that state.
Look in the TWRP thread, I'm mobile right now, but basically you need to open a command prompt where fastboot is located and then
fastboot flash recovery recovery.img
Thanks so much for getting me out of this mess. Twrp is back on so I should be ok now with a bit of trial and error.
Hi Guys,
I want to root my LG G5 with TWRP & SuperSU
So first i unlocked the bootloader for my phone.
2. Dwonloaded TWRP & SuperSU
3. Installed TWRP with CMD
works everything fine, but i cant enter in the TWRP recovery it just loads the normal recovery where i can swipe my data.
I also tried to "fastboot boot" into TWRP recovery and also install TWRP and remove battery so android cannt boot.
Unfortunately nothing worked
I really dont know what to do ?
thx 4 help
trash195 said:
Hi Guys,
I want to root my LG G5 with TWRP & SuperSU
So first i unlocked the bootloader for my phone.
2. Dwonloaded TWRP & SuperSU
3. Installed TWRP with CMD
works everything fine, but i cant enter in the TWRP recovery it just loads the normal recovery where i can swipe my data.
I also tried to "fastboot boot" into TWRP recovery and also install TWRP and remove battery so android cannt boot.
Unfortunately nothing worked
I really dont know what to do ?
thx 4 help
Click to expand...
Click to collapse
Start your phone in fastboot mode, flash TWRP, disconnect and reconnect the battery.
Now hold volume down + power until you see the LG logo, keep holding volume down and let go of the power button for a moment and then hold the power button again while still holding the volume down button.
You will now see a prompt asking if you'd like to factory reset, press yes to both prompts.
You will now be inside TWRP.
Which variant you are using.
mass/cls/ said:
Start your phone in fastboot mode, flash TWRP, disconnect and reconnect the battery.
Now hold volume down + power until you see the LG logo, keep holding volume down and let go of the power button for a moment and then hold the power button again while still holding the volume down button.
You will now see a prompt asking if you'd like to factory reset, press yes to both prompts.
You will now be inside TWRP.
Click to expand...
Click to collapse
I've tried this process myself and I get the same result. Reply Yes, Yes to factory reset and it *should* then start TWRP but it doesn't. You end up with a wiped phone and have to start all over again. Tried process a few times and never works.
lywyn said:
I've tried this process myself and I get the same result. Reply Yes, Yes to factory reset and it *should* then start TWRP but it doesn't. You end up with a wiped phone and have to start all over again. Tried process a few times and never works.
Click to expand...
Click to collapse
The only reason it wouldn't work is if you did not flash TWRP correctly, make sure flashing TWRP with fastboot was successful before disconnecting the battery and entering the factory reset prompt.
mass/cls/ said:
The only reason it wouldn't work is if you did not flash TWRP correctly, make sure flashing TWRP with fastboot was successful before disconnecting the battery and entering the factory reset prompt.
Click to expand...
Click to collapse
It is successful, and I pull the battery and go straight into recovery as recommended. Used latest version.
lywyn said:
It is successful, and I pull the battery and go straight into recovery as recommended. Used latest version.
Click to expand...
Click to collapse
This is not something I've ever had a problem with, every time I've wiped my phone and installed a new version this has worked.
Flash the latest version of android with LGUP and try again.
mass/cls/ said:
This is not something I've ever had a problem with, every time I've wiped my phone and installed a new version this has worked.
Flash the latest version of android with LGUP and try again.
Click to expand...
Click to collapse
On V20a-234-30. I have flashed TWRP successfully in the past. Might try LGUP to V20D and then try, but if it factory resets I waste hours while phone goes through setup to try again
lywyn said:
On V20a-234-30. I have flashed TWRP successfully in the past. Might try LGUP to V20D and then try, but if it factory resets I waste hours while phone goes through setup to try again
Click to expand...
Click to collapse
Yes I know it is very annoying when that happens, you should definitely flash the latest version regardless, I'm sure you won't have the problem after flashing :good:.
trash195 said:
Hi Guys,
I want to root my LG G5 with TWRP & SuperSU
So first i unlocked the bootloader for my phone.
2. Dwonloaded TWRP & SuperSU
3. Installed TWRP with CMD
works everything fine, but i cant enter in the TWRP recovery it just loads the normal recovery where i can swipe my data.
I also tried to "fastboot boot" into TWRP recovery and also install TWRP and remove battery so android cannt boot.
Unfortunately nothing worked
I really dont know what to do ?
thx 4 help
Click to expand...
Click to collapse
Found it! After you install twrp, you just execute 2 more commands:
fastboot format userdata
fastboot format cache
Don't reboot, just turn it off.
Works like a charm!
I unlocked bootloader, went to fastboot and tried to flash TWRP - https://eu.dl.twrp.me/mido/ (I have SN version of RN4). Flash went without error, but then I pressed volume-up and power-on and phone didn't go on. Notification LED for battery doesn't light when connected and I can't turn the phone on or access the fastboot. It seems bad to me. Is there anything I can do? I spent my only money for this device and fact I might kill it makes me cry.
gr4nis said:
I unlocked bootloader, went to fastboot and tried to flash TWRP - https://eu.dl.twrp.me/mido/ (I have SN version of RN4). Flash went without error, but then I pressed volume-up and power-on and phone didn't go on. Notification LED for battery doesn't light when connected and I can't turn the phone on or access the fastboot. It seems bad to me. Is there anything I can do? I spent my only money for this device and fact I might kill it makes me cry.
Click to expand...
Click to collapse
Did you flash twrp successfully right?
If yeah, then try enter into fastboot mode [volume down + power key] use fastboot commands to boot to TWRP -
Fastboot boot <whatever the recovery name.img> hit enter, then wait sometime it'll eventually boot to trwp, from twrp flash lazyflasher zip, reboot your phone, that's the way.
If you can't go on fastboot mode, then try this - http://en.miui.com/thread-565784-1-1.html
deleted
sachin n said:
Did you flash twrp successfully right?
If yeah, then try enter into fastboot mode [volume down + power key] use fastboot commands to boot to TWRP -
Fastboot boot <whatever the recovery name.img> hit enter, then wait sometime it'll eventually boot to trwp, from twrp flash lazyflasher zip, reboot your phone, that's the way.
If you can't go on fastboot mode, then try this - http://en.miui.com/thread-565784-1-1.html
Click to expand...
Click to collapse
Well, I managed to do what you said, I was in TWRP and flashed lazyflasher. I clicked reboot but phone don't go on. If I hold power on phone long enough (7 sec or so) it just shows Xiaomi logo for a split of second and then go off. Before I did that, I held button long enough and was able to boot into system. Now I can't.
gr4nis said:
Well, I managed to do what you said, I was in TWRP and flashed lazyflasher. I clicked reboot but phone don't go on. If I hold power on phone long enough (7 sec or so) it just shows Xiaomi logo for a split of second and then go off.
Click to expand...
Click to collapse
Ohhh! Yeah! I too faced this issue bruh! [look here - https://forum.xda-developers.com/redmi-note-4/help/redmi-note-4-isnt-booting-flashing-twrp-t3587781] same issue, it's just pops mi logo for a sec when I long press power key.
How I recovered my device -
Went to fastboot mode - volume down + power key.
Then fastboot boot <recovery.img>
Wait let it boot to TWRP, once you get into twrp, just wipe everything except internal /SD card, then choose install zip, flash los14.1. Firmware, then flash any custom rom + Gapps, hit reboot!
This fixed my issue.
Try this»^
---------- Post added at 11:46 ---------- Previous post was at 11:41 ----------
Links - firmware.zip
DL this rom
Choose gapps - opengapps.org [choose Pico variant, or whatever the package you want] (7.1/arm64)
RESOLVED
sachin n said:
Ohhh! Yeah! I too faced this issue bruh! [look here - https://forum.xda-developers.com/redmi-note-4/help/redmi-note-4-isnt-booting-flashing-twrp-t3587781] same issue, it's just pops mi logo for a sec when I long press power key.
How I recovered my device -
Went to fastboot mode - volume down + power key.
Then fastboot boot <recovery.img>
Wait let it boot to TWRP, once you get into twrp, just wipe everything except internal /SD card, then choose install zip, flash los14.1. Firmware, then flash any custom rom + Gapps, hit reboot!
This fixed my issue.
Click to expand...
Click to collapse
Oh, dude! You really saved my ass. It worked! Thank you very much. You are the hero of the day. Long be your life!
gr4nis said:
Oh, dude! You really saved my ass. It worked! Thank you very much. You are the hero of the day. Long be your life!
Click to expand...
Click to collapse
Hahaha! :silly:
I'm glad you fixed it! now, play with custom ROMs, Miui sux.
sachin n said:
Hahaha! :silly:
I'm glad you fixed it! now, play with custom ROMs, Miui sux.
Click to expand...
Click to collapse
Yeah, it does But actually one more question. I tried to get to TWRP once again but there is no TWRP after holding Vol+ and Power on. There is still stock recovery something which looks like this. Everything else is fine but I don't feel like going through fastboot when recovery is needed.
gr4nis said:
Oh, dude! You really saved my ass. It worked! Thank you very much. You are the hero of the day. Long be your life!
Click to expand...
Click to collapse
gr4nis said:
Yeah, it does But actually one more question. I tried to get to TWRP once again but there is no TWRP after holding Vol+ and Power on. There is still stock recovery likeTHIS. Everything else is fine but I don't feel like going through fastboot when recovery is needed.
Click to expand...
Click to collapse
Dude nah!!
Follow this to boot recovery mode -
Power off your device
Press volume up + power key until you see MI logo, when you see it, just leave power key but keep hold the volume up.
BTW, which rom did you flashed?
sachin n said:
Dude nah!!
Follow this to boot recovery mode -
Power off your device
Press volume up + power key until you see MI logo, when you see it, just leave power key but keep hold the volume up.
BTW, which rom did you flashed?
Click to expand...
Click to collapse
Yeah, I did just like that. Even when I enable advanced reboot in dev options and choose to reboot directly to recovery from system, I get that black screen instead of TWRP.
I flashed LOS 14 for now. Maybe I'll go with RR later.
gr4nis said:
Yeah, I did just like that. Even when I enable advanced reboot in dev options and choose to reboot directly to recovery from system, I get that black screen instead of TWRP.
Click to expand...
Click to collapse
Damn!
Get terminal Emulator from play store -
su hit enter -
Then -
reboot recovery - - hit enter
@gr4nis, Sup now? Still the same Mi pc suite screen?
sachin n said:
Damn!
Get terminal Emulator from play store -
su hit enter -
Then -
reboot recovery - - hit enter
@gr4nis, Sup now? Still the same Mi pc suite screen?
Click to expand...
Click to collapse
It said "su: not found" but I entered "reboot recovery" anyway and got the same black screen as before.
gr4nis said:
It said "su: not found" but I entered "reboot recovery" anyway and got the same black screen as before.
Click to expand...
Click to collapse
Eh, it looks like twrp is gone. Ehh
Nothing to worry, tell me what rom are you on at the moment?
sachin n said:
Eh, it looks like twrp is gone. Ehh
Nothing to worry, tell me what rom are you on at the moment?
Click to expand...
Click to collapse
This one: https://forum.xda-developers.com/re...other-development/rom-lineageos-14-0-t3566095
I believe the same you recommended.
Should I maybe try to "fastboot boot recovery.img" ?
gr4nis said:
This one: https://forum.xda-developers.com/re...other-development/rom-lineageos-14-0-t3566095
I believe the same you recommended.
Should I maybe try to "fastboot boot recovery.img" ?
Click to expand...
Click to collapse
Yeah, just fastboot boot recovery.img, once you are in recovery, just flash lineageOS addon.zip [look here - addonsu-arm64-signed.zip] ,reboot. Then tell me..
Link for the addon.zip - https://download.lineageos.org/extras [Download '' addonsu-arm64-signed.zip''.
sachin n said:
Yeah, just fastboot boot recovery.img, once you are in recovery, just flash lineageOS addon.zip [look here - addonsu-arm64-signed.zip] ,reboot. Then tell me..
Link for the addon.zip - https://download.lineageos.org/extras [Download '' addonsu-arm64-signed.zip''.
Click to expand...
Click to collapse
Oh, root was missing, sure. That's why "su" didn't work. Okay, rooted now. What's next?
BTW: I'm starting to think I never flashed TWRP. I guess I was too hasty after it said it's done. Maybe I should gave it some more time. I immediately pushed Vol+ and Power button. Maybe it wasn't flashed at all or wasn't flashed properly. Should I try to flash it again?
@sachin n
gr4nis said:
Oh, root was missing, sure. That's why "su" didn't work. Okay, rooted now. What's next?
BTW: I'm starting to think I never flashed TWRP. I guess I was too hasty after it said it's done. Maybe I should gave it some more time. I immediately pushed Vol+ and Power button. Maybe it wasn't flashed at all or wasn't flashed properly. Should I try to flash it again?
@sachin n
Click to expand...
Click to collapse
Wait, you got su access? Then wait, u don't need a pc now!
You can flash recovery.img from flashify app [DL it from PS]
Download flashify app from PS, open it, give su access.
Then choose flash recovery.img from the list, locate twrp.img, once its done just hit the reboot now, when it prompts.
sachin n said:
Wait, you got su acces? Then wait, u don't need a pc now!
You can flash recovery.img from flashify app [DL it from PS]
Click to expand...
Click to collapse
Yeah, I thought it was the reason why you asked me to flash that addonsu-arm64-signed.zip. But I installed Flashify and it said I don't have a root. So I flashed SuperSU and then flashed recovery through Flashify. Now it works! So, again, thank you! You helped me a lot today. :good:
gr4nis said:
Yeah, I thought it was the reason why you asked me to flash that addonsu-arm64-signed.zip. But I installed Flashify and it said I don't have a root. So I flashed SuperSU and then flashed recovery through Flashify. Now it works! So, again, thank you! You helped me a lot today. :good:
Click to expand...
Click to collapse
Ah yep, that's the reason I told you to flash su.
Anyway, you're good with TWRP now?
It's easy to enter into recovery mode using physical buttons?
sachin n said:
Ah yep, that's the reason I told you to flash su.
Anyway, you're good with TWRP now?
It's easy to enter into recovery mode using physical buttons?
Click to expand...
Click to collapse
Yeah, it totally works now. Vol+ and Power button takes me to TWRP. Much better, I was already sick of Fastboot