Howdy.
I royally screwed up somehow and my G2 on Sprint is now soft bricked.
So here's what happened: I had been running an unofficial CM 10.2 ROM on my phone and I saw that the official nightlies were available and apparently pretty stable, so I decided to try that out. I backed up what I need and went into TWRP to wipe system and I flashed the original G2 ROM so that I could update PRL before I dove into CM 11. Well, when it booted into the stock ROM, it started to download a new update which I couldn't stop and it rebooted to install it. I figured there was no harm in that, but it turns out there was because it would not install and it was stuck at 0% for a good hour, so I decided to force it to shut down, wipe the system and re-flash the unofficial CM, but it wouldn't boot.
Everything I tried only went straight into TWRP and I have become stuck there. Well, I did the stupid thing and I advanced wiped my system and cleared the internal storage as well because I thought that might help. Now I have no backup, but it charges through the usb cable and I can ADB push files for installation. So far, all of my efforts to install and boot a ROM have not worked and I am currently in a state of TWRP limbo and can't get out.
Any suggestions as to what I can do? Thanks.
how did you solve it? I've the same problem
this way? adb sideload https://www.youtube.com/watch?v=CivvxcM1PCY
Related
Soooo. The photon i've been using since june lost it's identity (IMEI, ESN, MEID, etc. all GONE and DFS tool kept throwing nasty errors every time it tried to read or write to the phone) so i swapped the board out of my other photon with a broken screen into the pristine chassis of the amnesiac phone.
now the fun starts: i RSD back to stock to activate the phone, all's good while i'm on stock. but if i flash a rom like skrillax's CM 10.2, the phone will boot fine the first time, then upon reboot will hang at the unlocked bootloader warning screen. restoring a backup of stock fixes this issue, but i'd really love to have my CM back
Any ideas?
Weird
I had that once, during my endeavors. After wiping cache and dalvik again, it finally booted after like 5 minutes, though (never had anything take that long to rebuild the dalvik, though)
...but I assume you tried that already. Hrm.
angahith said:
Weird
I had that once, during my endeavors. After wiping cache and dalvik again, it finally booted after like 5 minutes, though (never had anything take that long to rebuild the dalvik, though)
...but I assume you tried that already. Hrm.
Click to expand...
Click to collapse
well, i wiped everything (system, data, cache, and dalvik) like 4 times and flashed again. It did hang on reboot again, but i wiped cache and dalvik 3 more times and it's working great now!.
Thanks for the advice!
solitarywarrior1 said:
well, i wiped everything (system, data, cache, and dalvik) like 4 times and flashed again. It did hang on reboot again, but i wiped cache and dalvik 3 more times and it's working great now!.
Thanks for the advice!
Click to expand...
Click to collapse
Update: it still seems to have issues rebooting without clearing caches, but shutting it down and cold-booting works perfectly.
solitarywarrior1 said:
Update: it still seems to have issues rebooting without clearing caches, but shutting it down and cold-booting works perfectly.
Click to expand...
Click to collapse
I just ran into this issue too, after flashing CM10.2.
I can't boot any ROM right now. The phone always shows the unlocked bootloader screen and returns (without button press) to the recovery..
I will try flashing the stock FW with RSD Lite.
I have just been searching for a reason for this issue also.
I was running stock jelly bean, unlocked, twrp. Flashed CM 10.2, and it runs fine right until I reboot the device then it hangs at the red Motorola symbol. I have to hold the power button until it starts vibrating to shut it off. If I boot into recovery and do a factory reset it will then boot again.
I have tried updating to the latest version of TWRP (from 2.5), and tried both Milestone and Nightly versions of CM. I have flashed this phone at least 20 times today. Issue persists with or without Gapps.
I REALLY don't want to go back to stock after all this time I've spent, any ideas on what is causing this?
i had a similar problem monthes ago. i was able to boot but its not a fix more a workaround.
go to bootloader menu (Power+Vol-Up+Vol-Down)
and try the first option it called "normal powerup"
if it not work go again to bootloader menu and try "BP Tool"
same problem here...
after flashing cyanogenmod 10.2 and the first reboot the phone hangs
i restored original moto 4.1.2 from nandroid and now phone runs without problems. is there a problem with cm 10.2 ?
i used last night 20131127 gsm and swapped bootloaderimage.
Know this is an old thread, but after Motorola recently announced that they won't be bringing KitKat to the Photon Q, I finally decided to root and flash mine.
Can't begin to say how disappointed I am at Motorola on this one - the MSM8960 is well supported by KitKat and there are no technical reasons not to... at least Motorola is tactily admitting this is a penny-pinching business decision.
Anyways, I'm stuck at the same hang. Tried flashing known-good Photon Q builds and using the latest TWRP.
It took three flashes just to get the latest stable TWRP for it to take. I suspect the "JBBL" (Motorola Jelly Bean-era Boot Loader) is at fault here. CM just committed some patches to (in the near future) resume issuing builds for JBBL devices, but that won't fix the underlying problems.
And, since Motorola is abandoning the device, it looks like those won't get fixed either.
My next step is to restore via RSDLite, update PRL, Firmware, and Profile in stock ROM, and then start over. Disturbing that's needed, but now Motorola is Lenovo's problem I guess.
How long did you let it boot? Out of five XT897's I've owned, one woul ALWAYS take 15-60 minutes after an initial flash. I guess something was wrong with the memory. After an RSD-return-to-stock and back to CM it would take at least an hour to boot (repair process in the back during bootloader-logo). A wipe (internal too) and CM and it would take 10-15 minutes to get past bootloader logo.
Yesterday I restored a nandroid, wouldn't boot. Installed via zip and 15 minutes later it did boot again.
So just maybe you also have one of those special Photon's . It's worth a try.
I used TWRP 2.7.1.1 and M8 Snapshot in case you were wondering.
Hi all
I’m a complete noob at this and it seems like I have got myself into a bit of a pickle. Sorry for the massive description but I thought it would make it easier to get a good answer.
My Phone:
Samsung Galaxy S4 GT 19505 LTE
PDA I9505XXUEMK8
CSC I9505BTUEMK5
MODEM I9505XXUEMK8
I successfully rooted my phone using Odin. In Odin I added the "CF-Auto-Root-jflte-jfltexx-gti9505.tar.md5" file to the PDA field then rebooted the device. Then I added the "openrecovery-twrp-2.6.3.1-jfltexx" file to the PDA field, rebooted the device and the phone automatically opened in TWRP recovery. In recovery mode I wiped the cache, system and dalvik cache. I then went to install, browsed to the "I9505 Official_Google_Edition_4.3_by_Jamal2367_Finaly_v2.0" file on my SD card, rebooted the device and the Google logo came up on the screen for a few minutes and all was good. Got my new ROM, ran a root checker and all was good.
After some research I decided I wanted to use the Pacman ROM as it seemed to a lot more customisable. Using the same method I went to TWRP recovery wiped the cache, system, and dalvik cache. I then went to Install, browsed for the pacman ROM and the Gapps file on my SD card and everything installed ok, the phone restarted and the pacman logo came up everything was fine. Although I did notice on start up that I got this message.(and have had this error message ever since)
kernel is not seandriod enforcing
set warranty bit : kernel
After using the Pacman ROM for a day I noticed a lot of bugs like my apps would disappear, I couldn't use my banking apps and my phone was generally performing very badly. So I decided to remove the ROM and use CyanogenMod ROM under the recommendation of a friend. So again I pressed home+power+vol up to enter recovery mode but this time it didn’t enter the TWRP recovery it entered the stock recovery mode. This was slightly concerning but I proceeded to use the list menu and cleared the cache etc, browsed the SD card and went to the CyanogenMod 10.2 ROM I previously downloaded. It began to install but in red I got the error message stating that I didn’t have the right permission or signature. The phone rebooted back to the Pacman ROM. I tried the above three times and it still continued to boot back into Pacman ROM sometimes I struggled to even get back into recovery mode.
Soooooo I decided to try and go back to the Google Edition 4.3 ROM and play it safe, using the method from my first paragraph. But when it installed through TWRP I got an error message saying cant find MD5 file. The device rebooted and the Google edition logo came up on the screen but it seems to be locked in a loop. The Google logo wont go away and the phone vibrates once then three times quickly every 10 seconds.
I can still enter both TWRP recover and Download Mode. But I don’t want to mess around with it anymore without getting some advice. Any help would be much appreciated as I really need my phone working.
Thanks again
Aiden
Did you create a backup while on your first run with google edition? If so wipe cache, system, and dalvik and restore to your backup. Should put you back to where you began.
Sent from my LGMS769 using XDA Premium 4 mobile app
I know I should, but I didnt. Is it still fixable ?
*Update*
Couldnt help myself had to have a tinker around. Managed to get Cyanogenmod 10 working with Gapps. Gonna see how I get on with this. Although still would like to know I have been having all these problems.
Sometimes things just dont go as planned: p I have easily soft bricked my phone around 10 times and always able to fix it. You really should have made a stock backup before flashing anything. I recommend doing it now so you at least have a known working configuation backed up for future use. Trust me backups are your friends!
Sent from my LGMS769 using XDA Premium 4 mobile app
Thanks for your replies.
Ye gonna that right now Cyan Mod so far is running very smooth without any problems.
Regards
Aiden
Okay, so just today I was looking through some articles and saw that Android 4.4.4 was able to be downloaded for the Moto G, I have a rooted Moto G, so I know that I can't install the OTA updates without reverting back to stock.
So it was early in the morning, I was still tired and not thinking strait; and I forgot that I couldn't install the OTA updates without reverting; So I made an idiotic mistake and used the settings update method to download the new version..... so now I am stuck in a boot loop because when ever I get to the Clockworkmod recovery, it says it can't complete it and it reboots my phone. Then the phone detects the phone didn't update and it goes into recovery. This just keeps happening over, and over, and over again,
See, the thing is, I would revert back to the stock, but I can't install the stock onto the internal SD because the phone reboots before I can actually get the stock zip onto the phone... so I'm stuck at this point, and I really don't know what to do... and I really don't think there is much I can do at this point.
Here Is My Phone Info:
Model: XT1031
Clockworkmod Recovery Version: v6.0.4.7
Can you turn off the phone with the power button and then boot in to recovery?
If that works try deleting the update zip from /cache directory with cwm.
meekrawb said:
Can you turn off the phone with the power button and then boot in to recovery?
If that works try deleting the update zip from /cache directory with cwm.
Click to expand...
Click to collapse
I've already tried this, It hasn't worked the three times I've done it. I have got it to stop rebooting, and I've got it to the original recovery. The 4.4.4 update isn't showing up anymore though. My battery is always at 1% battery now too.... so now I have another problem.
xLOLxTSNOOPS said:
I've already tried this, It hasn't worked the three times I've done it. I have got it to stop rebooting, and I've got it to the original recovery. The 4.4.4 update isn't showing up anymore though. My battery is always at 1% battery now too.... so now I have another problem.
Click to expand...
Click to collapse
Leave it plugged in for a few hours and then fastboot flash the stock firmware for your model number.
Unless someone else knows an easier way to get you going.
I went to bed last night, did what I normally do, set my alarm and turned on sleep tracking. I woke up this morning to find that my phone had booted back into TWRP. I rebooted and found that after the LG screen it goes directly into TWRP which had replaced factory reset using bump. I tried to restore the phone using a saved backup and that didn't work. I tried to wipe it then restore and that didn't work. I am afraid that my phone is a lost cause and that I cannot get a replacement due to it booting to the TWRP screen every time it is turned on. The phone had been working fine for the past week since I had installed TWRP. Does anyone have any suggestions on what to do or what might have caused this?
Look in the lg g3 international forum there is a fix there your phone tried to flash a ota update
jerrycoffman45 said:
Look in the lg g3 international forum there is a fix there your phone tried to flash a ota update
Click to expand...
Click to collapse
Sounds awesome thanks.
All the times that I tried to it to flash a ROM itself it doesn't do it but it does it by itself.
Here is a link http://forum.xda-developers.com/showthread.php?t=2908290 after you fix it freeze software update with titanium backup
I cannot get the first step to work. ADB cannot see the device. I tried installing the Google USB Driver but that didn't work and TWRP ADB sideload doesn't work either.
EDIT: I put the zip on my phone using MTP and flashed it using TWRP but it still stuck booting into TWRP.
EDIT 2: Tried one more time again after flashing my backup ROM. Now it loads.
I can't help more on a road trip sorry
Try this, worked for me
Go to this website and do what ot says. http://forum.xda-developers.com/newreply.php?do=newreply&noquote=1&p=57453756 this should fix it. I had the same issue and this worked :good: sorry if im late.
Hello, I need serious help with my phone.
So, after a long while of having my phone rooted, and had a case of boot loop with twrp, I decided to go back to stock os and hung up the root days. I thought i did it right by getting a stock os and flashed it, and it worked for couple months, until yesterday.
My phone keeps going into Cyanogen Recovery, I tried rebooting so many times, once it did boot up to OS, but it went back after i restarted phone or it died.
Now I can't no longer get back, I thought factory resetting will work but it didn't. (Tried both wipe cache partition and Full factory reset option from the recovery) I found unroot your phone toolkits, thinking it could help fix my problem and just unroot/ give me back to OS (I wished i found this before flashing that custom stock rom).
But the toolkit doesn't work for me, it finds adb devices, but it cant find fast boot devices, because my phone cant even go into fast boot.
I tried manual, and the option from the recovery, it keeps going back to recovery. I have an option for apply update, and then apply from ADB, that was the only way for my pc to recognize my phone from adb devices. Any clues on how to fix?
Hi !
I may suggest you this thread https://forum.xda-developers.com/oneplus-one/general/tool-oneplus-one-return-to-stock-t2970390
Good luck !
xanthrax said:
Hi !
I may suggest you this thread https://forum.xda-developers.com/oneplus-one/general/tool-oneplus-one-return-to-stock-t2970390
Good luck !
Click to expand...
Click to collapse
Will try, Ill respond back if anything happens!
Hmm I'm still having trouble because, I can't get into fast boot for some reason. It's keep going back to Cyanogen recovery. It has the option to reload into bootloader, but goes into cyanogen recovery again.
There is an option in dev options, uncheck the "update cyanogen recovery" and flash twrp again
Sent from my SHIELD Tablet using Tapatalk