I can't get my GT-N7100 to boot any Android 7.1 custom rom.
I used to install lots of roms earlier like Android 5,6 custom roms, then I went back to rooted stock again a few months ago.
Recently I tried to install Android 7.1 with the traditional steps: wiping everything (system/data/cache/dalvik/internal storage) then I install the rom and gapps, but I couldn't get any rom to boot. They all stuck on the rom boot logo playing without proceeding to the rom itself. Yet, when I restore my twrp backup of the stock rom it works fine.
I even tried to install android 6 yet it didn't boot as it used to do before, the same logo stuck thing happens without any progress.
Any idea how to fix that ? what could be the reason behind that ?
Should I reinstall a stock rom and re-root it again?
I can't find a good reason for what I have regarding that problem.
I have: GT-N7100 with the following:
OS: wesam.othman ROM 4.4.2 stock rooted rom.
Recovery: twrp 3.0.2
Kernel: AGNi pureSTOCK N7100
Boot loader version: N7100XXUEMJ5
SD Card: 32 GB
I'm using a script that swaps storage so I have nothing on my device internal storage.
Thanks in advance.
Fixed by doing the following:
Installing an original 4.1.2 stock unrooted rom.
re-rooting again using cf auto root.
installing custom recovery
installing a 4.4.2 modem
then finally installing the 7.1 rom
Related
Hi,
I've rooted and unlocked my t989D. To do that I pushed recovery-clockwork-5.0.2.7-hercules.tar via odin and then flashed SGH-T989_UVLH1_Stock_Deodex_Rooted_signed and Tmo_SGH-T989_UVLE1_radio to be at at 4.0.4 ROM and radio.
Now I want to upgrade to cm 10.2. I tried flashing it, and it required a newer radio, so i flashed Tmo_SGH-T989-UVMC6_radio. Then I reflashed cm 10.2 and the installation completed, but I only get a boot loop with the CM sign. I figured it was because I was using an old recovery. So I tried to flash a newer CWM (recovery-clockwork-touch-6.0.3.1-hercules), and that failed, so instead I pushed the latest TWRP (openrecovery-twrp-2.6.3.0-hercules.tar) via Odin. I'm in the same position as with the older version of CWM: I can boot recovery, I can successfully flash 10.2, but I get stuck in a boot loop with the CM sign. Can someone correct me? Id appreciate it if you could correct my logic as well plz.
Update:
I pushed the old CWM back (5.0.2.7), then flashed an older version of CM (9.1) and it got stuck in boot loops as well. I then flashed the stock 4.0.4 ROM back and it gets stuck in boot loops (during samsung logo). I then pushed TWRP 2.6.3 back and reflashed the stock 4.0.4 rom ROM and it boots
Basically, the only combination that well allow a full normal boot is TWRP 2.6.3 + stock 4.0.4 rom (SGH-T989_UVLH1_Stock_Deodex_Rooted_signed)
Update 2:
Solution seems to be a dark side super wipe http://forum.xda-developers.com/showthread.php?t=1477955
So far, this allows me to get 9.2 working. Haven't figured out how to get 10.2 going yet.
Install latest twrp recovery then use superwipe zip file (that is mention in your archive post) than install your rom.
As far as about your boot loop issue wipe your internal and external card than just put rom installation files in it.
Sent from my SGH-T989 using XDA Premium 4 mobile app
(I've been flashing quite a lot ... but unfamiliar with this device)
A friend asks me to help to move from with his Stock v2.3.6 to a customed 4.3 (since 4.4.x isn't 100% yet...).
So I got a Recovery on it and flashed latest superSU1.86 (is it compatible ???) to get root.
Afterward I can't flash some 4.3 ROMs (CM10.2, Slimbean4.3), all "aborted" in many recoveries (CWM 6.0.4.4, 6.0.3.7 & TWRP 2.6.3.0, 2.6.1.0).
I did all the wipes/factory-reset/systems/data ... Finally I just restore the Stock-backup so he can still use the phone for now.
At least, it's still rooted with a TWRP on it.
What did I do wrong ?
Thanks.
Update: flashed stock 4.1.2 then went to Slim4.3 without issue with TWRP 2.6.1.0
Hello, a friend of mine installed a custom rom at my lg g3 android phone. The rom is ressurrection remix. I accidently dirty flashed an older version of the same rom, I had 5.1.1 r6 and I flashed 5.0.3, and now neither adb works nor download mode due to killswitch. The only thing it does is show the old rr boot image. It's on a bootloop and since it doesn't open I don't know how to fix it. Can someone tell me what should I do?
Can you use the button combo to boot into TWRP? If you can get into TWRP then just flash the ROM you want and be sure to follow the rom threads instructions before flashing of course.
hi guys
so I tried installing Dot OS V5.1 on my a70q, I flashed vbmeta and then twrp using a guide on XDA and I can boot twrp and install the rom with no errors but after rebooting my phone boots into download mode and the only way I can fix it is by flashing the stock rom using odin
I also tried lineage 18.1 but it has the same problem
(bootloader is unlocked, flashed gapps arm64 android 11 pico version with both roms, I can root my device using twrp and stock rom by flashing magisk with no problems it happens only when I try to install a custom rom)
any help is appreciated
hi guys
so I tried installing Dot OS V5.1 on my a70q, I flashed vbmeta and then twrp using a guide on XDA and I can boot twrp and install the rom with no errors but after rebooting my phone boots into download mode and the only way I can fix it is by flashing the stock rom using odin
I also tried lineage 18.1 but it has the same problem
(bootloader is unlocked, flashed gapps arm64 android 11 pico version with both roms, I can root my device using twrp and stock rom by flashing magisk with no problems it happens only when I try to install a custom rom)
any help is appreciated