Database Info

[Q] Xoom memory/flash LOCKED, Can not Factory Default ???

Posted this General, but hope to get a better response in here ...
Ok i will explain ...
Got my Xoom ROOTED but decided to put it back to stock, so I UNROOTED by flashing my Canadian 3.0 version, boot it up update to the 3.1 OTA and then setup my market, the XOOM FC out alot so i want to try "hacked firmware".
Boot to fastboot to flash CWM recovery, all the flash show completed OK, reboot into recovery to only found out that it's not there ... ok, try factory reset from the Recovery, all good and then the Xoom reboot ... all my data is still there, then try Setting > Private > factory reset ... all OK, but can boot into the Recovery to fully reset ... no problem, i will reflash a different version via Fastboot.
Try the US-Wifi version, all the flash/erase when OK but still at Canadian 3.1 ... then try installing ROM manager, install fine and working (of cause no Root access). Reboot and the ROM manager is gone ...
Look like the Memory of the Xoom somehow is LOCKED?
Anyone have a idea? i'm taking out the battery for 1h now and hope to have some reaction ... but still nada!!!
Help!!! Thanks

Use adb to flash stock imgs. You need to fastboot flash instead of using cwm. Cwm sucks! I refuse to use it because it doesn't seem to flash crap right. Once your rooted you can use it to flash a rom and that's it. ADB is easy as long as you go one line at a time and be patient as you do it. Start with OEM unlock, then flash the boot, recovery, system, erase the cache, and the reboot.
Sent from my Xoom using xda premium

hammer4203 said:
Use adb to flash stock imgs. You need to fastboot flash instead of using cwm. Cwm sucks! I refuse to use it because it doesn't seem to flash crap right. Once your rooted you can use it to flash a rom and that's it. ADB is easy as long as you go one line at a time and be patient as you do it. Start with OEM unlock, then flash the boot, recovery, system, erase the cache, and the reboot.
Sent from my Xoom using xda premium
Click to expand...
Click to collapse
All flashboot flash command is confirmed to be working, but i think it's not written to the Xoom memory, because as soon as i boot it, it's just boot into the Old version (the one this is there before flash).
So can not event flash CWM or Rooted ... when i go to Recovery and try update with update.zip, it's alway fail with E: verify something ....
Any other ideal or else ... i guess this is the 1st "Working BRICKED Xoom"

Could be the wrong update file. Make sure of the file as well. Re download it too. Could be corrupted.
Sent from my ADR6400L using xda premium

Oh you need root again? If that's the case you have to adb push the file and update via adb to get there. You can't do it from cwm.
Sent from my ADR6400L using xda premium

hammer4203 said:
Oh you need root again? If that's the case you have to adb push the file and update via adb to get there. You can't do it from cwm.
Sent from my ADR6400L using xda premium
Click to expand...
Click to collapse
His Xoom has been relocked and needs to be unlocked again in order for him to be able to flash anything at all.
This thread is already active in General, don't waste more time here.

Yeah I see that. He needs to fastboot OEM unlock.
Sent from my Xoom using xda premium

Guys, thanks for you reply, but I know how to OEM unlock etc ... i have also make the "factory cable" for it, i have another Xoom that i'm testing all the steps and files and the others Xoom working like charm ... but this one is a [email protected]#%ch ...
If i can only flash CWM and i will be good, because i have make a backup from it to start, but now can not event flash anything to it ... memory seem to be "volatile" so event files that i copy into it will be wipe once the tablet reboot ... so it's beyond flashboot or adb ... i've event gone to RSD Lite but can not fine (or know how to dump my other Xoom) a right dump to flash it from there ...

NS4G- cm9 froze, pulled bat. stuck at boot, can access CWM Recovery, can't mnt SD

I'm was using CM9 nightly and it froze, I removed the battery and tried to boot but it hangs at Google screen.
I can access bootloader and recovery but, in CWM touch recovery, I can't mount or format system, sdcard, or data but can wipe and mount/unmount cache.
And I can't mount USB in recovery
I can access through fastboot, so what would I need to go about doing to get this thing back up and running?
I don't want to try to many things and screw it up worse or something. It seems to me like the partitions got screwed up or something, but that's just a wild guess. Can anyone help me fix this or point me in the right direction?

