Database Users

[Q] Stock ROM without HBOOT etc. (FM Radio)

Sorry for the newb-ish question. I'm in a mad rush to build my FM app and would prefer not to have to research this issue for hours.
I have my FM app running on Blayo ROM, using btipsd_cli, and I think it should then work on the stock ROMs. AFAICT they also include btipsd_cli.
So I want to test on a stock ROM. Which one should I use ? I'm avoiding the RUU's because I don't want to have to mess with Windows etc.
So I'm looking at: OTA_Legend_Froyo_S_Vodafone_UK_3.14.161.1-2.05.161.1_R_P_release_135177_156984k4i146wit81sj23a.zip
But the embeded firmware.zip includes an HBoot and radio and recovery.
I don't want to lose my S-Off, or my CM recovery.
Can I do this ? What's the easiest/safest way ? Or any other stock ROM I should use ? Perhaps I should test with the oldest ROM and the newest ROM.
Thanks much !

Sure m8. Just extract whichever img you want and flash it via fastboot. I'm not sure about system.img. Some guys reported that flashing system.img doesn't actually work. In that case put it on /sdcard, fire up CWM, format system partition, mount it and then inside adb shell unyaffs the image into /system dir.
EDIT: Ahh one more thing. You can't just install any OTA you want. What OTA does is binary patching of existing files. That said it means you have to have binaries that actually match to their patches but I guess you knew that before
Sent from my HTC Legend

BlaY0 said:
Sure m8. Just extract whichever img you want and flash it via fastboot. I'm not sure about system.img. Some guys reported that flashing system.img doesn't actually work. In that case put it on /sdcard, fire up CWM, format system partition, mount it and then inside adb shell unyaffs the image into /system dir.
EDIT: Ahh one more thing. You can't just install any OTA you want. What OTA does is binary patching of existing files. That said it means you have to have binaries that actually match to their patches but I guess you knew that before
Click to expand...
Click to collapse
Thanks BlaY0 !
No I didn't know about the patching of files. So that's what the *.p files are for... Yuck, that's messy IMO.
I WOULD have known if I spent much time in this area but I haven't. A few months back I finally had my phone in a nice state and haven't looked back. It was VERY painful doing all that, and at least twice I messed up badly and had to restart. So I don't want to repeat that.
I haven't figured out how all the partitions/image files interact, so I won't go down that road at this time. I'm guessing it may not be possible to go back to stock temporarily and then revert to the other ROMs easily.
So for now I think I'll continue to use your ROM as a proxy for a stock ROM and hopefully my app will work as well on stock ROMs. BTW, I'm now running your new 8.4 and it's working very nicely thank you...

Those .p files are standard bsdiff patches. At least they should be, but HTC once again made some internal changing to that so I was unable to manually apply those patches on my PC.
If you are S-OFF which I believe you are, all you have to care about are boot.img and system.img. 1st is image made of kernel + initrd and 2nd is basically yaffs2 image. 1st can be flashed with flash_image and 2nd can be unpacked with unyaffs (after you format system partition and mount it on /system via CWM). All needed tools are available in CWM recovery and they are also part of AOSP and are compiled separately each as its own bin. Flashing can also be done via fastboot, but I'm not sure about HTC's system.img as I'm not S-OFF. You should try that.
Sent from my HTC Legend

Useful Files if You are Having Problems Updating to ICS

