Okay now that I've got your attention I'd like to address my problem. I made a back up of my stock Rom when I first rooted it, I'm trying to restore it but it keeps getting bootloops, I've only flashed two roms and that's cm10 and meanrom ics I wanna go back to complete stock but cant because I can't download ruu and I downloaded the p739373929 or what ever it was off the s on back to stock guide and ran it and dun dun dun nothing happened, it ran rebooted right back into mean Rom like wth lol... Anyone got any idea why my restore isn't working? And why it keeps getting bootloop?
Sent from my EVO using xda app-developers app
I don't know why your getting boot loops, are you saying that you want to go back to stock as in unroot?
Sent from my EVO using xda premium
josh030181 said:
I don't know why your getting boot loops, are you saying that you want to go back to stock as in unroot?
Sent from my EVO using xda premium
Click to expand...
Click to collapse
Technically yes but my restore is stock rooted, which is fine with me I miss my insane battery life I'm Lu ky if I get 4-5 hrs on mean or on cm10
Sent from my EVO using xda app-developers app
If you're son then you need to flash the kernel for what ever base you had through fastboot or use dumlock to restore the entire back up in one attempt. To use dumlock you will need a working rom
om4 said:
If you're son then you need to flash the kernel for what ever base you had through fastboot or use dumlock to restore the entire back up in one attempt. To use dumlock you will need a working rom
Click to expand...
Click to collapse
Ya I figured it out like 10 seconds after my reply lol damn brain farts
Sent from my EVO using xda app-developers app
I generally stay away from dumlock on son devices but for nandroid restore its less hassle then having to download a corresponding kernel or trying to extract it
Related
I have been on miui and wanted to try ics. It was all good and it was running fine but i missed miui. I flashed chads kernel through the flashimage app and wiped all and reflashed miui and its stuck on the logo. I have tried to wipe and reflash 10 times and still the same thing. I dont have a comp now so what do i do????
Hboot 1.5 s-on
Sent from my GT-I9000 using XDA App
Anyone?
Sent from my GT-I9000 using XDA App
Did you flash through flash gui or by putting the phone into recovery via command prompt?
vt_hokie2008 said:
Did you flash through flash gui or by putting the phone into recovery via command prompt?
Click to expand...
Click to collapse
Flash gui
Sent from my GT-I9000 using XDA App
I dont understand why if i flashed a aosp kernel through flashimage app why it didnt work. I wiped all its stuck on the miui boot logo. Wtf!!! i dont have my comp now so what do i do? im so confused cause ive done it a million times and this time it did this.
Sent from my GT-I9000 using XDA App
Why didn't you make a nandroid of miui for when you wanted to go back? As we all know ics isn't near complete yet,
Always nandroid, works out better in long run waiting.g those couple mins.
Shot from my sharp shooter in 3d
cleanrom2.9.5
Ok so i think im screwed until i get my comp back. One question is since i.have twrp installed can i still flash through fastboot? if so then im all good. Its weird i thought maybe the kernel didnt take so i reflashed ics and it boots fine but once the main screen pulls up the screen is unresponsive. I think my only option is fastboot.
Sent from my GT-I9000 using XDA App
I have a MoPho with unlocked bootloader running 2.3.4 and everytime I try to flash back to my saved stock backup from any custom rom I keep getting an "error while flashing boot image" I tried to do an advanced restore and picked the files one at a time but I keep getting the same result. Can someone please help, thank you in advance...
Sent from my MB855 using xda app-developers app
Are you restoring using the same utility you did the nandroid backup with? Joker recovery vs twrp vs cwm recovery
Sent from my MB855 using Tapatalk 2
I created the back up using cwm and trying to restore through cwm...
Sent from my MB855 using xda app-developers app
Stray2thaB said:
I created the back up using cwm and trying to restore through cwm...
Sent from my MB855 using xda app-developers app
Click to expand...
Click to collapse
Are you using a working recovery? Jokers? Twrp? Photon3? Or the ROM manager one? ROM manager version does not work.
Sent from my MB853 using XDA
As far as I know, I am using Clockworkmod Recovery v5.0.2.8. I've tried Rom Manager but I usually get an error while trying to perform a NANDroid backup...
Sent from my MB855 using xda app-developers app
Stray2thaB said:
As far as I know, I am using Clockworkmod Recovery v5.0.2.8. I've tried Rom Manager but I usually get an error while trying to perform a NANDroid backup...
Sent from my MB855 using xda app-developers app
Click to expand...
Click to collapse
as mentioned previously the ROM Manager one DOES NOT WORK. 5.0.2.8 DOES NOT WORK! you NEED to user Jokers, TWRP or the 5.0.2.7-photon3 recoveries ONLY. you can find the working recoveries on my site. choose which one suits you best! don't use Jokers V4 because it won't flash google apps properly.
http://www.motosunfire.com/clockworkmod-recovery/
Ok thanks a lot, I will try the two you just recommended...
Sent from my MB855 using xda app-developers app
OK I downloaded the TWRP recovery you had suggested, I backed up my current from but when I tried to restore a different from I keep getting an error "the process com.android.phone has stopped working" and I have no service now...
Sent from my MB855 using xda app-developers app
Stray2thaB said:
OK I downloaded the TWRP recovery you had suggested, I backed up my current from but when I tried to restore a different from I keep getting an error "the process com.android.phone has stopped working" and I have no service now...
Sent from my MB855 using xda app-developers app
Click to expand...
Click to collapse
alright? well that doesn't say alot? as you could be using any one of 20 different ROMs. which are you using?
na7q said:
alright? well that doesn't say alot? as you could be using any one of 20 different ROMs. which are you using?
Click to expand...
Click to collapse
I am running cm7, or rather was running cm7 coz now my phone is stuck in the boot loop limbo. Kept getting the error "com.android.phone stopped working" and I was unable to make or receive calls all day. So I thought relocking and unlocking the bootloader would do the trick but now I'm stuck on a rock and a hard place. Sssoooooo, do you have any tricks up your sleeves I could use, I would really appreciate it...
I've been able to run a hand full of fastboot commands to bring my phone back out of limbo, I am past the boot image and able to activate with the sprint network. Thank you all who took the liberty of viewing my post, I appreciate the help...
Stray2thaB said:
I am running cm7, or rather was running cm7 coz now my phone is stuck in the boot loop limbo. Kept getting the error "com.android.phone stopped working" and I was unable to make or receive calls all day. So I thought relocking and unlocking the bootloader would do the trick but now I'm stuck on a rock and a hard place. Sssoooooo, do you have any tricks up your sleeves I could use, I would really appreciate it...
Click to expand...
Click to collapse
Stray2thaB said:
I've been able to run a hand full of fastboot commands to bring my phone back out of limbo, I am past the boot image and able to activate with the sprint network. Thank you all who took the liberty of viewing my post, I appreciate the help...
Click to expand...
Click to collapse
hmmm... CDMA user? or GSM? i remember that bug being around in the very early builds of CM7. are you on the latest nightly or stable release?
i might also recommend changing some build prop info (which could be causing this?) to make sure it tells the radio to operate in the correct mode. gsm or cdma. if you look for ro.telophony.default_network=? the ? should be a 4 for CDMA or a 7 for GSM. change to your liking. then reboot. this was an issue in CM9 for the longest time and this is how it was resolved. it's possible it could be the same for CM7.
another option is to of course start over. wipe the cache,data,system partitions, possibly even twice. flash cm7. twice to be safe. then gapps. twice to be safe. then give it another shot.
other than that it might be a bad download or a bad build. so try another if it doesn't work. hope this helps you!
CDMA user, for now I am able to have my phone back on, but I will probably steer away from CM7 AND perhaps try CM10. All I keep finding is an unofficial release, is this the only one there is?
Sent from my MB855 using xda app-developers app
Stray2thaB said:
CDMA user, for now I am able to have my phone back on, but I will probably steer away from CM7 AND perhaps try CM10. All I keep finding is an unofficial release, is this the only one there is?
Sent from my MB855 using xda app-developers app
Click to expand...
Click to collapse
there will never be any officials releases unless somehow Motorola decides they want to give us drivers/source for ICS or JB. which is never. unless we get a leak.
the other day i tried restoring a back up via TWRP but it didnt work until i fastboot flashed boot.img...Alright so i updated my TWRP via goomanager app to the latest version (whatever is on there via goomanager) as in the TWRP forum discussions it was stated that previous versions were not working properly wihen restoring. So today i flashed a new ROM (NOS ROM) but that didnt work so i decided what better time than now to try restoring again, no dice didnt work and i had to fastboot flash the boot img for the restore file to take and boot up just fine again...ok peeps what am doing wrong??? again im fairly new at this flashing ROMS scene but i thought witht he TWRP update i would be good to go. Am i missing some settings ticks/options/checks? i saw a check box that said "recovery" i think in the restore or back up process dont remember which process. i tried going onto the TWRP discussion but it is locked down and states that there will no longer be any support for it...should i just switch to CWM?? thanks in advance to whom ever replies
twrp recovery..
kenohki88 said:
the other day i tried restoring a back up via TWRP but it didnt work until i fastboot flashed boot.img...Alright so i updated my TWRP via goomanager app to the latest version (whatever is on there via goomanager) as in the TWRP forum discussions it was stated that previous versions were not working properly wihen restoring. So today i flashed a new ROM (NOS ROM) but that didnt work so i decided what better time than now to try restoring again, no dice didnt work and i had to fastboot flash the boot img for the restore file to take and boot up just fine again...ok peeps what am doing wrong??? again im fairly new at this flashing ROMS scene but i thought witht he TWRP update i would be good to go. Am i missing some settings ticks/options/checks? i saw a check box that said "recovery" i think in the restore or back up process dont remember which process. i tried going onto the TWRP discussion but it is locked down and states that there will no longer be any support for it...should i just switch to CWM?? thanks in advance to whom ever replies
Click to expand...
Click to collapse
What did you have checked while making the backup? data? recovery? cache? system? and did you rename the back up?
System, data and boot are checked...I didn't mess with the options just hit restore and let it do it's thing...should I change something or check the other 2 boxes (one of them being "recovery" forgot what the other option was)?
Sent from my HTC6435LVW using xda app-developers app
kenohki88 said:
System, data and boot are checked...I didn't mess with the options just hit restore and let it do it's thing...should I change something or check the other 2 boxes (one of them being "recovery" forgot what the other option was)?
Sent from my HTC6435LVW using xda app-developers app
Click to expand...
Click to collapse
I would check recovery as well and try again.....also make sure to wipe everything before flashing anything
---------- Post added at 12:42 PM ---------- Previous post was at 12:34 PM ----------
canemaxx said:
I would check recovery as well and try again.....also make sure to wipe everything before flashing anything
Click to expand...
Click to collapse
also some roms are picky about which recovery is used to install/backup. I can say I have had no issues backing up stock or custom roms with twrp on my DNA
Alright sounds good maybe later on tonight when I'm at my computer just in case thank you for the tips I as well haven't had much trouble flashing ROMS with TWRP, albeit I've only tried flashing 2 or 3 been very happy with ViperDNA just wanted to check out different ones and easily restore back to viper
Sent from my HTC6435LVW using xda app-developers app
kenohki88 said:
Alright sounds good maybe later on tonight when I'm at my computer just in case thank you for the tips I as well haven't had much trouble flashing ROMS with TWRP, albeit I've only tried flashing 2 or 3 been very happy with ViperDNA just wanted to check out different ones and easily restore back to viper
Sent from my HTC6435LVW using xda app-developers app
Click to expand...
Click to collapse
Check out NOS its a great rom
canemaxx said:
Check out NOS its a great rom
Click to expand...
Click to collapse
That's exactly what I was trying when all this happened...I flashed it via flash gui app like I've been doing but for some reason it didn't work...when I went to unlock screen it would pull up HTC splash screen and just stay stuck there... I'm not S-off yet so would that have something to do with NOS ROM not functioning?
Sent from my HTC6435LVW using xda app-developers app
kenohki88 said:
That's exactly what I was trying when all this happened...I flashed it via flash gui app like I've been doing but for some reason it didn't work...when I went to unlock screen it would pull up HTC splash screen and just stay stuck there... I'm not S-off yet so would that have something to do with NOS ROM not functioning?
Sent from my HTC6435LVW using xda app-developers app
Click to expand...
Click to collapse
no thats how that rom boots....leave it alone for about 5-10 minutes youlll see the notificatiion light come on and your =e good to go
Let me rephrase that...it boots up, screen comes on silver background from butterfly then I go pull ring to unlock and it pulls up the HTC splash screen once I unlock and will not move from there...so that's when I reset and went back to viper...???
Sent from my HTC6435LVW using xda app-developers app
kenohki88 said:
Let me rephrase that...it boots up, screen comes on silver background from butterfly then I go pull ring to unlock and it pulls up the HTC splash screen once I unlock and will not move from there...so that's when I reset and went back to viper...???
Sent from my HTC6435LVW using xda app-developers app
Click to expand...
Click to collapse
Flash the new Nos build, and flash cpalmers kernel after the Rom install and then reboot.
Sent from my ADR6425LVW using Xparent Red Tapatalk 2
Haven't tried it since I posted this, but ok I'll give it another spin/attempt this weekend thanks for the tip
Sent from my HTC6435LVW using xda app-developers app
kenohki88 said:
Haven't tried it since I posted this, but ok I'll give it another spin/attempt this weekend thanks for the tip
Sent from my HTC6435LVW using xda app-developers app
Click to expand...
Click to collapse
I may have misread but did you wipe everything before loading nos? I saw what was checked for backup but not about wiping. You should wipe everything-system, then cache, then delvik cache-not exactly in that order (make SURE there IS a backup just in case). Load the rom AND flash the correct image file with adb. Also, many roms when FIRST loading up sit a long time before they start up, not sure if nos does this or not-I have been jumpy about the time sitting with a few roms when waiting was all I needed to do. I have had different Viper versions on a few times and moving to another rom was quirky each time I did so, not sure why.
NOS did that to me too. Just wait....it will load into the setup wizard. I think being s-on, which I still am...twrp isn't able to back up and restore your roms boot.img. just a guess but I to failed to restore a backup when an install went awry. Makes sense to be being that you can't install a kernel from recovery either.
Sent from my HTC6435LVW using xda app-developers app
Ajj915 said:
NOS did that to me too. Just wait....it will load into the setup wizard. I think being s-on, which I still am...twrp isn't able to back up and restore your roms boot.img. just a guess but I to failed to restore a backup when an install went awry. Makes sense to be being that you can't install a kernel from recovery either.
Sent from my HTC6435LVW using xda app-developers app
Click to expand...
Click to collapse
I looked at the install instructions for nos, if you are s-on you need to do one extra step. You have to extract the rom into a folder somewhere to get the image file, copy the image file from it. Flash that image file using adb on your pc and THEN install the rom from your phone with goomanager. Without the image file loaded, I don't think it would work. If you are s-off this step is not needed.
rootntootn said:
I looked at the install instructions for nos, if you are s-on you need to do one extra step. You have to extract the rom into a folder somewhere to get the image file, copy the image file from it. Flash that image file using adb on your pc and THEN install the rom from your phone with goomanager. Without the image file loaded, I don't think it would work. If you are s-off this step is not needed.
Click to expand...
Click to collapse
I get that. I'm purely talking about after a full while that I'm not sure if twrp will restore the boot.img from a nandroid. S-On of course.
Sent from my HTC6435LVW using xda app-developers app
Ajj915 said:
I get that. I'm purely talking about after a full while that I'm not sure if twrp will restore the boot.img from a nandroid. S-On of course.
Sent from my HTC6435LVW using xda app-developers app
Click to expand...
Click to collapse
I believe it will, if it had the image from the get go. I believe that the back up has everything it needs. At least my back ups have never needed an image file. I decided I should try NOS myself and must say it would not go for me (S-off) it kept rebooting into recovery. I was going to try and also flash the boot image but have not done so yet.
---------- Post added at 10:10 AM ---------- Previous post was at 10:08 AM ----------
rootntootn said:
I believe it will, if it had the image from the get go. I believe that the back up has everything it needs. At least my back ups have never needed an image file. I decided I should try NOS myself and must say it would not go for me (S-off) it kept rebooting into recovery. I was going to try and also flash the boot image but have not done so yet.
Click to expand...
Click to collapse
Oh yeah, and I restored my back up and that works just fine
rootntootn said:
I believe it will, if it had the image from the get go. I believe that the back up has everything it needs. At least my back ups have never needed an image file. I decided I should try NOS myself and must say it would not go for me (S-off) it kept rebooting into recovery. I was going to try and also flash the boot image but have not done so yet.
---------- Post added at 10:10 AM ---------- Previous post was at 10:08 AM ----------
Oh yeah, and I restored my back up and that works just fine
Click to expand...
Click to collapse
Its the kernel in NOS. Flash NOS and then flash cpalmers kernel. Then reboot and do the setup and if you want to change to the zarboz kernel you need to delete system/bin/thermald or rename it to thermald_old.bak
Sent from my HTC6435LVW using Xparent Red Tapatalk 2
Hmmm well I did everything via my cell (been the way I've been flashing ROMS unless something goes wrong then I use ADB on computer) and everything when properly done works fine using Flash GUI APP love that app! I've flashed super charged hatka 320 (used that for a couple weeks) then switched over to viper...both using Flash GUI I tried using NOS but yes no dice loaded up but when I pull the unlock ring for whatever reason the splash screen comes up and it won't budge from there....and as for my original question haha TWRP did not work for me when restoring it tripped out like if it was missing the boot image (done that before so I'm familiar with that behavior haha)
Oh and I'm still S-on
Sent from my HTC6435LVW using xda app-developers app
CharliesTheMan said:
Flash the new Nos build, and flash cpalmers kernel after the Rom install and then reboot.
Sent from my ADR6425LVW using Xparent Red Tapatalk 2
Click to expand...
Click to collapse
That's what mine does too......just wait til the notification light turns orange and you will be all set......be patient.
canemaxx said:
That's what mine does too......just wait til the notification light turns orange and you will be all set......be patient.
Click to expand...
Click to collapse
Really? After it boots up? That's odd but ok I'll give it a shot again but probably tomorrow will post here again if it doesn't work....thanks everyone for responding. I'm out at the moment and need cell to be functioning hahaha just in case
Sent from my HTC6435LVW using xda app-developers app
i was on viper rom well i was gonna go back to the stock rom cuz my data speeds wasnt as fast well when i restored my backup im stuck on the bootloop no matter what i do i even made a full wipe i hope this aint already posted i tried looking but id didnt see anything like this ive never seen something like this before i feel like a major noob
Describe your full wipe. Did you format all partitions except sd card.
Sent from my HTC Ruby using xda app-developers app
avenged_sevenfold27 said:
i was on viper rom well i was gonna go back to the stock rom cuz my data speeds wasnt as fast well when i restored my backup im stuck on the bootloop no matter what i do i even made a full wipe i hope this aint already posted i tried looking but id didnt see anything like this ive never seen something like this before i feel like a major noob
Click to expand...
Click to collapse
i told you to take a nandroid backup before doing anything!!
ravike14 said:
i told you to take a nandroid backup before doing anything!!
Click to expand...
Click to collapse
Uum.. he already said he was restoring his backup, so wouldn't this mean he did do a android?
Sent from my HTC_Amaze_4G using xda app-developers app
avenged_sevenfold27 said:
i was on viper rom well i was gonna go back to the stock rom cuz my data speeds wasnt as fast well when i restored my backup im stuck on the bootloop no matter what i do i even made a full wipe i hope this aint already posted i tried looking but id didnt see anything like this ive never seen something like this before i feel like a major noob
Click to expand...
Click to collapse
you said something bout you had to flash faux kernel..you tried that aswell??
masondoctorjt said:
Uum.. he already said he was restoring his backup, so wouldn't this mean he did do a android?
Sent from my HTC_Amaze_4G using xda app-developers app
Click to expand...
Click to collapse
my bad for not noticing it
Im having the same problem
I rooted and flashed CM 10 for Amaze 4g and after the inslallation it booted into CM10 but after a minute or so the phone reboots. This hsppens every time. What should I do?
bad.ar said:
I rooted and flashed CM 10 for Amaze 4g and after the inslallation it booted into CM10 but after a minute or so the phone reboots. This hsppens every time. What should I do?
Click to expand...
Click to collapse
You was on GB or ICS earlier??
Sent from my HTC Amaze 4G
Juopunutbear S-OFF
Super CID
bootloader unlocked
Powered by Faux Kernel V024
HBOOT : 1.93.2222
hit the thanks button if i've helped you :good:
avenged_sevenfold27 said:
i was on viper rom well i was gonna go back to the stock rom cuz my data speeds wasnt as fast well when i restored my backup im stuck on the bootloop no matter what i do i even made a full wipe i hope this aint already posted i tried looking but id didnt see anything like this ive never seen something like this before i feel like a major noob
Click to expand...
Click to collapse
This happen to me after flashing faux kernel v29. What I had to do was fastboot flash stock kernel using hasoon2000 tool then flash v29 via 4ext. Your backup boot.image might be corrupted.
Sent from my HTC_Amaze_4G...Go Canes []_[]
So I screwed up royally and to an experienced rom flasher its probably no big deal and an easy fix. I was in my in recovery( TWRP 2.6.3) and installed the HTC Dumlock trying to flash a rom without a computer. My Rezound is 4.0.3, and now I get as far as the Verizon 4G LTE black screen and that's as far as it will boot... I've tried to wipe and restore like I have in the past when I've screwed up and now I'm out of ideas. I think that the boot image is "corrupted" don't know if thats the right lingo but when I reboot to bootloader the image name that always came up is now different. Can someone please help me with my dilemma? Oh and if detailed description is needed about everything that I did- I kinda freaked out and panicked and I tried so many things to fix it that I don't remember all that I did.
Sent from my DROID RAZR HD using XDA Premium 4 mobile app
undeadking said:
So I screwed up royally and to an experienced rom flasher its probably no big deal and an easy fix. I was in my in recovery( TWRP 2.6.3) and installed the HTC Dumlock trying to flash a rom without a computer. My Rezound is 4.0.3, and now I get as far as the Verizon 4G LTE black screen and that's as far as it will boot... I've tried to wipe and restore like I have in the past when I've screwed up and now I'm out of ideas. I think that the boot image is "corrupted" don't know if thats the right lingo but when I reboot to bootloader the image name that always came up is now different. Can someone please help me with my dilemma? Oh and if detailed description is needed about everything that I did- I kinda freaked out and panicked and I tried so many things to fix it that I don't remember all that I did.
Sent from my DROID RAZR HD using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Extract the boot.img from the ROM zip file, flash ROM, reboot into bootloader and start Fastboot, then flash boot.img via fastboot on a PC, should clear it up...
In the future I would recommend going S-OFF via rumrunner, no more need to worry about flashing boot partitions separately ever again.
Ace, you are a genius! Got the rezzie back up and running! Flashed Tachyon 1.2, flashed the boot image via twrp and it started right up! Now if I go and delete the PH98IMG.ZIP will it still die again if I reboot in the future???
Sent from my DROID RAZR HD using XDA Premium 4 mobile app
undeadking said:
Ace, you are a genius! Got the rezzie back up and running! Flashed Tachyon 1.2, flashed the boot image via twrp and it started right up! Now if I go and delete the PH98IMG.ZIP will it still die again if I reboot in the future???
Sent from my DROID RAZR HD using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Nope, your good.
Sent from my Nexus 4 using Tapatalk
Just made a backup in TWRP and rebooted and all is well, you're awesome man. Thanks again
Sent from my Rezound on Tachyon using XDA Premium 4 mobile app