Related
I need help, I got the Nexus (sprint) and have tried and tried to unlock. I had fits, read many forums, and was directoed to an unlocker forum. I used Superboot GR140. I had downloaded su 2.3.6.1 to my phone.
Using this method, it unlocked but now I am stuck. I cannot get anything else to load.
I'm not sure if I used an incorrect Superboot method (meaning for a different phone since the forums aren't split).
I have access to Fastboot Mode Screen, phone is recognized, but when using cmd, it shows C:\Superboot. I do not know what else to do to direct it to files I have on my computer or how to download these, 2.3.4 back to my phone. I'm stuck and really need help.
I will gladly push the Thanks button for any help I can get to get me up and
running again.
Thanks
Go look in the developer section, one of the stickies, the one that talks about the nexus s 4g cdma. You might have flashed something that was meant for the gsm nexus s. It has links to correct files and guides for the sprint version of the nexus.
Pm me and I will help u over the I'm client of your choice.
Basically, I have no service, and no card, so since I can access Fastboot Mode, and unlocked, is there a way to push a rom direct onto Sprint phone.
I looked in Developers Forums, I am not ready to jump in with custom rom yet (I have used extensively on other phones) but would like to start with stock, go with root and programs as needed.
So how would I push to phone via computer? and what programs, again, no idea of commands to use.
Have you flashed CWM yet? You can use that to reflash the stock ROM. Worst case you can use this thread:
http://forum.xda-developers.com/showthread.php?t=1072698
That will bring you to 100% out of the box factory settings
If you can get into fastboot, then you didn't brick it. You'll be fine, you just need to get in touch with someone that can walk you through the process of fixing it. Or search around, read, and take your time to figure out what to do.
It's not hard. The worse thing you can do is panic or rush to fix it.
Basically what you did when using superboot was you actually installed a boot.img file not meant for your device on your phone. What you should do is, go through the guide for your specific phone...you will have to install a recovery image and then install a custom rom or stock rom.
I do not know if you know your way around with fastboot....basically you could also ask a dev to send you the original boot.img and flash it using fastboot but the first stepi described is easier.
Sent from my Nexus S using Tapatalk
nmoreman said:
I need help, I got the Nexus (sprint) and have tried and tried to unlock. I had fits, read many forums, and was directoed to an unlocker forum. I used Superboot GR140. I had downloaded su 2.3.6.1 to my phone.
Using this method, it unlocked but now I am stuck. I cannot get anything else to load.
I'm not sure if I used an incorrect Superboot method (meaning for a different phone since the forums aren't split).
I have access to Fastboot Mode Screen, phone is recognized, but when using cmd, it shows C:\Superboot. I do not know what else to do to direct it to files I have on my computer or how to download these, 2.3.4 back to my phone. I'm stuck and really need help.
I will gladly push the Thanks button for any help I can get to get me up and
running again.
Thanks
Click to expand...
Click to collapse
If you are going to waste your brand new phone by being stupid how about giving it to me instead! Ill take good care of it.
Sent from my PC36100 using XDA App
Here Try this and let me know if it work:
1.Download this platform-tools.zip and extract it to your desktop
2.Connect your phone to the PC and enter bootloader mode
3.Press and hold Shift while right-clicking the folder you extracted 'platform-tools'
4.Click 'Open command window here' from the pop-up menu. cmd.exe window will open.
5.If the Bootloader is Unlocked continue to the next step. Type in the cmd.exe window 'Fastboot oem unlock' and follow the steps on the phone screen.
6.Type in the cmd.exe window 'fastboot flash boot boot.img'.
7.Type in the cmd.exe window 'fastboot reboot'.
nmoreman said:
I need help, I got the Nexus (sprint) and have tried and tried to unlock. I had fits, read many forums, and was directoed to an unlocker forum. I used Superboot GR140. I had downloaded su 2.3.6.1 to my phone.
Using this method, it unlocked but now I am stuck. I cannot get anything else to load.
I'm not sure if I used an incorrect Superboot method (meaning for a different phone since the forums aren't split).
I have access to Fastboot Mode Screen, phone is recognized, but when using cmd, it shows C:\Superboot. I do not know what else to do to direct it to files I have on my computer or how to download these, 2.3.4 back to my phone. I'm stuck and really need help.
I will gladly push the Thanks button for any help I can get to get me up and
running again.
Thanks
Click to expand...
Click to collapse
THANK YOU, for answer, but it didn't work.
I downloaded, opened, opened cmd from there.
My phone is unlocked, setting there with unlock screen, put it in bootloader mode, but when I type in instructions, it comes back "not recognized as internal, external command, program, batch file"
This is the problem I had when trying to unlock, so reading, used Superboot, probably wrong phone, so now it is wiped and empty.
I also read another thread suggesting Odin in this situation. Have downloaded that, SamsungSimpleDL, followed those directions, that doesn't work either. I have hacked and rommed Epic, very familiar with that, if it works, but cannot point to proper files (pda, pit, or bootloader).
So any other ideas, I am very good at directions, that is how I learned
My Phone is Fixed - YEAH
This did not work, but this link did
http://forum.xda-developers.com/showthread.php?t=1072698&page=4
Basically used Odin (my old backup from Samsung Epic) and it worked when all these suggestions wouldn't.
I couldn't unlock easily, like all of these, therefore used Superboot. Would recommend no one touches that!!
I couldn't run any of the commands before this, and still couldn't use these.
So the instructions to dig thru the Developers section is correct, but so hard with so many customs, phones, carriers, to choose from. Makes it difficult
So use this link if stuck like me, I am just glad I con't have a brick, and I'm still pushing the Thanks button for all who helped, that's what will make this fun.
I flashed the Eclipse ROM via safestrap and then restored the Eclipse ROM onto the stock ROM slot. For some stupid reason, instead of restoring the stock ROM slot before resetting the phone back to stock, I opted to use RSD Lite 6.1.4 and tried to flash the JB firmware (yes, I got into fastboot). When I tried to do this, the phone reboots past the Motorola M insignia, to the droid startup screen (with the flashing red light/circle), but does not get past the startup screen (yes, I gave it 30+ minutes to no avail). I also tried to reflash the JB firmware, but no matter what, I ended up stuck at the bootup screen.
For this reason, I tried to flash the ICS firmware instead (per instructions on XDA and other websites, I removed the lines in the XML file that had the word var, getvar, and oem). This did work! However, after RSD flashed the firmware, rather than restarting into the OS, the phone reboots into a black screen w/ the phrase "Fastboot Reason: Sticky bit factory_fastboot" at the very bottom. Anytime I try to restart the phone, it automatically boots into this screen. If I hold the volume up and down buttons, together w/ the power button, I am able to get back to the option to start normally.
When I tried to do the OTA JB update, the phone downloads the necessary files, but when the phone tries to reboot to install the OS update, it goes back into that black screen and does not install the update. Also, when I finally do get back into the OS, the phone then constantly reboots as if it were trying to install the OTA JB update.
Does anyone know what "Fastboot Reason: Sticky bit factory_fastboot" means? Also, if anyone knows how to "fix" this issue, I'd greatly appreciate it. If the fix requires command line work (like in this thread), I'd greatly appreciate if someone could walk me through it step-by-step, as I am not familiar w/ the command line process.
Thanks!
Edit 1: The next step I will try is to get root back on my phone, install Safestrap, and see whether I can flash a backup that I previously had.
Edit 2: In some threads for other Moto phones, there is some discussion regarding using ADB to fastboot/flash the stock ROM. Anyone know how this is different from using RSD? Also, can anyone walk me through HOW to ADB? I have zero knowledge in this regard.
Have you tried holding the buttons down to enter fast boot again and reflash? Worth a shot if you haven't. You could also attempt a factory reset from the boot menu. Maybe the corrupt file would correct itself.
You should definitely take the time to learn some ADB; at least a working understanding. It helps down the road.
Here's a good tutorial on ADB commands. http://mobile.tutsplus.com/tutorials/android/android-adb-quick-guide/
And to install ADB without Android SDK (app production software) http://mobilecon.info/install-adb-in-windows.html
Sent from my Nexus 7 using xda app-developers app
skippid said:
Have you tried holding the buttons down to enter fast boot again and reflash? Worth a shot if you haven't. You could also attempt a factory reset from the boot menu. Maybe the corrupt file would correct itself.
You should definitely take the time to learn some ADB; at least a working understanding. It helps down the road.
Here's a good tutorial on ADB commands. http://mobile.tutsplus.com/tutorials/android/android-adb-quick-guide/
And to install ADB without Android SDK (app production software) http://mobilecon.info/install-adb-in-windows.html
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Yes, I attempted to reflash on multiple occasions, both using the stock ICS and the stock JB roms. I must have reflashed close to 10x at this point. In any case, no matter how often I have reflahsed (including after doing a factory reset from within the OS as well as from within recovery), I still get the error. The good news is that I was successfully able to flash the JB ROM and have the phone OS actually start up, whereas, a few days ago, it would be stuck at the red circle/eye thing.
Furthermore, I attempted the command fastboot flash system [system.img], and I got the error:
(bootloader) Variable not supported!
target reported max download size of 31457280 bytes
error: cannot load '[system.img]': no error
I saved the system.img in both c:\android, as well as the internal SD card of the phone.
The other good news is that I am still able to use the phone if I get into the boot menu and ask the phone to boot normally. However, I am now unable to get root, and anytime I need to restart the phone, it gives me that error message.
I have also tried the command fastboot reboot bootloader but continue to get the same error message.
OK. Find a JB leak zip or current stock JB zip, access the screen where it asks for AP Fast boot and recovery, choose recovery, then volume up I believe when the phone shows the android with the red exclamation point.. Then choose update with zip. Search your SD card and install. It's worth a try in this manner in case you haven't already.
That's odd that your phone didn't respond well with RSD.
Sent from my XT907 using xda app-developers app
You need to use an updated fastboot binary for the new larger images in these devices.
http://db.tt/AveMC40y
skippid said:
OK. Find a JB leak zip or current stock JB zip, access the screen where it asks for AP Fast boot and recovery, choose recovery, then volume up I believe when the phone shows the android with the red exclamation point.. Then choose update with zip. Search your SD card and install. It's worth a try in this manner in case you haven't already.
That's odd that your phone didn't respond well with RSD.
Sent from my XT907 using xda app-developers app
Click to expand...
Click to collapse
Skippid, thanks for the suggestions. I tried your method as well. Went into recovery, selected to update from external SD (or something to that effect), selected the JB zip file, and let it flash that way. Unfortunately, I still received the same error message regarding the sticky bit factory_fastboot.
cellzealot said:
You need to use an updated fastboot binary for the new larger images in these devices.
http://db.tt/AveMC40y
Click to expand...
Click to collapse
cellzealot, thank you for the link. I've downloaded the file that you linked to. Could you be so kind as to now give me a step-by-step on how to re-attempt the flashing process?
Quick update - I was able to get root back, installed safestrap, and flashed the nandroid that I had made back when I first flashed Eclipse. However, I am still having the same issue:
Whenever I restart the phone, I get the sticky bit factory_fastboot error. If I use the command fastboot continue, the phone boots up as normal; however, it would be great to not have to do this each and every time I reboot the phone. Any help would be greatly appreciated. Thanks!
More updates (still not fixed):
After getting root, I reflashed my nandroid, factory reset (both within the OS and in recovery), and then tried flashing both the ICS and JB stock ROMs. I tried flashing both using mfastboot, as well RSD Lite. The files flash successfully; however, whenever I restart the phone, I continue to get the stick bit factory_fastboot error.
Also, when I get into recovery, I try to flash via "update from external SD". When I do so, recovery simply restarts without flashing the stock ROM.
Here's my last update as to this issue:
After trying all of the methods that I could think of (RSD Lite, flashing via fastboot and mfastboot, flashing from external), the problem did not correct itself.
I brought my phone into a Verizon store, where they told me that they had never seen that problem before. They agreed to replace my phone pursuant to the one-year warranty (I received my phone in December), which I received today. I've again rooted my phone, but have opted to not screw around w/ safestrap and custom ROMs this time around, as I find the stock JB experience to actually be quite good.
Found the soultion!!!!!!
Ok guys so after serching a while I found out similar moto phones have the same issue. I found in a latin forum and in a Droid forum people ponting to the same issue. So the solution that worked for my Razr HD xt925 was:
1) Enter fastboot mode in your phone (very easy since every time you restart the phone you end there anyways)
2) Write this command on the computer: fastboot oem fb_mode_clear
there will be a dialogue with the time take and OK
You are done!
Thought someone might find it useful
Thank you!
cerafio said:
Ok guys so after serching a while I found out similar moto phones have the same issue. I found in a latin forum and in a Droid forum people ponting to the same issue. So the solution that worked for my Razr HD xt925 was:
1) Enter fastboot mode in your phone (very easy since every time you restart the phone you end there anyways)
2) Write this command on the computer: fastboot oem fb_mode_clear
there will be a dialogue with the time take and OK
You are done!
Thought someone might find it useful
Click to expand...
Click to collapse
Thank you! This was the answer I needed after searching and searching trying all the different things for over 3 hours, this 2 second fix worked!
Namanati said:
Thank you! This was the answer I needed after searching and searching trying all the different things for over 3 hours, this 2 second fix worked!
Click to expand...
Click to collapse
#8 > http://forum.xda-developers.com/droid-razr-m/general/guide-faq-how-to-root-boot-unlock-t2869432
ATTACK said:
#8 > http://forum.xda-developers.com/droid-razr-m/general/guide-faq-how-to-root-boot-unlock-t2869432
Click to expand...
Click to collapse
Thanks, but that didn't come up when I googled AP Fastboot: flash failed, and since I didn't get it from rooting or unlocking my phone I didn't think to look for that.
cerafio said:
Ok guys so after serching a while I found out similar moto phones have the same issue. I found in a latin forum and in a Droid forum people ponting to the same issue. So the solution that worked for my Razr HD xt925 was:
1) Enter fastboot mode in your phone (very easy since every time you restart the phone you end there anyways)
2) Write this command on the computer: fastboot oem fb_mode_clear
there will be a dialogue with the time take and OK
You are done!
Thought someone might find it useful
Click to expand...
Click to collapse
Oh my god dude thank you so much. That fixed my bootloader issue that was plaguing me for weeks
Thanks again!!!
cerafio said:
Ok guys so after serching a while I found out similar moto phones have the same issue. I found in a latin forum and in a Droid forum people ponting to the same issue. So the solution that worked for my Razr HD xt925 was:
1) Enter fastboot mode in your phone (very easy since every time you restart the phone you end there anyways)
2) Write this command on the computer: fastboot oem fb_mode_clear
there will be a dialogue with the time take and OK
You are done!
Thought someone might find it useful
Click to expand...
Click to collapse
Thanks Man You really saved my razr.:good:
Edit : Sorry I asked stupid question!
Pierro29 said:
Edit : Sorry I asked stupid question!
Click to expand...
Click to collapse
there are no stupid questions if you question its because you dont know something and would like to fulfill the empty space where a reasonable answer could go. and s thanks for the solution to this error.
Okay, I have a "stupid"/newbie question. I flashed an image and I am getting the sticky boot thing. How to a get to a window to type the lines in?
Thanks!
cerafio said:
Ok guys so after serching a while I found out similar moto phones have the same issue. I found in a latin forum and in a Droid forum people ponting to the same issue. So the solution that worked for my Razr HD xt925 was:
1) Enter fastboot mode in your phone (very easy since every time you restart the phone you end there anyways)
2) Write this command on the computer: fastboot oem fb_mode_clear
there will be a dialogue with the time take and OK
You are done!
Thought someone might find it useful
Click to expand...
Click to collapse
Hey dude ! You save my life
Awesome trick
So i decided a few days ago to try and flash a factory image for kitkat on my N7. But i downloaded the image for the wrong device. the script has wiped recovery and system etc. The N7 now just boots to bootloader.
i got the proper factory image to flash, but i cannot get the device recognized on the pc running Windows 7 now. its showing as Other Devices / Android. I did install the drivers from the SDK and it now appears as Android ADB Interface. However ADB is still not recognizing it. I have done adb devices but nothing is found.
Any help, it is fixable isnt it??
You can't use adb commands in fastboot. You should use fastboot commands and flash the factory image
Sent from my Nexus 5
Tones1971 said:
So i decided a few days ago to try and flash a factory image for kitkat on my N7. But i downloaded the image for the wrong device. the script has wiped recovery and system etc. The N7 now just boots to bootloader.
i got the proper factory image to flash, but i cannot get the device recognized on the pc running Windows 7 now. its showing as Other Devices / Android. I did install the drivers from the SDK and it now appears as Android ADB Interface. However ADB is still not recognizing it. I have done adb devices but nothing is found.
Any help, it is fixable isnt it??
Click to expand...
Click to collapse
Well, I had a serious issue with something similar, after trying to update (not flash the factory image) to KitKat it produced an error and now it's bootlooping and, worse, my computer won't recognize the device, so I can't flash the factory image whatsoever. Your problem is much more light, as your computer is actually recognizing the device. What I'd suggest is using the Nexus Root Toolkit by WugFresh. Yes, I know, a lot of people here don't like using it but it's extremely useful when you have drivers issues.
It's actually a pretty straight forward procedure, you install the toolkit and it will ask you for your device model, android version, etc., then take you through the process of updates and stuff. Then, on the main window, you have this wizard "Full Driver Installation Guide" that will give you 4 ways to get your device working. You can find the Toolkit here: http://www.wugfresh.com/nrt/. Good luck!
I vote we ban all talk of toolkits. 99.9% of the help threads around here start with, "I was using/used x toolkit and now my device won't boot."
What happened to people learning about their devices?
How about learning how to fix your problems, rather than compound them by not understanding what you are doing? How about if you don't have the capacity to learn it, you leave it the F alone?
Sent from my Nexus 5
Pirateghost said:
I vote we ban all talk of toolkits. 99.9% of the help threads around here start with, "I was using/used x toolkit and now my device won't boot."
What happened to people learning about their devices?
How about learning how to fix your problems, rather than compound them by not understanding what you are doing? How about if you don't have the capacity to learn it, you leave it the F alone?
Sent from my Nexus 5
Click to expand...
Click to collapse
It's also difficult when trying to assist somebody... they're using the vocabulary of toolkits (which I'm not familiar with)... and I'm going on about fastboot... which they don't understand. It's like there are now two different languages... TOOLKIT and FASTBOOT.
Makes it very difficult to assist people.
Maybe I should have a tinker with Wugfresh... if for no other reason than to at least get an insight into how these things work.
Rgrds,
Ged.
The concept of the toolkit is great. It's the implementation and use of it that is horrible.
I think a toolkit should walk you through the actual steps and force you to type in the commands. You select an option of what you want it to do, it tells you what to type step by step to achieve said goal, and checks that you don't type in the wrong thing for the option you selected.
Unfortunately I don't think there is a market for that when you can get everything 'one clicked' for you.
Sent from my Nexus 5
Pirateghost said:
The concept of the toolkit is great. It's the implementation and use of it that is horrible.
I think a toolkit should walk you through the actual steps and force you to type in the commands. You select an option of what you want it to do, it tells you what to type step by step to achieve said goal, and checks that you don't type in the wrong thing for the option you selected.
Unfortunately I don't think there is a market for that when you can get everything 'one clicked' for you.
Sent from my Nexus 5
Click to expand...
Click to collapse
So an edit box where you could be prompted to type in things like fastboot flash recovery recovery.img... interesting idea... sort of walks you through the process, but doesn't obsessively hold your hand, where you don't learn anything.
I suspect most people just have problems with drivers, because, let's face it, fastboot and ADB aren't exactly difficult to use... unless people have difficulty understanding command lines in these GUI driven days, where everything is a simple menu or button click away... kind of sad really.
Rgrds,
Ged.
GedBlake said:
So an edit box where you could be prompted to type in things like fastboot flash recovery recovery.img... interesting idea... sort of walks you through the process, but doesn't obsessively hold your hand, where you don't learn anything.
I suspect most people just have problems with drivers, because, let's face it, fastboot and ADB aren't exactly difficult to use... unless people have difficulty understanding command lines in these GUI driven days, where everything is a simple menu or button click away... kind of sad really.
Rgrds,
Ged.
Click to expand...
Click to collapse
Basically yeah.
I have a feeling a good portion of the hesitation comes from the command line being scary to most people.
Sent from my Nexus 5
In the tgz file you download there is a 'flash-all.bat' file that does everything for you. If you open it in notepad, you see exactly what it does and in what order.
Yes, drivers are probably the issue, they were for me at least. I ended up using NRT (wugs toolkit) to install drivers (and root later, but that's a new topic)
Code:
PATH=%PATH%;"%SYSTEMROOT%\System32"
fastboot oem unlock
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot erase userdata
fastboot flash bootloader bootloader-grouper-4.23.img
fastboot reboot-bootloader
ping -n 10 127.0.0.1 >nul
fastboot -w update image-nakasi-jwr66y.zip
echo Press any key to exit...
pause >nul
exit
This is a Google way to flash the factory image.
---------- Post added at 10:02 PM ---------- Previous post was at 09:59 PM ----------
Pirateghost said:
The concept of the toolkit is great. It's the implementation and use of it that is horrible.
I think a toolkit should walk you through the actual steps and force you to type in the commands. You select an option of what you want it to do, it tells you what to type step by step to achieve said goal, and checks that you don't type in the wrong thing for the option you selected.
Unfortunately I don't think there is a market for that when you can get everything 'one clicked' for you.
Sent from my Nexus 5
Click to expand...
Click to collapse
The idea is great, try writing it
I'm sure it'll be greeted with appreciation.
Tones1971 said:
So i decided a few days ago to try and flash a factory image for kitkat on my N7. But i downloaded the image for the wrong device. the script has wiped recovery and system etc. The N7 now just boots to bootloader.
i got the proper factory image to flash, but i cannot get the device recognized on the pc running Windows 7 now. its showing as Other Devices / Android. I did install the drivers from the SDK and it now appears as Android ADB Interface. However ADB is still not recognizing it. I have done adb devices but nothing is found.
Any help, it is fixable isnt it??
Click to expand...
Click to collapse
As long as you can still boot into bootloader mode, it is still fixable. Try reinstalling fastboot drivers.
Pirateghost said:
I vote we ban all talk of toolkits. 99.9% of the help threads around here start with, "I was using/used x toolkit and now my device won't boot."
What happened to people learning about their devices?
How about learning how to fix your problems, rather than compound them by not understanding what you are doing? How about if you don't have the capacity to learn it, you leave it the F alone?
Sent from my Nexus 5
Click to expand...
Click to collapse
Yeah, because that was really helpful to him. I didn't tell him to use the toolkit to flash, root, unlock, or anything of the sort. For drivers issues, I do recommend (and will continue to do so) using the toolkit when official drivers don't work, because it has helped me a lot in the past, but I haven't used it to flash anything.
Download the image for your device and extract it into a folder
Download the zip below and move the files into the folder you created above
http://forum.xda-developers.com/showthread.php?t=1484407
Switch device off. Hold volume down and turn it back on, so it's in fastboot mode
Plug device into computer
Run "flash-all.bat" in the system image folder you extracted first
Want to thank everybody for their replies. Have had a family emergency so havent had a chance to try any suggestions, but didnt want to just ignore the thread i started.
Hello,
Problem:
factory reset my Droid RAZR M with the hope to resolve in-call audio problems (very low ear piece volume at full). When I rebooted the phone the Welcome screen appeared asking for a language choice. Chose english US. The Message: "Please wait, This may take a few minutes" appeared with a spinning icon. But nothing else ever happens. The phone never moves beyond this selection.
I have android-sdk (Linux setup) installed on my computer in order to use the suite of tools like fastboot and adb. The tools work, in that I can see the phone, pull data, upload to the phone and even get a command shell on the phone. However in order for adb to recognize the phone I have to put the phone in "BT Tools" mode. In "AP fastboot" mode fastboot sees the phone. As far as I remember USB debugging was turned on.
I do not have a recovery image installed.
The phone has Kitkat 4.4.2 ver 183.46.10 and is rooted with TowelRoot. I just unlocked the bootloader today via motoapocalypse package. Status of the phone is unlocked Code 3
I also removed some unused apps - like NFL and a few other space and bandwidth consuming apps that I will never use.
I'd like to get this phone to work again. Is there any hope?
Please advise and thanks for reading.
You can flash custom recovery via fastboot and then custom ROM or flash stock ROM via RSD. Guide is in first thread in general section.
http://forum.xda-developers.com/showthread.php?t=2869432
[GUIDE][FAQ][DIY][KK] How to Root, Boot Unlock & More
Thanks for the pointer. I gather that RSD is a Windows based app. At the present time I do not have a Windows computer. So I took a shot at the job using fastboot, adb and all as found in the android-sdk. Did the steps as described in the flashing post. Now all I ever see is the "Bootloader unlocked warning message" and the phone never progresses beyond the warning. I disassembled the phone, to disconnect the battery -- hoping for a reset miracle. No change after reassembly. Given the latest state of the phone as described above, is there any chance of reviving this phone now that it's stuck at the bootloader warning?
(I read a post about a Motorola Factory Cable -- and if I understand the factory cable puts the phone in a special mode for flashing looking into this option).
I am out to learn and am not afraid of poking around -- so at this point I have no more to lose.
Would the Windows computer make the difference? Using linux mint atm.
Klen2 said:
You can flash custom recovery via fastboot and then custom ROM or flash stock ROM via RSD. Guide is in first thread in general section.
http://forum.xda-developers.com/showthread.php?t=2869432
[GUIDE][FAQ][DIY][KK] How to Root, Boot Unlock & More
Click to expand...
Click to collapse
diordnAMRZAR said:
Thanks for the pointer. I gather that RSD is a Windows based app. At the present time I do not have a Windows computer. So I took a shot at the job using fastboot, adb and all as found in the android-sdk. Did the steps as described in the flashing post. Now all I ever see is the "Bootloader unlocked warning message" and the phone never progresses beyond the warning. I disassembled the phone, to disconnect the battery -- hoping for a reset miracle. No change after reassembly. Given the latest state of the phone as described above, is there any chance of reviving this phone now that it's stuck at the bootloader warning?
(I read a post about a Motorola Factory Cable -- and if I understand the factory cable puts the phone in a special mode for flashing looking into this option).
I am out to learn and am not afraid of poking around -- so at this point I have no more to lose.
Would the Windows computer make the difference? Using linux mint atm.
Click to expand...
Click to collapse
You can try using SBF_FLASH or mFastboot-v2 (which has a linux version) to flash the system.img .
SOLVED: [Q] Droid Razr M not fully booting: Help Please
That worked. Thanks! So the difference between the SDK fastboot and the one in the link provided (mfastboot-V2): the linux-fastboot seems to be smarter about uploading the larger image files to the flashable device (guessing). I am sure I did "flashboot flash system system.img" with the flashboot util from the SDK.
@ATTACK do you have the source for that version of fastboot or patches? Would like to have a look.
Thanks again! Got an unlocked rooted working Droid RAZR M!
diordnAMRZAR said:
That worked. Thanks! So the difference between the SDK fastboot and the one in the link provided (mfastboot-V2): the linux-fastboot seems to be smarter about uploading the larger image files to the flashable device (guessing). I am sure I did "flashboot flash system system.img" with the flashboot util from the SDK.
@ATTACK do you have the source for that version of fastboot or patches? Would like to have a look.
Thanks again! Got an unlocked rooted working Droid RAZR M!
Click to expand...
Click to collapse
Your guess is correct, mfastboot allows you to flash larger system.img's that wont otherwise flash in fastboot.
As for sources... I have no idea who created mfastboot or where it came from. It's just one of those things that get's passed around the internet.
ATTACK said:
Your guess is correct, mfastboot allows you to flash larger system.img's that wont otherwise flash in fastboot.
As for sources... I have no idea who created mfastboot or where it came from. It's just one of those things that get's passed around the internet.
Click to expand...
Click to collapse
Well I'm happy to have the utility that works. Can thank you enough -- or the creators. Found it also on goggle code after a properly crafted search string. All this for an in-call audio problem that only worsened after I took the phone apart. Still works on speaker mode though so that's good enough -- at low volume. And I learned a few things. One interesting thing: The shell prompt got rewritten to say ${USER}@scorpion_mini/ after flashing the system.img. Pretty sure it only said android prior to re-flashing . And the getprop helper app is a new thing for me.
Feel like a kid all over again exploring this little device.
EDIT: Well after a few hours of bashing around at it I managed to get the bootloader unlocked. However I am having one wicked time trying to get twrp installed as my recovery, and to S-off my device.
When I got to run : fastboot flash recovery twrp.img I get the error "unable to load twrp.img" Now I know darn good and well it is prob some stupid error on my part, but this is driving me batty and help would be greatly appreciated.
Brad
OK..Maybe I'm dumb...but I'd rather post a question than screw around and brick my phone.
Admittedly it has been a couple years since I had an HTC device. (Just got a Bolt today) Been to HTC Dev unlock to try and unlock my bootloader however I am running into an issue when trying to run oem get_identifier_token. Getting 'fastboot' is not recognized as an internal or external command. operable program or batch file.
Been thru this a couple times before on older HTC Devices (last one was an M8-HK Edition) and not had issues.
I installed everything it said to on the HTC site. But I'm stalled out at step 5 on the HTC Dev site. and can't seem to get any further than that. (and yes phone is in DL mode)
Anyone kind enough to help an old dummy out?
PodCulture said:
EDIT: Well after a few hours of bashing around at it I managed to get the bootloader unlocked. However I am having one wicked time trying to get twrp installed as my recovery, and to S-off my device.
When I got to run : fastboot flash recovery twrp.img I get the error "unable to load twrp.img" Now I know darn good and well it is prob some stupid error on my part, but this is driving me batty and help would be greatly appreciated.
Brad
OK..Maybe I'm dumb...but I'd rather post a question than screw around and brick my phone.
Admittedly it has been a couple years since I had an HTC device. (Just got a Bolt today) Been to HTC Dev unlock to try and unlock my bootloader however I am running into an issue when trying to run oem get_identifier_token. Getting 'fastboot' is not recognized as an internal or external command. operable program or batch file.
Been thru this a couple times before on older HTC Devices (last one was an M8-HK Edition) and not had issues.
I installed everything it said to on the HTC site. But I'm stalled out at step 5 on the HTC Dev site. and can't seem to get any further than that. (and yes phone is in DL mode)
Anyone kind enough to help an old dummy out?
Click to expand...
Click to collapse
1. make sure you're in download mode, not bootloader
2. make sure twrp.img is in your sdktools folder
maybe a bad download of twrp?
The saga continues...
Now Im stuck in this weird loop after S-off getting this screen:
It says "your phone is encrypted" enter your lock screen password. I did and it said correct, but your data is corrupted. You must do a factory reset. I try that process, the phone reboots, comes back up to that same "your phone is encrypted"
PodCulture said:
EDIT: Well after a few hours of bashing around at it I managed to get the bootloader unlocked. However I am having one wicked time trying to get twrp installed as my recovery, and to S-off my device.
When I got to run : fastboot flash recovery twrp.img I get the error "unable to load twrp.img" Now I know darn good and well it is prob some stupid error on my part, but this is driving me batty and help would be greatly appreciated.
Brad
OK..Maybe I'm dumb...but I'd rather post a question than screw around and brick my phone.
Admittedly it has been a couple years since I had an HTC device. (Just got a Bolt today) Been to HTC Dev unlock to try and unlock my bootloader however I am running into an issue when trying to run oem get_identifier_token. Getting 'fastboot' is not recognized as an internal or external command. operable program or batch file.
Been thru this a couple times before on older HTC Devices (last one was an M8-HK Edition) and not had issues.
I installed everything it said to on the HTC site. But I'm stalled out at step 5 on the HTC Dev site. and can't seem to get any further than that. (and yes phone is in DL mode)
Anyone kind enough to help an old dummy out?
Click to expand...
Click to collapse
PodCulture said:
Now Im stuck in this weird loop after S-off getting this screen:
It says "your phone is encrypted" enter your lock screen password. I did and it said correct, but your data is corrupted. You must do a factory reset. I try that process, the phone reboots, comes back up to that same "your phone is encrypted"
Click to expand...
Click to collapse
yes, after s-off u have to format data
OMJ said:
yes, after s-off u have to format data
Click to expand...
Click to collapse
I've no problem doing that, but teh phone isn't letting me do it.
PodCulture said:
I've no problem doing that, but teh phone isn't letting me do it.
Click to expand...
Click to collapse
How are you trying to format data?
Sent from my unknown using XDA Labs
Unlocked needs root and twrp
Honestly...I don't know where I screwed up. (in the various how-to's I read I didn't see a format data step) I took the phone to Sprint and they were kind enough to flash it for me...so I am back up and running. Booted into DL mode and verified that I'm still unlocked and S-off. But where to go from here I don't know. I'd love to flash twrp and SU, but paranoid about semi-bricking it again. I used to know how this crap worked but that was quite awhile ago. (a couple phones and a couple versions of Windows ago)
OMJ said:
How are you trying to format data?
Sent from my unknown using XDA Labs
Click to expand...
Click to collapse
PodCulture said:
Honestly...I don't know where I screwed up. (in the various how-to's I read I didn't see a format data step) I took the phone to Sprint and they were kind enough to flash it for me...so I am back up and running. Booted into DL mode and verified that I'm still unlocked and S-off. But where to go from here I don't know. I'd love to flash twrp and SU, but paranoid about semi-bricking it again. I used to know how this crap worked but that was quite awhile ago. (a couple phones and a couple versions of Windows ago)
Click to expand...
Click to collapse
flashing twrp & SU isn't difficult...since you unlocked bootloader, you should already have the fastboot tools needed.
1. download latest twrp (3.1.1-0 as of now) https://dl.twrp.me/pme/twrp-3.1.1-0-pme.img
2. copy that img to your sdktools/fastboot folder
3. reboot into download mode
4. flash twrp: fastboot flash recovery twrp-3.1.1-0-pme.img
5. reboot to bootloader, then reboot to recovery
6. create a backup if u want
7. flash/install SuperSU https://s3-us-west-2.amazonaws.com/supersu/download/zip/SuperSU-v2.82-201705271822.zip
Thanks! Got everything back up and running now. Nice to have a phone I can use the way I want to again. TONS of bloat though.
OMJ said:
flashing twrp & SU isn't difficult...since you unlocked bootloader, you should already have the fastboot tools needed.
1. download latest twrp (3.1.1-0 as of now) https://dl.twrp.me/pme/twrp-3.1.1-0-pme.img
2. copy that img to your sdktools/fastboot folder
3. reboot into download mode
4. flash twrp: fastboot flash recovery twrp-3.1.1-0-pme.img
5. reboot to bootloader, then reboot to recovery
6. create a backup if u want
7. flash/install SuperSU https://s3-us-west-2.amazonaws.com/supersu/download/zip/SuperSU-v2.82-201705271822.zip
Click to expand...
Click to collapse
How did u get s off