Okay, so I had a friend root my phone. He used the one click method to root the phone. I tried to unroot the phone. I tried flashing the 198_7 and everything went smoothly, then RSD lite said to reboot the phone manually. I tried that and now the phone is saying "Failed to boot 4 Starting RDS mode". I tried reflashing it and nothign happens... is there something I am missing? I just need the phone to work again. I tried searching the forum and it was telling me to use 154, but I tried several different downloads and everytime I open them up in RSD it gives me an error. The only working sbf I have is 198_7... any help?
Don't know if this helps.... I found a working 198_6 tried flashing it, and it failed, moved to a different USB port, and RSD ran through the process, and finished, at the end it told me to manually power up the phone, but the phone powered it self up... after it was finished, RSD said finished. But the phone still says Failed to boot 4... ???
lopezj760 said:
Don't know if this helps.... I found a working 198_6 tried flashing it, and it failed, moved to a different USB port, and RSD ran through the process, and finished, at the end it told me to manually power up the phone, but the phone powered it self up... after it was finished, RSD said finished. But the phone still says Failed to boot 4... ???
Click to expand...
Click to collapse
Maybe cause your phone battery is low.
Sent from my MB855 using Tapatalk 2
I have to fully charged batteries...
lopezj760 said:
I have to fully charged batteries...
Click to expand...
Click to collapse
You asking? or you have 2 full batteries?
Sent from my MB855 using Tapatalk 2
What version of rsd you using? You say it let's you flash 198-7 but it gives you error when done flashing and all other builds give an error on rsd before you even get to flash?
Sent from my MB855 using Tapatalk 2
Yes I have 2 fully charged batteries... and I'm using RSD Lite v5.6. and yes when I hit the "..." on the rsd, select the downloaded .zip files of any version build it gives me the following error "unzip fail"
lopezj760 said:
Yes I have 2 fully charged batteries... and I'm using RSD Lite v5.6. and yes when I hit the "..." on the rsd, select the downloaded .zip files of any version build it gives me the following error "unzip fail"
Click to expand...
Click to collapse
Do the files have Example (154.5.zip or .sbf) at the end of them? download 7zip extractor, to extract them any where you want then load the file on rsd. from the location you extracted to.
Sent from my MB855 using Tapatalk 2
Just finished trying to flash a working 154 build. Same thing, RSD gets to the end, says to manually boot phone, boots its self.. RSD says finished but phone still gives me failed to boot 4 error. Have tried to manually boot the phone too.. So far I have found the correct SBFs, narrowed down what USB prt to use, and have 2 fully charged batteries... any other methods to get it work I can try?
what happens when you press pwr+vol dwn?
Sent from my MB855 using Tapatalk 2
Tried all the builds that way also, extracting them with 7zip, and thru RSD.
Nothing happens when I press the power and vol dwn button, it just has the moto logo, and then it goes to fail to boot
lopezj760 said:
Tried all the builds that way also, extracting them with 7zip, and thru RSD.
Click to expand...
Click to collapse
Oh, I wouldn't let rsd extract the files for me (no reason why, just wouldn't )
When your phone was working what build Were you on? was your phone ever unlocked? ( I dnt mean not rooted)
Sent from my MB855 using Tapatalk 2
lopezj760 said:
Nothing happens when I press the power and vol dwn button, it just has the moto logo, and then it goes to fail to boot
Click to expand...
Click to collapse
Pwr+vol up?
Sent from my MB855 using Tapatalk 2
Build was: 4.5A-1_SUN-198_6 and to be honest with you, I'm not sure if it was unlocked or not, my friend that rooted the phone has the same phone and did it the same way, is there a way to check to see if it was unlocked?
Down to one battery, any other options I have here?
You have google talk?
Sent from my MB855 using Tapatalk 2
Sent you a PM...
Good news, with the help from valentinoh got it working again!! These are the steps we took:
1. Unistalled and reinstalled motorola drivers on my PC.
2. Pulled the battery out of the phone, then put it back in, press and hold PWR+Vol UP. This will put it in moto-fastboot mode.
3. On the computer, after reinstalling drivers, and moving the moto-fastboot folder on to the C:\ drive on my computer, started a cmd prompt. In the command prompt typed in "cd c:\" with out the quotations, hit enter, then "cd:\'name of folder containing moto-fastboot'" then hit enter again.
4. Then typed in: "moto-fastboot" and hit enter on the cmd prompt. This should bring up the moto-fastboot menu/commands. So at this point my phone is in fastboot mode, plugged into the computer. I then typed in "moto-fastboot devices" hit enter, my phone appeared below it. This is just to make sure you're connected correctly.
5. After I made sure everything else was going good, I went in and did a "moto-fastboot -w" to clear user data, and cache. I believe this was the problem that was giving me the Failed to boot 4 error!!!! I then typed "moto-fastboot reboot" phone re booted. If you go back to the same boot 4 error, just take the battery out then turn on the phone while holding PWR+VolUP buttons. I did this step three times, re booting after every time.
6. After all this I then rebooted the phone one last time, and let it go directly into RSD mode.
7. I then fired up RSD Lite, clicked the "..." found the correct SBF (I used 198_6) then started the flash. After it was finished, BAM! Phone rebooted, and all was good once again.
A few things to remember, make sure your battery is fully charged, both of mine ended up dying. If RSD fails, try a different USB cable and port. Make sure nothing else is plugged into the computer via USB.
Once again, a HUGE THANK YOU to valentinoh for all the help. If you have any questions, let me know and I will try to help you out as much as possible!
lopezj760 said:
Good news, with the help from valentinoh got it working again!! These are the steps we took:
1. Unistalled and reinstalled motorola drivers on my PC.
2. Pulled the battery out of the phone, then put it back in, press and hold PWR+Vol UP. This will put it in moto-fastboot mode.
3. On the computer, after reinstalling drivers, and moving the moto-fastboot folder on to the C:\ drive on my computer, started a cmd prompt. In the command prompt typed in "cd c:\" with out the quotations, hit enter, then "cd:\'name of folder containing moto-fastboot'" then hit enter again.
4. Then typed in: "moto-fastboot" and hit enter on the cmd prompt. This should bring up the moto-fastboot menu/commands. So at this point my phone is in fastboot mode, plugged into the computer. I then typed in "moto-fastboot devices" hit enter, my phone appeared below it. This is just to make sure you're connected correctly.
5. After I made sure everything else was going good, I went in and did a "moto-fastboot -w" to clear user data, and cache. I believe this was the problem that was giving me the Failed to boot 4 error!!!! I then typed "moto-fastboot reboot" phone re booted. If you go back to the same boot 4 error, just take the battery out then turn on the phone while holding PWR+VolUP buttons. I did this step three times, re booting after every time.
6. After all this I then rebooted the phone one last time, and let it go directly into RSD mode.
7. I then fired up RSD Lite, clicked the "..." found the correct SBF (I used 198_6) then started the flash. After it was finished, BAM! Phone rebooted, and all was good once again.
A few things to remember, make sure your battery is fully charged, both of mine ended up dying. If RSD fails, try a different USB cable and port. Make sure nothing else is plugged into the computer via USB.
Once again, a HUGE THANK YOU to valentinoh for all the help. If you have any questions, let me know and I will try to help you out as much as possible!
Click to expand...
Click to collapse
Awesome dude, glad I helped. All I ask is that you "pay it forward"
Sent from my MB855 using Tapatalk 2
Related
was going from gingerblur 2.5 on 1.56 then sbf to 1.83 and now it just says that after flashing.
tried to sbf 1.23 and 56 and same thing
am i doing something wrong?
in the rsdlite it sees the phone but says n/a for everything
Please HELP
Updated: I tried again fresh start on different computer and it worked!
must have been error in download, unzip, or there is something conflicting on my pc
hi i have same problem , went i flash OLYFR_U4_1.8.3_SIGNED_OLPSATTSPE_P013_HWolympus_1g_Service1FF.sbf ,
always after finish and rebooting then failed to boot 4 error raise,
i have use other computer to flash and the result is same failed to boot 4
i have install
- RSD Lite and 5.0
- Handset_USB_Driver_32_v4.9.0
plz can anyone help me ?
Sbf 4.1.26 or 4.1.57, then OTA to 4.1.83, root, sideload enable, flash CWM, flash GingerBlur.
bullghost said:
hi i have same problem , went i flash OLYFR_U4_1.8.3_SIGNED_OLPSATTSPE_P013_HWolympus_1g_Service1FF.sbf ,
always after finish and rebooting then failed to boot 4 error raise,
i have use other computer to flash and the result is same failed to boot 4
i have install
- RSD Lite and 5.0
- Handset_USB_Driver_32_v4.9.0
plz can anyone help me ?
Click to expand...
Click to collapse
i have the same problem
aaurnab said:
i have the same problem
Click to expand...
Click to collapse
please help
CaelanT said:
Sbf 4.1.26 or 4.1.57, then OTA to 4.1.83, root, sideload enable, flash CWM, flash GingerBlur.
Click to expand...
Click to collapse
thanks bro, i thinks that's the best way to update till 4.1.83,
here a little experience i have done
first time i try flash sbf 4.1.83 failed with that error booting,
and pull battery and back again to turn off the phone, and i flash the 1.26
then success with sim card inside,
iam not happy with failing on flash 4.1.83, then i thought the 4.1.83 sbf file is corrupt then i redownload again , after finish download,
i do the second time flashing with new 4.1.83 sbf
this second time is so frustrated, couz it fail again with same error.
until i have success full recover my atrix i do over 10 time flashing
and changing between computer and my notebook
and changing from windows 7 and windows XP
flashing random sbf from 1.83 and 1.26
the lasting i lost my hope , then suddenly the flash was success, WTF ,
lasting i remember is i pull the battery and pull out the sim card , then put back the battery, and do the flash,
the last time i flash 1.26 sbf
i thing
there is something no right with driver or RSD Lite not sync or missing something
until now iam still don't know how to solve it ,
pls anyone can find out what the problem and how to solve it
After about 4-5 hours and 7-8 tries using sfb method to upgrade to 1.83, I finally have a working phone again.
As to how I got stuck on the:
boot fail 4
starting RSD
and in RSD Lite, the phone's device name showing up as "SE Flash Olympus"
I decided to do a few things.
1. Go download the newest USB drivers. the 2.00.52 is what you should be on. If you can't find them, go to Motorola website and get MotoHelper 5.0 or whatever..install and then update your drivers. Restart your pc and keep trying to update your drivers until you get to USB 2.00.52 drivers.
2. USE THE ORIGINAL DATA CABLE THAT CAME WITH THE PHONE.
3. Make sure the connections are not loose at all (could've been why mine was messing up)
4. If you already have motohelper installed...go to the 'driverinstaller.exe' change operation mode to clean and reinstall, make sure the phone is unplugged. and click on start. (note, this part will be anywhere from 2 - 5 minutes depending on speed of your computer)
5. Restart RSD Lite, make sure you're using the latest one, and 'Run as administrator'.
**Go to config>Flash/Flex options... > only "check" Restart after Flexing..**
6. Now, I learned this the hard way...and many forums have it up there... GET YOUR BATTERY TO ABOVE 80% or IT WILL FAIL. (I had to go to a friend's at midnight to charge my battery from his atrix...hahaha)
7. Now turn your phone on again and it'll go to the "failed to boot 4 starting RSD" ...
8. Next, plug it in to your USB cable and click "Show Device" and then click once under the "USB 1 line" to view the device information at the top left. (Everything should be N/A except for your bootloader and you will also read "NS Flash Olympus now, instead of the SE Flash Olympus)
9. Put that '1.83_pudding.sfb' file in the "C:\ " directory to avoid any further complications.
10. Select the "...." browse to the '1.83_pudding.sfb' file and click start. It should work.... Now if it doesn't work... try and try again...
What I did was switched back and forth from 1.23 to 1.83... when I got mine to work, the device was registering as "SE Flash Olympus".
And for the longest time under bootloader, it would register as N/A...I finally decided to switch cables and it worked... once again, make sure to follow these:
* Full battery/80% above
* Stock Atrix USB cable
* 2.00.52 USB drivers
* RSD Lite 5.3.1
EDIT: GOOD LUCK! PM me if you need more assistance as those forward to XDA app
vash8806 said:
After about 4-5 hours and 7-8 tries using sfb method to upgrade to 1.83, I finally have a working phone again.
As to how I got stuck on the:
boot fail 4
starting RSD
and in RSD Lite, the phone's device name showing up as "SE Flash Olympus"
I decided to do a few things.
1. Go download the newest USB drivers. the 2.00.52 is what you should be on. If you can't find them, go to Motorola website and get MotoHelper 5.0 or whatever..install and then update your drivers. Restart your pc and keep trying to update your drivers until you get to USB 2.00.52 drivers.
2. USE THE ORIGINAL DATA CABLE THAT CAME WITH THE PHONE.
3. Make sure the connections are not loose at all (could've been why mine was messing up)
4. If you already have motohelper installed...go to the 'driverinstaller.exe' change operation mode to clean and reinstall, make sure the phone is unplugged. and click on start. (note, this part will be anywhere from 2 - 5 minutes depending on speed of your computer)
5. Restart RSD Lite, make sure you're using the latest one, and 'Run as administrator'.
**Go to config>Flash/Flex options... > only "check" Restart after Flexing..**
6. Now, I learned this the hard way...and many forums have it up there... GET YOUR BATTERY TO ABOVE 80% or IT WILL FAIL. (I had to go to a friend's at midnight to charge my battery from his atrix...hahaha)
7. Now turn your phone on again and it'll go to the "failed to boot 4 starting RSD" ...
8. Next, plug it in to your USB cable and click "Show Device" and then click once under the "USB 1 line" to view the device information at the top left. (Everything should be N/A except for your bootloader and you will also read "NS Flash Olympus now, instead of the SE Flash Olympus)
9. Put that '1.83_pudding.sfb' file in the "C:\ " directory to avoid any further complications.
10. Select the "...." browse to the '1.83_pudding.sfb' file and click start. It should work.... Now if it doesn't work... try and try again...
What I did was switched back and forth from 1.23 to 1.83... when I got mine to work, the device was registering as "SE Flash Olympus".
And for the longest time under bootloader, it would register as N/A...I finally decided to switch cables and it worked... once again, make sure to follow these:
* Full battery/80% above
* Stock Atrix USB cable
* 2.00.52 USB drivers
* RSD Lite 5.3.1
EDIT: GOOD LUCK! PM me if you need more assistance as those forward to XDA app
Click to expand...
Click to collapse
People 51_OLL iron-4.5.2A-lite 5.6 rsd 49_SIGNED_STABLE45LAOLYMPGBPERAR_P011_A026_M001_HWpd_Service1FF with ... and my error:
"Failde to boot 4"
rsd starting mode
I am reading is the battery problem that has to be for 80 %+...
If I turn on the power but the volume key + I fastboot protocol enters
If it lights only the error:
"Failde to boot 4" starting mode rsd
I can do twice the iron sbf with 2.3.6 official stock continues to give me the same error.
Lei may be because the battery is not 100% so fails.
How do I charge if the wall charger no load and light me alone with the legend:
"Failde to boot 4" rsd starting mode.
It can be for this, because this is not a 100% Bateias??
Another query may be that by command fastboot mode can be fixed??
So I have been trying a bunch of different roms for the RAZR today and I was having problems with the keyboard not working. I decided to try to load CM9, so I read I need to use "safestrap" and not "bootstrap" that I had been using. I downloaded it, installed then tried to boot into recovery and load CM9.
Now the safestrap boot screen appears and says "safe system disabled" "hit search to continue / hit the menu button to boot into recovery" if I hit the menu button it just reboots, if I hit search the screen just goes blank and I have to do a reset to get it to start the process again.
I have RSD but I have never used it before. I have my phone plugged into my computer but my computer doesnt see it.
Help!
dreamsti said:
So I have been trying a bunch of different roms for the RAZR today and I was having problems with the keyboard not working. I decided to try to load CM9, so I read I need to use "safestrap" and not "bootstrap" that I had been using. I downloaded it, installed then tried to boot into recovery and load CM9.
Now the safestrap boot screen appears and says "safe system disabled" "hit search to continue / hit the menu button to boot into recovery" if I hit the menu button it just reboots, if I hit search the screen just goes blank and I have to do a reset to get it to start the process again.
I have RSD but I have never used it before. I have my phone plugged into my computer but my computer doesnt see it.
Help!
Click to expand...
Click to collapse
Whats your razr. Its verizon? If not you should use bootstrap.
Safestrap is for verizon razr. But some uses bootstrap on it.
You have to put ur razr in ap fastboot mode: power+vol up+vol down in order to flash with rsd lite
Choose a stock rom to your razr and flash it. Make sure flash correct rom
Cheers
Sent from my XT910 using Tapatalk 2
I have the Verizon RAZR.
So my computer does not recognize the phone when in AP Fastboot, but it does recognize it when its in BP SDF flash. What am I doing wrong?
dreamsti said:
I have the Verizon RAZR.
So my computer does not recognize the phone when in AP Fastboot, but it does recognize it when its in BP SDF flash. What am I doing wrong?
Click to expand...
Click to collapse
Uninstall all motorola software, reinstall motocast 1.29 or newer then connect ur razr.
Use rsd lite 5.7 and make sure you got correct sbf file
You may have corrupted drivers.
Cheers
Cheers
Enviado de meu XT910 usando o Tapatalk 2
Do I need to install anything else other than those 2 things? It still doesnt work.
Would having Samsung drivers effect anything? I have a Galaxy Nexus too.
dreamsti said:
Would having Samsung drivers effect anything? I have a Galaxy Nexus too.
Click to expand...
Click to collapse
Sometimes it brokes motorola drivers. Doing what I said should work.
Edit:
BTW what's the version you were and what's the version you're trying to flash?
Some versions cannot downgrade when the one you're trying to flash have a lower security.
I was running Gummy when everything went wrong. Loading safestrap is when I started having the current problems.
I uninstalled the Samsung drivers, and loaded both RSDLite 5.7 and the Moto driver you suggested and RSD will not see my phone in AP Fastboot, but it will when in BP SDF flash. Very confusing.
I will load the latest version of GB when I can get my computer to see my phone in AP Fastboot.
Now my computer is trying to install the flash MZ600 driver and error's out. I googled MZ600 and it says its a Xoom driver???
dreamsti said:
Now my computer is trying to install the flash MZ600 driver and error's out. I googled MZ600 and it says its a Xoom driver???
Click to expand...
Click to collapse
Yup. You've a driver problem, better unistall others devices you may have.
Or, do it in other pc, like a notebook.
So I finally got the drivers working and now RSD see's my phone when in AP Fastboot, but I get an error when flashing the file. This is the error I get.
"Failed flashing process. 22/23 flash "radio.img" -> Phone returned FAIL."
It was flashing for about 5 minutes before I got this error.
Edit: I'm using the file from this thread.
http://rootzwiki.com/topic/13566-droid-razr-fastboot-file/
Blur_Version.6.12.173.XT912.Verizon.en.US
I think the battery went dead, ugh. Ill recharge and report back.
If you are reading this and were having the same situation then time is very important here. First off if you are stuck looping into fastboot and cannot get it to do anything else quickly go throw your Razr onto a wall charger (This will not charge up your phone but it will stave off its death) Reboot until fastboot says battery OK.
Okay relax we have a little bit of time now.
I AM IN NO WAY SHAPE OR FORM RESPONSIBLE IF YOU BRICK YOUR DEVICE
Go download (adb /fastboot files) http://dottech.org/downloads/adb_fastboot_and_other_tools.zip
And Download (Droid Razr Utility) http://www.filefactory.com/file/7ki1gjhtk1jj/n/DroidRAZRUtility1_51_ICS_COMPATIBLE_zip
I DID NOT MAKE EITHER OF THESE TOOLS BUT COMBINED THEY SAVED ME
1: Extract the adb / fastboot files to your desktop
2: Copy the SYSTEM.IMG out of the Razr utility into the folder with your adb / fastboot stuff
3: Hold shift and right click inside the folder with all your adb / fastboot files and select open command prompt here
4: Unplug your Razr and plug your Razr into your computer DO NOT REBOOT IT (Make sure it still says battery OK)
5: Type in the command (Do not type in the brackets) [fastboot flash system system.img]
6: WAIT its going to take a little over a minute to send the file and a little over a minute to write the file
7: Once the system file has been sent over reboot
8: You should see the Droid Razr boot image just give it time to start up
9: CHARGE YOUR PHONE
10: Go back and run Droid Utility and press 1 on its options to properly reimage the device.
I hope this was helpful I havent seen any guides like this before. I was almost to the point of caving in and tearing the Razr open but I really didn't feel comfortable doing that. I was looking everywhere for a guide to trick fastboot or get the Razr to charge in fastboot (No luck) I was in that scary place were I thought I had bricked my first phone ever but I was able to recover from it. If you still have life in your phone this should work. The reason the Droid Razr utility does not work is it reboots the phone and then knows the battery is dying. This guide tricks fastboot into thinking the battery is okay. Once fastboot is tricked you should be able to flash by pushing it yourself.
If your phone dies while doing this you are probably hard bricked now.
-Xaikar
Xaikar, I am in the exact same boat you were, stuck in bootloop after a botched flashing, slow leak of life for 2 days now, had to travel 2 hours to get high speed so i can dl these damn files, I live in boondocks for the moment where service and internet is piss poor. Anyways tried your method with a system.img from the later version of Matt's DroidRAZRUtility1.6_final (shouldn't matter changelog didn't mention anything about changing the file); and it had a INFOPreflash validation failure FAILED <remote: >. So I am running out of ideas & time man, tried everything else. probably have to find a different system.img, which version was your phone, or how would I go about making my own system.img from the fastboot files for my signed GSM-LATAM system?
Try getting a GSM version of a system.img, I was able to do the utility one because I am cdma. Also try flashing the recovery. fastboot flash recovery recovery.img that might help get back a working recovery so you can get some kind of image on there to charge the Razr back up.
HELP!!
Idk if im just THAT computer dumb but i finally downloaded the files after roughly 4 hours and i dont see a "SYSTEM.IMG" file within it. You are literally my only hope cause i've looked everywhere for a solution and this is the only one close to what i need!!!
Did you extract the utility into its own folder? Inside of that folder there should be a System file somewhere you might not see system.img unless you have extensions turned on. You should still see a SYSTEM file name it should be rather large in size. Let me know if that works.
how will I know when the system file will be done sending in order to reboot? it just keeps saying sending system?
Should take a few minutes 5 at the most. It should say something like writing system complete. Let me know if you need more help.
apixelheDrew said:
Xaikar, I am in the exact same boat you were, stuck in bootloop after a botched flashing, slow leak of life for 2 days now, had to travel 2 hours to get high speed so i can dl these damn files, I live in boondocks for the moment where service and internet is piss poor. Anyways tried your method with a system.img from the later version of Matt's DroidRAZRUtility1.6_final (shouldn't matter changelog didn't mention anything about changing the file); and it had a INFOPreflash validation failure FAILED <remote: >. So I am running out of ideas & time man, tried everything else. probably have to find a different system.img, which version was your phone, or how would I go about making my own system.img from the fastboot files for my signed GSM-LATAM system?
Click to expand...
Click to collapse
I ran into a problem using the util today but you can simply unzip another rom and replace the files in the " files " folder to the new rom and then run it again. It will install it via fastboot just like the rom that came with it.
I got the same flash failed message.. have you found any to fix it?? I tried flashing the recovery and I got the same message for that too
Can you be more elaborate on the error mesaage
Sent from my Galaxy Nexus using xda app-developers app
INFOPreflash validation failure
FAILED <remote:
This is what I get when I try to flash the system.img
Is it a GSM or CMDA Razr?
I have a CDMA Razr
uuh... all I get is a <waiting for device> message. I can't get the phone to respond. It's stuck on the red droid-eye boot screen. I'm CDMA, btw
I have the system.img file in the same folder as all your other files, and followed the directions exactly. Help?
Florestan2 said:
uuh... all I get is a <waiting for device> message. I can't get the phone to respond. It's stuck on the red droid-eye boot screen. I'm CDMA, btw
I have the system.img file in the same folder as all your other files, and followed the directions exactly. Help?
Click to expand...
Click to collapse
You need to install the MOTOROLA Drivers that why it says you are waiting for device. I need to edit the guide to include that sorry I would do it now but I am crazy tired.
Xaikar said:
You need to install the MOTOROLA Drivers that why it says you are waiting for device. I need to edit the guide to include that sorry I would do it now but I am crazy tired.
Click to expand...
Click to collapse
They are installed.... I've checked 3 times...
When you are in the command prompt. Try typing
fastboot devices
Did it show any devices?
Also try loading your task manager and killing any ADB.exe running so it can reboot those utilities.
Xaikar said:
When you are in the command prompt. Try typing
fastboot devices
Did it show any devices?
Also try loading your task manager and killing any ADB.exe running so it can reboot those utilities.
Click to expand...
Click to collapse
It returns:
014e64e40101100D fastboot​
Yup - killed all instances of ADB* in task manager, too.
Great so it sees the device thats great news. What do it say about the battery does it say its low or battery OK?
Xaikar said:
Great so it sees the device thats great news. What do it say about the battery does it say its low or battery OK?
Click to expand...
Click to collapse
It says:
Device is locked. Status Code: 0
Battery OK
OK to program
Transfer Mode:
USB Cable
I understand that I am in no way the first person to have boot loop problem with the font installer but the solution always seems to be to flash a rom. My problem however is that I don't have cynagonmod or aokp, I only have stock jelly bean 4.1.2 on my LG p769
I did root my Phone and I have changed my font 2 other times before but this time when I did it my phone just went into a boot loop, do I need cwm recovery? because I don't think I have that and honestly this entire process has ben nothing but confusing.
If you don't have a custom recovery then you have to flash a ROM. You have to install adb and then fastboot then sw mode to flash the right ROM. Sounds complicated but it's kinda easy once you get the hang of it. Good luck
Sent from my LG-P769(20F) using the xda-developers app. If I helped you please hit the "thanks" button.
Nathan.7118391 said:
If you don't have a custom recovery then you have to flash a ROM. You have to install adb and then fastboot then sw mode to flash the right ROM. Sounds complicated but it's kinda easy once you get the hang of it. Good luck
Sent from my LG-P769(20F) using the xda-developers app. If I helped you please hit the "thanks" button.
Click to expand...
Click to collapse
By S/W mode do you mean the S/W upgrade mode? and After I install adb and Fastboot how do I go about flashing the ROM? Thanks in Advance.
CoryKenzie said:
By S/W mode do you mean the S/W upgrade mode? and After I install adb and Fastboot how do I go about flashing the ROM? Thanks in Advance.
Click to expand...
Click to collapse
Yes sw upgrade mode. You will need to use camendra and Lelus method for flashing.
EDIT: THIS is what I followed:
http://forum.xda-developers.com/showpost.php?p=44325657&postcount=4&nocache=1&z=6862240654882044
Sent from my LG-P769(20F) using the xda-developers app. If I helped you please hit the "thanks" button.
Nathan.7118391 said:
Yes sw upgrade mode. You will need to use camendra and Lelus method for flashing.
EDIT: THIS is what I followed:
http://forum.xda-developers.com/showpost.php?p=44325657&postcount=4&nocache=1&z=6862240654882044
Sent from my LG-P769(20F) using the xda-developers app. If I helped you please hit the "thanks" button.
Click to expand...
Click to collapse
I'm having problems trying to sort this out, I've jut spend over an our trying to update the driver for my phone with the device manager but I can't tell what the phones name is under the device manager... long story short, If there is anyway to simplify the process for me due to my inability understand the Android Lingo
Gotta follow the steps on the post. Ok go to the post I sent you which will immediately send you to another post to install omap4 on your phone. Then go back to the original post to install the u-boot and x-loader for p769 then get back into the fastboot and choose 1 for fastboot. Enter sw upgrade mode and flash your ROM.
Sent from my LG-P769(20F) using the xda-developers app. If I helped you please hit the "thanks" button.
Nathan.7118391 said:
Gotta follow the steps on the post. Ok go to the post I sent you which will immediately send you to another post to install omap4 on your phone. Then go back to the original post to install the u-boot and x-loader for p769 then get back into the fastboot and choose 1 for fastboot. Enter sw upgrade mode and flash your ROM.
Sent from my LG-P769(20F) using the xda-developers app. If I helped you please hit the "thanks" button.
Click to expand...
Click to collapse
No matter what I do the program always says Waiting for OMAP44xx Device... and I think I'm having problems installing this driver. I am using Windows 8 so do you think this might have anything to do with it?
I have tried on xp and win 7 which worked so idk about 8. Here try to follow just this for omap4boot.
http://forum.xda-developers.com/showthread.php?t=2119090
It took me a while to get it right but finally got it right. So don't give up! Then move on to the fastboot section.
Sent from my LG-P769 using xda app-developers app
Nathan.7118391 said:
I have tried on xp and win 7 which worked so idk about 8. Here try to follow just this for omap4boot.
http://forum.xda-developers.com/showthread.php?t=2119090
It took me a while to get it right but finally got it right. So don't give up! Then move on to the fastboot section.
Sent from my LG-P769 using xda app-developers app
Click to expand...
Click to collapse
So it turns out it was because I was using Windows 8 ( or possibly my surface pro) , I haven't flashed my phone yet but at least I've installed the driver and I'm running Fast Boot now, Thanks Nathan.7118391
I have reached a point where my phone has the the LG logo in black and white backwards, and it says fastboot v0.2 backwards... but the post doesn't say anything about how to flash the rom aferwards. and does it need to be an official kdz or can it be aokp?
I get as far as...
sending image to target...
size = 246272
usb_write 4
usb_write 246272
** Done **
< waiting for device >
then my phone re-enters the bootloop
I'm sorry to keep asking questions but every time I make progress there is always some problem and every forum just leads me to another forum.. I've already achieved fast boot on my phone, "I think" but I'm extremely confused as to how to flash the kdz. Any detailed explanation would be deeply appreciated. This probably seems really easy for you but am at wits ends. Thanks however for guiding me so far
I think I should add that I'm newish to XDA and this is my first post
Alright, I'm send you to some more threads, but this will get everything working lol
Use lelus modified batch script for l9
http://forum.xda-developers.com/showthread.php?t=2292828
His has an easy option to flash (with fastboot), the ice cream x & u for your device.
You need to do this to get the offline flash working.
Once you flash the x & u run the offline flash. Look at carloswii5 video to see how it is done.
http://forum.xda-developers.com/showthread.php?p=41388372
Note, you are not doing the other stuff in the vid, just learn how to install and use the offline flash. plus checkout this thread for more info
http://forum.xda-developers.com/showthread.php?p=36351786
Good luck.
CM 10.1 P769
CoryKenzie said:
I get as far as...
sending image to target...
size = 246272
usb_write 4
usb_write 246272
** Done **
< waiting for device >
then my phone re-enters the bootloop
Click to expand...
Click to collapse
Ok I'm assuming you are having trouble with the omap4boot commands. As the instructions say take out your battery from your phone and disconnect from computer. Run the program from your computer to get to the menu then select #3 for Prada and once you press enter put the usb cord into the phone then wait about 5 seconds then place your battery in. Should be smooth sailing after that. Once it asks you do you want fastboot just say no, and no to loading u-boot. Just disconnect your phone and you are done with this part. .Let me know when you are finished with this.
You can't flash a custom ROM in fastboot so you will have to load a stock kdz file but that's later. .
I finished that, I got all the way to the end where it says
--------------------------------------------
------------------------------
Please remove USB cable
and wait until LG Logo on
then reconnent USB cable again
------------------------------
fastboot devices (y/N) ? and press <ENTER> n
ls: resigned/p940-MLO*.bin: No such file or directory
Do you want to replace u-boot (y/N) ?n
ls: cwm/p940-*.img: No such file or directory
Press any key to continue . . .
I assume that is all I have to do here so should I just follow the New Lelus method now?
CoryKenzie said:
I finished that, I got all the way to the end where it says
--------------------------------------------
------------------------------
Please remove USB cable
and wait until LG Logo on
then reconnent USB cable again
------------------------------
fastboot devices (y/N) ? and press <ENTER> n
ls: resigned/p940-MLO*.bin: No such file or directory
Do you want to replace u-boot (y/N) ?n
ls: cwm/p940-*.img: No such file or directory
Press any key to continue . . .
I assume that is all I have to do here so should I just follow the New Lelus method now?
Click to expand...
Click to collapse
No Lelus method yet. You can do as Kuma has said above or what I did. Either way we are both trying to help you. Now that you got that done and congrats on that! Follow this http://forum.xda-developers.com/showpost.php?p=44325657&postcount=4&nocache=1&z=6862240654882044 which will help you with getting u-boot and x-loader on your phone. Skip getting the drivers because you already did that. But you will do the same thing that you did with the earlier program just now you are installing the x-loader and u-boot for your phone so your computer can "see" it. Once you've done that then you can flash with the Lelus method. But be sure to get it done right and practice if you need to.
Nathan.7118391 said:
No Lelus method yet. You can do as Kuma has said above or what I did. Either way we are both trying to help you. Now that you got that done and congrats on that! Follow this http://forum.xda-developers.com/showpost.php?p=44325657&postcount=4&nocache=1&z=6862240654882044 which will help you with getting u-boot and x-loader on your phone. Skip getting the drivers because you already did that. But you will do the same thing that you did with the earlier program just now you are installing the x-loader and u-boot for your phone so your computer can "see" it. Once you've done that then you can flash with the Lelus method. But be sure to get it done right and practice if you need to.
Click to expand...
Click to collapse
OK thanks for clearing my confusion on the Lelus method... but I have tried both Omap... and Fastboot, my problem with fastboot is that it get to step 3 of http://forum.xda-developers.com/showpost.php?p=44325657&postcount=4&nocache=1&z=6862240654882044
My phone screen is inverted and it says fastboot, but my computer never says press any button, just stops at <waiting for device>
about 1 minute after this appears, my phone just reboots into the loop. and I've seen other people post the entire script so I know my phone, or computer is stopping right before the x-loader and u-booter, for whatever reason.
CoryKenzie said:
OK thanks for clearing my confusion on the Lelus method... but I have tried both Omap... and Fastboot, my problem with fastboot is that it get to step 3 of http://forum.xda-developers.com/showpost.php?p=44325657&postcount=4&nocache=1&z=6862240654882044
My phone screen is inverted and it says fastboot, but my computer never says press any button, just stops at <waiting for device>
about 1 minute after this appears, my phone just reboots into the loop. and I've seen other people post the entire script so I know my phone, or computer is stopping right before the x-loader and u-booter, for whatever reason.
Click to expand...
Click to collapse
Ah, ok, ok, ok. . .Try this: bring the program up with the choices then press #5 but don't hit enter just yet. Now take your battery out and put the usb into the computer but don't connect it to your phone. Hold the cable next the plug in and hit enter. . .then it will say something like requesting omap4boot that's when you place the cable into your phone then it will go through some stuff pretty fast don't pay any attention just count in your head to 4 or 5 seconds then put your battery and wait 'till the fastboot comes up. . .that's it. once that happens your phone is u-boot and x-load ready.
After that this point sucked for me. You have to take out the battery and unplug your phone from your computer at the same time then wait 2 seconds and put your battery back in then immediately afterward hold the volume up button while inserting your cable back into the computer. . .wait for S/W upgrade mode. THEN YOU DO THE LELUS METHOD!!!
CoryKenzie said:
OK thanks for clearing my confusion on the Lelus method... but I have tried both Omap... and Fastboot, my problem with fastboot is that it get to step 3 of http://forum.xda-developers.com/showpost.php?p=44325657&postcount=4&nocache=1&z=6862240654882044
My phone screen is inverted and it says fastboot, but my computer never says press any button, just stops at
about 1 minute after this appears, my phone just reboots into the loop. and I've seen other people post the entire script so I know my phone, or computer is stopping right before the x-loader and u-booter, for whatever reason.
Click to expand...
Click to collapse
Looks like you aren't running fastboot as an admin
I am running as admin... and as a response to Nathan.7118391 BWUUAAA :eek : ,
I unplugged everything from my phone, then I press 5.
I press enter on the next page that says something about plugging out the phone and taking out the battery
Then I click Enter and plug in my phone. It goes through some things and than says " Wait 5 -lelelele
Than I put in the battery and it runs down to
** Done**
<Waiting for Device>
Does it matter that my phone is on Jellybean, or that I have an unlocked Bootloader?
CoryKenzie said:
I am running as admin... and as a response to Nathan.7118391 BWUUAAA :eek :,
I unplugged everything from my phone, then I press 5.
I press enter on the next page that says something about plugging out the phone and taking out the battery
Then I click Enter and plug in my phone. It goes through some things and than says " Wait 5 -lelelele
Than I put in the battery and it runs down to
** Done**
<Waiting for Device>
Does it matter that my phone is on Jellybean, or that I have an unlocked Bootloader?
Click to expand...
Click to collapse
Nope, it doesn't matter ...have you tried using different usb port ? preferably not usb3
I have a blind N10 on bootloader that is it doesnt show anything on fastboot mode but it does go there. I researched and found other people with similar problem http://rootzwiki.com/topic/37629-bootloader-fastboot-weirdness/ . However they managed to unlock the device by clicking the vol+ once and then power key as I also saw on youtube videos. IT WORKED. and then it went downhill. it got stuck on bootloop. SO i tried to go into fastboot again and it went and then pressed vol+ twice to go into recovery and there was a android with "!" red sign on middle.
and of course it won't boot. So I tried to use the Wugs toolkit, put it on back to stock with bootloop option. and it started to do its work, but got stuck at the sending bootloader (1280KB) sign for more than 10-15 mins. I pressed the power button and it failed that step saying too many links and wugs kit continued the process got stuck again and then completed and my device still goes to fastboot, but cant go into recovery anymore I think as it shows blank screen. Please mind that I am still blind on the screen and nothing comes. my only way of knowing it goes to fastboot is through cmd line. PLEASE HELP, dont wanna brick this.
Is there any way to ODIN it. I cant find online any ODIN insturctions? help help
I cant even turn it off now! Its always going to fastboot. Please help
mustafansu said:
I cant even turn it off now! Its always going to fastboot. Please help
Click to expand...
Click to collapse
I think that's a good thing, if you can get to Fastboot then I would say to forget about the toolkits and just download the latest Google MantaRay image from here https://dl.google.com/dl/android/aosp/mantaray-jwr66y-factory-3d8252dd.tgz
Make sure your Android SDK is updated, unzip the downloaded file once and copy the contents to your Fastboot folder, shift/right click inside your fastboot folder and select "open command window here" then type "fastboot devices" and make sure your device id is shown, after that just type in your cmd window "flash-all.bat" and let it do its magic. If everything goes well by the time it completes you will have a factory restored Nexus10 and then you can start the hacking all over again.
Good Luck! and remember when in doubt, just ask.
Erik
ricco333 said:
I think that's a good thing, if you can get to Fastboot then I would say to forget about the toolkits and just download the latest Google MantaRay image from here https://dl.google.com/dl/android/aosp/mantaray-jwr66y-factory-3d8252dd.tgz
Make sure your Android SDK is updated, unzip the downloaded file once and copy the contents to your Fastboot folder, shift/right click inside your fastboot folder and select "open command window here" then type "fastboot devices" and make sure your device id is shown, after that just type in your cmd window "flash-all.bat" and let it do its magic. If everything goes well by the time it completes you will have a factory restored Nexus10 and then you can start the hacking all over again.
Good Luck! and remember when in doubt, just ask.
Erik
Click to expand...
Click to collapse
Hi ricco333
thanks for the reply. I have updated the SDK and tried to run the command as you mentioned. However it is the same thing. Its getting stuck at sending bootloader. I am attaching a screenshot here. it stays there until i press ctrl+c. then it tries to continue and gets stuck again at sending boot. which is the second screenshot.
Is there any other way to restore factory image. i thought samsung devices had ODIN system. Thanks again for the reply.
Try connecting the Nexus to a different USB port, also try another USB cable, as a last resort I will go as far as using a different PC, based on your screenshots it is being recognized but my guess is that it is having a problem writing the new partitions.
Erik
Also try re downloading the stock images...
Maybe you have a corrupted file.
Have you tried using the Nexus 10 Toolkit?
http://forum.xda-developers.com/showthread.php?t=2001868
IT WORKED!!
ricco333 said:
Try connecting the Nexus to a different USB port, also try another USB cable, as a last resort I will go as far as using a different PC, based on your screenshots it is being recognized but my guess is that it is having a problem writing the new partitions.
Erik
Click to expand...
Click to collapse
Thanks so much guys.After trying 2 different cables and a new computer, a fresh installation of ADB and samsung drivers it finally worked. Thanks again. HUGE SIGH of RELIEF