Hey, I have been messing around with my phone recently, and I have gone to the OTA update after I had root, to check it out. Well I decided to root again, so I was at RC30 and the build is JFv1.3. Now, I put on Haykuro's 6.0R1 (Uses new SPL) my memory card, as update. I tried to do it, but it didn't work. Now I am stuck in a JFv1.3 Recovery screen. No matter what I do, I can't get out. Does anyone have any advice? I would appreciate it, because I have been looking online for the past hour to fix it.
Thanks,
Chris
Ok lets get some more information:
Is the recovery screen responsive or frozen?
If it is responsive make sure you have the update.zip on your phone and and do an Alt+W to wipe all data and the Alt+S to install the update.
If it is NOT responsive then your recovery image is corrupted and you need to re-install it.
This will require fastboot, if you search around you can find it, and if you are in windows you will need the usb drivers.
You need to download the JF recovery image which should be called recovery.img
Put it in the same folder that has the fastboot files in it.
Boot the phone into fastboot mode (Camera+Power)
in the terminal(linux) or CMD(windows) type
1. fastboot erase recovery - erases the broken one
2. fastboot flash recovery recovery.img - puts the new one in
3. fastboot reboot - reboots the phone
then you can install the new ROMS if you want.
Post back with any other problems.
Related
Overview
I upgraded a Holiday N1 from ERD56C to Stock ERE27 today without a SIM, and thought the instructions might be useful for someone else. This should update any version to ERE27. The phone does not need to have the bootloader unlocked to do this.
I collected the necessary files into one zip to make life a little easier as well, you can find it below.
These instructions will wipe your phone! You may not need to wipe/factory reset so you could try skipping it, but if you have force closes you may just need to wipe.
Instructions
First, grab and extract the zip file in this post. You'll also need fastboot for your operating system.
http://www.overridex.net/files/ERD56C_to_ERE27.zip
md5sum: 6a6a3de5707b3e84a2f4fd581b8604dc
1) Boot your phone while holding down the trackball to boot into the SPL and plug your phone into your computer via USB. It should say fastboot usb on the screen.
2) Run 'fastboot devices' to ensure your phone shows up.
3) Run the following commands to flash the images from the zip file. YES the hboot is the engineering SPL, not the ship one. Mine was an older version and wouldn't apply the update without 0.33.2012.
Code:
fastboot flash boot boot.img
fastboot flash splash1 splash1.img
fastboot flash system system.img
fastboot flash userdata userdata.img
fastboot flash hboot hboot-0.33.2012.img
4) Reboot the phone, then select to mount the SD card from the notification bar once it's booted back up.
5) Copy signed-passion-ERE27-from-ERD79.a487b405.zip to the SD card and rename it to update.zip
6) Reboot the phone while holding the volume down button. Press volume down, then power to select recovery.
7) Once in recovery (the android with the warning triangle) press volume up + power once or twice until you get a menu. Use the trackball to select apply update.zip, once it completes select wipe data/factory reset and wipe cache for good measure. Select to reboot the phone.
It will then write the radio image, and reboot to a screen of a android with an arrow out of a box while it updates the radio, it will then reboot a couple of times before fully booting up. This is normal.
That's it, you'll be on the latest ROM with lots of bug fixes, dock settings and multitouch to pinch and zoom to your heart's content.
Resources:
http://android.modaco.com/content/g...te-zip-online-kitchen-optional-root-insecure/
http://android.modaco.com/content/g...d-and-unrooted-optional-radio-optional-himem/
http://forum.xda-developers.com/showthread.php?t=628916
Does this unlock bootloader and void warranty?
Of course it does.
You couldn't find any older post to bring up?
It's from February 6, dealing with both stock and update versions of long-time-irrelevant Eclair (2.1)...
meravnooyi said:
Does this unlock bootloader and void warranty?
Click to expand...
Click to collapse
Holiday Nexus Ones are the development model given generally to Google employees... Their security is off so you can unlock and relock the bootloader freely, they don't have a warranty anyway.
These are not the retail Nexus One phones.
-Dan
Reply long overdue. Thanks mate. You were a life saver.
Bought a brand new unused Holiday N1 from ebay. Was stuck in some unknown android version. This post saved my life.
Today I tried to change ROM in my G1. With that I also wanted to change SPL and recovery. It was my first conact with flashing that phone. I flashed Samsung i7500 before, so I have some Android experience.
Recovery and SPL went OK. When I was flashing ROM, something has gone wrong, so I decided to restore nandroid backup I made before flashing new ROM. When I restored backup, system didn't load. It stops on "Android" text or on black screen. Recovery also got lost (I don't know how) - now I can see only picture with triangle and "!" sign.
First thought I have was to use fastboot to flash new recovery and have it working. But there is my problem - when I enter fastboot mode, PC doesn't see any new device. There is no difference in device manager when phone is connected or not. When I turn phone on normally (so system's stops loading on Android text), it's recognized by PC.
Have anybody had such problem? What should I do to restore recovery or flash working rom?
What ROM u trying to flash? Some ROMs need some base files. You can even install a new Recovry Image through Recovery Console. Thats what I did
OK, What SPL you have right now...
Once you flash new SPL, old nandroid might not work properly as the partition layout has been changed....
Let us know the SPL you have now, sometimes if the phone is not getting recognized..then you have some old driver installed, try to see if that's the issue...
ms93 said:
Today I tried to change ROM in my G1. With that I also wanted to change SPL and recovery. It was my first conact with flashing that phone. I flashed Samsung i7500 before, so I have some Android experience.
Recovery and SPL went OK. When I was flashing ROM, something has gone wrong, so I decided to restore nandroid backup I made before flashing new ROM. When I restored backup, system didn't load. It stops on "Android" text or on black screen. Recovery also got lost (I don't know how) - now I can see only picture with triangle and "!" sign.
First thought I have was to use fastboot to flash new recovery and have it working. But there is my problem - when I enter fastboot mode, PC doesn't see any new device. There is no difference in device manager when phone is connected or not. When I turn phone on normally (so system's stops loading on Android text), it's recognized by PC.
Have anybody had such problem? What should I do to restore recovery or flash working rom?
Click to expand...
Click to collapse
I have installed haykuro SPL as I remember right.
I tried to update SDK and its USB drivers, but no result.
I remember also, that "USB debugging" wasn't on - maybe that's why phone in fastboot isn't recognized on PC?
To be clear: when I plug USB cable in fastboot mode, PC doesn't show that there is some new device. It acts like no device was connected to it.
There are other new and safe method to achieve the same or more then what you are trying to achieve with Haykuro SPL...see here..Custom MTD
But anyhow you are stuck with it...when you say Phone is not getting recognized..try restarting the phone in fastboot mode while connected to PC...when you are pressing back button are you getting fastboot..
I am not a good person to suggest something on this...If I would have been in your place I would have flashed DREAMIMG.nbh file and would have started from start....but wait till somebody better will tell you how to recover the device....
ms93 said:
I have installed haykuro SPL as I remember right.
I tried to update SDK and its USB drivers, but no result.
I remember also, that "USB debugging" wasn't on - maybe that's why phone in fastboot isn't recognized on PC?
To be clear: when I plug USB cable in fastboot mode, PC doesn't show that there is some new device. It acts like no device was connected to it.
Click to expand...
Click to collapse
G1sanju, I don't know what to say!
You saved my phone
Flashing DREAMIMG.nbh helped, phone has booted
OK, I have a new problem now.
Recovery is still not working - I have Android 1.0 in phone.
Fastboot is still not recognized by PC, so I can't flash it. I don't have root, so I can't flash recovery by terminal - is there any Android 1.0 root instruction?
Or maybe DREAIMG.nbh of 1.5 or 1.6 ROM?
EDIT:
Now everything works, I flashed recovery using telnet.
DREAMIMG.nbh is an default image for G1, so it remove root access and leave the phone with the stock image...now you have 1.x radio and stock SPL...flashing haykuro SPL right now can brick your phone....
unlocker.com has some good guide to get the root access if you are looking for it....
Do not flash the Haykuro SPL or DangerSPL......That's of no use now....also there are chances that it can brick your phone....
Use Safe SPL...1.33.2003 those are full engineering SPL with fastboot access....
use CustomMTD to get the increase size as mentioned in my post above...
ms93 said:
OK, I have a new problem now.
Recovery is still not working - I have Android 1.0 in phone.
Fastboot is still not recognized by PC, so I can't flash it. I don't have root, so I can't flash recovery by terminal - is there any Android 1.0 root instruction?
Or maybe DREAIMG.nbh of 1.5 or 1.6 ROM?
EDIT:
Now everything works, I flashed recovery using telnet.
Click to expand...
Click to collapse
I installed recovery via telnet, then changed radio, installed CustomMTD and ROM. All working fine.
Its great that you have used customMTD rather then Haykuro SPL...this is safe method....I just warned you because that's a very common way to brick the phone....flashing NBH and then installing SPL assuming you have the correct radio is a very common way of bricking the phone...
Also if you are playing with SPL and radio's then its advisable to erase the recovery first...then do the install from fastboot and then reinstall recovery...
ms93 said:
I installed recovery via telnet, then changed radio, installed CustomMTD and ROM. All working fine.
Click to expand...
Click to collapse
Hi,
I bought a faulty Nexus one from ebay, thought I can fix it, as I did buy a faulty desire from ebay and was able to fix it. This time im not so lucky I guess.
So here it is:
The phone is stuck at X when booting normally.
I can access HBoot (But not Hboot USB Plug, because USB debugging is not enabled) and Fastboot USB. I unlocked Hboot. Fastboot in PC recognizes the phone but ADB does not as usb debugging is not enabled.
The phone is not Rooted
Here are my ideas so far:
Get somehow debugging on with some commands (No luck from reshearching in google)
Reflash stock rom with PASSIMG.ZIP in sdcard, but my phone does not recognize the file from my sdcard (I'm pretty certain im doing something wrong or my idea is somehow wrong)
Flash new images through FASTBOOT, but every time Signature check fails (Shipped-roms.com).
Root with superboot, but signature check failed here too.
Flash a recovery, signature check fails.
I will reguraly update my tries
Please suggest correction to my ideas or suggest new ones!
Help will be much appreciated!
I admit it, the phone might be briked, but I want to make sure that I have tried everything before I abandon this project.
And ofcourse I have no Warranty.
What file are you using for passimg.zip? Make sure it's not a zip inside a zip.
What images are you using via the fastboot flash command?
Sent from my Nexus One
You didn't unlock the bootloader, it seems - because if you did, it wouldn't be checking signatures, and you'd be able to flash anything.
First of thanks to both of you for helping.
I'm pretty sure that i do not have zip inside zip and I downloaded them from shipped roms.com -> android -> Passion-> PASSIMG_Google .... .ZIP, (Then renamed it ofcourse) Is there a difference what version of android i use?
The issue with this is, it checks the SD CARD and does not find anything. I have seen from google that the most common issue is that it starts to check the .zip file but then aborts. Does the SDCARD have to be a goldcard (I do have a goldcard but it might be faulty, right?)
I tried fastboot flash PASSIMG_Google.... .ZIP; Fastboot Flashall ( With having boot, recovery, system in my fastboot folder)
Maybe I should try to flash everything the .zip has in it seperately because that succeded for boot, system and recovery but I was too afraid to flash every partitation (Like Radio which seems to be the scariest and the most easiest way to brick phone)
For the third answer, I have ***UNLOCKED*** in bootloader in purple and top on the screen.
Once again thanks and keep suggesting!
Unpack the ZIP and flash each image separately.
Leave the radio as is, if it's updated enough (5.08 or 5.12). In any case, fastboot won't allow you to flash bad radio - and the risk of bricking the phone using fastboot is near 0.
For passimg.zip, you need to download the FRG33 shipped ROM from shipped-roms.com then EXTRACT the zip file that is inside the zip that you downloaded. Rename that file to passimg.zip
For fastboot, flash boot and system seperately.
When you boot the device normally, do you see the lock icon below the four colored x?
Sent from my Nexus One
Okay,
Did it one by one (PASSIMG_Passion_Google_WWE_2.16.1700.1_FRG33_release_signed.zip):
Succeeded:
Boot, Recovery, System and Userdata (that was only 3Kb)
Failed with signature check (Remote:Signature check failed):
Splash1, spcustom,
Did not do:
Radio
I'm going to post more details:
When booting up, it displays the X normally with the unlocking badge on the bottom of the screen and vibrates once. Then it goes black for a second or even less, the same images comes on and then it vibrates 6-7 times.
now that you successfully flashed the stock recovery, cam you boot into it?
Sent from my Nexus One
Nope, it does that what I described on the previous post
Oh and what's more it randomly during no activity being in fastboot vibrates as well for 5 times or so. It does this rarely but it's there
http://forum.xda-developers.com/showthread.php?t=710937
Thanks, Well thats it then for now, just have to figure out what to do now
Sounds like you need to get the PASSIMG.zip method to work, or unlock and flash a new recovery like amon ra, and flash a full rom with sig checks off.
siimplangi said:
Nope, it does that what I described on the previous post
Oh and what's more it randomly during no activity being in fastboot vibrates as well for 5 times or so. It does this rarely but it's there
Click to expand...
Click to collapse
Ok, but can you boot into recovery? In other words, boot into the bootloader and select recovery.
any solution?
efrant said:
Ok, but can you boot into recovery? In other words, boot into the bootloader and select recovery.
Click to expand...
Click to collapse
hi guys.i have exactly same situation.
does anyone have a solution fir this?
kobi_eidelman said:
hi guys.i have exactly same situation.
does anyone have a solution fir this?
Click to expand...
Click to collapse
Did you try all the solutions suggested above (passimg, fastboot flash, etc)? If yes then no I don't think so.
Hi everyone
Since I restarted my phone last night, my phone has been in a endless bootloop and I can't even enter recovery, without it rebooting again and going into the same endless bootloop again, around 2 seconds after showing the "Teamwin" logo.
I'm using ARHD, and if I remember correctly it's version 71.1. TWRP is "openrecovery-twrp-2.6.3.3-m7" and running ElementalX kernel.
I expect my partition is somehow corrupted, but I'm at a loss of ideas as to how I can recover my phone again. I would apreciate if I could somehow manage to make a backup of my data, but it that's totaly hopeless, I'm thinking of going for the ArtMOD ROM instead and starting fresh.
Is there a helpfull soul out there, that could maybe give me some insights as to what I can do from here? Thanks in advance!
I was hoping I could install a stock ROM and start from scratch again, but I somehow suspect having used a modified ROM has gotten me in trouble now and the ROM Upgrade utility sees this as a downgrade. I've not been able to find a newer ROM for the .401. series than "RUU_M7_UL_K44_SENSE55_MR_HTC_Europe_4.19.401.9_R_Radio_4A.23.3263.28_10.38r.1157.04L_release_353069_signed_2-1.exe". Although the updater believes I'm updating from 4.19.401.11 (the ARHD ROM).
I can get into FASTBOOT USB and the phone goes to the black HTC logo screen when trying to update, but quickly fails on the PC during the process at "Updating 1/5". When unplugging the USB cable the phone shows:"
RUU
Security fail!
Update Fail!
I've attached two screenshots, to better explain
Can some kind soul out there please help me getting a working phone again? What ROM I'll end up with doesn't really matter
Since you're using unlocked bootloader, why don't you try RUU to get back on Stock ROM.
Here is the collection of ROMS
Download your ROM.
from Windows Command prompt
adb reboot bootloader #
If it didn't work, Press and Hold Power button along with Volume down of your phone,
When you reach to bootloader, get into fastboot mode.
Now follow the following commands to restore the STOCK Rom. (make sure your downloaded ROM are in the same directory where you have fastboot.exe, abd, and abdwin.api etc)
1) fastboot erase cache
2) fastboot oem rebootRUU
3) fastboot flash zip RUU.zip (RUU.zip is of course your downloaded Stock ROM). If it says Failed, try again.
4) fastboot erase cache
5) fastboot reboot-bootloader
6) fastboot reboot
Good Luck
Hope that helps.
Thank you so much for helping out!
After several tries, tries and retries, I finally managed to get the phone back up and running with the stock ROM. I believe what finaly did the trick, was to use "fastboot oem lock" to get the stock ROM installed. From here, I'm now able to unlock it again and install a custom recovery (TWRP) and ROM (I went for ARTMOD). Thanks again!!!
So I recently tried to flash TWRP onto my HTC 626 and it seems like everything went well except a completely random group of inputs just loads my phone into fastboot list as follows:
Trying to enter recovery mode from menus
Trying to enter recovery mode from adb
Trying to perform a factory reset from menus
Plugging the device into a pc while powered off
The phone can still boot into the os and it runs just like normal. I have been frantically googling the problem but I have no idea what is going on.
I would have just done a reset but it just loads into fastboot.
DrLolCat said:
So I recently tried to flash TWRP onto my HTC 626 and it seems like everything went well except a completely random group of inputs just loads my phone into fastboot list as follows:
Trying to enter recovery mode from menus
Trying to enter recovery mode from adb
Trying to perform a factory reset from menus
Plugging the device into a pc while powered off
The phone can still boot into the os and it runs just like normal. I have been frantically googling the problem but I have no idea what is going on.
I would have just done a reset but it just loads into fastboot.
Click to expand...
Click to collapse
Guess what? I just might be able to save the day, mighty mouse style. Are you ready for this?
Try this out and see if it works for you like it worked for me.
But before you do this, I am on the MM-update android 6.0.1...this was what I used for this particular os. If you've update to Marshmallow already, please continue with the following......
Download these files first to your pc.
Twrp recovery - https://goo.gl/sO4Huz
BETA-SuperSU-v2.62 - https://www.androidfilehost.com/?fid=24269982087018189
Credit to my buddy IsaacGuti for the files.
fastboot flash the recovery
Make sure to either rename the Twrp recovery image to "recovery.img" before flashing or be sure to type the exact name of the twrp image file name verbatim. I'd suggest renaming it to "recovery.img just to be on the safe side.
in command prompt, it should look like this when you type it in "fastboot flash recovery recovery.img" without the parenthesis
( "<----These guys to the left....don't add those in)
To make it easier, just copy and paste what's in the parenthesis into the command prompt.
flash the supersu.zip in recovery. (Meaning after the flashing of the recovery is successful, then reboot into TWRP recovery to flash BETA-SuperSU-v2.62) But Don't forget to move the BETA-SuperSU file to your internal sd on your device.
If you've done all of this, you should have success. Just send me a virtual HI-5 and we're all good:highfive: