Database Develop

Softbricked? Help Please

Hey, I have been messing around with my phone recently, and I have gone to the OTA update after I had root, to check it out. Well I decided to root again, so I was at RC30 and the build is JFv1.3. Now, I put on Haykuro's 6.0R1 (Uses new SPL) my memory card, as update. I tried to do it, but it didn't work. Now I am stuck in a JFv1.3 Recovery screen. No matter what I do, I can't get out. Does anyone have any advice? I would appreciate it, because I have been looking online for the past hour to fix it.
Thanks,
Chris

Ok lets get some more information:
Is the recovery screen responsive or frozen?
If it is responsive make sure you have the update.zip on your phone and and do an Alt+W to wipe all data and the Alt+S to install the update.
If it is NOT responsive then your recovery image is corrupted and you need to re-install it.
This will require fastboot, if you search around you can find it, and if you are in windows you will need the usb drivers.
You need to download the JF recovery image which should be called recovery.img
Put it in the same folder that has the fastboot files in it.
Boot the phone into fastboot mode (Camera+Power)
in the terminal(linux) or CMD(windows) type
1. fastboot erase recovery - erases the broken one
2. fastboot flash recovery recovery.img - puts the new one in
3. fastboot reboot - reboots the phone
then you can install the new ROMS if you want.
Post back with any other problems.

[Q] Need a lot of Help!

I was dumb enough to root my phone and try using some custom roms just to get a black notification bar and a couple other things. Thats literally all I wanted. Used Cyan, couldnt get notification bar to change color so went back to original. Anyways thought I'd try flashing the black desire bar or w/e, and failed.
Tries booting up and gets half stuck on the nexus 'X' animation loop. It gets really laggy and studders, never fully completing the loop. So I say eff it after fifteen or so minutes and reboot to recovery. Only it's the stock android recovery, not that clockwork one? So I'm lost, can't flash back to original, and decide i'll just try the factory reset. I have no time for this stuff at this point, and just want my phone so I can talk to people.
Did factory reset/wipe option, and still nothing, stuck on boot. Don't know what to do and I would greatly appreciate some help or advice. Honestly would be so sad if this $500 phone is a paperweight.

Dude relax,
1.First boot to superboot
2.Flash your clockwork (Or any other recovery). DONT REBOOT.
3.Go straight to recovery,
4.Restore your nandroid back up,
--- If you dont have back up then you have to download rom what you want (Stock froyo can be found some where in htc site)
--- Select mass storage option in the recovery and copy there the zip file, then flash it.
Tadaa everything is working again

Read my signature, "unroot / restore your Nexus", and execute. If you have ever updated to FRG83, you might be out of luck and no PASSIMG.ZIP will flash. In this case, you'll need to connect using ADB and run flash_image to flash recovery (most probably you'll get adb shell even if your phone isn't finishing boot - just make sure you run adb shell early enough in the boot). Once you've flashed the recovery, get into it and proceed with a custom ROM. If you flash stock again, your recovery will be lost again. If you didn't set up ADB (enable "USB Debugging" option on your phone) - then you're seriously out of luck. If you have it, but don't know how to use it - spend time reading and understanding "flashing Recovery" guide in the same place from my signature (Wiki), and if you have any further questions along the way - ask here.
You're not booting up because you've screwed up framework-res.apk and possibly some other system files - so you're stuck in boot loop. Need to read and understand what you're doing before you're doing it. It's really not that hard, and not willing to spend enough time understanding things "pays off" if mishaps happen - and they happen.
elkyur said:
Dude relax,
1.First boot to superboot
Tadaa everything is working again
Click to expand...
Click to collapse
He can't boot! Do you read what I read? He's stuck in a bootloop! What boot are you talking about?!
Take your time reading before you rush answering with wrong and incomplete instructions that won't get the OP anywhere. A good portion of mishaps happens because of instructions like these.

