Hboot: 2.10
Radio 1.13.11.1105
Recovery: Twrp 2.7.0.8
S-on
About a year ago I bricked my phone. Now I'm trying to salvage it to have something to play around with. Here's the run down
-Wiped entire phone by accident (no longer has an OS!)
-Phone was stuck in boot loop
-When trying to fastboot cm-11, I was getting E:unable to mount /sdcard
-Was unable to mount internal sdcard to format it in Windows
-Flashing cm-11 in TWRP would fail due to E:unable to mount /data
-Somehow I have gotten my phone back to where I have TWRP installed and can mount sdcard in adb and it is recognized in Winddows
-reformatted internal sdcard
-after reformat attempted to flash cm-11. Now i'm getting md5 error
-downloaded cm-12
-attempted to flash cm-12, it failed. Tried a second time, it was successful
-Now, when i flash a rom in Twrp it fails the first 1-2 times. Eventually the rom successfully flashes
-after the rom flashed, I choose to reboot system and install Su
-When booting into the rom, phone gets stuck at HTC boot screen
What am I doing wrong? What would cause the rom not to boot after successful install?
Take pics of the failed installs and post em. Try a RUU. That should get you back to a working phone from where you're at.
down2mars said:
Hboot: 2.10
Radio 1.13.11.1105
Recovery: Twrp 2.7.0.8
S-on
About a year ago I bricked my phone. Now I'm trying to salvage it to have something to play around with. Here's the run down
-Wiped entire phone by accident (no longer has an OS!)
-Phone was stuck in boot loop
-When trying to fastboot cm-11, I was getting E:unable to mount /sdcard
-Was unable to mount internal sdcard to format it in Windows
-Flashing cm-11 in TWRP would fail due to E:unable to mount /data
-Somehow I have gotten my phone back to where I have TWRP installed and can mount sdcard in adb and it is recognized in Winddows
-reformatted internal sdcard
-after reformat attempted to flash cm-11. Now i'm getting md5 error
-downloaded cm-12
-attempted to flash cm-12, it failed. Tried a second time, it was successful
-Now, when i flash a rom in Twrp it fails the first 1-2 times. Eventually the rom successfully flashes
-after the rom flashed, I choose to reboot system and install Su
-When booting into the rom, phone gets stuck at HTC boot screen
What am I doing wrong? What would cause the rom not to boot after successful install?
Click to expand...
Click to collapse
The reason you're getting hung up when you boot is due to being S-on. You have to install the kernel separately from the ROM, depending upon the ROM. Hit the top link in my sig and read the section on S-on kernel flashing. My recommendation would be to gain S-off.
Bingo!
Magnum_Enforcer said:
The reason you're getting hung up when you boot is due to being S-on. You have to install the kernel separately from the ROM, depending upon the ROM. Hit the top link in my sig and read the section on S-on kernel flashing. My recommendation would be to gain S-off.
Click to expand...
Click to collapse
Yeah, so it was a long day, but i'm finally up and running. It ended up being a combination of issue stemming from me flashing an unstable kernel. I was only able to get the stock RUU to flash. I flashed the boot.img separately like you said and then booted into recovery to flash the zip and, voila! I had to wipe and format my data partition to get rid of a "Decrypt Storage" lockscreen, but everything is up now.
Thanks!
Related
So i've posted pieces of this in other threads assuming i knew what the problem was, but nobody has been able to help me so far so i'm posting the whole saga anew.
First off, my phone:
LazyPanda S-OFF
HBOOT:1.12.111
RADIO-1.12.11.0809
I was running MeanRom 4.8 with TWRP 2.3.0.1
Like so many others i tried to OTA update just to get stuck at the recovery screen on reboot. I then found out that i had no ROM installed. I tried to wipe (cache, dalvik, system, etc) and flash a new ROM but i kept getting FAIL messages in TWRP.
"Formatting and mounting partition...
e:error in /sdcard/meanrom-ics-v49-jewel-ltevo.zip
(status 1)
error flashing zip '/sdcard/meanrom-ics-v49-jewel-ltevo.zip'
updating partition details"
I figured it might be a botched DL so i did it manually, MD5 checked out after copying to the mounted device. Attempted to flash the clean DL and i got the same error message. I nandroid restored an old stock rooted ROM I had and it installed just fine. After booting up to the system ROM for the first time I immediately got an "Internal storage is low" error. Checked and after a clean restore (no apps installed, fresh out of the box...) i only have ~200MB free in the app storage section (out of 1.92GB). I can't fathom what's taking up all the other space, nothing seems to be there. Because of this i can't install Titanium, Rom Toolbox, or anything else that may be remotely useful. I tried fixing permissions and re-wiping, re-restoring and i got the same thing.
I tried to flash the TWRP 2.2.2.0 image from recovery thinking this was the problem and got this message:
"updating partition details
E:unable to open ums lunfile 'sys/class/android_usb/android/f_mass_sto.....
Formatting cache...done
Formatting Data... done
Using rm -rf on .android_secure
Updating partition details
E:unable to open ums lunfile 'sys/class/android_usb/android/f_mass_sto.....
E:unable to open zip file."
And THEN i tried to ABD flash the TWRP image through fastboot with "fastboot flash recovery openrecovery-twrp-2.2.2.0-jewel.img" then 'fastboot flash boot openrecovery-twrp-2.2.2.0-jewel.img' and got this error:
"FAILED (remote partition is not allowed to be flushed!)"
So, i'm stuck with a device that loads a stock ROM, cant flash a new recovery or ROM, and cant' install anything useful because it's full after a restore. Does anyone have any suggestions how to clean/resore my partitions through ADB or a script? Your advice is much appreciated.
I can't help, but I suspect you'd have better luck posting this in the TWRP thread.
I'm wondering if fastboot erase cache would help here. I've seen that command used I think to clean a partition, but it may have been for something else. Sorry, this is a bit over my head. Hope you get help.
hurled from my AOKP'd Evo LTE. Enjoy.
You might have to re lock and run the RUU and then unlock and flash twrp, 2.3 has issues with the partitions for some reason so stick to 2.2
Try updating to the latest twrp. The latest is 2.3.1.0 not 2.3.0.1.
2.3.0.1 had issues which you can read about here
http://www.pocketables.com/2012/10/...for-htc-evo-4g-lte-fixes-rom-flash-death.html
It's been updated already? Cool
om4 said:
It's been updated already? Cool
Click to expand...
Click to collapse
Yeah, it fixes the mounting of the sdcards and the flashing rom problem
You may also want to get the 1.12.2222 hboot from the unlimited site. It has fastboot commands enabled.
I noticed you tried flashing TWRP to both the recovery and boot partitions...Do you get the same error when you flash to just recovery? TWRP should not be on boot.
Sent from my EVO LTE
Hi,
My battery ran flat on my I9100 International GS2 I plugged it in and turned it on, it started to boot and then shut down. I left it to charge to 100% and now when I turn on I get bootloop around the Samsung logo. I suspect it's corrupted my bootloader and/or device partitions.
I'm running Stock+Root XXLSJ with Philz CWM 3.00 recovery (based on CWM 6.0.1.5)
When I boot into CWM - I get message: "E:Can't open /cache/recovery/last.log"
When I try to mount /cache it fails with similar message. (I also cannot mount /data. The others are OK)
When I try to wipe cache partition it fails to format it (hangs for about 10 mins saying "formatting", and then reboots my phone)
When I try to factory reset it fails to format /data (hangs for about 10 mins saying "formatting", and then reboots my phone)
So I suspect my /data and /cache are corrupt and need to be recreated.
How can I recreate these partitions?
I thought reflashing CWM might stick them back if they are missing - I tried a couple of different versions. No luck. Same errors.
I thought I'd take the opportunity to upgrade to CM10.1 RC2 - But I can't flash ROM in CWM - it fails with "Installation aborted (Status 7)"
I think I need to flash via ODIN and click the "Re-Partition" option unfortunately CM ROMS can't be flashed in with ODIN! Arrrgh!
So I think I need to flash another stock ROM via ODIN with re-partition option, then flash CM via CWM. It's a bit of a pain, do you think this should work (is that what repartition option does) or is there some other easier/better way?
Thanks
-KENT
As you've already tried dirty flashing (without wipe) your kernel (which rarely works, but worth a shot anyways), yeah, back to stock via Odin & restore backup or reflash rom/kernel & start again if you don't have recent backup.
Will this work ? It should. One bit of advice tho, I noticed you're planning to repartition.
Don't.
At least not in the first instance. Do a normal Odin flash of stock & see how that goes before you go down the repartition route. Doing that when not necessary seems to cause more bricked phones than every other cause put together.
I had a NT that was running CM11 well.
It ran CWM 6.0.4.5 from internal memory.
Decided to try CM12.1
Wiped cache and delvik
Installed cm-12.1-20151117-SNAPSHOT-YOG7DAO1K6-acclaim.zip and GAPPS
CM12.1 booted but ran very poorly. Tried various things. Each time I installed
there was a message when exiting CWM "Root access possibly lost. Fix?".
At first I responded no, then finally Yes. Since them Android won't boot.
It always boots to recovery now.
Tried again after updating to CWM_6.0.4.8_chrmhoffmann.zip
No luck.
Installed TWRP 2.6.3.1 and tried to install various versions of CM.
During the install I get error messages, Unable to mount '/bootdata'.
If I try to mount /bootdata directly with TWRP it fails. Even tried to create
the folder with Terminal.
Guidance is appreciated.
So I got boot Android to boot again. Created a bootable SD with TWRP v2.8.5.2.
Replaced the recovery.img in a v2.6.3.1 .ZIP file with v2.8.5.2 image.
Loaded the zip so TWRPv2.8.5.2 now loads from Internal Recovery.
CM12.1 and gapps install and load with this TWRP but it behaves poorly.
Lots of pauses and a few spontanious reboots.
Reloaded cm-11-20141112-SNAPSHOT-M12-acclaim.zip and gapps. Seems to run
cleanly.
Wish CM12.1 would behave.
Boot loop with Nook Tablet Acclaim 16gb
I tried installing the latest snapshot: cm-12.1-20151117-SNAPSHOT-YOG7DAO1K6-acclaim.zip
I used this gapps: open_gapps-arm-5.1-pico-20150923
This is the recovery: cm-12.1-20151117-SNAPSHOT-YOG7DAO1K6-acclaim-recovery
I first downloaded and used the tablet to install this snapshot. Continuous boot loop.
Then I tried the usual manual mode erasing everything that needed it and still continuous boot loop ???
Is there something that I am doing wrong ??????
I had to revert to the previous snapshot and everything is back to normal.
HELP ?!?!?!?!?!?
nandroid123-
I copied http://techerrata.com/file/twrp2/acclaim/openrecovery-twrp-2.8.5.2-acclaim-sdcard.img over the recovery.img of my bootable sd.
Wiped/FactoryReset and installed CM with it. It fixed my no load of Android problem for both CM11 and CM12.1 but CM12.1 was not stable so I reverted to CM11 (cm-11-20141112-SNAPSHOT-M12-acclaim.zip).
I then installed http://techerrata.com/file/twrp2/acclaim/openrecovery-twrp-2.8.5.2-acclaim.img internally.
Boot looping
So no resolution for the boot looping on this latest snapshot !??!?!?!
nandroid123 said:
So no resolution for the boot looping on this latest snapshot !??!?!?!
Click to expand...
Click to collapse
Is your device boot loop to recovery? If so, see http://forum.xda-developers.com/showthread.php?p=21381141#post21381141 for potential cause and solution.
Digimax my 16gb Acclaim will boot loop when this: "" cm-12.1-20151117-SNAPSHOT-YOG7DAO1K6-acclaim.zip "" is installed.
When I revert back to the previous snapshot it works normally ??????
I will check out your link.
Thanks
Dennis
ETM said:
CM12.1 booted but ran very poorly. Tried various things. Each time I installed
there was a message when exiting CWM "Root access possibly lost. Fix?".
At first I responded no, then finally Yes. Since them Android won't boot.
It always boots to recovery now.
...
Installed TWRP 2.6.3.1 and tried to install various versions of CM.
During the install I get error messages, Unable to mount '/bootdata'.
If I try to mount /bootdata directly with TWRP it fails. Even tried to create
the folder with Terminal.
Click to expand...
Click to collapse
So here is the trick, I actually needed both.
Start with TWRP (SD version) to cleanup the system for clean install, etc...
Then, boot CWM, use its menu system to remount the bootdata partition <-- I think there was a typo thats tripping things up there
Then, boot with TWRP again, and get your installs in.
You can load a copy of Superuser from the SD while you're in there to be certain its rooted.
Hi guys,
Having a bad time setting up my S7 Edge (international model).
End goal is to have it rooted with a Lineage OS ROM.
Successfully flashed TWRP (3.1.1.0) using Odin3 (v3.12) and had no issues booting into TWRP and looking around.
Issues began when I tried to wipe the internal storage in preparation for a new ROM; I got errors along the lines of "unable to mount /data" invalid directory, "unable to mount /system" etc, and the wipe would fail.
Following another user's guide I formatted my /data partition to ExFat (plan was to then format it back to Fat4, which supposedly fixes the issue), however this froze the phone. I was able to reboot it after leaving it a few hours, however now the phone just freezes on the TWRP logo when I try boot into recovery.
I have reflashed TWRP to no avail.
From what I've read online, flashing a new ROM via Odin might recreate all required partitions (namely /data) ? Issue with this is I can only find .zip, not .tar ROM's as required by Odin.
Have I just turned my phone into a brick ?
Any suggestions on what to do next would be greatly appreciated !
Many thanks,
Pron
i had the TF201 running on Cyanogenmod kitkat but it was getting slow and some apps needed a new verision of android.
As i hade no further upgrade path through Cyanogen mod i "downgraded" to Hairybean https://forum.xda-developers.com/showthread.php?t=2407248 as a starting point for upgrading as all ROM how-to's were advising a bootloader upgrade.
i got hairybean recovery+bootloader & JB installed and working successfully, then proceeded to try to upgrade to Zombipop.
Made two mistakes that i'm aware of.
i didn't do a backup of the working system i had. (dumb)
i installed TWRP 2.6.3 which was the latest version listed on the TWRP website for the TF201 https://dl.twrp.me/tf201/ instead of the reccomended 2.8
somewhere along the line i messed something up and found myself in the following situation
i have Android cardhu-user bootloader <1.00 e> released by "ww_epad-10.6.1.27.1-20130711
and at that poiint i also had TWRP recovery 2.6.3 installed
No OS, the tablet dropped straight into recovery mode.
TWRP recovery 2.6.3 was asking me for a password. i have never had a password on this machine and TWRP was not previously asking for this prior to my attempt at installing zombipop.
if i cancel that request then i can't mount any storage in order to try install anything further. The internal file structure is there but it's not showing any files
"Storage: internal storage (0MB)
i cannot enter sideload mode
Errors read: cannot find partition size for /misc / staging /data /boot /recovery
and cannot mount cache.
i assume files are there but are encrypted and cannot be accessed without password
Back in bootloader mode, with fastboot i then tried to flash TWRP 2.8.5.1 blob file ( which i have subsequently found on another site) which i was able to do.
and after getting into that it was no longer asking me for a password but
i can't do a factory reset ( wipe, data, cach and dalvik) prior to trying to flash a new ROM. i just get a load of errors about being unable to mount /system /cache and /data. this makes me wary of trying to flash anything else. it's like what ever the issue that was prompting me for a password previously, is still there. the only difference is with 2.8.5.1 i can actually mount external cards now, though i still cant start ADB sideload properly it reports unable to mount /data
Ultimately i'd like to get it on any rom greater than KitKat which was the last working CynogenMod I had. But right now i'd just settle for having it working on anything at all again.
i'd be grateful for any advice.
<update> using the advanced wipe functions in TWRP I think i have sorted the problems with the /system /cache and /data folders. they are no longer giving errors.
stopping for night now though and coming back to this tomorrow with a fresh head.
Harani said:
i had the TF201 running on Cyanogenmod kitkat but it was getting slow and some apps needed a new verision of android.
As i hade no further upgrade path through Cyanogen mod i "downgraded" to Hairybean https://forum.xda-developers.com/showthread.php?t=2407248 as a starting point for upgrading as all ROM how-to's were advising a bootloader upgrade.
i got hairybean recovery+bootloader & JB installed and working successfully, then proceeded to try to upgrade to Zombipop.
Made two mistakes that i'm aware of.
i didn't do a backup of the working system i had. (dumb)
i installed TWRP 2.6.3 which was the latest version listed on the TWRP website for the TF201 https://dl.twrp.me/tf201/ instead of the reccomended 2.8
somewhere along the line i messed something up and found myself in the following situation
i have Android cardhu-user bootloader <1.00 e> released by "ww_epad-10.6.1.27.1-20130711
and at that poiint i also had TWRP recovery 2.6.3 installed
No OS, the tablet dropped straight into recovery mode.
TWRP recovery 2.6.3 was asking me for a password. i have never had a password on this machine and TWRP was not previously asking for this prior to my attempt at installing zombipop.
if i cancel that request then i can't mount any storage in order to try install anything further. The internal file structure is there but it's not showing any files
"Storage: internal storage (0MB)
i cannot enter sideload mode
Errors read: cannot find partition size for /misc / staging /data /boot /recovery
and cannot mount cache.
i assume files are there but are encrypted and cannot be accessed without password
Back in bootloader mode, with fastboot i then tried to flash TWRP 2.8.5.1 blob file ( which i have subsequently found on another site) which i was able to do.
and after getting into that it was no longer asking me for a password but
i can't do a factory reset ( wipe, data, cach and dalvik) prior to trying to flash a new ROM. i just get a load of errors about being unable to mount /system /cache and /data. this makes me wary of trying to flash anything else. it's like what ever the issue that was prompting me for a password previously, is still there. the only difference is with 2.8.5.1 i can actually mount external cards now, though i still cant start ADB sideload properly it reports unable to mount /data
Ultimately i'd like to get it on any rom greater than KitKat which was the last working CynogenMod I had. But right now i'd just settle for having it working on anything at all again.
i'd be grateful for any advice.
<update> using the advanced wipe functions in TWRP I think i have sorted the problems with the /system /cache and /data folders. they are no longer giving errors.
stopping for night now though and coming back to this tomorrow with a fresh head.
Click to expand...
Click to collapse
Is easy. You have to reset everything through fastboot, bootloader, recovery, system literally everything. Then flash stock rom to recover stock everything, like stock recovery and stock system. Then you are good to go rooting again and so on