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
Related
tried to get OTA 5.0.1 today. woudn't take. I have (had)rooted,s-off,bootloader unlocked. Now i somehow wiped everything off.No OS, no recovery. No idea how to begin again. Screen is on white with HTC logo and Powered by android showing. won't power down. Any ideas?
Try holding volume up with power button down for ten seconds.
---------- Post added at 03:47 PM ---------- Previous post was at 03:46 PM ----------
Are you sure you wiped everything, or are you just assuming this based on the screen you are seeing?
update
ok, i held power up/power for 20 seconds, then power down/power and got into twrp recovery. there is NOTHING else on the phone. No OS at all. what's the best way to proceed? PC wont pickup device,so adb cmd prompt isn't working. thanks
stlsports said:
ok, i held power up/power for 20 seconds, then power down/power and got into twrp recovery. there is NOTHING else on the phone. No OS at all. what's the best way to proceed? PC wont pickup device,so adb cmd prompt isn't working. thanks
Click to expand...
Click to collapse
What I would do is pop out my MicsoSD card, back everything up on it then download my original OS I WAS running before I blew it up onto the SD card and attempt to flash it. From there I'd hit up this thread http://forum.xda-developers.com/showthread.php?t=2714456 to see if I could glean how to return back to stock. I'm sure someone will yell at me if you shouldn't do it, not that am I saying you should do that, I'm just saying what I'd do.
i was able to get lollipop dream on my sd card and flash it. WHEW! but, i really want stock rooted lollipop. i actually enjoy sense 6.0 a little bit. gonna keep at it..
thanks.
Theoriginalgiga said:
What I would do is pop out my MicsoSD card, back everything up on it then download my original OS I WAS running before I blew it up onto the SD card and attempt to flash it. From there I'd hit up this thread http://forum.xda-developers.com/showthread.php?t=2714456 to see if I could glean how to return back to stock. I'm sure someone will yell at me if you shouldn't do it, not that am I saying you should do that, I'm just saying what I'd do.
Click to expand...
Click to collapse
stlsports said:
i was able to get lollipop dream on my sd card and flash it. WHEW! but, i really want stock rooted lollipop. i actually enjoy sense 6.0 a little bit. gonna keep at it..
thanks.
Click to expand...
Click to collapse
Well now that you're up and running, you can go through the process of flashing the old stock rom (not the lollipop rom), unroot and restore the stock BL, then take the OTA update and I believe you should be able to reroot if you wanted to.
Theoriginalgiga said:
Well now that you're up and running, you can go through the process of flashing the old stock rom (not the lollipop rom), unroot and restore the stock BL, then take the OTA update and I believe you should be able to reroot if you wanted to.
Click to expand...
Click to collapse
couldn't he just flash the most current RUU?
deepsouth06 said:
couldn't he just flash the most current RUU?
Click to expand...
Click to collapse
Maybe, I'm not sure. I was able to because I was coming from just the stock rom rooted with xposed on it I know that at the least BL needs to be stock and match the version of stock ROM you nandroided back on. If you're using RUU I don't think unrooting is important. Whether or not you have to lock the BL I'm not aware of myself but it's an easy process. Below is what I did.
Being on a rooted stock ROM running xposed I downloaded drivers, BL that matched my ROM, ADB/fastboot current RUU I was on and latest RUU.
I was on 4.4.4, I verified the version of my ROM and got the matching BL. I've heard rumors that mismatching BL/ROM will cause an error.
FIRST I booted into my custom recovery and did a back up. Better safe than sorry right?
booted into fastboot and installed the recovery using fastboot flash recovery {recoveryname}.img
locked BL using "fastboot oem lock" rebooted my phone into the OS then fired up the latest[/B ]RUU and let it run and it ran just fine.
I then unlocked my BL again and installed the latest version of TWRP, reinstalled root and my apps. phone runs really well. I need to start going through and freezing apps but hey we skip those things at 2am don't we?
Mind you I have S-off on my phone and I didn't mess with S-off at all.
I would surmise that if you're experiencing getting the latest RUU to install that you might want to make sure your BL and rom number match and if that doesn't work try flashing the RUU that you're currently running and then the latest RUU.
I consulted this list to verify my version I was running, I happened to be running at the time 3.32.531.2 so I hunted for that BL.
https://support.t-mobile.com/docs/DOC-10366
I unrooted my phone ages ago, havent done anything to it since, but yesterday my phone just decided to cut out, started with apps not loading, then my phone wouldn't turn on, now my phone just gets stuck into bootloop
How do I determine which stock firmware to go back to via Odin?
My phone is UK, and unlocked
When i try to go into recovery, I get the following
RECOVERY BOOTING....
SET Warranty Bit: Recovery
and it's driving me nuts, Ive tried installing a UK firmware that I believe might be the one, and Odin doesn't come back with any errors, but the same damn message applies, as far as I know, once you can get recovery working and clear cache, you should be fine, but I just cant get it to work
I've tried installed custom bootloaders, but same ol same message
Gimba89 said:
I unrooted my phone ages ago, havent done anything to it since, but yesterday my phone just decided to cut out, started with apps not loading, then my phone wouldn't turn on, now my phone just gets stuck into bootloop
How do I determine which stock firmware to go back to via Odin?
My phone is UK, and unlocked
When i try to go into recovery, I get the following
RECOVERY BOOTING....
SET Warranty Bit: Recovery
and it's driving me nuts, Ive tried installing a UK firmware that I believe might be the one, and Odin doesn't come back with any errors, but the same damn message applies, as far as I know, once you can get recovery working and clear cache, you should be fine, but I just cant get it to work
I've tried installed custom bootloaders, but same ol same message
Click to expand...
Click to collapse
Did you tried to make an custom ROM on your SD-Card?
Your right Firmware is on Sammobile by the way
Okay so i went through the bootloader unlock process on my Note 4 without any major hickups, was running on CM13 ever since until i wanted to play with Gear VR which from what i could find required me to be on a stock based/touchwiz rom, first up was Omega which installed fine but would boot loop at welcome screen, so then i went with Evolution and almost same story, just boot loop. Figured it had to be a problem with the firmware version on my phone and without thinking i downloaded the CPF1 firmware and flashed with Odin. Flash went fine with no problems, booted into marshmallow just fine, enabled usb debugging and rebooted to flash TWRP for recovery and i get zilch. Every single TWRP and CWM recovery file i try to flash end in a failure. Can't even get Kingroot to give me root in MM so I think i'm stuck...dont even see the Unlock logo and Custom on the main screen after i hit the power button to turn on.
SO.........
Big question is, did i just re-lock my bootloader when i flashed firmware CPF1?
I think I did this same thing a while ago, were you on an older version of CM13 from May or so? Anyway, what I had to do was flash stock 5.1 in Odin with the up to date kernel, modem, etc and follow the guide to re-unlock your bootloader
Well got it re-flashed and unlocked again, gotta give a shout out to the great guys here on XDA.
Next question is do i need to flash a new bootloader or modem in odin/twrp before moving to a MM rom or is that stuff usually included in the rom? My experience in roms and stuff is from my old Razr Maxx HD and never jumped operating system version with it so i'm not sure on this one.
I own a canvas A1 4GB variant, I had rooted my phone and flashed custom recovery(everything was finee), After a while my phone's battery started giving me problems(lasted only few hours), I considered flashing Stock ROM or any other trusted ROM, I had flashed RR M[07/07] based on android MM, The battery was still giving problem, A week later, My mom's phone broke and she had to use this(A1) temporarily, I formatted everything and thought of flashing stock ROM and handing over the phone to her, I tried flashing the official zip via TWRP, It gave me some error regarding unable to mount system, System partions or something(I don't remember). And after that, I could't flash any ROM, I tweaked some settings in TWRP and now my phone is totally dead, It does not boot up at all, No recovery mode turns on, Nothing except a black dead screen, I tried flashing stock firmware via SP flash tool, It completes and says successful but still nothing happens, Just wanna know if something can happen to this one? I really loved that device and would be great to have it back working.
Flash correct stock firmware in sptools
arunassain said:
Flash correct stock firmware in sptools
Click to expand...
Click to collapse
doesn't work. I have tried various STOCK Roms on mine but didnt work. Please post a link if possible which u think works.
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.