Database Info

110 Error RUU 1.56 Fix - 100% unroot too!

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

[CWM Touch][TWRP] Root + Recovery for Tilapia

Shinj1EVA reported that koush's web builder is now producing boo table CWM Touch images. I have built one and added it to the download page. I have not updated the regular CWM to 6.0.2.3 since there are no commits that affect how it works since I last built 6.0.2.1
12/20- All recoveries are functionally up to date as of this day.
I have seen most of the guides recommend flashing the 'grouper' recovery image. Don't do this. This is why your OTAs and update.zips are failing with 'Status 7'. Those zips have an assert check that ensures you are flashing your zips to the correct device. This is failing if you have a recovery image that was made for a different device.
Those assert checks are there for your protection and you should not get in the practice of working around them. Using grouper recovery.imgs is ill-advised and conceivably dangerous. The two devices differ in more respects than a simple assert check, including having different recovery.fstab files, which are used to make and configure recovery.
I have ported TWRP and compiled a CWM-based (Touch and non-touch) recovery image, made from CM10.1 tilapia source. You will need fastboot, at minimum, to write this recovery. To root, you will need the CWM-flashable zip of SuperSU by chainfire..
Instructions
Boot into the bootloader (2 choices)
Turn the device on while pressing volume down; or
Code:
adb reboot bootloader
Unlock your bootloader
THIS WILL WIPE ALL OF YOUR DATA! No way around it...
Code:
fastboot oem unlock
With your Nexus 7 3G in the bootloader and connected to your computer through the usb cable:
replace recovery-CWM-tilapia-regular with the name of the recovery image you chose to download.
Code:
fastboot flash recovery recovery-CWM-tilapia-regular.img
To make CWM your permanent recovery: (this can, despite the warnings, be undone. Do it.)
Boot into recovery mode by pressing 'vol up' and when the menu says 'recovery mode' press the power button.
Mount system in the 'mounts' menu
Code:
adb shell
mv system/recovery-from-boot.p system/recovery-from-boot.bak
exit
To Root (With /system still mounted):
Code:
adb push CWM-SuperSU-v0.98.zip /sdcard/
Flash the SuperSU zip in recovery ('Install' menu with TWRP or 'choose zip from sdcard' in CWM)
Reboot System
Congratulations, you now have the proper tilapia custom recovery and can flash roms and OTAs. Anytime you get a 'status 7' from now on, you know that rom was not made for your device. CWM will have instructions that gives you the option of preserving custom recovery and maintaining root.
If you just want to boot into custom recovery instead of overwriting the stock or grouper recovery(playing fast and loose- keeping grouper recovery on-device for grouper roms, at least until devs add tilapia asserts to their updater-scripts), use
Code:
fastboot boot recovery recovery-CWM-tilapia-regular.img
If you want to keep tilapia recovery but have a grouper rom you want to try, you will have to change the updater-script of that rom. It takes two seconds. Look at the third post for instructions.
Downloads
Recovery (just pick one)
CWM Recovery (Touch/Non-Touch) (6.0.2.1)
TWRP 2.3.2.1
Root (Get the CWM flashable zip)
SuperSU
ClockworkMod is the work of the estimable koush and TWRP is from the good men of Team Win.

a mirror please?

How to use grouper roms w/tilapia recovery
Use an archive manager like 7zip and open your rom without unzipping.
Open META-INF/com/google/android/updater-script
Look for the line (usually the first) that says something like this:
Code:
assert(getprop("ro.product.device") == "grouper" || getprop("ro.build.product") == "grouper");
[*]
Change 'grouper' to 'tilapia'
Save and flash!
Hopefully soon, devs will make two versions of their roms, although that may not happen until we finish porting the GSM stack. A solution for the meantime would be to edit the above assert to (off the top of my head):
Code:
assert(getprop("ro.product.device") == "grouper" || getprop("ro.build.product") == "grouper") || (getprop("ro.product.device") == "tilapia" || getprop("ro.build.product") == "tilapia")
For anything meant to service both devices. The devs should not be expecting users to run another device's recovery in my opinion, even if it is working. Because, as we know, it breaks other things, like OTAs and other update.zips.
My expectation would be that they will begin to build separate roms, as that is best practice and doesn't make use use the grouper fstab stuff. Not the most efficient use of bandwidth, I concede...
Ather said:
a mirror please?
Click to expand...
Click to collapse
Sure. Is techerrata/Goo a non-working option for some people? I use it for a project that is has mostly international users and haven't had any complaints. What/where would be helpful to you?
Update: Since I am here...I will post CWM Touch eventually. CWM Touch still has closed source elements, so the only way I know of to compile it is to use koush's web builder. But the result of that build is not booting. I ported Touch by hand, but it is too buggy to release, something needs to be modified in the recovery.fstab, I guess.

Mirror:
http://core.routed.com/nexus7/

If this is installed, will I be barred from installing grouper roms? I currently have multirom running, with stock as the main rom and PA as the alternate. PA doesn't get 3G but it works fine. Other grouper roms still work too, just no 3G. This is holding me over until they get the "tilapia" roms up. I just installed the OTA manually through fastboot.

Xentar712 said:
If this is installed, will I be barred from installing grouper roms? I currently have multirom running, with stock as the main rom and PA as the alternate. PA doesn't get 3G but it works fine. Other grouper roms still work too, just no 3G. This is holding me over until they get the "tilapia" roms up. I just installed the OTA manually through fastboot.
Click to expand...
Click to collapse
You will have to hack the grouper roms to change their assert to read tilapia rather than grouper (assuming they have them, and it is REALLY easy to do either way, easier than flashing an OTA in fastboot easy). I tend to be of the opinion that it is better to have a hack like that when you know you are doing something dangerous as opposed to the reverse.
Not that it is all that dangerous with the Nexus devices. But if you are flashing a rom from a different device onto your tablet, I think that you should have to indicate you are aware you are doing it.
The best thing would be for roms that are able to work on both devices should have updater-scripts that reflect that. You shouldn't be required to run recovery not for your device. But personal choice, as always.
Edit: As indicated on the OP, grouper and tilapia have different layouts. Look at the recovery.fstab, tilapia has this line:
Code:
/radio ext4 /dev/block/platform/sdhci-tegra.3/by-name/RDO
That file is used in making and configuring recovery...the rom makers will have to be able to work with tilapia recovery if they ever hope to have the GSM stack work, I would guess.

