I recently installed CyanogenMod 11 on my S3 about a month ago. Yesterday, I got a notification on my phone stating that an update was available for CyanogenMod. I let it install and when the phone rebooted, it was stuck on the bootloader for at least an hour or two. I figured that I must've bricked the phone. I can still get into recovery mode and download mode.
So, I tried to reinstall the stock AT&T GS3 ROM as I had never particularly liked CyanogenMod. I thought this would be a great time to reinstall the stock ROM. I factory reset the phone and flashed the stock ROM (which I downloaded from another thread) using Odin. It automatically rebooted, the Samsung logo flashed for a second and the CyanogenMod bootloader showed up and it has not gone away since. So, what have I done wrong here and is there a way to save my phone? Any help would be greatly appreciated.
Where did you get the ROM you flashed? Did your phone have the 4.3 bootloader? What about Knox?
If your phone has the 4.3 bootloader, you cannot flash the 4.3 ROM via Odin as it was never released as a complete ROM, only as an update. THis might help: http://forum.xda-developers.com/showthread.php?t=2658486
So the old ROM I was on (a super outdated Android Revolution) needed to be updated because my battery was draining a lot and I figured I would update everything. Apparently I flashed a bad or wrong version of TWRP, so I can't get into recovery. It just sits there trying to get into recovery but it keeps failing. Then I tried using MultiRom recovery and installing that through the app in the play store. Now my phone won't go into recovery and just boot loops. I can get into the HBOOT menu but I can't get into recovery or boot the device at all. Does anyone have any ideas to get a working recovery or working ROM? I already backed up my pictures and videos and stuff, but I forgot to transfer my titaniumbackup files I've been trying to look around and see how to fix it but I don't want to do something that will cause more damage than I've already done. I did all this to update my firmware so that I can use the newer ROMs. Anyway if anyone has any ideas I'm all ears.
Thanks in advance.
You didn't mention whether or not you are S-off and/or bootloader unlocked.
Since you already have a custom ROM, you must have unlocked your bootloader at some point, so if it is STILL unlocked, just reflash the correct recovery from fastboot. If it is not, unlock it with HTCdev first, then reflash the correct recovery.
Alternately, if you just want the phone fixed, you can always re-run the AT&T RUU - though that will trash any files you have on the phone.
Yeah that's what I did yesterday thanks for the response!
I've had Google phones for years now, including previous Pixel, but I just got an XL 2 yesterday and I'm regretting it.
It's Google unlocked and running June's latest image. I've experienced various app crashing on stock, and random reboots.
Then there's the rooting and flashing. I unlocked the bootloader and installed the most recent, twrp (the one verified to work on xda for roms) but can't flash anything.
My twrp either hangs on the twrp start screen, or when it does load, the touch screen doesn't work. When I can get it going, every rom I flash gives me an error on the second step. I'm flashing on slot B by the way, that's what boots up when I boot to twrp.
Lastly, I am unlocked both for flashing and flashing_critical thru adb, so I'm at a loss and seriously confused.
When I FIRST unlocked everything, I was able to flash Nitrogen rom but I got stuck at the rom splash screen.
Tldr:
-What is the Correct install method/sequence for roms?
-do the slots matter?
-is random reboots and app crashing on stock a sign of a hardware issue?
I haven't installed a custom ROM on my P2XL, so I'm running rooted stock. Anyway, for rooted stock, this is what I did.
Entered bootloader mode.
Booted into recovery using the command "fastboot boot recovery.img", where "recovery.img" is the TWRP recovery iteslf. In my case, I renamed it "taimen.img".
Flashed the TWRP installer zip needed for the P2XL (Required if intending to replace the stock recovery).
Rebooted into recovery.
Flashed a custom kernel (Recommended - resolves touch issues in TWRP).
Flashed Magisk.
6. Rebooted.
If installing a custom ROM, flash it prior to the custom kernel. Slots only matter if running stock. Random reboots and app crashes are not signs of a hardware issue.
stevew84 said:
I've had Google phones for years now, including previous Pixel, but I just got an XL 2 yesterday and I'm regretting it.
It's Google unlocked and running June's latest image. I've experienced various app crashing on stock, and random reboots.
Then there's the rooting and flashing. I unlocked the bootloader and installed the most recent, twrp (the one verified to work on xda for roms) but can't flash anything.
My twrp either hangs on the twrp start screen, or when it does load, the touch screen doesn't work. When I can get it going, every rom I flash gives me an error on the second step. I'm flashing on slot B by the way, that's what boots up when I boot to twrp.
Lastly, I am unlocked both for flashing and flashing_critical thru adb, so I'm at a loss and seriously confused.
When I FIRST unlocked everything, I was able to flash Nitrogen rom but I got stuck at the rom splash screen.
Tldr:
-What is the Correct install method/sequence for roms?
-do the slots matter?
-is random reboots and app crashing on stock a sign of a hardware issue?
Click to expand...
Click to collapse
Ya know my friend, after our conversation yesterday, and your questions in the nitrogen thread, and now random reboots and app crashes, I think it's time to consider a factory reset. You shouldn't be having those problems on a stock setup. If that's not successful, then I would definitely consider an RMA. Just my 2 cents worth :good:
I agree. I got it used tho which is an issue.
Badger50 said:
Ya know my friend, after our conversation yesterday, and your questions in the nitrogen thread, and now random reboots and app crashes, I think it's time to consider a factory reset. You shouldn't be having those problems on a stock setup. If that's not successful, then I would definitely consider an RMA. Just my 2 cents worth :good:
Click to expand...
Click to collapse
Just so you know, I got the rom to flash finally, but it's stuck at the rom splash screen during first boot. I'm going to leave it and hope it eventually boots up.
stevew84 said:
Just so you know, I got the rom to flash finally, but it's stuck at the rom splash screen during first boot. I'm going to leave it and hope it eventually boots up.
Click to expand...
Click to collapse
If it doesn't after 5 minutes, do a hard restart with the power button. If that doesn't work, then reboot to twrp and flash the rom and twrp installer zip again.
Ok cool thanks. I relocked bootloader last night and went back to stock. Unlocked it all this morning from my work computer and different unlock app. So here's hoping.
Badger50 said:
If it doesn't after 5 minutes, do a hard restart with the power button. If that doesn't work, then reboot to twrp and flash the rom and twrp installer zip again.
Click to expand...
Click to collapse
I finally got everything to work. My vendor image is a mismatch but I could just flash junes and be done with it, right?
stevew84 said:
I finally got everything to work. My vendor image is a mismatch but I could just flash junes and be done with it, right?
Click to expand...
Click to collapse
What did you do to get it to work? You could just flash the June vendor.img to both slots. If you keep getting a vendor mismatch, probably nothing to worry about according to the Dev of nitrogen.
Different machine, cable and unlocking tool.
But I went to bone stock with locked bootloader, then flashed the newest twrp with the newest all in one tool. Was on slot A so wiped everything and flashed rom plus twrp again. I rebooted system to slot B, but then it just hung at the rom splash screen.
So I did it all over on slot A, ignored the "no os installed" message and booted anyway. Then it fired up. Rebooting into twrp from there took me to B, which is where I need to be for an image file or root.
So yea, thanks for the help.
I'm having this issue also. I tried flashing nitrogen, it hung. I tried to go back with factory reset Img and nothing happens in adb. Flashed the may img and it wouldn't boot all the way up. Now I'm stuck in bootloader trying to figure this all out. Seems like nothing in doing is working. I can get recovery to boot, but no files inside so idk. Tried to sideloadb nitrogen, but it said adb out of date for device when sdk is fully updated.
MatthewRobinson said:
I'm having this issue also. I tried flashing nitrogen, it hung. I tried to go back with factory reset Img and nothing happens in adb. Flashed the may img and it wouldn't boot all the way up. Now I'm stuck in bootloader trying to figure this all out. Seems like nothing in doing is working. I can get recovery to boot, but no files inside so idk. Tried to sideloadb nitrogen, but it said adb out of date for device when sdk is fully updated.
Click to expand...
Click to collapse
You didn't mention the out of date message in your other post, but uninstall SDK and then download the stand-alone adb/fastboot binaries from May of this year. Dump that in a folder (eg. c:\adb) and put that folder in your path statement. Manually flash the full factory image without modifying flash-all.bat. Post your screeen if you have any errors. :good:
stevew84 said:
I agree. I got it used tho which is an issue.
Click to expand...
Click to collapse
Google knows the date the phone was purchased based on imei number and honors their warranty by date, not owner. Unless it was blacklisted.
smartymcfly said:
Google knows the date the phone was purchased based on imei number and honors their warranty based on that.
Click to expand...
Click to collapse
Thanks. I might try to take advantage.
So I flashed a firmware update from this post, since I wasn't able to go back to stock after flashing a custom rom. "Fastboot flashing and firmware". I flashed the firmware zip via fastboot, then I ran the RUU.exe and it said the installation was completed. However, upon the first boot, my devices get stuck into the " HTC powered by Android" screen and stays there for a long time and nothing happens. I have left it for hours to see if it finally boots up but nothing happens.
My devices model is 2SP6500 US unlocked version.
It is worth mentioning that my device was originally tmobile version but after a few tweaks I convert it to the us unlock version. At first, everything worked perfect. But when I was running the US unlocked version I decided to try a custom ROM . But then I decided to go back to stock so I re-flashed the RUU.exe and that's where the problem begun. For some f#$ing reason i cant got back to stock
It is also worth mentioning that I'm able to use Resurrection Remix and LineageOS, everything boots up and all, but for some fu#ing reason, I can't go back to stock.
Now I have a very expensive paperweight.:crying::crying:
fry98654 said:
So I flashed a firmware update from this post, since I wasn't able to go back to stock after flashing a custom rom. "Fastboot flashing and firmware". I flashed the firmware zip via fastboot, then I ran the RUU.exe and it said the installation was completed. However, upon the first boot, my devices get stuck into the " HTC powered by Android" screen and stays there for a long time and nothing happens. I have left it for hours to see if it finally boots up but nothing happens.
My devices model is 2SP6500 US unlocked version.
It is worth mentioning that my device was originally tmobile version but after a few tweaks I convert it to the us unlock version. At first, everything worked perfect. But when I was running the US unlocked version I decided to try a custom ROM . But then I decided to go back to stock so I re-flashed the RUU.exe and that's where the problem begun. For some f#$ing reason i cant got back to stock
It is also worth mentioning that I'm able to use Resurrection Remix and LineageOS, everything boots up and all, but for some fu#ing reason, I can't go back to stock.
Now I have a very expensive paperweight.:crying::crying:
Click to expand...
Click to collapse
Download the ruu zip for your variant and run it from your SD card. No reason why you can't go back to stock
I recently dug out my old G4 to see if I can repurpose it for anything or just have it as a back up.
It's an H815 European variant with unlocked bootloader. When I last used it I had it running a custom ROM but when I got a new phone I wiped it somehow with TWRP (this is a few years ago so I can't remember).
Now whenever I turn it on, it boots into TWRP. If from TWRP I choose reboot to system, it boots to TWRP.
I tried to install a ROM but it wouldn't, giving the error "this ROM is for P1,G4,H815 (or something like that), your device is .".
So, I edited the ROM metadata and took out the device requirements and it installed fine, as did GAPPs & SuperSU, but still it only boots to TWRP. I've flashed bootloaders, kernels, god knows what else, but it only boots to TWRP. That's it.
I also tried to return it to stock using these: https://forum.xda-developers.com/g4/general/guide-lg-g4-stock-firmware-to-stock-kdz-t3107848 but it had errors connecting to servers and never installed anything.
I'm aware that I won't be able to recover anything on the device and that's fine! I just want to boot it with ANY ROM, and I'd be grateful for any help! Thanks!
mrmrchoice said:
I recently dug out my old G4 to see if I can repurpose it for anything or just have it as a back up.
It's an H815 European variant with unlocked bootloader. When I last used it I had it running a custom ROM but when I got a new phone I wiped it somehow with TWRP (this is a few years ago so I can't remember).
Now whenever I turn it on, it boots into TWRP. If from TWRP I choose reboot to system, it boots to TWRP.
I tried to install a ROM but it wouldn't, giving the error "this ROM is for P1,G4,H815 (or something like that), your device is .".
So, I edited the ROM metadata and took out the device requirements and it installed fine, as did GAPPs & SuperSU, but still it only boots to TWRP. I've flashed bootloaders, kernels, god knows what else, but it only boots to TWRP. That's it.
I also tried to return it to stock using these: https://forum.xda-developers.com/g4/general/guide-lg-g4-stock-firmware-to-stock-kdz-t3107848 but it had errors connecting to servers and never installed anything.
I'm aware that I won't be able to recover anything on the device and that's fine! I just want to boot it with ANY ROM, and I'd be grateful for any help! Thanks!
Click to expand...
Click to collapse
Go to thw official TWRP thread and flash the latest preview TWRP version.
Sent from my OnePlus 6T using XDA Labs
Try latest rom and one by one different rom. It's rom related issue. Don't worry, it'll be okay.