Hi,
I seem to be bricked more than usual. Don't ask me how, I was doing something, rebooted and now I can't get into early usb mode or android recovery. I have no clue what half the other boot options are.
I can use rsd lite to flash sbfs, no problem. Phone is stuck at initial m, no animation. I suspect it is something dumb like the internal memory having an error, something is causing the linux bit to loop. Not reboot, not crash, just hang there.
i can use fastboot, but since it uses names for partitions, I don't know how to flash exact partitions or know what they all are, I have system, webtop, boot, recovery, cdrom, other things like pds are not allowed.
I have a dev usb cable made up, can do everything without a battery, which is cool, have an extra battery and external battery charger. Obviously, I have all the partitions available as backups.
Somehow, I need to get the partitions restored, and internal memory formatted perhaps.
Any ideas? Short of trying to send it back?
Thanks.
for my little experience a full wiped pds let you run the os...and you know better than me which are the others partitions not overwritten by a flash with full sbf
I had a backup of my pds, but no way to flash it or erase it.
Thanks!
in milestone i was having your problem when changing builds (froyo,ginger, eclair) via update.zip without the correct boot.img
but if you already flashed the sbf...
have you tried flashing boot and recovery partition, and then entering it? maybe you regain adb access
I think I am getting blocked before I even get to recovery, early usb, android recovery, etc.
I have fastboot access and nvflash, so in other words I have fastboot.
I can flash boot, recovery, system, webtop, cdt, cdrom, preinstall, but not pds, and I can't erase boot etc.
Thanks.
...i searched for nvram in android:
maybe it's useful (from droid incredible dev area)
dknlght said:
I finally successfully recovered my BootLooped Incredible after i incorrectly updated the NV item of my phone. My situation was a little different than most bootloop error because no matter which stock rom or recovery image I flash nothing would stop it from rebooting because the NV items weren't overwritten during the flash. Then I came across a solution for the EVO by cutthroatamft on how he recovered his EVO from the same Mistake but unfortunately all his files were geared toward the EVO. After much searching I accidentally came across a single comment that posted a link for the ENG-HBOOT for the incredible. Now i manage to replace all the EVO specific files with the Dinc equivalent. Below is the link to the files and instructions compile by cutthroatamft but I updated it for the Dinc. Hopefully this helps someone else that has this problem. can't post a live link but I think you can figure it out
www megaupload . com /?d=RCZBCDDA
Click to expand...
Click to collapse
hope it helps somehow
Well, the file is about HTC phones, so it doesn't really apply, no hboot to swap to get a fastboot.
"fastboot erase nv"
"fastboot erase userdata"
"fastboot erase system"
"fastboot erase recovery"
"fastboot erase microp"
"fastboot erase boot"
"fastboot erase radio"
"fastboot flash nv nv.img"
I could try to do a flash nv nv.img perhaps, probably not a good idea since I have no idea what is in it, and likely locked against flashing. Interesting to see more fastboot partition names, although erase system or boot won't work.
Cheers!
NFHimself said:
Well, the file is about HTC phones, so it doesn't really apply, no hboot to swap to get a fastboot.
"fastboot erase nv"
"fastboot erase userdata"
"fastboot erase system"
"fastboot erase recovery"
"fastboot erase microp"
"fastboot erase boot"
"fastboot erase radio"
"fastboot flash nv nv.img"
I could try to do a flash nv nv.img perhaps, probably not a good idea since I have no idea what is in it, and likely locked against flashing. Interesting to see more fastboot partition names, although erase system or boot won't work.
Cheers!
Click to expand...
Click to collapse
i did not say that file was for you.
but if you can flash boot recovery system and your system won't boot it's something else in the bootstrap process (excluding hardware failures, you could not access fastboot then).
as i read you can flash (already flashed?) almost every partition except pds (useless for your needs) and nv.
i reported a case of other guys experiencing your same problem, with i guess the same cause.
i give you an idea, unfortunately i'm not a dev to give you solution
cheers
As I know, unlocking bootloader will erase the DRM data in my phone.
If fastboot.exe can write something to that hidden partition in fastboot mode, why can't we back it up?
hi folks,
I wanted to update on lollipop but no success.
I don't know why but my Z2 (locked bootloader, rooted, 4.4.4. custom rom, philzdualrecovery) don't work as it should.
In flashtool I stuck in "reading device information" by flashing a stock rom.
In recovery (TWRP or PhilzTouch) I cannot format all my partitions. System, cache and boot did work but data not!
(I formatted system, cache and boot for preparing for a new rom.)
I see "/data" as an empty partition with 0 MB size. What happened? Entering recovery only works with an insered SD Card. Fastboot mode works also.
I tried to erase partitions but fastboot-cmd said "failed: remote command not allowed" (or something like that).
Have you any idea? Do you need more information?
Thanks alot!
So, I was trying to format my SD Card, partition table & all, since Marshmallow's adoptable storage feature messes up the partition table. Since my SD Card doesn't work in my pc, I have to use dd in recovery. This wasn't a big deal since I've already done this successfully 2 or 3 times already. So, since I knew the path of the SD Card already, I typed "dd if=/dev/zero of=/dev/mmcblk1 bs=1M count=1" . Except, I made a slight mistake & typed /dev/mmcblk0 instead of /dev/mmcblk1.
Thankfully, fastboot still worked, so all I had to do is fastboot flash partition gpt.bin to repartition my phone. Or so I thought. When I type this, it says "(bootloader) Preflash validation failed". I already know from prior experience that this error happens when you try to flash an old version of gpt or bootloader. However, these files are from the latest stock rom version, which is "SURNIA_BOOST_5.1_LPI23.29-18-S.2_cid9_subsidy-DEFAULT_CFC.xml".
So, is there anyway I can fix this, or am i hard bricked? Do I just need a newer firmware?
EDIT: Just found a newer firmware, however it is not for my country or carrier. Nevertheless, I am still downloading it & I'm going to see if it can unbrick it or not.
Update
OK, so flashing the gpt.bin from the newer firmware worked, & I was able to flash TWRP, but now I have a different problem. The recovery can't mount system, cache, or data. Attempting to wipe these does nothing. When I try to format these in fastboot, I get the message "Formatting is not supported for filesystem with type 'raw'.".
What do I do now?
Flash only system pertision then data then boot. Via fastboot with original firmware of ur model no
I fixed it! Turns out constantly formatting & rebooting with TWRP actually worked.
Hi guys I just recently encountered this issue where fastboot cannot flash anything (boot.img, system.img) on my device if its data and cache partitions are on F2FS. It shows the device serial number if I key in "fastboot devices", however.
Are there any modifications that I need to make to make fastboot work with a F2FS-enabled device?
Side Question: Does flashing a ROM via TWRP revert the F2FS partition back to EXT4? Or would it cause some problems with the ROM/flashing process?
No, only when you format that partition, then it go back to EXT4. Some roms work in EXT4 only, some work both