mateorod said:
You will have to hack the grouper roms to change their assert to read tilapia rather than grouper (REALLY easy, easier than flashing an OTA in fastboot easy). I tend to be of the opinion that it is better to have a hack like that when you know you are doing something dangerous as opposed to the reverse.
Not that it is all that dangerous with the Nexus devices. But if you are flashing a rom from a different device onto your tablet, I think that you should have to indicate you are aware you are doing it.
The best thing would be for roms that are able to work on both devices should have updater-scripts that reflect that. You shouldn't be required to run recovery not for your device. But personal choice, as always.
Click to expand...
Click to collapse
Cool, I'll give it a go once you get TWRP up and running. Maybe Tassadar, over in the MultiROM forum, can tweak it for MultiRom as well. I'm really liking MultiRom - IMHO it's less risky when toying with unknowns. It's probably more risky in reality though, and I'm just crazy

I've flashed this recovery to get 4.2.1 on my Nexus 7 3G, but it seems that I can't go into recovery mode anymore. The screen shows me picture of an android lying down with its front open.
The only way I'm able to go into recovery is to reflash, or do a
Code:
fastboot boot recovery recovery-CWM-tilapia-regular.img
This works for that 1 boot, after which I get the same issue.

superc0w said:
I've flashed this recovery to get 4.2.1 on my Nexus 7 3G, but it seems that I can't go into recovery mode anymore. The screen shows me picture of an android lying down with its front open.
The only way I'm able to go into recovery is to reflash, or do a
Code:
fastboot boot recovery recovery-CWM-tilapia-regular.img
This works for that 1 boot, after which I get the same issue.
Click to expand...
Click to collapse
Okay. After I flashed the OTA, CWM asked me if I wanted to make it permanent, but maybe that by itself us not enough. I had already done the following step.
flash recovery and boot into it. Mount system, and then:
Code:
adb shell
mv system/recovery-from-boot.p system/recovery-from-boot.bak
exit
CWM asked me if i wanted to prevent the updates from flashing stock recovery and if I wanted to secure the root (su binary). But maybe that doesn't work right out of the box.

mateorod said:
Okay. After I flashed the OTA, CWM asked me if I wanted to make it permanent, but maybe that by itself us not enough. I had already done the following step.
flash recovery and boot into it. Mount system, and then:
Code:
adb shell
mv system/recovery-from-boot.p system/recovery-from-boot.bak
exit
CWM asked me if i wanted to prevent the updates from flashing stock recovery and if I wanted to secure the root (su binary). But maybe that doesn't work right out of the box.
Click to expand...
Click to collapse
Yup, I renamed recovery-from-boot.p to recovery-from-boot.p.bak using ES File Explorer and it's all good now. I'm now able to use CWM. However, CWM always asks me if I want to prevent updates from flashing stock recovery and I always chose no (since it warns that this is irreversible).
Strange though. I assumed that even if CWM doesn't stick without renaming recovery-from-boot.p, the N7 3G would flash stock recovery and it would still be functional.

installed last night, works great..frankly i prefer the non-touch, dunnow why but its much better...i tried to rename the files, but there werent any files in the /system , flashed the CWM package, took a nandroid..all works great

Somehow this still does not seem to work for me:
After I reflashed the tilapia recovery (CWM 6.0.1.9), I executed the nakasig file and get:
Code:
Finding update package...
Opening update package...
Installing update...
Verifying current system...assert failed: apply_patch_check("/system/framework/framework-res.apk". "212e537985a59a7d40ff8b450a3de597ade4251c". "521503fb2a63dc6d80c4a1ecf72770c3745c4178")
E:Error in /sdcard/0/65880f45b1c0.signed-nakasig-JOP40D-from-JOP40C.65880f56.zip
(Status 7)
Installation aborted.

