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
Hey XDA
Iv had my Nexus 7 for a day now and am dying to root and mabe install CM10
i currently have a Samsung Galaxy S3 with CM10 on it...thot its extremly buggy sadly... anyways i have been looking up on how to root the nexus 7 but i need to know if i can instead of using toolkit can i instead just use odin to flash stock rom and cwm and so on instead of having to unlock the device?
i am used to using odin for flashing and cwm but here the nexus is close to the same with htc one x in the way it has that fastboot thing and from what iv heard the nexus 7 requires unlock before it can be rooted, also is the tookit the best way to unlock and root the device?
also does unlocking break the warrenty and if i ever decide to return to stock unroot how do i flash stock rom back onto the device? am not sure where i would find the stock roms for it and also can odin be used to flash it...:S
i hate sounding like a noob lol
ok iv used the toolkit 2.0 and its worked great so far...im stuck at not being able to boot into cwm recovery
it installed fine thru the toolkit but whenever i try to hold up and power i cant get it to boot into cwm recovery...
i tryed to reinstall again but still cant get it to boot into cwm am i doing something wrong?
Doing the following won't cause you to loose warranty:
- Unlocking the bootloader
- Rooting
- Flashing custom ROM's and Kernels (however, if you flash a custom kernel that causes your device to explode... I'm somewhat certain this won't be covered)
However, if you are doing anything like that, and have to send the device in for warranty, you "should" factory restore it. Google provides Factory Images for the Nexus 7, which can be restored to your device with semi-ease.
I use this guide to factory restore: http://forums.androidcentral.com/ne...ide-factory-image-restore-your-nexus-7-a.html Some filenames might need changed though since I think that guide is based off an older factory image (instructions are the same though).
There is a good chance a toolkit also has an easy method for factory restoring, but I don't recommend this at all.
Stop using toolkits.
Sent from my Nexus 7 using Xparent White Tapatalk 2
ÜBER™ said:
Stop using toolkits.
Click to expand...
Click to collapse
Amen, +1. http://forum.xda-developers.com/showthread.php?t=1830108
encryptioncsta said:
ok iv used the toolkit 2.0 and its worked great so far...im stuck at not being able to boot into cwm recovery
it installed fine thru the toolkit but whenever i try to hold up and power i cant get it to boot into cwm recovery...
i tryed to reinstall again but still cant get it to boot into cwm am i doing something wrong?
Click to expand...
Click to collapse
I've never used a toolkit before (until this issue had me stuck). I'm unable to get the Nexus 7 to book into recovery (CWM) after flashing it via fastboot. After giving up, I rooted it using the toolkit.. scariest thing I've ever done.. it did work.. but I'd like to get to the bottom of why a number of people like me seem to be having issues flashing and booting CWM on the Nexus 7.
Did you rename the original system/recovery to .bak first?
Travisdroidx2 said:
Did you rename the original system/recovery to .bak first?
Click to expand...
Click to collapse
No, I flashed it as I normally do.. using the .img file. In this case, CWM.. recovery-clockwork-6.0.1.0-grouper.img
Why would renaming it to .bak be needed?
xyzulu said:
No, I flashed it as I normally do.. using the .img file. In this case, CWM.. recovery-clockwork-6.0.1.0-grouper.img
Why would renaming it to .bak be needed?
Click to expand...
Click to collapse
Its not actually.
Sent from my Nexus 7 using Xparent White Tapatalk 2
I had to rename the stock recovery under system to .bak before I could get twrp to work. Or else when I went into recovery it would get stuck on the android.
But I see you are using fast boot it should write over it.
Travisdroidx2 said:
I had to rename the stock recovery under system to .bak before I could get twrp to work. Or else when I went into recovery it would get stuck on the android.
But I see you are using fast boot it should write over it.
Click to expand...
Click to collapse
I didn't have to. Flashed twrp and forgot to put a ROM on it and went back into recovery and it was twrp still.
Sent from my Nexus 7 using Xparent White Tapatalk 2
I should of just flashed the image file and flashed it myself but I was in a hurry and used goo im and it bit me in the ass. Lesson learned.
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
I just installed TWRP on my N4 and have never used it before. I always used CWM and I just wiped it through recovery. My issue is that I wiped EVERYTHING. It says "no OS detected" and won't boot past the Google logo. Can't install drivers when connected to the computer, and I can't for the life of me figure out how to flash a stock image, or fix it with the nexus root toolkit. Could someone PLEASE give me a walkthrough for a noob of how to go about fixing this? I don't understand a lot that deals with ADB and all that. Thank you.
Sent from my Z665C using xda app-developers app
Google tool adb fastboot drivers. Then Google nexus 4 factory image and download that. Use 7-zip to extract it. Flash the flash-all.bat while your phone is in fastboot mode and connected to your pc
Sent from my Nexus 5
Do I she the factory image it originally had which was 4.2.2 or do I use the image I updated to which was 4.3? Don't know if it matters, but I've never done this so I don't want to make anything worse.
Sent from my Z665C using xda app-developers app
If you don't understand, this time right now seems a good reason to learn about it right?
As to you problem, can you boot into recovery..the twrp? If yes, then it is easy. Just sideload a rom (preferably a 4.2.2 rom as it was the last rom on your device). Oh and yeah, sideload does use a bit of adb command (see how important it is for us, the nexus user?).
The other way is to simply use toolkits (which is a shortcut, not good as you will learn nothing of the whole process and it just takes all the fun away). Look in original android dev section for wugfresh toolkits (but I really, really, really hope that you learn ADB. After all, we need to learn to count before we start using a calculator right? ). Good luck. Don't sweat it so much.
p/s: That video there can be used for any android version and any rom of nexus 4.
Sounds easy enough. My only issue has been that I couldn't install any drivers. I can boot into twrp, but that's it. Any guide I've researched says to turn on USB debugging, which I can't figure out how to do since it won't boot past the Google logo, and the drivers won't install correctly when I connect the nexus to a computer.
Sent from my Z665C using xda app-developers app
Use wugfresh nexus root tool kit to flash a stock rom.
USB debugging is not required to flash a stock ROM via fastboot.
sinndissension said:
Sounds easy enough. My only issue has been that I couldn't install any drivers. I can boot into twrp, but that's it. Any guide I've researched says to turn on USB debugging, which I can't figure out how to do since it won't boot past the Google logo, and the drivers won't install correctly when I connect the nexus to a computer.
Sent from my Z665C using xda app-developers app
Click to expand...
Click to collapse
The easiest in my opinion would be sideloading a new rom, like cm11, paranoidandroid etc. Then you could easily install it on your n4
See here how to do it: http://teamw.in/ADBSideload , http://forum.xda-developers.com/showthread.php?t=2559200 , http://forum.xda-developers.com/showpost.php?p=45798359&postcount=825
Tried the toolkit yesterday. Didn't work because it couldn't install the drivers
Sent from my Z665C using xda app-developers app
Install drivers manually. Just Google "nexus 4 USB drivers" download and install. Then get toolkit and flash stock image.
Sent from my Nexus 4 using xda app-developers app
I'll try again. I was able to figure the drivers out. Tried flashing a stock image I downloaded, but I still wouldn't boot past the Google logo. I flashed it to the system partition, but I didn't know what partition to flash it to. Do I need to use the modified boot image it wants me to download, or am I supposed to flash it to a certain partition?
Sent from my Z665C using xda app-developers app
FIXED IT!!! thank you all for your help.
For anyone else with this problem, I downloaded "universal naked drivers" and installed them manually, use the Nexus Root Toolkit selected "soft brick, than flash stock/unroot, let it download RETORT and the modified boot image, flash it in fast-food, then when it booted up, re-rooted. (You lose root access when you do this).