Related
I was wondering if anyone might be able to help me in my quest to install the OTA update for the Incredible S to 2.3.5, sense 3.0.
I have previously rooted, back in the Summer of this year so think it would have been Alpha or Revoked. Have tried a couple of things to restore S-On in order to run the stock update.
I have tried several methods to flash a new HBOOT, including flashing the OTA from Sense and the bootloader, and have tried to flash a new PG32IMG as well.
Most recently I have extracted a Rom.zip from a working Incredible S/Vivo RUU, and tried to put on the Hboot from this after running the Vivo Downgrade.img - for both of these I keep getting "Can not roll back hboot version" on the bootloader screen after pushing to the device with FASTBOOT.
Since installing the PG32IMG.zip I tried, I have changed to Vivo PVT SHP S-OFF RL on the bootloader. The other details are:
HBOOT - 700.1000
RADIO - 3805.04.03.22_M
eMMC - boot
Other than having S-Off and being rooted, I am running Stock 2.3.3 with Sense 2.1
Does anyone have any suggestions as to where I'm going wrong, or what Hboot I can flash to overcome this please!
Is your Inc s locked to a network or did you get it sim free, that could be a problem you might be having. If you went from a custom rom to stock rom did you use the correct ruu to go to rom which is right for your country.
The phone itself is sim free. I used an RUU that was as similar to the OTA update naming as possible:
RUU_Vivo_Gingerbread_S_HTC_WWE_2.30.405.1_Radio_20.2808.30.085AU_3805.06.03.03_M_release_199308_signed
elthrawno , i have the same problem?
have a solution??
plzz help...
thank you...
elthrawno said:
I was wondering if anyone might be able to help me in my quest to install the OTA update for the Incredible S to 2.3.5, sense 3.0.
I have previously rooted, back in the Summer of this year so think it would have been Alpha or Revoked. Have tried a couple of things to restore S-On in order to run the stock update.
I have tried several methods to flash a new HBOOT, including flashing the OTA from Sense and the bootloader, and have tried to flash a new PG32IMG as well.
Most recently I have extracted a Rom.zip from a working Incredible S/Vivo RUU, and tried to put on the Hboot from this after running the Vivo Downgrade.img - for both of these I keep getting "Can not roll back hboot version" on the bootloader screen after pushing to the device with FASTBOOT.
Since installing the PG32IMG.zip I tried, I have changed to Vivo PVT SHP S-OFF RL on the bootloader. The other details are:
HBOOT - 700.1000
RADIO - 3805.04.03.22_M
eMMC - boot
Other than having S-Off and being rooted, I am running Stock 2.3.3 with Sense 2.1
Does anyone have any suggestions as to where I'm going wrong, or what Hboot I can flash to overcome this please!
Click to expand...
Click to collapse
Since you are S-Off using Revolutionary, the Revolutionary HBOOT is preventing you from overwriting it so you won't lose S-Off. If you truly want to return to a stock ROM then you need to follow this procedure:
http://forum.xda-developers.com/showpost.php?p=15732727&postcount=14
I've followed the method on there, but not convinced I have the full SDK suite installed, so might be worth me retrying once I have.
So, with all the excitement of just getting my HTC one on saturday, I got down to business today doing some rooting. This is not my first htc device, i owned the evo 4g before.
With that said, What I did was have a rooted stock rom. I never flashed a new rom to the phone at all. I was trying to do the HTC logo button hack, I downloaded the kernel and flashed away. well, now the problem is the phone will start up and get to where the lock screen should be, It will show the status bar at the top and thats it, hangs for about 20 seconds and then restarts
It constantly does this... I have just updated the sprint software maybe 1.31 something? it was OTA I did before rooting.
I have tried to sideload a rooted odexed stock rom and have not had any success. I also tried running the sprint RUU but it was for 1.29, so it got almost to the end and told me it couldnt do it.
I am working from a mac, but have access to PC if needed. I am using clockwork mod recovery and can still get into it. just stuck on where to go from here..
All help is appreciated, ive spent the last 7 hours trying to fix this problem!
Guys, I am without a phone until this issue is fixed, any and all help is appreciated!!!
mattgfx said:
Guys, I am without a phone until this issue is fixed, any and all help is appreciated!!!
Click to expand...
Click to collapse
Do you have a rom downloaded on your phone? Did you make nandroid? If yes just restore. Do you have otg cable? If yes, download a rom. Do full wipe, cache, dalvik cache, data, and system. Try flashing the rom from otg. What kernel did you flash?
Sent from my lair.
The guy who made the htc one logo hack made a kernel that he released, I flashed that on top of the stock sprint rom. I had a nandroid, but it got wiped. I do not have an OTG cable. I have tried to sideload various roms and I can get it to boot, but I get no cell signal, sometimes i get the error that the system is not responding and i have the option to wait or kill.
I have gotten into the baseband settings and see that I do not have a baseband in there, maybe thats the issue? Also I just took the 1.31 ota update, I am getting an error using the sprint RUU about the boot loader not being correct version. from the fastboot screen I have the following
perhaps bad boot.img??
***TAMPERED****
****UNLOCKED***
M7_WLS PVT SHIP S-ON RH
HBOOT-1.44.0000
OPENDSP-v31.120.274.0617
eMMC-boot
Jul 5 2013, 17:19:22:-1
all help is much appreciated!!!
Use this http://forum.xda-developers.com/showthread.php?p=40712553. Please follow directions to a t.
Sent from my lair.
mattgfx said:
The guy who made the htc one logo hack made a kernel that he released, I flashed that on top of the stock sprint rom. I had a nandroid, but it got wiped. I do not have an OTG cable. I have tried to sideload various roms and I can get it to boot, but I get no cell signal, sometimes i get the error that the system is not responding and i have the option to wait or kill.
I have gotten into the baseband settings and see that I do not have a baseband in there, maybe thats the issue? Also I just took the 1.31 ota update, I am getting an error using the sprint RUU about the boot loader not being correct version. from the fastboot screen I have the following
perhaps bad boot.img??
***TAMPERED****
****UNLOCKED***
M7_WLS PVT SHIP S-ON RH
HBOOT-1.44.0000
OPENDSP-v31.120.274.0617
eMMC-boot
Jul 5 2013, 17:19:22:-1
all help is much appreciated!!!
Click to expand...
Click to collapse
A flashed kernel will overwrite your boot.img, so that really shouldn't be it. An RUU requires your bootloader be locked though, which is probably part of your issue.
volk9029 said:
Use this http://forum.xda-developers.com/showthread.php?p=40712553. Please follow directions to a t.
Sent from my lair.
Click to expand...
Click to collapse
I tried those last night, I relocked the boot loader and went through the steps. When it got to the end, it said something about the bootloader and error code 140
any ideas?
I see that the file Sprint_HTC_One_m7wls_1.29.651.10_RUU.zip is available through android filehost, well, I am at work and its blocked as spyware, anyone have an alternate link anywhere? ive tried looking and can only find android filehost
Thanks!
mattgfx said:
I see that the file Sprint_HTC_One_m7wls_1.29.651.10_RUU.zip is available through android filehost, well, I am at work and its blocked as spyware, anyone have an alternate link anywhere? ive tried looking and can only find android filehost
Thanks!
Click to expand...
Click to collapse
I don't think you can RUU backwards meaning 1.31 back to 1.29 check android development for indrects thread for the latest firmware i think he posted the 1.31 RUU
Sent from my Eliptic Nexus 7
bigdaddy619 said:
I don't think you can RUU backwards meaning 1.31 back to 1.29 check android development for indrects thread for the latest firmware i think he posted the 1.31 RUU
Sent from my Eliptic Nexus 7
Click to expand...
Click to collapse
Just tried using his RUU and im still getting the same thing, was able to get into settings breifly and it told me that it didnt know what baseband version there was. Any Ideas?
It keeps rebooting because of the system not responding, not getting any cell service at all
mattgfx said:
Just tried using his RUU and im still getting the same thing, was able to get into settings breifly and it told me that it didnt know what baseband version there was. Any Ideas?
It keeps rebooting because of the system not responding, not getting any cell service at all
Click to expand...
Click to collapse
Are you sure that you relock your bootloader ?
Sent from my lair.
volk9029 said:
Are you sure that you relock your bootloader ?
Sent from my lair.
Click to expand...
Click to collapse
problem with that though, I do not see a windows executable from there. the other issue is im using a mac, as far as i know everything works the same when it comes to adb and fastboot.
How would I flash a zip file if I cannot access my recovery? for instance how do I push the file to my device? when i relock the phone, and try to enter recovery, i get routed right back to bootloader
Figured out the issue, turned out that the problem came from firmware being absent... I was able to reflash the firmware and away it went, able to get into the phone now and do what i please!
Thanks for all help from everyone!!!
Hello All,
Here's my dilemma. I successfully rooted my HTC One (AT&T), and was recently attempting to unroot it. I followed this one here http://forum.xda-developers.com/showthread.php?t=2182823. Since I have the AT&T version, I downloaded the first one the list found there, however it wouldn't verify. Next I downloaded the AT&T AIO here http://forum.xda-developers.com/showthread.php?t=2242635. I was able to use that to figure out according to the info it displayed that I actually needed the Google Edition one from the previous link. I thought that was weird since I dont have the google edition one. But when I fast booted that one, everything appeared to go through with a hitch.....Until it restarted.
After it restarted, I only have a black screen. No start up. I restarted the phone and went into the bootloader and to my surprise, the bootloader was black instead of the normal white.
I've tried several RUUs found here http://www.androidruu.com/index.php?developer=M7
I've tried both the exe and flashing the zip.
I have no clue what to try next. Please XDA, your my only hope.
Are you s-off? I would assume so if you've been able to run multiple RUUs and are getting weird signature results. What mods/roms did you do to your phone before you started all this?
If you can get to bootloader, you're not bricked. You're on the 3.06 GE hboot, but it's not clear why you can't boot up.
iElvis said:
Are you s-off? I would assume so if you've been able to run multiple RUUs and are getting weird signature results. What mods/roms did you do to your phone before you started all this?
If you can get to bootloader, you're not bricked. You're on the 3.06 GE hboot, but it's not clear why you can't boot up.
Click to expand...
Click to collapse
----From the top of bootloader down----
***Tampered***
***Relocked***
M7_UL PVT SHIP S-ON RH
HBOOT-1.54.0000
RADIO-4A.18.3263.15
OpenDSO-V31.120.274.0617
(in red) OS-3.03.1700.10 (3.06.1700.10)
eMMC-boot 2048MB
Aug 1 2013, 18:48:40.0
Does that help at all?
Tylegn said:
----From the top of bootloader down----
***Tampered***
***Relocked***
M7_UL PVT SHIP S-ON RH
HBOOT-1.54.0000
RADIO-4A.18.3263.15
OpenDSO-V31.120.274.0617
(in red) OS-3.03.1700.10 (3.06.1700.10)
eMMC-boot 2048MB
Aug 1 2013, 18:48:40.0
Does that help at all?
Click to expand...
Click to collapse
Were you ever s-off? You should not have been able to run that GE RUU on an s-on AT&T phone.
iElvis said:
Were you ever s-off? You should not have been able to run that GE RUU on an s-on AT&T phone.
Click to expand...
Click to collapse
I hate to say.... I have no clue if I was before or not. I just relocked it like the directions told me. Is there any saving me? Also, thank you for your quick responses.
Tylegn said:
I hate to say.... I have no clue if I was before or not. I just relocked it like the directions told me. Is there any saving me? Also, thank you for your quick responses.
Click to expand...
Click to collapse
You bought it new? Not used from someone else? If so, it was always s-on.
You're on GE firmware somehow. It's possible you have a conflict with your model or carrier ID. Can you run through the exact steps you took when you started trying to unroot? Exactly which files you used and how you ran them?
iElvis said:
You bought it new? Not used from someone else? If so, it was always s-on.
You're on GE firmware somehow. It's possible you have a conflict with your model or carrier ID. Can you run through the exact steps you took when you started trying to unroot? Exactly which files you used and how you ran them?
Click to expand...
Click to collapse
I received the phone directly from HTC through a sell to earn contest.
Not sure if it matters much but I unlocked the bootloader through HTC Dev.
To unroot,
1) Put phone in bootloader with fastboot
2) Relocked bootloader
3) fastboot oem rebootRUU
4) fastboot flash zip 2.24.401.1.zip (failed)
Used one of the AIOs that stated I had modelid: PN0712000 and cidnum: CWS__001. That when I grabbed the GE version.
5) fastboot flash zip 3.06.1700.10.zip
6) Phone finished, rebooted to a black screen
7) Rebooted into bootloader (Which is now black instead of white)
8) Sad ever since....
Where did you get that GE zip? I'm not sure why the AIO toolkit told you that you were GE but I'd like to check the file.
I suspect the problem is that you have 4.3 GE firmware but a 4.1 OS. Flashing a 4.2 or 4.3 rom might fix.
ageldea consider
iElvis said:
Where did you get that GE zip? I'm not sure why the AIO toolkit told you that you were GE but I'd like to check the file.
I suspect the problem is that you have 4.3 GE firmware but a 4.1 OS. Flashing a 4.2 or 4.3 rom might fix.
Click to expand...
Click to collapse
This is where I got:
http://forum.xda-developers.com/showthread.php?t=2182823
I'll need a step by step from you if you can because, I'm having a h3ll of a time trying to get anything to flash.
Tylegn said:
This is where I got:
http://forum.xda-developers.com/showthread.php?t=2182823
I'll need a step by step from you if you can because, I'm having a h3ll of a time trying to get anything to flash.
Click to expand...
Click to collapse
:facepalm: Just realized the issue.
Your bootloader is locked and you still have custom recovery installed, I'm guessing. Can you select Recovery in bootloader and see what happens? If you're still with TWRP or CWM, that's the issue; you can't boot locked on custom recovery.
You have to unlock again or flash the stock recovery in fastboot. Unlocking will wipe your phone, unfortunately.
Flashing recovery in fastboot is easy if you have the stock recovery file.
fastboot flash recovery [filename].img
iElvis said:
:facepalm: Just realized the issue.
Your bootloader is locked and you still have custom recovery installed, I'm guessing. Can you select Recovery in bootloader and see what happens? If you're still with TWRP or CWM, that's the issue; you can't boot locked on custom recovery.
You have to unlock again or flash the stock recovery in fastboot. Unlocking will wipe your phone, unfortunately.
Flashing recovery in fastboot is easy if you have the stock recovery file.
fastboot flash recovery [filename].img
Click to expand...
Click to collapse
You are right about having the recovery option in the bootloader but when I try to select that option, Android shows up with the spinning blue thing in it's stomach, then it dies with a red triangle.
I'll try flashing the recovery again. After I find a stock recovery img. LOL
Thanks again!!!
I'll post what's going on as I do it.
iElvis said:
:facepalm: Just realized the issue.
Your bootloader is locked and you still have custom recovery installed, I'm guessing. Can you select Recovery in bootloader and see what happens? If you're still with TWRP or CWM, that's the issue; you can't boot locked on custom recovery.
You have to unlock again or flash the stock recovery in fastboot. Unlocking will wipe your phone, unfortunately.
Flashing recovery in fastboot is easy if you have the stock recovery file.
fastboot flash recovery [filename].img
Click to expand...
Click to collapse
Found the stock recovery. Attempted to flash it and got this:
sending 'recovery' <16303 KB>...
OKAY [ 1.786s]
writing 'recovery'...
<bootloader> signature checking...
FAILED <remote: 12 signature verify fail>
finished. total time: 3.178s
Is there a different way I should be doing it.
HTC One has the Gray HTC logo chilling on the screen...
Also tried in normal fastboot mode...
Tylegn said:
You are right about having the recovery option in the bootloader but when I try to select that option, Android shows up with the spinning blue thing in it's stomach, then it dies with a red triangle.
I'll try flashing the recovery again. After I find a stock recovery img. LOL
Thanks again!!!
I'll post what's going on as I do it.
Click to expand...
Click to collapse
Actually, I think that red triangle is stock recovery. I think to get to the recovery options you press power+vol up on that screen. But it doesn't matter because clearly you're not on custom recovery.
I don't see that 3.06 firmware package in the OP of that thread. Can you find the post you found it attached to?
iElvis said:
Actually, I think that red triangle is stock recovery. I think to get to the recovery options you press power+vol up on that screen. But it doesn't matter because clearly you're not on custom recovery.
I don't see that 3.06 firmware package in the OP of that thread. Can you find the post you found it attached to?
Click to expand...
Click to collapse
If you click on the download link in that post for the GE it downloads as that 3.06 firmware..
Also, not sure if it was smart or not but I unlocked the bootloader again to see if it would fix the conflicts you mentioned before. Haven't tried flashing anything yet...
ADD: I just successfully flashed the stock recovery.... Too scared to muck something up so I'll waif for your superior guidance!
Thanks again
Tylegn said:
If you click on the download link in that post for the GE it downloads as that 3.06 firmware..
Also, not sure if it was smart or not but I unlocked the bootloader again to see if it would fix the conflicts you mentioned before. Haven't tried flashing anything yet...
Click to expand...
Click to collapse
I forgot Mike updated that link.
Okay, I see what you did now. You've essentially upgraded your phone to a GE because the android-info.txt in this official firmware matched your MID and CID; that allowed it to run. The problem is that you can't go back now because you're s-on. Your phone won't boot because you have the GE kernel installed but I assume a Sense rom.
This should be easy to fix. You can flash custom recovery now that you've unlocked, then flash a custom rom. This will get your kernel and rom consistent again and you should be able to boot.
Unrooting is a different story. You can't go back to the stock configuration you had when you got the phone without s-off, which you can't get on 1.54 hboot. I'm afraid you're stuck until AT&T releases 4.3 and you can run a RUU.
iElvis said:
I forgot Mike updated that link.
Okay, I see what you did now. You've essentially upgraded your phone to a GE because the android-info.txt in this official firmware matched your MID and CID; that allowed it to run. The problem is that you can't go back now because you're s-on. Your phone won't boot because you have the GE kernel installed but I assume a Sense rom.
This should be easy to fix. You can flash custom recovery now that you've unlocked, then flash a custom rom. This will get your kernel and rom consistent again and you should be able to boot.
Unrooting is a different story. You can't go back to the stock configuration you had when you got the phone without s-off, which you can't get on 1.54 hboot. I'm afraid you're stuck until AT&T releases 4.3 and you can run a RUU.
Click to expand...
Click to collapse
So no getting my white bootloader back till next release? That's ok.
However, how do I flash the custom ROM. I got the customer recovery going but I don't know how to get the ROM on there.... Flashing isn't working, still getting signature failures.
Sorry
Tylegn said:
So no getting my white bootloader back till next release? That's ok.
However, how do I flash the custom ROM. I got the customer recovery going but I don't know how to get the ROM on there.... Flashing isn't working, still getting signature failures.
Sorry
Click to expand...
Click to collapse
You can only run a later firmware. When the signed 4.3 Sense firmware is released (it may be there now), you should be able to run that and get back the stock HTC bootloader.
You need to adb push the rom file onto your phone. There is a tutorial for doing it here: http://forum.xda-developers.com/showthread.php?t=2317986
iElvis said:
You can only run a later firmware. When the signed 4.3 Sense firmware is released (it may be there now), you should be able to run that and get back the stock HTC bootloader.
You need to adb push the rom file onto your phone. There is a tutorial for doing it here: http://forum.xda-developers.com/showthread.php?t=2317986
Click to expand...
Click to collapse
Thank you so much! I believe I can take it from here.....Until I brick my phone when the signed 4.3 comes out. LOL
Until next time. Thanks iElivis you are a BADA$$!:good::good::good:
Hi,
First of all, accept my apologies in advance if i sound a complete NOOB, cuz really I am. Im just looking for some help regarding the know-how of the phone I just bought.
We dont get locked phones in my country ( and by locked I mean like as u say these At&T and verizone or Sprint etc locked). I bought a silver HTC One and have been using it all fine and easy until I saw this blue HTC one( a used one) SO I exchanged my phone and now I have this blue HTC one...
The info from the software information is:
Android Version - 4.2.2
Sense - 5.0
Software number - 2.24.401.8
HTC SDK API level - 5.34
Kernel version - 3.4.1 - g28df0d6 [email protected] #1 SMP PREEMPT
Build number - 2.24.401.8 CL235216 release-keys
(guess thats all there is to tell)
But apparently it is not working as it should. And by that I mean I tried hard resetting it and a weird screen came on...
it goes like this ....
TAMPERED ... and so on... and then there were other options like to Fastboot, factory reset etc that I could select from the volume keys..
So i got afraid that things are a little bit more technical than I can handle so i dint reset it.
- Now, the thing is I want to know that if my phone is unlocked than what carrier it originally was - whether resetting will lock me to that carrier or not?
- Apparently my phone was rooted ( dont know for sure, although I downloaded the root checker from play store and it says that I have root access ) SO why was it rooted in the first place. CAN it be that by rooting, my phone was unlocked from the carrier?
- IF i want to return to stock, how can I do that?
- Will returning to stock render my phone useless?
- Im upgrading to And 4.3.. but is it safe to do that with the state of my phone...?
By now, Im sounding like a complete BUM even to myself... so... but I really need help...
Unlocked network is not the same as unlocked bootlooter. Rooting will do nothing with the network lock (although there are some apps that can network unlock using root).
As for the screen you saw, that's the recovery screen which is acces via power + vol up, that's normal and is where you can reset your phone. "TAMPERED" means that the bootloader was unlocked before (to allow ROM flashing) but has been relocked to try make it stock again. I guess that means you bought it second hand?
Follow this guide if you wish to return to stock: http://forum.xda-developers.com/showthread.php?t=2358738. Make sure to take note of your CID, which you can see at the top of the recovery screen or using CID getter, and getting the RUU that matches it.
Once you followed that guide you should have a completely stock device that's got a locked bootloader, S-On and without the TAMPERED flag (so HTC does not know it's been rooted) with the stock firmware. Then just boot into the phone, set it up, and check for updates in the settings and it will upgrade to the latest version for your CID (either 4.3 or 4.4).
Ok, according to the CID getter, my CID is HTC_001, so now,
I go find the RUU for the HTC_001 and then do all that what was said above. I wanted to ask one thing before doing anything.. I bought this phone second hand.. Yes.. how can i tell that whether its and international version or an unlocked version for some network. It has no tell-tale logos of any network on it. Is there any sure shot way of telling which one is it?
Here is the info from the TAMPERED screen.. just thought about posting it so that if could further help in anyway..
***TAMPERED***
*** RELOCKED ***
*** Security Warning ***
M7_UL PVT SHIP S-ON RH
HBOOT-1.54.0000
RADIO 0-4A.17.3250.14
OpenDSP-v31.120.274.0617
OS-2.24.401.8
eMMC-boot 2048MB
Aug 9 2013, 16:15:36.0
CID tells you if it's been locked down to a carrier. HTC__001 (two _) is the unlocked UK version. So it's never been locked to a network, and I guess the previous owner just wanted to play around with cutsom ROMs.
I have managed to S-off my phone and downloaded the files required.. Im not sure about one thing.. is the kernel on my phone a stock one or what?
I have this Kernel version - 3.4.1 - g28df0d6 [email protected] #1 SMP PREEMPT
which one is it?
hey.. can someone point me out to the right RUU for my phone..?
Im tryin to match all these things but somehow one or the other stays diff..
rteepu said:
hey.. can someone point me out to the right RUU for my phone..?
Im tryin to match all these things but somehow one or the other stays diff..
Click to expand...
Click to collapse
You need the 1.28.401.7 ruu.exe from here http://www.htc1guru.com/downloads/ruu-file-downloads/
but you will need to downgrade hboot to 1.44 before.
Now.. DO I REALLY NEED TO REVERT BACK TO STOCK?
I mean, i just found mod (maximus HD) inside my phone and flashed that using cwm.
I have no problems so far and I do not have to send the phone back for warranty or anything, so do i really need to get back to stock? Cuz i think for that my expertise are lacking atm. I just wanted to update to the latest android... but figure i can do that using the same method i did for the maximus rom... no?
Any thoughts?
rteepu said:
Now.. DO I REALLY NEED TO REVERT BACK TO STOCK?
I mean, i just found mod (maximus HD) inside my phone and flashed that using cwm.
I have no problems so far and I do not have to send the phone back for warranty or anything, so do i really need to get back to stock? Cuz i think for that my expertise are lacking atm. I just wanted to update to the latest android... but figure i can do that using the same method i did for the maximus rom... no?
Any thoughts?
Click to expand...
Click to collapse
its up to you, if you don't have to send the device for repair then its not needed to revert back to stock and you can use your phone with the custom rom if you like it.
Hey, a quick question...
Will wiping the phone before flashing a custom ROM wipe my recovery image too? Im using TWRP. And just before hitting wipe, i thought what if this wipes my twrp as well.. So, I stopped and rushed here... anyone?
Here is what i was gonna do.. I moved the ROM zip into the internal storage of my phone --- > went into the recovery (TWRP) using GOO app ---> was gonna do the wipe (here is where I stopped) ---- %% after the wipe, i was going to "Find in Recovery "Choose zip from sdcard" choose appropriate zip file" and then follow the Aroma installers instructions ----%% reboot.
@alray
Thanks man..
As long as I have access to this forum, I feel brave enough to continue messing around with my phone.
rteepu said:
Hey, a quick question...
Will wiping the phone before flashing a custom ROM wipe my recovery image too? Im using TWRP. And just before hitting wipe, i thought what if this wipes my twrp as well.. So, I stopped and rushed here... anyone?
Here is what i was gonna do.. I moved the ROM zip into the internal storage of my phone --- > went into the recovery (TWRP) using GOO app ---> was gonna do the wipe (here is where I stopped) ---- %% after the wipe, i was going to "Find in Recovery "Choose zip from sdcard" choose appropriate zip file" and then follow the Aroma installers instructions ----%% reboot.
@alray
Thanks man..
As long as I have access to this forum, I feel brave enough to continue messing around with my phone.
Click to expand...
Click to collapse
No, wiping will not clear your recovery partition
Sent from my HTC One using xda app-developers app
Hello, I apologize in advance if I'm wrong section or anything like that ..
my htc is not 'a google edition factory but a few months ago I changed the cid and flashed
a ruu google edition and until a few days ago all good ..
unfortunately I had to format everything from cwm recovery and re install a ruu not successful, I found myself without os after several attempts I managed to put it back
now I'll post some specific
tempered
relocked (I can unlock it)
m7_ul pvt ship S-ON rh
hboot-1.54.0000
os-3.58.1700.5
now .... how can I do to install a rom and at the very least be able to turn it on?
thank you very much in advance I hope someone will be able to help me <3
edit: I forgot ... the cid is 'GOOGL001, I can not turn it on so I can not do s off to ... I flashed the boot and recovery and then the firmware but still not turn onD:
trying to flash a ruu from rebootRUU --> error signature verify fail --- 12 ---
Is your recovery working?
If so, maybe try flashing a stock GPE ROM.
Sounds like you used a custom "RUU" (maybe the one by graffixnyc) to install GPE the first time.
The same ROM is available as a standalone download (look for a thread by bigxie).
If recovery is not working you may have challenges. Me personally, I would want S-OFF before doing anything else.
Sent from my HTC One using xda app-developers app