[Q] Help! Fried EMMC or not? 4Ext continue reentering. - HTC Desire S

Hi,
My Desire S has been RUU to 2.3.5/SENSE 3.0. HBOOT is 2.00.0002. then I unlocked it by htcdev, flashed the 4EXT recovery 2.2.7 RC5 and rooted.
Everything is normal before I try to flash a custom ROM.
I copied a custom ROM to sdcard. and go to 4Ext to install zip from sdcard.
It was stranged. the boot(kernel) didn't change. So I used fastboot flash boot boot.img. Then kernel was changed. Everything was normal until here. this ROM was used extract_dir to copy files to /system & /system/lib.
I changed the ROM. let the ROM contain two img: lib.img & system.img. My target was extract lib.img to /system/lib, and system.img to /system. I got this two img from RUU and remove some packages. But this time I failed. so I combined lib.img to system.img.(cp lib to /system/lib under linux). I wanted to extract the system.img(both /system & /system/lib) to /system because I thought 4EXT didn't support lib partitions is the reason I failed. my updater-script like that:
---------------------------------------------------
ui_print("updating system... ");
show_progress(0.1, 180);
ui_print("formatting system... ");
format("ext4","EMMC","/dev/block/mmcblk0p25");
show_progress(0.8, 180);
ui_print("copying system... ");
package_extract_file("system.img", "/dev/block/mmcblk0p25");
--------------------------------------------------------------------------
then something wrong. After reboot, it ran into recovery automatically and show the main menu. below the menu, some wrong message followed, as bellow:
--------------------------------------------------------------------------
E:Can't mount /cache/recovery/log
E:Can't open /cache/recovery/log
E:Can't mount /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
--------------------------------------------------------------------
after the wrong message, it is the partition info. the partitions seems ok.
The real problem is the phone keep in recovery, switch between two screen, one is menu + fault + partition info, the next second it switch to black screen, then menu+fault + info.
I can't select menu item or do anything. I try vol down + power, vol up + down + power to restart phone.
vol down + power : not work.
vol up + down + power: phone reboot, htc logo will show twice. but I can't enter bootloader(down + power). then it will go to recovery after serveral seconds.
According to this guide. http://forum.xda-developers.com/showthread.php?t=1146601, I don't thing pull out the battery will be a good idea.
Can anybody help me out. Thank you.

To get /system/lib on a different partition in not only to copy the files there. The kernel should support this also (to mount it on mmcblk0p28). For this you have to extract the ramdisk from the boot.img and modify init.saga.rc. Then you need to remove the library files from the ROM and modify the update script to flash them on /system/lib together with the kernel.
But basically you do not need this! The difference is that you will have 150 MB free space in /system, but this space is fixed anyway (no current ROM is more than 550 MB at this moment). When in future ROMs become bigger then the devs will add the separate lib partition scheme to their kernels and it will be supported.
So now better reflash the recovery from fastboot (you can go in bootloader with "adb reboot bootloader" while in recovery), install a normal ROM of your choise and then flash its boot.img

amidabuddha said:
To get /system/lib on a different partition in not only to copy the files there. The kernel should support this also (to mount it on mmcblk0p28). For this you have to extract the ramdisk from the boot.img and modify init.saga.rc. Then you need to remove the library files from the ROM and modify the update script to flash them on /system/lib together with the kernel.
But basically you do not need this! The difference is that you will have 150 MB free space in /system, but this space is fixed anyway (no current ROM is more than 550 MB at this moment). When in future ROMs become bigger then the devs will add the separate lib partition scheme to their kernels and it will be supported.
So now better reflash the recovery from fastboot (you can go in bootloader with "adb reboot bootloader" while in recovery), install a normal ROM of your choise and then flash its boot.img
Click to expand...
Click to collapse
Thank you very much.
I let the battery drained. then inserted another 100% battery, rebooted with vol down+power, I ran into fastboot mode successfully.
I tried several methods to recover system.
1) copied ROM.zip from RUU to sdcard, renamed it as PG88IMG.zip. bootloader found and loaded the zip but did nothing. Maybe because there is no signature in the zip.
2) in fastboot mode, tried "fastboot update PG88IMG.zip". failed.
3) in fastboot mode, connected USB and tried to RUU. failed with code 155. the progress bar never showed up.
Finally, I recalled someone said the system must be relocked before RUU. (my phone has been unlocked). SO...
In fastboot mode, run the command "fastboot oem lock", the HBOOT show "RELOCKED". then tried to RUU again and everything went smoothly, and I get the lovely "quietly brilliant" again!
Thank for all of the experience.

Related

[Q] Update from 3.1 & Tiamat 1.4.4 failed

