Hi, I've a Nexus1 stock FRF91 ROM Rooted, and with an unlocked bootloader.
I had Amon RA Recovery 2.0 installed and all worked fine. After I known that FRG83D has been released, I've wanted to update to this version. I've tried in many ways, but I've discovered that it needed a stock recovery to flash it. I've tried to restore stock recovery, but now when I try to access it, the screen remain stuck, black, and I must to pull the battery to start a reboot. Could you suggest me how I can repair stock recovery, to obtain latest release?
Just curious, but what version is your bootloader?
Sent from my Nexus One using XDA App
Did you get the stock recovery img from an older build? Is your phone SLCD? If both are true, you flashed a recovery incompatible with your display. Try the recovery from the FRG33 PASSIMG.zip.
Sent from my Nexus One using XDA App
BTW, if you have hboot 0.35, you may not be able to do the PASSIMG...
Sent from my Nexus One using XDA App
he can simply flash a compatible stock recovery through adb
Here is a compatible recovery coming directly from my SLCD phone: http://gravufo.kicks-ass.org/Android/mtd1_Stock_Recovery.img
If you do not have flash_image, get it from here: http://cyanogen-files.carneeki.net/flash_image.zip
Please unzip it and put both the recovery image and the flash_image binary into your SD card and run these commands from your phone terminal emulator or through adb shell in window command line
su
mount -o rw,remount /dev/block/mtdblock4 /system
cat /sdcard/flash_image > /system/bin/flash_image
chmod 775 /system/bin/flash_image
flash_image recovery /sdcard/mtd1_Stock_Recovery.img
rm /system/etc/install-recovery.sh
rm /system/recovery-from-boot.p
How to know if my display is a slcd?
I will try and tell you if resolve
Sent from my Nexus One using XDA App
antognio said:
How to know if my display is a slcd?
I will try and tell you if resolve
Sent from my Nexus One using XDA App
Click to expand...
Click to collapse
http://www.youtube.com/watch?v=gUF4dLVdFKc
RIGHT = SLCD
LEFT = AMOLED
Hy, I have the same problem with my nexus one (from Videotron, Québec)
I try your stock recovery and all I got is this /!\ logo in my screen... Have to take off the batery.
Now, I have 2.2.1 FRG83 ( no D ... )
So I will re-flash amon_ra 2.0... And wait for a solution from other since I'm a newbee in all this.
Gregore said:
Hy, I have the same problem with my nexus one (from Videotron, Québec)
I try your stock recovery and all I got is this /!\ logo in my screen... Have to take off the batery.
Now, I have 2.2.1 FRG83 ( no D ... )
So I will re-flash amon_ra 2.0... And wait for a solution from other since I'm a newbee in all this.
Click to expand...
Click to collapse
Hey Gregore, please check my website, made especially for Vidéotron customers.
There is a tutorial on how to get the stock recovery back in place with the exact same recovery that came with your Vidéotron Nexus One! Check it out, it's the last one...I assume you speak French, since everything is in french there
http://gravufo.kicks-ass.org/android.html
PS: Garde en tête que ce site est hosté sur mon ordi, donc si jamais il est offline, c'est que je dors!
Gregore said:
Hy, I have the same problem with my nexus one (from Videotron, Québec)
I try your stock recovery and all I got is this /!\ logo in my screen... Have to take off the batery.
Now, I have 2.2.1 FRG83 ( no D ... )
So I will re-flash amon_ra 2.0... And wait for a solution from other since I'm a newbee in all this.
Click to expand...
Click to collapse
The /!\ logo *is* stock recovery. Once you've hit that screen, you press some combination of the power button and one of the volume keys, I forget exactly which... try them all out... and you'll hit the stock recovery screen.
cmstlist said:
The /!\ logo *is* stock recovery. Once you've hit that screen, you press some combination of the power button and one of the volume keys, I forget exactly which... try them all out... and you'll hit the stock recovery screen.
Click to expand...
Click to collapse
Oh damn lol I misread his post and thought he wasn't getting the stock recovery in... well yeah, you simply have to press PWR and VOL Down(-) OR VOL Up(+) simultaneously and you'll get in.
Ignore my earlier post then (although there are some interesting if you speak french and want some extremely detailed tutorials on stuff )
hum... so I have all right... sorry bothering you guys, and thank you!
Stock recovery restored succesfully, but I can't obtain FRG83D update
antognio said:
Stock recovery restored succesfully, but I can't obtain FRG83D update
Click to expand...
Click to collapse
Just download it yourself from here: http://android.clients.google.com/p...signed-passion-FRG83D-from-FRG83.ecb21b75.zip
I never understood peoples fascination with the OTA update...
efrant said:
I never understood peoples fascination with the OTA update...
Click to expand...
Click to collapse
Just a feel good freebee...but flashing feels much better
Now I've frf91, I've tried to force update manually but obtain signature error
Sent from my Nexus One using XDA App
antognio said:
Now I've frf91, I've tried to force update manually but obtain signature error
Sent from my Nexus One using XDA App
Click to expand...
Click to collapse
Flash Amom_RA 1.9 recovery and try it again.
efrant said:
Flash Amom_RA 1.9 recovery and try it again.
Click to expand...
Click to collapse
No, that will not work.
You need to manually update to FRG83 before being able to apply this update.
gravufo said:
No, that will not work.
You need to manually update to FRG83 before being able to apply this update.
Click to expand...
Click to collapse
Obviously that depends on which file he is using. If he is using the FRG83D from FRF91 then he does not need to update... but if he is using the FRG83D from FRG83, then yes he does...
efrant said:
Obviously that depends on which file he is using. If he is using the FRG83D from FRF91 then he does not need to update... but if he is using the FRG83D from FRG83, then yes he does...
Click to expand...
Click to collapse
Obviously, but the file you told him to download earlier was from FRG83...skip the attitude, I'm trying to help him, not trying to be mean to anyone.
Related
I just rooted my Nexus 1 Froyo per instructions on theUnlockr.com. I installed ADB first, Then proceded to root. I then flashed a recovery rom: recovery-RA-nexus-v1.7.0.1-cyan.img. This was successful. I then booted phone into recovery mode. Selected recovery and the first couple times I received a black screen with an exclamation point in the middle of a triangle next to green android. I flashed recovery rom once again and this time it allowed me to enter. I made my backup image and even booted into recovery mode again�wiped phone clean and restored image. I thought I was golden! Later I tried to boot into recovery mode again and I received same problem as mentioned above. I tried again no luck. I even flashed recovery rom again and It still dose not work. Why could this be happening? I even went through the steps to root phone again (that went well). But still no recovery mode. I even tried another recovery rom: recovery-RA-nexus-v1.7.0.1.img. It did the same thing. Worked one time and then nothing! I need to fix this before I load custom Roms.
Sent from my Nexus One using XDA App
follow this guide
http://forum.xda-developers.com/showthread.php?t=636795
Amritttt said:
follow this guide
http://forum.xda-developers.com/showthread.php?t=636795
Click to expand...
Click to collapse
I was able to flash recovery via your instructions but phone STILL will not boot into recovery mode. I hold down the volume key and power.....all I get is triangle with droid net to it. Im going to try and Un-root my phone and start from scratch! Thanks for the help!
you are getting the triangle with the droid because the recovery did not flash correctly, try usung rom manager if for nothing else, just to install Amon/clockwork
Poseidon20 said:
I was able to flash recovery via your instructions but phone STILL will not boot into recovery mode. I hold down the volume key and power.....all I get is triangle with droid net to it. Im going to try and Un-root my phone and start from scratch! Thanks for the help!
Click to expand...
Click to collapse
Did you remove the two scripts like you were told? /system/etc/install-recovery.sh and /system/recovery-from-boot.p
you are getting the triangle with the droid because the recovery did not flash correctly, try usung rom manager if for nothing else, just to install Amon/clockwork
Cool thanks for the advice! I did try Rom Manager and used Amon/Clockwork recovery. After flashing the Recovery Image I booted into recovery from Rom Manger. No problem! BUT.....when I rebooted phone from recovery menu I again went in to Rom Manager and tried to Boot back in to recovery and I got the triangle with the Droid next to it. I pulled battery and started phone again. I flashed Amon/Clockwork recovery again from Rom Mang. and again I was able to successfully boot in to recovery. This pattern goes on and on. It seams that every-time I want to boot into recovery I need to flash Amon/clockwork image. Somewhere phone is not retaining the information. Everything looks to work just fine as long as I Flash before I go into recovery. I'm sure this is not the way it should work. Any ideas?
khaytsus said:
Did you remove the two scripts like you were told? /system/etc/install-recovery.sh and /system/recovery-from-boot.p
Click to expand...
Click to collapse
Khaytsus,
When was I told to remove the two scripts? Where did this come from? Please let me know what they are for and why removing them would help? Also, if I do need to remove these would it be done by using Root File Manager, finding file and selecting delete? Sorry if I sound new to this.....it's because I am! LOL. Thanks for any help you can provide!
Try this.
http://forum.xda-developers.com/showpost.php?p=7378018&postcount=47
Poseidon20 said:
Khaytsus,
When was I told to remove the two scripts? Where did this come from? Please let me know what they are for and why removing them would help? Also, if I do need to remove these would it be done by using Root File Manager, finding file and selecting delete? Sorry if I sound new to this.....it's because I am! LOL. Thanks for any help you can provide!
Click to expand...
Click to collapse
It's documented in random places, of course the post below also has the same info. I don't know precisely what the two files do, but they apparently try to restore the recovery.
Trust me, it will fix the problem. Remove them, re-flash recovery.
khaytsus said:
It's documented in random places, of course the post below also has the same info. I don't know precisely what the two files do, but they apparently try to restore the recovery.
Trust me, it will fix the problem. Remove them, re-flash recovery.
Click to expand...
Click to collapse
Khaytsus,
You saved my Droid! You were right! deleting those 2 files worked. I'm well into flashing Custom ROMs. Your the only one who got it right! Good job! Thanks Again!
khaytsus said:
Did you remove the two scripts like you were told? /system/etc/install-recovery.sh and /system/recovery-from-boot.p
Click to expand...
Click to collapse
So, I'm not the OP, but I am having trouble deleting the files despite the fact that they are both say "YES" in read and write in properties. I tried to reflash from ROM Manager and I keep getting an error there. Not sure what to do.
BTW, I'm using a Galaxy Nexus. Would love some help as this is all uncharted terrain for me.
sadako12 said:
BTW, I'm using a Galaxy Nexus. Would love some help as this is all uncharted terrain for me.
Click to expand...
Click to collapse
You are in Nexus One Q&A Forum. Did you tryed with Galaxy Nexus Recoveries files and guides ?
ldFxl said:
You are in Nexus One Q&A Forum. Did you tryed with Galaxy Nexus Recoveries files and guides ?
Click to expand...
Click to collapse
I tried pretty much everything other than wiping the whole thing again. It's quite unfortunate.
sadako12 said:
I tried pretty much everything other than wiping the whole thing again. It's quite unfortunate.
Click to expand...
Click to collapse
If I understand, your problem is that you can't actually flash a custom recovery from ROM Manager ?
Which do you use ?
Are you trying to flash a recovery in recovery mode ?
Please link here files you tried to flash.
ldFxl said:
If I understand, your problem is that you can't actually flash a custom recovery from ROM Manager ?
Which do you use ?
Are you trying to flash a recovery in recovery mode ?
Please link here files you tried to flash.
Click to expand...
Click to collapse
I can't flash from ROM Manager. Initially, I didn't want to purchase the download capability. So, first, I used the program tools and flashed from there. I got Clockwork Mod to work, but then when I restarted it and went into "recovery," I got nothing.
Now, I can't flash at all.
The galaxy nexus should have fastboot capabilities, this is the best and safest way to flash your recovery partition
Be sure to use the proper recovery image for your device
If you need help finding it or setting up fastboot let me know
Sent from my Nexus 4 using XDA Premium 4 mobile app
demkantor said:
The galaxy nexus should have fastboot capabilities, this is the best and safest way to flash your recovery partition
Be sure to use the proper recovery image for your device
If you need help finding it or setting up fastboot let me know
Sent from my Nexus 4 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I have only ever found a guide for a temporary flash. I would follow the instructions and then CWM wouldn't stick. =\
So here is the typical steps to follow
fastboot oem unlock
fastboot flash recovery nameofrecovery.img
And that's it, were you using fastboot to just boot it? Were you doing another method? The more details you give the faster and more accurate your help will be
Sent from my Nexus 4 using XDA Premium 4 mobile app
demkantor said:
So here is the typical steps to follow
fastboot oem unlock
fastboot flash recovery nameofrecovery.img
And that's it, were you using fastboot to just boot it? Were you doing another method? The more details you give the faster and more accurate your help will be
Sent from my Nexus 4 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I used instructions from http://androidforums.com/internatio...root-samsung-galaxy-nexus.html#enter-recovery.
The ROM wouldn't "stick" and then the USB wasn't even recognized by the end of everything.
Start by booting into your bootloader and writing down everything word for word on that screen here. Next boot to recovery and write down what you see there. Even better upload pics of each. Again the more detailed you can be the more help you can get
Sent from my Nexus 7 using XDA Premium 4 mobile app
Hello,
Kind of a noob here. tech-savvy but new with android. Had my N1 for 3 days now.
SLCD version with Amon Ra 1.9.0 alpha recovery. Didn't unlock the bootlader
I'm having fun with custom ROMs. Installed CM6 and now wanted to go back to stock. Didn't realise the FRF91 ROM was not compatible with my SLCD phone and I flashed it on my device. Now it boots into a blank FRF91. I can get it to go into recovery console (power + volume down), but when I select Recovery, I see the nexus on logo and the screen goes black (maybe the recovery is not working anymore or it's juste not showing?).
I can't get adb to work since I need to enable USB Debugging. Is there any way I can enable it without the screen. I don't even know if the touchscreen works (I think it doesn't). So to enable it I need to navigate with the trackball I guess. But I don't know where to go to enable it when I don't see anything.
This is fun and all but I like my phones with something on the screen
Can anybody help?
EDIT RESOLVED :
I used the PASSIMG.ZIP trick to flash a stock rom onto it (FRG33 I think) via the HBOOT menu.
Thank you danger-rat and Jack-R1 for your help!
http://forum.xda-developers.com/wiki/index.php?title=Nexus_One/Recovery_Images
Try the 'blind' version for locked bootloader.
Sent from my Nexus One using XDA App
danger-rat said:
Try the 'blind' version for locked bootloader.
Click to expand...
Click to collapse
I can't get adb to work, it doesn't detect my phone. I guess it's because I haven't enabled usb debugging on the phone or because I'm not root.
How can I do those things without a screen?
You may have lost root when you reverted to stock (was it a rooted stock image?)
What is not working with adb? Have you tried "adb devices"? What response are you getting?
Sent from my Nexus One using XDA App
danger-rat said:
You may have lost root when you reverted to stock (was it a rooted stock image?)
What is not working with adb? Have you tried "adb devices"? What response are you getting?
Sent from my Nexus One using XDA App
Click to expand...
Click to collapse
I flashed a stock rom, yes. So I guess I lost root.
adb devices turns up an empty list of devices.
Did you try to connect ADB when you're booted to recovery?
Jack_R1 said:
Did you try to connect ADB when you're booted to recovery?
Click to expand...
Click to collapse
If he followed the instructions he did...
Sent from my Nexus One using XDA App
I'm not sure he followed the instructions. He might be missing it, or assuming something wrong. So I want to make sure he did...
I thought the same myself...
Sent from my Nexus One using XDA App
Jack_R1 said:
Did you try to connect ADB when you're booted to recovery?
Click to expand...
Click to collapse
By connect I suppose you mean launching the adb app in android-sdk/tools? Then yes I tried it when I was in the HBOOT menu and after when I was in the black Amon_RA recovery. Still no devices detected.
The ROM I flashed was an unrooted stock ROM.
When I boot into the black Amon_RA recovery or the black FRF91, my computer detects the nexus one device that is connected but I can't see it in adb.
It seems I need to enable USB debugging on my black FRF91 and root it to be able to use adb with it.
I hate the 5 min posting limit
The problem is that you don't have the black Amon_RA's recovery. You have the stock FRF91 recovery, because you've flashed a stock image - and it overwrites everything, including recovery. Amon_RA wouldn't require to enable USB debugging to have ADB working in recovery.
I hope you have the ADB driver installed correctly. Please double-check that.
And after you do, if it's installed and you can't do anything - please look at my signature, go to the link, find "unroot / restore your Nexus", and execute. Download the latest FRG83 ROM from HTC, the link is also in the Wiki.
Jack_R1 said:
The problem is that you don't have the black Amon_RA's recovery. You have the stock FRF91 recovery, because you've flashed a stock image - and it overwrites everything, including recovery. Amon_RA wouldn't require to enable USB debugging to have ADB working in recovery.
I hope you have the ADB driver installed correctly. Please double-check that.
And after you do, if it's installed and you can't do anything - please look at my signature, go to the link, find "unroot / restore your Nexus", and execute. Download the latest FRG83 ROM from HTC, the link is also in the Wiki.
Click to expand...
Click to collapse
My drivers are installed correctly, since I used them to flash Amon_RA earlier today.
Gonna try the unroot thing in the wiki.
Tried the superboot and :
I get FAILED( remote : not allowed) in the FASTBOOT USB recovery page
It hangs at downloading boot.img .... on the HBOOT recovery page. Should it take more the 3-4 mins?
On the superboot thread, he says an unlocked bootloader is required. Don't think it will work.
What superboot?
It was "UNROOT", not "ROOT"! Using PASSIMG method.
DO NOT revert HBOOT to older version. I've updated the page.
http://forum.xda-developers.com/wik...des_&_Tutorials#Unroot_.2F_Restore_your_Nexus
Use the passimg method, and use a card reader on your PC to get the zip to your SD card...
I think you want FRG83 (not sure what shipped with the SLCD)?
Sent from my Nexus One using XDA App
FRG83 it is.
Jack_R1 said:
What superboot?
It was "UNROOT", not "ROOT"! Using PASSIMG method.
DO NOT revert HBOOT to older version. I've updated the page.
http://forum.xda-developers.com/wik...des_&_Tutorials#Unroot_.2F_Restore_your_Nexus
Click to expand...
Click to collapse
OK, I'll need to get a SDcard to microSD adapter to try this I guess.
You can always unlock, and use fastboot - but I'm guessing you don't want to?
Sent from my Nexus One using XDA App
danger-rat said:
You can always unlock, and use fastboot - but I'm guessing you don't want to?
Sent from my Nexus One using XDA App
Click to expand...
Click to collapse
You're right, I don't want to
Ok, I downloaded signed-passion-img-FRG83_0923.zip from the htc website, renamed it to PASSIMG.ZIP. Copied it to the root of my sd card then booted into recovery. As soon as it enters it scans for various PASSIMG.XXX files, find the PASSIMG.ZIP file and starts a progress bar which lasts 20 sec. When the progress bar completes, it returns to the recovery menu and I can reboot. It never really asks me anything.
But reboot still leads me to the black screen.
I think it didn't do the update
Kapoue2 said:
When the progress bar completes, it returns to the recovery menu
Click to expand...
Click to collapse
Can you now see the recovery menu, or do you mean boot menu?
Sent from my Nexus One using XDA App
Here it is:
http://www.mediafire.com/?511onap95wh90zv
No apparent new features, just bugfixes.
(Compiled by Mur4ik)
This must mean an update swiftdroid will come soon.
Sent from my GT540 using XDA Premium App
It doesn't meant it lol. I has been released several days ago (about week ago).
It does mean that Mur4ik is syncing and compiling CM7 code while "on a break" - this recovery was posted on 2nd April. I'd say that's pretty positive
How to install that CloclkworkMod Recovery?
tata78 said:
How to install that CloclkworkMod Recovery?
Click to expand...
Click to collapse
put your phone into fastboot mode (hold camera button and press power)
connect to pc
open a terminal in the directory where the recovery image is and type:
fastboot flash recovery recovery_clockwork_3.0.2.4_swift.img
I am sorry for questions, but how to put in fastboot? When I press camera and power it starts normaly.
tata78 said:
I am sorry for questions, but how to put in fastboot? When I press camera and power it starts normaly.
Click to expand...
Click to collapse
Sounds like you don't have fastboot. What ROM do you have flashed on your phone? Is it a stock Android version 1.6, 2.1 or do you have a custom ROM 2.1, 2.2 or 2.3? You need a custom ROM with fastboot mode enabled - an explanation of this is beyond the scope of this thread. Try this thread to flash a 2.1 ROM with fastboot enabled. Sorry to be brief but there are tutorials on flashing recovery images and this thread is really just a newsflash for a new release... HTH
I have stock rom 2.1. I did not flash anything yet exept root.
tata78 said:
I have stock rom 2.1. I did not flash anything yet exept root.
Click to expand...
Click to collapse
If you have a stock rom you can't flash recovery because you don't have fastboot.
fdespotovski said:
If you have a stock rom you can't flash recovery because you don't have fastboot.
Click to expand...
Click to collapse
You CAN flash recovery with a non-fastboot enabled ROM. Here's the tutorial:
JackG from MoDaCo said:
Yes there is, make sure you have the fastboot rom flashed and you are rooted, and download something called "flash_image" (from the attachments below) and put it in the root of your SD Card, get your recovery image in the root of the card too.
Then, download Terminal Emulator from the market when it opens press the menu button and select "Toggle Soft Keyboard" when the keyboard comes up type in
CODE
su
cd /sdcard
chmod 755 flash_image
./flash_image recovery /sdcard/recovery.img
(Change the recovery.img to the name of your recovery image eg. recovery_clockwork_2.5.1.8_swift.img or recovery_clockwork_2.5.0.5_swift.img)
Then, reboot the phone, and hold down the Menu+Power and you should be welcomed with the Clockwork menu.
Click to expand...
Click to collapse
despotovski01 said:
You CAN flash recovery with a non-fastboot enabled ROM. Here's the tutorial:
Click to expand...
Click to collapse
Ok I didn't know about that.
@despotovski01 @fdespotovski very simalar names aren't you the same man???
ZduneX25 said:
@despotovski01 @fdespotovski very simalar names aren't you the same man???
Click to expand...
Click to collapse
They're brothers, I think...
ZduneX25 said:
@despotovski01 @fdespotovski very simalar names aren't you the same man???
Click to expand...
Click to collapse
there brothers lol
Sent from my GT540 using XDA Premium App
Is it worth flashing new recovery, if no new update? Will my backups still run ok got clockmod...3.0.1.4...what's new dude? See you got rid of that Joestones clean Ginger.any reason? Cheers m8....:-d
Sent from my GT540 using XDA Premium App
deamonjones said:
Is it worth flashing new recovery, if no new update? Will my backups still run ok got clockmod...3.0.1.4...what's new dude? See you got rid of that Joestones clean Ginger.any reason? Cheers m8....:-d
Sent from my GT540 using XDA Premium App
Click to expand...
Click to collapse
It's compatible. Flash if you like to have the newest of everything
Bugs have been fixed but I don't know what...
I stopped using Joe's ROM because I ran out of space for all my apps. I'll still try his new releases though!
Sent from my GT540 using XDA Premium App
ZduneX25 said:
@despotovski01 @fdespotovski very simalar names aren't you the same man???
Click to expand...
Click to collapse
We're brothers.
That's cool
Hi, can i check whether how do i install clockworkmod Recovery mode into my GT540? I'm in stock 1.6 now.
Hi, i've decided to jump off the official rom and go to custom, i've decided to go with MIUI
I just wanted to ask a few questions.
After looking on the website, i found out that it comes with its own recovery, do I have to install this to get OTA updates? or could I just install updates with my own recovery image? (I have 4EXT)
Also, is there any other good roms you recommend?
I also don't want to jump into changing partitions (yet)
EDIT: I have made a nandroid backup and i'm ready to go, I just wanted to ask, I currently have the rom GRJ22, I had a look on the internet for it and on this forum and I have downloaded the image incase I want to revert it
the file I have is called: "PASSIMG_Passion_Google_WWE_3.10.1700.1_GRJ22_release_signed.zip" Is this right? it was from shipped-roms.com
After looking on my phone the 3.10... part is the build number, mine is 3.11... does this make a difference?
Make a nandroid backup before you flash.
That's it.
OOPS double post
I have, I just want to make sure that I can get the rom my phone is running now
but I think I might just flash now as its only the build number thats different. specified in my first post. I have also seen that the recovery doesn't matter
Ok then, I am going to flash this rom now but I have a small problem
I have 4EXT as my recovery, when I select recovery when I turn my phone on (Power + trackball) I get a picture of an android and an exclamation mark
I know I have recovery, as I can load it through the 4EXT app, how EXACTLY do I access it through the other menu, as I would need this incase somthing goes wrong
Ok then. I tried going into my bootloader again so i reflashed it.
After this it worked. So i waited for my phone to load up then i tried again and it diddnt work!
Sent from my Nexus One using XDA App
If you get the android with the question mark, it means your recovery got reverted back to stock. You no longer have 4EXT on there. You will need to reflash it before you can do anything else.
Why does it keep reverting. How can i stop it?
Sent from my Nexus One using XDA App
Just tried it again and the same thing happened on the second load. Whats happening?
Sent from my Nexus One using XDA App
Because you didn't listen, and didn't make nandroid backup, but tried flashing a stock ROM instead. It overwrites the recovery. Not a smart move - you don't have custom recovery anymore, and need to reflash it.
You might want to spend some more time reading and understanding, what nandroid backup does, what flashing a ROM does, and why you shouldn't be flashing stock ROMs unless you want your phone completely back to stock.
Warmo161 said:
Just tried it again and the same thing happened on the second load. Whats happening?
Sent from my Nexus One using XDA App
Click to expand...
Click to collapse
Have you tried installing ROM Manager and flashing Clockwork recovery?
Sent from my Sexynos SGH-i777 using XDA Premium.
I havent changed the rom at all and i did make a backup. All i need to do is sort out the recovery
Sent from my Nexus One using XDA App
wrenchmonkey26 said:
Have you tried installing ROM Manager and flashing Clockwork recovery?
Sent from my Sexynos SGH-i777 using XDA Premium.
Click to expand...
Click to collapse
Yep. It diddnt work so i movrd to 4ext
Sent from my Nexus One using XDA App
Warmo161 said:
I havent changed the rom at all and i did make a backup. All i need to do is sort out the recovery
Sent from my Nexus One using XDA App
Click to expand...
Click to collapse
The ROM comes with it's own recovery, which would explain why this is happening. Make sure you read the entire thread for that ROM. The best way to get into recovery on a MIUI ROM is through the MIUI power button.
Sent from my Sexynos SGH-i777 using XDA Premium.
Ok, I don't know if my messages I posted were understood so i'll do it again
I am on the STOCK rom atm and am trying to go onto MIUI
After flashing 4EXT, I reboot my phone and load up the recovery, which works for the first time, after my phone boots up, I turn it off and try it again and it loads to the stock recovery
All I want is to find out why it does this and fix it so I can install custom roms, as I dont really trust it as if somthing goes wrong then i'm stuck
I was thinking it could be because my bootloader is still locked or the OS reflashes it on bootup but that was just a guess
When you are running stock, anytime you reboot, the stock OS checks the recovery, and if it is not the stock recovery, it reflashes it. There are files you have to remove to prevent this from happening, but I can't remember which ones they are.
bassmadrigal said:
When you are running stock, anytime you reboot, the stock OS checks the recovery, and if it is not the stock recovery, it reflashes it. There are files you have to remove to prevent this from happening, but I can't remember which ones they are.
Click to expand...
Click to collapse
Now we are getting somewhere!
right, im gonna look now
Theres an image you can flash that I found on the wiki, but is there any other way to do it? Like deleting the files yourself or downloading an app to do the job??
Warmo161 said:
Theres an image you can flash that I found on the wiki, but is there any other way to do it? Like deleting the files yourself or downloading an app to do the job??
Click to expand...
Click to collapse
I did some digging and I think this is all you need to do from your computer.
Code:
adb shell
su
mount -o remount,rw -t yaffs2 /system
rm /system/etc/install-recovery.sh
bassmadrigal said:
I did some digging and I think this is all you need to do from your computer.
Code:
adb shell
su
mount -o remount,rw -t yaffs2 /system
rm /system/etc/install-recovery.sh
Click to expand...
Click to collapse
What does the command do?
And what would happen if I just move/delete the "install-recovery" file
That reminds me, I have to set up adb...
Hello,
I have a xt860 Bell/ca phone.
I see updates available but with clockworkmod I cannot install them.
- Is there a way to go back to stock recovery?
Thank you!
Yess press x+power (then press both vol+ and- ) or m+power (I don't remember) when the phone is off
DoubleYouPee said:
Yess press x+power (then press both vol+ and- ) or m+power (I don't remember) when the phone is off
Click to expand...
Click to collapse
Hello,
x shows an exclamation mark and a little android.
m launches a menu and when I choose recovery it does the same
This suggestion is aimed at rebooting entering stock receovery? I guess it is gone and there is only cwm... any way of restoring the original one?
Thanks!
#G# said:
Hello,
x shows an exclamation mark and a little android.
m launches a menu and when I choose recovery it does the same
This suggestion is aimed at rebooting entering stock receovery? I guess it is gone and there is only cwm... any way of restoring the original one?
Thanks!
Click to expand...
Click to collapse
press vol +- at the same time when you see the little android
Stock recovery is not removed y installing CWM, from the exclamation point screen press volume up and volume down together. If you are trying to accept the OTA you need to remove the hijack and modified logwrapper. I cannot for the life of me remember where they are located.
Sent from my XT860 using xda premium
Endoroid said:
Stock recovery is not removed y installing CWM
Click to expand...
Click to collapse
this i great news to read
Endoroid said:
If you are trying to accept the OTA
Click to expand...
Click to collapse
yep this is what I am trying to do
Endoroid said:
you need to remove the hijack and modified logwrapper. I cannot for the life of me remember where they are located.
Click to expand...
Click to collapse
this is where I need help / specific hints.
If there was SBF I'd restock the whole phone and start from there.
I read there is no Bell SBF.
What steps can I take then?
I have no clue I think I used odin or similar to flash CWM...
Please share any ideas.
Thanks!
G
#G# said:
this i great news to read
yep this is what I am trying to do
this is where I need help / specific hints.
If there was SBF I'd restock the whole phone and start from there.
I read there is no Bell SBF.
What steps can I take then?
I have no clue I think I used odin or similar to flash CWM...
Please share any ideas.
Thanks!
G
Click to expand...
Click to collapse
Odin is a samsung thing. there are no fastboot files(sbf)for bell. If you end up bricked there are fastboot files for other carriers you can use to recover, but atm you can't get back to bell.
CWM installs through an apk on the xt860…I don't know how you would flash it on to the phone.
I'll look for those files after work
Sent from my XT860 using xda premium
Endoroid said:
Odin is a samsung thing
Click to expand...
Click to collapse
Yep I've been fixing samsungs and motorolas lately this is springtime for my devices
Endoroid said:
CWM installs through an apk on the xt860…I don't know how you would flash it on to the phone.
Click to expand...
Click to collapse
I'm wrong then (worked on it 2 months ago and have a goldfish's memory
I rooted and CWMed readin on xda anyway 0-)
Endoroid said:
I'll look for those files after work
Click to expand...
Click to collapse
yyyes! thank you in advance )
any hints/news?
Hello,
Any news/hints?
Thanks
2nd-int and hijack.killall can be found in /sbin. Take those files out and it may work. I suggest moving them to your sdcard rather than deleting them just to be safe. Did you use bootstrap, safestrap or rom manager to install CWM?
Sent from my XT860 using xda premium
I think I have what you need...
http://forum.xda-developers.com/showthread.php?t=1449027
That is a dd image of each of the partitions.
You should try to apply the stock recovery partition first, so download the 4th link unzip it then copy the recovery partition to the SDCard, then run the command as root (in block 1), from your computer with ADB connection to it:
Code:
adb shell
su dd if=/sdcard/recovery-mmcblk1p16.img of=/dev/block/mmcblk1p16
Try to restart into recovery mode and see if it works.
If it still isn't working, you can put back the factory image of the /system by downloading the 3rd link, then copying the *EXTRACTED* file to the sdcard then run the following command from your computer with ADB connection to it:
Code:
adb shell
su dd if=/sdcard/system-mmcblk1p21.img of=/dev/block/mmcblk1p21
I'm not responsible if it bricks your phone, but I'm *pretty* sure it wil work. I've given the same instructions to another user before and it worked fine.
See this : http://forum.xda-developers.com/showthread.php?t=1340492
Hello!
fyi in /sbin I only find:
-rwxr-x--- root root 117976 1970-01-01 01:00 adbd.old
lrwxrwxrwx root root 1970-01-01 01:00 ueventd -> ../init
and doing a search (find command missing on cli, used root total commander) returned no results.
I do not remember what I used to install CWM, probably a guide on xda found at the beginning of december / pete tools I think.
@Danifunker, I cannot download anything since fbi blocked Megaupload. (
[edit] users from Holland could find just Megaupload in mirror page.. using it from IT I could see all other mirrors.
First result dd if=[...]/recovery-mmcblk1p16.img of=/dev/block/mmcblk1p16 = still CWM, now downloading system
Yay! Second result = dd if=/path/to/system.image of=/dev/block/mmcblk1p21 = perfect!
Thanks, super thanks If you hadn't done this dd image I would have been stuck I guess.
Now I have the 2.3.6 latest stock rom;
I'll do a dd of /dev/block/mmcblk1p21 for system
mmcblk1p23 for preinstall (and understand how to restore it / with what aim)
mmcblk1p22 for cache (what is the use of this iyo? Shouldn't we just clear cache partition?)
in all the rest: what can actually be used and for what?
and what else?
Once done I'll multiupload them