Related
I used revolutionary to S-Off but didn't flash the twrp right away I just rebooted the phone. Now I can't get back into recovery mode! Holding the volume down key does not work. Does anyone know a command I can type or something to go into recovery mode and fix this? Please help!
kthwaits said:
I used revolutionary to S-Off but didn't flash the twrp right away I just rebooted the phone. Now I can't get back into recovery mode! Holding the volume down key does not work. Does anyone know a command I can type or something to go into recovery mode and fix this? Please help!
Click to expand...
Click to collapse
Since you didn't flash twrp right away, and don't have custom recovery, I'm assuming that by 'recovery mode' you're referring to the bootloader? So then from the bootloader you can flash twrp?
"adb reboot bootloader" will boot you to fastboot mode. You probably need to go to menu>settings>power, and disable fastboot in order for power+volume down to allow you to boot into the bootloader.
Also, removing the battery and then replacing it will allow you to boot to the bootloader via volume down and power button.
Also, once you get recovery and flash the su/busybox/super user zip, so that you have full root...the easiest way to get to recovery or bootloader after that is to use an app from the market called 'quickboot'. Good luck
Make sure fastboot is turned off in settings> power.
Is it possible to enter fastboot without a pc? I ask because I had read that if you enter recovery via fastboot its almost like being s-off. I was actually able to flash a kernel that way. Thanks for replying.
jagrave said:
Is it possible to enter fastboot without a pc?
Click to expand...
Click to collapse
Most ROMS will give you the option on the power menu (when you press down power button) to "reboot to bootloader". From there, fastboot is the first option in bootloader. edit: also you could hold down power and vol-down at the same time from powered off state, also AmonRa will give you the option to reboot to bootloader under developer options.
I ask because I had read that if you enter recovery via fastboot its almost like being s-off. I was actually able to flash a kernel that way. Thanks for replying.
Click to expand...
Click to collapse
No technique or series of events will ever magically allow an S-ON user to bypass the secure flag and flash a complete kernel, boot.img and all, through recovery. Simply is not possible.
You need to fastboot flash the boot.img which requires a PC.
Rebooting to recovery from the Rom, or entering recovery through bootloader doesn't make a difference.
But to get to bootloader which is what I think you want, turn off the phone then boot by holding power+volume down button.
I think you're talking about flashing a kernel in hboot, which doesn't have anything to do with fastboot. You place the PH98IMG.zip onto your external sd card and boot to hboot, say yes to the update, and if you get a main version is older error message, there's a fixmainversionlow.zip that you can flash to avoid that.
That puts you in hboot. To go into fastboot mode, you select fastboot there on the hboot screen.
Sent from my ADR6425LVW using xda premium
fo0you said:
Most ROMS will give you the option on the power menu (when you press down power button) to "reboot to bootloader". From there, fastboot is the first option in bootloader. edit: also you could hold down power and vol-down at the same time from powered off state, also AmonRa will give you the option to reboot to bootloader under developer options.
No technique or series of events will ever magically allow an S-ON user to bypass the secure flag and flash a complete kernel, boot.img and all, through recovery. Simply is not possible.
Click to expand...
Click to collapse
Well, he might be talking about HTC Dumlock, but other then that, you're right.
Argumentation said:
Well, he might be talking about HTC Dumlock, but other then that, you're right.
Click to expand...
Click to collapse
I use HTC dumlock for all my s-off needs even though I am currently son.
Sent from the Rage that is ICS via this funky struck rezound
I am running santod's rooted Stock ICS rom, which has been running excellent, love it very much. Today I went to do a backup in recovery and noticedit will not boot into recovery. I am running the 4EXT recovery as suggested in the rom forum post. Nothing I do seems to be able to boot the recovery. I can't reboot into recovery from the 4EXT app. I boot the phone with the volume down key, and try to enter recovery from there. Still nothing. I get my initial boot logo, then screen goes black, then boot logo again and it proceeds to boot up normally. I have tried re-flashing the recovery from the 4EXT app, I even tried rom manages and using the latest clockwork mod recovery. Nothing gets me into recovery. Also have noticed my phone will not stay powered off when on the charger. If I power off, plug the charger in, after a few seconds phone powers itself on. Could it be related?
I followed the rom installation instructions to the letter.
Installed the 4EXT recovery.
Flashed the ICS radios.
Wiped all my partitions except my SD card.
Flashed rom and have enjoyed for weeks now.
Only other info I know to provide is I installed the debloated/deodexed rom
Did not flash the kernel as I didn't experience boot loops.
Thanks in advance for any assistance folks!
JM1084 said:
I am running santod's rooted Stock ICS rom, which has been running excellent, love it very much. Today I went to do a backup in recovery and noticedit will not boot into recovery. I am running the 4EXT recovery as suggested in the rom forum post. Nothing I do seems to be able to boot the recovery. I can't reboot into recovery from the 4EXT app. I boot the phone with the volume down key, and try to enter recovery from there. Still nothing. I get my initial boot logo, then screen goes black, then boot logo again and it proceeds to boot up normally. I have tried re-flashing the recovery from the 4EXT app, I even tried rom manages and using the latest clockwork mod recovery. Nothing gets me into recovery. Also have noticed my phone will not stay powered off when on the charger. If I power off, plug the charger in, after a few seconds phone powers itself on. Could it be related?
I followed the rom installation instructions to the letter.
Installed the 4EXT recovery.
Flashed the ICS radios.
Wiped all my partitions except my SD card.
Flashed rom and have enjoyed for weeks now.
Only other info I know to provide is I installed the debloated/deodexed rom
Did not flash the kernel as I didn't experience boot loops.
Thanks in advance for any assistance folks!
Click to expand...
Click to collapse
Did you rename or remove the Radio file from the sd card as suggested in the OP of the rom thread?
It will not let you get into Recovery if there is a PG05IMG.zip present on the root of the sd card.
If that's not the case, reflash 4ext from within the Recovery control app.
Just installing the app doesn't install the Recovery.
You must also install the actual Recovery from within the app if you haven't.
santod040 said:
Did you rename or remove the Radio file from the sd card as suggested in the OP of the rom thread?
It will not let you get into Recovery if there is a PG05IMG.zip present on the root of the sd card.
If that's not the case, reflash 4ext from within the Recovery control app.
Just installing the app doesn't install the Recovery.
You must also install the actual Recovery from within the app if you haven't.
Click to expand...
Click to collapse
Yeah, there is no PG05IMG.zip in the sd card root. Also I have tried reinstalling the recovery from the 4EXT recovery control app.
Current verson of recovery installed is 4EXT Recovery Touch v1.0.0.5 RC8.
Tried reflashing that, and also the RC9 test build that is out right now.
Still no go on getting into the recovery.
Thanks.
When you do the volume down and power option with the device off, you need to first press the volume down and then while holding that, then press and also hold the power button, you should feel it vibrate, keeeeeep holding them down, do not let go.
Wait until you see what should be a white hboot screen with menu options, then you may let go.
If you hold power first or don't hold them both down long enough, it will just try to boot normally.
Not that that would explain why you can't get there from within Recovery Control app.
What is your hboot version and how did you root your device?
santod040 said:
When you do the volume down and power option with the device off, you need to first press the volume down and then while holding that, then press and also hold the power button, you should feel it vibrate, keeeeeep holding them down, do not let go.
Wait until you see what should be a white hboot screen with menu options, then you may let go.
If you hold power first or don't hold them both down long enough, it will just try to boot normally.
Not that that would explain why you can't get there from within Recovery Control app.
What is your hboot version and how did you root your device?
Click to expand...
Click to collapse
It was rooted using the Revolutionary method, did it a year or more ago.
Hboot version is 6.04.1002
When I try to go to recovery from the hboot screen it does the same, vibrate, white HTC screen, black screen, vibrate, white HTC screen, normal boot. No recovery.
Is there any other method of getting into recovery or re-flashing the recovery?
JM1084 said:
It was rooted using the Revolutionary method, did it a year or more ago.
Hboot version is 6.04.1002
When I try to go to recovery from the hboot screen it does the same, vibrate, white HTC screen, black screen, vibrate, white HTC screen, normal boot. No recovery.
Is there any other method of getting into recovery or re-flashing the recovery?
Click to expand...
Click to collapse
Yes, you can flash Recovery images from hboot, just like you flash a radio.
With it named PG05IMG.zip and placed on the root of the sd card.
HERE is one you can try.
If that doesn't work, I may have something you can try from fastboot to clear the Recovery cache, and maybe that will resolve the issue.
I have only seen one other user have this occur and his device simply ended up getting replaced because he wasn't able to mount to usb for doing fastboot commands either.
santod040 said:
Yes, you can flash Recovery images from hboot, just like you flash a radio.
With it named PG05IMG.zip and placed on the root of the sd card.
HERE is one you can try.
If that doesn't work, I may have something you can try from fastboot to clear the Recovery cache, and maybe that will resolve the issue.
I have only seen one other user have this occur and his device simply ended up getting replaced because he wasn't able to mount to usb for doing fastboot commands either.
Click to expand...
Click to collapse
Still no go flashing that recovery in hboot. What is the process of clearing recovery cache?
On a side note, in talking to my father, his bolt seems to have the same issue. We both were rooted with the same method, and I believe we have the same hboot version. Only difference is he flashed the rom using clockwork recovery.
Edit: I confirmed his hboot is 6.04.1002. same as mine
JM1084 said:
Still no go flashing that recovery in hboot. What is the process of clearing recovery cache?
On a side note, in talking to my father, his bolt seems to have the same issue. We both were rooted with the same method, and I believe we have the same hboot version. Only difference is he flashed the rom using clockwork recovery.
Click to expand...
Click to collapse
Well, I've got several Bolts here, and a couple of them have that same hboot and were used to test the stock roms with.
So I do not think it's a root or hboot issue, but I do not know what the issue would be other then corrupt Recovery cache.
To try and fix it by clearing the cache, do the following:
Download the erasecache.zip file from www.4ext.net/erasecache.zip
First boot your device into bootloader while connected via usb.
If it reads "fastboot usb" you are already in fastboot mode.
If it reads "hboot usb" then select "fastboot" in the bootloader menu.
Extract the file anywhere on your computer, and then start the file erase_cache.cmd with
elevated rights (right click erase_cache.cmd and select to run as administrator)
Watch for any error messages and tell me the results please.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
If the above method fails, try this way:
This requires a little adb or command line knowledge(not much) and the appropriate files on your system.
Please boot into bootloader -> fastboot mode
and then issue the following fastboot command:
fastboot erase cache
afterwards boot recovery from the bootloader menu and enter the
wipe menu and format cache
santod040 said:
Well, I've got several Bolts here, and a couple of them have that same hboot and were used to test the stock roms with.
So I do not think it's a root or hboot issue, but I do not know what the issue would be other then corrupt Recovery cache.
To try and fix it by clearing the cache, do the following:
Download the erasecache.zip file from www.4ext.net/erasecache.zip
First boot your device into bootloader while connected via usb.
If it reads "fastboot usb" you are already in fastboot mode.
If it reads "hboot usb" then select "fastboot" in the bootloader menu.
Extract the file anywhere on your computer, and then start the file erase_cache.cmd with
elevated rights (right click erase_cache.cmd and select to run as administrator)
Watch for any error messages and tell me the results please.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
If the above method fails, try this way:
This requires a little adb or command line knowledge(not much) and the appropriate files on your system.
Please boot into bootloader -> fastboot mode
and then issue the following fastboot command:
fastboot erase cache
afterwards boot recovery from the bootloader menu and enter the
wipe menu and format cache
Click to expand...
Click to collapse
Alrighty, I will give that a shot. I am at work right now and am about to head out of town so I will be unable to try it until sunday. I'll post the results here asap. Thanks again!
Same ROM, same problem,I even tried flashing a different recovery. Rooted using really old one click method a month after thunderbolt release.
Sent from my HTC Thunderbolt
zomgalama said:
Same ROM, same problem,I even tried flashing a different recovery. Rooted using really old one click method a month after thunderbolt release.
Sent from my HTC Thunderbolt
Click to expand...
Click to collapse
What is your h boot version?
Sent from my ADR6400L using Tapatalk 2
santod040 said:
Well, I've got several Bolts here, and a couple of them have that same hboot and were used to test the stock roms with.
So I do not think it's a root or hboot issue, but I do not know what the issue would be other then corrupt Recovery cache.
To try and fix it by clearing the cache, do the following:
Download the erasecache.zip file from www.4ext.net/erasecache.zip
First boot your device into bootloader while connected via usb.
If it reads "fastboot usb" you are already in fastboot mode.
If it reads "hboot usb" then select "fastboot" in the bootloader menu.
Extract the file anywhere on your computer, and then start the file erase_cache.cmd with
elevated rights (right click erase_cache.cmd and select to run as administrator)
Watch for any error messages and tell me the results please.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
If the above method fails, try this way:
This requires a little adb or command line knowledge(not much) and the appropriate files on your system.
Please boot into bootloader -> fastboot mode
and then issue the following fastboot command:
fastboot erase cache
afterwards boot recovery from the bootloader menu and enter the
wipe menu and format cache
Click to expand...
Click to collapse
No Go, my tbolt will not mount in Win7, it just says the device has malfunctioned. Rebooting into the bootloader with USB in will not show anything in Windows, even in fastboot. It makes the device connection sound but no devices show up. Running the CMD file in the zip you linked does nothing, I'm at 10 minutes now where it just says "Waiting for device". Is my device just done for?
JM1084 said:
It was rooted using the Revolutionary method, did it a year or more ago.
Hboot version is 6.04.1002
When I try to go to recovery from the hboot screen it does the same, vibrate, white HTC screen, black screen, vibrate, white HTC screen, normal boot. No recovery.
Is there any other method of getting into recovery or re-flashing the recovery?
Click to expand...
Click to collapse
I think I had a similar problem once. Boot back into your hboot screen. Then select "factory reset". If you have a 3rd party recovery installed, like it sound like you have (4ext, right?), it will boot you to recovery so you can administer the reset yourself (it doesn't actually wipe anything, just brings you to your recovery's home screen).
Let me know how it goes.
coltspackers said:
I think I had a similar problem once. Boot back into your hboot screen. Then select "factory reset". If you have a 3rd party recovery installed, like it sound like you have (4ext, right?), it will boot you to recovery so you can administer the reset yourself (it doesn't actually wipe anything, just brings you to your recovery's home screen).
Let me know how it goes.
Click to expand...
Click to collapse
Thanks for the info, but this didn't work either. I'm also on 6.04.1002 and rooted mine a week after the T-Bolt shipped manually via adb.
This happened about a month ago also, and I thought it was ext4 but managed to get an older TWRP recovery to work after working on it for about a day and a half without a working phone. At least I have a working phone at this point.
Same ROM, same recovery (4ext), same problem. Rooted by adb a month after launch, hboot 6.04.1002
allo_87 said:
Same ROM, same recovery (4ext), same problem. Rooted by adb a month after launch, hboot 6.04.1002
Click to expand...
Click to collapse
Might be wise to bring it to Max's attention.
He makes the Recovery that is disappearing and may have suggestions or ideas on how to prevent this in the future.
I have flashed every rom I have ever posted at least once.
Most of them, may times and have yet to run into this issue.
I have had Recovery become corrupted once or twice quite some time back and not be able to get into it.
But it was easily fixed by reinstalling/reflashing a recovery.
I guess what I'm saying, is if there is a common issue occuring on our device with some ICS users and his Recovery, he should know about it.
Here's how to contact him: LINK
Hopefully he can help or look into the root of the issue, since I know he has had a few users with this same issue in the past.
santod040 said:
Might be wise to bring it to Max's attention.
He makes the Recovery that is disappearing and may have suggestions or ideas on how to prevent this in the future.
I have flashed every rom I have ever posted at least once.
Most of them, may times and have yet to run into this issue.
I have had Recovery become corrupted once or twice quite some time back and not be able to get into it.
But it was easily fixed by reinstalling/reflashing a recovery.
I guess what I'm saying, is if there is a common issue occuring on our device with some ICS users and his Recovery, he should know about it.
Here's how to contact him: LINK
Hopefully he can help or look into the root of the issue, since I know he has had a few users with this same issue in the past.
Click to expand...
Click to collapse
Excellent advice, thanks man.
Sent from my ADR6400L using Tapatalk 2
My thunderbolt's recovery spin mysteriously started working again yesterday, not sure why.
Doesn't matter though since I switched carriers now:/
Sent from my Sprint LG Optimus G
Still nothing for me. Worse yet is the fact that I can't adb because my usb has not worked properly since "the soup incident"
Sent from my ADR6400L using Tapatalk 2
santod040 said:
Might be wise to bring it to Max's attention.
He makes the Recovery that is disappearing and may have suggestions or ideas on how to prevent this in the future.
I have flashed every rom I have ever posted at least once.
Most of them, may times and have yet to run into this issue.
I have had Recovery become corrupted once or twice quite some time back and not be able to get into it.
But it was easily fixed by reinstalling/reflashing a recovery.
I guess what I'm saying, is if there is a common issue occuring on our device with some ICS users and his Recovery, he should know about it.
Here's how to contact him: LINK
Hopefully he can help or look into the root of the issue, since I know he has had a few users with this same issue in the past.
Click to expand...
Click to collapse
After going over the issue with Max and trying several fixes he suggested (he even made me an app that would format my cache), it seems I either need to obtain an RUU and flash the stock software/recovery back on and re-root or try flashing an updated hboot that already has s-off. The thinking is that it is my hboot that is causing the issue. Does anyone know what files I need? I have a couple of things to try at home to see if I can get my usb working again, if not, anything I do will have to be a flashable zip from the bootloader. Thanks!
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
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