what is the point of making backup? - HTC Incredible S

i made a stock backup before going to cm10.1 and then try to restore stock backup but i stuck on htc screen, i installed vipervivo and made a backup before applying a new stock and afterwords i want to back to vipervivo and some restore error in recovery mode, i never changed my recovery im using CWM 5.0.2. hboot2.02, s-on. one thing i dont understand if these backups never gonna work so whats point to made them??. now i have to install vipervivo again and all the app again. crap

Mr909 said:
i made a stock backup before going to cm10.1 and then try to restore stock backup but i stuck on htc screen, i installed vipervivo and made a backup before applying a new stock and afterwords i want to back to vipervivo and some restore error in recovery mode, i never changed my recovery im using CWM 5.0.2. hboot2.02, s-on. one thing i dont understand if these backups never gonna work so whats point to made them??. now i have to install vipervivo again and all the app again. crap
Click to expand...
Click to collapse
You need to get the boot.img from the restore and flash it in fastboot -.-

072665995 said:
You need to get the boot.img from the restore and flash it in fastboot -.-
Click to expand...
Click to collapse
i did in my stock recovery, but how on earth i can do it on my vipervivo rom backup because CWM is nor restoring my backup,i dont remember now but some restore failed error.

Mr909 said:
i did in my stock recovery, but how on earth i can do it on my vipervivo rom backup because CWM is nor restoring my backup,i dont remember now but some restore failed error.
Click to expand...
Click to collapse
I would suggest to achieve S-Off and then you could try another recovery.
And btw. most backups work for me, just sometimes backup of /system fails, but I can still restore the Rest
I am pretty sure that the bootloops accur, because every Rom you installed uses another kernel and your device is S-On, so you can't flash the boot.IMG within recovery

Gizmo648 said:
I would suggest to achieve S-Off and then you could try another recovery.
And btw. most backups work for me, just sometimes backup of /system fails, but I can still restore the Rest
I am pretty sure that the bootloops accur, because every Rom you installed uses another kernel and your device is S-On, so you can't flash the boot.IMG within recovery
Click to expand...
Click to collapse
I tried many times to s-off my device but i every time when i ran RUU i got the 170 error usb connection and i did many things to resolve that error but failed

Mr909 said:
I tried many times to s-off my device but i every time when i ran RUU i got the 170 error usb connection and i did many things to resolve that error but failed
Click to expand...
Click to collapse
Then you could still try another recovery, but remember, you always have to take the boot.IMG from the backup and flash it with fastboot

Gizmo648 said:
Then you could still try another recovery, but remember, you always have to take the boot.IMG from the backup and flash it with fastboot
Click to expand...
Click to collapse
i tried again and this time when i ran RUU i got the unknown error 155.do u have any idea how i solved this issue im using
HTML:
http://forum.xda-developers.com/showthread.php?t=2118187
this guide

Mr909 said:
i tried again and this time when i ran RUU i got the unknown error 155.do u have any idea how i solved this issue im using
HTML:
http://forum.xda-developers.com/showthread.php?t=2118187
this guide
Click to expand...
Click to collapse
Error 155 means that you are trying to run the RUU on a phone with an unlocked bootloader.

Gizmo648 said:
I would suggest to achieve S-Off and then you could try another recovery.
And btw. most backups work for me, just sometimes backup of /system fails, but I can still restore the Rest
I am pretty sure that the bootloops accur, because every Rom you installed uses another kernel and your device is S-On, so you can't flash the boot.IMG within recovery
Click to expand...
Click to collapse
now my device is s-off and blackrose ae well but still cant restore those backups, what a waste

Mr909 said:
now my device is s-off and blackrose ae well but still cant restore those backups, what a waste
Click to expand...
Click to collapse
then it might be a recovery related problem.use another recovery like 4ext or twrp

072665995 said:
then it might be a recovery related problem.use another recovery like 4ext or twrp
Click to expand...
Click to collapse
i have found some where, will it apply to me?
You got that error because you were trying to restore a backup that uses the rfs file system on a CWM that only works with the ext4 file system. You can only restore a stock ROM with CWM 5.0.2.7. Here's a link

