Razr hd downgrade to jb stock firmware - RAZR HD Q&A, Help & Troubleshooting

HELLO GUYS
i really need help with my Razr HD , i want to downgrade from kitkat 4.4.2 to jelly bean since the kikat update caused nothing but trouble to me , i am newbie , so please someone help me to downgrade my phone to 4.1.2 step by step and make it simple as possible .
i have RSD lite 6.1 , tried to flash on fastboot mode , got failed flashing process 5/27 error ,
all drivers are installed
i have stock firmware 4.1.1 , 4.1.2 , 4.4.2 xlm files
must mention that my system version is on 183.46.15XT926
Developers mode activated , USB Debugging checked
:angel:

You cannot downgrade from 183.46.15 unless you unlocked your bootloader before upgrading to 183.46.15.
You cannot now unlock your bootloader if you have 183.46.15.
What trouble are you having with KitKat? You can get root, and I then installed Nova Launcher, Titanium Backup, and Xposed Framework with GravityBox to customize things the way I like them.

Spott07 said:
You cannot downgrade from 183.46.15 unless you unlocked your bootloader before upgrading to 183.46.15.
You cannot now unlock your bootloader if you have 183.46.15.
What trouble are you having with KitKat? You can get root, and I then installed Nova Launcher, Titanium Backup, and Xposed Framework with GravityBox to customize things the way I like them.
Click to expand...
Click to collapse
first thank you for replying to me , My bluetooth is gone , i can't seem to connect or send a file to any device
and now so is my wifi , it says saved but not connected and i know it's not router issue because others can connect to the same router with no problem at all

i have Droid razr hd toolkit 5.0 , couldn't unlock my bootloader with it , also couldn't downgrade to jb
how can i root my device using this toolkit with my bootloader still locked ? any instructions please !

First, I'd try reflashing the stock firmware (183.46.15) and see if that fixes your Bluetooth and WiFi problems. I use RSD Lite and it works well. I know the stock firmware works fine on this phone, that's the same configuration I'm using.
To get root, you can either use the "hydrogen peroxide" method, or kingroot. I'd get your radio problems straightened out first before worrying about root.

Spott07 said:
First, I'd try reflashing the stock firmware (183.46.15) and see if that fixes your Bluetooth and WiFi problems. I use RSD Lite and it works well. I know the stock firmware works fine on this phone, that's the same configuration I'm using.
To get root, you can either use the "hydrogen peroxide" method, or kingroot. I'd get your radio problems straightened out first before worrying about root.
Click to expand...
Click to collapse
i tired flashing the stock firmware , but i get this error on the 5th step
i rooted my device , installed superuser , now i am having issue with cmw recovery image
i can't install it on the device

You have to comment a couple of lines out of the install package to get the firmware to flash. There's details in the hydrogen peroxide instructional thread, down where it takes about upgrading from 182.46.15 to 183.46.15.
You can't really install an effective custom recovery (like CWM) with a locked bootloader.
What on earth are you trying to accomplish? If you're trying to fix your WiFi and Bluetooth problems, then both getting root and installing a crippled recovery isn't going to get you there very well. Focus on reflashing the stock firmware first, then come back to root (and don't even waste your time with that broken CWM and the deodexed ROM, they don't gain you anything, and cause more problems than they solve. I soft-bricked my phone three times trying to get anything out of them. The only way to recover from that was to....wait for it....reflash the stock firmware. Notice a pattern here?)

Spott07 said:
You have to comment a couple of lines out of the install package to get the firmware to flash. There's details in the hydrogen peroxide instructional thread, down where it takes about upgrading from 182.46.15 to 183.46.15.
You can't really install an effective custom recovery (like CWM) with a locked bootloader.
What on earth are you trying to accomplish? If you're trying to fix your WiFi and Bluetooth problems, then both getting root and installing a crippled recovery isn't going to get you there very well. Focus on reflashing the stock firmware first, then come back to root (and don't even waste your time with that broken CWM and the deodexed ROM, they don't gain you anything, and cause more problems than they solve. I soft-bricked my phone three times trying to get anything out of them. The only way to recover from that was to....wait for it....reflash the stock firmware. Notice a pattern here?)
Click to expand...
Click to collapse
i am trying to install cm 12 custom rom , since flashing the stock failed many times
i used motoeclipse to unlock the bootloader after rooting , don't know if it works or not
now i am giving a shot at custom roms

