I bricked my wind mobile g2 a few days ago with autorec, restored it and now i have twrp 2.6.3.2, im afraid to update recovery again because i dont want to end up in fastboot again , now im stuck on a stock 4.2.2 rom and want kk back , also auto rotate an sensors are not working anymore, maybe because im using a bell stock rom, if anyon e can help me out id be very happy , i have root access but no computer ._. D have to flash zips, thanks
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.
now i'm on L-29c185b580 rooted unlocked bootloader and i had flash twrp
i tried to remove it by flashing stock recoveries found on the internet but it's not that stock it looks weird just restore recovery and reboot or shutdown and the top left called 'erecovery'
i wanted to update to b582 via firmware finder but failed many times i just wanted my phone to restore to normal
knowing that dload method don't work for some reason
any help please
Hi all. Long story short, trying to fix this phone up for a relative. I used the bootloader unlock to unlock it (it's a VZW variant). After, I flashed a CM14 nightly build. Shortly after, I purchased a new phone and it basically got put away in early 2016 if I remember correctly.
Well, yesterday, I tried wiping and flashing a rom called SkiesROM to it, which failed to boot after the AROMA setup. After, I tried flashing a QA1 stock rooted ROM which has also failed to boot and won't do anything except boot loop when it gets to the red verizon logo.
In short, I want to figure out how to get this phone working again on ANY Android version with TWRP. I don't know what version of firmware I'm on now. I don't know what bootloader version it is now. All I know is that I can access TWRP when I want to. I assume that gives me an edge in flashing whatever I need to flash on it.
I forgot that I needed to be on certain levels of firmware to change ROMs on this phone, so I think that's where I messed up and now I don't know how to backtrack and get into any working ROM. Can someone help me please?
TL;DR: I can get into TWRP. I don't know what firmware or bootloader version this thing is on. It's a VZW variant that I bootloader unlocked but I don't know if it's still bootloader unlocked. I want to boot this thing on any stable ROM even if it's a stock one. Please help me.
You can flash latest rom at https://forum.xda-developers.com/verizon-galaxy-s5/general/update-qi2-t3688046 with Odin and then reflash TWRP with Odin. Just make sure you flash the Dev Friendly version of the Rom so you don't lose your unlocked boot loader status.
If you can eat to recovery did you not back up your current ROM? Always back up always I bricked S7 before lol learned my lesson on that one but now on s5 mini so playing around is great but any more help you need if I can help mm
hi ! Please need help. Firstly I was on custom rom. Then I flashed stock fast boot rom sucessfully & then I got the update of android 8.1 if upadted my software to 8.1 . After two days I revert back to custom roms . Now I just wants to go back to stock so i flashed the earlier version of stock rom but i ****ed up my device now its not booting up on bootloader mode is showing. what to to now? i m from india.
Which custom rom u were on?
Which version did u downgrade to?
Did u take entire backup (efs and persist) before flashing custom rom?
For temporary solution : Try selecting "start" in bootloader?
zooreo said:
hi ! Please need help. Firstly I was on custom rom. Then I flashed stock fast boot rom sucessfully & then I got the update of android 8.1 if upadted my software to 8.1 . After two days I revert back to custom roms . Now I just wants to go back to stock so i flashed the earlier version of stock rom but i ****ed up my device now its not booting up on bootloader mode is showing. what to to now? i m from india.
Click to expand...
Click to collapse
Is your bootloader is working or it get stucks on bootloader image.
You downgraded your bootloader. (I suppose)
"Now I just wants to go back to stock so i flashed the earlier version of stock rom"
Well... That's bad.
"my device now its not booting up on bootloader mode is showing."
What is it showing? Is it showing the bootloader? What version?
(Do you know how to check that? Please use a translator if English is not your main language or something.)
"After two days I revert back to custom roms."
Better act more decisively next time. That cost your device a potential brick.
Thanks guys i recovered my device by just pressing restart.