Related
Hi, I've been following countless guides on how to root the Nexus S, and I've used countless different root and recovery .img files and none have worked. When I boot the phone, I'm stuck at the Google logo screen and it won't go anywhere from there.
My phone is Wind's Nexus S, GT-i9020... under the battery it says model:GT-9020T
Flash the latest clockwork 3 recovery img and then hold down the volume up and power to get into recovery.
Flash a cyanogen rom or something.
You may need to mount storage through USB in clockwork to copy rom's to it.
Sent from my Nexus S using XDA Premium App
Make sure you flash a compatible boot image file. I, too, was stuck on the boot screen until I flashed the right boot image file. Some people swear that the data cable that comes in the box is junk and leads to headaches when trying to root. I have not experienced that, but it's worth a try. Uninstall any Android drivers on your system, and ONLY install the Google provided drivers. That's all I can think of right now, when I was trying to root my phone. I hope this helps.
I needed the Google USB drivers from the SDK and the PDAnet drivers. This was on a Windows 7 laptop.
Its not hard to find the right clockwork 3 img file. I did have to rename the img file from clockworkrecovery3blahblah.img to recovery.img
Once that is done flashing, boot into clockwork recovery and choose to mount the USB storage. Copy a cyanogen rom to the phone then choose to install zip from sdcard in clockwork.
Sent from my Nexus S using XDA Premium App
Thanks for the responses. It seems I should not have flashed the boot.img at all. I was able to reset the phone to stock using the zip from this post[/quote], and from there did a correct root using 4002-orange.img for recovery and su-2.3.6.1-ef-signed.zip. There are a lot of bad guides on rooting out there, it took hours of searching and some second luck on stumbling across the right post to reset the phone to factory.
nxt said:
I'm guessing you flashed a boot.img to try and root it?
That's what screwed up.
Take battery out, put it back in, hold volume up and power at the same time to get to Bootloader.
Flash the latest cwm recovery, boot to recovery. mount the internal usb,
go to: [url]http://forum.xda-developers.com/showthread.php?t=1056062
Click to expand...
Click to collapse
nxt said:
download: http://android.clients.google.com/p...206299fe6.signed-soju-ota-121341.da820629.zip (Model: i9020T Full Rom: GRJ22, KD1 )
put it in the root of the internal sd.
boot back up to bootloader and start it, it will auto wipe/restore back to stock 2.3.4
Click to expand...
Click to collapse
So I rooted, then put CM10.1 nightly and gapps on my sdcard, then went to flash, and I spaced out and accidentally formatted SDCARD when i know that I shouldnt have. crap.
i tried using the "sideload" feature but it wouldnt work on my adb-mac version, i also tried adb pushing ROM files to SDCARD, it says transfered but when i go to flash it says no files in SDCARD, I also tried pushing to SDCARD/0 but i get an error that it isnt a directory since it is formatted.
SOME ONE PLEASE give me instructions on what to do. Do I have to go back to stock or can I just get this to go straight to CM10.1? Id prefer straight to CM10.1 obviously.
crackmulah said:
So I rooted, then put CM10.1 nightly and gapps on my sdcard, then went to flash, and I spaced out and accidentally formatted SDCARD when i know that I shouldnt have. crap.
i tried using the "sideload" feature but it wouldnt work on my adb-mac version, i also tried adb pushing ROM files to SDCARD, it says transfered but when i go to flash it says no files in SDCARD, I also tried pushing to SDCARD/0 but i get an error that it isnt a directory since it is formatted.
SOME ONE PLEASE give me instructions on what to do. Do I have to go back to stock or can I just get this to go straight to CM10.1? Id prefer straight to CM10.1 obviously.
Click to expand...
Click to collapse
Push cwm via fastboot then reflash the rom
Fastboot flash recovery (your recovery)
Sent from my Nexus 4
Hindsight 20/20, but it never hurts to do an adb backup, it will b/u your sdcard as well.
For the future: http://forum.xda-developers.com/showthread.php?t=1420351
mark manning said:
Push cwm via fastboot then reflash the rom
Fastboot flash recovery (your recovery)
Sent from my Nexus 4
Click to expand...
Click to collapse
did this, but still same error, no files found in sd card. i did not think this would solve it but i tried anyway...
crackmulah said:
did this, but still same error, no files found in sd card. i did not think this would solve it but i tried anyway...
Click to expand...
Click to collapse
So you've successfully flashed a recovery img via fasboot? Did you also push a copy of the ROM zip back to your phone?
Boot to recovery and then adb push the ROM to the sd card.
Code:
adb push yourROMsName.zip /sdcard/
The above code assumes you've placed the rom zip in the adb or platform-tools folder on your PC.
Can't you just boot into fastboot, flash a recovery, boot into said recovery and mount the internal storage and drag and drop the files from your computer?
How did you format the SD card when the phone doesn't have one?
jakejm79 said:
Can't you just boot into fastboot, flash a recovery, boot into said recovery and mount the internal storage and drag and drop the files from your computer?
How did you format the SD card when the phone doesn't have one?
Click to expand...
Click to collapse
The internal storage is considered an SD card.
Sent from my Nexus 4
CMNein said:
So you've successfully flashed a recovery img via fasboot? Did you also push a copy of the ROM zip back to your phone?
Boot to recovery and then adb push the ROM to the sd card.
Code:
adb push yourROMsName.zip /sdcard/
The above code assumes you've placed the rom zip in the adb or platform-tools folder on your PC.
Click to expand...
Click to collapse
yes i did repush the rom file. this isnt working because i dont believe that flashing a recovery adds folder/partition information to the sdcard. maybe im wrong, but it didnt work.
crackmulah said:
yes i did repush the rom file. this isnt working because i dont believe that flashing a recovery adds folder/partition information to the sdcard. maybe im wrong, but it didnt work.
Click to expand...
Click to collapse
Are there any spaces in the ROM zips name?
CMNein said:
Are there any spaces in the ROM zips name?
Click to expand...
Click to collapse
lol no
I am currently using Wug's Nexus Toolkit to try to flash stock from softbrick mode...will let you know how it goes
EDIT:: This is giving me some trouble as I cant turn on USB DEBUGGING (because i have no OS installed) to install the drivers and such.....
PLEASE KEEP IDEAS ROLLIN...
crackmulah said:
lol no
I am currently using Wug's Nexus Toolkit to try to flash stock from softbrick mode...will let you know how it goes
EDIT:: This is giving me some trouble as I cant turn on USB DEBUGGING (because i have no OS installed) to install the drivers and such.....
PLEASE KEEP IDEAS ROLLIN...
Click to expand...
Click to collapse
Just go back to stock
Sent from my Nexus 4
mark manning said:
Just go back to stock
Sent from my Nexus 4
Click to expand...
Click to collapse
this is what im trying to do lol...having trouble tho. what is your recommended method?
crackmulah said:
this is what im trying to do lol...having trouble tho. what is your recommended method?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2010312
Sent from my Nexus 4
You could also try wugfresh's toolkit and selecting "Back to Stock" -> "Soft-bricked".
mark manning said:
http://forum.xda-developers.com/showthread.php?t=2010312
Sent from my Nexus 4
Click to expand...
Click to collapse
ya im gonna do that if this Wug's Toolkit wont do the trick...seems to be working now tho...in middle of flashing stock
crackmulah said:
ya im gonna do that if this Wug's Toolkit wont do the trick...seems to be working now tho...in middle of flashing stock
Click to expand...
Click to collapse
You should learn how to do this without tool kits. Those things while helpful are nothing more than a crutch
Sent from my Nexus 4
mark manning said:
The internal storage is considered an SD card.
Sent from my Nexus 4
Click to expand...
Click to collapse
Yeah but doesn't the Nexus 4 lump all the internal storage together, I know other devices like the OXL have like 6GB internal storage and then a 'simulated' mSD card of about 10GB, making 16GB total. But the Nexus 4 uses the whole 16GB (or 8GB) as internal storage.
mark manning said:
You should learn how to do this without tool kits. Those things while helpful are nothing more than a crutch
Sent from my Nexus 4
Click to expand...
Click to collapse
yes definitely agreed.
although ive always wanted to try one, and it worked! if this were to happen again (if i dont shoot myself) then i will be doing it manually.
Thanks so much to everyone for all the help! I am now running Official CM10.1 Nightly (newest) and running beautifully so far. This is my second N4 tho, so I will be using my 1st stock one for today since its already setup, have to go to work now and will setup my new CM10.1 N4 later, hopefully wont find any crazy bugs...
I had the same problem and after reading this thread I tried the Fastboot method first:
after I finished it didnt boot so I continue with the inst', then it booted but only with 8GB, so I continue with the inst' and from that stage it just didnt boot.
At the end I tried the root toolkit V1.6.2 and the phone back to life with stock rom and 16GB.
I'm back to stock now. But I've used the sideload successfully. After you get your phone restored, you'll probably want to do a full factory reset because some of your pushes have probably gone through and are now eating up space. You can't delete them that I know of unless you FULLY format.
ANYWAY
When I got sideload to work, I had to push it to /sdcard/0/, /sdcard0/, or something like that. Wish I could be more specific, but I don't want to change from stock to install cwm (the ROMS have too many bugs so far, and we might be getting 4.2.2)
The key is finding the right directory to push it to. Experiment with slashes, and it SHOULD work.
My Nexus 10 stopped working after I've transferred about 14gb of movies on it. I copied them in windows 8 when nexus was plugged in USB.
It doesn't boot pass Google logo now, doesn't even reach Nexus symbol.
I can boot device in a bootloader and load a recovery. I did wipe/factory reset and also cleaned the cache, but that didn't help to solve the problem.
I have a suspicion that a filesystem is corrupt and e2fsck needs to run and fix the problems but I don't know how to start it.
I'm running a stock 4.2.1 not rooted or unlocked.
The battery level is above 70 and devices has been charging from the wall for 2 hrs at least.
Can anyone advice something to resolve the problem?
well, you still have a warranty.
that'd be my best bet, since if you hack it and its' still broken, you *might* not have a warranty.
Did you try flashing a stock image off the forums?
Sent from my Galaxy Nexus using Tapatalk 2
Less than a month old too..
Sent from my HTC PH39100 using xda app-developers app
I would replace it. It would suck to tinker with it and find out you can't fix it and the warranty is void.
Either get it replaced, or attempt to root it and flash a new ROM. I know you said wiping didnt help, but when you unlock it does a complete wipe of EVERYTHING so it might make a difference.
THe faster option to try is obviously rooting it, the safer option is probably just to get it RMA'd
Guys, Thanks for replies and suggestions.
So what I tried to do in last few days was:
I downloaded official 4.2 stock Rom and tried to reflash it together with a bootloader. I used "fastboot" to erase all partitions first, then flashed a bootloader and then flashed Rom. I had to run "oem unlock" otherwise fastboot didn't want to perform an operation.
The tablet still doesn't work, it's stuck on Google logo on a boot stage, not even reaching nexus symbol.
I didn't try to root it and install a custom Rom, because I'm afraid that I with loose a warranty. I believe the procedure above does wipe everything possible on a filesystem so I didn't go for a custom Rom solution.
I don't see a possible solution to restore a device now so I will return it on a warranty.
jodvova said:
My Nexus 10 stopped working after I've transferred about 14gb of movies on it. I copied them in windows 8 when nexus was plugged in USB.
It doesn't boot pass Google logo now, doesn't even reach Nexus symbol.
I can boot device in a bootloader and load a recovery. I did wipe/factory reset and also cleaned the cache, but that didn't help to solve the problem.
I have a suspicion that a filesystem is corrupt and e2fsck needs to run and fix the problems but I don't know how to start it.
I'm running a stock 4.2.1 not rooted or unlocked.
The battery level is above 70 and devices has been charging from the wall for 2 hrs at least.
Can anyone advice something to resolve the problem?
Click to expand...
Click to collapse
If you want to try e2fsck look at this quote/post: http://forum.xda-developers.com/showpost.php?p=34865732&postcount=162
wptski said:
If you want to try e2fsck look at this quote/post: http://forum.xda-developers.com/showpost.php?p=34865732&postcount=162
Click to expand...
Click to collapse
As I understand I need to be rooted with a custom recovery?
Can I run "adb" under a stock recovery?
jodvova said:
Guys, Thanks for replies and suggestions.
So what I tried to do in last few days was:
I downloaded official 4.2 stock Rom and tried to reflash it together with a bootloader. I used "fastboot" to erase all partitions first, then flashed a bootloader and then flashed Rom. I had to run "oem unlock" otherwise fastboot didn't want to perform an operation.
The tablet still doesn't work, it's stuck on Google logo on a boot stage, not even reaching nexus symbol.
I didn't try to root it and install a custom Rom, because I'm afraid that I with loose a warranty. I believe the procedure above does wipe everything possible on a filesystem so I didn't go for a custom Rom solution.
Click to expand...
Click to collapse
A custom ROM wouldnt help I dont think. The procedure you did is the important part before flashing a new ROM so if it didnt work then dont bother with anything custom.
jodvova said:
As I understand I need to be rooted with a custom recovery?
Can I run "adb" under a stock recovery?
Click to expand...
Click to collapse
ADB commands are run when you are booted into the tablet if I remember right.
Now that you've installed a stock ROM, go into recovery and factory reset. This may help your bootloop issue.
Sent from my Galaxy Nexus using Tapatalk 2
Blueback22 said:
Now that you've installed a stock ROM, go into recovery and factory reset. This may help your bootloop issue.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
I did that couple of times, it didn't help.
Guys,
Looks like a partition table got screwed up, because when I run e2fsck on any of partitions (system, userdata, boot), it says: "attempt to read block from filesystem resulted in short read".
Does anyone know how to fix it?
Or where can I find Nexus 10 PIT file?
jodvova said:
Guys,
Looks like a partition table got screwed up, because when I run e2fsck on any of partitions (system, userdata, boot), it says: "attempt to read block from filesystem resulted in short read".
Does anyone know how to fix it?
Or where can I find Nexus 10 PIT file?
Click to expand...
Click to collapse
Have you tried to go into stock recovery, and select the adb side load and try manually push the files like that?
Sent from my Nexus 10 using xda app-developers app
evolishesh said:
Have you tried to go into stock recovery, and select the adb side load and try manually push the files like that?
Sent from my Nexus 10 using xda app-developers app
Click to expand...
Click to collapse
Can you elaborate here?
Which files should I push? A Rom?
I am facing the same situation and it is not going past the nexus logo screen lol. I tried flashing factory images from here in fastboot mode but its still not working. In recovery, its showing can't mount SD card even after I tried mounting SD card and i tried wiping, factory reset and nothing. SD card still can't mount also and I wonder if that is the problem. I'm try some more.
So, I just fixed it and my nexus 10 boots up and all good again. Basically in bootloader, you just need to flash the userdata.img and cache.img also from the extracted files of the factory image file as I noticed it wasn't flashing those 2 files when I just flashed/updated the image.zip file with this command fastboot -w update image-mantaray-jop40c.zip and it was only flashing the system.img, recovery.img, boot.img so I extracted this image-mantaray-jop40c.zip file and I flashed the userdata.img and cache.img files manually and rebooted and its all good again back to stock.
NeverAlwaysEver said:
So, I just fixed it and my nexus 10 boots up and all good again. Basically in bootloader, you just need to flash the userdata.img and cache.img also from the extracted files of the factory image file as I noticed it wasn't flashing those 2 files when I just flashed/updated the image.zip file with this command fastboot -w update image-mantaray-jop40c.zip and it was only flashing the system.img, recovery.img, boot.img so I extracted this image-mantaray-jop40c.zip file and I flashed the userdata.img and cache.img files manually and rebooted and its all good again back to stock.
Click to expand...
Click to collapse
Just to clarify did you use fastboot to flash userdata.img? Which command did you use "fastboot -w update userdata.img"?
Also where did you find userdata.img ???
It doesn't come in nexus 10 factory image. It only has boot, cache, recovery, system and a bootloader.
So I just repaired my broken screen and after booting I had an old custom rom on my Nexus so I downloaded a new rom with Gapps file. Well for some reason I decided to delete some older files, which included some older roms. Well the rom failed and now my nexus stays booted into CWM recovery. It won't let me mount the storage to add files from my computer for some reason. Also I've tried Rom toolkits and they keep getting stuck waiting for device.
There must be some easy way to ADB push some files to my download folder right?
rezistrat said:
So I just repaired my broken screen and after booting I had an old custom rom on my Nexus so I downloaded a new rom with Gapps file. Well for some reason I decided to delete some older files, which included some older roms. Well the rom failed and now my nexus stays booted into CWM recovery. It won't let me mount the storage to add files from my computer for some reason. Also I've tried Rom toolkits and they keep getting stuck waiting for device.
There must be some easy way to ADB push some files to my download folder right?
Click to expand...
Click to collapse
1) First, beware of discharging the tablet by letting it sit with either the bootloader (fastboot mode) or the custom recovery running. I will presume you can get the tablet into full-shutdown when you are not working on it... unless you say otherwise. Make sure you keep the tablet charged to prevent the situation from getting worse.
2) Your mention of "mounting" is a little bit ambiguous; but as an alternative you can put a ROM on a USB memory stick and mount it via a OTG cable. TWRP can do this; I'm not sure about CWM as I don't use it.
3) Yes you should be able to push a big ROM file via adb when a custom recovery is running.
There a a couple of things that could prevent this:
a) you don't have drivers on your Win-doze PC working correctly,
b) you have a flaky USB hardware link,
c) the ext4 filesytem which is in the userdata partition is so bolluxed up that it can't be mounted, so even if there are no problems such as (a) or (b), there is no "destination" for the ROM file to be copied to. You could try to flash a ROM directly from an OTG-mounted USB key, but it will still fail if the /data partition ca't be mounted.
Note that condition (b) above sometimes has the behavior that small files such as the bootloader or boot image can be transferred (e.g. via fastboot flash or adb push), but larger files will error out or stall. That is simply because if you have a flaky conection, the probability of failure increases in proportion to the amount of data being transferred. Sometimes these types of problems can be resolved by using a different USB port on the PC, or different data cable; other times using a different PC.
From your description it is not clear whether you have condition (a), (b) or (c) going on; please clarify.
Thanks for the reply. I used the toolkit which was awesome. Side loaded factory image and finally it worked
I somehow deleted my recovery as well so no adb but fast boot worked fine. Needless to say I thought I was bricked thank god for developers
Sent from my SPH-L900 using xda app-developers app
I accidentally wiped the OS from advanced wipe option. How do I get my phone to work again. I tried to operate adb sideload from recovery but it failed. I have downloaded the stock rom but I do not know how to install it.
Please help.
Thanks.
Kalaxy said:
I accidentally wiped the OS from advanced wipe option. How do I get my phone to work again. I tried to operate adb sideload from recovery but it failed. I have downloaded the stock rom but I do not know how to install it.
Please help.
Thanks.
Click to expand...
Click to collapse
Just flash it from custom recovery, so download it into ur phone go to recovery and simply flash it and all should be good.
Sent from my Nexus 6P using Tapatalk
Exiwolfman said:
Just flash it from custom recovery, so download it into ur phone go to recovery and simply flash it and all should be good.
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
How do I download it to my phone if I cannot boot into it. Is there any way I can copy a zip file (rom) onto the phone's internal memory.?
Your phone should boot into recovery, so as long as it goes on and boots all u do u is use ur pc to move file over and flash it...
Sent from my Nexus 6P using Tapatalk
Kalaxy said:
How do I download it to my phone if I cannot boot into it. Is there any way I can copy a zip file (rom) onto the phone's internal memory.?
Click to expand...
Click to collapse
Boot into bootloader (hold power and system on), flash the though recovery through adb, mount your .zip,, flash your .zip through recovery. Sorry if that doesn't make sense, I've been drinking with the roommates, lol.
Edit: if that doesn't work, send me an IM and I will help you in the morning
Sent from my Huawei Nexus 6P using XDA Labs
Which state is your phone in right now? Is it bootlooping or in recovery?
Sent from my HTC 10 using Tapatalk
The same thing happened to me also! The whole /data (incl. sdcard) partition went corrupt (showed up in TWRP as eemc instead of ext4) & the /vendor failed to mount.
First I had to repair the /data partition (unfortunately the data was lost, as it repaired to a blank partition). I ended up having to go home (was at work at the time) & hook the phone up to the PC & download the ROM & transfer it onto the sdcard. I'm not entirely sure why/how this happened, but I believe it was because a corrupt vendor IMG. Although that theory doesnt include why the /data partition corrupted, it only explains why the /vendor partition failed to mount.
Fastboot flash system system.img
?
removed
I have the same issue. The problem is, that my computer will not recognize the phone in bootloader mode or in recovery mode(MTP enabled). How can install usb drivers without being able to boot into phone OS???? I've tried Nexus Toolkit with no success. Please help?
Have a look here how to load in bootloader, flash, etc.
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
So I did the same thing. I'm sitting in TWRP right now but have nothing on the phone. Will I be able to reboot from TWRP into the bootloader and just use the flash-all command to get my phone to boot back up, then just go through the process of custom recovery again?
Basically I'm worried about leaving twrp without an OS. I didn't wipe bootloader did I? Also, I tried to download a ROM and just drag it to internal memory, but I can't seem to add anything to the internal memory.
dbroer91884 said:
So I did the same thing. I'm sitting in TWRP right now but have nothing on the phone. Will I be able to reboot from TWRP into the bootloader and just use the flash-all command to get my phone to boot back up, then just go through the process of custom recovery again?
Basically I'm worried about leaving twrp without an OS. I didn't wipe bootloader did I? Also, I tried to download a ROM and just drag it to internal memory, but I can't seem to add anything to the internal memory.
Click to expand...
Click to collapse
Hi... Just boot into recovery and reflash system.img from the factory image of your choice in bootloader with fastboot. Also flash the vendor image from the same factory image. Done...
Or reflash the whole package with flash all (manually is better imho). But you'll waisted time... Let your phone reboot into Android and you'll have your internal storage back.
5.1 said:
Hi... Just boot into recovery and reflash system.img from the factory image of your choice in bootloader with fastboot. Also flash the vendor image from the same factory image. Done...
Or reflash the whole package with flash all (manually is better imho). But you'll waisted time... Let your phone reboot into Android and you'll have your internal storage back.
Click to expand...
Click to collapse
Thats what I thought. JUst wanted to make sure I could get into bootloader still
dbroer91884 said:
So I did the same thing. I'm sitting in TWRP right now but have nothing on the phone. Will I be able to reboot from TWRP into the bootloader and just use the flash-all command to get my phone to boot back up, then just go through the process of custom recovery again?
Basically I'm worried about leaving twrp without an OS. I didn't wipe bootloader did I? Also, I tried to download a ROM and just drag it to internal memory, but I can't seem to add anything to the internal memory.
Click to expand...
Click to collapse
Yes TWRP has a reboot to bootloader option available. So you can access fastboot via bootloader to flash the necessary images. Just don't forget to re flash TWRP image again in case the stock recovery image was flashed beforehand.
The odd thing was that I did choose that option to boot to bootloader in twrp and it didn't work. I ended up having to reboot to bootloader manually. Not a big deal. All is working now, but thought that was interesting.
Kalaxy said:
I accidentally wiped the OS from advanced wipe option. How do I get my phone to work again. I tried to operate adb sideload from recovery but it failed. I have downloaded the stock rom but I do not know how to install it.
Click to expand...
Click to collapse
Exactly which partitions did you wipe? system? data? Internal Storage (userdata)? all of the above? Hopefully you did not wipe userdata (all your stuff). Were you on a stock ROM? You should be able to d/l the Google image from the same build you were on, extract system and data and fastboot flash those. Don't flash userdata. All your stuff should be there. Follow the tutorial on how to set up fastboot and selectively flash partitions.
---------- Post added at 06:49 AM ---------- Previous post was at 06:44 AM ----------
This thread got hijacked at least 3 times. Let's hope OP can find his way back.
pocholo36 said:
I have the same issue. The problem is, that my computer will not recognize the phone in bootloader mode or in recovery mode(MTP enabled). How can install usb drivers without being able to boot into phone OS???? I've tried Nexus Toolkit with no success. Please help?
Click to expand...
Click to collapse
Try this Hope you get solution to your problem of installing adb and fastboot tools in the correct manner.
I just by mistake deleted my internal storage.
I have TWRP, how do i put the ROM on there and flash it? Someone please help.
Thanks