You cannot unlock the bootloader of 183.46.15. You cannot install custom ROMs, or even older stock ROMs, with a locked bootloader.
You did not unlock the bootloader, and you're lucky you didn't brick your phone trying.
Sorry, but with that phone and that firmware, there's just no way that anyone's discovered to unlock it (and it's been that way so long that very few are even trying any more).
That rudimentary CWM that's available is not designed for your phone, is only barely compatible, will not allow you to flash custom ROMs, and that fact is stated boldly and repeatedly in the post where you found it. You're stuck with a very specific Motorola 4.4.2 kernel in the bootloader and you can't change it, and if you install a ROM that's not perfectly compatible with it (that is, anything other than the 183.46.15 firmware) you'll end up with a phone that won't boot.
You might be "giving it a shot" but your magazine's full of blank ammo.
You must slow down and read carefully before you brick your phone, because you've already missed a lot of important information that you'll need to keep you out of trouble.
Also, if you can't figure out how to flash a stock ROM, you're not qualified to pursue custom ROMs even if you could. What do you think happens if a flash fails and you're stuck with a soft-brick? The only way out of that is to flash a stock ROM and start over.
You have two options at this point: Either accept your phone the way it is without Bluetooth and WiFi, or do the research necessary to learn how to reflash the stock ROM and fix your problem. Here's a hint: I know exactly why your flash attempts failed, and it's quite easy to fix it, and I've already told you where to find the information to do so, in a previous post.
Now you're on your own, as I probably cannot help you any more.

how can i get pass the 5th step is rsd ?
i wanna go back to the same stock firmware4.4.2 or downgrade to 4.1.2 but i cant

sorry sir for bothering you , i am just doing researches haven't done anything passed the root
my phone status now : rooted with superuser , stock recovery still in
bootloader still locked
i have heard of this tool DROID_RAZR_HD_Utility_1.41_KK here: http://forum.xda-developers.com/showthread.php?t=2474393
i don't know what to do ?

You must slow down and read carefully. Especially the first paragraph of post #7.
It's not useful to do research if you don't read the results.

Spott07 said:
You must slow down and read carefully. Especially the first paragraph of post #7.
It's not useful to do research if you don't read the results.
Click to expand...
Click to collapse
thanks , just to let you know , i have found the same stock firmware and flashed successfully , still with wifi and bluetooth issues
i have been told that downgrading to jelly bean will sort all my issues
waiting for advice , don't know what to do next

I don't know who told you that downgrading to JB will help you, but they're wrong, because 1) it's impossible for you to downgrade, and 2) the KK firmware works quite well with very few bugs.
Perhaps the wireless chip inside your phone is damaged. Does the GPS work?
Perhaps the wireless service is disabled in the settings. Do you have airplane mode turned on? Do you have WiFi and Bluetooth disabled? Have you tried deleting or "forgetting" your WiFi connection, and then re-entering it again from the beginning?

i tried all of this , airplane mode , wifi advanced settings , everything
what if i downgraded the kernel from 15 to 10 , would i be able to unlock my bootloader and downgrade to jelly bean ?

You cannot downgrade the kernel. It's within the locked bootloader. I told you that in post #9.
You cannot unlock the bootloader on this phone. End of story. Hundreds of the best developers have tried every possibility they could think of, and have given up.
Perhaps some miracle will occur and someone will find a way, but don't count on it. This phone is old and those with the proper skills have moved on to newer, better things. As of right now, and for the foreseeable future, it is impossible.
Also, you never answered whether your GPS works.

flashed back to stock , now my wifi works outta nowhere

Sorry, I got confused about the conversation, I'll explain below.

it's not like that , first i followed your instructions and flashed the stock 183.46.15 , when nothing worked then i flashed the modified 183.46.10 suddenly wifi started to pick up signals , then drops every once and a while
i have no issues with rooting , i can root the device in minutes which i have

Sorry for being so rude earlier, I got confused.
I usually use the Tapatalk app to read these forums, but right now the login server is down, so I had to log in on the website. When I looked on the website, the screwy timestamps appeared to indicate that you had replied a couple hours ago, so I clicked on the link. (The timestamp options are terribly difficult to find, so I hadn't corrected them for my timezone, and then forgot that fact.) Instead of taking me to the last post in the thread, it displayed the first page of 10 posts (I'm used to seeing 50/page with Tapatalk) and I saw your (old) post at the bottom asking how to get the firmware to flash with RSD. At that point I got frustrated and failed to check any farther, and responded as if that were another repetitious request for the same information.
So, between the Tapatalk login server, the awkward behavior of this site, and my frustration and impatience, I responded very badly.
You didn't deserve that response, and I'm sorry.
I don't know why re-flashing the 183.46.15 firmware didn't work, it has few bugs and is pretty stable for everyone who's stuck with it. I don't know anything about any "modified 183.46.10" firmware that could be flashed on our phones, where did you find that? Are you referring to this? If so, it's great that it works, but it's risky and certainly won't permit you to unlock your bootloader.
Scott