Help for a newbie.
I followed this procedure:
1 - Copied file to sd card and renamed to update.zip (in a windows computer)
2 - turned xoom on and wento to rom manager
3 - wiped user and dalvik cache
4 - Tried to load file from zip, but it was not possible to find the update .zip file.
I get the following message:
E: Can't open /sdcard/update.zip
(bad)
Tried also without renaming and got:
E: Can't open /sdcard/update_US-Xoom-Wifi-3.2_HTJ85B-from HMJ37_stachre-solarnz-boot-img_v05.zip
After many trials rebooted.
System info showed the same 3.1 and Tiamamat 1.4.4
Opened rom manager again.
seleced install rom from sdcard
System backed up info and rebooted.
Had to reload all apps from store.
System info shows I am running 3.1 and Tiamat 1.4.4.
Also I keep receiving a message that there is a system update available.
I can't understand what I did wrong.
I g
Can anyone help?
Thank you
rogerodd said:
Help for a newbie.
I followed this procedure:
1 - Copied file to sd card and renamed to update.zip (in a windows computer)
2 - turned xoom on and wento to rom manager
3 - wiped user and dalvik cache
4 - Tried to load file from zip, but it was not possible to find the update .zip file.
I get the following message:
E: Can't open /sdcard/update.zip
(bad)
Tried also without renaming and got:
E: Can't open /sdcard/update_US-Xoom-Wifi-3.2_HTJ85B-from HMJ37_stachre-solarnz-boot-img_v05.zip
After many trials rebooted.
System info showed the same 3.1 and Tiamamat 1.4.4
Opened rom manager again.
seleced install rom from sdcard
System backed up info and rebooted.
Had to reload all apps from store.
System info shows I am running 3.1 and Tiamat 1.4.4.
Also I keep receiving a message that there is a system update available.
I can't understand what I did wrong.
I g
Can anyone help?
Thank you
Click to expand...
Click to collapse
You may have the wrong version of CWM recovery installed. You need Tiamat v3.2.0.0 R4c. If you are trying to flash thru Rom manager it may have had you update to v4.0.0.4 which is not compatible with the external sdcard. If this is the case, re-install the correct recovery version, and then redo your backup so that it is on the external sdcard where it can be safe if you need to wipe/factory reset. You can use Rom manger just to reboot into recovery, or df Quick Boot from the market and use that instead.
Good luck!
okantomi said:
You may have the wrong version of CWM recovery installed. You need Tiamat v3.2.0.0 R4c. If you are trying to flash thru Rom manager it may have had you update to v4.0.0.4 which is not compatible with the external sdcard. If this is the case, re-install the correct recovery version, and then redo your backup so that it is on the external sdcard where it can be safe if you need to wipe/factory reset. You can use Rom manger just to reboot into recovery, or df Quick Boot from the market and use that instead.
Good luck!
Click to expand...
Click to collapse
Rom manager says it is 4.0.0.4 but when in recovery is say CWM recovery-Tiamat-R4c-100611-1150-cwm or Tiamat v3.2.0.0 R4c ( I don't remember exectly) and the error is the same.
Also, I tried reflash recovery-Tiamat-R4c-100611-1150-cwm.zip from the SD card and get an error.
I really don't have a clue of what to do.
Any help would be welcome.
rogerodd said:
Rom manager says it is 4.0.0.4 but when in recovery is say CWM recovery-Tiamat-R4c-100611-1150-cwm or Tiamat v3.2.0.0 R4c ( I don't remember exectly) and the error is the same.
Also, I tried reflash recovery-Tiamat-R4c-100611-1150-cwm.zip from the SD card and get an error.
I really don't have a clue of what to do.
Any help would be welcome.
Click to expand...
Click to collapse
The problem is that you can't flash anything from the external sdcard with v4.0.0.4. In rom manager, see if you can find"all clockwork recoveries" and find 3.2.0.0. If not, find 3.0.2.8 or 3.0.2.5 and flash one of them, preferably the latest of those I have listed. I think those will at least recognize your sdcard. If you can't do that, you will need to reflash the correct recovery the same way you did when you rooted. Remember, never flash a zip file through adb.
Good luck!
I tried to flash recovery-Tiamat-R4c-100611-1150-cwm.img via adb.
I could flash boot sector. Then I reboot into recovery and try to apply zip from card with file update_US-Xoom-WiFi-3.2-HTJ85B-from-HMJ37_stachre_solarnz-boot-img_v05.zip, but there is a NO at the end of the name of the file and I can't go on.
Trying to rename as update.zip and run apply zip from card results in same error:
E: Can't open /sdcard/update.zip
(bad)
what should I do?
Thank you
possible bad download... download again... also, don't think this would be an update... leave it as originally named, just choose the option to choose which zip file to install from the sd card
rogerodd said:
I tried to flash recovery-Tiamat-R4c-100611-1150-cwm.img via adb.
I could flash boot sector. Then I reboot into recovery and try to apply zip from card with file update_US-Xoom-WiFi-3.2-HTJ85B-from-HMJ37_stachre_solarnz-boot-img_v05.zip, but there is a NO at the end of the name of the file and I can't go on.
Trying to rename as update.zip and run apply zip from card results in same error:
E: Can't open /sdcard/update.zip
(bad)
what should I do?
Thank you
Click to expand...
Click to collapse
It sounds like you are flashing recovery ok, but you keep overwriting it with the stock recovery.
Here is some important information that should help a lot with making your new recovery "stick"and this was taken from the Idiot's guide to flashing...in the Development section, and originally written by publicanimal:
4. Install recovery image (CWM)
Download the recovery image file and save it to your computer
Boot into flash mode with 'adb reboot bootloader'
Install your downloaded recovery image
C:\Documents and Settings\Anders> fastboot flash recovery recovery-Tiamat-R4c-100611-1150-cwm.img
Restart the device with 'fastboot reboot'. Timing is essential here, so be alert when the device restarts, or you will have to redo this section
Enter CWM with the following procedure
Once the Motorola logotype is shown, start counting to 3. At 3, press the Volume Down button. This should result in the text 'Android Recovery' in the top left corner. If it does not work, experiment with the timing ...
When 'Android Recovery' is shown press the Volume Up button. This should invoke the CWM recovery menu. If that works, then congratulations for reaching this far .
Here is a potential pitfall. If you are unable to enter CWM *before* the device boots into Honeycomb, then the newly installed recovery image will be overwritten by the system default recovery. If that happens, or if you see "starting fastboot protocol " your timing wasn't right and you need to reflash the recovery image and try it again.
See original post,below for more information.
http://forum.xda-developers.com/showthread.php?t=1130996

ClockworkMod Recovery for Motorola Triumph

Just making a new thread that has download links for ClockworkMod Recovery (CWM) that are readily apparent.
First to explain to anyone who does not know what ClockworkMod Recovery is:
quoting from this post:
What Is ClockworkMod Recovery And How To Use It On Android [Complete Guide]
ClockworkMod – also known as Clockwork and CWM – is a custom recovery for Android phones and tablets that allows you to perform several advanced recovery, restoration, installation and maintenance operations on your Android device that aren’t possible with the stock recovery.
The download links are at the end of this post.
Installation Instructions:
*****************************************************
To install CWM, do the following. If you wish to UPGRADE an existing CWM recovery that you already have installed, you still follow the following steps or alternatively, you can try the steps at the end of the post in the UPGRADE CWM USING FLASHABLE ZIP IN RECOVERY section:
1. Download the CWM Recovery file using one of the links at the end of the post. I recommend one of the latest versions--currently version 5.5.0.4. Unzip the recovery.img file from the Zip file you downloaded (using WinZip, 7-Zip, or another zip utility) onto your desktop so it is easy to find.
2. Turn OFF your Motorola Triumph (MT) phone.
3. Once the phone is off, make sure that it is not plugged into anything at this time.
4. Hold down the Power + Volume Down buttons simultaneously until the phone vibrates. (I usually hold the phone in one hand and then simultaneously press one button with my thumb and the other button with my forefinger)
5. The phone will boot into Download Mode. You will see the following types of messages on the screen:
polling, get oemsbl_mode=1
6. Now plug the phone into your computer. A drive labeled MOBILE will appear in your computer (MAC or Windows. Not sure about Linux)
7. Open the MOBILE drive and you should see a folder named image.
8. In the image folder, you will now see the recovery.img file.
9. Rename the file to recovery.img.old (or something like that) so you have a backup in case you ever want to revert back to the stock recovery.
10. Copy the recovery.img file that you unzipped in step 1 into the MOBILE folder on the phone.
11. After the copy is complete, unplug the phone from the computer and take out the battery, wait a second, and put the battery back into the phone.
12. To boot up into CWM, hold down the Power + Volume Up and Volume Down simultaneously until the phone vibrates.
Please note: DO NOT be alarmed if you see these types of error messages. Many people (including me) get them and none have reported that the errors affect the operation of ClockworkMod Recovery:
E:Can't mount /cache/recovery/command
E:Can't mount /cache/recovery/log
E:Can't open /cache/recovery/log
E:Can't mount /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
The MT should boot up into CWM. The latest stock version 5.5.0.4 will have blue lettering.
The controls for CWM 5.5.0.4 (as well as all previous Isaacj87 versions) in the MT are:
Volume up --> up
Volume down --> down
Power --> turns screen black
Menu --> select
Home --> nothing
Back --> back
Search --> nothing
If you want to view a video of how to install CWM on the MT, Minus5252 put together this video on this post -- just don't download the version shown in the video as that version is old:
http://androidforums.com/triumph-al...-recovery-motorola-triumph-4.html#post3021427
Download links:
Current Base CWM recovery.img:
CWM 5.5.0.4 (20120527) --RECOMMENDED VERSION
MT_CWM_5504_20120527.zip
MT_CWM_5504_20120527.zip
MD5: 0f847a44474b3cad5663b4409c089826
This Zip file is a flashable Zip file in clockworkmod recovery or follow the instructions above to install if you do not already have a previous version of clockworkmod recovery installed.
This version will recognize the .no_confirm or .one_confirm files in your clockworkmod folder when wiping data and cache also in addition to installing zips. See this post for instructions if you are interested in using the .no_confirm or .one_confirm:
http://androidforums.com/triumph-al...od-recovery-motorola-triumph.html#post4293429
Changelog from previous 5.5.0.4:
-Added "Power off" menu option back to main menu.
Themed CWM Versions based on sources from Tickerguy and Isaac:
b_randon14 5.0.2.7 (themed to be lime green):
recovery.img
agentc13 5.0.2.7 (Doctor Who theme using mostly blues):
http://www.mediafire.com/?p7oz58f6i9s95ro
Older versions linked here for posterity:
CWM 5.0.2.8:
MT_CWM_5028_recovery.zip
CWM 5.0.2.6 (thanks to isaacj87 and tickerguy) supports ext4
recovery-cwm-5.0.2.6-triumph.zip - reposting Isaac's link from Isaac's MIUI thread.
recovery-cwm-5.0.2.6-triumph.zip
recovery-cwm-5.0.2.3-triumph.zip
http://tinyurl.com/7ddvpcb
CWM 4.0.1.5 (thanks to isaacj87) supports ext 4
http://tinyurl.com/82f6qup
CWM 4.0.1.4 (thanks to isaacj87)
http://tinyurl.com/7e682nk
CWM 4.0.0.9 (thanks to tjstyle)
http://tinyurl.com/7cnrjyn
UPGRADE CWM USING FLASHABLE ZIP IN RECOVERY:
If you already have a Recovery on your MT and wish to flash a newer or different recovery version, b_randon14 has provided the following flashable ClockworkMod Recovery Zip files that you can just put on your SDCard and flash as normal--I have not tested them so, as usual, do so at your own risk:
Themed CWM Versions in flashable Zip:
b_randon14 5.0.2.7 (themed to be lime green):
b_randon14_CWM_5.0.2.7.zip
Stock CWM versions:
Here is the v5.0.2.3:
Isaacj87_CWM_5.0.2.3_signed.zip
v4.0.1.5(isaacj87's):
Isaacj87_CWM_4.0.1.5_signed.zip
v4.0.1.4(isaacj87's):
Isaacj87_CWM_4.0.1.4_signed.zip
Triumph STOCK RECOVERY in flashable Zip:
MT_stock_recovery.zip
CWM Recovery - NO TOUCHSCREEN - in flashable Zip:
MT_CWM_5504_20120527_yellow.zip
MT_CWM_5504_20120527_yellow.zip
MD5: a3e40a036d6123ebbb2065c8ddb6286b
Changelog:
MT_CWM_5504_20120527_yellow.zip
-Changed menu and text color to YELLOW.
-Always show the "Go Back" menu options on submenus.
-The keys for this version are:
Volume up --> up
Volume down --> down
Power --> select
Menu --> nothing
Home --> nothing
Back --> back
Search --> nothing
Huge thanks to Koush on whose work all CWM is based on. Thanks to isaacj87 who did the original port to the MT on which these are based. If I missed anything or forgot to thank anyone, let me know and I'll update this.
I'm a slow adopter and I think my clockwork is still at 4.0.0.9. Thank you for posting this relatively informative compilation of info.
Any outstanding features you want to mention right off the bat? The kind of stuff that would belong in OP?
Sent from my ADR6400L using Tapatalk
The main reasons to upgrade are:
1. The newest versions support ext 4 partitions which are necessary if you want to flash the latest CM7 ROM.
2. This may or may not be true, but I think they sync'ed the latest CWM code from the CM code and that was how it got updated to the 5.0.2.3. So there may be bug fixes that got pulled down--I could be wrong though--just guessing here.
3. I read some people report that in the CWM 4.0.0.9 there was an option to "format /fat" which they did and semi-bricked their phones. This option does not exist in the Isaac/Tickerguy CWM versions and so there's less chance of a user accidentally bricking their phones.
I tried all of these recovery imgs
I followed all of the directions and once I boot onto cwm I see below some errors
CWM-based Recovery v5.0.2.3
E:Can't mount /cache/recovery/command
E:Can't mount /cache/recovery/log
E:Can't open /cache/recovery/log
E:Can't mount /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
I've never experienced that but i've seen other people report the same thing. However, they also indicate that it doesn't seem to cause them issues. Try doing a backup and then a restore to see if that works for you.
Sent from my MOTWX435KT using XDA App
Mine always says can't mount cache/recovery/command
Hey llorn I'm making some cwm flashable zip recoveries tonight and ill pm you the links so you can add them to the open! I finally figured out how to flash recoveries from cwm!
Sent from my OC'ed Triumph!
Hey llorn, sorry but would you mind guiding me a bit, i would usually find a way to this without help but how should i backup and restore? Isnt that done through cwm? Whenever cwm loads i try pressing power for any option and all i get is a screen with nothing but a hat. Any suggestions?
jjuanml22 said:
Hey llorn, sorry but would you mind guiding me a bit, i would usually find a way to this without help but how should i backup and restore? Isnt that done through cwm? Whenever cwm loads i try pressing power for any option and all i get is a screen with nothing but a hat. Any suggestions?
Click to expand...
Click to collapse
As stated in the OP:
The controls for CWM 5.0.2.3 (as well as the Isaacj87 versions 4.0.1.5 and 4.0.1.4) in the MT are:
Volume up --> up
Volume down --> down
Power --> back
Menu --> select
Home --> nothing
Back --> back
Search --> nothing
And yes, you would do the backup and restore in the "Backup and Restore" option.
Older versions remove the menus if you push the...back button, I believe. They are returned if you push the button again but it's still disconcerting.
I wonder if there's any issues with wiping cache if you decide to do so... It's rather difficult to properly mount things on the Triumph, it seems!
Sent from my ADR6400L using Tapatalk
llorn do you know how embarrassed I feel. I can't believe i overlooked this. I'm an idiot! Just booted up cm7! I wish I could still install a custom kernel though....
Nah ur good wiping anything(besides fat!!!!) With these recoveries! Yeah this phone is partitioned weird but I haven't had a problem getting stuff to mount in my update zips!
Sent from my OC'ed Triumph!
updated OP to include the latest 5.0.2.6 CWM posted by Isaac.
No need to update if you don't want to if you are already using 4.0.1.5 or 5.0.2.3 -- unless you're like me and just have to have the latest versions...
jjuanml22 said:
I followed all of the directions and once I boot onto cwm I see below some errors
CWM-based Recovery v5.0.2.3
E:Can't mount /cache/recovery/command
E:Can't mount /cache/recovery/log
E:Can't open /cache/recovery/log
E:Can't mount /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
Click to expand...
Click to collapse
I got the same, by a mistake i picked an older version 4.0.1.5, and that worked just fine, but flashed to v5.0.2.3 and I got these errors and if I try to use any command it freezes. If I go back to 4.0.1.5 again it works. What can be causing this? Will a wipe first fix it?
i followed the directions but volume down and power doesn't boot me into download mode. I just get an exclamation mark and an android guy...suggestions?
edit: nevermind, i figured it out.
jjuanml22 said:
I followed all of the directions and once I boot onto cwm I see below some errors
CWM-based Recovery v5.0.2.3
E:Can't mount /cache/recovery/command
E:Can't mount /cache/recovery/log
E:Can't open /cache/recovery/log
E:Can't mount /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
Click to expand...
Click to collapse
I too am getting this on my Triumph with v5.0.2.6. I was able to load the CM7 Beta 8 after making a backup, but am wondering what these errors could mean for trying to restore from the Backup I created at the beginning.
vsanch24 said:
I too am getting this on my Triumph with v5.0.2.6. I was able to load the CM7 Beta 8 after making a backup, but am wondering what these errors could mean for trying to restore from the Backup I created at the beginning.
Click to expand...
Click to collapse
They won't affect anything. you should be fine.
llorn said:
They won't affect anything. you should be fine.
Click to expand...
Click to collapse
I got them too, but everything worked fine.
When i try to boot into recovery the phone vibrates endlessly until i do a battery pull. I followed the instructions but i did rename the CWM file from Recovery to Recovery.img could that be why its doing this?
Edit: Nevermind. That was the problem
jerenater10 said:
When i try to boot into recovery the phone vibrates endlessly until i do a battery pull. I followed the instructions but i did rename the CWM file from Recovery to Recovery.img could that be why its doing this?
Edit: Nevermind. That was the problem
Click to expand...
Click to collapse
If you were in windows 7 you named the file Recovery.img.img
Sent from my Revolting Revolution. Powered my mtmichaelson.
llorn said:
UPGRADE CWM USING FLASHABLE ZIP IN RECOVERY:
If you already have a Recovery on your MT and wish to flash a newer or different recovery version, b_randon14 has provided the following flashable ClockworkMod Recovery Zip files that you can just put on your SDCard and flash as normal--I have not tested them so, as usual, do so at your own risk:
Here is Isaac's 5.0.2.6:
http://www.mediafire.com/file/6kl88wot71do07l/Isaacj87_CWM_5.0.2.6_signed.zip
Here is the v5.0.2.3
http://www.mediafire.com/file/muzezh1mu9okmok/Isaacj87_CWM_5.0.2.3_signed.zip
v4.0.1.5(isaacj87's):
http://www.mediafire.com/?kl86quxsblcc6g7
v4.0.1.4(isaacj87's):
http://www.mediafire.com/?8sgd567mt86utan
If I missed anything or forgot to give anyone credit, let me know.
Click to expand...
Click to collapse
None of these links work for me

[Q] FUBAR'd (Status 7)

i seem to have fubar'ed my nexus s (uk version) i updated to ics, didnt like it so tried to restore to a backup i made earlier today...
at the moment when i turn on my phone it shows
fastboot mode- No Boot or Recovery img
lock state - unlocked
I can enter recovery. but cannot restore.
tried wiping cache,dalvik etc.
When hitting restore it returns with:
... system.img not found. skipping restore of /system/
also does the same with
data.img
cache.img
sd-ext.img
i have no idea what to do... if you could help it would be greatly appreciated.
Try flashing a rom. U can mount SD card within recovery.
Sent from my Nexus S 4G using xda premium
yeah tried flashing ...
gets stuck on google screen
Do you have a One Click return to stock available for your model? It wouldn't hurt to start fresh. I did that on my NS4G last week. Does your PC recognize the phone?
Sent from my SPH-D710 using Tapatalk
looking into the unbrickable mod atm... my phone seems to have no .img files.
tried restoring to stock and still the same issue... it says it cant find .img so skips them then when i try to re boot it sticks on the google screen
After trying to apply from zip (cm7, that i have used numerous times before)
i get this ---
Installing update...
assert failed: getprop("ro.product.device") =="crespo" ll getprop("ro.build.Product") == "crespo" ll getprop("ro.product.board") == "crespo"
E:Error in /sdcard/update-cm-7.0.3-NS-signed.zip
(Status 7)
Installation aborted.
i havent the faintest idea what to do...
Tried re-flashing CWM recovery?
yup tried re flash,
i think i need to replace the .img files... i just dont know how
it says that
system.img not found
data.img not found
cache.img not found
sd-ext.img not found.
it skips the restore of these say restore complete. yet there is obviously nothing to restore.
there must be a way of fixing this???
Do you have the latest version of CWM flashed? (5.0.2.0)
yeah re installed/reflashed (5.0.2.0)
it seems to be working
*~~~~~~*
Facepalm
*~~~~~~*
Such a noob
I have had a similar problem before, and even advised on that exact thing.
lesson learned.
KEEP RECOVERY.IMG UP TO DATE
Thank you for pointing out the obvious.
I'm such a ****
No problem flex59, best way to learn is the long and hard way . I had a similar status 7 problem on my move up to ICS. Figured the latest recovery will save me wasted hours down the track eventually, and hopefully someone elses.
To downgrade from ICS, you need to flash the full GB 2.3.6 ROM first...
I downgraded from OTA ICS 4.0.3 due to battery, Wifi & lag issues as well. A NANDroid backup does NOT contain the bootloader and radio AFAIK. Here's what I did.
Find the appropriate FULL ROM here and download and copy to your SD card.
Download this flashable Superuser here and copy to your SD card.
Make sure you are familiar with and set up for fastboot and have the latest CWM recovery img file. You will have to reinstall CWM. These instructions are assuming that CWM recovery is already installed on your device.
1. Make sure the full ROM and SU zip are on the root your SD card.
2. I did a full wipe of data, cache, dalvik.
3. Go into CWM recovery and flash the full ROM. Now flash the SU zip.
4. At this point, the full ROM flashed GB2.3.6, stock recovery, bootloader and radio back. But you should be rooted due to step 3.
5. Boot into Android. I installed ES File Explorer from the market. In ES File Explorer settings, select both root settings “Root Explorer” and “Mount File System” to navigate and modify root files. Allow permissions in SuperUser.
6. Navigate to /system/etc and rename (tap&hold on file) install-recovery.sh to install-recovery.sh.bak (this file reinstalls the stock recovery at every boot)
7. Using fastboot on your computer, flash CWM recovery again.
8. NOW using CWM, restore your GB 2.3.6 NANDroid backup.
Like nothing ever changed.

Recovering from /data mount issues

Guys,
I have had an device impacted by TWRP 2.7.X build that created the problem of not being able to mount /data and sometimes(/cache & /system) partitions.
I have managed to make it run a ROM by using information from
http://forum.xda-developers.com/showthread.php?t=1869673 & http://forum.xda-developers.com/showthread.php?t=1843062.
the problem is that the mounts are not remaining permanent and my modified boot.img does not boot the devices. So i have to mount the partition manually during the boot process over a shell and then the device boots.
Need help from experts to do a kernel which can mount sdext partition and an updated recovery image which also mounts the sdext partition as /data so that roms can be flashed easily.
I will try and do a writeup of how i made it run.
Resurrecting Pyramid
As mentioned in the earlier thread, my sensation got into trouble with TWRP 2.7 version and i was having trouble mounting /data, /system and /cache partitions.
I eventually got the /cache partition mounted by using mkfs.ext4 utility but could not get other and hence started working on a way to move both /data and /system partitions completly off SD card. Lot of people have already attempted that for other devices, feel free to go and check the threads linked in the post 1. Lets get started:
Assumptions: You have a sensation on which /data and /system partitions are an issue - not getting mounted / formatted etc. /cache is expected to be ok/working.
Requirements:
1) Your phone is booting and can go into recovery. Please get 4EXT recovery installed. You can download an img file from here
2) You have basic adb and fastboot setup on your machine(Win/Linux). Just google them out, if you dont have , there are plenty of tools out there.
3) Download Revelation 1.0.3 from here. you can choose any other ROM but i worked on this and have the boot image patched to look at /system from sd-ext.
4) download the two files attached with this thread.
Steps to recover:
1) Boot your phone in recovery. We will first get the SD Card set up. A Class 10 card is preferred, you will have a good feel on the phone.
2) Using 4EXT partition tool for sd card, create 2 sd ext partition in addition to your sdcard. I suggest first partition(which we will use as /system) to be more than 800 MB and second partition( which we will use as /data) to be more than 1024 MB.
3) Verify using the 'info' option of 4ext recovery that you can see sd-ext, sd-ext2 and sdcard partitions.
4) Extract the ROM you have downloaded using 7z/Winzip /winrar and replace the following files you have downloaded from this thread.
a) updater-script in /META-INF/com/google/android/ folder.
b) boot.img in /KERNEL folder.
5) Zip the file again and copy to your sdcard. Choose install from sdcard from the 4ext recovery menu. Choose default options in AROMA installer.
6) Reboot.
Hope your phone boots. If not, this is how you debug
Android will create a /proc/kmsg file when the kernel boots. So open two terminal(linux) windowds, in one, type this
Code:
adb pull /proc/kmsg
and in the second terminal(make sure the directory is same), type this:
Code:
cat kmsg | less
and then go through the error messages to see what is going wrong. If you can share your kmsg file created, I can try and help you debug.
Good luck !!!!!
Hi,
I followed your instructions but the Aroma installer always stops and the log shows this:
Code:
AROMA INSTALLER version 2.56
(c) 2012 by amarullz xda-developers
ROM Name : Revelation
ROM Version : 1.0.3
ROM Author : SebastianFM
Device : HTC Sensation/XE/4G
Start at : Fri Jan 2 00:00:31 1970
line 4 col 1: syntax error, unexpected BAD, expecting IF or STRING or '!' or '('
line 44 col 70: syntax error, unexpected BAD
2 parse errors
Installer Error (Status 6)
Jack Daniel's said:
Hi,
I followed your instructions but the Aroma installer always stops and the log shows this:
Code:
AROMA INSTALLER version 2.56
(c) 2012 by amarullz xda-developers
ROM Name : Revelation
ROM Version : 1.0.3
ROM Author : SebastianFM
Device : HTC Sensation/XE/4G
Start at : Fri Jan 2 00:00:31 1970
line 4 col 1: syntax error, unexpected BAD, expecting IF or STRING or '!' or '('
line 44 col 70: syntax error, unexpected BAD
2 parse errors
Installer Error (Status 6)
Click to expand...
Click to collapse
Pick the files from here and then try...
http://forum.xda-developers.com/htc-sensation/help/bricked-htc-corrupted-partitions-t2804222/page3
rmann said:
Pick the files from here and then try...
http://forum.xda-developers.com/htc-sensation/help/bricked-htc-corrupted-partitions-t2804222/page3
Click to expand...
Click to collapse
I tried that before.
Same result but it shows one error less.
Code:
...
line 4 col 1: syntax error, unexpected BAD, expecting IF or STRING or '!' or '('
1 parse errors
Installer Error (Status 6)
Jack Daniel's said:
I tried that before.
Same result but it shows one error less.
Code:
...
line 4 col 1: syntax error, unexpected BAD, expecting IF or STRING or '!' or '('
1 parse errors
Installer Error (Status 6)
Click to expand...
Click to collapse
Which recovery are you using... I have re-tested the script and it works ok for me.
rmann said:
Which recovery are you using... I have re-tested the script and it works ok for me.
Click to expand...
Click to collapse
I get the same exact error as Jack Daniel's.
I am using as recovery 4EXT Recovery Touch v1.0.0.5 RC5.
antiziclon said:
I get the same exact error as Jack Daniel's.
I am using as recovery 4EXT Recovery Touch v1.0.0.5 RC5.
Click to expand...
Click to collapse
did you try to update the recovery to the latest version?
rzr86 said:
did you try to update the recovery to the latest version?
Click to expand...
Click to collapse
Just tested with v1.0.0.6 RC3 build 8, same error
antiziclon said:
Just tested with v1.0.0.6 RC3 build 8, same error
Click to expand...
Click to collapse
redownload the zip file
after that i am out of ideas
ok, I found out the issue.
The issue is on the encoding of the "updater-script" file.
It needs to be in Unix encoding. If you use Windows (as I do) when unzipping the Zip file or when creating a new file with a text editor, the encoding gets changed and it is not Unix encoding.
To solve it:
- Open the file in Notepad++.
- Go to Edit --> EOL Conversion --> UNIX
It will change the enf of lines to comply with Unix encoding. Then add the file to the Rom zip file and you are ready to go
Enjoy!
Successful Pyramid rescue
I have a sensation with corrupted emmc caused by TWRP, /data cannot be mounted.
I followed your instructions and addition re script encoding and successfully installed Revelation to partitioned sdcard.
Phone boots and works.
That's great, thanks.
I have some questions:
1. Is 512 MB sufficient for swap partition? What would be the optimal size?
2. My sensation is s-on unlocked, and I had to flash boot via fastboot after install, 4ext did not flash it despite smartflash option turned on. Is that normal?
2. Superuser does not seem to work, I have no root. I checked with root validator and I have su binary, superuser and busybox, but no root is given to apps that require it, su binary update fails, and there are no logs left in superuser to check (or I simply don't know where to look).
Thank you.
rmann said:
As mentioned in the earlier thread, my sensation got into trouble with TWRP 2.7 version and i was having trouble mounting /data, /system and /cache partitions.
I eventually got the /cache partition mounted by using mkfs.ext4 utility but could not get other and hence started working on a way to move both /data and /system partitions completly off SD card. Lot of people have already attempted that for other devices, feel free to go and check the threads linked in the post 1. Lets get started:
Assumptions: You have a sensation on which /data and /system partitions are an issue - not getting mounted / formatted etc. /cache is expected to be ok/working.
Requirements:
1) Your phone is booting and can go into recovery. Please get 4EXT recovery installed. You can download an img file from here
2) You have basic adb and fastboot setup on your machine(Win/Linux). Just google them out, if you dont have , there are plenty of tools out there.
3) Download Revelation 1.0.3 from here. you can choose any other ROM but i worked on this and have the boot image patched to look at /system from sd-ext.
4) download the two files attached with this thread.
Steps to recover:
1) Boot your phone in recovery. We will first get the SD Card set up. A Class 10 card is preferred, you will have a good feel on the phone.
2) Using 4EXT partition tool for sd card, create 2 sd ext partition in addition to your sdcard. I suggest first partition(which we will use as /system) to be more than 800 MB and second partition( which we will use as /data) to be more than 1024 MB.
3) Verify using the 'info' option of 4ext recovery that you can see sd-ext, sd-ext2 and sdcard partitions.
4) Extract the ROM you have downloaded using 7z/Winzip /winrar and replace the following files you have downloaded from this thread.
a) updater-script in /META-INF/com/google/android/ folder.
b) boot.img in /KERNEL folder.
5) Zip the file again and copy to your sdcard. Choose install from sdcard from the 4ext recovery menu. Choose default options in AROMA installer.
6) Reboot.
Hope your phone boots. If not, this is how you debug
Android will create a /proc/kmsg file when the kernel boots. So open two terminal(linux) windowds, in one, type this
Code:
adb pull /proc/kmsg
and in the second terminal(make sure the directory is same), type this:
Code:
cat kmsg | less
and then go through the error messages to see what is going wrong. If you can share your kmsg file created, I can try and help you debug.
Good luck !!!!!
Click to expand...
Click to collapse
Ok try to make that in unix
Extreme lag
Hi there,
I followed all the staps, but when the rom was installed, it was very laggy and i experinced a lot of force closes. Is this because the partions are to small or because the sd is to slow EDIT: its a class 4 card?
Greetings,
Danil
Extreme unuseful slow
With my sensation XE i also followed all steps. Revelation 1.0.3 is booting, but not to use at all, it stucks in every step, cant even receive a call, can't go to any menu. Pls someone help me out of here. Do I need a swap partition? Or are the partitions to small? sd-ext has 1024Mib; sd-ext2 1537Mib.
danilandroid said:
Hi there,
I followed all the staps, but when the rom was installed, it was very laggy and i experinced a lot of force closes. Is this because the partions are to small or because the sd is to slow EDIT: its a class 4 card?
Greetings,
Danil
Click to expand...
Click to collapse
Hi Danil, could you solve the problem? I encounter same symptoms. My Phone: Sensation XE; Revelation 1.0.3. Cant use it at all , it boots but gets totally stuck. Have original sd, dont know the class. Greetings dididoner
dididoner said:
Hi Danil, could you solve the problem? I encounter same symptoms. My Phone: Sensation XE; Revelation 1.0.3. Cant use it at all , it boots but gets totally stuck. Have original sd, dont know the class. Greetings dididoner
Click to expand...
Click to collapse
probably you need a sdcard with high speed of w/r but i am not sure
Lag
rzr86 said:
probably you need a sdcard with high speed of w/r but i am not sure
Click to expand...
Click to collapse
I'm going to buy a sd-card class 10 and than I will try the same thing agian. I will report later.
@ rmann Btw thanks for the amazing thread, I was completely stuck and now my phone is alive again kinda.
Danil
danilandroid said:
I'm going to buy a sd-card class 10 and than I will try the same thing agian. I will report later.
@ rmann Btw thanks for the amazing thread, I was completely stuck and now my phone is alive again kinda.
Danil
Click to expand...
Click to collapse
rzr86 said:
probably you need a sdcard with high speed of w/r but i am not sure
Click to expand...
Click to collapse
dididoner said:
Hi Danil, could you solve the problem? I encounter same symptoms. My Phone: Sensation XE; Revelation 1.0.3. Cant use it at all , it boots but gets totally stuck. Have original sd, dont know the class. Greetings dididoner
Click to expand...
Click to collapse
So, I bought a class 10 card, revelation is running now!! At first start it was still very slowly an got stuck allover. But at second start it is running now! Thanks for that perfect thread!!:good:
I wonderd why vipers wont start the same way? When I try to boot it , 4ext recovery is starting rightaway with little delay!
Hi, when I got the same problem with /data, /cache and /system not mounting. I followed the steps from #2 post http://forum.xda-developers.com/showpost.php?p=55157092&postcount=2
and when I try to install from zip it says that the zip isn't meant to be flashed in recovery and it aborts the installation. First I tried renaming the new_boot.img you provided to boot.img but it's the same result.

