Related
My phone was running CM 11 M12 with TWRP 2.7.1.0 recovery. I used ROM Tools from JRummy to flash the TWRP 2.8.3.0 image, and it flashed successfully. I rebooted into recovery to verify, but my phone ended up stuck in download mode. I couldn't reboot to system or recovery, it kept coming back to download mode. I attempted to unbrick via ODIN by flashing an old 4.2.2 stock tar file (using Qbking77's "How to Unroot and Unbrick the Samsung Galaxy S4" YouTube video), but now it is stuck in a bootloop at the AT&T logo. When I try to reboot into recovery, the Samsung Custom screen appears, "recovery booting" appears on top, and the phone reboots again back to system and proceeds to get stuck at the AT&T logo once more. This has all has to be related with my recovery getting screwed up, but I have no idea how to fix that issue.
I really don't want to be without a working phone any longer than I need to, any help would be greatly appreciated.
EDIT: Before CM 11, I was running Danvdh's GS4 4.4.4 GPE ROM, which changed my phone's model number to i9505. Should I redo the unbrick with an i9505 tar file? Again, any help will be appreciated.
Do not flash a 9505 file. Go to sammobile.com and download the 4.2.2 file for the i337. Try that in Odin
Sent from my Nexus 9 using XDA Free mobile app
On download mode my note 3 shows SECURE DOWNLOAD : ENABLE in blue colour which I guess means my bootloader is locked . Whenever I flash any custom rom like cyanogen mod or any custom kernel I get stuck on kernel is not seandroid enforcing set warranty bit kernel . I'm currently on stock lollipop rom .
so my question is how to unlock note 3 bootloader so I can flash custom rom (I can flash and boot rom darkera but not cyanogenmod or aosp , aokp rom)
And how to remove SECURE DOWNLOAD : ENABLE from download mode
Please Please help
Secure download enable doesn't means locked bootloader. If your phone model is n9005, it unlocked already.
Sent from my SM-N920C
Theres no unlocking for Samsung, you have Odin for that. Flash a custom recovery with it, boot in there and install the custom ROM. Done. There are dozens of manuals for that in here ^^ (Thats the 3rd time I post this one in a row... GUYS, ONE POST IS ENOUGH!)
i have samsung not 3. when i start a message id flashed and my mobile gets block. can anyone help me to inlock my mobile
fayaz
Which note 3 do you have? What message appears? Which rom is on the phone?
baig50 said:
i have samsung not 3. when i start a message id flashed and my mobile gets block. can anyone help me to inlock my mobile
fayaz
Click to expand...
Click to collapse
Information about to be flashed ROM, current ROM, current mobile, COMPLETE error message like.... by taking a picture of it, would be quite useful. Otherwise noone can help you because sadly the mods disabled glass ball support in here
Hi, I need some help.
I have Note 3 SM-N9005 Lollipop 5.0 stock rom (N9005XXEGBNL8) and rooted with TWRP recovery. I really want Xposed, tried to flash it and got stuck in bootloop, so I tried deodexing my rom, I did it with Joel Droid Lollipop Batch Deodexer, it went well until I tried to install it with TWRP, instant bootloop again, then I tried flashing any custom rom with TWRP and before flashing I always do advanced wipe, but nothing helps, roms doesn't even start installing, my phone just reboots and I'm in a bootloop again, but after flashing rom bootloop is different it doesn't show Samsung logo it just shows Samsung Galaxy Note 3 SM-N9005. So my question is can it be bootloader and if so how can I unlock it? Or is it something entirely different?
Please help...
misskiss said:
Hi, I need some help.
I have Note 3 SM-N9005 Lollipop 5.0 stock rom (N9005XXEGBNL8) and rooted with TWRP recovery. I really want Xposed, tried to flash it and got stuck in bootloop, so I tried deodexing my rom, I did it with Joel Droid Lollipop Batch Deodexer, it went well until I tried to install it with TWRP, instant bootloop again, then I tried flashing any custom rom with TWRP and before flashing I always do advanced wipe, but nothing helps, roms doesn't even start installing, my phone just reboots and I'm in a bootloop again, but after flashing rom bootloop is different it doesn't show Samsung logo it just shows Samsung Galaxy Note 3 SM-N9005. So my question is can it be bootloader and if so how can I unlock it? Or is it something entirely different?
Please help...
Click to expand...
Click to collapse
Maby look here
http://forum.xda-developers.com/xposed/official-xposed-lollipop-t3030118
samsung galaxy note 3 SM-N9005 has been stuck in downloading mode
Actually,i had rooted my device yesterday now, when i am trying to install cutom recovery TWRP on my device it suddenly rebooted and locked at downloadin mode.
Can,anyone suggest me any way to reboot again to normal touchwiz mode
Suggests you flashed the wrong recovery for your model .CHECK
See multiple identical posts .
READ the TWRP thread .
To the phone back to stock, flash the phone with Odin and a stock ROM from Sammobile.com.
Hi everyone, i was testing whether editing the build.prop file changes the settings displayed in about device. I edited the build.prop of my s3 changed the product name and model to s5 but unfortunately i did not make a backup of my current rom and now the screen shows s3 neo logo and then shuts down. I can still access the stock recovery but my question is should i find stock rom of s5 since build.prop is now s5 which bricked the phone or should i find stock rom for s3 ? please it's urgent any help would be appreciated!. and if anyone has the rom which i need to install please upload it somewhere
Either flash the rom/firmware or find & copy the S3 Neo BUILD.PROP (to root/system) with costume recovery & change permissions as according.
I don't know how you got to the idea to put S5 build.prop in the first place.
Download s3 neo's stock firmware and flash it using odin
or if u want to try any other custom roms u can flash a custom recovery via odin then go into recovery and flash the particular custom rom....
My phone is a Samsung Note 3 SM-9005, currently it's stuck in an infinite bootloop even after removing the battery for an hour.
I get this message:
RECOVERY BOOTING ...
RECOVERY IS NOT SEANDROID ENFORCING
Set Warranty Bit : recovery
... along with the Samsung SM-N9005 logo, a couple of beeps/buzzes and then it repeats ad infinitum.
Here's what I did over the last day to get to this sorry state of affairs:
1. Upgraded from Android 4.3 (the original operating system) to 5.0 using the Samsung N9005XXUGBOA5 ROM with Odin 3.12. This worked fine but the phone lost root.
2. I rooted the phone again using Odin and Chainfire Auto-Root. All good so far.
3. I installed TWRP (the official TWRP App 1.5, going by my records)
4. I flashed the latest custom recovery which would have been 3.0.x and this seemed to be fine. So far no problems.
5. I then got ideas above my lowly station, apparently. I wanted to flash one of the newer ROMs: [Rom][N7 Port][12.12.2016] [Multi-DPI] Phronesis Rom N7 v4.1 Feature Rich & Smooth
https://forum.xda-developers.com/ga...m-phronesis-mm-rom-v1-0-feature-rich-t3463244
6. In the instructions, it said to use TWRP recovery version 2.8.7. I found that and flashed it. (Yes, it was for the Samsung SM N9005).
7. I rebooted into recovery mode to make a backup with that 2.8.7 version.
8. Now I'm stuck in boot loop hell with ...
RECOVERY BOOTING ...
RECOVERY IS NOT SEANDROID ENFORCING
Set Warranty Bit : recovery
... with the Samsung SM-N9005 logo, a couple of beeps/buzzes and so on (as stated above).
I've tried leaving the battery out for an extended period and this hasn't worked. The phone never gets to the stage where I can talk to it with Odin or get any kind of menu. Is the phone truly bricked now?
If so, was it a critical error to go from the 3.0.x TWRP recovery back to 2.8.7 for the purposes of this custom ROM upgrade?
If not, what can be done to regain control of the phone?
This is obviously an older phone as I've had it for about 3 years now, but I'd love to get it working again if possible. I really loved it and was planning to use it for a couple more years (hence the upgrade path I've explained above).
Can you boot into download mode? I suspect you flash the 4.3 version of twrp, you need a 4.4 version. This one https://dl.twrp.me/hlte/twrp-2.8.7.0-hlte-4.4.img.tar.html
Boot into download mode and flash it with odin.
I suggest flashing the latest stock ROM, flash the latest tar version of twrp with Odin, root with supersu.zip in twrp.
Stonedead, you were right on the money. I did what you suggested (Download mode) and that different TWRP file, and it worked.
Thanks so much.
Thanks audit13 also, although I didn't need to go that far to undo my mistake.
I got the same problem with my note 3. Thank you for the solution. Now how do I exactly get TWRP working on my phone. It is already rooted.
See TWRP thread.
Basics flash twrp tar through odin
Root is not needed to install the tar version of TWRP with Odin.
Thanks. Managed to get twrp working now. Also installed the note 8 Rom
Hi ok im having the same problem kinda follow the installation as posted,so i have note 3 sm-n9005 stock rom,root and replaced twrp 4.3 for 4.4 to install phronesis n7 v7 for note 3 followed all instructed then rebooted went to samsung boot then booted to twrp recovery ive been on it all day thinking what da hell ive done wrong?can someone instruct me of what i did or didnt do or have i completely mess stuff up?cheers anyone.
instructions .
Boot into recovery (say TWRP 2.8.7.0)
JJEgan said:
instructions .
Boot into recovery (say TWRP 2.8.7.0)
Click to expand...
Click to collapse
Sorry jjegan not following?it already reboots into twrp recovery after the galaxy note 3 logo appears for 20 seconds?I have read and followed threads that have same or similar problems but no avail im am totally lost and from reading this rom it sounds great if I can get there that is,so please simple instructions would be very helpful as I'm still learning very sorry for being dumb.
This rom
phronesis n7 v7 for note 3
all Aroma roms require TWRP 2.8.7 and not newer versions .As posted multiple times in the thread .
Search results for query: TWRP
forum.xda-developers.com
JJEgan said:
This rom
phronesis n7 v7 for note 3
all Aroma roms require TWRP 2.8.7 and not newer versions .As posted multiple times in the thread .
Search results for query: TWRP
forum.xda-developers.com
Click to expand...
Click to collapse
Hi JJEgan,thank you for the reply back much appreciated for your time so far,so do you mean twrp-2.8.7.0-hlte-eu.tar file?and not twrp 2.8.7.0-hlte-4.4 img.tar file?that's the one I am using to flash the rom with and having problems with.
Hi there again ok im so confused not sure which one,there are so many of the 2.8.7.0 versions with 4.3 or 4.4-img.tar im not sure if im downloading 4.4 or 4.3 as im still a noob and love tech,I have read threads upon this rom problems still can't get the grasp of the simple twrp version I have lte au version android 5,and when I read 2.8.7.0 im think is it 4.4 4.3 or just 2.8.7.0 tar file?I'm following the installation up into the problem of not booting up in stays In galaxy note 3 boot and I have removed the battery 5mi z replaced then recovery and factory reset then it does the same again and I have tried 3 times waited longer each time im thinking maybe go back to stock I don't think my phone is agreeing with me,jjEgan thanks for the info amd time im sorry if annoy you with a simple installation to you,still I have read and grasp the concept of twrp installer version yeah??
Only use 2.8.70 as said later versions wont flash that rom.
2.8.7.0 TAR flashed through Odin .
JJEgan said:
Only use 2.8.70 as said later versions wont flash that rom.
2.8.7.0 TAR flashed through Odin .
Click to expand...
Click to collapse
Thanks for the reply JJEgan,no I have finally fix the problem solution start over fresh instalments installed stock,flash twrp 4.4, flashd supersu threw twrp,wiped 3x install,instead of rebooting threw Aroma rebooted system threw twrp it loaded first go,thanks for the threads I took bits n pieces frm each threaded problems,cheers JJEgan love the version rom,one more thing what kernel would be better or what would your choice be cheers
Hello everyone,
I search this forum and found similar posts (most already closed) about TWRP having an "error" with some Galaxy J1 devices. I tried to reach to TeamWin but in their website they refer people to this forums, so I am adding this post hoping to clarify the issue and maybe solve it.
The error goes basically like this:
1. Download any version of TWRP for Samsung Galaxy J1 aka j1acevelte
2. Flash to Galaxy J1 device with Odin (autoreboot enable or disable)
3. Use manual boot to recovery, the device "comes back to stock recovery"
4. Repeat, install, reboot, stock recovery.
Some had "luck" using manual boot recovery, but many had never been able to use TWRP on any J1 device (I found SM-J111M and SM-J110H post in this forum, and many others around the web).
After looking (googling) the internet, I went directly to TeamWin githup repositories for TWRP j1acevelte (the "culprit") and I found that there is only one branch for these devices and it is for KitKat 4.4, since there are some J1 phones like SM-J110F with 4.4 firmwares, and some others like (mine) SM-J111M with 5.1.1 I will like to ask the experts here:
Could this be the reason why some people is able to use TWRP (KitKat users) while others like me (Lollipop users) never got the TWRP to work?
If that is the reason: Are there any options?
If is not, them we just have bad luck?
Really appreciate any feedback on this. I am cooking my own rom for this phone, flashing with Odin works well but will like to have TWRP or any other custom recovery.