Related
My TMo springboard became almost useless, so - with TWRP installed - I decided to reformat system, data and cache, in the hope that the external SD would suffice to boot out of or mount a new image. No go.
I am now stuck in a loop, as follows:
- Huawei main logo
- Original lock screen
- slide to unlock
- message: "encryption unsuccessful... Data on your tablet no longer available... To resume using your tablet you must performance à factory reset...", which I opt for (choice named "reset tablet")
- Huawei mediapad logo
- teamwin splash screen
- TWRP trying to mount all sorts, but fails on all, of course
- back to Huawei mediapad
- back to Huawei main logo... and repeat all of the above
Any way I could break this cycle, by making an image available to TWRP? How? I don't seem to be able to use any touch screen or buttons to stop and a better change the options of TWRP. It just keeps trying to mount the default assumed partitions, nowhere to be found...
Sent from my SGH-T999 using Tapatalk 2
netfortius said:
My TMo springboard became almost useless, so - with TWRP installed - I decided to reformat system, data and cache, in the hope that the external SD would suffice to boot out of or mount a new image. No go.
I am now stuck in a loop, as follows:
- Huawei main logo
- Original lock screen
- slide to unlock
- message: "encryption unsuccessful... Data on your tablet no longer available... To resume using your tablet you must performance à factory reset...", which I opt for (choice named "reset tablet")
- Huawei mediapad logo
- teamwin splash screen
- TWRP trying to mount all sorts, but fails on all, of course
- back to Huawei mediapad
- back to Huawei main logo... and repeat all of the above
Any way I could break this cycle, by making an image available to TWRP? How? I don't seem to be able to use any touch screen or buttons to stop and a better change the options of TWRP. It just keeps trying to mount the default assumed partitions, nowhere to be found...
Sent from my SGH-T999 using Tapatalk 2
Click to expand...
Click to collapse
If you have TWRP installed you can simply download one ROM (CM10, CM10.1 or AOKP) in zip format and flash it from TWRP.
Just follow instructions on the DEV board.
GuZuRa said:
If you have TWRP installed you can simply download one ROM (CM10, CM10.1 or AOKP) in zip format and flash it from TWRP.
Just follow instructions on the DEV board.
Click to expand...
Click to collapse
Thank you. This is what I was hoping to hear
Would that work with an image from the external SD card (i.e. would the TWRP "see" the SD card and search for the zip file on it)? I am asking vs just trying it, because I only have one microSD, which is presently in my SGIII, so I thought of checking this before I start backing up my SD, clean it up, getting the CM 10.1, putting it on ... )
Thx again!
netfortius said:
Thank you. This is what I was hoping to hear
Would that work with an image from the external SD card (i.e. would the TWRP "see" the SD card and search for the zip file on it)? I am asking vs just trying it, because I only have one microSD, which is presently in my SGIII, so I thought of checking this before I start backing up my SD, clean it up, getting the CM 10.1, putting it on ... )
Thx again!
Click to expand...
Click to collapse
Replying to myself - I did copy the zip file to the microSD, but TWRP keeps trying to mount - at least apparently, to me - only the "known" partition (/data), then just fails and the mediapad goes back into reboot. Is there a sequence of keys that force TWRP to stop, and point it to the microSD, instead?!?
Any pointers will be appreciated.
R: Springboard w/out system or data
netfortius said:
Replying to myself - I did copy the zip file to the microSD, but TWRP keeps trying to mount - at least apparently, to me - only the "known" partition (/data), then just fails and the mediapad goes back into reboot. Is there a sequence of keys that force TWRP to stop, and point it to the microSD, instead?!?
Any pointers will be appreciated.
Click to expand...
Click to collapse
Try this:
1 reinstall TWRP with after_silence automated installer (shouldn't be necessary but... who knows?)
2 turn completety off MP by pressing on/off switch for a while (MP will shortly vibrate and turn off)
3 format a microsd in fat32 with a PC windows or linux
4 put the zip file of one of the ROM in dev board on the SD through the PC
5 insert microsd into MP
6 boot into TWRP. From device turned off, turn it on pressing on/off switch and volume up and keep volume up pressed until you see TWRP logo
7 reinstall Rom following instructions in the Dev board
Let me know....
Inviato dal mio Huawei MediaPad con Tapatalk 2
GuZuRa said:
Try this:
1 reinstall TWRP with after_silence automated installer
<snip>
Click to expand...
Click to collapse
Thank you for the reply. I pretty much already did all the steps you previously posted, except for "1." (reinstalling TWRP). I did a search for after_silence automated installer, but could not find any links to such - could you, please, post one?
Thx...
netfortius said:
Thank you for the reply. I pretty much already did all the steps you previously posted, except for "1." (reinstalling TWRP). I did a search for after_silence automated installer, but could not find any links to such - could you, please, post one?
Thx...
Click to expand...
Click to collapse
And I just noticed that TWRP continues running OpenRecoveryScript every time, which ends up trying to mount /data (unsuccessfully), wiping cache, reformating ext4fs, end then rebooting ...
netfortius said:
And I just noticed that TWRP continues running OpenRecoveryScript every time, which ends up trying to mount /data (unsuccessfully), wiping cache, reformating ext4fs, end then rebooting ...
Click to expand...
Click to collapse
One more update - I was able to get the system enough to run a:
$ fastboot flash system system.img.ext4
which worked just fine, but upon reboot TWRP takes over and starts again ... mount /data ... failure ... reformatting ...
Any ideas here on how to break this cycle?
huawei boot loop, fastboot mia
I followed the after silence cm install steps but failed at using fastboot to install the twrp image
adb connects fine & triggers a reboot into fastboot, then fastboot can't communicate so I installed the twrp recovery via goomanager
booted into twrp, made a backup, wiped system / cache / data (oops?)
tried to install cm10.1 and it said error in file
tried to reboot into recovery and now stuck on huawei logo, fastboot still kaput
anybody know why fastboot won't communicate or what I can try next???
update:
got back into twrp by holding power and vol up buttons until it reset, then releasing power while continuing to hold vol up
it appeared to loop several times then booted into twrp
Formatting the data partition was the culprit, methinks. I managed that, too.
You need to flash the third bootimg from After Silence´s Toolkit, not CWM and not TWRP. Then you can flash stock roms via a dload folder on the sdcard. Reflashing the already installed Comec v2 lite caused the aforementioned encryption error and before ending with an unrooted stock rom i tried CleanICE v1.5. Worked. Whether this rom is buggy or there just went something wrong during install, it didn´t contain the system app "networklocation.apk", so no wifi or 3g based localization would work, only gps, which is unavailable in my home. So i installed TWRP again and could successfully flash AOKP. Flashing AOKP directly after bricking wouldn´t fix the brick.
I was using my phone and all had been working fine for ages. It was in my pocket for a while and when i took it out to use it I saw that it was on the boot animation of CM11. My phone was already on when I last used it so I had assumed it had crashed. I took the battery out and turned the phone on again but it got stuck on the CM boot animation. The last time I turned on my phone before that was when I flashed a supersu zip file to make my root work as I was having some problems. After flashing the supersu zip and told my CWM recovery to restart the system, it prompted me to "fix root" or something like that, and I clicked yes and it booted normally. That was the last time it booted normally before being stuck as it is now. First thing I did after it got stuck was go into recovery and reflash my current rom ( a CM11 snapshot) I then got faced with a status 7 error and so couldnt flash the rom. So then I flashed multiple other CM11 roms, none of which worked, so I flashed a CM10.2 stable rom which worked. I then got faced with the fix root before reboot thing and so I clicked yes. Still had the stuck booting thingy. I tried many things, flashing kernals roms gapps etc and nothing made a difference. I wiped cache, dalvik cache and no difference. I even wiped the system and tried to flash roms but only the 10.2 one would work, still got a status 7 with the CM11 ones. When I wiped my data however and flashed CM 10.2, it booted. I still couldn't flash the CM11 roms though even after a factory reset. So I have the reason to believe something in the data is wrong, not cache system or anything like that. What could it be? I don't want to have to lose all my data in order to be able to use my phone again, even then, something is still wrong as my phone won't flash CM11 roms anymore. So my questions are;
What things could have caused this?
Can this be a problem from flashing the supersu zip (a root issue)
Is it possible to somehow view or copy the internal data on a computer (since I cant get into the operating system), and this would allow me to get all my pictures contacts music etc anything so I can use my phone by wiping data?
Thanks, sorry this is quite long and probably hard to understand whats going on, but help is appriciated thanks
Don't fix root if you wish to use SuperSU instead builded-in cm superuser. Also try to flash via Odin latest recovery. TWRP should be fine. You can mount partitions from recovery level to download data to your computer. Of course if it still exists. If not, if they are corrupted you need to flash stock ROM and repeat whole cm11 adventure again. If Odin successfully flash the stock then it's a chance your partition layout and user data are untouched.
____________________________________________
P3110 / I9300 / I9100 / NEXUS 5 / iPAD2
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,
First I apologise for not having made a back up of my filesystem, I had grown overconfident from previous successful projects ;-/
I have unlocked the phone and installed TWRP recovery. I then used SUPERSU to root the phone under TWRP. After SUPERSU the phone did not boot, it stayed on the WARNING BOOTLOADER UNLOCKED splash for over an hour and did not boot after a reset.
I read through the forums and looked for a kernel to try as I had read that the OS may be damaged, and I wanted to flash a ROM in any case. I read to clean the boot partition before flashing so I did this. The kernel I tried was Squid. This made the phone display "fall through from normal boot mode". So I tried Cyanogen Mod 14, which put the phone on a very rapid bootloop cycle (about every 15 secs), then tried Squid Kernel R22B which put the phone on a long (about 8 minute) bootloop cycle.
Not sure what else I can do. I don't want to give up on the phone as it still mostly works (it has a bootloader, recovery and a file system). I have tried to find a stock ROM to install but proving difficult to track down - links seem to be down)
I apologise if I have got any technical terms wrong. I hope you can help!
Thanks,
Caroline
Caroline300 said:
Hi,
First I apologise for not having made a back up of my filesystem, I had grown overconfident from previous successful projects ;-/
I have unlocked the phone and installed TWRP recovery. I then used SUPERSU to root the phone under TWRP. After SUPERSU the phone did not boot, it stayed on the WARNING BOOTLOADER UNLOCKED splash for over an hour and did not boot after a reset.
I read through the forums and looked for a kernel to try as I had read that the OS may be damaged, and I wanted to flash a ROM in any case. I read to clean the boot partition before flashing so I did this. The kernel I tried was Squid. This made the phone display "fall through from normal boot mode". So I tried Cyanogen Mod 14, which put the phone on a very rapid bootloop cycle (about every 15 secs), then tried Squid Kernel R22B which put the phone on a long (about 8 minute) bootloop cycle.
Not sure what else I can do. I don't want to give up on the phone as it still mostly works (it has a bootloader, recovery and a file system). I have tried to find a stock ROM to install but proving difficult to track down - links seem to be down)
I apologise if I have got any technical terms wrong. I hope you can help!
Thanks,
Caroline
Click to expand...
Click to collapse
Assuming you've the Lineage 14 zip in your internal storage or micro sd,. Enter TWRP, select wipe, advanced wipe, check system data cache and dalvik, swipe to wipe. Now you've clean wiped your phone.
Then go "install", select the Lineage zip and flash it.
Hi DroidFreak32, thank you for your help. The phone is now booting for the first time since it's "adventure".
Hi,
Unfortunately the phone is still in the boot logo screen. It stayed on the Lineage logo for 2 hours. I have powered off and rebooted once more, and it is still in the boot logo screen now (1 hour later). I'll wipe and install again and post an update.
Hi,
I reflashed Lineage, same problem. I did notice that each time I installed a zip file, SUPERSU asked me to install it prior to reboot to root the phone and I have always hit Yes. On the final flash, I powered off the phone when it prompted me to install SUPERSU, and the phone booted normally. Very nice design on the mod, I like the way the apps are displayed alphabetically. Good work Lineage Team!
Hey all, so it appears that I screwed my phone, I am not sure how.
I was running LineageOS, and wanted to update to Android 10 one, so I followed the steps, and I think I screwed the sideloading part, so... long story short now when rebooting from OrangeFox RecoveryProject it says no OS detected, and when it boots it says encryption unsuccessful, I tried wiping and installing DisableForceEncryption_Treble_v17.2 and restarting, and the same thing happens.
I tried to flash through recovery both, and did not work:
https://xiaomifirmwareupdater.com/firmware/beryllium/
https://xiaomifirmwareupdater.com/archive/vendor/beryllium/
And when trying to flash through miFlash it doesn't work:
I go to fastboot in poco, hit refresh in miflash, it shows a device in the list, but the phone goes dark with 'something key to shutdown` written in the top left corner and if I hit the flash button nothing happens.
Can anyone assist with that please?
kishikaisei said:
Hey all, so it appears that I screwed my phone, I am not sure how.
I was running LineageOS, and wanted to update to Android 10 one, so I followed the steps, and I think I screwed the sideloading part, so... long story short now when rebooting from OrangeFox RecoveryProject it says no OS detected, and when it boots it says encryption unsuccessful, I tried wiping and installing DisableForceEncryption_Treble_v17.2 and restarting, and the same thing happens.
I tried to flash through recovery both, and did not work:
https://xiaomifirmwareupdater.com/firmware/beryllium/
https://xiaomifirmwareupdater.com/archive/vendor/beryllium/
And when trying to flash through miFlash it doesn't work:
I go to fastboot in poco, hit refresh in miflash, it shows a device in the list, but the phone goes dark with 'something key to shutdown` written in the top left corner and if I hit the flash button nothing happens.
Can anyone assist with that please?
Click to expand...
Click to collapse
This happened to me when I accidentally deleted the OS when flashing the latest MIUI 11 build (using TWRP). THIS IS HOW I FIXED IT.
Find a full firmware of whatever you wanted to flash, either Lineage or MIUI 11. Then flash via your recovery (you said you have orangefox). Use an external sd card, external USB or HDD since you technically wouldn't have access to your internal data. After flashing, same process as most updates, clear cache and dalkiv. Then flash a newer DFE (if you still want to decrypt, there is a page here in xda with it. Or go to miui forums Happybuddhist, the mod there, made a new one prebuilt with Magisk). Then reboot into recovery to make sure you keep your custom recovery. Once booted to recov. Boot to system. Should fix the issue.
You could check my guide here on how to unbrick your pocophone:
https://forum.xda-developers.com/poco-f1/how-to/unbrick-flashing-stable-rom-pocophone-t3901152
mecoromeo said:
This happened to me when I accidentally deleted the OS when flashing the latest MIUI 11 build (using TWRP). THIS IS HOW I FIXED IT.
Find a full firmware of whatever you wanted to flash, either Lineage or MIUI 11. Then flash via your recovery (you said you have orangefox). Use an external sd card, external USB or HDD since you technically wouldn't have access to your internal data. After flashing, same process as most updates, clear cache and dalkiv. Then flash a newer DFE (if you still want to decrypt, there is a page here in xda with it. Or go to miui forums Happybuddhist, the mod there, made a new one prebuilt with Magisk). Then reboot into recovery to make sure you keep your custom recovery. Once booted to recov. Boot to system. Should fix the issue.
Click to expand...
Click to collapse
I tried that, now I am a step forward I think, I flashed the stock firmware I found, and installed the latest stock ROM, rebooted (doesn't say no os anymore), but the only thing I see is a DELETE ALL DATA button and at the bottom 'Encryption was interrupted and can't be completed. As a result, the data on your phone is no longer accessible.
To resume using your phone, you need to perform a factory reset. When you set up your phone after the reset, you'll have an opportunity to restore any data that was backed up to your Google account.'
Darklouis said:
You could check my guide here on how to unbrick your pocophone:
https://forum.xda-developers.com/poco-f1/how-to/unbrick-flashing-stable-rom-pocophone-t3901152
Click to expand...
Click to collapse
I have an issue with the MiFlash part, it seems that it doesn't work as I mentioned...
Aight all, formatting data partition to ext4 worked, now it is booting
kishikaisei said:
Aight all, formatting data partition to ext4 worked, now it is booting
Click to expand...
Click to collapse
Works now?
mecoromeo said:
Works now?
Click to expand...
Click to collapse
So I had an OS-less phone that don't get recognised in MiFlash, and I had orangeFox recovery.
The steps to fix were:
- Flash a full stock Firmware
- Flash the stock ROM
- Flash DFE
- Format data to ext4
- Reboot and it works
So thanks all for your help