Related
Help please...
I tried to flash CM7 onto my unlocked motorola Atrix 4g. Before doing so, I made a restore with Clockwork recovery and proceeded to flash the CM7 beta found on XDA. Before flashing, I made sure to wipe data/cache.
After doing this, my phone is stuck on the boot screen. I tried using the backup that I made to restore, but it says "can not find system.info" and finished. Then when rebooting it is still stuck at the boot screen.
Worst of all, my battery is now dead and wont charge! I searched and did some things in fastboot to try to fix it, but whenever I try to use fastboot, it gets stuck on "waiting for device".
Is there any way that I can save my phone or am I done for?
asdad123 said:
Help please...
I tried to flash CM7 onto my unlocked motorola Atrix 4g. Before doing so, I made a restore with Clockwork recovery and proceeded to flash the CM7 beta found on XDA. Before flashing, I made sure to wipe data/cache.
After doing this, my phone is stuck on the boot screen. I tried using the backup that I made to restore, but it says "can not find system.info" and finished. Then when rebooting it is still stuck at the boot screen.
Worst of all, my battery is now dead and wont charge! I searched and did some things in fastboot to try to fix it, but whenever I try to use fastboot, it gets stuck on "waiting for device".
Is there any way that I can save my phone or am I done for?
Click to expand...
Click to collapse
take your battery out and plug your phone into a wall charger. Then place the battery back in and let your phone charge.
After that fastboot flash romracer's recovery from the dev section. Reinstall cm7 and enjoy!
Sent from my MB860 using xda premium
Doing that to charge the battery didnt work
Also, I tried using romracer's recovery last night before the battery died, but it kept getting stuck on "waiting for device"
Did I use a wrong version of fastboot or something?
asdad123 said:
Doing that to charge the battery didnt work
Also, I tried using romracer's recovery last night before the battery died, but it kept getting stuck on "waiting for device"
Did I use a wrong version of fastboot or something?
Click to expand...
Click to collapse
http://www.youtube.com/watch?v=9pYcgmLhUcQ
follow the instructions in that video to charge your phone, use a SPARE USB CABLE. do NOT hack apart your Motorola charger, you can pick up a USB cable for 2-3 bucks off the internet.
download the fastboot files from here: http://forum.xda-developers.com/showthread.php?t=1138092
after you get your phone charged (let it charge for about half an hour with that method) try to boot into fastboot and do a fastboot -w (this will wipe EVERYTHING)
download the latest recovery from here: http://forum.xda-developers.com/showthread.php?t=1204500
after you fastboot -w, you should flash Romracer's latest recovery by doing the command 'fastboot flash recovery <recovery.img name goes here>'
then boot into recovery mode and wipe Dalvik Cache, wipe Data, and wipe Cache.
after that, install CM7 beta. or any other ROM you want. you should proceed to make a backup immediately after your first boot into the device.
please don't ever try to flash anything if your phone is not at 100% charge.
Woo Thank you guys!
I went to a best buy and they switched out the battery for me and I was able to fix it with the directions you guys provided! Thank you so much!
Happened to me too. Minus the dead battery part. It was fine till I tried flashing fauxs 1.3ghz kernel. Then all hell broke loose
Sent from my MB860 using XDA App
I follow your instructions and i revived my atrix
thaks you so much!!!!
10 character
I rolled back from MMROM to NOTTACHTRIX Today and now my phone is stuck in CWM. (Cold Boot Android by selecting Boot Anroid NO BP option doesnt work either).
I have flashed MROM, Neutrino, NOTTACHTRIX, CM10.120120720 and all ended up into clockwork mod recovery. Kindly tell me an alternative -.- I am stuck with this from past 12 hours and no luck.
Update
I have managed to boot into android using Cold Boot without BP (i-e GSM radio will be disabled). I am recharging my phone battery and experimenting.
Before flashing NOTTACHTRIX, my phone had SKT version of 2.3.5 v167. I directly went for unlocking bootloader blabla recovery to get the NOTTACHTRIX working (thats like 4 months ago when I bought this phone)
So I tried going back to a version near 2.3.5 or higher. So going for 141 AT&T version didnt seem a problem for me except the .91 version bricks the device if u downgrade from 2.3.5 or above.
RSD Lite gave me 0x703e error and I couldn't flash the stop sbf.
Second resort I did was flashing 2.3.5 and 2.3.6 fruitcakes and still ended up in recovery.
I can only coldboot into android with Neutrino ROM other roms give me rebootloop when I choose coldboot.
I am suspecting a corrupted system or some kind of corrupt script in boot which keeps me in a loop into recovery. I did try adb script for ASUS TF101 to exit recovery bootloop but to no luck.
Also, I tried exitrecovery.zip flashable and still couldnt get into regular android OS.
This device is a headache for me now -.- and seemingly no one bothers to reply or to help me solve this issue >_>
Thanks for reading atleast
Update 3
Fixed it myself.
I downloaded fastboot, 2.3.6 fruitcake (system and boot), the older clockwork mod recovery, the one comes with Bootloader unlocking not some 5.0 version.
All I did was erased RECOVERY from fastboot, then boot and system. Frasled boot and system. Rooted with the bootloader unlocker package. Installed the old recovery and flashed NOTTACHTRIX.
Did all rom u flash succesfull..or fail mount?
Can u mount/unmount system..data etc..
If no..then yr cwm was not fr yr models..try another version
Yr detail on process but without the error msg..if flash ok then should be boot if not it must giv aome error while falshing even its completed
Sent from my e2001v21_v89_jbl1a698_2g using xda app-developers app
mynonama said:
Did all rom u flash succesfull..or fail mount?
Can u mount/unmount system..data etc..
If no..then yr cwm was not fr yr models..try another version
Yr detail on process but without the error msg..if flash ok then should be boot if not it must giv aome error while falshing even its completed
Sent from my e2001v21_v89_jbl1a698_2g using xda app-developers app
Click to expand...
Click to collapse
It was the bug of rebooting into CWM recovery and yes I was using right recovery for my Atrix i-e Rom Racers. Right now I am 4.x recovery and that works 100% to my needs on NOTTACHTRIX
And I flashed the fruitcake using fastboot. No flashing of stock sbf
Please help...recovery bootloop
dark_prince said:
It was the bug of rebooting into CWM recovery and yes I was using right recovery for my Atrix i-e Rom Racers. Right now I am 4.x recovery and that works 100% to my needs on NOTTACHTRIX
And I flashed the fruitcake using fastboot. No flashing of stock sbf
Click to expand...
Click to collapse
I have the same problem and tried several CWMs, and TWRP.
I can only boot to recovery, unless I try to boot with the BP HW Diag & Boot AP. Then I can cold-boot into Android, but with no USB support (so no ADB or charging capabilities).
I should have left my phone alone...I was running Nottachtrix just fine. Tried to flash CM 7 and then encountered this problem.
I have tried to restore, flashed new Roms, flashed new recoveries, flashed new boot.img, etc. No luck yet.
Tried the exitrecovery.zip, scripts to reset boot flags, full wipe and reload nottachtrix, flash radio, etc.
Still no luck.
Tried CWM version 4.xxx following instruction above, flashed fruitcake, rooted...still no luck.
Anyone have any advice?
Thanks in advance.
noobButStudying said:
I have the same problem and tried several CWMs, and TWRP.
I can only boot to recovery, unless I try to boot with the BP HW Diag & Boot AP. Then I can cold-boot into Android, but with no USB support (so no ADB or charging capabilities).
I should have left my phone alone...I was running Nottachtrix just fine. Tried to flash CM 7 and then encountered this problem.
I have tried to restore, flashed new Roms, flashed new recoveries, flashed new boot.img, etc. No luck yet.
Tried the exitrecovery.zip, scripts to reset boot flags, full wipe and reload nottachtrix, flash radio, etc.
Still no luck.
Tried CWM version 4.xxx following instruction above, flashed fruitcake, rooted...still no luck.
Anyone have any advice?
Thanks in advance.
Click to expand...
Click to collapse
did you try the updated and usually standardly used CWM, 5.0.2.6?
palmbeach05 said:
did you try the updated and usually standardly used CWM, 5.0.2.6?
Click to expand...
Click to collapse
Yes, thanks for the reply. I tried this one, and the CWM touch version advertised as designed for this phone model. No luck.
Aaaand.....I got impatient and tried to flash an sbf. Stupid, I know. Now, I have a shiny new brick.
Oh well, I ordered a new one from ebay, and I will spend my free time learning about possible ways to unbrick a phone.
noobButStudying said:
Yes, thanks for the reply. I tried this one, and the CWM touch version advertised as designed for this phone model. No luck.
Aaaand.....I got impatient and tried to flash an sbf. Stupid, I know. Now, I have a shiny new brick.
Oh well, I ordered a new one from ebay, and I will spend my free time learning about possible ways to unbrick a phone.
Click to expand...
Click to collapse
What's the msg that your brick is giving you? did you try flashing the pudding sbf and then trying to flash a custom ROM?
Resolved!
palmbeach05 said:
What's the msg that your brick is giving you? did you try flashing the pudding sbf and then trying to flash a custom ROM?
Click to expand...
Click to collapse
So here's the full story:
It would boot up and say "failed to boot 1"
It would not boot into fastboot(power on while pressing vol down). When I tried to boot into RSD(power on while pressing vol up), it would give the same error and say "PWR REASON PWR KEY PRESS" and then say Fastboot Protocol Support.
Using RSD, it would recognize the phone as being in fastboot mode, and any flashes would fail...including pudding.
Using fastboot, it would connect but give errors if I tried to flash or erase anything, like it was locked. When I tried to unlock again, it would say " OEM unlock not implemented."
This is why I figured it was bricked...the bootloader seemed hosed. Couldn't use RSD, and fastboot was useless.
But...after screwing around with it (battery pulled and re-inserted while holding various buttons) while connected to RSD, I noticed that the same error was there but somehow RSD recognized it! (I think the magic combo was to hold power and vol up while actually inserting the battery.)
So I flashed pudding, and it worked! Re-rooted, loaded CWM (using auto unlock 4.2), and the phone booted to stock config. It was still acting flaky (I don't think the sbf had loaded right), and it was unable to boot back into recovery, but I flashed CWM again using rom manager and was able to do a full recovery!
Yay!! I am ridiculously happy right now!
Anyway, when my ordered phone comes in, I will have a spare to play with. This one is staying as is from now on. (until I get bored again)
noobButStudying said:
So here's the full story:
It would boot up and say "failed to boot 1"
It would not boot into fastboot(power on while pressing vol down). When I tried to boot into RSD(power on while pressing vol up), it would give the same error and say "PWR REASON PWR KEY PRESS" and then say Fastboot Protocol Support.
Using RSD, it would recognize the phone as being in fastboot mode, and any flashes would fail...including pudding.
Using fastboot, it would connect but give errors if I tried to flash or erase anything, like it was locked. When I tried to unlock again, it would say " OEM unlock not implemented."
This is why I figured it was bricked...the bootloader seemed hosed. Couldn't use RSD, and fastboot was useless.
But...after screwing around with it (battery pulled and re-inserted while holding various buttons) while connected to RSD, I noticed that the same error was there but somehow RSD recognized it! (I think the magic combo was to hold power and vol up while actually inserting the battery.)
So I flashed pudding, and it worked! Re-rooted, loaded CWM (using auto unlock 4.2), and the phone booted to stock config. It was still acting flaky (I don't think the sbf had loaded right), and it was unable to boot back into recovery, but I flashed CWM again using rom manager and was able to do a full recovery!
Yay!! I am ridiculously happy right now!
Anyway, when my ordered phone comes in, I will have a spare to play with. This one is staying as is from now on. (until I get bored again)
Click to expand...
Click to collapse
The RSD issue and not being able to do anything. you are the 4rd person that i've dealt with to have that issue. we had a guy on here a few wks ago that me and andresrivas were trying to help. he wasn't getting the bootloop you were getting, but he had a very similar issue and had the RSD issue. like a wk later, i ended up having the RSD issue as well. Andresrivas also has experienced this issue. All i know is flashing that pudding is what saved us as well.
Idk what ROM you're going to put on there, but i would definitely keep that spare around. if your digitizer dies, you have a backup digitizer
I have the Galaxy Note SGH-I717R (Rogers version), with the stock android 4.0.4 installed. I want to install a custom ROM but I cannot get TWRP Recovery to work on this phone. I have followed all the guides but it will not work, even though it appears to install correctly. I put my phone into download mode, start odin in admin mode, attach my phone, it is recognized by odin, then I choose PDA and select the TWRP Recovery tar file (which is the correct one for my device). After I click Start on Odin it goes through these messages as it installs and reboots my device:
<ID:0/003> NAND Write Start!!
<ID:0/003> RQT_CLOSE !!
<ID:0/003> RES OK !!
<ID:0/003> Removed!!
<ID:0/003> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
and the box in the upper left corner turns green and says "Pass!".
After this, I have my phone usb disconnected and I reboot into recovery mode.. Only when it starts in recovery, it is the same stock recovery mode that comes with stock android! With this, I cannot flash the custom ROM because it gives the error that verification failed.
I have tried installing TWRP through goo manager as well, but when I choose the openrecoveryscript option, it says that nothing was found for my device.
What am I missing here? How can I install this custom recovery to allow me to flash a custom ROM?
I also tried this with 2 different versions of TWRP - 2.5.0.0-quincyatt.img and the latest 2.6.3.0-quincyatt.img
This may seem like a silly question but does the TWRP package include root in it? I have had to root with Clockwork mod tar first and then I have installed TWRP after that.
There are free utilities on Google Play that can tell you if you are rooted or not.
Download the 2.6.1.0.IMG.tar file and flash it. Also change the USB port you are using, and reinstall the Samsung USB drivers before attempting it again.
fraughtsigewulf said:
This may seem like a silly question but does the TWRP package include root in it? I have had to root with Clockwork mod tar first and then I have installed TWRP after that.
There are free utilities on Google Play that can tell you if you are rooted or not.
Click to expand...
Click to collapse
according to others, you do not need to be rooted to flash a rom.
I flashed a zip file for TWRP, just like a normal rom. once you flash, it replaces your cwm.
the error????????? if it is status 7, your recovery needs to be updated
OK, I've solved the problem. I followed another video that said to uncheck auto reboot on odin when installing TWRP, then remove the battery and unplug once it loads it on. I did this, and ended up bricking my phone, it wouldn't start saying need to fix bad firmware in kies recovery. Kies wouldn't even detect my phone at this point, so I started Odin again and was able to run a recovery from there by pressing start, it said it removed something, and was successfully recovered. I tried rebooting into recovery mode again on my phone, and magically it loaded into TWRP! From there I was able to flash the custom Revolt ROM and now my phone is running fine.
You got it. The Canadian phones have a script that reinstalls the 3e stock recovery on the reboot. So you have to pull the battery to stoo that script from running. When you rhen boot into recovery it makes it the default recovery.
ok, i've flashed via odin, pulled the battery and started it up but it still goes to stock recovery.
I've also flashed, shut it down, pulled the battery, rebooted and then selected reboot in recovery with no luck either.
Am I missing something?
Thanks
rangercaptain said:
You got it. The Canadian phones have a script that reinstalls the 3e stock recovery on the reboot. So you have to pull the battery to stoo that script from running. When you rhen boot into recovery it makes it the default recovery.
Click to expand...
Click to collapse
Thanks! I was trying to instal ClockworkMod Recovery with no luck, I have an Australian Version of GT-I9506, and your tip worked for me! Solved... :victory::victory:
can't get it done
rangercaptain said:
You got it. The Canadian phones have a script that reinstalls the 3e stock recovery on the reboot. So you have to pull the battery to stoo that script from running. When you rhen boot into recovery it makes it the default recovery.
Click to expand...
Click to collapse
I just can't get recovery to work after pulling the battery, it keeps on saying firmware error. What I am doing wrong?
rangercaptain said:
You got it. The Canadian phones have a script that reinstalls the 3e stock recovery on the reboot. So you have to pull the battery to stoo that script from running. When you rhen boot into recovery it makes it the default recovery.
Click to expand...
Click to collapse
mayoni said:
I just can't get recovery to work after pulling the battery, it keeps on saying firmware error. What I am doing wrong?
Click to expand...
Click to collapse
I'm having the same problem with an SGH-I717R. I flash TWRP with ODIN, pull the battery and disconnect the USB cable so the phone powers off. Then I hold Vol Up+Vol Down+Power until the phone vibrates, I see the "Samsung Note" logo on the screen for a fraction of a second, then it goes into "ODIN MODE", tells me how many custom binaries I've flashed, etc, and says "Firmware upgrade encountered and issue" and tells me to run recovery from Kies. If I restart the device normally, it goes into this mode as well. I can return the phone to a usable state by booting into download mode, flashing TWRP again with ODIN, then letting the phone reboot without holding any buttons down, but then recovery is back to stock 3e.
I've also tried this using CWM and Heimdall, as per the instructions on the CM wiki, with the same results. I've uninstalled and reinstalled the USB drivers and also enabled USB debugging on the device, since I read somewhere that might be an issue. I realize I'm replying to a 2-year old comment from rangercaptain, but do you have any more suggestions?
mdm_ said:
I'm having the same problem with an SGH-I717R. I flash TWRP with ODIN, pull the battery and disconnect the USB cable so the phone powers off. Then I hold Vol Up+Vol Down+Power until the phone vibrates, I see the "Samsung Note" logo on the screen for a fraction of a second, then it goes into "ODIN MODE", tells me how many custom binaries I've flashed, etc, and says "Firmware upgrade encountered and issue" and tells me to run recovery from Kies. If I restart the device normally, it goes into this mode as well. I can return the phone to a usable state by booting into download mode, flashing TWRP again with ODIN, then letting the phone reboot without holding any buttons down, but then recovery is back to stock 3e.
I've also tried this using CWM and Heimdall, as per the instructions on the CM wiki, with the same results. I've uninstalled and reinstalled the USB drivers and also enabled USB debugging on the device, since I read somewhere that might be an issue. I realize I'm replying to a 2-year old comment from rangercaptain, but do you have any more suggestions?
Click to expand...
Click to collapse
There is an Odin flashable cwm at rootgalaxynote. Once that is flashed you can load a su zip to your phone and flash or change to twrp by flashing it with cwm..not Odin. You then just reboot to recovery and you will be in twrp. You should probably use one from gimmeitorilltell version 2.8.0.0 or higher. I use 2.8.0.0 as it supports theming still. If you need more detail hit me up for the links. Searching the forum or googling should get you there though.
Sent from my SAMSUNG-SGH-I717
developweb said:
There is an Odin flashable cwm at rootgalaxynote. Once that is flashed you can load a su zip to your phone and flash or change to twrp by flashing it with cwm..not Odin. You then just reboot to recovery and you will be in twrp. You should probably use one from gimmeitorilltell version 2.8.0.0 or higher. I use 2.8.0.0 as it supports theming still. If you need more detail hit me up for the links. Searching the forum or googling should get you there though.
Sent from my SAMSUNG-SGH-I717
Click to expand...
Click to collapse
Thanks for the pointers! Would you say this tutorial[1] is more or less what you're suggesting I try? And then from there, flash TWRP 2.8.0.0 from CWM recovery?
[1] XDA won't let me embed a link because my account is too new, but it's a page on rootgalaxynote that ends with /galaxy-note-i717-roms/how-to-root-att-galaxy-note-sgh-i717-icsgingerbreadeasiest-method/
EDIT: Ugh, scratch that idea. I followed the instructions on that site and exactly the same thing happened. Flashing CWM through ODIN appears to work fine, but if I reboot immediately after flashing I end up with stock 3e recovery again, and if I hold Vol Up+Vol Down+Power to reboot immediately after flashing, I get the ODIN mode "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again." message and can't get past it until I flash CWM with ODIN again and let the stock recovery overwrite on reboot.
EDIT #2: So I finally got it to boot CWM by holding Vol Up+Vol Down as ODIN reboots the device, but trying to flash the Superuser zip from that site results in an error and the instant you boot system, it overwrites recovery with stock again. Am I correct to assume that if I can get into CWM and flash a custom ROM, recovery will stop being reset to stock on every boot?
mdm_ said:
Thanks for the pointers! Would you say this tutorial[1] is more or less what you're suggesting I try? And then from there, flash TWRP 2.8.0.0 from CWM recovery?
[1] XDA won't let me embed a link because my account is too new, but it's a page on rootgalaxynote that ends with /galaxy-note-i717-roms/how-to-root-att-galaxy-note-sgh-i717-icsgingerbreadeasiest-method/
EDIT: Ugh, scratch that idea. I followed the instructions on that site and exactly the same thing happened. Flashing CWM through ODIN appears to work fine, but if I reboot immediately after flashing I end up with stock 3e recovery again, and if I hold Vol Up+Vol Down+Power to reboot immediately after flashing, I get the ODIN mode "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again." message and can't get past it until I flash CWM with ODIN again and let the stock recovery overwrite on reboot.
EDIT #2: So I finally got it to boot CWM by holding Vol Up+Vol Down as ODIN reboots the device, but trying to flash the Superuser zip from that site results in an error and the instant you boot system, it overwrites recovery with stock again. Am I correct to assume that if I can get into CWM and flash a custom ROM, recovery will stop being reset to stock on every boot?
Click to expand...
Click to collapse
Did you repeat steps as instructed at this point?
If you get any errors at this point, don’t worry about it and repeat Steps 13 to Step 16 twice more and reboot. You will still get root.
Sent from my SAMSUNG-SGH-I717
developweb said:
Did you repeat steps as instructed at this point?
If you get any errors at this point, don’t worry about it and repeat Steps 13 to Step 16 twice more and reboot. You will still get root.
Sent from my SAMSUNG-SGH-I717
Click to expand...
Click to collapse
Yep, I was finally able to root the device doing that, but I still can't get CWM recovery to persist. I can flash it with ODIN, then hold down Vol Up+Vol Down as ODIN resets the device, which gets me into CWM recovery. From there I can do the usual CWM recovery stuff, and if I reboot, then hold down Vol Up+Vol Down immediately, I can get back into CWM recovery. I can do this as many times as I like and it always brings up CWM recovery. As soon as I let the phone boot the stock OS, CWM recovery is gone and I'm back to stock 3e. My end goal is to flash a custom ROM to this device; I assume if I do that, the stock recovery will stop being restored on every boot?
mdm_ said:
Yep, I was finally able to root the device doing that, but I still can't get CWM recovery to persist. I can flash it with ODIN, then hold down Vol Up+Vol Down as ODIN resets the device, which gets me into CWM recovery. From there I can do the usual CWM recovery stuff, and if I reboot, then hold down Vol Up+Vol Down immediately, I can get back into CWM recovery. I can do this as many times as I like and it always brings up CWM recovery. As soon as I let the phone boot the stock OS, CWM recovery is gone and I'm back to stock 3e. My end goal is to flash a custom ROM to this device; I assume if I do that, the stock recovery will stop being restored on every boot?
Click to expand...
Click to collapse
Sorry this didn't work for you, but I'll throw in the last bit anyway.
" With Android 4.0.4 update, your phone might overwrite the ClockworkMod Recovery you flashed in ODIN. To get around the problem, simply flash ClockworkMod Recovery again in ODIN, then when you see “PASS!”, immediately hold down Volume Up and Volume Down buttons, you should be in ClockworkMod Recovery instead of the Belly-up Andy Android figure."
Sent from my SAMSUNG-SGH-I717
Same Problem
Huge problem
Hey guys -
I'm having trouble getting CWM Recovery to work with my YP-G70. I've rooted, installed ROM Manager, wiped data and partitions, installed Odin, Used Odin to (supposedly) flash the DD_01142012.tar recovery to the device. Everything looks successful, but when booting back up ROM manager only gives me the option to go to "recovery setup" instead of the normal flash option. Even when I reboot it in recovery, it just goes to the standard android recovery screen. Any ideas on how to fix this? It may be painfully obvious, this is my first root.
Hydraulix_93 said:
Hey guys -
I'm having trouble getting CWM Recovery to work with my YP-G70. I've rooted, installed ROM Manager, wiped data and partitions, installed Odin, Used Odin to (supposedly) flash the DD_01142012.tar recovery to the device. Everything looks successful, but when booting back up ROM manager only gives me the option to go to "recovery setup" instead of the normal flash option. Even when I reboot it in recovery, it just goes to the standard android recovery screen. Any ideas on how to fix this? It may be painfully obvious, this is my first root.
Click to expand...
Click to collapse
Rom Manager does not work for this device ( I think ) and you should not use it. "DD_01142012.tar" is not just a recovery, it's the kernel too. They are integrated. Flash it again and hold power and vol-up during boot up to get to recovery then flash your rom...
I had my phone rooted with SuperSU. Decided that I wanted to use Magisk for the hide root features. Re-Flashed my phone to Stock Firmware, then checked if TWRP was still installed. It wasn't so I flashed it with ADB said that it flashed but I can not boot into it. When I go into recovery it boots to factory recovery.
I've tried erasing the the recovery and re-flashing with TWRP through ADB still boots to factory.
I have my bootloadrer unlocked from with I rooted the first time. Under Developer option it's Greyed out in the On position. Oh and USB Debugging is on.
Any help will be appreciated.
Keaso said:
I had my phone rooted with SuperSU. Decided that I wanted to use Magisk for the hide root features. Re-Flashed my phone to Stock Firmware, then checked if TWRP was still installed. It wasn't so I flashed it with ADB said that it flashed but I can not boot into it. When I go into recovery it boots to factory recovery.
I've tried erasing the the recovery and re-flashing with TWRP through ADB still boots to factory.
I have my bootloadrer unlocked from with I rooted the first time. Under Developer option it's Greyed out in the On position. Oh and USB Debugging is on.
Any help will be appreciated.
Click to expand...
Click to collapse
If you can boot your phone into system, download flashify. I had similar problem recently. Flashify helped me flash twrp into my phone & I was able to get into recovery with no problem. Also download a copy of twrp into o your phone.
PS: did you try to flash with the fastboot command? I've always had issues when I try to do anything with adb on this phone.
Keaso said:
I had my phone rooted with SuperSU. Decided that I wanted to use Magisk for the hide root features. Re-Flashed my phone to Stock Firmware, then checked if TWRP was still installed. It wasn't so I flashed it with ADB said that it flashed but I can not boot into it. When I go into recovery it boots to factory recovery.
I've tried erasing the the recovery and re-flashing with TWRP through ADB still boots to factory.
I have my bootloadrer unlocked from with I rooted the first time. Under Developer option it's Greyed out in the On position. Oh and USB Debugging is on.
Any help will be appreciated.
Click to expand...
Click to collapse
Hopefully you got this fixed dalready but I'm pretty sure after flashing twrp you are just rebooting without removing battery to power down, I had the same problem when I didn't remove batt. then put back in and boot to recovery that way. I guess the stock system will replace twrp if it gets booted into os before you boot into recovery.. Hope this helps.
Its the white screen throwing you off right click yes on both continue to hold voulme down and power then it will boot to twrp. Any it will not i repeat it will not wipe your data even thow you chose yes on white screen, hope this helps.
I'm in the same position as the OP, Keaso.
Bootloader unlocked, loaded custom recovery through fastboot, battery removed, but when I boot into recovery, I get the stock recovery, white screen, if I select yes and yes, it goes back to the factory white screen. And contrary to what 420bud420 posted, it DOES I repeat it DOES wipe your data.
This does not seem like an uncommon glitch with this phone, any help appreciated.
Double post