gwisch said:
Somehow this still does not seem to work for me:
After I reflashed the tilapia recovery (CWM 6.0.1.9), I executed the nakasig file and get:
Code:
Finding update package...
Opening update package...
Installing update...
Verifying current system...assert failed: apply_patch_check("/system/framework/framework-res.apk". "212e537985a59a7d40ff8b450a3de597ade4251c". "521503fb2a63dc6d80c4a1ecf72770c3745c4178")
E:Error in /sdcard/0/65880f45b1c0.signed-nakasig-JOP40D-from-JOP40C.65880f56.zip
(Status 7)
Installation aborted.
Click to expand...
Click to collapse
That error message has absolutely nothing to do with the recovery image.
This special talapia version of CWM isn't some magic pill that will make every other problem go away. It's simply designed to accurately reflect the hardware for the tablet you own (talapia vs grouper) so you don't run into as many problems down the road installing OTA updates and custom ROMs that check.
However, you still need to meet ALL the other requirements of the updates. So if you made changes to your /system files, kernel (not in this case, but in general), build.prop, etc., the OTA update will still abort and explain why.
Did you even read the error message?
Verifying current system...assert failed: apply_patch_check("/system/framework/framework-res.apk".
It's pretty clear that you modified the framework file. You will need to revert that back to stock and flash the OTA again afterwards. Any other tweaks/modifications/freezes/removals/etc. of system apps will most likely result in the same thing.

TWRP is up...
I compiled a TWRP image for tilapia as well.
This actually took a little doing...my intention here was to simply compile some images, but since tilapia is only Android 4.2, and we don't have CM10.1 (officially), I actually endied up having to port TWRP whole cloth. This is compiled from TWRP source code, with a few tweaks.
There are a couple things about the port I would like to eventually tweak, I had to copy the sbin folder over by hand, and due to the intertwined nature of grouper/tilapia, settings derived from common files in the source code are named grouper still, (i.e. ueventd.grouper.rc instead of ueventd.tilapia.rc) but that is quibble stuff and may end up staying that way regardless, since many of the tilapia make files are merely pointers to the grouper files. It certainly doesn't hurt anything.
The TWRP image has been confirmed working with the OTAs.
I thought long and hard about possibly modifying these recovery images to allow users to flash grouper roms as well. I know it is unlikely that everything will be made available in two versions, even though it should be.
Any thoughts on this? It is a demonstrably better idea than having people use the grouper images, but I still think the developers/modders should be the ones handling this problem. People are going to NEED this recovery image once the nightlies of AOKP/CM10.1 and whatever start coming down, but I know that grouper zips will still be tempting to many.

Under the instructions in the first post, it says:
OR: If you just want to boot into custom recovery instead of overwriting the stock or grouper recovery(playing fast and loose- keeping grouper recovery on-device for grouper roms, at least until devs add tilapia asserts to their updater-scripts), use
fastboot boot recovery recovery-CWM-tilapia-regular.img
Click to expand...
Click to collapse
So without flashing anything, I should be able to just point fastboot towards the clockworkmod file on my computer and it should reboot into clockworkmod right?
When I try to do this, it doesn't work, and I just get this:
Code:
C:\Program Files\Droid Explorer\SDK\tools>fastboot boot recovery D:\Downloads\recovery-CWM-tilapia-regular.img
cannot load 'recovery'
I also tried to follow the main instructions and it fails on step 2 with:
Code:
C:\Program Files\Droid Explorer\SDK\tools>fastboot flash recovery D:\Downloads\recovery-CWM-tilapia-regular.img
sending 'recovery' (6568 KB)... FAILED (remote: Bootloader is locked.) finished. total time: 0.021s
I looked at other threads and found out that normally flashing a custom recovery requires issuing a fastboot oem unlock command that wipes all data. Am I missing anything or is this actually required before either of these?

manekineko said:
Under the instructions in the first post, it says:
So without flashing anything, I should be able to just point fastboot towards the clockworkmod file on my computer and it should reboot into clockworkmod right?
When I try to do this, it doesn't work, and I just get this:
Code:
C:\Program Files\Droid Explorer\SDK\tools>fastboot boot recovery D:\Downloads\recovery-CWM-tilapia-regular.img
cannot load 'recovery'
I also tried to follow the main instructions and it fails on step 2 with:
Code:
C:\Program Files\Droid Explorer\SDK\tools>fastboot flash recovery D:\Downloads\recovery-CWM-tilapia-regular.img
sending 'recovery' (6568 KB)... FAILED (remote: Bootloader is locked.) finished. total time: 0.021s
I looked at other threads and found out that normally flashing a custom recovery requires issuing a fastboot oem unlock command that wipes all data. Am I missing anything or is this actually required before either of these?
Click to expand...
Click to collapse
Yep. My bad.
I originally just posted the images as an alternative to the recoveries for the regular Nexus 7 (non-3g) images people were using. I later realized that some new people would come by so I threw rooting instructions as well. I didn't go back far enough, sorry. I will fix it now.
What you need to do is easy though, just like you mentioned you need to unlock your bootloader. So once you boot into the bootloader,
Code:
fastboot oem unlock
This will wipe all of your data, and there is no way around this, sorry. It is a security measure of some sort. There will be a screen where you acknowledge this and then the bootloader will unlock. You can then follow the rest of the instructions. Sorry for the confusion.
Update: Fixed and streamlined OP. Glad you got me to do this, I think it is better now.

In the rooting instructions, this line wasn't working for me, as /sdcard/ was for some reason a directory containing 3 folders (0, odb, legacy), where 0 had the normal contents of /sdcard/:
adb push CWM-SuperSU-v0.98.zip /sdcard/
Click to expand...
Click to collapse
Instead, I had to do:
adb push CWM-SuperSU-v0.98.zip /sdcard/0/
After that change, I was able to flash the zip and root successfully.

Hi OP,
I followed your instructions and managed to root my nexus 7 3G running stock Android 4.2.1. Thanks.
However there are some extra "incidents" which is not captured in your instructions and somehow it happen on my side, so I just detailed down what happen in case it can be of help to others:
Below is the full OP's original instruction and some extra "incidents" during rooting
Instructions
1. Boot into the bootloader (2 choices)
Turn the device on while pressing volume down; or
Code:
Code:
adb reboot bootloader
2. Unlock your bootloader
THIS WILL WIPE ALL OF YOUR DATA! No way around it...
Code:
Code:
fastboot oem unlock
My Nexus rebooted after this step and all the ADB drivers on my Windows 7 pc is gone. With my Nexus 7 still connected and booted up, when I do "adb device", I cannot see my device. I open the Device Manager and notice that the "ADB Composite Interface" driver is gone!
I got to re-install all my drivers for my Nexus 7 manually. I downloaded WugFresh Toolkit and follow the first step to re-install all the drivers. (I just wana try manual rooting, that's why I didn't use WugFresh Toolkit)
After making sure my device can be listed after "adb device", I proceed to
2a. Reboot into bootloader
Code:
adb reboot bootloader
3. With your Nexus 7 3G in the bootloader and connected to your computer through the usb cable:
replace recovery-CWM-tilapia-regular with the name of the recovery image you chose to download.
Code:
Code:
fastboot flash recovery recovery-CWM-tilapia-regular.img
4. To make CWM your permanent recovery: (this can, despite the warnings, be undone. Do it.)
Boot into recovery mode by pressing 'vol up' and when the menu says 'recovery mode' press the power button.
Mount system in the 'mounts' menu
Code:
Code:
adb shell
mv system/recovery-from-boot.p system/recovery-from-boot.bak
exit
5. To Root (With /system still mounted):
There is no error when pushing the zip file to /sdcard/ but the file just didn't appear. The windows command prompt also indicate that the push was successful. I notice that the my /sdcard/ directory is softlink to /data/media/, so I push to /data/media/ instead and it works! The zip file now appear in /sdcard/. I am not sure why is this so.
Code:
Code:
adb push CWM-SuperSU-v0.98.zip /data/media/
Flash the SuperSU zip in recovery ('Install' menu with TWRP or 'choose zip from sdcard' in CWM)
Code:
Reboot System
5a. CWM will give a warning message stating overwriting of flash recovery. I cannot recall what is that exact message. But you will be presented with a llist of options with one "Yes" and all "No". I choose "Yes" to retain CWM as my recovery.

COLOR="Red"]My Nexus rebooted after this step and all the ADB drivers on my Windows 7 pc is gone. With my Nexus 7 still connected and booted up, when I do "adb device", I cannot see my device. I open the Device Manager and notice that the "ADB Composite Interface" driver is gone!
I got to re-install all my drivers for my Nexus 7 manually. I downloaded WugFresh Toolkit and follow the first step to re-install all the drivers. (I just wana try manual rooting, that's why I didn't use WugFresh Toolkit)
After making sure my device can be listed after "adb device", I proceed to
Click to expand...
Click to collapse
I can't speak as to how Windows works exactly, but I can tell you that fastboot code does nothing to the 'host' PC. Not saying it didn't happen, but it wasn't fast boot.
There is no error when pushing the zip file to /sdcard/ but the file just didn't appear. The windows command prompt also indicate that the push was successful. I notice that the my /sdcard/ directory is softlink to /data/media/, so I push to /data/media/ instead and it works! The zip file now appear in /sdcard/. I am not sure why is this so.
Click to expand...
Click to collapse
The person above you reported that they had to push to /sdcard/0. I checked my original instructions and they work for me. I haven't decided what to put yet. They have been playing around with the standard nomenclature for emulated storage, but I have yet to see anything that explains the varied experiences. I haven't looked yet really, either
5a. CWM will give a warning message stating overwriting of flash recovery. I cannot recall what is that exact message. But you will be presented with a llist of options with one "Yes" and all "No". I choose "Yes" to retain CWM as my recovery.
Click to expand...
Click to collapse
I originally told people to follow the CWM directions on having permanent recovery. But some user experience taught me that some people are going to skip this step due to confusion over the warnings. So I decided to put in the manual method.
Thanks for your feedback.

