Database Develop

My G1 is stuffed, but not bricked. Mount from Recovery? Wave invites for help.

Ok. So yesterday night I was trying to give my G1 a new ROM. I wasn't really concentrating. I was tired. I've done it successfully before. I was following the instructions on Cyanogen Wiki for phones already with custom SPL and OTA.
Something screwed up, I did the firstROM a while ago so it probably wasn't the right one. Maybe it needed deathspl.
Regardless, it is now stuck on the T-Mobile G1 screen (and its stuck, I've left it for an entire night: still stuck) . I can take out the battery and boot into recovery mode. So at this point I basically need to mount my SD through USB (i dont have adapter) so I can start from scratch with SPLs, Radios and Images. This is the problem.
I've read you can do it by pressing Alt+X, going into console/terminal and type some commands in. I press Alt+X but nothing happens. I'll tell you what happens when I do other things:
---------
Alt+S= E:Can't mount /dev/block/mmcblk0p1 (or /dev/block/mmcblk0) (Invalid argument)
Can't mount sdcard
Alt+A= <<same thing except for last line:>> E:Can't mount SDCARD:
Move apps+dalvik-cache to SD: Error: run apps2sd via adb
Apply sdcard:update.zip: Can't mount sdcard
Apply sdcard:choose zip: E: CAn't mount SDCARD:
Wipe data/factory reset: Data wipe complete.
Nandroid v2.2 backup: Can't mount sdcard
Nandroid v2.2 restore: Can't mount sdcard, aborting.
Format SD : fat32+ext2+swap: Format complete!
Format SD : fat32: Format complete
Repair ext filesystem: Error : run e2fsck via adb!
Convert ext2 to ext3: Error : run upgrade_fs via adb!
Fix package uid mismatches: Error : run fix_permissions via adb!
-----------
Alrighty. So its royally stuffed up.
Please help! I'm telling myself its not bricked, because it has small but definite programs and calculations running.
It mentions adb, and I have used it in the past to skip through a tutorial (back when you couldn't skip through it) because it needed internet connection and at the time I didnt have data transfer on my SIM, but I did have Wireless. How exactly I did this escapes. Do I need to download anything?
I have no idea if this helps, but I was trying to think of a sort of prize for anybody to help and I have Google Wave invites. Whether thats a big deal or not, I have no idea.
Please help!

Well you can assure yourself that you are not bricked.
First check your SPL and Radio.
If they are:
SPL=1.33.2005
Radio=2.26.19.26I
then your good in that area.
you just need to wipe everything and retry the ROM.
If not then you might want to get the latest stuff and try again that way.

Thanks
Thanks.
But how do I check?
I can't get into the proper Android OS, the three states my phone can be in are:
Off
Stuck on T-Mobile Screen
Recovery Mode
Also, how can I get some new stuff on my SD card if I the only things I have are: the phone described above (i.e. the only workable state being recovery mode), an SD card and a USB cable.
Whats your email so I can send you an invite if you want it?

lachy95 said:
Thanks.
But how do I check?
I can't get into the proper Android OS, the three states my phone can be in are:
Off
Stuck on T-Mobile Screen
Recovery Mode
Also, how can I get some new stuff on my SD card if I the only things I have are: the phone described above (i.e. the only workable state being recovery mode), an SD card and a USB cable.
Whats your email so I can send you an invite if you want it?
Click to expand...
Click to collapse
To see you SPL and Radio do this:
Turn off phone
Hold Home and End Call buttons.
If you see:
Hboot-1.33.2005 or something like that then that means that you have the latest SPL
Radio-2.22.19.26I then you have the latest Radio too.
First we need to check to see what your SPL and radio is before you try to do anything that involves flashing ROMs
What recovery image do you have?

Can't see it
When I press Home + End Call I can see is:
Android System Recovery:
<the options I described before, with their errors>
The above is in green font, the background is black with an HTC logo, at the very bottom is white font that says this:
Build: RAv1.2.1G
Sorry for not replying as fast as could. I mega-ly appreciate this so I'll try to be more vigilant.
I'll look around for other key combos to get some more info.

lachy95 said:
When I press Home + End Call I can see is:
Android System Recovery:
<the options I described before, with their errors>
The above is in green font, the background is black with an HTC logo, at the very bottom is white font that says this:
Build: RAv1.2.1G
Sorry for not replying as fast as could. I mega-ly appreciate this so I'll try to be more vigilant.
I'll look around for other key combos to get some more info.
Click to expand...
Click to collapse
And I just did that! I pressed back + home and got a white background with three skateboarding androids with this text:
DREAM PVT 32B ENG S-OFF
HBOOT-1.33.2005 (DREA*****)
CPLD-4
RADIO-2.22.19.26I
Apr 20 2009, 15:30:43
CLEARSTORAGE
Delete all user data?
<ACTION> Yes
<POWER> No
--------
Well thats atleast one step we've bypassed. Stay with me here.
Alrighty so I know the Radio and SPL, and apparently they are up to date.
What next?

From your above post, it seems your SDcard is not being read by your phone. Not sure what the issue is there.
But, if you can get it recognized by the phone, try the following:
It seems you have ADB set up, you may be in luck.
Connect the USB cable in recovery and type these commands on cmd prompt in Windows:
adb shell
ums_enable
This should mount your phone to your PC.
You can now move in necessary files to save your phone.
I suggest doing a FULL WIPE, then reflashing a ROM such as CM 4.2.14.1 (latest build).
If that doesn't work, you may have to start over by flashing DREAIMG.nbh (RC29), flashing latest radio, flashing SPL, DON'T REBOOT, then flashing rom RIGHT AFTER SPL.
Good luck, keep us updated.

Nearly There
Ok. So I got adb up and running.
I ran adb devices and it was blank so I followed part 2 of:
<do google search for "the unlockr hot to set up adb usb drivers for android devices>
After reinstalling drivers via USBDeview:
My Device Manager is now registering my phone as the Android Composite ADB Interface, but when I run adb devices it still has a blank list.
Keep in mind I am in recovery mode.
When I try and run adb shell, it errors with 'no device found' so I need to do this devices command successfully.
Does anybody know whats happening?

lachy95 said:
Ok. So I got adb up and running.
I ran adb devices and it was blank so I followed part 2 of:
<do google search for "the unlockr hot to set up adb usb drivers for android devices>
After reinstalling drivers via USBDeview:
My Device Manager is now registering my phone as the Android Composite ADB Interface, but when I run adb devices it still has a blank list.
Keep in mind I am in recovery mode.
When I try and run adb shell, it errors with 'no device found' so I need to do this devices command successfully.
Does anybody know whats happening?
Click to expand...
Click to collapse
Try running it while the Phone is on instead of recovery.

Say run terminal and post the output of:
cat /proc/cmdline
By the way you can still flash images using fastboot mode.

Its stuck
When you say 'on' do you mean on the T-Mobile Screen?

Thanks
Thanks again guys this is really good and I think we're getting close. OK. Here's an update as of right now:
My computer recognizes my phone in T-Mobile Logo, Fastboot (or thing with three skating Androids, Home and Back), and Recovery.
When I cd to my tools folder I can run adb commands but when I run 'adb devices' it shows:
List of devices attached
....
No serial number or anything. I've reinstalled the drivers.
When I do the command 'run terminal' it says 'run' is not recognized as an internal or external command blah blah
This is the same with 'cat /proc/cmdline'
I still can't run terminal with Alt+X in recovery mode (at least, nothing happens)
My phone cannot turn 'on'. It is stuck on the T-Mobile Screen.
What should I do?

lachy95 said:
When you say 'on' do you mean on the T-Mobile Screen?
Click to expand...
Click to collapse
Normal boot.

That doesn't work.
How can I see it in adb devices?
Argh!
Any ideas just throw them out there.

Have you tried another sdcard? That's the first thing I would try if the phone is complaining about not being able to read it.

Check ur drivers.
sounds like u need to update them.
Try the attachment

Technochris1 said:
Check ur drivers.
sounds like u need to update them.
Try the attachment
Click to expand...
Click to collapse
It works!
Sweet Technochris1, Sweet, sweet person. Thou hath skills and prowess!
I uninstalled the drivers then installed yours. Now adb devices is functioning and sees my device! Now to mount, transfer and fix! I'm indebted to you greatly, for you fixed my phone and everybody else on this thread! Thank you so much.

Please Help- FRF91 unable to root with Superboot! Bricked?

I'm having serious issues with my N1 since receiving it back from HTC for a repair. I had rooted the phone before it was repaired for a crack in the glass, but the repair center had re-locked the bootloader. I followed steps the way I had done before to root my phone and succeeded in re-unlocking bootloader but when I did superboot (using mac terminal) did not come to screen where root permissions were offered... booted phone, no wifi signal, did not recognize sd, very glitchy, unstable and maybe worst of all unable to mount to computer. So I don't know if anyone with this small amount of information would have any clue as to what I can do. Oh yes and when I had gotten my phone back from repair center I had done update to FRF91.. so I know I'm an idiot for trying to use superboot when there isn't one for the FRF91. There you go gentlemen. If someone is willing to help I can provide any other information required.

As long as you can get to your recovery screen, you're not bricked. Most important, are you running a custom recovery like Amon_RA's?
Edit: If you have a stock recovery and want the superuser/unsecured boot use the updates from here
-If you have a custom recover just flash a ROM that includes superuser/unsecured boot
*Always do a Nandroid

I didn't have it before I unlocked my bootloader, and I can't seem to install it considering that every post says you put it on the sd.. and as I said I cant even mount my phone So apparently I'm on stock..

Micro SD adapter?
That does make things interesting, the only thing i can think of is getting a Micro-sd adapter and putting the update on the sd, then place the sd back in your phone and flash.

Thread moved to Q&A.

Can't you adb push the file while in the recovery menu?

I can't flash if I can't mount my sd card right? So that would make the ROM with superuser useless.. Can you think of a way I can get Amon_Ra recovery through bootloader?

I can't flash if I can't mount my sd card right? So that would make the ROM with superuser useless.. Can you think of a way I can get Amon_Ra recovery through bootloader?

I've heard about this but I'm a total n00b, don't know how to..

I was referring to the adb push.. any help with this would be GREATLY appreciated!

ADB method
If you still have the adb ability try fastboot flashing...just follow the steps here

Emul8tor I really appreciate the continuing advice- home from work now.. I can't seem to get adb if i have done everything correctly working on terminal mac os.. have android sdk and i should be running it under sdk/tools dir correct? i type in adb or adb devices and I get adb: command not found..suggestions?

Have you used the adb method before, kinda sounds like you haven't set the PATH for your environment. I don't have any clue about the set-up for Mac, but theres a tutorial here

okay going to read through this again especially part on creating the PATH.. back soon

really don't know what to think I have no idea how to create a .bash profile and I'm not so sure this is why adb isn't working. Thoughts?

and I didn't use the adb method before.. only fastboot

found this by googling, adding tools to your path lets you run Android Debug Bridge (adb) and the other command line tools without needing to supply the full path to the tools directory when typing commands in Terminal

Dude this guy's having the same problem as me, I guarantee you he used the wrong version superboot with FRF91 http://androidforums.com/all-things-root-nexus/127689-please-help.html
I'll bet he can't mount sd card either

Alright I ran adb command but it isn't registering the phone after list of devices attatched. But it did issue a string of commands after so I assume it is working... Now i guess I can say that I am truly scared because my adb doesn't even recognize the device.

Just a hunch...is debugging enabled on your device?

[Q] Dell Streak 7 Restore problem **Help**

Hi all.
I am hoping someone out there can help me.
I recently bought a used Dell Streak S7.
I tried to restore the DS& back to a factory out of the box state and no luck.
Tried the follwoing three
menu ->setting-> Privacy->Factory Data reset
pin hole by sd card\
Volume + and power -> 1. and 3.
I have added info for Wi-fi and everytime DS7 is turned off and turned on the wi-fi settings are lost.
I was able to root it with One Click Superoot but when i turn DS7 off and turn it off the SU dissapears.
I read http://forum.xda-developers.com/showthread.php?t=1011654 and i can't access CWM thorugh Goggle market.
The original owner account info still remains regardless of reboot and etc.....
I don't have a SD card for it and i am not sure what impact that has.
Android Version 2.2
Baseband Version 11.809.05.03.00
OEM version GLUNB1A132233
Build Number 14291
ANy information or any ideas would greatly help.
Thanks,
Dennis

Dennis,
Did you every resolve your issues?
I am having nearly the same issues as you were.
I bought a used Dell Streak that had been updated to Froyo. When I try to reset the device to factory settings to remove the original owners email address it acts like it works but each time the device boots back up all the original owners info is still there. Their wallpaper, email accounts, facebook accounts, twitter acounts, etc.
I have tried to use the Settings>Privacy>Factory Data Rest, it seems to work but doesn't clear the system all data remains.
I have tried turning off the unit and holding the volume up and power and using the restore option from there but each time it boots back with all the original owners info.
I can not get it to do a factory reset thus I can not associate my gmail account with the device.
Does anyone have a solution?
Thanks,
Frankie4life

No luck yet.
Still waiting and hoping.

Have you guys tried restoring with NVFlash? this procedure works great and helped me a bunch. http://forum.xda-developers.com/showthread.php?t=1018809&highlight=nvflash
If you are successful but your streak still wont get past the dell logo on boot, boot back into recovery (Vol+ and Power) and do a factory restore.
warning, this will erase EVERYTHING on your streak

Same thing here
I am having the same exact issue. I have tried restoring using nvflash... No luck
I have tried using the Fastboot method... No Luck
I even found an Update.pkg to try and update it using the built in recovery... No luck, It ends with an error of "Modem Error" says it completed successfully and then reboots to its previos state.
I have tried flashing the clockwork recovery via Fastboot and also.... No Luck
I am not a Noob and I have the the proper ADB and fastboot drivers installed, I am very familiar with using the android sdk and adb command from the SDK folder location.
I beleive at this point either due to an error or something the previous owner did the Streak is now "write protected" is this possible?
My biggest problem is when I root the devices using super one click it gives me root access and when launching the ADB SHELL i receive the "#" indicating that the shell has root, If I try and run ADB remount i receive and error
"c:\androidsdk\tools>adb remount
remount failed: Operation not permitted
c:\androidsdk\tools>"
this indicates to me that I cannot mount any memory from the device as read/write.
Any info would be helpful
Tom

wikedbubble said:
I am having the same exact issue. I have tried restoring using nvflash... No luck
I have tried using the Fastboot method... No Luck
I even found an Update.pkg to try and update it using the built in recovery... No luck, It ends with an error of "Modem Error" says it completed successfully and then reboots to its previos state.
I have tried flashing the clockwork recovery via Fastboot and also.... No Luck
I am not a Noob and I have the the proper ADB and fastboot drivers installed, I am very familiar with using the android sdk and adb command from the SDK folder location.
I beleive at this point either due to an error or something the previous owner did the Streak is now "write protected" is this possible?
My biggest problem is when I root the devices using super one click it gives me root access and when launching the ADB SHELL i receive the "#" indicating that the shell has root, If I try and run ADB remount i receive and error
"c:\androidsdk\tools>adb remount
remount failed: Operation not permitted
c:\androidsdk\tools>"
this indicates to me that I cannot mount any memory from the device as read/write.
Any info would be helpful
Tom
Click to expand...
Click to collapse
hi, i'm going through something similar, where did you find the update.pkg? i've been looking for it everywhere, thank you

the answer i would suggest is use nvflash like navycow suggested you have 2 choices with that you can install unrooted 2.2.2 or honeycomb, search the thread for it and if you can't find it let me know i will post a link.

It seems that alot of people are having this problem I found the link for the OTA update here.
http://www.streaksmart.com/updates/page/2/
From there you can download the update.pkg manually or OTA
Make sure you don't use the O2 update because that is for the Streak released in EU. It took a little browsing but I found it in there somewhere

[Q] M7 missing /dev/block/mmcblk0p22 and higher

Sorry for the novel, but I want to show the whole backstory to rule out quick fixes... I have an m7 a coworker asked me to take a look at. I don't know the full story, but apparantly he didn't do anything to the phone, he just woke up one day and it was suddenly broken. I'm not sure whether I believe him but I digress...
When I got it, about half the time the phone would just hang at the htc logo. If you power it off and back on, the other half of the time it would automatically bring itself to the bootloader. The bootloader said Tampered, locked, and security warning at the top.
I fought with it for a while, factory reset did nothing. I used htcdev to unlock the bootloader, and flashed twrp 2.8. Twrp was full of errors saying can't mount /data, can't mount /system, can't mount /cache etc. any time I tried to do anything it would keep complaining that it couldn't write to /cache/log/whatever.
Trying to format / wipe any of the partitions would fail. When I went to the mount screen, it showed "internal storage: 0mb" and clicking on that let me choose from internal storage 0mb and dgs USB 0mb.
Trying to adb side load in twrp failed as well, it would just say side load failed as soon as I entered the side load screen.
I installed twrp 2.3.6, and it did the exact same thing.
I then installed CWM touch 6.0.4.8, and it had basically the same errors about not being able to mount any partitions. The only difference with CWM was that the ADB side load would start, but trying to actually send any files to it fails. (Sending the file from the computer counts up and gets to 100%, but as soon as it gets to 100% it says the file is invalid (don't recall the exact error)
I finally found this link: (too new to port links, but google htc recover corrupted partitions, it's the first hit, from android revolution blog) and followed those steps, but when I run mkfs.ext4 for mmcblk0p36, 35 or 34 it complains that mmcblk0p36 is not a block special device.
I opened up adb shell, and ran ls /dev/block, it shows some mmcblk0, mmcblk0p1, mmcblk0p2, etc all the way up to p21, but there's nothing higher than 21. When I run that same command on my own m7 (running cm11) it has all the way up to p37.
I've tried to find more info about what's going on from there, but the only people I've found with similar problems all sent their phones back for warranty, and this one is out of warranty now.
So long story short, at this point am I right that it looks like a hardware fault and I'm sol? Or is there anything I'm missing about why half of those blocks would be missing? Do I stand a chance of remapping /data /system and /cache to lower numbered blocks or am I out to lunch?
This post was long enough without attaching logs or exact error messages, but if anyone thinks they might be of value let me know and I can include them.
Thanks!

joetomato said:
Sorry for the novel, but I want to show the whole backstory to rule out quick fixes... I have an m7 a coworker asked me to take a look at. I don't know the full story, but apparantly he didn't do anything to the phone, he just woke up one day and it was suddenly broken. I'm not sure whether I believe him but I digress...
When I got it, about half the time the phone would just hang at the htc logo. If you power it off and back on, the other half of the time it would automatically bring itself to the bootloader. The bootloader said Tampered, locked, and security warning at the top.
I fought with it for a while, factory reset did nothing. I used htcdev to unlock the bootloader, and flashed twrp 2.8. Twrp was full of errors saying can't mount /data, can't mount /system, can't mount /cache etc. any time I tried to do anything it would keep complaining that it couldn't write to /cache/log/whatever.
Trying to format / wipe any of the partitions would fail. When I went to the mount screen, it showed "internal storage: 0mb" and clicking on that let me choose from internal storage 0mb and dgs USB 0mb.
Trying to adb side load in twrp failed as well, it would just say side load failed as soon as I entered the side load screen.
I installed twrp 2.3.6, and it did the exact same thing.
I then installed CWM touch 6.0.4.8, and it had basically the same errors about not being able to mount any partitions. The only difference with CWM was that the ADB side load would start, but trying to actually send any files to it fails. (Sending the file from the computer counts up and gets to 100%, but as soon as it gets to 100% it says the file is invalid (don't recall the exact error)
I finally found this link: (too new to port links, but google htc recover corrupted partitions, it's the first hit, from android revolution blog) and followed those steps, but when I run mkfs.ext4 for mmcblk0p36, 35 or 34 it complains that mmcblk0p36 is not a block special device.
I opened up adb shell, and ran ls /dev/block, it shows some mmcblk0, mmcblk0p1, mmcblk0p2, etc all the way up to p21, but there's nothing higher than 21. When I run that same command on my own m7 (running cm11) it has all the way up to p37.
I've tried to find more info about what's going on from there, but the only people I've found with similar problems all sent their phones back for warranty, and this one is out of warranty now.
So long story short, at this point am I right that it looks like a hardware fault and I'm sol? Or is there anything I'm missing about why half of those blocks would be missing? Do I stand a chance of remapping /data /system and /cache to lower numbered blocks or am I out to lunch?
This post was long enough without attaching logs or exact error messages, but if anyone thinks they might be of value let me know and I can include them.
Thanks!
Click to expand...
Click to collapse
I don't know if the Unbrick Project would help or not. At least take a look at it to see if your situation might fit the criteria.

Low Storage Warning, Now Bootloop

My wife was using her moto x4 to take pictures yesterday and apparently used up almost all her storage space. she got a message saying such and that some apps won't work properly until storage is freed up. She was able to take a couple more pictures but when she tried to text them to someone she couldn't open up hangouts. She rebooted her phone and now its stuck in a bootloop. Won't go past the Android One logo, and restarts after a few seconds. I've been able to get to recovery mode where I thought there used to be a delete cache option, but the only thing I saw was data/factory reset and I wanted that to be the last option since my wife doesn't want to lose her pictures of our kids. They weren't backed up to photos yet because we weren't on wifi. I have used ABD in the past and found a command to delete cache "fastboot erase cache" but that didn't help. I did also tried Mount /system and after doing that the first try it blipped a Motorola logo after the Android One but then went immediately back to bootloop and not getting past Android One.
Is it possible to pull the pictures off her device without being able to boot?
Any ideas to make it boot without doing a factory reset? I assume this is a storage issue but maybe just big coincidence?
I have the Motorola USB utility on my computer, and the device is stock Android 8.1, stock recovery and not rooted or anything.
Thanks,
Richard

boot back into recovery and adb pull the pictures.
so, you boot into recovery..then do adb shell.
then cd /sdcard/DCIM
do ls
you should see another folder or the pictures and videos.
then do exit to come out of adb shell and follow this to pull the folder
https://stackoverflow.com/questions...pull-all-files-of-a-folder-present-in-sd-card

munchy_cool said:
boot back into recovery and adb pull the pictures.
so, you boot into recovery..then do adb shell.
then cd /sdcard/DCIM
do ls
you should see another folder or the pictures and videos.
then do exit to come out of adb shell and follow this to pull the folder
Thanks for the quick reply. I get an error: no devices/emulators found. I don't think my wife has USB debugging enabled. Any other options?
Thanks,
Richard
Click to expand...
Click to collapse

when did you get the error?

Sorry, it occurs at the first step, the adb shell command.
Granted, my experience with using adb is limited but my understanding was that you can't use it unless USB debugging is enabled. Playing around a bit more, my computer doesn't seem to recognize the usb connection unless I chose apply update from ADB but I think that only allows sideloading. The adb shell didn't work and adb devices empty there as well.
Thanks,
Richard

rjschwar said:
My wife was using her moto x4 to take pictures yesterday and apparently used up almost all her storage space. she got a message saying such and that some apps won't work properly until storage is freed up. She was able to take a couple more pictures but when she tried to text them to someone she couldn't open up hangouts. She rebooted her phone and now its stuck in a bootloop. Won't go past the Android One logo, and restarts after a few seconds. I've been able to get to recovery mode where I thought there used to be a delete cache option, but the only thing I saw was data/factory reset and I wanted that to be the last option since my wife doesn't want to lose her pictures of our kids. They weren't backed up to photos yet because we weren't on wifi. I have used ABD in the past and found a command to delete cache "fastboot erase cache" but that didn't help. I did also tried Mount /system and after doing that the first try it blipped a Motorola logo after the Android One but then went immediately back to bootloop and not getting past Android One.
Is it possible to pull the pictures off her device without being able to boot?
Any ideas to make it boot without doing a factory reset? I assume this is a storage issue but maybe just big coincidence?
I have the Motorola USB utility on my computer, and the device is stock Android 8.1, stock recovery and not rooted or anything.
Thanks,
Richard
Click to expand...
Click to collapse
I feel horrible for you. The one pro of iOS is that bootloops are less often but can happen (happened on iPad 6 but reinstalled iOS without data loss). I will always root my phone and install TWRP out of these horror stories. Do you still have the issue?