Database Develop

[Q] HELP! :( Semi Bricked. Tried EVERYTHING

Ok
Please forgive me I have spent up to 7 hours today searching and trying but to no luck.
So I didnt realise what i was doing and Semi Bricked my Phone. I edited build.prop and saved it in MyExplorer(name?) to try and turn off the camera sounds and when I rebooted, it just gets stuck on the galaxy S 2 screen, boot loop.
I'm on SGSII (Australia) Stock Vodafone's ICS 4.0.3 Rooted.
I have CWM installed but tried a few things:
- I can get into Download MOde (no idea what to do here)
- I can get into CWM mode 5.0.2.7 Recovery mode but cant do anything still.
- I tried various Edify script builders to try and put the original build.prop back in but get multiple Status 0 errors whenever I try update.zip from the SD card.
- I tried rebuilding the backup on there and changing the build.prop file on there and trying to restore but MD5 check fails. Even tried rebuilding the MD5 file with the modified files and still no luck. MD5 files fails.
Would anyone have any suggestions and how to resolve this without a flash or wipe? I didnt back recent backup and will lose everything.
I am coming to a point where I really am wanting to back to Apple
There are 2 build.props attached. One is the bad one that stopped me from booting up and I found another one that was named .bak (extension taken off) I found in the same directory (/SYSTEM)
If anyone can help me build an update.zip to push in via CVM I would greatly be in your debt (I tried for 4 hours with no luck)

If you have recovery and download mode yet nothing is lost.
In first, do saved your apps ?
If you had saved them or if it doesn't matter to you, reflash a rom via recovery
LINK HERE:
http://download.cyanogenmod.com/get/jenkins/2773/cm-9-20120615-NIGHTLY-galaxys2.zip
Flash it GoogleApps folder
http://goo.im/gapps/gapps-ics-20120317-signed.zip
The rom that I attached to the reply is a CM9 ICS version, it's quitly stable and we can have some settings on it.
If it doesn't work reflash with Odin (it's with software who use the Download Mode)
http://hotfile.com/dl/149514867/aea2f22/I9100XXLPQ_I9100OXALPQ_XEO.zip.html
Instructions
-Unzip the Rom Folder ( I9100XXLPQ..........)
-Open the included Odin
-Put your phone on Download Mode
-Click PDA and select I9100_CODE_I9100XXKP*_CL*_REV02_user_low_ship.tar.md5
-Click PHONE and select MODEM_I9100XX*_REV_02_CL*.tar.md5
-Click CSC and GT-I9100-MULTI-CSC-OXA*.tar.md5
-Click Start and don't touch anything still the colored case become green
-And now your phone resurrects
Reply me of results

thanks for your reply
unfortunately i didnt save my apps and havent got backups of my data either
i cant reach the file via ADB either, when i run ADB (have KIES installed and worked before) - adb devices.
nothing shows up when the phone is stuck on "Samsung GS2" screen.
do you have any recommendations around keeping my data there?

If you find the exact same software your on now to download you could try flashing that in cwm without wipes I think that would work i think it replaces all system stuff so it will work, worth a try
Sent from my GT-I9000 using xda premium

understood thanks
what if i just want to flash build.prop via update.zip?
i tried so many methods but it always fails. is anyone able to create a update.zip for me?

i used a GUI script creator to try and update it via CWM recovery mode but it doesnt seem to like it.
If i turn off signature verification, it gives me a (status 0) error saying : E: Error in /sdcard/update.zip
and if i turn on verification toggle, it says E: signature verification failed
can anyone help?

calum96 said:
If you find the exact same software your on now to download you could try flashing that in cwm without wipes I think that would work i think it replaces all system stuff so it will work, worth a try
Sent from my GT-I9000 using xda premium
Click to expand...
Click to collapse
i know there are 2 types of ROMS right? the nonwipes and wipes. i really dont want the wipe versions.
the one i downloaded is 1G which i'd imagine is the wipe version if i were to upgrade via odin?
http://www.androidaddicted.com/firm...-vodafone-australia-firmware-update-1267.html

Can you mount any sd on your pc, because you can the recovery mount trick to access to your data.
When you are in the recovery menu, go to mount and storage and click on "mount usb storage" and the internal and external sd will appear on your pc.

you are posting in galaxy s thread....repost in galaxy s2 thread