I originally told people to follow the CWM directions on having permanent recovery. But some user experience taught me that some people are going to skip this step due to confusion over the warnings. So I decided to put in the manual method.
Click to expand...
Click to collapse
Hi,
In fact I am also confused about the warning. Not sure does choosing "Yes" means retain CWM or not. So I just choose "Yes" and saw that CWM is still the recovery after reboot.
So do you mean after this step:
Code:
adb shell
mv system/recovery-from-boot.p system/recovery-from-boot.bak
exit
It does not matter whether I choose "Yes" or "No" in the final phase, and I will still have CWM as my recovery?

[ROOT][CWM][ROM]Pantech Discover P9090 (Magnus) Root & Modification Guide

Pantech Discover P9090 (Magnus) Root & Modification Guide
This thread is intended as an updated version of the original Ultimate Pantech Discover/Magnus/P9090 Rooting & Modding Thread thread. I created this thread to bring the latest knowledge and tutorials to the top. If you are interested in the evolution of Discover rooting and modding pour yourself a cup of coffee, tea, or ??? and review the posts in that thread and when you are ready to modify your Discover come back here.
Available Mods
Root access
ClockworkMod Recovery
TWRP Recovery
Restore unlocked bootloader for Jellybean devices
CWM flashable ROM/partition updates
Warning/Disclaimer
The tutorials posted in this thread at the time of this writing have been tested and should do what they claim to do without causing harm to your phone, however, if for any reason things go awry when doing any kind of update or modification to your phone the authors of these tutorials or thread posts are not responsible. There is always a chance that modifying your phone can cause damage or a loss of features. Proceed at your own risk. I suggest you read the procedure you intend to implement thoroughly and if necessary ask questions before you proceed. Also, installing mods may make it so you cannot receive or install updates from Pantech/AT&T.
Modification Procedure Order
Determine if your device is running Ice Cream Sandwich (ICS) or Jellybean (JB)
Open the Settings app and tap on "About phone"
If the "Android version" is 4.0.4 you are running ICS, if it is 4.1.2 you are running JB
Set up and ensure you have ADB access to the phone
For now you will have to find an ADB installation tutorial elsewhere
Root your device
Follow the tutorial here.
Jellybean (JB) users should revert back to the unlocked (ICS) bootloader to increase the chance of brick recovery
Follow the tutorial here.
Install ClockworkMod Recovery or TWRP
Follow the tutorial here (CWM) or here (TWRP).
(Optional) Install custom ROM(s)
Follow the tutorial here.
Useful links
Pantech Discover Specs
Ultimate Pantech Discover/Magnus/P9090 Rooting & Modding Thread - Not all content is still relevant but a great read
PantechDevTeam Github - The original Pantech devs (a ton of awesome work here)
PantechDiscover Github - Put together by @Unjustified Dev with contributions from @mifl and myself
Pantech Discover Jellybean Kernel Source
Pantech Discover ICS Kernel Source
Thanks to everyone who helped test and provide feedback for these advancements. A big thanks to @Unjustified Dev & @mifl for their continued development help and porting TWRP (Unjustified Dev) and to @ShotSkydiver for creating the original Pantech Discover mod thread.

Root
Rooting the Pantech Discover P9090
WARNING: Please review the Warning/Disclaimer in the original post before following this procedure!
Click "CLICK TO SHOW CONTENT" to proceed.
Users running ICS
Download recovery-magnus.img, su, and SuperSU_1.65.apk and move them to a directory of your choosing hereafter known as <install-directory>
Boot the phone in fastboot (bootloader) mode by holding down both volume buttons and the power button, once the menu appears use the volume buttons to select "fastboot", then hit the power button
Attach your phone to your computer
Open a cmd window (Windows) or terminal/shell (unix flavors) and type the following command (hit enter after each):
Code:
cd <install-directory>
Now boot to the magnus recovery by typing:
Code:
fastboot boot recovery-magnus.img
The phone should be booted to CWM, now type:
Code:
adb push su /sdcard/
adb push SuperSU_1.65.apk /sdcard/
adb shell
You should now be in an adb terminal on the phone, type the following:
Code:
mount /dev/block/mmcblk0p14 /system
cd /sdcard
cp SuperSU_1.65.apk /system/app/
cp su /system/xbin/
chmod 4755 /system/xbin/su
exit
If all goes well you should be back in your computer's terminal, reboot the phone with
Code:
adb reboot
Enjoy!
Users running Jellybean
Download and install the Framaroot app (version 1.6.1 or later) from here.
Install and open the app
Select "Gandalf"
Reboot the phone for good measure
Enjoy!

