Everytime I install TWRP and boot into it. It shows Zero internal storage and when I reboot it outlines there isnt an OS installed.
The system OS isnt wiped (although I thought that the first 50 times). When I enter fastboot again TWRP inst installed.
No idea what going on... tried latest and previous TWRP files.
thanks in advance
Heres the Log
-------------
Z:\NewNexus7Root\platform-tools>adb reboot bootloader
Z:\NewNexus7Root\platform-tools>fastboot flash recovery twrp-2.8.7.0-flo.img
sending 'recovery' (8956 KB)...
OKAY [ 0.291s]
writing 'recovery'...
OKAY [ 0.271s]
finished. total time: 0.564s
Z:\NewNexus7Root\platform-tools>adb reboot recovery
error: device not found
error: device not found
Got it working after I found the MultiRom fix on this site.
Seems I had one of those unique "locked down" Nexus's 2013; mines from Amazon.
I did the b10 update yesterday, fully stock.
After the update it keeps getting stuck at the boot screen.
Luckily recovery still works.
I downloaded an official rom package, put the update.zip on 3 different sdcards.
all 3 cards get the same response from recovery. 'Sorry, you can't sdcard upgrade'.... great... fine sideload it is.
so tried to sideload, got this message:
C:\adb>adb sideload update.zip
loading: 'update.zip'
* cannot read 'update.zip' *
Then tried to fastboot twrp
got this message:
C:\adb>fastboot flash recovery twrp-3.0.4-0-ailsa_ii.img
target reported max download size of 536870912 bytes
sending 'recovery' (14472 KB)...
OKAY [ 0.402s]
writing 'recovery'...
FAILED (remote: unknown command)
finished. total time: 0.424s
I have had several galaxy phones in the past, but never encountered this troubles.
Does anybody have a idea what's going on? im kinda lost here.
FREEKR said:
I did the b10 update yesterday, fully stock.
After the update it keeps getting stuck at the boot screen.
Luckily recovery still works.
I downloaded an official rom package, put the update.zip on 3 different sdcards.
all 3 cards get the same response from recovery. 'Sorry, you can't sdcard upgrade'.... great... fine sideload it is.
so tried to sideload, got this message:
C:\adb>adb sideload update.zip
loading: 'update.zip'
* cannot read 'update.zip' *
Then tried to fastboot twrp
got this message:
C:\adb>fastboot flash recovery twrp-3.0.4-0-ailsa_ii.img
target reported max download size of 536870912 bytes
sending 'recovery' (14472 KB)...
OKAY [ 0.402s]
writing 'recovery'...
FAILED (remote: unknown command)
finished. total time: 0.424s
I have had several galaxy phones in the past, but never encountered this troubles.
Does anybody have a idea what's going on? im kinda lost here.
Click to expand...
Click to collapse
Your battery percentage is low. Make sure you charge it until at least 80%
EDIT: Enable OEM unlock in developper settings
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
Hi, I just changed the lcd screen on an old p8lite my girlfriend wasn't using for a year or so. Fact is she can't remember the pin.
Pressing power+vol down I can enter fastboot and rescue mode, but phone was never unlocked so i don't know what commands I can really execute from here, if I press vol up and get into rescue mode I am given the option to download a new recovery, but when downloading it says 'getting package info failed'. In rescue mode I don't have other choices besides rebooting and shutdown.
What can I do to unlock the phone?Can somebody help me?????
UPDATE: on one of many reboots instead of showing me just the options to reboot, shutdown and download recovery, Emui recovery showed the possibility of making a wipe, so i went on wiping, downgrading, rooting, unlocking the bootloader, but i couldn't install twrp - every time I try these are the results:
C:\adb>fastboot flash recovery_ramdisk TWRP-3.2.3-0-Hi6250-Askuccio-v1.0.img
target reported max download size of 471859200 bytes
sending 'recovery_ramdisk' (10816 KB)...
OKAY [ 0.277s]
writing 'recovery_ramdisk'...
FAILED (remote: partition does not exist)
finished. total time: 0.303s
C:\adb>fastboot flash recovery TWRP-3.2.3-0-Hi6250-Askuccio-v1.0.img
target reported max download size of 471859200 bytes
sending 'recovery' (10816 KB)...
OKAY [ 0.287s]
writing 'recovery'...
OKAY [ 0.183s]
finished. total time: 0.484s
But TWRP doesn't get installed, anyway....
I would also like to try to run a datarecovery software to recover photos and stuff my girlfriend left in, but without having the p8 lite mass storage in explorer the results I get with android data recovery softwares are pretty useless, is there a way to make show the storage in explorer? If anyone would be willing to help me with some hints, I'd be very grateful. Thanks
Hello. I'm new in playing with smartphones around and flashing roms and all the other things.
But I wanted to learn, and began with something like the Android 12 Beta.
I found this article: Install Android 12 GSI
I used the ARM64 because after the command to check the architecture I got: arm64-v8a outputted.
I tried it with gApps and without. After every command I reboot and after that I'm in a bootloop. I get the Huawei Logo and after that the "warning" that I have an unlocked bootloader and it can't be trusted. After a bit, I get the Huawei Logo again and so on. After 3 times I guess eRecovery comes.
C:\Users\weber\Desktop\dc-unlocker2client_1.00.1435>adb reboot bootloader
C:\Users\weber\Desktop\dc-unlocker2client_1.00.1435>fastboot flash vbmeta vbmeta.img
target reported max download size of 471859200 bytes
sending 'vbmeta' (4 KB)...
OKAY [ 0.017s]
writing 'vbmeta'...
OKAY [ 0.036s]
finished. total time: 0.073s
C:\Users\weber\Desktop\dc-unlocker2client_1.00.1435>fastboot erase system
erasing 'system'...
OKAY [ 37.155s]
finished. total time: 37.169s
C:\Users\weber\Desktop\dc-unlocker2client_1.00.1435>fastboot flash system system.img
target reported max download size of 471859200 bytes
Invalid sparse file format at header magi
sending sparse 'system' 1/4 (460796 KB)...
OKAY [ 13.484s]
writing 'system' 1/4...
OKAY [ 4.426s]
sending sparse 'system' 2/4 (456612 KB)...
OKAY [ 14.049s]
writing 'system' 2/4...
OKAY [ 3.476s]
sending sparse 'system' 3/4 (460796 KB)...
OKAY [ 13.959s]
writing 'system' 3/4...
OKAY [ 3.582s]
sending sparse 'system' 4/4 (173628 KB)...
OKAY [ 5.140s]
writing 'system' 4/4...
OKAY [ 1.580s]
finished. total time: 59.786s
C:\Users\weber\Desktop\dc-unlocker2client_1.00.1435>fastboot -w
wiping userdata...
Erase successful, but not automatically formatting.
Can't determine partition type.
FAILED (remote: Command not allowed)
erasing 'userdata'...
(bootloader) success to erase cryypt info in oeminfo
OKAY [ 1.711s]
finished. total time: 1.719s
C:\Users\weber\Desktop\dc-unlocker2client_1.00.1435>fastboot reboot
rebooting...
finished. total time: 0.043s
Click to expand...
Click to collapse
Those are the outputs ov ervery command. Did I do something wrong? Or is the Huawei P10 Lite not able to flash the Androdi 12 Beta?
I appreciate any help!
Traijan said:
Hello. I'm new in playing with smartphones around and flashing roms and all the other things.
But I wanted to learn, and began with something like the Android 12 Beta.
I found this article: Install Android 12 GSI
I used the ARM64 because after the command to check the architecture I got: arm64-v8a outputted.
I tried it with gApps and without. After every command I reboot and after that I'm in a bootloop. I get the Huawei Logo and after that the "warning" that I have an unlocked bootloader and it can't be trusted. After a bit, I get the Huawei Logo again and so on. After 3 times I guess eRecovery comes.
Those are the outputs ov ervery command. Did I do something wrong? Or is the Huawei P10 Lite not able to flash the Androdi 12 Beta?
I appreciate any help!
Click to expand...
Click to collapse
Hi...
first....the untrustet warning is normal even the bootloader is unlocked. Thats just ah info!
sec...did you come from Stock Rom or any other custom Rom and if custom then was this rom rootet. if yes (root) then you need to unroot first or you get bootloop. for unroot you must restore the stock ramdisk image thats the boot image. If you have no backup (btw greatest fail you could do by developing any Device) the recover stock Rom with erecovery and after initia boot activate dev options and usb debugging again. After that start from a clean stock Rom.
next...did you encrypt your internal storage with the fstab.hi6250b.zip and reboot to TWRP and then format Data then wipe Cache, Dalvik, Data, internal Storage and System then (Method a) reboot again to TWRP and flash the Rom. Yor also can also (Method b) not reboot to Bootloader not to TWRP and flash it with fastboot command.
But it is possible that the GSI Rom Android 12 actually not compatible with p10 lite. Its beta State and gapps for A12 would be beta to i think. So my thinking is just to wait for the official release what no garat for compatibility with p10 lite is but then the Rom isnt beta anymore.
solong
speedson
Supplement...the Part with the vbmeta is not necessary as far as i know.
solong
speedson
speedson said:
Hi...
first....the untrustet warning is normal even the bootloader is unlocked. Thats just ah info!
sec...did you come from Stock Rom or any other custom Rom and if custom then was this rom rootet. if yes (root) then you need to unroot first or you get bootloop. for unroot you must restore the stock ramdisk image thats the boot image. If you have no backup (btw greatest fail you could do by developing any Device) the recover stock Rom with erecovery and after initia boot activate dev options and usb debugging again. After that start from a clean stock Rom.
next...did you encrypt your internal storage with the fstab.hi6250b.zip and reboot to TWRP and then format Data then wipe Cache, Dalvik, Data, internal Storage and System then (Method a) reboot again to TWRP and flash the Rom. Yor also can also (Method b) not reboot to Bootloader not to TWRP and flash it with fastboot command.
But it is possible that the GSI Rom Android 12 actually not compatible with p10 lite. Its beta State and gapps for A12 would be beta to i think. So my thinking is just to wait for the official release what no garat for compatibility with p10 lite is but then the Rom isnt beta anymore.
solong
speedson
Click to expand...
Click to collapse
Hey, I used the default rom installed on my huawei p10 lite.
I did a complete clean install yet.
Before that I used twrp to install it (because I thought it worked with .img) and after that I startet from a clean install of the default rom again and did the linked tutorial.
I'm not root on this device, I just have a unlocked bootloader.
I also didn't encrypted my internal storage. Do I have to do it?
What you mean with not reboot to bootloader? I did the commands in the link on fastboot (holding vol - and connect to pc)
Do you have an idea what I can do? I really would like to test android 12.
A good place to start when figuring out why no rom install's in my system-as-root...
Back to stock it is...