jivetrky said:
I'm was using CM9 nightly and it froze, I removed the battery and tried to boot but it hangs at Google screen.
I can access bootloader and recovery but, in CWM touch recovery, I can't mount or format system, sdcard, or data but can wipe and mount/unmount cache.
And I can't mount USB in recovery
I can access through fastboot, so what would I need to go about doing to get this thing back up and running?
I don't want to try to many things and screw it up worse or something. It seems to me like the partitions got screwed up or something, but that's just a wild guess. Can anyone help me fix this or point me in the right direction?
Click to expand...
Click to collapse
sounds like the sd(storage) is gone bad or going bad.

simms22 said:
sounds like the sd(storage) is gone bad or going bad.
Click to expand...
Click to collapse
Any way I could test that theory, through ADB or something?

jivetrky said:
Any way I could test that theory, through ADB or something?
Click to expand...
Click to collapse
maybe a logcat while trying to access the storage? but really, if it isnt accessible, thats all the info you should need.

Wow... internal memory already gone bad? Have you tried fastboot flash the factory images for ns4g?
Sent from my Nexus S 4G using XDA

rasengan82 said:
Wow... internal memory already gone bad? Have you tried fastboot flash the factory images for ns4g?
Sent from my Nexus S 4G using XDA
Click to expand...
Click to collapse
the internal storage going bad is actually a very common problem.

I guess locking bootloader and claiming warranty is the way to go.
Sent from my Nexus S 4G using XDA

rasengan82 said:
I guess locking bootloader and claiming warranty is the way to go.
Sent from my Nexus S 4G using XDA
Click to expand...
Click to collapse
How might I go about doing that?

jivetrky said:
How might I go about doing that?
Click to expand...
Click to collapse
fastboot oem lock
with fastboot while in the bootloader. provided that fastboot sees your device(fastboot devices).

Just a warning... if you oem lock you won't be able to oem unlock again IF you internal memory is indeed corrupted.
Sent from my Nexus S 4G using XDA

rasengan82 said:
Just a warning... if you oem lock you won't be able to oem unlock again IF you internal memory is indeed corrupted.
Sent from my Nexus S 4G using XDA
Click to expand...
Click to collapse
very true. but if youre doing it to send back to samsung for a warranty repair, does it matter?

I don't know the inner workings of Android or this device specifically, but isn't there just a single bit of flash on the phone which is divided/partitioned into SD, system, etc. Is it possible that the partitions have just been corrupted or something like that? I was playing around just seeing what the phone could do and Odin3 will recognize it, but I didn't want to play around and screw anything up even more than it is.
Is it possible to use Odin to try and attempt a fix? I see there is a re-partition option, I was wondering if that could be worth a try?

Well, I guess I've given up and I'll just hope for Samsung to replace/fix it.
Google-foo has not shown me anything as far as trying to repartition just in case it was corrupted or something; couldn't find any images out there with PITs. I'm able to write the bootloaders and recovery so I just used the one-click-stock provided boot and recovery images and flashed them with fastboot then locked it.
Doesn't boot and recovery go on the same flash that is theoretically bad which is stopping SD, system, & data from being mounted?

Just for the sake, what happens now if you do fastboot oem unlock?
Do you get an error? If you don't get an error, unlock it and then download this:
https://dl.google.com/dl/android/aosp/sojus-imm76d-factory-10660f4c.tgz
Unzip everything and put it on a folder (you will find several img files). Now start the phone again in fastboot mode.
fastboot flash bootloader bootloader-crespo4g-d720sprke1.img
fastboot reboot-bootloader
fastboot flash radio radio-crespo4g-d720sprlc1.img
fastboot reboot-bootloader
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash userdata userdata.img
fastboot erase cache
fastboot reboot

