Database Users

Confuse about unlocking bootloader

I bought this tablet and I want to install a custom rom. I am not interested in dual booting. I found a thread titled
"[GUIDE]A500/501/G100W-Installing ICS V8 UNL-BL & CWM Or back to HC BL(24-6-2012) "
Information there is a little confusing to me. On my A200, the steps were simple, unlock boot loader, install CWM and then root/install rom. Then I was done. Seems like I have to do more steps on theA500, which I don't mind I just want to do it right. Is it my understanding that the thread is for dual booting, it also talks about CPU ID.
I found another thread that talks about Afterota v1.09, do I only need to just do this for what I want to do or do I need to do more? Why would I need to install a ICS bootloader, I have ICS now, stock, doesn't it already have it? I tried looking at the Q/A but I just ended up more confuse.
Could someone just give point me in the right direction so I can go about unlocking bootloader and installing CWM so I can install a custom rom.
I have Android 4.0.3 Kernel Version 2.6.39.4+ Stock
Side question, my unit is a 16gb model but its only reading about 12.71gb, does anyone know why?

A500 works differently: the stock ICS BL is locked and cannot be unlocked from fastboot. What we can do however, is to flash custom BL, since we know the device "Secure Boot Key". In general the term "ICS BL" means my patched BL, which you can find in my signature. There is a bunch of guides to get it flashed on the forum, and blackthunder made a tool to simplify the process.

Skrilax_CZ said:
A500 works differently: the stock ICS BL is locked and cannot be unlocked from fastboot. What we can do however, is to flash custom BL, since we know the device "Secure Boot Key". In general the term "ICS BL" means my patched BL, which you can find in my signature. There is a bunch of guides to get it flashed on the forum, and blackthunder made a tool to simplify the process.
Click to expand...
Click to collapse
Alright, so I do not need to do
Option 1 use Afterota for A500/G100W IF YOU ARE ON OTA ICS and follow this thread
or
Option 2 , keep reading.... don't be a chicken , just do it !!.
then I just need to use blackthun3r tool? I tried it but when I launch A500APXFLASH.EXE it ask me for a SBK and the guide said this "the v0.4 APX flash tool will give your SBK automaticly !!" but its blank it has not given me SBK automatically. So I was directed to this thread
http://forum.xda-developers.com/showthread.php?t=1810618
which has the "SBCalc "
which then directed me to
http://forum.xda-developers.com/showthread.php?t=1624645
which reads
GET ME MY CPUID!!!
There are 2 different cpuid
ICS CPUID has only 13 digits/characters and is your "serial no." as reported in settings, on your sdcard cover and on the box
we are only interested in the 15 digit HC CPUID this can only be got:
(1) From a PC using Blackthund3rs A500 manager
(2) From your device using Terminal Emulator App
(3) From USBDeview must have previously used the Tab under HC with the PC you're using
(4) From a uid.txt in any Honeycomb-cwm backup in external_sd/clockworkmod/backup/"your_HC_backup" folder
(5) From adb devices if you're running honeycomb
(6) From cwm 1.7.2 via on screen display and a text file - great if you are on ICS already
(7) Master_Ellis has posted that he found the HC cpuid in /sys/firmware/fuse/acer_cpuid - add a zero to the front!!!
please if anyone uses this let us know if this is correct!!!
thanks Master for the heads Up!!!
(8) Gersma's most excellent OTA Toolmakes most of this thread obsolete!!!! Thankyou Gersma for all you've done OTA Tool is all anyone ever needs....
Features :
I don't get it though, I thought you said all I needed was the blackthund3r apx flash utility. I'm really confuse, can you specify what I need to do?
I went back to the original thread where the blackthund3r flash tool is and it clearly says
"3-When it askes for your SBK you need to type it in , the v0.4 APX flash tool will give your SBK automaticly !!"
But I do not see the SBK come up automatically. Man all I want is to be able to flash roms ;/ Can you specify what I need to do please I do not want to jump the gun here and brick my device. I see two files in the zip file, a500 Manager v1.0.2 and Apx Flash Utility v0.4

