Hi,
For about a few days, I can't flash any touchwiz based rom, even the ones I could flash without any problem before. After I flash any touchwiz rom, my phone goes into a bootloop cycle. Though I can boot into recovery and download mode with key combinations. I don't know when this happened for the first time but as far as I can remember, it would be after I flashed some 4.4 AOSP rom (could be Omnirom, I'm not sure though)
What I did to recover from boot loop:
- Wipe cache, wipe dalvik cache and reboot, no joy.
- Wipe cache, wipe dalvik cache, wipe data, reboot, no joy.
- Wipe cache, wipe dalvik cache, wipe data, wipe data/media, reboot, no joy.
- Pulled out the battery between these steps too.
At first, I thought something was wrong about the aroma installer itself because the phone was getting frozen during aroma installer setup screen, then I came up that it was caused due to my older CWM version, so I updated the recovery and it didn't freze again during installation.
And by the way, I've lost my efs partition during these processes, thankfully I've had a nandroid backup from a couple of months before.
Now I'm stuck with AOSP roms and the only way I can use a touchwiz rom is to flash the stock rom via odin. But I want to use the new leaked version based Note3 featured roms.
I've seen similar topics at S4 section but I couldn't be sure if I can do the exact steps for an N7100 international device.
I'm pretty familiar with linux system and I can use adb so I can provide any kind of information you need to diagnose this issue. Thanks in advance. Best regards.
HOW I SOLVED THIS PROBLEM
- Wiped everything (system, data, sdcard, of course internal sdcard)
- Flashed n7100 16GB pit file via odin
- Flashed stock rom via odin
- During these steps, I realized that my CSC code had been changed, I've corrected it acording to my country code
- Rooted my phone again
- Flashed CWM 6.0.4.3 recovery
- Flashed DN3 V3.1 rom
- Bingo, I successifully booted into DN3 rom but had no WIFI
- Flashed MJ5 bootloader
- Rebooted, then WIFI worked without a problem
- Setup my phone and did some restore
It's all good now. Thanks for everything, I hope these steps can help someone facing the same problem.
Guys, I really need some help.. Any idea about what might the problem be?
Sent from my GT-N7100 using XDA Premium 4 mobile app
Download HD wipe script,flash the script zip via cwm/philz then try installing the rom of your choice.
I found the script from tamirda's phoenix rom thread and is very useful:http://d-h.st/fWr
Full wipe cache and reset in recovery menu, clear everything, you should be up and running.
akp.ajinkya said:
Download HD wipe script,flash the script zip via cwm/philz then try installing the rom of your choice.
I found the script from tamirda's phoenix rom thread and is very useful..
Click to expand...
Click to collapse
Thanks for the reply. I flashed this superwipe script, then flashed DN3 rom but still I got stuck at Samsung Galaxy Note II screen boot loop. I really don't understand this. What am I missing? What would happen if I wipe the entire internal memory block, I mean the whole things, even the root partition too.. I'm thinking that maybe there's some file inside the root partition that prevents me to flash touchwiz roms or perhaps something wrong about touchwiz based roms' bootloaders.. I'm truely pissed..
(InsertNameHere) said:
Full wipe cache and reset in recovery menu, clear everything, you should be up and running.
Click to expand...
Click to collapse
Have you read my first message? I remember that I've mentioned I've done already what you ask me to do.. Believe me I wouldn't shoot a new thread if I could've solved my problem with such easy steps. I've already done so many wipes, including internal SD and whatsoever.. I'm really confused and NEED help. Thanks anyway..
I think you can go for the method you mentioned.But also give a try to start fresh i.e pit file flashing...wiping everything n installing stock rom then rooting,flashing custom recovery n then installing any TW custom rom.
Also give other TW based roms a try too.
Im having the same problem but after flashing kernels (e.i. saber & perseus).
Im currently running on Tigra rom. Is this a compatibility issue or im just missing something here too?
I came across flashing bootimg but this thread http://forum.xda-developers.com/showthread.php?t=1752270
is for One S, im not sure if will work on Note 2 & haven't tried it yet.
Any suggestions? help pls...
akp.ajinkya said:
I think you can go for the method you mentioned.But also give a try to start fresh i.e pit file flashing...wiping everything n installing stock rom then rooting,flashing custom recovery n then installing any TW custom rom.
Also give other TW based roms a try too.
Click to expand...
Click to collapse
Well, the problem is gone.
What I did was the things you said.
- Wiped everything (system, data, sdcard, of course internal sdcard)
- Flashed n7100 16GB pit file via odin
- Flashed stock rom via odin
- During these steps, I realized that my CSC code had been changed, I've corrected it acording to my country code
- Rooted my phone again
- Flashed CWM 6.0.4.3 recovery
- Flashed DN3 V3.1 rom
- Bingo, I successifully booted into DN3 rom but had no WIFI
- Flashed MJ5 bootloader
- Rebooted, then WIFI worked without a problem
- Setup my phone and did some restore
It's all good now. Thanks for everything, I hope these steps can help someone facing the same problem.
Happy to help you bro
Related
My T-Mobile Galaxy s4 M919 will not boot after any custom ROM flashes. I tried 4 different ROMs with success messages. As soon as I reboot my phone after the ROM flash, it's stuck at the Samsung Galaxy S4 logo and would not enter the "phone desktop". I can easily enter download mode and recovery mode without any issue.
Background: I rooted with Odin successfully. (Used both CWM and OUDHS with the same no-boot results after flashing any custom ROMs). I can restore back to stock and phone boot up fine but tried root again and then with custom ROM and it would not boot. Any help would appreciate it.
After flashing a rom, go into recovery, and erase stuff. Like cache and dalvik cache. Possibly even data
Sent from my SGH-M919 using XDA Premium 4 mobile app
Android_Monsters said:
After flashing a rom, go into recovery, and erase stuff. Like cache and dalvik cache. Possibly even data
Sent from my SGH-M919 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I did that after each ROM flash. 1. Wipe data/factory reset, 2. wipe cache part, 3. wipe dalvik cache. Did not fix the problem. No good. Please clarify "possibly even data". I am not sure which wipe is that.
anothersaddream said:
I did that after each ROM flash. 1. Wipe data/factory reset, 2. wipe cache part, 3. wipe dalvik cache. Did not fix the problem. No good. Please clarify "possibly even data". I am not sure which wipe is that.
Click to expand...
Click to collapse
using CWM:
*wipe data/factory reset
*wipe cache
*wipe, dalvik cache
*wipe system
*wipe sdcard (only if you have the ROMs you plan on flashing on your external sdcard, this will erase internal sd)
now flash your ROM of choice. reboot (will take 1-2min on first boot)
use cwm touch. what ROMs have you tried so far?
I am thinking you are flashing something not specific to the TMo S4, so your not getting the right kernel installed. Try installing a TMo specific kernel immediately after flashing a rom and see what happens.
Yeah, what ROMs have you tried already? Have you tried TWRP 2.5 recovery?
Sometimes it'll take up to 10 minutes to boot up (I haven't experienced this yet with the GS4, but I have with other phones). How long did you wait before determining it was just stuck?
I switched to PhilZ Touch Recovery a couple of weeks ago and have not had Any issues as I did before.
TWRP 2.5.0.2 was issue free for months, until I started flashing ROMs with Aroma.
Nothing but issues re Samsung splash screen freezes, different solutions working sometimes and sometimes not, having to ODIN back to stock on many occasions, having to wipe INTERNAL SD on many occasions, etc., etc.
PhilZ was the solution.
This is coming from a hard core TWRP guy......
Check the link in Red in my sig for PhilZ and other good stuff
dynospectrum said:
using CWM:
*wipe data/factory reset
*wipe cache
*wipe, dalvik cache
*wipe system
*wipe sdcard (only if you have the ROMs you plan on flashing on your external sdcard, this will erase internal sd)
now flash your ROM of choice. reboot (will take 1-2min on first boot)
use cwm touch. what ROMs have you tried so far?
Click to expand...
Click to collapse
Where do you "wipe system"? I see a format /system inside Mounts and Storage Menu. Please confirm.
DKYang said:
Yeah, what ROMs have you tried already? Have you tried TWRP 2.5 recovery?
Sometimes it'll take up to 10 minutes to boot up (I haven't experienced this yet with the GS4, but I have with other phones). How long did you wait before determining it was just stuck?
Click to expand...
Click to collapse
I have not tried TWRP 2.5 recovery yet. I mostly use CWM. I have waited 20+ minutes after flashing a custom ROMs but to no success.
I have done the following ROMs:
Insanity v1
VirginROM
stevessvt said:
I am thinking you are flashing something not specific to the TMo S4, so your not getting the right kernel installed. Try installing a TMo specific kernel immediately after flashing a rom and see what happens.
Click to expand...
Click to collapse
I did try the InFamous ROM for Tmobile s4. This ROM also has a kernal. Same results, stuck at Samsung Galaxy s4 Logo screen. It would not go anywhere after that.
Really needing help here.
anothersaddream said:
I did try the InFamous ROM for Tmobile s4. This ROM also has a kernal. Same results, stuck at Samsung Galaxy s4 Logo screen. It would not go anywhere after that.
Really needing help here.
Click to expand...
Click to collapse
Okay let's start over from scratch.
First off can you restore the stock ROM using your nandroid backup?
Second, I don't think you are properly wiping everything prior to flashing the new ROM. You need to wipe system, data, dalvik, and cache in the CWM wipe menu prior to flashing the new ROM.
Wipe all 4 things. Wiping any less than all 4 things will cause the problems you are experiencing.
Once you've done that, then flash the ROM.zip and reboot and it should work just fine.
anothersaddream said:
Where do you "wipe system"? I see a format /system inside Mounts and Storage Menu. Please confirm.
Click to expand...
Click to collapse
wipe = format
yes, format system in mounts/storage.
Skipjacks said:
Okay let's start over from scratch.
First off can you restore the stock ROM using your nandroid backup?
Second, I don't think you are properly wiping everything prior to flashing the new ROM. You need to wipe system, data, dalvik, and cache in the CWM wipe menu prior to flashing the new ROM.
Wipe all 4 things. Wiping any less than all 4 things will cause the problems you are experiencing.
Once you've done that, then flash the ROM.zip and reboot and it should work just fine.
Click to expand...
Click to collapse
I did exactly what you stated. Restored to stock. Rooted successfully. Wiped all 4 things. ROM flash stated success. Still NO good. Stuck samsung S4 logo. You think there is something wrong with the hardware???? The s4 does randomly reboot on stock.
anothersaddream said:
I did exactly what you stated. Restored to stock. Rooted successfully. Wiped all 4 things. ROM flash stated success. Still NO good. Stuck samsung g4 logo. You think there is something wrong with the hardware???? The s4 does randomly reboot on stock.
Click to expand...
Click to collapse
When I was flashing ROMs w/Aroma using TWRP 2.5.0.2, I would sometimes get Samsung boot screen freezes. The only way I could resolve this was by wiping Internal SD, in addition to the other wipes mentioned, and flashing the ROM again.
find stock kernel, flash the roms you want and flash the stock kernel after and see if you boot
Biker1 said:
When I was flashing ROMs w/Aroma using TWRP 2.5.0.2, I would sometimes get Samsung boot screen freezes. The only way I could resolve this was by wiping Internal SD, in addition to the other wipes mentioned, and flashing the ROM again.
Click to expand...
Click to collapse
I also tried your suggestion exactly what you stated. Restored to stock. Rooted successfully. Wiped all 4 things + format /sdcard (internal SD). ROM flash stated success. Still NO good. Still Stuck Samsung S4 logo.
Is there any custom ROMs I can flash using odin?
anothersaddream said:
I also tried your suggestion exactly what you stated. Restored to stock. Rooted successfully. Wiped all 4 things + format /sdcard (internal SD). ROM flash stated success. Still NO good. Still Stuck Samsung S4 logo.
Is there any custom ROMs I can flash using odin?
Click to expand...
Click to collapse
ODIN Samsung Stock Firmware.
Boot.
ODIN Custom Recovery.
(I use PhilZ Touch Recovery. Flashes ROMs flawlessly )
Boot.
Flash custom ROM afterwards.
If ROM doesn't have Root, then Root with CF-AUTO-ROOT by Chainfire via ODIN prior to installing Custom Recovery.
Then flash custom ROM.
Biker1 said:
ODIN Samsung Stock Firmware.
Boot.
ODIN Custom Recovery.
(I use PhilZ Touch Recovery. Flashes ROMs flawlessly )
Boot.
Flash custom ROM afterwards.
If ROM doesn't have Root, then Root with CF-AUTO-ROOT by Chainfire via ODIN prior to installing Custom Recovery.
Then flash custom ROM.
Click to expand...
Click to collapse
I did as you stated. I love Philz Touch recovery UI. Very nice. Unfortunately, did not work as well. It stated successfully. I tried 2 rom, Infamous S4 v.2.5 and also the VirginROM v2.3.1. Both stated successful flashed but would not boot into the phone desktop. Stuck for over 10 minutes on black and white "Samsung Galaxy S4" logo.
I will send you a nice Starbucks gift card if anyone can fix this problem.
anothersaddream said:
I did as you stated. I love Philz Touch recovery UI. Very nice. Unfortunately, did not work as well. It stated successfully. I tried 2 rom, Infamous S4 v.2.5 and also the VirginROM v2.3.1. Both stated successful flashed but would not boot into the phone desktop. Stuck for over 10 minutes on black and white "Samsung Galaxy S4" logo.
I will send you a nice Starbucks gift card if anyone can fix this problem.
Click to expand...
Click to collapse
I have no idea why it ain't working for you.
On the plus side, I don't know everything
If you ODINd Stock.
ODINd Recovery.
Did a Md5 Checksum match between the ROM file and your Download.
Wiped Internal SD.
Flashed the ROM......
and you're still having issues.......
I'm at a loss....
Try again is my only suggestion, and insure the steps taken are correct, including ODINing the proper files for your device.
Check & Double check
Including making sure you have a good usb cable, which sometimes can work and sometimes not....
If you haven't, try flashing from internal sd card. Maybe remove th external sd card just in case.
Hello, my name is Sebastian. First time I post here. I´ve been reading a lot here in Xda, but no posting before.
I have a little question for you all, experts, and I think its kinda simple but I can´t figure it out.
My N7100 was running fine with a stock rom (Android 4.1) and then flashed a custom rom, I think Phoenix Rom (Android 4.1) and working very fine too..
Now I wanted to flash a newer rom, and I've tried a lot, with no good results:
PHOENIX ROM V15 (ANDROID 4.3)
DR KETAN CUSTOM ROM V6.1 (ANDROID 4.3)
DN3 V3.1 (ANDROID 4.3)
HURRICANE V6.0 (ANDROID 4.3)
I can install them all very fine, but when I restart the phone, it get stuck at the Galaxy Note II N7100 logo.
My CWM is version 6.0.3.7 and I`m using Philz touch 5.15.0 (I've tried Philz touch 6 with the same results).
I tried installing a new radio with Odin, version DDUMJ9 Modem and still the same result, stuck at boot logo.
Its weird cause I can install very fine the custom rom PROBAM 5.0 (Android 4.3) and it don´t get stuck at the boot logo, and the system runs very fine. I also can install custom rom REVOLUTION HD 19.0 (Android 4.1 based).
So, my problem its with Android 4.3 and most of the custom roms based in that system that are holded here in Xda.
What can i do? What I'm doind wrong? What is missing?
I'll be very grateful for any help that you can give me.
Best regards.
you stuck at bootloader..what bootloader you use ?
try flash mj5 bootloader
sora9009 said:
you stuck at bootloader..what bootloader you use ?
try flash mj5 bootloader
Click to expand...
Click to collapse
Ok I will try that and post later...any link to download MJ5 bootloader?
Thank you
Ok I flashed MJ5 bootloader using joeldroid instructions (post found here in Xda) via Odin.
Then went to recovery, wipe cache, wipe full/factory reset and installed Phoenix ROM v15 and....still no luck, I'm stuck at the boot logo.
here its the post from joeldroid:
http:// forum. xda-developers .com/ showpost.php?p=46901976&postcount=741 (without spaces)
melankoly said:
Ok I flashed MJ5 bootloader using joeldroid instructions (post found here in Xda) via Odin.
Then went to recovery, wipe cache, wipe full/factory reset and installed Phoenix ROM v15 and....still no luck, I'm stuck at the boot logo.
here its the post from joeldroid:
http:// forum. xda-developers .com/ showpost.php?p=46901976&postcount=741 (without spaces)
Click to expand...
Click to collapse
Phoenix ROM V15 has some issues installing first time.. try complete wipe (keep installation zip on external SD card and format internal SD card in order to clean every thing) then try couple of times... alos select less apps and mods.. you can download app later..
I was on phoenix and gave me troubles installing but was able to in 2-3 attempts always...
ameyamg said:
Phoenix ROM V15 has some issues installing first time.. try complete wipe (keep installation zip on external SD card and format internal SD card in order to clean every thing) then try couple of times... alos select less apps and mods.. you can download app later..
I was on phoenix and gave me troubles installing but was able to in 2-3 attempts always...
Click to expand...
Click to collapse
Thanks a lot man, but I've tried to install Phoenix ROM like...7 times? And before every installation I do the following:
1. Wipe dalvik cache
2. Wipe cache
3. Wipe cache/full factory reset
4. Wipe and clean to install a new ROM (Philz touch option)
And then I perform the installation. Like I said in my first post this is happening to me with every Android 4.3 custom ROM, not just Phoenix ROM.
Do you have any other idea? Thanks in advance.
Best regards.
from what you said,you only do factory reset before install.
did you do factory reset after install ?
sora9009 said:
from what you said,you only do factory reset before install.
did you do factory reset after install ?
Click to expand...
Click to collapse
Yes I've done factory reset to every installation I've made, and I even done it more than one time several times.
I did a new test, I formatted the internal SD and did all the wipe steps and tried to install Dr Ketan ROM (android 4.3 based) with no luck.
After all the new tests I did, finally decided to go back to Android 4.1 and flashed Revolution HD 19.0 and now my phone is working flawlessly.
What is missing in my phone to be able to run Android 4.3? I've seen other people with the same problem, but none seems to give and straight answer.
Here's is an example of the same problem:
http:// forum.xda-developers.com / showthread.php?t=2556414
melankoly said:
Yes I've done factory reset to every installation I've made, and I even done it more than one time several times.
I did a new test, I formatted the internal SD and did all the wipe steps and tried to install Dr Ketan ROM (android 4.3 based) with no luck.
After all the new tests I did, finally decided to go back to Android 4.1 and flashed Revolution HD 19.0 and now my phone is working flawlessly.
What is missing in my phone to be able to run Android 4.3? I've seen other people with the same problem, but none seems to give and straight answer.
Here's is an example of the same problem:
http:// forum.xda-developers.com / showthread.php?t=2556414
Click to expand...
Click to collapse
hurmm..this is weird..
why don't you try mj5 leak stock rom..since mj5 leak is a stock rom..i don't think you will face any problem..
after done mj5 flashing, apply patch from here then flash custom rom.
if that also not working, i dunno what wrong with your phone.
sora9009 said:
hurmm..this is weird..
why don't you try mj5 leak stock rom..since mj5 leak is a stock rom..i don't think you will face any problem..
after done mj5 flashing, apply patch from here then flash custom rom.
if that also not working, i dunno what wrong with your phone.
Click to expand...
Click to collapse
Ok I will try that and I will comeback to post my results.
I will use this guide from Dr Ketan if anyone need the same as me:
http:// forum.xda-developers.com / showthread.php?t=2500823
Best regards
melankoly said:
Thanks a lot man, but I've tried to install Phoenix ROM like...7 times? And before every installation I do the following:
1. Wipe dalvik cache
2. Wipe cache
3. Wipe cache/full factory reset
4. Wipe and clean to install a new ROM (Philz touch option)
And then I perform the installation. Like I said in my first post this is happening to me with every Android 4.3 custom ROM, not just Phoenix ROM.
Do you have any other idea? Thanks in advance.
Best regards.
Click to expand...
Click to collapse
Have you tried zoot's script mega wipe ?
Android 4.3 I notice there's a change on the usb internal storage folder. If the MJ5 bootloader you have tried already, you can try this megawipe. It will wipe very clean your internal storage. Don't worry, it won't wipe your EFS
I always use this script everytime I want to jump to new Android base, and so far never give me a problem.
Good luck!
Sent from the corner of this rounded earth.
You must use a Super Wipe script before the factory reset when installing a 4.3 Rom for the first time.
sent from somewhere
Agree because they change the partitioning.
Sent from the corner of this rounded earth (N7105 v4.3, powered by LionROM)
You can Flash leaked 4.3 mi6 rom via pc odin and it will automatically wipe your all data and int storage. You still will have old boot loader. After that,you can try any 4.3 custom rom.
Sent from my GT-N7100 using Tapatalk
Hello,
I have a unique issue. I'm having a problem installing any custom rom on my t999 (tmobile). I have been using a custom rom for over a year. Always used TWRP. Started with Paranoid Android and for the last few months I've been using PAC-Man (nightly) roms. I was having gps lock issues, I decided to upgrade the modem to a leaked UVUEMJC, this fixed the gps lock issue. But after the reboot, I was stuck on bootloader screen. The only way I could get the rom to work was to backup the rom, flash the system and data, and after that, the rom would work until reboot. I did this a few times until it stopped working. My efs was corrupted, IMEI missing, To recover it, I went into download mode, and noticed in red Warranty bit =1. I used odin to flashed a rooted cf 4.3 samsung touchwiz rom (root66_TMO_T999UVUEMJC). All imei/efs issues were fixed. I decided to try installing a custom rom again, PAC-Man rom, it installed just fine, all EFS/IMEI info was intact, but at reboot, I got stuck on the CM bootlogo. This happens everytime. IF I recover a backup, it gets stuck on the boot logo. I'm using TWRP v2.6.3.
Anybody have any suggestions on how to fix this issue?
Thanks!
Install TWRP 2.6.3.1. Then take a Nandroid.
Next wipe /Data. Then flash your Custom Rom. Wipe Dalvik + Cache after the Flash. Reboot and report.
Perseus71 said:
Install TWRP 2.6.3.1. Then take a Nandroid.
Next wipe /Data. Then flash your Custom Rom. Wipe Dalvik + Cache after the Flash. Reboot and report.
Click to expand...
Click to collapse
Thanks for the reply Perseus71. I'll give it a shot!
acedik said:
Thanks for the reply Perseus71. I'll give it a shot!
Click to expand...
Click to collapse
Upgrading to the newest TWRP did the trick! Everything is working fine now. :good:
Thanks for the help!
I'm also having trouble flashing PAC-man.
SGH-T999LUVUBMK4
Factory reset everything, wiped SD card.
Tried latest TWRP and CWM.
Suggestions?
D
Donny Orbit said:
I'm also having trouble flashing PAC-man.
SGH-T999LUVUBMK4
Factory reset everything, wiped SD card.
Tried latest TWRP and CWM.
Suggestions?
D
Click to expand...
Click to collapse
You need to post info about the error
Sent from my SGH-M919 using Tapatalk
It says
E: Error executing updater binary in zip '/external
Error flashing zip '/external_sd/pac_d2tmo-night
I tried flashing the Rom that doc fixed specifically for the T999LTE for the CM10.1.2 also with no avail.
Same problem.
D
wipe Dalvik and Cache before trying the rom again. If
I tried:
different recoveries ( 2 versions of TWRP and 1 other ) , flashing different kernels, wiping cache/dalvik cache/factory reset like 100 times, 3 ROMS that used to work in the past
I didn't try flashing a rom with adb because I can't get it to work, but I don't know if it would help.
The only thing that works is stock ROM with stock kernel and stock recovery. ( ROM from EN MIUI forum )
Everything else just gets stuck on the boot animation ( the cyanogenmod/mokee/... logo )
btw: already tried googling, but all I found is how to fix the problem by installing stock everything but the problem is I hate the stock rom/recovery and If I flash a custom recovery and ROM after fixing it, it just gets stuck again.
Thanks in advance
As you already tried TWRP and not working, here is something u can try...
1)Flash Original miui for redmi 1s
2)then flash philz touch through stock recovery
3)then try to install CM 11 or other ROM
Not sure if it will work for you but you can try
BANG that THANKS button
lanadekat said:
I tried:
different recoveries ( 2 versions of TWRP and 1 other ) , flashing different kernels, wiping cache/dalvik cache/factory reset like 100 times, 3 ROMS that used to work in the past
I didn't try flashing a rom with adb because I can't get it to work, but I don't know if it would help.
The only thing that works is stock ROM with stock kernel and stock recovery. ( ROM from EN MIUI forum )
Everything else just gets stuck on the boot animation ( the cyanogenmod/mokee/... logo )
btw: already tried googling, but all I found is how to fix the problem by installing stock everything but the problem is I hate the stock rom/recovery and If I flash a custom recovery and ROM after fixing it, it just gets stuck again.
Thanks in advance
Click to expand...
Click to collapse
Had you tried to wipe cache, dalvik, data, and system before? I had my problem solved with custom rom
See here, focus what written at Edit section, ignore else. Just curios thou.. Need to be confirmed by others. Thanks
presetz said:
Had you tried to wipe cache, dalvik, data, and system before? I had my problem solved with custom rom
See here, focus what written at Edit section, ignore else. Just curios thou.. Need to be confirmed by others. Thanks
Click to expand...
Click to collapse
Could be the problem I asked the guy/girl who posted it how he fixed the problem. I'll also look for another non-CM based ROM and see if it works.
lanadekat said:
Could be the problem I asked the guy/girl who posted it how he fixed the problem. I'll also look for another non-CM based ROM and see if it works.
Click to expand...
Click to collapse
Just try what i said, wipe cache, dalvik, data, system,
As i recalled (i used twrp) reflash twrp. Leave it without OS
After reboot update twrp to 2.8.6.0 allow to install root, reboot.
And after you enter twrp recovery once again, do clean install as custom rom "how to install" instructed. Hope that help, might have to try other than cm, just for testing it.
Hit thanks if it work, else dont curse on me
presetz said:
Just try what i said, wipe cache, dalvik, data, system,
As i recalled (i used twrp) reflash twrp. Leave it without OS
After reboot update twrp to 2.8.6.0 allow to install root, reboot.
And after you enter twrp recovery once again, do clean install as custom rom "how to install" instructed. Hope that help, might have to try other than cm, just for testing it.
Hit thanks if it work, else dont curse on me
Click to expand...
Click to collapse
oh haha I didn't notice you were the same guyI thought you linked me to someone else's post xD I'll try it, I hope it works!
edit: thanks! reflashing the kernel, wiping everything, then fixing the permissions ( but not the SElinux permissions ) fixed the problem for me I'm back to android 12.1
I'll see if I can close the thread.
My Xperia ZL won't allow me to install a custom ROM.
Here are the steps I've taken.
1. Updated to 10.6.... (Lollipop fw) via Flashtool
2. Boots correctly, everything seems to work.
3. Flashed boot.img from Paranoid Android and went into TWRP to flash the ROM zip (wiped cache, system and data before).
Did step 3 to test the same for OmniRom too.
4. Phone boots, shows Bootanimation, shows Optimizing apps, then hangs after finish and does step 4 again.
Please help me, I could install custom ROMs on the device before, suddenly it does not work anymore.
Note: EVERYTHING works fine with Stock. Flashed stock ftf multiple times and tried these steps.
Thanks for your help
It seems to be a Bootloop. Try below steps;
1. Through TWRP wipe (system+cache+dalvic cache+data+android secure)
2. Install ROM.zip
3. Wipe cache+dalvic cache+data
4. Reboot
Hope the above steps helps you
Regards,
hitman-xda
@hitman-xda I've tried these steps, except for android secure.
What is that partition and what does it do?
Cannot find it in Advanced Wipe of TWRP.
Thanks
It is the mysterious part. Actually no one knows about it. Some says, it contains secured links/data of some apps.
If you are clean flashing ROM, that's means you have to wipe everything except storage part. That's the reason I mentioned it.
If you can't find it, just leave it
@hitman-xda So I've already done what you suggested, with no luck.
Guess I'm stuck on stock till someone helps me
Thanks for your reply
did you install de correct kernel?
maybe you should wipe everything, install the correct kernel and after that, install the custom ROM
i don't now if it will work, but at least try
I did fastboot flash boot boot.img (got it from ROM zip)
Then erased everything and flashed ROM.
No luck
Does that Paranoid Android was built for your phone?
Your phone loops from 'optimizing apps' , that means your phone is unable to load dalvic/art for the apps.
Also check weather PA ROM can be flashed over lollipop, if not then you have to downgrade an then try the same procedure.
Also you can download stock kernel with recovery, flash it and then directly try to flash your respective ROM.
Usually ROM.zip contains kernel and get flashed during installation of zip, just the thing is they can be flashable over some selective android versions.