I don't think so but then again I don't own a s2 but you can select advanced restore: restore data then flash a compatible ROM, then restore the data if you worried but as I said before flashing the same ROM shouldn't remove user data
Sent from my GT-I9000 using xda premium

[Q] JB OTA fails due to timezone fixer

Hi all,
I finally got offered the JB OTA update but it fails to apply because I used TimeZone Fixer to update my timezone files. From the recovery log (/cache/recovery/last_log):
Code:
Verifying current system...
file "/system/usr/share/zoneinfo/zoneinfo.dat" doesn't have any of expected sha1 sums; checking cache
failed to stat "/cache/saved.file": No such file or directory
failed to load cache file
script aborted: assert failed: apply_patch_check("/system/usr/share/zoneinfo/zoneinfo.dat", "6d285c458b0a42ae5310f8695ef84931a92cf8db", "413b1e0fdd323e9fdba5111132122bd311651a32")
assert failed: apply_patch_check("/system/usr/share/zoneinfo/zoneinfo.dat", "6d285c458b0a42ae5310f8695ef84931a92cf8db", "413b1e0fdd323e9fdba5111132122bd311651a32")
I thought I'd just restore these files from the 4.0.4 image I'm running now but while I have a large system.img.ext4 I can't figure out how to get anything out of it. It does not mount as an ext4 partition...
Does anyone know how I can extract the original timezone files for this phone?
Or can anyone send me the set of timezone files from this phone?
Or is there some other way to get the JB update installed (without resorting to a full phone wipe)?
I do have a backup of the phone's contents on an external SD card but I'd prefer not to wipe if possible.
Thanks in advance...

a1291762 said:
Or is there some other way to get the JB update installed (without resorting to a full phone wipe)?
Click to expand...
Click to collapse
Because I'm impatient and because I was bored, I looked at the fastboot image I had. It seems the "wipe" bit is optional so I flashed up the system part, leaving the rest intact. That left me with a cleaned out /system but didn't do anything to my apps (well... doesn't seem to have done anything to them - I haven't checked yet). Then I did the OTA process. Did you know you can put an OTA zip under /cache to avoid having to re-download it? The software says it's going to re-download but I guess it does an rsync or something so it completes quickly. Nice.
So... I'm now in the process of installing JB! It's been running longer than it did last time so here's hoping...

update: it's all going now.
Sent from my XT890 using xda app-developers app

Please help unbrick a Telus HTC One

Hi everyone.
I unlocked the bootloader and rooted a Telus HTC One. But the latest flash went wrong and I went into bootloop. Somehow, I seem to have gotten myself into a situation where there's no ROM installed. I can still get into Bootloader and Recovery. When I try to start the phone, it's stuck at "HTC Quietly Brilliant" screen.
I've tried factory resetting, wiping everything, relocking the bootloader and loading the Factory RUU Zip using the All-In-One tool kit by Hasoon, and sideloading a ROM. Nothing seems to work. I also managed to push a ROM to the phone using the adb push command. When I try to install it using TWRP, I get an error msg "Unable to open zip file." It failed using CWM recovery as well.
When I plug the phone into a computer, it recognizes something is plugged in. But I can't open the drive at all. I get error msgs when I try to mount sdcard, system, data, anything. Things don't seem to be mounting/recognized at all. HTC sync and drivers are installed.
Experts, what else can I try?

Try downloading a Telus clean nandroid backup. Then go back into recovery (depends of what nandroid you get, make sure you have the right recovery, so if you download a CWM nandroid use CWM).

G-Bus said:
Try downloading a Telus clean nandroid backup. Then go back into recovery (depends of what nandroid you get, make sure you have the right recovery, so if you download a CWM nandroid use CWM).
Click to expand...
Click to collapse
Thanks for the suggestion. Not having any luck finding a Telus nandroid. Would it make matters worse if I try to restore from a non-Telus nandroid? My phone can't mount the /sdcard right now. Suppose I'll have to adb push it to the phone again?

runlsd said:
Thanks for the suggestion. Not having any luck finding a Telus nandroid. Would it make matters worse if I try to restore from a non-Telus nandroid? My phone can't mount the /sdcard right now. Suppose I'll have to adb push it to the phone again?
Click to expand...
Click to collapse
You don't mount the sdcard in HTC One you mount the data partition.
Also what happens if you sideload a ROM?
PHP:
adb sideload <ROM>
Have you tried erasing cache after installing a ROM if successful?

