Database Develop

ROM doesn't start, recovery fails, fastboot not recognized by PC

Today I tried to change ROM in my G1. With that I also wanted to change SPL and recovery. It was my first conact with flashing that phone. I flashed Samsung i7500 before, so I have some Android experience.
Recovery and SPL went OK. When I was flashing ROM, something has gone wrong, so I decided to restore nandroid backup I made before flashing new ROM. When I restored backup, system didn't load. It stops on "Android" text or on black screen. Recovery also got lost (I don't know how) - now I can see only picture with triangle and "!" sign.
First thought I have was to use fastboot to flash new recovery and have it working. But there is my problem - when I enter fastboot mode, PC doesn't see any new device. There is no difference in device manager when phone is connected or not. When I turn phone on normally (so system's stops loading on Android text), it's recognized by PC.
Have anybody had such problem? What should I do to restore recovery or flash working rom?

What ROM u trying to flash? Some ROMs need some base files. You can even install a new Recovry Image through Recovery Console. Thats what I did

OK, What SPL you have right now...
Once you flash new SPL, old nandroid might not work properly as the partition layout has been changed....
Let us know the SPL you have now, sometimes if the phone is not getting recognized..then you have some old driver installed, try to see if that's the issue...
ms93 said:
Today I tried to change ROM in my G1. With that I also wanted to change SPL and recovery. It was my first conact with flashing that phone. I flashed Samsung i7500 before, so I have some Android experience.
Recovery and SPL went OK. When I was flashing ROM, something has gone wrong, so I decided to restore nandroid backup I made before flashing new ROM. When I restored backup, system didn't load. It stops on "Android" text or on black screen. Recovery also got lost (I don't know how) - now I can see only picture with triangle and "!" sign.
First thought I have was to use fastboot to flash new recovery and have it working. But there is my problem - when I enter fastboot mode, PC doesn't see any new device. There is no difference in device manager when phone is connected or not. When I turn phone on normally (so system's stops loading on Android text), it's recognized by PC.
Have anybody had such problem? What should I do to restore recovery or flash working rom?
Click to expand...
Click to collapse

I have installed haykuro SPL as I remember right.
I tried to update SDK and its USB drivers, but no result.
I remember also, that "USB debugging" wasn't on - maybe that's why phone in fastboot isn't recognized on PC?
To be clear: when I plug USB cable in fastboot mode, PC doesn't show that there is some new device. It acts like no device was connected to it.

There are other new and safe method to achieve the same or more then what you are trying to achieve with Haykuro SPL...see here..Custom MTD
But anyhow you are stuck with it...when you say Phone is not getting recognized..try restarting the phone in fastboot mode while connected to PC...when you are pressing back button are you getting fastboot..
I am not a good person to suggest something on this...If I would have been in your place I would have flashed DREAMIMG.nbh file and would have started from start....but wait till somebody better will tell you how to recover the device....
ms93 said:
I have installed haykuro SPL as I remember right.
I tried to update SDK and its USB drivers, but no result.
I remember also, that "USB debugging" wasn't on - maybe that's why phone in fastboot isn't recognized on PC?
To be clear: when I plug USB cable in fastboot mode, PC doesn't show that there is some new device. It acts like no device was connected to it.
Click to expand...
Click to collapse

G1sanju, I don't know what to say!
You saved my phone
Flashing DREAMIMG.nbh helped, phone has booted

OK, I have a new problem now.
Recovery is still not working - I have Android 1.0 in phone.
Fastboot is still not recognized by PC, so I can't flash it. I don't have root, so I can't flash recovery by terminal - is there any Android 1.0 root instruction?
Or maybe DREAIMG.nbh of 1.5 or 1.6 ROM?
EDIT:
Now everything works, I flashed recovery using telnet.

