Related
Hi guys,
I was trying to unroot my nexus S using the guide found here (http://forum.xda-developers.com/showthread.php?t=1088494&highlight=unroot)
After clicking start on odin, it started to do its thing and then it failed all of a sudden. and now im stuck on the yellow triangle Downloading screen. I press and hold power nothing happens. i dunoo what to do. I am a complete noob. someone please help. I am attaching the image of the what the screen looks like (http://postimage.org/image/3dhtlidg/)
and here what odin looks like now (http://postimage.org/image/3eqh3vpg/)
ok guys, i took out the battery and put it back on and turned it on again and it powered on but now i have no signal or empty bars. it shows aeroplane now.. i tried different sims no difference.. i get no service.. i think this odin fail at radio damaged my radio somehow..someone please advise me.. please .. i did volume up button + power and tried to go to recovery but i get triangle with exclamation mark. so i took out the battery and reboot it to normal. no signal. just the aeroplane icon. Also when i put the phone in USB mode, i see folders like clockworkmod and im able to see my back up that i made before doing all this. However not able to access it in the phone. I also see that all my apps and everything is gone, but i still some apps folders in the usb mode. what should i do?
First, your link goes to a NxS 4G guide, but you state you got a NxS (non-4G). Which one you got?
Following is for the __NxS only__ (as I have no experience with the 4G):
If a little Droid is holding the "triangle with exclamation mark" then that is normal as you're accessing the stock recovery, press vol up + power again to see the recovery.
Once done that go here and get a full rom flashable zip for your device. Get a "signed" version if available as those are flashable via stock recovery. (*) Put the zip on your sdcard, reboot into recovery again, wipe everything the options allow you to, install zip from sdcard, reboot. You're done with an unrooted, stock phone.
If there's no "signed" you gotta flash the cwm recovery via fastboot first (USB drivers seem to be working and your phone is recognized). Go mount and storage and choose "Mount USB storage" Then continue after the (*) and leave out the reboot after putting the zip on your sdcard.
yeh crap i just realized.. i used the guide for nexus s 4g.. i have the gsm model (non-4g). from here in canada. damn i feeel so stupid... fml..
ok so behind the battery the sticker says my phone model is I9020A and then I went to the page yu asked.. and i found the following two of interest.
Android 2.3.4/GTJ61/UCKE1 Radio/KA3 Bootloader
Works on: I9020A
Unofficial, unsigned, must flash through ClockworkMod Recovery. Contains recovery, radio and bootloader.
Courtesy of XDA forum member scott8281
Android 2.3.4/GRJ22/XXKD1 Radio/KA3 Bootloader
Works on: I9020T, I9023
Official, signed, can flash with ClockworkMod or stock recovery. Contains recovery, radio and bootloader.
My phone before all this mess occured was on GRJ22 build. So can i use the 2nd one here since its official and signed whereas the first one is unsigned. and like u suggested i should try to find a signed rom.
next question, how do i "wipe everything the options allow you to" ..
also when i do vol up + power and scroll to recovery and press power.. google logo comes up and then the droid with white triangle that has exclamation mark. I just cannot load into recovery :$
sorry for being so noob at this :$ But thanks for helping...
Breathe.
No, you cannot use the second flash "Android 2.3.4/GRJ22/XXKD1 Radio/KA3 Bootloader" This is not for the I9020A variant.
I can tell you how to get everything back to stock. Are you willing to unlock the bootloader? There is no full signed rom for the I9020A.
You need to:
http://wiki.cyanogenmod.com/wiki/Nexus_S:_Full_Update_Guide#Unlocking_the_Bootloader
http://wiki.cyanogenmod.com/wiki/Ne...de#Installing_the_ClockworkMod_Recovery_Image
Then install
http://forum.xda-developers.com/showthread.php?t=1033269
Then update back to 2.3.4
http://android.clients.google.com/p...5b.signed-sojua-GRJ22-from-GRI54.286d814d.zip
Then lock the bootloader.
Oh okay. yes please I am willing to do anything to get this phone working to normal. and by the way, when i do volume up+power, i see locked stated - unlocked. doesn't that mean my bootloader is already unlocked. I also see the lock icon along with google when i turn on the phone.
cool6324 said:
You need to:
http://wiki.cyanogenmod.com/wiki/Nexus_S:_Full_Update_Guide#Unlocking_the_Bootloader
http://wiki.cyanogenmod.com/wiki/Ne...de#Installing_the_ClockworkMod_Recovery_Image
Then install
http://forum.xda-developers.com/showthread.php?t=1033269
Then update back to 2.3.4
http://android.clients.google.com/p...5b.signed-sojua-GRJ22-from-GRI54.286d814d.zip
Then lock the bootloader.
Click to expand...
Click to collapse
okay so basically i start following the guide from the point it says Installing the ClockworkMod Recovery Image since my bootloader is already unlocked.
one question though, right now when i connect my phone through usb, i am able to see the folder such as clockworkmod in sd card, so if im installing clockworkmod recovery, am i just reinstalling this again?
also for flashing cyanogen mod, i would choose the "method via recovery" right since my phone is not really rooted right now. I don't have the ROM manager app. Thanks a lot cool6324
The rom has to be for your phone. If your phone is an i9020A you got to take the first one you marked red.
@cool6324, I think his phone's bootloader is unlocked as his phone was rooted before and later then 2.3.x, means no Gingerbreak to avoid unlocking the bootloader.
---
forpulse, you got ADB set up and ready to go? (If not go to: http://theunlockr.com/2009/10/06/how-to-set-up-adb-usb-drivers-for-android-devices/ to learn how to set it up)
If yes, download the rom to your pc. Also download the cwm recovery here. Boot phone into Android. Copy the rom on your sdcard (needs to be in the top folder). Copy the cwm recovery into the \tools (see below, (*))
Keep your phone connected via USB to your pc. Unmount the sdcard (the Droid got to be green not orange anymore), make sure you activated "USB Debugging" in settings (not sure of the right english terms should be in: "Apps/Programs" > Development). Now start a command prompt (windows key + r, then type "cmd", hit enter). (*)Navigate to the \tools inside ADB/SDK folder you created already or created by following the unlockr guide I linked above. To navigate simply type "cd <drive letter>:\<folder name>\tools and confirm with enter. Once inside the right folder you can start using the following commands:
adb devices (this should return you your device's id)
adb reboot bootloader (this takes a few secs and your phone will boot into bootloader menu)
fastboot flash recovery <recovery image name>.img (this should return a time and an "OK")
Now you can continue on your phone:
Navigate into recovery
Wipe > Factory reset, cache and dalvik cache
Mount and Storage > format system/boot
Install zip from sdcard, choose the ROM's name, install, confirm
"Go back" until you can choose "reboot system now", phone should boot into unrooted, stock Android now.
---
one question though, right now when i connect my phone through usb, i am able to see the folder such as clockworkmod in sd card, so if im installing clockworkmod recovery, am i just reinstalling this again?
Click to expand...
Click to collapse
That clockworkmod folder contains so called "Nandroid backups". This contains a full backup of your phone (__if__ you made one).
Did you make one before messing up your phone? If yes, follow my guide above to the point your going into recovery and just hit "backup and store", "restore" instead of flashing a new rom. I'd recommend to "wipe" "factory reset", "cache" and "dalvik cache" before though.
rentaric said:
The rom has to be for your phone. If your phone is an i9020A you got to take the first one you marked red.
@cool6324, I think his phone's bootloader is unlocked as his phone was rooted before and later then 2.3.x, means no Gingerbreak to avoid unlocking the bootloader.
---
forpulse, you got ADB set up and ready to go? (If not go to: http://theunlockr.com/2009/10/06/how-to-set-up-adb-usb-drivers-for-android-devices/ to learn how to set it up)
If yes, download the rom to your pc. Also download the cwm recovery here. Boot phone into Android. Copy the rom on your sdcard (needs to be in the top folder). Copy the cwm recovery into the \tools (see below, (*))
Keep your phone connected via USB to your pc. Unmount the sdcard (the Droid got to be green not orange anymore), make sure you activated "USB Debugging" in settings (not sure of the right english terms should be in: "Apps/Programs" > Development). Now start a command prompt (windows key + r, then type "cmd", hit enter). (*)Navigate to the \tools inside ADB/SDK folder you created already or created by following the unlockr guide I linked above. To navigate simply type "cd <drive letter>:\<folder name>\tools and confirm with enter. Once inside the right folder you can start using the following commands:
adb devices (this should return you your device's id)
adb reboot bootloader (this takes a few secs and your phone will boot into bootloader menu)
fastboot flash recovery <recovery image name>.img (this should return a time and an "OK")
Now you can continue on your phone:
Navigate into recovery
Wipe > Factory reset, cache and dalvik cache
Mount and Storage > format system/boot
Install zip from sdcard, choose the ROM's name, install, confirm
"Go back" until you can choose "reboot system now", phone should boot into unrooted, stock Android now.
---
That clockworkmod folder contains so called "Nandroid backups". This contains a full backup of your phone (__if__ you made one).
Did you make one before messing up your phone? If yes, follow my guide above to the point your going into recovery and just hit "backup and store", "restore" instead of flashing a new rom. I'd recommend to "wipe" "factory reset", "cache" and "dalvik cache" before though.
Click to expand...
Click to collapse
Yes, i do have ADB set up ready to go but if I understood your right. Do I follow what your saying after following cool6324's guide or don't follow that and do what u suggest. I have not yet started out on his suggestion as I was reading everything and trying to understand. Also, when i go to download the CWM recovery. it says NS4G, so is this again for the sprint 4G model? or it also works on non-4g model which is what i have. I am just confirming this since I don't want to make the same mistake as above. :$
forpulse said:
Yes, i do have ADB set up ready to go but if I understood your right. Do I follow what your saying after following cool6324's guide or don't follow that and do what u suggest. I have not yet started out on his suggestion as I was reading everything and trying to understand.
Click to expand...
Click to collapse
The linked guide's result is equal to mine if you don't flash the CyanogenMod, but the rom cool6324 linked. Just make sure you get a full rom for _your_ device this time
rentaric said:
Copy the rom on your sdcard (needs to be in the top folder). C
Click to expand...
Click to collapse
which top folder are u talking about. is it ".android_secure" ? and I don't extact the ROM zip file right? i just put that directly in "top folder" ? and just to make sure i'm using "Stock-GTJ61-I9020A-Unsigned"
(100mb) found from one of your earlier links.
When I went to download CWM recovery from ur provided link, I saw different ones.. is it only for colour different purposes or there is actually a valuable difference amongst them? or do i download them all... i sound so stupid right now asking such questions:$
I'm really sorry If I am frustrating you with these stupid questions.. i've only had this phones for 2 days and its my first time with android... but thanks again...
forpulse said:
which top folder are u talking about. is it ".android_secure" ? and I don't extact the ROM zip file right? i just put that directly in "top folder" ? and just to make sure i'm using "Stock-GTJ61-I9020A-Unsigned"
(100mb) found from one of your earlier links.
When I went to download CWM recovery from ur provided link, I saw different ones.. is it only for colour different purposes or there is actually a valuable difference amongst them? or do i download them all... i sound so stupid right now asking such questions:$
I'm really sorry If I am frustrating you with these stupid questions.. i've only had this phones for 2 days and its my first time with android... but thanks again...
Click to expand...
Click to collapse
Good morning.
Yes, the difference between those recoveries is just color of text. !!Don't get the 4G version!!
The top folder is the one you access when the usb storage pops up on your pc. The zip file goes in there unextracted.
File size seems correct for a full rom.
Sent from my Nexus S using XDA App
rentaric said:
Good morning.
Yes, the difference between those recoveries is just color of text. !!Don't get the 4G version!!
The top folder is the one you access when the usb storage pops up on your pc. The zip file goes in there unextracted.
File size seems correct for a full rom.
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
Good Morning,
Alrighty, I think I have understood everything now, although, I'm at work right now so I will begin the process 8 hours later today and get back to you with the results... thanks for being so patient...
Hey rentaric,
i followed your guide and im delighted to say that my phone is back to normal or at least i think so lol.. everything is worked out and so far the phone is running fine. i made calls and what not.. the only issue i got now is... auto-rotate does not work. i cannot type text in landscap mode even though i got auto-rotate checked in display settings.. even in gallery, photos do not auto-rotate.. pretty much auto-rotate does not work whether i turn it on or off :S ..would you happen to anything about this? nonetheless, thank you so much for helping me out..
forpulse said:
Hey rentaric,
i followed your guide and im delighted to say that my phone is back to normal or at least i think so lol.. everything is worked out and so far the phone is running fine. i made calls and what not.. the only issue i got now is... auto-rotate does not work. i cannot type text in landscap mode even though i got auto-rotate checked in display settings.. even in gallery, photos do not auto-rotate.. pretty much auto-rotate does not work whether i turn it on or off :S ..would you happen to anything about this? nonetheless, thank you so much for helping me out..
Click to expand...
Click to collapse
Glad to hear it worked out for you to some degree. Sadly I have no solution to the not workign sensor part. See, I'm not pro myself, I'd just try widgetsoid app first. It got an rotate on/off function in its widget, if that wouldn't work for me I'd prolly flash another rom to see if it's the sensor trying to bully me. In the end hardware failures are still a possibility even on teh NxS.
sounds good.. no worries... i have a feeling this phone might have a defective sensor since it did not work also before with the older ROM which was GRJ22 xxkd1 ... but anyway i'll search/ask around if anyone knows anything... thanks again man...
Dear forum,
I kind of hesitated to start a thread for my problem, but after a long time I still haven't found a solution. I have contacted HTC (no answer yet), but hope to resolve my problem in meanwhile instead of waiting 1 month+ for a replacement.
I got the -by now familiar- freeze, and after rebooting it would go beyond the HTC logo, then stay stuck in a backlit black screen mode. Tried removing the battery, sim card, sd card etc. Then decided to boot into recovery (vol down + power) which worked, but any option would freeze the phone, like factory reset which I tried first.
Right now, the phone already freezes at the carrier logo, and I can't even get into recovery again (vol down + power). The phone won't respond to the key presses, and eventially boot and freeze at the carrier logo. The weird thing is that before, after a lot of trying and re-inserting the battery, it would eventually boot and work just fine for about 1 in 10 tries.
Does anyone have any ideas what I could try? Any help would be greatly appreciated!
edit: Okay, after a while I finally managed to get into HBoot again! Now what should I do to get my phone resetted/fixed? I guess it's not possible for me to flash another ROM or something as i'm not rooted. Details shown are: S-OFF, HBOOT 98.0002
can you get into recovery from bootloader?
Seems like I now consistently can boot into HBOOT. When I choose recovery, it will reboot, show the carrier logo, show the green logo with circular arrows, and then switch to the phone logo with a red exclamation mark for two seconds. Then, it shuts off. Also, when I tried that just now, it buzzed for like 6 times very fast after turning off.
On the second try, exactly the same happened: red exclamation mark, screen off, +- 6 fast buzzes.
After doing that, it doesn't respond to vol down+power or power at all. After reinserting the battery, I can get back into HBOOT
edit: it didn't want to boot into HBOOT, but now it does again. Anyhow, chosing recovery is still green logo, red logo, screen off and some buzzes. The phone doesn't show up in "adb devices" neither.
Whatever you are going to do; do not root your device as it will void your warrenty.
Is there anything else i can try doing? The situation so far:
-normal boot just stays stuck into carrier logo
-hboot->recovery gives a reboot, green logo, switch to red logo, screen off and +- 6 fast buzzes, then nothing. Needs battery reinsertion to be able to respond to vol down + power again
-hboot->factory reset just freezes on the same screen, no response, needs battery removal
-noshow in adb devices (update: show in fastboot!)
Another update: after messing arround with the drivers which didn't seem properly installed, I know have my device showing up in "fastboot devices".
Please, I feel like I'm so close to fixing this. What could I do next? Fastboot in some different recovery with more options or something? Anyone?
Could I simply run the RUU for my 3UK branded phone now?? If I get the RUU from http://forum.xda-developers.com/showthread.php?t=1002506, it seems that the RUU is "signed", which would result in S-ON? While right now my phone is S-OFF?
edit: So, I ran the proper RUU, it will find my device, propose me to downgrade from 1.47 something to 1.37 or so. Click next. Then it stays on the "rebooting the bootloader" phase indefinitely
maxxur said:
Another update: after messing arround with the drivers which didn't seem properly installed, I know have my device showing up in "fastboot devices".
Please, I feel like I'm so close to fixing this. What could I do next? Fastboot in some different recovery with more options or something? Anyone?
Could I simply run the RUU for my 3UK branded phone now?? If I get the RUU from http://forum.xda-developers.com/showthread.php?t=1002506, it seems that the RUU is "signed", which would result in S-ON? While right now my phone is S-OFF?
edit: So, I ran the proper RUU, it will find my device, propose me to downgrade from 1.47 something to 1.37 or so. Click next. Then it stays on the "rebooting the bootloader" phase indefinitely
Click to expand...
Click to collapse
Slow down maxxur, wait for this quesstion to be out there for long enough for someone to answer it.
Dont go on a battery pulling spree, coz that is the first and most tempting response on a frozen phone. But i hope you know what that can do to this phone...
Give the xda community some time to figure this out. Hold your ground till then. Need to go in to the theatre now. Will get back in the evening and try to figure this out.
Try running the RUU while in the fastboot menu (usb mode). Also my suggestion is not to make the process more complicated by downgrading - just reflash 1.47...
Thanks for the response guys
The RUU I found was 1.37. Could you point me to a 1.47 RUU for the 3UK network?
Also, running that RUU when in Fastboot USB mode is what I tried. The info on the RUU shows that it hangs indefinitely at "rebooting bootloader". That is expected, as when I try to manually reboot bootloader in my fastboot menu, my phone will also freeze.
I'm wondering if running a different recovery image could be of any help? Last night I tried running CWM recovery to see my options, by entering "fastboot boot recovery.img" but i'd get a "remote: not allow" error.
Have not noticed that you are not rooted!
Why don't you try the revolutionary tool? If you have luck it will restore your bootloader if it is broken (keep in mind that is not the best option because it will break you warranty). Then you will just need to flash an eng hboot and run the RUU, or better try some custom ROM
But in my opinion the best option for you is to go for a replacement rather to try yourself, since you dont have any custom software on it it has to be covered by your warranty (probably it is a faulty device to go like this from nothing).
Thanks for the suggestion. Are there any other safer options for me?
Could I try extracting the rom.zip from the RUU and manually put it on the SD card, then try to flash it in CWM recovery? Since "fastboot boot recovery" doesn't work though, could I try "fastboot flash recovery" to get CWM on there? Atm the "stock recovery" seems to be dead anyway, as when I choose it in HBOOT, the phone simply freezes.
maxxur said:
Thanks for the suggestion. Are there any other safer options for me?
Could I try extracting the rom.zip from the RUU and manually put it on the SD card, then try to flash it in CWM recovery? Since "fastboot boot recovery" doesn't work though, could I try "fastboot flash recovery" to get CWM on there? Atm the "stock recovery" seems to be dead anyway, as when I choose it in HBOOT, the phone simply freezes.
Click to expand...
Click to collapse
Of course you can if you are eager to try this. When you run the RUU, even when there is no phone connected there is a folder in your C: drive created (I assume that you are using Windows). Open your Windows Explorer and search for the rom.zip. When you have it copy it somewhere and close the RUU screen. Then if you open the RUU all the *.img files are there. You can try flashing the stock recovery or hboot or whatewer using the fastboot command. But I have to say again the best option for you is to bring the phone for a repair before you end up with something irreversible and void your warranty.
Thanks for keeping me sane on what to do with my problem Mentally, I came to the point where I'd go flash CWM recovery on my phone and try to flash that RUU rom from there, but you helped me get around that thought and now I made arrangements for HTC to come and pick it up. I'll keep you guys posted!
PS: you've got to love our desire s community, it's the best.
Cheered too early
Now HTC suddenly responds that while entering my phone in their warranty service thingy and the phone seemed to be 3G UK branded, they told me they "can't" do repairs for those.
Seriously, HTC is trying to troll me saying the inner hardware could differ between a UK and a Belgian Desire S?? Could this be true in any way?? :/
Maybe some parts are cheaper but with the same parameters...but I thought that when you have a branded phone you should seek your warrancy support from the carrier's office?!?
Sent from my HTC Desire S
Options for solution!
Option 1: Copy rom.zip (from RUU_Saga_HTC_Europe_1.47.401.4_Radio_20.28I.30.085AU_3805.06.02.03_M_release_199410_signed) to your sd rename it to PG88IMG.zip and let m boot into hboot.
If option 1 is not ok try option 2.
Option 2: Boot in to fastboot connect it to your computer and on your computer open dos/terminal run fastboot oem rebootRUU then after that run ruu RUU_Saga_HTC_Europe_1.47.401.4_Radio_20.28I.30.085AU_3805.06.02.03_M_release_199410_signed.
If option 2 not OK then there is option 3.
Option 3: Boot in to fastboot connect it to your computer and on your computer open dos/terminal run fastboot oem rebootRUU after that run in dos/terminal fastboot flash zip rom.zip (extracted from RUU_Saga_HTC_Europe_1.47.401.4_Radio_20.28I.30.085AU_3805.06.02.03_M_release_199410_signed)
Let me know if one of these option worked for you if not I can help you with reflashing your hboot again.
NikMel,
Thank you so much for the tips. Currently I'm trying the first HBOOT + .ZIP method. It detected it, asked me to update and is now showing a pink "Updating" sign. How long should this normally take? I have a strong feeling it simply froze again, and it really turns out to be a hardware problem.
Is that updating next to radio?
If yes it will take realy long so wait!!
Hey guys,
Forgive me for being frantic and (probably) not taking the steps needed to research this issue, or not taking the time to do so, but I'm sure you can all presumably imagine -if you've not been in this situation before- that it SUCKS not having a phone in this day in age...
My problem: Atrix 2 (Rooted + CWM Recovery) now won't boot passed the "M" Motorola logo upon start up. It won't even allow me to access the factory Android Recovery by holding down Volume Up, Volume Down, and Power. I think I inadvertently bricked the phone? (Hope not!)
Further, the "M" Motorola logo is skewed in appearance, like its not even loading correctly. I'm not sure what to do. This is my first time rooting and getting experienced with custom ROMS.
Anyone able to help this helpless sap?
Thanks is advance to your replies...
Step 1 is where you tell what you did to get into the state you are in. You wouldn't believe how far it goes toward fixing something if you know how it got broken.
Sent from my MB865 using XDA
If you have CWM recovery on boot can't you just do a battery pull? You do NOT want to let that thing bootloop forever until the battery dies.
The End.
KEB64 said:
If you have CWM recovery on boot can't you just do a battery pull? You do NOT want to let that thing bootloop forever until the battery dies.
The End.
Click to expand...
Click to collapse
Agreed pull the battery. If you run out of juice you'll be in some serious trouble.
Did you try to flash the fkz? Unless you have CWM on Boot it's the only way you can get your phone working.
Okay, sorry for not giving a full rundown on what stupidity on my part cause all of this. Let me start by saying that (sadly) I am a great big n00b when it comes to Linux, and I thought that despite my research online I would sort of explore the CWM Recovery 'Advanced' sections.
I downloaded ROM Toolbox from the Play Store, and installed a custom boot animation, and replaced -or thought I was- the startup "M" logo with something else. This is what concerned me: After re-booting, the "M" logo was all crazy looking, with a "stretched" "M" logo over the top of the "regular" logo.
So, I uninstalled the app, but the logo was still all messed up. So, I used Root Uninstaller to get rid of the ROM Toolbox files, still no resolve to the crazy boot logo.
So, I went into CWM Recovery Advanced, and wiped everything. The Dalvik, cache, System, Data, etc... didn't think that it would -what appears to have happened- wipe out the OS on the phone.
I tried pulling the battery, and re-booting, won't boot passed the skewed "M" logo still. Tried getting into Android Recovery, and it looks to go through the recovery goes through its thing, but never boots normally afterward.
Sorry for being such an idiot, I really shouldn't have messed with this while half asleep, and again I can't apologize enough for being such a stupid n00b.
I can attach an image of the boot logo if that helps, but I'm worried I am just S.O.L. at this point...
Also, not sure what an FKZ is. I tried to install a 2.3.6 apk file to my wife's SD card on her phone and booting from the file after putting the SD card into mine. Still nothing.
pull the battery, put it back in, and hold vol up and down while turning on. choose ap fastboot at the menu. go to the thread in my signature and under the mirrors there is also a download of the return to stock script. run it while in fastboot and plugged in with usb. DO NOT pull the chord until it is done. when it is you should be good.
Apex_Strider said:
Okay, sorry for not giving a full rundown on what stupidity on my part cause all of this. Let me start by saying that (sadly) I am a great big n00b when it comes to Linux, and I thought that despite my research online I would sort of explore the CWM Recovery 'Advanced' sections.
I downloaded ROM Toolbox from the Play Store, and installed a custom boot animation, and replaced -or thought I was- the startup "M" logo with something else. This is what concerned me: After re-booting, the "M" logo was all crazy looking, with a "stretched" "M" logo over the top of the "regular" logo.
So, I uninstalled the app, but the logo was still all messed up. So, I used Root Uninstaller to get rid of the ROM Toolbox files, still no resolve to the crazy boot logo.
So, I went into CWM Recovery Advanced, and wiped everything. The Dalvik, cache, System, Data, etc... didn't think that it would -what appears to have happened- wipe out the OS on the phone.
I tried pulling the battery, and re-booting, won't boot passed the skewed "M" logo still. Tried getting into Android Recovery, and it looks to go through the recovery goes through its thing, but never boots normally afterward.
Sorry for being such an idiot, I really shouldn't have messed with this while half asleep, and again I can't apologize enough for being such a stupid n00b.
I can attach an image of the boot logo if that helps, but I'm worried I am just S.O.L. at this point...
Also, not sure what an FKZ is. I tried to install a 2.3.6 apk file to my wife's SD card on her phone and booting from the file after putting the SD card into mine. Still nothing.
Click to expand...
Click to collapse
Yeah wiping the system partition is a no no unless you flash another rom afterwards. Do like ikrasner says and you should be back to normal.
Sent from my MB865 using XDA
Thanks for all the help guys, I really hope that something positive comes about this... though, to go without mention, I certainly need more knowledge on WTH I am doing to my phone: understanding flashing ROMS, what dangers come with rooting, and a vast array of other "all things root" that I need to learn up on.
I will try to install from SD card the 2.3.5 zip tonight, but will it (the phone) look for the newest 2.3.6 OTA update and try to ask me to install? How does that work after rooting, will I re-brick my clearly bricked phone all over again?
As always, thanks for all your replies in advance -you guys really know what's going on here!
can you read chinese?
Maybe I can solve your question,but poor of my english.
and what is your phone type?
at&t hktw or china ?
Sent from my ME865 using xda premium
Apex_Strider said:
Thanks for all the help guys, I really hope that something positive comes about this... though, to go without mention, I certainly need more knowledge on WTH I am doing to my phone: understanding flashing ROMS, what dangers come with rooting, and a vast array of other "all things root" that I need to learn up on.
I will try to install from SD card the 2.3.5 zip tonight, but will it (the phone) look for the newest 2.3.6 OTA update and try to ask me to install? How does that work after rooting, will I re-brick my clearly bricked phone all over again?
As always, thanks for all your replies in advance -you guys really know what's going on here!
Click to expand...
Click to collapse
It should ask you to install 2.3.6. Just go into setting>about phone>check for updates. Or you could go and install one of the roms that are based on 2.3.6 such as Lithium Sonya or SCv5.
Okay gang, perhaps I'm just certifiably dumb, or I am simply just not doing this correctly. I downloaded the "Returntostock2.3.5.script" zip file and copied it to my wife's SD card to 'apply update from sdcard' option from the Android Recovery area by holding Vol Up, Vol Down, & Power buttons. What I got was this:
--Install /sdcard ...
Finding update package...
Opening update package...
Verifying update package...
E:signature verification failed
Installation aborted.
I tried to just plug the USB into the phone and run the 2.3.5. script from there. but again- I'm stuck in the crazy skewed "M" logo startup screen with nothing following. That's all the phone will do at this point, other than my getting into Android Recovery.
I'm not sure how or what fastboot is, or how it works. If the phone is plugged into the USB, it will only boot the stupid screwed up "M" logo screen. Noting else.
Apex_Strider said:
Okay gang, perhaps I'm just certifiably dumb, or I am simply just not doing this correctly. I downloaded the "Returntostock2.3.5.script" zip file and copied it to my wife's SD card to 'apply update from sdcard' option from the Android Recovery area by holding Vol Up, Vol Down, & Power buttons. What I got was this:
--Install /sdcard ...
Finding update package...
Opening update package...
Verifying update package...
E:signature verification failed
Installation aborted.
I tried to just plug the USB into the phone and run the 2.3.5. script from there. but again- I'm stuck in the crazy skewed "M" logo startup screen with nothing following. That's all the phone will do at this point, other than my getting into Android Recovery.
I'm not sure how or what fastboot is, or how it works. If the phone is plugged into the USB, it will only boot the stupid screwed up "M" logo screen. Noting else.
Click to expand...
Click to collapse
do not flash this. unzip it on your computer, choose to boot into fast boot in the same place you chose recovery, then run the .bat file that was in the zip.
Sent from my MB865 using XDA
What that file does is reflash your system.img, basically restoring your phone to factory default. And just as a sidenote you cannot flash things with the standard Android Recovery. You need CWM.
did you try apboot mode and ise fastboot to flash system.img ?
Sent from my ME865 using xda premium
Still not working... not sure how to flash from fastboot. I don't have any options to run a file from there, or at least not sure ow to go about that.
Fastboot sample, hope will help you.
http://bbs.gfan.com/mobile/android-3701449-1-1.html
Sent from my ME865 using xda premium
dickluo said:
Fastboot sample, hope will help you.
http://bbs.gfan.com/mobile/android-3701449-1-1.html
Sent from my ME865 using xda premium
Click to expand...
Click to collapse
So, if I'm looking at this correctly, I need to open command prompt from my computer, and type the commands in from there?
I don't think my computer is recogzining the phone in any way, as I cannot get into the 'manage usb connections' options.
If I have the 2.3.5.script downloaded on my desktop, and l plug my phone in after launching AP Fastboot on the phone, will the computer know where to flash the file to?
I know, I'm a dolt... please bear with me, I really need to get this thing working again -I feel naked without my phone!
Apex_Strider said:
So, if I'm looking at this correctly, I need to open command prompt from my computer, and type the commands in from there?
I don't think my computer is recogzining the phone in any way, as I cannot get into the 'manage usb connections' options.
If I have the 2.3.5.script downloaded on my desktop, and l plug my phone in after launching AP Fastboot on the phone, will the computer know where to flash the file to?
I know, I'm a dolt... please bear with me, I really need to get this thing working again -I feel naked without my phone!
Click to expand...
Click to collapse
Before using the restore script you need to install the usb drivers for your mb865, you can get those from here: http://www.motorola.com/staticfiles/Support/Experiences/Global_Drivers/MotoHelper_2.1.40_Driver_5.5.0.exe
Next unzip the Return to Stock 2.3.5 Fastboot SCRIPT.zip to anywhere you like in your pc (example: C:\RestoreScript\ )
Next connect your phone with the usb cable to the pc and get into fastboot mode for this in your phone press volume down + volume up + power it should appear a screen with some options, use the volume down key of your phone to navigate through the menu until you see the Fastboot option, then enter by pressing the volume up key, this will show you some messages and the finally it should said usb connected.
Then open the folder where you extracted the Return to Stock 2.3.5 Fastboot SCRIPT files and search a .bat file call "Stock Restore" then run the file (double click on it) and it should open a command promt screen with some instructions if the phone is connected correctly and you installed the drivers correctly then in some point the screen will show you the id of your device and it will wait you to press the enter key to start the proccess, press key enter wait all the proccess until the program said to you its finished, after that it will reboot your phone and install the stock 2.3.5 when it boots up you should see the android logo and a progress bar filling up.
when it's done wait the reboot and your phone should be ok.
hope this helps.
jfrank1485 said:
Before using the restore script you need to install the usb drivers for your mb865, you can get those from here: http://www.motorola.com/staticfiles/Support/Experiences/Global_Drivers/MotoHelper_2.1.40_Driver_5.5.0.exe
Next unzip the Return to Stock 2.3.5 Fastboot SCRIPT.zip to anywhere you like in your pc (example: C:\RestoreScript\ )
Next connect your phone with the usb cable to the pc and get into fastboot mode for this in your phone press volume down + volume up + power it should appear a screen with some options, use the volume down key of your phone to navigate through the menu until you see the Fastboot option, then enter by pressing the volume up key, this will show you some messages and the finally it should said usb connected.
Then open the folder where you extracted the Return to Stock 2.3.5 Fastboot SCRIPT files and search a .bat file call "Stock Restore" then run the file (double click on it) and it should open a command promt screen with some instructions if the phone is connected correctly and you installed the drivers correctly then in some point the screen will show you the id of your device and it will wait you to press the enter key to start the proccess, press key enter wait all the proccess until the program said to you its finished, after that it will reboot your phone and install the stock 2.3.5 when it boots up you should see the android logo and a progress bar filling up.
when it's done wait the reboot and your phone should be ok.
hope this helps.
Click to expand...
Click to collapse
jfrank1485,
This stepped me through the entire process without any confusion! Everything is back to normal! Hooray and three Huzzahs!
Also, many many thanks to dickluo, farshad525hou, lkrasner, mtnlion, and KEB64!
You guys really saved my stupid (you know what) on this deal! Next order of business: figure out what the heck I am doing before doing ANYTHING!
Problem solved, my world has regained sanity, and my phone is back to life!
You guys are the best, thank you all so much!!!
Apex_Strider said:
jfrank1485,
This stepped me through the entire process without any confusion! Everything is back to normal! Hooray and three Huzzahs!
Also, many many thanks to dickluo, farshad525hou, lkrasner, mtnlion, and KEB64!
You guys really saved my stupid (you know what) on this deal! Next order of business: figure out what the heck I am doing before doing ANYTHING!
Problem solved, my world has regained sanity, and my phone is back to life!
You guys are the best, thank you all so much!!!
Click to expand...
Click to collapse
I'm glad it work , keep it at hand before doing anything to your phone, it really helps
So I rooted my ATT One X and recently used the tool to get the token and unlock it via HTC. I've tried to install CWM via ROM manager and it says it is installed but if I try and boot to recovery it hangs at a screen with an HTC Logo saying that "this build is for development purposes only, etc..."
If I power down and reboot with the vol down held I get the menu and it says tampered, unlocked, S-On. Trying to boot into recovery from this menu produces the same result.
I'm sure I'm missing something here since I'm a bit of a noob with this but can anyone give me a suggestion?
Thanks in advance!
Ok, looks like I managed to get it down through ADB commands. It's times like this when us noobs actually learn a little bit about our phone
As you've discovered, I don't think that ROM Manager properly installs CWM on our phone. The best way is the one-click install in the Development forum.
Soft-bricked HTC One S. Where to find help with trying to recover it?
Hello.
How it happened
I rooted my HTC One S, then flashed CyanogenMod on it. Used it for a few months, very happy with it. Then I tried to update - automatically, not manually (that was mistake number 1). The phone was then stuck in a bootloop into recovery. (Off>Recovery>Off>Recovery). I didnt know what to do, so I pressed 'Reset phone', or something like that. Since then, the problem has gotten much worse. Now there's a different bootloop: Off>HTC opening screen. That's it. Im desperately trying to access recovery mode, to flash a new ROM to fix the situation.
What did I try
1. Power + VolumeDown does nothing.
2. Installed the HTC One S toolkit. When pressing 'boot into recovery', it says 'device not found'.
3. Tried to boot into recovery from ABD tools, but it says device not found. I tried putting screenshots here, but XDA forum new user limitation doesnt let me. Anyway, if you add this to the imgur url, youll see the screenshots (sorry about this inconvenienace):
/SblBm3M
/6HEvZDk
TL;DR
Phone is stuck in a bootloop. Cant access recovery. Is there any way to fix this situation?
Thank you very much in advance for your time to help me out.