Riyal said:
You don't mount the sdcard in HTC One you mount the data partition.
Also what happens if you sideload a ROM?
PHP:
adb sideload <ROM>
Have you tried erasing cache after installing a ROM if successful?
Click to expand...
Click to collapse
When I sideloaded, It said
Can't Open /sdcard/rom.zip" (bad).
Installation aborted
Sideloading now gives me this error
failed to open driver control: No such file or directory
Restarting adbd
hmm, okay. I thought since recovery says "Install zip from sdcard" i thought /sdcard needed to be mounted. /data is mounted at the moment. No connectivity between computer and the phone unless through the All-in-one kit.

Riyal said:
Have you tried erasing cache after installing a ROM if successful?
Click to expand...
Click to collapse
And I haven't had successfully installed a ROM since I bricked the phone.

Install a custom ROM and kernel on your USB from the computer, mount the USB in Twrp using the otg cable. Flash ROM, if it doesnt boot, flash the kernel.
Flashing the kernel fixed it for me.
Another way is to use an adb pusher app and transfer thevfiles to your SD card.
Sent from my Nexus 10 using XDA Premium HD app

Thanks everyone. Somehow it sideloaded when I tried for the twentieth time.

[SOLVED] [Q] Nook HD Only boots to CWM

PROBLEM SOLVED thanks to digixmax for the bootloader zip
http://forum.xda-developers.com/showpost.php?p=57096448&postcount=11
Cyanogenmod 11.
Tablet was acting weird. Wasn't turning on in general, just black. Then I tried to reset it using the n and power buttons for 30 seconds. It did boot up eventually.
Then it froze and rebooted, and ever since only boots to CWM.
I've tried factory reset and reflashing to no avail, only cwm will boot.
I read it might have something to do with bootdata.
Like I said, I got it to work initially after it would only boot to a black screen, then it froze, now this. I'm worried I might have corrupted the EMMC way way back with an older rom.

It's likely that your problem is one that is described at http://forum.xda-developers.com/showpost.php?p=21381141&postcount=1 (the post was written for the Nook Tablet, but the BCB & BootCnt exist and work same way for the HD/HD+), in which case you can try to reset/restore BCB & BootCnt by flashing flashable_fix_bootdata-hummingbird.zip available at http://www.mediafire.com/download/04qhwylk36sofbl/flashable_fix_bootdata-hummingbird.zip.
If resetting BCB & BootCnt does not help then I'd suggest you try re-installing CM11.

thx for the advice
albeit, I received an error when flashing the file using cwm.
Code:
EMMC CWM-based recovery v6.0.4.6
-- Installing: /external_sd/flashable_fix_bootdata-hummingbird.zip
Finding update package...
Opening update package...
Installing update...
E:Error in /exteranl_sd_flashable_fix_bootdata-hummingbird.zip
(Status 4)
Installation Aborted.

Status 4 is a problem with the script in the zip. Double triple checked search and I've seen it before myself.
http://forum.xda-developers.com/showthread.php?t=2355223
Just a thought that since you can get into cwm, you could try using adb and browsing the emmc to see if its there and intact. twrp (just put it on an sdcard) has a file manager built-in as well. Is that worth doing? If need be you could save files that way too if its still intact.

Thistleknot said:
thx for the advice
albeit, I received an error when flashing the file using cwm.
Code:
EMMC CWM-based recovery v6.0.4.6
-- Installing: /external_sd/flashable_fix_bootdata-hummingbird.zip
Finding update package...
Opening update package...
Installing update...
E:Error in /exteranl_sd_flashable_fix_bootdata-hummingbird.zip
(Status 4)
Installation Aborted.
Click to expand...
Click to collapse
I fixed the error in the file-name of "updater-script" in the flashable zip file.
You can re-download flashable_fix_bootdata-hummingbird.zip and give it another try.

redownloaded the same zip as instructed: flashable_fix_bootdata-hummingbird.zip; in the 1st mediafire link http://www.mediafire.com/download/04...ummingbird.zip you have posted. (which has an uploaded date of 9-21-2014) Same issue.
btw. I have flashed cm11 over this, that will flash (but not fix my nook, still boots only to cwm). However, this update file will not take.
How should this file structure look like unzipped? I keep reading about an update script file. the only file I see named update is buried way deep in some android subfolder
update-binary
updater-script-bootdata