This is alot for me to take learn in such quick time to be honest.
I can't even get adb to recognize my phone and i've followed all the steps. My computer makes the noise that something has been plugged in through USB, but nothing else. Under that program to uninstall drivers, I try uninstalling them, but they just stay there, nothing changes.
As for the USB debugging and me being ****ed, I'm pretty sure I left that on.
Maybe it would help me if I told you more about what I know and what I've done.
Literally just followed the step by step instructions from this site theunlockr.com/ to root my phone and use a custom rom.
In the process it made me install PDANet (again probably means nothing, but I don't know).
If adb isn't recognizing my phone, I can't flash using it. Again thank you for the help, as I really am clueless about most stuff like this.
Most of the time when doing anything that could possibly do any harm to a device, I am very cautious. I have hacked several PSP's and didn't think this would be much different...
I read all about the rooting, and knew full well all i wanted to do was get a new notification bar, I didn't really read into the rest as I had no desire or use for that information. Then everything went well, and I learnt how easy it was to go back if I screwed up or didn't like what I had flashed. Not to mention people saying it's near impossible to brick your phone unless your really trying to. Maybe that was just me being ignorant, this could not have happened at a worse time. And I cannot thank you enough for your help thus far.

Thank you for the help. Your guides were very helpful. But unfortunately every step of the way I have run into some sort of problem.
When trying to install the sdk drivers, it won't let me install the amd64 or the i386, but only both of them together. As in it selecting usb_drivers installs (where both of the seperate drivers can be found). I don't know if this is right or not.
When typing in "fastboot devices", "HT036P901361 decives" shows up, but when viewed in USBDeview, 2 of the 3 HT036P901361 drivers show as not connected. The only one that shows as connected is the "vendor specific" one.
Also adb devices, shows nothing.
So again, I'm asking for advice or help.
Edit: So I can reboot fastboot through my computer, but cannot flash anything,
typing in "flashboot flash recovery recovery.img" I get a "cannot load recovery.img".
My recovery.img file is saved on the root of the SD card which is in the phone. Is this the correct way to do it? If so I assume it's still because of the issue stated at the beginning of this post (before edit).
Edit 2: Okay decided to try this
fastboot flash recovery C:\CWrecovery.img (where its located on my hdd), and it starts then says failed infoSignature.

volsey said:
Thank you for the help. Your guides were very helpful. But unfortunately every step of the way I have run into some sort of problem.
1. When trying to install the sdk drivers, it won't let me install the amd64 or the i386, but only both of them together. As in it selecting usb_drivers installs (where both of the seperate drivers can be found). I don't know if this is right or not.
2. When typing in "fastboot devices", "HT036P901361 decives" shows up, but when viewed in USBDeview, 2 of the 3 HT036P901361 drivers show as not connected. The only one that shows as connected is the "vendor specific" one.
3. Also adb devices, shows nothing.
So again, I'm asking for advice or help.
4. Edit: So I can reboot fastboot through my computer, but cannot flash anything,
typing in "flashboot flash recovery recovery.img" I get a "cannot load recovery.img".
My recovery.img file is saved on the root of the SD card which is in the phone. Is this the correct way to do it? If so I assume it's still because of the issue stated at the beginning of this post (before edit).
Edit 2: Okay decided to try this
fastboot flash recovery C:\CWrecovery.img (where its located on my hdd), and it starts then says failed infoSignature.
Click to expand...
Click to collapse
Let's get one thing straight. You need to read more, I guess, because you still don't know the basics - and with the lack of knowledge, it's going to be hard to help you.
Fastboot commands and driver only work when you're booted into bootloader - which is, 3 droids on skateboards on white screen and text menu, get there by booting with trackball or volumedown button pressed.
adb works only when you're booting the OS - which means, you don't touch anything and let the phone boot. Right when boot animation starts, adb should also start.
1. That's correct.
2. Are you booting into bootloader? There should be no other way to view fastboot driver. In that case, DON'T boot to bootloader, just reboot your phone and let it loop, and only then try "adb devices". If it works - use the "flash_image" method to flash recovery.
3. Read (2) above.
4. If your bootloader isn't unlocked (does it show a padlock below Nexus logo when you boot?), you won't be able to flash non-standard recovery through fastboot. You might be able to flash a complete system image through fastboot, though. Download a factory image, FRF91 for example, unzip it, then do "fastboot flash system system.img", "fastboot flash boot boot.img", and reboot.
When you flash something, you should open the Command prompt in the same directory as the file you're trying to flash! Or use full path for the image you're flashing. And it should be on the computer, not on SD card.
If everything fails - just unlock your bootloader and fastboot flash anything you want.

I am using bootloader.
C:\android-sdk-windows\tools>fastboot flash system system.img
sending 'system' (58570 KB)... OKAY [ 8.293s]
writing 'system'... INFOsignature checking...
FAILED (remote: signature verify fail)
finished. total time: 15.014s
That's the error I'm getting everytime.
I got the system.img from hXXp://developer.htc.com/adp.html, I tried looking for FRF91 but could only find megaupload links, and I had exceeded my limit somehow.
As for adb, still getting no devices when I leave it to boot by itself even though I've:
Uninstalled the 3 drivers, unplugged/rebooted, plugged back in/turned back on, and it automatically installs the wrong drivers again too quickly to do anything about it. I've gone into advanced system settings and checked it to never install system drivers automatically. Tried updating drivers, all say they're up to date.
1)So is bootloader not an option for me? Or is there something else I haven't tried? Why am I getting the signature errors?
2)Is it the drivers that are keeping adb from recognizing my phone? How do I fix this?
Any suggestions?

