Galaxy S3 i9305T i9305 unable to boot, Bootloop when installing custom rom - Galaxy S III I9305 (4G LTE + 2GB RAM) Q&A, Help &

Hi
I have a GS3 i9305T. I can install and run any official rom without any problem up to 4.4.4. but when i install TWRP and then install any by any I mean every single custom rom on android 5.x.x it will just show the boot logo of CyanogenMod or nameless or any other one! nothing after that!
What i have tried is
Done factory reset before installing, Done after that, or didnt even do that.
installed rom with Gapps and without gapps
installed a fresh Stock rom and then installed the custom roms
tried couple of different Kernels as below
3 Jun 2015] [AGNi][CM] 03-06-2015 AGNi pureCM v4.4.5 I9305 (ULTRA SMOOTH)
[20 Apr 2015] [AOSP] [ArchiToolchain] [14/04/15] ArchiKernel V2.X
[21 Mar 2015] [CM12.0] Boeffla 3.0-alpha10 - 21.03.2015
[02 Feb 2015] HboKernel v0.3 - 02.02.2015 (NamelessRom 5.0)
I have done everything that i could so please as you know my problem is not the factory reset! please advise me what should i do?

did you install twrp 2.8.7.0? If yes, that one is faulty. Flash stock rom again, flash 2.8.5.0 and everything is working.

I have installed the rom using TWRP 3different version, Philz recovery, CWM none work!

you didn't answer my question though.

Hello shamid202,
please use this odin-flashable Recovery:
openrecovery-twrp-2.8.7.0-alpha17-i9305.tar

problem is data part format should be changed.

shamid202 said:
problem is data part format should be changed.
Click to expand...
Click to collapse
I have exactly the same problem, I try to flash SlimLP is booting but stuck on rom boot logo. I try to flash PAC rom same issue.
I use twrp 2.8.7.0 and openrecovery-twrp-2.8.7.0-alpha17-i9305.
 @shamid202 do you have resolved the issue ?

Solved for me
After having problem with weird usb cable, I finally success to install SlimLP F2FS Rom with this procedure:
Flash TWRP VERSION 2.8.5.0 recovery with heimdall (or odin) heimdall --RECOVERY twrp2.8.5.0.img --no-reboot
Reboot in recovery mode
Flash from recovery Twrp openrecovery 2.8.7.0 alpha17 zip
Reboot in recovery mode
Go to Wipe/advanced and format /system /cache /data partitions to F2FS
Then finally flash SlimLP F2FS ROM zip
Twrp 2.8.7.0 work but I was unable to flash alpha17 after installing this version ...
Recovery Thread http://forum.xda-developers.com/gal...covery-i9305-cwm-philz-twrp-versions-t2694249

Related

xzdr for cm12.1 or cr droid ub (Not tested on ub)

no i think i its time to help a bit because of
some people have issues with the cm recovery on cm12.1 roms
cm rec is not really good
some people want to use (flash) xposed or so
so here is my file (moded kernel ) for cm12.1 (also works on cr droid 02.08)
credits to
sony for the device z3tab comp lte because its the best 8inch tab
nut for the kernel repack and his xzdrec
cyanogen inc for the 06.08 nightly and the boot img
and the dev of ndr utills
Instrucktions
if you are on stock rom
1. flash cm or cr droid from dual recovery
2. flash gaaps
3.flash sgp621 kernel from attachments
4.boot to sytem
5. test to boot from system to recovery if it works all fine
6. if you see in step 5 the cm recovery boot device to fastboot
and unpack the twrp zip from attach and seleckt fastboot on flashtool then hotboot kernel or flash kernel select the twrp img and flash it now in twrp flash the attached cm kernel and reboot.
Anyone tried this yet?

Failed to flash any Custom Roms

