You know when you turn off your phone and you press the power button and bottom volume key at the same time and it brings you to a menu? Can someone tell what each thing means and does? Thankyou.
Sent from my PG06100 using Tapatalk
Which rom are you using?
i think he means where you get the white screen and it tells you if you have S-off and where you can click it get into recovery or bootloader. i would explain it to him but even i don't know what they all do
Its unrooted and stock. exactly corruption lol. Crap i really wanna know what all this stuff means
Sent from my PG06100 using Tapatalk
What would you like to know about in your bootloader?
Sent from my HTC Sensation Z710e
Everything except factory reset i obviously know what that is.
Sent from my PG06100 using Tapatalk
its stock recovery, theres nothing to know. its useless basically
At the top of the main screen:
SPEEDY XE etc talks about the model number and whether or not security is on.
HBOOT-0.93.2001 (PG0610000) says what version of HBOOT is running and the phone model in parentheses
RADIO-1.08.00.0506 tells you the current version of the radio firmware
eMMC-boot appears to correspond to the internal storage medium (eMMC for us)
Nov 15 2010,13:16:46 is, I'm guessing, the date of compile of the software.
FASTBOOT is a communication mode used to write to the phone's internal memory from the bootloader - you send files through it for higher-level access to the phone than what you get from recovery, I guess.
RECOVERY in its stock form is, as far as I know, used only to allow ROM updates to write to the phone. Unless you're rooted and installed a custom recovery - then, recovery allows you to write whatever you want to the phone. This menu option exits BOOTLOADER and starts RECOVERY.
The SIMLOCK setting probably can't do anything on our CDMA phones, but I imagine it's use on a GSM phone is related to disabling the carrier-specific SIM lock.
SYSTEM INFO will happily tell you things like your serial number and what pieces of hardware go into the phone
IMAGE CRC appears to calculate checksums on your hboot, boot, recovery, and system partitions.
If you select FASTBOOT to put the bootloader into fastboot:
BOOTLOADER takes you back to the main menu
REBOOT will restart the phone back to Android
REBOOT BOOTLOADER will restart the phone back into bootloader
POWER DOWN turns the phone off.
^^^
Couldn't be explained better.
Evo SHIFT
Thanks very much =]
There needs to be more people like you on here.
Sent from my PG06100 using Tapatalk
nurrwick said:
At the top of the main screen:
SPEEDY XE etc talks about the model number and whether or not security is on.
HBOOT-0.93.2001 (PG0610000) says what version of HBOOT is running and the phone model in parentheses
RADIO-1.08.00.0506 tells you the current version of the radio firmware
eMMC-boot appears to correspond to the internal storage medium (eMMC for us)
Nov 15 2010,13:16:46 is, I'm guessing, the date of compile of the software.
FASTBOOT is a communication mode used to write to the phone's internal memory from the bootloader - you send files through it for higher-level access to the phone than what you get from recovery, I guess.
RECOVERY in its stock form is, as far as I know, used only to allow ROM updates to write to the phone. Unless you're rooted and installed a custom recovery - then, recovery allows you to write whatever you want to the phone. This menu option exits BOOTLOADER and starts RECOVERY.
The SIMLOCK setting probably can't do anything on our CDMA phones, but I imagine it's use on a GSM phone is related to disabling the carrier-specific SIM lock.
SYSTEM INFO will happily tell you things like your serial number and what pieces of hardware go into the phone
IMAGE CRC appears to calculate checksums on your hboot, boot, recovery, and system partitions.
If you select FASTBOOT to put the bootloader into fastboot:
BOOTLOADER takes you back to the main menu
REBOOT will restart the phone back to Android
REBOOT BOOTLOADER will restart the phone back into bootloader
POWER DOWN turns the phone off.
Click to expand...
Click to collapse
You should give him a thanks!!!!! Cause i am
Sent from my HTC Sensation Z710e
No prob!
What I left out is why you might care about any of this...
All of the version numbering would be helpful in diagnosing problems with HTC support, assuming any of them ever did anything other than tell you to factory restore your phone and then hand you off to unresponsive second tier folks (not that I'm bitter...).
Checksumming can, if something weird is happening, tell you whether or not you have the same software you think you should. Again, also most useful in troubleshooting.
Fastboot is useful if you brick your phone most of the way (i.e. broken recovery image) or if you have an image file that needs to be pushed that way. It comes up every once in a while, but that's what the instructions to "put the phone into fastboot" are for.
Recovery, of course, is how you boot up to do nandroids and flash your lovely collection of .zip files, if you've rooted and installed a custom recovery.
One thing nobody really mentions is that booting into bootloader can also be a troubleshooting step on its own - it tells you the phone's screen and battery are still working and that at least there's enough life in the phone to run software. I also had luck with running stubborn RUUs on my old CDMA Hero by putting the phone in bootloader manually during the install process, so it has some practical value sometimes.
Related
I did all the steps to root the phone, 1 and 2, but got stuck in a bootloop. The sprint log stuff would come up, the the 4g, then back to sprint etc. I flashed the PC36IMG.zip of the shipped version, but now I can't get the RUU to take the phone into a fully factory state. It starts, then gets stuck waiting for bootloader with a black screen and htc on it. I really just want to make it factory again and start over with the root process. Any ideas?
Hold power and volume when turning on phone, then select fastboot and have the selection for bootloader highlighted, then start the RUU it should work then.
OK, so I tried the volume down + power btn deal, but still no dice. I really don't undestand wtf happened, cause before doing the 2nd part of root, I was able to load Damage ROM, now anything I load besides the PC36IMG.zip from part 1 just bootloops. Crazy
control_logic said:
I did all the steps to root the phone, 1 and 2, but got stuck in a bootloop. The sprint log stuff would come up, the the 4g, then back to sprint etc. I flashed the PC36IMG.zip of the shipped version, but now I can't get the RUU to take the phone into a fully factory state. It starts, then gets stuck waiting for bootloader with a black screen and htc on it. I really just want to make it factory again and start over with the root process. Any ideas?
Click to expand...
Click to collapse
ive seen this answered in the RUU threads. they mentioned the RUU doesn't automatically reboot the phone into the correct mode, i think it was bootloader? manually booting it into the correct mode, then connecting the USB, resolved the issue.
you might want to search/reference the RUU threads for more details as i never had the issue and am only recalling off the top of my head what ive read, which cant be 100% accurate!
When RUU stops/freezes and your phone has the black screen with "HTC" on it.... do not restart your phone or anything leave it the way it is. What you do is exit out of the RUU program by clicking "exit" when it freezes up. Then without doing anything to the phone, just restart the RUU program and it should pick up where it left off and complete the process. I found this fix in "Q and A" part of the Evo forum and it worked for me.
Sent from my PC36100 using Tapatalk
You need to format the phone rest and format cashe then install the rooted image and it will boot. I had the same problem.
Thanks for the responses, it is working again, YEAH!
So I have had this US beta streak since around January, the one that says 'Dell Confidential' at boot up, but it's never really worked correctly. I purchased it from a person that I know that got it through some sort of beta testing; the details weren't provided and I didn't press him for them. Anyways, I am currently trying to get the clockwork recovery flashed and able to be booted into, although the streak is giving me every possible problem I can imagine. I'll try to provide as much background info as I possibly can.
Firmware: 1.5
Baseband Version AUS_090716_01_BOSS_EVT2_3135
Kernel Version 2.6.27
Build Number QTC_3135
OEM Version: AustinBuild_090724_03_boss_evt2_3135_FixTouchSuspend
Under About Phone > Status
IMEI 011954000020995
IMEI SV 00
Service Tag FF8R6K1 (which dell.com cannot find)
The Problems:
When I try to get into bootloader to get into fastboot, by holding the camera button down while hitting the power button, rather than going into the screen that is shown in all of the different tutorial threads, I instead go into some sort of a diagnostic menu that doesn't have an option for fastboot, as much as I have seen. There is a picture attached below.
I (think) that I can get the phone recognized by adb, although I am not totally positive. When in cmd in windows, and I type adb devices, instead of getting the proper serial number of my devices, it shows instead 0123456789ABCDE (I may not have that exact, but it does start at 0 and ends in hex at E or F, I can't remember right now and don't have it connected at the moment.)
There was one time where I was able to flash recovery.clockwork.img to where it said that it successfully flashed the img, but when I go to try and boot into recovery by holding both volume up and down at the same time, and then hitting power, the phone just hangs at a blank, black screen. It will stay there for 30 minutes and not do a thing, I can't see it via adb or fastboot.
So I then gave recovery.alt.img a shot, was able to successfully flash that, or so it told me that it was successful, but still the same problem: just a black screen.
The reason that I think that it actually was working was that after flashing the recovery image both times, I sent the command adb reboot recovery, and the phone reboots, but not into recovery, just into android. adb reboot-bootloader doesn't work at all and returns an error or nothing, I can't remember.
I then focused my attention on trying to get fastboot to work, assuming that adb was not working at all. This is where fastboot gets strange. The only way for me to get the command 'fastboot devices' to show anything at all is by holding the volume down button prior and then hitting the power button to start it. This puts the phone into essentially a 'soft brick', which my friend calls 'safe mode', where it gets totally stuck at the 'Dell Confidential' screen and will not progress past it no matter what.
So, once I am in 'safe mode', I am able to then issue a 'fastboot devices' command, which ... partially works? I hope that my totally unsure tone of voice was able to be conveyed through that message, because the info returned once that command is sent is totally confusing to me. Unlike before, where I feel as though the Streak is just lying to me by saying 0123...DEF for the device ID, for fastboot devices it just gives me a question mark .. yes, simply a ?
The weird thing is that it will follow commands. I was able to flash recovery.clockwork.img to the streak, it gave me a read out that said successful, and I got very excited. And then I pulled the battery, put it back in, held both the volume buttons, and .... the same result, the black screen. So, not allowing myself to be deterred, I got right back into fastboot, or at least my quasi working version of fastboot which may not be working at all, and flashed recovery.alt.img, which turned around and told me that it was successful as well. This time, not allowing myself to get excited, I pulled the battery and, with both volume buttons held down, hit power to try to get into recovery.
Again, I was let down and found only a blank screen. At this point, I have no idea what else to try. With the bootloader not being where it's suppose to be, not really being able to get into fastboot or adb (I think), I turn to xda to try and find some answers. Does anyone have a suggestion as to what I am doing wrong or might be missing. I am hoping that it is something that is really obvious that I feel very stupid, like I'm hitting the wrong set of volume buttons, but ... I don't think it's that easy.
Again, I feel as though the phone was getting the commands from fastboot because I sent fastboot reboot recovery, and the phone rebooted, just not into recovery but android. Same thing for bootloader, it just didn't work at all
Also, as for android 1.5 itself, almost nothing works. This appears to be running a very early edition of android where most apps just end up with: Sorry! No applicatons can perform this action, so the One touch root is kind of out of the question.
I was able to do the dialer unlock method to get EMList, but the similarities end there. I don't have the Unknown sources option or anything else after leaving dialer.
Any and all suggestions are appreciated and will be accepted and followed (within reason). I'm just at the point where I'm hoping that it's not totally broken and that with determination and hard work and some critical thinking I (we) will be able to get it working again. Hopefully it isn't a paperweight.
Thanks,
Thursday
Hi
I had a problem with my htc magic after trying to flash the RA-sapphire-v1.0.0 recovery image into the phone. Before the problem occurred I rooted my phone and flashed RA-sapphire-v1.6.5, but because I had an issue with it I tried to flash an old version " RA-sapphire-v1.0.0".
Now my phone keeps rebooting endlessly and I can not access recovery mode, fastboot or anything else?
Is it bricked? Can I fix this issue?
The phone is 32A
Radio is 6.35 (I can not access fastboot so this is from my memory)
If you have no access to fastboot nor recovery, then you are pretty bricked!!!
Are you sure you can't get into fastboot? Pull the batter, press and hold down the back button, and put the battery back in. See if it goes into fastboot then. Do the same thing again, but holding the home button instead to see if you can get into recovery. I dunno why you used an old one and not the new one.
DonJuan692006 said:
Are you sure you can't get into fastboot? Pull the batter, press and hold down the back button, and put the battery back in. See if it goes into fastboot then. Do the same thing again, but holding the home button instead to see if you can get into recovery. I dunno why you used an old one and not the new one.
Click to expand...
Click to collapse
I tried both method and it did not work. The phone is still rebooting endlessly. I used the old recovery since the new one kept restarting the phone to the actual system after I go into recovery mode after 2-3 seconds.
1.6.5 isn't the new one. The newest version is 1.7.0. Well if that didn't work, then year your bricked.
so is there anything i can do to fix it?
JTAG is your only option.
Where are you from ?
usernome said:
Where are you from ?
Click to expand...
Click to collapse
I am from Australia
I have HTC Magic Vodafone (32B) and have a similar issue with phone in a reboot loop, however, i can get into fastboot but not sure what next to do. Is there a guide anywhere on what to recover my phone.
Depends, what is your current fastboot information?
Not sure what info you want from Fastboot screen so this is everything i can see
SAPPHIRE PVT 32B SHIP S-ON G
HBOOT-1.33.0013 (SAPP10000)
CPLD-10
RADIO-2.22.28.25
Oct 21 2009,22:33:27
Is this the right kind of information?
Two options. Downgrade to 1.5, then update to 1.6, then root, flash a custom ROM, reinstall the 1.33.0013 SPL and 2.22.28.25 radio, and then flash a new custom ROM. Optionally, you can downgrade to 1.5 and upgrade back up to 2.2.1. Either way just let me know and I can assist.
Thanks for you help with regards to the approach, is one easier than the other? If they are both roughly the same then would go for the Downgrade to 1.5 and upgrade back up to 2.2.1. route as it may be easier to sell in a few weeks when the Galaxy S2 out.
So, here we go, please read through all the steps before starting and then reading each step as you go along:
1. Go here and download "sappimg.nbh" and "update1-5.zip".
2. Put all of them on your SD card. I would suggest downloading to a folder on your computer, then copying them over. Have had issues in the pass with people downloading files directly to their SD card and it corrupting the file.
3. With the phone turn off and the SD card in it, boot holding (volume down+power) to get into hboot. The phone should detect the sappimg.nbh, check the file (you'll see a progress bar in the upper right-hand corner), and then ask you to hit "ACTION" to continue. (ACTION being pressing the trackball)
4. The phone will start flashing the different parts of the phones partitions. You'll see the progress bar in the upper right-hand corner a few more times, then after about 5 minutes, it'll ask you to hit "ACTION" again to reboot.
5. Let the phone boot all the way up (this may take a few minutes) and then turn it off without signing in.
NOTE: Unless you need the phone to access the SD card from the computer, in that case sign in and do the next step.
6. Access the SD card, find "update1.zip" and rename it to "update.zip".
7. With the phone off turn it back on by holding (home+power) to get into recovery. You'll see a triangle with an ! in it, press (home+power) again to bring up the menu.
8. Using the trackball, scroll to the "wipe data/factory reset" option and press the trackball to select it. After it completes, scroll to "apply update.zip from SD card" and select it. It should pickup the update file on the SD card and flash it, then reboot.
9. When you get to the login screen again, turn the phone off.
Note: Again, as before, you can optionally login to get into the ROM for access to the SD card from your computer.
10. Repeat steps 6-9 for the "update2-update5.zip" files. You will need to remove the old "update.zip" before renaming the next update file. When you get to the login screen the last time (after flashing "update5.zip") you can sign in and use the phone.
Thanks for the guide but I've hit a problem. The phone recognise the sappimg.nbh and starts to flash itself but when then a message:
model ID incorrect!
Update Fail!
appears and the flash has failed. I've tried this a few times now downloading the file again, formating the SD card etc but to no avail. Do you have any suggestion on how to get round this issue?
Geffen22 said:
Thanks for the guide but I've hit a problem. The phone recognise the sappimg.nbh and starts to flash itself but when then a message:
model ID incorrect!
Update Fail!
appears and the flash has failed. I've tried this a few times now downloading the file again, formating the SD card etc but to no avail. Do you have any suggestion on how to get round this issue?
Click to expand...
Click to collapse
Crap gave you the wrong sappimg. What country did you get the phone from?
Sent from my LG-P500 using Tapatalk
I got phone from Vodafone in the UK.
Geffen22 said:
I got phone from Vodafone in the UK.
Click to expand...
Click to collapse
Need the specific country.
United Kingdom or England to be exact.
I've had my htc panache (canadian mytouch 4g) for just one day, and it blew its fuse at me. When I went to sleep, it worked fine, but when I woke up, the screen was black and nothing was working. I pulled the battery out and plugged it back in, and now the phone is stuck at the HTC boot screen. I can get into hboot, but some options just don't work, and hangs the phone:
-REBOOT BOOTLOADER (from FASTBOOT menu)
-FACTORY RESET
-IMAGE CRC (hangs on "Calculating... please wait")
-RECOVERY (shows an image of two curved arrows with a regular arrow within, over a tilted cellphone, then the image is reversed, and the screen goes black and the phone vibrates exactly 7 times.)
I tried using the RUU, but my computer won't detect my phone either in hboot or recovery (not that it has the time to detect my phone in recovery). Perhaps I am missing drivers? the device manager shows the phone as a generic "USB Device".
I've tried to get into download mode, but the only other button combination aside from volume down + power that did anything was power + back button, and that brought me to hboot into the fastboot menu.
I tried to update the phone by putting the latest pd15img file from the wiki onto the sd card but after it scans the file, the phone doesn't ask me if I want to update. it just goes back to hboot, and rebooting hboot does the same thing.
How can I get into download mode, anyway?
EDIT: just found hboot drivers. something that works, for once.
Adb maby?
Sent from my LG-P970 using xda premium
wouldn't have been able to use adb if the phone wasn't detected, now was it?
anyway, I found some hboot drivers that seem to work. I'll try the ruu first.
Correct me if I'm wrong, but if I remember correctly the 7 vibrations while trying to enter recovery signifies hardware failure...
Sent from my myTouch 4G using XDA Premium HD app
Ok so... I managed to get the phone charged, and yet RUU still tells me my phone battery is charged at less than 30%, and I can only exit. what gives? Is there a way to bypass that?
(By the way, the hboot drivers I used were from a website called unrEVOked. perhaps these were for another model? where could I get hboot drivers for my phone?)
As for the hardware failure thing, I'm not buying it. at least not yet. If it trully were a hardware failure, the phone wouldn't boot, eh? I can get to hboot and fastboot and fiddle around for a bit, and recovery works for around 10 seconds before it goes blank at me.
So ADB doesn't see my phone but fastboot does. seeing how switching my phone to the fastboot menu installed htc's own drivers right away, I'm not surprised.
Where are the adb drivers for the glacier/panache/mytouch 4g? the only ones I could find are for motorola phones.
EDIT: "C:\sdk-tools>fastboot -p SH16KRM01484 -w
erasing 'userdata'... FAILED (status malformed (1 bytes))
finished. total time: 0.016s"
Try this thread for adb setup:
http://forum.xda-developers.com/showthread.php?t=928370
Also, did you have (flash) a recovery installed? If I remember right, a triangle around a phone when you enter recovery from hboot means you didn't have one installed/flashed. I also remember reading that 7 vibrates mean hardware failure. There are lots of phones that had failed emmc's and would still boot but get stuck at the splash screen. Are you verifying the md5 when downloading ruu?
http://www.htc.com/us/support/htc-mytouch-4g-tmobile/software-updates
That link is to the HTC drivers you're looking for. Once you get it set, you should be able to flash the RUU and I would suggest making sure you have a recovery flashed as well...would help a lot right now if you could at least get there.
Chomanator said:
http://www.htc.com/us/support/htc-mytouch-4g-tmobile/software-updates
That link is to the HTC drivers you're looking for. Once you get it set, you should be able to flash the RUU and I would suggest making sure you have a recovery flashed as well...would help a lot right now if you could at least get there.
Click to expand...
Click to collapse
It's the third driver I download, one was called htcdriver.exe, the second one was the same with a version number, and the third, this one, and none work. nothing happens when I click on them. on the task manager I see the process starting and just quitting for no reason.
I'm starting to think technology as a whole is against me.
I'm gonna try the drivers included with pdanet.
So after getting the right adb drivers...
"C:\sdk-tools>adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
C:\sdk-tools>"
nothing.
anyone?
(EDIT: fastboot started working. here's what getvar all gave me: )
C:\sdk-tools>fastboot getvar all
INFOversion: 0.5
INFOversion-bootloader: 0.89.0005
INFOversion-baseband: 26.09.04.26_M
INFOversion-cpld: None
INFOversion-microp: 0429
INFOversion-main: 2.10.1530.1
INFOserialno: SH16KRM01484
INFOimei: 357935045141682
INFOproduct: glacier
INFOplatform: HBOOT-7230
INFOmodelid: PD1510000
INFOcidnum: VIDEO001
INFObattery-status: good
INFObattery-voltage: 4183mV
INFOpartition-layout: Generic
INFOsecurity: on
INFObuild-mode: SHIP
INFOboot-mode: FASTBOOT
INFOcommitno-bootloader: 6a4abc53
INFOhbootpreupdate: 11
INFOgencheckpt: 0
all: Done!
finished. total time: 0.047s
I'm not sure if this can be helpful or not, but here.
It don't appear to be bricked...try flashing 4ext recovery.
Sent from my HTC Glacier
I tried to flash the phone using one of the pd15img.zip files, but I got the following error: "CID Incorrect!"
Does CID stand for Carrier ID?
So it shows you have s=on and latest gb hboot, so assuming you were running the stock rom. What was the last thing or things you did before plugging out in to go to sleep? Have you tried to select factory reset? If you only had the phone for 1 day, why don't you take it back to where you bought it?
ronin178 said:
So it shows you have s=on and latest gb hboot, so assuming you were running the stock rom. What was the last thing or things you did before plugging out in to go to sleep? Have you tried to select factory reset? If you only had the phone for 1 day, why don't you take it back to where you bought it?
Click to expand...
Click to collapse
Nothing. two hours before I went to sleep, I installed a few games and widgets, and everything went fine. I just quit what I was playing (some 3d racing game), put the phone on charge and went to bed.
Factory reset does nothing (the phone just hangs), and I can't return it because I got the phone from someone else (I doubt he's somehow responsible for this seeing how it's not the kind of defect you can just hide like that) and there was no warranty anymore on the phone, so I can't have it exchanged.
If I really can't do anything with that phone, I'll just sell it for parts on ebay I guess. but for now, I'm not giving up. I'm downloading the videotron ruu again, and will just put the zip file it extracts onto my sd card and rename it accordingly. Hopefully that will work.
I've downloaded the ruu, copied the rom.zip file from the temporary folder into my sd card, renamed it to pd15img.zip, and let it load in hboot. it asked me if I wanted to update, said yes, and it's stuck. I think it IS bricked, after all.
Parsing... [SD ZIP]
[1] BOOTLOADER -Updating
[2] BOOT
[3] RECOVERY
[4] SYSTEM
[5] SPLASH1
[6] USERDATA
[7] TP
[8] TP
[9] RADIO_VZ
[10] RADIO_CUST
Do you want to start update?
<VOL UP> Yes
<VOL DOWN> No
Update is in progress...
Do not power off the device!
Click to expand...
Click to collapse
It's stuck at where -Updating is, next to BOOTLOADER. I've left it there for 20 minutes now, and it hasn't budged. and I know that bootloaders aren't that big, unless the update is doing something fancy that makes it super slow, so... ****.
Is there a way to switch the phone to download mode? not hboot or recovery, but download mode.
adb just won't detect my phone :c
will somebody tell me how to put that phone into download mode?
Which RUU are you using?
Sent from my myTouch 4G using XDA Premium HD app
Hi, just bought a phone for my son secondhand, it's going to be sold again if I can't fix this! The phone was sold cheap as it had software issues (of course) so I figured I could fix these and get it going (install custom recovery, ROM etc). I'm slightly stumped at the moment, so maybe you can help me.
The phone's defaulting to the bootloader screen, lots of info on this but the key thing I noticed was that it says 'the device is locked status code: 2'.
Clicking 'start' takes me a 'warning unlocked bootloader screen' then it runs through the 'hello moto' startup screen and back to bootloader
Clicking 'recovery' - there is definitely no working recovery on it, I just a get the dead robot with 'no command' underneath.
Clicking 'Factory Mode' allows me so far through the startup (after the bootloader unlocked warning), and you can get so far through setting it up, but because the battery is so low (it's permanently on with the bootloader when plugged in) it never seems to charge up enough, and either way the screen freezes at or around the final setup steps and then it reverts back to bootloader. I thought if I got into developer options and security, I could enable the USB debugging, OEM unlock etc, but no go there.
I've installed Motorola USB drivers but it doesn't seem to be registering on the PC (Windows 10).
There is some suggestion on other forums (less reputable!) that the locked status code may mean the bootloader has been relocked, but this seems contrary to what the phone is telling me.
Any ideas welcome, thanks - it's a lovely phone, just not much use at the moment.
GitManMatt said:
Hi, just bought a phone for my son secondhand, it's going to be sold again if I can't fix this! The phone was sold cheap as it had software issues (of course) so I figured I could fix these and get it going (install custom recovery, ROM etc). I'm slightly stumped at the moment, so maybe you can help me.
The phone's defaulting to the bootloader screen, lots of info on this but the key thing I noticed was that it says 'the device is locked status code: 2'.
Clicking 'start' takes me a 'warning unlocked bootloader screen' then it runs through the 'hello moto' startup screen and back to bootloader
Clicking 'recovery' - there is definitely no working recovery on it, I just a get the dead robot with 'no command' underneath.
Clicking 'Factory Mode' allows me so far through the startup (after the bootloader unlocked warning), and you can get so far through setting it up, but because the battery is so low (it's permanently on with the bootloader when plugged in) it never seems to charge up enough, and either way the screen freezes at or around the final setup steps and then it reverts back to bootloader. I thought if I got into developer options and security, I could enable the USB debugging, OEM unlock etc, but no go there.
I've installed Motorola USB drivers but it doesn't seem to be registering on the PC (Windows 10).
There is some suggestion on other forums (less reputable!) that the locked status code may mean the bootloader has been relocked, but this seems contrary to what the phone is telling me.
Any ideas welcome, thanks - it's a lovely phone, just not much use at the moment.
Click to expand...
Click to collapse
OK, some progress, I have now unlocked the bootloader, so have the UNLOCKED Status Code:3 which is good, unfortunately has not yet helped with my issues. I can't use ADB, but MFastboot tool is working, so can run commands from that (hence me getting to that stage). Tried reinstalling firmware, may try and do this again now bootloader unlocked....
slightly further along...
GitManMatt said:
OK, some progress, I have now unlocked the bootloader, so have the UNLOCKED Status Code:3 which is good, unfortunately has not yet helped with my issues. I can't use ADB, but MFastboot tool is working, so can run commands from that (hence me getting to that stage). Tried reinstalling firmware, may try and do this again now bootloader unlocked....
Click to expand...
Click to collapse
I have now managed to flash stock firmwares using Mfastboot tool, but hasn't unfortunately fixed the boot up issues. However, I have now worked out how to access the recovery, by reading other posts on different Motorola phones:
boot to bootloader, power+vol down
in bootloader select recovery using the volume up/down buttons, press power button to select
phone boots into 'recovery,' showing the dead android with no command
at this point hold down the power and volume up, then release volume up but keep power held down
phones boots, by magic, into android recovery, where you can factory reset, wipe cache adb sideload and install from SD card
I now need to try and get a flashable recovery to sideload, as the attempts to flash it don't work for me. The OS I seem to be on is reteu 7.1.1, so I will try and go for a lower version, and see if that allows me to flash the custom recovery I desperately need.
But....things are improving slowly....:laugh:
GitManMatt said:
I have now managed to flash stock firmwares using Mfastboot tool, but hasn't unfortunately fixed the boot up issues. However, I have now worked out how to access the recovery, by reading other posts on different Motorola phones:
boot to bootloader, power+vol down
in bootloader select recovery using the volume up/down buttons, press power button to select
phone boots into 'recovery,' showing the dead android with no command
at this point hold down the power and volume up, then release volume up but keep power held down
phones boots, by magic, into android recovery, where you can factory reset, wipe cache adb sideload and install from SD card
I now need to try and get a flashable recovery to sideload, as the attempts to flash it don't work for me. The OS I seem to be on is reteu 7.1.1, so I will try and go for a lower version, and see if that allows me to flash the custom recovery I desperately need.
But....things are improving slowly....:laugh:
Click to expand...
Click to collapse
Never try to downgrade using stock firmware.
tyamamoto said:
Never try to downgrade using stock firmware.
Click to expand...
Click to collapse
OK thanks, I read that, but didn't realise it was a thing....should I be able to sideload a custom rom using ADB?