Related
Hi, I have a N1 with the stock firmware, updated to Froyo 2.2 build FRF91, but I have a modded recovery, Amon RA v.1.70. Now i wanna restore my recovery and flash the stock one, but i can't. I followed some tutorials but it's useless. Every time i type in the terminal fastboot flash recovery recovery.img, after went to the directory that I stored my unzipped files, it says FAILED signature. I don't know what I have to do. Help me please.
http://forum.xda-developers.com/forumdisplay.php?f=603
In before the lock!
Kinda of the wrong section but here is what frankyyy02 says he did,
frankyyy02 said:
Yeah i had the same problem when i tried to revert mine to stock. My bootloader was lock and wouldnt let me reflash the stock rom with verification failed.
NOT SURE IF THIS IS THE CORRECT WAY, DO AT YOUR OWN RISK :
I renamed the image to PASSIMG.zip and booted into bootloader. The bootloader automatically searches for PASSIMG and when it found it went through an update/installing process which took about 5minutes. When it booted phone was unrooted again, and had the stock recovery.
Once that was done, i installed the FRF85 (i think) update.zip from bootloader recovery, then did the same with update.zip for FRF91.
Again not sure if this was the correct way as i have never seen posts directing to do it this way - have posted questions about it in the past week or two, but never got any responses...
Click to expand...
Click to collapse
That doesn't seem to work for me
Sent from my Nexus One using XDA App
Solved!
Hi,
I have SLCD Nexus one(2.2) and I want to install custom rom.
But it shows black screen because it's not OLED.
Solved!! - Most custom roms having new kernels work, if it doesn't have new kernel installing new kernel works!
I've got the same problem. I even tried brute force, because I got everything working but got stuck on a black screen recovery, which I tried to get working for hours. I thought it might be the new rom or the new hboot, so I flashed a new image via fastboot. Now I'm stuck at a black screen os (thank god fastboot still works) - but I'd need a stock slcd rom to get back to where I started.
Could someone be so kind and upload an slcd rom? Or even better some slcd custom recovery+slcd+new hboot compliant custom rom?
I think, that a lot of people will get in this trap, because there are no warnings, that even the newest cm/ra_recovery won't work on a new nexus one.
Thanks in advance.
Update: Solved on my own. Now I'm just waiting for some slcd recovery + mod. ;-)
This is Amon Ra's Nexus One SLCD recovery dl.dropbox.com/u/4481275/recovery-RA-nexus-v1.8.0.1-aw.img
Well, at least be glad that fixing a dark Nexus One is probably much easier than fixing a dark HTC Desire!
I suggest this sequence if you have an SLCD N1:
1) Root first, then load ROM Manager
2) Install custom recovery but keep your ROM for now. Boot into recovery. If it's dark, wrong recovery - try again.
3) ONLY once you have a working recovery should you even think about trying other ROMs. And don't forget to take a full nandroid backup first. You should be able to restore that backup safely from recovery.
Zorr0theOne said:
This is Amon Ra's Nexus One SLCD recovery dl.dropbox.com/u/4481275/recovery-RA-nexus-v1.8.0.1-aw.img
Click to expand...
Click to collapse
Thanks, but I'm asking for custom rom, not recovery.
Anyway, thank you very much.
cmstlist said:
Well, at least be glad that fixing a dark Nexus One is probably much easier than fixing a dark HTC Desire!
I suggest this sequence if you have an SLCD N1:
1) Root first, then load ROM Manager
2) Install custom recovery but keep your ROM for now. Boot into recovery. If it's dark, wrong recovery - try again.
3) ONLY once you have a working recovery should you even think about trying other ROMs. And don't forget to take a full nandroid backup first. You should be able to restore that backup safely from recovery.
Click to expand...
Click to collapse
Thanks, but I'm asking for custom rom, not fix. (I already fixed it)
Anyway, thank you very much.
i have same problem as wisechild but u said u have fixed it and just waiting for custom rom if so how did u fix it. i no the recovery works in the background, when the screen is dark cause if u do a backup in rom manager and let it run despite dark screen it shows up when u go back to rom manager. the trouble is i have the hboot 0017 instead of 0012 so can't install cm roms. is there a rom that works with that hboot.
found solution, the latest Kang-o-rama rom work with the korean hboot 0.35.0017 . Installed it using rom manager install from sdcard option. despite not being able to see the recovery screen just let it run for like 5 mins then it reboots and u got a custom rom.
aljnbaptiste said:
found solution, the latest Kang-o-rama rom work with the korean hboot 0.35.0017 . Installed it using rom manager install from sdcard option. despite not being able to see the recovery screen just let it run for like 5 mins then it reboots and u got a custom rom.
Click to expand...
Click to collapse
Thanks, but I'll wait for custom rom supporting FM(ie NXSense).
Anyway thank you very much.
If you'd like a specific ROM to support SLCD, best to request this directly on the thread for that ROM.
I wonder if there is a component which can be swapped in easily to provide SLCD support?
wisechild said:
Solved!
Solved!! - Most custom roms having new kernels work, if it doesn't have new kernel installing new kernel works!
Click to expand...
Click to collapse
Can you verify with a ROM like CM6 or Evil Sense.
Please, do tell us how you implemented a fix .
Hmm
Can anyone help please?
I previously flashed an old Amon Ra recovery onto my N1 SLCD & suffered the blank screen fate. Since rooted with universal androot and tried to copy over and flash using adb shell (for some reason fastboot flash recovery doesn't seem to work - i still get the blank screen). However, adb shell denies permission to become su even though following root i can become su using terminal emulator on the phone ... Anyone have any ideas?
rob_2010 said:
Can anyone help please?
I previously flashed an old Amon Ra recovery onto my N1 SLCD & suffered the blank screen fate. Since rooted with universal androot and tried to copy over and flash using adb shell (for some reason fastboot flash recovery doesn't seem to work - i still get the blank screen). However, adb shell denies permission to become su even though following root i can become su using terminal emulator on the phone ... Anyone have any ideas?
Click to expand...
Click to collapse
I think fastboot flash recovery requires an unlocked bootloader.
With adb shell you have to type su and then, on the phone, look for the permissions dialog to come up. After you accept, it will give you a root shell. If it's not asking you for the permissions, I'm not sure what else to do.
I think you could also conceivably run flash_image from the terminal emulator as root and flash the correct recovery that way.
shundi82 said:
I've got the same problem. I even tried brute force, because I got everything working but got stuck on a black screen recovery, which I tried to get working for hours. I thought it might be the new rom or the new hboot, so I flashed a new image via fastboot. Now I'm stuck at a black screen os (thank god fastboot still works) - but I'd need a stock slcd rom to get back to where I started.
Could someone be so kind and upload an slcd rom? Or even better some slcd custom recovery+slcd+new hboot compliant custom rom?
I think, that a lot of people will get in this trap, because there are no warnings, that even the newest cm/ra_recovery won't work on a new nexus one.
Thanks in advance.
Update: Solved on my own. Now I'm just waiting for some slcd recovery + mod. ;-)
Click to expand...
Click to collapse
how did you solve the problem, i'm stuck with a blank screen os also the keys light up and work but no screen
Flash AmonRa's 1.8.0.1 recovery that supports SLCD, and then flash any ROM you like - most of them support SLCD now, and if you see that the one you flashed doesn't - flash another.
Jack_R1 said:
Flash AmonRa's 1.8.0.1 recovery that supports SLCD, and then flash any ROM you like - most of them support SLCD now, and if you see that the one you flashed doesn't - flash another.
Click to expand...
Click to collapse
cant really troubleshoot now cause i'm at work but how would i be able to enable usb debugging if i cant see the screen?
You couldn't get stuck in ROM if you flashed a recovery that doesn't support SLCD, because you wouldn't be able to install ROM without it - and you couldn't get stuck without ROM if you only flashed a recovery that doesn't support SLCD. So one of them should be working for you, and enable to make the other work.
That is unless you used ROM manager, which flashed the recovery for you and did all the stuff - and it didn't show anything, because Clockwork recovery doesn't support SLCD (so you would get your ROM installed for you and not see it, and then you'd get stuck with a ROM that doesn't support SLCD).
If that's the case, run the recovery and try to connect ADB (recovery runs ADB interface).
Jack_R1 said:
You couldn't get stuck in ROM if you flashed a recovery that doesn't support SLCD, because you wouldn't be able to install ROM without it - and you couldn't get stuck without ROM if you only flashed a recovery that doesn't support SLCD. So one of them should be working for you, and enable to make the other work.
That is unless you used ROM manager, which flashed the recovery for you and did all the stuff - and it didn't show anything, because Clockwork recovery doesn't support SLCD (so you would get your ROM installed for you and not see it, and then you'd get stuck with a ROM that doesn't support SLCD).
If that's the case, run the recovery and try to connect ADB (recovery runs ADB interface).
Click to expand...
Click to collapse
that was the case. i'll try in a few hours when i get home. once i'm in adb i would try to flash amon ra's recovery and start over correct?
Indeed, correct.
Use recovery flashing guide from Wiki. If you're rooted without unlocking - follow the "flash_image method" guide. If you find out that you need to install busybox - download the APK and install using ADB, instead of downloading from the Market.
I wrote this how-to, I think it might help you.
h**p://forum.xda-developers.com/showthread.php?t=785581
cestbibi said:
I wrote this how-to, I think it might help you.
http://forum.xda-developers.com/showthread.php?t=785581
Click to expand...
Click to collapse
It's essentially the same guide as in Wiki, but executed through ADB - which is good. I'll add your guide to the Wiki for reference, with a link. I saw, it doesn't require Busybox (uses "cat >" instead of "cp").
I'm having a problem with this recovery, whenever I do nandroid it does everything but then gets stuck on backing up data... and then i have to pull the battery I try to back up but then comes MD5 mismatch anyone know how to fix this nandroid error?
--As of Now-- Killed my phone -.-
--As of 30 secs later-- Fixed my phone with older nandroid backup...same recovery error...
--As of Now-- angry D:<
--10 mins later- I hate you clockworkmod...go RA recovery...
it hangs for quite a while when making the md5 sum. You sure you waited long enough?
shyam101 said:
I'm having a problem with this recovery, whenever I do nandroid it does everything but then gets stuck on backing up data... and then i have to pull the battery I try to back up but then comes MD5 mismatch anyone know how to fix this nandroid error?
--As of Now-- Killed my phone -.-
--As of 30 secs later-- Fixed my phone with older nandroid backup...same recovery error...
--As of Now-- angry D:<
--10 mins later- I hate you clockworkmod...go RA recovery...
Click to expand...
Click to collapse
clockworkmod works fine for me and yes it does hang for awhile let it sit for a good 20mins before taking the battery out, make sure the is space on the sdcard, and depending on th speed of the sdcard it might take longer.
noob with rooted hero...
So ive been using my rooted hero for awhile now i got the RA recovery working and the CM 6.x but I havent been able to get the clockworkmod working either. ive been using the rom-manager app from the market and whenever I try to flash the clockworkmod it says error while flashing? so is there another way to flash the clockworkmod or something else i can try to make it work, i havent been able to find much info out there. if you could direct me where to look or whatever i could use the help thanx. Im just testing everything out that i can so i learn the field ive been playing around in better.
danaff37 said:
it hangs for quite a while when making the md5 sum. You sure you waited long enough?
Click to expand...
Click to collapse
waited for 10 mins once and all it says is backing up data and wont continque
shyam101 said:
I'm having a problem with this recovery, whenever I do nandroid it does everything but then gets stuck on backing up data... and then i have to pull the battery I try to back up but then comes MD5 mismatch anyone know how to fix this nandroid error?
--As of Now-- Killed my phone -.-
--As of 30 secs later-- Fixed my phone with older nandroid backup...same recovery error...
--As of Now-- angry D:<
--10 mins later- I hate you clockworkmod...go RA recovery...
Click to expand...
Click to collapse
Open up Rom Manager and scroll down to Flash Alternate Recovery and touch that. It will ask 'Are you sure you want to flash an alternate recovery? blah blah blah.. Select OK. Once finished select OK. Scroll back to the top and select Flash ClockworkMod Recovery. Select the phone model (mine is HTC Hero (CDMA) and wait. Once finished select OK then scroll to Reboot into Recovery. Hope that helps
I7IZI said:
So ive been using my rooted hero for awhile now i got the RA recovery working and the CM 6.x but I havent been able to get the clockworkmod working either. ive been using the rom-manager app from the market and whenever I try to flash the clockworkmod it says error while flashing? so is there another way to flash the clockworkmod or something else i can try to make it work, i havent been able to find much info out there. if you could direct me where to look or whatever i could use the help thanx. Im just testing everything out that i can so i learn the field ive been playing around in better.
Click to expand...
Click to collapse
Is superuser installed? it is default with most custom roms, but if you are running stock sprint rooted it wont be, the app needs to have superuser permissions to flash.
Hmm, well before I got the opportunity to try installing superuser I goofed something and had to start over from scratch. But when I reinstalled rom manager I got it to flash the clockwork recovery, I think it may have been that I didn't install the clockwork rom before I did anything else the first time. Anyhow after flashing clockwork I goofed something again and decided I preferred Amon recovery more so now everything is working and stable again. Thanx for tip though I'll remember that if I ever go back to the stock sprint rom...
Sent from my HERO200 using XDA App
After I did the S-OFF unlock, the only way I could get a recovery on the phone was via the unlocked (S-OFF) HBOOT, taking the clockwork recovery image (.img) adding it and an android-info.txt (is that right?) I stole from someone elses HERCIMG.zip and making my own HERCIMG.zip then flashing via HBOOT menu.
If I try to use ROM Manager, I get an error that flashing failed too. Amon_Ra recovery flashes fine from ROM Manager, however.
Hope I didn't confuse anyone
where can I download Clockwork Mod Recovery 2.5.0.1,thanks!
Where can i download Clockwork Mod Recovery 2.5.0.1 thanks!
fenghua520 said:
Where can i download Clockwork Mod Recovery 2.5.0.1 thanks!
Click to expand...
Click to collapse
google? xda search?
Im AlphaRev S-off and running a gingebread orginial shipped rom from HTC, recieved a OTA update and installed it.. the phone rebooted and now im stuck at the white HTC screen, when i try to enter recovery section in bootloader it just skips back to the white HTC screen, tried to load an signed_RUU onto the mem card and install calling it PG32IMG without luck..
What to do ?
Can you connect to the phone via fastboot or adb?
Wait at least five minutes on the htc boot screen, sometimes the rom is busy working during this boot up time.
Sent from my HTC Incredible S using XDA App
Well...u r in problem
U can fix that easy...
1. Download 2.3.3 RUU
2. Downgrade from AlphaRev hboot to official *HOW TO GET BACK ON S-ON* http://forum.xda-developers.com/showthread.php?t=1359555
3.Install 2.3.3 RUU
4. boot 2.3.3 - run OTA update
***New hboot is 2.00.0000 its cant be S-OFFed ,so,phone cant be rooted for now
but u can try new Android Rev HD 2.1.0 based on new official update.
Procedure for installing new AHD 2.1.0 is same like before
1*super wipe script
2*install new rom from 4EXT recovery
Yeah, so i downloaded the rom you suggested, could not find 2.3.3 by the way? but tried with one of the other WWE roms, getting "no image or wrong image" when i try to load the PG32IMG.zip from bootloader, what do I do now? :S
Tried with 2 different mem cards as this error seems to have to do with the card.. but still no luck.. I would not have an problem if i could get into recovery mode, but when i press "recovery" in the bootloader it just gives me that damn white HTC screen..
Anyone? Maybe reinstall the old aplharev with ADB in a way? anybody?
iNzzane said:
Yeah, so i downloaded the rom you suggested, could not find 2.3.3 by the way? but tried with one of the other WWE roms, getting "no image or wrong image" when i try to load the PG32IMG.zip from bootloader, what do I do now? :S
Tried with 2 different mem cards as this error seems to have to do with the card.. but still no luck.. I would not have an problem if i could get into recovery mode, but when i press "recovery" in the bootloader it just gives me that damn white HTC screen..
Anyone? Maybe reinstall the old aplharev with ADB in a way? anybody?
Click to expand...
Click to collapse
Make sure you didn't copy it to the SD card as PG32IMG.zip.zip. That would give you the no image or wrong image message.
Yeah, correct name.. worked now but gets "incorrect model id" then i downloaded a coocked unzigned room, but gets "parsing.." and then it goes back to the bootloader.. anyone?
EDIT: Fixed, used a random shipped rom and it worked.. with the PG32IMG method.. strange.. anyhow thanks guys
Hey guys,
My situation is that I'm trying to get a working ICS rom working, but I get a black screen on bootup for both Virtuous Quattro and Ice Cold Sandwich. I've also tried different kernels, but the same thing happens.
What I did:
Reboot into ClockworkMod Recovery
Backup
Wipe data
Wipe cache
Wipe dalvik cache
Install zip from sd card > Choose zip > Picked my zip here > Confirm
The actual rom installs with no errors or anything... then when I try to reboot, I get the white screen with "htc" in green font, as normal, then it just goes to a black screen. The backlight is on, but the screen is black... softkeys are not lit, either. Like I said, I've reflashed multiple times to no avail. I've seen videos of people on YouTube flashing on IncS, but their devices go straight to the bootloader animation after the htc logo screen.
Anybody encountered this before or know how to fix it? Thanks in advance.
anonymousthing said:
Hey guys,
My situation is that I'm trying to get a working ICS rom working, but I get a black screen on bootup for both Virtuous Quattro and Ice Cold Sandwich. I've also tried different kernels, but the same thing happens.
What I did:
Reboot into ClockworkMod Recovery
Backup
Wipe data
Wipe cache
Wipe dalvik cache
Install zip from sd card > Choose zip > Picked my zip here > Confirm
The actual rom installs with no errors or anything... then when I try to reboot, I get the white screen with "htc" in green font, as normal, then it just goes to a black screen. The backlight is on, but the screen is black... softkeys are not lit, either. Like I said, I've reflashed multiple times to no avail. I've seen videos of people on YouTube flashing on IncS, but their devices go straight to the bootloader animation after the htc logo screen.
Anybody encountered this before or know how to fix it? Thanks in advance.
Click to expand...
Click to collapse
Your phone must be rooted before this and also verify your downloaded zip file with checksum to make sure about proper download.
I actually encountered the same problem a few days ago. I realized it was because I flashed an incompatible Kernal zip file. So I reflashed the ROM and rebooted without flashing any kernals and it worked for me.
I have rooted, and have superuser access. I have also redownloaded and checked the md5 sums. I'll try to download it again and test...
I just redownloaded and rechecked the md5 sums, and I still get the black screen. I've also tried no kernel, and tiamat and still nothing :S
anonymousthing said:
I just redownloaded and rechecked the md5 sums, and I still get the black screen. I've also tried no kernel, and tiamat and still nothing :S
Click to expand...
Click to collapse
have u converted you filesystem to ext4?
btw, what rom was previous? stock one or custom?
and i recommend you to use 4ext recovery instead of CWM
I have to use CWM for now, since I don't have access to fastboot right now (i'll download it later), but how do I check if it's ext4 or not in CWM? And if its not, do you know how to make it ext4?
And i'm using CM7, not stock
anonymousthing said:
I have to use CWM for now, since I don't have access to fastboot right now (i'll download it later), but how do I check if it's ext4 or not in CWM? And if its not, do you know how to make it ext4?
And i'm using CM7, not stock
Click to expand...
Click to collapse
if u have CM7 ur filesystem already converted )))
i think the reason of crashes on boots is old version of recovery. try to upgrade urs CWM or install the latest 4ext recovery
It's very easy to change CWm to 4ext: go to http://4ext.net/ and download 4EXT Recovery Updater, install it. With its help u will instal 4ext
Are you s-off?
Sent from my Incredible S using xda premium
I'm not S-OFF, but my bootloader is unlocked... i think it doesn't really matter much in this case if I have/can flash CM7 without issues
I'll try another version of CWM or try 4ext recovery tomorrow sometime
anonymousthing said:
I'm not S-OFF, but my bootloader is unlocked... i think it doesn't really matter much in this case if I have/can flash CM7 without issues
I'll try another version of CWM or try 4ext recovery tomorrow sometime
Click to expand...
Click to collapse
i'm afraid s-on is the reason of ur problems
I completely agree s-on does matter always.
I have the same problem on Quattro.
If you are s on you have to flash via fastboot the boot.img inside the Rom.zip from your wanted rom after flashing Rom via recovery.
Fastboot flash boot boot.img
Sent from my HTC Incredible S using xda premium
Indeed sniper is correct. However what I would do, get a rom working then look into becoming s-off. Its so much easier to mod your phone after.
Sent from my Incredible S using xda premium
Okay, thanks guys! I'll try it out later and see how it goes by flashing boot.img using fastboot.
Thanks guys, it works!
For people who come here looking for answers, basically just open the new ICS rom zip, extract boot.img, cd to that folder in cmd, and type:
fastboot flash boot boot.img
and it should now boot properly.
anonymousthing said:
Thanks guys, it works!
For people who come here looking for answers, basically just open the new ICS rom zip, extract boot.img, cd to that folder in cmd, and type:
fastboot flash boot boot.img
and it should now boot properly.
Click to expand...
Click to collapse
Or just make s-off one time and flash roms without any necessity to flash boot.img manually
Sent from my Incredible S using Tapatalk
I have HBOOT 2.0, sadly I accidentally updated my original htc and it updated HBOOT as well... and I can't be bothered to downgrade now lol
I'll do it later when I have the time to download the downgrade toolkit
anonymousthing said:
I'm not S-OFF, but my bootloader is unlocked... i think it doesn't really matter much in this case if I have/can flash CM7 without issues
I'll try another version of CWM or try 4ext recovery tomorrow sometime
Click to expand...
Click to collapse
I had a issue with something on my SD card after i wiped my SD and tried the re install it worked.
let me know if that helped.