Alright I figured out what I was missing and manage to go through the whole process easily. I have Apex now but how do I install CWM or TWRP? WHen I go into recovery I get a dead android.

Lots of trials and errors lol so I figured out Recovery only works the first time, is there any way to have CWM on there permanently?
Update
Recovery always works now, wasn't sure if that was a glitch or what. Anyways, thanks Skrilax, that little piece was enough for me to get going. I understood the guide once I knew what I needed which required me reading a few threads. Guide kinda needs to be tweaked a little.

F9zSlavik said:
Lots of trials and errors lol so I figured out Recovery only works the first time, is there any way to have CWM on there permanently?
Update
Recovery always works now, wasn't sure if that was a glitch or what. Anyways, thanks Skrilax, that little piece was enough for me to get going. I understood the guide once I knew what I needed which required me reading a few threads. Guide kinda needs to be tweaked a little.
Click to expand...
Click to collapse
Recovery not sticking is due to having a stock rom. Rooting with ICS Root 7.1.1 stops this
Sent from my Iconia A500 using Tapatalk 2

Just noting: stock recovery won't work, and if you ever applied OTA, booting Android will overwrite recovery, unless you remove the updater. And for the guides, all will work, some are more automated, some less.

Question About Software Error Message

Hi guys. Not new to rooting but new to my AT&T S4. I rooted it tonight with Motochopper and installed CWM recovery. Downloaded and tried to flash a ROM, and it simply didn't work. Then I tried Beanstalk 4.2.2, and it downloads, but then when I rebooted it, it gave me the yellow triangle unauthorized software message. So I pulled the battery and finally got it to boot into recovery, then installed the back up I had from the stock OS. My question is two fold-what's causing this and if I download a ROM with the Loki patch, will that bypass the error message I'm getting. I searched the forums but am not understanding what was written. I'm pretty confused, any help would be greatly appreciated.

chokem said:
Hi guys. Not new to rooting but new to my AT&T S4. I rooted it tonight with Motochopper and installed CWM recovery. Downloaded and tried to flash a ROM, and it simply didn't work. Then I tried Beanstalk 4.2.2, and it downloads, but then when I rebooted it, it gave me the yellow triangle unauthorized software message. So I pulled the battery and finally got it to boot into recovery, then installed the back up I had from the stock OS. My question is two fold-what's causing this and if I download a ROM with the Loki patch, will that bypass the error message I'm getting. I searched the forums but am not understanding what was written. I'm pretty confused, any help would be greatly appreciated.
Click to expand...
Click to collapse
So, to sum up development in this forum for the last 3 months: The ATT version of the S4 has a locked bootloader, which is a fancy way of saying ATT and Samsung don't want custom software on their phone partitions. To keep people from installing custom ROMs, their bootloader requires a verified signature present in the ROM to actually allow the device to boot.
An individual found a way to trick this verification process, and created a patch for it called LOKI.
When a ROM is "Loki'd" it contains this workaround for the verification process in the bootloader, allowing custom software to be installed.
To answer your question, when you root your phone and install the recovery (TWRP or OUDHS): a ROM must be lokied to work. OUDHS recovery has a feature which automatically installs the workaround in every ROM you flash using the utility. I recommend this version of Clockwork Recovery.
The link is here:
http://forum.xda-developers.com/showthread.php?t=2291956
I personally use the nightly CyanogenMod 10.1 builds for the ATT S4 (called jlteatt). They're quick and stable except for a few quirks with the camera, call-audio via headsets, and bluetooth audio.
The link to download is here:
http://get.cm/?device=jflteatt
*This version of CM 10.1 is already Loki'd
Have fun flashing, and if all else fails and you accidentally run into a scenario where you can't boot your phone, use this utility to restore the factory OS that comes with the phone.
http://forum.xda-developers.com/showthread.php?t=2261573