i was using AICP on my S3 LTE
received OTA update message so I downloaded and tried to flash for a newer version as usual today.
however, after flashing the newest AICP Rom, I cannot enter into my system.
I wiped all data, even system data and flash it again, but same.
i am stucked in the animation logo.
i tried the following, all failed
1. flash newest version of TWRP by Odin, and flash AICP in TWRP
2. flash newest version of TWRP by odin, and flash CM 12.1 in TWRP
3. flash newest version of CWM by odin, and flash AICP in CWM
4, flash newest version of CWM by odin, and flash CM 12.1 in CWM
all of the above, i used factory reset after flashing, however, still stuck in the animation logo.
but then, i flash original SamSung S3 9305 firmware using Odin, I successfully enter the system again~
so i would like to know, in my case, what should i do if i would like to use custom rom?
thanks!
Hi ecorange,
next time do this:
wipe:
Code:
cache
dalvik-cache
system
then flash:
Code:
gapps
Aicp.zip
I hope I could help you
androidlovei9305 said:
Hi ecorange,
next time do this:
wipe:
Code:
cache
dalvik-cache
system
then flash:
Code:
gapps
Aicp.zip
I hope I could help you
Click to expand...
Click to collapse
hello,
thanks for your reply.
i followed your steps but still, i am just seeing the animation logo, my phone does not boot into the system....
but if i flash the stock firmware, i can enter the system and successfully root it........
i failed to enter the system from any Custom Roms.....
With AICP you must flash a extra kernel. It's in preview post of AICP
BlissPop 3.8 by Rodman01
androidlovei9305 said:
With AICP you must flash a extra kernel. It's in preview post of AICP
BlissPop 3.8 by Rodman01
Click to expand...
Click to collapse
i remembered i did not flash any kernels when i first tried AICP few months ago and it worked perfectly.
anyway, i tried
wipe
cache
dalvik-cache
system
then flash
gapps
AICP
Kernel <downloaded from http://forum.xda-developers.com/galaxy-s3/development-i9305/rom-aicp-8-0-t3053000>
reboot....
and ........ again, seeing the animated boot logo only.........
i cannot enter the system even i did a wipe and flash only AICP, without gapp....
anyone can help me please?!

Stuck at CyanogenMod

Hi everybody! I wanted a better battery life for my Z1 (1 screen hour at 75% :crying: ) so i flashed the CM11 latest snapshot, (as we all know, the LP builds has a very horrible battery management) and it worked, but when i switched from MX ROM to CM11 i lost my recovery (dual recovery) and it were replaced with CWM, i tried to install TWRP with some apps like Rashr, Flashify, ROM manager, Multirom manager and many others but it wasnt successful, and now im trying to flash a stock build of LP but flashtool gives to me this error:
- root this bundle is not valid -
I tried with a KK build but it was the same result. So I am stuck in CM, i dont know what more can i do... Can anyone help me?
The Bankshooter said:
Hi everybody! I wanted a better battery life for my Z1 (1 screen hour at 75% :crying: ) so i flashed the CM11 latest snapshot, (as we all know, the LP builds has a very horrible battery management) and it worked, but when i switched from MX ROM to CM11 i lost my recovery (dual recovery) and it were replaced with CWM, i tried to install TWRP with some apps like Rashr, Flashify, ROM manager, Multirom manager and many others but it wasnt successful, and now im trying to flash a stock build of LP but flashtool gives to me this error:
- root this bundle is not valid -
I tried with a KK build but it was the same result. So I am stuck in CM, i dont know what more can i do... Can anyone help me?
Click to expand...
Click to collapse
KK custom roms have recovery inside kernel. You have recovery in your FOTA or Recovery partition. The in-kernel recovery won't let you start Fota recovery, no matter what you try to install. Latest LP roms, as well as MM don't have recovery in kernel. So, you want to fastboot an LP kernel that has no recovery: fastboot flash boot boot.img. Then fastboot TWRP: fastboot flash recovery recovery.img. After that, you can boot into TWRP recovery and install whatever you want...
optimumpro said:
KK custom roms have recovery inside kernel. You have recovery in your FOTA or Recovery partition. The in-kernel recovery won't let you start Fota recovery, no matter what you try to install. Latest LP roms, as well as MM don't have recovery in kernel. So, you want to fastboot an LP kernel that has no recovery: fastboot flash boot boot.img. Then fastboot TWRP: fastboot flash recovery recovery.img. After that, you can boot into TWRP recovery and install whatever you want...
Click to expand...
Click to collapse
Thanks a lot! Ill try it