Bootloader
Reverting to the Unlocked (ICS) Bootloader from the JB Bootloader
WARNING: Please review the Warning/Disclaimer in the original post before following this procedure!
Click "CLICK TO SHOW CONTENT" to proceed.
Context: The Jelly Bean update for the Pantech Discover flashes a locked bootloader over the unlocked Ice Cream Sandwich bootloader. The result is that you can no longer use fastboot to flash images or boot to external bootloaders. If you are on ICS this tutorial does not apply.
You can test to see if you have the locked bootloader by booting into fastboot (power off device, power on devices holding both volume keys, select fastboot), connect the device to your PC, and run the following command from a command terminal.
Code:
fastboot boot recovery-magnus.img
NOTE: If you don't already have the magnus recovery image download it from here.
If your output looks like the message below you have the locked bootloader and this guide applies to you.
Code:
downloading 'boot.img'...
OKAY [ 0.538s]
booting...
FAILED (remote: Not Support !!)
finished. total time: 0.543s
Procedure: If you have the locked bootloader, you would prefer not be locked, and you are willing to take the risk you can follow the procedure below.
Prerequisites
Phone must be rooted
ADB access
Download the ICS bootloader image (aboot.img) from here.
Connect your phone to your PC and from a command window in the download directory type:
Code:
adb push aboot.img /sdcard/
adb shell
If you are connected to your device at this point type:
Code:
su
cd /sdcard
md5sum aboot.img
The output should be:
Code:
7f55c5ab321cf20e595b841371f45cda aboot.img
The MD5 checksum should be the hex number above (beginning in 7f and ending in cda). If it does match download it again and make sure the checksum matches before proceeding. If no matter what you do you can't get a match then don't proceed.
If you are here then you have the ICS bootloader and it's ready to be flashed, before we do this you should check the checksum for the bootloader partition with the command:
Code:
md5sum /dev/block/mmcblk0p5
output:
Code:
8b6fa6881c7f155858243e94490d0a29 /dev/block/mmcblk0p5
If you are on JB the checksum should match mine.
Now you are ready to flash the ICS image. If you are feeling confident and risk adverse run the command below:
Code:
dd if=aboot.img of=/dev/block/mmcblk0p5
You should get the output:
Code:
5120+0 records in
5120+0 records out
2621440 bytes transferred in 0.458 secs (5723668 bytes/sec)
Don't be concerned if the transfer time is not precise.
Now confirm that our checksum is updated to the new image:
Code:
md5sum /dev/block/mmcblk0p5
Code:
7f55c5ab321cf20e595b841371f45cda /dev/block/mmcblk0p5
If not follow the bail out procedure outlined after this procedure, otherwise get back to your PC command window with:
Code:
exit
exit
Reboot into the ICS bootloader with:
Code:
adb reboot bootloader
Once you are in fastboot verify it worked with:
Code:
fastboot boot recovery-magnus.img
You should be rewarded with the following output:
Code:
downloading 'boot.img'...
OKAY [ 0.544s]
booting...
OKAY [ 0.020s]
finished. total time: 0.565s
You are done!!!!!
Invalid checksum: If the checksum you show does not match the checksum above you can reflash the JB bootloader and if all goes well you will be back where you started.
Download the JB bootloader (jb-aboot.img) from here.
Follow the procedure above to push the bootloader to the device and validate that the checksum matches the original JB checksum you copied on step above.
Flash the JB bootloader as per the guide above replacing aboot.img with jb-aboot.img.
If you have problems I strongly suggest you refrain from rebooting your phone and ask for help.