Furies said:
So, to some up development in this forum for the last 3 months: The ATT version of the S4 has a locked bootloader, which is a fancy way of saying ATT and Samsung don't want custom software on their phone partitions. To keep people from installing custom ROMs, their bootloader requires a verified signature present in the ROM to actually allow the device to boot.
An individual found a way to trick this verification process, and created a patch for it called LOKI.
When a ROM is "Loki'd" it contains this workaround for the verification process in the bootloader, allowing custom software to be installed.
To answer your question, when you root your phone and install the recovery (TWRP or OUDHS): a ROM must be lokied to work. OUDHS recovery has a feature which automatically installs the workaround in every ROM you flash using the utility. I recommend this version of Clockwork Recovery.
The link is here:
http://forum.xda-developers.com/showthread.php?t=2291956
I personally use the nightly CyanogenMod 10.1 builds for the ATT S4 (called jlteatt). They're quick and stable except for a few quirks with the camera, call-audio via headsets, and bluetooth audio.
The link to download is here:
http://get.cm/?device=jflteatt
*This version of CM 10.1 is already Loki'd
Have fun flashing, and if all else fails and you accidentally run into a scenario where you can't boot your phone, use this utility to restore the factory OS that comes with the phone.
http://forum.xda-developers.com/showthread.php?t=2261573
Click to expand...
Click to collapse
OK, thanks very much. So I was indeed on the right track. I'll try your ROM recommendation as well as the modified CWM recovery.

Help Recovering Please

I eventually decided to flash Kitkat onto my Defy+.
Followed this guide here:-
http://forum.xda-developers.com/showthread.php?p=52342403#post52342403
Everything worked fine until I got to the actual flashing of the KK Rom. TWRP had loaded fine but insisted I had no OS installed and on exit suggested device was not rooted?
Phone kept saying failed and to re partition. So I tried the Resize.zip from another guide. This did nothing either , still the same.
It had also had the following error, "Error Executing Updater Binary In Zip".
So I tried the solution here:-
https://kalitutorials.wordpress.com/2015/06/19/solve-error-executing-updater-binary-in-zip/
Now I cannot boot into TWRP or Clockworkmod recovery. When I try to boot phone it just sits on Motorola Sign but doesn't progress and no led flashes to enter TWRP. Battery needs to be removed to switch off.
If I power up with Volume down pressed, I get picture of Android Green Robot standing up with an yellow exclamation in a white lined triangle. No options are shown.
Pressing Vol up and down I get me to Android System Recovery <3e>. Options there are, reboot system now, apply update from sdcard, wipe data/factory reset, wipe cache partition.
I can also enter bootloader using vol up and power.
Any ideas anyone, found this guide to try to fix but don't want to try anything else without some confidence it will work.
http://www.tech-zealots.com/tutorials/unbrick-motorola-defy-or-defy-100-working/
I have a nandroid backup created in normal recovery btw. I would prefer to flash back to it if possible.
Thanks
G

You need to download a sbf file https://mega.nz/#!915TCAAD!X7_f1t83lVPkK5p7jUdokeE4SQ8qTRqPnBWNvfgyxWA (this one is stock android 2.3.6), then you need to install drivers and rsd lite and connect your phone (must be already in bootloader mode) to your pc and then reflash the sbf file. After that, your phone will boot up to the stock firmware and you can install cm11 then. Basically you can follow up the the guide that you posted. Good Luck

dc239 said:
You need to download a sbf file https://mega.nz/#!915TCAAD!X7_f1t83lVPkK5p7jUdokeE4SQ8qTRqPnBWNvfgyxWA (this one is stock android 2.3.6), then you need to install drivers and rsd lite and connect your phone (must be already in bootloader mode) to your pc and then reflash the sbf file. After that, your phone will boot up to the stock firmware and you can install cm11 then. Basically you can follow up the the guide that you posted. Good Luck
Click to expand...
Click to collapse
Thanks for your reply.
Tried what you suggested but after flashing that sbf the phone tries to boot up but after logo drops back to bootloader 9.10 with ERR:a5,69,35,00,27 .
I managed to get the Retail UK sbf referred to here:-
http://forum.xda-developers.com/showthread.php?t=1421526
Tried flashing it but end up with a black screen bootloader and just white led lit. Reflashed the sbf u suggested and back to Bootloader with Err.
Googling seems to suggest I am just needing to get the right sbf for the phone.
I have the Nandroid backup made with Clockworkmod recovery. Is there anyway to flash it?
TIA
G

