Related
Hey ppl.
I have a big problem, hope you can help me solve it.
I installed jboogies blurless ginger Froyo build 4 a while ago and everything worked fine. Now the gps module and the loudspeaker is broken and id like to send it in. I guess my guarantee is kinda gone when i sent it in with the modified ROM.
Is there any way to get the old bootloader and the normal Blurish Android?
Please help me.
Thanks in advance!
First, you need:
Original SBF of your country, seek for it here: http://forum.xda-developers.com/showthread.php?t=966537
RSD Lite + Moto Drivers: http://forum.xda-developers.com/showthread.php?t=1100585
Then, once you've got everything, power off you phone. You must enter into recovery mode: press volume down and keep pressing it, press power button. Wait for android robot to appear, then press both volume keys and select "Wipe data/factory reset".
Reboot your phone, this time by holding volume up button. Connect phone via usb to pc ( wait for pc to recognize device ), open rsd lite and flash your downloaded sbf.
i am still running the original factory settings + android update, is there a way to save the original factory settings before i try a new rom? sorry i am in a hurry so did not have much time to search the forum first, and as its along the same lines as the first poster i figured it would be a good place to ask a similar question and expand the thread rather then creating a new one
install cwm and make a nandroid backup of your system then search for a fixed sbf of your current software..as long as you have both of them you should be good to go.
Ty for the help one more what do i look at on my phone so i know im getting the right sbf?
at a guess you need t-mob 2.2 us rom
thanks much appreciated.
I might ruined my defy+
When I bought it, it was in German, i changed it to dutch and had android 2.3.6
Flashed it with the all-in-one Defy beginners guide
Had a working android version afterwards, only calling/sms/2g and 3g didn't work. Didn't try to fix it because i wanted to flash the latest cm7.2.
Don't know what i did after that (afterwards we went to carnaval, so i drank to much). I know I installed a uk rom 2.3.6 version and here it went wrong. It went into a bootloop. Got the M logo and spinning white thing around. Tried installing differnt roms, none worked. And now my phone doesnt do anything, wont start or go in to bootloader. RDS light find it but white led wont go on.
IMEI/ESN/MEID: N / A
Technology: N / A
Software Version: N / A
Flex Version: N / A
Bootloader Version: v0x000910
DRM Version: N / A
AP Die ID: 1040020f1fab3a0a0000d8ff0100
BP Die ID: 0000000000000000000000000000
AP Public ID: 9aff8fe986ef65565a0a1e805942bbeaa8460f87
BP Public ID: 0000000000000000000000000000000000000000
Tried different roms, didn't work. Tried the following
"Common Problems/Questions
Black Screens when booting up: (!) Tried to install a version of Android with a lower CG Version than the one currently on the phone.
Weird behavior after installing a Fixed SBF: Install a matching Nandroid backup with your SBF, and remember to clear Cache/Dalvik Cache using Recovery.
Installed full Gingerbread SBF and can’t go back to another rom: (!) aha! We have a issue here!, latest Stock Gingerbread full SBFs comes with a Version 5 of the CG, meaning until not long ago you were pretty much screwed. But wait, there is hope! A one kind Éclair has been found in China Defys that comes with Version 5 CG!.
How to fix it:
Download this SBF and Flash it
Root your Phone
Download 2nd Init 1.4.2 and Install ClockworkMod Recovery
Download and install this Nandroid Backupwent wrong here, multiupload is gone so couldnt continue
Enter Recovery, Wipe Data/Cache
After wiping, turn off your phone
Turn it on and get immediately into Bootloader mode
Flash this Fixed SBF
Delete Data/Cache again and reboot"
Anyone got a answer for this? I am searching this forum for over 6 hours in the last days.
Mate, when you say it doesn't start... Nothing happens when you hold the power button? Not even the M logo (bootscreen) shows up?
Can you access stock recovery? When your phone is off, press and hold Volume UP button and power button. Does anything happen?
When you enter the bootloader, what does it say? Please write everything down.
I'm 99% sure that your phone isn't dead, you've just flashed some wrong stuff. First of all, CM7.2 is not compatible with 2.3.6. There is a CM7.2 DEFY+ version, but it works with 2.3.4 only. If you used a normal defy CM7.2, it's for Froyo only. Anyway, whatever version you used, it's not strange that it wasn't successful.
P.S I've done the same thing first time I've tried to update to some custom ROM
One more thing. After CM7.2 flashing resulted in a frozen bootscreen (M logo), please write down all the steps you did? It's kinda hard to figure out from that guide you've posted..!
niksy+ said:
Mate, when you say it doesn't start... Nothing happens when you hold the power button? Not even the M logo (bootscreen) shows up? Yes nothing shows, looks like the batt is empty but that isn't the case
Can you access stock recovery? When your phone is off, press and hold Volume UP button and power button. Does anything happen?
No nothing
When you enter the bootloader, what does it say? Please write everything down.
I'm 99% sure that your phone isn't dead, you've just flashed some wrong stuff. First of all, CM7.2 is not compatible with 2.3.6. There is a CM7.2 DEFY+ version, but it works with 2.3.4 only. If you used a normal defy CM7.2, it's for Froyo only. Anyway, whatever version you used, it's not strange that it wasn't successful.
P.S I've done the same thing first time I've tried to update to some custom ROM
One more thing. After CM7.2 flashing resulted in a frozen bootscreen (M logo), please write down all the steps you did? It's kinda hard to figure out from that guide you've posted..!Didn't came to that
Click to expand...
Click to collapse
Do you have a good link witch describes how to go from 2.3.6 to 2.3.4? For when my phone works again.
thank you.
taarmen said:
Do you have a good link witch describes how to go from 2.3.6 to 2.3.4? For when my phone works again.
thank you.
Click to expand...
Click to collapse
Not really, buddy :-/
You should have answered my questions, that way I could have written you a step-by-step guide
What you should do:
0. Phone's off
1. Enter stock recovery
2. Wipe data and wipe cache
3. Turn off phone
4. Enter bootloader
5. Flash full stock 2.3.4 sbf - http://www.mirrorcreator.com/files/1HLS00W4/
6. Your phone should boot up normally after the process is done
If you can not enter stock recovery, then just enter bootloader and flash the sbf. The thing is, those fixed sbf's don't have all the codegroups, so some stuff from CM7.2 has probably remained in your system. Full sbf should do a much better job. But, it would be great if you can enter stock recovery. That way the flashing must be successful.
Note, I haven't tried that 2.3.4 sbf! But it's the only one I could find. I need it too and I will test it tomorrow morning, so if you want, you can wait for me to test it first. (I need it cause my defy+ is on Froyo now, and Froyo and defy+ don't really like each other ) I have tested one 2.3.5 sbf, I can point it to it if you wish so. (It doesn't matter which android version it is, as they all have version 6 signed codegroups, so you can switch between them without worrying! Only some latest 2.3.6 ROM's are signed as version 7, but it's highly unlikely that you have flashed your phone with one such)
I Agree with niksy+, can't help, I have a Green Lens Defy, so all i have to say is good luck, and a step-by-step would have been nice
Thank you for the effort, my defy+ is braindead. When i connect it to my pc the white top led goes on. And that is it, nothing on RSD, wont boot, wont go in the bootloader
There's a trick for that i think i remeber it's:
Plug phone it with rsd ready (the phone should be dead with white led)
Pull battery out and press vol up + down
Put battery back in
It might not be exactly that but i can assure you i read somewhere what to do with your issue
Sent from my 1Ghz CM7 + CM9 Defy
crakeron said:
There's a trick for that i think i remeber it's:
Plug phone it with rsd ready (the phone should be dead with white led)
Pull battery out and press vol up + down
Put battery back in
It might not be exactly that but i can assure you i read somewhere what to do with your issue
Click to expand...
Click to collapse
That process is called "force bootloader method" and it can be done on any and every Motorola, as far as I know..! (I've done it on my previous E398, ROKR E1 and ROKR E8 phones (yeah, I've killed all my phones dozens of times )) and, yes, sometimes it does get you into the bootloader when the normal way doesn't!
So, as crakeron said:
1. Battery out
2. Wait couple of seconds (to make sure the phone goes completely out of power > completely off)
3. Start up RSDlite (v5.3.1 minimum!)
4. Connect your phone to the usb (yes, without the battery)
5. Now, you need to press and hold a combination of buttons and insert the battery WHILE holding the buttons pressed and keep them pressed for couple of seconds.
*I'm not sure what the combination of keys is it, but I would try:
a) Volume UP and Volume Down
b) Volume UP and Power Button
c) Volume Down and Power Button
d) Volume UP and Volume Down and Power Button (this one is the least likely, I think)
6. Your phone should show up in RSDlite and you can flash it then. The bootloader maybe won't show up on the phone screen, but if it shows up in RSDlite - it's all that you need!
This forcebootloader thing isn't quite easy and it may take couple of tries to hit the exact needed timing, so try all combinations a couple of times. Let us know if you pull this off!
i have the popcorn out for this one - fun thread! will the defy be rescued??? tune in next time, same bat board, same bat sub board!
taarmen said:
I know I installed a uk rom 2.3.6 version and here it went wrong. It went into a bootloop. Got the M logo and spinning white thing around. Tried installing differnt roms, none worked. And now my phone doesnt do anything, wont start or go in to bootloader. RDS light find it but white led wont go on.
Click to expand...
Click to collapse
If the UK 2.3.6 ROM you installed was this one then you will not be able to downgrade to any other 2.3.6 ROM (except I think this one), let alone 2.3.5, 2.3.4 or Froyo (it does say that in the thread you linked).
You should still be able to flash either of those 2.3.6 ROMs with RSD Lite. But no other ROM - until some more with CG 7 or above become available - and it's currently not rootable either. So no chance of CM7 or other such like goodies. At least you should be able to get a working phone that you can sell on eBay if you desperately don't want to be stuck with the T-Mobile 2.3.6 ROM.
Morals of the story:
1) Read before you flash
2) Keep a written record of what you did (I know, boring)
Good luck, let us know how you get on.
niksy+ said:
That process is called "force bootloader method" and it can be done on any and every Motorola, as far as I know..! (I've done it on my previous E398, ROKR E1 and ROKR E8 phones (yeah, I've killed all my phones dozens of times )) and, yes, sometimes it does get you into the bootloader when the normal way doesn't!
So, as crakeron said:
1. Battery out
2. Wait couple of seconds (to make sure the phone goes completely out of power > completely off)
3. Start up RSDlite (v5.3.1 minimum!)
4. Connect your phone to the usb (yes, without the battery)
5. Now, you need to press and hold a combination of buttons and insert the battery WHILE holding the buttons pressed and keep them pressed for couple of seconds.
*I'm not sure what the combination of keys is it, but I would try:
a) Volume UP and Volume Down
b) Volume UP and Power Button
c) Volume Down and Power Button
d) Volume UP and Volume Down and Power Button (this one is the least likely, I think)
6. Your phone should show up in RSDlite and you can flash it then. The bootloader maybe won't show up on the phone screen, but if it shows up in RSDlite - it's all that you need!
This forcebootloader thing isn't quite easy and it may take couple of tries to hit the exact needed timing, so try all combinations a couple of times. Let us know if you pull this off!
Click to expand...
Click to collapse
Wel I hope that iolinux333 has enough popcorn because non of the mentioned forced bootloader steps works
When i put my + on the usb nothing happens for a few minutes after that a withe led will shine. Thats all.
Thank you all!
I asked you already on tweakers.net, but I'll ask the same questions here:
What's the status of your battery? (Full, empty, half-full?) What version of RSD-lite did you use? What version of drivers are installed on your computer? How many times did you try the different key combinations after pulling out battery, connecting to your computer? What did you see at each step?
Fotogravin said:
I asked you already on tweakers.net, but I'll ask the same questions here:
What's the status of your battery? (Full, empty, half-full?) What version of RSD-lite did you use? What version of drivers are installed on your computer? How many times did you try the different key combinations after pulling out battery, connecting to your computer? What did you see at each step?
Click to expand...
Click to collapse
Been away for a few days. Back and ready to repair, I appreciate all your help.
no sim and sd-card
win7 64-bit
Battery is Full
RSD Lite version 5.6
motorola 5.4.0 usb drivers 64-bit
Tried all combinations at least 10 times. First I disconnect usb -> take out bat -> make combination and count to ten -> put in bat -> holds for minimum of 10seconds -> click on "show device" on RSD -> Nothing show
Nothing ever shows.
You really should give us more... What happens when you try to power it on? I think you only get black so, does power+vol(+) give you something or do you get a white led when you plug it in the pc?
If yes, it should be recognizable. I don't think you can get into bootloader mode when power-on gives nothing. Maybe by putting the battery back while holding the volume(+) I think and the power button. (like stated earlier) But I thought the white led was enough.
If you don't get the white LED and you only get black screen, maybe try to borrow a battery from someone...
If you get the white LED but RSD doesn't find it: try a few ports, maybe other PC, ....
I also think a Win7 window should pop up first with something like: 'Motorola diag... device found' (or maybe something completely different)
Then I think the easiest = warranty. I'm from Belgium. Had to send it to a repair center in the Netherlands (for a totally different reason) and it took them a while to fix it (it needed to be send elsewhere, .. ).
Just tell them you tried to update your rom and it wend wrong. Anyway, it takes about a month I think...
labsin said:
You really should give us more... What happens when you try to power it on?
Compleet black nothing happens
I think you only get black so, does power+vol(+) give you something
Still nothing
or do you get a white led when you plug it in the pc?
Yes I got that
If yes, it should be recognizable. I don't think you can get into bootloader mode when power-on gives nothing. Maybe by putting the battery back while holding the volume(+) I think and the power button.
Still nothing, not even the white led
(like stated earlier) But I thought the white led was enough.
If you don't get the white LED and you only get black screen, maybe try to borrow a battery from someone...
If you get the white LED but RSD doesn't find it: try a few ports, maybe other PC, ....
Haven't been able to trie different pc's. Tried differt usb ports, even those of my mouse and keyboard so I know they fully function, only white led
I also think a Win7 window should pop up first with something like: 'Motorola diag... device found' (or maybe something completely different)
nothing to show
Then I think the easiest = warranty. I'm from Belgium. Had to send it to a repair center in the Netherlands (for a totally different reason) and it took them a while to fix it (it needed to be send elsewhere, .. ).
Just tell them you tried to update your rom and it wend wrong. Anyway, it takes about a month I think...
Think i got to trie it,what can hapen if they found out i lied?
Click to expand...
Click to collapse
Thank you for helping me, I just tried RSD Lite 5.7 and also nothing.
Sorry a bit late. You didn't lie
I should be recognizable. Especially with a full battery. If not, you might have had a bad install and they might have to replace the botherboard.
If you don't mind waiting a couple of days longer, bring it to the place you bought it. Then the delivery costs are free. But could take 1-2 weeks longer.
IF they do conclude it is your fault then you have to pay an amount of money to deliver it back or you can pay for repairing it (for motherboard could be 80-100 or more, actually don't know). Again when you went trough shop this takes a week or so. (motorola => shop => 3 days nothing => you => 3 days nothing => motorola).
They are not that picky at motorola except for water damage maybe (check for a red sticker below the battery. If it is still white => no prob)
Thank you all. I've sent my phone to the store where i bought it, on friday and the next friday i got it back. With a fresh stock rom.
Hi,
I did enough Google search to find how to check if the bootloader is unlocked or for that matter the bootloader lock status. I have found various threads which point me to different devices like HTC, Xperia, etc. but I have not seen any related with Galaxy S4.
From some articles over the internet I read that Samsung Galaxy S4 (T Mobile) has come with unlocked bootloader.
I am very curious to know if there is any app or a command to check the bootloader lock status. I assume that there would be something (e.g. flag or data element) that identifies the bootloader as locked or unlocked.
So, I would request any help in finding the bootloader lock status for Galaxy S4 (T-Mobile).
Is there a generic method for android devices using adb commands? OR
Is it means of any process? OR
finding the bootloader lock status is device dependent?
Thanks in advance
Bottom line....your bootloader is not locked. Samsung doesnt lock bootloaders.
BUT, the new 4.3.3 firmware (not released for Tmobile yet) may be a different stoty....
Sent from a Insane S4
SICK MADE DEVELOPMENT
Hi allowcowboy,
Thanks for your reply. I understand from different posts that t mobile galaxy s4 comes bootloader unlocked.
My question is, as a developer, how will I be able to find that bootloader lock status - for that matter, for any Android device?
Thanks.
Sent from my SGH-M919 using xda app-developers app
I think you know if the bootloader is lock in Download mode. Also Samsung have unlock bootloaders but carriers like ATT and Verizon locks them.. The 4.3 update will have unlock bootloader as well but it will have knox in it and will reset your counter.
gypsy214 said:
I think you know if the bootloader is lock in Download mode. Also Samsung have unlock bootloaders but carriers like ATT and Verizon locks them.. The 4.3 update will have unlock bootloader as well but it will have knox in it and will reset your counter.
Click to expand...
Click to collapse
@gypsy214
Thanks for shedding some light on the topic.
In Download mode, how would I be able to find it out?
Thanks.
bootloader
---------- Post added at 06:32 PM ---------- Previous post was at 06:22 PM ----------
bootloader 2 newuser
I'm not so sure why it's so hard to find information on this. After reading here, here, and here, I thought there might be a way to check it using the "fastboot" command. But then I read this, and finally this (the last one might be the only one worth linking for our SG4 case), there might be no way to check it using the "fastboot" command.
Then I searched through the [*#0011# > hard button back > key input Q > key input 0000 > select 7 ] menu, didn't find anything.
Installed an app named DevCheck System Info, under the System tab I see that my bootloader is listed as 'I337MVLUGOH1', googled 'I337MVLUGOH1 bootloader' thinking I might some information on it. Nope, but I found this list of many bootloader links.
This command also gets the same result: adb bugreport | find "bootloader"
Might just try to do what I wanted to anyway and see how it goes. I've already taken a good backup of my files.
RaniKheir said:
I'm not so sure why it's so hard to find information on this. After reading here, here, and here, I thought there might be a way to check it using the "fastboot" command. But then I read this, and finally this (the last one might be the only one worth linking for our SG4 case), there might be no way to check it using the "fastboot" command.
Then I searched through the [*#0011# > hard button back > key input Q > key input 0000 > select 7 ] menu, didn't find anything.
Installed an app named DevCheck System Info, under the System tab I see that my bootloader is listed as 'I337MVLUGOH1', googled 'I337MVLUGOH1 bootloader' thinking I might some information on it. Nope, but I found this list of many bootloader links.
This command also gets the same result: adb bugreport | find "bootloader"
Might just try to do what I wanted to anyway and see how it goes. I've already taken a good backup of my files.
Click to expand...
Click to collapse
RaniKheir,
You can always give it a try!
Just wanted to let you know, though, your phone is an I337, which is an AT&T phone, this is the T-Mobile forum.
Samsung, until the S7, did not lock bootloaders by themselves, but would lock them for other companies. AT&T always asks for the bootloader to be locked since the S4 was NB1. Since your AT&T phone is an OH1, it is a safe bet that it is locked.
-AlaskaLinuxUser https://thealaskalinuxuser.wordpress.com
AlaskaLinuxUser said:
Just wanted to let you know, though, your phone is an I337, which is an AT&T phone, this is the T-Mobile forum.
Click to expand...
Click to collapse
Woops, I found this thread through Google, sorry about that.
Would the process to check for locked/unlocked bootloaders be different if the carrier varies?
AlaskaLinuxUser said:
Since your AT&T phone is an OH1, it is a safe bet that it is locked.
Click to expand...
Click to collapse
It's actually a Koodo from Canada so its bootloader was unlocked.
I managed to install TWRP fine, then made a backup, and attempted to install Xposed. Got stuck on the load screen, read more and turns out I'll need to use a deodexed ROM for that, oh the joy of playing the experimentingxpatience game
I leaned something new! Glad to hear that!
RaniKheir said:
Woops, I found this thread through Google, sorry about that.
Would the process to check for locked/unlocked bootloaders be different if the carrier varies?
It's actually a Koodo from Canada so its bootloader was unlocked.
I managed to install TWRP fine, then made a backup, and attempted to install Xposed. Got stuck on the load screen, read more and turns out I'll need to use a deodexed ROM for that, oh the joy of playing the experimentingxpatience game
Click to expand...
Click to collapse
RaniKheir,
Since your bootloader is unlocked, you should try this rom:
http://forum.xda-developers.com/galaxy-s4-tmobile/development/rom-aokp-mm-t3391994
The people on this thread are using Xposed on this rom (which is made to flash on all S4's that use GSM - like yours). I know Xposed will work with this rom, since others are using it, and if you have trouble, you can ask them what to do.
In either event, I learned something new about Canadian phones - I guess maple does really make everything better!
I want to find the same answer....I preordered the Tmobile Note 7 and since the S7 was locked on TMobile its anyones guess about the Note 7 now... when I get it I want to be able to check it because if it is locked I want to return it. I did read that T-Mobile went to bat against Samsung and requested some S7 come unlock but that still doesn't mean that the Note series is the clear....
Sent from my SM-N920T using XDA-Developers mobile app
DionWhite33 said:
I want to find the same answer....I preordered the Tmobile Note 7 and since the S7 was locked on TMobile its anyones guess about the Note 7 now... when I get it I want to be able to check it because if it is locked I want to return it. I did read that T-Mobile went to bat against Samsung and requested some S7 come unlock but that still doesn't mean that the Note series is the clear....
Sent from my SM-N920T using XDA-Developers mobile app
Click to expand...
Click to collapse
This is the S4 T-Mobile thread. Please use the Note 7 thread:
http://forum.xda-developers.com/showthread.php?t=3442527
-AlaskaLinuxUser https://thealaskalinuxuser.wordpress.com
I apologize...I was in that thread..on my phone you can only see the 1st 3 words of the thread your in...wrong room..wrong message...Im gone..
Sent from my SM-N920T using Tapatalk
Samsung S4 I9505XXUHOJ2 bootloader unlock ?
Hi All
I just rooted my Samsung S4 I9505XXUHOJ2 on 5.0.1 - im tentative about the next step as ive made a mess of a few phones over the years
So now i need to install TWRP - but i am seeing in various posts my bootloader needs to be unlocked before i go any further
Ho do I unlock the bootloader on a rooted S4 I9505XXUHOJ2 please ?
Thanks
Don
dumbledon said:
Hi All
I just rooted my Samsung S4 I9505XXUHOJ2 on 5.0.1 - im tentative about the next step as ive made a mess of a few phones over the years
So now i need to install TWRP - but i am seeing in various posts my bootloader needs to be unlocked before i go any further
Ho do I unlock the bootloader on a rooted S4 I9505XXUHOJ2 please ?
Thanks
Don
Click to expand...
Click to collapse
Hi dumbledon,
Your phone is an i9505, which is the international version. If I am not mistaken, your version is already unlocked.
Follow these instructions and you should have no problems at all. If you do have any issue, just let us know and we can walk you through it:
Here is my recommendation:
If you use Windows instructions
Code:
Go to: https://dl.twrp.me/jfltexx/
and download 3.0.2-0 tar
Then, download this:
http://www.mediafire.com/download/7us5q44aab1xl9d/Odin304.zip
-Unzip Odin.
-Turn on your phone (normal turn on) boot up into the stock system.
-plug in your phone, let Windows find the drivers.
-Once Windows found your drivers, unplug the phone, turn your phone off.
-open Odin.exe
-Click on PDA, and choose the TWRP file you downloaded.
-With your phone unplugged and off, Now press and hold the DOWN volume button and the power button.
-When the phone vibrates, you can release the power button, but keep holding the down button.
-You will see a warning screen. Release the down button, and press the volume up button to enter "download" mode.
-Plug your phone into the computer.
-Press start/ok button on Odin.
You should see a blue bar on your phone screen that fills up from left to right. Odin should say "pass" or "success". Your phone should automatically reboot itself. If this did not happen, seek help. Seriously. :D
-Plug your phone into the computer again, and copy the Gapps and Rom from post #1 to your external sdcard of your phone.
-Now, turn off the phone again.
-Hold the UP volume button, and the power button.
-When the phone vibrates, you can release the power button, but keep holding the UP volume button.
-You will enter TWRP. Now you can release the UP volume button.
-You should now MAKE A BACKUP TO YOUR EXTERNAL SDCARD. -With this, you can always go back!
-After making a backup, you should wipe your phone. Select wipe, slide the slider to wipe your phone. This will not wipe your external sdcard.
-Install Rom.
-Wipe Cache and Davlik.
-Install Gapps. - Optional
-Reboot to system and enjoy!
If you use Linux instructions
Code:
Go to: https://dl.twrp.me/jfltexx/
and download 3.0.2-0 img
Then,
$ sudo apt-get heimdall heimdall-frontend -y
$ sudo heimdall-frontend
-This will open up heimdall.
-Click on the tab called Utilities
-With your phone unplugged and off, press and hold the DOWN volume button and the power button.
-When the phone vibrates, you can release the power button, but keep holding the down button.
-You will see a warning screen. Release the down button, and press the volume up button to enter "download" mode.
-Plug your phone into the computer.
-Under Detect Device, click "detect" - the Output box will say something like, detected.
-Under Download PIT -> destination file -> click save as.
-Choose a name for your pit, like jfltexx.pit
-Click Download.
-Exit heimdall-frontend and power off your phone by holding the power button.
-Open heimdall again with the command: $ sudo heimdall-frontend
-Click the tab called "Flash"
-Under "pit" click browse.
-Choose the pit file you downloaded.
-Under partitions(files), click "add"
-Under Partition Details, click partition name, and click recovery.
-Under File (recovery.img), click browse.
-Choose the 3.0.2-0 img you downloaded.
-Click on the "Utilities" tab.
-With your phone unplugged and off, Now press and hold the DOWN volume button and the power button.
-When the phone vibrates, you can release the power button, but keep holding the down button.
-You will see a warning screen. Release the down button, and press the volume up button to enter "download" mode.
-Plug your phone into the computer.
-Under Detect Device, click "detect" - the Output box will say something like, detected.
-Click on the Flash tab.
-Under Session, click "start"
You should see a blue bar on your phone screen that fills up from left to right. Heimdall should say "pass" or "success". Your phone should automatically reboot itself. If this did not happen, seek help. Seriously. :D
-Plug your phone into the computer again, and copy the Gapps and Rom from post #1 to your external sdcard of your phone.
-Now, turn off the phone again.
-Hold the UP volume button, and the power button.
-When the phone vibrates, you can release the power button, but keep holding the UP volume button.
-You will enter TWRP. Now you can release the UP volume button.
-You should now MAKE A BACKUP TO YOUR EXTERNAL SDCARD. -With this, you can always go back!
-After making a backup, you should wipe your phone. Select wipe, slide the slider to wipe your phone. This will not wipe your external sdcard.
-Install Rom.
-Wipe Cache and Davlik.
-Install Gapps. - Optional
-Reboot to system and enjoy!
Let us know if you need more help!
Click to expand...
Click to collapse
Thank You AlaskaLinuxUser :good:
OK folks - I have TWRP installed and root checker says im rooted - i'm a bit unsure of which direction to take for a custom ROM - im reading that the custom rom version must match stock version (for me 5.0.1) - is this the case ?
Im not really bothered about launchers and that - but i'd like bloatware removed , fairly fast , and good battery - i was thinking something CWM based but has the scene changed ?
open to recommendations
havent done anything like this for a couple of years - cheers
dumbledon said:
OK folks - I have TWRP installed and root checker says im rooted - i'm a bit unsure of which direction to take for a custom ROM - im reading that the custom rom version must match stock version (for me 5.0.1) - is this the case ?
Im not really bothered about launchers and that - but i'd like bloatware removed , fairly fast , and good battery - i was thinking something CWM based but has the scene changed ?
open to recommendations
havent done anything like this for a couple of years - cheers
Click to expand...
Click to collapse
I recommend these:
AOKP MM 6.0.1
http://forum.xda-developers.com/showthread.php?t=3391994
SlimLP 5.1.1
http://forum.xda-developers.com/showthread.php?t=3377731
They were built for jfltetmo, but have been proven to work very well on your phone.
Good luck and be sure to follow the flashing instructions!
-AlaskaLinuxUser https://thealaskalinuxuser.wordpress.com
Thanks AlaskaLinuxuser
I went for the AOKP - its great stable smooth fast light and debloated - no issues did i come across apart from a little favor
i think it would be nice if people could make the battery "percentage remaining" text a color of their choice
like 55 % or 55 % or 55 % etc etc
Overall great job :good:
Hi all
this rom AOKP MM 6.0.1 has been great for the past week or so - i have one quite substantial problem i have just encountered
An app which i use a lot called Vomino (available Play store) - is coming back with this error message after I install it
"Cannot load native library CPU arch is invalid for this build"
I've tried removing and reinstalling vomino a few times and always at the final part of installing - where it says enjoy our service it displays that error message - the interface remains in place and you can choose contacts but there is no response when dialing a phone number (or clicking a contact)
can someone please try it on their own devices ?
I really need to get this working - thanks
Hi all first i want to tell you that i dont have much exp with android flashing and ect. but everything was going good following the instr. and everything was fine whit my HOX and HOX+ now i have m8 and i unlock it with htc devs reboot and everything was just fine then i fastboot reboot it and clicked on recovery (just to make 1 stock) and surprise the phone got stuck on a red exclamation mark
1 holding power button - nothing
2 power button +vol down-nothing
3 power button +vol up-nothing
4 power +up+down(just in case ) nothing
5 connecting whit USB the PC i get the sound that its connected but in fastboot and adb i get no devices i got pissed off so i went for coffe and cigar when i get back the phone was ok and running alive (o and i removed the SD card and SIM before going for coffe and cigar ) so what do you think happen ??
PS - I know my english sucks from time to time just deal whit it sorry
That is the stock recovery you are seeing. You can't make a backup with it either. You need to flash a custom recovery, then take a backup with it before doing anything else. And to return to stock, you restore your backup, then flash your stock recovery version.
See this thread for help on most things...
http://forum.xda-developers.com/showthread.php?t=2711073
s7L said:
Hi all first i want to tell you that i dont have much exp with android flashing and ect. but everything was going good following the instr. and everything was fine whit my HOX and HOX+ now i have m8 and i unlock it with htc devs reboot and everything was just fine then i fastboot reboot it and clicked on recovery (just to make 1 stock) and surprise the phone got stuck on a red exclamation mark
1 holding power button - nothing
2 power button +vol down-nothing
3 power button +vol up-nothing
4 power +up+down(just in case ) nothing
5 connecting whit USB the PC i get the sound that its connected but in fastboot and adb i get no devices i got pissed off so i went for coffe and cigar when i get back the phone was ok and running alive (o and i removed the SD card and SIM before going for coffe and cigar ) so what do you think happen ??
PS - I know my english sucks from time to time just deal whit it sorry
Click to expand...
Click to collapse
Hold Volume up and TAP(NOT HOLD BUT TAP) the power button, that will take you to the option menu for the stock recovery. The rest you can follow in the post made by Darth.
Oh... Here's a guide to walk you through everything you want and more....
http://forum.xda-developers.com/showthread.php?t=2800727
thank you but firewater doesnt work on my m8
s7L said:
thank you but firewater doesnt work on my m8
Click to expand...
Click to collapse
What does Firewater have to do with anything? What exactly are you trying to do? Just make a backup of stock ROM/Data before flashing custom ROMs? Then you don't even need S-OFF, if you didn't know this then perhaps going S-OFF wouldn't be a good idea anyway, might just be a brick in the making then.
First things first, what CID are you at? Go to the Collection thread in general section and see if you have a backup of stock recovery there. If you do then you can just flash custom recovery and flash custom ROMs. IF you don't then you need to make a backup of your recovery and you'll have to boot the custom recovery(Philz) to make a backup of stock recovery.
Htc_032 i needed firewater cuz i need super cid cuz im branded and soon im leaving my country so i have to use diff sim
It's in the guide I linked last. You need Sunshine to s-off it looks like.
BerndM14 said:
Hold Volume up and TAP(NOT HOLD BUT TAP) the power button, that will take you to the option menu for the stock recovery. The rest you can follow in the post made by Darth.
Click to expand...
Click to collapse
Good to know. Even though my stock recoveries only last two or three days..
Sunshine you say sunshine i shall try then thank you people for the fast responds
Sent from my HTC One_M8 using XDA Free mobile app
Rooting A10s with Magisk [Very Early Root]
Hello community. I wanted to post my progress on trying to root this device and maybe was hoping for some pointers.
Unfortunately the steps are somewhat complicated, especially since we don't have a custom recovery.
Would appreciate some of the more experienced developers if you could give me a hand, since my knowledge is very very limited (don't know how to compile my own custom recovery, have 0 knowledge on even using git hub lmao)
Thanks for reading, here's what I got so far
Things to know about the A10s
It is a System As Root device
It is an AB device (after Android 10 update)
It has no custom recovery as of yet
The process may also work for the F variant
The process I used to root with Magisk is here: https://topjohnwu.github.io/Magisk/install.html
Special thanks to @topjohnwu for his very detailed guide
Ok and now well, to explain where I'm currently stuck. The final step to finish installation off is to reboot to stock recovery and wipe data. I'm guessing that this will fix the signal problem I have, but can't know for sure until I try. The problem with that is that topjohnwu states as follows:
We now want to boot into the stock recovery to factory reset our device.
Full data wipe is mandatory! Do not skip this step.
Press Power + Volume Down to exit download mode. As soon as the screen turns off, immediately press the combo key to boot to recovery (e.g. on the S10 it is Power + Bixby + Volume Up). Since we want to boot into stock recovery, continue pressing the volume up button until you see the stock recovery screen.
Use volume buttons to navigate through the stock recovery menu, and the power button to select an option. Choose Wipe data/factory reset to wipe the data of the device.
Click to expand...
Click to collapse
The problem here is that no matter how hard I try, I can't boot to stock recovery
I can boot the device as follows
System+No magisk (signal works here)
System+Magisk (RIL broken)
However I simply can't boot to stock recovery. Apparently I need to leave the VOL + button pressed and keep it pressed but it's simply not doing anything. Even using adb to reboot to recovery and holding the VOL + button since it even shuts down is not doing anything.
I don't know where to go from here, I simply can't boot to stock recovery
Would really like to know suggestions
Thanks for reading!
Currently I am hosting a Telegram group for anybody that wants to follow development as it progresses. But for questions, please keep them here on XDA
Link: https://t.me/a107X
I managed to boot to stock recovery by pressing power vol down and plugging usb in at the same time I think.
Update: Well, I flashed stock recovery with Odin. Managed to boot directly to recovery, wiped data and immediately flashed the magisk patched recovery. However this still did not fix the broken signal problem, as I expected. The search for a fix is still on.
you should follow topjohnwu's instructions for samsung devices..
edit: maybe you are, they are included in the link you posted but youre not specific in the steps youre taking for others to help you.
you could also im sure follow same steps as F variant id think but dont blame me for troubles lol
elliwigy said:
you should follow topjohnwu's instructions for samsung devices..
edit: maybe you are, they are included in the link you posted but youre not specific in the steps youre taking for others to help you.
you could also im sure follow same steps as F variant id think but dont blame me for troubles lol
Click to expand...
Click to collapse
Yeah I'll try that method in due time. But I'm really in no hurry since I've got root anyway and I just use it from time to time, so I just reboot to system+magisk only when I need to and just boot system normally every other time.
ShaDisNX255 said:
Yeah I'll try that method in due time. But I'm really in no hurry since I've got root anyway and I just use it from time to time, so I just reboot to system+magisk only when I need to and just boot system normally every other time.
Click to expand...
Click to collapse
Hey op, did you flash magisk with odin using patched file? if you did, could you share your patched file and the firmware version you used? Odin keeps failing when i try to patch.
MR2_Wei said:
Hey op, did you flash magisk with odin using patched file? if you did, could you share your patched file and the firmware version you used? Odin keeps failing when i try to patch.
Click to expand...
Click to collapse
I think I'll have some time this weekend, I'll try to put a in-depth tutorial with all the files required.
But, can you tell me the error you get on Odin and/or any error messages on your phone?
By the way, the signal problem has been reported on other occasions.
It seems to be a problem on this Mediatek SoC
https://github.com/topjohnwu/Magisk/issues/1801
topjohnwu seems to have just brushed it off so it doesn't seem like it's going to get fixed anytime soon
Sorry for butting in and my ignorance...I need HELP!
ShaDisNX255 said:
Rooting A10s with Magisk [Very Early Root]
Hello community. I wanted to post my progress on trying to root this device and maybe was hoping for some pointers.
Unfortunately the steps are somewhat complicated, especially since we don't have a custom recovery.
Would appreciate some of the more experienced developers if you could give me a hand, since my knowledge is very very limited (don't know how to compile my own custom recovery, have 0 knowledge on even using git hub lmao)
Thanks for reading, here's what I got so far
Things to know about the A10s
It is a System As Root device
It is an A-Only device
It has no custom recovery as of yet
The process may also work for the F variant
The process I used to root with Magisk is here: https://topjohnwu.github.io/Magisk/install.html
Special thanks to @topjohnwu for his very detailed guide
Ok and now well, to explain where I'm currently stuck. The final step to finish installation off is to reboot to stock recovery and wipe data. I'm guessing that this will fix the signal problem I have, but can't know for sure until I try. The problem with that is that topjohnwu states as follows:
The problem here is that no matter how hard I try, I can't boot to stock recovery
I can boot the device as follows
System+No magisk (signal works here)
System+Magisk (RIL broken)
However I simply can't boot to stock recovery. Apparently I need to leave the VOL + button pressed and keep it pressed but it's simply not doing anything. Even using adb to reboot to recovery and holding the VOL + button since it even shuts down is not doing anything.
I don't know where to go from here, I simply can't boot to stock recovery
Would really like to know suggestions
Thanks for reading!
Click to expand...
Click to collapse
I have a Samsung A10S (a107M) had it for a few days - I cannot get the bootloader unlocked. I can get it to the screen where it says long press vol up to unlock bootloader. When I do this it reboots, and starts 'normally' PLEASE if anyone can help I will happily buy you a beer!
SandsCayman said:
I have a Samsung A10S (a107M) had it for a few days - I cannot get the bootloader unlocked. I can get it to the screen where it says long press vol up to unlock bootloader. When I do this it reboots, and starts 'normally' PLEASE if anyone can help I will happily buy you a beer!
Click to expand...
Click to collapse
Just keep trying, and leave the VOL + button pressed even after it reboots. I remember last time I rooted, it took me approximately 4 or 5 attempts to finally get bootloader unlocked. Keep doing it until you can finally see the message that your bootloader is unlocked.
Hii there...
I've been trying to root my SM-107F(Samsung a10s) for months now with no luck,honestly speaking am very close to giving up even I wanted it so bad...And I've tried almost every top recommended methods out there,including using kingoroot,kingroot,irobot,magisk,supersu...But still no luck,the main problem is that I can't reboot successfully into bootloader and when I do so by clicking the vol up and power button simultaneously it just reboot...Plz anyone who has successfully rooted their Samsung a10s plz help me and I know all the side effects and disadvantages of rooting a mobile device including bricking and void warranty and am willing to take the risk...So if there is someone out there who can help,your help will be most appreciated.
Aaron_MK said:
Hii there...
I've been trying to root my SM-107F(Samsung a10s) for months now with no luck,honestly speaking am very close to giving up even I wanted it so bad...And I've tried almost every top recommended methods out there,including using kingoroot,kingroot,irobot,magisk,supersu...But still no luck,the main problem is that I can't reboot successfully into bootloader and when I do so by clicking the vol up and power button simultaneously it just reboot...Plz anyone who has successfully rooted their Samsung a10s plz help me and I know all the side effects and disadvantages of rooting a mobile device including bricking and void warranty and am willing to take the risk...So if there is someone out there who can help,your help will be most appreciated.
Click to expand...
Click to collapse
If you have Telegram, you can join our group and we can give you help in real time. TWRP will most likely be released soon so rooting is going to get a lot easier, if you can wait.
Aaron_MK said:
Hii there...
I've been trying to root my SM-107F(Samsung a10s) for months now with no luck,honestly speaking am very close to giving up even I wanted it so bad...And I've tried almost every top recommended methods out there,including using kingoroot,kingroot,irobot,magisk,supersu...But still no luck,the main problem is that I can't reboot successfully into bootloader and when I do so by clicking the vol up and power button simultaneously it just reboot...Plz anyone who has successfully rooted their Samsung a10s plz help me and I know all the side effects and disadvantages of rooting a mobile device including bricking and void warranty and am willing to take the risk...So if there is someone out there who can help,your help will be most appreciated.
Click to expand...
Click to collapse
i already done rooted my A10s (A107F) but now i want to know if there's someone in here can unroot this devices without flashing the stock rom...
i try flash the original boot.img and it didn't work for me cause it make my phone bootloop..
any suggest maybe...?
ShaDisNX255 said:
If you have Telegram, you can join our group and we can give you help in real time. TWRP will most likely be released soon so rooting is going to get a lot easier, if you can wait.
Click to expand...
Click to collapse
Telegram link please....?
jogijee said:
Telegram link please....?
Click to expand...
Click to collapse
It's on the seccond post
Can you help me I am trying to root a SM-A107M
i need some help here, couldn't find the solution anywhere else, after everything done the way it should be, in the last rooting step when i should get the magisk message: "requires additional setup" so the system reboots into root, i do not get that message at all, it does not appear in the screen, does somebody know what is wrong?