CWM
Installing ClockworkMod 6.0.2.8 on your Pantech Discover
WARNING: Please review the Warning/Disclaimer in the original post before following this procedure!
Click "CLICK TO SHOW CONTENT" to proceed.
Prerequisites
You must have adb and fastboot installed and working on your computer. There are literally hundreds of tutorials on this so I won't go into it here.
Your phone must be rooted
Optional but recommended
If you are on Jellybean and you haven't already done so I recommend reverting to the unlocked (ICS) booloader. An unlocked bootloader will increase the ability to restore a "brick" substantially.
Ready, set, go!
Option 1 (Do this if you have the unlocked ICS bootloader this is much faster)
Download update_magnus_clockworkmod-6.0.2.8.zip and recovery-magnus.img and move them to a directory of your choosing hereafter known as <install-directory>
Turn off the phone, copy update_magnus_clockworkmod-6.0.2.8.zip to a micro sdcard and install it in the phone
Boot the phone in fastboot (bootloader) mode by holding down both volume buttons and power, once the menu appears use the volume keys to select fastboot, then hit power
Attach your phone to your computer
Open a cmd window (Windows) or terminal/shell (unix flavors) and type the following command (hit enter after each):
Code:
cd <install-directory>
Now boot to the magnus recovery by typing:
Code:
fastboot boot recovery-magnus.img
The phone should be booted to CWM, now select the menu options:
install zip from sdcard > choose zip from external sdcard​
Select update_magnus_clockworkmod-6.0.2.8.zip then hit power and confirm by choosing
Yes - Install update_magnus_clockworkmod-6.0.2.8.zip​
Once the install is finished choose
Go Back > reboot system now​
Enjoy!
Option 2 (Do this if you have the locked Jellybean bootloader and do not wish to revert it):
Attach your phone to your computer and make sure it is booted to Android
Download recovery-magnus.img and move it to a directory of your choosing hereafter known as <install-directory>
Open a cmd window (Windows) or terminal/shell (unix flavors) and type the following command (hit enter after each):
Code:
cd <install-directory>
adb push recovery-magnus.img /sdcard/
adb shell
In the adb terminal type:
Code:
cd /sdcard
ls
Verify that the recovery-magnus.img file is there and if so type:
Code:
su
mount -o rw,remount /system
dd if=recovery-magnus.img of=/dev/block/mmcblk0p20
You should see output indicating that the image was flashed (I'll try to update this with the exact text). If you get an error don't continue and when you reboot to Android the original recovery should be restored. Otherwise type:
Code:
mv /system/recovery_from_boot.p /system/recovery_from_boot.p.bak
exit
exit
You should be back in your computers terminal, type:
Code:
adb reboot recovery
You should be in CWM 6.0.2.8 after a minute or so. The first time you reboot CWM will ask if you want to prevent recovery from being overwritten, go ahead and say yes.
You can use the backup feature to backup your ROM.
What works
Backup/restore from sdcard and external sdcard (including advanced restore)
Delete backup (sdcard and external sdcard)
Choose default backup method
Install zip from sdcard (external)
Wipe cache
Wipe dalvik-cache
Wipe data/factory reset
Mounts - mounting and unmounting partitions
Key test
Show log
Fix permissions (I ran this and it completed and the phone boots but I haven't done exhaustive testing so I don't recommend it, shouldn't need this feature at this point)
What hasn't been tested yet
Install zip from sideload
Format partitions (not recommended)
Partition external sdcard
Report error
Bugs
Backups do not reflect the correct date (common issue that can be resolved eventually)

ROM
Flashing a Custom ROM
WARNING: If you downloaded the ROM that was originally linked to in this guide (magnus-jb-4.1.2-cwm-unlocked_bootloader-rooted-all_partitions.zip) please do not flash it!! While this has worked on most phones the original IMEI on a couple of phones was wiped out.
WARNING 2 (Untested fix uploaded on 11/29, see below) : A couple of users have reported that this update failed on their phones but they were able to restore from a nandroid backup. If you still want to try this ROM please backup your current ROM in CWM first! If you try this please let me know if this works or does not work on your phone and which Android version you were on prior to flashing it. Thanks!
UPDATE 11/29/2013 Newly uploaded file will most likely fix the issues mentioned in warning 2 above, however, I still strongly encourage that you do a backup in CWM before flashing. Please respond with the results indicating which version of Android you flashed this over.
Click "CLICK TO SHOW CONTENT" to proceed.
This guide covers the procedure to flash a specific, JB ROM as discussed below, however, the basic procedure can be used to flash different ROMs as they become available.
Features
Jellybean 4.1.2 stock (other than noted below)
Rooted with /system/xbin/su
SuperSU installed as a system app
Magnus CWM recovery
ICS unlocked bootloader (aboot)
This update is intended to install the unlocked bootloader for all users; provide a restore point going forward; and serve as a basis for future ROMs and enhancements.
This update does not flash the cache or data partitions so your installed apps and data will remain.
WARNING: Please review the Warning/Disclaimer in the original post before following this procedure!
NOTE FOR ICS USERS: The AT&T/Pantech OTA JB Update (from ICS) provides patches to several partitions that are not patched as part of this update. If you are able to run the OTA update I recommend it, if not and you don’t mind having a “hybrid” ROM go for it at your own risk.
Since this flashes the bootloader I strongly recommend checking the MD5 Checksum as per the guide below before executing the update. Make sure the device has enough power, and don't unplug, wiggle, or otherwise mess with the device until the update is complete.
Prerequisites
Magnus CWM installed per the guide above (see OP)
Jellbean or ICS (see notes above before flashing over ICS)
ADB installed and functional
Make sure the battery level of the device is adequate
Flash from the internal sdcard
Download the update from here.
Boot into CWM recovery by holding down the volume up button and power button
Do a CWM nandroid backup
Select "mounts and storage > mount /sdcard > +++++Go Back+++++"
Select "wipe cache partition"
Select "advanced > wipe dalvik cache > +++++Go Back+++++"
OPTIONAL: Select "wipe data/factory reset". WARNING: This will remove your personal apps and data!
Once the download from step 1 is complete, plug the phone into your computer, open a command window, navigate to the download directory, and push the update to the sdcard with:
Code:
adb push magnus-jb-4.1.2-cwm-unlocked_bootloader-rooted2.zip /sdcard/
Check the md5 checksum to ensure you don't have a corrupt download (IMPORTANT!)
Code:
adb shell
cd /sdcard
md5sum magnus-jb-4.1.2-cwm-unlocked_bootloader-rooted2.zip
Should result in:
Code:
3dca0555f81cef97e304c17515c807fa magnus-jb-4.1.2-cwm-unlocked_bootloader-rooted2.zip
If not, download the update and try again. Do not proceed if your checksum doesn't match!
Exit adb shell:
Code:
exit
On the phone, select "install zip from sdcard > choose zip from sdcard", select the update file, and confirm
Wait patiently and do not unplug the device or disrupt the process!
When the update is finished select "+++++Go Back+++++" followed by "reboot system now", if you are prompted to "Fix root" select "Yes" to prevent it from warning again
Wait patiently while it boots, configures the apps, compiles & caches, and connects to your carrier. This can take a few minutes.
Enjoy!

Nice guide. Can't wait till this phone comes if I'm not mistaken cogency sent it again
Sent from my SCH-I535 using Tapatalk

Unjustified Dev said:
Nice guide. Can't wait till this phone comes if I'm not mistaken cogency sent it again
Sent from my SCH-I535 using Tapatalk
Click to expand...
Click to collapse
Thanks! I have been pretty swamped at work so I haven't been able to pull your kernel updates but I am anxious to get back to it. I am glad you have a phone on the way.

Great detailed guide, that provides easy to follow instructions.....nice work, again.

CM11.0
gj23 said:
Great detailed guide, that provides easy to follow instructions.....nice work, again.
Click to expand...
Click to collapse
I predict that on 2 months we will get CM11.0 (kitkat) for the p9090

eeter said:
I predict that on 2 months we will get CM11.0 (kitkat) for the p9090
Click to expand...
Click to collapse
I predict less than one month when my Discover comes in
Sent from my SCH-I535 using Tapatalk

I saw in the Original Thread that Updating to Jellybean on an ICS device doesn't work and he made it work by restoring a nandroid backup and then flashing the rom via CWM.
Any other way to directly upgrade to Jelly bean by flashing the zip via CWM directly without using nandroid backup?
Thanks.

vijayr2002 said:
I saw in the Original Thread that Updating to Jellybean on an ICS device doesn't work and he made it work by restoring a nandroid backup and then flashing the rom via CWM.
Any other way to directly upgrade to Jelly bean by flashing the zip via CWM directly without using nandroid backup?
Thanks.
Click to expand...
Click to collapse
If you are talking about the post below I think you misunderstood. Flashing Jellybean using the guide on the first page of this thread worked for him. He was outlining the history of what he has done on the device and nothing worked other than the magnus-jb-4.1.2-cwm-unlocked_bootloader-rooted.zip update.
If you are on ICS and you have CWM installed the guide in post #5 will get you on Jellybean with all of the goodies.
osopol4r said:
Confirmed working....
> ICS Unable to Update
> Updated to JB with nandroid provided here
> JB nandroid missing browser apk
> Restored from to and from previous ICS
> Installed zip from sd card magnus-jb-4.1.2-cwm-unlocked_bootloader-rooted.zip
> Phone booted correctly, so far so good
I'll report back any issued (if any)
Thanks!!!
Click to expand...
Click to collapse

New subforum in "DevsNest Developments" dedicated to Pantech P9090:
http://www.devsnest.com/forumdisplay.php?fid=142
We hope you include some content in it.
Greetings.

sandnap said:
If you are talking about the post below I think you misunderstood. Flashing Jellybean using the guide on the first page of this thread worked for him. He was outlining the history of what he has done on the device and nothing worked other than the magnus-jb-4.1.2-cwm-unlocked_bootloader-rooted.zip update.
If you are on ICS and you have CWM installed the guide in post #5 will get you on Jellybean with all of the goodies.
Click to expand...
Click to collapse
Great! I somehow misunderstood it. I will update after i install. Thank you for your time spent in contributing for Pantech Discover. Kudos!

vijayr2002 said:
Great! I somehow misunderstood it. I will update after i install. Thank you for your time spent in contributing for Pantech Discover. Kudos!
Click to expand...
Click to collapse
If u install the JB 4.1.2 from here that's rooted and CWM you won't need to update as u will be on Jellybean.

was having wifi issues and bluetooth issues and was ics/jb mix . everything flashed fine and updated fine. will post back after further testing but all seems to be working and volume seems a bit better now.

greg97526 said:
was having wifi issues and bluetooth issues and was ics/jb mix . everything flashed fine and updated fine. will post back after further testing but all seems to be working and volume seems a bit better now.
Click to expand...
Click to collapse
Glad to hear it! I have been waiting to hear from you. I am interested to know if this improves your wifi/bluetooth issues.

sandnap said:
Glad to hear it! I have been waiting to hear from you. I am interested to know if this improves your wifi/bluetooth issues.
Click to expand...
Click to collapse
Blue tooth works flawlessly. Still a bit lagging on wifi. Maybe I need to remove the files we added that didn't match up with what you had or did this update erase all of that?

greg97526 said:
Blue tooth works flawlessly. Still a bit lagging on wifi. Maybe I need to remove the files we added that didn't match up with what you had or did this update erase all of that?
Click to expand...
Click to collapse
This update completely wipes /system then copies over all of the stock Jellybean files so there are no remnants of our hand-crafted /system left. The update also flashes all of the Jellybean partitions that were patched as part of the OTA update so your device should now be consistent with those of everyone who has executed this update with the exception of your /data and /sdcard. You could try backing up your applications and doing a factory reset in CWM.

How about that!
Hi there!
I don't know if you remember me from the old post but...
I just realized my IMEI changed, I used to have my pantech discover unlocked (network unlock) and I believe after flashing the Jelly Bean update file some how relocked itself plus the IMEI also changed. I purchased the unlock code and I just compared the IMEI and it is not the same, plus the phone is now network locked.
I'll try my original nandroid backup and see what happens.

Lost cache partition fixed

Hi,
I got the terrible error "mounting cache failed" blabla and my Nexus 5 was dead. I tried with all ways I could find: fastbook flash cache cache.img; flashing factory image; LG Flashtool and TOT flashing, etc. All did not work.
But finally I found out the reason and made my Nexus 5 back to work.
The reason is simple: my cache partition should be EXT2 (or EXT4) but for some reason its type is unknown. That caused the mounting failed.
You could check your partition tables like:
adb shell parted -s /dev/block/mmcblk0 print
Keep an eye on your cache partition (27) type. Bingo, you can fix it if its type is blank!!
Fix the type (in the shell):
1) boot into recovery mode
1.1) adb shell
1.2) mkfs.ext2 /dev/block/mmcblk0p27
1.3) exit
2) boot into Fastboot
Flash the factory image (flash-all.sh) is the simplest way to make sure all works. Or simply flash the cache.img
fastboot flash cache cache.img
Reboot and you will see your Nexus 5 is back.
Good luck.
Yu
http: // clashin.com/

