I recently came across a modified Google Nexus One (N1) that has been experimented on. Upon boot up, I get a black screen with the HTC logo and four exclamation marks inside triangles in each of the four corners of the screen. As I attempted to enter hboot, I saw it has been replaced with Blackrose which leads me to believe it has been unlocked/rooted at some point in time. ( I am fairly new at this, but I lurk around the forum ). I tried hooking the N1 up to RUU to flash it back to a stock ROM, however that proved unsuccessful - the phone boots up to the above mentioned logo and stays that way. When I try to go to recovery/hboot, instead of the usual menu choices, there's only RUU as an option... Is the phone bricked, and if not, how can I revert it to a working state ?
I have attached pictures of what the boot screen looks like, as well as the recovery menu.
Thank you in advance.
It's in the middle of RUU mode, entered by executing "fastboot oem rebootRUU" (I might not remember it 100% correct, so check it with Google).
This should be enough for you to check with Google how you exit RUU mode.
The only way I see to exit this mode is if I flash it with something via fastboot ( since no recovery works, custom or stock ). What image file or zip do I flash it with, in order to revert it back to complete stock ( stock hboot, stock recovery, stock ROM ) - I want the phone like it was out of the box, so I can reroot it and unlock it myself.
I tried flashing it with PASSIMG_Passion_Google_WWE_3.13.1700.1_GRK39F_release_signed.zip through fastboot, for a moment it seemed to be going ok, then at the very end, while it was unpacking the [user data] image I get a partition update fail message 51, and after reboot - still the gray HTC letters and Blackrose instead of HBOOT.
Any suggestions ?
Short googling with the error would have revealed you the bad news.
Partition update fail means bad stuff - your NAND is malfunctioning, which equals a dead phone.
Have you tried to uninstall Blackrose?
tommert38 said:
Have you tried to uninstall Blackrose?
Click to expand...
Click to collapse
doesn't the phone need to be working in order for me to hook it up to Blackrose ? As of now, with this screen, the PC doesn't seem to detect it as a working phone, only fastboot. And Blackrose just says waiting for device... how do I uninstall it then?
I also tried this RUU: RUU_Passion_Vodafone_Generic_3.11.151.3_GRJ22_release, flashing the ROM to an image version 3.11.151.3, but at the end I get a message saying ERROR [110]: FILE OPEN ERROR. The RUU cannot open the requested files or the files are damaged. The RUU cannot continue with the update. Please get a complete RUU package and try again. Can someone please refer me to a working RUU package for the Nexus One, I am really scared of experimenting trying to find one by myself, seeing how the phone is already hanging in the balance, I would be thankful
You could try to flash this stock HBOOT, and if you have resized partitions I guess you could always use blackrose_manual_120421.zip to change to stock partition layout (145/95/196).
Edit: I've never flashed a HBOOT this way, and I never resized my partitions the manual way, so I would check the Blackrose for details. And I'm not responsible if you brick your phone
Edit2: I see you haven't got working recovery, so you should find a way to flash the HBOOT via fastboot. Maybe the Blackrose developer dla5244 can help you out (or Google).
Edit3: You could also try to flash this engineering HBOOT
tommert38 said:
You could try to flash this stock HBOOT, and if you have resized partitions I guess you could always use blackrose_manual_120421.zip to change to stock partition layout (145/95/196).
Edit: I've never flashed a HBOOT this way, and I never resized my partitions the manual way, so I would check the Blackrose for details. And I'm not responsible if you brick your phone
Edit2: I see you haven't got working recovery, so you should find a way to flash the HBOOT via fastboot. Maybe the Blackrose developer dla5244 can help you out (or Google).
Edit3: You could also try to flash this engineering HBOOT
Click to expand...
Click to collapse
Thanks for your time friend, I tried the above mentioned steps, it says OK all across the board in fastboot while I flash, but after I reboot it just goes back to the same screen, stuck in RUU. I did some digging around and found this which seems to be exactly my problem:
RUU PROBLEMS
"I tried using a RUU, but it failed, and now my phone is stuck on a black HTC Screen with /!\ In every corner!"
Possible Causes:
- You were S-OFF and you flashed a custom bootloader from alpharev
- You didn't check the MD5 Sums before proceeding, and the download may have been corrupted.
- You tried using the wrong RUU
Fixing your problem
Your phone is stuck in RUU mode. RUU mode is like fastboot mode, and can still receive fastboot commands, therefore it can be easily "fixed".
It helps to have a goldcard for this problem, so that you can use any RUU you want.
S-OFF
[STEP1]- download "Bravo Stock" from Alpharev
[STEP2]- download Android Flasher
[STEP3]- use android flasher to flash "Bravo Stock"
[STEP4]- run the RUU again and wait for it to finish
S-ON
If you're S-ON it eliminates the possibility of you having a custom bootloader, and the only possibility now is that the RUU was corrupted or you
used the wrong RUU for your device. Therefore, for this process you need a goldcard.
[STEP1]- Create the goldcard from the tutorial
[STEP1]- Use the WWE RUU
However, this is from a thread for the HTC Bravo. Anything similar for the N1 ?
Edit1: Could it be that the hboot partition was resized with Blackrose and therefore the RUU I tried to flash it with needs stock partition layout ?
Your partitions ARE resized. 2nd picture 2nd line JB-220/10/206. If it's b*tching about the resized partitions, then that would be about your cache partition (which is 85MB smaller than its stock size).
Edit: you should also try to wipe your partitions with fastboot, then flash the img's that are inside the passimg
what's the command line to wipe the partition ? fastboot format hboot/recovery/system ?
Dude, your Nexus One is dead, the internal NAND is damaged and therefore unrecoverable.
Sent from my Nexus S using Tapatalk 2
fastboot erase system/cache/userdata/boot
Related
Hi
Due to a bootloop on my Inc S running Cyanogen 7 i wanted to flash a new recovery and a new os. But when I try to flash the image via fastboot, the message "FAILED (remote: Image update error)" appears. It's also impossible to erase partitions via fastboot due to an "erasing error". I tried to flash with adb, but the device isn't listed in adb devices .
I also tried to update HBOOT from version 6.13.1002 to 2.00.0000 using a PG32IMG.zip on the sd card, but it hangs on the "Dont power off" dialog.
I'd be happy if someone could help me out...
Thanks and greez
visosilver
Visosilver said:
Hi
Due to a bootloop on my Inc S running Cyanogen 7 i wanted to flash a new recovery and a new os. But when I try to flash the image via fastboot, the message "FAILED (remote: Image update error)" appears. It's also impossible to erase partitions via fastboot due to an "erasing error". I tried to flash with adb, but the device isn't listed in adb devices .
I also tried to update HBOOT from version 6.13.1002 to 2.00.0000 using a PG32IMG.zip on the sd card, but it hangs on the "Dont power off" dialog.
I'd be happy if someone could help me out...
Thanks and greez
visosilver
Click to expand...
Click to collapse
Since you have Rvolutionary S-Off, you cannot simply overwrite the HBOOT with stock 2.00.0000. You need to follow this procedure:
http://forum.xda-developers.com/showpost.php?p=15732727&postcount=14
Then you would able to use the PG32IMG.zip.
I actually dont wan't to get S-ON, but do you think that it will be possible to flash a new recovery and rom after updating the HBOOT?
If your bricked than its definately worth trying. Sounds to me like your internal memory has some kind of error on it if you can't wipe. And it might not be hung when you try to flash the pg32 as it as it says don't power off and you did anyway you might own an unbrickable phone.
Sent from my Incredible S using xda premium
Visosilver said:
I actually dont wan't to get S-ON, but do you think that it will be possible to flash a new recovery and rom after updating the HBOOT?
Click to expand...
Click to collapse
That depends on if you can update the HBOOT. In order to make your current HBOOT 6.13.1001 overwritable, you need to follow the procedure steps 1-2d in the procedure I posted.
If that doesn't work, then there is no sense trying to go on. As the previous posted suggested there is something wrong with your phone's partitions.
If it does work, then I would defintely run a stock RUU to get back to a known working state.
thank you for your answers, i just tried the procedure.
Since the first link is down i wasn't able to install the RUU, so i just tried the second step but i got again the "remote: image update error"
Does this mean my phone is definitely bricked?
Visosilver said:
thank you for your answers, i just tried the procedure.
Since the first link is down i wasn't able to install the RUU, so i just tried the second step but i got again the "remote: image update error"
Does this mean my phone is definitely bricked?
Click to expand...
Click to collapse
Yes it appears that you are unable to flash any of the partitions on your phone, including the HBOOT partition.
Do you have another PC and USB cable to try just to rule out that those aren't causing an issue? If you do, make sure you have the latest HTC drivers installed.
didn't work but thanks for your help anyway
greez visosilver
Visosilver said:
didn't work but thanks for your help anyway
greez visosilver
Click to expand...
Click to collapse
There's no harm in trying a ruu
Sent from my Incredible S using xda premium
try fastboot boot recovery.img
where recovery.img is the recovery image CWM or 4EXT
this wont flash the image..i will just push the recovery on your mobile and then would start it..then try to format all the partions
and can u provide us with all details..like exactly how the error happened..???
and is your phone under warranty..??
i just tried to boot the cwm via fastboot.
the phone vibrated 8 times, three android dudes on a skateboard appeared and the phone rebooted into HBOOT.
I tried also this RUU: http://forum.xda-developers.com/showthread.php?t=1705913, but it results in a 171 USB Error...
The phone isn't under varranty anymore.
How the error occured: I was browsing around, when suddenly whatsapp crashed. So i rebooted the phone and it was stuck in a bootloop. Then i tried to flash a new rom and the error occured
edit: after following to this guide here http://community.htc.com/na/htc-forums/android/f/113/t/10043.aspx, i was able to flash the device using the RUU. But I couldn't use the phone due to crashing processes (mostly android.process.arcore), so I rebooted. Now the phone is stuck again in a bootloop...
try installing the RUU again...and if possible if you are installing a custom rom please wipe all partition ,cache and dalvik cache...
and try booting the mobile withouth the sim card...lets see if it works
i just tried it, with the same result
From what I understand, the bootloader program (hboot) is completely separate from the rest of the operating system and recovery programs. It's the first program that loads when the phone is started and orchestrates the rest of the boot process.
The bootloader need to be replaced in order to root the phone. But once this is done is it never needed to be touched ever again? When rooted, does this mean you can replace your bootloader at any time without affecting access to your installed recovery program?
cytherian said:
From what I understand, the bootloader program (hboot) is completely separate from the rest of the operating system and recovery programs. It's the first program that loads when the phone is started and orchestrates the rest of the boot process.
The bootloader need to be replaced in order to root the phone. But once this is done is it never needed to be touched ever again? When rooted, does this mean you can replace your bootloader at any time without affecting access to your installed recovery program?
Click to expand...
Click to collapse
With our heroc's the bootloader isn't needed to root and install a custom recovery. However people generally do it so you can flash via fastboot if ever needed.
Once you unlock (or install the eng-spl) hboot no it's never touched or needed to be touched again unless you RUU. You could replace the bootloader whenever you wanted and not effect anything else but there really isn't much of a point.
Shelnutt2 said:
With our heroc's the bootloader isn't needed to root and install a custom recovery. However people generally do it so you can flash via fastboot if ever needed.
Once you unlock (or install the eng-spl) hboot no it's never touched or needed to be touched again unless you RUU. You could replace the bootloader whenever you wanted and not effect anything else but there really isn't much of a point.
Click to expand...
Click to collapse
Thanks for the info, Shelnutt.
I'm kind of in a peculiar "Nexus" that I'm trying to extricate myself from. I have S-ON presently. I would like to change it to S-OFF, but I can't seem to do it. I suspect it's the bootloader preventing me, which is hboot 1.7. So, I tried to replace the bootloader and the attempts fail. I've tried it through the adb shell, fastboot, terminal emulator on the phone, and via the recovery manager (TWRP). Attempting to replace the bootloader results in "signature verify fail". Through TWRP, it also said verification failed.
I also tried to retrieve the identifier token (HTC dev) so that I could unlock the phone that way, but "fastboot oem get_identifier_token" fails with a "Command error" (although I can execute "fastboot oem rebootRUU" with no problem).
I also tried to use Regaw's boot mod tool, which replaces the bootloader and turns S-OFF. But it aborts because my Hero is already rooted. So I went into my z4Root application and selected "un-root". It said "done", but the phone remains rooted. I even tried to "Re-root" but it wouldn't complete (thinking if I root it again, I could then try another un-root).
I'm thinking I should just flash back to stock, but... I don't have any fresh nandroid backups to use. TWRP doesn't do nandroid. It does its own thing, which becomes a problem because TWRP needs Android 2.2 or higher. So... does that mean I need to install ROM Manager again, do a nandroid backup, then run an RUU back to full stock again?
For the eng-spl when it says signature failed, you just need to disable signature checking. In CWM it's in the flash .zip menu. Not sure where it's at for TWRP. If you have the 1.47 hboot like you say thought you can't flash to 1.46 without being s-off first.
For regaw's hboot, he hard hard coded radios version into it. So in all likelyhood you're error is about the radio. It never checks for root inside the room, as it doesn't effect flashing a new hboot. My suggestion is to flash this radio and see if regaw's method works.
https://docs.google.com/open?id=0B9lyYjZr_O3gYy1xclMzbURyd0k
Shelnutt2 said:
For the eng-spl when it says signature failed, you just need to disable signature checking. In CWM it's in the flash .zip menu. Not sure where it's at for TWRP. If you have the 1.47 hboot like you say thought you can't flash to 1.46 without being s-off first.
For regaw's hboot, he hard hard coded radios version into it. So in all likelyhood you're error is about the radio. It never checks for root inside the room, as it doesn't effect flashing a new hboot. My suggestion is to flash this radio and see if regaw's method works.
https://docs.google.com/open?id=0B9lyYjZr_O3gYy1xclMzbURyd0k
Click to expand...
Click to collapse
Thanks, you're right... in TWRP there's a checkbox to control that. There's also one to verify md5, but it requires a file (I guess it looks for [filename].md5). In any case, getting past that resulted in failure to load hboot 1.46 as you surmised.
The issue with Regaw doesn't seem to be the radio. It simply reports that there's nothing to do because the phone is already rooted. Apparently it will only run if the phone is not rooted. And to unroot, it appears the only way is by RUU. Z4Root is supposed to allow it, but when selected it doesn't do anything.
So, I finally came up with something that got me on the right path. :good:
I re-installed ROM Manager and flashed the latest ClockworkMod to Recovery. From there I could apply the hboot 1.46 ENG-SPL with no issues. I rebooted into the bootloader and saw................ HERO XC ENG S-OFF, HBOOT-1.46.2000. :highfive:
Hi All,
Help required with my HTC One 801n. I have read and search numourse posts but still cant load a ROM or anything back onto it
The phone details
M7 UL
Hboot 1.54
Radio 4A.17.3250.14
CID HTC_001
S ON
The phone was unlocked and rooted shortly after I bought it in July. I was using a Google edition Revolution HD 22 Rom, but I decided to try a CM10.2 ROM and this is where it all started to go wrong. I downloaded the CM Rom and started to flash it on my phone but I got a boot loop with a different screen repeating over the recovery screen so I tried to wipe it and reflash but in doing so I deleted everything. At that time I could get into the recovery screen where it said there wasn’t a ROM installed, so I tried flashing the ROM again but this time I can only get into the boot loader and Fastboot, with no option into recovery.
Things I have tried
unlocked In fastboot tried flashing various ROMs but at the end it says FAILED: (remote:not allowed
ROMs i have tried are the latest from HTC dev web site PN07IMG_M7_UL_JB43_SENSE50_MR_BrightstarUS_WWE_3.22.1540.1 & CM10.2 roms and bootimg files but just get the Failed message at the end.
I have tried locking the boot loader and trying a RUU file but the same thing with failed messages at the end or wrong signature.
Is there something pretty basic I am missing because the fastboot cmds seem to work just not for flashing.
Aslo tried the adb side load but it doesn’t list my device and the cmd don’t work, they work fine in fastboot.
Any help would be appreciated before it ends up in bits!!
The cid on the phone and the ruu has to be the same.
---------- Post added at 07:03 PM ---------- Previous post was at 07:03 PM ----------
Try -off
andyp1 said:
Hi All,
Help required with my HTC One 801n. I have read and search numourse posts but still cant load a ROM or anything back onto it
The phone details
M7 UL
Hboot 1.54
Radio 4A.17.3250.14
CID HTC_001
S ON
The phone was unlocked and rooted shortly after I bought it in July. I was using a Google edition Revolution HD 22 Rom, but I decided to try a CM10.2 ROM and this is where it all started to go wrong. I downloaded the CM Rom and started to flash it on my phone but I got a boot loop with a different screen repeating over the recovery screen so I tried to wipe it and reflash but in doing so I deleted everything. At that time I could get into the recovery screen where it said there wasn’t a ROM installed, so I tried flashing the ROM again but this time I can only get into the boot loader and Fastboot, with no option into recovery.
Things I have tried
unlocked In fastboot tried flashing various ROMs but at the end it says FAILED: (remote:not allowed
ROMs i have tried are the latest from HTC dev web site PN07IMG_M7_UL_JB43_SENSE50_MR_BrightstarUS_WWE_3.22.1540.1 & CM10.2 roms and bootimg files but just get the Failed message at the end.
I have tried locking the boot loader and trying a RUU file but the same thing with failed messages at the end or wrong signature.
Is there something pretty basic I am missing because the fastboot cmds seem to work just not for flashing.
Aslo tried the adb side load but it doesn’t list my device and the cmd don’t work, they work fine in fastboot.
Any help would be appreciated before it ends up in bits!!
Click to expand...
Click to collapse
Based on your CID you got the incorrect RUU. You should have gotten this one: 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 Going forward once you get back up, you should think of getting S-OFF. It would give you more flexibility with ROM etc. But you also have to be more carefull.
Also, to run the RUU your bootloader must be locked/relocked since you are S-ON.
majmoz said:
Based on your CID you got the incorrect RUU. You should have gotten this one: 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 Going forward once you get back up, you should think of getting S-OFF. It would give you more flexibility with ROM etc. But you also have to be more carefull.
Click to expand...
Click to collapse
that wont work as he is s-on, his HBOOT is 1.54 and that RUU has HBOOT 1.56, too many steps up, it will fail with image error.
you need to use this: http://www.htc1guru.com/2013/10/guru-reset-3-62-401-1-stock-rom/
or this one is probably better for you which is probably the same version you had on the phone to start with: http://www.htc1guru.com/dld/guru_reset_m7_2-24-401-8-zip/
push it to your internal storage and flash like a custom rom, select wipe data, install stock recovery and install stock radio when prompted, you should get OTAs after that.
Good morning,
I've 'inherited' an Incredible S where an attempt to try a custom ROM has gone wrong. The handset has ARHD 6 ROM installed in it which never gets past the white HTC bootscreen, probably because it hasn't had the BlackRose bootloader installed. Obviously there is no Nandroid to make life easy.
It's on HBoot 2.02, S-on, and the bootloader is unlocked with 4Ext installed.
Quick question: is there a ROM I can install on bootloader 2.2 via 4Ext that will enable the phone to be used, e.g. Virtuous Quattro?
Longer question: Can anybody point me in the direction of a good method to downgrade the bootloader, bearing in mind I can't boot to the ROM. I do seem to have fastboot access and don't mind command line work, I just can't see the best combination of bootloader/ROM that isn't on a dead link.
Alternatively an RUU suitable for the bootloader would be good, but for some reason the list on HTCDev.com doesn't seem to be filtering properly for me on Opera or Iron.
Thanks in advance,
RH
Bossk128 said:
Good morning,
I've 'inherited' an Incredible S where an attempt to try a custom ROM has gone wrong. The handset has ARHD 6 ROM installed in it which never gets past the white HTC bootscreen, probably because it hasn't had the BlackRose bootloader installed. Obviously there is no Nandroid to make life easy.
It's on HBoot 2.02, S-on, and the bootloader is unlocked with 4Ext installed.
Quick question: is there a ROM I can install on bootloader 2.2 via 4Ext that will enable the phone to be used, e.g. Virtuous Quattro?
Longer question: Can anybody point me in the direction of a good method to downgrade the bootloader, bearing in mind I can't boot to the ROM. I do seem to have fastboot access and don't mind command line work, I just can't see the best combination of bootloader/ROM that isn't on a dead link.
Alternatively an RUU suitable for the bootloader would be good, but for some reason the list on HTCDev.com doesn't seem to be filtering properly for me on Opera or Iron.
Thanks in advance,
RH
Click to expand...
Click to collapse
Download CM7.2
Go back to bootloader.
Go to Recovery.
Mount USB storage and transfer CM7.2 to SD card
Now Flash CM7.2
Flash boot.img of CM7.2
Enable USB Debugging after you've booted up (no need for GApps atm)
Continue with downgrade guide (Everything is in sticky roll up thread)
072665995 said:
Download CM7.2
Go back to bootloader.
Go to Recovery.
Mount USB storage and transfer CM7.2 to SD card
Now Flash CM7.2
Flash boot.img of CM7.2
Enable USB Debugging after you've booted up (no need for GApps atm)
Continue with downgrade guide (Everything is in sticky roll up thread)
Click to expand...
Click to collapse
Nice one, thanks. I've downloaded the ROM from http://get.cm/get/2KU and will flash from 4Ext recovery.
The bootloader in in that same zip file, I'll flash as follows:
At ADB prompt:
fastboot flash boot boot.img
Reboot, ROM should load up fine. I spotted the downgrade guide yeterday and it looks very good. I'll give it a shot if CM isn't suitable.
Again, thanks very much.
Time for 2 small questions? How long does it take to flash the boot.img, 10 seconds? 5 minutes? Why does the boot image have to be flashed manually?
Cheers!
Bossk128 said:
Nice one, thanks. I've downloaded the ROM from http://get.cm/get/2KU and will flash from 4Ext recovery.
The bootloader in in that same zip file, I'll flash as follows:
At ADB prompt:
fastboot flash boot boot.img
Reboot, ROM should load up fine. I spotted the downgrade guide yeterday and it looks very good. I'll give it a shot if CM isn't suitable.
Again, thanks very much.
Time for 2 small questions? How long does it take to flash the boot.img, 10 seconds? 5 minutes? Why does the boot image have to be flashed manually?
Cheers!
Click to expand...
Click to collapse
boot.img flashing should take >1s or around that at least...
And the boot.img has to be flashed manually only if you are S-ON. S-ON doesn't give you full clearance to some particular partition that I forget. S-OFF will so when you achieve S-OFF, you will no longer need to flash the boot.img manually
072665995 said:
boot.img flashing should take >1s or around that at least...
And the boot.img has to be flashed manually only if you are S-ON. S-ON doesn't give you full clearance to some particular partition that I forget. S-OFF will so when you achieve S-OFF, you will no longer need to flash the boot.img manually
Click to expand...
Click to collapse
OK, same as my HOX then. Anyway, I've followed your instructions.
Hm, ROM installed and now trying to flash boot.img (from the rom zip).
Fastboot devices shows one device.
Command line states "sending boot (2182 kb)..." but hasn't changed for over 3 minutes. Handset says Fastboot USB and is unresponsive (as expected) at this moment.
I'll leave it until it errors.
RH
Edit: 30minutes later i pulled the usb cable.
"FAILED (status read failed (Too many links))"
Handset is in the same state, i.e.fastboot/hboot and recovery are fine, but ROM doesn't boot and handset stalls at white screen with green HTC letters.
Any ideas why I can't flash the boot.img?
Success! After reinstalling the the drivers and moving the USB cable to another port, the boot.img was successfully pushed, and booted into CM.
I'll now go for downgrading!
thanks for the help.
RH
Hi all.
I tried to flash my HTC one from recovery (twrp) after doing a factory reset within twrp. (I thought at the time a had stock recovery, I didn't. I had twrp.
Now my phone won't boot. Gets stuck on splash screen. If i enter the bootloader (which works no problem) and choose recovery, it starts recovery, pops up with twrp splash screen for second, then reboots to frozen htc splash screen.
Fastboot is working.
I've tried clearing the cache using fastboot. samething
I've tried flashing other recoveries,. nothing samething. (others in different predicaments have been able to do this successfully)
I've been reading that returning back to stock using RUU.zip method is the only way to go.
I want to try that, but before I do, I must make sure I understand it correctly and I've done all I can.
Relock the bootloader? Can I unlock it again?
Find a RUU.Zip that matches my OS version
Flash using fastboot.
I've been looking through HTC1GURU at his collection of ruu.zip but can't find anything that really matches my OS.
Any suggestions and advice will be most welcome.
Thanks in advance
Phone info.....
my Original CID was....orang001
profixit said:
Hi all.
I tried to flash my HTC one from recovery (twrp) after doing a factory reset within twrp. (I thought at the time a had stock recovery, I didn't. I had twrp.
Now my phone won't boot. Gets stuck on splash screen. If i enter the bootloader (which works no problem) and choose recovery, it starts recovery, pops up with twrp splash screen for second, then reboots to frozen htc splash screen.
Fastboot is working.
I've tried clearing the cache using fastboot. samething
I've tried flashing other recoveries,. nothing samething. (others in different predicaments have been able to do this successfully)
I've been reading that returning back to stock using RUU.zip method is the only way to go.
I want to try that, but before I do, I must make sure I understand it correctly and I've done all I can.
Relock the bootloader? Can I unlock it again?
Find a RUU.Zip that matches my OS version
Flash using fastboot.
I've been looking through HTC1GURU at his collection of ruu.zip but can't find anything that really matches my OS.
Any suggestions and advice will be most welcome.
Thanks in advance
Phone info.....
my Original CID was....orang001
Click to expand...
Click to collapse
There isn't any ruu for orange (.61 base) only a nandroid backup which require a working recovery to be flashed. if you don't really care about staying with the orange sw, you could simply restore your phone to international EU version (.401 base). You already have s-off and the proper mid, so it will only require to downgrade hboot to 1.44, change cid to HTC__001 and run the 1.29.401 ruu.exe. you can use this guide
Thanks for the quick reply and the guide.
I don't care about orange sw. I'll do some reading. I do have a nandroid backup. No good to me, unless I get recovery working.
Not too confident about downgrading the Hboot, but i'll read and read.
profixit said:
Thanks for the quick reply and the guide.
I don't care about orange sw. I'll do some reading. I do have a nandroid backup. No good to me, unless I get recovery working.
Not too confident about downgrading the Hboot, but i'll read and read.
Click to expand...
Click to collapse
downgrading hboot is pretty easy
just follow the steps under ''If you’re on hboot which is above 1.44'' from nkk71's guide
then change cid
then run ruu.exe
but do not use a win 8.1 computer (compatibility issue with hboot 1.44)
Thanks for that last bit, what about Win8.
I've spotted the steps that apply to me, just playing them out in my head.
Out of curiosity after a downgrade the HBoot, will it be locked and s-on?
profixit said:
Thanks for that last bit, what about Win8.
Click to expand...
Click to collapse
windows 8.0 should be fine, but definitively not 8.1
alray said:
There isn't any ruu for orange (.61 base) only a nandroid backup which require a working recovery to be flashed. if you don't really care about staying with the orange sw, you could simply restore your phone to international EU version (.401 base). You already have s-off and the proper mid, so it will only require to downgrade hboot to 1.44, change cid to HTC__001 and run the 1.29.401 ruu.exe. you can use this guide
Click to expand...
Click to collapse
I noticed that particular 1.29.401 ruu exe has a different model ID, gonna course problems?
profixit said:
I noticed that particular 1.29.401 ruu exe has a different model ID, gonna course problems?
Click to expand...
Click to collapse
sry my bad
use this one: http://www.htc1guru.com/dld/ruu_m7_ul_jb_50_htc_europe_1-28-401-7_radio_4a-13-3231-27_10-31-1131-05_release_310878_signed-exe/
1.28.401
No worries, Thanks.
Can you try fastboot erase cache from fastboot menu and re enter recovery?
Tried that, thanks
Sent from my HTC One using Tapatalk
OK, a little lucky positive progress.
I managed to flash clockworkMod recovery, don't ask me how, maybe erasing the cache lots of times did it, i'm sure it was a recovery I had already tried. I checked my download list and confirmed I did download it., so i would of tried to flash it two days ago. Funny.
Still stuck on splash screen, but can boot into recovery. (clockworkmod)
Please, what is the best way to proceed, I'm thinking nandroid backup, but like I said, I couldn't care less about orange. I would love to put Mike1986 stock rom 4.3 or 4.4
I'm unable or don't know how to get folders or files on the phone's internal SD card, because it doesn't boot up a rom any more. Y-cable?
I'm concerned with all the "can't" at the bottom of recovery screen.