Database Users

No disk mode / device not recognized after flashing PB00IMG.zip

Hey all,
I've been playing with roms on my phone for a while and went to root my dad's phone today. I followed the instructions like this (but pre 2.1) to root my phone with no issue. http://forum.xda-developers.com/showthread.php?t=647707
When I flashed the PB00IMG.zip on my dad's phone, nothing seemed abnormal until i tried to mount the phone's SD Card. Now dad's phone doesn't mount. My phone is recognized in windows and linux, dad's phone isn't recognized and doesn't mount in either. It does charge, and i've been using the same cable.
What can I do?

I'm not really an expert, but I would try a few different things, such as:
Pop the SD card out and back in.
Reboot.
Finish rooting. You don't need the card to mount. As long as USB debugging is on, you should be able to finish the other steps. Once you do those, and flash a new rom, your problems might work themselves out.
Once you've done these, and they don't work, then someone better versed than I might be able to point you in the right direction.
PS. Your dad's phone didn't have the 2.1 Update already? The guide you listed was from 1.5 to 2.1. I'm not sure if that makes a difference, but something to think about... I just walked someone through online last night to root their phone with this guide: http://forum.xda-developers.com/showthread.php?t=725096

ec- i have inserted and removed the card a few times, and rebooted a few times. usb debugging is on. before i started this process, the phone firmware was version 1.5, so no, i don't think it had the 2.1 update.
i would like to install the custom recovery, but when i try issuing "adb shell mount -o rw,remount /dev/block/mtdblock3 /system" i get an error saying something to the effect of device not found.
is there another way to flash a rom than with custom recovery? can i flash a custom rom (like ivan's 1.0b) in the way i flashed the unlocked hboot rom? or flash a nandroid without the custom recovery?
tia

WARNING
The PB00IMG.zip at the following link will prevent disk mode on your phone.
http://www.sendspace.com/file/g4n2q4
(from
[Walkthrough] From stock (1.5) to rooted 2.1 (update - new link)
http://forum.xda-developers.com/showthread.php?t=647707 )

install
make sure you install the drivers.

Need some help rooting... doesn't seem to be working.

Okay, I rooted once, but when I went to flash something in recover or simply back up my rom it said, it that the signature verification failed. So I unrooted and began to reroot my device, however, now it will not root.
The first time I rooted I used the z4mod one-click method. I tried that again but the loading icon just spins endlessly.
Now I tried manually with the rage method, however, it says in the tutorial to wait until it says "Children forked" but that message never appears, and I can still push su and busybox to the phone but to no avail.
Any insight as to what I am doing wrong? Thanks in advance!

When I rooted, I did so with the rage method. However, my first attempt just hung forever. So, I control-C'd, entered back into shell, and tried again. It worked the second time. Note you don't need to repeat the other steps, just the rage.bin
PS> I am getting that same signature issue when I try to run a recovery zip, however my phone is still rooted in adb shell.

I tried to do it again, and I realized the command adb shell doesn't work anymore. It just hangs forever and doesn't every add the "$" at the beginning of the line.

Don't be discouraged. I just rerooted mine because of my recent incident. I used fallingup's guide to restore all the way to stock.
Manual root in under 5 minutes, kinda:
http://www.screencast.com/t/YuIMfbi5

Stuck in read only?

To keep it relatively short, for whatever reason, my recovery is corrupted or broken. I had flashed clockwork, did a full backup, and have my UID and all of that stuff. Today, sometime after I started downloading files from Google Music, my tablet restarted, and now programs and applications constantly crash, presumibly since the tablet seems to be locked in Read Only mode. Chmod seems to work, but then nothing actually changes. Ive been able to seemingly uninstall root, and reinstall it, but its a hassle, and I dont think that works correctly.
Obviously, without recovery, I cannot flash anything, and without being able to write correctly, I cant get it to update. Acer Recovery says that it is successful, but it is not, and simply reboots the tablet.
One user described it as "GroundHog Day" as the tablet returns to the state it was in previously.
So yeah, I need help getting recovery back and working again, so I can either wipe this rom or do something entirely different. Thanks!
Edit: I should say, the stock Acer recovery seems like it wants to load, then it errors with:
Secure Boot: image SOS checksum fail
But none of the fixes work, nor does hitting volume up and the toggle to clear user data.

Borman18 said:
To keep it relatively short, for whatever reason, my recovery is corrupted or broken. I had flashed clockwork, did a full nandroid backup, and have my UID and all of that stuff. Today, sometime after I started downloading files from Google Music, my tablet restarted, and now programs and applications constantly crash, presumibly since the tablet seems to be locked in Read Only mode. Chmod seems to work, but then nothing actually changes. Ive been able to seemingly uninstall root, and reinstall it, but its a hassle, and I dont think that works correctly.
Obviously, without recovery, I cannot flash anything, and without being able to write correctly, I cant get it to update. Acer Recovery says that it is successful, but it is not, and simply reboots the tablet.
One user described it as "GroundHog Day" as the tablet returns to the state it was in previously.
So yeah, I need help getting recovery back and working again, so I can either wipe this rom or do something entirely different. Thanks!
Edit: I should say, the stock Acer recovery seems like it wants to load, then it errors with:
Secure Boot: image SOS checksum fail
But none of the fixes work, nor does hitting volume up and the toggle to clear user data.
Click to expand...
Click to collapse
Are you using Iconia Root to root and unroot? Let's start there?

Off to bed, I'm sure one of the other "late nighters" will be able to help you.
My only question is that you stated you installed CWM, if so, why didn't you create a full backup with it instead of nandroid?

Yes, I used Iconia Root to do the deed, which has worked since I got the unit a week ago until today.
And thats what I mean in terms of backing up, my apologies (im just use to calling it Nandroid for whatever reason).
I have no idea how the recovery got wiped though.

Borman18 said:
Edit: I should say, the stock Acer recovery seems like it wants to load, then it errors with:
Secure Boot: image SOS checksum fail
But none of the fixes work, nor does hitting volume up and the toggle to clear user data.
Click to expand...
Click to collapse
I STRONGLY recommend you read the following thread.
http://forum.xda-developers.com/showthread.php?t=1129873
Looks like you flashed something and didn't run "itsmagic".

Ive tried that, and no go. As far as I can remember, I havent flashed anything in days, since updating to the latest update a few days ago. And its been fine since then, until today. I started downloading google music stuff, went to the bathroom, came back and my tablet was off. I can give it another go though.
If it wasn't clear, I can definitely boot, its just with all those errors

But you get a checksum error, right? Have you gone through the steps in that thread that detail how to fix the checksum error?
If so, I suggest you contact sc2k.

Correct, if I hold the volume - and power, it gives that error. Just ran through the steps for the "<CASE 1> SOS checksum error" again to be safe, and its the same. I PM'ed him earlier (maybe twice..), but I can only assume he's sleeping, so I was just trying to see if anyone has any ideas.
Edit: from my ADB Shell session, just to show that it seems to want to work anyway? But of course, the same old..
# /data/local/itsmagic
Some magic trick by @sc2k on xda
it tricks the bootloader to run any kernel you want.
Thx @Acer for making this so easy.. why did you say the BL is locked if it isn't?
USE AT YOUR OWN RISK!
Done. Have fun!
# exit

Your best option is to wait until sc2k gets back to you, then. Don't worry. He's a fairly nice guy and has helped plenty of folks sort out similar issues on their tabs. Just remember to beer him afterwards!

Of course Thanks for your help regardless, I figured it was worth a shot. Of course, it does this right before I am to go camping for a few days (I had some maps and stuff on here to use as backup).

Borman18 said:
Of course Thanks for your help regardless, I figured it was worth a shot. Of course, it does this right before I am to go camping for a few days (I had some maps and stuff on here to use as backup).
Click to expand...
Click to collapse
AH, y'see, now you know what caused it in the first place! You tempted the fates! Never tempt the fates, for they are mean and sadistic beings that just LOVE to screw with folks right before they go camping.
I hope sc2k is able to help you out.

[Q] Cant get Droid 2 Gingerbread 4.5.601.A955 Update

Ok... I have also used Z4root. I got the update, it failed. I unrooted with Z4root. Re-downloaded the update, it failed. I tried to reinstall the kindle and blockbuster app. Re-downloaded the update, it failed. I reset to factory. Re-downloaded the update, it failed. Downloaded root checker, ran root checker, it said that I am not rooted. Re-downloaded the update, it failed.
This is the Detailed Results I got from the Advanced Root Checker:
Root Access is not properly configured or was not granted.
Superuser.apk - is NOT installed!
The application Superuser is recommended as it provides basic security and is available for free in the Android Market
System Environment PATH: /sbin /system/sbin /system/bin /system/xbin
The adb binary is set to default shell user access as a standard non-root user
Standard su binary location: ls -l /system/bin/su:
/system/bin/su: No such file or directory
Standard su binary location: ls -l /system/xbin/su:
/system/xbin/su: No such file or directory
Alternate su binary location: ls -l /sbin/su:
/sbin/su: Permission denied
Alternate su type binary location: ls -l /system/xbin/sudo:
/system/xbin/sudo: No such file or directory
SU binary not found or not operating properly
Results provided on your DROID2 device by Root Checker version 3.7 from joeykrim in the Android Market -
___________________________________________
Have I done something wrong??? I don`t understand why I can not get the update. Please help.

This process should un root and put you back on stock Froyo. This is a complete factory wipe, so if you're wanting to back anything up, do it before any of these following steps. Once complete, go to Settings > About Phone > Check for Updates and report back.
WARNING: Only run the first set of instructions, do not flash the Gingerbread leak, you can get the official after running RSDlite.
To get back to stock: http://www.mydroidworld.com/forums/...id-2-gingerbread-2-3-3-release-prerooted.html
1. Grab the SBF File
You must start the process with your phone running the official 2.3.20. If you have already upgraded to gingerbread grab this 2.3.20 sbf file .... Download
2. Grab RSDlite
You must use RSDLite to use the sbf file from step 1 .... RSDLite
3. Grab the Drivers Drivers ....Download now
4. Run RSDLite and sbf your phone back to 2.3.20

Didn't work
I was unable to get the OTA to work. I was rooted using OneClickRoot and unable to update like everyone else (FAILED). I tried to sideload from a post on another page, but that didn't work either (not even sure that was the correct file). So I followed the direction as mentioned above, SBFing to a stock 2.3.20, but only after I did a complete wipe of the phone. Now that I have SBFed I don't have any phone signal and cant get it to work with anything I have tried. I don't want to go crazy trying stuff and brick my phone. So at this point, how do I get my phone working again. Screw GB for now, I just need my phone to work. HELP!

It's pretty hard to brick a D2 unless you happen to flush it down the toilet. SBF again to 2.2, do NOT root. Go to the about phone menu and run the OTA update to GB. After that run the one click root for Droid 3.

working
I don't know why, but after re-installing (SBF) 2.3.20 the phone decided to stop working. I thought it could have been a bad SBF file, and it could have been. The step that seemed to work was wiping the phone after the install. Once I did this step, of course you have to set the phon up again, but it prompted me to "Activate" the phone. So I hit activate and the phone called Verzon and run a programming function. Once that completed the phone worked fine. I am currently downloading the OTA, so here's hoping!
I did actually get the sideload (update.zip) file to work before going back to 2.3.20 as mentioned above, but I still didn't have phone. At this point I was going to do a wipe but could not get the phone to enter recovery, I'm thinking there must be some other method that's different to get it there. If anyone know, that would be good info to have.
Still downloading.....

I believe if you dial *228 it will activate for you.

I am also unable to get the OTA GB update to work. It gets all the way to re-boot and about 1/3 of progress bar after accepting to install the 4.5.601.A955. Just like mentioned in one of these other posts. I have tried everything - uninstalling and reinstalling z4 root, deleting SU, Bootstrap recovery, root explorer etc. All of which were not done properly or in the right order. I have been working on this the last 2 days. Yesterday, I even called tech support at Verizon, they helped me do a factory reset, and when it failed again, offered to send me a new D2 because my phone is still under warranty and won't accept the update, so I took their offer.
But then I got nervous because my clockwork mod was still showing up on power up, so I finally figured out how to remove that. I have SBF'd at least a couple of times since I got clockwork removed and update still fails.
My memory is not to good, but I think I first rooted in late Dec 2010. It seems like the 2.3.2 OTA update came out in Jan or Feb 2011. I don't believe I had to unroot to get that update. My current System Version is 2.3.20 A955 - Android version 2.2, and that is what it goes to after doing the factory reset on the phone. The Verizon tech didn't act like it should have gone back to an earlier version.
I have only one other issue - a week ago the phone took a bath when I fell in the water. Dried it off quickly and the only thing wrong other than barely-noticeble water damage to the display, is that the power button now requires exactly 3 pushes every time to boot the display to the unlock screen.
Sorry for the long post. Here are my questions: I no longer have clockwork at power up, it boots like a normal out of the box D2, am I missing something? Will Verizon be able to tell that I had rooted my phone? Could the water and resulting power button issue be the cause of it not accepting the update? TIA

Im having a similar problem. I can get the ota update just fine, but it will install aboutt 1/3 of it and just stop and reboot. All i did was root. I unrooted and same thing happpens. Downloaded this thing like 6 times already and same thing each time. Although a long time ago i did uninstall nfs, blockbuster, and i think kindle but i cant remember...

Are you doing a full factory wipe back to 2.3.2 when you do this or are you just "wipe data/factory reset" in recovery? Because if you only do that in recovery you're just wiping data. There's another thread here with a .zip you can run in stock recovery, not clockwork. Rename to update.zip, put it on the main directory of SD, boot holding X and power, then press the volume buttons. Hit install update.zip.

On the D2 - I am doing Settings<Privacy<Factory Data Reset<Reset Phone< Confirm.
How do you get into stock recovery? Do I need to be rooted again?

I would imagine but I don't know. Boot up holding the X key and power, should bring you to a droid guy with a !. Hit the volume buttons, if you get a blue and red recovery menu, you're in. It's not going to ask you for superuser so it's worth a shot at least.

Thanks for your help idefiler6. I got into stock recovery, but when I did the update it also failed - some logwrapper error. I am now having difficulty getting back in to stock recovery.
I had deleted system/bin/hijack and renamed system/bin/logwrapper.zip to system/bin/logwrapper to remove or stop the clockwork mod from booting up, which did make clockwork go away using Root Explorer. I found a post here to do this droidxforums.com/forum/droid-x-help/22080-im-begging-help-please-help-3.html
Anyway, my new phone is supposed to get here Wed. So I guess I'll just take my chances of whether Verizon cares or figures out I had rooted my phone. Regardless, the power button failing to work properly, should qualify for warranty coverage.

Crossing my fingers for you.

im getting mine replaced under warranty due to it cannot install the update no matter, how many times we have wiped it with tech support.
I also was very lucky since I got my 2nd warranty phone right before the one year mark so it extened the phone i have now another 90 days.

Problems all around
I too am having the OTA update problem. Downloads fine and gets about 1/3 of the way before rebooting and giving me an update failed message.
Current Device info:
D2G
System Version: 2.4.330.A956
Android Version: 2.2
Unrooted using Z4Root
Current logwrapper from November 12, 2010. No hijack or recovery .bin files in place.
I have tried RSDlite 4.8 and 4.9 using two separate downloads of the 2.3.20.A955 SBF from the link provided in this thread. Motorola Drivers are up to date and no errors are showing up in my Device Manager on my W7 PC.
The error I get when flashing in RSD is;
critical error febe 0047
Any thoughts? I'd like to try Gingerbread but haven't had any luck no matter what I try.

When in Doubt Go Linux!
Here's how I fixed the problem. I'm not a big Windows guy and the issues I was having were frustrating me because I had to update drivers, download new versions, blah, blah, blah.
I found a solution that allowed me to use my Fedora OS and it took me 10 minutes, no hassles, no errors. The incredible thing is, it kept ALL of my data, apps and settings on the phone! I had to upgrade from 2.29 (the flash from below) to 2.30 OTA and then to Gingerbread OTA Awesome stuff.
Here are the steps provided by hwertz from modmymobile.
"Download sbf_flash (just goggle it)
Download DROID2WE_X6_2.4.29_FULL.sbf.zip" (google this too)
(You would download these with firefox, make sure Firefox saves in the directory "Download".)
Open a terminal (Applications->Terminal)
Plug in your phone via USB, turn it off. Flip open the keyboard and turn it on WHILE holding down the up arrow. You'll see this screen with blocky white text, like right away -- it doesn't even get to the Motorola logo."
-----
OK, so in the terminal, you will
type "cd Download"
(If you saved somewhere else, cd to there. For instance if you saved to "Desktop" you would "cd Desktop" instead.)
Type "gunzip sbf_flash.gz"
If this gives an error, it's ok, it means you already had "sbf_flash" instead of "sbf_flash.gz"
type in "chmod +x sbf_flash"
Type in "unzip DROID2WE_X6_2.4.29_FULL.sbf.zip"
Then type in "sudo ./sbf_flash DROID2WE_X6_2.4.29_FULL.sbf"
If you are running a "real" copy of Ubuntu this'll ask for your password. The LiveCD has no password so it won't.
That's it! It'll appear to do nothing for a few seconds while it loads the flash, then it'll start flashing your phone which takes 5 or 10 minutes.
Good luck!
Thank you hwertz and thank you Linux!

cbotd said:
I too am having the OTA update problem. Downloads fine and gets about 1/3 of the way before rebooting and giving me an update failed message.
Current Device info:
D2G
System Version: 2.4.330.A956
Android Version: 2.2
Unrooted using Z4Root
Current logwrapper from November 12, 2010. No hijack or recovery .bin files in place.
I have tried RSDlite 4.8 and 4.9 using two separate downloads of the 2.3.20.A955 SBF from the link provided in this thread. Motorola Drivers are up to date and no errors are showing up in my Device Manager on my W7 PC.
The error I get when flashing in RSD is;
critical error febe 0047
Any thoughts? I'd like to try Gingerbread but haven't had any luck no matter what I try.
Click to expand...
Click to collapse
I don't particularly know how much of a difference this is, but the D2G and the D2 are two different phones, everything I have posted is for the OG D2. Might want to check the threads in the D2G forum because the files you need to SBF must differ in some way. I could be wrong...

that would explain it
idefiler6 said:
I don't particularly know how much of a difference this is, but the D2G and the D2 are two different phones, everything I have posted is for the OG D2. Might want to check the threads in the D2G forum because the files you need to SBF must differ in some way. I could be wrong...
Click to expand...
Click to collapse
That makes sense. Either way, I'm happy as can be and in love with my phone all over again. GB is fast and smooth on my D2G and after gaining root access again last night all my SU apps are back in working order.

Droid 2 updated
I had to revert back to stock 2.3.20 using the RSDLite flashing method, I let it do its thing, then performed a factory reset.
Powered the phone on, activated it, then just downloaded the OTA update over wi-fi to make it faster, installed like a charm, then ran the rooting utility.
Phone is rooted, deBloated, and rockin steady already.
Gotta say, I love my D2 again.

A955 & A957 Gingerbread sbf
On September 15th an official Gingerbread sbf was released from Motorola for the Droid 2 (not the Global). Here are the exact file names in case anyone has access:
A955:
1FF-p2a_droid2_r2d2_cdma_droid2_r2d2-user-2.3.3-4.5.1_57_DR2-32-110726-release-keyssigned-Verizon-US.sbf.gz
A957 (R2D2):
1FF-p2a_droid2_cdma_droid2-user-2.3.3-4.5.1_57_DR2-31-110719-release-keyssigned-Verizon-US.sbf.gz

[Q] N73G stuck on Google screen

I was using my N73G at home this evening and it spontaneously rebooted to the Google splash screen... and stayed there for well over 5 minutes. I tried long pressing power to reboot again, and it went back to the same screen.
TWRP is installed, and I am able to get into that. I tried wiping cache and dalvik, and it booted straight back to the splash screen again, solid for 3 minutes before I went back into TWRP. In the file manager my files all appear to be safe and sound. I am currently running a nandroid backup before I futz with it any further. TWRP has not given me any errors over the course of the backup.
I should note that I have had some trouble connecting to TWRP over ADB although I can use ADB when booted into the OS. So if I need to go fishing for files over USB, I hope I won't come up empty. If necessary I could try flashing CWM recovery instead, as I may be able to get my files more easily that way.
Anyway, ideas are welcome. I was running a bake of the Modaco custom ROM, and the zip for that ROM is still on the device, so I was thinking I might try reflashing that. But first I should try and get my nandroid off the slab.
As fortune would have it, I have already ordered an RMA device swap due to issues with the speaker blowing out. So if I fail to resuscitate it, help is already on the way. But I would like my tab to work again by the time I go back to work Monday

Update: Figured out the ADB recovery driver problem. Nandroid backup was successful. I'm now pulling the backup image to my desktop. Will try a ROM reflash next.

UPDATE UPDATE: The weirdest thing. I noticed while it was plugged into my machine, still stuck on the Google boot logo, that I was able to see the tab in ADB devices. So I typed in adb logcat and found some message about /system/xbin/busybox missing.
I browsed with ADB shell and found there is a busybox in /system/bin. So I did ADB remount, and then copied busybox from bin to xbin. Entered a reboot command, and bam! Five seconds on the Google splash, and then right to the booting X.
Why in the world would this have happened... maybe the busybox installer app got an upgrade and botched an attempt to upgrade busybox?

cmstlist said:
UPDATE UPDATE: The weirdest thing. I noticed while it was plugged into my machine, still stuck on the Google boot logo, that I was able to see the tab in ADB devices.
Click to expand...
Click to collapse
The adb daemon - adbd - is started by init as a service so long as you have previously enabled adb debugging. So, it happens before the whole android reboot sequence kicks off (checking that all .apks without odex files have up-to-date .dex entries in dalvik cache, permission checks, etc.) You can access it on devices that are "stuck" in the late stage of booting.
TWRP - for better or worse - does not claim the same USB vid/pid ID that is used by the N7's ADB facility, even though the exact same driver can be used for either adb mode ... so long as you manually went into the driver install package and add the "universal" vid/pid values used by TWRP to the driver's .inf file. I think this is done simply to minimize the effort keeping up with new device identifiers by the TWRP team. It does create the impression that separate drivers are needed - but only because neither of the two drivers (Google vs. Universal) have the "other's" vid/pid pair listed as matching devices in their .inf files.
Anyhow, you got it all sorted out - congrats.

Thanks! I had been worried maybe the whole file system was corrupted, so in comparison this was a relief.
Sent from my Galaxy Nexus using Tapatalk 2