rasengan82 said:
Just for the sake, what happens now if you do fastboot oem unlock?
Do you get an error? If you don't get an error, unlock it and then download this:
https://dl.google.com/dl/android/aosp/sojus-imm76d-factory-10660f4c.tgz
Unzip everything and put it on a folder (you will find several img files). Now start the phone again in fastboot mode.
fastboot flash bootloader bootloader-crespo4g-d720sprke1.img
fastboot reboot-bootloader
fastboot flash radio radio-crespo4g-d720sprlc1.img
fastboot reboot-bootloader
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash userdata userdata.img
fastboot erase cache
fastboot reboot
Click to expand...
Click to collapse
I can't unlock it now, as the bootloader pops up a screen that says to unlock it you have to wipe/factory reset. But it hangs on that probably because it can't see system/data.
I did try flashing it with fastboot though, before I locked it, and I could flash boot, recovery, and radio but it will just hang forever on flashing system. It never gives an error. I let it sit there for over an hour and it never did anything.
So I guess now that it's locked there really is nothing I can do.

Ok, I think Samsung warranty is the only thing left.

Forgot to update, sent to Samsung and they replaced the PBA, so the flash was apparently bad. Thanks for the advice, everyone!
Was only about a week turn around, just took me a while to actually get the RMA started.
They even send a UPS label to ship it to them then took a week turnaround, overall it was good service.

Relock bootloader without using recovery?

Hi.
I am about to RMA my phone and need to lock the bootloader..
BUT - I cant get into recovery.
I have tried everything, reverted to stock image (followed the thread how to return to stock image) , but no matter what, I cant boot into recovery.
I can get into the bootloader / fastboot , ie and run adb commands, but I cant boot into recovery.. its just flashed the google logo and then gets tuck there ..
Is there any way I can relock the bootloader given my predicament?
it's doing some other pretty weird stuff.. pretty sure the battery is near flat, but If I plug it in to charge, it flashes the charging logo and then about 10 seconds tries to boot,.. flashes the google logo and then about 1 second ofthe spinning colour circles.. then just black screen.. even if I go into the bootloader and hit power off..
If anyone has any Ideas I would love to know.
Does anyone know if google will RMA with an unlocked bootloader or am i screwed? This sucks!

1) you cannot run adb commands from fastboot. Adb commands only work in android or recovery
2) you just use fastboot commands from fastboot (bootloader). Accessing recovery is not part of the process
-----------------------
Sent via tapatalk.
I do NOT reply to support queries over PM. Please keep support queries to the Q&A section, so that others may benefit

You lock the bootloader from the bootloader, but it sounds like you have lots of problems. I would just send it back if you can't lock it
Sent from my Nexus 5

Just boot into bootloader and run fastboot oem lock. No need to go to recovery for locking the bootloader. If you have flashed the stock images already the data was already wiped.
Sent from my Nexus 5 using Tapatalk

Why is there a whole thread about relocking the bootloader and a zip to flash via CWM (talking about resetting the tamper flag?)
http://forum.xda-developers.com/showthread.php?t=2513701
If I just do fastboot oem lock isn't Google going to be able to tell I have been flashing..?

llewelld said:
Why is there a whole thread about relocking the bootloader and a zip to flash via CWM (talking about resetting the tamper flag?)
http://forum.xda-developers.com/showthread.php?t=2513701
If I just do fastboot oem lock isn't Google going to be able to tell I have been flashing..?
Click to expand...
Click to collapse
If you have a custom recovery/ROM on the phone then of course they'll know what you've done! You have to flash the factory image and then relock the bootloader and you'll be OK

EddyOS said:
If you have a custom recovery/ROM on the phone then of course they'll know what you've done! You have to flash the factory image and then relock the bootloader and you'll be OK
Click to expand...
Click to collapse
Why don't use Bootunlocker? You can unlock/relock directly from the Nex5 without loss data and no wipe!!

I seriously doubt that they will check the tamper flag. Maybe sprint would, but I doubt that Google will. Just relock the bootloader and send it in bro. You'll be OK. I've sent nexus 7, nexus 4 both back with an unlocked bootloader and got my replacement no questions asked.
Sent from my Nexus 5 using Tapatalk

enzippo said:
Why don't use Bootunlocker? You can unlock/relock directly from the Nex5 without loss data and no wipe!!
Click to expand...
Click to collapse
because I cant boot. - cant get past the google logo so I cant run any apps..

