Okay so I have a question I'm rooted on my gf shift 2.3.4 with S-on with clockworks do I need to downgrade to 2.2 or anything to flash any Rom here ??
Sent from my SPH-D700 using xda app-developers app
ivcesar said:
Okay so I have a question I'm rooted on my gf shift 2.3.4 with S-on with clockworks do I need to downgrade to 2.2 or anything to flash any Rom here ??
Sent from my SPH-D700 using xda app-developers app
Click to expand...
Click to collapse
It will make things a lot simpler for you if you are Fully Rooted ( S-Off ) . You can Flash Roms with S-On, but it is a bit more involved. Because you cannot flash any Kernels. Being that most Roms have custom Kernels it creates a bit of an issue. It can be done, it just means you are going to have to modify any Rom that has a Custom Kernel before you try and flash it. You were using THIS THREAD correct? I would recommend finishing the Downgrade process to 2.2 in order to achieve Full Root. It will make life much easier in the long run.
+1!
Sent from my PG06100 using xda premium
prboy1969 said:
It will make things a lot simpler for you if you are Fully Rooted ( S-Off ) . You can Flash Roms with S-On, but it is a bit more involved. Because you cannot flash any Kernels. Being that most Roms have custom Kernels it creates a bit of an issue. It can be done, it just means you are going to have to modify any Rom that has a Custom Kernel before you try and flash it. You were using THIS THREAD correct? I would recommend finishing the Downgrade process to 2.2 in order to achieve Full Root. It will make life much easier in the long run.
Click to expand...
Click to collapse
Thank you for taking your time an swering my questions its my first htc phone trying to root so I'm all lost an all over the place haha well to answer your question yes I'm stuck between 15 an step 18. I wasn't sure how flash misc.img file from adb or phone I was a little lost their
Sent from my SPH-D700 using xda app-developers app
ivcesar said:
Thank you for taking your time an swering my questions its my first htc phone trying to root so I'm all lost an all over the place haha well to answer your question yes I'm stuck between 15 an step 18. I wasn't sure how flash misc.img file from adb or phone I was a little lost their
Sent from my SPH-D700 using xda app-developers app
Click to expand...
Click to collapse
Make sure the misc.img is on the Root of your SD Card. Also the PG06IMG.zip from the OP. You can Copy and Paste. Or push them there with ADB. I use the Copy and Paste method. Since it sounds like your a little lost on the exact commands, I'll give them to you to do using Terminal Emulator as per the Guide.
Open Terminal Emulator.
Type: su
Hit Enter
Type: dd if=/sdcard/misc.img of=/dev/block/mmcblk0p17
Hit Enter
After that just go to Step #18 of the Guide, and follow the rest of the Instructions. Before you do anything I would suggest that you Reread instructions, and Re-watch the Videos. Just for your own peace of mind . Personally though I would probably if it were me start the Entire process over. RUU back to 2.3.4 and just redo the entire process. But that's just me .
prboy1969 said:
Make sure the misc.img is on the Root of your SD Card. Also the PG06IMG.zip from the OP. You can Copy and Paste. Or push them there with ADB. I use the Copy and Paste method. Since it sounds like your a little lost on the exact commands, I'll give them to you to do using Terminal Emulator as per the Guide.
Open Terminal Emulator.
Type: su
Hit Enter
Type: dd if=/sdcard/misc.img of=/dev/block/mmcblk0p17
Hit Enter
After that just go to Step #18 of the Guide, and follow the rest of the Instructions. Before you do anything I would suggest that you Reread instructions, and Re-watch the Videos. Just for your own peace of mind . Personally though I would probably if it were me start the Entire process over. RUU back to 2.3.4 and just redo the entire process. But that's just me .
Click to expand...
Click to collapse
Hey I just saw the reply thank you again for taking your time i figure it out i when into adb shell since i could get to do anything in terminal for nothing push with adb when to 2.2 root now in a search of a rom lol thank you for you help
Sent from my SPH-D700 using xda app-developers app
Glad you got it sorted out . I would try a few different Roms before settling on one. A few pieces of advice. One is to make sure you Flash the Rom, or Roms of your choosing correctly. Meaning do a Full Wipe, before Flashing. Also after you Flash a Rom, make sure that you give it a least a few days to settle in. That way you have a better idea of how each Rom is, before making a decision on whether you like it or not.
prboy1969 said:
Glad you got it sorted out . I would try a few different Roms before settling on one. A few pieces of advice. One is to make sure you Flash the Rom, or Roms of your choosing correctly. Meaning do a Full Wipe, before Flashing. Also after you Flash a Rom, make sure that you give it a least a few days to settle in. That way you have a better idea of how each Rom is, before making a decision on whether you like it or not.
Click to expand...
Click to collapse
So my question is... I had intentionally 'half rooted' my phone cause i wanted to stick with the stock ROM for the time being and SuperUser granted enough permissions to do some of the things i needed to do. Evervolv came out with a JB build that I wanted to try; so I have to get it to S-OFF now (which I did initially but restored it cause at the time I didn't like the ROM I flashed and ran an RUU). If I made a CWM backup of my current 2.3.4 settings, after I downgrade and root can i revert back to it if I don't like the new ROM?
Thanks
So I'm not sure I follow you. Are you currently " S-Off " ? If you are, and made a Nandroid backup. Then yes you can revert back to the Nandroid backup at any time. But if you ran an RUU, then no you cannot Nandroid back. The Nandroid backup is still on your SD Card, but you cannot access it with the Factory Recovery.
prboy1969 said:
So I'm not sure I follow you. Are you currently " S-Off " ? If you are, and made a Nandroid backup. Then yes you can revert back to the Nandroid backup at any time. But if you ran an RUU, then no you cannot Nandroid back. The Nandroid backup is still on your SD Card, but you cannot access it with the Factory Recovery.
Click to expand...
Click to collapse
Ok, sorry. I rooted it and got s-off when I first got my shift but decided to go back stock via RUU. few weeks later i went back and followed Vicodan's post only halfway to get root when I needed it via SuperUser. So I do have CWM installed and my backups work (I found out when the ROMS i been trying to load won't even boot and restoring from backups work fine). Thanks for clarifying that for me, here I come Evervolv
Just curious as to why you do not want Full Root ? Also if your still " S-On " trying to flash Roms can become a PIA . Reason being, most Roms have custom kernels. Which if you are not Full Root " S-Off " becomes an issue.
To flash any ROM while s-on unlocked you will need to use fastboot for the kernel. So have adb and fastboot setup and drag the boot.img from the ROM your flashing into your fastboot folder. Boot into recovery and do a full wipe as always and flash the ROM, Once the ROM is flashed plug the phone in and open a command prompt, cd to your platform-tools folder and type adb reboot bootloader, once it reboots into bootloader make sure it says fastboot usb in red. If it don't choose fastboot, then use this command fastboot flash boot boot.img and once it says it's done reboot to enjoy the custom ROM/KERNEL combo
Sent from my myTouch_4G_Slide using Tapatalk 2
strapped365 said:
To flash any ROM while s-on unlocked you will need to use fastboot for the kernel. So have adb and fastboot setup and drag the boot.img from the ROM your flashing into your fastboot folder. Boot into recovery and do a full wipe as always and flash the ROM, Once the ROM is flashed plug the phone in and open a command prompt, cd to your platform-tools folder and type adb reboot bootloader, once it reboots into bootloader make sure it says fastboot usb in red. If it don't choose fastboot, then use this command fastboot flash boot boot.img and once it says it's done reboot to enjoy the custom ROM/KERNEL combo
Sent from my myTouch_4G_Slide using Tapatalk 2
Click to expand...
Click to collapse
Yes Sir that's what he'd have to do every time he flashed a Rom with a custom kernel. Like I said, more involved than the way you would normally Flash a Rom . It's easier to be Fully Rooted, if your able to be IMO.
TEAM MiK
MikROMs Since 3/13/11
prboy1969 said:
Yes Sir that's what he'd have to do every time he flashed a Rom with a custom kernel. Like I said, more involved than the way you would normally Flash a Rom . It's easier to be Fully Rooted, if your able to be IMO.
TEAM MiK
MikROMs Since 3/13/11
Click to expand...
Click to collapse
Oh definitely, because if he wanted to test a kernel he would have to flash the new kernel in recovery so the modules for wifi/wimax are placed correctly then go into fastboot to flash the boot.img and that is just way to damn much work.
The advantages to s-off are endless IMHO
Sent from my myTouch_4G_Slide using Tapatalk 2
He'll yes to much work. Not mention you don't really gain anything by not having Full Root " S-Off " . In almost every case it makes things more difficult
TEAM MiK
MikROMs Since 3/13/11
prboy1969 said:
Just curious as to why you do not want Full Root ? Also if your still " S-On " trying to flash Roms can become a PIA . Reason being, most Roms have custom kernels. Which if you are not Full Root " S-Off " becomes an issue.
Click to expand...
Click to collapse
After going s-off and trying some roms initially, I reverted back and for a while I liked the stock 2.3.4, so I just rolled with that and was content with not having full root (the few things i wanted to tweak, superuser could do). Seeing now that there is finally a somewhat usable ICS build (4g is a non issue since I live in a fringe area anyways) I tried to load it to no avail. So it was time to be full s-off again :laugh:
Anyhow, I got s-off quickly and now running a new ROM :good:
Good to hear . I'm a big advocate of being Full Rooted " S-Off " on any Android device. Even if your running the Stock Rooted Rom. Which BTW since you said you liked it, did you see THIS thread. It's the latest OTA Stock Rooted.
prboy1969 said:
Good to hear . I'm a big advocate of being Full Rooted " S-Off " on any Android device. Even if your running the Stock Rooted Rom. Which BTW since you said you liked it, did you see THIS thread. It's the latest OTA Stock Rooted.
Click to expand...
Click to collapse
Thanks - I wanted to get away from GB for the time being and try the new ICS/JB stuff but I'll keep this one just in case
Related
Alright, so I got this phone a week ago. First off, I am loving it. Screw Apple.
Anyway, first thing I wanted to do was root it so I can debloat all of T-Mobile's poop applications they cram inside of it.
I've read places that HBOOT 1.45.0013 isn't rootable. I've read it IS rootable, but only with S-OFF on a previous HBOOT. And I've read that it is rootable, but you can't get S-OFF after root.
I've used HTC's unlock tool, which went successful because I flashed CWM through fastboot. I've tried HTC Supertool, MrRoot, and Revolutionary (which says it isn't compatible)
My question then is, which of the above statements is true? If it is rootable, I don't care about S-OFF too much. But I can't ever find a guide that tells me how to root it with this current HBOOT.
Halp pl0x? <3
If you download the Superuser zip (just google superuser android or something), you can flash it in recovery to get root. Alternatively, download a ROM with root preloaded (DS-mod is essentially stock with root and a few other standard root things added in) and flash it.
Limewirelord said:
If you download the Superuser zip (just google superuser android or something), you can flash it in recovery to get root. Alternatively, download a ROM with root preloaded (DS-mod is essentially stock with root and a few other standard root things added in) and flash it.
Click to expand...
Click to collapse
What's the difference in flashing Superuser, and downloading it from the Market?
Sent from my myTouch_4G_Slide using xda premium
It won't install correctly if you do it while the system is on and live (through the market) you have to do it while the operating system is not running (through clockworkmod)
Afterwards, it's fine to update through the market, but the initial install will fail if done on a running version of Android.
Blue6IX said:
It won't install correctly if you do it while the system is on and live (through the market) you have to do it while the operating system is not running (through clockworkmod)
Afterwards, it's fine to update through the market, but the initial install will fail if done on a running version of Android.
Click to expand...
Click to collapse
..Huh, just flashed Superuser. Weird that it's that easy. All the other threads were like "omg HBOOT 1.45.0013 can't be rooted hnnnnnggg"
So, now onto ROMs, are there any ICS based ones you reccomend?
Btw I see tht your question has been answered but in Mr Root's next update will include a Rooter/Unrooter for the newest H-Boot (Without S-Off)
MewTech said:
..Huh, just flashed Superuser. Weird that it's that easy. All the other threads were like "omg HBOOT 1.45.0013 can't be rooted hnnnnnggg"
So, now onto ROMs, are there any ICS based ones you reccomend?
Click to expand...
Click to collapse
For a while it was so - you couldn't do anything with 1.45.0013, HTC broke the OTA so you couldn't unlock it.
In my quest for s-on to s-off (still ongoing) I found a leaked copy of the OTA as a signed HTC package so now we can actually unlock them, and people can work with them and they are now rootable.
Still stuck with s-on though, which is unfortunate - we're working on it and hopefully can crack it soon. Got some leads we're chasing down, each layer we unravel shows us another that has to be solved below it.
ICS? Dunno - i'm not interested in ICS yet, still trying to learn gingerbread through and through (i'm an android newbie) before moving up to ICS. That's on hold right now because of the s-on issue i'm working on. tbalden has been leading the charge on ICS and I would recommend looking into his works if that is your interest.
Limewirelord said:
If you download the Superuser zip (just google superuser android or something), you can flash it in recovery to get root. Alternatively, download a ROM with root preloaded (DS-mod is essentially stock with root and a few other standard root things added in) and flash it.
Click to expand...
Click to collapse
can you explain in detail how to flash it to rom?????
Using CWM to flash it, you will need the super user ZIP file. Find it somewhere (it's everywhere, no doubt) and put it on your SD card. Reboot the phone to recovery mode, and using CWM recovery, select "flash any zip from SD card" (I'd look up the exact wording, except that my phone has been running a solid 24 days without reboot and I really wanna see how long it goes). Navigate to where your super user ZIP file is, and select it. Follow prompts, et voila, root on reboot.
Assuming all works. If something didn't work, you messed up. Try again from step 1, make sure you have a zip file and not an APK file, make sure you select the correct "flash zip" option (there are two, one specifically for update.zip and another for whatever zip you choose).
HIH
ok this is my huge problem i have the same hboot with s-on
i have the full stock stupid t-mobile mt4gs AOS 2.3.4 software# 1.55.531.3 and i DONT have CWM or any of the extras in only thing i succeeded is getting the bootloader unlocked so what should i do?
Install clockworkmod then flash either superuser pr a ROM - if staying stocl with root, be a good time to do some spring cleaning on all the junk it comes with pre-installed.
Blue6IX said:
Install clockworkmod then flash either superuser pr a ROM - if staying stocl with root, be a good time to do some spring cleaning on all the junk it comes with pre-installed.
Click to expand...
Click to collapse
ok i download this now i try flash CWM recovery and i get this
an error occurred while attempting to run privileged commands!
??????
what do i do next??
We love to title our posts here
crimedave1987 said:
ok i download this now i try flash CWM recovery and i get this
an error occurred while attempting to run privileged commands!
??????
what do i do next??
Click to expand...
Click to collapse
Well,
What exactly did you do that returned this error (mainly because I don't remember if fastboot or adb returns that)? What tutorial/guide were you following? Were you in adb trying to "dd" the CWM recovery image or were you trying to flash an img file from within fastboot? Either way, what was the exact command you typed?
Your other thread (sorry, didn't realize I had replied to you in two different places) received an answer as well. After looking around to get the info you need for this post, I see now you've posted in quite a few threads to which I'm subscribed (guess I just never noticed the name, sorry).
So I see you have an unlocked bootloader. At this point, yes, flash CWM. Blue6ix gave an excellent post on how to do this. Is this the one you are currently trying to follow in order to install CWM?
tried to use superuser
I tried to load the superuser zip file in recovery with cwm. installation aborted. any suggestions? I have mytouch4gslide with s on unlocked with HBoot 1.45.0013
wesomatic said:
I tried to load the superuser zip file in recovery with cwm. installation aborted. any suggestion? I have mytouch4g with s on unlocked with HBoot 1.45.0013
Click to expand...
Click to collapse
From my earlier post:
cj chitwood said:
Using CWM to flash it, you will need the super user ZIP file. Find it somewhere (it's everywhere, no doubt) and put it on your SD card. Reboot the phone to recovery mode, and using CWM recovery, select "flash any zip from SD Card”. Navigate to where your super user ZIP file is, and select it. Follow prompts, et voila, root on reboot.
Assuming all works. If something didn't work, you messed up. Try again from step 1, make sure you have a zip file and not an APK file, make sure you select the correct "flash zip" option (there are two, one specifically for update.zip and another for whatever zip you choose).
HIH
Click to expand...
Click to collapse
Did this help? Only things I can think of are (1) using ”flash update.zip” instead of ”flash [any] zip file” or, less likely, (2) trying to flash an apk instead of a zip.
--
Sent from my Android ”phone”:
HTC DoubleShot /T-Mobile MyTouch 4G Slide running Bulletproof
Yes, that thread did help me. I used your instructions. I even have a new sd card. I have read some threads about formating it first. I did not do that. Also where can I get a good zip file? I down loaded it from some file sharing program 2share I think... Tried again ROOTED!!!! It was so easy!!! Been doing this for a week!!! Wow!!!!!!!!!!!!!!!!!!!
bricked my phone!!!
Just want to add... Do not use ROM Manager from The Market. Bricked my phone. Just stays in start up. Had it rooted and everything!!!!
NO BRICK
Thank God For CWM!!!!!
I am stuck someplace in betweem
Hi:
I too have a MyTouch Slidwe 4G with the hboot 1.45.0013. All the contrary information I have found lead me to go to the professionals. I purchased the root-android.org software. It seemed to run fine - I got no errors and it said that the phone was rooted. I see the superuser app on the phone. However, when I try to run Titanium Backup, it says that the phone is not rooted. The people at root-android.org are not answering my emails (I did get my money back). Any ideas of where I should go from here?
Thanks!
You should never have to purchase root for any android, if it has been done once then chances are it is plastered how to all over the internet, if the phone has a thread on xda then it will be there. Being you got yourself this far I'll help you out a bit more
http://forum.xda-developers.com/showthread.php?p=29439712
Read and understand is my advice, always read until you understand, then search if you have questions, then finally ask questions here if you are still stumped.
For the most part every question you can ask is already answered by one of the super helpful xda folk here, and chances are it is the right information.
I do advice to gain radio soff with the wire trick, it will make life easier... Read up and happy flashing!
Sent from my Nexus 7 using xda premium
Apologies in advance if this is the wrong forum.
Today I successfully perm rooted my Doubleshot...
Then I tried to flash CM9 Alpha 5 using CW recovery.. downloaded the .zip...
Flashed it.. hit reboot... and it wont get past the mytouch splash screen.
I've tried flashing other roms, and other alphas.. but they all don't reboot into the rom.
I can still boot into recovery and get into ClockWork..
Any ideas on what I can flash or do to at least get any rom running on here... I'm not even picky at this point... I just wanted something like CM7 or some AOSP.
Thanks in advance.
sinistersai4d4d said:
Apologies in advance if this is the wrong forum.
Today I successfully perm rooted my Doubleshot...
Then I tried to flash CM9 Alpha 5 using CW recovery.. downloaded the .zip...
Flashed it.. hit reboot... and it wont get past the mytouch splash screen.
I've tried flashing other roms, and other alphas.. but they all don't reboot into the rom.
I can still boot into recovery and get into ClockWork..
Any ideas on what I can flash or do to at least get any rom running on here... I'm not even picky at this point... I just wanted something like CM7 or some AOSP.
Thanks in advance.
Click to expand...
Click to collapse
when you say perm root you mean s-off right?
im assuming he's s on....remember to take the boot.img out of the cm9 zip and flash it using fastboot. You can find out more info on how to do it here. Also apology accepted (this should be in general)
Over 500 posts and people still don't know what threads to post questions in...
Thread reported
Yes, perm root using the root tool. I believe that's S-off... but I'm not certain.
sinistersai4d4d said:
Yes, perm root using the root tool. I believe that's S-off... but I'm not certain.
Click to expand...
Click to collapse
its not s-off, go here to get s-off
http://forum.xda-developers.com/showthread.php?t=1576672
my HTC MyTouch 4G Slide using Tapatalk 2
gtmaster303 said:
Over 500 posts and people still don't know what threads to post questions in...
Thread reported
Click to expand...
Click to collapse
Badass
Sent from my myTouch_4G_Slide using xda premium
Let me take advantage of this newb. I got my new device, S-On Unlocked. I restored my modded version of stock and using blues UV 5% kernel. Wifi wont work, and my camera has weird lines on it. But the pics are still good. I just needa fastboot the boot.img righ'?
sinistersai4d4d said:
Apologies in advance if this is the wrong forum.
Today I successfully perm rooted my Doubleshot...
Then I tried to flash CM9 Alpha 5 using CW recovery.. downloaded the .zip...
Flashed it.. hit reboot... and it wont get past the mytouch splash screen.
I've tried flashing other roms, and other alphas.. but they all don't reboot into the rom.
I can still boot into recovery and get into ClockWork..
Any ideas on what I can flash or do to at least get any rom running on here... I'm not even picky at this point... I just wanted something like CM7 or some AOSP.
Thanks in advance.
Click to expand...
Click to collapse
1) This goes in General. I don't know why the mods can't just add a Q&A board to remove the n00b confusion.
2) Fastboot the ROM's boot.img before booting up.
blackknightavalon said:
1) This goes in General. I don't know why the mods just don't add a Q&A board to remove the n00b confusion.
2) Fastboot the ROM's boot.img before booting up.
Click to expand...
Click to collapse
Ok, I'm def S-ON but unlocked and nperm rooted.
Can someone walk me through what to do? How can I fastboot the rom's boot.img?
I'm sorry I'm new to this, that's why I'm using my secondary device to learn. I've been googling anything I can find and it got me to through the root process but now I'm stuck.
xmc wildchild22 said:
im assuming he's s on....remember to take the boot.img out of the cm9 zip and flash it using fastboot. You can find out more info on how to do it here. Also apology accepted (this should be in general)
Click to expand...
Click to collapse
This something I have to do with a PC (as opposed to Mac)? No way to unbrick this thing without methods like this? Just asking, before I try and commandeer a pc.
sinistersai4d4d said:
This something I have to do with a PC (as opposed to Mac)? No way to unbrick this thing without methods like this? Just asking, before I try and commandeer a pc.
Click to expand...
Click to collapse
Did you not read the stickies?
You have to take the bootimage from the rom that you are using and put in a folder and name it so you can reconize it. You follow the command prompt instructions they give in this thread. You have to have some knowlege of a PC in order to be successful. I had the same problems as you did. You can get it to work... Do you know how to use the command prompt for your PC?
Sent from my SGH-T959V using Tapatalk 2
wesomatic said:
You have to take the bootimage from the rom that you are using and put in a folder and name it so you can reconize it. You follow the command prompt instructions they give in this thread. You have to have some knowlege of a PC in order to be successful. I had the same problems as you did. You can get it to work... Do you know how to use the command prompt for your PC?
Click to expand...
Click to collapse
Not really. But I guess I'll start there...
And thanks for everyone's help. Here goes nothing.
sinistersai4d4d said:
Not really. But I guess I'll start there...
And thanks for everyone's help. Here goes nothing.
Click to expand...
Click to collapse
You can just flash back to stock to fix it. Learn to fastboot, then run CM9.
Sent from my Galaxy Nexus using Tapatalk 2
AgentCherryColla said:
You can just flash back to stock to fix it. Learn to fastboot, then run CM9.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Thanks again for all your help...
Last question before I fastboot, is it necessary to have the SDK or ADB to fastboot? Can I fastboot/flash the kernel using Hasoon's all-in-one-kit (the app I used to attain root)? Or is it too late since now the device wont boot and Hasoon "can't find the device"?
I have the boot.img I want in a place where I can locate it. Can I use the command prompt without the SDK/ADB?
Interestingly enough I was able to mount using recovery, and boot a new kernal... phone won't boot but at least it's stuck at a different splash screen lol "mikroms"..
I'm calling this progress.
*UPDATE*
Ok, got it!
I mounted the phone to my computer using recovery and used the Hasoon kit to flash the CM boot image.. then I rebooted and got the mikroms splash screen. That was because the last zip i flashed wasn't CM.. it was the MikRom..
so I went back into recovery, flashed CM.. now I'm good!
sinistersai4d4d said:
Thanks again for all your help...
Last question before I fastboot, is it necessary to have the SDK or ADB to fastboot? Can I fastboot/flash the kernel using Hasoon's all-in-one-kit (the app I used to attain root)? Or is it too late since now the device wont boot and Hasoon "can't find the device"?
I have the boot.img I want in a place where I can locate it. Can I use the command prompt without the SDK/ADB?
Click to expand...
Click to collapse
Of course not. 'Fastboot' is an 'ADB' command. BUT if Hasoon's tool 'can't find device'....that's an ADB error message and you probably don't have all the drivers installed that you need but he has the necessary files included for what you need for 'Unlocked" & recovering from a mess-up. You may as well go ahead & install ADB tho....you'll eventually need it.
---------- Post added at 10:12 AM ---------- Previous post was at 09:59 AM ----------
sinistersai4d4d said:
Interestingly enough I was able to mount using recovery, and boot a new kernal... phone won't boot but at least it's stuck at a different splash screen lol "mikroms"..
I'm calling this progress.
Ok, got it!
I mounted the phone to my computer using recovery and used the Hasoon kit to flash the CM boot image.. then I rebooted and got the mikroms splash screen. That was because the last zip i flashed wasn't CM.. it was the MikRom..
so I went back into recovery, flashed CM.. now I'm good!
Click to expand...
Click to collapse
I believe what you did is 'Flash' a ROM from MikROMs but the kernel didn't go because you have S-On. Take that same '.zip' you just flashed, look inside it and put the file named 'boot.img' where you can find it in the windows 'path' and THEN
'fastboot flash boot boot.img' http://forum.xda-developers.com/showthread.php?t=1508556
You should boot up fine then.
I am currently running Jelly Bean AOKP, but it's a bit crashy. I have a couple favorite apps that I wish would work again. Am I correct in understanding that the RUU is the factory ROM?
Yup, factory Rom. It's actually a program that runs on your pc that flashes the factory Rom. Make sure you dont use a newer one since it also flashes hboot.
Sent from my HTC One XL using xda app-developers app
How far back would one need to go to avoid flashing hboot?
hcricket said:
How far back would one need to go to avoid flashing hboot?
Click to expand...
Click to collapse
2.20 contains the new hboot. If you run it, you can no longer flash radios to your phone and you have to flash boot.img manually (which means no flashing phone back ups on the go to switch ROMs). Just go with the 1.85 RUU. Doesn't matter if you are going to root/rom anyway. Side Note, if your phone already has the 2.20 hboot, do not run the 1.85 RUU!
Btw, why are you running an RUU anyway if I may ask?
If away from a pc, I'm guessing you could actually use terminal emulator and dd the boot.IMG corresponding to the Rom or backup you want to flash, reboot recovery, flash Rom/backup then reboot...I'm unrooted so I can't confirm, but would be a fun test confirm if it works or not
18th.abn said:
If away from a pc, I'm guessing you could actually use terminal emulator and dd the boot.IMG corresponding to the Rom or backup you want to flash, reboot recovery, flash Rom/backup then reboot...I'm unrooted so I can't confirm, but would be a fun test confirm if it works or not
Click to expand...
Click to collapse
Don't you have to use clockwork to flash image from terminal emulator?
Edit: I guess that's only if I want the easy way with "flash_image"
RUU will not run when bootloader is unlocked. So remember to relock the bootloader before running the RUU.
Also RUU = ROM update utility
Butters619 said:
Don't you have to use clockwork to flash image from terminal emulator?
Edit: I guess that's only if I want the easy way with "flash_image"
Click to expand...
Click to collapse
Terminal emulator is ran from android as an app. It's a linux terminal to use a shell command to dd the .img to the proper partition.......I would actually love to see somebody test to ser if it sticks or not. If it did we could write a simple script that people could use so they could easily flash on the go without needing a pc to fastboot flash the image
You could always just flash a stock rom, like this one: http://forum.xda-developers.com/showthread.php?t=1872842. It is way easier than ruu-ing and you don't risk losing root
Thank you everyone for the replies. I ended up flashing CleanRom 4.5 and all is well. The RUU stuff looks like perhaps a bit more than I'm prepared for.
18th.abn said:
Terminal emulator is ran from android as an app. It's a linux terminal to use a shell command to dd the .img to the proper partition.......I would actually love to see somebody test to ser if it sticks or not. If it did we could write a simple script that people could use so they could easily flash on the go without needing a pc to fastboot flash the image
Click to expand...
Click to collapse
Do you happen to know what partition the boot.img is in?
I know it. Going to try this now. Wish me luck!!
Awesome...make sure you do rom change from aosp based to sense or vice versa. That way you know the boot.imgs are not compatible and you don't get a false result that the boot.img sticks thanks for testing it out
Sent from my SCH-R720 using xda premium
18th.abn said:
Awesome...make sure you do rom change from aosp based to sense or vice versa. That way you know the boot.imgs are not compatible and you don't get a false result that the boot.img sticks thanks for testing it out
Sent from my SCH-R720 using xda premium
Click to expand...
Click to collapse
Awwwww yeah. It worked. Going to try one more time to make sure
Hello Everyone,
As of today, my phone received the new OTA Update for my HTC One S. However, obviously I cannot update due to my phone being rooted. As a person who is still relatively new with rooting (about a month rooted with my phone-first time), I have a couple questions.
First and foremost, have you guys enjoyed the OTA Update so far? I have read about the list of improvements, and they look promising.
Secondly, I obviously want to stay rooted, are there any suggestions about how to update and then have my phone rooted? Preferably without losing my root, but I don't think that's possible.
Thirdly, I saw a thread about the viper (I believe that's what it's called) rom and that could be my possible solution. But, I am rooted on stock rom and have never put on another rom before. So what are your thoughts on this rom?
Thanks in advance
Sent from my HTC VLE_U using xda app-developers app
Problem Fixed
DrOfLife said:
Hello Everyone,
As of today, my phone received the new OTA Update for my HTC One S. However, obviously I cannot update due to my phone being rooted. As a person who is still relatively new with rooting (about a month rooted with my phone-first time), I have a couple questions.
First and foremost, have you guys enjoyed the OTA Update so far? I have read about the list of improvements, and they look promising.
Secondly, I obviously want to stay rooted, are there any suggestions about how to update and then have my phone rooted? Preferably without losing my root, but I don't think that's possible.
Thirdly, I saw a thread about the viper (I believe that's what it's called) rom and that could be my possible solution. But, I am rooted on stock rom and have never put on another rom before. So what are your thoughts on this rom?
Thanks in advance
Sent from my HTC VLE_U using xda app-developers app
Click to expand...
Click to collapse
Hey Dr.
I had the same issue and fixed it. I'm enjoying the OTA update...seems snappier and the option to change the menu button and get rid of that eyesore at the bottom of the screen is great....See this post on how to fix it:
http://forum.xda-developers.com/showthread.php?p=32069130
All you have to do is download the stock recovery (link located in the post above), rename it "Recovery.IMG" and put it in the /Data/Recoveries folder that your All In One Kit uses. Then open up the All In One root kit, flash the stock recovery, and reboot your phone. It should look the same, and give you the same notification that an update is available. Install the update, and then reflash your TWRP or CWM and reroot (the OTA unroots the device, so you need to reinstall SuperSu.
Thanks to all the people that have helped me do the same!!!
fsustrength said:
Hey Dr.
I had the same issue and fixed it. I'm enjoying the OTA update...seems snappier and the option to change the menu button and get rid of that eyesore at the bottom of the screen is great....See this post on how to fix it:
http://forum.xda-developers.com/showthread.php?p=32069130
All you have to do is download the stock recovery (link located in the post above), rename it "Recovery.IMG" and put it in the /Data/Recoveries folder that your All In One Kit uses. Then open up the All In One root kit, flash the stock recovery, and reboot your phone. It should look the same, and give you the same notification that an update is available. Install the update, and then reflash your TWRP or CWM and reroot (the OTA unroots the device, so you need to reinstall SuperSu.
Thanks to all the people that have helped me do the same!!!
Click to expand...
Click to collapse
I keep flashing the stock recovery with all-in-one and then downloading and installing the update. Everytime, about halfway it goes back to the red triangle with the exclamation point and restarts the phone five minutes later.
I check software and its still 4.0.3 and the update redownloads. I've tried several "stock recoveries" and the update afterwards... never works.
TheAdictsPunk said:
I keep flashing the stock recovery with all-in-one and then downloading and installing the update. Everytime, about halfway it goes back to the red triangle with the exclamation point and restarts the phone five minutes later.
I check software and its still 4.0.3 and the update redownloads. I've tried several "stock recoveries" and the update afterwards... never works.
Click to expand...
Click to collapse
I have also tried the steps and have run into the same problem. All is well when I flash into recovery, but when the phone starts updating about quarter or half-way through it also gives me the same red error message and the phone restarts soon after with no update. I have tried several times with the same problem.
However, thanks fsustrength for the instructions, before I was getting no where, but now I almost got it
Sent from my HTC VLE_U using xda app-developers app
ckpv5 said:
As there are many questions on how to do OTA update & to revert to stock after a device is rooted and bootloader unlocked; I made this simple guide which I hope will help the newbies especially.
NOTE : always do a backup and a nandroid backup before trying any of these.
OTA update:
A) ROM is stock, bootloader unlocked, stock recovery and not rooted.
- just run the OTA update, there is no need to relock the bootloader
B) ROM is stock, bootloader unlocked, CWM recovery and not rooted.
- flash the stock recovery that comes with your RUU, extract the RUU for the stock recovery.
* boot to bootloader
* fastboot flash recovery recovery_signed.img
* fastboot reboot-bootloader
* fastboot erase cache
* fastboot reboot
- run the OTA update
C) ROM is stock, bootloader unlocked, stock recovery and rooted
- download OTA Rootkeeper from Play Store
- run the OTA Rootkeeper and click protect root
- run the OTA update, there is no need to relock bootloader
- Once done, run OTA Rootkeeper and click restore root
D) ROM is stock, bootloader unlocked, CWM recovery and rooted
- download OTA Rootkeeper from Play Store
- run the OTA Rootkeeper and click protect root
- no need to relock bootloader
- boot to bootloader and fastboot flash the stock recovery
- run the OTA update
- Once done, run OTA Rootkeeper and click restore root
E) ROM is custom, bootloader unlocked, CWM recovery and rooted and you have a stock nandroid backup
- flash the stock boot.img if after nandroid restore, you have a bootloop
- flash the stock recovery.img
- relock the bootloader - fastboot oem lock
- boot your device and run the OTA update
F) ROM is custom, bootloader unlocked, CWM recovery and rooted and you don't have a stock nandroid backup
- if you dont have the stock nandroid backup, you need to run RUU
- before you can run the RUU you need to:
* flash the stock recovery.img
* flash the stock boot.img (maybe no need)
* relock the bootloader - fastboot oem lock
* run RUU
- run device setup
- run the OTA update
Flashing RUU to revert to stock or to update your One V after you have a custom ROM installed.
- you must have the correct RUU for your device.
- if you are not sure, download CID Getter from Play Store and run it, it will show your CID.
- with your CID, you may be able to find a correct RUU for your device
then (even though some people may not agree with this, but this will bring no harm and it is noob-proof) do this:
1- flash a stock recovery.img
fastboot flash recovery recovery_signed.img
fastboot reboot-bootloader
fastboot erase cache
2- flash a stock boot.img
fastboot flash boot boot_signed.img
fastboot reboot-bootloader
fastboot erase cache
3- re-lock bootloader
fastboot oem lock
fastboot reboot-bootloader
fastboot erase cache
4- flash RUU
Note : for people with ERROR 155 UNKNOWN ERROR they need to go into HBOOT and select FASTBOOT and run the RUU to revert to stock (thanks Lloir)
And usually:
Error 155 - usually wrong recovery.img /wrong boot.img
Error 140 - wrong bootloader / bootloader unlocked
Error 131 - wrong RUU for your device
Credit to all XDA members that posted all the guides in various forum thread and some from own experience which I compiled here for easy reference.
Click to expand...
Click to collapse
Some wonderful person wrote a guide for the One V. Every though it's not the same phone the rules are the same. If these instructions help you click the link and thank the guy for writing it.
http://forum.xda-developers.com/showpost.php?p=27288357&postcount=1
Wow, that is a very useful guide right there! However, while reading the guide, Step D is exactly what both TheAdictsPunk and I seem to have done (I'm making an assumption that he did). I did in fact have and used the root keeper app, put it on temporary unroot, and flashed the stock rom and ran the update. Yet, I still run into the problem of the red error sign. I'm sure there is a factor that maybe could cause it to stop, but I cannot put a finger on it.
However, I did notice something while following the procedures of the guide on my phone. When I flash the stock rom on my phone, I have to re-download the system update. While downloading the system update I notice that some of my apps get root permissions from SuperSu in the background, even though in root keeper I temporarily took off root. Rootkeeper also states that my phone is unrooted. Could this problem cause the red error message? If so, any way to fix it?
Sent from my HTC VLE_U using xda app-developers app
DrOfLife said:
Wow, that is a very useful guide right there! However, while reading the guide, Step D is exactly what both TheAdictsPunk and I seem to have done (I'm making an assumption that he did).
Sent from my HTC VLE_U using xda app-developers app
Click to expand...
Click to collapse
I did! Last night I even tried flashing the recovery image through fastboot instead of the all-in-one kit. Then, even, the recovery image wouldn't flash all the way through... maybe our phones are having a problem with the recovery being reflashed and not the update at all.
I had the same exact issue. I finally got fed up and just flashed the RUU with my computer and then just used the All-in-one program to re-root. I am now enjoying 2.31 and really glad I updated. Obviously the RUU wipes everything, but I had done a full backup using Titanium Backup, and then restored all the important settings and data (like accounts, wifi list, bookmarks, dictionary, etc.) (but not the system apps themselves! ) and it worked out pretty well. Still had some things to adjust, like sounds and such. If you want to keep your SMS's use the built-in backup in the messaging app, then restore after the update.. more reliable than any other app I've tried.
mmceorange said:
I had the same exact issue. I finally got fed up and just flashed the RUU with my computer and then just used the All-in-one program to re-root. I am now enjoying 2.31 and really glad I updated. Obviously the RUU wipes everything, but I had done a full backup using Titanium Backup, and then restored all the important settings and data (like accounts, wifi list, bookmarks, dictionary, etc.) (but not the system apps themselves! ) and it worked out pretty well. Still had some things to adjust, like sounds and such. If you want to keep your SMS's use the built-in backup in the messaging app, then restore after the update.. more reliable than any other app I've tried.
Click to expand...
Click to collapse
I'm strongly considering doing that, I can back all my contacts and apps and sms messages via Mobile Go. So, wiping my phone isn't too big of an issue for me because I can restore almost everything I need back on my phone. If you don't mind me asking, where did you get the source that you got the RUU? Also, I have never flashed an ruu before so is their a guide for our phone to flash a RUU?
Sent from my HTC VLE_U using xda app-developers app
DrOfLife said:
I'm strongly considering doing that, I can back all my contacts and apps and sms messages via Mobile Go. So, wiping my phone isn't too big of an issue for me because I can restore almost everything I need back on my phone. If you don't mind me asking, where did you get the source that you got the RUU? Also, I have never flashed an ruu before so is their a guide for our phone to flash a RUU?
Sent from my HTC VLE_U using xda app-developers app
Click to expand...
Click to collapse
http://www.lastnite.de/RUU_Ville_U_ICS_40_S_HTC_Europe_2.31.401.5.exe
Links to downloads are on that page.. just copy/paste.
Basically start your phone in fastboot, connect to usb, then run the ruu with admin privileges. Make sure you are on stock recovery, and already have the USB drivers installed on your PC (unless you're on Linux.. already has them.. and maybe Mac too?)
mmceorange said:
http://www.lastnite.de/RUU_Ville_U_ICS_40_S_HTC_Europe_2.31.401.5.exe
Links to downloads are on that page.. just copy/paste.
Basically start your phone in fastboot, connect to usb, then run the ruu with admin privileges. Make sure you are on stock recovery, and already have the USB drivers installed on your PC (unless you're on Linux.. already has them.. and maybe Mac too?)
Click to expand...
Click to collapse
Well I followed all your steps, and all was going well until I ran across RUU error 130, which states that it was using the incorrect RUU. I looked into it and I found that it was the Europe version, and I have the T-Mobile version of my phone. I'm assuming that this is the issue, am I right? Does the RUU in Europe different than the T-Mobile USA one? If so, are there any RUU's out there that cover my phone? I have searched for them with no luck..
Sent from my HTC VLE_U using xda app-developers app
DrOfLife said:
Well I followed all your steps, and all was going well until I ran across RUU error 130, which states that it was using the incorrect RUU. I looked into it and I found that it was the Europe version, and I have the T-Mobile version of my phone. I'm assuming that this is the issue, am I right? Does the RUU in Europe different than the T-Mobile USA one? If so, are there any RUU's out there that cover my phone? I have searched for them with no luck..
Click to expand...
Click to collapse
Ok I figured out a couple answers to my questions. One, the Europe version and the T-Mobile Version are different. That explains why the RUU did not work and gave me Error 130. However, the T-Mobile RUU, RUU_Ville_U_TMOUS_1.84.531.2_R2_Radio_0.16.31501S, is the alternate version that also recieves the OTA update. The RUU is found here http://androidforums.com/one-s-all-things-root/560329-ruu-download-mirrors.html
Then, following the steps, I have successfully updated my phone to the newer softeware!
But of course, I run into another problem.... The CWM recovery does not work for my phone. I flashed the recovery via the HTC One S All-in-One Toolkit. But when getting my phone into recovery mode, it "crashes." (By crashes I mean the phone will go into the htc developmental screen, then turn to black, then reload the normal bootup screen and boot normally up) So, I don't have CWM and I'm unable to root my phone again because I don't have CWM to flash SuperSu. Any thoughts on this?
Rerooting
DrOfLife said:
So, I don't have CWM and I'm unable to root my phone again because I don't have CWM to flash SuperSu. Any thoughts on this?
Click to expand...
Click to collapse
I'm still running stock 1.84, but I'm rooted and unlocked. I do not have any kind recovery like CWM or TWRP. You may have to flash a stock recovery image in order to re-install the recovery of your choice. If you want to get rooted again try this method: http://forum.xda-developers.com/showthread.php?t=1577831 It's what I used to gain root. It's a rather easy to follow guide. I used this instead of the AIO kit.
I'm going to try and revert to locked and unroot in order to get the update. Wish me luck.
DrOfLife said:
Well I followed all your steps, and all was going well until I ran across RUU error 130, which states that it was using the incorrect RUU. I looked into it and I found that it was the Europe version, and I have the T-Mobile version of my phone. I'm assuming that this is the issue, am I right? Does the RUU in Europe different than the T-Mobile USA one? If so, are there any RUU's out there that cover my phone? I have searched for them with no luck..
Sent from my HTC VLE_U using xda app-developers app
Click to expand...
Click to collapse
Oh lol sorry about that.
DrOfLife said:
Ok I figured out a couple answers to my questions. One, the Europe version and the T-Mobile Version are different. That explains why the RUU did not work and gave me Error 130. However, the T-Mobile RUU, RUU_Ville_U_TMOUS_1.84.531.2_R2_Radio_0.16.31501S, is the alternate version that also recieves the OTA update. The RUU is found here http://androidforums.com/one-s-all-things-root/560329-ruu-download-mirrors.html
Then, following the steps, I have successfully updated my phone to the newer softeware!
Click to expand...
Click to collapse
Awesome!
DrOfLife said:
But of course, I run into another problem.... The CWM recovery does not work for my phone. I flashed the recovery via the HTC One S All-in-One Toolkit. But when getting my phone into recovery mode, it "crashes." (By crashes I mean the phone will go into the htc developmental screen, then turn to black, then reload the normal bootup screen and boot normally up) So, I don't have CWM and I'm unable to root my phone again because I don't have CWM to flash SuperSu. Any thoughts on this?
Click to expand...
Click to collapse
I personally have never encountered that before, so I am of little help here. The suggestion above me sounds like the right direction though.
Red triangle error
dc211 said:
Some wonderful person wrote a guide for the One V. Every though it's not the same phone the rules are the same. If these instructions help you click the link and thank the guy for writing it.
http://forum.xda-developers.com/showpost.php?p=27288357&postcount=1
Click to expand...
Click to collapse
I'm using method C, i still get that red triangle error. Also i can't get the ruu for my phone. I'm desperate can you please help me.
lonegunman0 said:
I'm using method C, i still get that red triangle error. Also i can't get the ruu for my phone. I'm desperate can you please help me.
Click to expand...
Click to collapse
Im getting the same thing. Even after flashing "stock recovery" that i got from the modaco link, I can't update or even go into the stock recovery...I would absolutely love to enjoy the update too!
skidmarc11 said:
Im getting the same thing. Even after flashing "stock recovery" that i got from the modaco link, I can't update or even go into the stock recovery...I would absolutely love to enjoy the update too!
Click to expand...
Click to collapse
If this many people are running into this problem, maybe we can get a role call of whose using what method, if not stock ROM what custom they are using, and what carrier they us?
I'm stock ROM, Stock Recovery, and Tmobile US. I used Method C.
I'm wondering if they have changed the update in a way that is preventing some people from updating. like it detects a certain file before update or something idk. I'm not any sort of advanced android user so I am probably wrong, but it's the first thing that comes to mind. Otherwise, maybe they sent out a bad update file, but I feel like that probably wouldn't be the case since it's been happening for a couple days now.
Thought's ideas anyone, or am I alone in any of these thoughts?
Stock rom
mylegiscramped said:
If this many people are running into this problem, maybe we can get a role call of whose using what method, if not stock ROM what custom they are using, and what carrier they us?
I'm stock ROM, Stock Recovery, and Tmobile US. I used Method C.
I'm wondering if they have changed the update in a way that is preventing some people from updating. like it detects a certain file before update or something idk. I'm not any sort of advanced android user so I am probably wrong, but it's the first thing that comes to mind. Otherwise, maybe they sent out a bad update file, but I feel like that probably wouldn't be the case since it's been happening for a couple days now.
Thought's ideas anyone, or am I alone in any of these thoughts?
Click to expand...
Click to collapse
skidmarc11 said:
Im getting the same thing. Even after flashing "stock recovery" that i got from the modaco link, I can't update or even go into the stock recovery...I would absolutely love to enjoy the update too!
Click to expand...
Click to collapse
Yes i agree about the file detection. I'm running stock rom but i think i've just realised my problem. Although i have a stock rom my problem is that the stock rom i'm running is deodexed. I read somewhere that if the stock rom is tweaked in any way or if any bloatware is deleted you can't get OTA updates.
Hope this helped
Wouldn't an RUU fix any of those problems?
Yes it would
Sent from my HTC One S using xda app-developers app
Coming from a DX, the process to root / flash on the galaxy doesn't seem that much different. Although, there seems to be greater risk for issues around imei information, etc....
So, I've read about everything I can on the forums, trying to make sure I understand all of the ins and outs and I'm starting to feel pretty comfortable with the process, however I would like someone to just confirm that i've got everything correct......
Based on this guide ( [GUIDE][VZW Edition]How to root your Galaxy SIII & More!(ROMs/CWM/Stock)) , this is how I understand things if somone could either comfirm or correct my information I would greatly appreciate it!
1. using section 2 in the guide for windows users, I use the RootDebugFS bat file to root the phone.
2. After rooting, and prior to unlocking the boot loader, I backup my IMEI using Comprehensive IMEI/EFS Backup method listed in the guide.
3. From here I can unlock the bootloader and install CWM reovery.
4. At this point, back in the droid X world I would take a back up of my system so I have a semi - stock image to go back to.
5. Now I can download any of the different custom roms listed and follow the instructions in the OP to flash that rom.
Going back to stock.
1. Should I need to go back to Stock, I would just use the ODIN tool to flash one of the stock images.
Again, If someone could just let me know if i've missed anything or if I'm WAY off base I would appreciate it.
Thanks again, and I love the forum and the community!
yep you got it correct...also if you have any questions feel free to post in my thread!
droidstyle said:
yep you got it correct...also if you have any questions feel free to post in my thread!
Click to expand...
Click to collapse
Thank you very much, I really appreciate it!! Can't wait to get started.
I did try to post in your thread, but apparently I'm to much of a NOOB to do so LOL!
nickjensz said:
Thank you very much, I really appreciate it!! Can't wait to get started.
I did try to post in your thread, but apparently I'm to much of a NOOB to do so LOL!
Click to expand...
Click to collapse
I've got 2 more questions....
1. I tried to flash the synergy backup for the IMEI/EFS using stock recovery as per the instructions and I got a message that the signatures or something like that wasn't correct and it was aborted.... Thoughts?
2. As far as custom recoveries go.... I'm used to CWM, but I've heard a lot of good things about TWRP. Which would you recommend?
nickjensz said:
I've got 2 more questions....
1. I tried to flash the synergy backup for the IMEI/EFS using stock recovery as per the instructions and I got a message that the signatures or something like that wasn't correct and it was aborted.... Thoughts?
2. As far as custom recoveries go.... I'm used to CWM, but I've heard a lot of good things about TWRP. Which would you recommend?
Click to expand...
Click to collapse
#1-Have never had to use it as I have never lost IEMI. May be a way to disable signature check in recovery. Can do permanent fix with terminal emulator.
Type:
su (enter)
reboot nvbackup (enter)
#2- Recovery is personal choice. I have been using TWRP since pre-order release and never had a bad flash or backup. As far as I'm concerned it rocks. Easier navigation and looks good. Some prefer CWM. To each their own. Don't recommend flashing via Rom Manager. Flash straight from recovery.
prdog1 said:
#1-Have never had to use it as I have never lost IEMI. May be a way to disable signature check in recovery. Can do permanent fix with terminal emulator.
Type:
su (enter)
reboot nvbackup (enter)
#2- Recovery is personal choice. I have been using TWRP since pre-order release and never had a bad flash or backup. As far as I'm concerned it rocks. Easier navigation and looks good. Some prefer CWM. To each their own. Don't recommend flashing via Rom Manager. Flash straight from recovery.
Click to expand...
Click to collapse
Thank you very much for the advice! I really appreciate it!
signature verification error means you were in stock blue recovery and not cwm recovery.
droidstyle said:
signature verification error means you were in stock blue recovery and not cwm recovery.
Click to expand...
Click to collapse
Thanks DroidStyle Wouldn't have gotten this far without the help! Finally got CWM on and flashed i that way and it worked great!
Speaking of CWM though.... in EZRecovery, do I need to hit "FLASH" and then "Reboot" recovery everytime I want to go into CWM or TWRP? If I don't it just takes me to stock recovery.
nickjensz said:
Thanks DroidStyle Wouldn't have gotten this far without the help! Finally got CWM on and flashed i that way and it worked great!
Speaking of CWM though.... in EZRecovery, do I need to hit "FLASH" and then "Reboot" recovery everytime I want to go into CWM or TWRP? If I don't it just takes me to stock recovery.
Click to expand...
Click to collapse
you should only need to flash cwm or twrp once, then reboot recovery to get into cwm. im not sure why its not sticking but it should.