Mr909 said:
i have found some where, will it apply to me?
You got that error because you were trying to restore a backup that uses the rfs file system on a CWM that only works with the ext4 file system. You can only restore a stock ROM with CWM 5.0.2.7. Here's a link
Click to expand...
Click to collapse
Its certainly possible although Ive never had that problem. This is the reason why I recommended you get another recovery like 4EXT or TWRP.

072665995 said:
Its certainly possible although Ive never had that problem. This is the reason why I recommended you get another recovery like 4EXT or TWRP.
Click to expand...
Click to collapse
i tried 4EXT recovery as u suggest but no luck...
i successfully restore cm10.1 backup with CWM and now with 4EXT as well. while i made 2 of vipervivo ROM backup and both of them i cant restore, so it means it is the problem in ROM not in recovery??
i also made a stock backup and tried to restore with both CWM and 4EXT and same issue i faced with both, screen stayed on htc logo for few miniuets and then phone reboot to recovery mode by itself. now im almost 100% sure if i will install vipervivo again and will make abackup with 4EXT it wont be restore and will give a same issue "error while restore system"

Related

[RECOVERY] [Crespo] Official TWRP 2.8.x.x

If you want the Official TWRP Recovery (now compatible with KK) for your Nexus S just check this link, there will always be the latest TWRP recovery officially out.
For now the latest is: TWRP 2.8.7.0
LINK: https://dl.twrp.me/crespo/
How to flash this? (Recommended way)
- enter in fastboot mode
- plug to your pc
- open a command prompt at the path where fastboot.exe is located
- type: fastboot flash recovery (drag and drop .img file)
- when done, type: fastboot reboot
PS: You now have a custom recovery and you are rooted. Since 2.5.0.0, TWRP roots your phone for you. Just reboot to recovery, and reboot system, if you are not rooted it will prompt you to root, just slide to accept. Let it reboot ,go to the playstore and download SuperSU.
Or if u are rooted:
- download from the playstore: [ROOT]*Rashr - Flash Tool (Playstore) / [ROOT]*Rashr - The mobile Android Flash-Tool (XDA Thread)
- download the latest TWRP.img
- open the app
- select Flash Other Recovery Image
- browse to your downloads folder
- select the TWRP.img file you just downloaded
THANKS to:
Team Win Recovery Project for this awesome custom recovery.
@DsLNeXuS (XDA username) / Ashot Mkrtchyan for the FREE app.
downloading now. thanks
Hi, I have a problem with a nandroid backup done with 2.3.1.0.
One backup done a week ago, works fine
Backup done today (successful restore) not work (stuck on boot, google and the lock)
Two question:
Is there a way to understand way stuck on boot?
If I restore /system from backup one (same rom) and /data from the last one is the same as full restore the last?
thanks
donpippo said:
Hi, I have a problem with a nandroid backup done with 2.3.1.0.
One backup done a week ago, works fine
Backup done today (successful restore) not work (stuck on boot, google and the lock)
Two question:
Is there a way to understand way stuck on boot?
If I restore /system from backup one (same rom) and /data from the last one is the same as full restore the last?
thanks
Click to expand...
Click to collapse
cant know why it gets stuck... maybe a faulty backup
u can try to grab data end system and substitute with the first one
Cascabreu said:
cant know why it gets stuck... maybe a faulty backup
u can try to grab data end system and substitute with the first one
Click to expand...
Click to collapse
i restored system from the first backup, than data from the second one.
For now works fine. All apps restored with their data.
How is done the backup? Is a dd if=/system of=systembackup ?
If so can I mount -oloop systembackup?
thanks
donpippo said:
i restored system from the first backup, than data from the second one.
For now works fine. All apps restored with their data.
How is done the backup? Is a dd if=/system of=systembackup ?
If so can I mount -oloop systembackup?
thanks
Click to expand...
Click to collapse
Dont know... i made tgis thread just to share the best recovery ever
Sent from my TH3M3D NEXUS S
Is there any changelog from 2.2.2?
Zunex95 said:
Is there any changelog from 2.2.2?
Click to expand...
Click to collapse
stability.
goomanager worked perfectly... thanks for the update
This is no good
luv2vexx said:
This is no good
Click to expand...
Click to collapse
Why? I use it in my nexus and works flawlessly
sent from my brand new Nexus 7
problems with twrp
some roms like sense4all,jb4.1.1 stock rom etc doesn't work with twrp.but works fine with cwm.
Cascabreu said:
Why? I use it in my nexus and works flawlessly
Just tried to restore a TWRP backup, said it was successful, reboot to system and all I get is "Fastboot Mode - No boot or recovery img"
I can still boot to recovery (TWRP)....
What should I do??
Here's what I did to fix: After restoring backup I wiped caches and installed ROM over the top. It is booting now. Thank goodness... I really didn't want to have to start over from scratch!!
Sucks that I can't rely on my nandroid backups though. Unless I am missing something.. This bug needs to be fixed!
not worth it, i reverted back to clockwork 5.8.0
Click to expand...
Click to collapse
luv2vexx said:
Cascabreu said:
Why? I use it in my nexus and works flawlessly
Just tried to restore a TWRP backup, said it was successful, reboot to system and all I get is "Fastboot Mode - No boot or recovery img"
I can still boot to recovery (TWRP)....
What should I do??
Here's what I did to fix: After restoring backup I wiped caches and installed ROM over the top. It is booting now. Thank goodness... I really didn't want to have to start over from scratch!!
Sucks that I can't rely on my nandroid backups though. Unless I am missing something.. This bug needs to be fixed!
not worth it, i reverted back to clockwork 5.8.0
Click to expand...
Click to collapse
Had that issue once and i reflashed the backup and it worked... i still prefer trwp, but different folks for different strokes....
sent from my not almost retired Nexus S
Click to expand...
Click to collapse
luv2vexx said:
Just tried to restore a TWRP backup, said it was successful, reboot to system and all I get is "Fastboot Mode - No boot or recovery img"
I can still boot to recovery (TWRP)....
Click to expand...
Click to collapse
I have this problem too.
I workarounded by flashing ROM's zip and then restoring backup without boot partition
yerazero said:
I have this problem too.
I workarounded by flashing ROM's zip and then restoring backup without boot partition
Click to expand...
Click to collapse
I tried again today and i can confirm that issue, but no biggie if u have the rom too... Lets hpe next version fixes it
Or we are not checking the little box on bbackup the boot partition.... Dunno
sent from my brand new Nexus 7
Cascabreu said:
I tried again today and i can confirm that issue, but no biggie if u have the rom too... Lets hpe next version fixes it
Or we are not checking the little box on bbackup the boot partition.... Dunno
sent from my brand new Nexus 7
Click to expand...
Click to collapse
I'm absolutely sure that I checked System, Data and Boot
thanks for your great work anyway
yerazero said:
I'm absolutely sure that I checked System, Data and Boot
thanks for your great work anyway
Click to expand...
Click to collapse
Thanks but i dont make these recoveries im only sharing it cuz i think apart from this issues wich turn out to be not a problem, twrp is more realiable than cwm...
sent from my brand new Nexus 7
Sorry for being late, OP updated to the latest 2.3.3.0
Now totally supports 4.2 roms
Sent from my Nexus 7 using xda app-developers app
Flashed this as instructed but when I try to boot into recovery I get the dead android guy with the red "!" icon. I'm trying to boot recovery from fastboot, is there another way it should be done?