"This package is for A0001, this device is bacon." Wiped internal storage, cant flash

"This package is for A0001, this device is bacon." Wiped internal storage, cant flash
Like an idiot, I accidentally wiped internal storage while trying to flash a new ROM, so all my data ( which I dont care about ) and my backup images got deleted. I still have access to TWRP so I thought it wasnt that bad and went ahead installing ROMS as I usually would.
I transferred the zip files from PC to the phone via adb push method and tried to flash
However, I an unable to install any ROM as it gives me an error every time. This is what the error message reads:
Skipping MD5 check : no MD5 file found
This package is for device: A0001; this device is bacon
E: Error executing updater binary in zip ' /sdcard/cm...(name of the rom here).zip '
Error flashing zip ' /sdcard/(nameofrom).zip '
I did quite a bit of research and read on one of the official OnePlus that all the ROMs are signed for the device A0001 but the device itself reads itself as bacon, which is its codename. Since "bacon" != "A0001" the zip installation fails.
Am I stuck with an expensive paperweight here? Please help.
TLDR: Wiped internal storage, No OS, flashing throws up error every time
If you can acces TWRP, just by connecting the OPO to your PC should give you acces to storage. I guess that you are trying to install H2OS, download the fixed version with the updater-script fixed. If it gives you this error with another rom, just download another custom rom and put in on the internal storage or flash the stock OS with fastboot
KuranKaname said:
If you can acces TWRP, just by connecting the OPO to your PC should give you acces to storage. I guess that you are trying to install H2OS, download the fixed version with the updater-script fixed. If it gives you this error with another rom, just download another custom rom and put in on the internal storage or flash the stock OS with fastboot
Click to expand...
Click to collapse
Yep, inside the rom zip, there is a file called updater-script.
In this file, there is a line checking the phone name.
While most of the roms are using "bacon", H2OS original zip file uses "A0001" instead.
Can you try with any other rom?
niranjanbhat said:
Like an idiot, I accidentally wiped internal storage while trying to flash a new ROM, so all my data ( which I dont care about ) and my backup images got deleted. I still have access to TWRP so I thought it wasnt that bad and went ahead installing ROMS as I usually would.
I transferred the zip files from PC to the phone via adb push method and tried to flash
However, I an unable to install any ROM as it gives me an error every time. This is what the error message reads:
Skipping MD5 check : no MD5 file found
This package is for device: A0001; this device is bacon
E: Error executing updater binary in zip ' /sdcard/cm...(name of the rom here).zip '
Error flashing zip ' /sdcard/(nameofrom).zip '
I did quite a bit of research and read on one of the official OnePlus that all the ROMs are signed for the device A0001 but the device itself reads itself as bacon, which is its codename. Since "bacon" != "A0001" the zip installation fails.
Am I stuck with an expensive paperweight here? Please help.
TLDR: Wiped internal storage, No OS, flashing throws up error every time
Click to expand...
Click to collapse
Instead of using adb push metod try to flash stock rom (https://forums.oneplus.net/threads/oxygenos-2-1-4-for-the-oneplus-one.425544/) and then flash the rom you want.
Good luck!
Note: You will loose twrp, so you have to flash it via fasboot [fastboot flash recovery (recovery name).img]
I'd suggest you to start over with a clean flash of COS13 fastboot factory image. Sounds like you are on a very old base.
Try to reboot TWRP and flash again. Or remove that check string from the updater-script.
download CM11 factory recover tool from my google drive @ https://drive.google.com/open?id=0ByfGPjP5zNYSTDZZcXZpLU44Q00 and install drivers and go to fastboot and plug in the phone and run recovery tool to push default factory image then install whatever CM version you want directly
No updater-script file that I can see
Can't find that file!
Anghirrim said:
Yep, inside the rom zip, there is a file called updater-script.
In this file, there is a line checking the phone name.
While most of the roms are using "bacon", H2OS original zip file uses "A0001" instead.
Can you try with any other rom?
Click to expand...
Click to collapse
use usb otg, success each time!
setup on ubuntu
Instructions for install on linux (test on ubuntu)
1- install adb :
Code:
$ sudo apt-get install android-tools-adb
2- install fastboot :
Code:
$ sudo apt-get install android-tools-fastboot
3- Turn the phone off. Then boot it into fastboot mode by holding volume up + power. The phone will display "fastboot" text indicating that it has successfully entered fastboot mode.
4- test if the phone is detected with the cmd :
Code:
$ fastboot devices
5- unlock bootloader (/!\ it wipe the phone) :
Code:
$ sudo fastboot oem unlock
6- install TWRP :
- go to the path where is the img
Code:
$ cd path/to/twrp/folder/
- rename the image to twrp.img
Code:
$ mv old_name.img twrp.img
- flash the recovery
Code:
$ sudo fastboot flash recovery twrp.img
/!\ Once the flash has completed, Don't use the "Fastboot Reboot" Command Instead Unplug Your phone then Manually turn it off by pressing and holding power button until it switches off. Now to enter your newly installed custom recovery, hold volume down + power. The phone should boot into recovery mode. Now that you have a custom recovery, you may continue to the final step. /!\
7- install custom/official ROM with TWRP :
- Wipe > Swipe to Factory Reset
- Install > browse to the location where you previously copied the ROM zip and select it > Swipe to confirm the installation
- Install GApps using same process as ROM, then reboot. (optionnal: the official OnePlus ROM come with GApps pre-installed)
Possible errors with official ROM :
"This package is for device: A0001; this device is bacon" or "This package is for device: OnePlus; this device is A0001" or other similar
==> go into the ROM zip file, in "/META-INF/com/google/android/" there is an "updater-script" file. Open it, locate the expression ' getprop("ro.build.product") == "A0001" ' and replace the "A0001" by the device name you have. Replace the file in the archive. Note : after that, you can't verify the official MD5 !
- example : "This package is for device: A0001; this device is bacon", the ' getprop("ro.build.product") == "A0001" ' become getprop("ro.build.product") == "bacon" '
Sources :
https://forums.oneplus.net/threads/...oader-install-custom-recovery-and-root.64487/
https://forum.xda-developers.com/oneplus-one/help/package-a0001-device-bacon-wiped-t3457766
Oneplus one Oxygen Installation error using TWRP
niranjanbhat said:
Like an idiot, I accidentally wiped internal storage while trying to flash a new ROM, so all my data ( which I dont care about ) and my backup images got deleted. I still have access to TWRP so I thought it wasnt that bad and went ahead installing ROMS as I usually would.
I transferred the zip files from PC to the phone via adb push method and tried to flash
However, I an unable to install any ROM as it gives me an error every time. This is what the error message reads:
Skipping MD5 check : no MD5 file found
This package is for device: A0001; this device is bacon
E: Error executing updater binary in zip ' /sdcard/cm...(name of the rom here).zip '
Error flashing zip ' /sdcard/(nameofrom).zip '
I did quite a bit of research and read on one of the official OnePlus that all the ROMs are signed for the device A0001 but the device itself reads itself as bacon, which is its codename. Since "bacon" != "A0001" the zip installation fails.
Am I stuck with an expensive paperweight here? Please help.
TLDR: Wiped internal storage, No OS, flashing throws up error every time
Click to expand...
Click to collapse
check this post
wirelessindeed.blogspot.com/2017/07/oxygen-installation-error-on-oneplus.html
Update TWRP Recovery
I know this is an old post, so this is here in case anyone finds it in the future and requires help...
My mate asked me to upgrade his OnePlus (original, codename Bacon) and I received this error when upgrading from LineageOS 14.1 to 15.1.
To resolve, its extremely easy - simply upgrade the TWRP recovery. My mate originally had TWRP 3.1.1.0 installed, but the latest weekly LineageOS 15.1 required v3.2.3.0 installed which resolved the error message "This package is for device: bacon, a1001. this device is ."
Either Vol+ and Power to enter bootloader, or from command line:
adb reboot bootloader (with Android USB debugging turned on. You can test for connection using command "adb devices" and if successful it should show your phone's serial number). You will need to trust the computer's connection on your phone. To get to Android USB Debugging, you need to go Settings -> Developer menu options, and if you can't see that: Settings -> About Phone and tap "Build" 7 times for developer mode to appear.
Once phone goes into bootloader mode, type:
fastboot flash recovery "path:\twrp-x.x.x.x-bacon.img" (obviously path is the directory that the recovery is stored in, and x.x.x.x will be replaced with the version you've just downloaded. At time of writing, v3.2.3.0 is the latest. You can always use "fastboot devices" if you used Vol+ and Power to enter bootloader to ensure you have a valid connection, in USB debugging mode on your phone and correct Android adb drivers installed in Windows.
Wait until it's succeeded, and turn off phone. Now go into recovery and try again - and this time you should be good to go!!!
All the above implies your bootloader is unlocked. If you need to unlock your bootloader, there are plenty of instructions telling you how to do this - but HAVE A BACKUP as unlocking your bootloader will do a factory reset on your phone.
Hope this helps someone
......mmmmmm BACON!!!

Categories

Resources