[Q] Use old fashioned bin backing to trick CDMA One V? - HTC One V

was thinking about the issue with the newer hboot for the cdma one v not being able to be reverted to the original hboot so there is no special kernel needed to run rom because of the version error about the original hboot being to old. couldnt the information the device uses to determine whether or not the hboot is to old be bin hacked to reflect false information about the version so you could revert back? trick the device to believe it is in fact flashing a newer hboot vs the original. there has to be header info in whats being flashed that the device uses to determine version.

Related

[Q] Little Help with a radio change

First off i have been looking for about a day now as to how to change the radio, i found people changing back from stock but i think i have a different issue. the camcorder and gps along with a few other things do not work and i think it is because i have an old radio installed.
What i have now is the virtous rom, s-off, rooted(obviously) , clockwork mod, and the current radio is 1.00.03.04.06. the old non 2.x radio is what i belive to be the problem (please correct me if im wrong) so if someone could point me to a guide on how to upgrade just the radio id appreciate it.
P.S. i saw somewhere that i must unroot before a radio can be applied but that doesnt make much sense to me.
You rename the file pb31img and then boot in to hboot. Hboot will identify the file as a radio and you press vol up to install.
You must have soff to do this.
Sent from my HTC Incredible

[Q] Hboot - same data but renamed

I know nothing about developing so i'm dropping this in here.
Since when you are trying to update your hboot and roms from the newest version and the process gets stopped at the point where it checks for the version, would it be possible to take an old hboot 2.10 say, then just rename it to the next or newer version number that was used in the recent OTA?
seems its bogging down at that check?
From what I've gathered reading all the threads I believe any modification will break HTC's security signature and throw red flags
this is correct, i can guarantee you , this and many other simple ideas have been tried, goldcard, swapping sd cards midupdate, exploit has not been found yet afaik , not for evo anyways, just the 3d

[Q] Returning from the Dead

Hello Supersonic Community,
I come to you in my time of need, I have spend the last 3 days at work trying to downgrade an Evo 4g to 2.1. from 2.2.
Initially I ran unrEVOked3 reflash package as from what I read it would probably be the easiest place to start from an unrooted 2.2.
Once I was rooted on 2.2 I followed the guide from here
and used the RUU/Zip files from here
I currently have the phone in a state where it will only load into the bootloader and I do have a working amon ra recovery.
When I try flashing the RUU's PC36img.zip file from hboot I see that it "checks" the zip file however I am not prompted to run the update.
and when trying to run the RUU zip file from recover it says there is not update script.
My main question is if anyone knows why I am not prompted for the update from Hboot or if its possible to flash from recovery back to stock 2.1
I come from a Nexus S and HTC Desire background and have a bit of knowledge just kinda stumped right now on this one. I am currently trying different SD cards for the hboot flash as I have read that it can be a bit finicky.
Thanks in advance for any help.
PHone info
Android version 2.2
Baseband version 2.12.00.09.01
Kernel version 2.6.32.15-ge2fb08e
[email protected] #11
Build number 3.29.651.5 CL252548 release-keys
Software number 3.29.651.5
Browser version Webkit 3.1
PRI version 1.77_003
PRL version 60675
Hardware version 0003
h-boot 0.79.00
It all goes back to the Hboot version you have. I think it's anything over 2.10 you can't downgrade.
I think your best bet is to just flash a stock/Rooted 2.1 ROM or a custom Froyo ROM
Well my HBoot is .79 so I hopefully can recover to 2.1.
I basically can't have a rooted phone, I work in mobile QA and we can't test on devices that are rooted. Which I know is a bit retarded but thats how it works for us right now.
If I flash a stock 2.1 rooted Rom I should be able to unroot.... at the very least uninstalled su and my boss won't know hehe
Thanks for your reply.
Did your phone come with that hboot? If your hboot and radio match the ruu you are trying to flash, then it should be good to go. If you r s-off while trying, even better. Do you have 20k or 40k block sizes?
Sent From My Pocket
{ParanoiA} said:
Did your phone come with that hboot? If your hboot and radio match the ruu you are trying to flash, then it should be good to go. If you r s-off while trying, even better. Do you have 20k or 40k block sizes?
Sent From My Pocket
Click to expand...
Click to collapse
**********HBOOT VERSION IS .79 *************** TYPO IN OP
That would be the Hboot it came with these are testing devices at my work. they are ALL STOCK unless i personally change it as no one else here handles the android phones.
I am unsure of the 20/40 k block sizes you are referring too do you mean on my sd card?
So i have successfully flash a rooted 2.1 stock rom and am trying to uninstall super user. If anyone has any tips on this let me know
Issue resolved.
Set phone into recovery and used ADB to remove the Superuser apk
Thanks for the help

[Q] Updating HBOOT

