So I see a number of people reporting using Baseband: 1.13.11.1105, including Captain_Throwback. I'm on Baseband: 1.13.11.0830 and am having some trouble with the phone connection - dropped calls, static on the line, etc. but data is fine (in fact I can make voip calls through hangouts no problem, but incoming calls are normal phone).
I looked at C_T's firmware collection on themikmik but that only contains up to Baseband: 1.13.11.0830 with the 3.17 software version.
I'm S-OFF via rumrunner after having flashed the 2.10 hboot and 4.13 651.4 Sense 5 Android 4.3 - Deodex to update the partitions to the new format. I've since flashed CM11 snapshot M12. Same phone issues on the rooted Sense and CM11.
Thanks to Captain_Throwback for all the excellent guides and collections here. Any suggestions from you or anyone here on where to find the latest baseband, and if you think this or maybe a custom PRL may help. (Is it possible to flash a custom PRL in CM11 or do I have to flip back to my Sense nandroid first?)
Thanks!
The baseband you're looking for can be found with the 4.3 RUU. You can find said RUU in the first post of my Hboot thread (top link in my sig). Not sure how you updated your Hboot but not your firmware, but I suggest running the RUU. You'll remain S-off afterwards.
To answer your other question you have to be running a Sense ROM to install a custom PRL.
OK that's what i thought - that the baseband should come with the hboot. Can i try just the 2.10 hboot in captain_throwback's thread or does it need to be the full ruu? Otherwise the process would simply be to backup, ruu, flash recovery and restore, right?
Related question, is 2.8.0.3 the latest twrp that works with cm11 or is there a 2.8.1.0 that works as well?
cmags said:
OK that's what i thought - that the baseband should come with the hboot. Can i try just the 2.10 hboot in captain_throwback's thread or does it need to be the full ruu? Otherwise the process would simply be to backup, ruu, flash recovery and restore, right?
Related question, is 2.8.0.3 the latest twrp that works with cm11 or is there a 2.8.1.0 that works as well?
Click to expand...
Click to collapse
I would run the RUU. Once done, you'll need to unlock and install TWRP again. Then you can restore your backup. As far as recovery goes I'm not sure which is most recent.
Well, that was only partially successful, and I could use some suggestions.
I did a nandroid of my CM11 M12 snapshot image, and ran the RUU in your post (RUU_JEWEL_CL_JB43_SENSE50_MR_Sprint_WWE_4.13.651.4_R…igned_one_step.exe).
Afterwards Hboot is 2.10, and Radio is 1.13.11.1105. Great. Bootloader remains S-OFF (expected), and unlocked (unexpected, but cool).
I run fastboot flash recovery TWRP-Recovery-2.8.0.3-jewel-CPTB.img. Boot into recovery, restore my CM11 image, and reboot. Phone just spins on the boot animation.
Rebooted into recovery, wiped cache/dalvik/system/data, install flash CM fresh, wipe again, then restore (without boot) - same issue. About to wipe again and try restoring Sense nandroid, or flashing roms (CM and Sense) anew to see if i get different results.
Any other thoughts? Any way to verify the partition layout? Any way to get a log of what its hung up on while spinning the boot animation?
Thanks!
The issue you're describing reminds me of the issue that comes about from being S-on and having to flash the kernel separately from the ROM. You say you're S-off so that's not the issue, obviously. If you ran the RUU then you are on the new partition layout. Not getting any errors in recovery when you flash the ROM, are you? You might want to 're-download the ROM, check the MD5, and flash again.
Got it sorted out. Something must have gotten corrupted in the nandroid. A stock nandroid worked fine. So i restored cm11 then flashed the rom over the top to fix the boot partition. Im all set now, though the updated baseband didnt fix the static and dropped calls. Must be a hardware issue.
Related
So... I flashed scrosler's Stock Rooted RUU 3.14, and once that was cleanly on and working I got into amonra and cleared data, flashed Venasaur 3.1, and then in Hboot ran the 3.14 kernel again.
How did I go wrong and what's the simple fix that will get me with the pokemon? ~thanks <3
(I'm getting bootlooped that is)
You flashed an incompatible kernel. Are you s-on or s-off? If s-off just flash the Rom again in amon ra and reboot phone. No need to install a kernel it will do it for you. If s-on you need the kernel for venasaur Rom which may need to be flashed in fastboot unless someone has made it into a flammable zip. If s-on might as well take the plunge and s-off. It's a very easy process.
sent from my Clean Rezound
I am S-on, as soon as I find something condutable and more reliable than a paperclip i'll probably do S-off haha
I don't think anyway has, I just time getting the image boot file off of the rom and running it in H-boot, I still get a bootloop (I'm genuinely surprised that it didn't work), that's a pretty sticky situation, i'm stuck without a phone until that's solved =(
I repeal that statement, taking the boot.img out and flashing it in hboot worked, wonderful! thanks =)
Question for you?..
Now that that you have your Venusaur 3.1 running..are you having any issues with Wifi?
I did the re-lock, android police ruu, unlock, install recovery, clean wipe x10, install venusaur 3.1, and then installed sense4 boot image for the venusaur rom. However I keep getting Wi-fi Errors, I'm guessing my wifi modules are wrong but I'm just trying to figure out where I may have messed up. I tried flashing the wifi modules provided by http://forum.xda-developers.com/showthread.php?t=1642217 but no go...any ideas?
well i'm fairly curious how you were able to get the sense4 boot image, it gave me a mainver error, I took the boot image out of the rom and ran that.
Which got me in, and wifi isn't giving me a problem surprisingly, but I'm now curious to how your supposed to go 3g with the new setting setup.
My Sd card also can't mount I'm not sure if that's related to 3.14 and pokemon rom or just my terrible flashing
Watercycle, are you still having problems? If you flashed Scott's Rom that is not an ruu. I believe you are still o n the old firmware. You will need to go to nilsp business Rom in the development section and download the old firmware patch (i think it's in the 4th post) then flash in amon ra. You should be set after that.
sent from my Clean Rezound
actually I flashed scott's 3.14 deodex and old firmware patch + boot img before flashing the pokemon and pokemon boot img
I'm currently only struggling with the issue of sd card mount now
Watercycle said:
actually I flashed scott's 3.14 deodex and old firmware patch + boot img before flashing the pokemon and pokemon boot img
I'm currently only struggling with the issue of sd card mount now
Click to expand...
Click to collapse
The patch may still be on your sd card from Scott then and if not go to the thread I suggested. Just boot to recovery and flash the patch again. You will need that patch for any ics Rom you run because you are still on gb firmware. Don't panic your almost there.
sent from my Clean Rezound
how can you tell if your on old gb firmware? =( since it still boots up and works
darnit I thought i was on ics after that full ruu =o
so after having flashed the pokemon in Hboot i flash the old firmware again? (i'm scared it will bootloop me because i finally got it working haha)
ZombieCodeMonkey said:
Question for you?..
Now that that you have your Venusaur 3.1 running..are you having any issues with Wifi?
I did the re-lock, android police ruu, unlock, install recovery, clean wipe x10, install venusaur 3.1, and then installed sense4 boot image for the venusaur rom. However I keep getting Wi-fi Errors, I'm guessing my wifi modules are wrong but I'm just trying to figure out where I may have messed up. I tried flashing the wifi modules provided by http://forum.xda-developers.com/showthread.php?t=1642217 but no go...any ideas?
Click to expand...
Click to collapse
I briefly searched the venasaur thread (which you can do to) and found most people having WiFi issues either had the wrong kernel or just reset their router and bam, WiFi works. I can't help you anymore then that so you may want to ask in that thread.
Edit: did you unzip the Rom and get the boot.IMG there or did you download seperate? If you didn't unzip and take it out of the Rom then try that. You should be good.
sent from my Clean Rezound
What ruu did you use?
sent from my Clean Rezound
Give me like 20 minutes to get back to you...heading home....motorcycle can't multitask at night more obvious to others haha
Sent from my ADR6425LVW using Tapatalk 2
snow, since I sucsessfully was on
This
will flashing the old gingerbread fix my sd mounting or break everything?
sorry I have to be more direct, gotta get some sleep now =)
Watercycle said:
snow, since I sucsessfully was on
This
will flashing the old gingerbread fix my sd mounting or break everything?
sorry I have to be more direct, gotta get some sleep now =)
Click to expand...
Click to collapse
I think so
Watercycle said:
snow, since I sucsessfully was on
This
will flashing the old gingerbread fix my sd mounting or break everything?
sorry I have to be more direct, gotta get some sleep now =)
Click to expand...
Click to collapse
It will fix your sd card. You never ran the ruu if all you flashed was Scott's rooted, deodexd Rom. If you get with me tomorrow I can walk you through the ruu but I think at that point you might as well s-off. Time to find that wire
sent from my Clean Rezound
If you could see your sd card on Scott's Rom it was because of the patch. Make sure you report back. I need some sleep.
sent from my Clean Rezound
Okay...
I re-locked my bootloader using the usual, fastboot oem lock.
then I download the full leaked RUU from Android Police, androidpolice.com/2012/05/07/exclusive-download-htc-rezound-ice-cream-sandwich-build-3-14-605-5-brings-a-handful-of-fixes-and-newer-radios/"
Booted to Hboot with that file on the SD card in the proper name, completely flashed the phone with the Leaked RUU
Once OS loaded, rebooted back to fastboot and used hTcdev.com to unlocked my bootloader again. (I do not have S-Off yet).
Then I downloaded and flashed through fastboot commands the TWRP 2.1.1. Touchscreen recovery.
Once this was done, I downloaded and installed Venusaur 3.1.0 through recovery after performing scot's superwipe x10,
Then fastboot flashed the boot.img for the sense 4.0 roms.
Wi-Fi does not turn on at all...It will state Turning on...but not to long after will give error.
So after all of that I tried grabbing the wifi module.zip from one of the stock rom de-odexed rooted 3.14.605.5 roms, and tried flashing that through recovery and manually adding the file through root explorer..nothing.
Hope that helps clarify.
Also i would through an inquiry to there thread but I don't have enought posts yet to post in development.
ZombieCodeMonkey said:
Okay...
I re-locked my bootloader using the usual, fastboot oem lock.
then I download the full leaked RUU from Android Police, androidpolice.com/2012/05/07/exclusive-download-htc-rezound-ice-cream-sandwich-build-3-14-605-5-brings-a-handful-of-fixes-and-newer-radios/"
Booted to Hboot with that file on the SD card in the proper name, completely flashed the phone with the Leaked RUU
Once OS loaded, rebooted back to fastboot and used hTcdev.com to unlocked my bootloader again. (I do not have S-Off yet).
Then I downloaded and flashed through fastboot commands the TWRP 2.1.1. Touchscreen recovery.
Once this was done, I downloaded and installed Venusaur 3.1.0 through recovery after performing scot's superwipe x10,
Then fastboot flashed the boot.img for the sense 4.0 roms.
Wi-Fi does not turn on at all...It will state Turning on...but not to long after will give error.
So after all of that I tried grabbing the wifi module.zip from one of the stock rom de-odexed rooted 3.14.605.5 roms, and tried flashing that through recovery and manually adding the file through root explorer..nothing.
Hope that helps clarify.
Also i would through an inquiry to there thread but I don't have enought posts yet to post in development.
Click to expand...
Click to collapse
Why are you not s-off? Makes life much easier. What I have concluded is that you need to start over. You have the wrong kernel. Wipe everything then flash the Rom in recovery. You will have had to unzip the Rom on your pc then take the boot.IMG out and flash this in fastboot to the phone. I don't think there is a ph.zip file for this. There are very good directions if you search that thread.
sent from my Clean Rezound
Sorry guys but it's bed time. If you both follow those directions you should be fine. If not get with me in the morning.
sent from my Clean Rezound
So i ran the RUU for ICS through the bootloader (i am s-off). After I booted into the stock OTA, I flashed my TWRP recovery and then restored my nandroid of NeoMax 1.6 i had made just before flashing the RUU. So my question is does restoring my nandroid I made before flashing the RUU wipe out my flash of the official ruu putting me back where i was before i flashed the latest ICS RUU? any clarification would be really great. I basically just wanted to get back to having my phone and rom set up how i liked it because i am so sick of doing it over and over again. Also, would restoring only certain parts of my nandroid in TWRP change anything? Thanks again for any help
Software wise, not really. Firmware wise, not at all.
I don't want to be giving my friend the wrong information. When his sprint 3d was boot 1.5 I took it and soff it for him downgrading to 1.4. Now recently he upgraded to hboot 1.58 and it says relocked at the top. Of course he still has recovery and still is rooted.
My question is since his phone is soff can't he just still flash whatever with no issues? Does he have to do dev unlock again?
I own a rezound and have had many HTC devices and soff has always been the key to everything for me. Any help would be appreciated
With s-off there's no need to unlock his boot loader again. (For example) If he wants to flash an aosp rom, all he's gotta do is downgrade his hboot via boot loader.
Perfect. Already installed JP bear latest hboot and went to twrp. Making a backup now. That's what I was thinking but I wanted some confirmation. Its been a while since I messed with an Evo 3d
Hmmm. It won't flash paranoid android. Even tried the 1.04 eng hboot. Any ideas? Using twrp recovery. Latest radios and 1.04 eng hboot.
stkiswr said:
Hmmm. It won't flash paranoid android. Even tried the 1.04 eng hboot. Any ideas? Using twrp recovery. Latest radios and 1.04 eng hboot.
Click to expand...
Click to collapse
A lot of people have had better luck with 4EXT on the Evo 3D. You can download the Recovery Updater for free from the www.4ext.net website and install the current version of 4EXT Recovery from that app. Then "format all partitions except SD card" in the wipe/format menu of the recovery, and try flashing PA again.
ramjet73
ramjet73 said:
A lot of people have had better luck with 4EXT on the Evo 3D. You can download the Recovery Updater for free from the www.4ext.net website and install the current version of 4EXT Recovery from that app. Then "format all partitions except SD card" in the wipe/format menu of the recovery, and try flashing PA again.
ramjet73
Click to expand...
Click to collapse
K. I'm working on that now. I let you know soon its backing up now. Thank you for the heads up. Do you think I should go back yo the latest jbear hboot? Or just leave the 1.04 eng hboot? He wants to be able to run these jellybean builds that are out
stkiswr said:
K. I'm working on that now. I let you know soon its backing up now. Thank you for the heads up. Do you think I should go back yo the latest jbear hboot? Or just leave the 1.04 eng hboot? He wants to be able to run these jellybean builds that are out
Click to expand...
Click to collapse
Stay with the ENG 1.04 hboot for now. The GB and AOSP based ROM's won't boot with the latest JBear (1.58.5858) so if you want to use a JBear version 1.50.5050 is better.
ramjet73
ramjet73 said:
Stay with the ENG 1.04 hboot for now. The GB and AOSP based ROM's won't boot with the latest JBear (1.58.5858) so if you want to use a JBear version 1.50.5050 is better.
ramjet73
Click to expand...
Click to collapse
Wow thank you for all the help. I just did everything and unfortunately it is just stuck in a never ending splash loop. Doesn't seem like the kernel/boot is being flashed. Made a backup so I should be good. Just sucks doing all the steps and being stuck.
What kernel are you flashing with pa?
Jsparta26 said:
What kernel are you flashing with pa?
Click to expand...
Click to collapse
It doesn't come with a kernel?
stkiswr said:
Wow thank you for all the help. I just did everything and unfortunately it is just stuck in a never ending splash loop. Doesn't seem like the kernel/boot is being flashed. Made a backup so I should be good. Just sucks doing all the steps and being stuck.
Click to expand...
Click to collapse
Are you doing the "format all partitions except SD card" in 4EXT right before flashing the ROM? Make sure to give it plenty of time to boot since sometimes the first boot can take up to 10 minutes.
ramjet73
stkiswr said:
It doesn't come with a kernel?
Click to expand...
Click to collapse
Well go with ramjets suggestion and try format all partitions minus sdcard along with full factory data wipe and cache/dalvik wipe and see if it boots up all the way.( it couldn't hurt to do all the wipes two or three times before you flash the rom). Just to make sure everything was wiped all the way.
Oh yeah. Step by step . It just never gets past splash. I looked into the ROM downloaded and saw a boot IMG but it really seems like a boot issue. Doesn't make a lot of sense to me. Soff, everything in right place, correct recovery and no boot. Not complaining, he still has his backup he is running and it restores backup correctly.
His phone was soff and he upgraded firmware to the 1.58 so it said locked in hboot. I just flashed 3 dif bootloader with no issues. Its def soff.
Ok, try flashing a different kernel. Try the Mac kernel that's located in Mazda's aokp jb thread. I believe buttered toast came with pa that your trying to flash. It could also be a bad download as well. You could always redownload the rom as well to see if that works. You never know about these things sometimes.
stkiswr said:
Oh yeah. Step by step . It just never gets past splash. I looked into the ROM downloaded and saw a boot IMG but it really seems like a boot issue. Doesn't make a lot of sense to me. Soff, everything in right place, correct recovery and no boot. Not complaining, he still has his backup he is running and it restores backup correctly.
His phone was soff and he upgraded firmware to the 1.58 so it said locked in hboot. I just flashed 3 dif bootloader with no issues. Its def soff.
Click to expand...
Click to collapse
You've tried all the standard stuff to get AOSP ROM's to boot on the Evo 3D. At this point I can only suggest that you flash the 2.89.651.2 SPrint ICS RUU from here, then reflash a custom bootloader and recovery. That will make sure everything is in sync and has cleared up this problem for other users.
You don't need to relock the bootloader (although I think you said it is already relocked) when flashing the RUU if the phone is S-OFF.
ramjet73
Yes, I will try to download ROM again and also grab that kernel.
I soff this phone for him when it was hboot 1.50. Then I reverted to 1.40 via brick method to get it soff. He has ran some form of an hboot/radios update because he was told to do that. Now we are working together and I am trying to fix all his stuff and get him setup correctly. I have an soff rezound and am sure his phone isn't seeing the boot.IMG.
Now today his phone said locked or relocked am not sure. I went ahead an changed his hboot to a recommended 1.04eng hboot. Installed 4ext recovery via the app that was linked. I am downloading gangam style cm10 to test just to see if something will boot. It successfully flashed a sense based ROM and booted fine thru an aroma installer that came with the ROM. In the installer I stated it was soff and had no issues. I will try the ROM and it doesn't boot I will jump back to recovery and flash a kernel and see. Thanks very much for all the help
Well, I have done it all. Not much more I can do. He may try to run the ICS ruu later but I just can't get any cm10 jb based ROM to boot. Y'all have been more than helpful catching me back up to speed on the 3d and while I agree this should be flashing alas it is not booting. I am positive its just not accepting the boot img for what ever reason because it never makes it far enough after reboot from recovery. Just endless quick splash screen reboots.
No problem. I just wanted to add that a lot of users are having weird issues with paranoid android. ( I'm subscribed to the thread) so it could be that your phone doesn't like pa for some reason. ( Not a diss on Lens Flare at All) but he's been having some issues with the rom and is more than likely trying to work on it. Hopefully you can get gangnam style up and running or even aokp jb. If none of these work, I would go with ramjets suggestion and run a ruu and then back to Asop.
Edit: guess you already tried them. Hopefully you get some better luck after you try the ruu method. Good luck.
Hello!
My current phone setup is:
2.13.651.1 710RD stock ROM
1.12.11.0809 baseband
Hboot 1.19
S-ON
htcdev unlocked
TWRP 2.1.8
rooted (SuperSU)
The phone is bugging me to take the 3.16 upgrade. Stock ROMs are fine...I won't be playing around with custom ROMs (don't have time right now), and I don't need S-OFF.
After reading and researching, I'm still not sure how to go about upgrading, or if it is a good idea. There seem to be issues with the 3.16 stock ROM and TWRP, a number of users having trouble gettings ROMs flashed in, etc.
From where I'm at now, is the 3.16 upgrade worth it?
What would the procedure be?
1) Back up with Titanium
2) Relock
3) Take the OTA upgrade
4) htcdev unlock
5) Install recovery and root (install what version of TWRP?)
6) Restore Titanium backup
Seems like something is missing between (2) and (3).
Thanks for any suggestions and advice!
Not 100% sure but I believe you need to flash a stock recovery for the ota to work. So step 2.5 would be flash stock recovery.
{ParanoiA} said:
Not 100% sure but I believe you need to flash a stock recovery for the ota to work. So step 2.5 would be flash stock recovery.
Click to expand...
Click to collapse
Gotta do that BEFORE relocking.
Ahhh yes...flashing the stock recovery before relocking. Thanks for the tip!
I'm still a bit confused about the touch sceen problem, and exactly when that problem occurs. According to some posts, it seems to affect some versions of TWRP. If I flash TWRP after taking the 3.16 OTA upgrade, will the touch screen work in TWRP?
Thanks again!
jbhtexas said:
Ahhh yes...flashing the stock recovery before unlocking. Thanks for the tip!
I'm still a bit confused about the touch sceen problem, and exactly when that problem occurs. According to some posts, it seems to affect some versions of TWRP. If I flash TWRP after taking the 3.16 OTA upgrade, will the touch screen work in TWRP?
Thanks again!
Click to expand...
Click to collapse
As long as you flash TWRP 2.4.1.0, your touch screen will work fine.
Captain_Throwback said:
As long as you flash TWRP 2.4.1.0, your touch screen will work fine.
Click to expand...
Click to collapse
Captain. I am new to being S-OFF. Can I take the OTA and it not affect my S-OFF state. This is the first time an OTA has come out and
my phone being S-OFF.
Unlocked
S-OFF
Recovery: TWRP 2.3.3
Device: HTC Jewel/PJ75100 (EVO 4G LTE) | Hardware Version: 0003
Baseband: 1.12.11.1119 | PRI: 2.87_003 | PRL: 25012
HBOOT: 2.09.2222
michaeldm said:
Captain. I am new to being S-OFF. Can I take the OTA and it not affect my S-OFF state. This is the first time an OTA has come out and
my phone being S-OFF.
Unlocked
S-OFF
Recovery: TWRP 2.3.3
Device: HTC Jewel/PJ75100 (EVO 4G LTE) | Hardware Version: 0003
Baseband: 1.12.11.1119 | PRI: 2.87_003 | PRL: 25012
HBOOT: 2.09.2222
Click to expand...
Click to collapse
If you're S-OFF, taking an OTA won't change that.
Captain_Throwback said:
If you're S-OFF, taking an OTA won't change that.
Click to expand...
Click to collapse
Thanks fort the help captain. been looking for that answer for the longest.
I ahve 2 more question.
1) When taking the OTA will it replace the recovery with a a stock recovery. I am running TWRP 2.4.1. Will I have to reflash it.
2) Will the OTA relock my bootloader. Do I have to unlock that as well? Is it necessary to be unlock if I am S-OFF?
Thanks for the help.
michaeldm said:
Thanks fort the help captain. been looking for that answer for the longest.
I ahve 2 more question.
1) When taking the OTA will it replace the recovery with a a stock recovery. I am running TWRP 2.4.1. Will I have to reflash it.
2) Will the OTA relock my bootloader. Do I have to unlock that as well? Is it necessary to be unlock if I am S-OFF?
Thanks for the help.
Click to expand...
Click to collapse
1) Yes, taking the OTA will replace your custom recovery with a stock one. You will need to reflash TWRP.
2) When you're S-OFF your bootloader is unlocked. You will just need to flash the latest DirtyRacun HBOOT so that fastboot commands will function, since it will be replaced by a stock HBOOT with the OTA.
You'll have to first flash the DR HBOOT via PJ75IMG.zip, then you'll be able to fastboot flash TWRP.
Captain_Throwback said:
1) Yes, taking the OTA will replace your custom recovery with a stock one. You will need to reflash TWRP.
2) When you're S-OFF your bootloader is unlocked. You will just need to flash the latest DirtyRacun HBOOT so that fastboot commands will function, since it will be replaced by a stock HBOOT with the OTA.
You'll have to first flash the DR HBOOT via PJ75IMG.zip, then you'll be able to fastboot flash TWRP.
Click to expand...
Click to collapse
Thanks you. don't want to seem dense. I am newbie. I understand what you are saying. Is there an order in which these things are done., Is there a link with the steps for dong the previous stated instructions. In which order do I need to do this.
Should I take the OTA first and then try to flash. or do all of the flashing first then take the OTA? I kinda of confused by the order. I already have the latest
HBOOT and RUU (RUU 3.15.651.16 - HBOOT 2.09) from DR. That's How I go S-OFF. If there a set of sequential instructions you can point me to I would be greatly appreciative.
Just an update on how the upgrade went...
The upgrading to 3.16 part went fine, and TWRP 2.4.0.1 is working fine. The restore from Titanium part didn't work great.
First, Titanium says that you can make an adb backup and restore from it after unlocking/rooting. So after the upgrade and before rooting, I made an adb backup since it appeared that all (or most anyway) my settings were retained over the upgrade. That didn't work, as Titanium said the adb backup was corrupted or unrecognized.
Next, when trying to restore my Titanium backup, there was some glitch where I could change to the folder where my Titanium backup was located on the backup folder selection screen (and a backup was recognized there), but this change wasn't internally accepted, and thus when going back to the main status screen, the default folder location was shown, and no backups were found to restore. After rebooting the phone a couple of times, this problem sovled itself, and I was able to restore. For the most part, everything was restored, other than a couple of widgets and settings. I sent a request to Titanium about the adb backup issue, but never got a response so I proceeded to restore the Titanium backup.
However, now I have another problem, but since it's a different topic, I'll start a new thread for that.
I have installed CM 10.2 (Android 4.3) and have tried running an RUU (both through fastboot and the executable) to which they both end up failing. The fastboot states too many threads when writing the bootloader and the Windows executable gives an error 155.
[SOLVED] Look below!
Anyone able to help I am just starring at my boot loader screen all day. TWRP will not even allow me to sideload says cannot mount anything.
So after two days of not having a phone, I solved the issue.
It seems the RUU would not run with the newer version of HBOOT found in the GE version of the rom. So I reflashed HBOOT 1.44 (see attached) and BOOM RUU worked and back to stock!
Hope this helps someone
https://mega.co.nz/#!XhRlXBhB!V8In4VJhp5MXwj9r9gyleTCFiUIbKWxDFmcmn8v3zIU
is that the latest version? I am kind of new to rooting and stuff, I guess when you flash TWRP it replaces HBOOT so that is why you had to reflash HBOOT? I am going to install Android Revolution HD and would like to get all the info beforehand.
schn1tt3r said:
is that the latest version? I am kind of new to rooting and stuff, I guess when you flash TWRP it replaces HBOOT so that is why you had to reflash HBOOT? I am going to install Android Revolution HD and would like to get all the info beforehand.
Click to expand...
Click to collapse
Custom recovery does not replace hboot. You shouldn't have to replace hboot to flash ARHD. You don't even have to unlock the bootloader. Just S-off, flash custom recovery, nandroid backup, and flash ARHD. After Rom is flashed, flash new firmware to update your 1.29 firmware to 2.24
Sent from my HTC One using xda premium
Trying to go back to stock. I too tried the 4.3 firmware and hboot, radio. So right now I am on hboot 1.54 and firmware 3.06.1700.10
I want to go back to stock...any help?