zhudachang said:
Hi,
I got the terrible error "mounting cache failed" blabla and my Nexus 5 was dead. I tried with all ways I could find: fastbook flash cache cache.img; flashing factory image; LG Flashtool and TOT flashing, etc. All did not work.
But finally I found out the reason and made my Nexus 5 back to work.
The reason is simple: my cache partition should be EXT2 (or EXT4) but for some reason its type is unknown. That caused the mounting failed.
You could check your partition tables like:
adb shell parted -s /dev/block/mmcblk0 print
Keep an eye on your cache partition (27) type. Bingo, you can fix it if its type is blank!!
Fix the type (in the shell):
1) boot into recovery mode
1.1) adb shell
1.2) mkfs.ext2 /dev/block/mmcblk0p27
1.3) exit
2) boot into Fastboot
Flash the factory image (flash-all.sh) is the simplest way to make sure all works. Or simply flash the cache.img
fastboot flash cache cache.img
Reboot and you will see your Nexus 5 is back.
Good luck.
Yu
http: / / justcoolthings.net
Click to expand...
Click to collapse
Just want to say thank you for these steps! It fixed my phone as well and saved my sanity! LOL

5.1 OTA Update Screwed My Nexus 5
zhudachang said:
Hi,
I got the terrible error "mounting cache failed" blabla and my Nexus 5 was dead. I tried with all ways I could find: fastbook flash cache cache.img; flashing factory image; LG Flashtool and TOT flashing, etc. All did not work.
But finally I found out the reason and made my Nexus 5 back to work.
The reason is simple: my cache partition should be EXT2 (or EXT4) but for some reason its type is unknown. That caused the mounting failed.
You could check your partition tables like:
adb shell parted -s /dev/block/mmcblk0 print
Keep an eye on your cache partition (27) type. Bingo, you can fix it if its type is blank!!
Fix the type (in the shell):
1) boot into recovery mode
1.1) adb shell
1.2) mkfs.ext2 /dev/block/mmcblk0p27
1.3) exit
2) boot into Fastboot
Flash the factory image (flash-all.sh) is the simplest way to make sure all works. Or simply flash the cache.img
fastboot flash cache cache.img
Reboot and you will see your Nexus 5 is back.
Good luck.
Yu
http: // clashin.com/
Click to expand...
Click to collapse
Hi Yu,
I have the same problem as you mention above, occured after i had the office 5.1 OTA update 3 days back.
After updating, i was able to play with my phone for a while.. The next day, it was in a boot loop state with the "Google" image on my device.
I am able to ADB into my phone, and adb devices returns me my deviceId and sideload.
But when i attempt this command "adb shell" i get "error: closed".. Been searching the net to find out how to open this so i can do the fix, but none so far....
Any idea how to sort this out? Many thanks in advance.
p/s: my device is stock STOCK... non-unlock and non-rooted.
Cheers,
Keith