DREAMIMG.nbh is an default image for G1, so it remove root access and leave the phone with the stock image...now you have 1.x radio and stock SPL...flashing haykuro SPL right now can brick your phone....
unlocker.com has some good guide to get the root access if you are looking for it....
Do not flash the Haykuro SPL or DangerSPL......That's of no use now....also there are chances that it can brick your phone....
Use Safe SPL...1.33.2003 those are full engineering SPL with fastboot access....
use CustomMTD to get the increase size as mentioned in my post above...
ms93 said:
OK, I have a new problem now.
Recovery is still not working - I have Android 1.0 in phone.
Fastboot is still not recognized by PC, so I can't flash it. I don't have root, so I can't flash recovery by terminal - is there any Android 1.0 root instruction?
Or maybe DREAIMG.nbh of 1.5 or 1.6 ROM?
EDIT:
Now everything works, I flashed recovery using telnet.
Click to expand...
Click to collapse

I installed recovery via telnet, then changed radio, installed CustomMTD and ROM. All working fine.

Its great that you have used customMTD rather then Haykuro SPL...this is safe method....I just warned you because that's a very common way to brick the phone....flashing NBH and then installing SPL assuming you have the correct radio is a very common way of bricking the phone...
Also if you are playing with SPL and radio's then its advisable to erase the recovery first...then do the install from fastboot and then reinstall recovery...
ms93 said:
I installed recovery via telnet, then changed radio, installed CustomMTD and ROM. All working fine.
Click to expand...
Click to collapse

[Q] Fastboot.

Tried to install Cyanogen 6.1... It failed.
From there the device booted up normally on a fresh start, but I tried to recover my backup and that is where everything got all messed up.
Im stuck on the G1 screen.
Ive gotten it to the fastboot mode and Im downloading what I think I need to get my phone working again. Ive downloaded the Andriod 1.6 image from the HTC website. Do I need the recovery? I just want 1.6 until I have time to try and get Cyanogen installed.
Im currently installing JDK for the Andriod SDK.
Am I headed in the right direction?
I was using ROM Manager with Clockwork Mod. My old ROM was Super E... Not sure what version, but it was Andriod 2.1

What radio/spl do u have?

johnson8cyl said:
What radio/spl do u have?
Click to expand...
Click to collapse
2.22.19.26I

Tbry said:
2.22.19.26I
Click to expand...
Click to collapse
And spl? Do u have and eng spl? (S-off). If so u could fastboot erase your system and try to flash the rom through recovery. And fastboot flash a recovery of your choice first. Have u tried going on ezterry's thread with the new radio/spl and going that route?

Not sure what the version of the SPL is, but I know it is off. I'll check his thread out and give it a try. I might end up finding someone who actually knows what they are doing, or buying the Nexus S.