So I've recently decided to get the newer version of the Cyanogenmod for my One X (Android 4.2). However, after finding out that I get an error each time I try to install the new version, I did some searching and realized that I needed the newer version of HBOOT. I now know how, but I get the warning that after doing so, I will be unable to install a non-sense ROM. Is that so, and if true, is there a way around it apart from installing an earlier version of Cyanogenmod? Thank you
Not true afaik. Aosp roms runs fine on the higher hboots (JB). In fact there are JB non sense roms that need a JB hboot to run ! Do you have some links where that is written ?
http://forum.xda-developers.com/showthread.php?t=1786696
Quote: 'supports only newer hboots (1.28 and above)' - written in red. I think I have 1.12.
It confirms that you need a JB hboot of 1.28 at least....or higher, so it wont run on 1.12. You need to update the hboot in order to run it......so the question about not being able to run a Aosp rom on the higher hboots is not true ! You need one to run them
Thanks - just wanted to check to make sure I don't do anything wrong by upgrading the HBOOT.
Nope ....go right ahaed and flash CM10.1 after

Unable to find/install stock RUU on hboot 1.57

I did a little too much screwing around with my One V earlier today, and I'm honestly afraid that I've hard-bricked it at this point. I have middling experience when it comes to RUU installs and flashing/experimenting with new ROMs and kernels - but my last root/ROM flash attempt didn't go as planned. I'd installed the stock RUU earlier in the day in order to get the radio update (which, as I now realize, was more or less pointless as the new radio sounds like it's a pain to deal with), and had just finished unlocking and rooting the phone. I booted into TWRP to flash my favorite ROM, and I'm pretty sure this is where I messed up: rather than just wiping System, Cache, Dalvik, and Factory Resetting, I opted to wipe everything I could select in that menu. Please don't ask why (I was tired and out of it, and had planned on re-formatting my SD card at some point - it made sense at the time...) - I now realize how stupid this was, and I'm going out of my mind trying to fix it.
I thought it would be a simple matter of flashing the RUU file I currently have, but alas, I now have hboot 1.57 and the newest radio version - so I get an "hboot is older!" error when I attempt to install this older RUU. I can't locate an RUU based on hboot 1.57, and I'm not sure whether I'm just looking in the wrong places or interpreting RUU filenames incorrectly (perhaps certain RUUs would prove compatible despite incorporating a slightly downgraded hboot...?).
Any help you can offer would be greatly appreciated - if you need any more information from me in order to provide a solution, please let me know and I'll respond as quickly as I can.
EDIT: I have a CDMA One V.
don't boots said:
I did a little too much screwing around with my One V earlier today, and I'm honestly afraid that I've hard-bricked it at this point. I have middling experience when it comes to RUU installs and flashing/experimenting with new ROMs and kernels - but my last root/ROM flash attempt didn't go as planned. I'd installed the stock RUU earlier in the day in order to get the radio update (which, as I now realize, was more or less pointless as the new radio sounds like it's a pain to deal with), and had just finished unlocking and rooting the phone. I booted into TWRP to flash my favorite ROM, and I'm pretty sure this is where I messed up: rather than just wiping System, Cache, Dalvik, and Factory Resetting, I opted to wipe everything I could select in that menu. Please don't ask why (I was tired and out of it, and had planned on re-formatting my SD card at some point - it made sense at the time...) - I now realize how stupid this was, and I'm going out of my mind trying to fix it.
I thought it would be a simple matter of flashing the RUU file I currently have, but alas, I now have hboot 1.57 and the newest radio version - so I get an "hboot is older!" error when I attempt to install this older RUU. I can't locate an RUU based on hboot 1.57, and I'm not sure whether I'm just looking in the wrong places or interpreting RUU filenames incorrectly (perhaps certain RUUs would prove compatible despite incorporating a slightly downgraded hboot...?).
Any help you can offer would be greatly appreciated - if you need any more information from me in order to provide a solution, please let me know and I'll respond as quickly as I can.
EDIT: I have a CDMA One V.
Click to expand...
Click to collapse
Well i dont have a CDMA one v but i know that the RUU for hboot greater than v1.17 had not been released.. So the best method to recover stock ROM is using a stock ROM backup with the same hboot and radio version , if anyone bought a one v recently he should be on the latest hboot and radio version , you can get a stock backup from such a person or search on xda for such a backup..
There isn't a RUU for the Hboot 1.57 and the newest radio. Sorry to give the bad news. You will either have to use a nandroid backup or install one of the custom roms such as RhythmicRom, e3remeSense or myOneV. Good luck on your rooting journey!
Thanks. I ended up successfully installing Rhythmic, but I can't get x3reme Sense (my preferred ROM) to work, for some reason (which is sort of ironic - I know Rhythmic incorporates a fix to allow for compatibility, but I thought one of the OTA updates was supposed to prevent installing anything not based on Sense). Oh, well.
If you'll use this kernel, then x3reme Sense will boot. I tried it for a while, but for a sense based rom I prefer myOne. If you want to try it, Cyanprimo will boot and run fine with the RhythmicRom v1.2 kernel. That is my daily driver(at least for now).
http://forum.xda-developers.com/showthread.php?t=2261819

Categories

Resources