Related
A long time ago I rooted my phone and put CM9 on it. I decided I wanted to go back and try Jelly Bean (from factory then go outwards).
I had a difficult time with the CM flash and found one that worked, and thought I was good to go.
My phone: gt-i9020a nexus s
Product name: Herring
HW version 16
boot loader: i 9020xxkl
carrier att
fastboot enabled
unlocked state.
I can launch the official 2.3.6 (Build GRK39F), from google
then the OTA updated kicks in and the phone is stuck at 'boot' Google logo on the screen.
I have done the information below and the same keeps happening...
link: http://forum.xda-developers.com/showthread.php?t=1586845
first of all, the VQ8PQk is a patch file, not a full rom. So flashing that on something else than 2.3.6 will never work. Get into clockworkmod recovery wipe wverything from the mounts and storage menu, and then flash this file : http://android.clients.google.com/pa...o/ZD3PyN0t.zip and THEN this : http://android.clients.google.com/pa...o/hR7QFEtn.zip
and other steps I could try to work around, none of them seem to work.
Am I missing anything?
Thanks!
Use the full factory rom images (sojuaxxxx) from Google.
https://developers.google.com/android/nexus/images#sojua
Follow the instruction on that page (scroll up). If using Windows, use 7zip (or similar util) to expand the .tgz file, open content of "flashall.sh" and execute the commands one at a time.
Code:
fastboot flash bootloader bootloader-crespo-i9020xxlc2.img
fastboot reboot-bootloader
fastboot flash radio radio-crespo-i9020uckj1.img
fastboot reboot-bootloader
fastboot -w update image-sojua-jro03e.zip
The last command will wipe all data and install new 4.1.1 rom.
Edit: install CYGWIN to have linux-like commands (works with tar, adb, fastboot) in windows.
Do you have a backup (preferrably CWM backup) that you have prior to trying to get JB working? If so keep that handy, and preferrably store it on the PC. Titanium backup can ease migrating apps after a wipe and is highly recommended, so do one of these too if you havn't already.
After you make sure you have a solid backup with the information that you want/need on the phone, i would just start fresh. The best way to do this is to do a factory image flash (note: you want sojua if you have the 850MHz variant which is from AT&T). Flashing these will wipe all user data and the /system partition, the sdcard won't be touched. Basically you download it, extract it, then hook up your phone in fastboot mode and do the commands as written in the text file (or run it as a script if you know how). I've described it in more detail elsewhere as have others, doing a search should give results pretty quickly
This will become a factory install of android as given by google, in your chosen version. I'd go straight ot JB and then you can see how much you like it. CWM backup data can be extracted if you lost some crucial information in the flashing and all your apps and their data can be easily restored with titanium backup.
morning update
_android_ said:
Use the full factory rom images (sojuaxxxx) from Google.
Follow the instruction on that page (scroll up). If using Windows, use 7zip (or similar util) to expand the .tgz file, open content of "flashall.sh" and execute the commands one at a time.
Code:
fastboot flash bootloader bootloader-crespo-i9020xxlc2.img
fastboot reboot-bootloader
fastboot flash radio radio-crespo-i9020uckj1.img
fastboot reboot-bootloader
fastboot -w update image-sojua-jro03e.zip
The last command will wipe all data and install new 4.1.1 rom.
Click to expand...
Click to collapse
running linux, no cygwin needed
did this again this morning..and i'm stuck on the google boot screen with the unlocked padlock on the bottom.
how long should this run (20 minutes now)
I have tried the roms from that page, the 2.3.6 is the only rom that I was able to get working..
lost_man said:
running linux, no cygwin needed
did this again this morning..and i'm stuck on the google boot screen with the unlocked padlock on the bottom.
how long should this run (20 minutes now)
I have tried the roms from that page, the 2.3.6 is the only rom that I was able to get working..
Click to expand...
Click to collapse
Make sure you use the sojua versions.
Do you mean you finish all the steps and upon reboot, it's stuck on Google boot screen?
What do you mean by you can only get 2.3.6 working? It went past Google boot screen?
** ran 'flash-all.sh" see if that changes anything, nothing like a script to rule out human error.***
**** that was a mistake...now phone is not turning on, the screen is dead...when i plug in USB chord, nothing is detected no state change on the phone. When I press buttons no state change nothing changes on the screen. I actually think my phone is a true brick, not a software glitch that is fixable....any suggestions now? ****
lost_man said:
** ran 'flash-all.sh" see if that changes anything, nothing like a script to rule out human error.***
**** that was a mistake...now phone is not turning on, the screen is dead...when i plug in USB chord, nothing is detected no state change on the phone. When I press buttons no state change nothing changes on the screen. I actually think my phone is a true brick, not a software glitch that is fixable....any suggestions now? ****
Click to expand...
Click to collapse
Some (quite a few) Nexus S seemed to be vulnerable to Jelly Bean/CM10 update in that the mainboard is toast. I think the only option is to send back for warranty repair. There are some threads on rigging some kind of adapter cable but that will definitely void your warranty (physical mod).
Doesn't sound good, there have been instances where the flash storage has given up and ends up needing a new SoC (the whole mainboard) and similar issues. Some more information would be good to diagnose this better though.
-Take the battery out for 5 minutes, place back in, can you get into fastboot?
-Can you flash recovery and radio? Can you enter recovery?
-After the "fastboot -w update ...." command, what messages do you see on the phone (at the bottom)?
If you can't get the phone to turn on at all after a good 5 minutes without the battery inserted, give AdamOutlers resurrector a shot. A nice phone call to samsung might be a good idea if you're still within 12 months of purchasing. Hopefully it all turns out okay.
-Take the battery out for 5 minutes, place back in, can you get into fastboot?
-Can you flash recovery and radio? Can you enter recovery?
-After the "fastboot -w update ...." command, what messages do you see on the phone (at the bottom)?
If you can't get the phone to turn on at all after a good 5 minutes without the battery inserted, give AdamOutlers resurrector a shot. A nice phone call to samsung might be a good idea if you're still within 12 months of purchasing. Hopefully it all turns out okay.
Click to expand...
Click to collapse
Did all of the above, nothing. adamoutliers does not see a device connected.
lsusb shows nothing
dmesg shows my device disconnect, after the failed boot, no reconnect.
I'm headed out for a few hours, I will leave battery out, and phone disconnected but i'm thinking it's toast. Att will send an RMA phone to me, they gave me a choice of samsung focus (I asked how a windows phone was similar to an android?) or a samsung galaxcy II skyrocket...I'll try samsung next..
Thanks for all the help!
lost_man said:
Did all of the above, nothing. adamoutliers does not see a device connected.
lsusb shows nothing
dmesg shows my device disconnect, after the failed boot, no reconnect.
I'm headed out for a few hours, I will leave battery out, and phone disconnected but i'm thinking it's toast. Att will send an RMA phone to me, they gave me a choice of samsung focus (I asked how a windows phone was similar to an android?) or a samsung galaxcy II skyrocket...I'll try samsung next..
Thanks for all the help!
Click to expand...
Click to collapse
How do i close this thread? It's done, the phone is dead...rma...
I need help to update my phone, I bought this phone from a friend, the phone now has unlocked bootloader. CM10 installed, what steps should I take to upgrade to jb? - also has twrp recovery installed.
Thank you in advance.
--I have the RSD Lite v6.1.4 installed and motorola drivers too, and the file asanti_c_sprint-user-4.1.2-9.8.2Q-122_XT897_FFW-5-6-release-keys-cid9.xml , Downloade. just need help about what to do now!
I am in the same boat. Long time windows mobile user, and jumped ship when the photon Q came along.
Looking for an step by step idiots guide to backing up what I have and how to flash the new.
Would be willing to send a guy a few paypal bucks for your time to write it up.
RSD LIte is a minimal UI, windows app, not much to think about. Plus, this topic has been discussed and explained all over the web (that includes xda forums)
1) boot device to bootloader (power + camera - then select fastboot/bootloader - additional info on how to select is written on bootloader screen)
2) verifiy your device is recognized in fastboot mode
3) select file to flash
4) press start button
5) wait 'till device boots to android
http://www.youtube.com/watch?v=AHaEHjSzvQQ (different device, same procedure)
That simple (if you can get pc/rsd to recognize the device )
mrvek said:
RSD LIte is a minimal UI, windows app, not much to think about. Plus, this topic has been discussed and explained all over the web (that includes xda forums)
1) boot device to bootloader (power + camera - then select fastboot/bootloader - additional info on how to select is written on bootloader screen)
2) verifiy your device is recognized in fastboot mode
3) select file to flash
4) press start button
5) wait 'till device boots to android
http://www.youtube.com/watch?v=AHaEHjSzvQQ (different device, same procedure)
That simple (if you can get pc/rsd to recognize the device )
Click to expand...
Click to collapse
i follow all the steps but i get stuck on, flashing NON-HLOS.bin" partition="modem, It fails right there. any ideas ? thanks
* I need to remove any other line? I have removed the 2 lines required.
never mind!
VICTORY running rooted jelly bean with TWRP recovery!
I think now I learned about motorola phones It is very easy but takes a while, when you know nothing lol. I've always been on the HTC phones.
( SOLVED )
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:
I could really use some help on this one. I rooted my phone back in the summer of 2017 and used the Pure Nexus rom. I have not had any problems and did not do any updates since then.
Out of nowhere my phone shuts off. When I try to boot it, the screen flashes between being static (like a TV without reception) and the google screen that is off center (instead of google being in the middle, it only briefly displays "oogle" to the left side of the screen). I can access my bootloader, which is still unlocked, but I can no longer get into my recovery.
Any help is greatly appreciated. I do not remember which version of firmware I had but i do not think I ever updated it from the original firmware the phone came with.
Thanks in advance
Update: I think it is only fastboot I can get into, not the bootloader. i think I am on 7.1.2. It is the google store phone. I tried using the SkipSoft android toolkit to both install and sideload the factory stock image and it would not work, It just says, FAILED (remote: verify bootloader image failed on production device)"
I'm really stuck on this one
Try doing the update manually. Download the latest factory image file, and double-check the checksum value. Unzip the file and open a command prompt or terminal window in that directory. Separately, open the flash-all.bat or flash-all.sh file in a text editor. Run each of the flash commands yourself, and see where the errors show up. Copy/paste or screenshot any errors, and let us know what happens.
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!