[Q] return to stock

Think I have this figured out but just want some advice before I take the plunge! I have a Bell Mobility phone rooted with the lastest Viper Rom. Cracked my screen and want to return it for warranty...so what I gather is I need to relock the bootloader and flash the RUU?
As I cant seem to find an official Bell RUU I have downloaded this
http://bugsylawson.com/files/file/1818-m7-cwm-nandroid-backup-cid-bm-001-1296665/
Sound about right?
No RUU for Bell is available.
Only one solution I thing
1) Get S-OFF (using revone) and unlocked boootloader
2) Flash CWM custom recovery
3) Flash this
M7 CWM Nandroid Backup / CID BM___001 / 1.29.666.5
from here http://forum.xda-developers.com/showthread.php?p=39588860
4) Flash any stock recovery
5) Using revone ,remove TAMPERED , Lock bootloader.
6) Get S-On
7) Return phone to service.
ps.If you made the nandroid backup before flashed custom ROM , use it, instead of item 3.
it would be better.
tash2013 said:
No RUU for Bell is available.
Only one solution I thing
1) Get S-OFF (using revone) and unlocked boootloader
2) Flash CWM custom recovery
3) Flash this
M7 CWM Nandroid Backup / CID BM___001 / 1.29.666.5
from here http://forum.xda-developers.com/showthread.php?p=39588860
4) Flash any stock recovery
5) Using revone ,remove TAMPERED , Lock bootloader.
6) Get S-On
7) Return phone to service.
ps.If you made the nandroid backup before flashed custom ROM , use it, instead of item 3.
it would be better.
Click to expand...
Click to collapse
I cant find a stock recovery that will work
faroreefer said:
I cant find a stock recovery that will work
Click to expand...
Click to collapse
stock recovery is here: http://android-revolution-hd.blogspot.com/p/android-revolution-hd-mirror-site-var.html
credits to mike1986
argggg...so frustrated with this. cant flash my origianl back up (post root) says md5 mismatch. cant flash the one that is linked above. just says installation aborted. help??!!
herwegan said:
stock recovery is here: http://android-revolution-hd.blogspot.com/p/android-revolution-hd-mirror-site-var.html
credits to mike1986
Click to expand...
Click to collapse
Can you use that stock recovery on 4.2.2 firmware. As it says 4.1.2 recovery, thanks.
Sent from my HTC One using xda premium
faroreefer said:
argggg...so frustrated with this. cant flash my origianl back up (post root) says md5 mismatch. cant flash the one that is linked above. just says installation aborted. help??!!
Click to expand...
Click to collapse
well, if you get a md5 mismatch there's nothing you can do, this file must be corrupt then.
edit: can you give us some more information about your device/rom/bootloader? and which custom recovery are you using?
jadaress1 said:
Can you use that stock recovery on 4.2.2 firmware. As it says 4.1.2 recovery, thanks.
Sent from my HTC One using xda premium
Click to expand...
Click to collapse
yes, you should be able to use it since it's for 2.17.401.1 and all firmwares above 2 are based on 4.2.2. maybe mike just forgot to change it..
Hboot 1.44.0000
The rom is viper 1.0
Cwm recovery v6.0.3.0
Sent from my HTC One S using xda app-developers app
faroreefer said:
Hboot 1.44.0000
The rom is viper 1.0
Cwm recovery v6.0.3.0
Sent from my HTC One S using xda app-developers app
Click to expand...
Click to collapse
ok, so since the nandroid is for cwm and you are using cwm, this can not be the problem. are you sure that you've placed the nandroid backup in the correct cwm backup folder? so in cwm you can find it under "restore" but then you get an error?
edit: your bootloader is still unlocked isn't it?
herwegan said:
ok, so since the nandroid is for cwm and you are using cwm, this can not be the problem. are you sure that you've placed the nandroid backup in the correct cwm backup folder?[/
pretty sure. I made a backup of the current rom, and then placeed the backup in the same folder. The most current backup restores fine, so i dont think thats it.
Click to expand...
Click to collapse
faroreefer said:
ok, so since the nandroid is for cwm and you are using cwm, this can not be the problem. are you sure that you've placed the nandroid backup in the correct cwm backup folder?[/
pretty sure. I made a backup of the current rom, and then placeed the backup in the same folder. The most current backup restores fine, so i dont think thats it.
Click to expand...
Click to collapse
... i'd really like to help you, but this..... so your own backup file is corrupt and the one from the collection here on xda gives an error, right? do you have cid BM___001?
herwegan said:
ok, so since the nandroid is for cwm and you are using cwm, this can not be the problem. are you sure that you've placed the nandroid backup in the correct cwm backup folder? so in cwm you can find it under "restore" but then you get an error?
edit: your bootloader is still unlocked isn't it?
Click to expand...
Click to collapse
yep & s-off
faroreefer said:
yep & s-off
Click to expand...
Click to collapse
look what i found on the downloadpage: "Backup created with ClockworkMod Recovery v6.0.3.1"
maybe that's the key? try to flash cwm 6.0.3.1 and then the backup
herwegan said:
look what i found on the downloadpage: "Backup created with ClockworkMod Recovery v6.0.3.1"
maybe that's the key? try to flash cwm 6.0.3.1 and then the backup
Click to expand...
Click to collapse
YES!! that did it. so i have the stock rom flashed. but now ive flashed the recovery from the previous suggestion and all i have is a big red triangle?!
frustraion level 9.1
faroreefer said:
YES!! that did it. so i have the stock rom flashed. but now ive flashed the recovery from the previous suggestion and all i have is a big red triangle?!
frustraion level 9.1
Click to expand...
Click to collapse
great! don't worry, this is how it should be now because you've flashed STOCK-recovery all fine, now just leave it like that, use revone to lock your bootloader and finally use hasoon2000's toolkit to switch back to s-on. and voilĂ , you're completely stock then :highfive:
herwegan said:
great! don't worry, this is how it should be now because you've flashed STOCK-recovery all fine, now just leave it like that, use revone to lock your bootloader and finally use hasoon2000's toolkit to switch back to s-on. and voilĂ , you're completely stock then :highfive:
Click to expand...
Click to collapse
DONE and DONE! only took 2 days.lol
thanks for the assistance
faroreefer said:
DONE and DONE! only took 2 days.lol
thanks for the assistance
Click to expand...
Click to collapse
congrats, you're welcome, glad i could help