I would suggest you do a "flash-all" to your device.
1) Download the factory image ("hammerhead-lmy47i") from https: // developers.google.com /android/nexus/images
2) Boot your device into bootloader mode and run "flash-all.sh" to flash the 5.1 factory rom. It should fix all your errors.
Good luck.
Yu
liquanize said:
Hi Yu,
I have the same problem as you mention above, occured after i had the office 5.1 OTA update 3 days back.
After updating, i was able to play with my phone for a while.. The next day, it was in a boot loop state with the "Google" image on my device.
I am able to ADB into my phone, and adb devices returns me my deviceId and sideload.
But when i attempt this command "adb shell" i get "error: closed".. Been searching the net to find out how to open this so i can do the fix, but none so far....
Any idea how to sort this out? Many thanks in advance.
p/s: my device is stock STOCK... non-unlock and non-rooted.
Cheers,
Keith
Click to expand...
Click to collapse

liquanize said:
Hi Yu,
I have the same problem as you mention above, occured after i had the office 5.1 OTA update 3 days back.
After updating, i was able to play with my phone for a while.. The next day, it was in a boot loop state with the "Google" image on my device.
I am able to ADB into my phone, and adb devices returns me my deviceId and sideload.
But when i attempt this command "adb shell" i get "error: closed".. Been searching the net to find out how to open this so i can do the fix, but none so far....
Any idea how to sort this out? Many thanks in advance.
p/s: my device is stock STOCK... non-unlock and non-rooted.
Cheers,
Keith
Click to expand...
Click to collapse
Keep in mind that STOCK recovery does NOT let you connect to normal ADB, a custom recovery does. Also, you need to be root to 'mkfs.ext2', and the target partition must not be mounted, I believe.
Before attempting the steps @zhudachang posted below, i.e. To flash a factory image, you need to unlock your bootloader.
zhudachang said:
I would suggest you do a "flash-all" to your device.
1) Download the factory image ("hammerhead-lmy47i") from https: // developers.google.com /android/nexus/images
2) Boot your device into bootloader mode and run "flash-all.sh" to flash the 5.1 factory rom. It should fix all your errors.
Good luck.
Yu
Click to expand...
Click to collapse

[RECOVERY][UNOFFICIAL][3.7.0][Perseus] TWRP for Xiaomi Mi Mix 3

Code:
/*
*Disclaimer
*
* Your warranty is now void.
*
* We're 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 if
* you point the finger at us for messing up your device, we will laugh at you.
*/
Working :
Basic twrp features (boot, format data, etc, etc)
Decryption data up to android 13
Vibration
otg
Issues / Notes :
really messed fstab
/system is missing from wipeui, and i have no idea what happened (but flashing should works fine)
miui is partially support (due to using /cust as /system_ext)
Download : Link
Thanks :
aidan for sending me money to buy motherboard
Source :
device tree
kernel

reserved

Hey, thanks for sharing it.
I had some problems with installing custom ROM, because lack of appearing /system partition in format step and installed ROM went started to bootloop.
Fortunately I was able to pass this step by mounting system partition, entering into terminal and executing following command: " cd /system_root && rm -Rf * " -without quotes.
Please make sure to execute whole command at once or just ensure you will not delete files outside of proper system partition by executing part of command (for example when /system mounts in other location than /system_root). If you are not sure, execute "df" command and see last entry which should show you where system partition is mounted and adjust the command.
For some of you, who want to proceed with my advice. Please note, that I am not responsible for any problems you can cause on your device using my advice. It will surely not break your phone if done properly. if you don't understand what you do, please don't do it

Fiqusny said:
Hey, thanks for sharing it.
I had some problems with installing custom ROM, because lack of appearing /system partition in format step and installed ROM went started to bootloop.
Fortunately I was able to pass this step by mounting system partition, entering into terminal and executing following command: " cd /system_root && rm -Rf * " -without quotes.
Please make sure to execute whole command at once or just ensure you will not delete files outside of proper system partition by executing part of command (for example when /system mounts in other location than /system_root). If you are not sure, execute "df" command and see last entry which should show you where system partition is mounted and adjust the command.
For some of you, who want to proceed with my advice. Please note, that I am not responsible for any problems you can cause on your device using my advice. It will surely not break your phone if done properly. if you don't understand what you do, please don't do it
Click to expand...
Click to collapse
or fastboot erase system can help, if someone lack knowledge
i still finding the root cause for this, if i can fix it i'll release new one asap

loipuru said:
or fastboot erase system can help, if someone lack knowledge
i still finding the root cause for this, if i can fix it i'll release new one asap
Click to expand...
Click to collapse
I never would have thought about such obvious solution. Thanks

so, can i still use this to flash older MIUI versions like MIUI 12?
i should just use fastboot erase system after wiping via twrp. right?

bluviper said:
so, can i still use this to flash older MIUI versions like MIUI 12?
i should just use fastboot erase system after wiping via twrp. right?
Click to expand...
Click to collapse
yeah,
i don't have time to rebase tree yet. so it'll preferred method for now

yea. i just tried. and it worked.
did a full wipe and reinstalled miui-globe ROM.
thanks

new update out:
changelog: fix /system missing

loipuru said:
new update out:
changelog: fix /system missing
Click to expand...
Click to collapse
Flashed but upon rebooting into recovery it lost access to storage and sdcard directories.

tlxxxsracer said:
Flashed but upon rebooting into recovery it lost access to storage and sdcard directories.
Click to expand...
Click to collapse
known issues, but it only happened on some roms, no problem on sparks and los as i tried
it's source issues which is really tricky to fix