Related
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)
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
hi im new to the whole nexus 7 scene just got it today and its also my first nexus device. came from a highly locked down dx2 then to htc and now im trying this. i used the nexus root toolkit v1.5.5 to unlock and root and flash custom recovery. but when i hold power down+volume down i get into the boot loader and i choose recovery then GOOGLE splash screen comes up and it does absolutly nothing while no usb chord plugged in. with usb chord it stays at the google splash screen for but a moment then just boots into android.
i tried the advance utilities and flash the cwm that way but same results. im still on 4.1.0 jrn84d. what am i doing wrong? i don't fully understand adb so if there is quite litteraly a step by step please give me a link or write it down if no such link exists. my last hdd that had adb all setup and ready crashed so its not setup and i was talking to someone who helped me get it going. all i know is i need to use command prompt but getting it into adb and then using it to push and get into cwm i have no clue.
i would love to make a nandroid and then install a kernal to gget the full power out of this thing. it is unlocked and rooted already.
They using ROM Manager app to install CWM and also boot into recovery. Will work for sure as long as you're rooted.
Sent from my SPH-L710 using xda app-developers app
dante32278 said:
They using ROM Manager app to install CWM and also boot into recovery. Will work for sure as long as you're rooted.
Sent from my SPH-L710 using xda app-developers app
Click to expand...
Click to collapse
If you follow the steps correctly, it should have a custom recovery installed. check if your rom is actually rooted.
EDIT: What the hell are you doing on 4.1.0? I thought factory stock was 4.1.1.
Use this:
http://forum.xda-developers.com/showthread.php?t=1809195
Get GooManager from the play store. It can download and install TWRP recovery which I prefer. GooManager will let you reboot into recovery too.
Sent from my Paranoid Nexus 7 using XDA Premium
cakessi said:
EDIT: What the hell are you doing on 4.1.0? I thought factory stock was 4.1.1.
Use this:
http://forum.xda-developers.com/showthread.php?t=1809195
Get GooManager from the play store. It can download and install TWRP recovery which I prefer. GooManager will let you reboot into recovery too.
Sent from my Paranoid Nexus 7 using XDA Premium
Click to expand...
Click to collapse
lol i dunno just came with it. its the 16gb version dunno why it came with 4.1.0 but it did. and when i installed rom manager i flashed cwm with that then choose to boot into recover that way and it worked. i am unlocked and rooted and now have a nandroid. have yet to try going to cwm with power+volume down being pressed i will give it a shot later on and make another nandroid before i accept the update im being propted for.
ty guys for the help.
There was a bug that required the N7 to be connected to a PC-USB connection before it would work. They didn't fix the bug until 4.1.2.
Your best bet, if you can boot into Android, is to download a Reboot-to-Recovery app or use CWM or GooManager to reset into recovery. If you are boot looping, throw a USB connection into the mix when trying to do it. I believe it is VolDown+Power+USB connection. Drivers may also be a factor.
Thanks for the reply. I finally updated it. Had to do three updates though. First to 4.1.1 then to 4.1.2 and then to 4.2. I have a nandroid at 4.1.0 so if I need to do anything I'm just going back. I used ota root keeper and the cwm that's from rom manager allows you to choose to protect your custom recovery as well as root. But I don't know if that was working in tandem with ota root keeper since I made sure to back it up first before I did anything.
Sent from my Nexus 7 using xda app-developers app
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..
So i manage to remover the boot failure on from fastboot mode since it has been there everytime it boots up and it didnt boot up fully but after using droid utility to downgrade to 4.1.2 it no more goes to fastboot but now its stuck on a bootloop and my device is unlocked. So my question is. Can i install a rom to get out of this bootloop or is there any other way to get of the boot loop? Please i really need help!!!!
You should follow this to go back to 4.1.2 I would try to rsd back to whatever firmware you were on or just kk... Do you have a custom recovery on there to try and flash the ROM... What update were you on prior to doing what you did
Sent from my XT907 using XDA Premium 4 mobile app
ezknives said:
You should follow this to go back to 4.1.2 I would try to rsd back to whatever firmware you were on or just kk... Do you have a custom recovery on there to try and flash the ROM... What update were you on prior to doing what you did
Sent from my XT907 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I was running 4.4.2 kk but after ive tried to flash a image by using flasify to remove the boot loader unlocked message but it failed and it would start up on fastboot and thats it but after using droid utility to try to go back to 4.1.2 but after the reboot it stays in the bootloader message. but i do have a custom recovery im using twrp
I'm guessing you didn't make a backup before trying to flash the image... Or at all... I would say just restore your back up... If you want you could try to flash a ROM it would have to be comparable with whatever kernel you have and it may not work as you tried to use (I'm guessing) matt's utility... I would rsd the 4.4.2 firmware or use house of moto... If you want rid of the warning boot logo ATTACK just released some.... Always make a backup before attempting anything of that nature...and if you want to go back to 4.1.2 after the restore follow the method linked above
Sent from my XT907 using XDA Premium 4 mobile app
ezknives said:
I'm guessing you didn't make a backup before trying to flash the image... Or at all... I would say just restore your back up... If you want you could try to flash a ROM it would have to be comparable with whatever kernel you have and it may not work as you tried to use (I'm guessing) matt's utility... I would rsd the 4.4.2 firmware or use house of moto... If you want rid of the warning boot logo ATTACK just released some.... Always make a backup before attempting anything of that nature...and if you want to go back to 4.1.2 after the restore follow the method linked above
Sent from my XT907 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Yeah well for now on ill try to make a backups more often but is there any stock roms availible for my device
Not recovery flashable....you should also search around for yourself more...
Sent from my XT907 using XDA Premium 4 mobile app
LIKEABEAST said:
Yeah well for now on ill try to make a backups more often but is there any stock roms availible for my device
Click to expand...
Click to collapse
I've managed to fix my phone with house of moto and its really useful also I want to thank you by trying to help me