Related
My question is regarding flash stock + unroot using the Nexus Root Toolkit v 1.6.3
I have already unlocked and rooted my phone using the tool.
I am now trying to flash stock + unroot using the Nexus Root Toolkit.
I downloaded the build from Google's Factory Image Download page.
I get passed Which Factory Image? by clicking Other/Browse
Choice: I downloaded a factory image myself that I would like to use instead.
Choose a google facotry image: mysidspr-ga02-factory.tar
Analyzing factory image; please be patient
Hascheck Verification
Enter the md5 has given for: mysidspr-ga02-factory.tar
I enter: c93156606b39a6b61d371ef935a6a6ba from googles website.
Message pops up: Your file is good to extract and flash! Press OK to continue.
Please be patient...Checking ADB Status
Device Connected Rebooting your device into bootloader mode
Chekcing Fastboot Status
Device Connected
Checking Fastboot Status
Device Connected
CMD window opens
Booting up your freshly flashed stock device
Wait for your device to finish booting up...
- It will appear to be boot looping; just wait...
-It could take 5-10 minutes; please be patient...
When its finally booted back up, please remember to re-enable USB debugging if you plan on using the toolkit to perform other operations
Press any key to exit...
My phone remains on the Bootloader screen with the robot laying down with its hatch open.
Bootloader is on Start
below robot:
FASTBOOT MODE
PRODUCT NAME - tuna
VARIANT - toro 32GB
HW VERSION - 14
BOOTLOADER VERSION - PRIMELC03
BASEBAND VERSION - L700, FC12 COMA - L700, FC12
CARRIER INFOR - NONE
SERIAL NUMBER - 0A3C2C620401C009
SIGNING - production
LOCK STATE - UNLOCKED.
I have gone through this over and over and have waited anywhere from 15 minutes to 3 hours. Nothing else occurs.
So I click Press any key to exit from the command window and restart my phone and it is still on Android 4.1.1
Any suggestions/help would be greatly appreciated.
Hi, I noticed that if you choose the option where you have already downloaded the image (from google) it wont work. You have to select the option where the program downloads the image from that site goo.xxx.
Google's stock image is .tar and the image downloaded from the other site is .tgz ( supposedly the same thing, but the toolkit would only extract the second) To be honest, I would have rather use the image downloaded from google's...
Doesn't work for me too..
tessorodesoto said:
Hi, I noticed that if you choose the option where you have already downloaded the image (from google) it wont work. You have to select the option where the program downloads the image from that site goo.xxx.
Google's stock image is .tar and the image downloaded from the other site is .tgz ( supposedly the same thing, but the toolkit would only extract the second) To be honest, I would have rather use the image downloaded from google's...
Click to expand...
Click to collapse
I tried to do both ways but it doesn't work for me either..
I have Galaxy Nexus with Android 4.2.1. I have managed to unlock and root my phone easily using Nexus Root Toolkit 1.7.1. However when it comes to flash rom+unroot process, it is not working.. I tried to flash Android 4.2.2 and Android 4.3 by choosing both options but the process always stopped in the beginnig of CMD prompt window..
same problem
I rooted my newly aquaried nex which was a fully stock 4.1 in anticipation of flashing to boost and custom roms and all that fun stuff. NOW I cant flash I CANT change os. I CANT FACTORY RESTORE I CANT DO CRAP I HAVE A FREAKING PAPER WEIGHTT because I don't want sprint and there is no way ill put this back on ebay and give the head ache to someone else. HAS ANYONE FIGURED ANYTHING OUT YET? I can really use a hand. Ive spent over 15 hours researching downloading flashing fast booting etc. and I've gotten nowhere ANY HELP would be GREATLY APPRECIATED.
The BLU LIFE XL phone is an unlocked GSM platform device.
Currently there are absolutely no threads on the internet with information related to this device. I am not responsible for any damage done to your device, you assume sole responsibility for whatever you do to your devices. If you have questions, please reply to this or PM me, I'll be glad to help any of you!
================
Things you should know before you do anything listed in this post:
- Bootloader unlocking WILL ERASE USER DATA!!!!
- Successful root attempts disable OTA updates. (Unroot + Factory Reset MIGHT fix this)
- You must have OEM unlocking & USB debugging enabled in the developer menu.
- Common sense, don't flash anything you find on the internet randomly, you will cause irreparable damage, I learned that the hard way.
- Download & install the ADB Universal drivers & Android SDK tools (links @ bottom)
================
If you'd like to make a backup of your stock ROM, you can use romdump, it's a nifty tool that does exactly what it says, and it works on pretty much any rooted android phone. (yay) DL: http://d-h.st/ErS
- Download & extract to root directory of your sdcard.
- Open Root Browser (Or any file browser that's for rooted devices)
- Navigate to the path where you copied/downloaded romdump
- Move romdump to /data/local/
- Long press romdump and check all 3 rows of boxes above and press"OK"
- Open terminal emulator (or any equivalent terminal emulator app)
- Type "export PATH=/data/local/bin:$PATH"
- Type "su"
- Type "chmod 04755 /data/local/romdump"
- Type "/data/local/romdump"
- Wait until the process finishes, do NOT do anything with your device, set it down and leave it.
================
Rooting The Device:
- Have USB debugging, OEM unlocking & unknown sources enabled.
- Download & install the latest version of KingRoot.
- Swipe up three times, press "try it"
NOTICE: If your device restarts through the process, don't worry, your device isn't broken, but there's a good chance the root attempt failed.
================
Unlocking/Locking The Bootloader (THIS WILL ERASE ALL OF YOUR DATA!):
- Power off the BLU LIFE XL
- Hold down POWER + VOL UP until the phone turns on.
- Release POWER button, wait for the android to appear on your screen, it might say "No Command", in that case, just press the POWER button once to pull up the recovery menu.
- Use VOL DOWN to navigate down to "Reboot to bootloader" & Press VOL UP
- Plug your phone into your computer
- Navigate to your android SDK folder, and find fastboot. (If you don't have the android SDK downloaded, refer below)
- Type fastboot devices and see if your android device is recognized.
- Type "fastboot oem unlock"
- A menu should appear on your phone screen telling you about unlocking your phone, press VOL UP to unlock your bootloader, or VOL DOWN to cancel.
Alternatively, if you wish to re-lock your bootloader, follow these steps above, however type "fastboot oem lock" instead of "fastboot oem unlock"
================
FACTORY MODE & DEVICE TESTING MENUS:
- Power off BLU LIFE XL
- Press POWER & hold VOL DOWN until the phone turns on.
- Release grip of power button, whilst holding VOL DOWN.
================
Downloads:
Android SDK: https://dl.google.com/android/android-sdk_r24.4.1-windows.zip
ADB Universal Drivers: http://www.mediafire.com/download/uo3t409a9vz3kh3/adbdriver_v1.0.zip
KingRoot: https://androidmtk.com/download-kingroot-application
Romdump: http://d-h.st/ErS
My phone bricked while updating via OTA. It was a fresh L050U, so I don't know why it happened. The only existing stock firmware for repairing is behind a paywall, and I've only found a fw for L050L. Should I use them or what...?
redkvothe said:
My phone bricked while updating via OTA. It was a fresh L050U, so I don't know why it happened. The only existing stock firmware for repairing is behind a paywall, and I've only found a fw for L050L. Should I use them or what...?
Click to expand...
Click to collapse
I'm not sure what the differences are between the L050L & L050U. If you could provide me the ROM link, I'll peel through it and compare it to the dumped L050U rom that I have and get back to you.
By the way, I also replied to your comment on reddit.
TheDarknessz0rz said:
I'm not sure what the differences are between the L050L & L050U. If you could provide me the ROM link, I'll peel through it and compare it to the dumped L050U rom that I have and get back to you.
Really could use both those rom links. Can you guys help? rooted my phone and now OTA updates have been disabled.
Click to expand...
Click to collapse
blkkalel said:
TheDarknessz0rz said:
I'm not sure what the differences are between the L050L & L050U. If you could provide me the ROM link, I'll peel through it and compare it to the dumped L050U rom that I have and get back to you.
Really could use both those rom links. Can you guys help? rooted my phone and now OTA updates have been disabled.
Click to expand...
Click to collapse
The ROM I have dumped has personal applications and accounts integrated, I will get around to dumping a clean ROM for you guys soon.
Papa bless
Click to expand...
Click to collapse
BLU Life XL needs all that the mainstream devices have.
Thank you for the info above. It's such a shame this device has such limited info online. I'm not really a Noob, but also not close to a developer. How does one go about creating a custom recovery and a sweet ROM? Do you think you tube might have a how to that is on point or is there a spot here that we as users could request pros to check on it?
BLUE LIFE XL (L050U) has anyone else been successful using this root kit?
@do_root / TheDarknessz0rz, hey just wondering if the BLUE LIFE XL (L050U) you designed this tutorial for had a specific build that is needed to do this without bricking (like markressler/redkvothe whotf-ever did with his device)? In other words what was the build# of the L050U you designed this root process around? Just wondering man so I can get this done without any worries. I shouldn't have any issues using your root process on my BLU LIFE XL (L050u) Build: ALPS.L1.MP6.V2.15.2_6592.WET_P37 Custom Build version: BLU_L050U_V12_GENERIC, right? I've rooted every android device I've owned back to the original Droid1 without ever bricking during the flashing process. Just wondered if there might be a specific reason this other dude bricked his device.
Thanks in advance for even making a root kit for this device. Would appreciate any advice you have here.
-jim :fingers-crossed:
Edit: I'm ready to do this - just wanted to hear your feedback before I give it a rip.
@heatgap, I also have a L050U device. Where you able to unlock bootloader and root your BLU LIFE XL using the procedure desribed above? BTW, Thank you @TheDarknessz0rz
I am new at rooting, etc... Any additional steps you had to do? Or any advice you might give a rookie/noob to be able to get this done?
Many thanks!
Sisafokker
MOSTLY Stock images / Seeking assistance with recovery
Okay, I've dumped all of the raw images.
Most of them are stock, with the exception of system.img and recovery.img
recovery: insecure ADB, which really does no good until I can put together a custom recovery, or at least get a shell.
system: pre-rooted with SuperSU. Also, will NOT reflash recovery to stock on reboot.
Coming from stock, after you've backed up your user data (because it will be wiped), boot into fastboot mode.
Issue a "fastboot oem unlock-go" to unlock the bootloader. (This only has to be done once.) THIS WIPES EVERYTHING!
Then "fastboot flash system system.img" (This takes a while.)
After first boot and setup, download SuperSU from play store, install and update.
I'm working on putting together a working custom recovery, but I'm not an expert at this.
Succeded!!! Rooted device!
Following @TheDarknessz0rz initial post, plus some additional help from other posts (I am a noob, needed extra help) I was able to Root my Blu XL Life. Thank you @TheDarknessz0rz for you post, I took the liberty to expand on it in to make it more "Noob friendly" :
BTW, my Blu Life XL is:
Custom Build Version: BLU_L050U_V13_GENERIC
Android Version: 5.1
This is exactly what I did:
1 - Installed Android SDK on your computer: download the program, extract, Start the "SDK Manager" file and deselect everything except “Android SDK Platform-tools”)
2 - Power off the BLU LIFE XL
3 - Hold down POWER + VOL UP until the phone turns on.
4 - Release POWER button, wait for the android to appear on your screen, it might say "No Command", in that case, just press the POWER button once to pull up the recovery menu.
5 - Use VOL DOWN to navigate down to "Reboot to bootloader" & Press VOL UP
6 - Plug your phone into your computer with a USB cable. Your phone should indicate that the device is connected.
7 - On your computer, Navigate to your android SDK folder , open the "platform-tools" subfolder and Shift+Right Click on an empty area. Choose “Open a Command Prompt Here”
8 - On your computer, On the Command Prompt: Type "fastboot devices" and see if your android device is recognized.
9 - On your computer, On the Command Prompt: Type "fastboot oem unlock"
10 - A menu should appear on your phone screen telling you about unlocking your phone, press VOL UP to unlock your bootloader, or VOL DOWN to cancel.
11 - You should see on your computer´s command prompt "OKAY, Finished total time 20.4345 sec" (approx).
12 - Your phones screen should remain black, with a few rebooting options available. In my case, I had to type on the command prompt "fastboot continue" to make the phone reboot as the "volumen up or down" were not recognized when I pressed them on my phone.
13 - Phone will be hard rebooted. All data errased.
After you have successfully unlocked your Bootloader,
Download the Kingo Root and Root Checker apps
Run Kingo Root (I had to run it two times as the first time it rebooted when at 20% and it failed) and root the device
Run Root Checker to verify the device has been rooted.
CONGRATULATIONS, this is the first step.... read below.
Once your device has been rooted, then you need to:
1) Install Custom Recovery:
I was able to install a custom recovery on my device following a youtube tutorial: search on youtube for "CUSTOM RECOVERY TWRP PARA EL BLU LIFE XL" by Luis Robert (sorry, cannot post external links)
2) Update your SU Binary (you will be told about this when you open either SuperSu or Kingo Super User...
I had massive problems updating the SU Binary, tried 5 different methods but the only one that worked was this youtube tutorial: search for "How to Replace Kinguser KingRoot with SuperSU No PC" by Iron Tech. The tutorial was meant to replace KingoRoot by SuperSU, but in the process it updated my SU Binary (I spent at least a full day trying different methods that did not work for me)
In theory, now you can enjoy all the benefits and options that a rooted device provides...
Hope this helps
Thanks again for the help!
Cheers
Sisafokker
This is going to sound stupid, I screwed something up when I was editing a file in /system and now I'm in a boot loop. Also, when I went ot go try to download the raw stock roms images, the download would not initiate. Could you put the upload them somewhere else or is there anything that I can do with the stock recovery that could get me out? I also do not have like anything dumped or anything. L0051UU variant by the way. Thanks in advance
br21763 said:
This is going to sound stupid, I screwed something up when I was editing a file in /system and now I'm in a boot loop. Also, when I went ot go try to download the raw stock roms images, the download would not initiate. Could you put the upload them somewhere else or is there anything that I can do with the stock recovery that could get me out? I also do not have like anything dumped or anything. L0051UU variant by the way. Thanks in advance
Click to expand...
Click to collapse
I do not have any stock images, the images i have are for my device specifically, i'd have to rid the image of custom files first.
Okay, thanks I think I understand, but is there anything that you can think of that could help me in my situation? Or would I be best off contacting BLU?
Thanks again
br21763 said:
Okay, thanks I think I understand, but is there anything that you can think of that could help me in my situation? Or would I be best off contacting BLU?
Thanks again
Click to expand...
Click to collapse
well if you've got nothing to lose, I'd just try to flash the L050L firmware onto the device.
sisafokker said:
Following @TheDarknessz0rz initial post, plus some additional help from other posts (I am a noob, needed extra help) I was able to Root my Blu XL Life. Thank you @TheDarknessz0rz for you post, I took the liberty to expand on it in to make it more "Noob friendly" :
BTW, my Blu Life XL is:
Custom Build Version: BLU_L050U_V13_GENERIC
Android Version: 5.1
This is exactly what I did:
1 - Installed Android SDK on your computer: download the program, extract, Start the "SDK Manager" file and deselect everything except “Android SDK Platform-tools”)
2 - Power off the BLU LIFE XL
3 - Hold down POWER + VOL UP until the phone turns on.
4 - Release POWER button, wait for the android to appear on your screen, it might say "No Command", in that case, just press the POWER button once to pull up the recovery menu.
5 - Use VOL DOWN to navigate down to "Reboot to bootloader" & Press VOL UP
6 - Plug your phone into your computer with a USB cable. Your phone should indicate that the device is connected.
7 - On your computer, Navigate to your android SDK folder , open the "platform-tools" subfolder and Shift+Right Click on an empty area. Choose “Open a Command Prompt Here”
8 - On your computer, On the Command Prompt: Type "fastboot devices" and see if your android device is recognized.
9 - On your computer, On the Command Prompt: Type "fastboot oem unlock"
10 - A menu should appear on your phone screen telling you about unlocking your phone, press VOL UP to unlock your bootloader, or VOL DOWN to cancel.
11 - You should see on your computer´s command prompt "OKAY, Finished total time 20.4345 sec" (approx).
12 - Your phones screen should remain black, with a few rebooting options available. In my case, I had to type on the command prompt "fastboot continue" to make the phone reboot as the "volumen up or down" were not recognized when I pressed them on my phone.
13 - Phone will be hard rebooted. All data errased.
After you have successfully unlocked your Bootloader,
Download the Kingo Root and Root Checker apps
Run Kingo Root (I had to run it two times as the first time it rebooted when at 20% and it failed) and root the device
Run Root Checker to verify the device has been rooted.
CONGRATULATIONS, this is the first step.... read below.
Once your device has been rooted, then you need to:
1) Install Custom Recovery:
I was able to install a custom recovery on my device following a youtube tutorial: search on youtube for "CUSTOM RECOVERY TWRP PARA EL BLU LIFE XL" by Luis Robert (sorry, cannot post external links)
2) Update your SU Binary (you will be told about this when you open either SuperSu or Kingo Super User...
I had massive problems updating the SU Binary, tried 5 different methods but the only one that worked was this youtube tutorial: search for "How to Replace Kinguser KingRoot with SuperSU No PC" by Iron Tech. The tutorial was meant to replace KingoRoot by SuperSU, but in the process it updated my SU Binary (I spent at least a full day trying different methods that did not work for me)
In theory, now you can enjoy all the benefits and options that a rooted device provides...
Hope this helps
Thanks again for the help!
Cheers
Sisafokker
Click to expand...
Click to collapse
My device always returns status locked when I tell fastboot to dump the variables. I'm not sure why, bootloader unlock process says it's successful, however when it comes time to press VOL_UP to finish the process, none of the hardware keys are recognized, I've even issued fastboot continue from command prompt, yet the bootloader refuses to unlock. I'm going to try once more with "fastboot oem unlock-go" and see what happens from there.
TheDarknessz0rz said:
well if you've got nothing to lose, I'd just try to flash the L050L firmware onto the device.
Click to expand...
Click to collapse
Don't mean to sound so clueless but how would I go about doing that? I mean I couldn't find any firmware anywhere, even for other models so could you help me with that part? Also would I be flashing it from the "apply update from sd card" option on the stock recovery?
Thanks a lot
Never mind, I was able to figure out how to flash the system.img file onto my phone. Now it seems to be working perfectly. Thank you very much for all of the help and for uploading the img files, i really appreciate it.
Have a nice day
blu-life-xl Hard brick No problem !!!!!
blu-life-xl Hard brick No problem !!!!!
http://www.needrom.com/download/blu-life-xl-3g-l050l/
dont use the sp flash tool it has a virus only the img
download sp fflash tool from there own site
BLU download site
samgr said:
blu-life-xl Hard brick No problem !!!!!
http://www.needrom.com/download/blu-life-xl-3g-l050l/
dont use the sp flash tool it has a virus only the img
download sp fflash tool from there own site
Click to expand...
Click to collapse
Hey thanks for this link - - - - this site could help a lot of people
My phones backed up and i want to test the download file
hard brick NO! problem
Rickrocks013 said:
Hey thanks for this link - - - - this site could help a lot of people
My phones backed up and i want to test the download file
Click to expand...
Click to collapse
try it it works!!!!!!!!!!!!!!!!!!!:laugh:
.
Hi - I really am in need of help. My phone which is a T-Mobile Samsung Galaxy Note 5 (was) running latest 6.x firmware,
but custom and rooted via DarkStalker's awesome ROM. All was running fine for months. I did do one thing before my phone died,
I turned OFF developer option and forgot to turn it back ON before I i rebooted. Now the phone is bricked ( I pray it is SOFT not
hard bricked ). When I turn ON the phone it just says "FRP Lock is ON" and then shuts off.
I can enter download mode but NOT recovery. This phone is my work phone and has so much important stuff on it, I just have to fix this.
Plus my wife will shot me for paying $700 and breaking it.
Anyway ... I assume I must go back to stock some how. I can boot to download mode and connect to Odin. But I tried to flash:
1) SM-N920T_1_20160702132553_r0dr7864oe.zip
Also I tried this file ( again via Odin )
2) Noble_Kernel_Auto-Root_N920T_v0.1_Rebuid3.tar.md5
But BOTH files resulted in a FAIL on the Odin screen. ( SEE PIC BELLOW )
Now when I boot it boots to a screen that says this:
Odin Mode
Download Speed: Fast
Product name: SM-N920T
Current Binary: Custom
System Status: Custom
FRP LOCK: ON
Secure Download: Enabled
Knox Warrenty Void: 1
AP Swrev: B:2 K:0 S:0
=========
Custom Binary (Recovery) BLOCKED by FAP Lock
.
Click to expand...
Click to collapse
Sooooo basically I can NOT boot to the OS because the FRP lock is ON and I guess should be OFF, but when I try to Odin Flash I get a FAIL at the end of the flash. ( again see picture bellow )
PLEASE HELP I will try anything. .. My job and my wife are going to kill me soon.....
Cheers to all
Thanks
.
Thibor69 said:
.
Hi - I really am in need of help. My phone which is a T-Mobile Samsung Galaxy Note 5 (was) running latest 6.x firmware,
but custom and rooted via DarkStalker's awesome ROM. All was running fine for months. I did do one thing before my phone died,
I turned OFF developer option and forgot to turn it back ON before I i rebooted. Now the phone is bricked ( I pray it is SOFT not
hard bricked ). When I turn ON the phone it just says "FRP Lock is ON" and then shuts off.
I can enter download mode but NOT recovery. This phone is my work phone and has so much important stuff on it, I just have to fix this.
Plus my wife will shot me for paying $700 and breaking it.
Anyway ... I assume I must go back to stock some how. I can boot to download mode and connect to Odin. But I tried to flash:
1) SM-N920T_1_20160702132553_r0dr7864oe.zip
Also I tried this file ( again via Odin )
2) Noble_Kernel_Auto-Root_N920T_v0.1_Rebuid3.tar.md5
But BOTH files resulted in a FAIL on the Odin screen. ( SEE PIC BELLOW )
Now when I boot it boots to a screen that says this:
Sooooo basically I can NOT boot to the OS because the FRP lock is ON and I guess should be OFF, but when I try to Odin Flash I get a FAIL at the end of the flash. ( again see picture bellow )
PLEASE HELP I will try anything. .. My job and my wife are going to kill me soon.....
Cheers to all
Thanks
.
Click to expand...
Click to collapse
If you are in the latest firmware (PH2) you have to flash the same firmware (PH2)
.
Thank you sir. But ... im not sure how to tell if I am PH2 or not. Either way, could you point me to a download link for the firmware and I will try it .. please
Cheers
josezr said:
If you are in the latest firmware (PH2) you have to flash the same firmware (PH2)
Click to expand...
Click to collapse
Thibor69 said:
.
Thank you sir. But ... im not sure how to tell if I am PH2 or not. Either way, could you point me to a download link for the firmware and I will try it .. please
Cheers
Click to expand...
Click to collapse
I don't know if I can put links here, but here's
https://mega.nz/#!IJ5VlSRC!HPWdi1sjAhsDm1PoCsp_UK2jkSigsjUXsUxo2egcytE
josezr said:
I don't know if I can put links here, but here's
https://mega.nz/#!IJ5VlSRC!HPWdi1sjAhsDm1PoCsp_UK2jkSigsjUXsUxo2egcytE
Click to expand...
Click to collapse
Thank you so much my friend. I will try it and report back.
Cheers
Unfortunately I did the exact same thing as you one time. And unfortunately Odin wouldn't allow me to flash anything. But there was this tool we use to use all of the time for the s4 and it's called Samsung Kies. As in "keys". Basically as long as you can get in download mode it doesn't matter how you brick it.
You just soft bricked it but the bad thing is we can't flash unadulterated version of firmware with Odin. So if frp lock is on Odin is a no go. And when I say unadulterated I mean one that's not directly from Samsung not touched or changed in anyway.... which are hard to come by in many cases in my experience. When the recovery is changed it won't pass an Odin check usually if frp lock is on. Matter of a fact I don't think you can flash anything with fap lock on with Odin. Due to the fact that frp lock is basically saying bootloader locked.
When you turn off oem mode you unlock the checks put in place by the firmware and hardware during boot. Odin uses these checks also so when you try and flash it'll be a no go. Good news for you is this already happened to me and I figured why couldn't I just restore with heimdall. Well that's a no go to. So final solution was to try out kies that I had remembered using heavily with the s4.
1. Download Samsung Kies3. Link: http://www.samsung.com/pk/support/usefulsoftware/KIES/#none
2: Install and open kies.
3. Go to the the tools tab and select firmware upgrade and initialization.
4. It will ask for your model name. Type SM-N900T.
5. Now it will ask for the Serial Number of your device. It is located on the back of your phone toward the bottom. Type that in and hit enter.
6. Now a message pops up and says the device can be restored etc...... Hit OK.
7. Now a message says Now initializing latest version. Hit OK.
8. Now it will Prepare software for initialization.
9. A screen will come up that says "Please follow the steps below to proceed with emergency recovery.
A. Make sure that the device is turned off.
B. Switch the device to recovery mode and reconnect the cable.
- To switch to recovery mode, turn on the device by pressing the Power button while holding down the Volume control "▼" Button and the Home button, and then press Continue (the Volume control "▲") button.
10. When it detects you are in download mode it will take care of the rest.
Try not to make the same mistake again.
I just rebooted with the developer options turned off on Friday. I was on ph1 firmware. Saw joeyv (spelling?) Deodexed stock rom with an option for an Odin installation. Did the installation through Odin and was back to stock. Odin flashed the kernel and tarp combo and was back up and running with root. No information was lost. For anyone else having this problem.
Sent from my SM-G935T using Tapatalk
Thank you JohnMonsour for taking the time to write all that. I will save it for future use if needed. BUT ... thanks to Josezr I got it fixed.
I was able to boot into download mode like I stated, but I just needed the correct firm to flash. They all failed until I tried
N920TUVS4DPH2_N920TTMB4DPH2_TMB.zip ( Thank you Josezr ).
I just flashed that file and Odin completed and phone rebooted to OS. So ALL IS GOOD. My only question now is ... inside the developer
options section ( in settings ) I have turned Developer options back ON but ... all the options that can be set ON or OFF are in the OFF
position and I am not sure which should be turned on. Can anyone please give me a quick run down on how they should be set .. like this:
stay awake on
next ones set to,
on
off
off
off
on
off
ect............
=======================
Debugging
=======================
on
on
off
ect........
=======================
Networking
=======================
on
off
off
ect........
It would sure help me. Thanks again to all 3 of you guys for helping.
Cheers
This is crazy I just ran into my phone becoming locked yesterday. T mobile sent me a update and my phone of course was set to auto update and my phone would do nothing it was a FRP LOCK. All I did was download odin and used this site to walk me through it all files are provided thanks to [ROM] [STOCK] N920TUVU3DPG1 | 6.0.1 | Deodexed | KNOX Free | 7.22.2016 by jovy23. At the bottum of the page is the download and also instruction to use odin. This was a life saver. LINK/ http://forum.xda-developers.com/tmo...rom-n920tuvu1boh4-5-1-1-deodexed-ciq-t3194270. Copy and past everything you need to do to get out of a FRP Lock situation is in this tutorial. Thanks again Jovy23.
JohnMonsour said:
Unfortunately I did the exact same thing as you one time. And unfortunately Odin wouldn't allow me to flash anything. But there was this tool we use to use all of the time for the s4 and it's called Samsung Kies. As in "keys". Basically as long as you can get in download mode it doesn't matter how you brick it.
You just soft bricked it but the bad thing is we can't flash unadulterated version of firmware with Odin. So if frp lock is on Odin is a no go. And when I say unadulterated I mean one that's not directly from Samsung not touched or changed in anyway.... which are hard to come by in many cases in my experience. When the recovery is changed it won't pass an Odin check usually if frp lock is on. Matter of a fact I don't think you can flash anything with fap lock on with Odin. Due to the fact that frp lock is basically saying bootloader locked.
When you turn off oem mode you unlock the checks put in place by the firmware and hardware during boot. Odin uses these checks also so when you try and flash it'll be a no go. Good news for you is this already happened to me and I figured why couldn't I just restore with heimdall. Well that's a no go to. So final solution was to try out kies that I had remembered using heavily with the s4.
1. Download Samsung Kies3. Link: http://www.samsung.com/pk/support/usefulsoftware/KIES/#none
2: Install and open kies.
3. Go to the the tools tab and select firmware upgrade and initialization.
4. It will ask for your model name. Type SM-N900T.
5. Now it will ask for the Serial Number of your device. It is located on the back of your phone toward the bottom. Type that in and hit enter.
6. Now a message pops up and says the device can be restored etc...... Hit OK.
7. Now a message says Now initializing latest version. Hit OK.
8. Now it will Prepare software for initialization.
9. A screen will come up that says "Please follow the steps below to proceed with emergency recovery.
A. Make sure that the device is turned off.
B. Switch the device to recovery mode and reconnect the cable.
- To switch to recovery mode, turn on the device by pressing the Power button while holding down the Volume control "▼" Button and the Home button, and then press Continue (the Volume control "▲") button.
10. When it detects you are in download mode it will take care of the rest.
Try not to make the same mistake again.
Click to expand...
Click to collapse
its so much wrong with this write up its not funny...for one his model number is sm-n920t second if he is in frp lock then he cant turn his phone off, i tried this method it doesnt work period
you can't turn your phone off?
Yeah actually you can hard reset it and then enter download mode....
Hold volume down the home button and power for like 10 seconds then when the screen turns black you quickly hold volume down, home, and power......
You might not be able to turn it off but you can still enter recovery and download mode.
You might not be able to get into recovery depending on how screwed up your phone is.
And kies3 version was the only one that would work with the above method, now kies has checks in place that checks your knox status and if you've tripped knox it won't work. I can rewrite the guide and link the proper kies if it's really necessary. But this is from 2016 so I am sure that I don't need a proper rewrite.
And at this point I'm pretty sure it might not even matter what version of kies is used it probably does all checks server-side. So this method is obsolete for an almost obsolete phone.
Sorry I didn't help you.
Hello,
Please help me. My samsung a8 updated to android 9 and the call recording is disabled. I need to root the phone, but help me please in the following questions:
1. Do i need custom rom?
2. Do i need custom kernel?
3. Will the android self update as now?
So what is the most importnt steps just to root the device?
In my whole life i paid for one software (callrecorder) which is not working now.
Unfortuently there is no clear tutorial to root this phone but you car read here: [GUIDE][17.06.2019] RMM/KG bypass - Root/Install TWRP on Exynos Samsung after 2018
Snypie said:
Hello,
Please help me. My samsung a8 updated to android 9 and the call recording is disabled. I need to root the phone, but help me please in the following questions:
1. Do i need custom rom?
2. Do i need custom kernel?
3. Will the android self update as now?
So what is the most importnt steps just to root the device?
In my whole life i paid for one software (callrecorder) which is not working now.
Click to expand...
Click to collapse
1. Do i need custom rom?
no
2. Do i need custom kernel?
no
3. Will the android self update as now?
if you flashed TWRP, no
1. Do i need custom rom? No
2. Do i need custom kernel? No
3. Will the android self update as now? depend on your settings
1-to root it the first thing is to have OEM Unlock available and enabled in Dev Options
if not keep the device fully on and with data on dont restart, power off or reset for at least 7 days continuously (or a bit more) and you should have it
if it's not shown dot bother with the rest
2-to have Dev Menu available go to settings >> about phone >> software information >> on build number tape multiple times 10 times i guess, you will have a pop up confirmation
once back at settings menu you will find a new choice at the very bottom "Develper Options"
3-next step with to plug ur phone with PC with usb cable
after installing SAMSUNG DRIVERS & ODIN and downloading TWRP (custom recovery)
in ODIN 2nd tab, untick "AUTO REBOOT" VERY VERY IMPORTANT
chose the TWRP file using AP button/option in ODIN
put your phone in download MOD power off completely >> power back on while holding vol+ and vol- at the same time
flash the file using ODIN to your phone
4- now here is the tricky part
after fklashing TWRP if you reboot normaly you will be locked again and you wont have that OEM Unlock option i talked about and you will be stuck
so, after flashing TWRP, press vol- + power button to reboot the phone
AT THE VERY PRECISE MOMENT WHEN PHONE TURN OFF BEFORE POWERING BACK ON WHEN IT BLINK
RELEAS POWER BUTTON AND VOL+ and PRESS POWER BUTTON + VOL+ AGAIN VERY VERY QUICKLY
if successful you should boot into TWRP directly
5-once you are in TWRP wipe everything then format the device (ALL DATA WILL BE LOST)
of course you need to have the needed files already copied in the SD CARD
from twrp after the wipe and formatiing
go to install and flash in that order RMM_Bypass_v3_corsicanu or RMM-State_Bypass_Mesa_v2
then no-verity-opt-encrypt-6.0
then at the end flash Magisk-v19.3
once its done reboot the phone normally, you will have your phone working as normal
once you are in, install Magisk APK MagiskManager-v7.3.2
reboot again
and voilaaa, you should have root and everything shoul be functional for you
allthow of course I will not be responsible for any kind of software or hardware damage, and certainly not ressponsible for any data loss
as it is completely you responsibility
I would like to attach all the files mentioned above, to help better but dnt sems to find how
so you will have to download and gather them from previous posts
Thank you very much, but i have a question. You wrote this:
"4- now here is the tricky part
after fklashing TWRP if you reboot normaly you will be locked again and you wont have that OEM Unlock option i talked about and you will be stuck
so"
I this will happen what csn i do?
The most afraiding thing is to me about rooting if i get a brick.
Snypie said:
Thank you very much, but i have a question. You wrote this:
"4- now here is the tricky part
after fklashing TWRP if you reboot normaly you will be locked again and you wont have that OEM Unlock option i talked about and you will be stuck
so"
I this will happen what csn i do?
The most afraiding thing is to me about rooting if i get a brick.
Click to expand...
Click to collapse
its virtually impossible to brick samsung devices these days. Well, perma-brick that is. I have spent entire evenings after work bricking phones just so i could figure out what caused the brick and then fix it. the worst thing that would happen if the FRP lock gets enabled again is that youd have to go re-disable it.
i guess i didnt really explain that clearly after re-reading it. So, when he says "stuck" he means with TWRP installed and no method of rooting. The phone will boot normally in the situation described in point #4
I have bought a used Samsung S10e (SM-G970F/DS) it came with Android 12 and it was reseted.
My goal is to install iodeOS. Even if the iodeOS website says "Update the stock firmware to the latest" I considered the instructions from LineageOS and installed the latest Android 11 version, following this (https://iode.tech/en/iodeos-installation/#1629185391421-4cf1f5c8-d900) uninstall instructions.
After Android 11 was installed I enabled the developer options. OEM-Unlock was not available. Therefore I followed these instructions (https://www.xda-developers.com/fix-...y-s9-samsung-galaxy-s8-samsung-galaxy-note-8/) and the OEM-Unlock was available again.
Now it seemed that everything is ready to install iodeOS or LineageOS. Therefore I followed this instructions (https://wiki.lineageos.org/devices/beyond0lte/install). It worked fine until "Installing a cutom recovery using heimdall"
after the "heimdall flash --RECOVERY <recovery_filename>.img --no-reboot" command the S10e shows a bar which is filled from the left to the right and then it shows "Custom Binary (RECOVERY) Blocked By OEM Lock"
Now I have no clue what to do :-(
I would be glad for any help.
You need to unlock the bootloader. You've toggled the OEM Unlocking switch, so unlocking the bootloader is the next step.
Make sure you have the Samsung USB drivers installed on your PC.
Turn off your device.
While holding the Bixby and Volume Down buttons, connect your phone to your PC.
The device should start in Download Mode. Hold down Volume Up until you get a warning about unlocking the bootloader. Unlocking the bootloader will wipe your data. Click Volume Up to confirm.
Your device will wipe data, then reboot. At this point, you can reboot to download mode and flash a custom recovery using Odin or Heimdall.
Thanks a lot for all your help!
The problem was I entered the download mode by the adb command "adb reboot-bootloader" and this mode seems to be different to the one which can be accessed by pressing the keys.
Now everything worked fine
I have exactly the same problem here:
SM-A205G with OEM Unlock enabled
There is no unlock bootloader in the bootloader no option anymore
at least in the bootloder of this edition
And I suppose that if it is the bootloader that flashes everything, it is COMPLETELLY LOCKED, could be jailbroken by some new method, but until them... no option :sad:
V0latyle said:
You need to unlock the bootloader. You've toggled the OEM Unlocking switch, so unlocking the bootloader is the next step.
Make sure you have the Samsung USB drivers installed on your PC.
Turn off your device.
While holding the Bixby and Volume Down buttons, connect your phone to your PC.
The device should start in Download Mode. Hold down Volume Up until you get a warning about unlocking the bootloader. Unlocking the bootloader will wipe your data. Click Volume Up to confirm.
Your device will wipe data, then reboot. At this point, you can reboot to download mode and flash a custom recovery using Odin or Heimdall.
Click to expand...
Click to collapse
It seems that this <confirm> option in the bootloader is being removed by samsung, so... even if unlock oem is enabled... it will not work...
I can only reach the bootloader by going to recovery mode them selecting reboot bootloader, or by adb reboot bootloader, but it boots directly in download mode without the option to long-press volume up key
A flasher that doesn't flashes doesn't makes sense. Maybe samsung have hidden something new in there?...
Ok. I've found the solution
1 - Power the phone off
2 - Hold both volume up and down
3 - PLUG THE USB BUTTON WHILE YOU HOLD BOTH these buttons
4 - NO NEED TO PRESS POWER BUTTON
I guess this will work for all phones that don't have the option to start with power+down
Yes. A flasher that does not flash don't exists.
Good luck ! \o/
source:
HELP!!! Custom Binary (BOOT) Blocked By OEM Lock
Hi there, I've been having trouble rooting my Samsung Galaxy A20 - SM-A205GN for awhile now. I'm officially on Android Version 10 with One UI Version 2.0, I've followed the provided guide to root my device but it fails on Odin "all versions" when...
forum.xda-developers.com
wavedevice said:
Ok. I've found the solution
1 - Power the phone off
2 - Hold both volume up and down
3 - PLUG THE USB BUTTON WHILE YOU HOLD BOTH these buttons
4 - NO NEED TO PRESS POWER BUTTON
I guess this will work for all phones that don't have the option to start with power+down
Yes. A flasher that does not flash don't exists.
Good luck ! \o/
source:
HELP!!! Custom Binary (BOOT) Blocked By OEM Lock
Hi there, I've been having trouble rooting my Samsung Galaxy A20 - SM-A205GN for awhile now. I'm officially on Android Version 10 with One UI Version 2.0, I've followed the provided guide to root my device but it fails on Odin "all versions" when...
forum.xda-developers.com
Click to expand...
Click to collapse
Yes, you don't unlock the bootloader VIA the bootloader in Samsung phones.
so you know what happened? I accidentaly reset my phone! I have gone into download mode and there was additional choices: to unlock bootloader holt volup, so I did, then again to confirm unlocking press volup. I did so and then there was for a brief moment android logo and "erasing" and then after about 2 minutes of just Samsung logo phone restarted and asked me to perform setup as it was new! WTH? There was nothing mentioned about deletion
DaHansi said:
I have bought a used Samsung S10e (SM-G970F/DS) it came with Android 12 and it was reseted.
My goal is to install iodeOS. Even if the iodeOS website says "Update the stock firmware to the latest" I considered the instructions from LineageOS and installed the latest Android 11 version, following this (https://iode.tech/en/iodeos-installation/#1629185391421-4cf1f5c8-d900) uninstall instructions.
After Android 11 was installed I enabled the developer options. OEM-Unlock was not available. Therefore I followed these instructions (https://www.xda-developers.com/fix-...y-s9-samsung-galaxy-s8-samsung-galaxy-note-8/) and the OEM-Unlock was available again.
Now it seemed that everything is ready to install iodeOS or LineageOS. Therefore I followed this instructions (https://wiki.lineageos.org/devices/beyond0lte/install). It worked fine until "Installing a cutom recovery using heimdall"
after the "heimdall flash --RECOVERY <recovery_filename>.img --no-reboot" command the S10e shows a bar which is filled from the left to the right and then it shows "Custom Binary (RECOVERY) Blocked By OEM Lock"
Now I have no clue what to do :-(
I would be glad for any help.
Click to expand...
Click to collapse
I had the same problem on my samsung tab a10.1. That's why I had to flash the stock firmware 3 times. Every time I flashed twrp with odin, I got the error (custom binary blocked by oem lock).
I write what they should do in order.
1. Turn on the phone.
2. Open Developer mode
3. USB debugging mode - on
4. oem unlocking - on
5. then turn off the phone and disconnect from usb
6. Connect the phone to the PC with USB by holding down the volume up and volume down buttons at the same time. WITHOUT PRESSING THE POWER BUTTON
7. Press and hold the volume up button according to the instructions in the pop-up window.
oem unlocked
Sorry that, I had another problem. May I know how to unlock the OEM if my S10e phone can't turn on.
My device always on "samsung" display page, can't open to index. Do you know this issue? Expecting your reply.
Hi! I have the same issue on my Xiaomi Mi 11 Pro (It was Chinese) but it came unlocked with xiaomi.eu rom.
After i installed a global rom, and google wallet nfc pay did not work, so i thought okay i will lock it then so maybe wallet would accept it, (with the eu rom it worked before) so i put the device in fastboot and used fastboot oem lock on cmd...
And from then it stucks on miui recovery 5.0 screen, and says, this miui version can't be installed on this device...
I might not enabled oem unlocking before i shut if off, but i added it to my mi account so i dont know if after a week i can maybe unlock it. But i think the other possible solution would be to sideload the original chinese stock rom, which is for M2102K1AC, Mi 11 pro, codename mars, but i couldn't find it anywhere... If someone can upload a link to it, that would be a huge help! Or any idea! thx!
geraldmany said:
HI! i got a mi 11 pro 1 year ago, and it was offically chinese, but it came unlocked with Xiaomi.eu firmware, but i could't update it via the updater app, so i searched and found the global star version and just flashed it, everything worked, only now google pay nfc didnt work, it said that its probably because of the unlocked bootloader, so i got to fastboot and in cmd i sent fastboot oem lock, and since then my phone is stuck in miui recovery 5.0 screen and says that i cannot run this firmware on the device, i tried to unlock it but failed, maybe after a week, but i think that i didnt turn on oem unlocking on the phone itself before this... So im just hoping that after a week unlocking could be done... Or my other idea is, that i could install the original chinese rom with sideload, because i managed to install another global version on it since, but the result is still the same, the only problem is that i cannot find literally anywhere a mars codenamed firmware...
Click to expand...
Click to collapse
Anyone who might have the same situation, i found a simple, but effective solution, not sure if it works on every xiaomi device, but i will write down the steps here:
You need to use XiaomiADB, here is the download link and the description for how to use it -> https://xiaomiui.net/how-to-use-xiaomiadb-8044/ (if the page is not available, then feel free to msg me!)
For xiaomi adb, you need to go to 3rd option on the miui recovery screen, NOT THE FASTBOOT
So basically i went through the steps to “xiaomiadb sideload_miui <filename>”
And I tried to install a rom, BUT IT DIDNT ACCEPT IT!
The message was:
ERROR: This rom cannot be installed, server code -> 2001, server message -> Can't install unofficial rom
after trying 4 times all the same and: Installation of this rom via stock recovery is not allowed by Xiaomi
Says Installation failed, and then i just decided to download another rom so i PLUGGED OUT THE PHONE right after this, and went to another room to connect to wired network, to download and try a different rom... when i came back, to all my surprise, the phone was turned on, so i went to the setting dev ops and enabled bootloader unlocking, linked it to my account enabled adb and everything that is needed to flash another rom later, so then i rebooted and again, miui recovery 5.0 screen, but now i enabled unlocking, so i put the phone in fastboot, and tried MI UNLOCKER TOOL again, now it says: Please unlock 168 hours later. And do not add your account in MIUI again, otherwise you will wait from scratch.
So that means, after 7 days i wll be able to unlock it, until then, i can turn it on with the above method, in short try to sideload (copy and install) a rom to it, and then after it failed, plug it out and just wait like 10-20 maybe 30 seconds and bam your device is normally booted... I hope it helps to some of you, (i have been searching for the solution for almost a week, my other option was to pay someone who can MAYBE do it or send the phone back to china and pay the repairs, so im really happy with this method! If it helps to you, please reply so i and the others will know that it worked! Have a nice day!