Hi all expert,
my nexus s is unrooted. i installed ADB in my win7. I did wipe out all data/sd card without any back up. so my phone cant go anywhere ,except into clockworkmod recover. when I try to boot, error say it cant find any image. I cant instal image if i cant get in to the phone and set the usb connection. So my question is how to force install image into the phone without enablimg the usb connection? Please help. thank you
rongsokan said:
Hi all expert,
my nexus s is unrooted. i installed ADB in my win7. I did wipe out all data/sd card without any back up. so my phone cant go anywhere ,except into clockworkmod recover. when I try to boot, error say it cant find any image. I cant instal image if i cant get in to the phone and set the usb connection. So my question is how to force install image into the phone without enablimg the usb connection? Please help. thank you
Click to expand...
Click to collapse
you have clockwork recovery right? theres an usb storage option in the recovery itself. connect it to your computer, turn on the usb storage. download a rom(and gapps) to your computer, copy/paste into the device, turn off usb storage, then flash the files in clockwork recovery. then reboot.
After you do what he said, either do alot of research about rooting, and flashing roms and kernels or sell your phone.
Sent from my Nexus S 4G using xda premium
simms22 said:
you have clockwork recovery right? theres an usb storage option in the recovery itself. connect it to your computer, turn on the usb storage. download a rom(and gapps) to your computer, copy/paste into the device, turn off usb storage, then flash the files in clockwork recovery. then reboot.
Click to expand...
Click to collapse
So I did follow your instruction. I went storage->mount usb storage->unmount(I can only select this, I try reboot the phone still give me this only option). so I also tried mount sdcard, mount system, all that.
Finlally, I got removable disk on my computer, but it show 0 byte, when i click on it, it says plz insert a disk into removeable disk. so i went click
property->hardwares->highlight Android UMS composite usb device(type: disk drive) and property. then I select driver-> and there is driver details, update driver. So do I update this driver? If so which driver?
I try to format it, it gives errorlz insert a disk into removeable disk
I have clcokworkmod recovery v5.0.2.0 and it is unrooted. thank you for the help!
I also install PDAnet into my computer but it keep saying connecting to your phone..... I try using different usb port and no luck.
rongsokan said:
So I did follow your instruction. I went storage->mount usb storage->unmount(I can only select this, I try reboot the phone still give me this only option). so I also tried mount sdcard, mount system, all that.
Finlally, I got removable disk on my computer, but it show 0 byte, when i click on it, it says plz insert a disk into removeable disk. so i went click
property->hardwares->highlight Android UMS composite usb device(type: disk drive) and property. then I select driver-> and there is driver details, update driver. So do I update this driver? If so which driver?
I try to format it, it gives errorlz insert a disk into removeable disk
I have clcokworkmod recovery v5.0.2.0 and it is unrooted. thank you for the help!
Click to expand...
Click to collapse
By the way you just click on mount usb storage and LEAVE IT there for a few seconds. It takes a little time for the computer to recognize it usually. You only click unmount when your done...
ok i got it. now i could put files into the sd storage. Do you guys know what i need to put for stock, out-of box image?
I need to reset this to factory setting and root the phone.
I did some serach but the file needed to download is not working anymore. anyone know? thank you
rongsokan said:
ok i got it. now i could put files into the sd storage. Do you guys know what i need to put for stock, out-of box image?
I need to reset this to factory setting and root the phone.
I did some serach but the file needed to download is not working anymore. anyone know? thank you
Click to expand...
Click to collapse
Here is a thought... read some more before messing with your phone instead of asking questions which have been already answered many times.
Sent from my Nexus S 4G
I have been reading reading again... the whole day today. I just dont want to install the wrong drive or file. for nexus s tehre is so many version. the one i got for bootloader is i9020xxka3
for baseband version- i9020xxkf1
fastboot mode stil showing- NO BOOT OR RECOVERY IMG
I give up may be I am too idiot.
obsanity said:
Here is a thought... read some more before messing with your phone instead of asking questions which have been already answered many times.
Sent from my Nexus S 4G
Click to expand...
Click to collapse
Coming from someone that also finds conditions & situations similar but not precisely like my own in the multitude of answered threads..... Some of us can get to a certain point but get stuck, and since these are devices we need to work we want to be sure we don't do something to turn an expensive device into a pretty paperweight.
You learned by fiddling and asking questions did you not? If you are sick of the same old question don't answer the thread.
Sorry, I have no great advice for the OP, you aren't an idiot you are uninformed [just yet] of the proper fix for your problem. I'm still trying to fix something myself so the couple of snipes hit a nerve this morning.
I read read read and read again, its been almost a week. Good god I cant get the solution or may be i dont undderstand it. I try go to cmd prompt and "type fast boot lock" to get it rooted. No luck
my phone situation:
No back up or recovery ( I wipe all sd/back up/system)
fasboot mode-no boot or recovery img
Lock state- unlocked
can only go into clockwork mod
my Goal: lock the phone and flash it to factory stock setting.
I just own nexus s for 7 days and did a ton of research coz stuck at google X animation keep loading and install MIUI and unroot the phone. Soooo stupid of me now that I broke the warranty. Softkeys is no even working!!!!!! when i suscessfully get into the phone.
is there a proper step by step to do this? is there any expert here that can point to the right direction? I am checking this post every 5 minutes
Clearly this is too much phone for you.
Sent from my Nexus S 4G using xda premium
Ok I'll try to help you.
According to what I gather from your posts, you've been successful in unlocking the bootloader and managed to flash CWM recovery, that's a good first step.
Your goal is still unclear. Ok, you want to re-lock the phone and 'restore to factory stock settings'? Does that mean you want a stock firmware on your phone or would you settle for a custom firmware, like Cyanogenmod or MIUI? Either way, visit the Nexus S Development forum, there's a full list of firmwares , just pick whichever you want and download that.
Here's a fantastic topic with a list of all firmwares and also plenty of links to guides:
http://forum.xda-developers.com/showthread.php?t=1067813
Enter CWM recovery mode (VolumeUP + Power button and select Recovery in the Bootloader options).
Go to mounts and storage. We want to mount or SDcard so we can transfer files from the PC to the SDcard as a USB mass storage device. Make sure the phone is connected through USB.
So, select the option: - mount USB Storage. Wait for a few seconds, it takes a while to get initialized by the PC.
Once it's recognized by your PC, copy the downloaded firmware to the SDcard. It should have a .zip extension and be approximately 100mb (of course depending on which flavour you picked, but that's somewhat the standard).
Once it's copied, go back in the CWM main menu and select "Install zip from sdcard". If you want, you can first wipe your cache and Dalvik cache, but since you clearly wiped everything already this shouldn't be necessary, so anyway; install zip from sdcard and select your firmware.zip file. Select it and press the power button to execute the install.
It will install the firmware plus the kernel that it's packed with, all this should be enough to get your phone booted. So reboot your phone and it should work.
Once you've successfully booted into your device, you can do whatever you like. If you want to lock the bootloader again though, you'll need to reverse the steps you took to unlock it. This is through ADB and Fastboot. But this topic explains it step by step and in detail, all credits to the OP: (http://forum.xda-developers.com/showthread.php?t=875630).
If the bootloader is locked again, you shouldn't have any issues with the warranty. It's a Nexus...
Some of your posts were a bit contradictory so I can only assume what your current status is with your phone.
Maybe you should also understand what everything means and does instead of blindy formatting disks and running random commands. Learn what ADB is, learn what Fastboot does. See how the bootloader works and where the recovery comes in, read up on the different firmwares and what kernels do. It might seem like a big investment of your time, but it will help you understand the boot process of the Nexus.
Good luck,
Greetz
Related
I was running a hero ROM on my device, and wanted to try an Eclair ROM. I wanted to flash it but in the process I saw something like: E: Can't open /cache/recovery/command on the screen. I went ahead and performed a wipe because I read it was harmless. But then the installation was aborted because the file update.zip couldn't be found (even though it was on my phone). So I went ahead and rebooted my device. Now it always gets stuck at the little green android, then he disappears and I get a black screen. The device remains on however and I need to pull out the battery for it to turn off... COULD ANYONE PLEASE HELP ME
After doing all you did your device should boot normally. Obviously it didn't. I don't know what went wrong, but if you boot into recovery you should be able to flash a ROM.
Just make sure you have the right recovery and right ROM files.
I only have that Eclair rom on my device (which can't be flashed).
My PC won't read the SD card anymore so I can't put any rom on it...
ernestnwanu said:
I was running a hero ROM on my device, and wanted to try an Eclair ROM. I wanted to flash it but in the process I saw something like: E: Can't open /cache/recovery/command on the screen. I went ahead and performed a wipe because I read it was harmless. But then the installation was aborted because the file update.zip couldn't be found (even though it was on my phone). So I went ahead and rebooted my device. Now it always gets stuck at the little green android, then he disappears and I get a black screen. The device remains on however and I need to pull out the battery for it to turn off... COULD ANYONE PLEASE HELP ME
Click to expand...
Click to collapse
Your not bricked... you basically just failed the update process then wiped your current installed rom with the Wipe. Now you rebooted the phone but there's no rom to load. You now see only the boot starting up and hitting the wall with no rom to load.
That makes sense.. How can I fix this issue?
thank you
Would help if you could give us some info on your phone.
Can you enter recovery or fastboot again ?
phone model, spl & radio version ?
this is why Iphones were invented.... For people who cant understand simple directions or even read for that matter.
What recovery do you have? Get another rom, go into recovery, hit the USB toggle switch and put anothe rrom on. It doesnt have to be named update.zip...
Nevermind.. Doesnt matter what I type here you'll go an do what you want anyway.
I have the htc Magic
How do I get to see my radio and spl?
Yes, I can enter recovery mode.
thank you
I can enter fastboot!
RADIO: 3.22.20.17
SPL 1.33.2005
btw it's a 32A
Where is this USB toggle switch??
Android system recovery utility
Use trackball to highlight:
click to select.
reboot system now [Home+Back]
apply sdcard:update.zip [Alt+S]
wipe data/factory reset [Alt+W]
E: Can't open /cache/recovery/command
That's all I see.
Only the latest recovery has the Usb option in it.
http://forum.xda-developers.com/showthread.php?t=530492
How can I do it as I can't put the recovery on my SD card?
crypysmoker said:
this is why Iphones were invented.... For people who cant understand simple directions or even read for that matter.
What recovery do you have? Get another rom, go into recovery, hit the USB toggle switch and put anothe rrom on. It doesnt have to be named update.zip...
Nevermind.. Doesnt matter what I type here you'll go an do what you want anyway.
Click to expand...
Click to collapse
+1 to that.
You wipe your phone, couldn't boot it and you did not know the reason for this. You wiped your ROM, there's nothing to load up when you boot it. It's so simple.
ernestnwanu said:
I have the htc Magic
How do I get to see my radio and spl?
Yes, I can enter recovery mode.
thank you
Click to expand...
Click to collapse
ernestnwanu said:
How can I do it as I can't put the recovery on my SD card?
Click to expand...
Click to collapse
Wow, just wow. If you need spoonfeed after spoonfeed, How in the world did you root your phone in the first place? You run into problems at EVERY step. Honestly, get the iphone (It's not that badddddd of a phone! Just agreeing with what crypt said!) or don't root your phone. You fail to even look for instructions. I don't understand how your PC can't read your SD card? That probably means it's dead (Which means you need a new one) OR the thought of taking it out and plugging it into an sd adapter never occured to you. I bet you even wiped your SD card somehow.
How come you can't put the recovery on your SD card? Or the rom or anything else
ernestnwanu said:
But then the installation was aborted because the file update.zip couldn't be found (even though it was on my phone).
Click to expand...
Click to collapse
And why was the ROM (update.zip) on your phone and not your sd card? I believe that you fail fail fail to look at any instructions the awesome people have posted here. If you fail to follow instructions given on these forums, how will you follow instructions given from members trying to help you? I find it useless to bother helping any further.
I don't have an sd card adapter and since my phone won't start up, my pc won't recognize my device anymore. Take it easy btw, I'm only looking for help
If help is what you're looking for, then go look around under these forums. I suggest you go and buy an adapter as well, it'd help a lot. May even be your only choice. (I believe there's another way but I'm not going to bother with that as it may be too complicated for you. I dont' think it'd work either with your recovery)
I don't mean to be an ass but when questions like this are posted, I hope you understand. It's as bad as asking how to turn your phone on vibrate. The manual is with your phone and everything, take a look or get some common sense and try the volume buttons.
The forum is your manual. You wiped your ROM, well if you think about it, of course it wont boot up all the way. It has nothing to load. Can't put stuff on your sd card? Get an adapter. It's simple.
ernestnwanu said:
How can I do it as I can't put the recovery on my SD card?
Click to expand...
Click to collapse
I thought people would think right away that they would need an sd adapter to somehow get it onto their computer once they have no other choice lol.
okay that's clear, thank u for your time
For now I don't have an sd adapter, so I stuck the sd card in my brother's phone and tried to put the necessary files but now it seems I have to format the sd card.. Is this harmful or should I just go ahead?
I have the latest recovery but I get a popup message on my PC saying I should format the SD card. Will I still have the 'data' file where I need to put the recovery file under?
ernestnwanu said:
I have the latest recovery but I get a popup message on my PC saying I should format the SD card. Will I still have the 'data' file where I need to put the recovery file under?
Click to expand...
Click to collapse
what ever you have on it will be erased.
You can also use fastboot to flash the recovery without having to import it into the sdcard. I would not recommend it to you do since lack the basic android knowledge. (all the command are listed in the thread i posted earlier)
If I format the SD card, where should I put the recovery.img if there is no /data anymore? (using the reboot method)
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...
My Motorola Xoom is stuck in an BootLoop
It is an European Xoom.
It had 3.1 (OTA).
I unlocked the bootloader, with succes.
Using this guide: http://imransarwar.com/index.php/how-to-unlock-and-re-lock-motorola-xoom-for-flashing/
Then I used this guide:
http://imransarwar.com/index.php/how-to-root-motorola-xoom-wifi-from-stock-3-1/
http://forum.xda-developers.com/showthread.php?t=1078019
After catch-the-boot, I came in the ClockWorkMod Recovery, as expected.
But the clicking on 'Install zip from SD card' showed the contents of the internal storage, not the physical SD.
So I rebooted the device, and have put the Zip-file on the internal Storage.
I went into recovery-again, i selected the zip-file.
It says 'Done '.
I Click on Reboot Device Now.
*BOOT LOOP*
I can still use:
adb reboot
And when i have done 'adb reboot', i can also reach fastboot.
(there is still hope?)
My Assumptions:
As the recovery 'install zip from sd' uses the internal storage,
it has no use to try putting something on the physical sd-card.
Is there a way to get something (read: some fix zip-file) on the internal storage, using nothing but ADB and Fastboot?
like adb push, would that work? if that would work, what do i have to push?
Any help is appreciated !
EDIT:
Found possible solution.
I'll think I should try this:
http://www.dkszone.net/unroot-relock-motorola-xoom-honeycomb-guide
It will get the device back to stock (I hope).
EDIT2:
Ok.. I tried the guide above.
My Device hangs on the Dual Core-screen.
Just found out that the File i have downloaded for the above guide is not the right version for my European Xoom (Wifi).
It was for 3G-Xoom-devices.
Downloading the right version now..
I Hope that i can come into Fastboot again, so i can flash the correct version.
EDIT3:
The device is still hanging on the Dual-Core-Screen,
it does not respond to anything, no buttons, no adb, no fastboot...
I guess i have to wait till the battery is empty, (this might take a while)
then turn it on while holding the volume down button to try to get into fastboot
If I cannot get into fastboot, my device is bricked I guess.
frankkienl said:
My Motorola Xoom is stuck in an BootLoop
It is an European Xoom.
It had 3.1 (OTA).
I unlocked the bootloader, with succes.
Using this guide: http://imransarwar.com/index.php/how-to-unlock-and-re-lock-motorola-xoom-for-flashing/
Then I used this guide:
http://imransarwar.com/index.php/how-to-root-motorola-xoom-wifi-from-stock-3-1/
http://forum.xda-developers.com/showthread.php?t=1078019
After catch-the-boot, I came in the ClockWorkMod Recovery, as expected.
But the clicking on 'Install zip from SD card' showed the contents of the internal storage, not the physical SD.
So I rebooted the device, and have put the Zip-file on the internal Storage.
I went into recovery-again, i selected the zip-file.
It says 'Done '.
I Click on Reboot Device Now.
*BOOT LOOP*
I can still use:
adb reboot
And when i have done 'adb reboot', i can also reach fastboot.
(there is still hope?)
My Assumptions:
As the recovery 'install zip from sd' uses the internal storage,
it has no use to try putting something on the physical sd-card.
Is there a way to get something (read: some fix zip-file) on the internal storage, using nothing but ADB and Fastboot?
like adb push, would that work? if that would work, what do i have to push?
Any help is appreciated !
EDIT:
Found possible solution.
I'll think I should try this:
http://www.dkszone.net/unroot-relock-motorola-xoom-honeycomb-guide
It will get the device back to stock (I hope).
EDIT2:
Ok.. I tried the guide above.
My Device hangs on the Dual Core-screen.
Just found out that the File i have downloaded for the above guide is not the right version for my European Xoom (Wifi).
It was for 3G-Xoom-devices.
Downloading the right version now..
I Hope that i can come into Fastboot again, so i can flash the correct version.
EDIT3:
The device is still hanging on the Dual-Core-Screen,
it does not respond to anything, no buttons, no adb, no fastboot...
I guess i have to wait till the battery is empty, (this might take a while)
then turn it on while holding the volume down button to try to get into fastboot
If I cannot get into fastboot, my device is bricked I guess.
Click to expand...
Click to collapse
It's not bricked. It's really hard (but not impossible) to brick a Xoom. They are hardy beasts.
I do wish you hadn't tried the revert/relock thing. You just made it worse as you tried to flash a 3G image on a WiFi only device.
But don't worry, it is possible to come back from this.
Just so you know, your first mistake was using old guides (though filled with good info, but files are not necessarity right) and mixing the sources. There are much newer guides in the Development section (page 1) for non-US Xoom, and I think people have better result when they stick with one source (in this case xda Xoom forum).
Second mistake is that you used the wrong recovery image...you used the v4.0.0.4 from RomManager, which is not compatible with the external micro sd card. You need the v3.2.0.0 R4c (Tiamat version). That's still the best most current version for the Xoom.
http://forum.xda-developers.com/showthread.php?t=1074979
If you had not gotten impatient and tried to revert/relock, you could have just flashed the proper recovery image and you would be good to go.
Good luck!
You seem to know your way around adb and fastboot so I'm sure you will be able to recover. Find the proper stock images for your Euro WiFi Xoom and flash them, download and flash the correct recovery image and you can take it from there.
It works again !
I Fixed it it works again
( I Do not have Root, but i'm glad its not bricked)
My device was hanging on the Dual-core screen.
So I waited till the battery was empty.
I connected the charger and usb cable, powered it on while holding volume-down.
Guess what, I came into fastboot
I have downloaded the correct images from the motodev-website.
Just followed the instructions (on the motodev site) and was good to go.
All what was left was updating to 3.1. That also worked fine.
I will be more carefull next time I try to Root an Android device, and make sure the guide is not for a different device. I have learned from my mistake.
frankkienl said:
I Fixed it it works again
( I Do not have Root, but i'm glad its not bricked)
My device was hanging on the Dual-core screen.
So I waited till the battery was empty.
I connected the charger and usb cable, powered it on while holding volume-down.
Guess what, I came into fastboot
I have downloaded the correct images from the motodev-website.
Just followed the instructions (on the motodev site) and was good to go.
All what was left was updating to 3.1. That also worked fine.
I will be more carefull next time I try to Root an Android device, and make sure the guide is not for a different device. I have learned from my mistake.
Click to expand...
Click to collapse
Excellent! So glad to hear it. You have skills so I'm sure you will be coool from now on.
just an update
This is an old thread so I'm putting this here for google searchers, like me.
I had the same problem but here's what extra I found/noticed
(1) To restart the xoom when it's in this state hit power button and volume up
(2) You can see that the tablet is still responsive if you hit volume down after 2 seconds as you'll get some options
(3) For me it wouldn't work if I used the motorola cable (yes, the real one) in the front pc usb ports. I had to use the usb 3 ports at the back of my pc. Yes, it's that picky! The difference was when I used fastboot to install the system image. It took 3 minutes then gave up, stuck the cable in the back of the pc instead and it took about 10 seconds and worked first go!
(4) The pc didn't recognise the xoom and adb didn't work, i.e. it said no device attached. However fastboot did recognise it
After point (4) I realised it wasn't bricked and could move forward
thanks to the other posters here for making me realise there was hope
NS4G
Will boot to fastboot and recovery
CWMR Touch 6.0.1.0
Situation:
My device started bootlooping after about a week of random restarts and freezes. I had just flashed BlackBean and now this, so I decided I was just going to flash a new ROM/Kernel combo. I remembered someone saying I should format /system to install the specific ROM, but I'm fairly sure I formatted /boot along with it, like an idiot. FYI - Fast Charge and a build.prop tweak to set permissions on boot was enabled when this happened. So then I try and flash a new ROM/Kernel combo to fix my bootloop and it wouldn't read the sdcard afterwards. Now it boots straight to fastboot everytime. Toolkit seems to be able to do some things via USB control like reboot the bootloader, but it does not detect an ADB device when I run the driver check or try to restore my CWM backup. I ran the stock+unroot option in Toolkit (was going to send it in thinking the sdcard thing was hardware at first) and it seemed to have went through the whole process correctly... Until the end when it did not reboot automatically like it should have. After doing this, I now get "STANDARD_SET_CONFIGURATION" on the phone when I insert the USB cord while in fastboot. It did not do this before, whether it is the new cord or the flash I do not know. My old cord WAS having problems with data though.
Problem:
I now have no USB debug or SDcard functionality. I assume because of missing files on /boot. I can mount nothing (except cache, but the PC doesn't recognize) without getting a "can't mount" error. This puts a serious dent in my novice ability to fix it. Anything in Toolkit that runs via ADB commands doesn't seem to work properly because it says the device is not in debug mode. PDAnet USB Drivers seemed to install without a hitch and device is recognized on my PC.
Errors:
When trying to mount ANYTHING except the cache while in CWM, I only get: "E:/ Can't mount /sdcard/".
If I try to mount USB storage I get: "E:/ Unable to write to ums lunfile (No such file or directory)Error mounting /sdcard!"
If I try to run any one click methods that use ADB I get: "Daemon not running* No ADB device detected. Make sure you have debugging enabled on your phone"
The log in CWM recovery always shows: "I: Set boot command "" failed to open /sys/class/android_usb/android0/state: No such file or directory" over and over (as many times as I tried to mount something while in recovery for that session)
Questions:
Do you think USB Fast Charge or having the build.prop tweaks enabled could have done something to USB debug? Is there a way to at least just fix the USB Debug problem? Am I correct in assuming that wiping the /system along with the /boot folder is what caused me to not be able to mount the /sdcard to flash another ROM? Is there a way to push the files I need onto the device to restore sdcard function and flash another zip?
Also, what fastboot do I need to be in to do the StockROM+Unroot method in the Toolkit? I have two. Only hold Vol Up/Power takes me to "FASTBOOT". Holding both Volumes+Power puts me into "FASTBOOT - NO BOOT OR RECOVERY IMG"
What is the difference?
I only ask because the Toolkit wants me to hold both volumes and up to get into bootloader mode, but they describe a big green "Start" with an android lying on it's back, mine does not look like that. It simply looks like regular fastboot, but says "FASTBOOT - NO BOOT OR RECOVERY IMG" instead.
It seems you messed with the ROM zip with some tool. Sorry could read your lengthy post completely.
I just want to know one thing clearly, what is the problem basically? where are you stuck?
Edit - Made it as concise as I could, hope it helps. Sorry for length.
Basically, the phone has a formatted /boot, /data, /sdcard, /system, dalvik cache, and I can't seem to use any of the flashing tools via Toolkit in Fastboot mode because the Toolkit says it "cannot find ADB device" please enable "debug" mode. Even when I run the driver check, it says ADB Device Not Found. Though I do have some control of the device via USB (I can use Toolkit to soft reboot from the bootloader) telling me my drivers are probably OK? I couldn't flash any ROM zips (or anything, even backups on the device) because I lost /sdcard functionality.
After a bunch of reading last night, it seems I want to Push a backup of /system and /boot onto the device, which should then restore USB functionality and allow me to flash a ROM... Right?
DizturbedOne said:
Edit - Made it as concise as I could, hope it helps. Sorry for length.
Basically, the phone has a formatted /boot, /data, /sdcard, /system, dalvik cache, and I can't seem to use any of the flashing tools via Toolkit in Fastboot mode because the Toolkit says it "cannot find ADB device" please enable "debug" mode. Even when I run the driver check, it says ADB Device Not Found. Though I do have some control of the device via USB (I can use Toolkit to soft reboot from the bootloader) telling me my drivers are probably OK? I couldn't flash any ROM zips (or anything, even backups on the device) because I lost /sdcard functionality.
After a bunch of reading last night, it seems I want to Push a backup of /system and /boot onto the device, which should then restore USB functionality and allow me to flash a ROM... Right?
Click to expand...
Click to collapse
Your storage memory is completely inaccessible?
Yes, no way to access it via CWM. ADB stuff does not work either. It seems Fastboot stuff DOES. I would like to find a boot.img and system.img to flash via Toolkit (I believe toolkit uses fastboot or odin for these) to see if that would work for me. Any ideas?
It seems like the easy nature of unlocking, rooting, and customizing this phone leads to less of these kind of discussions, I can usually find many files and discussions pertaining to this for HTC phones, but never for this phone.
My bootloader version is KE1, but my baseband version is LF2, makes no sense to me.
The KE1 bootloader was when I was on ICS, but the LF2 baseband was from Jellybean... wth?
Do you think the time I flashed "stock+unroot" on the toolkit that it only partially took? (I did try to back it up to ICS because the Jellybean download didn't work). It seemed as if it flashed everything via fastboot, but never restarted at the end and still won't boot when done.
same problem kinda
i am having the same problem as this with my nexus. mine started after i downloaded Jellybean.it worked fine for about 1 month. i had changed nothing but when i would change my battery or restart my phone it would get stuck at the google screen every now and then, then it started more often. i could normally pull the battery and restart it and it would work after a couple of times doing that. but now this last time i tried that the phone wouldnt go past google screen at all. i can access my clockwork mods recovery but when i try to install zip from sd i get the error cant load sd i have tried everything i know and cant get nothing to work. please help. i miss my nexus this prevail is too slow and small...
Your drivers don't seem to be installed properly.
Get that right, then you can reflash your recovery via fastboot, then you can mount your usb and transfer anything (rom kernel gapps etc etc)
Edit: oh and Bamamac82, that's not the same problem at all. Create a topic of your own.
polobunny said:
Your drivers don't seem to be installed properly.
Get that right, then you can reflash your recovery via fastboot, then you can mount your usb and transfer anything (rom kernel gapps etc etc)
Edit: oh and Bamamac82, that's not the same problem at all. Create a topic of your own.
Click to expand...
Click to collapse
@ polobunny - There is no way for me to install them more properly if I can't go into debug mode to install them though... I wiped out ALL drivers and manually reinstalled the drivers from PDAnet that had previously worked perfectly on my device. But now it never installs as Nexus S, only as Samsung ADB Interface or some such. I've tried it with PDAnet drivers and the Samsung drivers and have followed every driver install guide on the web... Any other suggestions on how to do this properly? I was even thinking of installing a Google SDK just to see if the drivers would work better...
@ Bamamac82 - Yes, that is pretty much the exact same problem, with the exception of the fact that you didn't wipe the /boot partition as I did. But yeah, I installed a JB ROM, it got a few random restarts, froze up twice, then one morning got stuck in a bootloop after I pulled the battery on a freeze up. Not having a working USB cord at the time botched me, because I couldn't get my drivers reliably installed before anything happened, I was using AirDroid because my OEM cable wasn't working with data reliably.
I totally thought the sdcard problem was because I formatted /boot in a hasty ROM flash though. Could I be wrong here?
DizturbedOne said:
There is no way for me to install them more properly if I can't go into debug mode to install them though... I wiped out ALL drivers and reinstalled the drivers from PDAnet that had previously worked perfectly on my device. But now it never installs as Nexus S, only as Samsung ADB Interface or some such.
And Bamamac82 has the exact same problem, with the exception of the fact that he didn't wipe the /boot partition as I did. But yeah, I installed a JB ROM, it got a few random restarts, froze up twice, then one morning got stuck in a bootloop after I pulled the battery on a freeze up.
I totally thought the sdcard problem was because I formatted /boot in a hasty ROM flash though. Could I be wrong here?
Click to expand...
Click to collapse
When you're in fastboot mode on your phone, on your windows PC point the unknown device or the device with an exclamation/question mark to the path where the .inf for the drivers are located. If it still doesn't detect it, you can always try and force it to install a certain device (adb debug bridge or something of the sort).
Once that is done as I said you won't have any problem fastboot'ing to your phone and doing the other steps. Windows drivers and especially the adb drivers can be finnicky.
Your SDcard problem has nothing to do with the fact your formatted boot partition though, those are not linked.
Edit: Oh and I know there is some people, namely with NS4Gs, that had issues with the drivers. I believe for some reason there's some missing IDs in the inf making it impossible to install automatically. Forcing it should work though.
Polobunny thank you so much for your help so far. My device has been softbricked for a week and I'm using a HTC Hero for now! It's atrocious. I'm going to try as you said when I get home tonight and will update if fastboot allows me to flash after that.
Any idea where I can get all the .img's I need? I can only find the complete .tgz for IMM76D (which is fine for now just want it back to working state) and don't know how to extract .img's from it. Can't even find the complete .tgz for JRO03R though, the link is always down. At this point, all I want is a factory img to start from so I can upgrade to JRO03R, root it, and then make a fresh NAND backup from there.
If I were you, I would download Odin, a factory image from Google (just search nexus s factory image), the SDK tools (Google it) and would "reset" the phone.
You will easily find a guide for Odin. Then you'll just have to follow it and your nexus should be fine (but it will be factory reseted and you will have lost all your data )
Sent from my Nexus S using xda premium
Sorry guys, have been putting late hours in at work and haven't had much time until this weekend.
@BenHeng, that's what I am about to look into tonight. I didn't want to learn an entirely new aspect to restore this, I have been limited on free time and am starting to think it will be less hassle than dealing with this.
Only caveat to that, is that I definitely would like to know what happened to cause the SDCARD problem, because that was the main problem that got to me here, would like to prevent that from happening again.
ADB
Make sure ADB debuging is checked under Developer options
localpagefirst said:
Make sure ADB debuging is checked under Developer options
Click to expand...
Click to collapse
Please read the thread before replying.
@polobunny - I did a complete manual install of the RAW drivers, and got it to recognize properly as a Nexus S, as it did when USB Debug and everything worked correctly... But it still does not recognize it as an ADB device when running a driver check.
Is it safe to continue forward with a flash via ODIN in this state?
Hi, I don't understand why you want to use ODIN, fastboot commands still don't work after you installed correctly your driver?
Anyway you can find all (new and old) originals google image here:
http://www.randomphantasmagoria.com/firmware/nexus-s/
Listen mate, the best way would be to flash the factory image via fastboot in bootloader mode. Follow this simple step to step guide.
If you have any issues. post them there on the blog post itself :good:
DizturbedOne said:
Please read the thread before replying.
@polobunny - I did a complete manual install of the RAW drivers, and got it to recognize properly as a Nexus S, as it did when USB Debug and everything worked correctly... But it still does not recognize it as an ADB device when running a driver check.
Is it safe to continue forward with a flash via ODIN in this state?
Click to expand...
Click to collapse
Please, please don't use a shi**y 1-click package thing. There's no driver check to be done other than using adb and typing "adb devices". Do it manually and report the results. It should show your adb device ID, a long string of number and letters.
polobunny said:
Please, please don't use a shi**y 1-click package thing. There's no driver check to be done other than using adb and typing "adb devices". Do it manually and report the results. It should show your adb device ID, a long string of number and letters.
Click to expand...
Click to collapse
I get nothing when I do that. It says "List of devices attached" and a blank line underneath. When I plug the USB in during fastboot I get "STANDARD_SET_CONFIGURATION" at the bottom, which I never get until I install the drivers.
It seems as if the computer must recognize the device in debug mode in some way to properly install the drivers.
Why is my sdcard partition unable to be written to? This never would have been a problem as I always keep a couple backup ROM's on the phone. Either way, it seems as if all of this is for nothing if the phone will not allow me to read/write to the memory in the device.
Ok so I usually do searching (in this case a few hours of searching), to get help but I am in a very unique situation. Long story.
I tried updating my rooted nexus 5 to android 4.4.3 via CWM Recovery. It seemed to be taking an extremely long time to flash the rom. (I think it was a mod stock rom with root) So I shut it down, of course it wouldnt boot. So I did a whole wipe and reset in CWM, nothing. So I did it using Command prompt with one of the guides here. Worked great! Got it running, apps downloading. Then I noticed that my storage was cut in half. (It said I had 12 gigs and not 28, I have a 32 gig nexus 5) I read up and found someone who re locked, then unlocked hit boot loader. So I did that using Command Prompt. Now im stuck in a boot loop. Here's the kicker, When you lock the bootloader, the phone gets wiped. Well there went my USB debugging mode. So now, Im stuck in a boot loop and no way to get out. Ive tried using CWM to factory reset. Nothing.
I think I may have to get a new phone. From what Ive found theres no other way to get usb debugging mode on unless your in the phone. Without that, I cant do anything with command prompt. I dont post really at all, just read. So for me to do this means I am really stuck. Any advice or ideas would be greatly appreciated! I have all the latest drivers and everything.
Can you access the recovery? If so, format cache partition and then perform a factory reset and try to boot. If it fails, download the factory images and flash it. Factory images are flashed in fastboot mode and doesn't require a working OS or USB Debugging.
Follow the links in my signature and read everything mentioned it those threads. I'm sure your phone will be up and running in no time!
Thanks for the quick reply. Yes I can get into clockwork mod. Ive tried wiping data factory reset, wiping dalvik and cache partitions. When I do a factory data reset, I get this:
Formatting data /data...
error mounting /data...
Skipping format...
Formatting /cahce
Formatting /sd-ext...
E: Unknown volume for path [/sd-ext]
Formatting /sdcard/.android_secure!
Skipping format...
Data Wipe Complete
Still in boot loop.
zeroshift11 said:
Thanks for the quick reply. Yes I can get into clockwork mod. Ive tried wiping data factory reset, wiping dalvik and cache partitions. When I do a factory data reset, I get this:
Formatting data /data...
error mounting /data...
Skipping format...
Formatting /cahce
Formatting /sd-ext...
E: Unknown volume for path [/sd-ext]
Formatting /sdcard/.android_secure!
Skipping format...
Data Wipe Complete
Still in boot loop.
Click to expand...
Click to collapse
Dumb question, but do you have access to your latest back up on your phone?
Boot into recovery and adb push a rom zip
Sent from my Nexus 5 using Tapatalk
zeroshift11 said:
Ok so I usually do searching (in this case a few hours of searching), to get help but I am in a very unique situation. Long story.
I tried updating my rooted nexus 5 to android 4.4.3 via CWM Recovery. It seemed to be taking an extremely long time to flash the rom. (I think it was a mod stock rom with root) So I shut it down, of course it wouldnt boot. So I did a whole wipe and reset in CWM, nothing. So I did it using Command prompt with one of the guides here. Worked great! Got it running, apps downloading. Then I noticed that my storage was cut in half. (It said I had 12 gigs and not 28, I have a 32 gig nexus 5) I read up and found someone who re locked, then unlocked hit boot loader. So I did that using Command Prompt. Now im stuck in a boot loop. Here's the kicker, When you lock the bootloader, the phone gets wiped. Well there went my USB debugging mode. So now, Im stuck in a boot loop and no way to get out. Ive tried using CWM to factory reset. Nothing.
I think I may have to get a new phone. From what Ive found theres no other way to get usb debugging mode on unless your in the phone. Without that, I cant do anything with command prompt. I dont post really at all, just read. So for me to do this means I am really stuck. Any advice or ideas would be greatly appreciated! I have all the latest drivers and everything.
Click to expand...
Click to collapse
Try changing to TWRP recovery by using - fastboot flash recovery recoveryname.img
Format data, factory reset your devices in TWRP,
Then, install any rom using adb sideload in TWRP
Oh and if you're booting in any way possible, you're never screwed ?
Sent from my Nexus 5 using Tapatalk
zeroshift11 said:
Ok so I usually do searching (in this case a few hours of searching), to get help but I am in a very unique situation. Long story.
I tried updating my rooted nexus 5 to android 4.4.3 via CWM Recovery. It seemed to be taking an extremely long time to flash the rom. (I think it was a mod stock rom with root) So I shut it down, of course it wouldnt boot. So I did a whole wipe and reset in CWM, nothing. So I did it using Command prompt with one of the guides here. Worked great! Got it running, apps downloading. Then I noticed that my storage was cut in half. (It said I had 12 gigs and not 28, I have a 32 gig nexus 5) I read up and found someone who re locked, then unlocked hit boot loader. So I did that using Command Prompt. Now im stuck in a boot loop. Here's the kicker, When you lock the bootloader, the phone gets wiped. Well there went my USB debugging mode. So now, Im stuck in a boot loop and no way to get out. Ive tried using CWM to factory reset. Nothing.
I think I may have to get a new phone. From what Ive found theres no other way to get usb debugging mode on unless your in the phone. Without that, I cant do anything with command prompt. I dont post really at all, just read. So for me to do this means I am really stuck. Any advice or ideas would be greatly appreciated! I have all the latest drivers and everything.
Click to expand...
Click to collapse
First of all you most certainly not screwed.
Now what you have done is oem unlock without google stock recovery.
For the process of wiping userdata to complete , after you type fastboot oem unlock and restart the phone will boot to recovery and execute the wipe.
Because you have cwm recovery the process is stuck and hence the bootloop.
You need to boot to bootloader and type : fastboot -w (press enter) ,it will erase userdata and cache, and restart to system.
You can also try "fastboot format data " and "fastboot format cache" .but if -w worked then no need for that.
If you still stuck in bootloop then you need to flash the stock factory img.
zeroshift11 said:
Thanks for the quick reply. Yes I can get into clockwork mod. Ive tried wiping data factory reset, wiping dalvik and cache partitions. When I do a factory data reset, I get this:
Formatting data /data...
error mounting /data...
Skipping format...
Formatting /cahce
Formatting /sd-ext...
E: Unknown volume for path [/sd-ext]
Formatting /sdcard/.android_secure!
Skipping format...
Data Wipe Complete
Still in boot loop.
Click to expand...
Click to collapse
No need to worry. Download the 4.4.3 factory images and follow the guide "How to flash factory image" which is linked in my signature.
Or, if you want to try out a custom rom, you can push the rom.zip and gapps.zip to your device using "adb push" or sideload it in recovery.
I really appreciate the help guys. Ok I would love to try these, but, I cant do anything with the command prompt. It always says "waiting for device"
I have the latest good drivers installed from ADB. In my device manager the Yellow ! triangle is there beside the android bootloader interface. Ive tried uninstalling the drivers and the software and doing it again and nothing. Mind you, when I do that, it shows up as samsung android devices so that could be a a problem. Im going to try and work on that. Any other ideas?
zeroshift11 said:
I really appreciate the help guys. Ok I would love to try these, but, I cant do anything with the command prompt. It always says "waiting for device"
I have the latest good drivers installed from ADB. In my device manager the Yellow ! triangle is there beside the android bootloader interface. Ive tried uninstalling the drivers and the software and doing it again and nothing. Mind you, when I do that, it shows up as samsung android devices so that could be a a problem. Im going to try and work on that. Any other ideas?
Click to expand...
Click to collapse
I had a similar problem and solved it by going to update driver software, browes my computer, let me pick from a list on the computer. Then find the android adb interface
Sent from my Nexus 5 using XDA Free mobile app
jd1639 said:
I had a similar problem and solved it by going to update driver software, browes my computer, let me pick from a list on the computer. Then find the android adb interface
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Done that. A few times. Says it's up to date. Problem for me that I can see so far, any tutorial on how to unlock bootloader or side load, requires USB debugging, which is turned off. Thats why I get the waiting for device message in Command Prompt.
zeroshift11 said:
I really appreciate the help guys. Ok I would love to try these, but, I cant do anything with the command prompt. It always says "waiting for device"
I have the latest good drivers installed from ADB. In my device manager the Yellow ! triangle is there beside the android bootloader interface. Ive tried uninstalling the drivers and the software and doing it again and nothing. Mind you, when I do that, it shows up as samsung android devices so that could be a a problem. Im going to try and work on that. Any other ideas?
Click to expand...
Click to collapse
Are you in fastboot mode while running fastboot commands? If so,
Uninstall each and every driver installed on your computer. Download the full android sdk from here: http://developer.android.com/sdk/index.html
Open SDK manager and download all the required tools. Also, download the usb_driver from within the sdk manager. Now connect your device to your computer and let it detect. Now, open device manager, right click on the recognized device (Name of the nexus device may be different. Don't worry). Select update driver. Now navigate to the usb_driver folder which you had downloaded previously and select it. Once the driver is updated, windows might reconnect the device. (Ding ding sounds). Once it does, open cmd from the fastboot folder and try running the commands again.
zeroshift11 said:
Done that. A few times. Says it's up to date. Problem for me that I can see so far, any tutorial on how to unlock bootloader or side load, requires USB debugging, which is turned off. Thats why I get the waiting for device message in Command Prompt.
Click to expand...
Click to collapse
No, pick it yourself, see below the search for driver software
Sent from my Nexus 5 using XDA Free mobile app
vin4yak said:
Are you in fastboot mode while running fastboot commands? If so,
Uninstall each and every driver installed on your computer. Download the full android sdk from here: http://developer.android.com/sdk/index.html
Open SDK manager and download all the required tools. Also, download the usb_driver from within the sdk manager. Now connect your device to your computer and let it detect. Now, open device manager, right click on the recognized device (Name of the nexus device may be different. Don't worry). Select update driver. Now navigate to the usb_driver folder which you had downloaded previously and select it. Once the driver is updated, windows might reconnect the device. (Ding ding sounds). Once it does, open cmd from the fastboot folder and try running the commands again.
Click to expand...
Click to collapse
Doing that again. Maybe I missed a step last time but I tried that already a few times. Im trying again.
zeroshift11 said:
I really appreciate the help guys. Ok I would love to try these, but, I cant do anything with the command prompt. It always says "waiting for device"
I have the latest good drivers installed from ADB. In my device manager the Yellow ! triangle is there beside the android bootloader interface. Ive tried uninstalling the drivers and the software and doing it again and nothing. Mind you, when I do that, it shows up as samsung android devices so that could be a a problem. Im going to try and work on that. Any other ideas?
Click to expand...
Click to collapse
zeroshift11 said:
Done that. A few times. Says it's up to date. Problem for me that I can see so far, any tutorial on how to unlock bootloader or side load, requires USB debugging, which is turned off. Thats why I get the waiting for device message in Command Prompt.
Click to expand...
Click to collapse
I think the drivers aren't installed properly. My phone comes up as Android Device, then in the drilldown Android Composite ADB Interface.
I know you've said you've done it many times, but try reinstalling the drivers manually. Go to whatever it's listed as under Device manager->Right click->Update Driver. I can't remember the exact prompts, but basically don't let it look online. Tell it that you want to install drivers you have on your computer. Navigate to where ever you have driver files and install it.
Try different USB ports/cables. Computers are weird. Sometimes this actually works.
Ok so I uninstalled the drivers from the device manager, went to control panel did it there as well. I have the SDK on my desktop, I installed the google drivers. But I also had downloaded just the google driver manually from their website. Unrared it, plugged my phone in, it detected the phone, I manually updated drivers to the ones I got from the google page. It updated. I was in bootloader mode, and I get that the drivers installed successfully, then it also says Device could not start (error code 10). Anything I type into command prompt still says waiting for device.
Johmama said:
I think the drivers aren't installed properly. My phone comes up as Android Device, then in the drilldown Android Composite ADB Interface.
I know you've said you've done it many times, but try reinstalling the drivers manually. Go to whatever it's listed as under Device manager->Right click->Update Driver. I can't remember the exact prompts, but basically don't let it look online. Tell it that you want to install drivers you have on your computer. Navigate to where ever you have driver files and install it.
Try different USB ports/cables. Computers are weird. Sometimes this actually works.
Click to expand...
Click to collapse
Wow........switching usb ports worked..............Thanks so much! Ok so bootloader unlocked. Now Ill try factory reset, if nothing Ill flash original recovery and do it again. After I sideload the stock zip.
Thanks to everyone here my phone is back up. Who knew the USB would have been the issue I was having. Its up, but again my storage was cut in half. Back to 12 gigs. So Im going to look for a fix unless anyone here has it haha.
zeroshift11 said:
Thanks to everyone here my phone is back up. Who knew the USB would have been the issue I was having. Its up, but again my storage was cut in half. Back to 12 gigs. So Im going to look for a fix unless anyone here has it haha.
Click to expand...
Click to collapse
Clear cache and factory reset in the stock recovery
Sent from my Nexus 5 using XDA Free mobile app