Hi guys,
first sorry for my bad english.
I have a big problem to face with my N1
I wish to install a custom ROM, so I've rooted my phone and downloaded the Rom Manager apps from Market. I've flashed the clockwork recovery and downloaded the cyanogenmod. So I reboot my phone in fastboot mode, select recovery and now I have a black screen, nothing happens. My phone boot only when I take off the battery, so now I have no Recovery mode in my phone. Someone can help me please ?
I've already tryed to flash the original recovery and AmonRA recovery (1.7.0 and 1.8.0) from my PC but it fails everytime and I have this message => FAILED (remote: signature verify fail)
My N1 is in FRF91 build, with a Vodafone ROM from France (SFR)
The recovery is dependant on which screen you have. You've possibly flashed an incompatible recovery...
Which screen do you have?
How are you flashing your recovery?
Sent from my Nexus One using XDA App
ibolito said:
Hi guys,
first sorry for my bad english.
I have a big problem to face with my N1
I wish to install a custom ROM, so I've rooted my phone and downloaded the Rom Manager apps from Market. I've flashed the clockwork recovery and downloaded the cyanogenmod. So I reboot my phone in fastboot mode, select recovery and now I have a black screen, nothing happens. My phone boot only when I take off the battery, so now I have no Recovery mode in my phone. Someone can help me please ?
I've already tryed to flash the original recovery and AmonRA recovery (1.7.0 and 1.8.0) from my PC but it fails everytime and I have this message => FAILED (remote: signature verify fail)
My N1 is in FRF91 build, with a Vodafone ROM from France (SFR)
Click to expand...
Click to collapse
Is the USB cable plugged in AT ALL? I keep hearing Clockwork is unstable if it is.
I stick with Amon myself.
danger-rat said:
The recovery is dependant on which screen you have. You've possibly flashed an incompatible recovery...
Which screen do you have?
How are you flashing your recovery?
Sent from my Nexus One using XDA App
Click to expand...
Click to collapse
I have an SLCD screen and i've tryed all clockwork recoveries featured in Rom Manager app and the latest AmonRA ( 1.8.0 )
But the problem is when i try to flash it with my PC by connecting the phone in fastboot mode, i allways have this message : FAILED (remote: signature verify fail) which means I can't flash any recovery :s
Do you know what is the problem ?
Sounds like you flashed an incompatible recovery. You're heading in the right direction with Amon-Ra 1.8.0...
How are you flashing the recovery? (Since your current recovery has a black screen, are you using adb, trying to do it through Clockworkmod, etc?)
Sent from my Nexus One using XDA App
Yeah i've tryed to flash the latest clockwork recovery with Rom Manager, it works, i mean i can flash it this way but i have the same result : black screen. And flashing it with my PC using - fastboot flash recovery <recovery name>.img - code give me the failure message that i talk about on my last post
I've read a few posts about 1.8.0 failing with Clockworkmod, and I believe the adb and terminal methods require an unlocked bootloader. There are a few methods to flash custom recoveries without unlocking the bootloader (I still have a locked bootloader). Do a search, find one you like, and give it a try. Clockworkmod is one of those methods, but again, I've read problems with the 1.8.0 recovery on Clockworkmod...
Sent from my Nexus One using XDA App
http://forum.xda-developers.com/showthread.php?t=771507
Sent from my Nexus One using XDA App
thanks a lot for helping me by sending this link but as I said before, unfortunately I can't flash the recovery even with my PC, the only solution seems to make a bootloader unlocking, but I don't want to loose the warranty, i'll check other ways to do this without unlocking my bootloader, if someone know how to do this, i'll be thankful.
The link also discusses how to flash without unlocking the bootloader, which is why I sent it... (see posts from September 27)
Sent from my Nexus One using XDA App
Yes but see what hapen when I try it =>
The locked bootloader discussion points to this, which suggests using terminal emulator from your phone...
http://forum.xda-developers.com/showpost.php?p=7392149
Sent from my Nexus One using XDA App
thanks, I'm trying it immediately
...but with 1.8.0
Sent from my Nexus One using XDA App
Sure ? Not with 1.8.0.1 ? Because I have an SLCD screen
I meant 1.8x instead of the 1.7x they mention in the write up...
Also, you can ignore my comment about using terminal emulator, and use adb if you want (long day, and I'm tired)
Sent from my Nexus One using XDA App
I surrender, it doesn't work, and I'm tired of trying flashing a recovery. It means no custom ROM for me :'(
Take a break, and come back to it tomorrow...
Sent from my Nexus One using XDA App
OK, back to basics...
What ROM do you have (build number)
Hi, so my build number is FRF91, I bought it from SFR (Vodafone)
Related
I have a ME860 with official 2.3.4 updated, i yesterday unlocked the Bootloader with IHOP_Bell.sbf and have CWM flashed successfully. But my phone booted into command line saying OS not detected and was stucked at the command line with 14modes available.
I got into Recovery and flashed to CM7(latest Bat2F.zip) and it completed without error. Now the command line says OS will Boot in 5 secs but is again stucked with Cold Boot Linux Reading ODM Fuse:1 displayed.
I am new to this can someone help me out here ? Thank you
Are you messing around with RSD at all?
Sent from my Atrix XDA Premium App
the only time i used RSD is to flash the IHOP_Bell.sbf to enable unlocking the bootloader. As for flashing the CWM i did tru the Fastboot command from the computer. After that I have never touch RSD at all.
the phone boots up showing unlocked on the top left of the screen. however what i found a bit strange was, right after i flashed the IHOP_bell.sbf, the phone always boots up in the bootloader mode. i thought it was normal that way, so from there i selected the fastboot mode and the phone did boot into fastboot. then i connect the USB cable and entered the fastboot oem unlock and successfully unlocked the phone.
after that, i flashed the CWM recovery mode using moto-fastboot flash recovery and it was done, and i am able to get into CWM recovery options too.
Actually i am thinking of flashing the HKTW fruitcake sbf, do u think it is a good idea ? or should i try something else first?
I wouldn't touch that. I personally never used that. I would wait till another user comments.
Sent from my Atrix XDA Premium App
i tried the fruitcake anyways, and it actually booted up !!
i took a look at the phone details. my phone is now MB860 instead of ME860 which i had b4. anyways there seems to be minor bug with this stock HKTW ROM cuz in the phone details , the version number has a userdebug name in it. so i guess thats way its not stable
will try to flash CM7 again
CM7 still not working, any ideas anyone ??
minusioner said:
CM7 still not working, any ideas anyone ??
Click to expand...
Click to collapse
What CWM are you using? If it doesn't support ext4 that might be your problem. The things you've successfully flashed are all ext3.
Make sure you're using ROM Manager's or romracer's. Those are the only ones that support ext4.
Need to know what recovery you have installed & did you wipe data/factory rest & wipe both caches before flashing CM7????
Sent from my MB860 using xda premium
thank you guys ! i was using this CWM recovery-en-goapk-0630-1029.zip
also from xda so i thought everything was good
so now i have CM7 up and running !!!!
I thought that was deprecated? I may be wrong
I use romracers and sometimes the one in rom manager
but ididnt like it
Sent from my MB860 using xda premium
minusioner said:
thank you guys ! i was using this CWM recovery-en-goapk-0630-1029.zip
also from xda so i thought everything was good
so now i have CM7 up and running !!!!
Click to expand...
Click to collapse
Hello, i got one ME860 Atrix from Hong Kong, and updated the stock rom to 2.3.4 already.
I would like to try the Neutrino rom, as it so beautiful
i have unroot it by using superoneclick 2.2, installed RSD 5.3.1,
then i have confused what is my next step for unlock bootloader process...
i should flash the IHOP_Bell.sbf or OLYEM_U4_2.1.1_SIGNED_UCAOLYPORTFR_P014_A004_M001_HWolympus_1g_1FF.sbf
?? anyone can help me Anyway, thanks a lot~~
Motorola ME860 successful unlocked IHOP_Bell.rar
Then install recovery from fastboot
and ROM from CWM
I tried to root with gingerbread stuff in icecream and now my phone can't get to recovery... any help plz ?
( no brand )
???? U don't make any scene
Sent from my Nexus S 4G using xda premium
Abdou hammadi said:
I tried to root with gingerbread stuff in icecream and now my phone can't get to recovery... any help plz ?
( no brand )
Click to expand...
Click to collapse
i have no idea what you did to whatever model of nexus s you did it to, because you give no information at all. unless "gingerbread stuff in icecream" is enough info and im just missing something
anyways, try flashing either cwm recovery or twrp recovery through fastboot again.
Esteway.619 said:
???? U don't make any scene
Sent from my Nexus S 4G using xda premium
Click to expand...
Click to collapse
^^ fail.
haha
To the OP, post more info, in English so we can help out!
I think what he mite b tryin to say is that he used a gingerbread root method on ics...at least i think thats whats hes saying...lol
Sent from my Nexus S 4G using XDA Premium App
Flash clockwork recovery through fastboot and go straight into recovery (without restarting the phone).
Ahh sorry for the usless info.
I used a gingerbread root method on my nexus s i9023 and the root failed... It shows unlocked status but apps that require root doesn't work on the phone. I tried to unroot it using the gingerbread method and I failed to access to the recovery mode ( red triangle icone when i try recovery mod).
Any help ?
Read the stickies about rooting a nexus and they'll show you how to download CWM and use "fastboot flash recovery recovery.img" to install a new recovery. After this you use the latest superuser.zip (also stickied) for ICS. Once this is done you need to change a filename so ICS doesn't flash it's own bootloader again, then you can be on your merry way.
You will need to flash recovery again using fastboot method
You can find great guides on the forum.
Just make sure that when you do fastboot flash recovery, DO NOT REBOOT the phone, but using the volume buttons, highlight 'RECOVERY' and hit enter to go into CM recovery.
Also make sure you have latest CM recovery version.
Good luck!
Ok every guide I looked at said you can easily flash something to gain root again well in order to flash anything you have to have root so it doesn't make any sense and I didn't see any guides on this or related posts and I'm running 4.2.2
Sent from my Nexus 7 using xda app-developers app
fastboot oem unlock
fastboot flash recovery nameofrecovery.img
boot into recovery
flash the supersu.zip root package.
What is so complicated about that?
you dont need root to flash something, you need an unlocked bootloader and a custom recovery.....
i swear the word root has lost all meaning these days. everyone wants it, but it seems so very few actually understand what it is.
Pretty sure you just need to fastboot flash a custom recovery, then you can flash the superuser binaries by chainsdd (Google the package), then install superuser or superSU from the market.
Not familiar with nexus 7, but this is how I rooted a galaxy nexus. There should be a sticky in your device specific forum with links to the process and files.
From my Evo LTE, yup.
I went to fastboot but when I go into recovery I get an error
Sent from my Nexus 7 using xda app-developers app
Class_of_punk26 said:
I went to fastboot but when I go into recovery I get an error
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
An error?
if you want help, provide info
I'm in the car ATM but when I turn my device off and I go into boot loader I push either up or down like 2 times it shows recovery mode I click it and it shows a android guy with a red thing in the center of him
Sent from my Nexus 7 using xda app-developers app
Class_of_punk26 said:
I'm in the car ATM but when I turn my device off and I go into boot loader I push either up or down like 2 times it shows recovery mode I click it and it shows a android guy with a red thing in the center of him
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
thats stock recovery.....did you ever FLASH a custom recovery, like all the guides tell you to?
I tried downloading clockworkmod recovery from ROM manager but the download failed so I downloaded recovery manager from the play store and downloaded a recovery using the app it said the recovery installed
Sent from my Nexus 7 using xda app-developers app
Class_of_punk26 said:
I tried downloading clockworkmod recovery from ROM manager but the download failed so I downloaded recovery manager from the play store and downloaded a recovery using the app it said the recovery installed
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Dude,
As the guides tell you, and I lined out above, you need to FASTBOOT FLASH RECOVERY
unless you are already rooted, then downloading ROM Manager or 'recovery manager' from the app store doesnt do any good....
you need a computer to do this in fastboot mode.
Damn I was hoping I could avoid using my friends very slow comp lol
Sent from my Nexus 7 using xda app-developers app
I'm in the similar situation - I upgraded rooted 4.2.1 via modified OTA (original OTA was failing because of one apk) and now I have 4.2.2, but even though I had SuperSU which was ticked to "survival mode" (should keep the root), it apparently didn't. I don't have TWRP anymore, when I press power+vol dn I get the standard "start" screen (original recovery). Also, when I turn N7 on, it is displaying keychain that is OPEN, that means my bootloader is unlocked?
So my question(s)... my bootloader is probably unlocked? If I do the steps:
fastboot oem unlock
fastboot flash recovery nameofrecovery.img
boot into recovery
flash the supersu.zip root package
will I loose all data/apps? I ask because when I first rooted with toolkit, I lost all apps/data.
Also, where to find supersu.zip ? That is different to the installed SuperSU.apk, right?
Damn I can't make ADB work... I tried 2 computers.... Damn google for making this so [email protected]#[email protected]$ .... Constant problems, nothing else. Any clues? I ofcourse, tried kill-server and start-server, no matter what my device is showing offline....
Just checked with my phone (SGNII) and it is working just fine... no clue why Nexus is showing as offline..
I had to do a complete wipe from the computer and flashed clockwork mod recovery. Since it was likely an old version I had the double 0 partition problem which I fixed by manually moving the files. I tried to update the recovery to twrp, but it won't flash using goomanager. It downloads and says it's flashed but it's not there.
I also seem to have a weird problem where I have to push the power button to get it to boot past the Google screen. If I don't push power it gets stuck there forever.
Any ideas?
Sent from my Galaxy Nexus using Tapatalk 4
Follow the sticky at the top that says flashing a factory ROM using fastboot/return to stock. Start from scratch, get it working, and then flash whatever you want.
Sent from my Nexus 7(2012) that has zero issues.
SlowCobra96 said:
Follow the sticky at the top that says flashing a factory ROM using fastboot/return to stock. Start from scratch, get it working, and then flash whatever you want.
Sent from my Nexus 7(2012) that has zero issues.
Click to expand...
Click to collapse
That's what I did, that's why I'm stuck on the old recovery.
Sent from my Nexus 7 using Tapatalk 4
T-Keith said:
That's what I did, that's why I'm stuck on the old recovery.
Sent from my Nexus 7 using Tapatalk 4
Click to expand...
Click to collapse
This might be an odd question, but have you tried just updating CWM first, and THEN flashing TWRP? Sometimes the flash won't go smoothly with an older version of one recovery to a newer version of a different recovery- not sure why, but that's just been my experience. I would update CWM first then try flashing TWRP.
Also, if goo is not working for you, you could try Rom Manager to update CWM and then flash TWRP. It can flash either. (If you really want to flash via the device).
Otherwise, (me personally) I'd just use adb fastboot to flash a new recovery.
Hope that helps
Thanks I will try that.
Sent from my Galaxy Nexus using Tapatalk 4
T-Keith said:
Thanks I will try that.
Sent from my Galaxy Nexus using Tapatalk 4
Click to expand...
Click to collapse
No problem. Let us know how it works out for you.
Tried flashing with fastboot, now it won't boot into recovery, just hangs at the Google logo.
Still needs a bump from the power button to get it to boot normally.
Sent from my Galaxy Nexus using Tapatalk 4
T-Keith said:
Tried flashing with fastboot, now it won't boot into recovery, just hangs at the Google logo.
Still needs a bump from the power button to get it to boot normally.
Sent from my Galaxy Nexus using Tapatalk 4
Click to expand...
Click to collapse
Ahh, that sucks! How are you *attempting to* access recovery... via reboot menu, via adb, or via 3-button press? It shouldn't matter, but you could try all three methods to see if any way will give you recovery access. Then, if/when you manage to get in, you could reflash again straight from recovery. I'm going to do some digging to see if I can find a better solution. I KNOW I've read about the same issue before, I know there's a solution... I just have to find it again.
Worse comes to worse, you might have to reflash stock recovery then reflash custom recovery. Might be a corrupt recovery img, but I will check and try some things out and let you know what I find.
Edited to add:
Yes. there was a bug in the older bootloader that bypassed/refused access to recovery... so since you restored stock, you probably need to update your bootloader to at least to version 4.18 (via fastboot). THEN you should be able to access recovery. I can't add links, but I can give you a text link once I find just the IMG file instead of the full firmware. Honestly, I never do backups so I don't have the file on hand. However, I may do one backup at least so I can extract my boot img and give it to you.
OK, so I found the info I was looking for.
From Elsewhere:
Steps:
Install latest nexus 7 bootloader.
This fixes the boot loader bug and now you can enter recovery from the bootloader screen.
Update the bootloader to at least 3.18. Make sure NOT TO DELETE THE BOOTLOADER!!!!!!!!!!!!!
I cannot emphasize this enough!!!!!!!!!!! I bricked my first one this way.
Use
fastboot flash bootloader C:\>>>>>>\bootloader-grouper-3.18.IMG***
Click to expand...
Click to collapse
Do NOT erase bootloader before you flash the new one. And after you have flashed the new one type;
fastboot reboot bootloader
Click to expand...
Click to collapse
and check the bootloader version to make sure you succeeded.
Click to expand...
Click to collapse
***Or whatever you name the boot img file!***
https://dl.dropboxusercontent.com/u/19608328/boot.img.zip --> This is from MY Nexus 7. It's Bootloader version 4.23, and works with JB 4.2.2- it does NOT have the recovery access bug.
https://dl.dropboxusercontent.com/u/19608328/recovery.img.zip --> This is a copy of MY CWM, which I just updated to 6.0.3.6 yesterday.
I'd flash the bootloader, then flash your recovery of choice. Not being able to access recovery is a bootloader issue, not a recovery issue. The fact that you restored/reverted an older full firmware put you on an older bootloader that would not allow users to access recovery.
Try the new(er) bootloader, it should work. My device is a 16gb grouper Nexus 7 running 4.2.2. Before that, it ran 4.1.2 without any issues, so it should work to resolve the problem you're having.
I have been trying to change my custom ROM this entire week and I'm rooted and I unlocked my bootloader ,downloaded the ROM I want to use and gapps now the problem is the flash recovery everything I do it there is a problem the first time it said no command and showed the android guy with a caution sign now when I reboot to recovery it shows the bootloader warning sign and then it kinda like skip something then (I think the recovery) then just does a normally boot please help i have use ROM manager ROM installer and I just can't get it to work and I'm using a droid RAZR m version 4.4.2.
Sent from my XT907 using XDA Free mobile app
This has pretty much been covered... Check the linked thread...
Sent from my XT907 using xda app-developers app
Dr3loc said:
I have been trying to change my custom ROM this entire week and I'm rooted and I unlocked my bootloader ,downloaded the ROM I want to use and gapps now the problem is the flash recovery everything I do it there is a problem the first time it said no command and showed the android guy with a caution sign now when I reboot to recovery it shows the bootloader warning sign and then it kinda like skip something then (I think the recovery) then just does a normally boot please help i have use ROM manager ROM installer and I just can't get it to work and I'm using a droid RAZR m version 4.4.2.
Sent from my XT907 using XDA Free mobile app
Click to expand...
Click to collapse
The recovery must be a bad flash try to flash one of the following recovery in fastboot mode with a computer if you know how to do it, if not then try to flash with rashr app from playstore, download the recovery manually from the link below and then flash it with rashr by going into choose from storage accept the warnings... Done.
Twrp
http://androidhosting.org/Devs/Dhacker29/msm8960/TWRP2710-RAZR_M-KITKAT.img
Cwm
http://androidhosting.org/Devs/Dhacker29/msm8960/CWM6049-RAZR-HD_M-KITKAT.img
These are only to flash kk bootloader compatible ROM's
Edit: also you can change the unlocked bootloader waring logo into previous M or Google logo see this post(don't try to flash it with the app mentioned above)
http://forum.xda-developers.com/showpost.php?p=53579570&postcount=87