Related

[Q] How do I update a rooted, locked, 4.1.2 to 4.4.2 OTA?

Hello. I have a XT925 running 4.1.2. The phone was rooted a long time ago. I don't remember if I installed a recovery, nor which recovery (if any) was installed at the time (volume up + power yields a boot mode selection menu; it seems to be the original bootloader).
My carrier released the 4.4.2 OTA just today. When I try to update, the phone reboots and displays an "Update failed" error message. I uninstalled as many apps as AdAway and XPosed that I think could be tampering with the process, but still I can't install the update.
How can I update to KitKat? (If it isn't obvious by now, I don't follow most of the technicalities of this things with Android. I'm fairly knowledgeable about computers, just not Android. I've read a lot of threads here and still can't figure out how to do this!)
Will I be able to re-root the phone afterwards? Will I be able to unlock it?
Thanks!
unless you have some concerns about warranty, I suggest go ahead and unlock bootlocader via moto website. Then you are free to do as you please, meaning uprade to kk stock, custom rom and root without hassle.
hbenz2008 said:
unless you have some concerns about warranty, I suggest go ahead and unlock bootlocader via moto website. Then you are free to do as you please, meaning uprade to kk stock, custom rom and root without hassle.
Click to expand...
Click to collapse
Ok, I did it (and lost everything on the phone in the process). The phone said it was unlocked. The phone is now back to stock, clean 4.1.2. But I still can't update. I get the same "update failed" error message.
What should I do?
Dont panic! haha you will get it done I have no doubt.
First did you factory reset after all was done. Do that and try again
if not, there are other ways , some easier than others but all within your capabilities
http://forum.xda-developers.com/dro...tutorial-make-motorola-razr-hd-xt925-t2916465
http://forum.xda-developers.com/showthread.php?t=2760840&page=3

[Q] Want to wipe and keep root in 9.16.6 Razr Maxx HD - what are my options?

The goal: Get my sluggish phone (Razr Maxx HD, JB 4.1.2, currently 9.16.6.XT926.Verizon.en.US, rooted, bootloader locked) to be less sluggish.
The proposed method: Wipe phone and start over.
The "problem": Because I am rooted and want to stay that way, I am aware that I can't just do a factory reset. I believe that I need to unroot first, then wipe, then reroot. But there are many more possible methods to do this than there were before and I'm having trouble figuring out which might be the best method for me (or which will even work, at all).
Background: If I had just blindly done what I did the last time I wiped (I think I was starting from ICS 0.7.2 last time, not JB), I would have backed up everything, used DROID_RAZR_HD_Utility1.10 which I have from before (dates appear to be 1/28/2013) to go back to 0.6.25.X926., and, using the zip files I have from before, go from 0.6.25 to 0.7.2 to 9.1.41 to 9.16.6. (I was never able to successfully take OTA updates). Like this: http://forum.xda-developers.com/showthread.php?t=2024423 BUT, now that I'm on JB, it's not clear to me that I can even do this. One post is telling me that if I'm on 9.16.6, I should NOT use Droid Razr HD Utility 1.10. http://forum.xda-developers.com/showthread.php?p=33610625#post33610625 and when I found the thread for the 1.21 utility, it also says no 9.16.6.
I've been wandering around the relevant posts that are linked from here: http://forum.xda-developers.com/showthread.php?t=2247250
but for whatever reason, this is just making my head spin. I'm more confused about what I can and cannot do, than I was before I started. I think too many OTA versions have passed me by... I was happy with the way things were working so I just didn't care about updates, KitKat, etc. I don't have a good feel for how many versions there are between 9.16.6 and current.
My actual question: I think I could really use some help narrowing down my options. Do I have any options at all? If so, can anyone suggest what my realistic options actually are? I don't care if I end up in JB or KitKat at the end; I do want to be able to restore some of the data from some of my apps using Titanium Backup and/or MyBackup Pro; and I want to be rooted when I am done. Any suggestions would be greatly appreciated.
Thank you, dlc
dlc2001 said:
The goal: Get my sluggish phone (Razr Maxx HD, JB 4.1.2, currently 9.16.6.XT926.Verizon.en.US, rooted, bootloader locked) to be less sluggish.
The proposed method: Wipe phone and start over.
The "problem": Because I am rooted and want to stay that way, I am aware that I can't just do a factory reset. I believe that I need to unroot first, then wipe, then reroot. But there are many more possible methods to do this than there were before and I'm having trouble figuring out which might be the best method for me (or which will even work, at all).
Background: If I had just blindly done what I did the last time I wiped (I think I was starting from ICS 0.7.2 last time, not JB), I would have backed up everything, used DROID_RAZR_HD_Utility1.10 which I have from before (dates appear to be 1/28/2013) to go back to 0.6.25.X926., and, using the zip files I have from before, go from 0.6.25 to 0.7.2 to 9.1.41 to 9.16.6. (I was never able to successfully take OTA updates). Like this: http://forum.xda-developers.com/showthread.php?t=2024423 BUT, now that I'm on JB, it's not clear to me that I can even do this. One post is telling me that if I'm on 9.16.6, I should NOT use Droid Razr HD Utility 1.10. http://forum.xda-developers.com/showthread.php?p=33610625#post33610625 and when I found the thread for the 1.21 utility, it also says no 9.16.6.
I've been wandering around the relevant posts that are linked from here: http://forum.xda-developers.com/showthread.php?t=2247250
but for whatever reason, this is just making my head spin. I'm more confused about what I can and cannot do, than I was before I started. I think too many OTA versions have passed me by... I was happy with the way things were working so I just didn't care about updates, KitKat, etc. I don't have a good feel for how many versions there are between 9.16.6 and current.
My actual question: I think I could really use some help narrowing down my options. Do I have any options at all? If so, can anyone suggest what my realistic options actually are? I don't care if I end up in JB or KitKat at the end; I do want to be able to restore some of the data from some of my apps using Titanium Backup and/or MyBackup Pro; and I want to be rooted when I am done. Any suggestions would be greatly appreciated.
Thank you, dlc
Click to expand...
Click to collapse
to get rid of the slowness of the phone i recommend going to a lolipop rom , LP has to be the quickest my phone has ran... ever.
-step 1 use rsd lite to flash [4.4.2] 183.46.10 fxz (make sure it ends with a 10 not a 14 or 15 or you wont be able to unlock bootloader)
http://www.droidrzr.com/index.php/topic/45494-fxz-442-1834610/
-step 2 root and unlock use TR.apk (root)and motopocalypse.apk (bootloader unlock)
http://forum.xda-developers.com/showthread.php?t=2783912
-step 3 use ADB fastboot to Flash custom recovery, i personally use twrp there are others you can use if you decide to do the research
http://www.droidrzr.com/index.php/topic/51883-recoverytwrp-2810-11-01-14/
-step 4 flash LP custom rom, i use blisspop, it seems to have the most updates at the moment . it has really impressed me
http://www.droidrzr.com/index.php/topic/60153-rom502lollipopmsm8960-kkbl-blisspop-official/
that rom comes with supersu built in so you will have root. if your reason for having root is to have exposed, it doesnt work on lolipop so stop at sstep 3 and either flash a KK custom rom or just flash supersu which will give you root on stock kitkat
OK, I will spend a little more time absorbing/reading and then I'll give it a shot, thanks muchly. I want to do some backups just in case, so it'll take a while...
Couple of followup questions based on the reading I've done so far from the links you provided, just so I know what I'm doing before I do it:
1. I think I get Steps 1 and 2. After Step 2 I am rooted and on stock KK, correct? So if I stop there do I still need to "flash supersu" per your comment at the end? Does the root in step 2 put supersu in my apps, and if not can I not just install it from google play?
2. Seems like I can use the Step 1 method to flash back to JB (or any other FXZ I can find) if I want. If I do that, is there any way to root JB, or is this trip I'm about to take, a one-way trip? Just to clarify, JB hasn't always been slow for me... it's just slowed down recently. Not saying I want to go back to JB for sure, but I like to know what options I am closing off when I move forward, and reviews of KitKat are not universally splendid.... I hear you about the custom ROM but for various work-related reasons I may be better off staying stock (well, stock + root) for a while at least.
Again, thank you for your help.
dlc2001 said:
OK, I will spend a little more time absorbing/reading and then I'll give it a shot, thanks muchly. I want to do some backups just in case, so it'll take a while...
Couple of followup questions based on the reading I've done so far from the links you provided, just so I know what I'm doing before I do it:
1. I think I get Steps 1 and 2. After Step 2 I am rooted and on stock KK, correct? So if I stop there do I still need to "flash supersu" per your comment at the end? Does the root in step 2 put supersu in my apps, and if not can I not just install it from google play?
2. Seems like I can use the Step 1 method to flash back to JB (or any other FXZ I can find) if I want. If I do that, is there any way to root JB, or is this trip I'm about to take, a one-way trip? Just to clarify, JB hasn't always been slow for me... it's just slowed down recently. Not saying I want to go back to JB for sure, but I like to know what options I am closing off when I move forward, and reviews of KitKat are not universally splendid.... I hear you about the custom ROM but for various work-related reasons I may be better off staying stock (well, stock + root) for a while at least.
Again, thank you for your help.
Click to expand...
Click to collapse
yes you can install it from playstore, but once your bootloader is unlocked you can always root by flashing in custom recovery. you dont need exploits anymore
All done, worked great!

[Q] MAXX Unlocked 4.2.2, custom recovery. How to get to 4.4.4?

So as the title says, I recently sunshine unlocked my 4.2.2 (12.15.15 firmware) MAXX. At this point, I have a custom recovery from the root method I used on the phone a year ago, but other than that I'm just running the stock 4.2.2 Camera update.
What is the easiest way to get up and running on a current 4.4.4 build? Can I use RSDlite to return to stock 4.2.2, or does that not work with an unlocked bootloader? Could I RSDlite to 4.4.4 directly? What about flashing TWRP to my phone now and using that to flash a 4.4.4 rom? I dont care about losing all of my data or anything like that.
I'm a little confused on what I can and can't flash depending on the current version of andoid I'm on, so any help would be greatly appreciated. Thanks!
now that your bootloader is unlocked you can have root on any fw version you decide to update to. but you have to be on stock everything before you update to 4.4.4. if the recovery is the only thing you have changed you can just extract it from the fxz for 4.2.2 if that's what your on right now. flash it using fastboot or the easy way using rashr an app from play store. my fav for flashing recoveries. then take the update. after that you can flash T.W.R.P 2.8.4.0 for obake. then reboot to recovery. reboot to system to gain root if it is removed by updating
Thanks for the reply. I'll look into flashing that recovery and try the OTA. Would flashing the whole fxz (which i believe includes a bootlader) hurt me? Also, is there any way one of the OTA's changes the bootloader in a way that could mess up my unlock?
no. once your bootloader is unlocked then it won't relock unless you lock it by command prompt. yes you could use rsd to go back to stock. it has to be the exact version you are currently on. if you try to rsd a version your not on it will fail.
Will it fail in a "your phone is bricked" kind of way or an error message telling you it wont flash?
it will error telling it was aborted. i have done it once that's all it took for me to realise it needed the exact version. i was lucky to have the right one handy
here is a site for all the stock firmware.
http://motofirmware.center/files/category/
I'm in the same boat and going to do this tonight on my wife's phone.
She's currently on 4.2.2, bootloader is unlocked, rooted, and currently has TWRP installed.
If I'm correct, I need to
1. Flash stock recovery
2. Boot up and take the OTAs
then
3. Flash the latest TWRP
4. Use TWRP to re-root
4. Then I can flash a 4.4.4 rom, such as http://forum.xda-developers.com/showthread.php?t=2716824
Is that correct?
As long as my bootloader is unlocked, can I still regain root with the latest OTA?
Thanks guys, just making sure as the wife will be miffed if I screw up her phone!
Honestly, I doubt you have waited this long, but if you have, here is what I am gathering from your question... You want to run 4.4.4 roms instead of 4.2? While on 4.2.2 (if you still are) you can run OSE, AOSB, CM11, and pretty much any 4.4.4 custom rom. (though i can't get cm12 to work on a mini (same software/bootloader/recovery for the most part) on 19.6.3 so that may be out) The only reason you would have to update would be to be on stock 4.4.4. I haven't read up too much on the new OTA's, but I can say this, YOU CAN NEVER GO BACK TO WHAT YOU ARE ON ONCE YOU UPGRADE STOCK. this may not be a big deal for you, but personally, I liked the JB software the best (specifically 12.7.7 that my DEV MAXX came with) I haven't heard anyone say anything positive (really) about VOLTE or any new features, and honestly, not being able to go back on a DEV EDITION sucks. On a side note, I recently bought a Mini (bc my charge port on my DEV maxx crapped out and Moto doesn't have any more, so i am in phone purgatory waiting for *something* but pretty much anyone I have talked to is useless.) I just fxz'd back to 19.5.3 from 19.6.3, but I cannot go backwards any further *completely* @NWKENT has done it numerous times as best as it *can* be done. also, @NWKENT can confirm you absolutely cannot go back from 4.4.4 to an earlier edition. I hope this helps if you haven't upgraded yet. If you have, for most intents and purposes, you haven't really lost anything.

Updated to 6.0.1, CAN THIS BE UNDONE??

First, I'd like to say that while I'm not new to this, I AM quite rusty. So before you call me retarded for doing what I did, I already know. Now...
I have been just daily driving along on 4.4.2 for a good few years on my phone but I just got a Tab4 and rooted it and noticed that the TWRP version I wound up with was newer than on my phone, and had a few more options. Sooo, I tried to Odin the TWRP to my phone and caused all kinds of problems. Wouldn't boot. So I downloaded everything I could get my hands on to try to Odin onto the G900V to get it up and running again. The ONLY this I could flash was this...
PD1_Full_Factory_Restore_No_Aboot.tar
So now the phone is on the 6.0.1 which I figured was great but quickly noticed that not everything was working. No WiFi, no Camera, no Back and Recent keys, and no extsdcard recognition, so obviously unacceptable. Is this too new to be undone? I spent all night last night and today reading through the various forums, and I haven't seen it directly addressed.
Here are my questions...
1. Can I root this and fix the issues from there? If so, with what tool?
2. If I cannot yet root this, how do I downgrade from this kernel/firmware to something that is at least stable for this device?
Point me in the right direction, I'm not a total newb. I've rooted many devices, many times, but I really haven't been keeping up on anything for some time. Any help would be awesome, I'll pour some beer out for you, Thx in advance.
~Chris
I tried all of these, none will flash via Odin but the one that got me to where I am (PD1)
mods, please delete this post #2.
I edited it all into #1
Odin back to stock
I did something similar, which is what I get for just reading the instructions instead of the warnings at the top of a post.
I tried a number of things, but ended up using odin to do a complete wipe and go back to stock.
Thanks for the reply.
AFAIK this IS a stock ROM, but as I said this was the only thing I could get to flash after I tried to flash a new TWRP. Nothing else will go.
Being a bit rusty myself, it caught my ear when you mentioned the full wipe, I never performed a wipe of any sort during my efforts.
Could that be the problem?
Also, someone please refresh my memory, what piece is it that actually determines whether a device is rootable?
Is it the kernel? Is this one rootable? What is the modern method for acquiring root? I was using towelroot back in the 4.4.2/4.4.4 days.
Thanks
UPDATE : It also will not make a phone call. Hitting the CALL button or trying to answer when it rings will cause the phone to reboot, lol
Someone please get me back to a custom recovery, I've got some great TWRP backups and a ****load of titaniumBU
Just downgrade to PB1 using the stock TAR and unlock your bl from there...
Thank you for the PB1 advice.
Should I be able to accomplish this via Odin?
Is a full wipe/reset required?
Thank you for the PB1 tip
Got that handled, all is up and running, but not rooted
Gunna have to wait till after work for that stuff
Thanks again
OK so now I'm fully stock PB1, where do I want to go from here to acquire root?
Which of these 2 threads shall I follow?
[GUIDE] Unlocking the Galaxys S5 Bootloader using DEV Bootloader [KK-MM], OR...
Working Root Method For 5.0 Lollipop Roms [OE1] [OG5] [OK3] [PB1] [3-3-16]
I ask because above I was advised to "downgrade to PB1 using the stock TAR and unlock your bl from there..."
My question arises from the fact that I had this phone rooted for YEARS before I messed it up, and the thread proclaiming that "S5 bootloader unlock is here!" seems to be only 3 months old. Leading me to wonder, do I need an unlocked bootloader, or merely to acquire root? Seems like a valid question to me. I just want to make sure in advance before proceeding.
SO in summary, this is the question...
Which of these 2 threads shall I follow?
[GUIDE] Unlocking the Galaxys S5 Bootloader using DEV Bootloader [KK-MM], OR...
Working Root Method For 5.0 Lollipop Roms [OE1] [OG5] [OK3] [PB1] [3-3-16]
Also, what file system do I want for my SDcard?
Thank You
cjschriver3 said:
OK so now I'm fully stock PB1, where do I want to go from here to acquire root?
Which of these 2 threads shall I follow?
[GUIDE] Unlocking the Galaxys S5 Bootloader using DEV Bootloader [KK-MM], OR...
Working Root Method For 5.0 Lollipop Roms [OE1] [OG5] [OK3] [PB1] [3-3-16]
I ask because above I was advised to "downgrade to PB1 using the stock TAR and unlock your bl from there..."
My question arises from the fact that I had this phone rooted for YEARS before I messed it up, and the thread proclaiming that "S5 bootloader unlock is here!" seems to be only 3 months old. Leading me to wonder, do I need an unlocked bootloader, or merely to acquire root? Seems like a valid question to me. I just want to make sure in advance before proceeding.
SO in summary, this is the question...
Which of these 2 threads shall I follow?
[GUIDE] Unlocking the Galaxys S5 Bootloader using DEV Bootloader [KK-MM], OR...
Working Root Method For 5.0 Lollipop Roms [OE1] [OG5] [OK3] [PB1] [3-3-16]
Also, what file system do I want for my SDcard?
Thank You
Click to expand...
Click to collapse
https://www.youtube.com/watch?v=WS86FHqY6rE with appropriate files worked! Tremendous help for me.
Miilliiee said:
https://www.youtube.com/watch?v=WS86FHqY6rE with appropriate files worked! Tremendous help for me.
Click to expand...
Click to collapse
Thx for that. Being able to see the video helped a lot, not because I can't read, but just because I was able to see what was SUPPOSED to happen at each step.
All fixed up now. Thx again.

D6616, Possibly the worst phone to mess with! Hard bricked, absolutely lifeless!

I thought everything was fixable with flashtool as long as the bootloader is unlocked.. never been so wrong in my life.
Bought a used xperia z3 6166 t mobile version without knowing its support for custom roms (smh).. steps i did:
1)installed recovery.
2) rooted the device
3) unlocked the bootloader (successfully)
4) i thought i was ready to install custom roms like niaboc79's existenz which consequently I did, the phone did boot after that but was connecting in fastboot and flashboot so
5)using flashtool flash stock latest d6616 firmware and was back to step 1.
read somewhere that I could flash d6603 firmware because both phones have same specs so
6)flash d6603 firmware in order to get existenz working
7)flashtool gave some errors and failed
8)used fastboot to flash kernel
the device stops responding all of a sudden..
9) kept on charge for hours, still got nothing , no vibration, no lights , no hard rest via combination of buttons , nothing by pressing the yellow button inside the flap..
10) pc shows usb not recongnized after a couple of seconds of connecting ..
its been beyond frustrating going through the internet, scrolling through threads after thread but no avail.. people say at least the phone should be recognized by pc in any form other than usb not recongnized .. so I went to a local smartphone repair shop and gave it to him but he isnt too hopeful either.. I already have xperia z1c which i messed with so many times but it always responds to the flashtool.. but buying xperia z3 is literally the worst smartphone experience of my life!
is there any way to make this dead brick work again.. any unorthodox means to rewrite boot to make it jump start? any help is appreciated!
hash054 said:
I thought everything was fixable with flashtool as long as the bootloader is unlocked.. never been so wrong in my life.
Bought a used xperia z3 6166 t mobile version without knowing its support for custom roms (smh).. steps i did:
1)installed recovery.
2) rooted the device
3) unlocked the bootloader (successfully)
4) i thought i was ready to install custom roms like niaboc79's existenz which consequently I did, the phone did boot after that but was connecting in fastboot and flashboot so
5)using flashtool flash stock latest d6616 firmware and was back to step 1.
read somewhere that I could flash d6603 firmware because both phones have same specs so
6)flash d6603 firmware in order to get existenz working
7)flashtool gave some errors and failed
8)used fastboot to flash kernel
the device stops responding all of a sudden..
9) kept on charge for hours, still got nothing , no vibration, no lights , no hard rest via combination of buttons , nothing by pressing the yellow button inside the flap..
10) pc shows usb not recongnized after a couple of seconds of connecting ..
its been beyond frustrating going through the internet, scrolling through threads after thread but no avail.. people say at least the phone should be recognized by pc in any form other than usb not recongnized .. so I went to a local smartphone repair shop and gave it to him but he isnt too hopeful either.. I already have xperia z1c which i messed with so many times but it always responds to the flashtool.. but buying xperia z3 is literally the worst smartphone experience of my life!
is there any way to make this dead brick work again.. any unorthodox means to rewrite boot to make it jump start? any help is appreciated!
Click to expand...
Click to collapse
My sincerest apologize for your misfortune. I have not yet encountered this degree of issues. I am going to keep my bootloader locked I do believe. Just got this phone myself and I really wish I could help you. The TMO version of this phone is definitely the worst one I think given the lack of software support.
However I was wondering what method you followed to install recovery and if you attempted to install exposed.
arikdahn said:
My sincerest apologize for your misfortune. I have not yet encountered this degree of issues. I am going to keep my bootloader locked I do believe. Just got this phone myself and I really wish I could help you. The TMO version of this phone is definitely the worst one I think given the lack of software support.
However I was wondering what method you followed to install recovery and if you attempted to install exposed.
Click to expand...
Click to collapse
used the XZdualrecovery zip for locked bootloader.. it was fairly simple , did it twice without any problems! then used recovery to install superuser and update it binaries and the phone was rooted.. I didnt installed xposed because i want to upgrade from lollipop.. that I couldnt do! :crying:
May this thread be a warning to people who themselves arent developers but have a little knowledge about custom roms to do their homework before diving into things they cant get out of..
hash054 said:
used the XZdualrecovery zip for locked bootloader.. it was fairly simple , did it twice without any problems! then used recovery to install superuser and update it binaries and the phone was rooted.. I didnt installed xposed because i want to upgrade from lollipop.. that I couldnt do! :crying:
May this thread be a warning to people who themselves arent developers but have a little knowledge about custom roms to do their homework before diving into things they cant get out of..
Click to expand...
Click to collapse
I will second the f*** out of this, but I will also add that recovery TYPICALLY protects you from a ton of heartache. Not this time huh? Well, I cannot get Kingroot off my frickin' phone. I think it may have been commandeered by China. The uninstall always fails. So I may be in the same boat as you. Not sure if I can install recovery with it on there or not, but I do know it and SuperSU do not play nicely. I am debating which would be more risky, factory resetting a rooted phone to get rid of kingroot, or attempting to install recovery with this scary AF root manager. What a pain in the ass.
So this is the procedure you followed?
https://forum.xda-developers.com/showpost.php?p=60507399&postcount=171
arikdahn said:
I will second the f*** out of this, but I will also add that recovery TYPICALLY protects you from a ton of heartache. Not this time huh? Well, I cannot get Kingroot off my frickin' phone. I think it may have been commandeered by China. The uninstall always fails. So I may be in the same boat as you. Not sure if I can install recovery with it on there or not, but I do know it and SuperSU do not play nicely. I am debating which would be more risky, factory resetting a rooted phone to get rid of kingroot, or attempting to install recovery with this scary AF root manager. What a pain in the ass.
So this is the procedure you followed?
https://forum.xda-developers.com/showpost.php?p=60507399&postcount=171
Click to expand...
Click to collapse
No thats the rooting method.. I just simply flashed the recovery from http://nut.xperia-files.com/path/XZDualRecovery/XZDualRecovery_2.8.26 and just installed superuser and updated the binaries..
I did also have a problem with kingroot.. you can download the official ftf firmware for d6616 and just flash it in flashboot through flashtool.. its the only way to get rid of kingroot in my experience .. but I would give you caution to flash nothing else except official firmware through flashtool.. and do it only if you know how to handle it.. as far my experience is concerned, I did get rid of the kingroot this way not once but twice without problem .. its the stuff that followed bricked the phone.. also my bootloader was unlockable so it might have made a difference..maybe
hash054 said:
No thats the rooting method.. I just simply flashed the recovery from http://nut.xperia-files.com/path/XZDualRecovery/XZDualRecovery_2.8.26 and just installed superuser and updated the binaries..
I did also have a problem with kingroot.. you can download the official ftf firmware for d6616 and just flash it in flashboot through flashtool.. its the only way to get rid of kingroot in my experience .. but I would give you caution to flash nothing else except official firmware through flashtool.. and do it only if you know how to handle it.. as far my experience is concerned, I did get rid of the kingroot this way not once but twice without problem .. its the stuff that followed bricked the phone.. also my bootloader was unlockable so it might have made a difference..maybe
Click to expand...
Click to collapse
Well I guess I'll be doing that then. Thanks. So how do you flash that file without a recovery?
I do not know how to handle flash tool since I have only heard of it and never used it. It appears I'll be using it to get rid of kingroot. How does one learn how to handle it so's one doesn't go and mess anything up?
My bootloader is also unlockable but I don't wanna screw with all the things that unlocking it does to the phone so I'm leaving it alone. I like those features
Also did you ever try to remove bloat on the stock ROM? Everything I remove via titanium backup just reinstalls immediately after removal.
Sorry for all the questions instead of answers for you. You are one of the few still messing with this device and I appreciate all your help very much. All of the info on this forum is mostly applicable to when the phone came out. This means almost all of it only applies to android 4.4 or it doesn't apply to the T-Mobile variant b/c T-Mobile was less popular when this phone was a flagship and uses Wifi text/calling which requires special planning. That and the fact that the threads are several hundred pages long makes following along impossible and makes this site all but useless for these phones now.

Categories

Resources