Sorted
After extensive digging and climbing the steep learning curve. Decided the problem was that the sbf file u suggested was DFP 231 and possibly my phone was DFP 2311. Found Firmwares here:-
https://firmware.center/firmware/Motorola/Defy+ (MB526)/Stock/
And downloaded the DPF 2311 Rom, only was one. (DEFYPLUS_U3_4.5.1-134_DFP-2311_BLUR_SIGN_USADEFYEMARAB1B8TFDE004.0R_PDS03C_USAJRDNGIBRO2DE_P020_A025_M002_Service1FF.sbf). Tried flashing it and voila system is back, albeit it started up in German.
Gonna try the rooting mehod here:-
http://forum.xda-developers.com/showthread.php?t=1820282
For anyone elses benefit, the links for Roms at Android Developers don't work. The retail EU Firmware mentioned in the rootong guide is available on the site referred to above. U can tell when you click the link to the Android Developers site as the browser URL shows the full file name as follows.
DEFYPLUS_U3_4.5.1-134_DFP-231_GR_SIGN_UCADEFYEMARAB1B80AA004.0R_PDS03C_USAJRDNGIBRRTCEE_P022_A022_Service1FF.sbf.gz
The rooted one I think is the same one you linked me to and is still valid in the Rooting guide too.
Thanks for all help and I hope this is of use to someone else.
G

Minor question still remains.
If I am trying to install Kitkat rom. DO I still need to Root phone if the rooted 231 has been installed, I presume not?
G

Followed rooting guide and so now have a rooted 231. All good
Now for KK.
G

Samsung Galaxy Core Prime SM-G360P TWRP issues

Hello everyone,
I am posting today to bring up the subject of the SM-G360P variant of the Samsung Galaxy Core Prime.
I am having issues with getting TWRP custom recovery to work properly on my device. I am able to flash twrp-3.0.2-0-coreprimelte.img onto my device and it works except for 2 things that i have noticed that makes me very upset and i cant figure out what to do. When i enter recovery mode the back light does not function so i have to use a bright flashlight to see any of the options and the second problem is the GUI is upside down but the button mapping is in the proper place so i have to guess on where to tap on my screen. This makes it very frustrating to use especially when i want to wipe dalvik cache and the regular cache. I accidentally factory reset my device once by tapping the wrong spot. If anyone would be willing to help me out with my problem i am willing to be a guinea pig with anything you can try for the custom recovery to make the GUI reflect the proper button mapping and the back light to work. I can re-flash my device as many times as necessary to get a working custom recovery. I have included the recovery.fstab and the stock recovery along with the version of TWRP custom recovery i have been utilizing to an extent.
I am using the BST Australian variant of SM-G360P which can be rooted with Kingo Root and KingRoot. I used Kingo Root so i could use the SuperUser app rather than just using KingRoot. I have used CROM Service to unlock my bootloader. I have also tried to use CWM custom recovery on my device but it does not register the CWM custom recovery that is available for my device it just goes to a "fake" Odin mode screen. I would really love to get TWRP custom recovery working properly. I have tried to port both TWRP and CWM custom recoveries by using Android Image Kitchen but have not had any success at creating a recovery that works without the same issues i have with TWRP custom recovery. I am running 4.4.4 KitKat OS which is the latest update for SM-G360P and have full root permissions. If you need any other dump files or any other information i will gladly give it to you. I may need directions on how to do some things though.
I will be greatly appreciative if someone would have a look at what the problem may be with TWRP custom recovery and my Variant of SM-G360P. Please help. Thank you for your time and contribution.