A lot of people seem to have the same broken files so I figured I would post a few here. These are all from a US 32GB TpT on OTA2.5 but should work for any US TpT:
Original generic.kl
Original wpa_supplicant
Original gps.conf
Original busybox
My US OTA2 clean nandroid backup (not completely clean, you will need to replace Generic.kl and wpa_supplicant with the files provided above) If you are totally screwed up you can restore this in CWR, replace the two files mentioned, and then proceed to update normally (OTA2.5 then ICS). For US Tablets only!!!
A bunch of system files (I think this was copied when I was still on OTA1 but maybe some files will still be useful if they weren't patched).
The update.zip I flashed to restore stock recovery before updating to ICS. Use at your own risk, it has only been tested once by me. This should not be necessary but may help if you are getting the indigo failure message as I got that message in CWR but not with stock recovery.
Don't change any system files in ICS until someone gets CWR working: if you break your system without CWR you're gonna have a bad time.

I think you should mention which location each file is located at.

bigsnack said:
I think you should mention which location each file is located at.
Click to expand...
Click to collapse
I agree. I need to try this method but need help with the locations of the files that need to be streamlined into the nandroid backup provided.
Hope someone could help out.
Update:
1. Replace generic.kl @ this location: /system/usr/keylayout/
2. Replace wpa_supplicant @ this location: /system/bin/

Getting some MD5 mismatch when I try to restore your backup x.x

yahoowizard said:
Getting some MD5 mismatch when I try to restore your backup x.x
Click to expand...
Click to collapse
Redownload the file. I restored from the nandroid backup posted without MD5 chechsum error. Sometimes files get corrupt while downloading.

Blanco954 said:
Redownload the file. I restored from the nandroid backup posted without MD5 chechsum error. Sometimes files get corrupt while downloading.
Click to expand...
Click to collapse
Nope, happening again x.x

yahoowizard said:
Nope, happening again x.x
Click to expand...
Click to collapse
I've seen this happen before on different Android phones I owned that had CWR installed. I could not restore my backup due to MD5 checksum mismatch. It might be attributed to the version of CWR you have and the version used to create it.
What exactly is happening in your case? I didn't necessarily had to load this restore, the only problem with my upgrade was the "Indigo" error. I went thus route cause I was anxious and didn't research my problem. Need to practice some more self control before I hose my TPT. Maybe we can pitch in and help you figure something out.
Sent from my DROID RAZR using xda premium

E: failed to verify whole-file signature
E: signature verification failed
Then it aborts. It's not as specific as busybox or Indigo or any of the other errors people have been getting, so not sure what I'm supposed to be fixing.

yahoowizard said:
E: failed to verify whole-file signature
E: signature verification failed
Then it aborts. It's not as specific as busybox or Indigo or any of the other errors people have been getting, so not sure what I'm supposed to be fixing.
Click to expand...
Click to collapse
I assume your attempting to install the OTA that was downloaded to the tablet. I am not an expert but this error your getting is due to not having the stock recovery installed. There's a post on this forum where you can download the Lenovo ICS update files. Make sure you are stock with bloat. Download that pair of files and place them on the root of your SD card.. If you made a nandroid backup of stock OS when you rooted your tablet restore that backup. Temp unroot with OTA rootkeeper. Reboot to recovery and choose to install the update from SD card via CWR. Make sure its the large file first. You might get an assert check error "Indigo" if so you will need to restore the stock recovery using the file GodfatherIP linked in OP. Once you have restored stock recovery the update should install without a problem and you can enjoy ICS on TPT. It is way better than broken GB.
Sent from my DROID RAZR using xda premium

jhankinson said:
A lot of people seem to have the same broken files so I figured I would post a few here. These are all from a US 32GB TpT on OTA2.5 but should work for any US TpT:
Original generic.kl
Original wpa_supplicant
Original gps.conf
Original busybox
My US OTA2 clean nandroid backup (not completely clean, you will need to replace Generic.kl and wpa_supplicant with the files provided above) If you are totally screwed up you can restore this in CWR, replace the two files mentioned, and then proceed to update normally (OTA2.5 then ICS). For US Tablets only!!!
A bunch of system files (I think this was copied when I was still on OTA1 but maybe some files will still be useful if they weren't patched).
The update.zip I flashed to restore stock recovery before updating to ICS. Use at your own risk, it has only been tested once by me. This should not be necessary but may help if you are getting the indigo failure message as I got that message in CWR but not with stock recovery.
Don't change any system files in ICS until someone gets CWR working: if you break your system without CWR you're gonna have a bad time.
Click to expand...
Click to collapse
i have just restored your nandroid and also put hte two files you mentioned in place (Original generic.kl and Original wpa_supplicant). i am using a 64GB USA TPT too. i plan to make an updated nandroid before i try ota 2 and then ics and if all goes well, i'll post the updated nandroid in this thread.
update1:
after doing the above, i then:
-restored the stock recovery after your nandroid, rebooted twice still on cwr recovery
-did not seem to work at first however i then reran an custom update.zip for 0089US_CWR
-did a check for updates and noticed it went to the stock recovery update
-now am updating to ics!! hopefully that will go through smoothly.
update2:
-getting busybox assert error, putting busybox file in play next. used voodoo rootkeeper to make backup to keep root on ics too. temp unrooted, trying update again. :fingers-crossed:
update3:
ICS!!!!!!!!!!!!!!!!!! i'll post nandroid later today and can confirm these files combined w/a cwr update to 0089 got me out of my failed update funk. thanks again all!
My Contribution/Files:
note: i have a 64GB USA TPT (1839-27U). was running CWR and was rooted.
-USA, OTA2 Nandroid w/Original generic.kl and Original wpa_supplicant in place. You will still need to add back the busybox file after you update to 0089
nandroid zip
-0089 CWR update zip (not made by me, found somewhere on xda)
cwr update zip

seamonkey420 said:
i have just restored your nandroid and also put hte two files you mentioned in place (Original generic.kl and Original wpa_supplicant). i am using a 64GB USA TPT too. i plan to make an updated nandroid before i try ota 2 and then ics and if all goes well, i'll post the updated nandroid in this thread.
update1:
after doing the above, i then:
-restored the stock recovery after your nandroid, rebooted twice still on cwr recovery
-did not seem to work at first however i then reran an custom update.zip for 0089US_CWR
-did a check for updates and noticed it went to the stock recovery update
-now am updating to ics!! hopefully that will go through smoothly.
update2:
-getting busybox assert error, putting busybox file in play next. used voodoo rootkeeper to make backup to keep root on ics too. temp unrooted, trying update again. :fingers-crossed:
update3:
ICS!!!!!!!!!!!!!!!!!! i'll post nandroid later today and can confirm these files combined w/a cwr update to 0089 got me out of my failed update funk. thanks again all!
My Contribution/Files:
note: i have a 64GB USA TPT (1839-27U). was running CWR and was rooted.
-USA, OTA2 Nandroid w/Original generic.kl and Original wpa_supplicant in place. You will still need to add back the busybox file after you update to 0089
nandroid zip
-0089 CWR update zip (not made by me, found somewhere on xda)
cwr update zip
Click to expand...
Click to collapse
Excellent post. Thanks for your contribution, these files will come in handy for other members that are in a pinch.
Sent from my DROID RAZR using xda premium

seamonkey420 said:
update3:
ICS!!!!!!!!!!!!!!!!!! i'll post nandroid later today and can confirm these files combined w/a cwr update to 0089 got me out of my failed update funk. thanks again all!
My Contribution/Files:
note: i have a 64GB USA TPT (1839-27U). was running CWR and was rooted.
-USA, OTA2 Nandroid w/Original generic.kl and Original wpa_supplicant in place. You will still need to add back the busybox file after you update to 0089
nandroid zip
-0089 CWR update zip (not made by me, found somewhere on xda)
cwr update zip
Click to expand...
Click to collapse
Is there a version for 16gb US models, because I am getting MD5 mismatch.

bigsnack said:
Is there a version for 16gb US models, because I am getting MD5 mismatch.
Click to expand...
Click to collapse
i wonder if you can re-generate the MD5 checksum for the nandroid?
i'll find that post and link to it below:
http://forum.xda-developers.com/showthread.php?t=976453&page=2
For anyone who has had the Clockwork-mod Recovery MD5 mismatch! error.
Update: thanks Exca
If you have androids SDK ( ADB installed) try this easer method by Exca
This is a much easier way:
adb shell
# cd /sdcard/clockworkmod/backup/2010-06-29.20.22.53
# rm nandroid.md5
# md5sum *img > nandroid.md5
usually does the trick

This thread may save me. I'll try it and post back.

[Solved] OTA update fails on Yoga Tab 2 1050F

Hi,
i have the Yoga Tab2 1050F. The last OTA update fails to install.
I am currently on S100067_1507101258 and the update is for S100196_1511230539.
All earlier OTA's installed fine. I had my Tab rooted, but i unrooted it before installing the OTA update.
I also did a factory reset, the update still fails.
I only get an "Error" on the display with the tilted android avatar.
I saved the last OTA file, which is around 50MB large.
I also tried an update via the internal sd and the external sd card. None of these helped.
Can anyone help find the cause and help me install the latest update?
Regards
Jay

jayp57 said:
Hi,
i have the Yoga Tab2 1050F. The last OTA update fails to install.
I am currently on S100067_1507101258 and the update is for S100196_1511230539.
All earlier OTA's installed fine. I had my Tab rooted, but i unrooted it before installing the OTA update.
I also did a factory reset, the update still fails.
I only get an "Error" on the display with the tilted android avatar.
I saved the last OTA file, which is around 50MB large.
I also tried an update via the internal sd and the external sd card. None of these helped.
Can anyone help find the cause and help me install the latest update?
Regards
Jay
Click to expand...
Click to collapse
the thing is that not always the 'unroot' works for doing a system update, the unroot (have you performed the full one?) could leave behind modified binaries or maybe apps you installed have did that (for eg if you installed busybox it will leave the new binary) and the first step of the OTA update is to do a check of all the files that are going to be updated (patched) and if one of them doesn't match the sha1 checksum the update will abort (will not change anything on your tab when aborting). you can fix it by:
1. (complicated) restore the orginal files (you can check the recovery log on your cache partition to see where it failed)
2. (recommended) flash a stock rom matching your existing Android (you are on lollipop so you can use this for a stock lollipop install)
ps. factory reset doesn't save, that one just erases 'data' partition, has nothing to do with the ota (that usually updates files on the 'system' one or the 'boot/recovery/fastboot' partitions)

Thanks ionioni for your answer.
I don't want to flash a stock rom, that is not OTA. Just for security reasons. This would be my last resort.
I prefer to "repair" it. I am familiar with your tmp-root tool.
Do i have to mount something when i am in tmp-root, to search the su root files?
I think they reside in /system/lib and /system/bin.
Regards
Jay

jayp57 said:
Thanks ionioni for your answer.
I don't want to flash a stock rom, that is not OTA. Just for security reasons. This would be my last resort.
I prefer to "repair" it. I am familiar with your tmp-root tool.
Do i have to mount something when i am in tmp-root, to search the su root files?
I think they reside in /system/lib and /system/bin.
Regards
Jay
Click to expand...
Click to collapse
if you start with tmp_root it will open an early adb shell as root (regardless of whether your tab was or not rooted)
check after you shell in to see if the /cache is mounted (input a simple mount) and if it is not you need to mount it
afterwards you will need to go and do an adb pull on your recovery log (if i recall is on /cach/recovery ) and check inside to find on what did the ota failed
however this is cumbersome and even if you find on what it fails you still will have to find the original files (and after you try to OTA again it can fail many more times on other files as the OTA is aborted on the first non matching file and if there are many you will need to repeat these steps over again). i never did this, i am just saying that it could be done, but why would one waset maybe hours just so he can bring his system back to the same state it could bring in 3 minutes by flashing a stock rom? but if you want the complicated way feel free
if i were you i would just flash the stock rom in 3 minutes (that is how long it takes) and move along
what security reasons you are talking about?

I am just carefull. The images might be tampered.
But i get your point. It might get cumbersome to fix each file.
I'll try your method and flash the lollipop image.

jayp57 said:
I am just carefull. The images might be tampered.
But i get your point. It might get cumbersome to fix each file.
I'll try your method and flash the lollipop image.
Click to expand...
Click to collapse
oh, i see... i doubt they are tampered by anyone (except Lenovo of course ) the files i provide have already been used by others (and if they were to be tampered they would have failed future OTA's, the boot image is checked and it won't load if modified etc)
as a personal thought, to tamper a stock rom (to whatever purpose one would want) so that they cannot be detected by a future ota requires a level of knowledge that i think keeps us safe (i think one who is able to do such a thing would not 'waste' his time and resources on doing it to a normal/casual user like we are), so if you are able to take ota's you can safely assume that the files are the ones Lenovo put in there (not to say that Lenovo could not do funny things tho)
i wish you to become so important that one day this could be a real concern

yeah you are right.
thanks for your support. i managed to update my tablet.

Hi. I have the same problem. Did you have flash lollipop firmware again ? the ota works ?
Do you know where to get lollipop firmware for 1050F ? in all-in-one subject there is only kitkat firmware for 1050F.
Thank you.

saupiquet said:
Hi. I have the same problem. Did you have flash lollipop firmware again ? the ota works ?
Do you know where to get lollipop firmware for 1050F ? in all-in-one subject there is only kitkat firmware for 1050F.
Thank you.
Click to expand...
Click to collapse
the link is in my first reply here

How do I update to Android 7.0 on the Axon 7 (USA Model) with TWRP Recovery installed

I'm unable to unpate as of right now because I have TWRP recovery installed.
When I try to, it tells me " Package expects fingerprint of *original device fingerprint* this device has TWRP\Team_Win_Recovery_Proejct/ailsa_ii
Updater process ended with ERROR: 8
Error installing zip file '@/cache/recovery/block.map'"
I tried removing the part of the script that checks this, but then I got a different error (I don't remember what it was, it said something about "Boot:1826459185:1U57126581(Random numbers not the actual ones) contains unexpected content" or something like that
So I was wondering, how would I go and update to the new Android 7.0 update? (I also have the zip file of the update locally)
I would assume that I could flash stock recovery but a. I don't have the stock recovery.img, and b. I was reading around and someone mentioned that if I flashed stock recovery it'd delete all my data.
I'd be highly disappointed if the only way I could update to the 7.0 update is by deleting all my data. I'm sure there must be some way around it.
Can anyone help me out? I'm sure I'm not the only one that'll have this issue

EDIT: Flashed Recovery.img (Only recovery.img, via fastboot)
Results: Recovery is flashed and working.
Phone does boot up perfectly fine, no issues
Data is NOT lost.
Flashing the 7.0 update(A2017UV110B15) (Via stock recovery) [Remember to put it on your SDCard]:
Verifying update package...
Verified.
"EMC /dev/block/bootdevice/by-name/boot****load of numbers)" has unexpected contents
Aborted
Click to expand...
Click to collapse
( Same error as when I removed device verification.. maybe this is a user error and not a system/update error )
( Maybe I failed to download the update zip properly? I'll try the OTA update instead )
Downloading..
Rebooting..
Installing System Update...
Has unexpected contents
Package mixmatched
Aborted
Click to expand...
Click to collapse
( No, not a user error I suppose.. I don't know what is wrong then! This is odd )
System update failed
Reason: The system update package did not match the phone
Click to expand...
Click to collapse
And for the record, I am on A2017UV1.0.0B29

Andrew S.S. said:
I'm unable to unpate as of right now because I have TWRP recovery installed.
When I try to, it tells me " Package expects fingerprint of *original device fingerprint* this device has TWRP\Team_Win_Recovery_Proejct/ailsa_ii
Updater process ended with ERROR: 8
Error installing zip file '@/cache/recovery/block.map'"
I tried removing the part of the script that checks this, but then I got a different error (I don't remember what it was, it said something about "Boot:1826459185:1U57126581(Random numbers not the actual ones) contains unexpected content" or something like that
So I was wondering, how would I go and update to the new Android 7.0 update? (I also have the zip file of the update locally)
I would assume that I could flash stock recovery but a. I don't have the stock recovery.img, and b. I was reading around and someone mentioned that if I flashed stock recovery it'd delete all my data.
I'd be highly disappointed if the only way I could update to the 7.0 update is by deleting all my data. I'm sure there must be some way around it.
Can anyone help me out? I'm sure I'm not the only one that'll have this issue
Click to expand...
Click to collapse
Flashing stock recovery will not delete your data. Find your stock firmware download on the forum or zte, pull recovery.img from it and flash in twrp.
Of course those who whine about wiping data usually are the ones who need to do it most.
FYI I updated, flashed twrp and then restored data from my b29 backup without issue. At least this way you can make a new backup before attempting.
You can also wait for the flashable .zips to show up and avoid all the hassle.

lafester said:
Flashing stock recovery will not delete your data. Find your stock firmware download on the forum or zte, pull recovery.img from it and flash in twrp.
Of course those who whine about wiping data usually are the ones who need to do it most.
FYI I updated, flashed twrp and then restored data from my b29 backup without issue. At least this way you can make a new backup before attempting.
You can also wait for the flashable .zips to show up and avoid all the hassle.
Click to expand...
Click to collapse
Read my updated comment; Sorry that I didn't just edit the thread. And that makes sense. I think it would be wise for me to just wait.

First of all, flash rollback zip from DrakenFX.
Then update via OTA. That's all. I've done these steps yesterday and I'm using Nougat now.

WesTD said:
First of all, flash rollback zip from DrakenFX.
Then update via OTA. That's all. I've done these steps yesterday and I'm using Nougat now.
Click to expand...
Click to collapse
I saw your post then had forgotten about it til now ( haven't checked ) but in the last month I've forgotten where the rollback zip is located / what thread. Any help would be appreciated.

Only use ota if you don't want twrp/root anymore.

Andrew S.S. said:
I saw your post then had forgotten about it til now ( haven't checked ) but in the last month I've forgotten where the rollback zip is located / what thread. Any help would be appreciated.
Click to expand...
Click to collapse
Here you go; https://forum.xda-developers.com/showpost.php?p=68873482&postcount=2

OTA update ZIP packages for Lenovo Z6 Pro

So the version of the firmware I have is 11.0.054 which is a fairly old global firmware. It's really bad and I really want to update but since I don't own a PC my only option is to go through the process of manual installation of these ZIP packages...
The problem is though, I can't find the update files anywhere. I need 211 and so on until I get to 350.
Any idea where to get them?

Sorry the only file i can found for update.zip Ota start from 11.0.284.
You can look on 4pda
HTML:
http://4pda.ru/forum/index.php?showtopic=959099&st=820
Edit: i found your post on 4pda so my help is useless......... No ota by now ?

kzchy said:
So the version of the firmware I have is 11.0.054 which is a fairly old global firmware. It's really bad and I really want to update but since I don't own a PC my only option is to go through the process of manual installation of these ZIP packages...
The problem is though, I can't find the update files anywhere. I need 211 and so on until I get to 350.
Any idea where to get them?
Click to expand...
Click to collapse
I guess your bootloader is still locked. You have 2 options to upgrade to latest roms, both will involve wiping all data on your phone, so backup first:
- without unlocking BL, you can flash official ROM files with QPST. This will bring you to latest version and remain 100% stock; hence you will get future OTAs
- Unlock BL and flash any rom you want using fastboot or TWRP. This will give you the flexibility to swap rom versions, in most case you will be able to go from CN to ROW without wiping data. But you won't get OTAs. For all future upgrades you will need to flash with TWRP manually.
Before hand, you will have to choose whether you want CN (11.1.105) or ROW (11.0.350) rom.
You'll find walkthroughs here or using google.