Hey Everyone,
I was just testing CM7 but I kept getting black screens after I locked the screen, so I went back to CWM and restored. The restore went fine but when I pressed 'Reboot phone now' it went into a bootloop. I then pulled the battery and tried wiping everything and restoring again. No success, still bootlooping.
So...any ideas?
<Edit> I flashed CWM with NVFlash (i have no idea why i did that) so now im on an older version of CWM and it cannot find my backups.
Martin9630 said:
Hey Everyone,
I was just testing CM7 but I kept getting black screens after I locked the screen, so I went back to CWM and restored. The restore went fine but when I pressed 'Reboot phone now' it went into a bootloop. I then pulled the battery and tried wiping everything and restoring again. No success, still bootlooping.
So...any ideas?
<Edit> I flashed CWM with NVFlash (i have no idea why i did that) so now im on an older version of CWM and it cannot find my backups.
Click to expand...
Click to collapse
maybe u stored ur restore in the External SD...and it is not able to find it...maybe u can try to install ROM manager and flash the latest CWM via the ROM manager...did u try tht?
I cannot boot into my phone. The only thing I can access is my the old CWM that i got through NVFlash. Restoring worked but still bootlooped when I had the newer CWM.
Martin9630 said:
I cannot boot into my phone. The only thing I can access is my the old CWM that i got through NVFlash. Restoring worked but still bootlooped when I had the newer CWM.
Click to expand...
Click to collapse
As far as I remember....i think if u have stored your backup in the internal SD...then nvflash will do a wipe/....so u dont find it....do u have a backup in the computer which can be loaded to the EXTSD card and then try the restore....
Just a silly question:if u have restored....which backup u restored to???
Hey there. Thanks for your care and input. I've managed to fix my phone.
It happened to be that the CM7 I installed converted my phone to EXT4, I downloaded the EXT3 converter and now it's working.
Don't worry, your input is not wasted! I will still hit that thanks button.
Martin9630 said:
Hey there. Thanks for your care and input. I've managed to fix my phone.
It happened to be that the CM7 I installed converted my phone to EXT4, I downloaded the EXT3 converter and now it's working.
Don't worry, your input is not wasted! I will still hit that thanks button.
Click to expand...
Click to collapse
I appreciate this gesture mate....
Related
I rooted someone's phone earlier and first tried to flash AmonRA 1.5.2. It wouldn't load into recovery, so I flashed 1.2.3. That one worked, but wanted a newer one, so I went with God Speed. I made a backup and then flashed a 2.1 ROM. I was then showing him how to do a nandroid backup and restore and it wouldn't restore. I made another backup of the new ROM and tried to restore it. Still wouldn't restore. I then flashed AmonRA 1.6.2 and tried the same thing. Still would not restore. Everything works fine on my phone and they are both w/Google phones. I also copied his sdcard to my computer and reformatted his sdcard. Still would not work. Any ideas or suggestions.
'Wouldn't restore' is kind of vague. Did it appear to restore but not? Did the restore fail, and if so, what message came up?
try to rename the nandroid and make sure you phone is plugged into the wall or pc when restoring.
fixxxer2008 said:
try to rename the nandroid and make sure you phone is plugged into the wall or pc when restoring.
Click to expand...
Click to collapse
He'll only need to rename it if he already renamed it and put spaces in it. Plugging it into the wall won't make a difference unless the screen is shutting down due to power issues during the restore.
Two reasons why I asked for further clarification on what happens during a restore attempt.
smw6180 said:
He'll only need to rename it if he already renamed it and put spaces in it. Plugging it into the wall won't make a difference unless the screen is shutting down due to power issues during the restore.
Two reasons why I asked for further clarification on what happens during a restore attempt.
Click to expand...
Click to collapse
i dunno but that always worked for me. i had a message that said restore via adb.
fixxxer2008 said:
i dunno but that always worked for me. i had a message that said restore via adb.
Click to expand...
Click to collapse
restore via adb always happens when a nandroid has been renamed and has a space in it. I'm not saying that's the ONLY reason, but it's the only time I've ever seen or heard of it.
let me look at the copies on my computer.
The error I get is to do it via adb. But I didn't rename it or anything. All I did was
1. Flash the recovery
2. Reboot into recovery
3. Perform Nandroid Backup (just the basic nand backup)
4. Installed DC2.07 as that was what I had on my computer
5. Rebooted and let it load
6. Rebooted into recovery
7. tried to restore and I get the error about performing it via adb
Tried the same routine everytime I flashed a new recovery
Edit:Just checked the nandroid backups---There are no spaces
&RoidRage said:
let me look at the copies on my computer.
The error I get is to do it via adb. But I didn't rename it or anything. All I did was
1. Flash the recovery
2. Reboot into recovery
3. Perform Nandroid Backup (just the basic nand backup)
4. Installed DC2.07 as that was what I had on my computer
5. Rebooted and let it load
6. Rebooted into recovery
7. tried to restore and I get the error about performing it via adb
Tried the same routine everytime I flashed a new recovery
Edit:Just checked the nandroid backups---There are no spaces
Click to expand...
Click to collapse
Interesting. Then I'd try what fixxer said and plug it into the wall before trying the restore.
I will try that tomorrow
sandboxlove said:
hi there
i actually had the same problem today but then i learned (through a search...woah!!) that there is an newer ra, and after an update it worked like a beaut. perhaps your recovery is outdated...or maybe the nandroid is corrupted?
good luck!
Click to expand...
Click to collapse
I'm pretty sure 1.6.2 is the newest which is what is on there now. I've read of other peoples problems and solutions and tried what i rememebered, but it happened with every one I tried.
&RoidRage said:
I'm pretty sure 1.6.2 is the newest which is what is on there now. I've read of other peoples problems and solutions and tried what i rememebered, but it happened with every one I tried.
Click to expand...
Click to collapse
You're not on an ext4 filesystem are you? If so, you'll want godspeed (toast's version of the 1.6.2 recovery image). I believe it handles ext4 restores whereas the original 1.6.2 doesn't (if I remember correctly).
smw6180 said:
You're not on an ext4 filesystem are you? If so, you'll want godspeed (toast's version of the 1.6.2 recovery image). I believe it handles ext4 restores whereas the original 1.6.2 doesn't (if I remember correctly).
Click to expand...
Click to collapse
No, I did partition it to see if that would help, but only converted it to ext3. But I did not try nand+ext. I had him register with the site and will direct him to this thread.
Nandroid Restore
Yeah, i'm the one having this problem. I'm new to modding phones and not for sure what to do. &RoidRage is trying to help me out, if anyone else can that's figure it out that would be great.
Anytime I received the the "via adb" error, it was due to their not being enough memory on the sd card. I found you typically will need a little over 1 GB on the card remaining to do anything: Restore, or backup.
Hope that helps.
And make sure your battery is charged.
Hi guys, first of all I'm a total noob.. first android phone first time rooting, and installing a mod... I should of done more research before installing the CyanogenMod on my phone because now its all buggy and i feel it worked better before. If some one can help me get my phone back to 2.2 that would great.
-Do i fist install a stock rom from http://forum.xda-developers.com/showthread.php?p=12890619#post12890619
-I'm located in the philippines and I dont see any rom for my country all i remember is that I had v10b.
-im not sure if my phone is using ext3/or ext4 but i think its ext4 since im using cyanogenmod. do i need to set it back to ext3 first?
I backed up my phone using nvflash and nandflash.
-first thing i tried before was: wipe data/factory rest, wipe cache partition, wipe dalvik cache and then hit restore. afterwards i booted my phone and it was stuck at the loading bar. so tried the same steps again but nothing so i loaded cm7 zip again my my phone booted up. how do i take this off can someone help please.
i really dont know what im doing..
Follow this
http://forum.xda-developers.com/showthread.php?t=1007825
it will restore your phone back to stock
after nvflashing v10b back on your phone, you can restore your backup if you like to. root and clockworkmod must be installed first though. To install clockworkmod you can also download the clockworkmod recovery img and replace recovery.img in the nvflash files. this will install cwm directly and you don't need to root your device.
You don't need to convert back to ext3. I'm not even sure if cm7 uses ext4...
The reason why you are not able to restore your backup is because of some bug in cwm with restoring boot.img I think..
oscarlg said:
Hi guys, first of all I'm a total noob.. first android phone first time rooting, and installing a mod... I should of done more research before installing the CyanogenMod on my phone because now its all buggy and i feel it worked better before. If some one can help me get my phone back to 2.2 that would great.
-Do i fist install a stock rom from http://forum.xda-developers.com/showthread.php?p=12890619#post12890619
-I'm located in the philippines and I dont see any rom for my country all i remember is that I had v10b.
-im not sure if my phone is using ext3/or ext4 but i think its ext4 since im using cyanogenmod. do i need to set it back to ext3 first?
I backed up my phone using nvflash and nandflash.
-first thing i tried before was: wipe data/factory rest, wipe cache partition, wipe dalvik cache and then hit restore. afterwards i booted my phone and it was stuck at the loading bar. so tried the same steps again but nothing so i loaded cm7 zip again my my phone booted up. how do i take this off can someone help please.
i really dont know what im doing..
Click to expand...
Click to collapse
same thing had happened with me...
not a sigle CWM bakup working,no other zip working through CWM...
i tried with smartflash as well as with NVflash,but the results were same.
then one of the XDA user from this forum adviced me to use onther usb port(preefrably backside one)
and just repeat the NVflash process and guess what !!!!
finally i have managed to get rid of CM7 !!!! and now m back on v10b !!!
try it out,it should work,cheers
thank you
Thanks for the replies guys ill give it a go right now and let you know what happen.
Kickasskev said:
Follow this
http://forum.xda-developers.com/showthread.php?t=1007825
it will restore your phone back to stock
Click to expand...
Click to collapse
i followed the instructions on that page but when i get to the part where i click on nvflash a black screen like cmd pops up then disappears. i tried running as administrator but no go same thing.. am i missing something?
oscarlg said:
i followed the instructions on that page but when i get to the part where i click on nvflash a black screen like cmd pops up then disappears. i tried running as administrator but no go same thing.. am i missing something?
Click to expand...
Click to collapse
same thing had happened with me...
not a sigle CWM bakup working,no other zip working through CWM...
i tried with smartflash as well as with NVflash,but the results were same.
then one of the XDA user from this forum adviced me to use onther usb port(preefrably backside one)
and just repeat the NVflash process and guess what !!!!
finally i have managed to get rid of CM7 !!!! and now m back on v10b !!!
try it out,it should work,cheers
[CHANGE THE USB PORT AND IT WILL WORK FOR SURE]
Hi guys, just flashed 622 baseband with appropriate RIL and now I cant boot...
Here is what I did:
1) Turned phone off, flashed baseband file, it went ok
2) Booted into recovery, restored my CM7 backup and then flashed RIL - success
3) Rebooted phone - getting stuck at LG logo, nothing happens.
Any ideas? Thanks
EDIT:
Hmm, after wiping data, cache and installing plain rom again it booted... Although new clean rom smells fresh, I'd like to get my backup back on and rolling
EDIT2:
Okay booted again, the key was to restore backup and then flash CM7 nightly over it
DELETE PLEASE
.:george:. said:
Hi guys, just flashed 622 baseband with appropriate RIL and now I cant boot...
Here is what I did:
1) Turned phone off, flashed baseband file, it went ok
2) Booted into recovery, restored my CM7 backup and then flashed RIL - success
3) Rebooted phone - getting stuck at LG logo, nothing happens.
Any ideas? Thanks
EDIT:
Hmm, after wiping data, cache and installing plain rom again it booted... Although new clean rom smells fresh, I'd like to get my backup back on and rolling
EDIT2:
Okay booted again, the key was to restore backup and then flash CM7 nightly over it
DELETE PLEASE
Click to expand...
Click to collapse
Glad you figured it out. Yes, you have to flash the CM7 again after you have restored from backup, before booting up.
sacredsoul said:
Glad you figured it out. Yes, you have to flash the CM7 again after you have restored from backup, before booting up.
Click to expand...
Click to collapse
That shouldn't really be necessary unless you're using a defective version of CWM. Some versions didn't restore the boot image properly, which is why you needed to flash it again.
::Trym
TrymHansen said:
That shouldn't really be necessary unless you're using a defective version of CWM. Some versions didn't restore the boot image properly, which is why you needed to flash it again.
::Trym
Click to expand...
Click to collapse
I always do it, just to be on the safe side. Just another couple of mins anyway.
TrymHansen said:
That shouldn't really be necessary unless you're using a defective version of CWM. Some versions didn't restore the boot image properly, which is why you needed to flash it again.
::Trym
Click to expand...
Click to collapse
so, 3.2.0.1 is the most stable and safe at the moment and should not have this issue? want to upgrade to 0622 soon so would be nice to know.
3.2.0.0 upwards doesn't have that problem. I'm happy with 4.0.0.5 though, I like to have the latest.
Rusty! said:
3.2.0.0 upwards doesn't have that problem. I'm happy with 4.0.0.5 though, I like to have the latest.
Click to expand...
Click to collapse
The 4.0.0.5 got a bug. It wont format /system I think, becouse when I installed CM7 over my old FR17 I got FC on many LG apps and services (which isn't in CM ). And yes, I did wipe, but it doesn't matter becouse that's only /data .. It worked with manual format through Advanced menu and then flash rom, but that shouldn't be necessary..
Yes and no, early 4.0.0.5 does that, the later version of it is fixed.
I have tried this numerous times still no result.
Cm 10.1.3 works perfectly fine. But once i flash it with my Titanium backup update.zip file. There will be errors, and after i reboot it, it iwll just get stuck at the spinning blue circle. I have tried everything, from apps+data to only app data. Nothing works.
I would have to factory reset and reflash it again.
I use clockworks mod recovery.
My phone is a odin rooted Galaxy S3 Lte (i9305)
Shinny123 said:
I have tried this numerous times still no result.
Cm 10.1.3 works perfectly fine. But once i flash it with my Titanium backup update.zip file. There will be errors, and after i reboot it, it iwll just get stuck at the spinning blue circle. I have tried everything, from apps+data to only app data. Nothing works.
I would have to factory reset and reflash it again.
I use clockworks mod recovery.
My phone is a odin rooted Galaxy S3 Lte (i9305)
Click to expand...
Click to collapse
use recovery to flash roms not TB, its much more reliable.. i think the problem is because of apps and data you trying to restore with the update.zip. i know you use tb because you want to restore your apps+data easily while flashing new rom, but tb seems to give problems with this method
MaHo_66 said:
use recovery to flash roms not TB, its much more reliable.. i think the problem is because of apps and data you trying to restore with the update.zip. i know you use tb because you want to restore your apps+data easily while flashing new rom, but tb seems to give problems with this method
Click to expand...
Click to collapse
Nah, i didnt flash my rom with tb, i flashed it with recovery. Then once everything was done, i would go back into recovery and flash the update.zip file
Shinny123 said:
Nah, i didnt flash my rom with tb, i flashed it with recovery. Then once everything was done, i would go back into recovery and flash the update.zip file
Click to expand...
Click to collapse
yes i see, but that seems to be the problem ''restoring apps, data with tb'' and from what i know it occurs that this sometimes gives errors, fc's and bootloops like in your case
MaHo_66 said:
yes i see, but that seems to be the problem ''restoring apps, data with tb'' and from what i know it occurs that this sometimes gives errors, fc's and bootloops like in your case
Click to expand...
Click to collapse
So is there no way to go through with this? Maybe export my backups to another software or something? or am i supposed to start fresh?
Shinny123 said:
So is there no way to go through with this? Maybe export my backups to another software or something? or am i supposed to start fresh?
Click to expand...
Click to collapse
you could try to export your backups (only data) to pc temporary and after having flashed the rom with full wipe, install the apps again and put the backups manually in corresponding directories and see how that is gonna work out. I gave up on TB because of this problem and usually i always start fresh with new flashed roms. I only put my personal files on pc and put it back manually after rom install.
MaHo_66 said:
you could try to export your backups (only data) to pc temporary and after having flashed the rom with full wipe, install the apps again and put the backups manually in corresponding directories and see how that is gonna work out. I gave up on TB because of this problem and usually i always start fresh with new flashed roms. I only put my personal files on pc and put it back manually after rom install.
Click to expand...
Click to collapse
Thanks so much, I dont really need all my apps to be backed up, just important ones, has the manual method worked out for you?
Shinny123 said:
Thanks so much, I dont really need all my apps to be backed up, just important ones, has the manual method worked out for you?
Click to expand...
Click to collapse
yes, most of the times works fine but cant guarantee it will work with every app, i guess has something to do with permissions i.m.h.o
hi all, i made an xda account because i really cant understand whats going on with my phone
HTC One M8 running Android 6.0 (rooted)
so after rooting my phone, i proceeded to install xposed.
i flashed the zip - no problem
i installed the apk, and after choosing 4/5 modules that i wanted, i went ahead and enabled them all and rebooted to activate them.
this is where the problems started. my phone booted, however it kept on flashing a screen with the deafult One M8 wallpaper at me. after a few seconds, it came up with an error "com.android.systemui has stopped"
not sure what was going on, i went to twrp and directly restored my nandroid backup, but after waiting for 15 mins, i realised my phone was in bootloop, so i went back to twrp and did a factory reset and restored my nandroid. but again, it went into bootloop. i tried factory resetting and restoring 3 times before giving up.
my phone isnt connecting to my laptop anymore either, but if i need to flash anything i can do it with my sd card.
im not a complete noob but im still learning and ive never not been able to restore my nandroid.
thanks in advance for any help i can get
chaitra26 said:
hi all, i made an xda account because i really cant understand whats going on with my phone
HTC One M8 running Android 6.0 (rooted)
so after rooting my phone, i proceeded to install xposed.
i flashed the zip - no problem
i installed the apk, and after choosing 4/5 modules that i wanted, i went ahead and enabled them all and rebooted to activate them.
this is where the problems started. my phone booted, however it kept on flashing a screen with the deafult One M8 wallpaper at me. after a few seconds, it came up with an error "com.android.systemui has stopped"
not sure what was going on, i went to twrp and directly restored my nandroid backup, but after waiting for 15 mins, i realised my phone was in bootloop, so i went back to twrp and did a factory reset and restored my nandroid. but again, it went into bootloop. i tried factory resetting and restoring 3 times before giving up.
my phone isnt connecting to my laptop anymore either, but if i need to flash anything i can do it with my sd card.
im not a complete noob but im still learning and ive never not been able to restore my nandroid.
thanks in advance for any help i can get
Click to expand...
Click to collapse
*. Flash xposed uninstaller zip and try booting your device. Link here - http://dl-xda.xposed.info/framework/uninstaller/
-->> use thisĀ» make a full wipe from recovery, then restore nandroid backup.
*.While restoring nand. from recovery, make a full wipe like wipe system etc.. Then restore your nand. Then you're good to go.
thanks a ton for your reply
i already tried flashing the uninstaller - didnt work
but ill try your second method. thanks once again
chaitra26 said:
thanks a ton for your reply
i already tried flashing the uninstaller - didnt work
but ill try your second method. thanks once again
Click to expand...
Click to collapse
Hey, the 1st one won't works, Cuz you'd already did a factory data reset, so that's gonna be won't work. And you'd tried restoring nandroid over that, so that's failed.
I hope second one will works.
sachin n said:
*. Flash xposed uninstaller zip and try booting your device.
-->> use thisĀ» make a full wipe from recovery, then restore nandroid backup.
*.While restoring nand. from recovery, make a full wipe like wipe system / data etc.. Then restore your nand. Then you're good to go.
Click to expand...
Click to collapse
Um i think i seriously screwed up - i deleted everything including system and data and stuff - but now my nandroid is gone
what can i do now i dont even have a nandroid!
oh my god my phone doesnt have an os anymore... what have i done wrong?????
chaitra26 said:
Um i think i seriously screwed up - i deleted everything including system and data and stuff - but now my nandroid is gone
what can i do now i dont even have a nandroid!
Click to expand...
Click to collapse
Deym!!
So, look at the One m8 forums, you'll get the workarounds.
I've found one here - https://forum.xda-developers.com/ht...k-twrp-t3086860?_e_pi_=7,PAGE_ID10,5801529172
@chaitra26, either DL any custom ROMs and flash it via custom recovery [Twrp].
Look here for custom ROMs - https://forum.xda-developers.com/htc-one-m8/development?
Regarding that '' no OS installed'' error, that's common when you try to reboot your device from twrp without installing any system images /ROMs.
FYI - when you full wipe your device and tries to power up you'll get the same warning.