I tried unlocking my bootloader with ATT Unlocker for 1.8.3 and 4.5.91 ATT firmwares found in the pudding thread seemed to go well at first but when it rebooted I got:
SWF 105:1:2
Failed to boot 0x1000
No OS detected, going to rsd mode in 5 seconds press a key to stop count down available modes are:
1)rsd
2)fastboot
3)NvFlash
4)Bp HW Bypass rsd
5)BP HW bypass QC Dload
6)BP HW diag & Boot AP
7)BP HW Bypass BP only
8)BP SW Bypass RSD
9)Android recovery
10)boot android (no BP)
11)Device UID
12)console=tty50,115200n8
13 Early USB enumeration
14)BP tools
current choice is node:
RSD
starting Fastboot support protocol
but the volume keys were unresponsive and I couldn't select anything and nothing ever happened, it just stayed at that screen just like that. So I thought no worries I would just flash to stock and I would be ok at least. Then I tried to flash ATT 4.5.91 sbf from the firmware superthread, it failed almost immediately hitting start in RSD lite!
I then installed Motorola Software Update hoping that could fix it. While it detected the device it showed N/A in all the fields and couldn't upgrade my device.
After several battery pulls my device started to give the "battery too low to flash" message in addition to the above message so I plugged it into a wallcharger and the message stayed on screen the whole time. I left it charging overnight but, when I took it off the charger in the morning it died almost immediately.
When I plugged it into the PC with the USB cable I just get a black screen although the LED at the top left glows green. So I believe that the battery is totally dead with no way to charge it.
Getting very desperate, I called motorola for warranty purposes and they just sent me an email redirecting me to their troubleshooter which is unable to detect my device, as suspected.
So, Is my Atrix fixable or is it hard bricked? I have a warranty as the device is only 3 months old and Best Buy Black Tie Protection. I also fortunately have another upgrade on my family plan and can get another atrix from Amazon wireless for only $25(with a contract). Therefore I'm not too worried, but would like to fix my phone if possible!
Just continue the process with fastboot oem unlock and fastboot reboot
Sent from my MB860 using XDA App
Thanks for the reply, but I don't think that will work since my PC and subsequently ADB doesn't recognize my phone due to very low battery and it won't charge
The volume buttons are also unresponsive.
whenemusattack said:
Thanks for the reply, but I don't think that will work since my PC and subsequently ADB doesn't recognize my phone due to very low battery and it won't charge
The volume buttons are also unresponsive.
Click to expand...
Click to collapse
if you can boot into fastboot mode, use fastboot to use the 'fastboot oem unlock' command.
if you can't charge your phone, then try to take your battery out and plug your phone into the OEM wall charger, and then place your battery back in the phone causing it to charge.
So let me get this straight, alls I need to do is force it to charge then when it's charged go to cmd and get to android-sdk/tools and type fastboot oem unlock, agree to bootloader unlock then it will be back to normal?
whenemusattack said:
So let me get this straight, alls I need to do is force it to charge then when it's charged go to cmd and get to android-sdk/tools and type fastboot oem unlock, agree to bootloader unlock then it will be back to normal?
Click to expand...
Click to collapse
That should work, yes
Sent from my MB860 using xda premium
Im pretty sure you can't charge while in this mode, your gonna have to borrow another atrix or external charger to charge your battery
Sent from my MB860 using XDA App
one last question, is there anyway to be sure it's charging? Will the green light come on?
whenemusattack said:
one last question, is there anyway to be sure it's charging? Will the green light come on?
Click to expand...
Click to collapse
Read my post before your question
Sent from my MB860 using XDA App
sorry, I didn't see that, you're probably right but, I can still try, Unfortunately I don't know anyone with an atrix so I'll probably have to buy an external charger.
I think an universal charger can take care of it...
Just try...
I bought a universal charger from Amazon: http://www.amazon.com/gp/product/B004B8ECR4 should be here by Saturday, I'll let you know how it goes.
Thanks, I charged my battery via 3rd party charger, then did what you said, now I'm back to normal! Time to root my device now!
No. If i were you I would follow this guide. It will root your phone. This same thinghappened to me and i followed this guide and its works perfectly.
MOTOROLA Atrix 4g Root
TERMS & CONDITIONS
1. Note: ROOTING you phone WILL NOT allow you to install THEMES or ROMs. You will need to UNLOCK YOUR PHONE'S BOOTLOADER for that.
UPDATE 8/31/11 - WARNING: This will work on other phones besides AT&T, BUT it was designed for AT&T 4.5.91 and created using AT&T files. If you use this on other carrier phones you WILL have a problem installing future updates from Motorola and your carrier. Bell Canada users on 2.2.2 who have already used this and are now trying to update, see the bottom of this post.
This will work on all versions of the Motorola Atrix firmware and on any carrier. Yes, this works even if your bootloader is still locked and you're on the official AT&T 4.5.91; confirmed working on Bell Gingerbread as well (2.3.4 Gingerbread update.) This has been out for sometime, but I was oblivious to it possibly working after updating to 2.3.4. It's very simple and straightforward, just be sure to follow the directions exactly. This works whether you have been previously rooted before or not and even if you already have an old Superuser app.
WARNING: This will modify the system files of your phone and technically VOID YOUR WARRANTY. I will not take any responsibility if anything happens to your phone. Please know what you're doing and why you're doing it. Please read all directions fully at least twice before proceeding so you know what you're about to do. There is NO EASY WAY TO UNROOT this because the new 4.5.91 SBF is only a Service SBF and not Full. It helps, but you might still have to manually uninstall the Superuser.apk as well.
I have tested this on my phone being on AT&T 4.5.91 (2.3.4 Gingerbread) after the official OTA update, with a LOCKED bootloader, previously rooted with Superuser app left over from previous root. You don't need to have been rooted before and you can also have an unlocked bootloader as well.
Below instructions are for Windows only. Download links lead to the original posting website to give them traffic credit.
This method was created and posted to XDA-Developers by A.J. Birone
Motorola Atrix 4g – Complete Guide to root Motorola Atrix 4g
Prerequisites
o Drivers installed 32-bit or 64-bit
ADB-Fastboot package
o Root image
Instructions
3. You may plug your phone in to the PC via USB no and leave it plugged in the entire time.
4. Extract (you may need to download 7-Zip to extract the files from their .zip) the ADB-Fastboot package and root image to your C:\ Drive under a new folder titled “root” - You should now have everything in C:\root (Please see the picture at the bottom of the post that shows all files that are supposed to be in C:\root)
5. Put your device into Fastboot mode: – Turn off your device. – Hold down the power button and downward volume button until you see “Fastboot” on your screen – Push the upward volume button to start Fastboot (if you're already plugged in it will auto-reboot,just hold Vol down as it starts to reboot.)
6. Open your command prompt (Start >> run “cmd” >> enter)
7. Type the following commands, hitting Enter after each line:
Code:
cd C:/root
fastboot flash preinstall root.img
fastboot reboot
8. After phone fully reboots (wait about 30 seconds after it comes back up) go in and make sure to enable USB debugging (Settings >> Applications >> Development >> USB Debugging)
9. Type the following commands, hitting Enter after each line:
Code:
adb shell
/preinstall/dosu
10. You will now see this error, but this is where you're supposed to be: "bash: groups: command not found
[email protected]:/#"
11. Type the following commands, hitting Enter after each line:
Code:
/bin/mount /system -o remount,rw
cp /preinstall/su /system/bin/su
chmod 6755 /system/bin/su
PATH=/system/bin:$PATH pm install /preinstall/Superuser.apk
12. Congratulations! You are rooted!
13. Type 'exit' and hit Enter each three times to get out of root, ADB shell and the command prompt.
14. Make sure your USB selection on your phone is set to None and unplug the cable.
15. You're Done!!
***If you get an error when installing the Superuser.apk, just download the Superuser app from the Market***
Congratz for charge battery hehe. Now do what u wanna do xd
Sent from my MB860 using xda premium
another trick if you don't want to spend your hard earned cash on an external charger (i did this last night)
find a spare usb cable. strip some of the the black insulation from the cable (a good 4-5 inches should do it), cut away the metal shield, find the red and black wires and cut them close to the micro usb connector. strip about 1cm of the red and black insulation from the wires and then twist the wires and hold them over the correct terminals on the phone while putting the battery back in (red+ on right 2 terminals, black- on left 2 --- make sure they dont come in contact with each other, and the red wire doesn't touch any other metal parts on phone).
plug usb into pc (you dont need to plug micro usb into phone), and if done correctly the 'battery too low' message will no longer show up, and you will be able to use rsd mode to recover your phone using another usb cable.
by the way i am i not responsible if you don't follow these instructions carefully and damage your battery/phone in any way whatsoever. if you don't feel capable of doing it, find someone who can.
Sent from my MB860 using XDA App
Related
Hello, First time Poster here, please bare with me...
I really shouldn't of touched this.....
I have an Atrix w/ the newest updates to it, and attempted to unlock the phone. Using the guide from atrix4ghacks.com Everything started well, then it failed while writing to the device. Now, when I attempt to boot, I get the message
SVF:405;1:2
Failed to boot 0x1000
1- RSD
2-Fastboot
3-NVflash
4- BP HW Bypass RSD
5-BP HW Bypass QC DLOAD
6-BP HW Bypass & Boot AP
7-BP HW Bypass BP only
8- BP SW Bypass RSD
9- Andriod recovery
10- Boot Andriod (no BP)
11- Device UID
12- Console
13- Early USB
14- BP tools
I can get into fastboot, though I honestly am not sure what to do from there. I have the fastboot s/w downloaded, along with the gingerbread OS. When I tried to execute the command via Command prompt. I keep getting unknown command errors (yes, directories within the command are good).
Did I just kill my phone?
I have found a few posts here related to this, though I havent found what seems to be a solid answer to a "fix" for this. I would highly appreciate if someone could try to help me with this.
Sorry, I have broken a noob rule (was pretty late when I watched the video), I thank you all in advanced for any help
STOP!!! YOU HAVEN"T KILLED YOUR PHONE JUST YET!
BUT IF YOU SBF YOU WILL!!!
Go into fastboot and repeat all of the unlock commands, reboot and your phone should boot fine after that.
Ok, I will give that a shot!
Hopefully this will work. THANK YOU!
Ok, is there a way to force charge this?
I had it hooked up and when I was going to execute the flash, it gave the message of battery too low to flash.... Will just leaving it plugged in be ok? or is there a button function I can do that will ensure it charges the unit?
Thanks again
Grumbles said:
Ok, is there a way to force charge this?
I had it hooked up and when I was going to execute the flash, it gave the message of battery too low to flash.... Will just leaving it plugged in be ok? or is there a button function I can do that will ensure it charges the unit?
Thanks again
Click to expand...
Click to collapse
Ugh... from what I heard the battery won't charge while in fastboot mode. You need a standalone charger or a different battery.
So, it doesn't let you get into fastboot at all, huh?
I was afraid of that- I think ive found the solution to that on this link:
http://www.droidforums.net/forum/droid-labs/146492-how-why-make-your-own-motorola-factory-cable.html
That is def. something I can do, and will try. Otherwise, to answer your question. The PC sees the device- It is then the device that says battery is too low to flash (on any mode you choose). Once that message is shown, it wont allow me to access it at all.
Worse to worse, I will take a trip to the att store, or somewhere close to see if they have a wall or base charger. If the doc has a separate power connector, I may try that...
Grumbles said:
I was afraid of that- I think ive found the solution to that on this link:
http://www.droidforums.net/forum/droid-labs/146492-how-why-make-your-own-motorola-factory-cable.html
That is def. something I can do, and will try. Otherwise, to answer your question. The PC sees the device- It is then the device that says battery is too low to flash (on any mode you choose). Once that message is shown, it wont allow me to access it at all.
Worse to worse, I will take a trip to the att store, or somewhere close to see if they have a wall or base charger. If the doc has a separate power connector, I may try that...
Click to expand...
Click to collapse
The factory cable would allow you to use the phone without the battery, but it might take more money and time to make then you think.
From what I understand, RSD threw you an error when you were flashing bootloader unlock.
Anyway, you need to find a way to charge your battery and they do the fastboot unlock commands.
If that doesn't work you need to reflash the pudding SBF, (make sure you install the drivers Windows x64 version here prior to flashing and that your phone is recognized in RSDlited)
Get the correct pudding file from here: http://forum.xda-developers.com/showthread.php?t=1136261
Use instructions here (start at step 1) : http://briefmobile.com/how-to-unlock-the-atrix-4g-bootloader
Note that after pudding is flashed successfully and you do the unlock commands, you will get a failed to boot error (seems like what you have now). You need to redo the unlock commands in fastboot and it will fix the problem.
Good luck.!
Alright!
Got the cable completed and works!
So, battery situation is handled, now to follow your steps
THANK YOU! I will report back and let you know.
Ok,
Clearly I am doing something wrong here.....
I followed the instructions using the newest Pudding_preroot.sbf file, and the RSD software sees the device (as a SE flash not a NS if that matters) and will start the flashing process.
Everything works to plan until the phone does its reboot(99$ executed), gives the fail to boot message again. Then wants to start back up in RSD mode.... The RSD application on the otherhand, it seems like its trying to switch the phone to"BP passthrough mode" I do not see that exact option, and after it failed while rebooting to RSD. I tried to move it to fastboot, BP HW Bypass RSD, and finally BP SW bypass RSD... All with the same failure on the RSD screen:
"Failed Flashing Process. Phone (0000): Error switching to BP Pass through mode (0x70BE); phone connected"
I have a funny feeling that this part is obvious, for that I am sorry for my ignorance.
I am pretty sure this thing is toast...
After getting nowhere after step 12, and multiple attempts to install the pudding_preroot file. I did some searching around and found multiple atrix users that would get the same issues. From the flash showing up as SE rather than NE, to the constant failing during the flash via RSD lite, with the same failure errors.
I noticed a "NV flash" option, and found this link that could establish a recovery USB driver to the phone. Do you think this maybe my next best route?
http://forum.xda-developers.com/showthread.php?t=1123429
My factory cable is good, so that option IS open..... Though I am starting to think this is toast.
We cannot use NVFlash unless we get the SBK (signature file). Currently, we do not have it. Motorola does, so plead to them
OK, well now it decided to only mount itself as a unknown APX device... Not sure the whats or whys there. Nothing has changed since the last failures?
Hey man, I think RSD shows the flashing process as failed since it can't fully reboot the phone.
Go into fastboot mode and try doing the unlock commands. (try this twice if ita fails after the first time).
In the worst case scenario if unlocking fails no matter what, you can flash a complete 2.3.4 rom via SBF and that should get you back up and running.
Let us know how it goes.
Remember, if you can get into RSD or fastboot - the phone isn't bricked yet!
What's the easiest method to unlock the bootloader on the ATRIX?
Im having a hard time getting it done.
Sent from my MB860 using xda premium
Use the ihop (aka pudding) method from the development section...
Sent from my MB860 using xda premium
http://briefmobile.com/how-to-unlock-the-atrix-4g-bootloader
I have followed the directions to the letter and keep getting "oem unlock is not implemented"
Im so frustrated. I cant figure out what the problem is.
---------- Post added at 11:24 PM ---------- Previous post was at 11:06 PM ----------
By the way, Im on 2.3.4. Is that the issue?
Don't skip to 13, eat your pudding first.
From the Mighty Atrix 4G
This seems to work for most people. You'll get a soft brick but you'll be able to get out of it and finish the process. Read through the topic until you feel comfortable enough to try it. Also you can run the DOS file before you start the process just to see what each step tells you to do.
Automatic BL Unlock
LSUtigers03 said:
This seems to work for most people. You'll get a soft brick but you'll be able to get out of it and finish the process. Read through the topic until you feel comfortable enough to try it. Also you can run the DOS file before you start the process just to see what each step tells you to do.
Automatic BL Unlock
Click to expand...
Click to collapse
Does this work on Non AT&T phones, like mine which is UK Sim Free?
@home said:
Does this work on Non AT&T phones, like mine which is UK Sim Free?
Click to expand...
Click to collapse
The DOS file says it's for AT&T only.
LSUtigers03 said:
This seems to work for most people. You'll get a soft brick but you'll be able to get out of it and finish the process. Read through the topic until you feel comfortable enough to try it. Also you can run the DOS file before you start the process just to see what each step tells you to do.
Automatic BL Unlock
Click to expand...
Click to collapse
this worked perfect for me and it seemed to be the easiest way
In my opinion the soft brick was a headache. The briefmobile method was what ultimately worked for me. I wish I had used it sooner. The DOS method worked well for rooting though.
Sent from my MB860 using XDA App
fleurdelisxliv said:
this worked perfect for me and it seemed to be the easiest way
Click to expand...
Click to collapse
Were you on 2.3.4?
Ok, finally! I got it done and flashed to CM7. WOW! I love it!
I did notice some differences so I will post my experience here shortly. I will highlight the differences I found that worked for my 2.3.4 Rooted Atrix. Maybe it will help other newbs like me : )
By the way, credit to BriefMobile and the2dcour for the original guide
How To: Unlock the Atrix 4G Bootloader
Prerequisites
Backed up /data partition
You will lose all of your /data during this process!
Unlock SBF file [Mirror]
RSD Lite 5.3.1 or sbf_flash [Download if Atrix is Froyo]
Fastboot package [Mirror]
Also found in the Android SDK tools folder
Instructions
If you’re on Gingerbread, skip to step 13. I had to do all steps to get it to work, but I was also on 2.3.4
Power down your Motorola Atrix
Take out your microSD card and SIM card for the flashing process
While turning the phone on, hold the Volume Up button until it acknowledges RSD
Your device will say “Starting RSD protocol support”
Run “RSD Lite” on your computer
Press the “. . .” button next to the box labeled “Filename”
Load up the SBF file
The SBF file is located inside of the .zip file, you must extract it out before loading it into RSD Lite
Use WinRAR or 7-Zip to extract the .zip file on your computer
Plug your device into your computer
Use the USB ports on the back side of your computer for safety
RSD Lite should recognize your device and say “Model: NS Flash Olympus” and “Connected…”
Press the “Start” button
Be patient while the phone reboots. It will take a long time.
Open and extract the Fastboot package from above
Open a command prompt window
On Windows, press Start and type “cmd” then press the enter button
Type the following command. Your directory will be the folder where you extracted the Fastboot package.
(Example: cd C:\Users\Kenneth\Desktop\fastboot-package)
cd your directory here
Power down your Atrix device
Hold the power button and the downward volume button until you see “Fastboot”
Let go of the buttons and press the upward volume button once
You will now see “Starting Fastboot protocol support”
Plug your device into a USB port in the back slot of your computer
Front slots sometimes do not have enough power to stay connected to the device.
Type the following command:
fastboot oem unlock
You will now receive a warning along with a unique device ID
Type the following commands using your unique device ID in place of the ####:
fastboot oem unlock ####
fastboot reboot
Wait for your device to reboot. Congratulations! You now have an unlocked bootloader!
Source: the2dcour
Ok, finally! I got it done and flashed to CM7. WOW! I love it!
I did notice some differences so I will post my experience here. I will highlight the differences I found that worked for my 2.3.4 Rooted Atrix. Maybe it will help other newbs like me : )
By the way, credit to BriefMobile and the2dcour for the original guide
***I marked the differences I noticed when unlocking my 2.3.4 unlocked At&t Gingerbread***
How To: Unlock the Atrix 4G Bootloader
Prerequisites
• Backed up /data partition
You will lose all of your /data during this process!
• Unlock SBF file [Mirror]
• RSD Lite 5.3.1 or sbf_flash [Download if Atrix is Froyo]
• Fastboot package [Mirror]
Also found in the Android SDK tools folder
Instructions
1. If you’re on Gingerbread, skip to step 13. (I was on 2.3.4 Gingerbread and I also had to do all the steps. Dont skip!!!)
2. Power down your Motorola Atrix
3. Take out your microSD card and SIM card for the flashing process
4. While turning the phone on, hold the Volume Up button until it acknowledges RSD
5. Your device will say “Starting RSD protocol support”
6. Run “RSD Lite” on your computer
7. Press the “. . .” button next to the box labeled “Filename”
8. Load up the SBF file
The SBF file is located inside of the .zip file, you must extract it out before loading it into RSD Lite
Use WinRAR or 7-Zip to extract the .zip file on your computer
9. Plug your device into your computer
Use the USB ports on the back side of your computer for safety
10. RSD Lite should recognize your device and say “Model: NS Flash Olympus” and “Connected…” (Mine said SE Flash Olympus, not NS)
11. Press the “Start” button
12. Be patient while the phone reboots. It will take a long time. (Phone didn’t reboot. It went to a menu and said I “5 seconds to select Fastboot”. You have to use Vol down to move in the menu and the Vol up button to select “Fastboot”)
13. Open and extract the Fastboot package from above
14. Open a command prompt window
On Windows, press Start and type “cmd” then press the enter button
15. Type the following command. Your directory will be the folder where you extracted the Fastboot package.
(Example: cd C:\Users\Kenneth\Desktop\fastboot-package) (I extracted mine to the C:\ drive. Then you don’t have to type so much. Just cd C:\fastboot )
cd your directory here
16. Power down your Atrix device
17. Hold the power button and the downward volume button until you see “Fastboot”
18. Let go of the buttons and press the upward volume button once
19. You will now see “Starting Fastboot protocol support”
20. Plug your device into a USB port in the back slot of your computer
o Front slots sometimes do not have enough power to stay connected to the device.
21. Type the following command:
fastboot oem unlock
22. You will now receive a warning along with a unique device ID
23. Type the following commands using your unique device ID in place of the ####:
fastboot oem unlock ####
fastboot reboot
24. Wait for your device to reboot. Congratulations! You now have an unlocked bootloader! (Mine said “unlocked” in upper left hand corner, but didn’t reboot. I pulled the battery and restarted. Been working fantastic ever since!)
Source: the2dcour
hey guys i got an atrix telcel mexico running android cm7 2.3.7 and ive seen most of the people having trouble unlocking the bootloader
im actually new to xda and want to share how to unlcok bootloader its actually same method used as at&t
WARNING: USE AT YOUR OWN RISK WHEN FLASHING YOUR DEVICE
BEFORE STARTING REQUIREMENTS
RSD LITE 5.3.1
IHOP_BELL.SBF
FASTBOOT PACKAGE
UPDATED MOTOROLA DRIVERS
Stock rom 2.2 (in my case it was 2.2.1 others may have 2.2.2)
Instructions
1.Power down your Motorola Atrix
2.Take out your microSD card and SIM card for the flashing process
3.While turning the phone on, hold the Volume Up button until it acknowledges RSD
4.Your device will say “Starting RSD protocol support”
5.Run “RSD Lite” on your computer
6.Press the “. . .” button next to the box labeled “Filename”
7.Load up the IHOP SBF file◦The SBF file is located inside of the .zip file, you must extract it out before loading it into RSD Lite
◦Use WinRAR or 7-Zip to extract the .zip file on your computer
8.Plug your device into your computer◦Use the USB ports on the back side of your computer for safety
9.RSD Lite should recognize your device and say “Model: SE Flash Olympus” and “Connected…” (THIS WAS ACTAULLY WHERE MOST PEOPLE GOT STUCK SINCE ON THE AT&T MOTHOD ITS ''NS Flash Olympus'' AND THEY GOT AN ERROR ON THEIR SCREEN)
10.Press the “Start” button
11.Be patient while the phone reboots. It will take a long time.
12.Open and extract the Fastboot package from above
13.Open a command prompt window◦On Windows, press Start and type “cmd” then press the enter button
14.Type the following command. Your directory will be the folder where you extracted the Fastboot package.
◦cd your directory here
15.Power down your Atrix device
16.Hold the power button and the downward volume button until you see “Fastboot”
17.Let go of the buttons and press the upward volume button once
18.You will now see “Starting Fastboot protocol support”
21.Plug your device into a USB port
22.Type the following command:◦fastboot oem unlock
23.You will now receive a warning along with a unique device ID
24.Type the following commands using your unique device ID in place of the ####:◦fastboot oem unlock ####
◦fastboot reboot
25.Wait for your device to reboot. Congratulations! You now have an unlocked bootloader!
I hope this works for u
like i said im new and this is actually my first post
my atrix is working fine and i also have a custom recovery in it
Well done.
Hopefully you won't start a similar thread for:
- flashing a rom
- Flashing a kernel
- Updating the radio
- something else that is already documented
A link to the existing process is enough. Otherwise it looks like you created it all (which it sort of does in this case) and that is unfair & pi**es people off. Plus its dangerous because people can easily brick their phones and then run back to you for the explanation. Surely you don't want to deal with that..
A well meant advise.
Well Im form Mexico and got a new Atrix, so after reading lots of guides, the fact that this one assured me of working on a 2.2.1 telcel device, helped a little.
thanks a lot!
Dude, you're a lifesaver. While I understand the criticism made by 2ndP, I have to say that your post saved me from spending another 4 hours tweaking unsuccesfully with loads of files to unlock my brazilian Atrix
Hello, Guys. So I did a stupid thing today - I was poking around in the build.prop in my v20d P769. I changed the value of a line concerning the battery, something like "battery_genuine" - My thought was that it was going to enable some sort of alternate battery notification or icon or whatever, I'm not sure what I was thinking.
Anyway, long story short, I rebooted after editing build.prop and now when the phone turns on it just says "use genuine battery - powering off" and shuts off. I had previously uninstalled CWM (getting ready to manually apply v20f) so I can't get to recovery to mount /system. I have been trying all day to get the offline flash method to work and the damn thing won't work half the time. I went through the thread instructions to install small server and edit hosts file - then reboot - when the loopback ip's are in the hosts file the test link on the thread (127.0.0.1:9002) doesn't work and neither LG application will work. If I comment out the loopback lines and restart both of them will open but neither of them will do anything useful. LG Updater tool just says I have the latest software and the UptestEX_mod2_marwin application won't flash anything.
Hoping someone can help me out here so I can recover this phone.
boot the phone in fastboot mode, don't know how to do that with your model though
use fastboot to boot into any custom recovery by typing 'path_to_adb_toolkit_files\fastboot.exe boot your_recovery_image.img'
if fastboot hangs on <waiting for device> install usb drivers
then pull off build.prop, change that field to original value and push it back into the phone
sorry mate, can't explain more detailed
Either flash ICS uboot and xloader in fastboot mode and unbrick it after, or if you can access adb, try sometjing like the following:
cd to your adb directory on your PC
adb pull /system/build.prop (in a command prompt on your PC)
Modify the file (it will be in the adb folder)
adb push pathto/thefile/build.prop > /system/build.prop (again in the cmd)
Hope it helps
Sent from my LG-P760 using xda app-developers app
N00BY0815 said:
Either flash ICS uboot and xloader in fastboot mode and unbrick it after, or if you can access adb, try sometjing like the following:
cd to your adb directory on your PC
adb pull /system/build.prop (in a command prompt on your PC)
Modify the file (it will be in the adb folder)
adb push pathto/thefile/build.prop > /system/build.prop (again in the cmd)
Hope it helps
Sent from my LG-P760 using xda app-developers app
Click to expand...
Click to collapse
Thanks for the reply man - yeah I can't get to adb, that was my first though so i'm going to try fastboot, only problem is, I don't know how to boot fastboot. Is s/w upgrade mode the fastboot screen (volume up + plug in cable)?
Also, would anyone mind explaining why the small server only outputs "file not found" when attempting to start up the flash tool? The only way I can get the flash tool to even launch is to comment out the loopback lines in hosts. lol man it's times like this when I miss motorola!
*Edit - In case anyone wants to help on this front, here is the output I receive from small server when trying to open B2CappClient or UpTest or even hit the test link in the offline flash thread:
Accept-Language: en-US,en;q=0.8
^!!
!->02/08 23:54:39 [127.0.0.1:2173>9002] (t1 4) >\favicon.ico(Undefined/default)
Error. File not found.
!->02/08 23:54:39 [127.0.0.1:2173>9002] (t1 5) >HTTP in:279 out:1993 Time:31
!->02/08 23:54:41 [127.0.0.1:2177>9002] (t1 6)
GET /favicon.ico HTTP/1.1
Host: 127.0.0.1:9002
Connection: keep-alive
Accept: */*
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/28.0.1500.95 Safari/537.36
Accept-Encoding: gzip,deflate,sdch
Accept-Language: en-US,en;q=0.8
^!!
!->02/08 23:54:41 [127.0.0.1:2177>9002] (t1 7) >\favicon.ico(Undefined/default)
Error. File not found.
!->02/08 23:54:41 [127.0.0.1:2177>9002] (t1 8) >HTTP in:279 out:1995 Time:94
!->02/08 23:55:43 [127.0.0.1:2184>9002] (t1 9)
GET /client/app/live_update.jsp HTTP/1.1
Host: csmg.lgmobile.com:9002
Cache-Control: no-cache
^!!
!->02/08 23:55:43 [127.0.0.1:2184>9002] (t1 10) >\client\app\live_update.jsp(Undefined/default)
Error. File not found.
!->02/08 23:55:43 [127.0.0.1:2184>9002] (t1 11) >HTTP in:99 out:2012 Time:62
I recommended removing all lg drivers and etc. Redownload all files, disable firewall and antivirus. But first you need to install fastboot and flash the u-boot for ice cream.
Inside the fastboot zip by lelus is more instructions on how to set it up. And checkout the original thread about fastbooting the l9
And you might want to try on another PC,
You need a good and clean windows environment for all to work well. This is the problem with many people. Plus a lot of antivirus programs don't like the small server.
Sent from my LG-P769 using xda app-developers app
well, if you boot into a screen that is neither android nor recovery, it should be fastboot at least this applies to my phone
since the combination is one button + plug in cable i guess it's the right one
does it say fastboot mode in the top of the screen?
SuicideFlasher said:
well, if you boot into a screen that is neither android nor recovery, it should be fastboot at least this applies to my phone
since the combination is one button + plug in cable i guess it's the right one
does it say fastboot mode in the top of the screen?
Click to expand...
Click to collapse
Well I managed to get to fastboot with the p940 script. The screen that comes up with "S/W Upgrade Please wait while upgrading...". this may be some sort of fastboot derivative but there's no response to "fastboot devices" at the prompt. Can I flash cwm through fastboot if my bootloader is locked? I had it installed with the bootstrap method.
peoplegetpeople said:
Well I managed to get to fastboot with the p940 script. The screen that comes up with "S/W Upgrade Please wait while upgrading...". this may be some sort of fastboot derivative but there's no response to "fastboot devices" at the prompt. Can I flash cwm through fastboot if my bootloader is locked? I had it installed with the bootstrap method.
Click to expand...
Click to collapse
Fastboot is an inverted lg logo.
This will offer some more help,
http://forum.xda-developers.com/showthread.php?p=43703982
Hey don't flash ice cream and ect.
All you have to do is flash (in fastboot) the boot.IMG for the kdz you are on, and you're good to go.
Extract the boot.img from the kdz
Look at my guide. Or just wait until later tonight for me to upload it.
To tell you the truth, Lol, I did the same thing you did with the battery. I was fast enough to edit it before it shutoff. I had toolbox lite app installed.
CM 10.1 P769
Finally got it! :laugh: Turns out, the default path for small server is c:\shttps\www - the problem I gave myself is that when I didn't extract to the c root, I copied from my L9 directory - when I copied none of the contents of \www copied with it, once I moved those files to the correct position it all went through as it should!
Thanks for your help guys!!
kuma82 said:
Fastboot is an inverted lg logo.
This will offer some more help,
http://forum.xda-developers.com/showthread.php?p=43703982
Hey don't flash ice cream and ect.
All you have to do is flash (in fastboot) the boot.IMG for the kdz you are on, and you're good to go.
Extract the boot.img from the kdz
Look at my guide. Or just wait until later tonight for me to upload it.
To tell you the truth, Lol, I did the same thing you did with the battery. I was fast enough to edit it before it shutoff. I had toolbox lite app installed.
CM 10.1 P769
Click to expand...
Click to collapse
hahaha I saw this about 10 mins after I got it to boot! lol - oh well, I'm running 20f now, getting ready to root and see about unlocking the bootloader. Now that the flash tool is working correctly, the only thing I have to do is get a feel for the mirrored, wonky screen. I've been researching the bootloader method but could never get that flash tool to work correctly. I'm in the game now! WOOT!
Thanks for all your help man!
peoplegetpeople said:
hahaha I saw this about 10 mins after I got it to boot! lol - oh well, I'm running 20f now, getting ready to root and see about unlocking the bootloader. Now that the flash tool is working correctly, the only thing I have to do is get a feel for the mirrored, wonky screen. I've been researching the bootloader method but could never get that flash tool to work correctly. I'm in the game now! WOOT!
Thanks for all your help man!
Click to expand...
Click to collapse
Just be sure you are ready for everything,
I recommended flashing 20d then 20b.
Hold up I'll give you all the help I gave to someone in a p.m.
kuma82 said:
I didn't have a hard time, but then again I've studied my a** off, and I knew how to fix all problems that popped up. My advice to you is read all the threads about unlocking the bootloader. The video is good but it doesn't break it down enough.
Let me tell you about everything that can go wrong and how to fix it
Problems
1. After flashing the euro kdz your phone won't boot past the logo.
Okay, this problem will make things harder(but do able), because you have to hard reset the device by pressing/holding the vol (-) + home + power (let go of power button when the lg logo comes up)
Plus after a hard reset all data will be wiped and you will have to enable USB debugging on the wonky touch screen.
The chance of this happening is rare because you are not coming from a custom ROM.
2. After flashing you get a security error (or an error during the flashing process).
Now this one sucks because you will need to fastboot and flash the ice cream u-boot. Then put the phone in the s/w upgrade mode and perform the offline flash again.
I had this happen to me once, while flashing the wind kdz. Messing with fastboot is not hard but it takes time to understand it. Get familiar with it first before trying to unlock. I'll send you a link with some more info.
3.After flashing the euro kdz you find out you don't have root.
Sometimes rooting fails (dam computers)
Now I had this happen to me after flashing euro kdz (so no cwm) but I wasn't really worried about that because I had a signal and I could make/receive calls. I had a signal because when I was flashing I swapped out the euro radio (p760.fls) with the metropcs one (lgms769.fls)
Note: you have to extract the radio from the metro kdz and rename it to p760.fls
When flashing replace the 11th bin (with hex edited 11th bin for 20b) & the radio (from metro renamed).
Another thing don't rush the unlock. I waited about 3 to 4 hours before trying, plus I took a couple of calls on the 20b kdz. And I was on wifi.
I flashed the euro kdz at work and when I got home I turned on WiFi and waited another hour.
I'm not to sure about what the video says about turning off and flashing the radio.
When the unlock first came out, the instructions were to not turn off the device before unlocking.
When I flashed the euro kdz I was on the metropcs ROM.
This is what I recommend and did.
Enable USB debugging, show all touches, & allow install from unknown sources.
Leave your phone on normally(don't put it in s/w mode) and flash the euro kdz and hopefully no problems.
After waiting a couple of hours try the unlock command with Adb on your PC.
If all goes good the phone will take you to an inverted unlock screen, just press the volume up (make sure you press the Up button!)
This will take you to the official fastboot (but it's inverted), now in fastboot flash the cwm recovery image.
In cwm flash the touch screen fix and restore a backup.
Another thing make your own backup with the locked bl cwm (just in case you have to erase all data) make backup on external SD. Another thing, Lol ,make sure the backup is good, try to restore it. I have had several corrupted backups with cwm.
I know it's a lot to learn, but then again you want to be prepared.
Think of it like a final exam, Lol and you won't go wrong.
If you get lost just holla at me.
Sent from my LG-P769 using xda app-developers app
Click to expand...
Click to collapse
CM 10.1 P769
kuma82 said:
Just be sure you are ready for everything,
I recommended flashing 20d then 20b.
Hold up I'll give you all the help I gave to someone in a p.m.
CM 10.1 P769
Click to expand...
Click to collapse
Wow man! Awesome response, really appreciate your input and explanations. It really takes some of the unknown out of it. Thanks!
Sent from my LG-P769 using xda app-developers app
httGeneric Procedure - Turn on " Fake Battery Mode " ( Bypass Genuine Battery Test ).
Boot Error ( " Use Genuine Battery " -power off- )
Entered here since procedure seems to be generic " Turn on Fake Battery Mode " (Bypass Genuine Battery Test).
>> Also called Service Menu: Type in: ##LGSERVICEMENU send (##5473784296368) on the dialpad.
>>enter the security code: 000000, locate: SW/HW Tests or HW test or SW/HW Versions
>> find "bypass booting" in menu locate "fake battery mode" select it and choose on.
--- My phone LG Optimus G Pro E980 (note: the 980 in code refers to model)
when approx 90-95%, with new gold 4200mAh battery Boot up Error ( " Use Genuine Battery " -power off- )
so, i went into hidden menu 3845#*980# ->Settings->Battery->Battery Fake Mode (Turned it ON), seems to be fixed.
By the way, the gold battery tested WORSE THAN 3140mAh OEM, Save yourself time, buy the Quality LG OEM.
Hey so this issue is actually solved. If you want to see the process that I went through to get to the solution, please do! Its not that hard, I promise. Maybe a little stressful, but totally doable. Cheers!
----------------------------------------------------------------
I'm currently stumped on how to fix this issue that I'm currently having with my HTC Rezound at the moment. I did not buy this from any Verizon retailer, I bought it online in 2012. Anyway, the only issue that I've had the past few months is just that my battery kept dying super quickly and that my phone would randomly shut off after flashing Liquid Smooth ROM on my phone. I originally live in California but I moved to Spain, so any option of "take it to a retailer" or "take it to a cellphone repair shop" is not practical since NOBODY in Granada has ever heard of this phone.
The last time I had my phone operational was when I was using Mobile Data to chat with one of my friends on an app when it died, as usual. This time, I wasn't home to immediately plug it into the charger. One other thing I'd like to point out is that the number one reason why I think my battery kept dying so quickly is that while I was in Morocco, I was using an adapter to charge my phone. Maybe the difference in voltage fried my battery, not sure.
Anyway, I was out for at least 3-4 hours before I finally got home to put it on the charger. I plugged it in and went to bed without even looking at my phone. Woke up the next morning to power it up to find that not even the orange light is on (or green when fully charged). I unplug it, plug it back in and nothing happens. I take out my battery, keep it out for a couple hours and put it back in. I hold the Power button until the phone vibrates, screen turns on with the green HTC logo on a white screen, and then turns off. I take out the battery a couple more times and still same thing. I decide to leave the battery out for 2 hours and then put it back into the phone and directly to charge. The orange light turns on for about 3-5 seconds before turning off.
If I try to push the power button, nothing happens unless I take out the battery again. So I leave the battery to charge but then my phone started to get a little warm. Instead I just disconnect and leave the battery out of the phone for about 3 weeks until I had 2 spare new batteries shipped to me here in Spain. Once I got the batteries, I tried once again to get my phone working by replacing the batteries. Orange light comes on for 3-5 seconds before going out and its the same thing as before. I plug it into my laptop, use the CMD "adb devices" and I get nothing listed or "error: device not found". I can only boot into hboot by using Power + Down Volume and thats about it. By the way, its S-OFF and rooted with a custom ROM (Liquid Smooth) and the recovery should be Amon Ra.
If I get to fastboot/hboot and I select Factory Reset, Recovery, or Reboot, the screen dims, vibrates a bit and flashes the HTC logo on a white screen for 3 seconds before turning off. As of now, I can't connect to my phone through the PC as it doesn't even read via USB port, HTC Sync doesn't read, and I can't reach my phone through CMD prompt. Does anyone have any information on how I could fix this? And even though I have read most articles about the orange light thing and clockworks recovery, I'm still open to any/all solutions.
Update #1
Since I have not gotten any help from any community members or from other people, I decided to pursue this on my own to the best of my abilities. I decided to start looking up different articles with the same symptoms that I have and to see what the solutions were. Long story short, I combined a few solutions and one of the things some people did was just reinstall stock ROM altogether. For now, I am happy to say that I can access my phone via Command Prompt, but ONLY with "fastboot" commands. I came to this realization when I was looking up how to install stock ROM when one of the commands was to put "fastboot reboot-bootloader" and I happily had much success. Just make sure you're in FASTBOOT USB or else it won't work. I also ended up reinstalling all my HTC Drives and HTC Sync. At the moment, I cannot access internal memory via USB nor connect to HTC Sync. Also, to see what other commands that are available to your disposal, you can type "fastboot help".
Update #2
Since the last post, I've been looking around. Found out that the best solution would be to flash a stock RUU onto the phone. Requirements before flash would be to erase everything but the only command I can get to erase is with "fastboot earse cache" and thats about it. Everything else is unsuccessful. Anyway, instead of just going straight to downloading and flashing stock RUU, I accidentally decided to try following a procedure I read step by step by first locking bootloader with the command "fastboot oem lock" command and phone immediately shuts off. I try to power on again but just does same as before: boots to green HTC logo on white, stays on a for a few seconds, and turns off. This time, though, without the bootloader coming up. I believe I have bricked my phone.
Can you still get to Fastboot? If so, unlock again, and then download the latest TWRP recovery, and try:
fastboot boot recovery.img
replace recovery.img with the name of the recovery image file for TWRP.
Once that is done, look at your mounts and see if you can access any partitions.
Update #3
acejavelin said:
Can you still get to Fastboot? If so, unlock again, and then download the latest TWRP recovery, and try:
fastboot boot recovery.img
replace recovery.img with the name of the recovery image file for TWRP.
Once that is done, look at your mounts and see if you can access any partitions.
Click to expand...
Click to collapse
Alright so right now I am EXTREMELY happy!!! Thank you so much for the advice. My phone happened to not get into fastboot anymore for some reason after I thought I bricked it. The final attempt I made before going to bed that night was to put my Micro SD into my phone and attempt to get into fastboot one last time and by some miracle my phone decided to. This is the steps I took to get my phone back operational so please excuse the length. At the moment, its not completely solved until I get my phone 100% operational, but this is what I have so far. I listed a few notes before I started so here goes.
Update #3:
HTC Rezound 2014:
- S-OFF and rooted with Liquid Smooth ROM and Amon Ra recovery
- fastboot oem LOCKED (no bootloader access available)
- batteries all low powered, 1 fried (3 total)
- when plugged, charging light turns on for 3-5 seconds and turns off without charging battery or
allowing phone to power back on; requires battery pull to restart process
- Power + volume normally takes to bootloader; recovery, factory reset, and reboot option fail
- when attempting to boot, phone will vibrate, power on to green HTC logo on white screen and then
turns off to black
- any attempts to turn on phone result in said description and requires battery pull after each attempt
Current issues:
Batteries are not fully charged
Cannot access bootloader because of last command in console, "fastboot oem lock"
PC cannot read devices despite drivers installed and fully working USB cord
Possible causes:
- Extra batteries just aren't fully charged to allow phone to fully boot
- System files are corrupted; no recovery, no boot.img, no OS; nothing for the phone to read to start up
Attempt 1:
- Plug phone with battery inside and cover off
- Clear memory off SD card
- Remove battery and insert SD Card
- Note: Battery has little to no power
- Plug into USB cord connected to computer
- Before orange light comes on, hold down Power + Down Volume
- Failed; repeat (unplug from phone, battery pull and reinsert)
- Attempt to leave battery to charge for 8 minutes via USB
- Charge attempt failed; orange light turns on for 3 seconds before turning off
Attempt 2:
- Remove phone cover, take out battery and reinsert
- Hold Power + Down Volume and go into Fastboot USB
- If successful, plug into PC via USB cable
- Open console (Shift + Right Click in folder AndroidSDK\platform-tools)
- For list of fastboot commands, type in the console (which should read slike C:\AndroidSDK\platform-tools\) "fastboot help" without quotations
- To make sure you are connected, type the command "fastboot reboot-bootloader"
- If the phone reboots into FASTBOOT USB after the command, then you're good
- Type in the command "fastboot devices" to make sure your devices can be read by your computer (should show up like HT18BY892363 fastboot)
- Since the last thing I did on my phone was "fastboot oem lock", use the command "fastboot oem unlock" and hope for success
- Command prompt will read something like:
...
<bootloader> [ERR] Command error !!!
OKAY [ 0.014s ]
finished. total time: 0.017s
- Type into command "fastboot oem get_identifier_token"
- Submit Identifier Token to HTC Dev (need to create an account)
- Download file and save in platform-tools folder with the adb.exe and fastboot.exe files
- Type "fastboot flash unlocktoken Unlock_code.bin" into console
- Select "Yes" option and phone will reboot as follows: vibrates, shows HTC logo on white screen for 3 seconds and turns off
- Unplug phone from USB, take out battery and reinsert
- Hold Power + Down Volume and boot into FASTBOOT USB; should read "*** UNLOCKED ***" at top of screen
- Using TWRP 2.8.0.1F, extract "recovery.img" into "platform-tools" folder
- Type command "fastboot boot recovery.img" and profit!
Glad you got it working!
acejavelin said:
Glad you got it working!
Click to expand...
Click to collapse
I actually have another issue now. I have managed to install TWRP onto my phone but when I attempt to flash a RUU I downloaded, I get this error:
Installing '/external_sd/PH98IMG.zip' . . .
Checking for MD5 file . . .
Skipping MD5 check: no MD5 file found
file_getprop: failed to stat "/system/build.prop": No such file or directory
E: Error executing updater binary in zip '/'external_sd/PH98IMG.zip'
Error flashing zip '/external_sd/PH98IMG.zip'
Updating partition details . . .
E: Unable to mount '/cache'
E: Unable to mount '/data'
E: Unable to mount '/system'
E: Unable to mount '/devlog
E: Unable to mount storage.
Your partition table is corrupted... Being S-Off you have an option, you need to run an EXE RUU, not flash a ph98img... I think the last one was 3.12.605.12 and you run it from a Windows PC with the phone in download mode... If that doesn't work only a JTAG programming can fix it, if it can be fixed. Once you get to this point that all partitions are not mountable, it is tough to recover, if it can be done at all. You have about a 50/50 chance at best.
acejavelin said:
Your partition table is corrupted... Being S-Off you have an option, you need to run an EXE RUU, not flash a ph98img... I think the last one was 3.12.605.12 and you run it from a Windows PC with the phone in download mode... If that doesn't work only a JTAG programming can fix it, if it can be fixed. Once you get to this point that all partitions are not mountable, it is tough to recover, if it can be done at all. You have about a 50/50 chance at best.
Click to expand...
Click to collapse
So how would I go about finding an EXE RUU? Do I just google "HTC Rezound 3.12.605.12 RUU exe"? And I apologize for the noobish questions, this is actually my first time getting this bad with my Rezound haha. I found this article (although it isn't associated with the phone) and was wondering if I should give it a try or not. http://forum.cyanogenmod.org/topic/6433-solved-messed-up-partitions-on-internal-storage/
shock_and_awe said:
...
E: Unable to mount '/system' <<<<<< THIS is the real problem
E: Unable to mount '/devlog
Click to expand...
Click to collapse
Without /system being mountable, or even formatable, there isn't much you can do..
Since ALL partitions are unmountable it likely means the PIT (Partition Information Table) for the internal 16GB storage area is corrupted and it needs to be recreated.
This MAY be fixable manually if you have a Linux machine, and understand the partitioning of THIS device... The Linux part I have no issue with, but I no longer own the is device and do not have a copy of the partition table to help you repartition it.
Honestly, for all the work involved, why not just grab a cheap phone online and use it? I mean you can get a Galaxy Nexus, a replacement Rezound, or a handful of other LTE devices for under $100 on swappa.com
acejavelin said:
Without /system being mountable, or even formatable, there isn't much you can do..
Since ALL partitions are unmountable it likely means the PIT (Partition Information Table) for the internal 16GB storage area is corrupted and it needs to be recreated.
This MAY be fixable manually if you have a Linux machine, and understand the partitioning of THIS device... The Linux part I have no issue with, but I no longer own the is device and do not have a copy of the partition table to help you repartition it.
Honestly, for all the work involved, why not just grab a cheap phone online and use it? I mean you can get a Galaxy Nexus, a replacement Rezound, or a handful of other LTE devices for under $100 on swappa.com
Click to expand...
Click to collapse
I see what you mean. Honestly I would get another phone if I could but I'm no longer living in the States, I'm studying in Spain. Shipping is super expensive so I'll have to go local or figure something out. Its the only phone I have at the moment but I'll most likely just get another phone for cheap. I really appreciate the help and the advice though. If anything, this will be my "side project" to work on when I'm SUPER bored and fix it for sh**s and giggles.
shock_and_awe said:
I see what you mean. Honestly I would get another phone if I could but I'm no longer living in the States, I'm studying in Spain. Shipping is super expensive so I'll have to go local or figure something out. Its the only phone I have at the moment but I'll most likely just get another phone for cheap. I really appreciate the help and the advice though. If anything, this will be my "side project" to work on when I'm SUPER bored and fix it for sh**s and giggles.
Click to expand...
Click to collapse
Spain has mostly GSM service, correct? Why not look into cheap devices locally? Amazon.es has several devices under 200 euros, Moto G, Moto E (89 euro), LG G2 mini, Xiaomi Red Rice, BQ Aquaris E5, etc... Or local classifieds online.
Update #4
SOLVED!!!
The solution (as it appears to be on a few success stories) is to completely install an Official Stock RUU. You just have to be content with losing ALL your data (if there was anything to save in the first places). What I ended up doing was using a microSD adapter this whole time and I would not have been able to get my phone back without it. This is what I did (following the installation of TWRP Recovery):
Official Stock RUU:
http://www.androidpolice.com/2012/0...ull-ruu-build-4-03-605-2-for-the-htc-rezound/
Update #4 (Final):
For this process I used a microSD adapter, in which I plugged into my laptop and put the required files in there.
- Download file from Android Police and rename to "PH98IMG.zip"
- Using your storage device (whatever way you choose just do this) put the .zip file onto the SD card
- Place the SD card into your phone and boot into HBOOT using Power + Down Volume
- Wait a few minutes until the PH98IMG.zip is finished loading and press Volume Up for "Yes" when asked "Do you want to start update?"
- After about 10-15 minutes, the phone will ask you to reboot the system
- Profit!!!
- Don't forget to remove the PH98IMG.zip file from your SD card or else every time you boot into HBOOT, it will reload the file
acejavelin said:
Spain has mostly GSM service, correct? Why not look into cheap devices locally? Amazon.es has several devices under 200 euros, Moto G, Moto E (89 euro), LG G2 mini, Xiaomi Red Rice, BQ Aquaris E5, etc... Or local classifieds online.
Click to expand...
Click to collapse
I actually JUST fixed my phone haha but yeah there are a few local mobile phone stores here (like Phone House) where they sell discounted phones. I appreciate all the help and thank you so much for everything. Above all else, thank you for sticking through with this post
Glad its working!