Ok. If u follow his thread exactly and fastboot flash the radio/recovery/spl u should end up with everything as described in the thread and be able to move on with cm6 with appropriate kernel. Alternatively u could boot into fastboot and open up your terminal on your computer and type in code to fastboot recovery of your choice (after it's download and put in sdk/tools folder on your PC) he has amonra link in his thread for download . Then type fastboot erase system -w (hit enter). When it's done type fastboot erase boot (hit enter). Then power down. Power back into recovery with the rom on your sdcard and flash away.

That is actually what I'm trying to do. Its just about my only option at this point.
Im having problems getting everything set up correctly though.

What are u having problems setting up?

I installed Andriod SDK, seems to be working.
Downloaded the drivers, which seems to have stopped my computer from seeing the phone.
I downloaded the Fastboot.exe, tried to run it but it cannot find ADB.dll ( Pretty sure thats what it was.)
I was basically following the steps on the cyanogen wiki.
When I have some time, I will try the Fastboot for noobs guide.

I think I followed a guide in androiddevelopers.com or something like that. If I find it again ill post a link. I don't think I ran a fastboot exe file though. Just have it in my androidsdk/tools folder. Added the variable to my paths and was good to go. Not at my PC currently though.
Edit: developer.android.com/sdk/
I believe is what I followed

http://forum.xda-developers.com/showthread.php?t=532719
Following this for fastboot.
I cannot update anything. Home + power doesnt do anything.
Only thing I can access is fastboot mode.
Fortunately my radio is up to date, so I assume my SPL is as well.
Going to attempt to try the fastboot step, once I can get the SDK working correctly
edit: I knew if I spent enough time working at it that I'd get it working.
Only problem now is getting my device to be listed.
Edit2: at first when I entered fastboot mode, I would get the "Add new hardware" for the device "Andriod 1.0"
It now says "andriod bootloader interface"
I feel like I'm so close. I'm going to keep playing with it, but what can I do to get my device listed when I type the command "Fastboot devices"?
Edit 3: Awesome. I got fastboot to work and my phone is recognized. Only problem now is getting my SD card reader to work so I can put the proper files on
Final edit: MY phone is killing SD cards for some reason. Don't know what to do
Got the SD cards to work, for some reason though, some of the commands are not working. When I type fastboot shell, I just get the usage doc.
When I do fastboot update, I get the following: error: failed to load 'update.zip'

What are u trying to do in fastboot?
Sent from my T-Mobile myTouch 3G using XDA App

Well, I fixed my phone. Back to its original state.
I guess my only question at this point my only question is if I switch to Cyanogen 6.1, will it be less buggy than my Super E ROM?
For anyone wondering, Holding home + end for about 25 seconds is what I did. From there I just went to nandriod and tried to recover the same backup that gave me the problem.

I would say no. It will not be less buggy. U can always flash and try different roms though for experiment sake. Glad u got it back up
Sent from my T-Mobile myTouch 3G using XDA App

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.

[Q] Htc one Stuck on hboot screen when was flashing a custom rom

Hi i will put everything out so it can be answered without going back and forth : I was installing Trickdroid 10.3 and was about 95% done then it crashed I erased the wrong thing and now am stuck on hboot/fastboot screen everything I seleect either shuts down phone and restarts it back in same place or does nothing helpful. Usb can't be seen and recovery will do same flash off the right back to same screen s-on was s-off but is now back to on hboot is 1.44 radio 4a 14.3250.13 phone was rooted and bootloader was unlocked my device is TAMPERD and says UNLOCKED HAHAHA had to say T&U was funny when i got it saying it still is, but says ss-on... I have been looking and readin for a week and now it came down to taken suggestistions and hopefully we can get it fixed cause i dont want to end up with an electric bath toy for the babys!!!:crying:

DrzNikki said:
Hi i will put everything out so it can be answered without going back and forth : I was installing Trickdroid 10.3 and was about 95% done then it crashed I erased the wrong thing and now am stuck on hboot/fastboot screen everything I seleect either shuts down phone and restarts it back in same place or does nothing helpful. Usb can't be seen and recovery will do same flash off the right back to same screen s-on was s-off but is now back to on hboot is 1.44 radio 4a 14.3250.13 phone was rooted and bootloader was unlocked my device is TAMPERD and says UNLOCKED HAHAHA had to say T&U was funny when i got it saying it still is, but says ss-on... I have been looking and readin for a week and now it came down to taken suggestistions and hopefully we can get it fixed cause i dont want to end up with an electric bath toy for the babys!!!:crying:
Click to expand...
Click to collapse
Can you see the device in ADB mode?

dgtiii said:
Can you see the device in ADB mode?
Click to expand...
Click to collapse
No I can't......I also forgot I am running windows 8, when I use the adb device nothing, any adb codes, or serial numbers don't show up. No matter what is done recovery is not working. I have an s4, it too was in the same state, I was able to download ROM to external SD card, rebooted into recovery mode, and re-flash ROM. That is almost fixed...
If I get a female to female USB and mount the USB somehow will it give it the same effect? If so any suggestions? Or any other suggestions to help me get through this?

DrzNikki said:
No I can't......I also forgot I am running windows 8, when I use the adb device nothing, any adb codes, or serial numbers don't show up. No matter what is done recovery is not working. I have an s4, it too was in the same state, I was able to download ROM to external SD card, rebooted into recovery mode, and re-flash ROM. That is almost fixed...
If I get a female to female USB and mount the USB somehow will it give it the same effect? If so any suggestions? Or any other suggestions to help me get through this?
Click to expand...
Click to collapse
Yes, that would be my advice. Go to a site like Amazon, and search for a "micro USB OTG cable". They are inexpensive, and will allow you to use a flash drive with the phone in recovery. Then download a rom onto a flash drive, and install from there.

dgtiii said:
Yes, that would be my advice. Go to a site like Amazon, and search for a "micro USB OTG cable". They are inexpensive, and will allow you to use a flash drive with the phone in recovery. Then download a rom onto a flash drive, and install from there.
Click to expand...
Click to collapse
Thank you for replying!!! How would I get into recovery with no access to the phone? Is there a manual script to get into it? Also I can upload a picture of the only part of the phone I can see if that would help?

DrzNikki said:
Thank you for replying!!! How would I get into recovery with no access to the phone? Is there a manual script to get into it? Also I can upload a picture of the only part of the phone I can see if that would help?
Click to expand...
Click to collapse
Hold down the power button while holding down the volume down button at the same time until the phone reboots. If it does not, use the same procedure while holding the proximity sensor under a bright light (sounds weird but it works!). Phone will boot into bootloader mode, select recovery, and you will be good to go. I'll take a look if you upload a pic, sure

I had something similar, but managed to get in through ABD (windows 7), but also remembering that I was stuck in a boot loop, i wiped cache , re tried and rom loaded and booted. Have a read up on ABD in windows 8, see if there's anthing your missing or specific modded files needed for windows 8 and ADB running, just my opinion

So I tried to unlock via EDL...

...and I thought it had worked but as it turns out, it did not. I found out it did not when I tried to root to which the phone proceeded to tell me it was lock.
Now, when I go into Recovery Mode, the phone does not come up in ADB even when trying to unlock after using the ASUS unlocker tool... Is the ADB bridge fried forever? How do I reinstate it to be able to root? I don't mind wiping, I just want to recover the possibility to root. Any way to do that? God I feel dumb right now...
Edit: I've gotten ADB to recognize the phone in Recovery Mode by installing the exact Manufacturer and Model ADB drivers but the second I get into Fastboot mode, it's like the side USB-C suddenly becomes non-existent, same goes for the bottom one. Feels like a kill.switch from ASUS to me :/
Edit 2: Is there a way to flash while in Recovery? Or in normal OS operations? (sounds like a bad idea but I'm out of ideas as of now)

So neither of the two USB ports in the phone seem to work for you in bootloader mode?

dennis96411 said:
So neither of the two USB ports in the phone seem to work for you in bootloader mode?
Click to expand...
Click to collapse
Exactly, the bootloader is also unlocked after using ASUS's tool .apk, I am on 1910.44 WW, I tried different ADB's while in Windows, tried to copy DeviceID, it all works when in normal boot OR in recovery mode but the second I am in fastboot mode, both USB's stop working. As if ASUS locked the access when I mistakenly tried to gain root while the bootloader was locked. Maybe if I could lock it back but that would require me being in fastboot afaik.
Can I lock it back while in recovery? If so, what would be the prompt?

I would be very careful about locking the bootloader at this point. I heard it can cause a brick if the planets aren't aligned correctly.
Jokes aside, does device manager refresh itself when you plug or unplug the phone in fastboot mode? That would indicate it saw something from the phone.

dennis96411 said:
I would be very careful about locking the bootloader at this point. I heard it can cause a brick if the planets aren't aligned correctly.
Jokes aside, does device manager refresh itself when you plug or unplug the phone in fastboot mode? That would indicate it saw something from the phone.
Click to expand...
Click to collapse
Sadly no, tried 3 different computers, a plethora of cables, different USB ports. It's like the Fastboot killed the function altogether so as of now, I have yet to find a way to get the phone recognized while in fastboot.

WhyKlwd said:
Sadly no, tried 3 different computers, a plethora of cables, different USB ports. It's like the Fastboot killed the function altogether so as of now, I have yet to find a way to get the phone recognized while in fastboot.
Click to expand...
Click to collapse
Is there an option to apply a full OTA from the stock recovery?

dennis96411 said:
Is there an option to apply a full OTA from the stock recovery?
Click to expand...
Click to collapse
Before anything, thanks for helping, it's greatly appreciated!
So, no sadly, when I get in Recovery Mode my options are:
Reboot system now
Reboot to bootloader
Wipe data/factory reset
Power off
As anyone would, I tried kicking into bootloader from recovery hoping that it would trigger something different to give me fastboot but to no avail, I wiped a couple of times as well, that didn't pan out.
Edit: I feel like my best chance at this point is when ASUS releases a new WW firmware update, that it HOPEFULLY brings Fastboot Mode to it's original value... But according to a thread somewhere on XDA, it does not install a full partitioned recovery so I'm not having my hopes up...
The other thing would be to butcher a USB-C cable and see if I get a response when connected on the orange USB-C but that's also a risk to take. So that doesn't work, that USB-C gets no response whatsoever.

What firmware version are you on? You could try grabbing the stock firmware zip of the firmware you're on now from https://www.asus.com/Phone/ROG-Phone-II/HelpDesk_Download/, and increase the firmware version in the zip name - for example, if you're on the latest .44 build now, change the .44 in the zip name to .45. Then simply push it to the root of your internal storage, and reboot. After boot you should get a message that a system update file has been found, and that you can install it.
I don't know if this will fix your problem, but it should reflash the stock partitions. And yes, it's true that it far from flashes all partitions, but it's worth a try at least.

HomerSp said:
What firmware version are you on? You could try grabbing the stock firmware zip of the firmware you're on now from https://www.asus.com/Phone/ROG-Phone-II/HelpDesk_Download/, and increase the firmware version in the zip name - for example, if you're on the latest .44 build now, change the .44 in the zip name to .45. Then simply push it to the root of your internal storage, and reboot. After boot you should get a message that a system update file has been found, and that you can install it.
I don't know if this will fix your problem, but it should reflash the stock partitions. And yes, it's true that it far from flashes all partitions, but it's worth a try at least.
Click to expand...
Click to collapse
I did put the stock firmware but I hadn't thought of changing the name to "force" the phone to try and update! Sadly, when it reached 100%, it said install failed and while trying fastboot mode, it still didn't restore ADB but that was brilliant and definitely worth the try. Thanks for your suggestion, here's hoping the next legit firmware will do it!
EDIT: AND YET IT DID WORK!!! That must have fixed it after all... I unplugged, replugged while in bootloader and finally, that USB chime! T-T
Thanks both of you for your suggestions, 3 brains work better than one!

WhyKlwd said:
I did put the stock firmware but I hadn't thought of changing the name to "force" the phone to try and update! Sadly, when it reached 100%, it said install failed and while trying fastboot mode, it still didn't restore ADB but that was brilliant and definitely worth the try. Thanks for your suggestion, here's hoping the next legit firmware will do it!
EDIT: AND YET IT DID WORK!!! That must have fixed it after all... I unplugged, replugged while in bootloader and finally, that USB chime! T-T
Thanks both of you for your suggestions, 3 brains work better than one!
Click to expand...
Click to collapse
Nice, glad to see it worked! I tried it myself and it also said update failed, but it had flashed, so I think the error message may just be because the firmware version doesn't change.
I'm assuming fastboot works now then? Do keep in mind that you'll need the abl, xbl and xbl_config images from the edl unlock thread to be able to actually unlock the bootloader without using the Asus tool.

HomerSp said:
Nice, glad to see it worked! I tried it myself and it also said update failed, but it had flashed, so I think the error message may just be because the firmware version doesn't change.
I'm assuming fastboot works now then? Do keep in mind that you'll need the abl, xbl and xbl_config images from the edl unlock thread to be able to actually unlock the bootloader without using the Asus tool.
Click to expand...
Click to collapse
Yeah it works, or at least it did long enough for me to be able to root. I haven't tried it since but I would assume that it fixed it, tomorrow I'll most likely do a RAW flash to fix all potential risks as well as try the latest CN firmware. EDL never worked, that's what got me in that situation in the first place... well that and me not paying full attention.