Hi Guy's,
i got a small issue, one of my co workers tried to root his phone at home and got busted. I guess he tried the 1 click solution and it didnt work. he said the phone got stuck in an loop during back up.
When i boot all i get is a Triangle and a phone. I am trying to root the phone using the sdk but when i folow the guide it brings me to using the flashrec method. That wont work for me cause i dont seem to have any os!
Can someone help me out on getting this thing out of the mud its a rogers G1 with Dream PVT 32b with Hboot -1.33.0010
Thanks for the help!
This is not Development related. ALL questions that need answers (that are not development related) go in the Q&A section. Moved.
Okay he just told me he tried using the flasrec method and it got stuck looping during the backup. I guess the image has been erased
Is it possible to change the spl using the SDK and fastboot?
fastboot flash recovery recovery.img (only works if root was successful or reflashing original recovery)
is it possible he tried to flash the non-rogers recovery?
try flashing RA-Dream-v1.5.2R.img (R being the rogers version)
i still get downloading 'boot.img'... FAILED (remote: not allow)
Is it possible to root the phone Without using the flashrec? using the Fastboot/sdk to flash the bootloader to 2005? i cant seem to find any info on this... Or Since the root failed and there is no recovery is it possible to put back the image files to the phone so it can boot into the os? or do i absolutely need a recovery for this?
Close this i figured it out went into boot flas and wiped now its booted 1.5
thanks
Related
so i just installed the factory 2.3.3 gingerbread OTA update onto my nexus one witch was one click rooted locked bootloader and it downloaded and installed fine but now i want to root again most likely unlock bootloader way but i cant get into recovery now ? i boot into bootloader mode (hold trackball while turn on phone ) i hit bootloader then recovery and i get the damn green android with the exclamation mark??? anyone no why i cant get into recovery i searched for last hour cant find .......
nexus one not rooted
locked bootloader
OTA gingerbread 2.3.3
s-on
hboot-0.35.0017
AMOLED screen
radio - 5.08.00.04
drawde40599 said:
so i just installed the factory 2.3.3 gingerbread OTA update onto my nexus one witch was one click rooted locked bootloader and it downloaded and installed fine but now i want to root again most likely unlock bootloader way but i cant get into recovery now ? i boot into bootloader mode (hold trackball while turn on phone ) i hit bootloader then recovery and i get the damn green android with the exclamation mark??? anyone no why i cant get into recovery i searched for last hour cant find .......
nexus one not rooted
locked bootloader
OTA gingerbread 2.3.3
s-on
hboot-0.35.0017
AMOLED screen
radio - 5.08.00.04
Click to expand...
Click to collapse
Use fastboot to re-flash recovery img
lcchan1 said:
Use fastboot to re-flash recovery img
Click to expand...
Click to collapse
how exactly do i do that ? fastboot not detecting my device and i thought i read somewhere its because ( S-on ) ?
drawde40599 said:
how exactly do i do that ? fastboot not detecting my device and i thought i read somewhere its because ( S-on ) ?
Click to expand...
Click to collapse
download clockwork recovery from the app store.
Flash its recovery, then boot into recovery after a successful flash.
Out of curiosity, why did you install a non-rooted version of 2.3.3.?
You can get into recovery... what you're seeing is the front of the stock one. Hold volume+ and hit power.
The only way to get root on 2.3.3 currently is to unlock the bootloader and use fastboot. Being S-ON is nothing to do with it, 99% of N1s are.
Rusty! said:
You can get into recovery... what you're seeing is the front of the stock one. Hold volume+ and hit power.
The only way to get root on 2.3.3 currently is to unlock the bootloader and use fastboot. Being S-ON is nothing to do with it, 99% of N1s are.
Click to expand...
Click to collapse
HELL YA !! thank u much
Thread moved to Q&A, a sub-forum dedicated exclusively for questions like these. Please post all further questions here. Do not post new question threads in development, as you are not doing any even remotely related to Android development. That said, I'm glad you were able to figure out your issue.
Downloading clockworkmod will not work. He is not rooted so he can't flash the recovery with it.
Sent from my Nexus One using XDA App
This happened to me 2 days ago (word by word)!!
From Amon Recovery's page, this is what the problem is:
"Make sure that init.rc isn't calling any install-recovery.sh script, otherwise you'll boot back to stock recovery (exclamation mark with a little Android). More info on this here"
Here: http://forum.xda-developers.com/showpost.php?p=10467058&postcount=1638
My problem was even more complicated because I tried flashing froyo without a wipe so my phone started going into boot loop!
Thanks to danger-rat's reply, I was able to get into recovery at least once and then everything came back under control. He said "Recovery is only restored when you boot into system, so the idea is that you flash recovery, and go straight into it via the on phone menu, and then install what you need to..."
Here's my thread:
http://forum.xda-developers.com/showthread.php?t=980577
edit: I just realized that you are not able to fastboot either? I was able fastboot and flash recovery onto my phone and then without turning the phone off - I was able to go into recovery straight after flashing amon_recovery.img
passimg back to an earlier version of Android, root, then install a pre-rooted GB...
If you get the "main version is older" error, you're out of luck and your only option is to unlock the bootloader or wait for a new method to be found...
Sent from my Nexus One using XDA App
I want to flash a new radio and kernel to my G1 that is running CM6. My signal is atrocious and I get a few random oddities each day.
I have tried the recovery flash for the radio at least 6 times now in various ways following various guides and every time I do it it crashes my phone and I end up flashing the image, rooting, etc, to get back to CM6. it takes me over an hour to get back to normal and it just plain sucks!
So my question is..... Can I use fastboot flash to flash the image files for the radio and the kernel without being on the special Hboot 1.33.0013d and such?
I was planning to use the instructions from the ezterry kernel page and just want to check that I wont bork up my phone. I seem to recall that the fastboot flash bypasses all the need for FR-remove and such but want a second opinion before I take the dive this way.
Not trying to drive you away from CM 6, but have you tested other ROM to see if it has the same problem or similar.
I personally myself could not get CM6 to work properly on my G1 back when I was trying to use it.
I couldn't get the radio to recovery flash even on the stock ROM after rooting.
I guess I could try a different ROM.
I just now have proven to myself that i cant flash the EzTerry kernel from Rom Manager and clockwork recovery as I am in the midst of yet another image flash, re-root, and such after it wouldn't go past the reboot screen afterwards
This phone is just an extra toy but I am determined to figure it out.
I suppose I will just try the radio.img flash from fastboot tonight when I get home.
As long as I dont brick it I can always start over from scratch.
so I copied the image I want to flash onto the root of my sd card
did the camera+power boot
pressed the back key and I am at the screen with the red fastboot usb box
I plug into the computer (adb already installed and working fine) and go to the command prompt and type
fastboot flash hboot hboot-1.33.0013d.img
the screen says error: cannot load 'hboot-1.33.0013d.img'
Did I put the image file in the wrong place?
Edit: I put it in the root of the computers c: drive and typed
fastboot flash hboot c:\hboot-1.33.0013d.img
seems to have worked.
FireRaider said:
so I copied the image I want to flash onto the root of my sd card
did the camera+power boot
pressed the back key and I am at the screen with the red fastboot usb box
I plug into the computer (adb already installed and working fine) and go to the command prompt and type
fastboot flash hboot hboot-1.33.0013d.img
the screen says error: cannot load 'hboot-1.33.0013d.img'
Did I put the image file in the wrong place?
Edit: I put it in the root of the computers c: drive and typed
fastboot flash hboot c:\hboot-1.33.0013d.img
seems to have worked.
Click to expand...
Click to collapse
do the same thing with the radio and recovery
maximo360 said:
do the same thing with the radio and recovery
Click to expand...
Click to collapse
I got the recoveryand the hboot to flash but damned if I can get any radio to flash.
I get
writing 'radio'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
this is with both version of the radio downloaded from the links in the EzTerry thread
What in the world am I doing wrong that I cannot flash a new radio?
installed the spoofSPL... didnt help
edit: Started over again from scratch, rooted, flashed RA recovery, dangerSPL, then fastbooted and managed to install the hboot and the new radio. I guess CM6 hates the newer radios.
edit: Pretty sure CM6 does hate the radio because now its hung up on the install screen.
off to do more research.
People ... you should read before flashing around.
Ok, let me try to help.
1) As long as you have a fastboot enabled SPL, there is no need to 're-root'. Boot into hboot and flash the things you want.
2) Going to 1.33.0013d you *lose* most of your fastboot capabilities, e.g. flashing a new SPL/radio/recovery is no longer working. The only chance is to flash a signed nbh-file (e.g. fully signed rom)
I suggest you to read Terry' thread carefully (a link is in my signature) and then to retry ...
Btw: If you have installed the "new" radio/spl combo you need an adopted kernel, too, otherwise you will get bootloops.
Sent from my Gingerbread on Dream using XDA App
AndDiSa said:
People ... you should read before flashing around.
Ok, let me try to help.
1) As long as you have a fastboot enabled SPL, there is no need to 're-root'. Boot into hboot and flash the things you want.
2) Going to 1.33.0013d you *lose* most of your fastboot capabilities, e.g. flashing a new SPL/radio/recovery is no longer working. The only chance is to flash a signed nbh-file (e.g. fully signed rom)
I suggest you to read Terry' thread carefully (a link is in my signature) and then to retry ...
Btw: If you have installed the "new" radio/spl combo you need an adopted kernel, too, otherwise you will get bootloops.
Sent from my Gingerbread on Dream using XDA App
Click to expand...
Click to collapse
I managed to get everything work and am running CM6.1+2708 and 0013d with the .27 radio.
Why do we go to the 0013d if it screws up the fastboot? I notice in your signature you are running it also?
And say I want to flash a different rom now? I can only do it from RA recovery, Correct?
But as it stands now I ought to be able to experiment around with the other radio and other roms using recovery without any more issues? Or do they need to have certain parameters?
Once rooted, (to my knowledge) you do not required to re-root it again.
You can use RA Recovery to flash other ROMs with out having to re-root. (as to what I was told) And I recommend RA Recovery instead of ROM Manager/ClockMod Recovery (bad experience with it personnaly).
So as long as the ROM that you want to try is compatible with your current SPL/radio. You should be fine.
GSM SLCD Nexus One
Hboot 0.35.0017
S-On
Locked Bootloader
Somehow I managed to get stuck here, I'm still not sure how. If I had to guess it would be the bootmanager application, although I haven't used it since this morning.
I really would like to keep the bootloader locked if at all possible. The phone was rooted before.
I figured I could just flash a recovery that's signed (hboot signature verification fails on cwm and amon_ra, via fastboot) but I can't for the life of me find one.
In the bootloader, I click on recovery, shows the n1 splashscreen briefly, then sends me to fastboot.
Thanks for the help.
You won't be able to put a custom recovery on there without unlocking the bootloader or reseting your phone. If you are really wanting to keep the bootloader intact, the easiest thing would be to do the PASSIMG method. Have a look in the wiki and it will explain everything to you. Then once you get back into Android, root the phone before it updates to Gingerbread and then install ROM Manager to get your custom recovery back.
I actually just ended up unlocking it and using fastboot to put a new recovery on it. I didn't know about the PASSIMG method. Thanks for your response anyway though.
Hi
Due to a bootloop on my Inc S running Cyanogen 7 i wanted to flash a new recovery and a new os. But when I try to flash the image via fastboot, the message "FAILED (remote: Image update error)" appears. It's also impossible to erase partitions via fastboot due to an "erasing error". I tried to flash with adb, but the device isn't listed in adb devices .
I also tried to update HBOOT from version 6.13.1002 to 2.00.0000 using a PG32IMG.zip on the sd card, but it hangs on the "Dont power off" dialog.
I'd be happy if someone could help me out...
Thanks and greez
visosilver
Visosilver said:
Hi
Due to a bootloop on my Inc S running Cyanogen 7 i wanted to flash a new recovery and a new os. But when I try to flash the image via fastboot, the message "FAILED (remote: Image update error)" appears. It's also impossible to erase partitions via fastboot due to an "erasing error". I tried to flash with adb, but the device isn't listed in adb devices .
I also tried to update HBOOT from version 6.13.1002 to 2.00.0000 using a PG32IMG.zip on the sd card, but it hangs on the "Dont power off" dialog.
I'd be happy if someone could help me out...
Thanks and greez
visosilver
Click to expand...
Click to collapse
Since you have Rvolutionary S-Off, you cannot simply overwrite the HBOOT with stock 2.00.0000. You need to follow this procedure:
http://forum.xda-developers.com/showpost.php?p=15732727&postcount=14
Then you would able to use the PG32IMG.zip.
I actually dont wan't to get S-ON, but do you think that it will be possible to flash a new recovery and rom after updating the HBOOT?
If your bricked than its definately worth trying. Sounds to me like your internal memory has some kind of error on it if you can't wipe. And it might not be hung when you try to flash the pg32 as it as it says don't power off and you did anyway you might own an unbrickable phone.
Sent from my Incredible S using xda premium
Visosilver said:
I actually dont wan't to get S-ON, but do you think that it will be possible to flash a new recovery and rom after updating the HBOOT?
Click to expand...
Click to collapse
That depends on if you can update the HBOOT. In order to make your current HBOOT 6.13.1001 overwritable, you need to follow the procedure steps 1-2d in the procedure I posted.
If that doesn't work, then there is no sense trying to go on. As the previous posted suggested there is something wrong with your phone's partitions.
If it does work, then I would defintely run a stock RUU to get back to a known working state.
thank you for your answers, i just tried the procedure.
Since the first link is down i wasn't able to install the RUU, so i just tried the second step but i got again the "remote: image update error"
Does this mean my phone is definitely bricked?
Visosilver said:
thank you for your answers, i just tried the procedure.
Since the first link is down i wasn't able to install the RUU, so i just tried the second step but i got again the "remote: image update error"
Does this mean my phone is definitely bricked?
Click to expand...
Click to collapse
Yes it appears that you are unable to flash any of the partitions on your phone, including the HBOOT partition.
Do you have another PC and USB cable to try just to rule out that those aren't causing an issue? If you do, make sure you have the latest HTC drivers installed.
didn't work but thanks for your help anyway
greez visosilver
Visosilver said:
didn't work but thanks for your help anyway
greez visosilver
Click to expand...
Click to collapse
There's no harm in trying a ruu
Sent from my Incredible S using xda premium
try fastboot boot recovery.img
where recovery.img is the recovery image CWM or 4EXT
this wont flash the image..i will just push the recovery on your mobile and then would start it..then try to format all the partions
and can u provide us with all details..like exactly how the error happened..???
and is your phone under warranty..??
i just tried to boot the cwm via fastboot.
the phone vibrated 8 times, three android dudes on a skateboard appeared and the phone rebooted into HBOOT.
I tried also this RUU: http://forum.xda-developers.com/showthread.php?t=1705913, but it results in a 171 USB Error...
The phone isn't under varranty anymore.
How the error occured: I was browsing around, when suddenly whatsapp crashed. So i rebooted the phone and it was stuck in a bootloop. Then i tried to flash a new rom and the error occured
edit: after following to this guide here http://community.htc.com/na/htc-forums/android/f/113/t/10043.aspx, i was able to flash the device using the RUU. But I couldn't use the phone due to crashing processes (mostly android.process.arcore), so I rebooted. Now the phone is stuck again in a bootloop...
try installing the RUU again...and if possible if you are installing a custom rom please wipe all partition ,cache and dalvik cache...
and try booting the mobile withouth the sim card...lets see if it works
i just tried it, with the same result
Hi, I have tried being clever and rooting my HTC ONE Mini, which all went perfectly well. Unlocked Bootloader and installed TWRP.
I found a radio update on a website and tried installing it, with S-ON. As you can imagine I am not stuck in Bootloop.
I somehow managed to wipe all the data off my phone and sdcard too.
So I am stuck with a phone in bootloop with recovery from TWRP.
Everytime i try and fastboot flash any file even an Android ROM.zip it doesnt like it. I am novice at this so you are probably reading this and think what is he doing.
Can someone help me or guide me to getting my phone back and running again. Please??
wrighty29 said:
Hi, I have tried being clever and rooting my HTC ONE Mini, which all went perfectly well. Unlocked Bootloader and installed TWRP.
I found a radio update on a website and tried installing it, with S-ON. As you can imagine I am not stuck in Bootloop.
I somehow managed to wipe all the data off my phone and sdcard too.
So I am stuck with a phone in bootloop with recovery from TWRP.
Everytime i try and fastboot flash any file even an Android ROM.zip it doesnt like it. I am novice at this so you are probably reading this and think what is he doing.
Can someone help me or guide me to getting my phone back and running again. Please??
Click to expand...
Click to collapse
You can't use fastboot to flash a rom.zip! It must be pushed to your phone (use either adb push or adb sideload from recovery) and installed from custom recovery.
Btw this is the wrong forum for your device. Htc one mini forum is here