Code:
E:Can't open /cache/recovery/log
E:Can't open /cache/recovery/log
E:Can't open /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
When you see this message in your recovery do not panic.
Setup adb/fastboot on your computer (there is a simple guide in my signature). Then connect your device to the PC, enter recovery, open cmd (command prompt) on the PC and type:
Code:
adb shell
dmesg | grep mmc0
If the output contains the following strings:
Code:
mmc0: failed to get card ready
mmc0: reinit card
mmc0: Starting deferred resume
mmc0: Deferred resume failed
Than you internal memory (eMMC) is corrupted i.e. your chip is "fried". This is a hardware issue (reference here) and the chip has to be replaced. Sorry, no other solutions available.
If not - your chip is not fried!
This message results from a destroyed /cache partition - some relevant info here
Some basic thing has to be done to solve this problem easily:
NEVER PULL THE BATTERY! Better have the patience to wait it to be completely drained
always keep a Backup of your current ROM and/or the Stock ROM, made from Recovery on your SDcard
enable USB Debugging in your Settings -> Applications -> Development and keep it that way
disable Fastboot in Settings -> Power to have total shutdown on power off
after unlocking (S-OFF) your device with Revolutionary flash an Engineering bootloader (e.g. 0.98.2000) to be able to overwrite it when needed
use 4EXT Recovery rather than ClockworkMod it has much better functionality
To restore one of the following has to be done:
restore the Nandroid backup if you have done it
or
restore the cache partition - wipe /cache from the Recovery (preferred - thanks forcefreak). If the size of the partition says <null> (when Printing partition info in 4EXT Recovery) connect your device to a PC, go into adb shell (look the link in my signature for adb setup) and type
Code:
mke2fs /dev/block/mmcblk0p27
do not pay attention to the busy partition message, then
Code:
reboot recovery
Note that this option will format your cache as ext2 or ext3 type. If you are using ext4 just use the 4EXT Recovery to reformat them as ext4
or
According to craigcharlie's post
selecting the Factory reset option in the HBOOT is also a way to boot to Recovery and then flash a custom ROM or restore a backup
or
if steps 1/ 2/ 3 are not working flash the relevant RUU (the same or higher version than your current and correct region/brand - you can find the available for Desire S here) when your phone is in FASTBOOT USB mode in bootloader (you may need to reinstall the HTC drivers) [credits go to dave303 and the guide in his blog.]
4.1 If you have a 6.98.1000 hboot
Change your hboot with this one
Download PG88IMG.zip, extract it and use Android Flasher to flash the extracted hboot.img
The hboot version now should be 0.98.2000
Search in this thread for the proper RUU and install it.
4.2 If you have a 6.98.1002 hboot
Change your hboot with this one
Download the hboot_0.98.0000.zip and extract it, boot your phone to Recovery, connect to PC, copy the hboot.img file to your SDcard, open command prompt and type:
Code:
adb devices [I](your device serial number should be displayed)[/I]
adb shell [I](there should be a command prompt with the # symbol in front if not type "su" without the quotes)[/I]
dd if=/sdcard/hboot.img of=/dev/block/mmcblk0p18[I][/I]
if not working try to unmount/mount the SDcard:
Code:
adb devices [I](your device serial number should be displayed)[/I]
adb shell [I](there should be a command prompt with the # symbol in front if not type "su" without the quotes)[/I]
umount /sdcard [I](not a typo the command is umount, not u[B]N[/B]mount)[/I]
mount /sdcard
dd if=/sdcard/hboot.img of=/dev/block/mmcblk0p18[I][/I]
Search in this thread for the proper RUU and install it.
NOTE: If you have a custom ROM and no info about your original software version the solution is as follows:
Connect the device, enter the bootloader and type the following command in the cmd:
Code:
fastboot getvar version-main
This is the number of your original software.
If this number is higher than the one of your RUU and you cannot flash it, change the number with the version of your RUU (be careful - use the correct RUU for your brand/region!) with misc_version that can be found here - post #1, link from step 1.
If you have problems with some of the above post in the Desire S General forum or in this thread to receive support. Some cases can be individual but there is always a chance to fix before going for a replacement
You should PM ben_pyett, he has full guides on this whole thing. Also so he could add it to the "index" thread ^.^
Wow.sick tutorial. this must get a place in the index in very very big, bold letters.
Sent from my HTC Desire S/S510e using XDA App
Other way to solve this problem?
Hi
I had the same error after installing a new RADIO version on my Desire S.
-> Market closes unexpected
-> Can't open cache... in recovery
I fixed the problem with CWM Recovery!
1. Restart phone to ClockworkMod Recovery
2. Choose "wipe cache partition"
3. "reboot system now"
DONE
Just checked my chip and luckily I'm not affected. Sympathy to l u guys who are. (
Sent from my HTC Desire S using xda premium
forcefreak said:
Hi
I had the same error after installing a new RADIO version on my Desire S.
-> Market closes unexpected
-> Can't open cache... in recovery
I fixed the problem with CWM Recovery!
1. Restart phone to ClockworkMod Recovery
2. Choose "wipe cache partition"
3. "reboot system now"
DONE
Click to expand...
Click to collapse
I have tried this as well but my partition size was null. Tried formatting as Ext3 and Ext4. Honestly haven't tried just to format...
Btw the command mk2fs (the 2nd method in my initial post) makes exactly the same as your solution but from the command prompt. Anyway yours is easier so thanks for the contribution! But keep in mind that in both ways the partirion will be restored as ext3 so you will have to use 4EXT Recovery later to convert if you want to use the advantages of ext4
Hello,
I've just one question: why this happens?
Every time I wipe the cache and the dalvik-cache through the Recovery, I get this error. Should be considered as normal hence?
fbcyborg said:
Hello,
I've just one question: why this happens?
Every time I wipe the cache and the dalvik-cache through the Recovery, I get this error. Should be considered as normal hence?
Click to expand...
Click to collapse
"Every time" is definately not NORMAL! Check your partiton type ext2/3/4. If not ext4 format it as such with 4EXT Recovery
And one piece of advice: change your bootloader version, in case you stuck. This cannot be overwritten so you will go straight to replacement (most probably paid by you)
Sent from my HTC Desire S using Tapatalk
How can I see which filesystem type is it?
Anyway, I use ClockworkMod now, and I don't think it is ext4.
---------- Post added at 05:00 PM ---------- Previous post was at 04:35 PM ----------
Checked: it is a ex2 partition.
I've just flashed the 4EXT Recovery.
So, you suggest to change the bootloader? Which version?
I didn't understand what could cause the stuck: the partition type change? What cannot be overwritten? Maybe it's not clear to me what is the risk.
fbcyborg said:
How can I see which filesystem type is it?
Anyway, I use ClockworkMod now, and I don't think it is ext4.
---------- Post added at 05:00 PM ---------- Previous post was at 04:35 PM ----------
Checked: it is a ex2 partition.
I've just flashed the 4EXT Recovery.
So, you suggest to change the bootloader? Which version?
I didn't understand what could cause the stuck: the partition type change? What cannot be overwritten? Maybe it's not clear to me what is the risk.
Click to expand...
Click to collapse
The best option IMO is the hboot from my signature: 0.98.2000 (2.0.2002 reduces your cache space and maybe will be useful in future, but for now it isn't)
The reason: Revolutionary/Alpharev is permanent, which means that it cannot be overwritten (I have an untested method that may unlock it but I cannot verify and definitely will not brick my device to try it out ), unlike the other ENG Bootloaders which provide the same functionality but can be easily replaced (by RUU for example) if necessary. Like if you flash some incompatible software that bricks your phone and you are not able (or just do not have) to restore a Nandroid backup there is nothing you can do except to go to a repair center, where they will see that your bootloader is 6.98.1002 and most probably you will pay the repair (the eMMC chip costs about 1/3 of the phone price). On other hand if you can restore the system or at least the bootloader with the Stock one (e.g. from RUU) you can always say that your phone just collapsed and you do not know anything about it. I hope now it will be more clear to you.
P.S.: 4EXT Recovery is the best choice!
Thanks a lot for the explanation. You was very clear now.
So, if I'm not wrong, and if I've really understood everything, you mean that my old ClockworkMod Recovery is still there, and the 4EXT (that is a modified CWM recovery), is a sort of upgrade of CWM.
Anyway, I have a doubt about the hBoot you mentioned: the 0.98.2000 which is reported as the original one in the related thread, but before S-Offing and rooting my phone with revolutionary, I had 0.98.0002. Is it not different?
fbcyborg said:
Thanks a lot for the explanation. You was very clear now.
So, if I'm not wrong, and if I've really understood everything, you mean that my old ClockworkMod Recovery is still there, and the 4EXT (that is a modified CWM recovery), is a sort of upgrade of CWM.
Anyway, I have a doubt about the hBoot you mentioned: the 0.98.2000 which is reported as the original one in the related thread, but before S-Offing and rooting my phone with revolutionary, I had 0.98.0002. Is it not different?
Click to expand...
Click to collapse
4EXT Recovery is based on ClockworkMod, but is has more functionality...now you can still use your backups from CWM, even to convert them to ext4 format (check the 4EXT thread in my signature all is described there.
Now, my explanation above was related to the bootloaders (hboot)
For the Desire S there are the following hboot versions:
0.98.0000, 0.98.0002 and 2.00.0002 - Stock. The latter currently cannot be unlocked by Revolutionary exploit
0.98.2000 - "old" Engineering bootloader that allows you to flash system stuff like custom Recovery, different Radio version, unsigned stuff, etc.
2.00.2002 - Engineering bootloader with the same functions as the "old" one but with different partition style (/cache is 150 MB smaller and /system has 150 MB more space), but currently supported only by the new OTA (Stock) ROM
6.98.1000 and 6.98.1002 - Revolutionary/Alpharev Engineering bootloader that is installed on your device after S-OFF, with the same functions and partition style as 0.98.2000, but cannot be directly overwritten by RUU if you get in trouble...
I've just put the 0.98.2000 ENG hBoot, but as regard the filesystem type: do you mean I have to convert all partitions to ext4 or only the cache partition?
fbcyborg said:
I've just put the 0.98.2000 ENG hBoot, but as regard the filesystem type: do you mean I have to convert all partitions to ext4 or only the cache partition?
Click to expand...
Click to collapse
system, data and cache. Then flash the new ROM. Of course you can use ext3 without any problems. Do some reading here and decide for yourself, but it is mentioned that:
The ext4 filesystem is backward compatible with ext3 and ext2, making it possible to mount ext3 and ext2 filesystems as ext4. This will slightly improve performance, because certain new features of ext4 can also be used with ext3 and ext2, such as the new block allocation algorithm.
Click to expand...
Click to collapse
I've followed your suggestions, and this time, with 4EXT and the cache wipe, I've not seen the messages I've reported when I used the CWM. Formatted all partitions (not the sdcard) to ext4 and all is OK!
fbcyborg said:
I've followed your suggestions, and this time, with 4EXT and the cache wipe, I've not seen the messages I've reported when I used the CWM. Formatted all partitions (not the sdcard) to ext4 and all is OK!
Click to expand...
Click to collapse
Glad to hear
Awesome post.
I have one extra problem right now and that is my phone will not power up?
I have the symptoms of fried eMMC chip, but since switching it off at one point it will not power up anymore. Tried battery in a different phone and it is nearly full.
Any Ideas?
clubbtraxx said:
Awesome post.
I have one extra problem right now and that is my phone will not power up?
I have the symptoms of fried eMMC chip, but since switching it off at one point it will not power up anymore. Tried battery in a different phone and it is nearly full.
Any Ideas?
Click to expand...
Click to collapse
is there any vibration when you turn it on or does the led light?
have you altered your device eg root or custom ROM etc?
If no return under warranty as sounds like hardware issue
Swyped from my Desire S using XDA Premium
Ben, right now nothing happens when I press the power button.
My saga was rooted through AlphaRev and I was trying few different ROMs
Somewhere along the way I changed my SD card and after powerup into recovery I noticed for the first time these errors in CWM.
After reading on here I tried few things and at one point shut it off and since can't power back on. My hboot and recovery were still working but as said can't power up anymore now.
When I attach the USB cable the led flashes on and off about every second or two. This stops when I press the power button but the phone doesn't power up.
Looks like bricked to me :-(
clubbtraxx said:
Ben, right now nothing happens when I press the power button.
My saga was rooted through AlphaRev and I was trying few different ROMs
Somewhere along the way I changed my SD card and after powerup into recovery I noticed for the first time these errors in CWM.
After reading on here I tried few things and at one point shut it off and since can't power back on. My hboot and recovery were still working but as said can't power up anymore now.
When I attach the USB cable the led flashes on and off about every second or two. This stops when I press the power button but the phone doesn't power up.
Looks like bricked to me :-(
Click to expand...
Click to collapse
Yes seem like a total brick...I think that you have flashed something that is not belonging to your phone (probably you are branded). Anyway try adb and fastboot, if any of these commands can detect the phone you can try to reboot to bootloader or recovery. If not go straight for a repair and do not mention the custom software part
P.S. curious what you did before this happened?
Related
Update - 2/21/2011
If you have bricked an HTC EVO this will likely NOT work for you and this is the wrong info to be reading. I have gotten a few emails from this link about EVO 110 errors.
12/26/2010 - This thread is super old now:
If you ran the 1.56 RUU and your phone no longer turns on visit htc.com, go to support, choose Hero (Sprint) and download the 2.1 system update.
Remove battery from your phone and start it up again, then run the exe file that you just downloaded -
http://member.america.htc.com/downlo...2.27.651.6.exe
------All the info below is kept for reference -------
(As of 3/31/2010 - I am 10 for 10 for getting these back and working!! 3/3 of going back to 100% stock)
Edit: I have no longer kept track... its been over a month and I know personally I've done about 15 more of these... with about half being return to stock.
If you need to contact me, PLEASE EMAIL instead of using private messages, it'll probably turn into a google talk chat anyways, so add me on there, [email protected] (Its just easier than having to log in here and reply to private messages, since I get emails on the go as well.)
So you just ran the 1.56 RUU and got a 110 error. Now your screen turns on and stays black and if you plug the phone into USB you see the HTC logo. Unplug it and see the RUU menu.
Like you, I decided to attempt to roll back using the RUU 1.56. I was hit with the 110 error, and nothing but fastboot would work, I was able to launch ./fastboot-mac oem boot to get into the system.
I tried ./fastboot-mac boot image/bootname.img and a billion other things like everyone else who is having the issue, but just like them I had no success. In the second post below are the steps to resolve this issue. This will either take you to your first Nandroid backup or to whatever ROM you choose to flash once you get recovery back. I have not found a way to get back to 100% stock, but at least your phone wont be a brick.
EDIT:As of 3/30/2010 @ 8:30 PM I was able to get my phone completely 100% to stock. I was able to do this by retrieving a Nandroid restore from someone who used flashrec to make their initial backup. This restore does not touch the recovery image but I was able to boot into my recovery then write the HTC recovery back on top of it. I now have 100% un-rooted phone. See Post number 2 for the right way to do this.?
I've helped a few people over log me in now.
I'm willing to continue doing this but it is cutting into my family time, I will do this for a "respectable" amount of money.
Feel like I've helped you??
Buy me some coffee!
(Zip attached includes fix and stock folders. Use the fix folder FIRST to get completely booted. You can use the stock folder if you want to get 100% stock after you have a running unrooted system but have RA recovery.)
Steps to resolve:
(You SHOULD have a Nandroid backup of some sort, if not download a ROM... Fresh1.1??)
1) Boot the phone to black screen
2) Plug phone into PC/MAC - The HTC logo should appear at this point
---- If you've been doing anything else, rerun the RUU and let it fail and reboot to the HTC logo.
3) PC - fastboot oem boot | MAC - ./fastboot oem boot
(Make sure you turn on USB Debugging under Settings --> Applications --> Developer)
4) Root your phone using asroot2
Code:
adb push asroot2 /data/local/
adb shell chmod 0755 /data/local/asroot2
adb shell
/data/local/asroot2 /system/bin/sh
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
cd /system/bin
cat sh > su
chmod 4775 su
5) This is where your Nandroid backup comes into play.
(Browse to your nandroid folder, find your first backup and copy all of the .img files except system and cache to your SD card root directory)
NOTE: At this point you should dismount the SD card if you mounted inside of Android OS(Sense/Launcher)
6) run adb shell (PC - adb shell | Mac - ./adb shell)
7) type su
8) Run the following commands (if you get out of memory errors, type su again and try once more)
NOTE: Do not copy the "#"'s in the commands, the # just means you are running as SU, as opposed to the "$"
Code:
# flash_image recovery /sdcard/recovery.img
# flash_image boot /sdcard/boot.img
# flash_image misc /sdcard/misc.img
9) now... type reboot recovery
This time you should get your recovery menu, should have been RA or whatever you used... from there I did a complete nandroid restore and my system booted.
Also, after I did this I did try to let it boot without doing a recovery and it wouldnt go anywhere... but I'm fairly impatient... it may have wanted to load. I figured it best to do an entire Nandroid restore though.
-------------------------------------------------------------
100% Stock Configuration Work Around
-------------------------------------------------------------
Non-Rooted Nandroid Backup:
nandroid.7z
I was able to get my phone completely 100% to stock. I was able to do this by retrieving a Nandroid restore from someone who used flashrec to make their initial backup. This restore does not touch the recovery image but I was able to boot into my recovery then write the HTC recovery back on top of it. I now have 100% un-rooted phone. I'm not sure how to go about posting a 127MB file, what do you think it the best place?
After restoring the Nandroid backup I tried this:
Code:
Dustan-Bonneys-MacBook:tools dustanbonney$ ./adb shell
$ su
su: permission denied
Then I rebooted to recovery (I used RA 1.5.2)
Code:
Dustan-Bonneys-MacBook:tools dustanbonney$ ./adb remount
remount succeeded
Dustan-Bonneys-MacBook:tools dustanbonney$ ./adb shell
/ # mount -a
mount: mounting /dev/block/mmcblk0p2 on /system/sd failed: No such file or directory
/ # cd /sdcard
/sdcard # flash_image recovery /sdcard/Stock/recovery.img
flashing recovery from /sdcard/Stock/recovery.img
/sdcard # reboot recovery
I was booted to the Triangle and exclamation mark... I pulled the battery and booted up normally.
Stock Kernel - 2.6.27-533ce29d [email protected] )
Stock Build - 1.56.651.2 CL85027 release-keys
Other things that should be mentioned:
If you used RA 1.6.2 - I was unable to get my boot.img or the stock boot.img from the RUU's rom.zip to flash back to the recovery partition. I had to use the RA 1.6.2.img and "flash_image recovery /sdcard/recoverynamegoeshere.img"
It seems that if you've flashed the radio update, the RUU does not write the radio back successfully. Others have had issues going back to the stock radio using the upgrade.zip option as well.
I attempted to use the boot.img, recovery.img, from the RUU's rom.zip with no success. I might try it again. I was able to get to stock recovery (Triangle and exclamation) and to the Hboot menu... but from hboot I had to run the RUU and rebrick the device cause I couldnt get anything at that point, even fastboot oem boot wouldnt load.
There have been times when I get weird issues writing the flash recovery, boot, or misc and when you reboot and load "fastboot oem boot" it wont look like it goes anywhere.... check "adb devices" and your device should be listed. From there do an "adb remount" and then "adb shell" and reflash once more and then "reboot recovery".
If all else fails, I'm available for a small fee.
[email protected]
Anxiously waiting your news. Just encountered this problem today.
Updated ...
imekul said:
Anxiously waiting your news. Just encountered this problem today.
Click to expand...
Click to collapse
Wow! If you've fixed this, I think you're everyone's hero now. We won't have to worry about using the RUU now
I was going to try something similar to this today, but i was unable to brick my phone using the 1.56.651.2 RUU. I was running Flipz updated radio and DamageControl v2.0r2.. The RUU completed successfully..
I was reading over the forum post in http://forum.xda-developers.com/showthread.php?t=645002 and i read that you could boot the system using the command 'fastboot oem boot' I was going to try to use FlashRec to do the work of Flashing the recovery, then booting into recovery and use nandroid.. but you beat me to it! Good work!
I attempted flashing a new recovery image this way with no avail... I also attempted only
Code:
flash_image recovery /sdcard/recovery.img
and still was unable to boot the phone into recovery. I think it had to have been something with doing boot.img and recovery.img at the same time... I dont know what the misc.img does and I'm assuming data.img is userdata... but I did them all and then it worked...
Other users also tried flashrec and with no success... right track though.
chavo2005 said:
I was going to try something similar to this today, but i was unable to brick my phone using the 1.56.651.2 RUU. I was running Flipz updated radio and DamageControl v2.0r2.. The RUU completed successfully..
I was reading over the forum post in http://forum.xda-developers.com/showthread.php?t=645002 and i read that you could boot the system using the command 'fastboot oem boot' I was going to try to use FlashRec to do the work of Flashing the recovery, then booting into recovery and use nandroid.. but you beat me to it! Good work!
Click to expand...
Click to collapse
What do u mean by 3) PC - fastboot oem boot | MAC - oem boot?
blankd3ckskat3r said:
What do u mean by 3) PC - fastboot oem boot | MAC - oem boot?
Click to expand...
Click to collapse
if your using a pc type fastboot oem boot
if your using a mac type ./fastboot oem boot
This!
Thanks Regaw
regaw_leinad said:
if your using a pc type fastboot oem boot
if your using a mac type ./fastboot oem boot
Click to expand...
Click to collapse
Trying this right now.
So far, am getting lots of "mtd: write error" and "mtd: re-read error" Out of memory errors for flashing the recovery image. Guess I'll give this some time, and try to su again and reflash? Or should I kill it as soon as the Out of memory errors pop up and try again?
If you get errors like...
adb shell
su
flash_image recovery .........
(out of memory... etc)
Then...
just su again... so you really su twice
its what I had to do.
imekul said:
Trying this right now.
So far, am getting lots of "mtd: write error" and "mtd: re-read error" Out of memory errors for flashing the recovery image. Guess I'll give this some time, and try to su again and reflash? Or should I kill it as soon as the Out of memory errors pop up and try again?
Click to expand...
Click to collapse
Trying it a second time, and so far am getting a bunch of Out of memory errors. After the first one "finished," I did as you recommended and typed "su" a second time, and then typed the "flash_image recovery /sdcard/recovery.img" command.
So far, looks like it's giving the same errors the second time around.
This second attempt, it ended with "error writing recovery: No space left on device."
Just to be sure, I checked the SD card, and that has over 1 GB of free space.
If you're willing to allow something like logmein.com or some way for me to remote assist you, I would like to try. [email protected] if you're in.
imekul said:
This second attempt, it ended with "error writing recovery: No space left on device."
Just to be sure, I checked the SD card, and that has over 1 GB of free space.
Click to expand...
Click to collapse
Sounds awesome. Thanks. I'll e-mail you now.
Dun Dun Dun... The results are in!
imekul said:
Sounds awesome. Thanks. I'll e-mail you now.
Click to expand...
Click to collapse
dfbonney is the man!!
After a friendly little session on LogMeIn Express, I am good as new! How awesome!!
imekul said:
dfbonney is the man!!
After a friendly little session on LogMeIn Express, I am good as new! How awesome!!
Click to expand...
Click to collapse
We ended up just needing to run
Code:
adb shell
reboot
fastboot oem boot
adb shell
su
//flash commands here
that seemed to do it. so make sure if you're having issues to restart the device and try again!
Edit: Also, we didnt get data.img to work so we only did boot, recovery, and misc.img's
Before I start this thread, I should say that all credit goes to otaking71 for finding this crack.
The two original threads are here
http://forum.xda-developers.com/showthread.php?t=1255043
http://forum.xda-developers.com/showthread.php?t=1255360
All of the work was done in the #htc_evo_shift channel on freenode irc.
Table of contents:
1. Hboot information about the exploit.
2. Downgrading
2.1 Notes
3. Full root(Updated 2.2 root)
4. Links
5. Credits/donation links
I will aim to make it so this mod can be ported to other devices to help downgrade bootloaders and software. Please read the entire thread before flashing anything and trying this.
Hboot
Hboot uses a hidden partition to check everything it flashes against, this partition is "misc", or hboot -1, or on the shift mmcblk0p17(hboot itself is at mmcblk0p18).
Some raw dumps of this partition using strings to filter ascii strings brings out this type of dump.
Locked bootloader for the evo shift's dump
"SPCS_001
DeviceWarmBoot
CE Serial InUse
Debug Cable Ena
CE USB InUse
ClearAutoImage
2.76.651.4
FNOC
FNOC"
Unlocked bootloader for the verizon thunderbolt
"VZW__001
DeviceWarmBoot
CE Serial InUse
Debug Cable Ena
CE USB InUse
ClearAutoImage
1.02.605.6
FNOC
FNOC"
Eng spl unlocked evo shift
"FN0C
FN0C
FN0C"
Now the place to focus at is the version numbers, 2.76.651.4. Hboot will check all items you try to flash via hboot or ruu utility against this number and if it is lower than what you are trying to flash, it will allow you to proceed in flashing through hboot, or ruu. If the number is higher, it will reject the flash. If the number doesn't exist(like in the eng spl) it will assume it is able to flash it(ONLY TESTED ON ENG SPL, not locked bootloaders). So by dumping the TB's misc partition into our own, we made it so the locked hboot would accept flashes. Either by RUU or hboot.
We believe the package you flash still needs to be signed though so that only leaves you with official ruu's and extracted ruu zips.
Joeykrim's history(Located on the second page of this thread)
joeykrim said:
for those curious, a lil bit of history:
same method as used on the evo part 2 thread by toastcfh at xda.
only diff is shift is emmc and evo was mtd. shift emmc partitions are a bit more in number and named differnetly when compared to the evo mtd partitions. on the evo this partition was labeled as "misc" in /proc/partitions. the misc partition being flashed holds the software version number which hboot checks against to verify whether or not it will allow an RUU to be loaded.
also, i want to recall a web site somewhere which allows users to create a custom misc file with a provided version number.
thought this partition was protected by the internal memory write protection but appears it wasn't. not much of a surprise as the first release of the shift didn't have write protection for the hboot partition turned on.
great this works! sadly, they'll prob patch it next OTA around as they did for the evo.
good job on testing (sorry about the lost shift), publishing and releasing! glad to see the shift has unlocked internal memory write protection again!!!
you're path to the internal partition location is incorrect. as the OP states, use:/dev/block/mmcblk0p17
full command: dd if=/sdcard/misc.img of=/dev/block/mmcblk0p17
great article with the history and usage of dd, its a classic unix/linux command. very good to become familiar with: http://en.wikipedia.org/wiki/Dd_(Unix)
Click to expand...
Click to collapse
How to downgrade your device
For the shift, will be different on other devices with a bit of modding.
1. Temproot(With Fre3vo for the shift) http://forum.xda-developers.com/showthread.php?t=1185243
2. Move the file misc.img to the root of your sdcard, and PG06IMG.zip too if you plan on flashing through hboot.
3. Modify the misc partition to bypass the version check, type the following in an adb shell or a terminal emulator on your phone.
Code:
dd if=/sdcard/misc.img of=/dev/block/mmcblk0p17
Note for other devs: misc.img is the image from the TB, could be other images as long as it has a lower version number.
4. This is up to you, you can either use the ruu utility to revert or the PG06IMG.zip in hboot. I'll include links to both. Since both utilities check the misc partition, both are able to flash =)
5. Reboot and then full root like normal on your downgraded device.
Notes
1. When flashing hboot/using this exploit it always flashes twice/stops early and recontinues. Don't worry about it, this is normal(Sometimes it looks like more than 2 but just chill out).
2. Some SDcards are not recognized by hboot, so you will either have to switch cards for this operation or use the ruu utility method.
3. Remove the PG06IMG from your sdcard after flash, or hboot will pick it up next time.
Full root for downgraded 2.2
Flash ENG bootloader
1. Download these files and extract them to the root of your sdcard: www.thebcblends.com/shift/Shift-root.zip
2. Obtain temproot from z4Root, visionary, OR CM's temproot wiki
3. Flash hboot with Engineer SPL:
Code:
dd if=/sdcard/Shift/hboot_eng.nb0 of=/dev/block/mmcblk0p18
4. Boot into bootloader and check for S-OFF
Flashing a recovery
1. Grab latest shift recovery from: http://www.koushikdutta.com/2010/02/clockwork-recovery-image.html
2. Make sure you're temprooted(may have to temp root again)
3. Install recovery from rom manager
Alternative install can be done if you grab another recovery's recovery.img and do one of the following below.
a. Okay this is for those with fastboot - flash the recovery with fastboot: fastboot flash recovery recovery.img
b. This is for those where fastboot doesn't work or they don't have it - 1. Place recovery.img on the root of your sdcard, then type the command below.
Code:
dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p21
Full root/Rom flashing
Well I know you don't have anything you want to save from the 2.2 ruu since it's just a stock flash, so I am going to leave it off here as flash whatever rom you want over the new system via recovery and you should end up with a fully rooted android.
Just remember to wipe data/factory reset after flash.
Links - MD5Sums aren't terribly important here as the files will not flash if they are not correct due to the signatures.
Fre3vo temp root for GB - http://forum.xda-developers.com/showthread.php?t=1185243
misc.img for the misc partition - http://dl.dropbox.com/u/41040697/misc.img MD5Sum: c88dd947eb3b36eec90503a3525ae0de
Misc.img mirror(You guys took down my second dropbox.....trying a different site now): http://www.box.net/shared/0l8ex73zne0tfr10ob69
Second mics.img mirror: http://dl.dropbox.com/u/15373824/misc.img
Another mirror for misc.img: http://dev-host.org/a9dbnuzgb9qv/misc.zip (Thanks Fdxrider)
Official ruu file for downgrading to 2.2 - http://www.multiupload.com/15N2D30H6C MD5SUM: a4b880954d2ac29d5bdf0dade9dede3c
PG06IMG for hboot downgrading to 2.2 - http://dl.dropbox.com/u/41040697/PG06IMG.zip MD5SUM: d20be478fd860b80f5e800c958f79077
Mirror for PG06IMG(First link went down temporarily due to generating too much traffic on my account, good job guys xD) - http://dl.dropbox.com/u/15373824/PG06IMG.zip
Mirror for PG06IMG: http://dev-host.org/xmlaaco0s2ph/PG06IMG.zip
2.2 root [Bcnice guide]- http://forum.xda-developers.com/showthread.php?t=932153
Cm's rooting method(For those without z4root or visionary) - http://wiki.cyanogenmod.com/wiki/HTC_Evo_Shift_4G:_Full_Update_Guide
Credits
Otaking71 - Discoverer of this exploit for the shift and working throughout the night to establish it as a working downgrade.
Bcnice20 & other 2.2 root devs - I borrowed your root methods for this guide, and linked to them. Just had to update it for recovery basically.
Stuke00 - Fre3vo temp root for 2.3.3
Joeykrim - Donating that history for the curious minds.
Donation links:
Otaking71 - Main driver of this discovery/creator and came up with this theory
http://forum.xda-developers.com/donatetome.php?u=1762836
Should we vote this to the front or try to keep it on the downlow?
^ Shift Faced
I'm at work now, but am I to understand that there is now a full root for shifts on gb?
Sent from my PC36100 using XDA App
totalnub911 said:
I'm at work now, but am I to understand that there is now a full root for shifts on gb?
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
Something of that sort, you can obtain full root through this exploit. Though it's through downgrading the firmware you use old 2.2 rooting methods.
totalnub911 said:
I'm at work now, but am I to understand that there is now a full root for shifts on gb?
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
that is correct if you downgrade then root with shiftRR. thats what i'm getting from all this
EDIT: got beat to it
YoungCorruption said:
that is correct if you downgrade then root with shiftRR. thats what i'm getting from all this
EDIT: got beat to it
Click to expand...
Click to collapse
sounds like its time to change your siggy there youngcorruption!
Im sorry for the noobish but what does this mean and how do i do this
2. Modify the misc partition: dd if=/sdcard/misc.img of=/dev/block/mmcblk0p17
misc.img is the image from the TB, could be other images as long as it has a lower version number.
halrulez said:
Im sorry for the noobish but what does this mean and how do i do this
2. Modify the misc partition: dd if=/sdcard/misc.img of=/dev/block/mmcblk0p17
misc.img is the image from the TB, could be other images as long as it has a lower version number.
Click to expand...
Click to collapse
In more specific directions it means to move the downloaded file misc.img to /sdcard , then to type the command "dd if=/sdcard/misc.img of=/dev/block/mmcblk0p17 misc.img" without quotes. The rest just means it'll be different on other devices.
Nice write up, thanks to otaking and scary you all saved the shifters from a horrible ota update
Sent from my Supreme Shift using Tapatalk
Scaryghoul said:
In more specific directions it means to move the downloaded file misc.img to /sdcard , then to type the command "dd if=/sdcard/misc.img of=/dev/block/mmcblk0p17 misc.img" without quotes. The rest just means it'll be different on other devices.
Click to expand...
Click to collapse
ok can do this in terminal from my phone or do i have to do this in adb from my computer?
and if so what are the full steps to get to the point so i can enter this. I am trying to understand adb hell i am just starting in linux so i am hella noob
halrulez said:
ok can do this in terminal from my phone or do i have to do this in adb from my computer?
and if so what are the full steps to get to the point so i can enter this. I am trying to understand adb hell i am just starting in linux so i am hella noob
Click to expand...
Click to collapse
Either one, you can either mount your phone on usb and move the misc.img to your sdcard then type the command in terminal on your phone.
OR
You can adb push the file to your sdcard then adb shell the command.
I'll make the instructions more detailed in a bit.
What do you mean by: Modify the misc partition: dd if=/sdcard/misc.img of=/dev/block/mmcblk0p1?
I moved the misc.img to sdcard but I have no mmcblk0pl in dev/block. Do I have to create that folder? And dd and of....lost me there.
I just did it and it worked perfectly. Back on 2.2, ready to root. Thanks again to otaking and scary for all your hard work.
ok so i was able to do this from the terminal from my android
bow though when i am trying to run the ruu from my computer is starts to go but keeps says that it is waiting for the booloader. the phone wont boot in to the boot loader
halrulez said:
ok so i was able to do this from the terminal from my android
bow though when i am trying to run the ruu from my computer is starts to go but keeps says that it is waiting for the booloader. the phone wont boot in to the boot loader
Click to expand...
Click to collapse
you might need to install htc sync to run ruu's. http://www.htc.com/managed-assets/support/software/htc-sync/setup_3.0.5557.exe
im just going to put this out there as well because i have had problems with the drivers that came with sync and i was forced to use the modified usb drivers found in the unrevoked evo tool, i dunno its weird but my vista pc didnt like anything but them drivers, and another guy i helped ruu from a major mess up, he couldnt get anything with sync to reconize his shift untill he used the same modified evo drivers . i hope no one has an issue but if it come about this is how to fix a driver issue
Best day ever!!!!!!!!!!!!!!!!!!!!!!!!!
strapped365 said:
im just going to put this out there as well because i have had problems with the drivers that came with sync and i was forced to use the modified usb drivers found in the unrevoked evo tool, i dunno its weird but my vista pc didnt like anything but them drivers, and another guy i helped ruu from a major mess up, he couldnt get anything with sync to reconize his shift untill he used the same modified evo drivers . i hope no one has an issue but if it come about this is how to fix a driver issue
Click to expand...
Click to collapse
provide link to said drivers?
riggsandroid said:
provide link to said drivers?
Click to expand...
Click to collapse
kinda cant provide an actual link directly to the drivers because i had to set up unrevoked just like i was rooting an evo, so i just hinted they were in the tool
http://unrevoked.com/recovery/
thats where you can get the tool from to setup your drivers if you have issues with sync not playing well or your pc just dont want to read the drivers right
for those curious, a lil bit of history:
same method as used on the evo part 2 thread by toastcfh at xda.
only diff is shift is emmc and evo was mtd. shift emmc partitions are a bit more in number and named differnetly when compared to the evo mtd partitions. on the evo this partition was labeled as "misc" in /proc/partitions. the misc partition being flashed holds the software version number which hboot checks against to verify whether or not it will allow an RUU to be loaded.
also, i want to recall a web site somewhere which allows users to create a custom misc file with a provided version number.
thought this partition was protected by the internal memory write protection but appears it wasn't. not much of a surprise as the first release of the shift didn't have write protection for the hboot partition turned on.
great this works! sadly, they'll prob patch it next OTA around as they did for the evo.
good job on testing (sorry about the lost shift), publishing and releasing! glad to see the shift has unlocked internal memory write protection again!!!
blakeatl said:
What do you mean by: Modify the misc partition: dd if=/sdcard/misc.img of=/dev/block/mmcblk0p1?
I moved the misc.img to sdcard but I have no mmcblk0pl in dev/block. Do I have to create that folder? And dd and of....lost me there.
Click to expand...
Click to collapse
you're path to the internal partition location is incorrect. as the OP states, use:/dev/block/mmcblk0p17
full command: dd if=/sdcard/misc.img of=/dev/block/mmcblk0p17
great article with the history and usage of dd, its a classic unix/linux command. very good to become familiar with: http://en.wikipedia.org/wiki/Dd_(Unix)
Hi, first of all sorry for my english.
I'm S-off, rooted, using TWRP touch and android 5.0 (from ivanich).
I went out of memory on my internal storage, so I had a pop-up that says lower your storage (my sd card couldn't be mounted). Then i went in recovery to wipe cache and data for it would free some space, but I got theses issue:
mount: failed to mount /dev/block/platform/msm_sdcc.1/by-name/userdata at /data: No such device
unmount of /data failed; no such volume
script succeeded: result was [0,200000]
updating partition details...
E:Unable to mount '/cache'
E:Unable to mount '/data'
...done
I also tried by advanced wipe> wipe Data and I went stuck on this :
"Formatting Data using make_ext4fs function"
If i try to reboot on the rom it's bootloop
I tried a few command in the terminal command that I've found here http://forum.xda-developers.com/showthread.php?t=2683787
mke2fs -T ext4 /dev/block/mmcblk0p8
I get this :
filesystem too small for a journal
writing superblocks and lifesystem accounting information : done
This filesystem will be automatically checked every 37 mounts or 180 days, whichever comes first. Use tune2fs -c or -i to override.
So I have no idea how to fix this I never had this error before and I can't find anything about it, only Odin but correct me if I'm wrong but Odin doesn't work for Sensation ?
Thanks for any help I appreciate
you are facing probably the same issue with others that faced with twrp
those partitions corrupted after using the wipe options
the only thing i can suggest you is to use this solution
http://forum.xda-developers.com/htc-sensation/help/recovering-data-mount-issues-t2859588
best wishes
So yeah, i've try so many things, and none of them is fixing my problem.
First i've installed 4ext recovery and i had still the same issue, not able to wipe cache or data or factory reset.
I've tried to install adb but it doesn't recognize my phone, even with SDK tools, i can't tell the program what my phone is.
now i've tried to install the RUU (dl the .exe, found the rom.zip, and put on my phone renamed it "PG58IMG.zip" now when i'm on the fastboot it loads the file and then it get stuck at the userdata part....
If i try to boot the normal way i get the black screen with the red triangle and exclamation mark ....
I'm going to keep looking but it's getting harder than expected
(still sorry for my english)
ni4rkx said:
So yeah, i've try so many things, and none of them is fixing my problem.
First i've installed 4ext recovery and i had still the same issue, not able to wipe cache or data or factory reset.
I've tried to install adb but it doesn't recognize my phone, even with SDK tools, i can't tell the program what my phone is.
now i've tried to install the RUU (dl the .exe, found the rom.zip, and put on my phone renamed it "PG58IMG.zip" now when i'm on the fastboot it loads the file and then it get stuck at the userdata part....
If i try to boot the normal way i get the black screen with the red triangle and exclamation mark ....
I'm going to keep looking but it's getting harder than expected
(still sorry for my english)
Click to expand...
Click to collapse
I can't help with issue but userdata is not mmcblk0p8, it's mmcblk0p23 on our device.
hinxnz said:
I can't help with issue but userdata is not mmcblk0p8, it's mmcblk0p23 on our device.
Click to expand...
Click to collapse
Hmm thanks for this info, I will try to do again all this but on an other computer tomorrow maybe it will work... I hope!
So after hours of trying to repair it, it still doesn't work.
But i've found something that might be intersting.
In recovery 4ext but now I'm twrp so I don't have the exact information again but when I went in storage information, it was written that the internal storage was --mb, and --mb free, so I guess it means that my partition doesn't exist anymore.. Anyway I've found that I'm not the only one with this but I still didn't find any solution to fix it..
ni4rkx said:
Hi, first of all sorry for my english.
I'm S-off, rooted, using TWRP touch and android 5.0 (from ivanich).
I went out of memory on my internal storage, so I had a pop-up that says lower your storage (my sd card couldn't be mounted). Then i went in recovery to wipe cache and data for it would free some space, but I got theses issue:
mount: failed to mount /dev/block/platform/msm_sdcc.1/by-name/userdata at /data: No such device
unmount of /data failed; no such volume
script succeeded: result was [0,200000]
updating partition details...
E:Unable to mount '/cache'
E:Unable to mount '/data'
...done
I also tried by advanced wipe> wipe Data and I went stuck on this :
"Formatting Data using make_ext4fs function"
If i try to reboot on the rom it's bootloop
I tried a few command in the terminal command that I've found here http://forum.xda-developers.com/showthread.php?t=2683787
mke2fs -T ext4 /dev/block/mmcblk0p8
I get this :
filesystem too small for a journal
writing superblocks and lifesystem accounting information : done
This filesystem will be automatically checked every 37 mounts or 180 days, whichever comes first. Use tune2fs -c or -i to override.
So I have no idea how to fix this I never had this error before and I can't find anything about it, only Odin but correct me if I'm wrong but Odin doesn't work for Sensation ?
Thanks for any help I appreciate
Click to expand...
Click to collapse
I decided to try TWRP yesterday and Im having a similar issue. However when i flash roms I have no issues at all. However i get stuck at the HTC logo forever when i try and boot. I have manually flashed boot.img so that isnt the issue. I even tried doing some mkfs.ext4 executions and i still have the same issue. Im going back to my E63 to see if i can still repair this. However looks like another device is looking likely.
Can anyone tell me if you can run some error logs for when the device is in the boot stage, and by that i mean when the HTC logo so showing? I dont think ADB will work in that mode.
When you try to mount data from recovery does it fail?
Can you tell me which twrp your using? I mean which r stands at the end of the filename?
little_lerroyy said:
I decided to try TWRP yesterday and Im having a similar issue. However when i flash roms I have no issues at all. However i get stuck at the HTC logo forever when i try and boot. I have manually flashed boot.img so that isnt the issue. I even tried doing some mkfs.ext4 executions and i still have the same issue. Im going back to my E63 to see if i can still repair this. However looks like another device is looking likely.
Can anyone tell me if you can run some error logs for when the device is in the boot stage, and by that i mean when the HTC logo so showing? I dont think ADB will work in that mode.
Click to expand...
Click to collapse
What do you mean "some mkfs.ext4 executions" ? I wanted to try that but I couldn't find how to do it, I tried in ADB it didn't work & terminal from twrp neither maybe I didn't type correctly.
I'll suggest you to re flash it, or wipe & flash. (but it's not the point of my thread tho ...)
Sajito said:
When you try to mount data from recovery does it fail?
Can you tell me which twrp your using? I mean which r stands at the end of the filename?
Click to expand...
Click to collapse
Yes I can't mount it..
openrecovery-twrp-2.8.4.0-pyramid.img that i've flash by ADB
ni4rkx said:
What do you mean "some mkfs.ext4 executions" ? I wanted to try that but I couldn't find how to do it, I tried in ADB it didn't work & terminal from twrp neither maybe I didn't type correctly.
I'll suggest you to re flash it, or wipe & flash. (but it's not the point of my thread tho ...)
Yes I can't mount it..
openrecovery-twrp-2.8.4.0-pyramid.img that i've flash by ADB
Click to expand...
Click to collapse
Where did you download that image?
That sounds like you just experienced the brick bug.
Sajito said:
Where did you download that image?
That sounds like you just experienced the brick bug.
Click to expand...
Click to collapse
http://techerrata.com/browse/twrp2/pyramid from http://teamw.in/project/twrp2/66 the recovery img method.
Well I'm not sure because It booted the rom (cm12 from ivanich) but yeah bootloop on the CM logo
ni4rkx said:
http://techerrata.com/browse/twrp2/pyramid from http://teamw.in/project/twrp2/66 the recovery img method.
Well I'm not sure because It booted the rom (cm12 from ivanich) but yeah bootloop on the CM logo
Click to expand...
Click to collapse
I'm sorry to say, but that's definitely the brick bug. Only the link rzr86 posted might help you using your phone. Ivanich made twrp builds, which use his kernel and device trees, so we're pretty sure his twrp is not affected by that bug (that just as an info for anyone using the twrp from the official site. So if anyone reads this and is using twrp newer than 2.6 from official site, get ivanich's build).
The problem is that your data partition is corrupt, not the system partition. But you need the data partition, to use any rom, which is now not mountable anymore. So your able to flash roms and get until bootanimation, but without data partition working it won't boot.
@little_lerroyy did you use ivanich's twrp or the one from official site too?
Sajito said:
I'm sorry to say, but that's definitely the brick bug. Only the link rzr86 posted might help you using your phone. Ivanich made twrp builds, which use his kernel and device trees, so we're pretty sure his twrp is not affected by that bug (that just as an info for anyone using the twrp from the official site. So if anyone reads this and is using twrp newer than 2.6 from official site, get ivanich's build).
The problem is that your data partition is corrupt, not the system partition. But you need the data partition, to use any rom, which is now not mountable anymore. So your able to flash roms and get until bootanimation, but without data partition working it won't boot.
@little_lerroyy did you use ivanich's twrp or the one from official site too?
Click to expand...
Click to collapse
So you're saying that TWRP didn't do their job good enough and bricked my phone ? =/ that's pretty sad
thanks for the info tho but maybe there is a way to re create the data partition, since I think I'm not the only one who has this issue
ni4rkx said:
So you're saying that TWRP didn't do their job good enough and bricked my phone ? =/ that's pretty sad
thanks for the info tho but maybe there is a way to re create the data partition, since I think I'm not the only one who has this issue
Click to expand...
Click to collapse
The problem is not caused by twrp, but the faulty device/kernel trees which were used for that image. Unfortunately nobody knows who built these images, nor do we know which sources were used.
I had that too, I know that sucks.
Sajito said:
The problem is not caused by twrp, but the faulty device/kernel trees which were used for that image. Unfortunately nobody knows who built these images, nor do we know which sources were used.
I had that too, I know that sucks.
Click to expand...
Click to collapse
Alright then.... I have an old motorola defy yeahhhh :good:
ni4rkx said:
Alright then.... I have an old motorola defy yeahhhh :good:
Click to expand...
Click to collapse
You can still try to mount your sdcard as data partition, as explained in the link posted on page 1, it seems to work for some.
ni4rkx said:
What do you mean "some mkfs.ext4 executions" ? I wanted to try that but I couldn't find how to do it, I tried in ADB it didn't work & terminal from twrp neither maybe I didn't type correctly.
I'll suggest you to re flash it, or wipe & flash. (but it's not the point of my thread tho ...)
Yes I can't mount it..
openrecovery-twrp-2.8.4.0-pyramid.img that i've flash by ADB
Click to expand...
Click to collapse
Connect phone to pc, boot into recovery, open terminal and type 'adb devices', your device should show.
To try mount data enter 'adb shell mount /data'.
To check structure enter 'adb shell /sbin/e2fsck -n -f /dev/block/mmcblk0p23'.
Maybe this could help?
Sajito said:
You can still try to mount your sdcard as data partition, as explained in the link posted on page 1, it seems to work for some.
Click to expand...
Click to collapse
Hm I've take a look but it looks complicated :s
hinxnz said:
Connect phone to pc, boot into recovery, open terminal and type 'adb devices', your device should show.
To try mount data enter 'adb shell mount /data'.
To check structure enter 'adb shell /sbin/e2fsck -n -f /dev/block/mmcblk0p23'.
Maybe this could help?
Click to expand...
Click to collapse
Well I'll give it a try when I can work on an other computer because I also have an issue with windows 8.1, it doesn't recognize my phone, so I can't use adb to work with the phone. It worked on windows 7 on an other computer but I can't use it for now.. Thanks anyway I'll keep you in touch
ni4rkx said:
What do you mean "some mkfs.ext4 executions" ? I wanted to try that but I couldn't find how to do it, I tried in ADB it didn't work & terminal from twrp neither maybe I didn't type correctly.
I'll suggest you to re flash it, or wipe & flash. (but it's not the point of my thread tho ...)
Yes I can't mount it..
openrecovery-twrp-2.8.4.0-pyramid.img that i've flash by ADB
Click to expand...
Click to collapse
Follow this link, the process is done in ADB
http://android-revolution-hd.blogspot.com.au/2013/10/fix-data-htc-one.html
Just make sure where it says "mmcblk0p37" in step number 10, you put in "mmcblk0p23" which is your data partition, but i doubt you will have much access doing this.
little_lerroyy said:
Follow this link, the process is done in ADB
http://android-revolution-hd.blogspot.com.au/2013/10/fix-data-htc-one.html
Just make sure where it says "mmcblk0p37" in step number 10, you put in "mmcblk0p23" which is your data partition, but i doubt you will have much access doing this.
Click to expand...
Click to collapse
Thanks but as I said, I can't use ADB on my computer. I'll still try when I can use an other one !
Another ArchiKitchen project. But first...
Code:
#include
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and
* YOU acknowledge you are doing so at your own risk.
*/
Given that, this ROM, is PURE STOCK, with root (if you choose that option). This is here to save your butt because you de-bloated some apps, or otherwise bricked your tab and forgot to make a nandroid first. This will bring you back to the latest version (3.1.0.42).
Please NOTE: This ROM is only designed for the WW SKU only! If you have a different SKU, and are that desperate, find another way first!
Because this is untouched stock, everything should work. Please recognize I have not tested this myself, as I have not found the need to use it (and the alternatives - that is, the ways to get out of it if it fails - are limited). So, if anyone finds their way to have to use this, please continue to note any success or failure, and any considerations in the comments - be it this thread, or the Q&A thread.
DOWNLOAD:
I am offering two versions these days (the old two had an updater-binary incompatible for the CWM provided) - a slightly modified version (built by the "bb" command in ArchiKitchen, accepting all the prompts - so permissions and symlinks are redone), and the other with the same but with root and SuperSU tacked on in the updater-script. If you are wondering which version to use, the former has been tested (at least once), but the latter is more straightforward.
K00L_Back_To_Stock_Updater-Binary.zip (MD5: 47ed2e94221c1d70bee17f39fd62bdff)
K00L_Back_To_Stock_With-SuperSU.zip (MD5: e78b6a4022a4f707e4d54f9440761be4)
INSTRUCTIONS:
Download ROM above
Download SuperSU update zip (optional, if you want root and using the first zip)
Connect your tab to the PC with appropriate adb, fastboot, and drivers available
If your device is bricked, enter fastboot and unlock bootloader with these instructions (or skip this part for post #3 instructions instead)
Download CWM to your PC (since the aforementioned link is down, post #62 has a source, and now I do as well)
Having completed that, reboot into fastboot and issue the following commands (or use the method in post #3):
Code:
fastboot flash recovery recovery_cwm.img
fastboot flash misc misc_reboot-recovery.img
fastboot reboot
Your tab will reboot into CWM
Push file(s) to your SD card ("adb push K00L_Back_To_Stock.zip /sdcard/" )
Nandroid/Back up broken device (optional, but highly recommended)
Wipe cache and data/factory reset (especially if you used XPosed - you can try dirty flashing, but from what I hear the data partition gets bunged after flashing anyway - thinks it is encrypted - so you are better off with the previous step and then salvaging from there)
Install ROM
Wipe Dalvik cache
Reboot
Enjoy!
RESOURCES:
CWM-based recovery
MeMO Pad 8 General Discussion
CREDITS:
Androtab.info
Chainfire for SuperSU
JustArchi for ArchiKitchen
Did I miss anything? I appreciate the feedback, and any thanks as well!
Alternate Flash / Other Info...
DD-BASED FLASH:
Thanks go to @t-mobile_mda for this method.
Since I have encountered others unable to flash the ROM zip in their CWM, I am providing a precursor that is more forgiving, but harder to accomplish, and as it is more forgiving, it is up to the end user to ... know what you are doing. So to recap...this ROM is for:
ASUS MeMO Pad 8 (ME180A)
Code named K00L
WW region only
With that out the way, you will need (besides the above device):
boot and system images
rebooted into CWM (see methods in posts above and/or below this post), and backup made
When ready, run the following commands:
Code:
adb devices
adb push boot.img /external_sd/
adb push system.img /external_sd/
adb shell
su
mount -o rw,remount /system
dd if=/external_sd/boot.img of=/dev/block/platform/emmc/by-name/boot
dd if=/external_sd/system.img of=/dev/block/platform/emmc/by-name/system
If CWM does not understand the logical mounts:
Code:
adb devices
adb push boot.img /external_sd/
adb push system.img /external_sd/
adb shell
su
mount -o rw,remount /system
dd if=/external_sd/boot.img of=/dev/block/mmcblk0p3
dd if=/external_sd/system.img of=/dev/block/mmcblk0p6
With all that successful, then factory reset and reboot.
RECOVERY FSTAB:
For anyone who wishes to make their own ROM...small piece of the puzzle
Code:
# Android fstab file.
#<src> <mnt_point> <type> <mnt_flags and options> <fs_mgr_flags>
# The filesystem that contains the filesystem checker binary (typically /system) cannot
# specify MF_CHECK, and must come before any filesystems that do specify MF_CHECK
/dev/block/platform/emmc/by-name/system /system ext4 noatime,nodiratime,noauto_da_alloc,discard wait
/dev/block/platform/emmc/by-name/userdata /data ext4 noatime,nodiratime,nosuid,nodev,noauto_da_alloc,discard wait,encryptable=/dev/block/platform/emmc/by-name/hidden
/dev/block/platform/emmc/by-name/cache /cache ext4 noatime,nodiratime,nosuid,nodev,noauto_da_alloc,discard wait
/dev/block/platform/emmc/by-name/parameter /parameter emmc defaults defaults
/dev/block/platform/emmc/by-name/misc /misc emmc defaults defaults
/dev/block/platform/emmc/by-name/kernel /kernel emmc defaults defaults
/dev/block/platform/emmc/by-name/boot /boot emmc defaults defaults
/dev/block/platform/emmc/by-name/recovery /recovery emmc defaults defaults
/dev/block/platform/emmc/by-name/backup /backup emmc defaults defaults
/dev/block/platform/emmc/by-name/adf /adf emmc defaults defaults
/dev/block/platform/emmc/by-name/apd /apd emmc defaults defaults
/dev/block/platform/emmc/by-name/hidden /hidden emmc defaults defaults
/dev/null /sdcard datamedia defaults defaults
/dev/block/mmcblk1p1 /external_sd auto defaults defaults
#/devices/platform/rk29_sdmmc.0/mmc_host/mmc /external_sd auto defaults voldmanaged=sdcard1:auto
#/devices/platform/usb20_otg/usb auto auto defaults voldmanaged=usbdisk:auto
Alternate way to install CWM
Thanks go to @mm2dd...
You may find that any attempt to unlock the bootloader to install CWM will ultimately fail. This provides another way.
First you need a Debian, Ubuntu, or derivative - essentially a GNU/Linux OS that handles .deb packages. This can be achieved with a VMWare or VirtualBox virtual machine, if you don't have (or want) a dual-boot setup.
Follow the steps to download, install, and run the RkFlashKit package:
http://www.hotmcu.com/wiki/Flashing...Using_The_Rockchip_Tool#Installing_RkFlashKit
Make sure the tab is plugged into the PC (and having the appropriate Windows drivers if using a VM) and the tab is in Rockchip bootloader mode before running RkFlashKit.
With the CWM Recovery files saved to the Linux Box (be it computer or virtual machine), make sure "Devices" is no longer blank (if it is, a step above got skipped), and set "NAND Partitions" to "Recovery".
You may want to "Backup Partition" before continuing.
Under "Image file to flash", choose the recovery_cwm.img file.
When ready, press "Flash Image"
Repeat for misc_reboot-recovery.img to the misc partition, and when done, select "Reboot Device", while holding the magic keys to get into recovery.
@OfficerJimLahey
This thread saved my ME180A Thank you so much and also androtab too...so sad there is no custom roms for this model and im noob to make my own Rom...anyways thanks again.
Hi there,
This thread could save my tablet from a loooong time mistake..
but.. when i arrive to the part of installng cwm, small issue, in fastboot..
Everything is good, drivers and adb installed, the tab appears when i give the command adb devices, but when in fastboot (well.. think it is.. the screen stays black..) , once i give the next command it stays at ''waiting for device'' .. and i cant see the device anymore when typing adb devices..
.. what can be the issue?
puss2puss said:
Hi there,
This thread could save my tablet from a loooong time mistake..
but.. when i arrive to the part of installng cwm, small issue, in fastboot..
Everything is good, drivers and adb installed, the tab appears when i give the command adb devices, but when in fastboot (well.. think it is.. the screen stays black..) , once i give the next command it stays at ''waiting for device'' .. and i cant see the device anymore when typing adb devices..
.. what can be the issue?
Click to expand...
Click to collapse
When in fastboot mode, use fastboot command instead.
OfficerJimLahey said:
When in fastboot mode, use fastboot command instead.
Click to expand...
Click to collapse
Thanks for the reply
Well actually, i do use fastboot commande once in fastboot mode.. but it was not detected but i noticed that when in fastboot, it use a different driver so when booting in fastboot, i replaced manually the driver kool for one that contain the words bootloader and it now detect it, but when writing the command ''fastboot devices'' it gives 123456789 ... but now i can give the commands from fastboot to reboot etc..
BUT.. ..when i type :
fastboot flash recovery recovery_cwm.img
fastboot flash misc misc_reboot-recovery.img
fastboot reboot
.. it says something like failed, device is locked..
puss2puss said:
Thanks for the reply
Well actually, i do use fastboot commande once in fastboot mode.. but it was not detected but i noticed that when in fastboot, it use a different driver so when booting in fastboot, i replaced manually the driver kool for one that contain the words bootloader and it now detect it, but when writing the command ''fastboot devices'' it gives 123456789 ... but now i can give the commands from fastboot to reboot etc..
BUT.. ..when i type :
fastboot flash recovery recovery_cwm.img
fastboot flash misc misc_reboot-recovery.img
fastboot reboot
.. it says something like failed, device is locked..
Click to expand...
Click to collapse
Yup, the bootloader will be locked. Post one is one way to go about it (bullet point four), post two is the other way.
OfficerJimLahey said:
Yup, the bootloader will be locked. Post one is one way to go about it (bullet point four), post two is the other way.
Click to expand...
Click to collapse
I know, if i.m asking for help, its because it fails on my side
after commands, it gives:
Writing 'recovery' ...
FAILED (remote: device is locked)
And if i try the commands ''fastboot oem unlock61646
fastboot oem unlockD696E'' , it gives:
FAILED (remote: oem admunlock not requested)
..what am i missing..
puss2puss said:
And if i try the commands ''fastboot oem unlock61646
fastboot oem unlockD696E'' , it gives:
FAILED (remote: oem admunlock not requested)
..what am i missing..
Click to expand...
Click to collapse
Yeah, that fails for whatever reason for some. If I gambled any amount I would say different device batches. The workaround would be post two. The advantage with that one is that you don't need to unlock the bootloader for CWM this way, at the downside of it's a bit more work (especially if you don't have access to a GNU/Linux PC or even a PC with a GNU/Linux live CD).
I never did this method (never had to) so unfortunately, my capability for help with this part is very limited.
.. in post 2 you explain how to make a rom.. not sure it will help me.. ah well.. thanks anyway and keep up the good work.
puss2puss said:
.. in post 2 you explain how to make a rom.. not sure it will help me.. ah well.. thanks anyway and keep up the good work.
Click to expand...
Click to collapse
Sorry, meant post three, titled "Alternate way to install CWM".
Well ubuntu did the trick i loaded latest ubuntu yesterday and boom everything went as expected i am now installing the stock rom! The story of this tablet is finally getting an happy ending lol..
When i bought the tablet long ago, i rooted it and deleted some apps and then i was never able to update it, but was using it everyday, utill the day it magicly fell on the ground.. glass broke.. tears crawld my cheeks.. then bought win8.1 tablet.
.. but a couple of weeks ago i ordered a glass and digitizer from aliexpress for 16$, repaired it, and now updating it from a fresh stock rom
Thanks for your great work here, keep it up mate!
Small question: do you (or anyone else) knows if kitkat is available somewhere for it? I read that its suppose to run kitkat but i cant find any direct info..
And when i click to update it doesnt find anything..
Not a big deal, but would be great
puss2puss said:
Small question: do you (or anyone else) knows if kitkat is available somewhere for it? I read that its suppose to run kitkat but i cant find any direct info..
And when i click to update it doesnt find anything..
Not a big deal, but would be great
Click to expand...
Click to collapse
I have heard something in passing recently somewhere along those lines. I don't think anything amounts to that or maybe someone was mistaken between the MeMO Pad models (ME181C has Kitkat).
Given this is a device released in 2013, ASUS would have long given up on it.
Yah thats what i think to..
And the more i read, the more i realize its the other models, its now clear.
Last year i was working on a rom but ţe progress stopped when the tab took a 'brake' .. ..so, now i wanna get back to it.
Where to start if i wanted to include an updated android into the rom?
puss2puss said:
Yah thats what i think to..
And the more i read, the more i realize its the other models, its now clear.
Last year i was working on a rom but ţe progress stopped when the tab took a 'brake' .. ..so, now i wanna get back to it.
Where to start if i wanted to include an updated android into the rom?
Click to expand...
Click to collapse
I know a little about that. You will need a device tree. Problem is, I don't think one is available.
Sent from my ASUS_Z00AD
Hi there!
I'm trying to install a new ROM on my MemoPad 8 (K01H), but I keep getting errors
When I type
Code:
fastboot flash recovery recovery_cwm.img
I get an error which says I have to unlock first. Even if this tutorial says I don't need to unlock it for CWM, I tried, but I get another error saying: "remote: unknown oem command".
I have 5.0.1 on my tab, I checked in the developer menu, and I don't have enable OEM unlock option at all o.o
I tried every possibilities I found and nothing worked. My tab is rooted. What I did wrong?
Yaime said:
Hi there!
I'm trying to install a new ROM on my MemoPad 8 (K01H), but I keep getting errors
When I type
Code:
fastboot flash recovery recovery_cwm.img
I get an error which says I have to unlock first. Even if this tutorial says I don't need to unlock it for CWM, I tried, but I get another error saying: "remote: unknown oem command".
I have 5.0.1 on my tab, I checked in the developer menu, and I don't have enable OEM unlock option at all o.o
I tried every possibilities I found and nothing worked. My tab is rooted. What I did wrong?
Click to expand...
Click to collapse
Wrong model. Please see first post on what this is for. Please don't continue to try to flash this ROM, or that CWM to your device. You will end up in a worse hole.
OfficerJimLahey said:
Another ArchiKitchen project. But first...
Code:
#include
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and
* YOU acknowledge you are doing so at your own risk.
*/
Given that, this ROM, is PURE STOCK, with root (if you choose that option). This is here to save your butt because you de-bloated some apps, or otherwise bricked your tab and forgot to make a nandroid first. This will bring you back to the latest version (3.1.0.42).
Please NOTE: This ROM is only designed for the WW SKU only! If you have a different SKU, and are that desperate, find another way first!
Because this is untouched stock, everything should work. Please recognize I have not tested this myself, as I have not found the need to use it (and the alternatives - that is, the ways to get out of it if it fails - are limited). So, if anyone finds their way to have to use this, please continue to note any success or failure, and any considerations in the comments - be it this thread, or the Q&A thread.
DOWNLOAD:
I am offering two versions these days (the old two had an updater-binary incompatible for the CWM provided) - a slightly modified version (built by the "bb" command in ArchiKitchen, accepting all the prompts - so permissions and symlinks are redone), and the other with the same but with root and SuperSU tacked on in the updater-script. If you are wondering which version to use, the former has been tested (at least once), but the latter is more straightforward.
K00L_Back_To_Stock_Updater-Binary.zip (MD5: 47ed2e94221c1d70bee17f39fd62bdff)
K00L_Back_To_Stock_With-SuperSU.zip (MD5: e78b6a4022a4f707e4d54f9440761be4)
INSTRUCTIONS:
Download ROM above
Download SuperSU update zip (optional, if you want root and using the first zip)
Connect your tab to the PC with appropriate adb, fastboot, and drivers available
If your device is bricked, enter fastboot and unlock bootloader with these instructions (or skip this part for post #3 instructions instead)
Download CWM to your PC
Having completed that, reboot into fastboot and issue the following commands (or use the method in post #3):
Code:
fastboot flash recovery recovery_cwm.img
fastboot flash misc misc_reboot-recovery.img
fastboot reboot
Your tab will reboot into CWM
Push file(s) to your SD card ("adb push K00L_Back_To_Stock.zip /sdcard/" )
Nandroid/Back up broken device (optional, but highly recommended)
Wipe cache and data/factory reset (especially if you used XPosed - you can try dirty flashing, but from what I hear the data partition gets bunged after flashing anyway - thinks it is encrypted - so you are better off with the previous step and then salvaging from there)
Install ROM
Wipe Dalvik cache
Reboot
Enjoy!
RESOURCES:
CWM-based recovery
MeMO Pad 8 General Discussion
CREDITS:
Androtab.info
Chainfire for SuperSU
JustArchi for ArchiKitchen
Did I miss anything? I appreciate the feedback, and any thanks as well!
Click to expand...
Click to collapse
hi..
i am getting error while installing ROMs.. can u pls check it.?
Hi. This is my first post and I hope I didn't have to post in some other section just for present myself, since I'm doing it now.
Anyway, I tried to flash a new rom since my HTC Sensation (no 4g nor XE) was totally stucked. I even installed the minimum software that I needed, and the result was a phone that could barely make calls.
So I did a backup of all my datas, then proceeded to a factory reset.
After that I followed the procedure on the htcdev website to unlock the bootloader and everything went smooth.
The first problem happened when, following a video explanation of a french guy that didn't say that I needed a wire, I had to improvise with what I could find at a late time in the night, and it was some iron wire insulated with some paper. At first the phone reeboted but not like I needed, and the following tries were totally useless so I used that software called rumrunner that claims to do be able to turn S-OFF without the wire trick.
I don't really know if it worked or not: I have S-OFF but during the process in the cmd there was "WTF: what are you doing" and "process stopped" even if I didn't touch anything.
Anyway, let's assume that I have S-OFF:
I then tried to flash the recovery 4-EXT using a software called like "Sensation_All-In-One_Kit_v3.1". I didn't noticed any significant change, nor the other functions were working properly since everything said "phone not found". So I used cmd and flashed "recovery-clockwork-touch-5.8.0.9-pyramid" and it worked flawlessy.
Then I rooted the phone using the recovery and installing from the sdcard the file "su-2.3.6.3-efgh-signed".
Then I downloaded cm12.1 by ivanich and installed it, but I forgot to do a backup before that and when I turned on the phone, nothing was loading. It was a black screen with the superior bar. The touch was not working, the on/off button the same. So I reopened the recovery, wiped out the data and cache to factory reset, and did again the SU and custom SO install.
Now the phone boots but it's again the factory reset version, not the one that I installed. I see that from all the bloatware still there. Also, its version is wrong. It's android 4.0.3, while there wasn't that version when it was produced.
I need help.
edit: I found out that when I try to install the rom I get only errors saying :
[the first part is missing since I can't scroll up]
mount: failed to mount /dev/block/platform/msm_sdcc.1/by-name/system at /system: no such file or directory
unmount of /system failed; no such volume
mount: failed to mount /dev/block/platform/msm_sdcc.1/by-name/userdata at /data: no such device
unmount of /data failed; no such volume
patching system image unconditionally...
mount: failed to mount /dev/block/platform/msm_sdcc.1/by-name/system at /system: no such file or directory
unmount of /system failed; no such volume
script succeded: result was [0.200000]
Install from sdcard complete.
FINAL EDIT:
I searched in many places for help. I found the man in a IRC chat. Seems that I had to change the recovery app and install twrp. Then it worked flawlessy.
Ciome said:
Hi. This is my first post and I hope I didn't have to post in some other section just for present myself, since I'm doing it now.
Anyway, I tried to flash a new rom since my HTC Sensation (no 4g nor XE) was totally stucked. I even installed the minimum software that I needed, and the result was a phone that could barely make calls.
So I did a backup of all my datas, then proceeded to a factory reset.
After that I followed the procedure on the htcdev website to unlock the bootloader and everything went smooth.
The first problem happened when, following a video explanation of a french guy that didn't say that I needed a wire, I had to improvise with what I could find at a late time in the night, and it was some iron wire insulated with some paper. At first the phone reeboted but not like I needed, and the following tries were totally useless so I used that software called rumrunner that claims to do be able to turn S-OFF without the wire trick.
I don't really know if it worked or not: I have S-OFF but during the process in the cmd there was "WTF: what are you doing" and "process stopped" even if I didn't touch anything.
Anyway, let's assume that I have S-OFF:
I then tried to flash the recovery 4-EXT using a software called like "Sensation_All-In-One_Kit_v3.1". I didn't noticed any significant change, nor the other functions were working properly since everything said "phone not found". So I used cmd and flashed "recovery-clockwork-touch-5.8.0.9-pyramid" and it worked flawlessy.
Then I rooted the phone using the recovery and installing from the sdcard the file "su-2.3.6.3-efgh-signed".
Then I downloaded cm12.1 by ivanich and installed it, but I forgot to do a backup before that and when I turned on the phone, nothing was loading. It was a black screen with the superior bar. The touch was not working, the on/off button the same. So I reopened the recovery, wiped out the data and cache to factory reset, and did again the SU and custom SO install.
Now the phone boots but it's again the factory reset version, not the one that I installed. I see that from all the bloatware still there. Also, its version is wrong. It's android 4.0.3, while there wasn't that version when it was produced.
I need help.
edit: I found out that when I try to install the rom I get only errors saying :
[the first part is missing since I can't scroll up]
mount: failed to mount /dev/block/platform/msm_sdcc.1/by-name/system at /system: no such file or directory
unmount of /system failed; no such volume
mount: failed to mount /dev/block/platform/msm_sdcc.1/by-name/userdata at /data: no such device
unmount of /data failed; no such volume
patching system image unconditionally...
mount: failed to mount /dev/block/platform/msm_sdcc.1/by-name/system at /system: no such file or directory
unmount of /system failed; no such volume
script succeded: result was [0.200000]
Install from sdcard complete.
FINAL EDIT:
I searched in many places for help. I found the man in a IRC chat. Seems that I had to change the recovery app and install twrp. Then it worked flawlessy.
Click to expand...
Click to collapse
you just had a very old version of recovery
i assume that guy gave you the proper twrp because there is a false one which messes up with emmc after using wipe option
rzr86 said:
you just had a very old version of recovery
i assume that guy gave you the proper twrp because there is a false one which messes up with emmc after using wipe option
Click to expand...
Click to collapse
No he just told me to get the last version for my phone.
Ciome said:
No he just told me to get the last version for my phone.
Click to expand...
Click to collapse
actually i am saying the same thing