Install Nandroid ZIP Woes

I can't for the life of my install a stock nandroid to my HTC One. I have tried everything and i can't restore it to the BM___001 nandroid. I need to restore it to stock and i am out of tricks. Suggestions?
Want to give some more details? Which custom recovery are you using? What commands have you been using? What errors you get?
deeevan said:
Want to give some more details? Which custom recovery are you using? What commands have you been using? What errors you get?
Click to expand...
Click to collapse
I am trying to install the BM____001 nandroid with CWM. I put the unzipped folder in the right location and cwm does see it. I tried flashing the straight zip and it fails. I try flashing through ROM Manager and it fails. I will re flash to get error codes for you.
MKVFTW said:
I am trying to install the BM____001 nandroid with CWM. I put the unzipped folder in the right location and cwm does see it.
Click to expand...
Click to collapse
You can forget about the rest of your attempts. CWM nandroids are not flashed. Just report back the error you got when you selected the folder to restore.
deeevan said:
You can forget about the rest of your attempts. CWM nandroids are not flashed. Just report back the error you got when you selected the folder to restore.
Click to expand...
Click to collapse
I knew that but tried anyways. I can't even get the the folder to show up in the backup menu to try and restore.
MKVFTW said:
I knew that but tried anyways. I can't even get the the folder to show up in the backup menu to try and restore.
Click to expand...
Click to collapse
I thought you said CWM could see it? Was that a typo?
I'm guessing you're on a 4.2.2 ROM? CWM still thinks your sdcard is at /data/media not the new /data/media/0. Move the clockworkmod folder into /data/media and CWM should be able to see your backups.
deeevan said:
I thought you said CWM could see it? Was that a typo?
I'm guessing you're on a 4.2.2 ROM? CWM still thinks your sdcard is at /data/media not the new /data/media/0. Move the clockworkmod folder into /data/media and CWM should be able to see your backups.
Click to expand...
Click to collapse
.
Got it, and have restored with the CWM backup. Now once it boots, the touch screen does not work. Previously i was on GPe 4.3 and have since updated the firmware.
Downloaded the appropriate BM OTA from the RUU collection and tried to install it and it gives me CID missmatch. I changed from CID 1111111 back to BM___001 and it still gives me the same issue. So i pulled the firmware.zip from the OTA and flashed it via rebootRUU. It flashed sucessfully (both times) and restarted. Still the touch wont work.
I am at a loss with this thing.

