I've follow instrucctions from this site to flash rooted pre-image to my phone:
http://www.asus-zenfone.com/2015/04/asus-zenfone-2-pre-root-systemimg.html
But no luck, I'm stucked after enter "flash system system.img" get <waiting for device> for ever, any idea how to continue?
Did you allow adb device on your phone. Did you install driver?
Yes I did, I did "adb devices" and returns my phone serial number.
Dumb question, did you reboot into bootloader?
Thanks for your help, but I did it, and get this message: "target reported max download size of 536870912 bytes"
U in Windows?
Yes, window 8.1
Sent from my ASUS_Z00AD using XDA Free mobile app
I did it on Linux but shouldn't be any different. Just put phone on bootloader mode, extract image to platform tools Folder and fastboot flash system system.img
afrugone said:
Thanks for your help, but I did it, and get this message: "target reported max download size of 536870912 bytes"
Click to expand...
Click to collapse
Just wait a few minutes, then the file will begin to transfer with log like this:
target reported max download size of 536870912 bytes
erasing "system"...
OKAY [ 6.014S]
sending sparse 'system' <524257 KB>
OKAY [528.321S]
sending sparse 'system'.....
............
It's a long process (maybe because I doesn't use the original cable by ASUS).
Thanks TieuphongDN,
Whe I got the the message "target reported max download size of 536870912 bytes" I thought that something was wrong, I wait as you told, and could flash the rom, thanks for your help
I was able to successfully root and update firmware from CN to WW using that tutorial and this thread too. Thank you!
hkdmjack said:
I was able to successfully root and update firmware from CN to WW using that tutorial and this thread too. Thank you!
Click to expand...
Click to collapse
so after u updated firmware CM to WW ..... can u go on 4G?? LTE??
hermieee said:
so after u updated firmware CM to WW ..... can u go on 4G?? LTE??
Click to expand...
Click to collapse
Nope, still working on that but I'm a novice at best at this so I'll keep trying things as new methods come out. H+ is more than sufficient now for the most part though.
Related
Hi guys,
I need some help, I'm rooted running on the stock rom.
I was running the 6.0 L and decided to update to 6.0.1 vie fastboot.
I followed this guide (http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928) section 10- and did the exact same thing.
Every thing was flashing fine till I reached system.img and this is what I get.
C:\SDK\android-sdk-windows\platform-tools\6.0.1>fastboot flash sysytem C:\SDK\android-sdk-windows\platform-tools\6.0.1\system.img
target reported max download size of 494927872 bytes
sending sparse 'sysytem' (463062 KB)...
OKAY [ 10.395s]
writing 'sysytem'...
FAILED (remote: Permission denied!)
finished. total time: 10.410s
I did not flash the recovery because it says it's optional. I proceeded with the vendor and rebooted the device. When the device starts I get a pop up saying : There's an internal problem with your device. Contact your manufacture for details.
In the setting im still on 6.0 L build but bootloader and radios are on the latest firmware.
any suggestions?
Thanks
I did some search and couldn't find a decent answer.
If this is copy/paste directly from Terminal, then you misspelled "system" in your initial command:
C:\SDK\android-sdk-windows\platform-tools\6.0.1>fastboot flash sysytem C:\SDK\android-sdk-windows\platform-tools\6.0.1\system.img
target reported max download size of 494927872 bytes
sending sparse 'sysytem' (463062 KB)...
OKAY [ 10.395s]
writing 'sysytem'...
FAILED (remote: Permission denied!)
finished. total time: 10.410s
Click to expand...
Click to collapse
Notice the bold, the command is looking for "sysytem" which does not exist. You'll be good to go, if the typo is removed.
SlimSnoopOS said:
If this is copy/paste directly from Terminal, then you misspelled "system" in your initial command:
Notice the bold, the command is looking for "sysytem" which does not exist. You'll be good to go, if the typo is removed.
Click to expand...
Click to collapse
:| facepalm...... thanks man, I should not flash things at 1 AM.
I assume I dont need to flash the BL and radios again? just wipe cache install boot, system and vendor?
mr.dj26 said:
:| facepalm...... thanks man, I should not flash things at 1 AM.
I assume I dont need to flash the BL and radios again? just wipe cache install boot, system and vendor?
Click to expand...
Click to collapse
Correct, as long as you flashed the proper bootloader and radio. Just keep it all matching and you should be set. I try to avoid doing phone tinkering at night lol just never feel like troubleshooting at that time if I mess up.
Sent from my Nexus 5X using Tapatalk
SlimSnoopOS said:
Correct, as long as you flashed the proper bootloader and radio. Just keep it all matching and you should be set. I try to avoid doing phone tinkering at night lol just never feel like troubleshooting at that time if I mess up.
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
lol, ya i'm falling asleep so i'll do it tomorrow, thanks again and good night.
So i think im bricked somehow, does anyone have a link for an update.zip to flash through fastboot? i cant boot into twrp or boot into the system either. please help
Not so cool huh
rubiicon59 said:
Not so cool huh
Click to expand...
Click to collapse
how is that even helpful?
If you get into download mode you can still fix it.
---------- Post added at 03:47 AM ---------- Previous post was at 03:46 AM ----------
I was in the same boat a few weeks back this guide helped me out. https://forum.xda-developers.com/v20/how-to/restore-v20-to-100-stock-bricked-devices-t3524903
jameslapc2 said:
If you get into download mode you can still fix it.
Click to expand...
Click to collapse
i try to boot into that mode and keeps on rebooting .
press volume up and connect the usb cable and it shows the little download box and then just reboots.
try to flash recovery via fastboot and get the following message
C:\adb>fastboot flash recovery recovery.img
target reported max download size of 536870912 bytes
sending 'recovery' (24092 KB)...
OKAY [ 0.734s]
writing 'recovery'...
FAILED (remote: unknown command)
finished. total time: 0.750s
the bootloader is unlocked,, get the same error when its locked too
Sorry, it wasn't.
I was looking at your sig..... found it ironic.
rubiicon59 said:
Sorry, it wasn't.
I was looking at your sig..... found it ironic.
Click to expand...
Click to collapse
yea i suppose lol
Can anyone help
My best guess would be if you have Jump just tell T-Mobile you updated your device and the update bricked it. It's worth a shot.
nofroyo said:
Can anyone help
Click to expand...
Click to collapse
I would definitely try the LGup method via download/firmware mode. I've used it before to save my behind. Make sure you come from a completely powered off state. Hang in there bud.
oneplus 5 FAILED remote: Requested download size is more than max allowed
$ fastboot flash recovery recovery.img
target reported max download size of 536870912 bytes
sending 'recovery' (24404 KB)...
FAILED (remote: Requested download size is more than max allowed
)
finished. total time: 0.001s
my oneplus 5 version oxygenos 4.5.5 latest
abuawaahed said:
oneplus 5 FAILED remote: Requested download size is more than max allowed
$ fastboot flash recovery recovery.img
target reported max download size of 536870912 bytes
sending 'recovery' (24404 KB)...
FAILED (remote: Requested download size is more than max allowed
)
finished. total time: 0.001s
Click to expand...
Click to collapse
Try 'boot recovery.img' then flash it via twrp
Krsambhav16 said:
Try 'boot recovery.img' then flash it via twrp
Click to expand...
Click to collapse
how to try boot recovery
please explain
abuawaahed said:
how to try boot recovery
please explain
Click to expand...
Click to collapse
I'm sorry but you seem to be doing something without researching or understanding what it is. If you don't know what you're doing please don't do it.
abuawaahed said:
oneplus 5 FAILED remote: Requested download size is more than max allowed
$ fastboot flash recovery recovery.img
target reported max download size of 536870912 bytes
sending 'recovery' (24404 KB)...
FAILED (remote: Requested download size is more than max allowed
)
finished. total time: 0.001s
my oneplus 5 version oxygenos 4.5.5 latest
Click to expand...
Click to collapse
i got the same error while using cmd from windows 10, but i was able to successfully install the recovery using git bash.
https://git-scm.com/download/win
pankajsammal said:
i got the same error while using cmd from windows 10, but i was able to successfully install the recovery using git bash.
https://git-scm.com/download/win
Click to expand...
Click to collapse
git bash for what
@abuawaahed
Try this command..
fastboot erase recovery
fastboot erase cache
fastboot flash recovery xxxx.img
fastboot reboot bootloader
Their select recovery and boot to recovery mod..
If this not helps you... Please use toolkit..
Also it's better to ask in Question and answer thread...
abuawaahed said:
git bash for what
Click to expand...
Click to collapse
Used gitbash terminal to use the fastboot command to flash recovery.
mukesh22584 said:
@abuawaahed
Try this command..
fastboot erase recovery
fastboot erase cache
fastboot flash recovery xxxx.img
fastboot reboot bootloader
Their select recovery and boot to recovery mod..
If this not helps you... Please use toolkit..
Also it's better to ask in Question and answer thread...
Click to expand...
Click to collapse
thanks but also not working
fastboot erase recovery
failed (remote :unknown command )
fastboot erase cache
failed (remote :unknown command )
pankajsammal said:
Used gitbash terminal to use the fastboot command to flash recovery.
Click to expand...
Click to collapse
$ fastboot flash recovery twrp-3.1.1-0-oneplus5.img
sending 'recovery' (24404 KB)...
FAILED (remote: Requested download size is more than max allowed
)
finished. total time: 0.001s
also failed
Have you unlocked bootloader.....
If yes change USB port/cable may help you...
Also check that you've enabled usb debugging in developer option....
And which version you are using adb&fastboot setup and drivers? Try different versions Adb setup 1.4.3 example.
mukesh22584 said:
Have you unlocked bootloader.....
If yes change USB port/cable may help you...
Also check that you've enabled usb debugging in developer option....
Click to expand...
Click to collapse
yes unlocked bootloader done
oem enable
usb debugging on
Download the latest Platform Tools package directly from Google and try with these: https://dl.google.com/android/repository/platform-tools-latest-windows.zip
Also indeed make sure that you have "checked" if you have properly unlocked your bootloader (follow the directions here
Gonik said:
Download the latest Platform Tools package directly from Google and try with these: https://dl.google.com/android/repository/platform-tools-latest-windows.zip
Also indeed make sure that you have "checked" if you have properly unlocked your bootloader (follow the directions here
Click to expand...
Click to collapse
not working
i think because of oxygenos 4.5.5
abuawaahed said:
not working
i think because of oxygenos 4.5.5
Click to expand...
Click to collapse
No it's not. It's something that you are doing wrong or your fastboot executable is too old or something. Works fine in OOS 4.5
just update to latest fastboot/adb package and flashing should be fine.
inffy said:
No it's not. It's something that you are doing wrong or your fastboot executable is too old or something. Works fine in OOS 4.5
Click to expand...
Click to collapse
see image unlock bootloader is ok
acmerw said:
just update to latest fastboot/adb package and flashing should be fine.
Click to expand...
Click to collapse
adb-setup-1.4.3 installed
I had the exact same issue, my main rig is on the latest update of windows so the adb minimal drivers couldn't install properly (windows problem)
so tried to do this on my laptop (not on the latest update) and was able to install the drivers.
Now when it came to flashing the recovery - I kept getting the same error as you.
To fix this I tried a different USB port (2.0) and it worked.
Give it a try, should work now.
Hey everyone, I've spent the last 5 hours trying to fix my phone and I'm not getting anywhere.
It gets to the second part of the starting up process, where it makes the sound as well and it just keeps glowing over and over.
I'm able to access the recovery mode, I've already tried clearing the partition cache & I've also done a factory reset.
I've tried flashing recovery.img & boot.img from B170 which I read somewhere, I've done that successfully but it doesn't seem to do anything.
I had this before and I fixed it by flashing system.img but for some reason it keeps giving me an error when I try to do it now: "error: cannot load 'system.img'"
Also flashing the bootloader doesn't seem to work:
"C:\Users\Leron\Desktop>fastboot flash bootloader twrp-2.8.7.1-p8.img
target reported max download size of 471859200 bytes
sending 'bootloader' (25880 KB)...
OKAY [ 0.547s]
writing 'bootloader'...
FAILED (remote: partition does not exist)"
I've read something about buying a card adapter but as I said, I have no money...
I tried to root my phone, bad f***ing move because for some reason it's impossible on the Huawei P8, excuse my bad language but im extremely frustrated i should have never done this. any help is welcome
thanks
usleronus said:
Also flashing the bootloader doesn't seem to work:
"C:\Users\Leron\Desktop>fastboot flash bootloader twrp-2.8.7.1-p8.img
target reported max download size of 471859200 bytes
sending 'bootloader' (25880 KB)...
OKAY [ 0.547s]
writing 'bootloader'...
FAILED (remote: partition does not exist)"
Click to expand...
Click to collapse
Big mistake, no wonder it won't flash.
TWRP is NOT a bootloader but is a recovery, so therefore the correct fastboot command is:-
fastboot flash recovery twrp.img
The P8 is quite easily rooted see here:-
https://forum.xda-developers.com/showpost.php?p=74206273&postcount=305
and here:-
https://forum.xda-developers.com/huawei-p8/how-to/rooting-huawei-p8-marshmallow-emui4-0-1-t3431249
Oh my bad haha.
I fixed it using SRKToolHuawei, which is very useful. I'm very new to this so that's why I screwed up so bad lol
Thanks for the help though. I'll check out the links you sent me and try to root again. Hopefully this time I won't break my phone lmao.
my h872 is brick,even though the download mode and system,now i can only boot into the fastboot,how can i get my phone work?
i have tried fastboot flash command to flash boot or recovery ,etc,it always show:
sending 'bootloader'
ok,
target reported max download size of 536870912 bytes
sending 'laf' (29916 KB)...
OKAY [ 1.029s]
writing 'laf'...
FAILED (remote: unknown command)
finished. total time: 1.050s
might my drives is not proper? i have change the usb point or another device,it always is this...
小阿瑟 said:
my h872 is brick,even though the download mode and system,now i can only boot into the fastboot,how can i get my phone work?
i have tried fastboot flash command to flash boot or recovery ,etc,it always show:
sending 'bootloader'
ok,
target reported max download size of 536870912 bytes
sending 'laf' (29916 KB)...
OKAY [ 1.029s]
writing 'laf'...
FAILED (remote: unknown command)
finished. total time: 1.050s
might my drives is not proper? i have change the usb point or another device,it always is this...
Click to expand...
Click to collapse
How'd you get here? (Your phone bricked)
christopherrrg said:
How'd you get here? (Your phone bricked)
Click to expand...
Click to collapse
i use the twrp flash a wrong recover or maybe wrong root？mostly it is ，
小阿瑟 said:
i use the twrp flash a wrong recover or maybe wrong root？mostly it is ，
Click to expand...
Click to collapse
I just asked because the logs show that your LAF partition isn't flashing and from what I've been reading so far about the LAF partition is that it is a very fragile thing.
Have you tried a factory kdz with LGUP?
christopherrrg said:
I just asked because the logs show that your LAF partition isn't flashing and from what I've been reading so far about the LAF partition is that it is a very fragile thing.
Have you tried a factory kdz with LGUP?
Click to expand...
Click to collapse
what a amazing ! i got another‘s help,now i can boot into the twrp,
but after i install the AospExtended, it just play the aex booting video,how many times i erase all date include system and date,cache,etc.
now ,iwant to konw how to get it into a system
Find stock.kdz to flash using LGUP, reflash TWRP using fast boot commands. Should boot correctly after stock .kdz is applied. Once confirmed your phone works correctly.. Boot into TWRP factory reset, and wipe partition, then attempt to flash your choice of custom ROM.
小阿瑟 said:
what a amazing ! i got another‘s help,now i can boot into the twrp,
but after i install the AospExtended, it just play the aex booting video,how many times i erase all date include system and date,cache,etc.
now ,iwant to konw how to get it into a system
Click to expand...
Click to collapse
Hi mate,
I got into the same problem as u did, i hope you solved your problem by now. Will share to me how you solve it?
Did u flash twrp via fastboot? If u do, can you share to me the command u used?
Thanks alot for your help.
spaceantz said:
Hi mate,
I got into the same problem as u did, i hope you solved your problem by now. Will share to me how you solve it?
Did u flash twrp via fastboot? If u do, can you share to me the command u used?
Thanks alot for your help.
Click to expand...
Click to collapse
Download mode via holding VOL+ and plug in GOOD USB-C cable into Windows 10 laptop/desktop with LG USB drivers, Uppercut, LGUP installed. Then KDZ 10E image to bring back to stock Nougat (losing all root, data, and it'll force encryption): http://firmware-up.com/system/files/basicpr/8d0e1fc8/H87210e_00_0322.kdz
LG G6 H872 stucked in Download mode with 5 dots
My phone LG G6 H872 got stucked in download mode with 5 dots in the process of getting it rooted, pls anyone with information on how to get it out of this should pls help. you can mail me direct on [email protected]