[C6903] - cant run new NOUGAT custom roms - bootanimation 2-3 sec and phone turns off

At the beginning, please forgive me the quality of my English.
Me and other friends using c6903 have posted on the forum about trouble with running Nougat ROMs:
- [ROM][7.1.X][27/07/17][STOCK-CAMERA][3.4 KERNEL][TESTING] LineageOS 14.1 - UNOFFICIAL
- [ROM] [7.1.2] [OMS] [OFFICIAL] [Honami] Resurrection Remix Nougat v5.8.3 [01/08/2017]
- [ROM] [7.1.2] [Substratum/OMS] [UNOFFICIAL] [Honami] Android Ice Cold Project 12.1
For example LinageOS 14.1.
I flashed build from 11/07 without any problems.
Everythings worked fine, but when i try to flash newest build I encountered a big problem.
Bootanimation continues 2-3 sec. and phone turn off [check plz video].
Then only the launch button was active.
Everything I do exactly the same as in 11/07 build.
Why rom can't run?
The situation applies to all the above versions.
Resurrection Remix Nougat from 28/06 booted fine too.
Newer versions not...
One of friends - MIcHiJK - suggested that this could be a problem with changing the screen for "fake".
Me and him changed screens probably for counterfeiting.
Maybe someone else did it and have this problem?
....but why build from 11/07 (LinageOS), 26/08 (RR) and 20/06 (ACIP) booted without any problems?? In my case change screen was earlier.
What have I done so far to solve the problem.
- used TWRP 3.0.0 and 3.0.2
- Always full wiped (a few times format internal storage using twrp too)
- flashed roms when using Cyanogenmod 12.1
- flashed roms when using stock .236
- restored software using EMMa and Flashtool, then root (kingroot), flashed twrp by fastboot, full wipe, flash rom - without result
- used others kernels referenced by creators roms (flashed after installation rom).
Nothing worked.
I know I'm not alone. Many guys have problem like me.
Is anyone able to give a solution?
May God bless guy which will solve our problems!
"https://youtu.be/sOBquHNlbzQ"
Hello to all ppl which had this problem.
Since I replace my broken original xperia z1 Display, I wasn´t able to boot any of the new Nougat rom releases.
I solved this problem with a new Kernel.
Super Lamic Posted this Kernel to test the Battery Life but with this Kernel the problem was solved and I was able to run the new Releases on my fake Display.
Kernel Link: https://mega.nz/#!RN1nFYRT!546WMDdM2ToJEeZlleKTjS-TdR54rkYiOGKUDDWQ-t0
Install new LineageOS build on your xperia z1 with TWRP 3.1 (with 3.0 it wasnt able to install the boot.img).
Before you reboot select images, boot and flash the boot.img.
Then the new build should run without problems.
On other roms like Resurrection Remix it endet in invinite boot so I was just able to run normal Lineage.
I hope it helped someone. Im still interested what the devs changed that causes this problem. And I hope there will be improvments in future that this problem wont happen anymore.
same problem for me like OP. Would be interesting whats the reason for this behaviour that some nougat roms don't run on phones with replaced display. for me some still run, but then i have the problem that recovery is not available.
For those wo will flash AICP maybe this solution will work in RR too.
In normal Lineage it worked when i flashed cm12.1 Nouagt Kernel after flashing LOS 14.1.
But for RR or AICP it ended in infinite boot. Here is how I managed to get it work.
1. Download AICP (Latest Version [2017/08/01]) then download AICP (Version 2017/06/20).
2. Delete 'boot.img' from the Latest Version zip and put the 'boot.img' from the older relase into the Latest
3. Boot into TWRP 3.1 or 3.0, Wipe all and flash your Latest AICP zip with the older boot.img.
4. Boot phone. The z1 will show you just the Sony Logo. I waited some Minutes and powered off with power + volume up.
5. Connect phone in fastboot mode on PC and flashed cm12.1 Nougat Kernel.
6. Type 'Fastboot Reboot', the phone Turns on with the newer Boot screen where xperia stands on the bottom. You will finally see AICP Boot Animation and after some time rom boots.
---------- Post added at 10:09 PM ---------- Previous post was at 10:07 PM ----------
Aaskereija said:
same problem for me like OP. Would be interesting whats the reason for this behaviour that some nougat roms don't run on phones with replaced display. for me some still run, but then i have the problem that recovery is not available.
Click to expand...
Click to collapse
Just Install Recovery via Fastboot. If you dont know how to do this you need to set up android sdk. You will find many tutorials in the internet.
MIcHiJK said:
Just Install Recovery via Fastboot. If you dont know how to do this you need to set up android sdk. You will find many tutorials in the internet.
Click to expand...
Click to collapse
really funny. sound good, doesn't work
Aaskereija said:
really funny. sound good, doesn't work
Click to expand...
Click to collapse
How did you installed the rom?
From which rom you came and which recovery did you used and how did you installed the recover?
different ways, but mostly with my standard custom-rom Tesla which is on Android 5.1.1. TWRP is on 3.1 which i install via cmd (fastboot flash recovery) cause build in recovery of tesla is broken.
Or i go over latest stock with dualrecovery, flash boot.img of the custom-rom (wich work) and then flash rom. but still recovery is gone after that.
@Aaskereija
I can tell you how I installed. I never lost my recovery. I came from xproject rom and I had nuts dual recovery. I flashed via fastboot advanced kernel, rebooted directly into inbuild TWRP 3.1, wiped all and flashed nougat rom. I had no recover so I flashed via fastboot official TWRP 3.0 and now I have a recovery. Since I installed TWRP one Time i never done it again. Everytime I flash a new rom it's still there. Maybe you try some different ways to install a nougat rom cuz it should work we all have the same device. Another question. Can you give me link to TWRP 3.1 for honami. I can't find TWRP 3.1 for z1 I used it just with advanced kernel. I just can find official TWRP on the internet witch is outdated
Guys, you don't have to create threads for this. I'll have an aftermarket display too, so I'll be forced to fix it anyway. And I have an idea what can be wrong...
MIcHiJK said:
@Aaskereija
I can tell you how I installed. I never lost my recovery. I came from xproject rom and I had nuts dual recovery. I flashed via fastboot advanced kernel, rebooted directly into inbuild TWRP 3.1, wiped all and flashed nougat rom. I had no recover so I flashed via fastboot official TWRP 3.0 and now I have a recovery. Since I installed TWRP one Time i never done it again. Everytime I flash a new rom it's still there. Maybe you try some different ways to install a nougat rom cuz it should work we all have the same device. Another question. Can you give me link to TWRP 3.1 for honami. I can't find TWRP 3.1 for z1 I used it just with advanced kernel. I just can find official TWRP on the internet witch is outdated
Click to expand...
Click to collapse
how do u installed it? fastboot flash recovery or else?
i was mistaken, its 3.0.2 not 3.1 if u still ned it, download
Aaskereija said:
how do u installed it? fastboot flash recovery or else?
i was mistaken, its 3.0.2 not 3.1 if u still ned it, download
Click to expand...
Click to collapse
Android Sdk put twrp.img in platform tools folder then open CMD in this foder, fastboot flash recovery TWRP.img.
I asked about twrp cuz in advanced kernel is TWRP 3.1 inbuild but I can't find just the twrp 3.1 IMG without kernel. Strange.

How to install TWRP

Nwver had problem like that, but I canno manage it on my own.
What I have:
rooted E1 Single (e2005),
kernel with Philx Touch,
zip with FalconSS Revamp R2,
zips with TWRP 2 and TWRP 3.
What I do:
Flash kernel with Philz.
Copy zips to E1.
Boot to Philz.
Flash FalconSS.
Flash either of TWRPs.
WIpe Cache and Dalvik.
Bootloop on Sony logo.
Should I use normal Falcon? (will try it in a moment)
Or maybe other stock firmware? (have 20.1.A.2.19)
All I want is working TWRP with support for Nougat.
Ok. Normal Falcon was what I needed. Now LOS14.1 is booting

Categories

Resources