[Q] 4.4.2 CM11, return to all stock?

I have an HTC One on sprint, running a CM11 nightly. While I liked it for a while, due to business aspects, I need to go back to iphone. I am just gonna trade someone I know for my HTC for their iphone. I guess what i was wondering is what is the process of returning it back to stock? They still want root access, just not a custom ROM. I'm S-ON, HBOOT 1.56.000, Radio, 1.00.20.1100, and OS 4.06.651.4.
I'd like a step by step process hopefully (not an expert on androids, more used to iphones). But i do have some experience with cmd. I was also wondering if I turn it back to stock, will i lose all of my data (contacts, photos,etc.) I know you lose apps, but when I flashed to CM11, I backed up with TWRP, and then had to use CWM, so i couldn't restore my contacts. I do have a backup of my original ROM before i went to CM11 in TWRP, but I had to flash to CWM, so I'm not sure if it's still there.
Also, if they wanted to keep the CM11 on it, would there be any problems switching phone numbers and whatnot on it? I'd assume not because it still has an IMEI, but just wanted to make sure.
Find a flashable zip of twrp and if you didn't delete it ur backup of ur stock rooted should work...u have to have Sprint base Rom to swap phones so NO cm11 will not work when you go to trade phones
Sent from my HTCONE using Xparent Red Tapatalk 2
noXcape said:
Find a flashable zip of twrp and if you didn't delete it ur backup of ur stock rooted should work...u have to have Sprint base Rom to swap phones so NO cm11 will not work when you go to trade phones
Sent from my HTCONE using Xparent Red Tapatalk 2
Click to expand...
Click to collapse
I tried to reflash twrp. It wouldnt work. it wouldnt recognize touches.
So if I want it all stock, except for root, can I use an RUU? I know it wipes everything, but better than nothing. plus i could sync with htc manager and get everything i had back.
FireGuy2014 said:
I tried to reflash twrp. It wouldnt work. it wouldnt recognize touches.
So if I want it all stock, except for root, can I use an RUU? I know it wipes everything, but better than nothing. plus i could sync with htc manager and get everything i had back.
Click to expand...
Click to collapse
what version of twrp did you flash, should be 2.6.3.0 or higher. thus the touch problems, you don't need to ruu.(openrecovery-twrp-2.6.3.0-m7wls.img)
Aldo101t said:
what version of twrp did you flash, should be 2.6.3.0 or higher. thus the touch problems, you don't need to ruu.(openrecovery-twrp-2.6.3.0-m7wls.img)
Click to expand...
Click to collapse
I used that originally i believe. So if I re-flash my recovery to twrp, I can restore from my back up, even if I was rooted? and would i still have CM11, or stock sense?
FireGuy2014 said:
I used that originally i believe. So if I re-flash my recovery to twrp, I can restore from my back up, even if I was rooted? and would i still have CM11, or stock sense?
Click to expand...
Click to collapse
yep, you'll still have the same rom after flashing recovery til you restore a previous backup, you can back up cm 11 too.
Aldo101t said:
yep, you'll still have the same rom after flashing recovery til you restore a previous backup, you can back up cm 11 too.
Click to expand...
Click to collapse
I'm selling it and the person wants a stock rom, but also rooted. So Would I have sense or CM11 if i flash my twrp and restore my backup?
FireGuy2014 said:
I'm selling it and the person wants a stock rom, but also rooted. So Would I have sense or CM11 if i flash my twrp and restore my backup?
Click to expand...
Click to collapse
if your backup is stock sense it will be sense.i have no idea what your backup is. you should know that.
Aldo101t said:
if your backup is stock sense it will be sense.i have no idea what your backup is. you should know that.
Click to expand...
Click to collapse
I tried using the twrp manager from the play store but it says I'm not supported. 2.7.0.0 is the latest. It shows the backup i have though. Does anyone know where I can download it from and flash it onto my phone?
FireGuy2014 said:
I tried using the twrp manager from the play store but it says I'm not supported. 2.7.0.0 is the latest. It shows the backup i have though. Does anyone know where I can download it from and flash it onto my phone?
Click to expand...
Click to collapse
http://techerrata.com/browse/twrp2/m7wls is where to go 2.7.0.1 is the latest, flash this with adb fastboot, in your bootloader
Aldo101t said:
http://techerrata.com/browse/twrp2/m7wls is where to go 2.7.0.1 is the latest, flash this with adb fastboot, in your bootloader
Click to expand...
Click to collapse
would the command be fastboot flash recovery openrecovery-twrp-2.7.0.1-m7wls.img?
FireGuy2014 said:
would the command be fastboot flash recovery openrecovery-twrp-2.7.0.1-m7wls.img?
Click to expand...
Click to collapse
yessir
Aldo101t said:
yessir
Click to expand...
Click to collapse
should i erase my cache first?
Or just plug it up, go to bootloader, and flash it, then restore?
FireGuy2014 said:
should i erase my cache first?
Or just plug it up, go to bootloader, and flash it, then restore?
Click to expand...
Click to collapse
not sure on the cache erase some say do some say don't i'd try it without first if you have issues wipe it and reflash recovery
Aldo101t said:
not sure on the cache erase some say do some say don't i'd try it without first if you have issues wipe it and reflash recovery
Click to expand...
Click to collapse
tried to no avail. I tried and it was stuck on HTC logo for 15 minutes. I reflashed to CM11, and im downloading the RUU now to completely wipe/restore it. Unless i did something wrong? I erased cache using adb, then booted up, restored my stuff, and it said successful, but it was on the htc logo. I tried again to the same thing. then i reflashed cm11 and it worked. did i forget to do a factory reset before i restored everything? it said it wiped stuff before it restored it.
FireGuy2014 said:
tried to no avail. I tried and it was stuck on HTC logo for 15 minutes. I reflashed to CM11, and im downloading the RUU now to completely wipe/restore it. Unless i did something wrong? I erased cache using adb, then booted up, restored my stuff, and it said successful, but it was on the htc logo. I tried again to the same thing. then i reflashed cm11 and it worked. did i forget to do a factory reset before i restored everything? it said it wiped stuff before it restored it.
Click to expand...
Click to collapse
after you erased cache did you flash recovery, then reboot recovery and restore a backup
when you are on the htc logo hold the power button down til it reboots and see if it goes past the htc screen
you don't have to factory reset to restore a rom just hit restore and select the backup
Aldo101t said:
after you erased cache did you flash recovery, then reboot recovery and restore a backup
when you are on the htc logo hold the power button down til it reboots and see if it goes past the htc screen
Click to expand...
Click to collapse
I flashed recovery, then erased cache, then rebooted to recovery, and restored a backup. when it said successful, i rebooted from there, and it vibrated on bootup, but stayed at the htc screen for a while. I held the power button and rebooted. same thing.
FireGuy2014 said:
I flashed recovery, then erased cache, then rebooted to recovery, and restored a backup. when it said successful, i rebooted from there, and it vibrated on bootup, but stayed at the htc screen for a while. I held the power button and rebooted. same thing.
Click to expand...
Click to collapse
well, i don't know, i'd try 2.6.3.0 twrp and don't wipe cache, thats what i been using, what the hell can't hurt to try at this point in the game
sometimes it takes awhile on the first boot, i've had some take quit awhile, but i don't know
Aldo101t said:
well, i don't know, i'd try 2.6.3.0 twrp and don't wipe cache, thats what i been using, what the hell can't hurt to try at this point in the game
Click to expand...
Click to collapse
I'm gonna try an RUU. I'm downloading the latest one right now (4.06.651.4 i believe). I'll let you know how it works out. since i'm S-ON, all i need to do is relock boot loader and then run the RUU correct?
FireGuy2014 said:
I'm gonna try an RUU. I'm downloading the latest one right now (4.06.651.4 i believe). I'll let you know how it works out. since i'm S-ON, all i need to do is relock boot loader and then run the RUU correct?
Click to expand...
Click to collapse
yes,

