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.
Related
Hello. I am on 6.0.1 MMB29M trying to flash TWRP. I get this error message while doing this.
c:\angler>fastboot flash bootloader twrp-2.8.7.2-angler.img
target reported max download size of 494927872 bytes
sending 'bootloader' (16880 KB)...
OKAY [ 0.392s]
writing 'bootloader'...
FAILED (remote: partition table doesn't exist)
finished. total time: 0.414s
Bootloader is unlocked as well as debugging. I have followed a lot of different guides but can't get passed this error. I had TWRP working on MDB08K but the camera was not working for some strange reason. If anyone can help me get TWRP on MMB29M, that would be great.
bauwoo said:
Hello. I am on 6.0.1 MMB29M trying to flash TWRP. I get this error message while doing this.
c:\angler>fastboot flash bootloader twrp-2.8.7.2-angler.img
target reported max download size of 494927872 bytes
sending 'bootloader' (16880 KB)...
OKAY [ 0.392s]
writing 'bootloader'...
FAILED (remote: partition table doesn't exist)
finished. total time: 0.414s
Bootloader is unlocked as well as debugging. I have followed a lot of different guides but can't get passed this error. I had TWRP working on MDB08K but the camera was not working for some strange reason. If anyone can help me get TWRP on MMB29M, that would be great.
Click to expand...
Click to collapse
Your command is wrong, The command to use is: fastboot flash recovery twrp.the name of your file.img
Just like @jawmail said, you're flashing twrp on the bootloader """slot""
-fastboot flash recovery ***TWPR***.img
-fastboot reboot-bootloader
When your phone reboots, using your volume keys, search for "recovery" and using the power button, confirm it.
PROFIT
bauwoo said:
Hello. I am on 6.0.1 MMB29M trying to flash TWRP. I get this error message while doing this.
c:\angler>fastboot flash bootloader twrp-2.8.7.2-angler.img
target reported max download size of 494927872 bytes
sending 'bootloader' (16880 KB)...
OKAY [ 0.392s]
writing 'bootloader'...
FAILED (remote: partition table doesn't exist)
finished. total time: 0.414s
Bootloader is unlocked as well as debugging. I have followed a lot of different guides but can't get passed this error. I had TWRP working on MDB08K but the camera was not working for some strange reason. If anyone can help me get TWRP on MMB29M, that would be great.
Click to expand...
Click to collapse
Whoa! Does your phone still boot to the bootloader? If so, you're extremely lucky. Flashing a non-bootloader image to the bootloader is pretty much the only way to hard brick a Nexus. You need to take much greater care when doing these things.
Haha. Thanks. Yeah I am really lucky. My phone is working now thanks. Just coming from the S6 Edge. Very different rooting method from that, so yeah I should be way more careful. Thanks for the awesome guide, btw Heisenberg. Running PureNexus with ExperimentalX kernel. Such an amazing combo.
Heisenberg said:
Whoa! Does your phone still boot to the bootloader? If so, you're extremely lucky. Flashing a non-bootloader image to the bootloader is pretty much the only way to hard brick a Nexus. You need to take much greater care when doing these things.
Click to expand...
Click to collapse
Update: nvm, figured it out myself.
I have a similar problem. I flashed the TWRP recovery and it booted into it. Made a nandroid and an EFS backup. Copied the backups to my PC. Wanted to flash the systemless root zip. Issued adb reboot recovery and I get the little Android on his back and saying "no command". Tried flashing recovery again, got this:
sending 'recovery' (16880 KB)...
OKAY [ 0.515s]
writing 'recovery'...
OKAY [ 0.238s]
finished. total time: 0.756s.
And still, I can't boot into twrp by either method. Getting the "no command".
What gives?
Puck24 said:
Update: nvm, figured it out myself.
I have a similar problem. I flashed the TWRP recovery and it booted into it. Made a nandroid and an EFS backup. Copied the backups to my PC. Wanted to flash the systemless root zip. Issued adb reboot recovery and I get the little Android on his back and saying "no command". Tried flashing recovery again, got this:
sending 'recovery' (16880 KB)...
OKAY [ 0.515s]
writing 'recovery'...
OKAY [ 0.238s]
finished. total time: 0.756s.
And still, I can't boot into twrp by either method. Getting the "no command".
What gives?
Click to expand...
Click to collapse
Please explain how you fixed your problem so the info is there for folks in future.
Sent from my Nexus 6P
Heisenberg said:
Please explain how you fixed your problem so the info is there for folks in future.
Sent from my Nexus 6P
Click to expand...
Click to collapse
guess it's a corrupted file?
Actually, I just tried flashing it one more time, rebooted to the bootloader with the phone, not with the command. Then I also used the phone to enter into recovery, not by issuing commands. And it works
Sent from my Nexus 6P using XDA Free mobile app
Hello
So H2OS boots up just fine. Fastboot mode works. When I boot into recovery mode the oneplus logo shows up, but it is as nothing happens afterwards. I left the device there for more than an hour and still nothing. Flashing from the OS twrp 2.8.7.0 or 3.0.0-2 has no change on this. Flashing from fastboot the same. When I try to boot from fastboot,I get the following error:
[email protected] ~/Downloads $ fastboot boot twrp-3.0.0-2-oneplus2.img
downloading 'boot.img'...
OKAY [ 0.807s]
booting...
FAILED (remote: dtb not found)
finished. total time: 0.873s
[email protected] ~/Downloads $ fastboot flash recovery recovery.img
target reported max download size of 536870912 bytes
sending 'recovery' (31700 KB)...
OKAY [ 0.815s]
writing 'recovery'...
OKAY [ 0.534s]
finished. total time: 1.349s
Any ideas?
Had the same problem. I just flashed MM firmware and then TWRP 3.0.1. It did not worked when i was flashing 3.0.0. Download official TWRP from their site, version 3.0.1.
I know it seems strange but it did help for me. Was not expecting that to fix the problem tho ..
http://forum.xda-developers.com/oneplus-2/general/firstaid-zip-revert-h2os-mm-beta-to-lp-t3306967
redh4t said:
Had the same problem. I just flashed MM firmware and then TWRP 3.0.1. It did not worked when i was flashing 3.0.0. Download official TWRP from their site, version 3.0.1.
I know it seems strange but it did help for me. Was not expecting that to fix the problem tho ..
Click to expand...
Click to collapse
From what I see there is no, 3.0.1 here,
twrp-3.0.0-2-oneplus2.img 31M
twrp-3.0.0-1-oneplus2.img 30.9M
twrp-3.0.0-0-oneplus2.img 29.2M
twrp-2.8.7.0-oneplus2.img 27.5M
https://dl.twrp.me/oneplus2/
So i have been trying to flash TWRP 3.0.0.1 onto my phone using the guide, http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928, and at first when i got to step 2 and tried to flash TWRP file, it would say "error: cannot load twrp.img"
and that went away and i was finally able to flash it after installing universal adb driver.
When i flash it i get this:
C:\SDK\android-sdk-windows\platform-tools>fastboot flash recovery twrp.img
target reported max download size of 494927872 bytes
sending 'recovery' (16904 KB)...
OKAY [ 0.415s]
writing 'recovery'...
OKAY [ 0.244s]
finished. total time: 0.665s
and when i try to reboot to the bootloader, it shows up the standard stock recovery. What am i doing wrong?
please help
Also, when i do adb devices, it wont show my device. But i saw on the forum that adb doesnt even matter.
NEVERMIND i got it to work. But now im having trouble flashing the lastest march update. It says error 7 and something about my SD card.
LifeOfNexus said:
So i have been trying to flash TWRP 3.0.0.1 onto my phone using the guide, http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928, and at first when i got to step 2 and tried to flash TWRP file, it would say "error: cannot load twrp.img"
and that went away and i was finally able to flash it after installing universal adb driver.
When i flash it i get this:
C:\SDK\android-sdk-windows\platform-tools>fastboot flash recovery twrp.img
target reported max download size of 494927872 bytes
sending 'recovery' (16904 KB)...
OKAY [ 0.415s]
writing 'recovery'...
OKAY [ 0.244s]
finished. total time: 0.665s
and when i try to reboot to the bootloader, it shows up the standard stock recovery. What am i doing wrong?
please help
Also, when i do adb devices, it wont show my device. But i saw on the forum that adb doesnt even matter.
NEVERMIND i got it to work. But now im having trouble flashing the lastest march update. It says error 7 and something about my SD card.
Click to expand...
Click to collapse
I flashed twrp 5 times.. before it "stick" and shows up twrp recovery.
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...