llewelld said:
because I cant boot. - cant get past the google logo so I cant run any apps..
Click to expand...
Click to collapse
What about trying Wugfresh toolkit he has a setting in it for recovering from a none booting/softbricked device.

Download the factory images, unzip the file, while in the bootloader, click on flash-all.bat. when that's done, get back into the bootloader, and open a command window, and type fastboot oem lock. Now you are back to a stock phone.
Sent from my Nexus 5 using XDA Premium 4 mobile app

lyall29 said:
Download the factory images, unzip the file, while in the bootloader, click on flash-all.bat. when that's done, get back into the bootloader, and open a command window, and type fastboot oem lock. Now you are back to a stock phone.
Sent from my Nexus 5 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Thanks.. did all that... and have had to RMA the phone.. its screwed just died.. I think the first time I have had a phone just die that is so new and not from any soft of physical damage. Thanks!

[Q] Stuck at X screen

Obviously I'm a noob, so sorry if this is stupid or there is an obvious answer (I've spent a lot of time looking and couldn't find it though). I was having problems with my phone so decided to flash back to stock and relock it to 'start again'.
Maybe that wasn't a great idea because I've had lots of problems since then. When I try to flash back to stock using nexus root toolkit I get "failed (remote: invalid bootloader)" and the phone finishes still in bootloader. There was a suggestion to force flash, but given the warnings around that I'm pretty nervous about doing that. If I then start my phone up it stays on the google screen for quite a while and then gets stuck on the X screen (it isn't frozen because the animation keeps running, but nothing else happens, even if I leave it for an hour).
I did a bit more reading and tried wiping the dalvik cache and cache. It then said it was upgrading android, optimising apps etc, but then got stuck again. I tried resetting again and the phone now restarts when I push the off button and slowly goes through both the google screen and X screen.
This might be a stupid problem, but I'm stuck so any help would be great.

Flash the stock images manually rather than with a toolkit. You can find a guide stickied under the nexus 5 general section.
Sent using xda-developers app

http://forum.xda-developers.com/showthread.php?t=2513701
[TUTORIAL] How to flash a factory image | Return to stock | Unroot your Nexus 5
Follow this carefully step by step using method 2. Be extremely careful flashing the boot loader, in fact you can probably skip that part. As long as your boot loader is always in tact it's virtually impossible to brick. As of right now you're stuck in what's called a boot loop. Most likely, either your boot.img (not the same as boot loader) or system.img (aka ROM/firmware) is messed up and is causing it.
Welcome to modding, have fun, but be smart
Sent from my Nexus 5 using xda app-developers app

