Related
Hi, new Android user here.
I was trying to root my Nexus S phone yesterday and I'm having problems. There is a lot of rooting guides out there and I used one from xda and also one from unlockr.com. Managed to root the phone ok (I think), but everytime I flash a custom ROM, the phone won't start at all, it just sits at the boot up screen and repeats itself.
So I'm thinking, I should just start over again. So I flash the stock ROM from xda back to 2.3.1. Everything seems ok, the phone starts up... but it's always stuck on airplane mode and the phone itself doesn't even show stuff like IMEI, mac address anymore.
So now I figure I've probably messed the phone up enough and need help lol. How do I go about reflashing the stock ROM and getting my Nexus back to out of the box condition (Stock ROM and no custom bootloader)?? Any guides or step by step instructions would be very helpful.
Thanks
Did you wipe before flashing roms?
Sent from my Nexus S c",)
Maybe flashing the KB2 modem would help that but the 9020a came stock with 2.3.3 and not 2.3.1 so that could be it...I'm not sure but that software wasn't meant at all for ours so it could be part of the problem. But if I was you I'd take a look at this thread wich has all the stock software for your phone. Make sure you wipe everything in clockework and then flash the stock rom. http://forum.xda-developers.com/showpost.php?p=13123996&postcount=39
dsixda uploaded the stock backup and the stock recovery, you can read more at that link, good luck hope it helps
You can download the full stock ROM from the link below:
http://goo.gl/8P8vl
Move the zip file to sdcard. Boot into recovery and flash the ROM. It should get you back to stock 2.3.4 ROM, all locked.
jungbum said:
You can download the full stock ROM from the link below:
Move the zip file to sdcard. Boot into recovery and flash the ROM. It should get you back to stock 2.3.4 ROM, all locked.
Click to expand...
Click to collapse
that did the trick. thanks everyone, now time to try rooting and flashing ROM again!
hrm lol now trying to update it to 2.3.4, it downloaded the update, but on reboot i get the white triangle with ! in it :\
this phone is so messed now
edit: well now everything is ok again, wiped data, flashed with CM7 and now it says 2.3.4, go figure.
Let's say I want to flash a rom and made a backup thru CWM of my stock rom will I be able to keep root if I flash it back to the stock rom ?
II'm doing this cause I care most about no auto brightness issue than the actual advantage to go with a custom rom.
Thanks
Why don't you just root your stock ROM then? You need to be rooted to flash CWM recovery anyways..
rener78 said:
Let's say I want to flash a rom and made a backup thru CWM of my stock rom will I be able to keep root if I flash it back to the stock rom ?
Click to expand...
Click to collapse
If your ROM is already rooted, and you're restoring it from CWM, yes. If you're using fastboot to re-flash the stock ROM, no, you'll have to re-root it.
I'm kind of confused about what you're asking, though. Can you give more specific details? Are you going to flash a different ROM and try to flash the stock ROM, or parts of it, on top of the new ROM? I wouldn't do that unless you're very sure of what you're doing.
I unlocked the bootloader. Roms like Synergy, Bean, etc no longer boot (stuck on samusg scrreeen)
Any idea?\
confusedman112 said:
I unlocked the bootloader. Roms like Synergy, Bean, etc no longer boot (stuck on samusg scrreeen)
Any idea?\
Click to expand...
Click to collapse
What methode did you use to unlock it? I'm running the stock no nonsense rom and I belive unlocked with no problems
Do other roms boot? Will the newest CM10 nightly boot? Will anything boot?
Did you flash a different recovery? If you were using kexec roms before (beans is one, so is synergy with imo's kernel) and then flashed a non-kexec-supporting recovery, that'd explain not being able to boot. If you're unlocked, you don't have to flash a new recovery.
If you did the unlock correctly, you should be able to boot whatever you were able to before. If you can't get anything at all to boot, it's possible you flashed a bad aboot image.
lazarus2405 said:
Do other roms boot? Will the newest CM10 nightly boot? Will anything boot?
Did you flash a different recovery? If you were using kexec roms before (beans is one, so is synergy with imo's kernel) and then flashed a non-kexec-supporting recovery, that'd explain not being able to boot. If you're unlocked, you don't have to flash a new recovery.
If you did the unlock correctly, you should be able to boot whatever you were able to before. If you can't get anything at all to boot, it's possible you flashed a bad aboot image.
Click to expand...
Click to collapse
CM10 ROMs boot.
I think it's because I used CWM 5.x rather than 6.x. Phone isn't recongized by PC, no idea why. Any idae how to get 6.x using the terminal app in CM10 and wifi?
confusedman112 said:
CM10 ROMs boot.
I think it's because I used CWM 5.x rather than 6.x. Phone isn't recongized by PC, no idea why. Any idae how to get 6.x using the terminal app in CM10 and wifi?
Click to expand...
Click to collapse
Install EZ-Recovery from the play store and flash 6.0.1.0?
PJnc284 said:
Install EZ-Recovery from the play store and flash 6.0.1.0?
Click to expand...
Click to collapse
Thanks. Flashing Synergy now to test it...let's see what happens.
EDIT: Flashed just great, but still isn't working. But, it's cool, CM10 mods work and I got what I needed (exported Verizon contacts and improted them to Google Contacts using My Verizon's webstie)
confusedman112 said:
CM10 ROMs boot.
I think it's because I used CWM 5.x rather than 6.x.
Click to expand...
Click to collapse
Yep, that's exactly the problem. You installed a non-kexec recovery and your roms still use kexec.
You're sure you selected the right options in EZ recovery? Open it, scroll to the recovery pane, select the "recovery" radio button, change the drop down menu next to it to CWM 6.0.1.0, click the "Flash!" button. That should let you install whatever roms or kernels you like.
lazarus2405 said:
Yep, that's exactly the problem. You installed a non-kexec recovery and your roms still use kexec.
You're sure you selected the right options in EZ recovery? Open it, scroll to the recovery pane, select the "recovery" radio button, change the drop down menu next to it to CWM 6.0.1.0, click the "Flash!" button. That should let you install whatever roms or kernels you like.
Click to expand...
Click to collapse
Dang. How do I undo the bootloader unlock so I can redo it with the proper CWM?
confusedman112 said:
Dang. How do I undo the bootloader unlock so I can redo it with the proper CWM?
Click to expand...
Click to collapse
Being unlocked shouldn't have any impact on being able to flash using ez-recovery. One thing you can try is use EZ-Recovery to flash stock recovery, odin back to the stock verizon image which should relock the bootloader and start all over.
confusedman112 said:
Dang. How do I undo the bootloader unlock so I can redo it with the proper CWM?
Click to expand...
Click to collapse
why dont you take some time and read before flashing...this s*** is getting rediculous! Your questions are answered in multiple threads on this forum. Actually I just answered your question in a thread right below this!! Sorry not trying to be a ****...sigh.
droidstyle said:
why dont you take some time and read before flashing...this s*** is getting rediculous! Your questions are answered in multiple threads on this forum. Actually I just answered your question in a thread right below this!! Sorry not trying to be a ****...sigh.
Click to expand...
Click to collapse
Because I am at work and don't have time to find and locate? Could you reference it, please?
PJnc284 said:
Being unlocked shouldn't have any impact on being able to flash using ez-recovery. One thing you can try is use EZ-Recovery to flash stock recovery, odin back to the stock verizon image which should relock the bootloader and start all over.
Click to expand...
Click to collapse
Why do you need to flash stock recovery to use Odin to flash stock Verizon rom? Odin has nothing to do with what recovery you have installed. I flashed stock unrooted rom while rooted and having CWM recovery, it worked just fine. Once you flash stock rom, it restores the stock recovery too anyway. I'm fairly sure of this, but if I'm wrong, please correct me anybody.
newuser134 said:
Why do you need to flash stock recovery to use Odin to flash stock Verizon rom? Odin has nothing to do with what recovery you have installed. I flashed stock unrooted rom while rooted and having CWM recovery, it worked just fine. Once you flash stock rom, it restores the stock recovery too anyway. I'm fairly sure of this, but if I'm wrong, please correct me anybody.
Click to expand...
Click to collapse
Just to be safe. Wanted to get rid of the sprint related elements from the original root so I Odin'd back to stock with cwm installed using the VRALF2 tar found here. Tried to boot into recovery to factory reset prior to first boot and had 0 recovery (not stock nor cwm). Luckily the rom booted and I used the simple root method to root and install EZ-Recovery to install CWM.
If I flashed synergy v1.7 and used rom manager v5.x.x and then unlocked the boot loader how would I flash a new rom? Do I have to use ez recovery with clockwork mod v6.x.x since it is now unlocked or can I continue using rom manager with clockwork mod 5.x.x. I'm a noob and won't be looking to switch roms until synergy gets jellybean. Thanks for the help and hopefully I made sense with my question
synergy to beans to synergy bootloop
I think my issue might be related to the issues stated above.
So after after having unlocked my bootloader with EZ unlock & installing beans custom Rom via TWRP , I decided to go back to synergy. I made a nandroid of my synergy which was origianlly installed with CWM and figured I could just wipe and restore that with TWRP. Total bootloop.
OK, so I pulled the battery, tried it again...bootloop.
SO I pulled the battery, wiped and installed the synergy zip thinking I could try a fresh install. I got a message in TWRP that E:sd-ext was not found, but wipe seemed to happen so I continued the process.
installation said it was successful but now when I try to boot up, I either get stuck in the android is upgrading applications (looping over and over) or it gets through there and tells me all teh com.android.xxxx applications unexpectedly stop.
is this a soft brick? can I recover from this? are there incompatibilities between the kernels of bean's custom rom and synergy for verizon samsung galaxy s3?
Hi to All,
I want to share my experience about revert to stock for users that have new HBOOT, unlocked bootloader and custom recovery; can't execute official RUU. ( This method i think is more safe that downgrade HBOOT )
Step ONE:
Install this custom ROM: MaximuS ROM ( read the thread for instruction about installation of this ROM )
( this ROM allow you to receive the message of OTA JB update, if you know another ROM that receive this message you can use as well i think )
Step TWO:
install the stock recovery of HTC One S via fastboot ( after flashing recovery erase cache )
Step THREE:
Reboot your phone in system, configure the rom for first use, go to settings, information, software update and press check now for update.
You'll receive the message for an update, download and install, and now you have stock JB ROM. after reboot you can do a reset ( go to setting => backup and restore ) to clean the application migrated from previous ROM ( MaximuS )
I hope this can help someone else.
p.s. Sorry for my English!
Thanks bro for this, but my problem is not resolved because this rom couldn't install on my HTC One S, i dont know why... Log show me: MD5 files not found
CybulPL said:
Thanks bro for this, but my problem is not resolved because this rom couldn't install on my HTC One S, i dont know why... Log show me: MD5 files not found
Click to expand...
Click to collapse
Witch recovery are you using at the moment? I installed this ROM ( MaximuS ) with Team Win Recovery ( TWRP ) v2.3.3.0 and it's works for me.
( after flashing ROM from recovery remember to flash boot.img by fastboot )
Maverick87Shaka said:
Witch recovery are you using at the moment? I installed this ROM ( MaximuS ) with Team Win Recovery ( TWRP ) v2.3.3.0 and it's works for me.
( after flashing ROM from recovery remember to flash boot.img by fastboot )
Click to expand...
Click to collapse
I use TWRP and CWM and the same. My mate told me that i have unmount 1 and 2 partition in recovery but i don't know how.
Hi everyone,
thanks a lot, this saved my ass ... I had upgraded my stock ICS to stock JB and then tried to go back to stock ICS with a CWM backup - with the result that I had a brick booting only to a black screen.
I still had access to CWM recovery and so could install the Maximus 2.5 ROM and also the update to stock JB ran through just fine.
I did a factory reset afterwards, is it 100% sure that I now have a pure stock JB or could there be some leftovers from the Maximus 2.5 ROM?
Cheers,
Tim
tim_h said:
Hi everyone,
I still had access to CWM recovery and so could install the Maximus 2.5 ROM and also the update to stock JB ran through just fine.
I did a factory reset afterwards, is it 100% sure that I now have a pure stock JB or could there be some leftovers from the Maximus 2.5 ROM?
Cheers,
Tim
Click to expand...
Click to collapse
Yes you have a stock JB, because with factory reset you've removed all extra application that there is inside MaximuS v.2.5.
All other unneeded file or executable ( like root executable and all other script in /system ect. ) was removed during installation of new ROM.
Remember just that you need to revert to stock to give your phone back to HTC for guarantee, I thinks you must leave on it the stock recovery.
tim_h said:
Hi everyone,
thanks a lot, this saved my ass ... I had upgraded my stock ICS to stock JB and then tried to go back to stock ICS with a CWM backup - with the result that I had a brick booting only to a black screen.
Cheers,
Tim
Click to expand...
Click to collapse
It's happened because from recovery the system was unable to flash the boot partition. So after you did the CWM restore, you have all the phone with ICS android, but JB kernel, this cause your black screen after boot!!!
If you have the boot.img ( with suitable kernel of your old ROM ) to flash after you did the CWM recovery, you can get back to your BACKUP without any problem.
Also if you don't have the exactly boot.img of your previous ROM of the backup, you can flash any boot.img by fastboot of ICS kernel and this is should be enough to keep your backup running again.
Thanks very much for the additional explanations. I do have the boot.img of my original CWM backup, so should be able to restore it via fastboot. Great!
But first I have to send in my phone to have the USB port fixed under warranty.
Holy ****, is working, thanks man...
zujko said:
Wait to see if i understood, i have now Custom ( Virtuous Ville+ RC-1) JB ROM, with hboot 2.15.0000... unlocked, root, twrp
1.install maximuS V2.5, wipe..
2. flash boot.img with fastboot
3.Check update for JB, and flash new update JB?
And that's it?
I guess we have to make relock bootloader, after flash ICS?
Tnx
Click to expand...
Click to collapse
You just forgot in the list to install the HTC Stock recovery before check the message of update, so:
1 => Wipe and install MaximuS V2.5 ROM
2 => flash with fastboot boot.img of MaximuS V2.5 ROM
3 => flash stock HTC Recovery via fastboot ( fastboot flash recovery ville_recovery_signed.img , then fastboot erase cache ) or get it from One_S_All-In-One_Kit_v1.0
4 => start the phone and check for the JB update
5 => after JB installation do a factory reset to clean up the ROM from the extra application that MaximuS ROM have.
You don't need to relock your bootloader, you just need to install the stock recovery, that's enough.
Hmm, wait, why need install stock recovery?
This JB will be working with custom twrp?
EDIT: I got it
I did it! I unmounted first 3 partitions in TWRP and installation successful.
I am on stock Rom now and used HTC offical update to get to jb...do u think I will have trouble rooting again?
Sent from my HTC One S using xda premium
k1llacanon said:
I am on stock Rom now and used HTC offical update to get to jb...do u think I will have trouble rooting again?
Sent from my HTC One S using xda premium
Click to expand...
Click to collapse
I will let you know if I can get it working and flashed it will be rooted in seconds just need stock recovery.
Rooted without a problem, recommend the attached superuser app.
Maverick87Shaka said:
You just forgot in the list to install the HTC Stock recovery before check the message of update, so:
1 => Wipe and install MaximuS V2.5 ROM
2 => flash with fastboot boot.img of MaximuS V2.5 ROM
3 => flash stock HTC Recovery via fastboot ( fastboot flash recovery ville_recovery_signed.img , then fastboot erase cache ) or get it from One_S_All-In-One_Kit_v1.0
4 => start the phone and check for the JB update
5 => after JB installation do a factory reset to clean up the ROM from the extra application that MaximuS ROM have.
You don't need to relock your bootloader, you just need to install the stock recovery, that's enough.
Click to expand...
Click to collapse
Will this work on a T-Mobile HOS with CID HTC__001?
I have followed all the steps from above
- installed the rom
- installed the stock recovery
- then I was able to start the update but when it finished downloading .. I was told that the HTC software on my device has been modified and please revert back and try the update again and it would not preform the update.
What am I doing wrong?
Thanks in Advance
Hi once more,
after going back to pure stock JB this way, can I relock the bootloader to get "RELOCKED" instead of "UNLOCKED/TAMPERED"? (That would be good for sending in my phone under warranty.) Or will the phone stop booting if I relock the bootloader?
As far as I understood, the "canonical" way to get "RELOCKED" would be to lock the bootloader and install the RUU, but since there is no RUU for the unbranded JB yet and downgrading with an older RUU is not possible, I cannot do this.
Cheers,
Tim
tim_h said:
Hi once more,
after going back to pure stock JB this way, can I relock the bootloader to get "RELOCKED" instead of "UNLOCKED/TAMPERED"? (That would be good for sending in my phone under warranty.) Or will the phone stop booting if I relock the bootloader?
Cheers,
Tim
Click to expand...
Click to collapse
You can do Relock bootloader, i think it will boot to system without problem(?)
blah blah blah said:
Will this work on a T-Mobile HOS with CID HTC__001?
I have followed all the steps from above
- installed the rom
- installed the stock recovery
- then I was able to start the update but when it finished downloading .. I was told that the HTC software on my device has been modified and please revert back and try the update again and it would not preform the update.
What am I doing wrong?
Thanks in Advance
Click to expand...
Click to collapse
+ 1
Sent from my HTC One S using xda app-developers app
The only word of caution that I think needs to be shared on almost all threads related to JB updates is to make sure you DO NOT have SuperCID... There have been numerous reports of phones bricking with the OTA JB update with a SuperCID... So if you had previously SuperCID your phone with 11111111, definately change it to something else.
AKToronto said:
The only word of caution that I think needs to be shared on almost all threads related to JB updates is to make sure you DO NOT have SuperCID... There have been numerous reports of phones bricking with the OTA JB update with a SuperCID... So if you had previously SuperCID your phone with 11111111, definately change it to something else.
Click to expand...
Click to collapse
I had to go supercid to run the euro ruu and changed it to HTC__001. Ota still didn't work
Sent from my HTC One S using xda app-developers app
Ok, so got my new XL today, and already want to flash it, can't stay away. lol. Used to all the steps and software and everything from my other phones, but want to go through the steps here first before I flash serajr's ROM. Read his steps, the part I'm not sure on this phone is how to get recovery on.
Ihave flash tools downloading, the current highest stock fw, and his files.
So I have to update to the latest stock first with flashtools and the ftf file.
???? Install recovery.
Flash his 2 files in recovery.
I have no problem in CWM/TRWP/AROMA scripts, etc, just not just how to get a recovery on this phone.
Also, what do I have to do with flashtool to start flashing? Is there a download mode for the XL?
Lastly, no problems flashing the latest stock overtop of the Wind mobile version? It's the C2104, but I'm on the A1 version still and Wind shows no updates available.
I got into flashmode once and now I can't again. Is it vol down and plugging in the usb at the exact time you press down?
New USB cable and a battery pull helped get me into flash mode. Got the A2 stock flashed, waiting on first boot, read it will take a long time for the first boot. Flash looked good though, no errors in flashtool. Like using Heimdall for sammy.s.
Ok, stock boots fine. Can't seem to flash a kernel with cwm. Do i need unlocked bootloaders for that?
Got the latest stock running, can't seem to flash vengence/thunderzap to get CWM.
Do I need to unlock boothloaders to flash the kernels so I have cwm so I can flash segarjr's packages, then flash the stock kernel back if I want wifi working, etc?
getochkn said:
Got the latest stock running, can't seem to flash vengence/thunderzap to get CWM.
Do I need to unlock boothloaders to flash the kernels so I have cwm so I can flash segarjr's packages, then flash the stock kernel back if I want wifi working, etc?
Click to expand...
Click to collapse
You will have to unlock bootloader to flash kernel.
Flash custom kernel containing CWM.
Flash your Rom.
Then again flash stock extended v2 kernel.
Done!
Always flash kernel through flashtool.
Switch off ur phone then connect to usb pressing volume up. It will enter fastboot mode and notification light will glow in blue colour.
Then flash
Done!!!!!
Sent from my C2104
Thanks but I think I'm screwed, I get
"Bootloader unlock not allowed"
So I can't unlock my bootloader to flash a custom kernel. Gonna suck if there is some good dev on this phone. lol.
getochkn said:
Thanks but I think I'm screwed, I get
"Bootloader unlock not allowed"
So I can't unlock my bootloader to flash a custom kernel. Gonna suck if there is some good dev on this phone. lol.
Click to expand...
Click to collapse
Oh! Very sad!!
Wait till CWM comes!
Anyway, You can root, deodex your Rom to add some mods
You can also use 'Flash Gordon' to flash anything but Rom..
Sent from my C2104