I have S-off Hboot 1.4
Was running Cleanrom 1.1 reborn. & Twrp
Flashed over to CM9 Nightly, worked fine.
Decided I wanted to go back to a sense ics rom, so I flashed the latest ICS meanrom.
Phone went into bootloop
Went back into recovery, flashed superwipe, then did factory reset/wipe cache
Flashed ICS Meanrom again, still boot loop.
Restored TWRP backup I have of stock rom, booted fine.
Tried flashing Cleanrom 1.1 reborn, went into boot loop.
Restored my stock rom, booted fine again.
Changed recovery to Ext4... didn't make a backup in ext 4.
Tried flashing both Cleanrom GB, Meanrom, sends me to boot loop on both.
What happened? I was able to use cleanrom before where as now it just sends it to boot loop, I can't restore my twrp backup as I am on ext4 now.
What do I do?
http://forum.xda-developers.com/showthread.php?p=26381636#post26381636
j4keg said:
I have S-off Hboot 1.4
Was running Cleanrom 1.1 reborn. & Twrp
Flashed over to CM9 Nightly, worked fine.
Decided I wanted to go back to a sense ics rom, so I flashed the latest ICS meanrom.
Phone went into bootloop
Went back into recovery, flashed superwipe, then did factory reset/wipe cache
Flashed ICS Meanrom again, still boot loop.
Restored TWRP backup I have of stock rom, booted fine.
Tried flashing Cleanrom 1.1 reborn, went into boot loop.
Restored my stock rom, booted fine again.
Changed recovery to Ext4... didn't make a backup in ext 4.
Tried flashing both Cleanrom GB, Meanrom, sends me to boot loop on both.
What happened? I was able to use cleanrom before where as now it just sends it to boot loop, I can't restore my twrp backup as I am on ext4 now.
What do I do?
Click to expand...
Click to collapse
maybe Cleanrom 1.1 isnt good......
j4keg said:
What happened? I was able to use cleanrom before where as now it just sends it to boot loop, I can't restore my twrp backup as I am on ext4 now.
What do I do?
Click to expand...
Click to collapse
Not that this solves your problem, but you could switch back to twrp to use your nandroid backup.
Sent from my PG86100
coal686 said:
Not that this solves your problem, but you could switch back to twrp to use your nandroid backup.
Sent from my PG86100
Click to expand...
Click to collapse
Sorry took so long to follow up.
Later on that day, I realized that my phone wasn't accepting the flash of zipped files. It go through the flashing process in like 5 seconds.
I did switch over to ext4, this was causing the same problem.
Couldn't boot into any rom, so I had to use fastboot and adb to send twrp to the phone. Finally restored my stock rom and was able to flash fine since.
j4keg said:
Sorry took so long to follow up.
Later on that day, I realized that my phone wasn't accepting the flash of zipped files. It go through the flashing process in like 5 seconds.
I did switch over to ext4, this was causing the same problem.
Couldn't boot into any rom, so I had to use fastboot and adb to send twrp to the phone. Finally restored my stock rom and was able to flash fine since.
Click to expand...
Click to collapse
Glad to hear it. Thanks for the followup.
Related
I flashed a ROM (InfectedROM) all was working and the phone was up and running until the phone crashed. The phone then went into an endless reboot so I booted into recovery (TWRP) and I restored the nandroid backup I made before I started, but now it goes to the HTC splash with the white background and won't do anything else.
[Edit]
Well I managed to kinda fix the problem. I booted into recovery and selected wipe all data (Factory reset), then I re-flashed InfectedROM and managed to get the phone to boot. Still can't understand why my nandroid backup don't work to make the phone boot.
I would like to revert back to the stock ROM but being able to use my phone is better than not...
My Device:
hboot: 1.5
Unlocked via HTC's method
trm96 said:
I flashed a ROM (InfectedROM) all was working and the phone was up and running until the phone crashed. The phone then went into an endless reboot so I booted into recovery (TWRP) and I restored the nandroid backup I made before I started, but now it goes to the HTC splash with the white background and won't do anything else.
[Edit]
Well I managed to kinda fix the problem. I booted into recovery and selected wipe all data (Factory reset), then I re-flashed InfectedROM and managed to get the phone to boot. Still can't understand why my nandroid backup don't work to make the phone boot.
I would like to revert back to the stock ROM but being able to use my phone is better than not...
My Device:
hboot: 1.5
Unlocked via HTC's method
Click to expand...
Click to collapse
Well when you did this did you fastboot boot recovery.img and wipe and then try the nan? Maybe what you need to do.. Also if you make future ones I would fastboot boot recovery.img and then make a nandroid backup..
reaper24 said:
Well when you did this did you fastboot boot recovery.img and wipe and then try the nan? Maybe what you need to do.. Also if you make future ones I would fastboot boot recovery.img and then make a nandroid backup..
Click to expand...
Click to collapse
Does it make a difference if I fastboot boot recovery.img to wipe before I restore my nan backup? To answer you question, no I did not. Here's what I did form the get go:
1) unlocked my bootloader via HTC's unlock method leaving my phone's bootloader unlocked with s-on
2) I after a while decided to try out anther ROM I went with InfectedROM, So I booted into recovery (TWRP) holding the vol down key while pressing the power key and made a nan backup
3) I rebooted my phone using reboot system from TWRP
4) I then rebooted my phone (adb reboot bootloader)
5) I went into fast boot and booted into recovery (fastboot boot recovery.img)
6) I wiped all data then went into install from zip selected the InfectedROM zip on my sdcard
7) Rebooted via recovery's reboot command
Please bear with me while I am a wiz at using the command line in both Linux and Windows I am a noob when it comes to flashing roms and such.
trm96 said:
Does it make a difference if I fastboot boot recovery.img to wipe before I restore my nan backup? To answer you question, no I did not. Here's what I did form the get go:
1) unlocked my bootloader via HTC's unlock method leaving my phone's bootloader unlocked with s-on
2) I after a while decided to try out anther ROM I went with InfectedROM, So I booted into recovery (TWRP) holding the vol down key while pressing the power key and made a nan backup
3) I rebooted my phone using reboot system from TWRP
4) I then rebooted my phone (adb reboot bootloader)
5) I went into fast boot and booted into recovery (fastboot boot recovery.img)
6) I wiped all data then went into install from zip selected the InfectedROM zip on my sdcard
7) Rebooted via recovery's reboot command
Please bear with me while I am a wiz at using the command line in both Linux and Windows I am a noob when it comes to flashing roms and such.
Click to expand...
Click to collapse
So you are on the latest software? If you want something close to stock just to keep things smooth you could try fresh rom or my rom I did both of these are stock based... If you want just the stock look with stock everything go for the stock rooted copies they have in the dev section..
I never made a nandroid copy of my orignal rom since a ruu will always save you when you have to unroot
Does the nandroid back up cause reboots or a hang... Sometimes it takes a good 3 mins for it to move on depends...
When you made the nan backup were you on the 2.08 software or the 2.17 ? Did you update to the 2.17 after you made a backup in the past?
reaper24 said:
So you are on the latest software? If you want something close to stock just to keep things smooth you could try fresh rom or my rom I did both of these are stock based... If you want just the stock look with stock everything go for the stock rooted copies they have in the dev section..
I never made a nandroid copy of my orignal rom since a ruu will always save you when you have to unroot
Does the nandroid back up cause reboots or a hang... Sometimes it takes a good 3 mins for it to move on depends...
When you made the nan backup were you on the 2.08 software or the 2.17 ? Did you update to the 2.17 after you made a backup in the past?
Click to expand...
Click to collapse
I am indeed running the latest software. Thank you I will check out your ROM!
My nandroid back backs up and restores fine but after I reboot after doing a restore the phone does not boot, it just stays on the HTC logo with the white screen.
I did not do any updates after I did my nan backup.
trm96 said:
I am indeed running the latest software. Thank you I will check out your ROM!
My nandroid back backs up and restores fine but after I reboot after doing a restore the phone does not boot, it just stays on the HTC logo with the white screen.
I did not do any updates after I did my nan backup.
Click to expand...
Click to collapse
the boot.img file you have in your restore set up is invalid... i would try to resave your settings agin and then restore from there...boot.img should write to the boot partition if not through recovery then through manual flashing in fastboot
MeanROM is also pretty nice. It is like FreshRom and CleanRom in the way that it is based around Stock, except that it has some pretty beefy features.
Hi,
I have a big problem. I was trying to install the newest Renovate ROM, and I think I did everything correctly. I pasted the ROM into my phone's storage, booted into recovery, and installed it choosing the "update only" option (I had Renovate 2.1 before).
Everything seemed fine, except rebooting the phone takes me to recovery, and every reboot option I could find always reboot me to recovery. I can also get to the bootloader, but eventually I ended up back at recovery...
What should I do? I have a Nandroid backup of the phone before I flashed Renovate 5.0, should I full wipe the phone and restore that backup?
Any help would be appreciated.
You should read before you mess with your phone.
Sent from my HTC One using Tapatalk 4
xexxonx said:
Hi,
I have a big problem. I was trying to install the newest Renovate ROM, and I think I did everything correctly. I pasted the ROM into my phone's storage, booted into recovery, and installed it choosing the "update only" option (I had Renovate 2.1 before).
Everything seemed fine, except rebooting the phone takes me to recovery, and every reboot option I could find always reboot me to recovery. I can also get to the bootloader, but eventually I ended up back at recovery...
What should I do? I have a Nandroid backup of the phone before I flashed Renovate 5.0, should I full wipe the phone and restore that backup?
Any help would be appreciated.
Click to expand...
Click to collapse
Restore your nandroid as long as all was working well before your issue.
well I was flashing MIUI V5 UNIVERSAL - v. 3.7.12 for the 3vo and it got stuck in a bootloop. to try and fix it I tried to restore a backup and that rom played a little of the boot animation but then gets stuck in a bootloop. I also tried to wipe/format everything but, that didn't work. If a logcat would help i would appreciate a link on how to do that without being able to boot. I can boot to 4ext recovery. The cause could be that while flashing I selected the file to flash, I selected a file that didn't finish downloading. Thanks in advance for any help
Also if it matters my original rom was negalite blurom.
cdog1213 said:
well I was flashing MIUI V5 UNIVERSAL - v. 3.7.12 for the 3vo and it got stuck in a bootloop. to try and fix it I tried to restore a backup and that rom played a little of the boot animation but then gets stuck in a bootloop. I also tried to wipe/format everything but, that didn't work. If a logcat would help i would appreciate a link on how to do that without being able to boot. I can boot to 4ext recovery. The cause could be that while flashing I selected the file to flash, I selected a file that didn't finish downloading. Thanks in advance for any help
Also if it matters my original rom was negalite blurom.
Click to expand...
Click to collapse
I ran into your same problem today.
At the time my phone was on latest sprint firmware, ICS coolrom (latest rom and kernel) with hboot 1.58 unlocked s-off.
The steps I did preparing to install MIUI was
1) wipe data/factory reset from 4EXT
2) format all (except sdcard)
3) Install MIUI > chose mirage kernal
4) rebooted
after reboot it was stuck at the logo, at least I thought it was, let it sit for about 5 minutes.
Pulled the battery and tried steps 1-4 again.
Kept getting bootloop at that point. Boot splash -> logo -> reboot.
Next I tried flashing the latest mirage kernel from 4ext.
No luck, same issue.
Tried repeating steps 1-4 again.
No luck stuck in bootloop.
At that point I tried to run recovery from a backup I knew was working.
Wiped all data and format all -> selected recovery from 4ext.
Result: still boot loop.
At that point I tried changing bootloader to 1.58.58 jbear. and wiping/formatting all and trying recovery again from known working cool ics backup.
Result: still bootloop.
Switched back to 1.58 bootloader and tried fresh install of CoolICS rom. (I always wipe all data and format all before any rom change.)
Result: still bootloop.
At this point I was getting frustrated but I had an idea that the MIUI install when selecting mirage kernel may have messed up the partition size for the kernel since the mirage kernel states it must be flashed from the flash gui app first to resize the boot partition.
Next I downloaded pacman rom and attempted that install.
result: could not install due to wrong bootloader.
Next I downgraded bootloader to 1.50.50 jbear.
Wiped everything and retried pacman rom.
Install success, before starting the reboot from recovery, I received a message that the boot image has changed and will make a backup/format/flash the new boot image.
upon reboot I was able to successfully boot into pacman rom.
At that point I tried to wipe all again and install CoolICS rom again.
result: bootloop, but probably because of bootloader version. Did not fully test it as at this point I just wanted a working phone again and wanted to try out MIUI.
Rebooted to recovery and wiped everything again.
Installed MIUI using stock kernel option. This time on reboot I let it sit at the rom logo without touching anything. I think it restarted once on its own.
Result: Success. Phone working normally now. such a headache I am just leaving it as is for now.
Jeffjb said:
I ran into your same problem today.
At the time my phone was on latest sprint firmware, ICS coolrom (latest rom and kernel) with hboot 1.58 unlocked s-off.
The steps I did preparing to install MIUI was
1) wipe data/factory reset from 4EXT
2) format all (except sdcard)
3) Install MIUI > chose mirage kernal
4) rebooted
after reboot it was stuck at the logo, at least I thought it was, let it sit for about 5 minutes.
Pulled the battery and tried steps 1-4 again.
Kept getting bootloop at that point. Boot splash -> logo -> reboot.
Next I tried flashing the latest mirage kernel from 4ext.
No luck, same issue.
Tried repeating steps 1-4 again.
No luck stuck in bootloop.
At that point I tried to run recovery from a backup I knew was working.
Wiped all data and format all -> selected recovery from 4ext.
Result: still boot loop.
At that point I tried changing bootloader to 1.58.58 jbear. and wiping/formatting all and trying recovery again from known working cool ics backup.
Result: still bootloop.
Switched back to 1.58 bootloader and tried fresh install of CoolICS rom. (I always wipe all data and format all before any rom change.)
Result: still bootloop.
At this point I was getting frustrated but I had an idea that the MIUI install when selecting mirage kernel may have messed up the partition size for the kernel since the mirage kernel states it must be flashed from the flash gui app first to resize the boot partition.
Next I downloaded pacman rom and attempted that install.
result: could not install due to wrong bootloader.
Next I downgraded bootloader to 1.50.50 jbear.
Wiped everything and retried pacman rom.
Install success, before starting the reboot from recovery, I received a message that the boot image has changed and will make a backup/format/flash the new boot image.
upon reboot I was able to successfully boot into pacman rom.
At that point I tried to wipe all again and install CoolICS rom again.
result: bootloop, but probably because of bootloader version. Did not fully test it as at this point I just wanted a working phone again and wanted to try out MIUI.
Rebooted to recovery and wiped everything again.
Installed MIUI using stock kernel option. This time on reboot I let it sit at the rom logo without touching anything. I think it restarted once on its own.
Result: Success. Phone working normally now. such a headache I am just leaving it as is for now.
Click to expand...
Click to collapse
well I went to go try and boot P.A.C. and my phone just booted normally. So thanks for the help
What fixed it for me:
I had made a backup through TWRP 2.6.3.0, but then upgraded to 2.3.6.1 after. Not sure why it didn't work on 3.1, I flashed back to 2.6.3.0, flashed my backup, and everything works again.
So, I've been having one hell of a battle trying to get MJ9 and ROMs based off it to work in the last couple days. In the end, I have decided to go back to my Liquid ROM that I have a backup of yesterday morning in TWRP. This backup, until now, has served me well and has gotten my phone back to how it was.
Until now.
I wiped everything through TWRP and tried to recover my ROM image... Now when I boot, it's stuck at Samsung Galaxy Note 2 screen, and stays there indefinitely. I can boot to recovery if I pull the battery. How does this happen? I was recovering back to this backup just fine until now.
I've deleted system/cache/internal storage, flashed, then deleted cache, no luck.
I flashed Beans stock deodexed 4.3 image. That booted ok, but when I go back to recovery, my Liquid backup still will just hang at the Note 2 screen.
What can I do from here to get it working? Do I need to ODIN a pit file? I'm at a loss.
Hey guys, I kinda at my wits ends.
I have a Note 2 and I was running Sophisticated rom 3.1 just fine. I wanted to try Beans new Alliance 23 Rom. So I booted into TWRP 2.6.3.1 and backed up Sophisticated 3.1 first, then wiped everything and flashed Beans 23. Phone would not get past the boot animation. I tried to use the restore I had just created and TWRP fails. Tried upgrading TWRP to 2.6.3.2, didn't work, now any rom I try to install or recover from I get errors in TWRP saying too many files open and a second one about data/data/com.contacts. I tried Philz CWM recovery, I even tried downgrading back to TWRP 2.6.3.0 and nothing. I can not get a rom to boot past the boot animation. Please help. I have unlimited data and I can't go use an upgrade.
Dugall12 said:
Hey guys, I kinda at my wits ends.
I have a Note 2 and I was running Sophisticated rom 3.1 just fine. I wanted to try Beans new Alliance 23 Rom. So I booted into TWRP 2.6.3.1 and backed up Sophisticated 3.1 first, then wiped everything and flashed Beans 23. Phone would not get past the boot animation. I tried to use the restore I had just created and TWRP fails. Tried upgrading TWRP to 2.6.3.2, didn't work, now any rom I try to install or recover from I get errors in TWRP saying too many files open and a second one about data/data/com.contacts. I tried Philz CWM recovery, I even tried downgrading back to TWRP 2.6.3.0 and nothing. I can not get a rom to boot past the boot animation. Please help. I have unlimited data and I can't go use an upgrade.
Click to expand...
Click to collapse
I am using twrp 2.6.3.1. I would reflash the recovery. Then I would wipe everything except your external SD card. I have noticed that if I don't wipe my internal SD for awhile I will start having goofy stuff happen. That usually fixes any issues I have.
Sent from my SCH-I605 using Tapatalk
Yeah, I tried all that as well. Rehashed that version the new version and the older version then tried Phil's, tried wiping internal, external and still had errors. I had to bite the bullet and Odin back to stock 4.1.2 then jailbreak again and after a day lost I finally got it back up. I'm leaving TWRP 2.5 on it
Sent from my SCH-I605 using xda app-developers app