Hello @sosthenisRR. I just got this device, the Boost Prevail LTE American version. I was wondering if you've made any headway finding a TWRP for it. I will be trying some things myself... Gotta have TWRP... And I wanted to let you know that if you root with kingroot, super-sume (free version) works to get you supersu.

Odin TWRP 2.8.7.0 for the SM-S820L...it works, i tried V3 as well with no favorable results.
https://forum.xda-developers.com/galaxy-core-prime/development/twrp-2-8-7-0-sm-g360p-t3462592

eeriikk said:
Odin TWRP 2.8.7.0 for the SM-S820L...it works, i tried V3 as well with no favorable results.
https://forum.xda-developers.com/galaxy-core-prime/development/twrp-2-8-7-0-sm-g360p-t3462592
Click to expand...
Click to collapse
If that doesn't work, install and run this apk, this is what finally allowed me to Odin TWRP to my G360P without errors. Now if only we could get a custom ROM for this variant...

New to SM-T280. What's the status of bootloader, root and TWRP?

I recently picked up a Samsung SM-T280. The first thing I did was to come to XDA and see what modifications are possible. I haven't read everything but I've read a LOT trying to learn what the situation currently is as regards this device. A forum that tracks several different devices together (SM-T580, SM-T350, etc) makes this process a bit harder.
Ideally I'd like to unlock the bootloader, root the device, install TWRP then install a custom ROM. From what I've been able to gather:
- It appears to not be possible to unlock the bootloader of the SM-T280
- There are several methods to root the SM-T280 and then install TWRP
- There seem to be a couple of custom ROMs for the SM-T280, although I may be misreading this as I thought you couldn't install a custom ROM on a device with a locked bootloader.
Could someone who's followed the development of the SM-T280 far more closely than I give me a general sense of what's currently available for this device? I AM reading the threads in the forum and I AM trying to look these things up for myself. I just can't be sure that what I'm reading constitutes the best and most undated information.

lesdense said:
I recently picked up a Samsung SM-T280. The first thing I did was to come to XDA and see what modifications are possible. I haven't read everything but I've read a LOT trying to learn what the situation currently is as regards this device. A forum that tracks several different devices together (SM-T580, SM-T350, etc) makes this process a bit harder.
Ideally I'd like to unlock the bootloader, root the device, install TWRP then install a custom ROM. From what I've been able to gather:
- It appears to not be possible to unlock the bootloader of the SM-T280
- There are several methods to root the SM-T280 and then install TWRP
- There seem to be a couple of custom ROMs for the SM-T280, although I may be misreading this as I thought you couldn't install a custom ROM on a device with a locked bootloader.
Could someone who's followed the development of the SM-T280 far more closely than I give me a general sense of what's currently available for this device? I AM reading the threads in the forum and I AM trying to look these things up for myself. I just can't be sure that what I'm reading constitutes the best and most undated information.
Click to expand...
Click to collapse
It is a complicated and sad story. Lol. No there is root for device but it is Samsung and do not use bootloader to root. Little different with Sammy. There is an app for PC called Odin that directly flashes you rom if it's in tar format. . Md5 also works. Or you can use heimadal but I have no experience with this. @ashyx has a guide to rooting device and it worked perfect for me. I actually am without a PC at the moment and have had to flash. Img files to get back to kinda stock recently. Rom development is almost moot for our device although the 285 had a crap ton of stuff and our s had all the same insides from what I can tell even the ril files. They and phone. Sec have been blocked but if you expierement you may be able to get a working rom with the 285 files. I could be wrong though. I would just stick with the one available for 280 if you are not familiar with rom making (like myself). It is called tinker edition and is rooted with Xposed installed all beit a old version. But I thank that man everyday for that rom. Really makes a huge difference in usability. If I can help in any other way let me know good luck

That was incredibly helpful! Thanks for taking the time. I've used Odin many times so I'll likely start with Odin for root and TWRP. No unlocked bootloader is a shame but root is the thing I need most, as I imagine is true for most people. Thanks again.

