Hi,
I'm not very knowledgeable with this phone.
I updated the phone, but then it went into CWM-based Recovery screen and it won't let me get to the home screen. I have no idea what to do. Please help.
ogee87 said:
Hi,
I'm not very knowledgeable with this phone.
I updated the phone, but then it went into CWM-based Recovery screen and it won't let me get to the home screen. I have no idea what to do. Please help.
Click to expand...
Click to collapse
You have soft bricked your phone. The update will only work if NEITHER CWM or TWRP recoveries are installed. You must be on stock recovery for the update to work, otherwise you end up where you are - soft bricked.
Now you will have to help yourself. Either you are going to have to read and learn how to use LG Flash Tool to re-install a stock ROM, or you are going to have to use ADB to try and undo what you've done - see this post: http://forum.xda-developers.com/showpost.php?p=49370751&postcount=70
Also, be advised that if you restore your phone and then update while you are unrooted, the new update will prevent you from rooting your phone.
Thanks visionlogic for your replied. I almost updated before re-rooting it. You saved me! THANK!
visionlogic said:
You have soft bricked your phone. The update will only work if NEITHER CWM or TWRP recoveries are installed. You must be on stock recovery for the update to work, otherwise you end up where you are - soft bricked.
Now you will have to help yourself. Either you are going to have to read and learn how to use LG Flash Tool to re-install a stock ROM, or you are going to have to use ADB to try and undo what you've done - see this post: http://forum.xda-developers.com/showpost.php?p=49370751&postcount=70
Also, be advised that if you restore your phone and then update while you are unrooted, the new update will prevent you from rooting your phone.
Click to expand...
Click to collapse
Related
Hi,
This may be a stupid question but I'm new to Samsung phones so I don't know all the details (I've only been using HTC so far).
So I've followed all the steps and got root fine. However, I tried to reboot into recovery afterwards and it's like Clockworkmod has vanished.... It just gets into what looks to me like the stock recovery. Am I doing something wrong or does the phone automatically restore its stock recovery???
Also, can someone explain to me if it is possible to manually flash a recovery from the img file using fastboot like you do on HTC phones?
Oh, and another thing. What's this Odin thing? I never used anything like that with HTC...
Thanks
ovimunt said:
Hi,
This may be a stupid question but I'm new to Samsung phones so I don't know all the details (I've only been using HTC so far).
So I've followed all the steps and got root fine. However, I tried to reboot into recovery afterwards and it's like Clockworkmod has vanished.... It just gets into what looks to me like the stock recovery. Am I doing something wrong or does the phone automatically restore its stock recovery???
Also, can someone explain to me if it is possible to manually flash a recovery from the img file using fastboot like you do on HTC phones?
Oh, and another thing. What's this Odin thing? I never used anything like that with HTC...
Thanks
Click to expand...
Click to collapse
May I ask what variant you are using? GT-i9195?
Then please boot your phone into download mode, this can be done by first switching of your phone completely then holding the power button, home button and volume down button until the download screen appears where you press continue. Once you have done that connect your phone using the usb cable and make sure all drivers have been installed! Once the drivers are installed start up Odin uncheck the f.rest time box and click the AP section and then select the recovery file provided by Sir Arco in the root thread.
If you need more help please ask, If it worked then still reply
Odin is the software used to flash files to Samsung phones.
You will need to catch the first recovery boot after flashing the recovery image, or else the stock recovery will be reflashed once the phone boots up. Just reflash the recovery via Odin and make sure to boot into recovery right after the phone reboots after the flash.
Whosat said:
Odin is the software used to flash files to Samsung phones.
You will need to catch the first recovery boot after flashing the recovery image, or else the stock recovery will be reflashed once the phone boots up. Just reflash the recovery via Odin and make sure to boot into recovery right after the phone reboots after the flash.
Click to expand...
Click to collapse
Thanks for the response. Yeah, I kind of realized that's what's happening. I've managed to boot into the custom recovery right after the flash and did what I had to do in there, but then after I reboot the phone again, the custom recovery is gone. Is there a way to stop stock recovery being reflashed automatically?
Also, if I want to install a custom kernel, how can I backup the current one so that I can restore it at a later date if I need to? I know how to do this on HTC phones but it all seems to be a bit different on Samsung and I don't want to mess up anything.
How did you reboot? If you select the reboot option in the CWM recovery,it should follow with a question on whether you want to continue rebooting with reverting to stock recovery or not.
Whosat said:
How did you reboot? If you select the reboot option in the CWM recovery,it should follow with a question on whether you want to continue rebooting with reverting to stock recovery or not.
Click to expand...
Click to collapse
Umm... yeah, I think it did ask but I just accidentally pressed no before reading what it said... So I guess I'll just have to flash the recovery again and then answer yes to that question.
Thanks
Yes that would be the correct way to do it.
Hope all goes well!
Okay so here's the thing. I been following XDA for a while and I never had a problem with rooting and installing roms. Yesterday we received a Samsung Galaxy Tab 3 from Sprint. I believed it's the T217S version but anyways I looked up info and found out how to root it and put a custom recovery. Everything went fine until I decided to install the Remedy Rom. Now I wasn't sure if I had to wipe anything but just to be safe I did except the SD card. After that I Installed the Remedy Rom but before I could install the Knox Remover 1.2 it had already rebooted when it rebooted it bricked on the Samsung Logo. Now I began to panic but I researched and found out running the Stock Rom from Odin would fix this little issue. After running it back to stock. I again tried to get into Recovery but this time I got a different Recovery it said no command in the background and in the top Android system recovery. I remember I installed TWRP. I'm not sure what went wrong but now I can't restore it back to how it was. I can't even get into download mode to re root it.
Can anyone help me with this dilemma?
Can no one help me with this issue?
There was a recent sprint update to this device as of a few days ago. It's possible that the older rooting and recovery may not be compatible.
You might be able to Odin back to the prior version, then try root/recovery.
cougarcougar said:
There was a recent sprint update to this device as of a few days ago. It's possible that the older rooting and recovery may not be compatible.
You might be able to Odin back to the prior version, then try root/recovery.
Click to expand...
Click to collapse
Thank you for the reply. As I said I cant access download mode anymore so how can I run Odin through it? I can still boot into the Device itself I just can't enter recovery or download mode.
Hello,
I'm sure there are many threads on about what I'm about to asked but I am a noob and I don't know what to do!!
I tried to flash cm11 to my I747 last night but it failed. So I tried to flash my recovery and it failed at first but second time around it was successful. Only thing is that when it booted, it got stuck on AT&T splash. I left it for about 15-20 minutes but nothing happened. Wasn't sure if my screen was going to burn the image so I turned it off and removed the battery. I have been doing research on how to recover but I want to make sure I do everything correct so I can at least go back to stock.
If there is anyone out there that can please give me some help I would greatly appreciate it!
Thanks!!
Is this fixable?
loc626 said:
Hello,
I'm sure there are many threads on about what I'm about to asked but I am a noob and I don't know what to do!!
I tried to flash cm11 to my I747 last night but it failed. So I tried to flash my recovery and it failed at first but second time around it was successful. Only thing is that when it booted, it got stuck on AT&T splash. I left it for about 15-20 minutes but nothing happened. Wasn't sure if my screen was going to burn the image so I turned it off and removed the battery. I have been doing research on how to recover but I want to make sure I do everything correct so I can at least go back to stock.
If there is anyone out there that can please give me some help I would greatly appreciate it!
Thanks!!
Is this fixable?
Click to expand...
Click to collapse
\
Yeah. Should be fixable. First, can you try booting to recovery and doing a wipe/reset? I presume you have custom recovery? If this doesn't work, then you can try flashing a complete compatible stock restore image via recovery to get the phone working or flash a custom ROM? What Android version were you on prior to the attempt to flash CM? This would let us know what stock version to revert to.
I was running 4.3 before trying to flash the custom rom. I tried flash the stock rom last night using Odin, but it the flash failed on me twice. I also noticed that the micro sd I had in my cell is now completely dead. When I plug it into my pc it does not show up. I think it still shows up in recovery but it doesnt seem to be working. Im worried about sticking another card in and for some unknown reason it going dead too.
I only found a flash for 4.1.1 as far as stock rom goes.
loc626 said:
I was running 4.3 before trying to flash the custom rom. I tried flash the stock rom last night using Odin, but it the flash failed on me twice. I also noticed that the micro sd I had in my cell is now completely dead. When I plug it into my pc it does not show up. I think it still shows up in recovery but it doesnt seem to be working. Im worried about sticking another card in and for some unknown reason it going dead too.
I only found a flash for 4.1.1 as far as stock rom goes.
Click to expand...
Click to collapse
If you were already on 4.3, please do not try to flash 4.1.1 now otherwise you could risk bricking your phone. If you tried doing the hard wipe/reset via (custom) recovery and this did not work, you can try flashing a complete stock restore image via recovery. See the instructions in the following thread ....
http://forum.xda-developers.com/showthread.php?t=2658486
Unfortunately, you would need to load the stock restore zip to a (micro) SD card. Unless you are able to save files to your phone, there is no other way. Once you have the restore zip ready, boot your phone to recovery mode and flash. You can revert to a custom ROM once your phone is back to working normally.
I had this problem TeamWin Recovery. I put Philz recover on there and it worked fine. You will probably have to ADB philz recovery to your phone, if you chose to try Philz. This is what worked when I rooted my girlfriend's phone.
An easy way to install Philz Touch recovery would be to download and install the latest tar version for the d2lte and flash it via Odin.
http://goo.im/devs/philz_touch/CWM_Advanced_Edition/d2lte
Thanks to everyone for your help and solutions.
My co-worker, who flashed my root and recovery, was able to get it back to 4.3 stock. Unfortunately, the backup that he made before rooting did not work in recovery [twrp]. So I lost all my pics from the last two months since getting my phone.
As sad as I was that I couldn't recover the pics, I am happy to have my phone back to normal+root.
I'm not sure, but maybe it bricked from trying to flash cm11 thru twrp?! Can't really say, but the recovery did not go thru either.... It went thru "successfully" but after I would reboot then it would stay on ATT splash.
Oh well... all is good now. I will steer away from custom roms for now and wait until the 4.4 update comes out for my i747. Or if i get another phone later on, I can use the s3 as a lab rat.
Again, thanks to everyone!
I've searched around for this specific problem and haven't found anything that will help me. I have the SPH-L710 model through Sprint that was previously running Android 4.4.2. That version killed the battery, so I attempted to root and install a custom ROM. I have rooted before, so superSU was already on the phone. I opted to follow the rooting directions from galaxys3root.com, which uses ClockworkMod Recovery v5.5.0.4. I did that and installed superSU again via a .zip file. When I rebooted the phone, superSU kept stopping. After some frustration, I found that there was an updated superSU v2.01 that I installed via CWM. Being an idiot, I figured I would just go right ahead and trying to install the custom ROM without checking anything. I then attempted to install the Carbon ROM 4.4.4 from galaxys3root.com without first making a backup of my existing version (again, idiot). There was some sort of error, and after that point, I was unable to boot up the phone...it would display the Samsung GS3 screen and then do a continuous bootloop.
I tried finding stock ROMS, but they usually have to be loaded from the SD card rather than through ODIN, and they so far haven't been working. I have downloaded more than one that claimed to be an MD5, but they turned out not to be. My wife has the exact same phone so I thought maybe if I use CWM to save a backup of hers to my SD card, perhaps I could restore that and boot up my phone. I got a bit farther this time and boot up made it through the Samsung GS3 and various Sprint 4g screens before getting stuck on the last Samsung screen.
If I can get the phone to boot up again, I've since learned that once you update superSU, you can have it disable knox, thereby allowing me to root, and thereby allowing me to install a custom ROM, but at this point I just need to get the phone to boot up so I can use it again.
Summary:
Attempted to root using CWM v5.5.0.4
Did not properly disable Knox first and had an error loading custom ROM
Phone stuck in bootloop
Did not back up phone first but have a backup of my wife's exact same model
Used that backup and it gets stuck on very last Samsung screen
Any and all help is appreciated.
Matt
huntley said:
Summary:
Attempted to root using CWM v5.5.0.4
Did not properly disable Knox first and had an error loading custom ROM
Phone stuck in bootloop
Did not back up phone first but have a backup of my wife's exact same model
Used that backup and it gets stuck on very last Samsung screen
Any and all help is appreciated.
Matt
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2738533 <-----Odin stock ND8 rom use Desktop Odin
https://goo.im/devs/philz_touch/CWM_Advanced_Edition/d2lte/philz_touch_6.48.4-d2lte.tar.md5/ <------flash this recovery through Odin as well it gives you the option to root the stock ND8 rom under Philz settings choose option re-root(SuperSU)
6th_Hokage said:
http://forum.xda-developers.com/showthread.php?t=2738533 <-----Odin stock ND8 rom use Desktop Odin
https://goo.im/devs/philz_touch/CWM_Advanced_Edition/d2lte/philz_touch_6.48.4-d2lte.tar.md5/ <------flash this recovery through Odin as well it gives you the option to root the stock ND8 rom under Philz settings choose option re-root(SuperSU)
Click to expand...
Click to collapse
Thank you. That image worked perfectly, and the recovery is a newer version than I was trying to use earlier.
huntley said:
Thank you. That image worked perfectly, and the recovery is a newer version than I was trying to use earlier.
Click to expand...
Click to collapse
i know lol but its the best one for stock ND8 honestly
HELP: I have CWM 6.0.5.1.4a and installed the latest rooted rom. Now I have a bricked device in boot loop. I am able to get into CWM with the ALT+i+prt scrn method.
I have tried installing varoius roms but my device does the same every time. It is just stuck in the color Fire TV logo.
Since I don’t have SU from CWM I cannot get ADB to upgrade to kernel boot menu or downgrade to stock firmware.
What should I do? Any help greatly appreciated!
I also tried the factory reset from CWM but with no result…
henningdalgaard said:
HELP: I have CWM 6.0.5.1.4a and installed the latest rooted rom. Now I have a bricked device in boot loop. I am able to get into CWM with the ALT+i+prt scrn method.
I have tried installing varoius roms but my device does the same every time. It is just stuck in the color Fire TV logo.
Since I don’t have SU from CWM I cannot get ADB to upgrade to kernel boot menu or downgrade to stock firmware.
What should I do? Any help greatly appreciated!
I also tried the factory reset from CWM but with no result…
Click to expand...
Click to collapse
Install 51.1.4.0 from CWM to fix it. Then follow all the instructions/requirements for the latest.
thanks! I installed 51.1.4.0 pre-rooted rom CWM and it worked. I thougt it failed and started the loop again but after a wile it booted into the amazon software.
I used the same one...
SSAPIR11 said:
I installed 51.1.4.0 to un-brick. i followed the guide to install su and busybox, verifited rom. I installed custom rom 51.1.5.0_515030720, rebooted and now stuck at amazon fireTV logo. any suggestions?
Click to expand...
Click to collapse
Seems you followed part of the guide but did you take all precautions? You need boot menu and unlocked bootloader for that fw. If you have these and confirmed they work, plus you checked mdsums...I can't imagine why it's in bootloop.
henningdalgaard said:
I am able to get into CWM with the ALT+i+prt scrn method.
Click to expand...
Click to collapse
What is that method exactly?
Alright, got a question, tried to find an answer everywhere.
Went to update to the newest version through CWM (51.1.5.0_515030720). Forgot to re-install Boot Menu, am now in a brick/bootloop. Despite what I've read, no amount of wiping the data/cache/dalvik cache gives me back the option to simply "reboot." In addition, all the guides tell me that I need to downgrade by installing 51.1.4.0_514006420. That's all well and good, but I have no way to get 51.1.4.0_514006420 onto my Fire TV to install it. Sideloading doesn't work, as ADB isn't functioning properly through CWM. Fastboot doesn't let me install roms or push files on.
Can someone please help me figure out what to do next? I can get to recovery, I have a keyboard, and I don't know how to get this older rom onto the Fire TV.
Neo3D said:
What is that method exactly?
Click to expand...
Click to collapse
there is a guide here:
http://www.aftvnews.com/how-to-unbrick-and-prevent-bricking-an-amazon-fire-tv/