Chromium_ said:
Flash the stock images manually rather than with a toolkit. You can find a guide stickied under the nexus 5 general section.
Sent using xda-developers app
Click to expand...
Click to collapse
Thanks. Either a new problem or a related one - following the guide for setting up adb and fastboot, when i type adb devices into the command prompt nothing is listed (says "list of devices attached", but there isn't anything listed).

beshakey said:
Thanks. Either a new problem or a related one - following the guide for setting up adb and fastboot, when i type adb devices into the command prompt nothing is listed (says "list of devices attached", but there isn't anything listed).
Click to expand...
Click to collapse
Go into fastboot mode and run "fastboot devices". If the device shows up there, that's good enough.
Sent using xda-developers app

Chromium_ said:
Go into fastboot mode and run "fastboot devices". If the device shows up there, that's good enough.
Sent using xda-developers app
Click to expand...
Click to collapse
Thanks, that worked. But having done it when I reboot the phone it does the same thing (hangs of the Google screen for a long time then moves to the X screen and stays there). My phone is rooted and I have clockworkmod installed, so I selected fix root when asked, not sure if that is relevant?

Did you continue to follow the guide and flash the stock images in fastboot
Sent from my Nexus 5 using xda app-developers app

Yeah I did. I got the message "FAILED (remote:invalid bootloader image) and archive does not contain 'boot.sig' 'recovery.sig' and 'system.sig'. Everything else was OKAY. Put into recovery mode fine (with clockworkmod), wiped data and rebooted (fixing root when asked) but the problem described above remains.

More problems - tried doing it again, now it won't even boot up to the google/Android X screens. When I restart the screen lights up but nothing else. I can still reboot into the bootloader though. Arggh

beshakey said:
More problems - tried doing it again, now it won't even boot up to the google/Android X screens. When I restart the screen lights up but nothing else. I can still reboot into the bootloader though. Arggh
Click to expand...
Click to collapse
And you are following the factory image flashing guide that has been provided above?
Can you try going through the guide again, and tell us the specific errors that you are encountering.

And use method two, not the first one that talks about running the flash all script. You should be doing command's like "fastboot flash boot boot.img"
Sent from my Nexus 5 using xda app-developers app

beshakey said:
More problems - tried doing it again, now it won't even boot up to the google/Android X screens. When I restart the screen lights up but nothing else. I can still reboot into the bootloader though. Arggh
Click to expand...
Click to collapse
Don't worry, you'll get it, eventually. When you first start doing this kind of thing, it takes some getting used to because you have to read VERY carefully, and perform each step EXACTLY as stated. Computers are absolutely unforgiving of even the tiniest mistake, so you have to take your time, and be patient when you have to start all over. But, it's a challenge, and a learning process, and a lot of fun, once you get the hang of it.
Sent from my Nexus 5

OK, step by step. If you need more detail yell out.
1) I've downloaded ADB and Fastboot
2) If I put ADB devices into the command prompt I don't get any devices listed. But if I put in Fastboot devices I get the serial number of my phone
3) Previously I'd been using method one. So I now extract the image for hammerhead krt16m to my f:\ drive. I've also extracted radio-hammerhead-M8974A-1.0.25.0.17 and bootloader-hammerhead-HHZ11d to the same location and renamed them to radio.img and bootloader.img respectively
4) Phone is connected to computer and in fastboot (and detected by fastboot devices)
5) In command prompt when I type in fastboot flash bootloader f:/bootloader.img I get the error message FAILED (remoteL invalid bootloader image).
6) Flashed radio.img and rebooted bootloader and system.img (no reboot) without any errors (although they took a while)
7) Flashing userdata.img got the error 'FAILED (remote: flash write failure)
8) Performed all the remaining commands without any errors (when erasing the cache I got the message 'Did you mean to fastboot format this partition? erasing 'cache'... OKAY
9) Entered recovery mode. Earlier when I did this it was fine, but now (like when I try to start the phone) the screen lights up but no text etc appears
10) At this point I'm stuck, as I can't see the cwm text so can't select wipe data/factory data reset (although I did do this as part of earlier attempts)
From the 'on but no text' state, I can using the on button to restart into the same state or can enter fastboot (where text etc appears fine)

One at the boot loader you said you put f:/bootlaoder.img that was wrong, no drive letter. You do not need to flash your boot loader though anyways. Avoid doing that unless you have to, it is the only thing that will brick your phone.
You said system.img flashed fine, did not see any Menton of a boot.img or recovery.img. you need all three of these.
So, start over again. Make sure you flash a boot.img system.img and recovery.img separately. DO NOT flash the bootloader.img unless you have to (to update). Again, the boot loader is the one thing that will brick your phone if done wrong.
Sent from my Nexus 5 using xda app-developers app
---------- Post added at 07:31 AM ---------- Previous post was at 07:28 AM ----------
Sorry I just read through that tutorial and it does tell you to use drive letters. Im used to flashing with my files in the location of fastboot so I don't need to do that.
Sent from my Nexus 5 using xda app-developers app

@op why you are flashing 4.4 images?? it has a different bootloader then 4.4.2.
i guess your primary bootloader now is 11k and not 11d or 11a .....(since you took the ota out of the box)
bootloader version must match with the rest of images.
so download 4.4.2 images and flash them using 11k bootloader. (note that you have the old and new bootloaders on your device, volume down + power will take to the new bootloader 11k, and Volume down + volume up + power will take you to the old bootloader).
regarding adb command, it will not work in fastboot mode, it works when booting in os with usb debugging enabled, or in custom recovery mode

Good catch.
Sent from my Nexus 5 using xda app-developers app

