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!
Related
I think i may have bricked my nexus 10.. I was trying to install the chainfire3d application from the market, and when it rebooted, it wouldnt go past the X logo. waited for a long time, so i tried a hard reset, and still nothing. So i figured i would try using the toolkit to help fix. tried to relock, flash, and re-unlock, and it wouldnt work..after the step where you go into factory reset/wipe, it woudlnt go further. I cant get a custom recovery to install, it wont save the file. tried doing that step separately, and it seems to stick on sending the file over. this seems to be a common issue with anything i try.
The screen says:
"sending TWRP touch recovery..
sending 'recovery' (7246 KB) ...
and is just stuck there. this seems to happen in several places, with a few different things ive tried. When trying to flash the stock image, it will get stuck in similar places, perhaps not with the recovery step, but with a portion of the stock image. Been at this for a couple of hours... any help would be greatly appreciated!.
Also, as of now... it wont boot past the google logo. I can get it into fastboot by holding down the buttons, and I can get it into the stock recovery, but thats it. I don't even think adb is detecting the device. I have a feeling that may be a major roadblock to getting this thing fixed. Does anyone know how I can get the tablet to be detected by adb if i cant even get past the google logo screen at boot?
Update 1:
Still cant unbrick my device. any time i try to transfer or flash files to it... it stalls, and if i disconnect the device, i get this error:
FAILED (data transfer failure (too many links)).
Your Device will now boot into Android and detect ADB mode.
problem is, it doesnt reboot, and even if it did, it wouldnt be able to boot into android, since it wont go past the google logo when the device turns on. in fact, i cant even turn it off. only way to turn it off would be to wait for the battery to drain.
If this helps, here is what it says on the fastboot screen:
Device Information
Product Name: manta
Variant: wifi
H/W version : 8
Bootloader Version: MANTALJ12
Carrier Info: none
Serial Number: *********** (not going to publish that, lol)
LOCK STATE: Unlocked
Reboot Mode Flag: none.
anyone have any ideas at all how I can salvage this thing? Im kindof embarrassed honestly. Ive had 5 android devices prior to this one, and have rooted, flashed, and reflashed each of them countless times, and never, ever ran into this before. I could really use the help.
Quick note:
I just noticed that when i try to flash anything to the tablet, the following appears under the rest of the info i listed above.
FASTBOOT STATUS - DATA00713800 (this text is highlighted in light blue)
Update 2:
ok, so i tried to do the factory restore, and am running into the same wall as always. here is the text from the window, perhaps that may clue you into the problem:
7-Zip (A) 9.20 Copyright (c) 1999-2010 Igor Pavlov 2010-11-18
Processing archive: put_google_factory_image_here\mantaray-jop40c-factory-0d641789.tg
z
Extracting mantaray-jop40c-factory-0d641789.tar
Everything is Ok
Size: 329369600
Compressed: 326396069
Now extracting flashable Images
7-Zip (A) 9.20 Copyright (c) 1999-2010 Igor Pavlov 2010-11-18
Processing archive: put_google_factory_image_here\mantaray-jop40c-factory-0d641789.ta
r
Extracting mantaray-jop40c
Extracting mantaray-jop40c\image-mantaray-jop40c.zip
Extracting mantaray-jop40c\flash-base.sh
Extracting mantaray-jop40c\bootloader-manta-mantalj12.img
Extracting mantaray-jop40c\flash-all.sh
Extracting mantaray-jop40c\flash-all.bat
Everything is Ok
Folders: 1
Files: 5
Size: 329358105
Compressed: 329369600
Factory Images extracted. Starting Flash Process.
Now Flashing Bootloader Image..
sending 'bootloader' (1280 KB)... OKAY [ 0.232s]
writing 'bootloader'... OKAY [ 0.113s]
finished. total time: 0.345s
rebooting into bootloader... OKAY [ 0.001s]
finished. total time: 0.001s
Now Flashing Factory Image: Boot, Cache, Recovery, System and Userdata..
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: MANTALJ12
Baseband Version.....: no modem
Serial Number........: R32CB01KDWW
--------------------------------------------
checking product... OKAY [ 0.001s]
checking version-bootloader... OKAY [ 0.002s]
sending 'boot' (4606 KB)...
Its just stuck on that last part, sending 'boot' (4606 KB)...
and under all the info on the fastboot page, the following appeared while this was happening:
FASTBOOT STATUS - DATA0047f800 (this line is highlighted in light blue)
*Bump* That's really unfortunate. I managed to fixed my soft brick after unlocking and flashing TWRP with a factory image. There was no highlighted blue text, everything went smooth. I hope your issue get fixed
P.S. I did not use the toolkit. If you can boot to your bootloader (fastboot), try running the shell/batch scripts included with the factory image? (This is just following Google's instruction on the factory image download page)
cuguy said:
*Bump* That's really unfortunate. I managed to fixed my soft brick after unlocking and flashing TWRP with a factory image. There was no highlighted blue text, everything went smooth. I hope your issue get fixed
P.S. I did not use the toolkit. If you can boot to your bootloader (fastboot), try running the shell/batch scripts included with the factory image? (This is just following Google's instruction on the factory image download page)
Click to expand...
Click to collapse
can you link it?
cuguy said:
*Bump* That's really unfortunate. I managed to fixed my soft brick after unlocking and flashing TWRP with a factory image. There was no highlighted blue text, everything went smooth. I hope your issue get fixed
P.S. I did not use the toolkit. If you can boot to your bootloader (fastboot), try running the shell/batch scripts included with the factory image? (This is just following Google's instruction on the factory image download page)
Click to expand...
Click to collapse
trying that....
so far so good... dont want to get my hopes up though... below is what ive got so far in the cmd screen:
sending 'bootloader' (1280 KB)...
OKAY [ 0.162s]
writing 'bootloader'...
OKAY [ 0.125s]
finished. total time: 0.288s
rebooting into bootloader...
OKAY [ 0.002s]
finished. total time: 0.003s
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: MANTALJ12
Baseband Version.....: no modem
Serial Number........: R32CB01KDWW
--------------------------------------------
checking product...
OKAY [ 0.001s]
checking version-bootloader...
OKAY [ 0.002s]
sending 'boot' (4606 KB)...
OKAY [ 32.528s]
writing 'boot'...
OKAY [ 0.116s]
sending 'recovery' (5106 KB)...
OKAY [ 56.840s]
writing 'recovery'...
OKAY [ 0.119s]
sending 'system' (528847 KB)...
Its been about 30 minutes now... and its still stuck on "sending 'system' (528847 KB)..." in the cmd window.... not sure what that means... it did take about a minute for the recovery to get sent over, and its about 100x larger in size, so i guess i will leave it connected like this for the next hour or so... and hope that it is just going REALLY slowly. Got my fingers crossed...
Battery died while waiting.... this is the complete text of the CMD screen while i was waiting.. forgot that it doesnt charge while in fastboot. got it plugged into an outlet for faster charging while its off.... hopefully when its charged up, i can try again and ill continue to progress
sending 'bootloader' (1280 KB)...
OKAY [ 0.162s]
writing 'bootloader'...
OKAY [ 0.125s]
finished. total time: 0.288s
rebooting into bootloader...
OKAY [ 0.002s]
finished. total time: 0.003s
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: MANTALJ12
Baseband Version.....: no modem
Serial Number........: R32CB01KDWW
--------------------------------------------
checking product...
OKAY [ 0.001s]
checking version-bootloader...
OKAY [ 0.002s]
sending 'boot' (4606 KB)...
OKAY [ 32.528s]
writing 'boot'...
OKAY [ 0.116s]
sending 'recovery' (5106 KB)...
OKAY [ 56.840s]
writing 'recovery'...
OKAY [ 0.119s]
sending 'system' (528847 KB)...
FAILED (data transfer failure (Too many links))
finished. total time: 3941.094s
Press any key to exit...
Did you try to run e2fsck on all partitions (boot, system, userdata) and check whether there are any errors?
You can run it via adb once you boot into TWRP or CWM recovery. Here is more info:
http://forum.xda-developers.com/showthread.php?p=34923662
Ps.
I also bricked my nexus 10 while transferring files on it in windows. Nothing so far helped me. e2fsck doesn't see any partitions
I believe this is something to-do with a corrupted flash memory. Your case looks about the same.
jodvova said:
Did you try to run e2fsck on all partitions (boot, system, userdata) and check whether there are any errors?
You can run it via adb once you boot into TWRP or CWM recovery. Here is more info:
http://forum.xda-developers.com/showthread.php?p=34923662
Ps.
I also bricked my nexus 10 while transferring files on it in windows. Nothing so far helped me. e2fsck doesn't see any partitions
I believe this is something to-do with a corrupted flash memory. Your case looks about the same.
Click to expand...
Click to collapse
I cant get it to load a custom recovery! any advice on how to get that going?
ltracte said:
I cant get it to load a custom recovery! any advice on how to get that going?
Click to expand...
Click to collapse
So, if you run "fastboot boot twrp-image.img" under your current bootloader it doesn't boot it?
Also, If I remember it correctly, you can also boot in to a existing recovery and then run shell commands via adb.
ltracte said:
I cant get it to load a custom recovery! any advice on how to get that going?
Click to expand...
Click to collapse
Dumb question, if using a desktop PC are you using the front or rear USB ports? I had a similar issue where it would just get stuck on the "sending system" message. Switched the USB from front port to back port on my linux box and it solved my problem.
Sent from my Nexus 10 using Tapatalk 2
jodvova said:
So, if you run "fastboot boot twrp-image.img" under your current bootloader it doesn't boot it?
Also, If I remember it correctly, you can also boot in to a existing recovery and then run shell commands via adb.
Click to expand...
Click to collapse
i got twrp to load that way! thanks... what now? i cant get the device to mount so i can put the zip file of a rom on there.
ltracte said:
i got twrp to load that way! thanks... what now? i cant get the device to mount so i can put the zip file of a rom on there.
Click to expand...
Click to collapse
What I meant was, you can now run e2fsck and check all partitions for consistency. Refer to a thread that I posted a few comments back. You can run e2fsck either via a terminal session in TWRP or via adb shell.
jodvova said:
What I meant was, you can now run e2fsck and check all partitions for consistency. Refer to a thread that I posted a few comments back. You can run e2fsck either via a terminal session in TWRP or via adb shell.
Click to expand...
Click to collapse
couldnt get the command to work via adb, so i tried it using terminal inside TWRP, and this what it spit back at me:
/dev/block/platform/dw_mmc.0/by-name/system: clean. 11/51296 files. 6651/204800 blocks
i have no idea what that means, nor what else to do....
Fixed it!!!!
ltracte said:
Fixed it!!!!
Click to expand...
Click to collapse
Glad you fixed your problem. Please post any relevant information that may help people in the same situation.
Mark.
mskip said:
Glad you fixed your problem. Please post any relevant information that may help people in the same situation.
Mark.
Click to expand...
Click to collapse
well.. i loaded it into the bootloader, unzipped the factory image, and everything inside it into the platform-tools folder in my android sdk directory on my pc so i could use ADB
then i did the following via adb
fastboot flash bootloader bootloader-manta-mantalj12.img
fastboot reboot-bootloader
fastboot -w update image-mantaray-jop40c.zip.
the first time it got stuck pushing the system.img file, i let it run for almost an hour before giving up. then the battery on the tablet died. let it charge for about an hour, plugged it back in, reran the last command from above, and for some reason, the whole thing went through without a hitch. wish i could explain why it worked that time, but I cant. hope this helps someone else that encountered the issue.
thanks again to everyone that offered any input!
Whew! So glad you finally had success & thanks for sharing. I'm reading up, research, etc. I received my N10 yesterday. I'm getting ready to unlock/root today.
Sent from my Nexus 7 using Tapatalk 2
ltracte said:
well.. i loaded it into the bootloader, unzipped the factory image, and everything inside it into the platform-tools folder in my android sdk directory on my pc so i could use ADB
then i did the following via adb
fastboot flash bootloader bootloader-manta-mantalj12.img
fastboot reboot-bootloader
fastboot -w update image-mantaray-jop40c.zip.
the first time it got stuck pushing the system.img file, i let it run for almost an hour before giving up. then the battery on the tablet died. let it charge for about an hour, plugged it back in, reran the last command from above, and for some reason, the whole thing went through without a hitch. wish i could explain why it worked that time, but I cant. hope this helps someone else that encountered the issue.
thanks again to everyone that offered any input!
Click to expand...
Click to collapse
Hmm, did you try the flash-all.bat file that comes with the factory image? It does those 3 commands, + erases all partitions automatically.
ltracte said:
well.. i loaded it into the bootloader, unzipped the factory image, and everything inside it into the platform-tools folder in my android sdk directory on my pc so i could use ADB
then i did the following via adb
fastboot flash bootloader bootloader-manta-mantalj12.img
fastboot reboot-bootloader
fastboot -w update image-mantaray-jop40c.zip.
the first time it got stuck pushing the system.img file, i let it run for almost an hour before giving up. then the battery on the tablet died. let it charge for about an hour, plugged it back in, reran the last command from above, and for some reason, the whole thing went through without a hitch. wish i could explain why it worked that time, but I cant. hope this helps someone else that encountered the issue.
thanks again to everyone that offered any input!
Click to expand...
Click to collapse
That's exactly what I did. Just followed the factory image flashing instruction on google's page(where you download the image file for N10). Did you figure out why it wassnt able to transfer the first time?
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 originally did a boot unlock, a fash of twrp-2.8.7.2-angler.img, and when I could not get the pattern on twrp recovery to function, I did a sideload of the twrp.img instead of an install.
This failed in a boot loop.
SO I did a flash back to stock with angler-mdb08m-factory-dbc17940.tgz (after unpacking this).
Then I restored all my apk, etc.
BUT now when I do:
fastboot flash recovery twrp-2.8.7.2-angler.img, I SEE:
target reported max download size of 494927872 bytes
sending 'recovery' (16880 KB)...
OKAY [ 0.561s]
writing 'recovery'...
OKAY [ 0.247s]
finished. total time: 0.809s
---- all looks fine, but the device itself does not seem to react and when I reboot, and select recovery, it just goes into Google recovery.
Has anyone else seen this, and do you know how to get past this?
I already tried to unlock again and it tells me error, already unlocked.
So my next step would be to do a lock and then an unlock again, but that would probably cause me to take several hours restoring after another flash to stock, and I fear that I will be back where I am now??? any thoughts??
SOLVED!
It seems that somehow, I just hadn't waited long enough. I was able to now reboot into recovery.
Thanks to any that looked at this issue.
I was trying to install the AOSiP rom and when I I was doing the twrp installation:
fastboot flash boot twrp-mata_11.img
the error pops out:
target reported max download size of 536870912 bytes
sending 'boot_a' (45048 KB)...
OKAY [ 1.196s]
writing 'boot_a'...
FAILED (remote: Error flashing partition.)
finished. total time: 1.856s
I don't see same errors over the XDA forum. can someone help me?
p.s. screen now is showing fastboot mode
device state - unlocked
Did you unlock critical?
Sent from my ONEPLUS 3T using Tapatalk
seabro01 said:
Did you unlock critical?
Sent from my ONEPLUS 3T using Tapatalk
Click to expand...
Click to collapse
uhh no I did not see that in the tutorial.
I tried: ./fastboot flashing unlock_critical
and looks like it freezes after that command...
ytlei said:
I was trying to install the AOSiP rom and when I I was doing the twrp installation:
fastboot flash boot twrp-mata_11.img
the error pops out:
target reported max download size of 536870912 bytes
sending 'boot_a' (45048 KB)...
OKAY [ 1.196s]
writing 'boot_a'...
FAILED (remote: Error flashing partition.)
finished. total time: 1.856s
I don't see same errors over the XDA forum. can someone help me?
p.s. screen now is showing fastboot mode
device state - unlocked
Click to expand...
Click to collapse
are you rooted?
have you tried downloading the file again?
and if you can still go to bootloader your phone is not bricked, just download stock boot from essential and flash it
yenkoPR said:
are you rooted?
have you tried downloading the file again?
and if you can still go to bootloader your phone is not bricked, just download stock boot from essential and flash it
Click to expand...
Click to collapse
no not rooted
now im trying to flash back to stock, but when I run flash-all.sh error keeps popping up:
remote: Error flashing partition.
FAILED (remote: Error flashing partition.)
finished. total time: 2.025s
target reported max download size of 536870912 bytes
sending 'boot_b' (65536 KB)...
OKAY [ 1.735s]
writing 'boot_b'...
FAILED (remote: Error flashing partition.)
finished. total time: 1.782s
target reported max download size of 536870912 bytes
sending 'cmnlib_a' (512 KB)...
OKAY [ 0.103s]
writing 'cmnlib_a'...
FAILED (remote: Error flashing partition.)
finished. total time: 0.169s
target reported max download size of 536870912 bytes
sending 'cmnlib_b' (512 KB)...
OKAY [ 0.101s]
writing 'cmnlib_b'...
FAILED (remote: Error flashing partition.)
finished. total time: 0.188s
...
Dang now its totally bricked after the flashing failure... cannot boot up. what should I do? send it back to Essential?
What do you mean by can't boot up? Do you see boot animation and have you tried to go back to fast boot or recovery?
Sent from my ONEPLUS 3T using Tapatalk
Try different USB ports and cables. When 8.1 came out I had to swap my cable and change the port I was using on my desktop, for some reason the cable I had been using and the port I had been using since I got the phone was no longer adequate. There were a number of other people having the same issue. Some commands would look to complete properly, but following up with the same command (something un-damaging like fastboot --set-active=a | fastboot --set-active=b) would either error again or show that the 'completed' command hadn't actually done anything. I switched cables/ports around (ended up with an Antek USB-A to USB-C cable in a USB3.1 port) and everything worked properly.
If you're trying to flash a stock build image from Essential, you will probably need critical unlocked because those images do contain a bootloader that gets flashed, and that is secured behind critical.
ytlei said:
Dang now its totally bricked after the flashing failure... cannot boot up. what should I do? send it back to Essential?
Click to expand...
Click to collapse
What cable are you using?
Do not use the cable that came with the phone!!!!!
We are screwed mate, I am on the same boat with you. Essential took no responsibility and offered a 200$ replacement device. The phone doesn't power on anymore and no light indicators are working, so hard bricked.
I had a Asoip screw up(did not disable password) and was only able to get fastboot. Had to see what slot was active and flashed to that slot that was active boot.img,twrp,Asoip and was back up and running. My bootloader was unlocked. I read through all the posts and peoples screw ups and was able to get it up and running again in a day. I never posted as I wanted to learn it on my own. Good luck.........
ytlei said:
I was trying to install the AOSiP rom and when I I was doing the twrp installation:
fastboot flash boot twrp-mata_11.img
the error pops out:
target reported max download size of 536870912 bytes
sending 'boot_a' (45048 KB)...
OKAY [ 1.196s]
writing 'boot_a'...
FAILED (remote: Error flashing partition.)
finished. total time: 1.856s
I don't see same errors over the XDA forum. can someone help me?
p.s. screen now is showing fastboot mode
device state - unlocked
Click to expand...
Click to collapse
What cable did you use while connecting to your computer?
And what is the status now? Are you able to turn it on at all by volume and power key combination?
same here. The phone doesn't power on anymore. btw I used the usb-c TDB cable came with my MacBook pro.
I sent email to essential and they say they can't help me since I tried to flash custom rom...
ytlei said:
same here. The phone doesn't power on anymore. btw I used the usb-c TDB cable came with my MacBook pro.
I sent email to essential and they say they can't help me since I tried to flash custom rom...
Click to expand...
Click to collapse
and pressing the volume down key + power key at the same time doesn't work?.. what happens when you plug your phone into the charger? does it vibrate?
ive had fastboot command problems previously myself with this device and found that the usb port can play a pretty large factor. Swapping usb ports and reattempting to run the commands (as others recommended may be useful) make sure you are using latest version of adb/fastboot and have up to date drivers installed for the phone.
Look at the rooting tutorial there is information in there about swapping active slots (the essential has both a and b paritions) if you set the other slot as the active slot you may be able to regain some communication within fastboot (i would suggest you verify with fastboot devices prior to attempting to flash to partitions).
Additionally you should be able to still recover back to stock without custom recovery using the default recovery partition. I would think that if you are able to access the bootloader you should be able to access the default essential recovery partition. If you can access the standard recovery you should be able to factory reset the phone and sideload a new rom (id suggest the default factory image from essential until you can get back to square one)
I'm in the same boat. Tried to flash twrp after upgrading to 8.1 and got the same Error flashing partition, and now I'm stuck on the bootloader.
I've found that if I lock/unlock and lock/unlock critical it will let me flash the stock 8.1 boot and every other partition except for system and vendor, but gives a flash write error for those. I'm still unable to get past the bootloader.
Essential basically said I'm SOL. $200 out of warranty replacement assuming I live in the US, which I don't.
Mine was doing this too, but it was only a few days old so I returned it. I'm pretty sure it's defective flash memory.
My phone was doing this exact thing. Botched factory installs rendered my phone hardbricked.
Tried a thousand+ things to get it to turn on to no avail. LUCKILY I bought it second hand and have no warranty D:
I want to cry
I got my OnePlus 5 back from the OnePlus support people the other day (I'll provide background for that if requested, I don't want this to get too long), and just yesterday sat down to install TWRP and root it. I unlocked the bootloader with no issues, but then when it came time to install TWRP, I ran into the issue. So I'll be in fastboot, and will enter in the command prompt:
"fastboot flash recovery [the recovery file]"
Which will return the following:
"target reported max download size of 536870912 bytes
sending 'recovery' (25860 KB)...
OKAY [ 0.557s]
writing 'recovery'...
OKAY [ 0.007s]
finished. total time: 0.566s"
Which seems to indicate that everything works, right? But when I then enter the command:
"fastboot boot [recovery name]"
It returns:
"downloading 'boot.img'...
OKAY [ 0.530s]
booting...
OKAY [ 10.104s]
finished. total time: 10.638s"
and boots back into fastboot mode.
I have tried this on both my HP laptop which is running Window 8.1 and my Dell laptop which is running the most recent version of Debian (I used sudo), and to the same results. I have tried multiple tool kits such as the one mentioned in this thread:
https://forum.xda-developers.com/android/software/tool-tool-one-driversunlocktwrpfactory-t3358711
and the one mentioned here:
https://www.teamandroid.com/2017/07/12/download-oneplus-5-toolkit/
which (to the best of my knowledge) only seem to enter the same commands I do.
I have also tried unplugging the phone after flashing the recovery and using the button combos to enter the recovery. It always takes me to the default recovery instead of TWRP.
Some miscellaneous details:
The phone is unlocked.
I have developer options enabled and OEM unlocking is enabled.
I have done no modifications besides unlocking the phone.
I checked to make sure the phone is fully updated. It is.
I have no problem with erasing everything on the phone if need be.
I apologize in advance for any weird grammar usage, spelling mistakes, and/or formatting issues. Any and all help is much appreciated. I really have no clue what's going wrong here.
What TWRP are you trying to use?
I tried using version 3.2.2.0. I grabbed it from here: https: // twrp.me / oneplus / oneplus5. html
Nunna the Insane Gerbil said:
I tried using version 3.2.2.0. I grabbed it from here: https: // twrp.me / oneplus / oneplus5. html
Click to expand...
Click to collapse
It's not a good version. It's broken, in fact.
I'd recommend codeworkx 3.2.1-0
https://sourceforge.net/projects/cheeseburgerdumplings/files/15.1/cheeseburger/recovery/
It works, thank you so much!
Nunna the Insane Gerbil said:
It works, thank you so much!
Click to expand...
Click to collapse
You're welcome. :good: