Hi guys.
I've been an xda member for a while but i wrote very few posts, i usually found here or there something to fix the problem that was already reported and fixed, so no need to post until now.
I finally decided to try a custom rom on my xperia tablet Z (sgp321e2/b , so the pollux LTE 16GB model);
unlocked bootloader via official sony method; :victory:
extracted boot.img from the rom (aokp 4.2.2) and flashed via fastboot; :good:
booted to the cwm recovery, O.K.; :fingers-crossed:
wipe data/factory reset and <bum>: data partition can't be wiped.
At first i didn't noticed that, so i flashed the rom via recovery, but it took almost no time (so i guess it can't wipe but also can't write that). As a result, stuck in bootloop.
I thought it was smth wrong with the recovery that could not access the partitiion, so i tried the same process with CM10.1 from freexperia project, but with the same result.
I tried searching for similar issues, i only found 2 answers: one from a guy that did flash a rom for the lte model on a non-lte device (not my case), and one that had the exact same /data partition issue on a xperia z phone.
They both solved flashing back the firmware with Flashtool and (as suggested) 'trying again'.
So ok, I put the 10.1.1.A.1.253 unbranded firmware and at least the tab boots to stock again, but when i repeat the procedure to boot the recovery and wipe or install one of those rom, /data still can't be mounted or wiped so i'm stuck with stock (lol).
It must be smth very rare or smth extremely noobish, 'cause everyone seems to be fine just by doing all the steps i already did and have no issue with the /data partition...
Any suggestion?Is this a known issue? Anyone else experiencing this?
Thx in advance
Yorgan said:
Hi guys.
I've been an xda member for a while but i wrote very few posts, i usually found here or there something to fix the problem that was already reported and fixed, so no need to post until now.
I finally decided to try a custom rom on my xperia tablet Z (sgp321e2/b , so the pollux LTE 16GB model);
unlocked bootloader via official sony method; :victory:
extracted boot.img from the rom (aokp 4.2.2) and flashed via fastboot; :good:
booted to the cwm recovery, O.K.; :fingers-crossed:
wipe data/factory reset and <bum>: data partition can't be wiped.
At first i didn't noticed that, so i flashed the rom via recovery, but it took almost no time (so i guess it can't wipe but also can't write that). As a result, stuck in bootloop.
I thought it was smth wrong with the recovery that could not access the partitiion, so i tried the same process with CM10.1 from freexperia project, but with the same result.
I tried searching for similar issues, i only found 2 answers: one from a guy that did flash a rom for the lte model on a non-lte device (not my case), and one that had the exact same /data partition issue on a xperia z phone.
They both solved flashing back the firmware with Flashtool and (as suggested) 'trying again'.
So ok, I put the 10.1.1.A.1.253 unbranded firmware and at least the tab boots to stock again, but when i repeat the procedure to boot the recovery and wipe or install one of those rom, /data still can't be mounted or wiped so i'm stuck with stock (lol).
It must be smth very rare or smth extremely noobish, 'cause everyone seems to be fine just by doing all the steps i already did and have no issue with the /data partition...
Any suggestion?Is this a known issue? Anyone else experiencing this?
Thx in advance
Click to expand...
Click to collapse
Ok, after 2 days of failures i solved it just a few hours after posting the question :highfive:
To everyone experiencing the issue, you have to revert back to official SGP321 10.1.1.A.1.307 Unbranded, seems to be the only one working for me.
Cheers
No way CM 10.1 on Xperia tablet Z LTE?
Yorgan said:
Hi guys.
I've been an xda member for a while but i wrote very few posts, i usually found here or there something to fix the problem that was already reported and fixed, so no need to post until now.
I finally decided to try a custom rom on my xperia tablet Z (sgp321e2/b , so the pollux LTE 16GB model);
unlocked bootloader via official sony method; :victory:
extracted boot.img from the rom (aokp 4.2.2) and flashed via fastboot; :good:
booted to the cwm recovery, O.K.; :fingers-crossed:
wipe data/factory reset and <bum>: data partition can't be wiped.
At first i didn't noticed that, so i flashed the rom via recovery, but it took almost no time (so i guess it can't wipe but also can't write that). As a result, stuck in bootloop.
I thought it was smth wrong with the recovery that could not access the partitiion, so i tried the same process with CM10.1 from freexperia project, but with the same result.
I tried searching for similar issues, i only found 2 answers: one from a guy that did flash a rom for the lte model on a non-lte device (not my case), and one that had the exact same /data partition issue on a xperia z phone.
They both solved flashing back the firmware with Flashtool and (as suggested) 'trying again'.
So ok, I put the 10.1.1.A.1.253 unbranded firmware and at least the tab boots to stock again, but when i repeat the procedure to boot the recovery and wipe or install one of those rom, /data still can't be mounted or wiped so i'm stuck with stock (lol).
It must be smth very rare or smth extremely noobish, 'cause everyone seems to be fine just by doing all the steps i already did and have no issue with the /data partition...
Any suggestion?Is this a known issue? Anyone else experiencing this?
Thx in advance
Click to expand...
Click to collapse
Hi Riccardo,
i have the same problem (stucked on boot..i have followed the istructions for pollux on cyanogenmod wiki)
so i reverted my SG321 to stock 307...
No way to install CM 10.1 on our tablet ??
Thanks,
Maurizio
Related
Hi there,
Today I received my Xperia Tablet Z and sure enough, the first thing I did was flash a custom Rom
But my device wouldn't boot up anymore...
Basically I unlocked the bootloader via Sony's key, flashed a boot.img via fastboot and then flashed the Rom via the recovery.
All I got was a bootloop - regardless of which custom Rom I used (AOKP, Cyanogen stable, Cyanogen nightly, Cyanogen unofficial, ...)
I tried doing a factory reset but to no avail.
I manually checked for each delete / wipe option in the recovery, but the device simply would not boot further than the boot animation.
However, after some time I stumbled across a Rom that contained the TWRP recovery instead of CWM.
And this one asked me for a password when I booted.
"A password? What for?!"
Well, simply cancelling the request works.
But it seems that my whole problem had to do with that password request
As it turns out, the data partition was encrypted would not let me access it.
For some reason unknown to me, it was not wiped in CWM (some error popped up when trying to format /data).
TWRP allows for doing a format on this one ("full wipe" if my memory does not fool me) and voila - the tablet would boot!
So to sum it up:
After unlocking the tablet, there might still be an encrypted /data that can't be accessed by any custom Rom.
Wiping this /data solves the problem - and can be done via TWRP.
I just banged my head on that issue for 5 straight hours - downloading new custom roms, looking for similar bootloops, ...
Maybe this information will help someone
FrozenLord said:
Hi there,
Today I received my Xperia Tablet Z and sure enough, the first thing I did was flash a custom Rom
But my device wouldn't boot up anymore...
Basically I unlocked the bootloader via Sony's key, flashed a boot.img via fastboot and then flashed the Rom via the recovery.
All I got was a bootloop - regardless of which custom Rom I used (AOKP, Cyanogen stable, Cyanogen nightly, Cyanogen unofficial, ...)
I tried doing a factory reset but to no avail.
I manually checked for each delete / wipe option in the recovery, but the device simply would not boot further than the boot animation.
However, after some time I stumbled across a Rom that contained the TWRP recovery instead of CWM.
And this one asked me for a password when I booted.
"A password? What for?!"
Well, simply cancelling the request works.
But it seems that my whole problem had to do with that password request
As it turns out, the data partition was encrypted would not let me access it.
For some reason unknown to me, it was not wiped in CWM (some error popped up when trying to format /data).
TWRP allows for doing a format on this one ("full wipe" if my memory does not fool me) and voila - the tablet would boot!
So to sum it up:
After unlocking the tablet, there might still be an encrypted /data that can't be accessed by any custom Rom.
Wiping this /data solves the problem - and can be done via TWRP.
I just banged my head on that issue for 5 straight hours - downloading new custom roms, looking for similar bootloops, ...
Maybe this information will help someone
Click to expand...
Click to collapse
I usually just hit the thanks tab but feel I have to than you personally for this post. After hours of messing about I found this post, flashed the TWRP recovery, wiped data and was able to flash and boot my xperia..
Thank you for sharing this info..
For others searching you can get the twrp recovery in this rom http://forum.xda-developers.com/showthread.php?t=2383800
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
Hi people,
I hope I'm in the correct thread. On my SGS II (i9100) I managed to install the TWRP 3.0.2.1 (latest version i found in this forum).
So I can boot to Upload mode and Recovery without any problems.
For the installation i wiped "dalvik", "cache", "system" and "data".
For repartioning I used Heimdall-Suite and set the system to 1GB, data to 6GB and Preload to 512MB. (Was using CM12.1 previously with 1GB-system, 6GB-data and only 45MB preload)
Then started the install of the latest nightly build as of 2016-10-29.
After that I installed OpenGapps 6.0 pico also as of 2016-10-29.
After the installation i checked the contents with the linux-terminal within TWRP (great feature).
At the end I rebooted the phone.
The white Sasmung logo and text appears. Then the blue CyanogenMod logo appears and the white circle behind it keeps pulsating (boot animation)
But the phone is stuck in this situation. It never finished booting. Due to the fact, that i have no logs during this process (maybe this can be archived somehow?) I don't know where to start searching for the problem.
Thats the point where I think you can give me a hint.
In other threads I read about clearing dalvik again solved some problems. Other took out the battery for at least 5 mins.
Of course I tried all of this, and to install an other kernel (kernel-Lanchon-20160406-cm-13.0-i9100) which is IsoRec capable. Tried another nightly of CM13. But nothing helped me. The phone still is not booting.
Previously I have had CM12.1 on the device. There I only got the system to boot with Kernel_Dorimanx-V11.0b006-[16-07]-[28-07]-LP-SGII-GSSTUDIOS-TRIM-signed. All others also stuck in the boot animation loop.
Maybe this is a hint to my problem, unfortunatelly I don't know.
I really will appreciate your help in this situation.
Thanks in advance
CptAmerica
BTW.lease don't bother me for my english I'm from Austria and not used to write in english. But i hope i can point out my problem.
Solution for this Problem
Hi @ll,
due to the fact that I also posted this problem in the CM13.1 development thread I got good advises and the final solution for solving this problem.
Because I think other people might also have this problem I'd like to post the procedure how to solve the hanging boot loop issue.
Prerequisite:
For my luck I had a running Download Mode and a Running Recovery Mode
TWRP 3.0.2.1 installed on the phone.
Additional Information:
I was running CM12.1 on my phone with the kernel: Kernel_Dorimanx-V11.0b006-[16-07]-[28-07]-LP-SGII-GSSTUDIOS-TRIM-signed
This was the only kernel who managed to boot my phone with CM12.1. Maybe at this stage I already had my issue with the phone but the kernel bypassed it somehow.
Because also under CM12.1 no other kernel managed to boot the phone.
Procedure which caused the problem:
Due to the fact, the phone only bootet with the DorimanX Kerlen i thought why not updating to CM13.1 and get rid of the boot problem.
First I downloaded TWRP 3.0.2.1 and CM13.1 to the /sdcard01 partition.
I bootet in the DorimanX Recovery which was based on the CMR.
Whith this help I installed the new TWRP 3.0.2.1 which worked fine.
Rebooted to TWRP 3.0.2.1 and wiped /system, /data, /dalvik-cache /cache.
After that installed CM13.1 and OpenGapps Pico for Marshmellow.
Rebooted the device and here we are-> Hanging in the boot animation
I thought due to the fact that I used a partioning with only 43MB for the preload area once I installed CM12.1 this might kepping CM13.1 from booting.
Procedure which solved the problem:
After reading and trying a lot on the phone @the.gangster posted me a help to solve the problem.
I started a repartioning with the Heimdall-Suite with I9100_1GB-System_6GB-Data_512MB-Preload.pit which worked fine (I was thinking)
Then re-installed CM13.1 and again got stuck in the boot animation.
With the info from @the.gangster he told me, that most of the people which repartioning their device forgett to reformat the preload partition which keeps Android from booting.
So i started into TWRP 3.0.2.1 and selected "Advance"->"Terminal" which is a really cool feature, because you are in a full linux-terminal on your phone.
The preload partition is /dev/block/mmcblk0p12 (aka /dev/block/platform/dw_mmc/by-name/HIDDEN)
I fired of the following command:
Code:
mke2fs -t ext4 /dev/block/mmcblk0p12
which advices the phone to set up the ext4 filesystem on the given path, which later is mounted by the OS as preload area.
After that back to the main screen and then Reboot->System.
Now my phone took about 8-10 Minutes to start and I was back in Android with CyanogenMod 13.1 and a working phone!! :laugh::good::laugh:
I hope this might help you out there, if you have the same problem.
If you like to read the original thread this is the links: http://forum.xda-developers.com/galaxy-s2/development-derivatives/rom-cyanogenmod-13-t3223808/page629
Thanks for the hint as i gave up cm13 for Dirty Unicorns (which is great btw) for the same reason.
I repartitioned ny phone and get rid of the preload partition as I thought I didn't need it on cm13.
Now i know that first i need it and also need to reformat it...
But why?
Sent from my GT-I9100 using Tapatalk
Namoi said:
Thanks for the hint as i gave up cm13 for Dirty Unicorns (which is great btw) for the same reason.
I repartitioned ny phone and get rid of the preload partition as I thought I didn't need it on cm13.
Now i know that first i need it and also need to reformat it...
But why?
Sent from my GT-I9100 using Tapatalk
Click to expand...
Click to collapse
Hi @Namoi,
unfortunatelly I'm not a Android developer. So I'm not able to tell you the meaning of the preload partition. But @the.gangster - which helped me a lot in my case - seems to know whats this area is about.
Maybe he gets an info due to my mention of his name in this post, so maybe he will follow up and answer your question.
Bye
KaeptnAmerica said:
Hi @Namoi,
unfortunatelly I'm not a Android developer. So I'm not able to tell you the meaning of the preload partition. But @the.gangster - which helped me a lot in my case - seems to know whats this area is about.
Maybe he gets an info due to my mention of his name in this post, so maybe he will follow up and answer your question.
Bye
Click to expand...
Click to collapse
How, I know what this partition is : it was introduced by Samsung to allow the installation of Jelly Bean as the standard partition was too small to accomodate all the bloat ware they put in. So it shouldn't be used by other no Samsung based Rom. As I said, on Dirty Unicorns I removed it (well made it 0MB) and I have no issue, but as you pointed for CM 13 it seems it is needed... Why, I have no clue at all...
Yes, the partition was actively used on stock Samy-ROMs to incorporate all the Samsung addons.
And even if it is not being actively used by any non-Samsung stock ROM, at least the CM-ROMs I've seen on the Galaxy S2, still kind of checked the partition's presence or filesystem if present.
I never explored the exact reason, but I do know, if the preload partition is there but does not contain a filesystem (is not formatted), which is the case if a PIT-file changed the starting sector, it is very likely that the CM ROM will hang upon booting up. This might be kernel-related as - if I remember correctly - e.g. some DorimanX kernels didn't show that problem on the same ROMs. But the latter *do* use the preload partition for supporting dualboot.
I am not a friend of removing partitions completely anyway. Rather minimize them to e.g. 8MB. That will at least provide the space needed to put a filesystem on it.
That's also the method used by this great tool.
But for those who still use PIT-files, as @KaeptnAmerica did and who run into the problem, I created a modified TWRP-Recovery (IsoRec!) now, that provides the option to format the preload partition.
Hope it helps. @KaeptnAmerica: as you see, quoting worked
P.S.: By the way: reading the title of this thread just wanted to point out, that the issue of CM not booting when preload is not containing a filesystem is not related to what IsoRec-Recovery is installed or if there is one installed at all. This would also happen with no additional IsoRec-recovery is installed.
Its my daughters bog standard, cheap chinese MTK6580 phone (uhappy up580 if it matters)
It came with stock 5.0 a few years back so I flashed TWRP, rooted it, ported a CRdroid 5.1 rom for it and was working fine. Yesterday on boot every app refused to start, or stopped, or froze including stock launcher and settings so I couldnt do anything at all. Booted to TWRP and wiped cache and dalvik but although TWRP said completed, it hadnt.
So decided to wipe EVERYTHING including data and again TWRP said it had but upon reboot the faulty rom was still there, not working.
Tried to flash a backup that ended in tar error, fixed that and it flashed the backup fine, rebooted but it hadnt.
Tried to TWRP flash a new rom, said it had but it hadnt,
Used SPFlash tools to flash the stock 5.0 rom, THAT said it completed after the usual time and procedure, rebooted but it hadnt
Used SPFlash tools to completely format and wipe the phone which also said it had completed but it hadnt.
I CANNOT wipe this phone using any method I know of! or install or flash anything! Just this same custom rom that was fine for years and just went wrong. Does ANYONE know how I can somehow wipe this phone or flash a new rom? Tried flashing a TWRP with SP tools AND a TWRP .img and they all said completed but obviously, nothing did.... I've accidently bricked phones easier than I can deliberately wipe this one
Any help greatly appreciated.
emmc is weared out. therefore it is read only
aIecxs said:
emmc is weared out. therefore it is read only
Click to expand...
Click to collapse
Gah... exactly what I suspected but hoped not
cheers
EDIT: Ignore this!
It just worked this time...
Dear mods, this thread can be deleted.
Hi there,
i really need some help.
Got my hands on a xperia x compact today and it already was on latest stock.
So i unlocked it and flashed LineageOS 19.1
Everything was okay but i had some issues and decided to wipe and start over with lineage 18.1.
After 18.1 bootlooping, it automatically booted into TWRP and from there it hang on splash screen forever.
Also after a reset, it wouldn´t boot into TWRP.
So i tried erasing userdata and cache via fastboot...
After that, TWRP loaded up again but now it had the famous can´t mount data, cache, issue.
So i ended up with a device, that won´t format data, won´t boot any rom (automatically enters recovery mode).
I decided to flash stock via EMMA and accidentally flashed the oldest firmware from the list!
Why is it even on top???
I just noticed it booting up fine and all, but TWRP won´t recognize touch inputs (touch works in stock 7.0 though)
I guess it´s because of the old firmware i just flashed.
So i picked the latest version from the list but unfortunately it seems like it´s still on old android 7 firmware instead of oreo!
The version i flashed is 34.4.A.2.118 which corresponds to oreo, but it seems like something went totally wrong here.
It´s still on the old firmware somehow...
I´m not a noobie flashing phones and stuff but this really is 100% confusing and driving me crazy right now
I actually managed to get 34.3.A.0.252 flashed now, which is slightly newer but still 34.4.A.2.118 won´t upgrade...
Any help is very appreciated
Thank you very much