Related
I have an N1 that I unlocked and rooted and was running CM7 RC1 when I decided to try the stock Gingerbread. This switch went perfectly, but now I don't think I want to stay on the stock GB but I can't seem to get ROM Manager to boot into recovery to allow me to flash another ROM. Do I have to do something differently now? BTW, I do not have root on the 'new' GB.
Thanks.
Unless you flashed a pre-rooted version of Gingerbread, you will have lost root and your custom recovery...
If this is the case, you have two options:
1 - Flash a custom recovery through an unlocked bootloader.
2 - passimg back to an older version of Android and root again...
Sent from my Nexus One using XDA App
tsprks said:
BTW, I do not have root on the 'new' GB.
Click to expand...
Click to collapse
This is your problem. ROM Manager installs a custom recovery, but only when your phone is rooted. You need to re-root GB.
Can I ask them how people flash custom recoveries without having root? I see threads all over the place that say that you don't have to root your phone to run these custom ROM's.
tsprks said:
Can I ask them how people flash custom recoveries without having root? I see threads all over the place that say that you don't have to root your phone to run these custom ROM's.
Click to expand...
Click to collapse
You have to root, but you don't have to unlock your bootloader.
You have to do one of the things:
1) Root.
2) Unlock the bootloader.
Rooting allows you to bypass security mechanisms from within the OS, and flash the custom recovery from there.
Unlocking the bootloader turns off the security mechanisms, and you can flash whatever you want directly from bootloader.
Both achieve the same thing, but in different ways.
Root privileges in OS are lost upon official upgrades.
Unlocked bootloader is never lost.
Unlocked bootloader allows for an easy way to gain root in the first place, regardless of the ROM.
How does an unlocked bootloader allow me to flash whatever ROM I want? ROM Manager won't run without root? Am I missing something? I've read the wiki's and threads about rooting an N1 and they all just seem to stop at unlocking the bootloader, well, my bootloader is unlocked but I can't get it to boot into CWM so that I can select another ROM. Is there another way to do this?
ROM Manager is only one, and not the most successful nor most powerful, way to flash ROMs or recovery. ROM Manager was made for non-understanding people to make the process look and feel easier. The most powerful way is directly from bootloader - which needs to be unlocked to allow it.
If you read all the threads, you'll see that unlocking the bootloader is just a first step - you can look carefully at "installing custom ROM" guide in Wiki. Or, for example, here:
http://forum.xda-developers.com/showthread.php?t=636795
Read the Wiki, look for recovery installation instructions using unlocked bootloader, execute. I suggest Amon_Ra's.
i had a nexus one and was able to unlock the bootloader but i think i updated it to 2.3.4 and then tried to install CWM, which didn't work. i then discovered the antenna was not working correctly so i had to exchange the phone for another new one. once i get my new nexus one i was still thinking about installing CM7 and i just want to get some things straight about 2.3.4 and installing clockworkmod recovery.
will i be able to install CWM after i update my nexus one to stock 2.3.4? if not what is the highest stock build i would be able to do it with?
concerning the radio, if it is not possible to update to 2.3.4 and then install CWM i guess i'd have to update the radio by itself right?
You can unlock the bootloader and install cwm, or you can revert to an earlier version of Android, root, and then install cwm...
so i guess it's not possible to root and install CWM on 2.3.4? what's the latest version of android i would have to revert to for rooting and installing CWM?
There is no exploit for 2.3.4, so there is no easy root...
To downgrade, you have to do the passimg with a shipped image, and the most recent is FRG33. However, once rooted you can update all the way to 2.3.4 and keep root, if you do things in the right order...
You could also update to 2.3.3 and root and update to 2.3.4 keeping root - but the end result is the same...
You can also root 2.3.4 after unlocking the bootloader and flashing a custom recovery. From there, you would need to flash one of the su.zip files floating around (you may need a specific one for Gingerbread), which should remove the stock recovery checks (what replaces the custom recovery when you boot a stock install) and should add the necessary files for root access.
the first nexus one i received was on 2.2.1 so i guess if i plan on installing CM7 i should just keep in there and not bother upgrading anything (maybe the radio only)? just want to make sure where i stand so someone could help me accomplish these things. i know how to unlock the bootloader and i think i'll be fine installing CWM so what order should i:
unlock the bootloader
upgrade the radio (i guess i don't have to do this if i upgrade to 2.3.4)
install CWM
root
upgrade to 2.3.4
install CM7
i'm just making sure i know what i'm doing before i get my replacement nexus one and while i have attempted searching for answers i haven't been able to find the specific order or answer to my question. if anyone can correct any mistakes or assumptions i've been making please let me know.
If you are unlocking the bootloader, there is no need to root the current android install. The whole point of rooting the phone is so you can get the custom recovery on there so you can load CM on the phone. Since you are unlocking the bootloader, you can load the custom recovery using fastboot, then boot into it, wipe the phone and flash CM (and gapps).
And if it is a replacement, it will most likely be running the 5.08 radio, which seems to be the best one for Gingerbread.
So it would be:
Unlock bootloader
flash clockworkmod
boot clockworkmod (select the bootloader screen and then recovery, don't reboot)
wipe phone
flash CM and gapps
reboot
????
profit
DarkKnight62 said:
unlock the bootloader
upgrade the radio (i guess i don't have to do this if i upgrade to 2.3.4)
install CWM
root
upgrade to 2.3.4
install CM7
Click to expand...
Click to collapse
You don't need to upgrade to 2.3.4 unless you want to upgrade the radio and hboot. Of course, you can upgrade them without updating the OS, though upgrading them with OS will be safer.
ok, now that i know that installing CM7 will root my phone if i do it by unlocking the bootloader and installing CWM i am wondering if my phone will be rooted once i restore my nandroid backup that i will make (of stock 2.3.4 android) right before i install CM7?
No. Root is separate from unlocking your bootloader and whatever recovery you are running. Root is at the OS level. Most custom firmwares come pre-rooted. That is, they contain the software needed to allow you to escalate your priveledges to root level. Stock firmwares, do not have this additional software, and anytime you get an update for stock, it will replace everything you had with your previous install, which will make you lose root if you had it.
So, if you install CM7, it will be rooted, but if you restore your stock 2.3.4, it will become unrooted (because it was unrooted when you made the backup).
What is your final plan for software on the phone? Stock 2.3.4, stock 2.3.4 with root, CM7? What is the point of restoring your nandroid of 2.3.4?
So,
My HTC Incredible S is rooted, and the bootloader is unlocked (what the point of unlocking the bootloader is I still don't know as I can't install custom ROMS... but back to the point at hand...), and the OTA update to 2.3.5 arrived 2 weeks ago.
Needless to say, the update would not install. Despite researching the issue, I'm still confused as to what exactly is preventing the update from working. Is the the fact that my device is rooted? Or is it the unlocked bootloader? I tried relocking the bootloader and that had no effect, so I'm assuming rooted devices for some reason are rejected by the update.
So considering I can't install custom ROMs (I'm HBOOT 1.16 and the downgrade guide didn't work for me, so no s-off), and I now can't upgrade officially, I'm feeling a little stuck.
Is there a way to force an official update to install on a phone in my 'condition'?
Note: My recovery is custom - Revolutionary CWM - and I can't find (and therefore cannot flash) an original recovery image... would this affect the updating process?
Thanks guys/gals,
G
Root won't stop an ota but an unlocked bootloader will. You can check in your boot screen if its still unlocked or if its relocked.
nope_okay said:
So,
My HTC Incredible S is rooted, and the bootloader is unlocked (what the point of unlocking the bootloader is I still don't know as I can't install custom ROMS... but back to the point at hand...), and the OTA update to 2.3.5 arrived 2 weeks ago.
Needless to say, the update would not install. Despite researching the issue, I'm still confused as to what exactly is preventing the update from working. Is the the fact that my device is rooted? Or is it the unlocked bootloader? I tried relocking the bootloader and that had no effect, so I'm assuming rooted devices for some reason are rejected by the update.
So considering I can't install custom ROMs (I'm HBOOT 1.16 and the downgrade guide didn't work for me, so no s-off), and I now can't upgrade officially, I'm feeling a little stuck.
Is there a way to force an official update to install on a phone in my 'condition'?
Note: My recovery is custom - Revolutionary CWM - and I can't find (and therefore cannot flash) an original recovery image... would this affect the updating process?
Thanks guys/gals,
G
Click to expand...
Click to collapse
You need to replace CWM with the standard HTC recovery (you simply need to extract the recovery.img file from a RUU/ROM.zip file) and then relock the bootloader before the OTA will install correctly.
At hboot 1.16 and rooted all you should have to do is install Cwm and than you can flash custom ROM's..... Not sure what your problem is.
Sent from my anus using xda crap
@itsbeertimenow - yeah, unlocking the bootloader never did anything for me in terms of being able to flash custom ROMs... I guess 's-off' is required
@tpbklake, nonverbose
Yeah, I had a feeling the custom recovery had something to do with it. As I mentioned before, even relocking the bootloader had no effect.
Does the recovery have to be a specific version? I'm running Android 2.3.3, so will any 2.3.3 recovery work or does it have to be a recovery for an HTC Incredible S running Android 2.3.3 - that's a little harder to find. Any suggestions for an ruu/zip file to extract a recovery img from?
Thanks again for the helpful responses.
G
nope_okay said:
@itsbeertimenow - yeah, unlocking the bootloader never did anything for me in terms of being able to flash custom ROMs... I guess 's-off' is required
@tpbklake, nonverbose
Yeah, I had a feeling the custom recovery had something to do with it. As I mentioned before, even relocking the bootloader had no effect.
Does the recovery have to be a specific version? I'm running Android 2.3.3, so will any 2.3.3 recovery work or does it have to be a recovery for an HTC Incredible S running Android 2.3.3 - that's a little harder to find. Any suggestions for an ruu/zip file to extract a recovery img from?
Thanks again for the helpful responses.
G
Click to expand...
Click to collapse
Instead of trying to install the OTA update for Sense 3/2.3.5 why don't you flash the stock, rooted version of 2.3.5/Sense 3 ROM that I posted in the Dev section. With the unlocked bootloader and CWM you can flash this ROM and then manually flash the boot.img in that ROM's zip file and you should be good to go.
@tpbklake
I think I'd already tried that and the update process aborted pretty early on. I'll give it another go and check out troubleshooting threads related to the process. thanks again.
G
Update: I'm following the instructions as per this thread: http://forum.xda-developers.com/showthread.php?t=1337105
Update 2: It worked and I managed to install CM7... happy day Thanks guys
nope_okay said:
@tpbklake
I think I'd already tried that and the update process aborted pretty early on. I'll give it another go and check out troubleshooting threads related to the process. thanks again.
G
Update: I'm following the instructions as per this thread: http://forum.xda-developers.com/showthread.php?t=1337105
Update 2: It worked and I managed to install CM7... happy day Thanks guys
Click to expand...
Click to collapse
Here is the 2.3.5/Sense 3.0 stock, rooted ROM built directly from the OTA you were trying to install. You would flash it in CWM just like you did for CM7.
http://forum.xda-developers.com/showthread.php?t=1430535
Thanks for the link, will come in handy when I want to go back to a 'stock' setup... wasn't very impressed with CM7 so I then tried the Virtuous Affinity ROM (2.3.5/S3.5) - fantastic. Thanks again for your help!
G
Hey guy
So i need to update firmware currently on 1.32.531.33 on my t mobile htc one m9 s-on. I was gonna use ruu.exe from herehttp://forum.xda-developers.com/tmobile-one-m9/general/please-read-rooting-using-twrp-t3069022. To my understading this will unroot and flash stock rom and i will be able update via OTA. Am I suppose to use the 1.32.531.33exe or 2.7.531.6exe(since on trying to update it)? Do I need to be s-off to use? Will this relock my bootloader? Is there any other changes in adb I need to make. Anything else I should be on the lookout for? Planning on rerooting after update. I couldnt find a guide with this info so any help is much appreciated. Thanks!
Accidental Genius said:
Hey guy
So i need to update firmware currently on 1.32.531.33 on my t mobile htc one m9 s-on. I was gonna use ruu.exe from herehttp://forum.xda-developers.com/tmobile-one-m9/general/please-read-rooting-using-twrp-t3069022. To my understading this will unroot and flash stock rom and i will be able update via OTA. Am I suppose to use the 1.32.531.33exe or 2.7.531.6exe(since on trying to update it)? Do I need to be s-off to use? Will this relock my bootloader? Is there any other changes in adb I need to make. Anything else I should be on the lookout for? Planning on rerooting after update. I couldnt find a guide with this info so any help is much appreciated. Thanks!
Click to expand...
Click to collapse
If you are looking to upgrade to the latest 2.11.531.19, you can get the RUU here.
You do not need to S-Off unless you plan on flashing older or intl firmware, Ruu will not relock the bootloader.
keep in mind, running RUU will completely wipe the phone, so Backup.
I would
1. Run latest RUU let it boot and set up.
2. Reboot to bootloader, flash Twrp (fastboot flash recovery twrp-2.8.7.0-hima.img)
3. Reboot to recovery and flash SuperSU here.
Unless you are going to flash roms then you only need to flash the firmware and twrp and rom
You can get the firmware in my thread here
Hope this helps
kc6wke said:
If you are looking to upgrade to the latest 2.11.531.19, you can get the RUU here.
You do not need to S-Off unless you plan on flashing older or intl firmware, Ruu will not relock the bootloader.
keep in mind, running RUU will completely wipe the phone, so Backup.
I would
1. Run latest RUU let it boot and set up.
2. Reboot to bootloader, flash Twrp (fastboot flash recovery twrp-2.8.7.0-hima.img)
3. Reboot to recovery and flash SuperSU here.
Unless you are going to flash roms then you only need to flash the firmware and twrp and rom
You can get the firmware in my thread here
Hope this helps
Click to expand...
Click to collapse
Thanks! I took a chance yesterday and ran the 1.32.531.33.exe to play it safe and updated via OTA to 2.7.531.6. But for future reference is it's okay to run RUUs that are above current firmware or do you have to use the one your current firmware matches (for instance running 2.7.531.6.exe when the device firmware is on 1.32.531.33). Also will roms running on older firmware work if device firmware is on 2.11.531.19?
Accidental Genius said:
Thanks! I took a chance yesterday and ran the 1.32.531.33.exe to play it safe and updated via OTA to 2.7.531.6. But for future reference is it's okay to run RUUs that are above current firmware or do you have to use the one your current firmware matches (for instance running 2.7.531.6.exe when the device firmware is on 1.32.531.33). Also will roms running on older firmware work if device firmware is on 2.11.531.19?
Click to expand...
Click to collapse
With S-on you can only use current of newer firmware.
They might, depends the roms base.
Hey guys,
I just got HTC ONE M9 T-Mobile version. I'm trying to unlock it. Saw a bunch of stuff online and keep trying everything what is out there. Tried to unlock it from htcdev but it says token is too long. I copied it multiple times the way it was described, still nothing happened. Copied it piece by piece, typed it... nothing worked same thing. Questions is this, I can't get it to root, unlock bootloader, s-off or any of that so what's going to happen if I install a RUU which is rooted so at least I'll have a start cause now I can't do ANYTHING. Whatever ideas you have, please let me know.
I tried htcdev, sunshine, kingroot, kingoroot, supersu, root apps.... nothing. The tmobile unlock app, no chance... Thanks
dohcvtec said:
Hey guys,
I just got HTC ONE M9 T-Mobile version. I'm trying to unlock it. Saw a bunch of stuff online and keep trying everything what is out there. Tried to unlock it from htcdev but it says token is too long. I copied it multiple times the way it was described, still nothing happened. Copied it piece by piece, typed it... nothing worked same thing. Questions is this, I can't get it to root, unlock bootloader, s-off or any of that so what's going to happen if I install a RUU which is rooted so at least I'll have a start cause now I can't do ANYTHING. Whatever ideas you have, please let me know.
I tried htcdev, sunshine, kingroot, kingoroot, supersu, root apps.... nothing. The tmobile unlock app, no chance... Thanks
Click to expand...
Click to collapse
I'm still an amateur myself but here is my understanding and recommendations.
RUU will update firmware and flash stock rom basically bringing you back to square one. You should be able to use it with a locked bootloader. If you can't do anything with the phone I would suggest to to use RUU dot exe of the latest firmware and update all OTAs. I used a video guide on youtube by "sakitech" when I rooted mine. Just search "root HTC One m9" it should be the first link. Make sure you're copying no more no less than your token ID. Hope this helps
You're way ahead of yourself, RUU is not rooted. It's a completely stock system. Like if you were to buy a brand new phone. It will wipe your phone completely too, nothing on sdcard.
Sent from my SM-N920T using Tapatalk
Hey guys,
Thank you very much for responding.
So what would be the best thing for me to do?
So I accidentally messed up my stock rom by dirty flashing, stupid of me I know.. without a backup.
Id like to know.. where can I download a stock firmware, debloated and latest if possible or if not just simply a stock firmware. Ive been trying to figure out for a day how to fix my problem but of no avail.
I use a custom recovery TWRP. Unlocked BL and rooted.
Help please
can u post a screenshot from device info ???
I have uploaded it
I can't find the b390 stock rom, but you could install the rollback package and go back to a previous build that for instance you can find here: https://www.getdroidtips.com/huawei-p9-stock-rom-firmware-collection/
And afterwards you could use the integrated updater.
But if possible oem unlock it first to save you from possible bricking. (oem lock restricts fastboot commands).