Related
I am quite new to the android rooting & custom recovery and having a problem with my Huawei P8 GRA-UL00 flashing (purchased from China), when I try the procedure with MAC OS X. My step by step actions and result was as follows:
1. I installed "SDK Tools Only" for Mac. Connected the device via USB, launched terminal and successfully see the device with the "adb devices" command.
2. Vol +, Vol- and Power didn't work to enter to the fastboot&rescure mode. However, Vol- and Power worked. (Also, Vol+ and Power enters to the Huawei eRecovery mode, which shows EMUI logo, Reboot, Download new version and recovery and Shutdown buttons. I guess this is stock recovery???)
3. In the fastboot mode, I have successfully seen the device with "fastboot devices". Then I unlocked the bootloader with the code. The first problem was here, there were no auto-reboots and I entered "fastboot reboot" command, and stuck in seeing "reboooting..." in terminal. Nothing happened after this command. After 10 minutes I manually rebooted the phone by pressing power and entered into the fastboot mode. I was written as "Phone Unlocked". (Do u think it was really successful?)
4. I tried to flash the TWRP file which was uploaded by @jniklast (openrecovery-twrp-2.8.7.0-p8-ul10-r4.img). The result was like that:
MacBook-Airlatform-tools go$ ./fastboot flash recovery openrecovery-twrp-2.8.7.0-p8-ul10-r4.img
target reported max download size of 471859200 bytes
sending 'recovery' (25566 KB)...
OKAY [ 0.703s]
writing 'recovery'...
OKAY [ 0.353s]
finished. total time: 1.056s
MacBook-Airlatform-tools go$
5. Tried fastboot reboot, but I wasn't successful:
MacBook-Airlatform-tools go$ ./fastboot reboot-bootloader
rebooting into bootloader...
ERROR: usb_read failed with status e00002ed
FAILED (status read failed (No such file or directory))
finished. total time: 0.121s
MacBook-Airlatform-tools go$
I am not sure if I have correctly defined my problem. I guess I wasn't successful to install TWRP even it says so. What should I do after finishing the flash recovery command?
Can anyone help me with this error?
@landros57 That recovery is only for Android 5.1.1 beta version. You should flash the @jniklast 's GRA-L09 version of TWRP which is for Android 5.0.
I'm not quite sure what the problem is? You enter rescue mode via power + vol- so that's correct. You enter recovery via power + vol- and vol+ so what happens if you do that after flashing TWRP? And better not use the adb command go voot into recovery as that will lead to a bootloop to recovery which has to be broken by manually booting into it once.
samusalo said:
@landros57 That recovery is only for Android 5.1.1 beta version. You should flash the @jniklast 's GRA-L09 version of TWRP which is for Android 5.0.
Click to expand...
Click to collapse
Thank you samusalo.. Then I understand that TWRP for GRA-L09 can work on a GRA-UL00. I will try.
jniklast said:
I'm not quite sure what the problem is? You enter rescue mode via power + vol- so that's correct. You enter recovery via power + vol- and vol+ so what happens if you do that after flashing TWRP? And better not use the adb command go voot into recovery as that will lead to a bootloop to recovery which has to be broken by manually booting into it once.
Click to expand...
Click to collapse
I don't use adb reboot, I manually press Vol - and Power. Then, the Fastboot & Rescue mode opens, and I enter to the terminal "fastboot flash recovery openrecovery-twrp-2.8.7.0-p8-ul10-r4.img". It quickly shows that the installation is successful. Then I enter fastboot reboot-bootloader (I guess this is required to launch TWRP) but it shows that usb read error.
@jniklast and @samusalo thank you for your explanations. They both worked.
I flashed the GRA-L09 version of the TWRP to my GRA-UL00 and it worked! Now I have a backup...
I also realized that I am doing something wrong.. After installing TWRP, I was trying to fastbot reboot-boatloader in order to get TWRP launched automatically. However, the only thing I need to do is to follow jniklast's instructions and after the phone shut down, press Vol+ Vol- and Power together to get the TWRP launch.
Now I will try to flash an official International ROM, instead of my Chinese ROM.
Is the following command correct for this?
fastboot flash system "HUAWEI P8 Firmware(GRA-UL00&UL10,Android5.0,Emtion UI 3.1,V100R001C900B141,General Version).zip"
No, you need to extract the img files to be able to flash it via fastboot. Look for huawei image extractor
jniklast said:
No, you need to extract the img files to be able to flash it via fastboot. Look for huawei image extractor
Click to expand...
Click to collapse
Many .img files exists in the update.app file. I guess I need to flash only the system.img?
If I flash the recovery.img or boot.img inside the update.app, will I lose the custom recovery and my backup?
I'd first try to only flash system.img. If that doesn't work also flash boot.img. it might be though that you have to flash another cust.img as well and I'm not quite sure if that's possible via fastboot. In that case you'd have to do it via TWRP which is a bit tricky
Partially Successful
jniklast said:
I'd first try to only flash system.img. If that doesn't work also flash boot.img. it might be though that you have to flash another cust.img as well and I'm not quite sure if that's possible via fastboot. In that case you'd have to do it via TWRP which is a bit tricky
Click to expand...
Click to collapse
Flashing boot and system was successful! Then, again, my "fastboot reboot-bootloader" didn't work and retured me my initial error. But I rebooted manually and successfully launched my phone OS.
I now have a slow-operating new Android firmware, which is a little weird )) I think it is now a international&chinese hybrid version. Some apps disappeared and I have a complete new page for google services and apps. However, my chinese stuff (baidu spotlight search, notifications, etc.) remains The EMUI Build is: GRA-UL00V100R001C00B120, which should be V100R001C900B141 as I have flashed the img files of this update.
I tried "fastboot erase userdata", "fastboot erase cache" and "fastboot erase system" but they both returned with "FAILED (remote: Command not allowed)".
The following were my successful fastboot flash commands:
MacBook-Airlatform-tools go$ ./fastboot flash boot boot.img
target reported max download size of 471859200 bytes
sending 'boot' (23256 KB)...
OKAY [ 0.653s]
writing 'boot'...
OKAY [ 0.569s]
finished. total time: 1.222s
MacBook-Airlatform-tools go$ sudo ./fastboot flash system system.img
target reported max download size of 471859200 bytes
sending sparse 'system' (459646 KB)...
OKAY [ 20.184s]
writing 'system'...
OKAY [ 6.149s]
sending sparse 'system' (450260 KB)...
OKAY [ 22.868s]
writing 'system'...
OKAY [ 6.051s]
sending sparse 'system' (437337 KB)...
OKAY [ 18.146s]
writing 'system'...
OKAY [ 5.952s]
sending sparse 'system' (460637 KB)...
OKAY [ 19.570s]
writing 'system'...
OKAY [ 6.267s]
sending sparse 'system' (448019 KB)...
OKAY [ 18.582s]
writing 'system'...
OKAY [ 5.982s]
sending sparse 'system' (165186 KB)...
OKAY [ 6.853s]
writing 'system'...
OKAY [ 2.206s]
finished. total time: 138.824s
MacBook-Airlatform-tools go$
jniklast said:
it might be though that you have to flash another cust.img as well and I'm not quite sure if that's possible via fastboot. In that case you'd have to do it via TWRP which is a bit tricky
Click to expand...
Click to collapse
I was finally successful to flash cust.img with fastboot and now I have B141 and all Chinese apps are removed. All Chinese ROM specific apps are disappeared and the only remaining Chinese stuff is the text in the Magazine Unlock, accessible when swiped up from the bottom of the screen at the lock screen.
The remaining problem for now is; when I press the Dialer, Contacts and Messages apps at the bottom, they crash.
Do I need to flash any other from the following extracted img files?
3RDMODEM.img
CACHE.img
CRC.img
CURVER.img
DTIMAGE.img
EFI.img
FASTBOOT.img
HIFI.img
MCUIMAGE.img
MODEM.img
MODEM_DSP.img
MODEMNVM_UPDATE.img
RECOVERY.img
RECOVERY2.img
SENSORHUB.img
SHA256RSA.img
TEEOS.img
TRUSTFIRMWARE.img
USERDATA.img
VERLIST.img
XLOADER.img
This is now delicate stuff, you could try and flash the radio (aka modem.img) but that will probably break connectivity as that is different in hardware. Maybe you'd need to install the dialer and messaging apks from the ul00 firmware. Does an alternate dialer work so that you can actually call someone?
And I think fastboot reboot-bootloader doesn't exist. It's either fastboot reboot bootloader or maybe only fastboot reboot. Anyway, booting into bootloader or recovery is better done by pressing the keys on the P8
jniklast said:
This is now delicate stuff, you could try and flash the radio (aka modem.img) but that will probably break connectivity as that is different in hardware. Maybe you'd need to install the dialer and messaging apks from the ul00 firmware. Does an alternate dialer work so that you can actually call someone?
And I think fastboot reboot-bootloader doesn't exist. It's either fastboot reboot bootloader or maybe only fastboot reboot. Anyway, booting into bootloader or recovery is better done by pressing the keys on the P8
Click to expand...
Click to collapse
Hello again,
Actually the hardware is the same, it is GRA-UL00. The device originally had: GRA-UL00-UL10_EMUI3.1_Android5.0_C00B173
I tried to fastboot the following ROM:
HUAWEI P8 Firmware(GRA-UL00&UL10,Android5.0,Emtion UI 3.1,V100R001C900B141,General Version)
I was successful to flash Root, CUST and System but when I try to flash any Modem-related img files (Modem.img, 3RDMODEM.img, MODEM_DSP.img, MODEMNVM_UPDATE.img), I get the following error:
sending 'modem' (38865 KB)...
OKAY [ 1.038s]
writing 'modem'...
FAILED (remote: Command not allowed)
finished. total time: 1.039s
I didn't try to install APKs.
I am still having crash problems with the dialer, contacts, messages, google play, and some other google services.
Network Mode FREEZE AUTO
Hi did you try checking Mobile Networks In Settings, As i m unable to open that. As soon as i click on it the network gets released and then comes back. THATS' ALL. I have the same phone and did the same stuff. Unable to Flash Modem.IMG as well.
Finally Done!
meetkhems said:
Hi did you try checking Mobile Networks In Settings, As i m unable to open that. As soon as i click on it the network gets released and then comes back. THATS' ALL. I have the same phone and did the same stuff. Unable to Flash Modem.IMG as well.
Click to expand...
Click to collapse
I finally succeeded.
After flashing the Boot.img, system.img and cust.img and launching the phone, I flashed the stock recovery and made a wipe/reset to factory settings. First, I extracted the recovery.img from the update.app file which you can find after downloading the official firmware and running the Huawei Update Extractor script available in the forum. Then I flashed this stock recovery.img in the fastboot mode. And finally I entered in the stock recovery (Huawei eRecovery) mode by pressing the Vol+, and Power buttons. After the wipe & reset to factory settings, I launched the phone and all problems with the radio, dialer, contacts, google services, etc were solved.
Thank you @jniklast for your help.
landros57 said:
I finally succeeded.
After flashing the Boot.img, system.img and cust.img and launching the phone, I flashed the stock recovery and made a wipe/reset to factory settings. First, I extracted the recovery.img from the update.app file which you can find after downloading the official firmware and running the Huawei Update Extractor script available in the forum. Then I flashed this stock recovery.img in the fastboot mode. And finally I entered in the stock recovery (Huawei eRecovery) mode by pressing the Vol+, and Power buttons. After the wipe & reset to factory settings, I launched the phone and all problems with the radio, dialer, contacts, google services, etc were solved.
Thank you @jniklast for your help.
Click to expand...
Click to collapse
Thanks a lot but i m still facing the problem. As soon as i select Mobile networks in settings nothing opens just the network gets released "NO Service" & comes back. I m unable to open it to select Network Mode or to change apn. It is not greyed Out but still not opening rest everything is working beautifully. Please Help. @jniklast for your help.[/QUOTE]
meetkhems said:
Thanks a lot but i m still facing the problem. As soon as i select Mobile networks in settings nothing opens just the network gets released "NO Service" & comes back. I m unable to open it to select Network Mode or to change apn. It is not greyed Out but still not opening rest everything is working beautifully. Please Help. @jniklast for your help.
Click to expand...
Click to collapse
Just checked and realized that I also have the same problem. THe contents of the "Mobile Networks" button doesn't show up and it works like a reset button. When I press, it disconnects me from the network and then the it reconnects to the network automatically.
Any Update on this anyone? I am unable to use the phone as it drains a lot of battery on 3G and i cant change it to 2G as due to Blank Mobile Network Settings.
Guys I have one problem I want to flash stock recovery for P8 L09 but in cmd it fails like not allowed command anybody knows why ?
landros57 said:
Just checked and realized that I also have the same problem. THe contents of the "Mobile Networks" button doesn't show up and it works like a reset button. When I press, it disconnects me from the network and then the it reconnects to the network automatically.
Click to expand...
Click to collapse
Hi landro57 have you tried to flash the update.app file of 18 Kb from local update? Some owners of the P8 gra ul09 variant are using that file to debrand their P8s. The mobile networks problem you ae experiencing is the same some other people have turnaround with that trick. You should check with it and report back to us, because if that goes ok, it means no more china firmware on our P8 gra ul00, we can simply flash the international general P8 firmware V100R001C900B141.
Inviato dal mio SGP311 utilizzando Tapatalk
GryphonA said:
flash the update.app file of 18 Kb from local update
Click to expand...
Click to collapse
Hi GryphonA, I don't get it, which 18kb update.app file do you mean?
I got the same problem (no access to mobile networks settings) and I can't remember if I never had that access or it happened due to my rooting/cusomizing activities.
I have GRA-UL00C433B180. I flashed also C470B180 but that didn't solve the problem.
BTW: There are a lot of mobile network setting apps and widgets in the Play Store but all apps I tested show the same failure as the mobile network settings: There seems to be a network reset and nothing more.
I will update my unbricking process with every attempt
Attempt 1:
Tried to flash grossoshop fastboot rom 17s by manually erasing boot, system, userdata, cache and recovery. Phone doesn't wake up with any. Still responds to ADB and Fastboot commands with no errors
If browsed through adb, system partition only shows two directories lib and lib64
Attempt 2:
Trying to manually flash mbn files present in the official 20s rom of x720. QPST is not recognizing my phone. I have to somehow put the phone into 9008 mode rather than 9025 mode (which is diagnostic)
There are no QPST compatible files around for Le Pro 3. Guess I finally put my 240$ to the trashcan....
Attempt 3:
I tried to flash the mbn, elf and bin files to their corresponding partitions via fastboot, everything went okay with the flashing. Then I flashed the boot.img, stock recovery and splash..... Went okay.
Rebooted my phone into recovery and its still dead. I can only see ADB interface in device manager and device is recognized correctly in adb.
If I power off my phone by pressing both volume buttons + power and then just insert USB cable, I end up in QDLoader 9008 mode. There is still hope if LeEco ever releases service rom for Le Pro 3 just like it released earlier for Le1, Le2, Le Max 2 etc. Leeco.re has all the firmwares except Le Pro 3.
Flagship my ass, LeEco ripped us off with its amazing chinese U-turn yet again. There is no hope in unbricking the phone unless I get QFill factory service rom meant to be compatible with QPST flasher.
Attempt 4:
Finally found the unbrick service rom which is to be flashed with FlashOne program but turns out the file is incomplete.
Ref Thread: http://www.leeco.re/topic/1906-helpx720-bricked/#comment-33155
I charged my x720 last night (just 10 hrs ago), drove to office with battery last known at 87% just 30 minutes ago.
I took it out of my pocket, sent a couple of text msgs, put it on my office table. Now all of a sudden phone is black, no display, no sign of life except short two vibrations everytime I try to turn it on. I have no idea what has just happened. Still got 6 hrs to stay at office then to home where I might try to charge/put phone to PC and check....
I literally have no idea what just happened.
I'm on CM13 by Team Superluminal and never had any problems like this in the past....
I'll update what was the problem once I get home and thoroughly check my phone :/
Click to expand...
Click to collapse
leave power button and vol down pressed for some time........ it's not the normal waiting time....... just leave it pressed until you get into download mode......
it happened to me with a past custom rom.......... your boot-loader may be locked again......
TURBO
TURBO2012 said:
leave power button and vol down pressed for some time........ it's not the normal waiting time....... just leave it pressed until you get into download mode......
it happened to me with a past custom rom.......... your boot-loader may be locked again......
TURBO
Click to expand...
Click to collapse
Phone vibrates very momentarily after about 10 seconds of holding power button and then vibrates like that every 10 seconds if I keep power button pressed.
I connected it to my Computer and it shows up as QUSB_BULK in device manager. Looks like my device is bricked until LeEco releases QFIL files for Le Pro3. I already have installed Qualcomm QDLoader 9008 drivers.
I am leaving this phone on charger overnight and will check if Battery really was depleted this fast in-case phone lives up. Otherwise its a sad story until LeEco releases QFIL files.
Update # 2
I managed to connect my phone stable with Computer without any stupid black rebooting.
I'm able to see my device in ADB under recovery, and ADB under composite interface and even I can issue ADB Reboot Bootloader command to take it to fastboot.
If I just flash TWRP, it flashes successfully but stays black. Even if I boot recovery image, it reboots into composite interface instead.
Next stop: Grossoshop fastboot rom. Im downloading it right now from https://mega.nz/#!VEM1QIYL!HwT9hk7-GA6KZBTRMv0IQ9kleYaG-el63UF21S6P0us
I REALLY REALLY REALLY HOPE IT WORKS. Phone died on me while on nearly full battery so if it stayed on during whole day it still would have half the juice left to be flashed in fastboot. I don't know if the phone is recharging on adapter or not.
Code:
D:\ADB>adb devices
List of devices attached
50a2127e recovery
D:\ADB>adb reboot bootloader
D:\ADB>adb devices
List of devices attached
D:\ADB>fastboot devices
50a2127e fastboot
D:\ADB>fastboot flash recovery lepro3_twrp.img
target reported max download size of 536870912 bytes
sending 'recovery' (47052 KB)...
OKAY [ 1.313s]
writing 'recovery'...
OKAY [ 0.328s]
finished. total time: 1.641s
D:\ADB>fastboot boot lepro3_twrp.img
downloading 'boot.img'...
OKAY [ 1.331s]
booting...
OKAY [ 0.344s]
finished. total time: 1.675s
D:\ADB>adb reboot -p
D:\ADB>adb devices
List of devices attached
50a2127e device
D:\ADB>adb reboot recovery
D:\ADB>adb reboot bootloader
D:\ADB>fastboot devices
50a2127e fastboot
D:\ADB>fastboot oem device-info
...
(bootloader) Device product name: [le_zl1_whole_netcom]
(bootloader) Device tampered: false
(bootloader) Device unlocked: true
(bootloader) Device critical unlocked: true
(bootloader) Charger screen enabled: false
(bootloader) Serial console enabled: false
(bootloader) Serial hw output enabled: false
(bootloader) Display panel:
OKAY [ 0.078s]
finished. total time: 0.078s
D:\ADB>
Update # 3 Phone is still in coma after flashing Grossoshop 17s rom via fastboot
Incomplete log since the batch file window can't be maximized or scrolled
Code:
*****
**********************************************************************
***** FLASH SYSTEM *****
**********************************************************************
target reported max download size of 536870912 bytes
erasing 'system'...
OKAY [ 0.000s]
sending sparse 'system' (487311 KB)...
OKAY [ 14.516s]
writing 'system'...
OKAY [ 9.544s]
sending sparse 'system' (518775 KB)...
OKAY [ 14.934s]
writing 'system'...
OKAY [ 7.324s]
sending sparse 'system' (524287 KB)...
OKAY [ 15.657s]
writing 'system'...
OKAY [ 5.031s]
sending sparse 'system' (524284 KB)...
OKAY [ 15.755s]
writing 'system'...
OKAY [ 4.486s]
sending sparse 'system' (500922 KB)...
OKAY [ 15.109s]
writing 'system'...
OKAY [ 7.818s]
sending sparse 'system' (484095 KB)...
OKAY [ 14.501s]
writing 'system'...
OKAY [ 89.072s]
finished. total time: 213.780s
**********************************************************************
***** FLASH KERNEL *****
**********************************************************************
target reported max download size of 536870912 bytes
sending 'boot' (35764 KB)...
OKAY [ 1.016s]
writing 'boot'...
OKAY [ 0.234s]
finished. total time: 1.266s
**********************************************************************
***** FLASH TWRP *****
**********************************************************************
target reported max download size of 536870912 bytes
sending 'recovery' (48272 KB)...
OKAY [ 1.344s]
writing 'recovery'...
OKAY [ 0.344s]
finished. total time: 1.687s
**********************************************************************
***** REBOOT RECOVERY *****
**********************************************************************
-- If process was OKAY.....
-- Press any Key to start Recovery then.....
1. Wipe DATA, CACHE and DALVIK CACHE for new rom installation.....
2. Wipe CACHE and DALVIK CACHE if you are updating BB72 rom.....
3. Restart at the end of the process.....
-- First boot takes long.....
D:\ADB\GSLEPRO3\18S>
Update # 4:
Phone is still dead, only recognizeable through ADB, Fastboot, QDLoader 9008. Screen never comes alive, only the vibrator gives the sign of life if not for the device Manager.
I managed to flash the mbn, elf and bin files to corresponding parittions with no errors, then I flashed official boot.img, splash.img and stock recovery but upon reboot, phone is still dead.
Dang it man. I in the same boat. I can get to the fastboot and that is it. If i try to boot recovery it flashes the recovery screen and then goes back... im so dumb for even trying to unlock and flash a rom on this thing...
Same here - qdload 9008 mode and no qfil compatible rom pack from LeEco. Relying blindly on them releasing the files sometime in the future seems like a lost cause to me.
coolmaster121 said:
Dang it man. I in the same boat. I can get to the fastboot and that is it. If i try to boot recovery it flashes the recovery screen and then goes back... im so dumb for even trying to unlock and flash a rom on this thing...
Click to expand...
Click to collapse
I am out and have OmniRom installed atm. Thank your XDA!
In case this helps you guys fix it:
https://forum.xda-developers.com/showpost.php?p=71704244&postcount=595
coolmaster121 said:
I am out and have OmniRom installed atm. Thank your XDA!
In case this helps you guys fix it:
https://forum.xda-developers.com/showpost.php?p=71704244&postcount=595
Click to expand...
Click to collapse
Your case was different. At least ur phone showed signs of life by momentarily showing u the recovery screen. My phone doesn't live up at all not even. LED notification light or screen. Just fastboot or ADB or QDLoader.....
Had a similar effect yet from different reason. I dropped my phone in salty water (I thought it would survive as it did in fresh water for a minute LoL) and it won't turn off but just in a boot loop to Recovery.
Then the screen died, won't turn on at all, phone vibrates once or twice every restart infinitely. The battery drained out and I put the phone in a bucket of rice for a day and voila it turned on again. I was able to relock the bootloader and sent it back for repair (with fingers crossed hoping they won't dismantle the phone and find water traces inside =D). They replaced it with new one and so I am happy camper again. =D
Joms_US said:
Had a similar effect yet from different reason. I dropped my phone in salty water (I thought it would survive as it did in fresh water for a minute LoL) and it won't turn off but just in a boot loop to Recovery.
Then the screen died, won't turn on at all, phone vibrates once or twice every restart infinitely. The battery drained out and I put the phone in a bucket of rice for a day and voila it turned on again. I was able to relock the bootloader and sent it back for repair (with fingers crossed hoping they won't dismantle the phone and find water traces inside =D). They replaced it with new one and so I am happy camper again. =D
Click to expand...
Click to collapse
I just happened to buy the phone and get it shipped to wrong country where Leeco support doesn't exist neigther the country supports such repair correspondance. Customs here will charge me around 150$ when I will recieve my phone after repair, moreover my Leeco warranty isnt covered because I didnt buy from their official store (rather a chinese store through a friend and get it shipped to me). So Im left out in the dark waiting for the on-shelf recovery measures.
Man, sucks when we break it this much, huh? I just tried to remove the encryption (was asking for password) after having gotten encrypted from flashing TARS 21s on my 727. Now I can fastboot and see recovery but I can't push any files because adb says it's "unauthorized".... I can't authorise because I have no OS!!! No files either obviously, I just wiped the storage entirely to remove that encryption. Anybody have any ideas on this one? Going to have use a Walmart burner for a little while until I can get a usb-c OTG drive. That's the only thing I can think of since I CAN enter recovery/fastboot flash things
benjmiester said:
Man, sucks when we break it this much, huh? I just tried to remove the encryption (was asking for password) after having gotten encrypted from flashing TARS 21s on my 727. Now I can fastboot and see recovery but I can't push any files because adb says it's "unauthorized".... I can't authorise because I have no OS!!! No files either obviously, I just wiped the storage entirely to remove that encryption. Anybody have any ideas on this one? Going to have use a Walmart burner for a little while until I can get a usb-c OTG drive. That's the only thing I can think of since I CAN enter recovery/fastboot flash things
Click to expand...
Click to collapse
Do you have twrp installed? And an OTG?
benjmiester said:
Man, sucks when we break it this much, huh? I just tried to remove the encryption (was asking for password) after having gotten encrypted from flashing TARS 21s on my 727. Now I can fastboot and see recovery but I can't push any files because adb says it's "unauthorized".... I can't authorise because I have no OS!!! No files either obviously, I just wiped the storage entirely to remove that encryption. Anybody have any ideas on this one? Going to have use a Walmart burner for a little while until I can get a usb-c OTG drive. That's the only thing I can think of since I CAN enter recovery/fastboot flash things
Click to expand...
Click to collapse
You can try "adb sideload" in twrp usually it bypasses "unauthorized" status and flashes away directly.
ivangotoy said:
You can try "adb sideload" in twrp usually it bypasses "unauthorized" status and flashes away directly.
Click to expand...
Click to collapse
That actually did the trick, thanks! I'd be really screwed without TWRP booting.
We, in the qh-usb boat, are rly screwed right now
benjmiester said:
That actually did the trick, thanks! I'd be really screwed without TWRP booting.
Click to expand...
Click to collapse
I am screwed. Can yu explain how this adb sideload worked?
zman123 said:
I am screwed. Can yu explain how this adb sideload worked?
Click to expand...
Click to collapse
Sorry I didn't see this earlier. I was lucky in that my phone would still work in fastboot mode with my computer even though adb push would not so I couldn't push files to flash.
If you can get to twrp, or fastboot (volume DOWN + power, hold until it boots to fastboot screen) then you can open fastboot command window on PC, type fastboot devices and make sure it shows a device is attached and recognized. If so, flash twrp with command fastboot flash boot twrp.zip (or whatever you name it). Once in twrp, you can go to sideload option, have to toggle it on in twrp and it will say ready (waiting to accept zip over adb). Then have rom zip and gapps zip in adb/fastboot folder on pc.
Use command adb sideload rom.zip then same for gapps.zip. It will show progress on the phone if working.
benjmiester said:
Sorry I didn't see this earlier. I was lucky in that my phone would still work in fastboot mode with my computer even though adb push would not so I couldn't push files to flash.
If you can get to twrp, or fastboot (volume DOWN + power, hold until it boots to fastboot screen) then you can open fastboot command window on PC, type fastboot devices and make sure it shows a device is attached and recognized. If so, flash twrp with command fastboot flash boot twrp.zip (or whatever you name it). Once in twrp, you can go to sideload option, have to toggle it on in twrp and it will say ready (waiting to accept zip over adb). Then have rom zip and gapps zip in adb/fastboot folder on pc.
Use command adb sideload rom.zip then same for gapps.zip. It will show progress on the phone if working.
Click to expand...
Click to collapse
Thank you! I was finally able to get sideload to work. I was using Darkobas recovery and that caused issues. Flashing normal TWRP worked. I was able to get back to stock via recovery so know I am trying to fix the prolem that started this mess... Google play store wont work on cellular..... most annoying problem in the world!
Hello,
I was trying to bring phone back to factory state and I messed things up. My options are very limited and I'd like to ask for help.
I have Revolution Recovery installed on my phone. I made backups of data, system, boot, oeminfo, cust. I flashed custom oeminfo from this thread. I hoped to download a rescue package via Huawei eRecovery. But it said that my data partition is corrupted and asked me to format it. So I did. My data is wiped and formatted. But it shows cannot download package after trying.
Right now, I can access fastboot, but I cannot flash anything:
Code:
$ fastboot flash recovery ~/Desktop/RevolutionRecovery_Nougat_P9Lite/TWRP.img
target reported max download size of 471859200 bytes
sending 'recovery' (27434 KB)...
OKAY [ 0.691s]
writing 'recovery'...
FAILED (remote: Command not allowed)
finished. total time: 0.697s
When I try to start the phone (normal start, or volume up + power key) it goes straight to Huawei eRecovery. I cannot open recovery.
My phone is VNS-L31, before any changes I wrote down build number from system settings: VNS-L31C432B371. I bought it through an online store in Switzerland last summer, so I probably have some Europe edition. I don't have any backups from the initial state before I even had my custom rom installed.
Is there any chance to install recovery or whatever straight from SD card?
I'm happy to provide any additional data if I know what else is needed.
Thanks for help!
There is. That "FAILED (remote: Command not allowed)" just means you somehow locked your booloader again.
Mou must revert back to MM, which uses dload method.
It is quite easy, just follow https://forum.xda-developers.com/hu...torial-rollback-n-to-mm-c432-devices-t3563955
Hi all I've been searching for help but can't find many similar cases to mine.
Here is the situation: after rooting my huawei p8 lite 2017 with magisk I installed xposed framework and it soft bricked my device (again for the third time this week)
I decided to restore a backup i had made, when i had magisk root but no xposed installed, via TWRP
The backup ends but the phone won't boot and TWRP doesn't want to boot either, it continues to boot between twrp and the stock rom without success.
In fastboot i can't find info of my phone to download the right software from a site to do dload but I do have an update.app file for my phone
When i flash boot.img it gives me:
C:\adb>fastboot flash boot BOOT.img
target reported max download size of 471859200 bytes
sending 'boot' (15524 KB)...
OKAY [ 0.389s]
writing 'boot'...
FAILED (remote: partition length get error)
finished. total time: 0.413s
My info is this:
bootloader: unlocked
recovery: not working
huawei eRecovery: tried but failed to boot after
fastboot: partly working
the android version is 8.0
device : PRA-LX1C432B209
I cannot use dload with the update.app from firmware finder
If anyone could help me i would be very thankfull.
I have a motorola g4 play (HARPIA) phone, with the latest lineageos version available to ir, it was not used by several months and when turned on it lasted a couple of minutes at the initial screen (the blank one that says the phone is unlocked) and then battery died (my bad)
And now the phone fails at all when starting... it shows an error
Start Up Failed:
Your device didn't start up successfully.
Use the Software Repair Assistant on computer to repair your device.
Connect your device to your computer to get the Software Repair Assistant.
I have adb & fastboot installed (it is a linux machine), adb do not see the device at all... using fastboot I have tried to flash recovery img file and it shows:
(bootloader) has-slot:recovery: not found
(bootloader) is-logical:recovery: not found
Sending ' recovery' (14526 KB) OKAY 0.876 s
Writing 'recovery' OKAY 0.188 s
Finished. Total time 1.423 s
Then tried to go to recovery mode and it fails...:
failed to validate recovery image
ERROR: Failed to pass to pass validaton, backup to fastboot
Boot up failed
Any idea? What to check? what to do? what to try? D-:
A very LONG time ago I have used a windows application, that flashed motorola factory rom files... someone remembers the name? and where to find those factory roms?
At first get Google's up-to-date ADB and fastboot for Linux.
Then get the latest TWRP recovery for harpia.
Then boot yout device to bootloader mode.
Now try the boot-option within fastboot:
--> fastboot boot <twrp-recovery>.img
(Maybe try different USB-cables if this fails)
Now you can install/update TWRP within this booted TWRP instance
--> switch to install image and choose the recovery partition to install it.