Hi everyone, i swear i red every thread here but i had a problem yesterday and i haven't found a solution here.. So here is what: I unlocked bootloader and was ok, then i flashed a TWRP (3.1.1) and i got bootloop when i selected reboot system (wtf). So i tried to get back on TWRP and flash a custom rom. I flashed the Paranoid 7.3 and was ok, so i flashed pico gapps and i got error. Never happened before.. Anyway i reeboted my phone, it started but asked me a password for decrypted data.. I entered the correct pin but said it was wrong and told me to factory reset :-/ so i clicked to factory reset and it has rebooted in twrp, this time i cannot flash files. So via flashtool and xperifirm I resurrected my xperia X, but I'd like to try a custom rom.. Do you guys can suggest me something? Thank you.
Related
Hi Friends,
Model Number - GT-P7510
I recently rooted and installed the CM9 ICS nightly rom using the noob video instructions (This included rooting with Odin, installing CMW recovery 4.0.0.4, then I flashed the ROM cm-9-20120624 Nightly and finally flashed GAPPS-ics).
I over clocked using the CM9 settings and everything worked perfectly for about a week, it was great. Then it just crashed while I was reading my email and began to bootloop. After reading for similar errors I rebooted to recovery and tried wiped the cache and dalvic cache, I wiped data and factory reset several times but nothing worked, always the same bootloop. I re flashed the same ROM and still nothing, after a while the boot screen would simply freeze instead of bootloop.
Then I connected to my PC, and did this to no avail. In fact it simply added to the problem by adding a yellow warning triangle while attempting to boot so I did the Oden thing again like the first time I rooted however I installed CMW version 5.5.0.4 instead thinking it might help but it hasn't.
One last point, when I attempt to wipe data/factory reset the tablet seems to freeze and attempt to reboot rather than say something like "success" as it would during a cache wipe. This maybe normal or it maybe the problem! who knows?
On that point, I would be very grateful if some of you could help get me to the point when my PC recognises the tablet so I can reflash a new ROM.
Thanks in advance,
Karl
I once got the same problem. The only thing that helped was to flash back the stock rom via Odin with the pit file. And don't forget to do a hard reset after flashing the rom. I'll just stick to the stock rom until the official update is getting released.
Sent from my GT-P7501 using xda app-developers app
Questions go in the Q&A section
I think the best way is still to do factory reset, go back to the stock ROM first and try custom HC ROM until the official ICS is released.
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
Hi,
well yesterday i took my elephone and updated the phone , see : https://forum.xda-developers.com/el...m-11-08-lineageos-14-1-android-7-1-2-t3654592
the update went thru wihtout any issues. but:
- sim card did not get recognized
- some media app issues
so i thought , ok i'll do a factory reset, let's see if this solve the sim card issue.
well, the drama come's in here after the factory reset from the phone i'am in the boot TWRP loop and don't have a chance to flash something to the phone.
i guess that the factroy reset writes a file on the phone that causes the phone allways to boot into recovery, so is there a chance to delete this "file" ?
or does someone know this "file" ?
TWRP 3.02.8 and also tried to flash the beta 3.1
some hint's how i can solve this issue would be awesome.
cheers from germany
i had the same issue
the steps are
-first flash android 6 to the phone
-boot the phone with android 6 and you will see the SIMM is working
-flash the TWRP-3.0.2-8-P9000.img
-flash the lineage_p9000-ota-ec5aeedfbd.zip
-install gapps on it
this must work !!!
in my case it did
Michael
Hi,
thanks for your answer.
I ' am not able to flash the Phone with SP flash tools, because the phone reboots constantly and dont cares about sp flash.
also if i try to flash android 6 via TWRP the phone still rebbots.
so i' am stuck here.
Hi all i need some help here really! i installed CWM 4.0.4.6 installed oden, flashed my xcover with cwm booted in cwm installed CM10.0 then Gapps stucked a long time on cyogenmod logo so rebooted in recovery wiped factory and reset cleared partisions and cleared dalvik cache booted up and worked now i dont have network coverage tried vladir 4.4.4 tried other roms still no network, and with my stupidity never made a backup of my stock rom so im basically f##ked like i understand i needed to make a backup of my baseband and efs file so how the hell can i fix this maybe a stock firmware or rom? if so where can i get one im from South Africa, tried Sammobile site for stock rom or original firmware but you have to be a premium user to download there if someone could maybe give me a link or some guidance i will be more than happy?
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