Related
I'm having a problem using the following guide, and I can't seem to find anyone asking the same question...
http://forum.xda-developers.com/showthread.php?t=1622425
Following all the instructions, at step 3 in the directions, I get all the info from checking my SBK number, however the last two lines read: file not found bootloader.img, command failure bootloader download failed.
As there was no bootloader.img and I couldn't find any info on such a file, I pushed ahead, thinking this was common.
I can get into APX mode without issue, its the following steps where I seem to have a problem.
Using the first method listed in step 6, I am never prompted with a "press any key to continue", it just launches straight into attempting the install, and freezes installing (I forget the exact file name but I believe it's the bootloader, it is right in the beginning) it stalls at 131702/78908 (I think those numbers are right)
Using blackthun3r's tool renders the same result. I've tried everything can't figure it out.
I am on a stock 033.00_PA_CUS1 rooted using blackthun3r's tool, which worked perfectly...
Also, I never see the tab entering download mode when in APX it just sits with a black screen.
Anyone have any clue where I'm going wrong here?
Are APX/Download mode drivers installed properly
killdevilfalls said:
I'm having a problem using the following guide, and I can't seem to find anyone asking the same question...
http://forum.xda-developers.com/showthread.php?t=1622425
Following all the instructions, at step 3 in the directions, I get all the info from checking my SBK number, however the last two lines read: file not found bootloader.img, command failure bootloader download failed.
Click to expand...
Click to collapse
the most important thing at step 3 is having the tool "see your uid" the rest...dont worry about.....
I can get into APX mode without issue................
............Also, I never see the tab entering download mode when in APX it just sits with a black screen.
Click to expand...
Click to collapse
ok, you must ensure the apx/download mode drivers are installed.
For your tab to enter download mode it needs the apx drivers...you should see the windows new hardware wizard installing them, and check out the guide again there's a picture of where to look for them in Device Manager....
Yes APX mode is a black screen AND the white led is lit on the power button.
with the apx flash tool, did you install the .apx files from the guide?
thats about all i can offer, dont know anything about step 6.
just make sure u have the boot/recovery aka apx aka download mode drivers installed and installed correctly...good luck
Right Driver
The driver listed when I connect the device in ATX mode is "Acer USB Boot-recovery driver"... is this the correct ATX driver or is there another, as the image shows "Acer Picasso USB-Boot-recovery driver"
killdevilfalls said:
The driver listed when I connect the device in ATX mode is "Acer USB Boot-recovery driver"... is this the correct ATX driver or is there another, as the image shows "Acer Picasso USB-Boot-recovery driver"
Click to expand...
Click to collapse
That, is a very good question!!! I dont know whether there is a dedicated APX driver or whether its a generic term for the 'Picasso' drivers as seen in the image.
All I know is that if these 'boot/recovery' Drivers are not installed then the flash wont work. Keep in mind too, that these nvflash methods are fairly new to most of us, so we're all on a steep learning curve -
I'd suggest going thru the process again, write out each step in your own words if you need to, and take your time - it can be difficult relating the instructions your eyes see on screen with what your fingers are tapping out on the keyboard AND having your head trying to make sense of it all!!! Pick one of the methods, it doesn;t matter which, and stick with it - switvhing between 2 or more can make things even more confusing....
I;m about to go on try civs method now, will let u know how i go
***************************************
UPDATE
steps 1-2-3 check
on getting into apx mode noticed driverrs didnt install
but checked dev man and they were listed as Acer not picasso
ran nvflash
entered 1
entered sbk
command window says nvflash starting.......
that was it couldnt get any further....no entering download mode on tab
uh-oh -
***************************************
Yes- there is a dedicated APX Driver
***************SUCCESS***********
What a mish!!!! Got it going on the 5th time.....flashing r14 as i write...woohoo!
If I knew how to post images then I would...took screenies all the way thru.
Reinstalled all drivers after the first fail.
On next start found new hardware wizard wanted to install drivers for APX!!!!
I have never seen that before
After poking around a bit got them installed with...wait for it...under adb???
They installed as Acer "FastBoot Interface".....
It never showed in my system tray or as Picasso USB etc....in dev man
my next try failed again....waiting for tab to enter download mode......
For my last go at for the nite I bbutton comb'ed to APX first a
nd connected cable 2nd.....within a minute or two Acer Logo on tab
followed by :"entering download mode....within 10 mins I was good to go......
All I can tell you is to keep trying till u get it!!!!!
Probelm installing v3 bootloader/recovery
I have the same problem tried everything your not the only one.
shenny585 said:
I have the same problem tried everything your not the only one.
Click to expand...
Click to collapse
Driverz reinstall them......each time u attempt a flash and it fails at some point, you must reinstall them.
After poking around a bit got them installed with...wait for it...under adb??? They installed as Acer "FastBoot Interface"..... It never showed in my system tray or as Picasso USB etc....in dev man my next try failed again....waiting for tab to enter download mode...... For my last go at for the nite I bbutton comb'ed to APX first a nd connected cable 2nd.....within a minute or two Acer Logo on tab followed by :"entering download mode....within 10 mins I was good to go....
Click to expand...
Click to collapse
If they don't show up in either device manager (under adb/apx or USB controllers) or the system tray "safely remove h/ware then they are not installed, if u continue with flash and it fails then u have to reinstall Acer drivers again!!!
install a500 boot manager u can check for a proper connection with this tool....
See link in my sig for a pictorial showing step by step instructions for using apxflash tool
If this still does not work then post back with the following:
What rom and bootloader u have now or began with
What rom u installed at step 4
R u rooted and do u have a custom recovery installed
On validating yr sbk, at step 3, the most important thing here is to see the system info in the command window,
Boot.img errors u see at the end IS A NORMAL PART OF THE VALIDATION in other words its what you're supposed to see. Correct me if I'm wrong but at that command window aren't u supposed to type: go
I have followed many threads but cannot find a working solution. I will outline what I have done as briefly as possible.
While streaming to TV with HDMI, the screen switched to the android robot on his back with red triangle and "!".
I put Acer_A500_1.031.00_WW_GEN1 on a SD and tried to reboot, showed robot working and then on back with "!" again.
Put in fastboot and used ADB command lines to try to put Thor recovery on, stated device locked on screen.
Entered cmd to unlock, got positive response, tried thor again, same result.
powered down, re-installed asus drivers, connected it did not connect as APX so rolled back drivers and was able to connect as APX.
Ran AFTEROTA, cannot find device
Ran Blackthund3r manager, stated a500 connected in APX mode, but when trying to get Serial program runs but returns nothing. And when trying to get logs returns "no device found" but at the bottom still shows connected in APX Mode.
I am unable to get the CPUID and the device does not boot for me to put in USB development mode so I am unsure where to go from here. Again I have spent several hours following everystep in multiple threads and I keep getting stuck. Any help in helping me return my A500 to working condition would be great. Also, before crash I was running ICS OTA stock.
v/r
i also have the same problem & also try almost everything of what you did but mine is not rooted a virgin tablet running on latest ics . i can also get into apx mode but cannot generate the uid.. i know there is a solution to this using ubuntu but i dunno how to use ubuntu or libusb or visualc+ as what it stated to generate the uid & was hoping that some1 might try to make a step by step thread in using linux or winusb in windows
NavyRazorback said:
I have followed many threads but cannot find a working solution. I will outline what I have done as briefly as possible.
While streaming to TV with HDMI, the screen switched to the android robot on his back with red triangle and "!".
I put Acer_A500_1.031.00_WW_GEN1 on a SD and tried to reboot, showed robot working and then on back with "!" again.
Click to expand...
Click to collapse
so u flashed stock ICS (or tried to) - doing this overwrites your custom recovery with the silly stock one
Put in fastboot and used ADB command lines to try to put Thor recovery on, stated device locked on screen.
Click to expand...
Click to collapse
???? huh!!! do u have the unlocked bootloader????
what rom were u running before u flashed stock???
you were on the right track with fastboot if you'd tried that first rather than flashing a stock rom (for future ref!)
Entered cmd to unlock, got positive response, tried thor again, same result.
Click to expand...
Click to collapse
what is this unlock thing, sorry for my ignorance, but I've noticed a couple of reports lately that mentions this problem??
powered down, re-installed asus drivers, connected it did not connect as APX so rolled back drivers and was able to connect as APX.
Click to expand...
Click to collapse
I hope u meant to type "acer drivers"
unless you do have an asus tab....which then explains your troubles!!!!
Ran AFTEROTA, cannot find device
Ran Blackthund3r manager, stated a500 connected in APX mode, but when trying to get Serial program runs but returns nothing. And when trying to get logs returns "no device found" but at the bottom still shows connected in APX Mode.
I am unable to get the CPUID and the device does not boot for me to put in USB development mode so I am unsure where to go from here. Again I have spent several hours following everystep in multiple threads and I keep getting stuck. Any help in helping me return my A500 to working condition would be great. Also, before crash I was running ICS OTA stock.
v/r
Click to expand...
Click to collapse
heck you are in a bit of a pickle m8!!!
i think you can only use an update.zip (no cpuid required)
have a look at jdgM3NTL's thread " revert to factory stock the easy way" http://forum.xda-developers.com/showthread.php?t=1839313
IF this doesnt work you'll be in for the long haul - you will need to use linux as that is the only other way to get yr cpuid - have you checked out the cpuid thread (u only need to read the OP)
there are at least 7 different methods for retrieving yr cpuid, u might try usbdeview
---------- Post added at 11:05 AM ---------- Previous post was at 10:59 AM ----------
botzgori said:
i also have the same problem & also try almost everything of what you did but mine is not rooted a virgin tablet running on latest ics . i can also get into apx mode but cannot generate the uid.. i know there is a solution to this using ubuntu but i dunno how to use ubuntu or libusb or visualc+ as what it stated to generate the uid & was hoping that some1 might try to make a step by step thread in using linux or winusb in windows
Click to expand...
Click to collapse
check out srbeens thread here http://forum.xda-developers.com/showthread.php?t=1751978
have you checked out the cpuid thread (u only need to read the OP) there are at least 7 different methods for retrieving yr cpuid
Click to expand...
Click to collapse
if you can still boot then method 7 for you
Thank you for your reply.
In response to some of your questions. Yes I meant to type Acer and not Asus, I do in fact own the Acer A500.
About my initial attempt to flash the stock ROM, I never had an unlocked bootloader, before the tablet was bricked I was running Stock ICS OTA and had never done any modifications.
I tried using USBDeview but the serial number is blank. It looks like I will have to try the Linux method. Again thank you for your help.
NavyRazorback said:
Thank you for your reply.
In response to some of your questions. Yes I meant to type Acer and not Asus, I do in fact own the Acer A500.
About my initial attempt to flash the stock ROM, I never had an unlocked bootloader, before the tablet was bricked I was running Stock ICS OTA and had never done any modifications.
I tried using USBDeview but the serial number is blank. It looks like I will have to try the Linux method. Again thank you for your help.
Click to expand...
Click to collapse
And this is WHY IM DONE following or using XDA THREADS. Most of the time someone experienced helps for a bit than leaves people hanging. I just unbricked my a500 when no one answered for my help. This guy here responded back and no o e help him. Hit and miss here. Go to another forum if you canr find your solution aleeady poSted. Cause if you reply or start NEW THREAD, no answer 90% time. Mine was bricked And rooted. Stuck on acer screen. Tried everything I could. No answers fron this sites threads. But I did it on my own, simple fix for apparent hard brick a500, but it was not really hard bricked. All symptons showed hard bricked. You wanna know what really fixed my tab without changing main board...?? Hint.. xbox red ring.....xda, you suck, no support for newbies here. Out. Unsubscribed..deuces. .
Hi guys,
I searched forums, web with no positive results. So I start a new thread. Here is the situation: one day my Nexus S (Worldwide edition) froze on restarting with the Google Logo on the screen. Every time I try to turn the phone on it stacks at Google logo. When in the fastboot mode the status is Locked. Every time I try fastboot oem unlock I get Phone’s prompt with Yes or Not to unlock bootloader and after choosing Yes, the status doesn’t change to Unlock. Tried on Linux, Mac, Windows (drivers installed successfully), the same result. Tried to force Flash Stock + Unroot in Wugfresh, doesn’t work due to the Locked Bootloader.
typing "adb devices" in cmd (should return the device number) shows:
List of devices attached
......
Empty line above
Any word of advise how to force Unlocking the Bootloader would be greatly appreciated. Please help. Thank you!
alpheus said:
Hi guys,
I searched forums, web with no positive results. So I start a new thread. Here is the situation: one day my Nexus S (Worldwide edition) froze on restarting with the Google Logo on the screen. Every time I try to turn the phone on it stacks at Google logo. When in the fastboot mode the status is Locked. Every time I try fastboot oem unlock I get Phone’s prompt with Yes or Not to unlock bootloader and after choosing Yes, the status doesn’t change to Unlock. Tried on Linux, Mac, Windows (drivers installed successfully), the same result. Tried to force Flash Stock + Unroot in Wugfresh, doesn’t work due to the Locked Bootloader.
typing "adb devices" in cmd (should return the device number) shows:
List of devices attached
......
Empty line above
Any word of advise how to force Unlocking the Bootloader would be greatly appreciated. Please help. Thank you!
Click to expand...
Click to collapse
It looks like your device is not recognized in Fastboot mode...
Have you turned on USB Debugging while connecting PC and Allow in Device when Prompt some message ..
Go to fastboot mode and write this command... fastboot devices
If it will give you a message like this
List of devices
1235456785164
Then your devices is successfully recognized...:good:
It is not recognized by adb devices, but:
fastboot devices - gives the following output:
ERROR: could not get pipe properties
3331E6EBCA6000EC fastboot
Click to expand...
Click to collapse
fastboot oem unlock - gives the following:
ERROR: could not get pipe properties
...
FAILED (remote: Erase Fail)
finished. total time: 4.753s
Click to expand...
Click to collapse
alpheus said:
It is not recognized by adb devices, but:
fastboot devices - gives the following output:
fastboot oem unlock - gives the following:
Click to expand...
Click to collapse
Pretty sure you have a bad USB cable, the error means the fastboot binaries are working on PC but can not connect to device, often this is due to a bad USB cable or port
Try a new cable, one you can verify works transferring data
demkantor said:
Pretty sure you have a bad USB cable, the error means the fastboot binaries are working on PC but can not connect to device, often this is due to a bad USB cable or port
Try a new cable, one you can verify works transferring data
Click to expand...
Click to collapse
Thanks, I tried 3 different cables on 3 different operating systems, with the same problem unlocking the fastboot. When I send fastboot oem unlock the device opens a prompt with Yes or No choice, but after choosing Yes, it stays Locked
Something indeed is strange...
So fastboot is for bootloader and adb is for within os and in recovery.
Try booting into recovery and see if adb works, also boot normal into your bootloop and see if adb works there too
demkantor said:
Pretty sure you have a bad USB cable, the error means the fastboot binaries are working on PC but can not connect to device, often this is due to a bad USB cable or port
Try a new cable, one you can verify works transferring data
Click to expand...
Click to collapse
demkantor said:
Something indeed is strange...
So fastboot is for bootloader and adb is for within os and in recovery.
Try booting into recovery and see if adb works, also boot normal into your bootloop and see if adb works there too
Click to expand...
Click to collapse
Loading into basic recovery and trying to wipe data/factory reset - doesn't work. adb devices returns the following output:
./adb-linux devices
* daemon not running. starting it now *
* daemon started successfully *
List of devices attached
****empty line here****
Somehow, adb doesn't recognize the device, whereas fastboot devices shows it.
Is there a way to flash new bootmode with the currently locked bootloader?
Thank you!
alpheus said:
Loading into basic recovery and trying to wipe data/factory reset - doesn't work. adb devices returns the following output:
./adb-linux devices
* daemon not running. starting it now *
* daemon started successfully *
List of devices attached
****empty line here****
Somehow, adb doesn't recognize the device, whereas fastboot devices shows it.
Is there a way to flash new bootmode with the currently locked bootloader?
Thank you!
Click to expand...
Click to collapse
I am damn Sure What's Your problem is, ADB is not working..
PROCEDURE:-
1) Download My attachement and unzip it and Place it in Folder...
See image 1.png
2) Go to that folder and Press CTRL+SHIFT+ Right click on mouse and Select Open Command Window here..
See image 2.png
3) Now type here Fastboot devices and Now you will get Those list of devices Number..
See image 3.png
If Everything will be done as Procedure and you will get List of devices Number... Now, You type those command for Unlocking bootloader and Root Your Devices...:good:
Hope this Guide will help..
UPDATE (resolved)
Here is an update. Hope this would help others with similar issue, as I've read many threads and folks complaining that they weren't able to unlock fastboot and further root their Nexus S, and who can't boot the phone, which stacked with Google Logo (soft loop). This was the case with my device and finally I got it resolved. I've read some guy tried to hit the phone and after that he was able to boot phone normally. It related to some hardware electrical circle issue. Anyways, I tried to hit my phone by placing it under the direct sun in balcony for some time until the phone got hot and then power it on. And ooops, my phone started booting passed by that Google Logo which was the good sign. Once the phone booted up, I went ahead and activated USB debugging and restarted the phone into the Fastboot mode. while the phone was still hot and in Fastboot mode I run "fastboot oem unlock" and hey, fastboot is Unlocked! Again, this was done while the phone was hot, any previous attempts (read above) weren't successful. From that point, I went ahead and rooted my Nexus S by Nexus Root Toolkit, available on wugfresh.com/nrt, without a slightest problem. Now my phone is fully rooted, bootable and working fine. I thank all who replied to my thread and tried to help and hope this info would help someone with the similar issue.
Rushabh22 said:
I am damn Sure What's Your problem is, ADB is not working..
PROCEDURE:-
1) Download My attachement and unzip it and Place it in Folder...
See image 1.png
2) Go to that folder and Press CTRL+SHIFT+ Right click on mouse and Select Open Command Window here..
See image 2.png
3) Now type here Fastboot devices and Now you will get Those list of devices Number..
See image 3.png
If Everything will be done as Procedure and you will get List of devices Number... Now, You type those command for Unlocking bootloader and Root Your Devices...:good:
Hope this Guide will help..
Click to expand...
Click to collapse
Thank you for your help and suggestions.
Q Mobile X 32
bootloader oem unlock problem
plz help
Q-mobile said:
Q Mobile X 32
bootloader oem unlock problem
plz help
Click to expand...
Click to collapse
Wrong device thread..
Try here..
https://forum.xda-developers.com/showthread.php?t=2363923
Setting.Out said:
Wrong device thread..
Try here..
https://forum.xda-developers.com/showthread.php?t=2363923
Click to expand...
Click to collapse
can you help me in rooting Qmobile x32
Q-mobile said:
can you help me in rooting Qmobile x32
Click to expand...
Click to collapse
That thread didn't help?
Here's what the guide says...
Hi guys,i was looking for guide how to unlock Axon 7 with latest update 1.2.0B05 but can't find anything. Can someone please help? I want to flash resurrection remix rom and not to brick phone...or is there better roms?
I cannot believe you're asking this question.
YOU HAVEN'T READ ANYTHING.
This board is full with uncountable guides.
https://forum.xda-developers.com/showthread.php?t=3573108
Not working....error: Length cannot be less than zero. Parameter name: length
salle25 said:
Not working....error: Length cannot be less than zero. Parameter name: length
Click to expand...
Click to collapse
Really, the last thing this forum needs is people unable to find guides on their own...
Ask @bkores about the error
WTF is wrong with you ppl?? I came to ask for help and you told me i'm retarded and stupid in nice way! If you don't wan't to help anyone then don't post reply or help and don't QQ about that! Thanx a lot!
salle25 said:
WTF is wrong with you ppl?? I came to ask for help and you told me i'm retarded and stupid in nice way! If you don't wan't to help anyone then don't post reply or help and don't QQ about that! Thanx a lot!
Click to expand...
Click to collapse
I'm sry but there's nobody here who will tell you're stupid,
People here are willing to help, but if you are too lazy to search for the guides (yes more then one is available) people will tell you that you are lazy.
Now I link a working guide for you
https://forum.xda-developers.com/axon-7/how-to/guide-install-twrp-unlock-bl-flash-t3517379
If you want it easier, search for the toolkit, it will make the most work for you.
Nope....not working. axon7tool.exe keeps crashing: "This application has requested the Runtime to terminate it in an unusual way.
Please contact the application's support team for more information."
Toolkit is useless too,MiFlash doesn't see phone when in EDL mode,reinstaled every possible driver i found and not even Zadig helped. I had custom roms on every singe phone i had,but this one is pain in the ...
Got it sorted....renaming to .bin was problem,thanx
question
me too
salle25 said:
Got it sorted....renaming to .bin was problem,thanx
Click to expand...
Click to collapse
Yes it's a bit harder to unlock and flash, good you managed that, I forgot to tell you that there are two toolkits win32 and win64.
Help cant repair my Axon 7 G latest B05
coremania said:
Yes it's a bit harder to unlock and flash, good you managed that, I forgot to tell you that there are two toolkits win32 and win64.
Click to expand...
Click to collapse
I try to use both method and still withaut succes also have message before run my phone "Your device software can't be checked for corruption, Please lock the bootloader"
I try almost evrything and nothing.
Bizon86 said:
I try to use both method and still withaut succes also have message before run my phone "Your device software can't be checked for corruption, Please lock the bootloader"
I try almost evrything and nothing.
Click to expand...
Click to collapse
So what don't you understand on this message? It tells you that your bootloader is already unlocked [emoji779] [emoji779]
marcus.linkenbach said:
So what don't you understand on this message? It tells you that your bootloader is already unlocked [emoji779] [emoji779]
Click to expand...
Click to collapse
No is not unlocked Axontooolkit says something oposit. I try both guides from this topic and:
- twrp dosent instal
- cant allow oem unllock
- when use UNLOCK BOOTLOADER Miflash dosent see my devices
Bizon86 said:
I try to use both method and still withaut succes also have message before run my phone "Your device software can't be checked for corruption, Please lock the bootloader"
I try almost evrything and nothing.
Click to expand...
Click to collapse
Your bootloader is unlocked, you only got to managed the rest, read this thread here, you will see it's familiar to your situation, read to the end.
https://forum.xda-developers.com/axon-7/help/to-date-guide-rooting-a2017g-b04-t3666808
I try this and still. nothing
Bizon86 said:
I try this and still. nothing
Click to expand...
Click to collapse
This is a bit thin.
A bit more details, you don't manage to go to edl mode ?
Did you try zadig to to get the right drivers working ?
What do see in device manager ?
Can you boot to stock recovery?
Did you tried to start from scratch with the guide, not the toolkit ?
No detail, no help
Edit: if you use only the toolkit, may ask in the toolkit thread for help ???
coremania said:
This is a bit thin.
A bit more details, you don't manage to go to edl mode ?
Did you try zadig to to get the right drivers working ?
What do see in device manager ?
Can you boot to stock recovery?
Did you tried to start from scratch with the guide, not the toolkit ?
No detail, no help
Edit: if you use only the toolkit, may ask in the toolkit thread for help ???
Click to expand...
Click to collapse
Zadig works for axon7tool only, MiFlash uses COM while axon7tool uses usb protocol
- The edl is dont working because phone go blank after use command and computer dosent see it.
- i try zading and try another driver effect is the same.
- in device menager i see android device but only when smartfon is running
- i start from the scratch the effect is the same
- i cant turn allow oem
the problem is with phone if i use adb reboot computer dont see phone
Bizon86 said:
Then what i must do any idea?
Click to expand...
Click to collapse
First of all, understand what you just did. If you don't explain it in an understandable way, we won't get any of it...
So:
-You unlocked the bootloader.
-axon7toolkit failed somewhere, and you didn't tell us exactly where
-you didn't try to use any guide to retake from where it ended up failing
-you didn't try to enter any mode
So just try to get to recovery or fastboot, using the 5 sec screen. After that we'll see
Bizon86 said:
- The edl is dont working because phone go blank after use command and computer dosent see it.
- i try zading and try another driver effect is the same.
- in device menager i see android device but only when smartfon is running
- i start from the scratch the effect is the same
- i cant turn allow oem
the problem is with phone if i use adb reboot computer dont see phone
Click to expand...
Click to collapse
If you go to edl, by adb command or by pressing both volume buttons while connecting usb the screen goes blank, that's ok, it has to be this way.
Why you want to turn on allow oem, you are already unlocked.
Your issue seems to be the driver, I guess.
Edit: try this maybe, from the toolkit FAQ
The toolkit says my device is connected through ADB but adb commands don't work?
Your device may be unauthorized. Unlock your device, open a cmd window, type in "adb devices" and then accept the "Allow USB debugging" prompt on your phone. Make sure to check the "Always allow from this computer" box as well. If you don't get the prompt, try retoggling USB debugging, replugging your device in, and revoking all USB debugging authorizations in developer options.
Hello, im new to the forums and i would like to get some help with this huawei on what to do. I recieved this phone already bricked from a friend, so i would like to see if i can make it work again. I dont know how the phone got bricked and i have no idea of what to do. The problem is that the phone starts in the huawei logo and then goes to a black screen and turns itself off again. The phone doesnt make it past that point. I tried to make a reset from recovery, but it doesnt work. In download mode i tried to download the latest recovery, but it says failed to download. In fastboot mode the phone says "Phone unlocked" in red letters and "FRP locked" in green letters.
Any idea of what to do in order to recover the phone ?.
BrattPitlord said:
Hello, im new to the forums and i would like to get some help with this huawei on what to do. I recieved this phone already bricked from a friend, so i would like to see if i can make it work again. I dont know how the phone got bricked and i have no idea of what to do. The problem is that the phone starts in the huawei logo and then goes to a black screen and turns itself off again. The phone doesnt make it past that point. I tried to make a reset from recovery, but it doesnt work. In download mode i tried to download the latest recovery, but it says failed to download. In fastboot mode the phone says "Phone unlocked" in red letters and "FRP locked" in green letters.
Any idea of what to do in order to recover the phone ?.
Click to expand...
Click to collapse
Hello and welcome !
Just thinking you should try to start a fresh & clean install
rolling back to android 6 regardless of the current firmware.
Took a look inside the UNIFIED HELP THREAD but didn't find
any L23 rollback package...
However, I found another LINK that looks promising.
Good luck :fingers-crossed:
For further explanations try asking here.
Dadditz said:
Hello and welcome !
Just thinking you should try to start a fresh & clean install
rolling back to android 6 regardless of the current firmware.
Took a look inside the UNIFIED HELP THREAD but didn't find
any L23 rollback package...
However, I found another LINK that looks promising.
Good luck :fingers-crossed:
For further explanations try asking here.
Click to expand...
Click to collapse
Nice, i will try this and inform back later.
Dadditz said:
Hello and welcome !
Just thinking you should try to start a fresh & clean install
rolling back to android 6 regardless of the current firmware.
Took a look inside the UNIFIED HELP THREAD but didn't find
any L23 rollback package...
However, I found another LINK that looks promising.
Good luck :fingers-crossed:
For further explanations try asking here.
Click to expand...
Click to collapse
Well it didnt work. It says "incompatibility with this version"
BrattPitlord said:
Well it didnt work. It says "incompatibility with this version"
Click to expand...
Click to collapse
Hi,
you should use the follovinq commands in fastboot mode and then post the results please:
fastboot oem get-build-number
fastboot oem get-product-model
fastboot getvar version
fastboot getvar vendorcountry
Can you access Recovery ? (Power + Volume Up)
-Alf- said:
Hi,
you should use the follovinq commands in fastboot mode and then post the results please:
fastboot oem get-build-number
fastboot oem get-product-model
fastboot getvar version
fastboot getvar vendorcountry
Can you access Recovery ? (Power + Volume Up)
Click to expand...
Click to collapse
im new to this, so i put those commands in windows CMD with the phone connected or how ?
I can get to the stock recovery from huawei.
BrattPitlord said:
im new to this, so i put those commands in windows CMD with the phone connected or how ?
I can get to the stock recovery from huawei.
Click to expand...
Click to collapse
Use ADB commands.
Open developers option and turn on the USB debugging. Connect your device to PC in MTP/FILES mode. Run command
ADB reboot bootloader
(the device will reboot to fastboot mode)
Now you can type fastboot commands.
-Alf- said:
Use ADB commands.
Open developers option and turn on the USB debugging. Connect your device to PC in MTP/FILES mode. Run command
ADB reboot bootloader
(the device will reboot to fastboot mode)
Now you can type fastboot commands.
Click to expand...
Click to collapse
How do i turn debugging if the phone is bricked ? I cant get past the huawei logo. However, i do have access to fastboot mode.
BrattPitlord said:
How do i turn debugging if the phone is bricked ? I cant get past the huawei logo. However, i do have access to fastboot mode.
Click to expand...
Click to collapse
Oh, sorry, my mistake . Okay, install on your PC "Minimal ADB and fastboot" , open it , connect the device in fastboot mode, and run commands.