Related
..that is the question
I just bought a brand new Nexus S (cheaply compared to other phones of this caliber), and I'm really loving the the speed, stock Gingerbread and basically everything about it.
This is my first Android phone, but previously I used a Nook Color (rooted it myself) with CM7 so I'm also familiar with Cyanogen team's work.
I have been using it only for a few days and considering to root it, but here's what's stopping me:
- Google's ICS update (any estimates when it will hit the Nexus S?)
- warranty (any way to save to stock ROM and return it if I need to send the phone?
- bricking?
So I'm asking you guys who are using your Nexus S' for awhile:
- are there any special options in the CM7 for the Nexus S?
- what specific features are in CM7 that are missing from stock Gingerbread?
- which kernels do you guys suggest (with what major features)?
Regarding rooting and warranty:
- can I somehow unroot my Nexus S later on, when the ICS OTA update is available
- possibility of bricking? How high is it? I'm never had to do some ADB stuff so far, so as I see this won't be exactly just a walk in the park...
I know I bombed this post with questions but basically all I want to know from you guys: is it worth rooting, what are the advantages of rooting (beside the obvious one - having a root access for some apps that needs it) and most importantly what is "fixed" and tweaked in various kernels for the Nexus S?
Thanks in advance,
Atila
atirage said:
..that is the question
I just bought a new Nexus S (cheaply compared to other phones of that caliber), and I'm really loving the the speed, stock Gingerbread and basicly everything about it.
This is my first Android phone, but previously I used a Nook Color (rooted it myself) with CM7 so I'm also familiar with Cyanogen team's work.
I have been using it only for a few days and considering to root it, but here's what stopping me:
- Google's ICS update (any estimates when it will hit the Nexus S?)
- Warranty (any way to save to stock ROM and return it if I need to send the phone?
Click to expand...
Click to collapse
If you only unlock, flash CWM and flash the SU binary you will have root access and OTAs will still work fine.
Unlike the Nexus One unlocking the boot loader on the Nexus S does not automatically void the warranty. The language has changed to *may* void the warranty.
To save the stock rom, install CWM and make a nandroid backup. Flash that back, reboot and let install-recovery.sh restore the stock recovery and you're back in stock business.
atirage said:
Regarding rooting and warranty:
- can I somehow unroot my Nexus S later on, when the ICS ota update is due
- possibility of bricking? How high it is? I'm never had to do some ADB stuff so far, so as I see this wont be exactly a walk in the park..
Click to expand...
Click to collapse
- Restore nandroid to go back to stock, fastboot oem lock to relock the boot loader
- Possibility of bricking is insanely low. Essentially don't pull the battery during a radio flash (if you are updating the radio) and don't flash a CDMA radio to your GSM device. Other than that it's going to be near impossible to really brick it (in the sense that you can't recover it using recovery or fastboot).
krohnjw said:
If you only unlock, flash CWM and flash the SU binary you will have root access and OTAs will still work fine.
Unlike the Nexus One unlocking the boot loader on the Nexus S does not automatically void the warranty. The language has changed to *may* void the warranty.
To save the stock rom, install CWM and make a nandroid backup. Flash that back, reboot and let install-recovery.sh restore the stock recovery and you're back in stock business.
- Restore nandroid to go back to stock, fastboot oem lock to relock the boot loader
- Possibility of bricking is insanely low. Essentially don't pull the battery during a radio flash (if you are updating the radio) and don't flash a CDMA radio to your GSM device. Other than that it's going to be near impossible to really brick it (in the sense that you can't recover it using recovery or fastboot).
Click to expand...
Click to collapse
quick question how can you still receive OTAs after installing CWR because you essentially replaced the recovery, I was told that once you mod the recovery OTAs won't work. When 2.3.6 was launched I never received it until I went back to stock completely. Please help
anishs said:
quick question how can you still receive OTAs after installing CWR because you essentially replaced the recovery, I was told that once you mod the recovery OTAs won't work. When 2.3.6 was launched I never received it until I went back to stock completely. Please help
Click to expand...
Click to collapse
You were told incorrectly. I've flashed plenty of OTA's over CWM on both the Nexus One and the Nexus S. There is no assert done on the recovery in the OTA update script, it merely erases it and flashes a full recovery image over it.
Receiving the OTA has NOTHING to do with the status of your system (rooted, not rooted, custom recovery, locked/unlocked). Your device periodically checks to see if there are updates, if your IMEI / ESN is flagged for an update and you are running a previous build (based on build fingerprint) you'll get the notification to download the OTA.
oh wow alright thanks a lot!
@anishs: OTA update is basically downloading an update.zip which the stock recovery later flashes into the stock rom.
When rooted, you will probably have to tell CWM to flash the update.zip you just received from Google via OTA.
Please correct me if I'm wrong (@krohnjw).
@krohmjw: Thanks a lot for your answers, cleared up bunch of things for me, most of all the fear from bricking.
So could you please tell me some improvements done in CM7 compared the stock rom? (I didn't follow it's development and now I wouldn't know where/how to search for this.)
And the same question regarding the kernels available on XDA - do they improve speed or battery life or anything in particular you'd highlight as a new/better feature?
And regarding kernels: is a stock ROM + custom kernel (flashed by CWM) possible?
Thanks in advance,
Atila
PS: You said you also have a Nexus One, do you remember how long it received the Gingerbread update (and how was that done) after they started rolling out the Nexus S in December last year?
Was the community faster with the update then el Goog?
I wouldn't rely on the word "may" in regards to warranty. They'll argue and say "just unlocking won't void warranty, but further actions that require an unlocked bootloader will".
rentaric said:
I wouldn't rely on the word "may" in regards to warranty. They'll argue and say "just unlocking won't void warranty, but further actions that require an unlocked bootloader will".
Click to expand...
Click to collapse
Honestly, I wouldn't worry about it. I sent in an unlocked Nexus One that was damaged in a car accident - repaired under warranty for no charge. If it's a clear hardware defect you're fine, if you burn our your LED or toast your speaker then they may give you grief.
atirage said:
@anishs: OTA update is basically downloading an update.zip which the stock recovery later flashes into the stock rom.
When rooted, you will probably have to tell CWM to flash the update.zip you just received from Google via OTA.
Please correct me if I'm wrong (@krohnjw).
Click to expand...
Click to collapse
Correct
atirage said:
@krohmjw: Thanks a lot for your answers, cleared up bunch of things for me, most of all the fear from bricking.
Click to expand...
Click to collapse
It's really difficult to "brick" in the traditional sense.
atirage said:
So could you please tell me some improvements done in CM7 compared the stock rom? (I didn't follow it's development and now I wouldn't know where/how to search for this.)
And the same question regarding the kernels available on XDA - do they improve speed or battery life or anything in particular you'd highlight as a new/better feature?
Click to expand...
Click to collapse
I don't use CM7 or any non standard kernel any longer - too many stability issues early on and stock AOSP runs fine. Someone else will need to chime in here.
atirage said:
And regarding kernels: is a stock ROM + custom kernel (flashed by CWM) possible?
Click to expand...
Click to collapse
Yes - this will modify the boot partition though, so OTAs that assert boot to patch it will fail.
atirage said:
PS: You said you also have a Nexus One, do you remember how long it received the Gingerbread update (and how was that done) after they started rolling out the Nexus S in December last year?
Was the community faster with the update then el Goog?
Click to expand...
Click to collapse
The OTA didn't come out until last Feb if memory serves correctly. AOSP Gingerbread roms were being built for the Nexus One in December though.
Thank you again for all your answers
Can somebody explain to me what are the improvements in CM7 and a stable kernel over the stock ones?
Which rom and kernel combo is super stable for everyday use and have some major improvements/features compared to the stock rom?
Anyone can make some good points to root the phone?
atirage said:
Which rom and kernel combo is super stable for everyday use and have some major improvements/features compared to the stock rom?
Anyone can make some good points to root the phone?
Click to expand...
Click to collapse
A lot..just read at nexus S development..
If you want to safe..
flash CM 7.1/brainmaster MIUI/Formel MIUI/Pete Alfonso/Oxygen 2.3
kernel matrix V8, TEUV,TUV stable
I am personally holding out till ICS is released.
My conclusion...
borrowedchief said:
I am personally holding out till ICS is released.
Click to expand...
Click to collapse
After several days of research, that's the conclusion I got too.
It's all nice what I can do with a rooted device and an unlocked bootloader, but on the other hand the unrooted device is also very customizable and powerful.
The stock rom/kernel works fast and stable, so why risk it?
And the faster ICS official update (earlier then on any other device) is the main reason I bought this phone...
PS. Although I think we won't see an official ICS OTA update before 2-3 months after it's premier (which is next week). Most probably the XDA developers will make an ICS rom much, much sooner and we gonna end up unlocking/rooting our devices anyways.
thanky you to anyone ahead of time for reading this post. I really could use some help.
I have a Verizon galaxy s3 which I rooted 3 weeks ago when i got it. I know it was rooted as i had super user permissions, and deleted many bloatware apps. I waited until cm10 came out to flash a new rom and after doing so last night my phone now boots up with this message "System software not authorized by verizon wireless has been found on your phone. Please turn off your phone and go to the nearest Verizon Wireless store for help."
So I tried to boot it in to recovery mode but when I did, the same message came up, only this time it said "recovery booting" in small blue writing in the top left corner.
I followed the directions to a T from a page entitled "Jelly Bean for Verizon Galaxy S3: Unofficial CyanogenMod 10 (CM10) Nightlies Available for Flashing!
From what I understand, the bootloader was somehow never unlocked by kexec. because I cant get in to recovery mode, I was wondering if there was a way to disable the bootlock by installing kexec via odin.
Also, whether it was a good idea or not, I re flashed the stock rom via oden last, which was successful but, nothing has changed still the same response all boot ups. Download boot obviously works though as I have been able to mess with it in odin.
any insight on this would be graciously appreciated.
Lembro said:
thanky you to anyone ahead of time for reading this post. I really could use some help.
I have a Verizon galaxy s3 which I rooted 3 weeks ago when i got it. I know it was rooted as i had super user permissions, and deleted many bloatware apps. I waited until cm10 came out to flash a new rom and after doing so last night my phone now boots up with this message "System software not authorized by verizon wireless has been found on your phone. Please turn off your phone and go to the nearest Verizon Wireless store for help."
So I tried to boot it in to recovery mode but when I did, the same message came up, only this time it said "recovery booting" in small blue writing in the top left corner.
I followed the directions to a T from a page entitled "Jelly Bean for Verizon Galaxy S3: Unofficial CyanogenMod 10 (CM10) Nightlies Available for Flashing!
From what I understand, the bootloader was somehow never unlocked by kexec. because I cant get in to recovery mode, I was wondering if there was a way to disable the bootlock by installing kexec via odin.
Also, whether it was a good idea or not, I re flashed the stock rom via oden last, which was successful but, nothing has changed still the same response all boot ups. Download boot obviously works though as I have been able to mess with it in odin.
any insight on this would be graciously appreciated.
Click to expand...
Click to collapse
Okay, first, If you did follow the directions for that thread, i'm sure it would of worked, I'm pretty sure you are missing something here and i'm pretty sure from reading your post that I think you didn't unlock your bootloader. kexec was a workaround for the locked bootloader, it doesn't unlock it. I would follow droidstyle's guide to unlocking the bootloader, http://forum.xda-developers.com/showpost.php?p=28530409&postcount=2 after you unlocked it, i'm pretty sure you forgot that step. But the issue when flashing back to stock via odin and still showing up its a custom rom, I don't know why that would happen but I suggest reading section 2 of droidstyle's guide on flashing back to stock. http://forum.xda-developers.com/showpost.php?p=28530394&postcount=1
So first, I suggest to return to stock, then root, then unlock bootloader, and then install the rom of your choice, preferably without kexec, if you don't want the triple reboot.
RyanW114 said:
Okay, first, If you did follow the directions for that thread, i'm sure it would of worked, I'm pretty sure you are missing something here and i'm pretty sure from reading your post that I think you didn't unlock your bootloader. kexec was a workaround for the locked bootloader, it doesn't unlock it. I would follow droidstyle's guide to unlocking the bootloader, http://forum.xda-developers.com/showpost.php?p=28530409&postcount=2 after you unlocked it, i'm pretty sure you forgot that step. But the issue when flashing back to stock via odin and still showing up its a custom rom, I don't know why that would happen but I suggest reading section 2 of droidstyle's guide on flashing back to stock. http://forum.xda-developers.com/showpost.php?p=28530394&postcount=1
So first, I suggest to return to stock, then root, then unlock bootloader, and then install the rom of your choice, preferably without kexec, if you don't want the triple reboot.
Click to expand...
Click to collapse
Agreed! Op, do more reading and less flashing before you end up with a 600.00 paperweight!
Like he says above you have not unlocked your bootloader . Restore nandroid or recover to stock. Then unlock your bootloader and try again
Sent from my SCH-I535 using xda premium
Get rid of the Verizon screen of death
I got the same error msg after flashing a nightly of d2hacker's unofficial cm10, after I had flashed a few nightly's before of the same ROM w/ no problems. I had to
1. Flash a stock bloated unrooted ROM via odin (lemme know if you need a link to one)
2.boot into droid recovery and do a factory reset, and wipe the cache partition also.
If you don't do step 2 you end up w/ a permanent verizon 4G LTE rainbow boot screen :silly:
I haven't re-rooted yet but I'll be trying the official cm10 now that it's up.
MDMoore313 said:
I got the same error msg after flashing a nightly of d2hacker's unofficial cm10, after I had flashed a few nightly's before of the same ROM w/ no problems. I had to
1. Flash a stock bloated unrooted ROM via odin (lemme know if you need a link to one)
2.boot into droid recovery and do a factory reset, and wipe the cache partition also.
If you don't do step 2 you end up w/ a permanent verizon 4G LTE rainbow boot screen :silly:
I haven't re-rooted yet but I'll be trying the official cm10 now that it's up.
Click to expand...
Click to collapse
Refer to my last post
droidstyle said:
Refer to my last post
Click to expand...
Click to collapse
Note that even when I flashed back to stock, my initial boot screen still had the unlocked lock, w/ "Custom" under it, suggesting my bootloader is unlocked
MDMoore313 said:
Note that even when I flashed back to stock, my initial boot screen still had the unlocked lock, w/ "Custom" under it, suggesting my bootloader is unlocked
Click to expand...
Click to collapse
Incorrect. It actually means the opposite. The only way to tell if your bootloader is unlocked is to flash a custom rom/kernel and boot up. Please people, do some reading before you turn your phone into a paperweight. That unlocked lock/custom means you're running or were running custom software and it's been detected as such. One possible culprit is your "custom" recovery. If your bootloader is unlocked, you will not have that problem.
MDMoore313 said:
Note that even when I flashed back to stock, my initial boot screen still had the unlocked lock, w/ "Custom" under it, suggesting my bootloader is unlocked
Click to expand...
Click to collapse
refer to post #3 and read this link
http://forum.xda-developers.com/showpost.php?p=30479625&postcount=13
Zalithian said:
Incorrect. It actually means the opposite. The only way to tell if your bootloader is unlocked is to flash a custom rom/kernel and boot up. Please people, do some reading before you turn your phone into a paperweight. That unlocked lock/custom means you're running or were running custom software and it's been detected as such. One possible culprit is your "custom" recovery. If your bootloader is unlocked, you will not have that problem.
Click to expand...
Click to collapse
Thanks for clearing that up, Where did you find this info? I'm coming from a Droid incredible, so I never had to worry about such things....
EDIT: I just saw Droidstyle's post @ http://forum.xda-developers.com/showpost.php?p=30479625&postcount=13, makes a little sense, but why all of a sudden Verizon's screen of death is odd, if it was already detecting custom s/w to begin with. I used kexec also as a workaround, but this was back when there was no way to unlock the gs3 bootloader.
Yeah absolutely I follow the steps here http://forum.xda-developers.com/showpost.php?p=28530394&postcount=1
MDMoore313 said:
Thanks for clearing that up, Where did you find this info? I'm coming from a Droid incredible, so I never had to worry about such things....
EDIT: I just saw Droidstyle's post @ http://forum.xda-developers.com/showpost.php?p=30479625&postcount=13, makes a little sense, but why all of a sudden Verizon's screen of death is odd, if it was already detecting custom s/w to begin with. I used kexec also as a workaround, but this was back when there was no way to unlock the gs3 bootloader.
Yeah absolutely I follow the steps here http://forum.xda-developers.com/showpost.php?p=28530394&postcount=1
Click to expand...
Click to collapse
I think it has to do with the "degree" of customization. IE a custom ROM or Kernel will get you the verizon screen of death for sure if you're not unlocked. The custom/unlock icon seems more for minor things like a custom recovery, possibly different firmware or tweaking specific settings.
Zalithian said:
I think it has to do with the "degree" of customization. IE a custom ROM or Kernel will get you the verizon screen of death for sure if you're not unlocked. The custom/unlock icon seems more for minor things like a custom recovery, possibly different firmware or tweaking specific settings.
Click to expand...
Click to collapse
That makes more sense, as the nightlys progress and more modifications are being made, overnight the "switch is flipped" so to speak, and if you're not running a custom rom,
MDMoore313 said:
If you don't do step 2 you end up w/ a permanent verizon 4G LTE rainbow boot screen :silly:
Click to expand...
Click to collapse
Could he Odin back to stock through download mode though? Or will the locked bootloader block download mode and recovery mode too when it detects tampering?
MDMoore313 said:
Thanks for clearing that up, Where did you find this info? I'm coming from a Droid incredible, so I never had to worry about such things....
EDIT: I just saw Droidstyle's post @ http://forum.xda-developers.com/showpost.php?p=30479625&postcount=13, makes a little sense, but why all of a sudden Verizon's screen of death is odd, if it was already detecting custom s/w to begin with. I used kexec also as a workaround, but this was back when there was no way to unlock the gs3 bootloader.
Yeah absolutely I follow the steps here http://forum.xda-developers.com/showpost.php?p=28530394&postcount=1
Click to expand...
Click to collapse
The secure aboot.img only checks 3 of the 5 system images on boot. Since we can flash a custom recovery to the recovery partition, the secure aboot img lets it ride, but knows it there....hence why you see the custom lock screen, but device still boots. Kexec allowed the bootloader aka secure aboot.img to see the stock kernel(boot.img) and pass signature checks, then side loads the custom kernel. Thats why there was 3 reboots...now that the bootloader is unlocked, we ditch kexec because unsecure aboot is unlocked and not checking signatures.
However, if you flash a kernel thats non kexec and the bootloader is locked, you will get the verizon screen of death since the secure aboot.img is checking signatures. So never lock the bootloader unless your on stock rom/kernel or using kexec.
Deleted
Jesus. All of these people who don't read up on things before they flash something astounds me.
Lol, the exact same thing happen to me as Op, I was unlock (ezrecovery app) and rooted(casual-revision131) but when I flash unofficial CM10 KANG I was lock out by Verizon message.Thanks to DroidStyle awesome GUIDE i just Odin back to stock along with kernel.Thank you to all the cool people here at xda who help and evolve Android:thumbup:
Ezrecovery app must not have work properly even tho it said unlock, so I use Adam casual R131 flash Unsecure Aboot too.
Sent from my SCH-I535 using xda premium
EvoSideHustlAZ said:
Lol, the exact same thing happen to me as Op, I was unlock (ezrecovery app) and rooted(casual-revision131) but when I flash unofficial CM10 KANG I was lock out by Verizon message.Thanks to DroidStyle awesome GUIDE i just Odin back to stock along with kernel.Thank you to all the cool people here at xda who help and evolve Android:thumbup:
Ezrecovery app must not have work properly even tho it said unlock, so I use Adam casual R131 flash Unsecure Aboot too.
Sent from my SCH-I535 using xda premium
Click to expand...
Click to collapse
ezrecovery to unlock? What?
MDMoore313 said:
Note that even when I flashed back to stock, my initial boot screen still had the unlocked lock, w/ "Custom" under it, suggesting my bootloader is unlocked
Click to expand...
Click to collapse
No, that just means that it normally has detected some changed files. If you WERE unlocked you would never see that icon.
TAPPED in on my (now unlocked bootloader) Verizon S3
strung said:
Could he Odin back to stock through download mode though? Or will the locked bootloader block download mode and recovery mode too when it detects tampering?
Click to expand...
Click to collapse
Well, step 1 is going Odin back to stock, but if a cache wipe and factory reset aren't done (like in Droidstyle's guide), then it will never completely boot, at least that's what I experienced after my phone sat at that screen for 10+ minutes. It doesn't run the user setup again.
dear all,
has anybody tried this? http://forum.xda-developers.com/showthread.php?t=1940630
Already rooted, going to try it on a demo phone at work,
sent from my giant f$%&en Q
I tried it today works great, thanks posting it here i wanted root but didnt want unlock it.
Sent from my XT897 using xda app-developers app
Thanks a lot for confirming this as I am in the same boat. I will eventually unlock based on the fact that I hear you can't have custom recovery unless you unlock. I also came from a samsung epic and I haven't quite gotten the moto lingo down so I don't quite follow the boot and fastboot stuff yet. I think i have pieced together that moto has a better stock recovery than Samsung therefor you don't necessarily need a custom recovery to flash stuff if unlocked, but please correct me if I have assumed to much. Thx again.
Sent from my XT897 using xda app-developers app
bryanfritz1 said:
Thanks a lot for confirming this as I am in the same boat. I will eventually unlock based on the fact that I hear you can't have custom recovery unless you unlock. I also came from a samsung epic and I haven't quite gotten the moto lingo down so I don't quite follow the boot and fastboot stuff yet. I think i have pieced together that moto has a better stock recovery than Samsung therefor you don't necessarily need a custom recovery to flash stuff if unlocked, but please correct me if I have assumed to much. Thx again.
Sent from my XT897 using xda app-developers app
Click to expand...
Click to collapse
I unlocked and trashed the stock recovery and ported TWRP immediately after getting the device...
BUT with that said, typically stock recoveries will only flash signed/stock stuffs. So I doubt you'll be able to install anything aftermarket with their stock recovery... Obviously I don't know if this is true or not, I never even had stock reco on long enough to find out .
This worked great for me. No unlocked bootloader prior to running the script.
Now if only I could get wifi tether working...
bryanfritz1 said:
Thanks a lot for confirming this as I am in the same boat. I will eventually unlock based on the fact that I hear you can't have custom recovery unless you unlock. I also came from a samsung epic and I haven't quite gotten the moto lingo down so I don't quite follow the boot and fastboot stuff yet. I think i have pieced together that moto has a better stock recovery than Samsung therefor you don't necessarily need a custom recovery to flash stuff if unlocked, but please correct me if I have assumed to much. Thx again.
Sent from my XT897 using xda app-developers app
Click to expand...
Click to collapse
no stock recovery can flash OTA's and thats all
i was wondering how long it would take people to find this . reason why i dindt post it? next OTA that comes and wipes it out youve gutta wait until a new exploit is found... or unlock the bootloader and flash a recovery.
Install ota rootkeeper from the market and you will keep root through an update. Works great. I obviously haven't used the app on the photon q but it worked on a few other devices.
Having said that, sometimes updates come with different bootloaders and sometimes you don't want a newer bootloader.
Hi Guys,
I know this may be frustrating for some of you, but as a complete beginner in using Android, I was wondering whether someone could help me out here. I have tried searching various forums, but my knowledge of androids is limited. I used the tutorial from Rootwiki to successfully unlock my bootloader, install TWRP recovery and root my phone
Does this mean I am not using a stock rom?
Now I sort of regret deciding to do this and would like to return to stock so that I can get any OTA updates without further tampering with my phone. Unfortunately while following the above tutorial, I only made a backup after TWRP was installed and not before, so I need help in going back please.
I can see that there are a few people in my position, so I'm sure others will benefit from this as well.
My software details are:
Android version - 4.2.2.
Software number - 1.33.206.1
HTC SDK API level - 5.41
Network - o2 uk
Can I use any stock recovery file or does it have to be specific to the above?
Can you please provide a step by step guide with a list of files that I will need to download?
or can I simply just factory reset my phone, and everything goes back to normal? I don't mind having to re install apps etc?
Thank you all very much
i have a HTC One mini 4.3 and i am in the exact same situation. i like to get stock recovery but those ive tried hasent been working.
If you didint flash a rom after you installed your recovery, the back up you made is then of stock os
Maybe if you take the ota, it will cancel out ur root and five you stock recovery back, i havent browsed these forums.. Try searching for a RUU and stock recovery, the phone is fairly new, so can take time for someone to put something together
Sent from my HTC6500LVW using xda app-developers app
the stock recovery must match HBOOT /Main-Version....
wich HBOOT do you have?
epolus said:
the stock recovery must match HBOOT /Main-Version....
wich HBOOT do you have?
Click to expand...
Click to collapse
Thank you for your replies, my HBOOT is 2.19.0000
Ok guys, I got the notification for the OTA update today, I have downloaded it but haven't installed it. From a different thread, I found a link for a stock recovery which is about 9.5mb from androidfile host (/?fid=23252070760975668)
can I just flash this recovery and proceed with the update? or will there be compatibility issues with the version I have above?
Thanks
Anyone?
I am getting desperate to the point that I might actually pay HTC to repair it for me
Did u have any look for I'm looking for the same but have an unrooted mini
Sent from my HTC One mini using Tapatalk
nbbcj said:
Did u have any look for I'm looking for the same but have an unrooted mini
Sent from my HTC One mini using Tapatalk
Click to expand...
Click to collapse
not yet, but MirageBlader has been quite helpful and has said the following in a private message to me, which I have yet to try:
"Very easy mate, open your ota and flash the stock recovery from the ota. You can only install it with stock Rom, stock boot and stock recovery. Your bootloader musst be locked and your phone unrooted. s-off is not needed if you already got the ota"
drewkp said:
not yet, but MirageBlader has been quite helpful and has said the following in a private message to me, which I have yet to try:
"Very easy mate, open your ota and flash the stock recovery from the ota. You can only install it with stock Rom, stock boot and stock recovery. Your bootloader musst be locked and your phone unrooted. s-off is not needed if you already got the ota"
Click to expand...
Click to collapse
I'd be very interested to know the results of your attempt to go back to "stock".
Can I ask if you are doing this just to get the 4.3 update? Also, do you plan to root and customise your ROM after the update, or leave it stock?
Thanks, and good luck....
---------- Post added at 01:14 AM ---------- Previous post was at 01:10 AM ----------
nbbcj said:
Did u have any look for I'm looking for the same but have an unrooted mini
Sent from my HTC One mini using Tapatalk
Click to expand...
Click to collapse
If your phone isn't rooted, what exactly is the issue? Do you have a custom recovery installed, and is your bootloader unlocked? If you are looking to upgrade, did you get the OTA download on your phone?
Hi nelvinchi I am trying to get back to android ver 4.2, I have a stock mini it's not been rooted or mod'd in any way. Just had the 4.3 ota that was update automatically just woke up and my phone had updated looking at settings it was set to auto update and install when on charge Grr dam phone so many probs with this ota
Sent from my HTC One mini using Tapatalk
nelvinchi said:
I'd be very interested to know the results of your attempt to go back to "stock".
Can I ask if you are doing this just to get the 4.3 update? Also, do you plan to root and customise your ROM after the update, or leave it stock?
Thanks, and good luck....
---------- Post added at 01:14 AM ---------- Previous post was at 01:10 AM ----------
If your phone isn't rooted, what exactly is the issue? Do you have a custom recovery installed, and is your bootloader unlocked? If you are looking to upgrade, did you get the OTA download on your phone?
Click to expand...
Click to collapse
I haven't got round to trying this out yet, will update this thread once I do, just quite busy this month and can't afford to mess up my phone. Yep, just doing it for the update, I only rooted my phone in the first place to get rid of bloatware, which i realised is a lot more complicated than just rooting, and all the other benefits of rooting don't really appeal to me, or are too much hassle for a beginner such as myself.
Just need to figure out how to unroot and relock my bootloader before I can go ahead with this :s
Hey nelvinchi. You seem to be knowledgeable enough on the matter and have been looking for help with my device. I posted a separate thread yesterday. If you have time/think you can help, could you take a look? Would much appreciate it.
drewkp said:
I haven't got round to trying this out yet, will update this thread once I do, just quite busy this month and can't afford to mess up my phone. Yep, just doing it for the update, I only rooted my phone in the first place to get rid of bloatware, which i realised is a lot more complicated than just rooting, and all the other benefits of rooting don't really appeal to me, or are too much hassle for a beginner such as myself.
Just need to figure out how to unroot and relock my bootloader before I can go ahead with this :s
Click to expand...
Click to collapse
If you have SuperSU installed on your phone, the app has a settings option called "Full unroot" - this will get rid of root. Relocking your bootloader - there are various methods, you could try HTCDEV site (probably how you unlocked originally), or the revone option which will lock the bootloader and remove the "tampered" label. Try a search, but if you are unsure, jusk ask!
2664963463
Got everything sorted with the great help of Nelvin. I had previously gone to the twrp support IRC and after answering a few questions, they just stopped talking... Glad there are people out there still willing to help! He spent a good hour or so with me making sure everything was working.
nelvinchi said:
If you have SuperSU installed on your phone, the app has a settings option called "Full unroot" - this will get rid of root. Relocking your bootloader - there are various methods, you could try HTCDEV site (probably how you unlocked originally), or the revone option which will lock the bootloader and remove the "tampered" label. Try a search, but if you are unsure, jusk ask!
Click to expand...
Click to collapse
Thanks for your reply nelvinchi, can I just confirm whether the SuperSU app you're talking about it the one by Chainfire in the marketplace? And is it just a matter of installing this from the marketplace to unroot my device, or is it a bit more complicated than that?
I'll do some research on relocking my bootloader with revone.
Also do you reckon the above method of getting the stock recovery from my update file will work?
Thanks for your help
drewkp said:
Thanks for your reply nelvinchi, can I just confirm whether the SuperSU app you're talking about it the one by Chainfire in the marketplace? And is it just a matter of installing this from the marketplace to unroot my device, or is it a bit more complicated than that?
I'll do some research on relocking my bootloader with revone.
Also do you reckon the above method of getting the stock recovery from my update file will work?
Thanks for your help
Click to expand...
Click to collapse
If you are rooted then you more than likely have supersu already installed. Check your app drawer.I rooted using HTC DEV and supersu was flashed to the phone with twrp as part of the process
drewkp said:
Thanks for your reply nelvinchi, can I just confirm whether the SuperSU app you're talking about it the one by Chainfire in the marketplace? And is it just a matter of installing this from the marketplace to unroot my device, or is it a bit more complicated than that?
I'll do some research on relocking my bootloader with revone.
Also do you reckon the above method of getting the stock recovery from my update file will work?
Thanks for your help
Click to expand...
Click to collapse
Can I make a suggestion? Given where you are with your phone currently, It would be much simpler, and virtually risk free, to flash tr1gg3r's Stock Sense 5.5 4.3 rooted deodexed rom from the One Mini Android Development forum.
You will get the 4.3 update, and have a fast and very stable ROM. All future updates will be incorporated into a newer ROM version.
Returning to "stock" carries FAR more risk - and you'll never have true stock because it isn't possible. Soon as the bootloader is unlocked, your phone is tampered, and no tool or utility can change that (other than cosmetically!)
It's your choice obviously, but if I was you, I'd stay rooted and enjoy the benefits it brings!
If you still want to try to go back to stock, I'll help..... But I've now helped three members get out of a soft brick after they attempted to go stock.......
So I have always rooted my phones in the past.
I rooted my Samsung Galaxy S2 because well, it needed KitKat and Samsung is lame...
Now I am faced with the decision to root or not to root. My N5 is awesome it has Full support and is the raw experience I want, rooting would let me have a little more fun in the way of mods and tweaks, but all the problems everyone seems to be having is kinda putting me off so I guess I just need help.
Also there is a difference between unlocking boot loader and rooting, does the unlocking void warranty?
All guides and info threads are linked in my signature and will answer almost all your questions
I'm not sure of all these "problems" you're referring to. Basically, idiots have the most problems. Normal people don't really have any
Sent from my Nexus 5 using Tapatalk < Yes, I want you to know that I'm using a mobile client
rootSU said:
Basically, idiots have the most problems. Normal people don't really have any
Click to expand...
Click to collapse
this. i have been rooted since day one and have ZERO problems.
I think this: http://forum.xda-developers.com/showpost.php?p=54746284&postcount=8
Applies here too, what do you think, @rootSU?
Right. Root doesn't modify files that can cause an issue assuming you're doing it right. I'd highly recommend NOT using a toolkit and rooting yourself and unlocking the bootloader yourself, it assures nothing goes wrong and you get some experience.
rootSU's guide are a treasure trove of information, take a looksie.
unlocking the bootloader lets you flash a custom recovery to flash things, it has nothing to do with root. you can flash any roms or kernels you want, without root. all root does is give you permission to change system files. and you would flash the root zip in your new recovery once you unlock the bootloader.
simms22 said:
unlocking the bootloader lets you flash a custom recovery to flash things, it has nothing to do with root. you can flash any roms or kernels you want, without root. all root does is give you permission to change system files. and you would flash the root zip in your new recovery once you unlock the bootloader.
Click to expand...
Click to collapse
So would unlocking the boot loader void the warranty?
Spectrys said:
So would unlocking the boot loader void the warranty?
Click to expand...
Click to collapse
depending on who you bought it from, yes and no. but anyways, you can lock the bootloader after as well, easily. generally, google will still except warrenty if the bootloader is unlocked for any hardware issue. other companies will void the warrenty, including LG. but again, it can be relocked
simms22 said:
depending on who you bought it from, yes and no. but anyways, you can lock the bootloader after as well, easily. generally, google will still except warrenty if the bootloader is unlocked for any hardware issue. other companies will void the warrenty, including LG. but again, it can be relocked
Click to expand...
Click to collapse
So would unlocking allow me to do things like mods, such as rings and boot screens?
Sorry kinda new to boot loaders.
Spectrys said:
So would unlocking allow me to do things like mods, such as rings and boot screens?
Sorry kinda new to boot loaders.
Click to expand...
Click to collapse
yup. anything that needs to be flashed will go through your custom recovery, which needs an unlocked boitloader to get flashed onto your device. then youll use that recovery to flash things, and make backups.
Spectrys said:
So would unlocking allow me to do things like mods, such as rings and boot screens?
Sorry kinda new to boot loaders.
Click to expand...
Click to collapse
Unlocking the bootloader is a requirement in order to use a custom recovery. And most mods are installed by flashable zips in recovery. So yes kind of required.
Sent from my Nexus 5 using Tapatalk
Awesome! You guys are great I am going to unlock later today or tomorrow.
Now next question the ota updates will I be able to install those if I keep stock with an unlocked boot loader?
Spectrys said:
Awesome! You guys are great I am going to unlock later today or tomorrow.
Now next question the ota updates will I be able to install those if I keep stock with an unlocked boot loader?
Click to expand...
Click to collapse
If you click the link in my signature, theres a thread about ota. All guides and info is there. Every question you've asked today is answered there
Sent from my Nexus 5 using Tapatalk < Yes, I want you to know that I'm using a mobile client
Pretty sure you told me that earlier, thanks.
Looking at it now.
Spectrys said:
Pretty sure you told me that earlier, thanks.
Looking at it now.
Click to expand...
Click to collapse
Yepp. Loads of good stuff there
Sent from my Nexus 5 using Tapatalk < Yes, I want you to know that I'm using a mobile client
sure
root is best thing to do . just root and install custom kernel
MohamedHusseinMohamed said:
root is best thing to do . just root and install custom kernel
Click to expand...
Click to collapse
you do not need root to install custom kernels
all you need root for is to change system files. well, that's all root does, is give you permission.
Spectrys said:
So I have always rooted my phones in the past.
I rooted my Samsung Galaxy S2 because well, it needed KitKat and Samsung is lame...
Now I am faced with the decision to root or not to root. My N5 is awesome it has Full support and is the raw experience I want, rooting would let me have a little more fun in the way of mods and tweaks, but all the problems everyone seems to be having is kinda putting me off so I guess I just need help.
Also there is a difference between unlocking boot loader and rooting, does the unlocking void warranty?
Click to expand...
Click to collapse
You have to unlock the boot loader in order to root. Personally at this time I would not root because of android L around the corner. With rooting, you can longer receive ota's. Yes it fun to tweak but if I were in your position I wouldn't....
Sent from my Nexus 5 using XDA Premium 4 mobile app
dec1153 said:
With rooting, you can longer receive ota's.
Click to expand...
Click to collapse
Not true. You can receive OTA's if rooted (read the OTA help-desk thread) However, what's the big deal about OTA's?
1) You can get a rooted rom flashed based on the latest build BEFORE you get the OTA
2) Much less to go wrong that way than with OTA.
I think too many people put too much importance in OTA updates. Its a poor method of delivery and not even quick
rootSU said:
Not true. You can receive OTA's if rooted (read the OTA help-desk thread) However, what's the big deal about OTA's?
1) You can get a rooted rom flashed based on the latest build BEFORE you get the OTA
2) Much less to go wrong that way than with OTA.
I think too many people put too much importance in OTA updates. Its a poor method of delivery and not even quick
Click to expand...
Click to collapse
Personally, I think that if you don't know how to update manually and are completely reliant on OTAs, then you shouldn't have root access in the first place because you don't know what you're doing.