Related
trmacdonal said:
How to Restore your phone on a Windows PC using a Nandroid backup
I am going to assume you already have a Nandroid backup created on your SD card using JF 1.31's recovery Alt-B feature. The backup will create a folder called nandroid on your SD.
What you need:
The Android SDK:
Fastboot Windows Binary in this post:http://forum.xda-developers.com/showpost.php?p=3083753&postcount=1
From your Nandroid backup you need three files:
data.img
system.img
boot.img
Steps to restore your phone
1) Put the files Adb and AdbWinApi.dll from the tools folder in the Android SDK into C:\WINDOWS\System32 folder on your PC. Substitute the correct drive letter if windows is not installed on you C: drive
2) Put the Windows Fastboot.exe into the C:\WINDOWS\System32 folder on your PC
3) Create a folder on the C: drive of your PC called android. The path should be C:\Android.
4) Copy the Nandroid backup files data.img, system.img, and boot.img from your SD card to the folder called Android you created by mounting your SD card as removable disk.
5) Unplug the USB cord and power off your phone
6) Power up your phone by holding CAMERA+POWER, you should see three androids on skateboards. If you don't see this go install the Engineering boot loader
7) Plug the USB cord back into your phone and press back. The screen on your phone should say fastboot.
8) Make sure your pc is using the correct driver. Open the device manager on your pc. It is helpfull to have all other USB storage devices besides your phone unplugged for this part. Look for a USB Mass Storage device in the list of the USB devices. Right click on it and update the driver. Pick the option to browse for a driver on your pc. The driver is located in the Android SDK your downloaded in the folder called usb_driver. If this is done right you will now see a device called HTC Dream
9) Press start, go to run and type cmd (If you are on Vista just type cmd in the search box and hit enter). The command prompt will pop up.
10) Type cd C:\android
then enter the following commands:
fastboot flash system system.img
it will say Sending, then writing and say OKAY if it was successful
then type
fastboot flash userdata data.img
wait for the second OKAY and type
fastboot flash boot boot.img
wait for the second OKAY and type
fastboot reboot
Your phone should now be restored exactly as you had it when it was backed up.
Click to expand...
Click to collapse
I'm young yet in my android/linux learnings and this guide here is great. I've been soaking in information for weeks now on the boards but still, my kungfu is weak.
Hence I'm having an issue today and I've been working on it almost all day so far. Something happened and I ended up having to factory restore my phone and I'm attempting to recover from my nandroid backup files.
I've followed the above instructions to the letter, but now that I'm ready to do the actual fastboot flash system system.img command, I keep getting a "FAILED <command write failed <Too many links>> error". And I've searched high & low looking for a solution to this.
My HTC is correctly running in Fastboot as an ADB Interface in WinXP Pro SP3, I've got my nandroid backup files placed in the C:\Android folder on my pc as directed. Fastboot is in the /system32 folder (and in cmd Fastboot devices lists my phone), but I keep banging my head into this error over & over. Its driving me pretty insane and any help would be appreciated. I know you guys aren't a support desk and I'm probably screwing up something elementary, but I just wanted to say that I'm finally asking as a last resort. I've been trying to figure this out myself for about 9 hours now. My thanks in advance.
Xeroproject said:
I've followed the above instructions to the letter, but now that I'm ready to do the actual fastboot flash system system.img command, I keep getting a "FAILED <command write failed <Too many links>> error". And I've searched high & low looking for a solution to this.
Click to expand...
Click to collapse
If it transfers the image to the phone but aborts halfway or at the end, try adding a ferrite core to your usb cable at the host side, or use one with an integrated ferrite core.
Unfortunately we don't have the source to the SPL so I'm mostly clueless what the "too many links" error means. Alternatively, try on a different pc.
infernix said:
If it transfers the image to the phone but aborts halfway or at the end, try adding a ferrite core to your usb cable at the host side, or use one with an integrated ferrite core.
Unfortunately we don't have the source to the SPL so I'm mostly clueless what the "too many links" error means. Alternatively, try on a different pc.
Click to expand...
Click to collapse
Thanks for the suggestion, I'll have to see if I can find a suitable USB cable, although from some inquires to linux buddies more in the know, I was told it was indicating a "a circular reference symlink" either in fastboot or in the command I used.
Considering I used exactly the commands in the guide, I'm puzzled. Also, I pulled the fastboot.exe for win32 from JF's own attachment.
Regarding another PC, yes, that would be ideal for troubleshooting this, however the pc I have at home is Vista 64bit (unfortunately), so shouldn't I run into issues there?
Xeroproject said:
Hrm, sorry about the few posts in here mods, it seems my issue isn't related to a mistype in the command line of trmacdonal's guide like I thought it was, so its most likely not related to this thread & needs to be split into a separate thread to prevent clutter.
I have noticed something regarding my situation: in command line when I type "fastboot devices" it recognizes & lists my phone. However when I type "adb devices" it does not list my phone. Might this be related?
Click to expand...
Click to collapse
ADB won't see your device till it has booted into android.
And send me a PM with the post numbers and a new thread title and I will move your posts and any posts related to them.
So unfortunately getting any work done on this on my Vista machine has been a total no-go. Vista won't take the 64-bit homebrewed driver, regardless of disabling driver authentication.
So I'm stuck. Day 2 here and I still get the "too many links" error. I've since retraced all my steps, redownloaded the SDK, JF's fastboot-win32, and completely removed all drivers from the system (including registry entiries) then reinstalled everything, and tried a shielded USB cable today. Still pulling up that error.
Is there any information I can include that would help pinpoint whats causing this issue?
Xeroproject said:
So unfortunately getting any work done on this on my Vista machine has been a total no-go. Vista won't take the 64-bit homebrewed driver, regardless of disabling driver authentication.
So I'm stuck. Day 2 here and I still get the "too many links" error. I've since retraced all my steps, redownloaded the SDK, JF's fastboot-win32, and completely removed all drivers from the system (including registry entiries) then reinstalled everything, and tried a shielded USB cable today. Still pulling up that error.
Is there any information I can include that would help pinpoint whats causing this issue?
Click to expand...
Click to collapse
Have you tried booting normally at least once?
Maybe try "fastboot erase cache", then try again?
JesusFreke said:
Have you tried booting normally at least once?
Maybe try "fastboot erase cache", then try again?
Click to expand...
Click to collapse
If you mean booting normally into Vista 64, yes, it sees the G1 as an "unknown device" in Device Manager and when I point it to the 64-bit driver, it won't take it. Same for when driver auth is disabled. (although the message changes from "no device drivers found" to "this driver is not compatible with your device)
If you mean the phone, yes, the phone works, its not bricked, but there's a lot of data I'm losing if I can't solve this issue & backup from my nandroid backups.
I'll give the erase cache thing a shot now and post results, thanks for the suggestion.
interesting, the "fastboot erase cache" command also returns a "FAILED <status read failed <Too many links>>" error
Perhaps the problem is with the fastboot.exe file?
Xeroproject said:
interesting, the "fastboot erase cache" command also returns a "FAILED <status read failed <Too many links>>" error
Perhaps the problem is with the fastboot.exe file?
Click to expand...
Click to collapse
I doubt it. I remember seeing this error once when I stopped a fastboot flash while it was doing it's thing. I don't remember exactly what I did to fix it. I thought I just rebooted or something.
It's a shot in the dark, but maybe take the battery out for a few seconds and put it back in and try again?
I would also try any and all of the fastboot commands
If nothing else, you could try reflashing the engineering SPL, or even the RC29 nbh.
JesusFreke said:
I doubt it. I remember seeing this error once when I stopped a fastboot flash while it was doing it's thing. I don't remember exactly what I did to fix it. I thought I just rebooted or something.
It's a shot in the dark, but maybe take the battery out for a few seconds and put it back in and try again?
I would also try any and all of the fastboot commands
If nothing else, you could try reflashing the engineering SPL, or even the RC29 nbh.
Click to expand...
Click to collapse
Yeah, I wish I knew the cause of it, but the initial use was uninterrupted (and everytime I reboot, I will get 5-10sec lag before getting the error, while after that the error will popup immediately)
I'm happy to try any of the fastboot commands, but being a little nubbin, I'm a little afraid of doing any damage. I did try fastboot reboot and fastboot reboot-bootloader and got no response from the phone. "fastboot devices" immediately sees my phone. "fastboot flashall" returns: "error: neither -p product specified nor ANDROID_PRODUCT_OUT set".
Removing the battery is something I've done a couple times the other day, just gave it another shot now, same result. I've noticed the too many links error will say it "failed to read" on the first attempt, after that it reverts to "failed to write".
Concerning reloading the phone back to RC29....you mean taking it back to RC29, then reflashing the Engineering SPL, then immediately trying to backup from my nandroid backups? (prior to installing any of the JF OS versions?)
I have also faced this error few time, what I do is disconnect the USB, restart both PC and G1, next time I get proper connection, once time I was able to resolve just by moving the ramdisk.img and kernel file from the directory, this was when I was using the fastboot -w flashall command!!
-Pramod
Might be onto something there JF, I just checked my SPL edition and I'm running the HardSPL not the EngineSPL.
Is the HardSPL not suited for this perhaps?
for fastboot -w flashall to work you need to set the ANDROID_PRODUCT_OUT variable, where boot.img, recovery.img and system.img file are, on window just use the set command
set ANDROID_PRODUCT_OUT=c:\<your directory where the files are>
and then run fastboot -w flashall
-Pramod
pramods said:
for fastboot -w flashall to work you need to set the ANDROID_PRODUCT_OUT variable, where boot.img, recovery.img and system.img file are, on window just use the set command
set ANDROID_PRODUCT_OUT=c:\<your directory where the files are>
and then run fastboot -w flashall
-Pramod
Click to expand...
Click to collapse
Alright, I'm with you, just returned "error: could not load android-info.txt"
The same directory also need to have android-info.txt file, this file just have a single entry as board=trout in it, if you don't have it create this file and then run fastboot again
-Pramod
pramods said:
The same directory also need to have android-info.txt file, this file just have a single entry as board=trout in it, if you don't have it create this file and then run fastboot again
-Pramod
Click to expand...
Click to collapse
Alright, so I did a search on my computer to see if I had an android-info.txt I could copy over, didn't have anything (including in the android-sdk files). So I went ahead and created one and just put "board=trout" in it like you said. New error: "getvar:version-bootloader FAILED <command write failed <Too many links>>"
Progress?
btw Pramod, you're a stud, thank you for all these suggestions
Xeroproject said:
I've noticed the too many links error will say it "failed to read" on the first attempt, after that it reverts to "failed to write"./QUOTE]
Do you mean on the first attempt after a reboot?
This makes me suspect usb issues. Do you happen to have any usb cords with a ferrite bead on them laying around that you could try?
Reboot, and then try flashing one of the splash images. They are relatively small, so if it is an issue with usb communication, there is less of a chance of it failing. Try it a couple of times.. if you can get it to work once, then I would say it's more than likely some sort of usb communication issue, bad cable, interference, etc.
Click to expand...
Click to collapse
JesusFreke said:
Xeroproject said:
I've noticed the too many links error will say it "failed to read" on the first attempt, after that it reverts to "failed to write"./QUOTE]
Do you mean on the first attempt after a reboot?
This makes me suspect usb issues. Do you happen to have any usb cords with a ferrite bead on them laying around that you could try?
Reboot, and then try flashing one of the splash images. They are relatively small, so if it is an issue with usb communication, there is less of a chance of it failing. Try it a couple of times.. if you can get it to work once, then I would say it's more than likely some sort of usb communication issue, bad cable, interference, etc.
Click to expand...
Click to collapse
Yeah, the first attempt after a reboot.
Yeah I actually picked a ferrite bead USB cable up the other day and then I also shut off my speakers (just in case a magnet or something was causing interference). Just checking around my desk at work, I don't really have anything else that would interfere to my knowledge. We deal with high speed check scanners at work and I haven't had any issues with the images they pull (also via USB, same computer).
I'll give the image deal a whirl, I believe I have all that software for converting them already on my computer.
Click to expand...
Click to collapse
Just try one more thing, creat a new directory and put all *.img files and *.txt file there and reboot your system(PC and G1[fastboot mode]) then set the ANDROID_PRODUCT_OUT variable and then fire the command fastboot devices , if the fastboot return the device identity then try fastboot -w flashall command
-Pramod
pramods said:
Just try one more thing, creat a new directory and put all *.img files and *.txt file there and reboot your system(PC and G1[fastboot mode]) then set the ANDROID_PRODUCT_OUT variable and then fire the command fastboot devices , if the fastboot return the device identity then try fastboot -w flashall command
-Pramod
Click to expand...
Click to collapse
All *img & *txt files off the SD card you mean?
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.
I recently aquired a Streak 7 and am having trouble resetting it since it has all the original owners info on it.
1. I encountered a force close error upon first boot.
- android.process.acore stopped unexpectedly
2. After this error continued to appear I said F*** this and rebooted into the Stock Dell recovery(Volume + and Power)
I chose option 3 for a factory reset and erase internal tablet storage.
Rebooted and Bam same bull**** errors. I did this 3 more times powering off with the pin hole off button after the streak kept booting with this error.
I read this entire forum development and general questions to see what problems others are having, I came across a few threads all very informative on how to attempt to restore your Streak 7.
Before attempting the various methods of either NVFlash, the fastboot method and even flashing clockwork recovery through fastboot I figured I would see what I could get the Streak to do in it's current state.
*Note* I am very familiar with ADB and Fastboot but if I over looked something I will not be offended if anyone can provide some useful information.
OK, Here is my story
I put the streak on my HDMI dock and was able to succefully install the ADB drivers on Windows 7 x64. From there I launched the ADB Shell
c:/androidsdk/tools> adb shell
$
once in the shell i found I could launch the android setting using this command
$ am start -a android.intent.action.MAIN -n com.android.settings/.Settings
Once in the settings and periodically hitting forceclose and quit to the .acore error I was able to retrieve this information
Android Version
2.2
Baseband Version
11.809.05.02.00
Kernel version
2.6.32.9
OEM Version
GLUNB1A132433
Build Number
14394
I also realized that I can install apps through adb so I went and installed the latest standalone ADW Launcher which installs fine and allows me to actually use the device a little.
c:\androidsdk\tools>adb install launcher.apk
1307 KB/s (2533717 bytes in 1.892s)
pkg: /data/local/tmp/launcher.apk
Success
You will notice that apps install to this location
/data/local/TMP
it turns out that even installing the new launcher won't allow me to do much because the previose owner changed his google password so I have no market acces or anything like that.
I then tried doing the factory reset within the Android settings>privacy>factory data reset.
The device reboots and I again encounter the same error and the device has also not reset the user data.
So i rooted the device and found that even root was only temporary, the ADB shell returns the # sign indicating that it has root, great but when the device is rebooted it returns to the condition I got it in.
If I run ADB remount with root I get this
c:\androidsdk\tools>adb remount
remount failed: Operation not permitted
c:\androidsdk\tools>
this tells me that even though the phone has root it will not mount any file system with read/write permissions
I then installed the latest free Clockwork Rom Manger via ADB
it prompts me for root permissions I select allow and then the app closes after it downloads and tries to write the clockwork recovery image. I said fine this won't work.
I moved on to the Flashing Clockwork Recovery via Fastboot
In Fastboot I get this
c:\androidsdk\tools>fastboot devices
? fastboot
c:\androidsdk\tools>fastboot -i 0x413C flash recovery clockwork.img
sending 'recovery' (4416 KB)...
OKAY [ 0.560s]
writing 'recovery'...
OKAY [ 0.110s]
finished. total time: 0.670s
c:\androidsdk\tools>
WOW I didn't know that 4MB could be sent and flashed over usb in under a second!!!! WTF!!!!!
So obviously there is something going on here where I cannot write to the internal memory...
I decided to just use NVFlash because people seem to be having luck with it
http://forum.xda-developers.com/showthread.php?t=1018809
I Didn't.......
I spent a hell of a lot of time downloading and redownloading the different images and finally got them all downloaded successfully. I run the restore.bat file and it says everything went fine but it didn't, I tried NVFlash with and without P14.img and it just doesn't seem to do anything it always restores it to how it was when i got it errors and all.
Now for the best method I tried, the fastboot method by flashing boot_orig.img, recovery_orig.img and system_orig.img
http://forum.xda-developers.com/showthread.php?t=1011654
Flash_image is not and ADB Shell command
and I also don't beleive the images are writing to the disc that fast.
I'm tired of typing now so please if anyone has any info on how I can write information to the internal ROM memory not the internal sd card I would greatly appreciate it.
Tom
wikedbubble said:
I recently aquired a Streak 7 and am having trouble resetting it since it has all the original owners info on it.
1. I encountered a force close error upon first boot.
- android.process.acore stopped unexpectedly
2. After this error continued to appear I said F*** this and rebooted into the Stock Dell recovery(Volume + and Power)
I chose option 3 for a factory reset and erase internal tablet storage.
Rebooted and Bam same bull**** errors. I did this 3 more times powering off with the pin hole off button after the streak kept booting with this error.
I read this entire forum development and general questions to see what problems others are having, I came across a few threads all very informative on how to attempt to restore your Streak 7.
Before attempting the various methods of either NVFlash, the fastboot method and even flashing clockwork recovery through fastboot I figured I would see what I could get the Streak to do in it's current state.
*Note* I am very familiar with ADB and Fastboot but if I over looked something I will not be offended if anyone can provide some useful information.
OK, Here is my story
I put the streak on my HDMI dock and was able to succefully install the ADB drivers on Windows 7 x64. From there I launched the ADB Shell
c:/androidsdk/tools> adb shell
$
once in the shell i found I could launch the android setting using this command
$ am start -a android.intent.action.MAIN -n com.android.settings/.Settings
Once in the settings and periodically hitting forceclose and quit to the .acore error I was able to retrieve this information
Android Version
2.2
Baseband Version
11.809.05.02.00
Kernel version
2.6.32.9
OEM Version
GLUNB1A132433
Build Number
14394
I also realized that I can install apps through adb so I went and installed the latest standalone ADW Launcher which installs fine and allows me to actually use the device a little.
c:\androidsdk\tools>adb install launcher.apk
1307 KB/s (2533717 bytes in 1.892s)
pkg: /data/local/tmp/launcher.apk
Success
You will notice that apps install to this location
/data/local/TMP
it turns out that even installing the new launcher won't allow me to do much because the previose owner changed his google password so I have no market acces or anything like that.
I then tried doing the factory reset within the Android settings>privacy>factory data reset.
The device reboots and I again encounter the same error and the device has also not reset the user data.
So i rooted the device and found that even root was only temporary, the ADB shell returns the # sign indicating that it has root, great but when the device is rebooted it returns to the condition I got it in.
If I run ADB remount with root I get this
c:\androidsdk\tools>adb remount
remount failed: Operation not permitted
c:\androidsdk\tools>
this tells me that even though the phone has root it will not mount any file system with read/write permissions
I then installed the latest free Clockwork Rom Manger via ADB
it prompts me for root permissions I select allow and then the app closes after it downloads and tries to write the clockwork recovery image. I said fine this won't work.
I moved on to the Flashing Clockwork Recovery via Fastboot
In Fastboot I get this
c:\androidsdk\tools>fastboot devices
? fastboot
c:\androidsdk\tools>fastboot -i 0x413C flash recovery clockwork.img
sending 'recovery' (4416 KB)...
OKAY [ 0.560s]
writing 'recovery'...
OKAY [ 0.110s]
finished. total time: 0.670s
c:\androidsdk\tools>
WOW I didn't know that 4MB could be sent and flashed over usb in under a second!!!! WTF!!!!!
So obviously there is something going on here where I cannot write to the internal memory...
I decided to just use NVFlash because people seem to be having luck with it
http://forum.xda-developers.com/showthread.php?t=1018809
I Didn't.......
I spent a hell of a lot of time downloading and redownloading the different images and finally got them all downloaded successfully. I run the restore.bat file and it says everything went fine but it didn't, I tried NVFlash with and without P14.img and it just doesn't seem to do anything it always restores it to how it was when i got it errors and all.
Now for the best method I tried, the fastboot method by flashing boot_orig.img, recovery_orig.img and system_orig.img
http://forum.xda-developers.com/showthread.php?t=1011654
Flash_image is not and ADB Shell command
and I also don't beleive the images are writing to the disc that fast.
I'm tired of typing now so please if anyone has any info on how I can write information to the internal ROM memory not the internal sd card I would greatly appreciate it.
Tom
Click to expand...
Click to collapse
Bump for a resolution. A lot of folks seem to be encountering this issue; I think it has something to do with a Linux failsafe measure (from another thread), but I'm not savvy enough in Linux to know for sure. Good luck to you!
Hey Thanks for the Bump, I am tearing my hair out over thins thing.
On another note I found this post for the LG GX2 for flashing clockwork recovery through APX with NVFLASH
http://www.techofweb.com/technology/flashing-cwm-recovery-g2x.html
I hope there might be a way to do this on the Streak, but I don't know that much about NVFlash. My hope in getting the clockwork recovery is that the restore and recovery tools used in clockwork recovery will in theory allow me to format and write roms to the internal memory...... I hope
Anyway I hope someone is reading and understanding my trouble other than Z4nd4r
Tom
I've been having similar problems with my streak7. It was working fine on stock 2.2.2 then got stuck in boot loop at the "stick together" screen.
I tried to factory reset in recovery. No change.
I tried to restore with nvflash. It completed fine, but no change.
http://forum.xda-developers.com/showthread.php?t=1018809
I tried with fastboot (boot.img, restore.img and system.img). It completed fine, no change.
I tried the 2.2.2 update.pkg in recovery, but it stops at "install modem error", no change.
I tried to flash DJ_Steve's honeycomb, and it stops at:
Formatting partition 2 BCT please wait... FAILED!
command failure: create failed (bad data)
bootloader status: partition table is required for this command (code: 8) message: nverror:0x2 (0x2) flags: 0
I tried formatting all partitions with:
nvflash --bl bootloader.bin --format_all
then restore with nvflash
It completes with no errors, but still no change.
I also tried to get clockwork on the streak 7 with fastboot. Even though I didn't get any errors, clockwork recovery did not get installed. So I'm thinking it's some sort of write protect error, since nothing I write to the device seems to be sticking.
If I format all partitions, would the streak 7 even get to the t-mobile "stick together" logo? I would think it would get stuck at the dell logo. I'm stuck at this point and have no idea what to try next. Any suggestions?
Could the problem be due to previous owner(s) trying to root the DS7 and Dell had implemented some kind of security measure to prevent rooting of the DS7?
Bump for a real solution.
I found a solution and my solution was to sell it before I threw it against a wall.
What's the common denominator, here? Were these all purchased used/3rd party?
Mine was bought new and ran great till mothers day and my sis asked to use it to post pics to facebook so I unmounted my sd and gave it to her she poped in her 32 gig sd card and got tired of waiting for the the gallery to populate and ejected the card without unmounting it and handed it back to me and said it was junk an and slow .......ever since its been stuck in read only
Ive dissasymbled it formated it flashed it factory reset it and reguardless of what I do still comes back the same as though I hadnt touched it.......even tried to short the nand chip out to clear it..........its like a cockroarch thats wounded .....it just wont finish dieing
I think we need a jtag solution. Doesn't seem like anything done with current tools will help.
I've scoured the internet and turned up nothing.
My streak 7 is collecting dust and probably going on eBay soon. To hell with Dell. This is my first Dell android device and probably my last.
Edit: found information
So I found the datasheet for the NAND chip the Streak 7 uses (http://omapworld.com/iNAND_e_MMC_4_41_IF_data_sheet_v1_0[1].pdf). Aparently the NAND has a write protect feature (temporary and permanent). Tech5 from this thread http://forum.xda-developers.com/showthread.php?t=1113264 says there's a failsafe function that locks the NAND in write protect mode. I don't have the hardware expertise to dig down and see if the system is write protecting the system by locking the chip in write protect mode. If we can somehow figure out how to disable the write protect on the chip, we may have a solution. Maybe someone with good hardware knowledge can take a look and give some feedback?
I'm having this same issue over here. I've tried NVFLASH and Fastboot and it acts like it's happening and then you reboot and get back to the same image every time. Maybe time for a call to Dell on this?
Call Dell
It looks like these Streaks are all stock and having the same problem. I tried calling dell but they wouldn't help me because the streak I got doesn't have the flap for the sd card and that is where they say the Service Tag is written. Freaking BullSh!t. Anyway if someone is willing to call dell and see what they have to say that would be awesome.
Dell is the only solution?
I had a same problem too. No matter what I do, the unit reverts back. It became Read-Only Mode. I guess it happens often enough DELL aware of this problem and the tech supports knows what to do. Only way to fix the unit at this point is ship it back.
I shipped back to Dell and Dell repaired it. Turn Around time: 1 Week.
This is my 1st post.
I do have Streak 5 and 7. I love Streak 5 and DJ Steve's ROM Rocks in Streak 5.
wikedbubble said:
It looks like these Streaks are all stock and having the same problem. I tried calling dell but they wouldn't help me because the streak I got doesn't have the flap for the sd card and that is where they say the Service Tag is written. Freaking BullSh!t. Anyway if someone is willing to call dell and see what they have to say that would be awesome.
Click to expand...
Click to collapse
Settings > About > Status > Service Tag at the bottom.
I'm on the phone with Dell right now about this as I can't find another solution and another user had to get theirs repaired. We'll see what they say.
Solution to write protect?
I was trying to copy some music to mine and got the write protect error message. I took out the micro SD card holder and it indeed was locked. Flipped the switch and back in business! Hope this helps someone!
I wonder if it is newer streaks that are doing this, because I think mine was in stock with Tmobile for a while. They had plenty of them there. They must be "Locking the bootloader" so to speak. If anyone wants to send one to a Dev maybe they can do something about it.
any luck with this any 1? =(
I had a similar issue last week, it looks to be the "Read-Only" Bug. I had to send mine back to Dell, and they just sent me a new unit.
Whatever you do, make sure your DS7 does NOT hit 0% battery, it seems to be the cause of this "Ready-Only" bug.
Hi, I have two Kindle Fire HD 7 inch, I think both are the older model. Until recently, one was bricked after i rooted but it started getting random restarts after being fine for months. I decided to try flashing a custom ROM, but due to following a YouTube video and not loading the ROM first before flashing, my fault as I mid heard the instructions, it died and I didn't know enough to reliase it could be fixed with a factory cable. I got a replacement and due to a **** up at Amazon, I managed to keep the broken one also.
I decided to root the newer one a few weeks in but months later it started having issues with dolphin browser constantly restarting, so I decided to buy a factory cable as a precusion and flash it to cyanogenmod. Everything went well so i dawned on me that I could fix the first one with my cable. I managed to fix with instructions from here and then flashed as well. Everything seemed to work fine until it started randomly restarting. Then it would get stuck at the blue kindle logo, would still allow me into twrp, so cleared dalvik and everything else and reflashed, it would load as newly flashed, but end up restarting again and eventually getting stuck at the blue logo again. I've seen a few threads with similar problems but couldn't find one that matched the circumstance.
So, my question, it this likely a hardware issue as it did get dropped once or twice in its short working life, or is it a software issue and something I could fix ???
damofitz said:
Hi, I have two Kindle Fire HD 7 inch, I think both are the older model. Until recently, one was bricked after i rooted but it started getting random restarts after being fine for months. I decided to try flashing a custom ROM, but due to following a YouTube video and not loading the ROM first before flashing, my fault as I mid heard the instructions, it died and I didn't know enough to reliase it could be fixed with a factory cable. I got a replacement and due to a **** up at Amazon, I managed to keep the broken one also.
I decided to root the newer one a few weeks in but months later it started having issues with dolphin browser constantly restarting, so I decided to buy a factory cable as a precusion and flash it to cyanogenmod. Everything went well so i dawned on me that I could fix the first one with my cable. I managed to fix with instructions from here and then flashed as well. Everything seemed to work fine until it started randomly restarting. Then it would get stuck at the blue kindle logo, would still allow me into twrp, so cleared dalvik and everything else and reflashed, it would load as newly flashed, but end up restarting again and eventually getting stuck at the blue logo again. I've seen a few threads with similar problems but couldn't find one that matched the circumstance.
So, my question, it this likely a hardware issue as it did get dropped once or twice in its short working life, or is it a software issue and something I could fix ???
Click to expand...
Click to collapse
i can take a few guesses at what would be causing a random reboot, i know dolphin can, i don't know why you would need to reflash to fix it though, thats very unusual unless maybe a filesystem error was causing it but it shouldnt have the same error everytime, i could suggest scanning the system partition for errors from recovery, i'd have to grab the command you'd need to run through adb. you dmesg would tell you if there were filesystem errors probably, mine was telling me about them so i finally got around to fixing them. i will mention i know dolphin can cause it to reboot randomly, i have had it happen before, i think it draws too much power trying to run it and causes the crash, not positive though.
On a side note you may want to rename the thread to 2012 kindle, the 2013 one is not rom-able, only rootable.
Did you overclock the processor?
stunts513 said:
i can take a few guesses at what would be causing a random reboot, i know dolphin can, i don't know why you would need to reflash to fix it though, thats very unusual unless maybe a filesystem error was causing it but it shouldnt have the same error everytime, i could suggest scanning the system partition for errors from recovery, i'd have to grab the command you'd need to run through adb. you dmesg would tell you if there were filesystem errors probably, mine was telling me about them so i finally got around to fixing them. i will mention i know dolphin can cause it to reboot randomly, i have had it happen before, i think it draws too much power trying to run it and causes the crash, not positive though.
On a side note you may want to rename the thread to 2012 kindle, the 2013 one is not rom-able, only rootable.
Click to expand...
Click to collapse
Sorry, your right, its the 2012, I just noticed that the 2013 doesn't have a front camera. As for dolphin, I uninstalled a bunch of times with the same result, but I like it because the flash player works well once set up properly. It always starts off fine then gets progressively more unstable on my working kindle. I don't know much about adb, just the basics but have KindleFireFirstAid and other programs that used the fix permission errors. I haven't got round to trying them get though as the kindle normally wont stay on long enough.
When it was just rooted, the kindle would still restart so I was hoping that flashing might fix it in case it was something I had done wrong.
Oh, and I haven't over clocked, I signed into play store and allowed it to download all my girlfriends crap so she could use it for a while while her galaxy tab goes into the shop as it has the red charging cross issue.
damofitz said:
Sorry, your right, its the 2012, I just noticed that the 2013 doesn't have a front camera. As for dolphin, I uninstalled a bunch of times with the same result, but I like it because the flash player works well once set up properly. It always starts off fine then gets progressively more unstable on my working kindle. I don't know much about adb, just the basics but have KindleFireFirstAid and other programs that used the fix permission errors. I haven't got round to trying them get though as the kindle normally wont stay on long enough.
When it was just rooted, the kindle would still restart so I was hoping that flashing might fix it in case it was something I had done wrong.
Click to expand...
Click to collapse
you mind booting it up into a os and running this from a command prompt?
Code:
adb shell dmesg > log.txt
you will need to have a command prompt cd'd into the directory of adb, so either in a kffa folder or srt folder will do, anything that came with adb really. if you don't know much about command prompt then do this: shift + right click the folder with adb, hit "open command window here", then run that command.
stunts513 said:
you mind booting it up into a os and running this from a command prompt?
Code:
adb shell dmesg > log.txt
you will need to have a command prompt cd'd into the directory of adb, so either in a kffa folder or srt folder will do, anything that came with adb really. if you don't know much about command prompt then do this: shift + right click the folder with adb, hit "open command window here", then run that command.
Click to expand...
Click to collapse
I normally go from the SDK platform tools folder to check the device is coming up, does that work?
damofitz said:
I normally go from the SDK platform tools folder to check the device is coming up, does that work?
Click to expand...
Click to collapse
Ok, i tried and it and it just shows the command line again. Have killed and restarted server but no difference
C:\Users\Kirsty\Desktop\SDK\sdk\platform-tools>adb devices
List of devices attached
D025A0A024060MRL device
C:\Users\Kirsty\Desktop\SDK\sdk\platform-tools>adb shell dmesg > log.txt
C:\Users\Kirsty\Desktop\SDK\sdk\platform-tools>
update: I have noticed that when plugged into my laptop, the Kindle will stay on indefinitely, but when I unplug or not long after, the Kindle then restarts, especially when im doing something like searching the web or opening apps, so could it be a power source problem?
damofitz said:
Ok, i tried and it and it just shows the command line again. Have killed and restarted server but no difference
C:\Users\Kirsty\Desktop\SDK\sdk\platform-tools>adb devices
List of devices attached
D025A0A024060MRL device
C:\Users\Kirsty\Desktop\SDK\sdk\platform-tools>adb shell dmesg > log.txt
C:\Users\Kirsty\Desktop\SDK\sdk\platform-tools>
update: I have noticed that when plugged into my laptop, the Kindle will stay on indefinitely, but when I unplug or not long after, the Kindle then restarts, especially when im doing something like searching the web or opening apps, so could it be a power source problem?
Click to expand...
Click to collapse
i probably should have mentioned that the commadn i asked you to run was outputting the text into a file called log.txt in the same folder you ran the commadn in... plz post it as a attatchment. sorry for my stupidity.
stunts513 said:
i probably should have mentioned that the commadn i asked you to run was outputting the text into a file called log.txt in the same folder you ran the commadn in... plz post it as a attatchment. sorry for my stupidity.
Click to expand...
Click to collapse
No need to apologize. I left the table on all night and its still on this morning. The log is attached
damofitz said:
No need to apologize. I left the table on all night and its still on this morning. The log is attached
Click to expand...
Click to collapse
think the filesystem is ok not seeing any errors...another thing you could do is leave the device plugged into the pc with this running
Code:
adb shell "su -c 'cat /proc/kmsg'"
and whenever it reboots just copy and paste the last lines it outputted.
Ok so this is the rundown. Ran Fix Contexts in TWRP recovery no longer could get phone to connect to pc to read SD card period. Ran several apps that didn't fix SD card permissions. wiped phone completely including DATA, SYSTEM, and SDCARD. had a custom rom on the phone didnt think it would wipe its wiped.
Im in TWRP no adb sideload, no fastboot from bootloader. something with file permissions is preventing phone from even being seen by PC. and no its not USB issues i tried to run RUU. it cant even see my phone. No one can even provide a suggestion i can still do terminal from TWRP but it has something to do with me using the fix contexts that screwed it up.
really no one has a suggestion? i have access to TWRP recovery and can run terminal commands i just need something to fix what ever fix contexts did so i can get access to usb functionality. please? if looked all over google and there is no one with this issue. every topic points to adb sideload and fastboot working but usb doesnt work in my case due to use of fix contexts.
M4rin3r said:
really no one has a suggestion? i have access to TWRP recovery and can run terminal commands i just need something to fix what ever fix contexts did so i can get access to usb functionality. please? if looked all over google and there is no one with this issue. every topic points to adb sideload and fastboot working but usb doesnt work in my case due to use of fix contexts.
Click to expand...
Click to collapse
i solved it mysself no thanks to a forum that supposed to help and yet im a noob at this ****.
for those of you who have done as i did and bricked the phone.
go into twrp recovery and go to terminal
Code:
busybox
echo "persist.service.adb.enable=1" >> default.prop
echo "persist.service.debuggable=1" >> default.prop
echo "persist.sys.usb.config=mtp,adb" >> default.prop
Reboot phone to see if it worked. then try to see if you can use adb on pc to sideload a rom.
M4rin3r said:
i solved it mysself no thanks to a forum that supposed to help and yet im a noob at this ****.
for those of you who have done as i did and bricked the phone.
go into twrp recovery and go to terminal
Code:
busybox
echo "persist.service.adb.enable=1" >> default.prop
echo "persist.service.debuggable=1" >> default.prop
echo "persist.sys.usb.config=mtp,adb" >> default.prop
Reboot phone to see if it worked. then try to see if you can use adb on pc to sideload a rom.
Click to expand...
Click to collapse
Well, I could have come in here and pretended I've seen this before, but honestly, I've never run Fix Contexts in TWRP (in fact, I've never heard of it). You've got to remember that most of us know what we know either through our own bad experiences or by following how others fixed their bad experiences. So, I appreciate that you marked it solved and put how you solved it in this thread. Next time someone has the same issue, I'll know where to look for a solution.
coal686 said:
Well, I could have come in here and pretended I've seen this before, but honestly, I've never run Fix Contexts in TWRP (in fact, I've never heard of it). You've got to remember that most of us know what we know either through our own bad experiences or by following how others fixed their bad experiences. So, I appreciate that you marked it solved and put how you solved it in this thread. Next time someone has the same issue, I'll know where to look for a solution.
Click to expand...
Click to collapse
Its also known as fix permissions.
@ M4rin3r
Can you PM me with more details on how to do this, I'm facing the same problem....