Related
I was trying to restore my phone back to stock and unroot my phone.
Now its stuck the boot screen with the unlocked padlock at the bottom.
Can I push a rom on the device? Or just a way to unroot it so I can send it back?
jhericurls said:
I was trying to restore my phone back to stock and unroot my phone.
Now its stuck the boot screen with the unlocked padlock at the bottom.
Can I push a rom on the device? Or just a way to unroot it so I can send it back?
Click to expand...
Click to collapse
Do you have basic windows skills? Can install drivers and use device manager if need be?
If so, install the fastboot drivers, and then download the factory images from google here http://code.google.com/android/nexus/images.html
Once you have fastbook working I'll tell you what to do next.
Luxferro said:
Do you have basic windows skills? Can install drivers and use device manager if need be?
Click to expand...
Click to collapse
I don't have a PC, I'm using a Mac. I been using the Terminal window to push the stock ROM but I must be doing something wrong.
The main thing I really want to do is get rid of the unlock icon, so I can send if back for a replacement.
well if you unlocked it you had to have fastboot working. so just fastboot oem lock
Hello All!
This is my guide to rooting, recovering, and "romming" the Motorola Droid Razr M!
ROM: CyanogenMod 10.1 Official
DISCLAIMER: All software that I will provide links to is AS-IS. I will NOT be responsible for anything that happens to your phone as a result of this guide
Lets Begin!
Pre-Reqs:
- All download links are in the text document below. I am not allowed to post outside links because this is my first post
-Razr M
-OEM Cable
-Software Version must be < 98.18.78.XT907.Verizon.en.US (If software is 98.18.78 and you haven't unlocked your bootloader follow this guide (link in text document below) to only root your device )
-Android Jelly Bean 4.1 (I did mine with 4.1.2. Not sure it will work on ICS)
-Battery % > than 90 %
-Patience
-MAKE SURE TO BACK EVERYTHING UP (CONTACTS, DATA, TXTS, ETC)!!
Part 1 (Rooting):
Step 1: Obtain the "motochopper.zip" file (Credit to Dan Rosenberg)
Step 2: Extract the zip
Step 3: Make sure to have the latest windows drivers for phone (If not on windows skip this step):
Step 4: Connect M to computer and make sure usb debugging is enabled (allows computer to "talk" to phone)
Step 5: Navigate to motochopper folder and click "run.bat"
Step 6: Follow on-screen instructions
Step 7: Jump for joy because you now have root!
Step 8: Proceed to Part 2
Part 2 (Bootloader):
Step 1: Obtain the "motopocalypse.zip" file (Credit to Dan Rosenberg)
Step 2: Extract the zip
Step 3: Connect M to computer
Step 4: MAKE SURE that you have root!!!!!
Step 5: Click "run.bat"
Step 6: Follow on-screen instructions
Step 7: Confirm that the bootloader is unlocked (Status code 3 or "Warning Bootloader Unlocked!" Screen on boot up)
Step 8: Proceed to Part 3 if confirmation is successful
Part 3 (Recovery/ROM):
Before you proceed you must be sure that you actually want to install a ROM on your device. My choice was CyanogenMod 10.1 Official for the Razr M.
If you find some other guide that has a safer way of doing this the use that one.
Step 1: Obtain a recovery image. I chose ClockworkMod 6.0.3.2
Step 2: Put this file inside of the "motopocalypse" folder
Step 2.1: Grab the CyanogenMod 10.1 Official Zip and the gapps package
Step 2.2: Put these files on the root of your Android phone (/sdcard) or on a microSD and put it into your phone
Step 3: From the command window type: "adb reboot-bootloader" and hit enter. You should be greeted with a familiar screen;
Ok, here is where the guides on the internet failed me. On the official cyanogenmod blog for the Razr M, it says to issue: "fastboot flash recovery your-recovery.img" and then "fastboot boot your-recovery.img". This first command worked but the second one didn't and I was unable to ever boot into CWM. That's when I had to turn to this command: "fastboot flash boot recovery.img". What this command does is replace your boot sequence (correct me if i am wrong) with CWM. So when you reboot, it will only boot into CWM. This is why your have to be serious about putting a ROM on your device. Installing a ROM fixes the boot sequence.
Step 4: If you want to continue issue the command: "fastboot flash boot your_recovery_filename.img" If you want to turn back now issue the command: "fastboot continue"
Step 5: If it installed the recovery correctly then issue "fastboot reboot"
Step 6: You will now hopefully boot into CWM.
Step 7: Use volume keys to scoll and power to select
Step 8: Choose wipe_data/factory_reset and confirm the choice
Step 9: Choose "install zip from sd" and select the CyanogenMod package. Confirm and you will see it install
Step 10: Choose "install zip from sd" and select the Gapps package. Confirm and you will see it install
Step 11: On the main menu select "reboot phone now"
Step 12: If everything was successful you will boot into CyanogenMod 10.1 Official!
Step 13: Set everything up.
Step 14: Proceed to Part 4
Part 4 (Recovery again/ Finishing up):
Step 1: Everything may seem ok, but you don't have a recovery partition anymore
Step 2: Connect M to computer if it isn't anymore
Step 3: Hold down vol+, vol-, and power at the same time to get to boot menu. Select bootloader with vol- and select it with vol+
Remember my big spiel earlier about how these commands didnt work. Well now they do! I suspect that the didn't work before because Verizon's OEM Android kept overwriting your custom recovery
Step 4: Go to "motopocalypse" folder and Issue "fastboot flash recovery the-same-file-you-flashed-earlier.img"
Step 5: It will succeed and then issue "fastboot continue"
Step 6: Now you have your recovery partition back! You can now boot into it from the boot menu or from the cyanogenmod menu
Step 7: Not over yet! Boot back into CyanogenMod and go to settings
Step 8: In Android 4.2+ the developer settings are disabled. To fix this tap on the build number in the "about phone" section 10 times
Step 9: From now on to use adb your will need to get the updated adb files for Android 4.2+ :
Step 10: You may notice that the screen has some kind of weird refresh bug when you scoll. To fix this, check the Developer Setting item that says "Disable HW overlays"
Step 11: Enjoy
Thank you guys so much for reading this guide and I hope you found it very helpful!
If you have any questions or problems leave a comment or just PM me. I will do my best to help you out.
Cheers,
Ryan (carb0nrain)
it works
it works on the Razr M 201M softBank.
Will this work with the latest OTA?
I know the latest OTA was supposed to have removed the unlock exploit. If I follow all the intructions will I still be able to root AND unlock?
Root with the latest OTA update
Forveralon said:
I know the latest OTA was supposed to have removed the unlock exploit. If I follow all the intructions will I still be able to root AND unlock?
Click to expand...
Click to collapse
This guide is only meant for people how don't have the latest OTA update. The latest OTA update removed the bootloader unlock exploit which means that you can't install a custom recovery or ROM. However, there is still a way to root your M with the latest OTA update. Look at the first link in the text document above (I can't post links directly in replies because i am a fairly new member). Hope this helps!
Cheers,
Ryan
I am the op of the other method in the dev forum.
Seems we approach it from opposite ends. Do we get the same results?
I need to check yours out....
Different Ends
aviwdoowks said:
I am the op of the other method in the dev forum.
Seems we approach it from opposite ends. Do we get the same results?
I need to check yours out....
Click to expand...
Click to collapse
This is how it worked for me. (See attached pic) Which part did we do differently. If anything is wrong, please feel free to correct me.
Cheers,
Ryan
Do you want to be on the old radio-...81p? The new is in my goodies...78p.
Radio
aviwdoowks said:
Do you want to be on the old radio-...81p? The new is in my goodies...78p.
Click to expand...
Click to collapse
Could you explain to me what the radio file is? And what is the difference between the 81p and the 78p radios. This is one of the subjects that i still dont know much about.
Thanks
Just flash it from recovery. It is from 981878.
Radio
aviwdoowks said:
Just flash it from recovery. It is from 981878.
Click to expand...
Click to collapse
Thanks
Could one of you in the know, please give the system versions that allow root? I just bought a Razr M, that came with 98.16.1.XT907 and the one click root worked fine. There is a nag wanting to do a OTA for version 98.16.3 but I keep telling it "later" as I do not know if that version is rootable. Is it?
Thank you, and I hope this helps someone else.
Rumblur said:
Could one of you in the know, please give the system versions that allow root? I just bought a Razr M, that came with 98.16.1.XT907 and the one click root worked fine. There is a nag wanting to do a OTA for version 98.16.3 but I keep telling it "later" as I do not know if that version is rootable. Is it?
Thank you, and I hope this helps someone else.
Click to expand...
Click to collapse
The new version is rootable but you can't unlock the bootloader. If you are still on the older version, you're lucky. Unlock the bootloader and don't take the update until afterwards. Even if you don't use it, you might regret not unlocking the bootloader because the update blocked the bootloader unlock exploit. Look for the RazrM Utility 1.20. It has the root method, bootloader unlock, recovery flash tool, and recovery tool all in one package.
RikRong said:
The new version is rootable but you can't unlock the bootloader. If you are still on the older version, you're lucky. Unlock the bootloader and don't take the update until afterwards. Even if you don't use it, you might regret not unlocking the bootloader because the update blocked the bootloader unlock exploit. Look for the RazrM Utility 1.20. It has the root method, bootloader unlock, recovery flash tool, and recovery tool all in one package.
Click to expand...
Click to collapse
So if I read you right, you're saying go ahead and unlock the bootloader, root it, take the OTA (just the one I mentioned or all of them? I think there's one even newer than that if not two) and then using the tool you mentioned, root it again?
Rumblur said:
So if I read you right, you're saying go ahead and unlock the bootloader, root it, take the OTA (just the one I mentioned or all of them? I think there's one even newer than that if not two) and then using the tool you mentioned, root it again?
Click to expand...
Click to collapse
Yeah, pretty much, but you'll need to root first, then unlock the bootloader (use utility 1.20 for this). After that, you can take the OTA and reroot by using Motochopper 1.3 or by just flashing a SU zip in recovery. The utility can be used on the previous update only, not the newest one. Another option for you after you unlock the bootloader and install a custom recovery, is using one of the stock based ROMs on this forum or Batakang. There are a couple of stock based, pre-rooted ROMs running around here.
RikRong said:
Yeah, pretty much, but you'll need to root first, then unlock the bootloader (use utility 1.20 for this). After that, you can take the OTA and reroot by using Motochopper 1.3 or by just flashing a SU zip in recovery. The utility can be used on the previous update only, not the newest one. Another option for you after you unlock the bootloader and install a custom recovery, is using one of the stock based ROMs on this forum or Batakang. There are a couple of stock based, pre-rooted ROMs running around here.
Click to expand...
Click to collapse
OK, I took the 3.1.6 update and the bootloader is still unlocked. I tried using the utility 1.20 afterwards and the root (option 5) failed. It said "SU already exists". If I uninstall SU would that help and then it take root? Or, is there another version of motochopper that I need to find and download?
Rumblur said:
OK, I took the 3.1.6 update and the bootloader is still unlocked. I tried using the utility 1.20 afterwards and the root (option 5) failed. It said "SU already exists". If I uninstall SU would that help and then it take root? Or, is there another version of motochopper that I need to find and download?
Click to expand...
Click to collapse
If your bootloader is unlocked and you have an aftermarket recovery installed, all you need to do is flash a SU zip in recovery.
RikRong said:
If your bootloader is unlocked and you have an aftermarket recovery installed, all you need to do is flash a SU zip in recovery.
Click to expand...
Click to collapse
No aftermarket (that I know of, but I'm rusty on this stuff as this is the first thing I've done since the HTC Inc2). I just found a DL for motochopper 1.1.2 and used it. I downloaded a root checker from the store and it says "this device has root access". So I guess I'm good!
While I have your help and attention here, I've looked at the ROMs listed on this site but there is not much information about why one is better than another etc. I'm perfectly fine with the stock phone "IF" it has root (which it does now) and IF the weird shutdown/lockup thing goes away. My other #1 main concern is anything that will increase reception.... I am leaving the Inc2 behind for that very reason... horrible reception.
Rumblur said:
No aftermarket (that I know of, but I'm rusty on this stuff as this is the first thing I've done since the HTC Inc2). I just found a DL for motochopper 1.1.2 and used it. I downloaded a root checker from the store and it says "this device has root access". So I guess I'm good!
While I have your help and attention here, I've looked at the ROMs listed on this site but there is not much information about why one is better than another etc. I'm perfectly fine with the stock phone "IF" it has root (which it does now) and IF the weird shutdown/lockup thing goes away. My other #1 main concern is anything that will increase reception.... I am leaving the Inc2 behind for that very reason... horrible reception.
Click to expand...
Click to collapse
If you want to run a custom ROM, you'll need to install TWRP or CWM. If you want to get the best reception, stick to stock and just tweak it, or find one of the customized/deodexed/tweaked stock ROMs running around here. I've had no issues with aftermarket ROMs and signal, but many people have complained about weaker reception on the aftermarket ROMs.
many thanks. I will check out the deodexed stuff. Is there any preference or reason to pick TWRP over CWM or vice versa? One last question after that.... when I had a Droid X, when I was ready to sell it I used a SBF CD to put it back to bone stock OEM. Is there something like that for the M?
Rumblur said:
many thanks. I will check out the deodexed stuff. Is there any preference or reason to pick TWRP over CWM or vice versa? One last question after that.... when I had a Droid X, when I was ready to sell it I used a SBF CD to put it back to bone stock OEM. Is there something like that for the M?
Click to expand...
Click to collapse
I prefer TWRP because it's easier use. Also, it seems to work better than CWM for the 4.3 ROMs that are out now. Yeah, you can run a XML in RSD and restore to stock. Here's a complete listing of Moto firmware.
http://sbf.droid-developers.org/
Im thinking of buying a Z5P and while i have searched a lot, i just cant seem to find the answer to a question i have maybe someone here can help. On Sonys developer website there is instructions on how to unlock the bootloader and the last line of the instructions are as follows, note the part in blue text.
Tap Service info > Configuration > Rooting Status. If Bootloader unlock allowed says Yes, then you can continue with the next step. If it says No, or if the status is missing, your device cannot be unlocked.[/B]
My question is how/where do i buy a Z5P that will definitely be Bootloader unlock allowed yes, surely its not just a case of random devices are unlockable is it? I was going to buy this from carphone its sim free so im expecting to be allowed to unlock the bootloader but dont want to buy it only to find i cant.
http://www.carphonewarehouse.com/phones/sony-xperia-z5-premium/handset?colourCode=BLACK
If the phone has no SIM lock, it's bootloader should be unlockable. I say "should" since I am not aware of other factors that keep the bootloader locked, but there might as well be.
On another note, unless you are a fairly advanced user and are set on flashing your device with a custom kernel, I would not recommend a bootloader unlock before root or an option to back up of TA becomes available.
It contains your device's DRM which gets irreversibly lost which makes your camera perform worse(BIONZ stops working), among other things.
CPW is the place to go for unlockable fones. I got my Z5P from there.
Sent from my SGP311 using XDA Free mobile app
As mentioned elsewhere, IN GENERAL (rare exceptions) - if it's SIM-unlocked it'll be bootloader-unlockable. If it's SIM-locked, the bootloader is almost guaranteed to be perma-locked.
While SIM locks and bootloader locks are technolgically independent, in the case of Sony devices (This rule of thumb can NOT be applied to any other manufacturer), SIMlocked devices have a permanent bootloader lock, devices sold without a SIM lock can have bootloader unlocked. Note that in the case of phones sold with a SIM lock that are later unlocked with a PIN - the bootloader lock is still disallowed.
Cheese for the replys everyone I got the phone from the carphone and its boot loader unlock allowed yes
I got the regular z5 instead though.
Hey, Dunno if I have an option or not, but my phone says Bootloader Unlock Allowed: No.
I imagine that it's a no, but is there any way to unlock the BL? If not I may consider swapping the Z5P out for something else, dunno if I can live without root
NJ72 said:
Hey, Dunno if I have an option or not, but my phone says Bootloader Unlock Allowed: No.
I imagine that it's a no, but is there any way to unlock the BL? If not I may consider swapping the Z5P out for something else, dunno if I can live without root
Click to expand...
Click to collapse
Try flashing another firmware through flashtool that is allowed.
KbaB.BroS said:
Try flashing another firmware through flashtool that is allowed.
Click to expand...
Click to collapse
Worth a punt, didn't think about that. The only concern is that Flashtool isn't supported for the Z5p according to Sony's site.
NJ72 said:
Worth a punt, didn't think about that. The only concern is that Flashtool isn't supported for the Z5p according to Sony's site.
Click to expand...
Click to collapse
As long as you use flashmode there is no need to be supported, because the program doesn't know which phone it is in that state. I flashed my Z5P once using flashtool about a week ago.
KbaB.BroS said:
As long as you use flashmode there is no need to be supported, because the program doesn't know which phone it is in that state. I flashed my Z5P once using flashtool about a week ago.
Click to expand...
Click to collapse
OK, cool, thanks.
Where do I get the firmware from for Flashtool? Can I flash something like AurRom using Flashtool?
Sorry for the idiot questions, but I haven't used Flashtool very much at all. Much more familiar with ODIN, ADB and flashing through recovery...
NJ72 said:
OK, cool, thanks.
Where do I get the firmware from for Flashtool? Can I flash something like AurRom using Flashtool?
Sorry for the idiot questions, but I haven't used Flashtool very much at all. Much more familiar with ODIN, ADB and flashing through recovery...
Click to expand...
Click to collapse
Install flashtool from "flashtool.net"
It comes bundled with Xperifirm where you can download ftf files for every Xperia device. You access Xperifirm through the Flashtool program.
You cannot flash AurROM through flashtool because it's not a ftf file. Flash a stock rom and try unlocking the Bootloader afterwards.
And don't worry about asking "stupid questions". This thread is made for every kind of questions, as long as it's about the device.
KbaB.BroS said:
Install flashtool from "flashtool.net"
It comes bundled with Xperifirm where you can download ftf files for every Xperia device. You access Xperifirm through the Flashtool program.
You cannot flash AurROM through flashtool because it's not a ftf file. Flash a stock rom and try unlocking the Bootloader afterwards.
And don't worry about asking "stupid questions". This thread is made for every kind of questions, as long as it's about the device.
Click to expand...
Click to collapse
Thanks very much.
One final question, in the UK I have EE WiFi calling currently - if I install non-carrier specific firmware I will most likely lose this. Is there any way I can backup the existing software so I can revert whether the flashtool flash works or not?
NJ72 said:
Thanks very much.
One final question, in the UK I have EE WiFi calling currently - if I install non-carrier specific firmware I will most likely lose this. Is there any way I can backup the existing software so I can revert whether the flashtool flash works or not?
Click to expand...
Click to collapse
You can try this guide:
http://m.youtube.com/watch?v=F0bSsGxFdks
NJ72 said:
Thanks very much.
One final question, in the UK I have EE WiFi calling currently - if I install non-carrier specific firmware I will most likely lose this. Is there any way I can backup the existing software so I can revert whether the flashtool flash works or not?
Click to expand...
Click to collapse
What you want to do is follow sonys instructions on how to check if your phone is able to unlock bootloader here: http://developer.sonymobile.com/unlockbootloader/unlock-yourboot-loader/
If you can unlock your bootloader, which you will know after performing the simple steps provided by sony, then you need to install android studio along with required drivers etc, before you can actually unlock the bootloader.
Android studio can be found here: http://developer.android.com/sdk/installing/index.html?pkg=studio
Read everything throughly, it is important to get all the details regarding usage and installation.
After installing Android studio, you should download all the required SDK's found inside android studio->Configure->SDK Manager.
On the left side you will see several options in the navigation menu.
First go to Appearance & Behavior->System settings->Android SDK. Then in the "window" you have, make sure the first tab is selected (SDK Platforms).
Here you need to check all the android versions your phone(s) run.
Then go to the second tab (SDK Tools) and download:
Android SDK Build Tools
Android SDK Tools 24.4.1
Android SDK Platform-Tools 23.1
Google USB Driver
Android NDK
I am not sure if you really need the NDK one, but the rest I think is required. You can do as I did and choose all if you want.
On the last tab (SDK Update Sites) I have checked everything.
When you have done all of this, you should install Flashtool and go to the install directory and open the Driver folder, where you will find a .exe file. Run this and click next untill you can choose a few items from a list, in this list you should check Fastboot drivers, and USB drivers, and any other options that are relevant to your use, then finish the installation. (The entire installation of Flashtool should be done with 100% admin rights on the user).
After this is done, connect your phone to your pc and go to device management on your pc and you will likely find something similar to this:
If you have this yellow exclamation mark triangle thingy, then you will need to manually install your USB drivers.
Download your driver here: http://developer.sonymobile.com/downloads/drivers/
Then right click the yellow exclamation mark triangle thingy device in device management, and select update driver, then select "Browse my computer for driver software".
On the next window, select "Let me pick from a list of device drivers on my computer".
In the list that appears, select "Show All Devices" and click next.
Click the "Have Disk" button, then navigate to the driver you downloaded, and you will get 3 options in the window on you screen, select "Android ADB Interface" and click next.
Confirm by pressing "Yes" Then press "Install".
If completed without problems you should see "Windows has successfully updated your driver software".
*NOTE* On the above steps, you can also navigate to the folder where you installed android studio, which should be something similar to this: C:\Program Files(x86)\Android\android-sdk\extras\google\usb_driver OR it can be found your USER folder.
and here you can install the usb_driver aswell, which should make most phones support USB debugging and ADB on via your pc.*NOTE*
now reconnect your phone and the exclamation mark triangle thingy should be gone, good!
Next thing you can do is navigate to the installation folder of Android studio, and go to the Platform-Tools folder.
Inside the folder, hold down shift, while right clicking any white empty space inside the folder, and click open terminal here.
In the terminal, type: "adb devices" /Without the " marks. then it should say something about daemon not running etc, when its done, do the same command again, and you should se you device listed. Good, at this point you are ready to unlock bootloader!
If you have succeeded in every step so far, then go ahead and unlock bootloader following sonys instructions!
When you are done, you can simply follow the guides provided in the custom Rom thread itself most of the time.
If not, then a simple way to do it is:
Get all the files you need for the rom flash. That means Kernel, rom img, and a custom recovery like TWRP and SuperSU.
It is REALLY important that all files are for your device specifically!
Put the SuperSU.zip and the custom Rom.zip on your sd card and put it in the phone.
To avoid any trouble, do as I did and save all those files in the Platform-Tools folder, because you need to open the terminal as shown earlier in the post, by holding shift and right clicking in the same folder as the files, this is a must.
Open the terminal from the same folder as the rom, kernel and recovery.
type:
Code:
fastboot flash boot NAMEOFYOUR_KERNEL.img (This is usually boot.img)
fastboot flash recovery NAMEOFYOUR_RECOVERY.img (Usually contains TWRP in name)
fastboot reboot
You should now press volume up key when a led lights up while you see the sony logo, a orange light, not the red one, this will bring you into recovery, from here choose install, then navigate to your SuperSU.zip and install it.
Reboot your phone and you are now rooted, if you also have a custom rom, then place it on your sd card like the SuperSU.zip, but make sure the custom rom is a ZIP file!
Boot into recovery and install the custom rom, wipe cache and dalvick cache.
Congratulations on your custom rom!
Hope this helps a bit, sorry for any errors, but this is exactly how I did it, as far as I can remember!
Btw, this can seem like alot of work, especially when and if you encounter any problems while installing. I know I did encounter ALOT of them, but hopefully with my simple guide you can avoid them!
Luckily, this is just something you have to do once if you do it 100% right!
xirt0n said:
What you want to do is follow sonys instructions on how to check if your phone is able to unlock bootloader here: http://developer.sonymobile.com/unlockbootloader/unlock-yourboot-loader/
If you can unlock your bootloader, which you will know after performing the simple steps provided by sony, then you need to install android studio along with required drivers etc, before you can actually unlock the bootloader.
Click to expand...
Click to collapse
The problem he has is that his stock ROM (or the phone itself) doesn't allow bootloader unlocking, probably because of SIM and carrier lock. Therefore he first needs to find a way to make the phone unlockable.
KbaB.BroS said:
The problem he has is that his stock ROM (or the phone itself) doesn't allow bootloader unlocking, probably because of SIM and carrier lock. Therefore he first needs to find a way to make the phone unlockable.
Click to expand...
Click to collapse
I am no expert on this, but doesnt the carrier decide if its locked or not?
I've seen people solve it by flashing different and unbranded firmware, but not for this particular phone tho, but I dont think it's officially possible.
xirt0n said:
I am no expert on this, but doesnt the carrier decide if its locked or not?
I've seen people solve it by flashing different and unbranded firmware, but not for this particular phone tho, but I dont think it's officially possible.
Click to expand...
Click to collapse
At this point he could at least try, he's got nothing to lose. I have never had this problem, because I buy my phones unlocked no carrier involved, so these are only suggestions.
KbaB.BroS said:
At this point he could at least try, he's got nothing to lose. I have never had this problem, because I buy my phones unlocked no carrier involved, so these are only suggestions.
Click to expand...
Click to collapse
Yeah, what I would try is first just try to do a full restore of your phone via PC Companion, and if that doesnt work then id try downloading an unbranded firmware from XperiFirm (If I am not mistaken, those named CUSTOM or something are unbranded) and then flash that via flashtool and see if that works, if not then your last hope is to get it replaced by warranty, which I'd say is fraud if the device isnt actually malfunctioning.
xirt0n said:
Yeah, what I would try is first just try to do a full restore of your phone via PC Companion, and if that doesnt work then id try downloading an unbranded firmware from XperiFirm (If I am not mistaken, those named CUSTOM or something are unbranded) and then flash that via flashtool and see if that works, if not then your last hope is to get it replaced by warranty, which I'd say is fraud if the device isnt actually malfunctioning.
Click to expand...
Click to collapse
I don't think PC Companion works at all, because the only thing it does is downloading identical firmware like the one on the phone. So Flashtool only choice.
I replaced mine with one from flashtool that has a lot less bloatware it originally came with.
KbaB.BroS said:
I don't think PC Companion works at all, because the only thing it does is downloading identical firmware like the one on the phone. So Flashtool only choice.
I replaced mine with one from flashtool that has a lot less bloatware it originally came with.
Click to expand...
Click to collapse
Ok, I never personally used PC companion so I didnt know what it does, I just saw people suggest it around
A step in the root method is to download a rooter .img, then boot to download mode and enter a few commands, but it 'FAIL's everytime I try to check the id. I have the port right, I have all the drivers, etc, but it keeps failing no matter how many times I do it.
Anyone got any help at all? Having Marshmallow won't affect it, right
potential solution
nerdsabs.blogspot.com/2016/08/root-t-mobile-lg-g4-h811-guide-on-ubuntu.html
I found fastboot can boot into twrp and then root from there
magicwindow said:
A step in the root method is to download a rooter .img, then boot to download mode and enter a few commands, but it 'FAIL's everytime I try to check the id. I have the port right, I have all the drivers, etc, but it keeps failing no matter how many times I do it.
Anyone got any help at all? Having Marshmallow won't affect it, right
Click to expand...
Click to collapse
if you are tring to root phone that has bootloader locked . by flashing rootedsystem.img... then yes it doesnt work on MM you must be on Lp .. it only works onlollipop... and you need to know if you can downgrade first. cause on mine tmobile thers antiroll back V2 and V3 so V2 LP10n and MM20i the same but new 20oMM if i upgrade and then i want to downgrade ill brick phone.. so ask first what antirollback version you are on.. and if you could downgrade
Hello,
I bought a Fire HD 8 (2018) from ebay, but it gives me some headaches. There is almost nothing on it, no playstore (neither amazon nor google), no browser, only six basic apps like a calculator. And there is something called WebView Browser Tester. When I enter Recovery and do a factory reset it reverts to this exact stage. I was able to use adb to install VLC Player but it acts a little strange. But when I install Google Playstore (+ Framework, Account Manager, Services) it will crash. Rebooting after that will end in a bootloop, that can only be broken by several attempts trying to get into recovery and do a reset.
So, I think this device once belonged to a developer. It also identifies itself as "kayak" in recovery menu. So I assumed it was unlocked at some point. But when I try to use fastboot to flash it, it states "locked hw". ADB sideload is not available.
I don't know what to do right now. I spend last night doing research without much success. Pretty much all Unlock-Tutorials assume that you are on stock firmware, and the ones for getting back to stock assume you have twrp installed which is also not the case here.
Hope somebody can help me getting this thing working again.
Thanks in advance,
Scoop
Can you unlock the BL
Well, I'm not quite sure how to do that. I only started to dive into the topic by yesterday. Do I have to setup a linux system to do that or is there another way?
Bro…. What are you trying to do if you did not unlock the BootLoader. Just follow a normal guide. Google.
Google brought me here ^^ I wanted to aks if there is en easier way to unlock it then opening it up and setting up a linux boot drive, given that the device has clearly been tinkered with before. I thought, it might be a "known" custom rom that has been to it flashed before. Just trying not to brick it...
But thanks for your answer.
I meant using fast boot….
Now you got me confused. I'm really sorry, but could you be a bit more specific? When I try to use the unlock command I'm always getting the error "the command you input is restricted on locked hw".
scoop111 said:
Now you got me confused. I'm really sorry, but could you be a bit more specific? When I try to use the unlock command I'm always getting the error "the command you input is restricted on locked hw".
Click to expand...
Click to collapse
do these (not at the same time, wait to boot into bootloader then do second and third cmd)
Code:
adb reboot bootloader
fastboot flashing unlock
fastboot reboot
That's exactly what I did. I also tried fastboot oem unlock instead of fast flashing unlock. But I'm always getting the same error "command restricted on locked hw".
I read on some site that "OEM unlock" must be enabled in developer options to have this working, but there is no such option.
ohhhhhh. Then your device is not unlockable.
I managed to unlock it via the hardware mod, but I'm stuck after that. It won't boot into recovery. Is there a way to flash the firmware just with fastboot access?
scoop111 said:
I managed to unlock it via the hardware mod, but I'm stuck after that. It won't boot into recovery. Is there a way to flash the firmware just with fastboot access?
Click to expand...
Click to collapse
If you did the hardware unlock all the way through, you should have TWRP recovery. From that you can flash anything.
scoop111 said:
I managed to unlock it via the hardware mod, but I'm stuck after that. It won't boot into recovery. Is there a way to flash the firmware just with fastboot access?
Click to expand...
Click to collapse
Can you message me in Telegram?
Have you had any success?
I have the exact same issue, and this is pretty much the only topic that shows up when searching "Kayak".
Fire Toolbox v30.3 doesn't like it either
'Codename "kayak" isn't supported/recognized by the Toolbox. Please plug in a supported Fire tablet and try again.'
What model is on the back there are hardware revisions of the 8 2018 L5S83A: Normal OG revision K29A5E: Pre production model for patching CLK Exploit