EDIT: Reposted to a more appropriate forum.
I tried installing several different ROMs onto my cursedAT&T phone (Note 3 N900A). I managed to downgrade to Android 4.4.2 and root the phone (from the current OEM-supplied OC3). I had different results for each ROM I tried:
cm-13-20151101-UNOFFICIAL-hlte.zip - Immediately produces a "failed" message trying to install from SafeStrap 3.75 hlteatt, because my phone is hlteatt and not hlte.
MagMa_NX_UX10_Ultimate_XDA.zip - Trying to install from Safestrap: progress bar freezes at 0% done.
RR-N-v5.8.2-20170309-hlte.zip - Installs successfully, but won't boot. First try reboot just stops on a black screen. 2nd reboot gives me the menu seen when booting with Vol Up + Home held down. (Is this the AT&T's firmware "bootloader?")
I used Safestrap to perform a Wipe of everything except my MicroSD card in the ROM Slot (#1) I was using before each ROM installation attempt. Any suggestions on getting any of these working? From reading other's experiences, it appears that some are successfully using some custom ROMs with this model phone.
In this forum its not normal to use Safestrap .
Custom roms are flashed as per the roms instructions generally via TWRP .
You should ask in the forum for your model .
Thanks. I reposted there and edited the original post here to say so.
u cant flash roms on safetrap, its only for flashing custpm recovery and then u flash custom rom
You may need to wipe the data partition to let roms boot properly on first boot
Related
Hi guys. Not new to rooting but new to my AT&T S4. I rooted it tonight with Motochopper and installed CWM recovery. Downloaded and tried to flash a ROM, and it simply didn't work. Then I tried Beanstalk 4.2.2, and it downloads, but then when I rebooted it, it gave me the yellow triangle unauthorized software message. So I pulled the battery and finally got it to boot into recovery, then installed the back up I had from the stock OS. My question is two fold-what's causing this and if I download a ROM with the Loki patch, will that bypass the error message I'm getting. I searched the forums but am not understanding what was written. I'm pretty confused, any help would be greatly appreciated.
chokem said:
Hi guys. Not new to rooting but new to my AT&T S4. I rooted it tonight with Motochopper and installed CWM recovery. Downloaded and tried to flash a ROM, and it simply didn't work. Then I tried Beanstalk 4.2.2, and it downloads, but then when I rebooted it, it gave me the yellow triangle unauthorized software message. So I pulled the battery and finally got it to boot into recovery, then installed the back up I had from the stock OS. My question is two fold-what's causing this and if I download a ROM with the Loki patch, will that bypass the error message I'm getting. I searched the forums but am not understanding what was written. I'm pretty confused, any help would be greatly appreciated.
Click to expand...
Click to collapse
So, to sum up development in this forum for the last 3 months: The ATT version of the S4 has a locked bootloader, which is a fancy way of saying ATT and Samsung don't want custom software on their phone partitions. To keep people from installing custom ROMs, their bootloader requires a verified signature present in the ROM to actually allow the device to boot.
An individual found a way to trick this verification process, and created a patch for it called LOKI.
When a ROM is "Loki'd" it contains this workaround for the verification process in the bootloader, allowing custom software to be installed.
To answer your question, when you root your phone and install the recovery (TWRP or OUDHS): a ROM must be lokied to work. OUDHS recovery has a feature which automatically installs the workaround in every ROM you flash using the utility. I recommend this version of Clockwork Recovery.
The link is here:
http://forum.xda-developers.com/showthread.php?t=2291956
I personally use the nightly CyanogenMod 10.1 builds for the ATT S4 (called jlteatt). They're quick and stable except for a few quirks with the camera, call-audio via headsets, and bluetooth audio.
The link to download is here:
http://get.cm/?device=jflteatt
*This version of CM 10.1 is already Loki'd
Have fun flashing, and if all else fails and you accidentally run into a scenario where you can't boot your phone, use this utility to restore the factory OS that comes with the phone.
http://forum.xda-developers.com/showthread.php?t=2261573
Furies said:
So, to some up development in this forum for the last 3 months: The ATT version of the S4 has a locked bootloader, which is a fancy way of saying ATT and Samsung don't want custom software on their phone partitions. To keep people from installing custom ROMs, their bootloader requires a verified signature present in the ROM to actually allow the device to boot.
An individual found a way to trick this verification process, and created a patch for it called LOKI.
When a ROM is "Loki'd" it contains this workaround for the verification process in the bootloader, allowing custom software to be installed.
To answer your question, when you root your phone and install the recovery (TWRP or OUDHS): a ROM must be lokied to work. OUDHS recovery has a feature which automatically installs the workaround in every ROM you flash using the utility. I recommend this version of Clockwork Recovery.
The link is here:
http://forum.xda-developers.com/showthread.php?t=2291956
I personally use the nightly CyanogenMod 10.1 builds for the ATT S4 (called jlteatt). They're quick and stable except for a few quirks with the camera, call-audio via headsets, and bluetooth audio.
The link to download is here:
http://get.cm/?device=jflteatt
*This version of CM 10.1 is already Loki'd
Have fun flashing, and if all else fails and you accidentally run into a scenario where you can't boot your phone, use this utility to restore the factory OS that comes with the phone.
http://forum.xda-developers.com/showthread.php?t=2261573
Click to expand...
Click to collapse
OK, thanks very much. So I was indeed on the right track. I'll try your ROM recommendation as well as the modified CWM recovery.
Greetings to everyone,
I would be happy if you can help me with a little problem on my Note 4.
For some reason I cant install a costum ROM on my Note 4 (N910F).
As soon as I have installed a ROM like NameLessROM the phone reboots, shows the Samsung logo for about 10 seconds, reboots, shows the logo, reboots, ...
Its the same thing happened to me once whileI tried to boot it with no system partition (wiped it)
I am using the newest TWRP.
Anyone got a solution?
Greetings
Robin
Sorry Robin for "hijacking" your thread but we're in the same boat
I'm having the exact same problem with my SM-N910F.
I've rooted the device using Odin3 and "CF-Auto-Root-trlte-trltexx-smn910f.tar.md5". This thread: http://forum.xda-developers.com/note-4/orig-development/sm-n910-cf-auto-root-t2897428
That went fine and I checked the root privillige afterwords with a terminal app on the phone. I issued the SU command and got at .....root#. Don't know if thats the right/best way to check it!
After rooting the phone I still had the stock recovery tool so again with Odin3 I installed "philz_touch_6.59.0-trlte.tar.md5".
This also went fine and I can now access "PhilZ Touch 6" recovery tool.
From here I've tried installing three different ROM's ("GlamourS6v3_1", "Super.Fast&LolliFamous™[S6+Style+v2][PART.4.0.]_BOC3" and "Super.Fast&LolliFamous_[.PART.6.0.]_BOD2") but keeps ending up with a phone that just keeps rebooting.
When I install the ROM I start with the "Clean to install a new ROM" option and after that install ZIP. The ROM's are located on my SD card.
The installation succed and when I reboot the phone just continues to reboot.
Any good advise?
Regards
John
You have to flash via odin the right modem and bootloader for the ROM that you're trying to install
mone, your a genius! Or maybe you just read the instructions more carefully than I did
I found the exact info and links in the ROM thread and everything is working now.
Thanks!
/John
RDieker201 said:
Greetings to everyone,
I would be happy if you can help me with a little problem on my Note 4.
For some reason I cant install a costum ROM on my Note 4 (N910F).
As soon as I have installed a ROM like NameLessROM the phone reboots, shows the Samsung logo for about 10 seconds, reboots, shows the logo, reboots, ...
Its the same thing happened to me once whileI tried to boot it with no system partition (wiped it)
I am using the newest TWRP.
Anyone got a solution?
Greetings
Robin
Click to expand...
Click to collapse
Okay for Nameless ROM to work on N910F you have to install the SimplKernel and need to update your bootloader and modem accordingly.
imladris said:
Sorry Robin for "hijacking" your thread but we're in the same boat
I'm having the exact same problem with my SM-N910F.
I've rooted the device using Odin3 and "CF-Auto-Root-trlte-trltexx-smn910f.tar.md5". This thread: http://forum.xda-developers.com/note-4/orig-development/sm-n910-cf-auto-root-t2897428
That went fine and I checked the root privillige afterwords with a terminal app on the phone. I issued the SU command and got at .....root#. Don't know if thats the right/best way to check it!
After rooting the phone I still had the stock recovery tool so again with Odin3 I installed "philz_touch_6.59.0-trlte.tar.md5".
This also went fine and I can now access "PhilZ Touch 6" recovery tool.
From here I've tried installing three different ROM's ("GlamourS6v3_1", "Super.Fast&LolliFamous™[S6+Style+v2][PART.4.0.]_BOC3" and "Super.Fast&LolliFamous_[.PART.6.0.]_BOD2") but keeps ending up with a phone that just keeps rebooting.
When I install the ROM I start with the "Clean to install a new ROM" option and after that install ZIP. The ROM's are located on my SD card.
The installation succed and when I reboot the phone just continues to reboot.
Any good advise?
Regards
John
Click to expand...
Click to collapse
If I''m not mistaken your phone model is N910F, if so you are flashing the incorrect ROMs as the ones you listed are for the exynos variant. So please look for ROMs in the correct thread "Galaxy Note 4 Android Development (Snapdragon)" And using PHilztouch recovery is not recommend and so I would advise you to install TWRP,
N910F = Trltexx
N910G = trltedt
Exynos:
N910C = treltexx
Hi All,
New to forum here and to Android *re-engineering* in general. Wife gave me a task: to remove the stock S4 OS and replace it with something better.
These are the steps I followed:
1. In Download mode, used Odin v3.10 to flash TWRP 3.02 recovery
2. Booted to Recovery Mode, it gets to TWRP recovery ROM properly.
3. Recovered to CM13 nightly builds and rebooted to System.
4. Boots to System with the following message:
KERNEL IS NOT SEANDROID ENFORCING
Set Warranty Bit: kernel
Samsung Galaxy S4
GT-I95016
After that it just stays stuck on the screen until I reboot into Download or Recovery Mode.
None of the CM13 OS downloads I used work so far. I've also tried to recover to CM11 after the initial problem, but it doesn't work. Note that there are no releases for this, only nightly builds. Tried for 2 weeks already and I think I probably need some help.
Any ideas?
zdfan said:
Hi All,
New to forum here and to Android *re-engineering* in general. Wife gave me a task: to remove the stock S4 OS and replace it with something better.
These are the steps I followed:
1. In Download mode, used Odin v3.10 to flash TWRP 3.02 recovery
2. Booted to Recovery Mode, it gets to TWRP recovery ROM properly.
3. Recovered to CM13 nightly builds and rebooted to System.
4. Boots to System with the following message:
KERNEL IS NOT SEANDROID ENFORCING
Set Warranty Bit: kernel
Samsung Galaxy S4
GT-I95016
After that it just stays stuck on the screen until I reboot into Download or Recovery Mode.
None of the CM13 OS downloads I used work so far. I've also tried to recover to CM11 after the initial problem, but it doesn't work. Note that there are no releases for this, only nightly builds. Tried for 2 weeks already and I think I probably need some help.
Any ideas?
Click to expand...
Click to collapse
The message during boot is normal if you've modified the Bootloader (in this case, by flashing the recovery).
By "recover" I assume you mean installed/flashed a ROM.
Are you flashing the right ROM for the model?
Did you wipe before flashing?
GDReaper said:
The message during boot is normal if you've modified the Bootloader (in this case, by flashing the recovery).
By "recover" I assume you mean installed/flashed a ROM.
Are you flashing the right ROM for the model?
Did you wipe before flashing?
Click to expand...
Click to collapse
Thanks for replying - ok good to know that message is normal.
1. Yes I flashed the TWRP recovery ROM.
2. In TWRP recovery mode I installed the custom ROM for cyanogenmod 13 for i9506, downloaded from the Builds in this link: __download.cyanogenmod.org/?device=ks01lte___ (copy paste the URL as I cannot post external URL yet)
3. Yes, wiped before flashing.
zdfan said:
Thanks for replying - ok good to know that message is normal.
1. Yes I flashed the TWRP recovery ROM.
2. In TWRP recovery mode I installed the custom ROM for cyanogenmod 13 for i9506, downloaded from the Builds in this link: __download.cyanogenmod.org/?device=ks01lte___ (copy paste the URL as I cannot post external URL yet)
3. Yes, wiped before flashing.
Click to expand...
Click to collapse
How much time did you wait for the phone to boot?
Have you tried other ROMs, from here on the forum?
There is a GT-I9506 section from where you can download various modified ROMs.
GDReaper said:
How much time did you wait for the phone to boot?
Have you tried other ROMs, from here on the forum?
There is a GT-I9506 section from where you can download various modified ROMs.
Click to expand...
Click to collapse
1. Waited up to 1/2 hr, same screen.
2. I've tried CM11 and CM13
3. Could you give an example?
zdfan said:
1. Waited up to 1/2 hr, same screen.
2. I've tried CM11 and CM13
3. Could you give an example?
Click to expand...
Click to collapse
I'm a GT-I9505 user, can't really recommend you anything.
There's AICP, various CM13 builds and others. Just look through the GT-I9506 section (here on the forum) until you find something promising.
Hi,
as the title says, my phone is not booting anymore, after I transplanted the motherboard from a frame with a broken screen into a new frame (from china).
Abbreviations used:
RR => Resurrection Remix 5.8.5
CWM => ClockWorkMod Recovery 6.0.4.6-kitkat
TWRP => TeamWinRecoveryProject 3.2.1-1
I was using RR from the Rock Stable Setup on it before and it worked beautifully.
What happened:
I performed the mainboard-transplantation according to the iFixit guide
I held the power button to boot the phone:
It vibrated
It showed this screen for a couple of seconds
It vibrated
Back to step 1
And that until I removed power.
Then I tried to boot into recovery mode by holding the key combination on boot:
Same as above, but with this bootscreen
Then I tried to boot into download mode by holding the key combination on boot:
The warning to confirm download mode poped up and I got to see this screen.
I connected it to my PC and opened odin 3.09 and it recognized the device.
I tried to get adb and fastboot to see the device, but nothing worked. (In the old frame and before I broke the screen, it would be recognized at this stage)
I flashed TWRP with odin, odin showed the green "PASS!", but booting to recovery still failed.
I proceeded to flash a stock ROM, which had worked when I had issues with RR.
It worked, I went through the Android 5 setup process, enabled debug and connected adb.
adb saw the phone.
I rebooted to recovery and stock recovery booted correctly.
Sideloading anything with adb failed due to signature verification.
I then went back to download mode and flashed CWM successfully.
It now boots into recovery, but whenever I try to flash anything with CWM, it fails showing this screen
Or something similar (the photo comes from flashing RR 5.8.5)
I have both linux and windows properly setup and used both with adb, fastboot and odin (only windows)/heimdal (only linux).
I checked drivers and usb cables.
I opened the phone back up and checked all connections.
But I can't get any version of RR, CyanogenMod or LineageOS on there.
I've searched the internet, but people that have these kinds of problems after replacing parts of their phones, seem to only have driver issues or skipped steps in the manuals of custom ROM installations.
If you have any idea on what I could try or what I'm doing wrong or not doing, please leave an answer.
I'll keep this post updated below here:
(no updates, yet)
Thanks so much in advance
Simon
Your picture shows stock recovery not CWM .
Try flashing TWRP recovery through Odin .
I did flash TWRP and afterwards there was no recovery anymore.
When I flash CWM, I get the recovery shown in the photo.
The stock recovery has a black background and no touch controls for me.
What you saw must have been CWM.
Update: I can flash twrp-2.8.7.0-hlte-4.4.img.tar and it works. It's the only image that works, but I still can't boot into or flash any custom OS.
The only working OS I have at the moment is a stock android 5.0, which is not all that useful...
If anyone has an idea, why I can't or how I can find out what is causing it, please say so.
I can flash twrp-2.8.7.0-hlte-4.4.img.tar and it works. It's the only image that works, but I still can't boot into or flash any custom OS. )
What do you mean by ANY ??
Well, exactly that.
Regardless of what zip I flash, I end up with a bootloop.
If I flash a recovery zip, the recovery bootloops, but the OS still boots.
If I flash a custom ROM, I can still boot into recovery fine, but booting normally results in a bootloop.
The only way to get software onto my phone has been via odin and only an old CWM, Philz Touch, TWRP (Version 2.8.7.0 and below) and STOCK Android (Versions 4.3, 4.4.2, 5).
Anything else I have tried so far did not result in an error, but I couldn't boot into it either.
If you have ideas for software I can try flashing, please tell. I really have no idea how to get the damn thing to work again...
What happens when you flash correct stock rom via Odin ??
I mean that I can boot into it after flashing it via Odin.
But its terribly slow and bloated compared to ROMs like ResurectionRemix, so I don't want to use it.
AnyTimeTraveler said:
I mean that I can boot into it after flashing it via Odin.
But its terribly slow and bloated compared to ROMs like ResurectionRemix, so I don't want to use it.
Click to expand...
Click to collapse
In that case phone is OK .
Usual is that user is failing to follow instructions .
Not sure what you mean by fastboot on a N9005 .sounds like not a N9005 .
Personally with TWRP 2.8.70 i would be flashing something like .
https://forum.xda-developers.com/galaxy-note-3/development/rom-magma-nx-rom-t3508672
as its correct TWRP .
I am able to follow instructions.
Thank you very much.
I followed exactly the same procedure that has worked many times when switching between custom ROMs.
Also, the phone has a perfectly working version of Ressurection Remix installed at the time my frame broke and it did get stuck in the same bootloop after replacing the frame, even thogh the software was exactly the same.
I am looking for help analyzing the boot process and some way of capturing the kernel log when booting to determine where the error occures that traps the phone in a bootloop.
AnyTimeTraveler said:
I am able to follow instructions.
Thank you very much.
I followed exactly the same procedure that has worked many times when switching between custom ROMs.
Also, the phone has a perfectly working version of Ressurection Remix installed at the time my frame broke and it did get stuck in the same bootloop after replacing the frame, even thogh the software was exactly the same.
I am looking for help analyzing the boot process and some way of capturing the kernel log when booting to determine where the error occures that traps the phone in a bootloop.
Click to expand...
Click to collapse
Dear Mate..
Have you solved your problem? I have same problem after transplating N900 frame.
Sorry, I gave up, since I dearly needed a working phone and bought a OnePlus 3 cheaply from ebay second hand. It's been working like a charm and I threw the note into my museum after I softbricked it for the n-th time and couldn't get it out of a bootloop that didn't leave me time to go into Fastboot.
Sorry friend, but I can't help with this.
after reading a lot of similar threads, seems like the hardware is the cause of us not able to update to higher versions of twrp(& custom roms)
Hello everyone, first of all am a newbie and I am trying to flash my Note3 with custom rom, I installed twrp using Odin, first I faced an error that Everytime Odin will say pass but phone will boot normal, how ever I find the solution by unchecking auto reboot in Odin, after pass I'll unplug the device, pull off battery then restart and it will get me to term recovery and it works fine afterwards. I tried installing few custom ROMs like magma nx, dark lord x etc but after everything done phone get stuck in bootloop. First I did the same and got stuck then I did a stock rom flash and got the phone working again, how ever I tried flashing again with magma nx and it got away from Samsung logo to pyeongchang edition logo and got stuck there, all the roms I tried give me same error. Am using twrp 2.8.7.0. I had also rooted using SuperSU, how can I get past this? Any help will be appreciated.. thank you
What phone model ??
Bootloop read the thousands of bootloop posts use roms SEARCH THREAD box bootloop .
Difficult to know what you are doing wrong without more information .
Model is a Note 3 N9005,
I have gone through most of the threads but I am not finding a solution yet, as I said :-
1) Installed TWRP using Odin
2) Rooted the device
3)Placed few Custom ROMs in SD
4)Flashed using TWRP (followed instructions)
5) Flashing finished successfully
6) Reboot
7) Bootloop
Stuck here, can I provide any other details?
3)Placed few Custom ROMs in SD
As in what rom one only not multiples .
4)Flashed using TWRP (followed instructions)
Right twrp wrong twrp ??
7) Bootloop
What did rom thread say about bootloop ??
Updated bootloader >>when required .
Magma has full instructions and full faqs .
---------- Post added at 02:02 PM ---------- Previous post was at 01:43 PM ----------
mAGMA
SEARCH THREAD Bootloop
https://forum.xda-developers.com/search/thread/3508672?query=bootloop
FAQ
Q: I have bootloop right after I flash the ROM
2. In first boot, when asked to "Consent for Diagnostic Report", you forgot to uncheck it. As written in OP, you have to "uncheck" the Consent for Diagnostic Report.
To solve it:
1. Power off phone
2. Remove sim card
3. Boot to ROM.
4. Go to settings/general management
5. Disable "Report Diagnostic Info"
6. Power off Device.
7. Insert sim card.
8. Boot up phone and continue using it
Managed to make them work already, thanks for the help bro.. appreciate it
I managed to work around the issue of bootloop bro, it had something to do with the kernal , I already flashed to magma and it is working now, how ever I was curious that each time when I restart the phone, it took a bit time to load up, like note 3 logo first, then magma note 8 logo, then after that it says optimizing apps and actually it shows around 240 apps or so, is it normal or is there any workarounds for the same? (How ever, boots up fine but boot up time is around 7-12 min approx)