Ok, looks like USB debugging isn't on. In that case, there are exactly 2 options:
1) from here:
http://developer.htc.com/
Download FRG83 image for Nexus, rename to PASSIMG.ZIP, put on the root of your SD card (you can't use the phone for it, so use SD card reader), reboot into bootloader, it'll ask you to flash system image, answer "yes", wait for it to flash. Keep the phone powered. WAIT.
2) if it doesn't work - you're out of luck. "fastboot oem unlock" it is. Then you can flash whatever you want with fastboot.

Help! Stuck at HBOOT, need ideas/help!

Hi,
I bought a faulty Nexus one from ebay, thought I can fix it, as I did buy a faulty desire from ebay and was able to fix it. This time im not so lucky I guess.
So here it is:
The phone is stuck at X when booting normally.
I can access HBoot (But not Hboot USB Plug, because USB debugging is not enabled) and Fastboot USB. I unlocked Hboot. Fastboot in PC recognizes the phone but ADB does not as usb debugging is not enabled.
The phone is not Rooted
Here are my ideas so far:
Get somehow debugging on with some commands (No luck from reshearching in google)
Reflash stock rom with PASSIMG.ZIP in sdcard, but my phone does not recognize the file from my sdcard (I'm pretty certain im doing something wrong or my idea is somehow wrong)
Flash new images through FASTBOOT, but every time Signature check fails (Shipped-roms.com).
Root with superboot, but signature check failed here too.
Flash a recovery, signature check fails.
I will reguraly update my tries
Please suggest correction to my ideas or suggest new ones!
Help will be much appreciated!
I admit it, the phone might be briked, but I want to make sure that I have tried everything before I abandon this project.
And ofcourse I have no Warranty.

What file are you using for passimg.zip? Make sure it's not a zip inside a zip.
What images are you using via the fastboot flash command?
Sent from my Nexus One

You didn't unlock the bootloader, it seems - because if you did, it wouldn't be checking signatures, and you'd be able to flash anything.

First of thanks to both of you for helping.
I'm pretty sure that i do not have zip inside zip and I downloaded them from shipped roms.com -> android -> Passion-> PASSIMG_Google .... .ZIP, (Then renamed it ofcourse) Is there a difference what version of android i use?
The issue with this is, it checks the SD CARD and does not find anything. I have seen from google that the most common issue is that it starts to check the .zip file but then aborts. Does the SDCARD have to be a goldcard (I do have a goldcard but it might be faulty, right?)
I tried fastboot flash PASSIMG_Google.... .ZIP; Fastboot Flashall ( With having boot, recovery, system in my fastboot folder)
Maybe I should try to flash everything the .zip has in it seperately because that succeded for boot, system and recovery but I was too afraid to flash every partitation (Like Radio which seems to be the scariest and the most easiest way to brick phone)
For the third answer, I have ***UNLOCKED*** in bootloader in purple and top on the screen.
Once again thanks and keep suggesting!

Unpack the ZIP and flash each image separately.
Leave the radio as is, if it's updated enough (5.08 or 5.12). In any case, fastboot won't allow you to flash bad radio - and the risk of bricking the phone using fastboot is near 0.

For passimg.zip, you need to download the FRG33 shipped ROM from shipped-roms.com then EXTRACT the zip file that is inside the zip that you downloaded. Rename that file to passimg.zip
For fastboot, flash boot and system seperately.
When you boot the device normally, do you see the lock icon below the four colored x?
Sent from my Nexus One

Okay,
Did it one by one (PASSIMG_Passion_Google_WWE_2.16.1700.1_FRG33_release_signed.zip):
Succeeded:
Boot, Recovery, System and Userdata (that was only 3Kb)
Failed with signature check (Remote:Signature check failed):
Splash1, spcustom,
Did not do:
Radio
I'm going to post more details:
When booting up, it displays the X normally with the unlocking badge on the bottom of the screen and vibrates once. Then it goes black for a second or even less, the same images comes on and then it vibrates 6-7 times.

now that you successfully flashed the stock recovery, cam you boot into it?
Sent from my Nexus One

Nope, it does that what I described on the previous post
Oh and what's more it randomly during no activity being in fastboot vibrates as well for 5 times or so. It does this rarely but it's there

http://forum.xda-developers.com/showthread.php?t=710937

Thanks, Well thats it then for now, just have to figure out what to do now

Sounds like you need to get the PASSIMG.zip method to work, or unlock and flash a new recovery like amon ra, and flash a full rom with sig checks off.

siimplangi said:
Nope, it does that what I described on the previous post
Oh and what's more it randomly during no activity being in fastboot vibrates as well for 5 times or so. It does this rarely but it's there
Click to expand...
Click to collapse
Ok, but can you boot into recovery? In other words, boot into the bootloader and select recovery.

any solution?
efrant said:
Ok, but can you boot into recovery? In other words, boot into the bootloader and select recovery.
Click to expand...
Click to collapse
hi guys.i have exactly same situation.
does anyone have a solution fir this?

kobi_eidelman said:
hi guys.i have exactly same situation.
does anyone have a solution fir this?
Click to expand...
Click to collapse
Did you try all the solutions suggested above (passimg, fastboot flash, etc)? If yes then no I don't think so.

How to get your 2X into fastboot mode

A quirk of the Advent Vega (also Tegra) that allows you to enter fastboot mode also applies on the 2X (Thanks Bumble-Bee for the tip!)
Basically, if you wipe the boot partition (e.g. 'dd if=/dev/zero of=/dev/block/mmcblk0p5') then reboot, the device drops to fastboot.
Handy testing feature for devs.
P

That sounds great!
Does fastboot boot work? Does fastboot flash work? Any other lockdowns there?

maxisma said:
That sounds great!
Does fastboot boot work? Does fastboot flash work? Any other lockdowns there?
Click to expand...
Click to collapse
Fastboot boot did, didn't try anything else yet!
P

Fastboot flash works, ish.
I could flash recovery, but not boot. What would be nice is a radio in .img format so I don't have to backup and restore the bastard thing when a new one is out.

Ahh this would be so awsome.. since i Smartflash can't detect my P990
(so i can't flash the latest basebands or revert them)
Gief Radio in .img format !

Would anyone Know how to get the radio as .img ?

Would this work on the T-Mobile LG G2X?

Good question.
I expect the boot partition is different, so don't blindly follow the command here.

Rusty! said:
Good question.
I expect the boot partition is different, so don't blindly follow the command here.
Click to expand...
Click to collapse
I did follow the command blindly with my P990, but no boot for me. Luckily there's an escape with the NVflash stock ROM.

It's fine on the P990, it's meant to 'not' boot, it's not broken at that stage, it's in fastboot. You can fastboot boot your way out of it.

Is this a safe option to try on my v10D? Fastboot decreases boot time by how much really?

That's not what fastboot means, to be honest, this isn't going to be for you

Hey All,
I was trying to install GingerStreak 2.4.4 from GingerStreak 2.4.3.
http://forum.xda-developers.com/show....php?t=1333010
According to the instructions, I flashed
amss.mbn - http://mirror2.streakdroid.com/amss.mbn
and
dsp1.mbn - http://mirror2.streakdroid.com/dsp1.mbn
(got both the files from the first link above)
Then when I tried to reboot into Bootloader (Power+Vol Up+Vol Down) but nothing happens apart from the Dell logo being displayed.
I try to boot normally, still stuck at the Dell logo. The phone never even reaches the boot animation.
I try to go boot into fastboot (power+camera key)mode, but the phone never even boots. The screen stays off, so do the LED lights.
I figured out that the files downloaded above were incomplete(due to slow speed Chrome showed incomplete files as download complete).
amss downloaded: 111KB. Actual Size: 15.41MB
DSP1 Downloaded: 250KB. Actual Size: 8.94MB
So, I flashed the wrong files.
Now, I guess, the phone is bricked big time.
I need big time to get into fastboot mode (to flash the correct files) or anyhow get my phone working.
Guys, need help. Please help me out and get this issue sorted out.

You should maybe consider the Streak forum...

Sorry, my bad. I just searched for my problem an found this thread. Poured out all my worried without bothering to check on the device name.
Thanks anyhow!

Stuck on HTC boot screen

Hey,
I attempted installing Android Revolution on my HTC One - but it rebooted the phone for some strange reason during the install - i am now stuck on the HTC white boot screen - it was looping but i cleared the cache. I can still enter fastboot mode but don't know how to get the phone back to a state where i can actually get past the boot screen.
The phone is a 3 UK one.
Any help would be greatly appreciated.
Zack.

can you try flashing the rom again or want it get that far?

ant78 said:
can you try flashing the rom again or want it get that far?
Click to expand...
Click to collapse
To be honest i am pretty new at this. I can access the recovery menu and enable fastboot and also access Clockworkmod T. Unsure where i am going from here.
Currently as it stands the phone will not get past the white HTC loading screen.

Right, i have an original ROM dump (system.img, boot.img, recovery.img) - I presume this would be the best way forward? I issued the following:
fastboot flash recovery recovery.img OK
fastboot flash boot boot.img OK
fastboot flash system system.img > load_file: could not allocate 1946156032 bytes, error: cannot load system.img, not enough space.
Can anyone help me? My phone is just stuck on the HTC boot screen