Boot Loop S On Help

Hi
I had cm11 installed but then tried to install a kernel which put my htc one m7 into a boot loop
now in the recovery screen it says:
TAMPERED
RELOCKED
S-ON
I didnt have a nandroid backup and I am in need of urgent help Please
elnino-1990 said:
Hi
I had cm11 installed but then tried to install a kernel which put my htc one m7 into a boot loop
now in the recovery screen it says:
TAMPERED
RELOCKED
S-ON
I didnt have a nandroid backup and I am in need of urgent help Please
Click to expand...
Click to collapse
Never relock your bootloader if your using a custom rom or recovery, so first of all, get it unlocked again.
which kernel did you flash ?
bulletproof kernel.. is there a guide to do that or can i follow the following one:
http://www.xda-developers.com/android/how-to-unlock-the-htc-one-bootloader-xda-developer-tv/
elnino-1990 said:
bulletproof kernel.. is there a guide to do that or can i follow the following one:
http://www.xda-developers.com/android/how-to-unlock-the-htc-one-bootloader-xda-developer-tv/
Click to expand...
Click to collapse
I believe bullet proof is a sense only kernel, CM is an asop rom not a sense rom.
Just unlock your bootloader at HTC Dev,
Once its unlocked, you might get lucky and just be able to flash a correct kernel to get booting again, failing that you'll either have to flash a new rom or restore your backup.
Sorry that took long it now says unlocked. How do i go about install cyanogenmod again or do i have to install a stock?
elnino-1990 said:
Sorry that took long it now says unlocked. How do i go about install cyanogenmod again or do i have to install a stock?
Click to expand...
Click to collapse
Try flashing an AOSP kernel now, something like this one, hopefully after that your phone will boot back to CM.
http://forum.xda-developers.com/showthread.php?t=2789806
is your backup a CM rom or a sense rom ?
Seanie280672 said:
Try flashing an AOSP kernel now, something like this one, hopefully after that your phone will boot back to CM.
http://forum.xda-developers.com/showthread.php?t=2789806
is your backup a CM rom or a sense rom ?
Click to expand...
Click to collapse
Thing is i did a factory rest so I wont have CM on the phone anymore will I? Also i didnt make a backup
elnino-1990 said:
Thing is i did a factory rest so I wont have CM on the phone anymore will I? Also i didnt make a backup
Click to expand...
Click to collapse
yes the rom will still be there if it was only a factory reset, if you did an advanced wipe inside something like TWRP then it wont.
Factory reset just restores whatever rom is on your phone to the state it was at when you first installed it, ie you will just have to set it back up again with email addresses and passwords, carrier and country etc after it boots.
Seanie280672 said:
yes the rom will still be there if it was only a factory reset, if you did an advanced wipe inside something like TWRP then it wont.
Factory reset just restores whatever rom is on your phone to the state it was at when you first installed it, ie you will just have to set it back up again with email addresses and passwords, carrier and country etc after it boots.
Click to expand...
Click to collapse
oh ok. as the kernel is in a zip do I have to extract it or use fastboot ?
elnino-1990 said:
oh ok. as the kernel is in a zip do I have to extract it or use fastboot ?
Click to expand...
Click to collapse
you will need to enter recovery, push or sideload it to your internal sdcard and then flash it in recovery.
Seanie280672 said:
you will need to enter recovery, push or sideload it to your internal sdcard and then flash it in recovery.
Click to expand...
Click to collapse
i sideloaded the kernel in recovery and nothing. it instaleld it but after a reboot it is stuck on the htc logo. also the same when i push the kernel to sd card

Categories

Resources