Thanks. I was gathering info for rooting my device and most one-click roots don't work. I have the same model, the SM-T280. So Odin would work even with a locked bootloader? And will it wipe any data?

androidmagnet said:
Thanks. I was gathering info for rooting my device and most one-click roots don't work. I have the same model, the SM-T280. So Odin would work even with a locked bootloader? And will it wipe any data?
Click to expand...
Click to collapse
Sorry, I hope this isn't too late. Yes, odin will flash directly to the device. First you will get the .tar for twrp and flash it using the ap slot in odin. Make sure to be ready to hit the keys to go into recovery.(power vol+ and home) you have to get in to the twrp recovery to format data the very first boot otherwise the stock system will overwrite recovery and you have to flash it again.

remarkablecow913 said:
Sorry, I hope this isn't too late. Yes, odin will flash directly to the device. First you will get the .tar for twrp and flash it using the ap slot in odin. Make sure to be ready to hit the keys to go into recovery.(power vol+ and home) you have to get in to the twrp recovery to format data the very first boot otherwise the stock system will overwrite rcovery and you have to flash it again.
Click to expand...
Click to collapse
Thanks!

Has there been any significant updates to this? It's hard to understand if custom rom was created or not since SM-T280 shows up in search along with SM-T285 and other A tablets.
So far I've been able to flash TWRP and install SuperSu, but I don't understand what to do from there. There is Tinker Edition out for the SM-T280 but I cannot for the life of me find out what that is and what it can do.
I'm on the fence whether to return this tablet after buying it on black friday for a more rootable tablet, or even a 7th Gen fire.

Lainwolf said:
Has there been any significant updates to this? It's hard to understand if custom rom was created or not since SM-T280 shows up in search along with SM-T285 and other A tablets.
So far I've been able to flash TWRP and install SuperSu, but I don't understand what to do from there. There is Tinker Edition out for the SM-T280 but I cannot for the life of me find out what that is and what it can do.
I'm on the fence whether to return this tablet after buying it on black friday for a more rootable tablet, or even a 7th Gen fire.
Click to expand...
Click to collapse
Did you manage to install any custom ROM to T280??
How have you managed to root it? Any guide you followed?
Thanks

Mathsiel said:
Did you manage to install any custom ROM to T280??
How have you managed to root it? Any guide you followed?
Thanks
Click to expand...
Click to collapse
I managed to root it using the many guides on the site. Unfortunately I did return the tablet because there are no custom ROMs for the T280, and likely there won't be any.

i didn´t can install a new twrp and i m sooooo streesed D´x somebody knows how can do it? odin give me PASS and green, but when i try to open the twrp new open the same old twrp. when the odin finish, in the tab on mode download say.
¨ ODIN MODE
SECURE DOWNLOAD: ENABLE
MDM DOWNLOAD BLOCK: 0
PRODUCT NAME: SM-T280
CURRENT BIN: CUSTOM
SYSTEM STATUS: CUSTOM
FAP LOCK: OFF
USB INIT START!
USB CORE RESET DONE!
SECURE CHECK FAIL: (RECOVERY)¨

koritsu said:
i didn´t can install a new twrp and i m sooooo streesed D´x somebody knows how can do it? odin give me PASS and green, but when i try to open the twrp new open the same old twrp. when the odin finish, in the tab on mode download say.
¨ ODIN MODE
SECURE DOWNLOAD: ENABLE
MDM DOWNLOAD BLOCK: 0
PRODUCT NAME: SM-T280
CURRENT BIN: CUSTOM
SYSTEM STATUS: CUSTOM
FAP LOCK: OFF
USB INIT START!
USB CORE RESET DONE!
SECURE CHECK FAIL: (RECOVERY)¨
Click to expand...
Click to collapse
Sorry to revive a dead thread, but you just have to hard reset so get out of download mode. I had the same problem. Just hold volume down and power button.