Related
Hi all,
I am completely at my wits end here and just don't know what to do
I have successfully unlocked my stock Nexus One boatloader, and have installed superboot to root it.
- I am using Windows 7 64 bit with all USB drivers for the nexus one correctly installed
- I have remembered to reset debuggingt mode in the Nexus USB settings
- Rooted apps seem to be working fine - I've just been playing with the LED torch app and I have a 'Superuser Permission' icon in my programs list
I am attempting to install the Amon_Ra recovery file - I've tried two different versions of it with no joy so far.... 1.7.0 and 1.6.2
I am able to boot into fastboot (with the skateboarding droids) with no probs. I can see the device using fastboot devices. However, when I try to send any recovery image using fastboot, it just hangs there with an empty progress bar on the right hand side of the screen in green that doesn't fill up.... Here is the terminal output:
---
C:\AndroidSDK\android-sdk-windows\tools>fastboot devices
HT9C(-REMOVED-) fastboot
C:\AndroidSDK\android-sdk-windows\tools>fastboot flash recovery recovery.img
sending 'recovery' (3948 KB)...
---
Anybody have any idea why it hangs here and if there is anything else I can do to maybe figure out why? I'm pretty certain I've almost cracked it - installing this recovery image is a problem
Thanks in advance!
Gil
don't rename the recovery.img file.
Then if that still doesn't work...maybe try using a terminal on your phone. Not sure myself which terminal app works.
SiNJiN76 said:
don't rename the recovery.img file.
Then if that still doesn't work...maybe try using a terminal on your phone. Not sure myself which terminal app works.
Click to expand...
Click to collapse
Thanks for the quick response!
It still fails even when I don't rename the recovery image.
Re 'using a terminal on my phone' - is there a guide to this anywhere? Do I download a shell or something?
TIA!
Gil
Go to market and search Android Terminal Emulator.
Then follow these instructions:
via terminal app
Code:
Copy recovery-RA-nexus-v1.7.0.img to the root of your sdcard
start the terminal app
su(press enter)
flash_image recovery /sdcard/recovery-RA-nexus-v1.7.0.img(press enter)
reboot recovery(press enter)
Got those instructions from the Recovery thread.
It looks like fastboot is not properly detecting your device? Also, did you install "superroot" before attempting to flash recovery image?
Thanks everyone for the help so far.
SiNJiN76 said:
Go to market and search Android Terminal Emulator.
Then follow these instructions:
via terminal app
Code:
Copy recovery-RA-nexus-v1.7.0.img to the root of your sdcard
start the terminal app
su(press enter)
flash_image recovery /sdcard/recovery-RA-nexus-v1.7.0.img(press enter)
reboot recovery(press enter)
Got those instructions from the Recovery thread.
Click to expand...
Click to collapse
I have tried these steps - when I issue the su command, I get root and a dialog box prompting me to allow it. However, when I type the flash_image command, I get the following message:
flash_image: not found
How is it that I don't have the flash_image command on my Nexus?!
aoch88 said:
It looks like fastboot is not properly detecting your device? Also, did you install "superroot" before attempting to flash recovery image?
Click to expand...
Click to collapse
I think fastboot is detecting my device, because I managed to display the serial number (I obsficated most of the output above for security reasons) and I also successfully unlocked the bootloader. After I unlocked the bootloader, I tried to copy over the recovery image, and it just hung, so I then went and installed Modaco's superboot version ERD27 with himem enabled. This allowed me root access but still will not allow me to flash with the recovery image.
In addition, I have noticed that since I installed superboot himem, I am having a couple of network issues. Firstly - my 3G signal has now dropped from virtually full strength all the time to now never more than 50% strength, and frequently gives network errors when accessing the android store. It has also said "emergency calls only" a couple of times and probably worst of all (!) no longer checks my gmail automatically (I have plenty of emails but don't get notified - texts work fine though and my contacts are all still there and my account seems to be linked) - could the superboot have affected this in any way?
Thanks all for your help - I'm getting a little worried I may have totally borked my phone now
Gil
A little extra info if it helps anyone - I just tried to erase the recovery image in fastboot to see if I could then write a new recovery image. Here is the output:
---
C:\AndroidSDK\android-sdk-windows\tools>fastboot devices
HT9CXP8##### fastboot
C:\AndroidSDK\android-sdk-windows\tools>fastboot erase recovery
erasing 'recovery'... FAILED (remote: not allowed)
---
Anybody have any clue what this means?
Try to redownload the recovery image, maybe you got a bad download.
thisisgil said:
when I try to send any recovery image using fastboot, it just hangs there with an empty progress bar on the right hand side of the screen in green that doesn't fill up....
Click to expand...
Click to collapse
Can you try a different USB port? I found when flashing mine that it didn't like USB1.1 only worked on USB2.0
thisisgil said:
A little extra info if it helps anyone - I just tried to erase the recovery image in fastboot to see if I could then write a new recovery image. Here is the output:
---
C:\AndroidSDK\android-sdk-windows\tools>fastboot devices
HT9CXP8##### fastboot
C:\AndroidSDK\android-sdk-windows\tools>fastboot erase recovery
erasing 'recovery'... FAILED (remote: not allowed)
---
Anybody have any clue what this means?
Click to expand...
Click to collapse
Another thing I discovered recently: Never use a port on a USB hub. Always use a USB port on the PC directly. I was having trouble flashing ROMs on my Acer Liquid and they went away when I stopped using a port on the hub.
without a doubt i bet its a naming issue, this is one of those things that go unmentioned and overlooked. either u do or dont have file extensions showing or not and or the .img does or does not need to be changed to .zip, i messed with this for days last year when flashing my g1. just go and change whatever you hide/show known file extensions is set to and see if ur problem is solved.
Sent from my Nexus One using the XDA mobile application powered by Tapatalk
AndyBurns said:
Can you try a different USB port? I found when flashing mine that it didn't like USB1.1 only worked on USB2.0
Click to expand...
Click to collapse
Thank you AndyBurns. I registered just to say that. You saved me a lot of time.
I had the same problem. Had the USB cable plugged into my front 1.1 ports instead of the back 2.0 ports. Switch ports and now I'm good to go.
Thank you.
Hi all -
Just wanted to post a follow up to this message, in the hope that it may help someone in the future!
Basically, I was not using the original USB cable that came with the nexus one (lost it), and instead was using a cable that I bought from a mobile phone retailer - it was basically one of those 6-in-1 multi USB cables where I had to put an adaptor on the end to switch it from mini to micro USB to fit the Nexus one.
Anyhow, for some reason, despite the fact that I could charge the phone using this new cable, and access it through device manager, explore the contents of the phone, root it etc etc, it would not do the flash as described above. I went out and bought a dedicated 1 metre gold plated micro USB cable, and it worked great
Dodgy cables - should have thought of this before I spent days frigging around and maybe even almost bricking the phone with a bad flash
I recently upgraded my G1 to the cyanogenmod 2.1 ROM and everything went fine untill i went to the market and installed a program called ROM manager. while i was using ROM manager it had an option, i cant remember what its name was, that said it fixes FC's if needed. Well i was getting those in ROM manager so i clicked it. It did a bunch of stuff and then suddenly tossed an error at me. Next thing i know im getting LOTS of FC's and when i rebooted my phone im suddenly stuck staring at the G1 boot screen and thats where it stays......indefinetly.
I cant get into recovery mode, already tried that. And so far the only thing(that i know of) that i can do is get into fastboot. Does anyone know how i can fix this? Its gotta be software related from whatever that ROM Manager program did to my permissions. But now im basically bricked and cant do anything.
My storage card still has all of the ROM's and files from when i flashed last but i dont know if or how i can use that to re-flash my phone again and start over.
Any suggestions?
I had a similar issue just yesterday. Dowloaded rom manager from the marketplace - attempted to flash recovery - pulled an error and ended up on the G1 screen. Could not get into recovery, but fastboot was available.
I followed these instructions
( reboot holding camera button, connect usb and press back button )
on pc
HTML Code:
fastboot erase system -w
fastboot flash recovery <recovery.img>where <recovery.img> is the full path to the recovery you want to flash
I had to do a full erase in fastboot - that is the first line of text above, I then flashed my recovery.img again - that is the second line of text above (I placed my recovery.img file directly in the adb folder - so it easy to find )
Once I was able to get back into recovery - I restored my last back-up, and the phone booted once again.
If you do not have any backups - I am not aware of the next step. Hopefully someone with more experience can direct you accordingly
Good luck
How is it that you send the commands? I plug in my USB, then hit back and it says FASTBOOT USB but how do i input the HTML codes to get it to do anything?
Do i make an HTML file on the pc and upload it, if so, how? I understand all of it except how to get the commands into it.
Well that and what the full path will be for the recovery.img.
well i feel like a total moron !!! lol
I had been being a script kiddie for the last few years and forgot my roots. I got it figured out and got the commands sent to fastboot in a CMD prompt.
Ugh, i gotta stop using google so much and finding all the easy ways out of things that others have already written.
Thanks for the help, much appreciated and worked a treat. I flashed everything and its working great again
I am looking for guidance this time.....I have a Nexus s I9020 (t mobile version) and a couple weeks ago I don't know what happened really but i may have been messing around with a newer version of clockwork recovery late one night .... then the phone wouldn't boot past the google screen and I couldn't do anything to fix it... I tried to figure things out the next day and this is a list of things i have figured out...
1. in clockwork it can't mount anything....like anything at all pertaining to the internal memory/storage
2. I was tired and irresponsible
3. I tried fastboot just about everything
4. I tried flashing newer/older versions of clock work......nothing worked
5. I have tried downloading and installing roms via adb and fastboot but an error message comes up...
6. now this I know is retarded but make fun of me as you will... I fastboot locked the device......i know stupid because now when I type in fastboot oem unlock it hangs and does nothing after I check unlock on the phone...
I can get into fastboot mode and it says no boot or recovery img?
now if I had access to the internal memory I would def. be able to go back to stock but there in lies the problem what on earth can i do to make this thing a paper weight?
this is what i'm talking about, the bootloader doesn't unlock it just hangs .... any thoughts?
"w w w.youtube.com/watch?v=C4cS0kMj4AI"
Hi,
I mangled my clockwork recovery and stupidly didnt update to a working one. now my G1 is stuck at the boot up screen and i cant do anything. I need to get into recovery to reflash a rom!
what can i do?
Some more infos would be helpful, e.g. phone version, radio, SPL ...
For example if you have an "european" G1, you could do this:
a) If you have a fastboot enabled SPL (e.g. 1.33.2003, 1.33.2005, ...) -> go into fastboot mode, flash recovery, boot into that recovery and flash ROM
b) If you don't have a fastboot enabled SPL, make a Goldcard, flash e.g. orange-xxx.nbh -> now you have a fastboot enabled SPL, flash recovery, radio, SPL as needed, then continue with a)
i have a Uk G1.
I have 1.33.2005.
When I go into fastboot mode but i dont see "flash recovery" anywhere..
Fastboot ist a command you use from you PC while having connected your phone by USB.
In this thread you can have an overview of adb / fastboot / ... and how to set up. If you are on Winxx, probably you would like to have a look at this thread.
Nevertheless if you have set up the fastboot environment, typing
fastboot flash recovery <recovery.img>
on your local console window, having <recovery.img> in the current working directory on your PC will flash the recovery image on your phone.
im at work so cant install any of those....theres nothing i can do from my phone direct?
Unfortunately not ... how would you like to do it, when your phone neither boots recovery nor the ROM?
i see your point ! lol
I thought since i can get into the hboot screen (CAMERA and on buttons together) maybe something can be done....but obviously not!
AndDiSa said:
Fastboot ist a command you use from you PC while having connected your phone by USB.
In this thread you can have an overview of adb / fastboot / ... and how to set up. If you are on Winxx, probably you would like to have a look at this thread.
Nevertheless if you have set up the fastboot environment, typing
fastboot flash recovery <recovery.img>
on your local console window, having <recovery.img> in the current working directory on your PC will flash the recovery image on your phone.
Click to expand...
Click to collapse
Will not getting past the boot screen hinder any of this process...? especially as i keep seeing "select USB debugging mode" in these guides?
Press back+power to start phone in fastboot mode. Connect it to your PC using USB. (Probably you need to select fastboot on your phone later on, I do not remember at the moment.) After your phone was recognized by your PC (check by typing "fastboot devices") you can flash your recovery again.
There should be not G1 screen visible when starting your phone.
Sent from my Gingerbread on Dream using XDA App
As long as you can get in the HBoot... lucky you it isn't hard bricked like mine
I think I just bricked my US Tmobile G1! I was messing up trying to reflash the SPL and now the phone won't even turn on. Is there anything I can do to rescue my G1? I love the little phone.
Sent from my LG-P999 using XDA Premium App
jtag, riffbox... i never used them but i heard many people say it un bricked they're G1's lol not sure if this helps either but look into making a gold card..? or something like that.. lol or mabe the orange thing... im sorry i forget what its called..
ldrifta said:
jtag, riffbox... i never used them but i heard many people say it un bricked they're G1's lol not sure if this helps either but look into making a gold card..? or something like that.. lol or mabe the orange thing... im sorry i forget what its called..
Click to expand...
Click to collapse
Gold Card doesn't work and it is cheaper to get a new phone than to get Jtag. Thanks for your ideas anyways!
Sent from my LG-P999 using xda premium
Hi guys
Let me start off by saying..I should have never attempted this myself.
I'm hoping somebody could please help me with my somewhat-bricked device..bricked in the sense that I don't know what to do with it. (i'm a noob to this). I've tried installing a custom rom and completely screwed up my dell streak 5.
So the phone doesn't boot anymore and just takes me to the option to install update.pkg off the sd card. I added the file along with recovery.img to the sd card.
360 17397 00 May 31, 2011 PKG Recovery Hash Latest Retail rom
My problem is that I cannot for whatever reason get Flashboot to work in order to flash the recovery.img first. under device manager you see android phone/android adb interface but still can't manage the connection to use cmd prompt/fastboot.
Is there any other way of getting the recovery.img to work without fastboot..maybe thru the sd card. I have no idea what i'm doing anymore. I've tried installing the update.pkg but after installation it just stays on the dell logo loading screen forever.
PLEASE help if you can.
Well lets start off to get you back on a stock rom, as it sounds like that would be the easiest at this point. We can move on to a custom rom from there.
The pkg file you downloaded....did you rename it update.pkg ?
If not, rename it update.pkg and make sure it is on the root of your sd card. Get to the recovery menu where you have the option of upgrading from update.pkg and choose it. In about 5 minutes, you'll have a clean stock rom.
I tried installing the 360 rom listed on http://forum.xda-developers.com/wiki/index.php?title=Dell_Streak
I did name it update.pkg
It went through the installation phase but on reboot it doesn't get past the Dell Logo loading screen. Any suggestions?
On the screen where you choose upgrade from update.pkg, choose factory reset and see if that helps
Tried both..unfortunately, same end.
Is flashing recovery a required step prior to doing this..because I was unable to do that.
Also, Thank you for taking an interest. I really appreciate it.
yes, you need to have the recovery for the rom you are flashing (at least when it comes to stock roms). My understanding is that the pkg file is encrypted and the recovery decrypts it.
I'm going to try to start from scratch here. I am also assuming you are using a Windows PC.
Download the drivers from Dell. Here's the link:
http://support.euro.dell.com/suppor...dateid=-1&formatid=-1&source=-1&fileid=433681
Install them and reboot your pc.
Download MultiRecoveryFlasher from here:
http://forum.xda-developers.com/showthread.php?t=1000455
Extract it to somewhere on you pc where you can find it.
Now this hasn't been updated to include 360's recovery, but that's ok. We don't have to run the utility. It's the support files that are included that we are going to use.
Download the recovery.img for 360 (which I think you have already done)
Put the recovery.img in the root folder of MultiRecoveryFlasher. There should be other files in there such as fastboot.exe, adb.exe, etc.
Power down your phone and restart it in fastboot mode (hold down camera and power button together until you get a white screen. When fastboot appears in upper right, select it and plug your phone into your pc)
Verify the phone displays fastboot ready
Open a command prompt on your PC
Type in the following command: fastboot.exe -i 0x413c flash recovery recovery.img
Once that is done type in the following command: fastboot.exe reboot
Get ready to hold down the Volume + and - as soon as the screen goes black.
Now choose Upgrade from update.pkg
It should work now. If not, someone else may have to help you with another method such as QDL tool. I've never had to use that.
This is a screenshot of the problem i keep running into. i installed the drivers just as you said and am at the step with fastboot.
imgur [dot] com/gw2A0
Any advice? Thanks again
im an idiot.
i got fastboot to run and send over the recovery.img
currently installing the update.pkg but its still stuck at the Dell Logo screen upon reboot. No idea what is going on.
FIXED. You're a miracle worker. Thank you so much.
Only problem I have now is an irritating sequence of flashing buttons every now and then. Have you had a similar issue in the past?
THANK YOU so much again!
Are you on a stock rom still? Or have you moved on to a custom rom? Typically the flashing led's happen when you are running a rom with an "incompatible" baseband, but that should be pretty near impossible if you are running a rom installed from an update.pkg rather than an update.zip.
running the update pkg off the wiki site.
Only other problem I've noticed is that I can't get it to root. I've tried gingerbreak and superoneclick..both of which worked flawlessly in the past.
Baseband GAUSB1A134700-US
KERNEL 2.6.32.9-PERF
BUILD 17397
I really want another crack at getting streakdroid, but the phone just isn't budging. Tempted to flash/install another rom but worried as heck that this same incident is going to come up. (the flashing lights started after i updated the AMSS and DSP last night--my first attempt at installing streakdroid 2.3).
Installing the stock rom via the update.pkg file will overwrite the amss and dsp1. That's the biggest difference to the end user on update.pkg vs update.zip. It's the actual recommended way to install a baseband. There are several firmwares, besides amss and dsp1, that get installed with a pkg.
Now that you have MultiRecoveryFlasher on your pc, installed StreakMod (custom recovery) should be a breeze for you. The only thing to watch out for is since you have a stock rom now, the first time it boots it will rewrite the recovery back to stock. Here is how to get around this:
Download the custom rom of your choice.
Place the zip file on the root of your sd card.
Get your phone back in fastboot mode
Using MultiRecoveryFlasher, flash StreakMod
As soon as the screen goes black for the reboot, hold the volume +/- keys.
Choose option 2 again, this time it should take you into StreakMod
Choose flash from update.zip
On the next screen, choose search for zip file (similar wording)
Choose the custom rom from earlier
Let it do it's thing.
Choose reboot system now
Again, as soon as the screen goes dark, hold Volume +/-
Now choose option 1 - Factory Rest
Let it do it's thing.
It should boot up now and your custom recovery will stay intact.
Let me give you some friendly advice: Streakdroid 2.3 is too much of a work in progress. Install one of the other Streakdroids, Longhorn, Simple Streak, or even my Streakin' 354. Play with it for a while and learn a little more before jumping into one that may not be as stable.
As far as rooting a stock rom, the preferred method is via superuser.zip. I'm not at home, so I don't have the file to upload for you, but its on these Dell Streak forums somewhere. You have to have a custom recovery to use it though. The custom roms are all rooted already.
Thank you for everything
No problem. Did you get it working?
Sent from my Dell Streak using xda premium
Absolutely and I couldn't have done it without you. If you had written out just one of the x number of tutorials out there, I don't think anyone would have run into the problems I did at first.
Streakdroid 191 runs like a charm---snappy and more responsive than stock ever was.
Glad to hear it...I was lost when I first started too. Someone helped me out and I just like to pay it forward. It's what makes this forum my favorite.
lordmorphous said:
Glad to hear it...I was lost when I first started too. Someone helped me out and I just like to pay it forward. It's what makes this forum my favorite.
Click to expand...
Click to collapse
Hi guys.. Hi Mr Lordmorphous.. im a super noobie in dell streak 5.. i got my dell streak a month ago.. today my phone doesnt work.. im stuck on Dell logo when i am going to switch it to on.. i really dont know where to start and how to type the codes like you are talking about like .pkg ing. etc. .. when im pressing the factory reset nothing happens.. i also tried to click software upgrade via update.pkg on SD card and nothing happens .. i clicked also the screen calibration it says *successful calibration done*.. im totally lost.. can u help me how to start from beginning (like for super noobie like me)? also the codes that im going to type in pc.. thanks in advance!
dwadetiu said:
Hi guys.. Hi Mr Lordmorphous.. im a super noobie in dell streak 5.. i got my dell streak a month ago.. today my phone doesnt work.. im stuck on Dell logo when i am going to switch it to on.. i really dont know where to start and how to type the codes like you are talking about like .pkg ing. etc. .. when im pressing the factory reset nothing happens.. i also tried to click software upgrade via update.pkg on SD card and nothing happens .. i clicked also the screen calibration it says *successful calibration done*.. im totally lost.. can u help me how to start from beginning (like for super noobie like me)? also the codes that im going to type in pc.. thanks in advance!
Click to expand...
Click to collapse
RTFM
http://forum.xda-developers.com/wiki/index.php?title=Dell_Streak
Hi again guys.. and mr lordmorphous!
im following what you told him (aaivazi)..
I'm going to try to start from scratch here. I am also assuming you are using a Windows PC.
Download the drivers from Dell. Here's the link:
http://support.euro.dell.com/support...&fileid=433681
Install them and reboot your pc.
Download MultiRecoveryFlasher from here:
http://forum.xda-developers.com/show....php?t=1000455
Extract it to somewhere on you pc where you can find it.
Now this hasn't been updated to include 360's recovery, but that's ok. We don't have to run the utility. It's the support files that are included that we are going to use.
Download the recovery.img for 360 (which I think you have already done)
Put the recovery.img in the root folder of MultiRecoveryFlasher. There should be other files in there such as fastboot.exe, adb.exe, etc.
Power down your phone and restart it in fastboot mode (hold down camera and power button together until you get a white screen. When fastboot appears in upper right, select it and plug your phone into your pc)
Verify the phone displays fastboot ready
Open a command prompt on your PC
Type in the following command: fastboot.exe -i 0x413c flash recovery recovery.img
(im already here but this is what the command prompt says:
'fastboot.exe' is not recognized as an internal or external command, operable program or batch file.)
what should i do ?
Streak4ever said:
RTFM
http://forum.xda-developers.com/wiki/index.php?title=Dell_Streak
Click to expand...
Click to collapse
hi streak4ever thanks for reply.. what does RTFM means? thanks