Okay, I figured out what I was supposed to fix to get past error 4
Name: META-INF/com/google/android/updater-script
SHA1-Digest: 29co0QiSKyDerOQ5Ggv0EV16f9g=
so i changed updater-script-bootdata to updater-script in the META-INF/com/google/android/ folder
then...
I got a different error
Code:
assert failed: getprop("ro.product.device") == "hummingbird" || getprop("ro.build.product") == "ovatino"
E:Error in /external_sd_/flashable_fix_bootdata-hummingbird-diff.zip
(Status 7)
Some flag check fails. This is a nook hd with cm11 emmc installed

Thistleknot said:
Okay, I figured out what I was supposed to fix to get past error 4
Name: META-INF/com/google/android/updater-script
SHA1-Digest: 29co0QiSKyDerOQ5Ggv0EV16f9g=
so i changed updater-script-bootdata to updater-script in the META-INF/com/google/android/ folder
then...
I got a different error
Code:
assert failed: getprop("ro.product.device") == "hummingbird" || getprop("ro.build.product") == "ovatino"
E:Error in /external_sd_/flashable_fix_bootdata-hummingbird-diff.zip
(Status 7)
Some flag check fails. This is a nook hd with cm11 emmc installed
Click to expand...
Click to collapse
You need to use a CWM older than v6045. The ones made for CM11 will not work.
Sent from my BN NookHD+ using XDA Premium HD app

The script could be fixed to eliminate status 7 error on cm11 recovery, but without any changes its like leapinlar says.

leapinlar said:
You need to use a CWM older than v6045. The ones made for CM11 will not work.
Sent from my BN NookHD+ using XDA Premium HD app
Click to expand...
Click to collapse
I wonder how much further down this rabbit hole I got to go...
where can I get get an older version from?

Thistleknot said:
redownloaded the same zip as instructed: flashable_fix_bootdata-hummingbird.zip; in the 1st mediafire link http://www.mediafire.com/download/04...ummingbird.zip you have posted. (which has an uploaded date of 9-21-2014) Same issue.
btw. I have flashed cm11 over this, that will flash (but not fix my nook, still boots only to cwm). However, this update file will not take.
How should this file structure look like unzipped? I keep reading about an update script file. the only file I see named update is buried way deep in some android subfolder
update-binary
updater-script-bootdata
Click to expand...
Click to collapse
Use this link for the corrected zip file: http://www.mediafire.com/download/30leabd7tjeytn4/flashable_fix_bootdata-hummingbird.zip.
Updater-script in folder META-INF\com\google\android\ is indeed the script used to flash BCB and BootCnt into /bootdata.
---------- Post added at 05:10 PM ---------- Previous post was at 04:45 PM ----------
Thistleknot said:
I wonder how much further down this rabbit hole I got to go...
where can I get get an older version from?
Click to expand...
Click to collapse
You can get the old version of verygreen's CWM from his CM10.1 thread or from https://www.mediafire.com/#6a4rivb8kkdfu -- the EMMC version is (recovery.img) in his flashable cwm-recovery-ovation-3.zip, the SD version is (ramdisk.cwm) inside his emmc-cwm-early2.1.img or inside verygreen_emmc-cwm-early2.1-boot.zip at https://www.mediafire.com/#6a4rivb8kkdfu (verygreen_emmc-cwm-early2.1-boot.zip has the same complete set of CM10.x compatible SD-based boot/CWM files as emmc-cwm-early2.1.img but packed in a .zip file).

Thistleknot said:
I wonder how much further down this rabbit hole I got to go...
where can I get get an older version from?
Click to expand...
Click to collapse
From my HD/HD+ CWM thread linked on my signature.
Sent from my BN NookHD+ using XDA Premium HD app

looks like
Use this link for the corrected zip file: http://www.mediafire.com/download/30...ummingbird.zip.
Click to expand...
Click to collapse
is working. I got past cwm at least.
derp, sorry I missed your [leapinlair] signature links. I swear I looked and didnt' see them.
WORKING GUYS. You guys are really too good to the community.

Tmobile update is live!

Hit that software update.

Wow thanks for the late news

my phone is upgrading now

Don't know if anybody else had trouble connecting their m9 with their Roku 3 before the update but the miracast feature now works with my Roku 3

Anyone have any suggestions on how to force the update? Still have not gotten the notification to download the update and I get the standard "There are no updates available for your phone" message when I got into settings and check for the update manually.