samersh72 said:
@op why you are flashing 4.4 images?? it has a different bootloader then 4.4.2.
i guess your primary bootloader now is 11k and not 11d or 11a .....(since you took the ota out of the box)
bootloader version must match with the rest of images.
so download 4.4.2 images and flash them using 11k bootloader. (note that you have the old and new bootloaders on your device, volume down + power will take to the new bootloader 11k, and Volume down + volume up + power will take you to the old bootloader).
regarding adb command, it will not work in fastboot mode, it works when booting in os with usb debugging enabled, or in custom recovery mode
Click to expand...
Click to collapse
Thanks I'll try that. Is there any way for me to confirm on my phone what my primary bootloader is?

beshakey said:
Thanks I'll try that. Is there any way for me to confirm on my phone what my primary bootloader is?
Click to expand...
Click to collapse
Boot into it using power volume down and it will list the version
Sent from my Nexus 5 using xda app-developers app

travisjustin said:
Boot into it using power volume down and it will list the version
Sent from my Nexus 5 using xda app-developers app
Click to expand...
Click to collapse
Will try that, thanks.
I'm pretty sure I've done something stupid to cause this and I had a thought about what it might be - my phone was still at 4.3 for some reason. It would receive the update and install it, but the version wouldn't change to the new one. So should I try to track down the old 4.3.? bootloader?

beshakey said:
Will try that, thanks.
I'm pretty sure I've done something stupid to cause this and I had a thought about what it might be - my phone was still at 4.3 for some reason. It would receive the update and install it, but the version wouldn't change to the new one. So should I try to track down the old 4.3.? bootloader?
Click to expand...
Click to collapse
4.3? The nexus 5 ships with kitkat 4.4 ...there is no 4.3 for it.
Sent using xda-developers app

[Q] Nexus 5 boots in "erasing"

Completely stock Nexus 5 wont boot. When it powers on it goes into the animation of the Droid with "erasing" under it. This began randomly last night after I unplugged it from a car charger. Up until this point the phone was perfect.
I can boot into the option menu where I can select Restart Bootloader or Recovery mode, but no matter what I choose the phone restarts and goes directly to Erasing.
Any tips on how to recover without losing everything?
Thanks in advance ~ Shaneous

I'm not sure what the problem is. I haven't seen this issue before. But I'd try booting into the bootloader and flashing the cache.img with fastboot from the factory image of whatever version of android you're on. See method 2 of this http://forum.xda-developers.com/showthread.php?p=47156064
Sent from my Nexus 9 using XDA Free mobile app

jd1639 said:
I'm not sure what the problem is. I haven't seen this issue before. But I'd try booting into the bootloader and flashing the cache.img with fastboot from the factory image of whatever version of android you're on. See method 2 of this http://forum.xda-developers.com/showthread.php?p=47156064
Sent from my Nexus 9 using XDA Free mobile app
Click to expand...
Click to collapse
Will give this a shot right now. Thanks

Shaneous said:
Will give this a shot right now. Thanks
Click to expand...
Click to collapse
Well Method 2 will wipe the phone which is what I am trying to prevent. Also my computer cannot detect the phone when it is in fastboot mode.

Factory reset?

Shaneous said:
Well Method 2 will wipe the phone which is what I am trying to prevent. Also my computer cannot detect the phone when it is in fastboot mode.
Click to expand...
Click to collapse
You only want to run the fastboot flash cache cache.img of method 2, not all the commands. But not being detected by your pc is another issue. Does it show up in device manager at all? Do you have usb drivers installed?
Sent from my Nexus 5 using XDA Free mobile app

jd1639 said:
You only want to run the fastboot flash cache cache.img of method 2, not all the commands. But not being detected by your pc is another issue. Does it show up in device manager at all? Do you have usb drivers installed?
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Don't think he mentioned if his bootloader was locked or unlocked..
If it's locked, there is nothing you can do except sent it in for a repair (you'll likely lose everything anyways since they'll probably just do a motherboard swap), or unlock it (and lose data).
It it's unlocked, then there a multiple things you can do; flash factory images, use a custom recovery, etc.