Related
Hello,
So I am in big troubles, I wanted to to a fresh install and wipe everything.
Except that I went too fast and wiped really everything... after I tried to install zRam script from Jay.
I still have access to fastboot and recovery and my device is detected as a fastboot device on my computer.
BUT, when i try to use fastboot comands, evyer single of them return "FAILED, unknown error"
I really have no idea on how to fix this. I guess I might need an OTG cable to access kernel+rom files and flash them.
I have access to the root folder through TWRP, if only i could push some files there it would be easy as pie...
Anyone has an idea to help me ?
F Yeah! I found the solution.
All I did was relock and then unlock my boot loader.
Then fastboot commands were working again.
Hello guys,
I had my phone rooted with latest twrp. I flashed stock+ rom with Franco Kernel 25r and the A.R.I.S.E file for better sound. I've done the same set up minus the ARISE file and never had an issue.
well to my luck it kept bootlooping and I wasn't able to get back into my custom recovery. When I got home and got my hands on a pc I did a factory reset by manually flashing stock google img . I even used a couple tools since I ran out of ideas and still no luck.
I'm able to do anything through fastboot but I can't seem to get into my recovery at all.
Any ideas or tips of where I should go next?
Not a Hardbrick
As long as you can get to the bootloader mode, you haven't hard bricked your device. Hardbricking is a point where you cant boot your device and in to bootloader so there is no way to flash your device to a useable state.
Now as you can boot to the bootloader, just fastboot boot twrp.img and if you have a factory image zip, copy it in your device internal storage and flash it. Its that simple, provided you are already using an unencrypted boot.img in your current setup. Or else the next step is to flash an decrypted boot.img(you will loose all your userdata and internal storage data.). There are ways to mount the the encrypted filesystem if you are using a pin or password combo with your fingerprint. But without it its a bit more trickier so just for ease and if you dont have any inseparable data in your device now just flash a decrypted boot.img and then you can easily mount your internal storage to your pc and copy the factory image and the rest you already know..
At this point, I'd recommend a full reset.
Flash all the images in the latest Android M factory image (don't flash DP5 or similar N based ROMs): Recovery, Boot, System, Bootloader, Radio, everything.
Once you get stabilized and back into a working phone, then start rooting and messing around with kernels and what not.
To be completely honest, I've flashed nearly every ROM for the 6p, as well as my other Nexus devices, Galaxy phones, Sony phones, and no-name brands and none of those ultra modified kernels did any noticeable change. I tried the F2FS, NTFS, etc file system changes, tweaks to the governors and IO's, all of that, and found the stock kernel was the best. If a kernel with a different IO Scheduler worked even 10% better than the current implementation, and was just as stable, don't you think the Google/Android Engineers would've pushed that to live?
Currently running Pure Nexus July 23rd Update, everything stock that comes with it, Systemless Root/XPosed, and Viper4Android and have never had a performance or stability issue. I'd recommend you do the same.
leninmon said:
As long as you can get to the bootloader mode, you haven't hard bricked your device. Hardbricking is a point where you cant boot your device and in to bootloader so there is no way to flash your device to a useable state.
Now as you can boot to the bootloader, just fastboot boot twrp.img and if you have a factory image zip, copy it in your device internal storage and flash it. Its that simple, provided you are already using an unencrypted boot.img in your current setup. Or else the next step is to flash an decrypted boot.img(you will loose all your userdata and internal storage data.). There are ways to mount the the encrypted filesystem if you are using a pin or password combo with your fingerprint. But without it its a bit more trickier so just for ease and if you dont have any inseparable data in your device now just flash a decrypted boot.img and then you can easily mount your internal storage to your pc and copy the factory image and the rest you already know..
Click to expand...
Click to collapse
First of all thank you for the response.
I've tried flashing the most current twrp and it seems to go through fine on fast boot but when I actually try to get into recovery from the device it will boot loop and just keep doing that.
How can I get into the phones storage through fastboot?
Where can I get the factory zip?
it feels as if everything seems to go good through fastboot but when I actually try to boot the phone nothing seems to work.
Wiltron said:
At this point, I'd recommend a full reset.
Flash all the images in the latest Android M factory image (don't flash DP5 or similar N based ROMs): Recovery, Boot, System, Bootloader, Radio, everything.
Once you get stabilized and back into a working phone, then start rooting and messing around with kernels and what not.
To be completely honest, I've flashed nearly every ROM for the 6p, as well as my other Nexus devices, Galaxy phones, Sony phones, and no-name brands and none of those ultra modified kernels did any noticeable change. I tried the F2FS, NTFS, etc file system changes, tweaks to the governors and IO's, all of that, and found the stock kernel was the best. If a kernel with a different IO Scheduler worked even 10% better than the current implementation, and was just as stable, don't you think the Google/Android Engineers would've pushed that to live?
Currently running Pure Nexus July 23rd Update, everything stock that comes with it, Systemless Root/XPosed, and Viper4Android and have never had a performance or stability issue. I'd recommend you do the same.
Click to expand...
Click to collapse
Thanks for the reply.
I've done the manual flashing already and flashed everything single item the most current factory image. Everything seemed to have gone through okay but when I rebooted the phone it was back to 0.
I'm actually considering getting rid of the phone now since it is my daily =/
Format each partition before flashing.
fastboot format <partition>
wait until it's done, then
fastboot flash <partition> <image>
Some partitions can't be formatted, which there are ways around, but try this first.
Just get to bootloader mode and try booting the twrp.img
fastboot boot twrp.img
From the twrp ui, go to advanced wipe and format your storage.
To mount the internal storage on your PC, enable mtp from twrp screen.
If U are using a decrypted boot.img, it will easily mount ur internal storage. Or try flashing a decrypted boot.img
fastboot flash boot boot.img
Then try the above again..
leninmon said:
Just get to bootloader mode and try booting the twrp.img
fastboot boot twrp.img
From the twrp ui, go to advanced wipe and format your storage.
To mount the internal storage on your PC, enable mtp from twrp screen.
If U are using a decrypted boot.img, it will easily mount ur internal storage. Or try flashing a decrypted boot.img
fastboot flash boot boot.img
Then try the above again..
Click to expand...
Click to collapse
I flashed the twrp.img and it went through successfully at least on the computer it did but when the phone actually tries to get into recovery (twrp) it will start to boot loop and keep on doing that. I tried both an encrypted and decrypted boot img but it still made no difference.
I'm really going crazy over this
Wiltron said:
Format each partition before flashing.
fastboot format <partition>
wait until it's done, then
fastboot flash <partition> <image>
Some partitions can't be formatted, which there are ways around, but try this first.
Click to expand...
Click to collapse
I just tried this and had no luck =/....the phone wont get past the google boot screen
You need to explain more on what you actually tried here.
Just download the latest factory image and try to flash the latest bootloader using fastboot.
Then boot to the bootloader and try formating the device. Not wiping
Then you have to
fastboot boot twrp.img
I believe you have only tried wiping not formating. I faced similar issue before. But once I flashed a decrypted boot.img, it cleared the user data and then I was able to get to twrp.
Maybe your twrp img is corrupted if this didn't work.
leninmon said:
You need to explain more on what you actually tried here.
Just download the latest factory image and try to flash the latest bootloader using fastboot.
Then boot to the bootloader and try formating the device. Not wiping
Then you have to
fastboot boot twrp.img
I believe you have only tried wiping not formating. I faced similar issue before. But once I flashed a decrypted boot.img, it cleared the user data and then I was able to get to twrp.
Maybe your twrp img is corrupted if this didn't work.
Click to expand...
Click to collapse
i just flashed the latest bootloader from the most recent factory image and i did the command format user data and then tried the fastboot boot twrp and the phone will then try to get into recovery, the google logo comes up lasts a couple seconds and boot loops all over to where is says my phone cant be check for corruption
By now i should have been able to get into recovery and it wont go through
edgarted said:
i just flashed the latest bootloader from the most recent factory image and i did the command format user data and then tried the fastboot boot twrp and the phone will then try to get into recovery, the google logo comes up lasts a couple seconds and boot loops all over to where is says my phone cant be check for corruption
By now i should have been able to get into recovery and it wont go through
Click to expand...
Click to collapse
download a factory image and run the flash all file...... it should reboot your phone after 5 minutes and the issue should be resolved.. a hard brick would be a device that does nothing.... in this case i believe that you just didnt do something right.
Then download the latest factory image and extract it
fastboot flash radio.img
fastboot flash bootloader.img
& do a fastboot update the rest archive file as it is
This will flash the rom via fastboot& U don't have to rely on TWRP or CWM
i42o said:
download a factory image and run the flash all file...... it should reboot your phone after 5 minutes and the issue should be resolved.. a hard brick would be a device that does nothing.... in this case i believe that you just didnt do something right.
Click to expand...
Click to collapse
I was really really hoping this would help. I erase/formated everything before flashing anything. I then ran the flash-all file and it took a couple of minutes and it said finished on the command box and my phone restarted and went into the white google logo and rebooted again with a bootloop. I waited around 15 minutes hoping it would start but it didn't.
It honestly feels as if the phone is not processing the full commands but on the pc it seems to go through successfully
is there a way to force an install of a rom and see if maybe a dirty flash over the stock one will allow it to start up?
leninmon said:
Then download the latest factory image and extract it
fastboot flash radio.img
fastboot flash bootloader.img
& do a fastboot update the rest archive file as it is
This will flash the rom via fastboot& U don't have to rely on TWRP or CWM
Click to expand...
Click to collapse
i know how to flash the radio and bootloader but how do i do a fastboot update?
edgarted said:
i know how to flash the radio and bootloader but how do i do a fastboot update?
Click to expand...
Click to collapse
Just unzip the factory image and there U can see the flash shell script files too. Open them in a text editor & U could see the exact command. In a factory img, they also do the same thing via script files. Flashing the radio & bootloader & updating the rest archive
so this is what I've done
I've manually flashed every file needed for the factory image from google.
I also tried wugfresh tool kit which is great but didn't help me much. I flashed stock recovery and treid to boot into to and nothing. I flashed a customer recovery and nothing.
It always does the same thing
the screen that says my phone can't be checked for corruption and then the google sign comes up stays on for a couple seconds and then it bootloops to the can't be checked for corruption.
I try to get into recovery using fastboot commands and the phone does the same exact thing.
I was even able to lock and relock the bootloader and I was able to successfully flash everything at least that is what it showed on the computer
so ive read almost every thread that had to do with bricking and I feel like an expert now but im starting to think it is done =/
edgarted said:
so this is what I've done
I've manually flashed every file needed for the factory image from google.
I also tried wugfresh tool kit which is great but didn't help me much. I flashed stock recovery and treid to boot into to and nothing. I flashed a customer recovery and nothing.
It always does the same thing
the screen that says my phone can't be checked for corruption and then the google sign comes up stays on for a couple seconds and then it bootloops to the can't be checked for corruption.
I try to get into recovery using fastboot commands and the phone does the same exact thing.
I was even able to lock and relock the bootloader and I was able to successfully flash everything at least that is what it showed on the computer
so ive read almost every thread that had to do with bricking and I feel like an expert now but im starting to think it is done =/
Click to expand...
Click to collapse
Hey there. First off make sure to unlock again your bootloader. Then you may follow post # 10 of @Heisenberg 's flashing guide for our device.
First images to flash would be bootloader and radio. First flash bootloader, then make sure to issue the command adb reboot-bootloader. Then afterwards once the phone has rebooted back to bootloader, flash radio, then again do the adb reboot-bootloader again.
Once the phone is again back to bootloader flash the rest of the images except userdata. For the boot.img and recovery.img, flash the stock ones-don't use the decrypted boot.img and don't flash the twrp.img yet. Once all necessary images have been flashed issue the reboot-booloater command one more time, then on the bootloader screen choose the reboot option. Wait anywhere from 3-10 minutes for the phone to load. Let us know how it goes for you.
blitzkriegger said:
Hey there. First off make sure to unlock again your bootloader. Then you may follow post # 10 of @Heisenberg 's flashing guide for our device.
First images to flash would be bootloader and radio. First flash bootloader, then make sure to issue the command adb reboot-bootloader. Then afterwards once the phone has rebooted back to bootloader, flash radio, then again do the adb reboot-bootloader again.
Once the phone is again back to bootloader flash the rest of the images except userdata. For the boot.img and recovery.img, flash the stock ones-don't use the decrypted boot.img and don't flash the twrp.img yet. Once all necessary images have been flashed issue the reboot-booloater command one more time, then on the bootloader screen choose the reboot option. Wait anywhere from 3-10 minutes for the phone to load. Let us know how it goes for you.
Click to expand...
Click to collapse
Hello and thank you for helping.
I tried this method a couple of minutes ago. I flashed them this same way
fastboot flash bootloader C:\angler\images\bootloader-angler-angler-xx.xx.img
fastboot reboot-bootloader
fastboot flash radio C:\angler\images\radio-angler-angler-xx.xx.img
fastboot reboot-bootloader
fastboot flash boot C:\angler\images\boot.img
fastboot erase cache
fastboot flash cache C:\angler\images\cache.img
fastboot flash recovery C:\angler\images\recovery.img
fastboot flash system C:\angler\images\system.img
fastboot flash vendor C:\angler\images\vendor.img
It does the same exact thing it will try and restart the phone, the message that says it can't be checked for corruption the google logo comes up and it repeats it self non stop.
This is what doesn't make sense to me.
This is the file that I had flashed through twrp when it was working fine
Leviticus 1.3 - http://forum.xda-developers.com/android/software/r-s-e-sound-systems-auditory-research-t3379709
edgarted said:
Hello and thank you for helping.
I tried this method a couple of minutes ago. I flashed them this same way
fastboot flash bootloader C:\angler\images\bootloader-angler-angler-xx.xx.img
fastboot reboot-bootloader
fastboot flash radio C:\angler\images\radio-angler-angler-xx.xx.img
fastboot reboot-bootloader
fastboot flash boot C:\angler\images\boot.img
fastboot erase cache
fastboot flash cache C:\angler\images\cache.img
fastboot flash recovery C:\angler\images\recovery.img
fastboot flash system C:\angler\images\system.img
fastboot flash vendor C:\angler\images\vendor.img
It does the same exact thing it will try and restart the phone, the message that says it can't be checked for corruption the google logo comes up and it repeats it self non stop.
This is what doesn't make sense to me.
This is the file that I had flashed through twrp when it was working fine
Leviticus 1.3 - http://forum.xda-developers.com/android/software/r-s-e-sound-systems-auditory-research-t3379709
Click to expand...
Click to collapse
This is weird. What version of the stock factory images did you flash? I've been using leviticus 1.3 since it came out and when i was still on stock rom. I switched over to cm builds and have been flashing every nightly since the 7/24th build, and in the process repeatesly reflashing the aound mod along, and i've had zero issues with the phone booting afterwards.
hello xda community
I made sure to try everything (or almost) before post here
my ZenFone 5 show a message that it cannot mount the cache partition and I am stuck on the Asus logo (I can access droidboot and recovery but I cannot replace them)
factory reset and cache wipe does not make any change (they return the same "can't mount cache" error.
I am trying to change the current droidboot and recovery to fastboot and TWRP but not matter how much I flash them, it does not take change (yes, I am unlocking the bootloader)
I am also executing a script to get the original partitions table back but when sec_offline_update_image.cmd executes the command "fastboot oem partition /tmp/partition.tbl" I get the error "FAILED(remote: GPT command failed)"
as this came out of thin air, I didnt have the chance to activate developer mode on my phone
I starting to get concerned .... any help?
thnk you very much in advance
@dgadelha any help ?
What are the specs of your Zen 5?
dgadelha said:
What are the specs of your Zen 5?
Click to expand...
Click to collapse
ZenFone 5 - A501CG T00J
Serial # with 0123456789ABCDEF issue
Box info: A501CG2 / A501CG-1F589 / CPU Intel Clover Trail Plus + Dual Core 1.6 Ghz, Purple, 8GB RAM
I already checked basically all links on Google related to the above issues (4 days Googling it already).
I really don't know what to do anymore.
A little more context @dgadelha.
2 months ago, I unlocked my bootloader for the 1st time and installed BlueLight 3.24.40.87... after the installation I locked my bootloader again using the boot, recovery and droidboot images contained in UL-ASUS_T00F-TW-3.24.40.87-user (Asus' official).
BlueLight worked fine with minor bugs for 2 months until past week when it suddenly started to crash a LOT, get slow and overheat (I didn't had time to fix it).
Then suddenly, all Android services and apps on the phone crashed and the phone turned off entering in a bootloop (Asus logo) everytime I reboot.
Since then I am getting the "E:Failed to mount /cache (Invalid argument)" issue when loading the recovery mode.
Since then I am also not being able to flash anything on my phone... no different recovery, no other fastboot and no other image... I get success messages on the flash process but nothing changes after restart (I can still access droidboot and recovery but nothing works there as the "Failed to mount /cache" error pops up for any action I try... recovery mode shows version 3.24.40.87_201).
When I try a system image via adb sideload I get error "Total xfer: 0.00x".
When I try "sec_offline_update_image.cmd" I get an error on the command "fastboot oem partition /tmp/partition.tbl"... the error is "FAILED(remote: GPT command failed)".
I have tried 2 different "partition.tbl" files... one that contains the "spare" partition and another one that contains "misc" instead... both failed.
I am now currently trying xFSTK (I don't even know what this does on my phone) and ASUS Flash Tool... ASUS Flash Tool returns "Flash image failure (FAILED (remote: GPT command failed))".
PS: I forgot to activate developer mode and other related options before the crash.
I hope that my phone is somehow alive... btw, thank you very much in advance!!!
jaabax said:
A little more context @dgadelha.
2 months ago, I unlocked my bootloader for the 1st time and installed BlueLight 3.24.40.87... after the installation I locked my bootloader again using the boot, recovery and droidboot images contained in UL-ASUS_T00F-TW-3.24.40.87-user (Asus' official).
BlueLight worked fine with minor bugs for 2 months until past week when it suddenly started to crash a LOT, get slow and overheat (I didn't had time to fix it).
Then suddenly, all Android services and apps on the phone crashed and the phone turned off entering in a bootloop (Asus logo) everytime I reboot.
Since then I am getting the "E:Failed to mount /cache (Invalid argument)" issue when loading the recovery mode.
Since then I am also not being able to flash anything on my phone... no different recovery, no other fastboot and no other image... I get success messages on the flash process but nothing changes after restart (I can still access droidboot and recovery but nothing works there as the "Failed to mount /cache" error pops up for any action I try... recovery mode shows version 3.24.40.87_201).
When I try a system image via adb sideload I get error "Total xfer: 0.00x".
When I try "sec_offline_update_image.cmd" I get an error on the command "fastboot oem partition /tmp/partition.tbl"... the error is "FAILED(remote: GPT command failed)".
I have tried 2 different "partition.tbl" files... one that contains the "spare" partition and another one that contains "misc" instead... both failed.
I am now currently trying xFSTK (I don't even know what this does on my phone) and ASUS Flash Tool... ASUS Flash Tool returns "Flash image failure (FAILED (remote: GPT command failed))".
PS: I forgot to activate developer mode and other related options before the crash.
I hope that my phone is somehow alive... btw, thank you very much in advance!!!
Click to expand...
Click to collapse
Hi,
Did you have any kernel mods when using BlueLight?
Sorry but I don't know if it had a custom kernel, but a custom one could have lead a storage drive crash.
Also, xFSTK will just attempt to restore your droidboot and dnx/ifwi, not the partition table or w.e.
Maybe you could try extracting the Jelly Bean RAW file with 7-Zip, flash the droidboot signed image (should be like, fastboot flash fastboot file.img, or fastboot flash droidboot file.img), the droidboot signed image name might be something like droidboot.signed_POS.bin (it's an img file too, but with a bin extension).
After flashing that droidboot image, reboot your bootloader and try running the sec_offline_image_update.cmd again.
I wish I had Zenfone Assist active yet, but had to take down it.
Thanks
Hey jaabax, were you able to fix your device ?
Hi @vikrammarkiv.
Sorry for the big delay in response... I am not using this e-mail anymore and I quit fixing my phone.
Unfortunately I could not fix it and I ended up buying another phone.
Could you fix it?
Sorry again and hope you fixed it.
Best regards.
same issue, anyone got any update on fix?
jaabax said:
A little more context @dgadelha.
2 months ago, I unlocked my bootloader for the 1st time and installed BlueLight 3.24.40.87... after the installation I locked my bootloader again using the boot, recovery and droidboot images contained in UL-ASUS_T00F-TW-3.24.40.87-user (Asus' official).
BlueLight worked fine with minor bugs for 2 months until past week when it suddenly started to crash a LOT, get slow and overheat (I didn't had time to fix it).
Then suddenly, all Android services and apps on the phone crashed and the phone turned off entering in a bootloop (Asus logo) everytime I reboot.
Since then I am getting the "E:Failed to mount /cache (Invalid argument)" issue when loading the recovery mode.
Since then I am also not being able to flash anything on my phone... no different recovery, no other fastboot and no other image... I get success messages on the flash process but nothing changes after restart (I can still access droidboot and recovery but nothing works there as the "Failed to mount /cache" error pops up for any action I try... recovery mode shows version 3.24.40.87_201).
When I try a system image via adb sideload I get error "Total xfer: 0.00x".
When I try "sec_offline_update_image.cmd" I get an error on the command "fastboot oem partition /tmp/partition.tbl"... the error is "FAILED(remote: GPT command failed)".
I have tried 2 different "partition.tbl" files... one that contains the "spare" partition and another one that contains "misc" instead... both failed.
I am now currently trying xFSTK (I don't even know what this does on my phone) and ASUS Flash Tool... ASUS Flash Tool returns "Flash image failure (FAILED (remote: GPT command failed))".
PS: I forgot to activate developer mode and other related options before the crash.
I hope that my phone is somehow alive... btw, thank you very much in advance!!!
Click to expand...
Click to collapse
Same problem, only fastboot and GPT failed (Asus zenfone 2 ze551ml). No solution
Exactly the same problem. It appears there are no fixes. How did the xf... thingy go?
Оh man.. I have the same issue, and can't fix it...
First of all, thanks for all the people here provide very useful message.
Acutally I encouter a lot of similar issues across the posts.
Please refer to the posts here:
Unbrick guide Z00l Ze550kl
Need QCN file for ZE550KL/Z00L (2GB Ram) Please.
[Solved]Stuck on logo when booting into custom ROM( Zenfone 2 laser ZE550KL Z00LD)
My model is ZE550KL 2GB/16GB version.
What need to be prepared (please look around from google)
1. CSCImage for recovery
2. QPST 2.7
3. Workable QCN, if you have no backup please make one from the other post. (you will need imei coverter and HxD)
4. Retail image WW_ZE550KL_1.17.40.1234-rel-user-20160304185904-secured-releaseAFT_QC
5. Offical latest image
6. TWRP
7. Minitool Partition Manager (I tried diskpart but not working, so please use this one)
8. Qualcomm Driver
Here are the procedures for reference (I do this for over 10 times and 3 nights)
Please make sure you have working QCN...otherwise you cannot recover the calling feature.
1. Erase aboot
fastboot_8916 erase aboot
use above command to erase the partition
you can unplug the battery and cable and replug them.
or simply use fastboot reboot command.
Result: Device enter into 9006 mode
2. Open Minitool Partition manager
Right click and Delete all partition.
Create one single partition using ext4 format
Once done, remove the battery and cable, replug them.
Result: Device enter into 9008 mode
3. If you installed QPST, you should have a program called QFIL
Please use it and extract the firmware from CSCImage, it should have all the items except emmc MBN, just copy it from the root folder.
If you do this correct (follow other post for more detail)
Replug the device will give you a fastboot screen
Result: Device with workable fastboot
4. Now you have a clean bootloader, but no other thing
Go to CSCImage and click flashall
Once it is done, all the partitions will be ok (sometimes I got /factory not mount, let's fix this later)
Result: you will have a engineering OS and bootloader unlocked, diag mode natively enabled.
5. Open Software Downloader from QPST, and recover the QCN, it will reboot the phone.
If you are not doing this correctly (and many issues here), you will get bootloop.
And you have to start over again.
My suggestion is do not touch any of the bootloader setting. (so do not try to use unofficial bootloader unlock guide)
Even you give a command like "fastboot oem adb_enable" it will cause a bootloop and have to start over.
So my suggestion is not touch any bootloader setting
Result: The phone calling and data should be recovered. You can test by making some call.
6. If you want to keep your bootloader unlocked, the retail image flashall you can search there is a "oem lock"
change to unlock and run it in fastboot mode.
Result: You will have a bootloader unlocked phone, with WW firmware.
You can start from here to do TWRP.
to fix /factory partition. you can install busybox and in adb shell, use mkfs.vfat for the partition.
What is CSCImage, I tried your method but got stuck on missing partitions. (Boot, Recovery, System, etc..)
christian.arvin said:
What is CSCImage, I tried your method but got stuck on missing partitions. (Boot, Recovery, System, etc..)
Click to expand...
Click to collapse
This means you didn't unlock your bootloader.
bootloader needs to be unlocked to flash the partition file, and then the partition will be recovered without data.
My bootloader was unlock.
I digged deeper in your method. And this is what i understand and let it be an information for those who will try.
Back up all partition before you delete all partitions. (Your serial and other sensitive data are stored in some of this partition)
Your method only restore 5 partition table that is inside the main0 gpt mbn.
Note: the whole partition table is listed in the both0 gpt mbn.
In my stupidity I renamed the both0 gpt to main0 gpt thinking that it would work. Instead I run into an unstoppable bootloader bootloop.
In an ending note my ZF2 Laser's only hope is a full eMMC reflash that requires external methods. Or let the official professionals handle it.
Seems I've just bricked my Nexus 7 3G. What I did:
1. After retiring my old Nexus 7 3G from car service (upgraded to Nexus 7 2013) I decided to make the system more mainstream.
2. First I decided to upgrade the TWRP to be able to flash some of the 7.1.2 ROMS. From that moment no version of TWRP I've flashed ever booted. The system booted normally, just no access to recovery. No idea why but this is not very important at the moment.
3. So I decided to go stock for the start. I downloaded factory image LMY47V and started flash_all.bat.
It went like this:
fastboot oem unlock - OK
fastboot erase boot - OK
fastboot erase cache - OK
fastboot erase recovery - OK
fastboot erase system - OK
fastboot erase userdata - OK
fastboot flash bootloader bootloader-tilapia-4.23.img - OK
fastboot reboot-bootloader - OK
ping -n 10 127.0.0.1 >nul
fastboot flash radio radio-tilapia-1231_0.18.0_0409.img - OK
fastboot reboot-bootloader - OK
ping -n 10 127.0.0.1 >nul
fastboot -w update image-nakasig-lmy47v.zip - failed while flashing system (I didn't remember the error)
4. From that moment my tablet behaves like that:
- attempts to get to bootloader (all possible button-press combinations) all end up with Google logo displayed forever
- long press of power button in this state results in restart (not power-off) - again to Google logo
- I can power off by simultaneously pressing all 3 buttons
- obviously, there is no way to connect by adb or fastboot
5. So, it seems like the bootloader is gone/inaccessable. Strange - it was indeed flashed in the unsuccessful re-stock attempt.
Is there any chance to unbrick?
Here is why I gave up googling and am asking here. There seem to be 3 categories of "bricked" Nexus 7, none of which fully fits my case:
1. Unbootable system but still accessible bootloader. Usually possible to access the device via fastboot and flash recovery. Not my case.
2. Device with positively deleted or corrupt bootloader. May be my case. But flash_all.bat seemed to successfuly flash the bootloader image.
3. Nexus randomly stuck in Goole logo, which may be "repaired" by physical force or mainboard replacement. Hardware fault. May be my case, but I know I screwed it up by my flashing attempts.
There are guides for unbricking with nVidia nvflash. But the assumption is the device is visible on computer's USB. Not my case.
Ok, now I see here on xda exactly the same situation reported here https://forum.xda-developers.com/nexus-7/help/n7-tilapia-stuck-logo-fastboot-access-t3990043. Sorry, I overlooked it. Still, in that thread there is no solution.
One difference is that the OP can see his tablet on OFF state as Uknown device in Windows, I might have overlooked this symptom in mine. It would be much more hopeful situation, at least for nvflash solution.
nalott said:
Ok, now I see here on xda exactly the same situation reported here https://forum.xda-developers.com/nexus-7/help/n7-tilapia-stuck-logo-fastboot-access-t3990043. Sorry, I overlooked it. Still, in that thread there is no solution.
One difference is that the OP can see his tablet on OFF state as Uknown device in Windows, I might have overlooked this symptom in mine. It would be much more hopeful situation, at least for nvflash solution.
Click to expand...
Click to collapse
Did you try reinstalling the drivers after removing all other drivers? If the attempt is successful and the tab is recognised, try the Wugfresh Toolkit. The toolkit itself has proper drivers and instructions to install the drivers.
Also try another cable, another USB port (2.0 not 3.0), another PC/Laptop.
Hope you succeed.
Thanks for help. I will try. But I have very little hope: I was using the particular setup (PC, cable, connector, drivers) and it worked fine until the crashed factory image flash. I'm still using it with my Nexus 7 2013 without problem.