nickmgray said:
Anyone have any suggestions on how to force the update? Still have not gotten the notification to download the update and I get the standard "There are no updates available for your phone" message when I got into settings and check for the update manually.
Click to expand...
Click to collapse
If you are 100% stock update using the ota from stock recovery.
Download and read here

So I ran into a small issue. I was rooted with TWRP, and i re-flashed the system image that i created when I first installed TWRP. This took, as I was prompted to reinstall SuperSu. I did not reinstall, then flashed the stock recovery back to the phone.
All good so far.
Then I went to install the OTA, and received the error message
E:unknown command [set_err_msg]
/dev/block/bootdevice/by-name/system has been remounted R/W
reflash device to reenable OTA updates
Did my reinstall of the system image not take? As far as i could tell, everything worked properly until installing the OTA.
Thanks in advance for any help.

AaronM7 said:
So I ran into a small issue. I was rooted with TWRP, and i re-flashed the system image that i created when I first installed TWRP. This took, as I was prompted to reinstall SuperSu. I did not reinstall, then flashed the stock recovery back to the phone.
All good so far.
Then I went to install the OTA, and received the error message
E:unknown command [set_err_msg]
/dev/block/bootdevice/by-name/system has been remounted R/W
reflash device to reenable OTA updates
Did my reinstall of the system image not take? As far as i could tell, everything worked properly until installing the OTA.
Thanks in advance for any help.
Click to expand...
Click to collapse
I had this same issue and finally figured it out yesterday. The reason is because in older versions of twrp, the minute the recovery is booted it mounts system as read/write. So any backup done after that was potentially flawed.
First you need to download a system and boot image from http://forum.xda-developers.com/tmobile-one-m9/general/please-read-rooting-using-twrp-t3069022. Note that the backup was created with a beta version of twrp so you have to modify the name of system file from system.emmc.win to system_image.emmc.win. Once this is done put it in your twrp folder.
The way i rectified the issue was to first flash the latest twrp recovery v2.8.7.0. The developer added a mount system as read only option in the mount section of twrp. Once you click on the checkbox. Go to restore the system backup, This time it will show up as a system image backup. Once restored, flash stock recovery and boot into os download the system update and it should go through without any hiccups.
Let me know if you have any questions

darll said:
I had this same issue and finally figured it out yesterday. The reason is because in older versions of twrp, the minute the recovery is booted it mounts system as read/write. So any backup done after that was potentially flawed.
First you need to download a system and boot image from http://forum.xda-developers.com/tmobile-one-m9/general/please-read-rooting-using-twrp-t3069022. Note that the backup was created with a beta version of twrp so you have to modify the name of system file from system.emmc.win to system_image.emmc.win. Once this is done put it in your twrp folder.
The way i rectified the issue was to first flash the latest twrp recovery v2.8.7.0. The developer added a mount system as read only option in the mount section of twrp. Once you click on the checkbox. Go to restore the system backup, This time it will show up as a system image backup. Once restored, flash stock recovery and boot into os download the system update and it should go through without any hiccups.
Let me know if you have any questions
Click to expand...
Click to collapse
Thanks. I kind of figured it out by following the thread about how to take the phone back to stock for OTAs, and used fastboot to flash the system.emmc.win file (wihtout modifying it.) After that, the phone wouldn't boot properly (probably because I didn't edit the filename,) so I flashed my system backup file. That made it so I could boot. I then flashed the stock recovery and it installed just fine.
Only really outlining what I did in case anyone else has the same issues- they can do what I did to get it up and running again.

kc6wke said:
If you are 100% stock update using the ota from stock recovery.
Download and read here
Click to expand...
Click to collapse
Thanks for sharing. I've tried this method on two different stock T-Mobile M9 phones, but both return an "E: Failed to map file" error message when selecting apply from phone storage.
Any suggestions?

nickmgray said:
Thanks for sharing. I've tried this method on two different stock T-Mobile M9 phones, but both return an "E: Failed to map file" error message when selecting apply from phone storage.
Any suggestions?
Click to expand...
Click to collapse
Are you placing the ota zip on internal or external sd?
It needs to be on the internal.

kc6wke said:
Are you placing the ota zip on internal or external sd?
It needs to be on the internal.
Click to expand...
Click to collapse
It's loaded to internal storage.