Ok so i need to send my inc 2 in for a refurb. I am currently running AOKP build 37 with aeroevans v9ics kernel and an unlocked BL. How do i return to complete stock unrooted?
i've seached all over the forum and can't find anything. It was easy with my droid x2 because you could just run the SBF with RSD Lite.
I also have the new software version 6.1 if thats any help.
Here you go: http://forum.xda-developers.com/showthread.php?t=1599767
Nicely posted by CondemnedSoul.
blazingwolf said:
Here you go: http://forum.xda-developers.com/showthread.php?t=1599767
Nicely posted by CondemnedSoul.
Click to expand...
Click to collapse
there is only one problem. I have the newest OTA software 6.1.x.x.x.x. and that post is for the 5.10.605.9 OTA. Will this still work or will i risk effin up my phone.
dets34 said:
there is only one problem. I have the newest OTA software 6.1.x.x.x.x. and that post is for the 5.10.605.9 OTA. Will this still work or will i risk effin up my phone.
Click to expand...
Click to collapse
Your running AOKP right now right? According to your first post you are anyways. That means your not running the 6.1 anymore. In other words you should be fine.
blazingwolf said:
Your running AOKP right now right? According to your first post you are anyways. That means your not running the 6.1 anymore. In other words you should be fine.
Click to expand...
Click to collapse
hmm never thought about it like that. I guess ill give it a try and see how wise you truly are.
Just tried running the PG32IMG.zip file in bootloader and it didnt work. Still running AOKP. any other ideas. What about an RUU
dets34 said:
Just tried running the PG32IMG.zip file in bootloader and it didnt work. Still running AOKP. any other ideas. What about an RUU
Click to expand...
Click to collapse
Hmm. What did it say as it went through the process?
It didnt say anything. It found the PG32IMG.zip file, ran it, and then returned to the bootloader screen. I tried running it again just in-case something weird happened, but same result.
also on a side note im s-on, the 6.1 OTA doesn't allow s-off at this time
dets34 said:
It didnt say anything. It found the PG32IMG.zip file, ran it, and then returned to the bootloader screen. I tried running it again just in-case something weird happened, but same result.
also on a side note im s-on, the 6.1 OTA doesn't allow s-off at this time
Click to expand...
Click to collapse
I didn't think about that. That could be the issue then. No nandroid backup of your stock ROM right?
I'm thinking the best you can do is find a similar to stock ROM and install that. Most times the service techs don't look to hard at a device to see that it is running a custom ROM.
blazingwolf said:
I didn't think about that. That could be the issue then. No nandroid backup of your stock ROM right?
I'm thinking the best you can do is find a similar to stock ROM and install that. Most times the service techs don't look to hard at a device to see that it is running a custom ROM.
Click to expand...
Click to collapse
i believe i have a nandroid of my pre AOKP rom, but that is still rooted.
dets34 said:
i believe i have a nandroid of my pre AOKP rom, but that is still rooted.
Click to expand...
Click to collapse
Great! Use that and then download one of the apps that helps to remove root. One such app is OTA Rootkeeper. https://play.google.com/store/apps/...m9yZy5wcm9qZWN0dm9vZG9vLm90YXJvb3RrZWVwZXIiXQ..
Hopefully that will help.
blazingwolf said:
Great! Use that and then download one of the apps that helps to remove root. One such app is OTA Rootkeeper. https://play.google.com/store/apps/...m9yZy5wcm9qZWN0dm9vZG9vLm90YXJvb3RrZWVwZXIiXQ..
Hopefully that will help.
Click to expand...
Click to collapse
Thank heavens for my overly cautious brain
Sorry about taking you down the wrong path before. Forgot about the S-off thing with the newer version.
blazingwolf said:
Sorry about taking you down the wrong path before. Forgot about the S-off thing with the newer version.
Click to expand...
Click to collapse
not a problem. however now that i just restored to my nandroid i had before flashing the AOKP rom im stuck at the droid eye screen =(. any idea?
dets34 said:
not a problem. however now that i just restored to my nandroid i had before flashing the AOKP rom im stuck at the droid eye screen =(. any idea?
Click to expand...
Click to collapse
Did you clear dalvik cache?
blazingwolf said:
Did you clear dalvik cache?
Click to expand...
Click to collapse
cleared everything. i just tried flashing the andybonestock or whatever rom, and im getting the same thing. stuck at the droid eye.
nvm i take that back. the andybonestock rom flashed, just took a little while to load
dets34 said:
nvm i take that back. the andybonestock rom flashed, just took a little while to load
Click to expand...
Click to collapse
Cool. That one should work for you as well.
blazingwolf said:
Cool. That one should work for you as well.
Click to expand...
Click to collapse
how do i go about removing an trace of root. well at least the superuser app. besides that my phone "looks" stock.
dets34 said:
how do i go about removing an trace of root. well at least the superuser app. besides that my phone "looks" stock.
Click to expand...
Click to collapse
The app I listed above.
SuperUser can also just be deleted but the modified su will still be there.
Related
So im going to take my phone in to the sprint store tomorrow because the camera is all grainy and messed up now. I tried to wipe it several times but its still grainy. Its probably from cyanogen and all the flashing but i cant tell. What are the steps i can take to go back to stock before i go there? How do i unroot and so on?
Sent from my CM 7 Monster Evol.
Go to the unrevoked site, download the s-on tool, flash in recovery, make sure you become s-on.
Then download a 3.70 RUU in PC36IMG form, or as an exe and then run it.
If you do the exe form, make sure the phone is connected in fastboot before you run.
Read my guide if you used unrevoked 3 I have the links u need. CM wouldnt of caused your cam issues some cams started going bad thats why 0004 got a fix for that.
Also, i have a custom rom flashed in right now.
Sent from my CM 7 Monster Evol.
Jason Black said:
Also, i have a custom rom flashed in right now.
Sent from my CM 7 Monster Evol.
Click to expand...
Click to collapse
Either of our methods will works; you'll be on a stock unrooted rom by the end of it.
teh roxxorz said:
Go to the unrevoked site, download the s-on tool, flash in recovery, make sure you become s-on.
Then download a 3.70 RUU in PC36IMG form, or as an exe and then run it.
If you do the exe form, make sure the phone is connected in fastboot before you run.
Click to expand...
Click to collapse
Dont i have to flash the stock rom first?
Jason Black said:
Dont i have to flash the stock rom first?
Click to expand...
Click to collapse
No, because if you do that, you could be left with s-off, then they'll know you were rooted. That's why you run the s-on first.
teh roxxorz said:
Either of our methods will works; you'll be on a stock unrooted rom by the end of it.
Click to expand...
Click to collapse
Oh alright thanks
Jason Black said:
Oh alright thanks
Click to expand...
Click to collapse
Never a problem.
reaper24 said:
Read my guide if you used unrevoked 3 I have the links u need. CM wouldnt of caused your cam issues some cams started going bad thats why 0004 got a fix for that.
Click to expand...
Click to collapse
Yah i only said that because i also flashed roms but once i started following the nightly and the went back to sense, my camera was all messed up. Not like im blaming anyone. Its my fault regardless.
Sent from my CM 7 Monster Evol.
reaper24 said:
Read my guide if you used unrevoked 3 I have the links u need. CM wouldnt of caused your cam issues some cams started going bad thats why 0004 got a fix for that.
Click to expand...
Click to collapse
Big thanks for the guide. Made my life easy. I'll do this in the morning before i go to the sprint store.
Sent from my CM 7 Monster Evol.
Jason Black said:
Big thanks for the guide. Made my life easy. I'll do this in the morning before i go to the sprint store.
Sent from my CM 7 Monster Evol.
Click to expand...
Click to collapse
NP man all links are there should make it easy as pie. Get the stock RUU PC36IMG.ZIP and the UNREVOKED FOREVER SON ZIP. FLASH THE UNREVOKED FOREVER SON ZIP FIRST IT WILL TURN S ON AND THEN BOOT INTO BOOTLOADER AND IT WILL RUN THE RUU PC36IMG.ZIP .
Make sure you delete them after your back to stock so sprint wont see them on your sd card.
Is much easier if u only do a ruu of the lastest update. U dont need no guide. Only make sure u have sync installed and format ur sd card ones ur done with the process.
Sent from my PC36100 using XDA Premium App
fennix said:
Is much easier if u only do a ruu of the lastest update. U dont need no guide. Only make sure u have sync installed and format ur sd card ones ur done with the process.
Sent from my PC36100 using XDA Premium App
Click to expand...
Click to collapse
It's got the links he needs man plus you have to turn s back on won't do you any good to flash a RUU with it off.
Or flash sprint lovers.. They never noticed me.. And that way you can just flash back afterwards
If you don't turn S on and you flash anything other then stock RUU there is always a chance you will get your warranty voided if they decide to do a hard reset and boot your phone into bootloader they will see it so why risk it.
Do what you want guide has links for you dummy proof lol
Yeah.. im unrooting lol. Its really easy to re-root anyway.
Sent from my CM 7 Monster Evol.
Ye, you shouldn't have any problems.
This is pretty much rooted stock. As with all of "my" (HTC's) plainjane roms, there won't be improvements until the next OTA.
http://www.multiupload.com/RVUCMAHD1M
thanks jcase. im excited to experience the inc2 on stock froyo without the vzw bloatware. its been a great handset out of the box.
jcase said:
This is pretty much rooted stock. As with all of "my" (HTC's) plainjane roms, there won't be improvements until the next OTA.
http://www.multiupload.com/RVUCMAHD1M
Click to expand...
Click to collapse
Thanks Buddy.
this is still just the rom right? s-off and root is still in beta?
applejacks108 said:
this is still just the rom right? s-off and root is still in beta?
Click to expand...
Click to collapse
Its a stock rom, for those with s-off. Mainly to get ppl back to stock but rooted, if they desire to.
Is it the chinese - english Stock Rom froyo ?
Just get s-off and tried to flash this rom. Everything went fine but i see no su in programs (( No any root sw wont work. Maybe im doing something wrong ? Ive opened zip and su and busybox is there in xbin folder but no su after rom flashed .
Getting stuck on the htc splash screen any time I try to install this...
I also am getting stuck at the HTC boot splash. I'm kind of new to the custom roms though.
I used fastboot and flashed the boot.img to the boot partition. Then took the /system and repackaged it into a yaffs2 image. Flashed the result to the system partition. Don't know if thats exactly what to do.
-Jim
You just have to flash it in recovery. Nothing tricky or difficult like what the previous poster described. The instructions for flashing can be found in almost any ROM thread.
Sent from my ADR6350 using XDA App
I have to return my phone to Verizon because the power/usb cable connection stopped working. I'm downloading this ROM to my sdcard and will flash with this.
Do you think this will be good enough to not void the warranty? I was linked to this: http://rootzwiki.com/showthread.php...X-INCREDIBLE-2-(vivow)-ONLY&p=39759#post39759 but I have no way of connecting my phone to a computer to run the commands.
Just attempted to install this using recovery... upon reboot I'm stuck at HTC splash screen. -this seems to have happened to others as well.
New Link
Hi The MutiUpload link is not working. Can anyone post the link to download this ROM? Thanks
xyz99002 said:
Hi The MutiUpload link is not working. Can anyone post the link to download this ROM? Thanks
Click to expand...
Click to collapse
This is very outdated.
Sent from my Incredible 2 using xda app-developers app
thenaut said:
This is very outdated.
Click to expand...
Click to collapse
But if you are looking to go stock you might peruse this thread.
tried to flash the new paranoid android rom... went to bootloop... now trying to get back using my nandroid backup... and my Hboot has vanished, phone going straight to recovery... Help anyone???
sumairmh said:
tried to flash the new paranoid android rom... went to bootloop... now trying to get back using my nandroid backup... and my Hboot has vanished, phone going straight to recovery... Help anyone???
Click to expand...
Click to collapse
are you pressing any buttons to get into recovery? or is it just bootlooping into it? you tried flashing an ruu? on second thought to flash an ruu, dont you need to have a locked, or relocked bootloader? and that requires fastboot, which is in hboot. damn. maybe you can send it off to htc?
sumairmh said:
tried to flash the new paranoid android rom... went to bootloop... now trying to get back using my nandroid backup... and my Hboot has vanished, phone going straight to recovery... Help anyone???
Click to expand...
Click to collapse
Try Flashing a Sense rom with APM, AKA MyOneV RC 3.0, and reboot into bootloader, and try Flashing an RUU
sumairmh said:
tried to flash the new paranoid android rom... went to bootloop... now trying to get back using my nandroid backup... and my Hboot has vanished, phone going straight to recovery... Help anyone???
Click to expand...
Click to collapse
First of all, the rom is fine. It boots fine, it installs fine. The partitions are fine (it has the same updater-script like CM9), so I VERY MUCH DOUBT that the rom deleted your Hboot or anything... Try downloading One V all in one tool and from there select reboot phone in bootloader. see if that helps.
Thanks,
1ceb0x
hey guys... thanks for all the help, i din say anything about the new rom doing this... but well i flashed rc3.0 and restored data, that fixed it... and sounding incredibly stupid it seems my battery was low... anyway its fixed now... i'm gonna try flashing paranoid once more when my battery is fully charged...:good:
sumairmh said:
hey guys... thanks for all the help, i din say anything about the new rom doing this... but well i flashed rc3.0 and restored data, that fixed it... and sounding incredibly stupid it seems my battery was low... anyway its fixed now... i'm gonna try flashing paranoid once more when my battery is fully charged...:good:
Click to expand...
Click to collapse
Glad it worked out for you!
1ceb0x said:
Glad it worked out for you!
Click to expand...
Click to collapse
hey i flashed yo rom, everything works fine (well whatever is working), except everytime i get a call android phone FC's, is this a known bug?
sumairmh said:
hey i flashed yo rom, everything works fine (well whatever is working), except everytime i get a call android phone FC's, is this a known bug?
Click to expand...
Click to collapse
Try to lower the DPI for the Phone.apk app. You can do this from Paranoid Android settings!
1ceb0x said:
Try to lower the DPI for the Phone.apk app. You can do this from Paranoid Android settings!
Click to expand...
Click to collapse
so i take it that its workin for u?
sumairmh said:
so i take it that its workin for u?
Click to expand...
Click to collapse
it was not tested completely. will need to do it so today! but try that fix. in general the FC's are from the DPI lowered...
looks like some prob with SU, it denies root access, tried updating it from play also tried changing default to prompt and allow, still doesn help... i loved the rom but if it doesnt let me make or take calls... well i guess i'll have to wait for the next update...
sumairmh said:
looks like some prob with SU, it denies root access, tried updating it from play also tried changing default to prompt and allow, still doesn help... i loved the rom but if it doesnt let me make or take calls... well i guess i'll have to wait for the next update...
Click to expand...
Click to collapse
easy fix for you....flash this in CWM http://download.chainfire.eu/204/SuperSU/CWM-SuperSU-v0.94.zip
it's a CM9 bug that i thought i had fixed....herp derp
As i've said. Didn't had enough time to test it but I'm glad someone is giving me feedback. I'll be working on it in the next days.
I had a backup of stock before root but when i tried to back up to it today it gave me a md5 mismatch so i couldnt back up to it. From what I seen in beaups thread that I need to be on a stock rom and stock kernal for his s-off method to work. Is there a stock rom that I could flash to use the s-off method?
I'd like this answered as well. I think andy's stock rom near the bottom of the page works, but I haven't had a confirmation yet. Also wondering if odex versus deodexed versions matter.
Same boat im in just waiting for somebody to say which one we can use when we are already rooted and unlocked. I dont know how my md5's mismatched on my stock before root backup but I can't go back to it so Im kinda stuck here until we get a answer.
Aggies1288 said:
Same boat im in just waiting for somebody to say which one we can use when we are already rooted and unlocked. I dont know how my md5's mismatched on my stock before root backup but I can't go back to it so Im kinda stuck here until we get a answer.
Click to expand...
Click to collapse
Just heard andy's bonestock works trying it myself to confirm.
EDIT: Downloading the 1.1 download not the newest. Under old downloads. I would think the more stock the better.
cstrife999 said:
Just heard andy's bonestock works trying it myself to confirm.
EDIT: Downloading the 1.1 download not the newest. Under old downloads. I would think the more stock the better.
Click to expand...
Click to collapse
Just tried v1.0a..... No dice.
I'd test 1.1 but for some reason it won't let me copy the zip over to my phone... Keeps saying the device has stopped working or has been disconnected. Tried many different USB ports.... Going to have to bluetooth it which is going to take even more time...
cstrife999 said:
I'd test 1.1 but for some reason it won't let me copy the zip over to my phone... Keeps saying the device has stopped working or has been disconnected. Tried many different USB ports.... Going to have to bluetooth it which is going to take even more time...
Click to expand...
Click to collapse
Im downloading 1.1 now. Ill get back with y'all on how it went.
Aggies1288 said:
Im downloading 1.1 now. Ill get back with y'all on how it went.
Click to expand...
Click to collapse
I found VZW_Stock_Rooted_deodex from Andy
Trying that now..
mcampos7 said:
I found VZW_Stock_Rooted_deodex from Andy
Trying that now..
Click to expand...
Click to collapse
This is what I've been on since launch day. Curious if this will work.
m4rk0358 said:
This is what I've been on since launch day. Curious if this will work.
Click to expand...
Click to collapse
Actually I'm having more problems with this than I did trying it on 1.0a and NOS...
I'm trying to find my nandroid of stock rooted but I think it was on a drive that failed.
Linux boot, next???
mcampos7 said:
Actually I'm having more problems with this than I did trying it on 1.0a and NOS...
I'm trying to find my nandroid of stock rooted but I think it was on a drive that failed.
Linux boot, next???
Click to expand...
Click to collapse
Yea i got made fun of when using that lol...
SUPER MEGA ULTIMATE DISCLAIMER: IIRC = IF I REMEMBER CORRECTLY. I AM NOT RESPONSIBLE IF THIS DOESN'T WORK/SCREWS UP YOUR DEVICE/BRICKS/ETC. YOU ARE WARNED. THIS WORKED FOR ME IN THE PAST WITH MY GALAXY NEXUS BACKUPS USING CWMTOUCH 6.0.3.6 AND 6.0.4.3.
YOU ARE WARNED.
I HAVE NEVER USED TWRP FOR BACKUPS. IT IS A MERE SUGGESTION THAT THIS METHOD WILL WORK WITH SIMILAR RESULTS. I HAVE NEVER BROWSED A BACKUP FOR TWRP. ANY ATTEMPT YOU MAKE USING A TWRP BACKUP IS OF YOUR OWN COGNIZANCE. YOU HAVE BEEN WARNED.
YOU ARE WARNED.
YOU ARE WARNED.
IIRC: If you have an md5 mismatch while trying to restore in a recovery, try this process:
IF YOU HAVE A BACKUP I HIGHLY SUGGEST STORING THE BACKUP FILE ON YOUR DESKTOP JUST IN CASE!!!!
Boot into whatever ROM you're on ATM.
Browse to your ClockworkMod (or TWRP backup must have an accessible folder for it's backups) using a Root file explorer, which I happen to use "Root Explorer" and open the backup file you just made.
Inside of that will be a nandroid.md5.
Delete that file and reboot into recovery, and try restoring again.
SUPER MEGA ULTIMATE DISCLAIMER: IIRC = IF I REMEMBER CORRECTLY. I AM NOT RESPONSIBLE IF THIS DOESN'T WORK/SCREWS UP YOUR DEVICE/BRICKS/ETC. YOU ARE WARNED. THIS WORKED FOR ME IN THE PAST WITH MY GALAXY NEXUS BACKUPS USING CWMTOUCH 6.0.3.6 AND 6.0.4.3.
YOU ARE WARNED.
YOU ARE WARNED.
YOU ARE WARNED.
This method did work for me several times on several backups, but root and S-Off being so new, I cannot attest that it works for the One. YOU ARE WARNED**!!
cstrife999 said:
Yea i got made fun of when using that lol...
Click to expand...
Click to collapse
For using what? Linux? NOS?
mcampos7 said:
For using what? Linux? NOS?
Click to expand...
Click to collapse
The sojo app called my issues dumb lol. It's hard to get frustrated when humor is involved with the errors.
cstrife999 said:
The sojo app called my issues dumb lol. It's hard to get frustrated when humor is involved with the errors.
Click to expand...
Click to collapse
Looks like we may have to flash the boot.img that they are talking about in the s-off thread anybody have a guide for doing that?
I take it nobody tried deleting the nandroid.md5?
rmaccamr said:
I take it nobody tried deleting the nandroid.md5?
Click to expand...
Click to collapse
I just tried looking for where the nandroid file was. I went to my sdcard on root explorer then to clockworkmod and didn't find any of my backups there. Is there another spot that i need to look in to do that?
Aggies1288 said:
I just tried looking for where the nandroid file was. I went to my sdcard on root explorer then to clockworkmod and didn't find any of my backups there. Is there another spot that i need to look in to do that?
Click to expand...
Click to collapse
If using CWM, they will be under the /data/clockworkmod/backup directory, not /sdcard/clockworkmod/backup.
I tried the odex stock rom, but it won't flash... Anybody have this issue?
santod040 said:
If using CWM, they will be under the /data/clockworkmod/backup directory, not /sdcard/clockworkmod/backup.
Click to expand...
Click to collapse
Ok i found it it was under /data/media/clockworkmod/backup but i dont see any files inside of that that are a md5 file im going to look in the data.ext4.tar file and the system.ext4.tar.a. Does any of those ring a bell? i see the boot.img, data.ext4.tar.a, recovery.img, system.ext4.tar.a, and system.ext4.tar.b. Thats all the files inside the backup i made before i rooted.
Just wondering how i can do this?
Im having over heating problems while video calling(the phone gets so hot it shuts down) and I need to take it back for exchange. If they see super user im dead in the water.
How do I unroot and go back to stock recovery?
combatmedic870 said:
Just wondering how i can do this?
Im having over heating problems while video calling(the phone gets so hot it shuts down) and I need to take it back for exchange. If they see super user im dead in the water.
How do I unroot and go back to stock recovery?
Click to expand...
Click to collapse
Just delete the super user app. There should be an unroot option in there somewhere. You shouldn't need to worry about the recovery. But I believe there is a stock recovery in the non carrier branded forum
Sent from my iPad using Tapatalk
Cuppeerr said:
Just delete the super user app. There should be an unroot option in there somewhere. You shouldn't need to worry about the recovery. But I believe there is a stock recovery in the non carrier branded forum
Sent from my iPad using Tapatalk
Click to expand...
Click to collapse
It just comes right back at start up. I tried a couple of times
combatmedic870 said:
It just comes right back at start up. I tried a couple of times
Click to expand...
Click to collapse
You could download this rom and once it's done downloading open the .zip up and delete Superuser.apk from either /system/app or Data/app. Then when you boot up it should look normal enough. After that you could just flash a stock recovery
IMO that's your best option since I haven't seen a ruu yet.
Cuppeerr said:
You could download this rom and once it's done downloading open the .zip up and delete Superuser.apk from either /system/app or Data/app. Then when you boot up it should look normal enough. After that you could just flash a stock recovery
IMO that's your best option since I haven't seen a ruu yet.
Click to expand...
Click to collapse
Great idea!
combatmedic870 said:
Great idea!
Click to expand...
Click to collapse
was the unrooting and trade in successful??????
psyman42 said:
was the unrooting and trade in successful??????
Click to expand...
Click to collapse
nope
combatmedic870 said:
nope
Click to expand...
Click to collapse
What happened?
DinoSoup said:
What happened?
Click to expand...
Click to collapse
I was charged 145 for sending back a dev unlocked device. They didnt ask, they just charged.
Please Help me Dudes
Yo
I have a quick question for the administrators. I was on Cyanogenmod with TWRP Recovery on my Htc one M8, i did everything stock (installed 2.22.401.4 odexx stock rom, with stock recovery, relocked the bootloader and turner S-ON) Now i have OTA update and when i click install now it shows red triangle and the update fails. When i go into recovery it shows something like 2.22.401.4 "something is wrong or missing something-i dont like to go into recovery to see again but i think you know this issue ) Can you please tell me what to do guys i dont want to sell my htc m8 and i want to get the OTA's in the future without any problem. Btw my phone is bought from T-Mobile Macedonia, where i wondered is this t-mobile RUU for all countries T-Mobile devices or just US?
I will be very grateful for your answers dudes.
Thank you in advance.