I am new here and I apologize if this is a repeat but I have spent hours reading threads and looking for a solution. If it's here I can't find it. Below is the screen I get when I turn it on. I've found threads that show the same screen but not how to fix it. I would like the simplest way to get it back working and booting again either to factory specs or to one of the mods. I have never flashed or rooting this phone and I need to find instructions that are step by step that I can follow. I've made sd cards for my nook before following instructions from here but I need them to be complete and thorough since I am not well versed. Any help will be greatly appreciated including pointing me to existing instructions if they exist because I can't find them.
I have a Droid Razr Maxx HD (XT 926) that failed. I have tried pretty much every suggestion that I could find to make it start up again without success. AT this point I can't tell you all the steps I have tried but I know I tried normal powerup, recovery, AP fastboot, factory and bp tools and nothing happens with any of them. I know at one point I got somewhere (hours of trying adn I no longer know all of what I have tried) where i had an option to format and recover or something like that. Yes i tried it and got nowhere. Yes go ahead and say I am in idiot because at this point I agree with you!!
When i power it on now I get the following screen - black background with white text:
AP Fastboot Flash Mode (S)
10.9B(*) (sha-1e9f557, 2013-05-25 01:04:26)
eMMC Info:Size 16gb
Device is LOCKED. Status Code: 0
Battery OK
Transfer Mode:
USB Connected
Failed to hab check for boot: 0x56
Fastboot Reason: Boot Failure
Any help is greatly appreciated as my wife's phone just died and we can't afford to buy a new one so i need to get this one back up and running. Thanks anyone and everyone.
"boot load selection menu" does nothing regardless of option selected
mspeter said:
I am new here and I apologize if this is a repeat but I have spent hours reading threads and looking for a solution. If it's here I can't find it. Below is the screen I get when I turn it on. I've found threads that show the same screen but not how to fix it. I would like the simplest way to get it back working and booting again either to factory specs or to one of the mods. I have never flashed or rooting this phone and I need to find instructions that are step by step that I can follow. I've made sd cards for my nook before following instructions from here but I need them to be complete and thorough since I am not well versed. Any help will be greatly appreciated including pointing me to existing instructions if they exist because I can't find them.
I have a Droid Razr Maxx HD (XT 926) that failed. I have tried pretty much every suggestion that I could find to make it start up again without success. AT this point I can't tell you all the steps I have tried but I know I tried normal powerup, recovery, AP fastboot, factory and bp tools and nothing happens with any of them. I know at one point I got somewhere (hours of trying adn I no longer know all of what I have tried) where i had an option to format and recover or something like that. Yes i tried it and got nowhere. Yes go ahead and say I am in idiot because at this point I agree with you!!
When i power it on now I get the following screen - black background with white text:
AP Fastboot Flash Mode (S)
10.9B(*) (sha-1e9f557, 2013-05-25 01:04:26)
eMMC Info:Size 16gb
Device is LOCKED. Status Code: 0
Battery OK
Transfer Mode:
USB Connected
Failed to hab check for boot: 0x56
Fastboot Reason: Boot Failure
Any help is greatly appreciated as my wife's phone just died and we can't afford to buy a new one so i need to get this one back up and running. Thanks anyone and everyone.
Click to expand...
Click to collapse
I spent another night reading threads looking for a solution without success. I believe by now I have lost everything including the OS so I need to find instructions for how to bring it back to ANY state, factory or CM anything. When i hold all three buttons down and the screen goes dark I release the power button (Still hold down both volumes) and eventually the "boot load selection menu" comes up. None of the options do anything except go back to AP Fastboot. Can anyone please help me with instructions for what to do to fix? Thanks for any assistance anyone can provide.
Install rsd lite 6.1.6, download your ROM from sbf android, don't recall the site name exactly. Install Motorola drivers. Flash it up while in boot mode.
That's a good start.
hbenz2008 said:
Install rsd lite 6.1.6, download your ROM from sbf android, don't recall the site name exactly. Install Motorola drivers. Flash it up while in boot mode.
That's a good start.
Click to expand...
Click to collapse
i downloaded all the files but before I proceed let me confirm you run RSD lite from a pc with teh phone connected right? I assume once that is done my droid menus will operate and I will be able to flash it from boot mode using 4.4.2? Like i said I have never done this before so i am trying to proceed caustiously so pardon my ignorance and hesitation if you can. And thanks again if you decide to stay with me and walk me through this.
Yes from pc while 926 is connected. Just make sure you have the right ROM for ur phone. Be back in few hours. Reverify, read, and proceed. You had stock on it before, flash stock then deal with update later.
hbenz2008 said:
Yes from pc while 926 is connected. Just make sure you have the right ROM for ur phone. Be back in few hours. Reverify, read, and proceed. You had stock on it before, flash stock then deal with update later.
Click to expand...
Click to collapse
I'm sorry I had to go out of town for three days but I;m back and unfortunately lost. I have been looking for an "SBF" file to use with RSDlite but maybe I have it and just don't know it because it's not called that. I downloaded several Motorola firmware files for my XT926. Below is the list of those files but none of them have a file type of SBF. Are these the right files?
Also when I run RSDlite and connect my phone it does not show up. When i click "show device" nothing happens. I unplugged and reconnect no luck. i shut down rsdlite and restarted no luck.
Android 4.0.4
Blur_Version.0.6.25.XT926.Verizon.en.US
Verizon US
605.3 MiB
433701B78701EFB5E5AA5D97BC9E07B5
Android 4.1.1
Blur_Version.9.1.41.XT926.Verizon.en.US
Verizon US
620.0 MiB
60D197DFEEB0DD3C138BB8E5DBA44FD6
Android 4.1.2
Blur_Version.9.16.6.XT926.Verizon.en.US
Verizon US
622.2 MiB
C17282528E409E1C4AE618DEFB5AE208
Android 4.1.2
Blur_Version.9.16.9.XT926.Verizon.en.US
Verizon US
621.0 MiB
4E25174CC00BC3B00CB3A53EAA510BE8
Android 4.1.2
Blur_Version.9.20.1.XT926.Verizon.en.US
Verizon US
626.7 MiB
B67F3A2D238BB9502FB82FCFBB89274D
Android 4.1.2
Blur_Version.9.30.1.XT926.Verizon.en.US
Verizon US
627.4 MiB
C374485427EFD219F4FBBEFE263267B5
Android 4.4.2
Blur_Version.183.46.10.XT926.Verizon.en.US
Verizon US
741.2 MiB
856606BFC7A74A473924954F67CC23C5
Hi :
Do you know what version was on your phone jelly bean 4.1.2 or kitkat 4.4.2? Anyway no harm trying to flash jelly bean:
Android 4.1.2
Blur_Version.9.30.1.XT926.Verizon.en.US
Verizon US
627.4 MiB
C374485427EFD219F4FBBEFE263267B5
Yor phone must be showing apfastboot, plus of course you must have motorola drivers installed on your pc in order for it to recognize your Droid.
hbenz2008 said:
Hi :
Do you know what version was on your phone jelly bean 4.1.2 or kitkat 4.4.2? Anyway no harm trying to flash jelly bean:
Android 4.1.2
Blur_Version.9.30.1.XT926.Verizon.en.US
Verizon US
627.4 MiB
C374485427EFD219F4FBBEFE263267B5
Yor phone must be showing apfastboot, plus of course you must have motorola drivers installed on your pc in order for it to recognize your Droid.
Click to expand...
Click to collapse
Thanks for your help. no unfortunately I don't know what version it used to be on. So you are pointing out the file i should run so thanks. i will see if i can run that in rsdlite and maybe get somewhere wtih this. back in a few.
That is at least a safe manoeuvre. It won't kill ur phone
hbenz2008 said:
That is at least a safe manoeuvre. It won't kill ur phone
Click to expand...
Click to collapse
ran the file using rsdlite and it decompressed apparently fine. It says for phone model "VANQUISH_CFC_IFLASH" and I don't know that is right. I have a XT926 Razr Maxx HD. My device does not show up in the device window and when I press the start button nothing appears to happen I presume because my phone does not show up in the window? Not sure how to proceed at this point?
Extract your download to a folder in your desktop. Make sure you point rsd lite to the xml file on the extracted folder. Let it do the rest. Did you download Motorola drivers?
hbenz2008 said:
Extract your download to a folder in your desktop. Make sure you point rsd lite to the xml file on the extracted folder. Let it do the rest. Did you download Motorola drivers?
Click to expand...
Click to collapse
i created a folder on my desktop, copied the file to it, ran rsdlite and it decompressed again (this time to that folder I assume) and i then selected the xml file. no device shows up yet and select the show device button does nothing. i then press start and again it seems to do nothing. the file properties box is filled in with info such as file name creation date size version etc. so that looks good. To me it appears to not be able t find the phone to run it on. the phone is in the AP Fastboot Flash mode screen - is this the correct place for the phone to be at?
also i have not downloaded drivers yet. I have downloaded some files based on other threads such as build files, somethign KITKAT, latest CM build from 20140918 and who knows what else at this point. I hae not used anything yet other than the xml you are having me try to run.
Google Motorola drivers 2.4.5 or go to MoTo website. Gotta have drivers for the pc to recognize the phone
---------- Post added at 04:14 PM ---------- Previous post was at 04:09 PM ----------
https://motorola-global-portal.custhelp.com/app/answers/detail/a_id/88481
---------- Post added at 04:14 PM ---------- Previous post was at 04:14 PM ----------
Download, reboot and try again
hbenz2008 said:
Google Motorola drivers 2.4.5 or go to MoTo website. Gotta have drivers for the pc to recognize the phone
---------- Post added at 04:14 PM ---------- Previous post was at 04:09 PM ----------
https://motorola-global-portal.custhelp.com/app/answers/detail/a_id/88481
---------- Post added at 04:14 PM ---------- Previous post was at 04:14 PM ----------
Download, reboot and try again
Click to expand...
Click to collapse
AWESOME. phone is now recognized so i am decompressing again and set it to flash when complete. Fingers crossesd and THANK YOU for getting me this far!! First Time i have felt maybe some progress.
Cool man, it will come back to life and be better than what it was.
mspeter said:
AWESOME. phone is now recognized so i am decompressing again and set it to flash when complete. Fingers crossesd and THANK YOU for getting me this far!! First Time i have felt maybe some progress.
Click to expand...
Click to collapse
Failed the flash. Info is as follows
Model= Fastboot Vanquish S
Port=1
Port type - USB
IME/ESN/MEID=n/a
Status = Failed flashing process. 2/29 flash sbl1 "sbl1.mbn"-> Phone returned FAIL
Result-Fail
There is a work around. What s the 2/29 on rsd lite say exactly?
---------- Post added at 04:30 PM ---------- Previous post was at 04:25 PM ----------
The xml file needs editing. But need to Know the exact error. Xml gets edited by note pad. Easy process
---------- Post added at 04:34 PM ---------- Previous post was at 04:30 PM ----------
Remove this Line between < get Var > and try again. Keep a fresh xml saved somewhere in ur pc
hbenz2008 said:
There is a work around. What s the 2/29 on rsd lite say exactly?
---------- Post added at 04:30 PM ---------- Previous post was at 04:25 PM ----------
The xml file needs editing. But need to Know the exact error. Xml gets edited by note pad. Easy process
---------- Post added at 04:34 PM ---------- Previous post was at 04:30 PM ----------
Remove this Line between < get Var > and try again. Keep a fresh xml saved somewhere in ur pc
Click to expand...
Click to collapse
It says precisely what I posted above - Failed flashing process. 2/29 flash sbl1 "sbl1.mbn" - > Phone returned FAIL
Remove line I posted above. Take the whole line. < >
hbenz2008 said:
Remove line I posted above. Take the whole line. < >
Click to expand...
Click to collapse
opened the file in notebook
found the line that mentioend sb1 adn i deleted it all leaving only the <>
selected "save as" and the file type option was text file
opened rsdlite again and when I selected the modified file box pops up saying ?PLease check input file. Either XML format is wrong or image files asociated with it are missing"
went back in and got rid of the open and close carrots and re-ran rsdlite
ran longer and i got a few beep tones but still failed.
this time it says
Failed Flashing process. 10/28 flash partition "gpt_main0.bin" - > Phone returned FAIL
Related
I was trying to SBF back to Android 2.3.4 because I wanted to load a custom ROM on my X2. I had the original Android (Version 2.3.5) rooted.
I followed the directions on another thread on this site and now I am stuck. I followed everything that this guide told me to do and up until Step 16, which says,
The Progress and Result columns will update with information as the flash progresses. When the flash is complete, the phone will reboot and RSD Lite SHOULD inform you that the process is complete. If not, you might have to do the process over. You may also receive a message to manually reboot your phone, this is normal and seems to happen about 30-40% of the time.
Click to expand...
Click to collapse
Everything was running fine until I noticed that the RSD Lite was stuck on 99% and saying "Switching phone to BD Mode" (not sure about it actually saying BD it might have been BP or something). My phone then booted up and it says. Failed to Boot 1. I have searched around the forums and other websites and I am lost. I cant even turn the phone on with the power button. I have to plug it into an outlet and then unplug it but it never loads past the "Failed to Boot 1" with the Motorola Icon in the middle. Please help me members of XDA-Developers I am in need.
Is my phone bricked? Or is it savable?
If it IS savable I would like to know what my options are... and how to fix this issue.
Also thanks for taking the time to read this. I hope someone here can help me with this issue.
This is the original link below.
http://forum.xda-developers.com/showthread.php?t=1317707
bbgun_2006 said:
I was trying to SBF back to Android 2.3.4 because I wanted to load a custom ROM on my X2. I had the original Android (Version 2.3.5) rooted.
I followed the directions on another thread on this site and now I am stuck. I followed everything that this guide told me to do and up until Step 16, which says,
Everything was running fine until I noticed that the RSD Lite was stuck on 99% and saying "Switching phone to BD Mode" (not sure about it actually saying BD it might have been BP or something). My phone then booted up and it says. Failed to Boot 1. I have searched around the forums and other websites and I am lost. I cant even turn the phone on with the power button. I have to plug it into an outlet and then unplug it but it never loads past the "Failed to Boot 1" with the Motorola Icon in the middle. Please help me members of XDA-Developers I am in need.
Is my phone bricked? Or is it savable?
If it IS savable I would like to know what my options are... and how to fix this issue.
Also thanks for taking the time to read this. I hope someone here can help me with this issue.
This is the original link below.
http://forum.xda-developers.com/showthread.php?t=1317707
Click to expand...
Click to collapse
If i remember right failed to boot 1 means the bootloader is corrupt or didnt flash properly. at that point it should default to rsd mode. my recomendation is retrying to sbf or follow this. that or find the bootloader .img and load it through fastboot.
failing and switch to bp, is often a drivers issue
fix drivers, read drivers issues in my list or use the ezSBF link
sd_shadow's [Collection] of Links for Droid X2
Sent from my XT862 using Tapatalk 2
sd_shadow said:
failing and switch to bp, is often a drivers issue
fix drivers, read drivers issues in my list or use the ezSBF link
sd_shadow's [Collection] of Links for Droid X2
Sent from my XT862 using Tapatalk 2
Click to expand...
Click to collapse
I thought that too but I went and I downloaded the most updated Motorola drivers from their website and still nothing. I could originally get the phone to boot in RSD mode but since my 'no power' issues I cant even get it to that now.
Lrs121 said:
If i remember right failed to boot 1 means the bootloader is corrupt or didnt flash properly. at that point it should default to rsd mode. my recomendation is retrying to sbf or follow that or find the bootloader .img and load it through fastboot.
Click to expand...
Click to collapse
OK I downloaded the iso file and burned it onto a CD and I have boot up my computer but my phone won't turn on when I plug it into a USB port when I am running the Linux Live CD with the SBF files on it. My phone however will turn on when I plug it into an outlet but about 2-3 seconds after I unplug the phone it shuts itself off. Also even when it is plugged into a wall outlet it still says "Failed to Boot 1". I have been trying to fix it but I haven't been able to figure it out. I was hoping that it would work but since I have tried everything that I could think of and still no results I decided to come back and ask for help with this too.
Thank you again for taking the time to look at this I am getting dire here.
missed that you have a milestone, which carrier?
and which sbfs have you tried
Sent from my Clear using Tapatalk 4 Beta
---------- Post added at 01:22 AM ---------- Previous post was at 01:19 AM ----------
do you have a spare battery? does it go into charge screen ?
Sent from my Clear using Tapatalk 4 Beta
---------- Post added at 01:41 AM ---------- Previous post was at 01:22 AM ----------
just reinstalling drivers may not fix driver errors did you read my drivers issues section in my list
sd_shadow's [Collection] of Links for Droid X2
what model is on label under battery?
---------- Post added at 01:51 AM ---------- Previous post was at 01:41 AM ----------
MB870 or MB867?
If you have the mx2 follow this guidehttp://forum.xda-developers.com/showthread.php?t=2101633
Sent from my SCH-I535 using xda premium
I have a tablet with this SoC Allwinner A83T. Its like a generic tablet (OEM) q102a. It has Android 5.1.1 what I managed to root with KingRoot. I followed this to replace KingRoot with SuperSU, and the device stuck in bootloop. Any help/solution would be appreciated. The tablet can go to recovery, but its an android recovery not custom. There is no ADB, ( adb cant see the device) and only what i found is .img image what I cant flash.
I found several frimware in here but dont know how can I flash it.
You can try Phoenixsuit this Flash tool.do you get rom?
52571abc said:
You can try Phoenixsuit this Flash tool.do you get rom?
Click to expand...
Click to collapse
yeah nice advice
hi
If you guys has any problem can ask me
cuz I flash my A31s tablet it was success!
i have that soc and trying to access boot loader just show the SPC logo and stay there.
the command 'C:\adb>fastboot.exe oem device-info
< waiting for device >
' isnt working.
help ?
Can you show me the photo?
For the SPC tablet dude (not the q102a), I found the original firmware for mine (Dark Glow model), it has only 2 buttons at the right side, Power and Back.
I can't post URLs, but just google for A83T_N102_N1021L1BC_20151123.img and you should find the location.
There are several firmwares there, check your model for the correct one!
Then flash it with PhoenixSuit and you are good to go!
If more help needed, just say it.
---------- Post added at 01:04 PM ---------- Previous post was at 12:24 PM ----------
Libi_79 said:
I have a tablet with this SoC Allwinner A83T. Its like a generic tablet (OEM) q102a. It has Android 5.1.1 what I managed to root with KingRoot. I followed URL to replace KingRoot with SuperSU, and the device stuck in bootloop. Any help/solution would be appreciated. The tablet can go to recovery, but its an android recovery not custom. There is no ADB, ( adb cant see the device) and only what i found is .img image what I cant flash.
I found several frimware in URL but dont know how can I flash it.
Click to expand...
Click to collapse
To flash the .img with PhoenixSuit (though I'm sure there are better tutorials out there):
Download and install PhoenixSuit in your PC (version I tried 1.0.0.1).
Open it; in the Firmware tab, browse the .img file and select it. If you click Upgrade, the program will say the device is not connected and it will show you instructions on how to put the tablet in Upgrade Mode, which I'll say now. Make sure the tablet battery is full.
With the tablet shut down, press and keep holding the volume buttons (+ and -, in case it has no volume buttons, any other buttons that are not the power button).
While pressing them, connect the tablet with the USB cable, then press the power button at least 10 times until your computer recognizes a new hardware. You can now release all buttons. Allow installation of this new hardware.
If it went OK, then PhoenixSuit should automatically recognize it and a window will appear asking to format, say Yes to all and wait for flash to finish. It should say Succeed at the end. You can now unplug the tablet, close PhoenixSuit and wait till the tablet starts up on its own (it can take some minutes with a new installation ).
GiantChicken said:
For the SPC tablet dude (not the q102a), I found the original firmware for mine (Dark Glow model), it has only 2 buttons at the right side, Power and Back.
I can't post URLs, but just google for A83T_N102_N1021L1BC_20151123.img and you should find the location.
There are several firmwares there, check your model for the correct one!
Then flash it with PhoenixSuit and you are good to go!
If more help needed, just say it.
---------- Post added at 01:04 PM ---------- Previous post was at 12:24 PM ----------
To flash the .img with PhoenixSuit (though I'm sure there are better tutorials out there):
Download and install PhoenixSuit in your PC (version I tried 1.0.0.1).
Open it; in the Firmware tab, browse the .img file and select it. If you click Upgrade, the program will say the device is not connected and it will show you instructions on how to put the tablet in Upgrade Mode, which I'll say now. Make sure the tablet battery is full.
With the tablet shut down, press and keep holding the volume buttons (+ and -, in case it has no volume buttons, any other buttons that are not the power button).
While pressing them, connect the tablet with the USB cable, then press the power button at least 10 times until your computer recognizes a new hardware. You can now release all buttons. Allow installation of this new hardware.
If it went OK, then PhoenixSuit should automatically recognize it and a window will appear asking to format, say Yes to all and wait for flash to finish. It should say Succeed at the end. You can now unplug the tablet, close PhoenixSuit and wait till the tablet starts up on its own (it can take some minutes with a new installation ).
Click to expand...
Click to collapse
I have some device
---------- Post added at 09:38 AM ---------- Previous post was at 09:37 AM ----------
52571abc said:
I have some device
Click to expand...
Click to collapse
I can help you
---------- Post added at 09:44 AM ---------- Previous post was at 09:38 AM ----------
52571abc said:
I have some device
---------- Post added at 09:38 AM ---------- Previous post was at 09:37 AM ----------
I can help you
Click to expand...
Click to collapse
Same device (wrong word sorry)
52571abc said:
I have some device
---------- Post added at 09:38 AM ---------- Previous post was at 09:37 AM ----------
I can help you
---------- Post added at 09:44 AM ---------- Previous post was at 09:38 AM ----------
Same device (wrong word sorry)
Click to expand...
Click to collapse
????
The HIPO A106T Android 5.1 has the same processor. Can I root it do you think?
baconboy said:
The HIPO A106T Android 5.1 has the same processor. Can I root it do you think?
Click to expand...
Click to collapse
I think you can try kingroot first
52571abc said:
I think you can try kingroot first
Click to expand...
Click to collapse
Is you tablet board look like this?
Has anyone found a modified (for this 9 inch Supersonic/Allwinner A83 1024*600) recovery? I've gotten the recoveries (TWRP) for an X10 tablet to flash, but the touch screen is inoperative.
try kingroot first
baconboy said:
The HIPO A106T Android 5.1 has the same processor. Can I root it do you think?
Click to expand...
Click to collapse
you can try kingroot first if you get root you can backup you rom first
rom backup teach :https://www.youtube.com/watch?v=C59zFu63BDU
---------- Post added at 02:50 PM ---------- Previous post was at 02:46 PM ----------
actionville said:
Has anyone found a modified (for this 9 inch Supersonic/Allwinner A83 1024*600) recovery? I've gotten the recoveries (TWRP) for an X10 tablet to flash, but the touch screen is inoperative.
Click to expand...
Click to collapse
can you show me your tablet photo or website\
I hate to open this thread back up, but I have acquired a chinese tablet A83t-N106. I got this from a business close out purchase.
I was some type of customer loyalty program. The screen worked but had a limited android OS on it. I used the PhoenixSuite to access the details.
I found this was the OS installed "A83T_N106_N1061L6BC_20160309-ok.img" I found this from a Chinese website. I flashed it without any error. I cannot get the screen to show anything. If i connect to my computer it sees the device and I can move/delete/add files to the files system.
I have updated my old script to root ZVB as well as ZVA. This should solve issues that some people were having.
Just extract the zip file, run the .bat file and follow the instructions. Should be pretty simple. Let me know if you run into any problems.
Note: If you are having issues with the script hanging try unplugging your phone and plugging it back in. That should help.
Prerequisites:
Code:
adb debugging
LG drivers
Diag mode enabled ##diag (makes things easier but you can do without it, eg. manual reboots.)
Reserved
I have yet to be able to root my G3. The files get pushed over to the device but after reboot I have to manually boot it into download mode but then the device never gets recognized by the script.. I am running Windows 10 and wonder if that could have an effect on how the LG drivers work??
wpmetts said:
I have yet to be able to root my G3. The files get pushed over to the device but after reboot I have to manually boot it into download mode but then the device never gets recognized by the script.. I am running Windows 10 and wonder if that could have an effect on how the LG drivers work??
Click to expand...
Click to collapse
Yeah you might need to update your drivers in device manager once in download mode (searching automatically for the best driver should do the trick)
wpmetts said:
I have yet to be able to root my G3. The files get pushed over to the device but after reboot I have to manually boot it into download mode but then the device never gets recognized by the script.. I am running Windows 10 and wonder if that could have an effect on how the LG drivers work??
Click to expand...
Click to collapse
On line 27 in the bat file, change
Code:
adb reboot
to
Code:
adb reboot download
.
That worked for me.
Tried on Windows 10 and Windows 7 machines, After I manually put my phone into download mode (will not go into download mode automatically) the script detects my phone and I get "Author : blog.lvu.kr
SPECIAL COMMAND : ENTER, LEAVE
#"
Then the script just stops with nothing else happening, I've let it sit for 30 minutes thinking it was doing something but nothing. Any suggestions on what to do. My phone and sd card are encrypted, could this be causing the issue?
Out2kill said:
Tried on Windows 10 and Windows 7 machines, After I manually put my phone into download mode (will not go into download mode automatically) the script detects my phone and I get "Author : blog.lvu.kr
SPECIAL COMMAND : ENTER, LEAVE
#"
Then the script just stops with nothing else happening, I've let it sit for 30 minutes thinking it was doing something but nothing. Any suggestions on what to do. My phone and sd card are encrypted, could this be causing the issue?
Click to expand...
Click to collapse
Yes an encrypted phone/sdcard is probably the issue.
Sorry for the nooby question, but will autorec work after using this to root ZVB? I'm about to get a new device through insurance and world hate to only have root and not custom recovery.
golpeen420 said:
Sorry for the nooby question, but will autorec work after using this to root ZVB? I'm about to get a new device through insurance and world hate to only have root and not custom recovery.
Click to expand...
Click to collapse
no autorec doesn't work.. but you can use twrp manager (free on google play) or flashimg.
l33tlinuxh4x0r said:
no autorec doesn't work.. but you can use twrp manager (free on google play) or flashimg.
Click to expand...
Click to collapse
Oh wow, had no idea twrp manager supported this device now. That makes things so much easier. Cause I just ordered my new device today and it'll probably come stock with ZVB. Thanks for the info, really thought id be doomed to stock for a minute there.
Bought a G3 from someone off Craigslist last night & used this earlier today to gain root & it worked perfectly. Thanks for sharing!
So when I run the bat file, it just says waiting for device, but my device is plugged in and I know the drivers are installed, even installed them again to be sure and still nothing, and advice?
---------- Post added at 10:50 PM ---------- Previous post was at 10:34 PM ----------
nevermind, I got it
This method worked for me, thanks!!! @l33tlinuxh4x0r your the man, thanks for sharing your knowledge with the community and helping others. After trying several other root methods and having none of them work this root method actually worked! I have a LGLS990 LG G3 32GB SPRINT Shine Gold Smartphone. Goodbye Sprint / LG bloatwear and hello new xda gear!
One tip I can give is towards the end you need to unplug the USB cable, power off your phone and manually go into download mode again. The script doesn't prompt you to do that action but I figured it out when I kept getting stuck at around 90%. After I put my phone into download mode manually and reconnected the USB the root completed and SuperSU was installed. I am now running CloudyG3_2.5 and it's working flawlessly, thanks again.
i have tried this rooting method and it gets to the point after entering download mode the command script recognizes it goes to the next step then the command prompt just closes out.....what the heck is going on there? its done that repeatedly every time it hits that step
Jamesredmond82 said:
i have tried this rooting method and it gets to the point after entering download mode the command script recognizes it goes to the next step then the command prompt just closes out.....what the heck is going on there? its done that repeatedly every time it hits that step
Click to expand...
Click to collapse
I am having the same issue after entering download mode the command script recognizes it goes to the next step then the command prompt just closes out... any help will be appreciated.
Duplicate
---------- Post added at 03:58 PM ---------- Previous post was at 03:56 PM ----------
Jamesredmond82 said:
i have tried this rooting method and it gets to the point after entering download mode the command script recognizes it goes to the next step then the command prompt just closes out.....what the heck is going on there? its done that repeatedly every time it hits that step
Click to expand...
Click to collapse
You can use this method, i just rooted my LG G3 using mathod B on the link below.
http://forum.xda-developers.com/spri...stock-t3211878
hkhan1 said:
Duplicate
---------- Post added at 03:58 PM ---------- Previous post was at 03:56 PM ----------
You can use this method, i just rooted my LG G3 using mathod B on the link below.
http://forum.xda-developers.com/spri...stock-t3211878
Click to expand...
Click to collapse
your link didnt work
http://forum.xda-developers.com/spr...990-zvb-root-method-zvb-rooted-stock-t3211878
On this forum go to page number 5 for instructions.
Try this link, this should work.
Rooted a brand new LG G3 sold for Boost Mobile with this method. Lollipop v 5.0.1
twelfth said:
Rooted a brand new LG G3 sold for Boost Mobile with this method. Lollipop v 5.0.1
Click to expand...
Click to collapse
how exactly did you go about doing this?
Hi
could someone please send me stock rom for Alcatel pop 4, My phone is stuck on Alcatel logo after installing a theme and i have tried everything but i can't find a rom anywhere on internet.
Thank You
I have the same problem and I can´t find any.
GolpeadorMágico said:
I have the same problem and I can´t find any.
Click to expand...
Click to collapse
I have managed to fix it with software upgrade tool.
if u need any help fixing yours let me know
JordieSnipezHD said:
I have managed to fix it with software upgrade tool.
if u need any help fixing yours let me know
Click to expand...
Click to collapse
Yes, please. I try to recover it with the "mobile upgrade" and that not work.
GolpeadorMágico said:
Yes, please. I try to recover it with the "mobile upgrade" and that not work.
Click to expand...
Click to collapse
I could upload twrp backup if help
mygadgetgeek.com said:
I could upload twrp backup if help
Click to expand...
Click to collapse
Please, I´m going to try anything for recover it.
GolpeadorMágico said:
Please, I´m going to try anything for recover it.
Click to expand...
Click to collapse
OK u have to give me bit time I had same problem I wiped mine and couldn't recover it I got another pop 4 backed it up and restore on mine u do need a backup of any kind of your phone as u have to copy my backup into it I try write instructions what I done
---------- Post added at 12:12 AM ---------- Previous post was at 12:10 AM ----------
mygadgetgeek.com said:
OK u have to give me bit time I had same problem I wiped mine and couldn't recover it I got another pop 4 backed it up and restore on mine u do need a backup of any kind of your phone as u have to copy my backup into it I try write instructions what I done
Click to expand...
Click to collapse
Will say I looked on net and tried mobile q and nothing worked just handy I got another phone
---------- Post added at 12:13 AM ---------- Previous post was at 12:12 AM ----------
mygadgetgeek.com said:
OK u have to give me bit time I had same problem I wiped mine and couldn't recover it I got another pop 4 backed it up and restore on mine u do need a backup of any kind of your phone as u have to copy my backup into it I try write instructions what I done
---------- Post added at 12:12 AM ---------- Previous post was at 12:10 AM ----------
Will say I looked on net and tried mobile q and nothing worked just handy I got another phone
Click to expand...
Click to collapse
I will never buy another there's no development or ROMs nothing I have installed exposed and root
mygadgetgeek.com said:
OK u have to give me bit time I had same problem I wiped mine and couldn't recover it I got another pop 4 backed it up and restore on mine u do need a backup of any kind of your phone as u have to copy my backup into it I try write instructions what I done
---------- Post added at 12:12 AM ---------- Previous post was at 12:10 AM ----------
Will say I looked on net and tried mobile q and nothing worked just handy I got another phone
---------- Post added at 12:13 AM ---------- Previous post was at 12:12 AM ----------
I will never buy another there's no development or ROMs nothing I have installed exposed and root
Click to expand...
Click to collapse
Yeah, this mobile sucks. My mom lend me it and its horrible. I lost the system (you know) and the mobile update (Alcatel) don´t do any. I put it, the mobile sometimes its not recognized... No more. Alcatel, not again.
mygadgetgeek.com said:
I could upload twrp backup if help
Click to expand...
Click to collapse
if you could that would be amazing. I am stuck in a locked bootloader and fastboot doesn't detect the phone (altough adb does) so I cannot unlock it.
zbaracki said:
if you could that would be amazing. I am stuck in a locked bootloader and fastboot doesn't detect the phone (altough adb does) so I cannot unlock it.
Click to expand...
Click to collapse
Can u get into twrp recovery
mygadgetgeek.com said:
Can u get into twrp recovery
Click to expand...
Click to collapse
yes.
I tried to flash supersu from twrp and since then I'm stuck in bootloader (couldn't unlock bootloader due to fastboot not seeing the phone). I still can get to recovery, but can't boot up the system.
Alcatel's Mobile Upgrade Q doesn't work for me either (tried on 2 different PC's).
I hope restoring clean non-rooted boot/system will help, if somebody can share the backup files.
zbaracki said:
yes.
I tried to flash supersu from twrp and since then I'm stuck in bootloader (couldn't unlock bootloader due to fastboot not seeing the phone). I still can get to recovery, but can't boot up the system.
Alcatel's Mobile Upgrade Q doesn't work for me either (tried on 2 different PC's).
I hope restoring clean non-rooted boot/system will help, if somebody can share the backup files.
Click to expand...
Click to collapse
Which Mobile Upgrade Q are you using? Try to use 5.0.3 version. Tried both on my 64bit Windows 10 and 7 for my 5051x Optus locked phone. But you need to manually put your phone to download mode (while your phone completely off, press all volume up + volume down + power), then plug in your phone, start the program and follow the prompt.
Had to reflash my phone numerous time, because supersu seems to brick the phone, while kingroot lost its root every reboot.
Cryonics said:
Which Mobile Upgrade Q are you using? Try to use 5.0.3 version. Tried both on my 64bit Windows 10 and 7 for my 5051x Optus locked phone. But you need to manually put your phone to download mode (while your phone completely off, press all volume up + volume down + power), then plug in your phone, start the program and follow the prompt.
Had to reflash my phone numerous time, because supersu seems to brick the phone, while kingroot lost its root every reboot.
Click to expand...
Click to collapse
which driver do you have installed? (what shows up in device manager?) When the phone is in download mode, my PC doesn't detect it. after several seconds the phone exits download mode, and then gets detected, but it doesn't auto-install any driver, so I have to manually choose something.
Still, if someone could send me full backup from TWRP, I could try to restore it on the phone and get it working this way.
zbaracki said:
which driver do you have installed? (what shows up in device manager?) When the phone is in download mode, my PC doesn't detect it. after several seconds the phone exits download mode, and then gets detected, but it doesn't auto-install any driver, so I have to manually choose something.
Still, if someone could send me full backup from TWRP, I could try to restore it on the phone and get it working this way.
Click to expand...
Click to collapse
Qualcomm HS_USB qdloader 9008 The driver you need is found:
http://www.androidbrick.com/download/latest-2017-qualcomm-diag-qd-loader-windows-10-drivers-signed/
or
http://www.androidbrick.com/download/qualcomm-qdloader-hs-9008-edl-usb-driver/
You may need to manually install the driver in device manager. Its under show all>qualcomm incorperated>Qualcomm HS_USB qdloader 9008
bulletbeef said:
Qualcomm HS_USB qdloader 9008 The driver you need is found:
http://www.androidbrick.com/download/latest-2017-qualcomm-diag-qd-loader-windows-10-drivers-signed/
or
http://www.androidbrick.com/download/qualcomm-qdloader-hs-9008-edl-usb-driver/
You may need to manually install the driver in device manager. Its under show all>qualcomm incorperated>Qualcomm HS_USB qdloader 9008
Click to expand...
Click to collapse
Thanks! With this driver it finally recognized the phone and flashed it successfully (using the latest Mobile Upgrade Q 5.1.8).
You're a saviour!
zbaracki said:
Thanks! With this driver it finally recognized the phone and flashed it successfully (using the latest Mobile Upgrade Q 5.1.8).
You're a saviour!
Click to expand...
Click to collapse
i had the same issue searched everywhere and nobody gave good drivers or complete answers not even alcatel themselves, so i figured it out, that's what this community is for
i have the same problem here. i Installl the driver and all try the download mode but nothing just happends... It wont reconise the phone.. My phone is alcatel 5051X i did just a normal factory reset and then the instalation just crash every time and keeps popping up unfortunately setup wizard has stoped and wont go anywhere so i have been trying to get stock firmware eveywhere but nothing seems to help....
---------- Post added at 03:16 AM ---------- Previous post was at 02:51 AM ----------
harrinus said:
i have the same problem here. i Installl the driver and all try the download mode but nothing just happends... It wont reconise the phone.. My phone is alcatel 5051X i did just a normal factory reset and then the instalation just crash every time and keeps popping up unfortunately setup wizard has stoped and wont go anywhere so i have been trying to get stock firmware eveywhere but nothing seems to help....
Click to expand...
Click to collapse
ok now i got that solved it was a problem of win 10 missing android driver but now the software just jams at 2 % and eventually crash... the closest model i have found int he software is alcatel 5051 but mine 5051X so do i need to use some other version or what? just says read terminal information failed check the phone status...
well now i got all that solved but the upgrader says there is no newer one than there is and wont do anything with the old 1 so my original problem stays..... the instalation crashes every time... is there anyway i could just swipe the whole instalation away sense it seems to be broken someway
I succesefuly installed the stock rom witout mobile upgrade mobil
harrinus said:
i have the same problem here. i Installl the driver and all try the download mode but nothing just happends... It wont reconise the phone.. My phone is alcatel 5051X i did just a normal factory reset and then the instalation just crash every time and keeps popping up unfortunately setup wizard has stoped and wont go anywhere so i have been trying to get stock firmware eveywhere but nothing seems to help....
---------- Post added at 03:16 AM ---------- Previous post was at 02:51 AM ----------
ok now i got that solved it was a problem of win 10 missing android driver but now the software just jams at 2 % and eventually crash... the closest model i have found int he software is alcatel 5051 but mine 5051X so do i need to use some other version or what? just says read terminal information failed check the phone status...
well now i got all that solved but the upgrader says there is no newer one than there is and wont do anything with the old 1 so my original problem stays..... the instalation crashes every time... is there anyway i could just swipe the whole instalation away sense it seems to be broken someway
Click to expand...
Click to collapse
I had the same issue i was unable to install the stock rom using mobile upgrade it will say this is the last firmware there is no new update so i searched the web and i found a solution finaly its callad a software named sugar
what you need is a usb cable a good internet conection and drivers installed
make sure to follow instruction of the software to download
you will find the all instructions on this russian thread https://4pda.ru/forum/index.php?showtopic=675134&st=440#entry46026273
if you need any help just send me a pm
mygadgetgeek.com said:
I could upload twrp backup if help
Click to expand...
Click to collapse
Removed:
mygadgetgeek.com said:
I could upload twrp backup if help
Click to expand...
Click to collapse
Can you upload your twrp backup, or at least your stock recovery pleeease? I really need it since this is my work phone and it should be as stock as it came when they check it.
i hard brick my phone yesterday. trying to flash bootloader with flashfire. (the lazy way) thats what i get. anyways could not turn on n6p, tried charging it for a couple of hours, try holding power button for 30 seconds, try power + volume . tried holding all buttons. nothing work.. read some threads saying its done. look for new phone or send to get repair. then i found tenfar thread. long story short. i used some of tenfar info and rwj5279955.. so big thanks to these two users
here is what i did to get my N6p to turn back on.. brick by bootloader.. this is my first how to .. bear with me. please.
you will need the following https://drive.google.com/file/d/0By19rrbnQfVUVFZEVUZqQzY1RWs/view?usp=sharing
Qualcomm drivers
QFIL software
3 files, patch0, prog_emmc_firehose, rawprogram0 .. for this to work
1. install qualcomm drivers, Connect phone to pc, open Device Manager. if you see under com port Qualcomm USB loader or something along those lines. your good, go to step 2. if not disconnect phone hold power button for 10 seconds, wait for 5 seconds connect phone to pc. check if in com ports you see Qualcomm drives. if you can not get qualcom drivers on com port. just stop. its not going to work..
2. extract the three files. in a folder somewhere easy to remember.
3. install the QFIL software, . once install run QFIL.
4. in QFIL software
if qualcomm driver are found it will say on top of QFIL software Qualcom USB loader 9008
Select Build Type: click Meta Build
Select Build :: patch0 ... if for some reason patch0 doesnt work try rawprogram0
Select Programmer:: pro_emmc_firehose
hit download ...if the blue bar get to half way mark your golden. its going to always fail. the trick is to get the blue bar at least half ways. then you disconnect phone, hold power button, it should turn on.. then you ADB what ever you need to do.
for those that get the fail right away.. while phone connected to pc, hold power button until drivers disappear from device manager.. then disconnect phone, wait for 5 seconds, hold power button, for 10 second,.. wait for 5 seconds .. then connect phone back to pc, wait for device manager to see drivers.. then hit the download button . do this part over and over again ..until it works..
sorry for this horrible guide.. it work for me.. hope it works for you..
That's a lot to take in! Is this for windows only then not Linux? Bootloader and radio does have to be flashed via fastboot
DEVILOPS 007 said:
That's a lot to take in! Is this for windows only then not Linux? Bootloader and radio does have to be flashed via fastboot
Click to expand...
Click to collapse
Windows
Lw00d said:
Windows
Click to expand...
Click to collapse
Luckily there's already alternative for linux
Hello thank you so much for your guide, currently trying to unbrick my nexus 6P stuck in 9008 port, could you provide a link for your version of Qfil please? as I'm struggling to find your 2.0.0.2 version I either get 1.0.0 or 2.0.0.3 and they're not working
Update: I've found the version! However when I quick Meta build and attempt to locate XML there's nothing I can select? sorry if this is really simple just never done before thank you
Clarkeofcurtis said:
Hello thank you so much for your guide, currently trying to unbrick my nexus 6P stuck in 9008 port, could you provide a link for your version of Qfil please? as I'm struggling to find your 2.0.0.2 version I either get 1.0.0 or 2.0.0.3 and they're not working
Update: I've found the version! However when I quick Meta build and attempt to locate XML there's nothing I can select? sorry if this is really simple just never done before thank you
Click to expand...
Click to collapse
place the files in a folder.
then in QFIL brows to the folder
need to select build path first.
What type of brick does this fix? Is this for the big one " boot loop of death" that's been well covered?
I ask out of curiosity. My phone's unaffected (knock wood)
KLit75 said:
What type of brick does this fix? Is this for the big one " boot loop of death" that's been well covered?
I ask out of curiosity. My phone's unaffected (knock wood)
Click to expand...
Click to collapse
hard brick. phone does not turn on at all
Lw00d said:
place the files in a folder.
then in QFIL brows to the folder
need to select build path first.
Click to expand...
Click to collapse
I have done as stated, however when attempting to select build after clicking META BUILD, I have to change the browsing options to ALL FILES from META BUILD CONFIGURATIONS otherwise I can't find anything?
Once selected Patch0, I proceed to select programmer path, but then my download content isn't clickable please?
Select build type click flat build. See if u could click on download
Lw00d said:
Select build type click flat build. See if u could click on download
Click to expand...
Click to collapse
I can start it VIA flat build, however I get this error
Now try with meta build
Lw00d said:
Now try with meta build
Click to expand...
Click to collapse
When trying with meta build this is the problem I'm faced with.
Can't select anything, am i using wrong version of Qfil perhaps or isn't that an issue as it's the newst?
I click load content and I can't view the files I'm supposed to be selecting
Clarkeofcurtis said:
When trying with meta build this is the problem I'm faced with.
Can't select anything, am i using wrong version of Qfil perhaps or isn't that an issue as it's the newst?
I click load content and I can't view the files I'm supposed to be selecting
Click to expand...
Click to collapse
That never happen to me.. Could be the version u have installed.
In flat build. When u hit download. Does the blue progress bar move?
Sorry, I've found it again. But this time - different error... :/ Any ideas?
Lw00d said:
That never happen to me.. Could be the version u have installed.
In flat build. When u hit download. Does the blue progress bar move?
Click to expand...
Click to collapse
Thank you for your help and replies, no blue bar when I click download on flat build, just gives me that port error about it taking 10 seconds to open when it should only be 3? I'll try it on your version and let you know bare with me
---------- Post added at 07:44 AM ---------- Previous post was at 07:32 AM ----------
Lw00d said:
That never happen to me.. Could be the version u have installed.
In flat build. When u hit download. Does the blue progress bar move?
Click to expand...
Click to collapse
Could you send me a link to your version please?
Sorry, I've found it again. But this time - different error... :/ Any ideas?
Clarkeofcurtis said:
Sorry, I've found it again. But this time - different error... :/ Any ideas?
Thank you for your help and replies, no blue bar when I click download on flat build, just gives me that port error about it taking 10 seconds to open when it should only be 3? I'll try it on your version and let you know bare with me
---------- Post added at 07:44 AM ---------- Previous post was at 07:32 AM ----------
Could you send me a link to your version please?
Sorry, I've found it again. But this time - different error... :/ Any ideas?
Click to expand...
Click to collapse
It's on first post
Lw00d said:
It's on first post
Click to expand...
Click to collapse
Getting this
Clarkeofcurtis said:
Getting this
Click to expand...
Click to collapse
did you do this..
for those that get the fail right away.. while phone connected to pc, hold power button until drivers disappear from device manager.. then disconnect phone, wait for 5 seconds, hold power button, for 10 second,.. wait for 5 seconds .. then connect phone back to pc, wait for device manager to see drivers.. then hit the download button . do this part over and over again ..until it works..
also try extracting all these files into the folder you made .. this includes the three files .. https://drive.google.com/open?id=0By19rrbnQfVUbFZSc3A3VXhGRzQ
Thank you so much! I messed up my 6P when I tried to flash a bootloader image via Flashfire. I hadn't been in a brick this bas since the good old days of Gingerbread and ROM Manager! For anyone else having similar issues, I got my dead 6P to be recognized as QHSUSB_bulk eventually in Windows 7. I then edited the rawprogram0.xml file (from OP's link) in a text editor. I removed the entries for all the other partitions I didn't want to overwrite (like system and vendor and userdata), leaving only the sbl1 (secondary bootloader, the part of the firmware that actually boots into the system/recovery/bootloader when the device is first powered on) partition entry - because that's what Flashfire said it had flashed the entire bootloader image to. Doing a bit of research, I found that our bootloader image is actually just many different small partitions all grouped together into a single image file. I couldn't figure out how to unpack the bootloader image, so I downloaded a full firmware OTA zip from Google, and lo and behold, there was a "bootloader.sbl1.img" (along with other small partitions) file in the OTA zip. I changed the sbl1.img entry in the rawprogram0.xml file so that it correlated with the filename "bootloader.sbl1.img", I moved the image file into the same folder as the rawprogram0.xml, and then I was able to restore my device to it's previous functionality using the "flat build" download configuration in QFil, though the whole process did take me like 3 hours. Lesson learned - screw using Flashfire for bootloader images.
ERROR: Could not access "C:\temp\vendor.img" with access mode 'rb'
When I'm finally lucky, rebooting, replugging the phone, it looks like it might flash...
...then I see this.
I've given all permissions to all users for full control, on the file, I've run time program as administrator, I don't know what else to do. If it can't open the file, I can't flash my phone. I'm not a Windows administrator so I don't really know what to do to get this to work and I can't find any hints on the forums.