Database Info

PD15IMG.zip not working Bricked Phone

I rooted my phone using the gfree method, i still have the file that saves to your phone when you perform that method. I got perm s-off with hboot 0.85.2007 I was and had been on a gorilla sense rom it was cool was working great, i already had flashed the zip that allowed me to go from clockwork 2.... to 3.... but before i went to thunderbolt rom I used trueblue_drew's updated zip the one he got from option94. I flashed the zip in recovery from clockwork 2....I did a nandroid and of the gorilla sense rom, booted back up and went into recovery again wiped data, partition and dalvik i then flashed thunderbolt from my sd card everything went through smooth. I rebooted completed the steps to set it up and was running smooth then out of nowhere my phone just turned off and went into bootloops, sowing the thunderbolt splash screen, i took off the battery and started my phone again and it wouldnt get past the first splash screen which is the initial my touch 4g splash but i had changed that screen a while back to a black screen from cynogen that reads rooted mytouch 4g with the green droid. I then took the battery out again then went into recovery by holding volume and power at this point i got the "cant mount" messages in clockwork i wiped the data but everytime it was done the "cant mount" messages would appear i tried to nandroid restore everyone i had on my sdcard and nothing worked. I tried flashing a older version of thunderbolt and nothing it just stays stuck on the first splash screen.
When i put the PD15IMG zip on my sd card it reads it then the blue status bar pops up and does its thing, it then asks me if i want to install update i press the volume button up for yes and a few seconds go by and on the first one 1.Bootloader i get the "fail PU" message and just says press power to reboot, i do and it takes me to the first splash screen and sits there.
When i am in Hboot screen and plug my phone in i see that it changes to "hboot usb plug" my system info is
sn-sh11yrmo7858
lcd-so-c2
touch panel-atmelc12_20aay
commit-7eafc656
os ver.-1.17.531.2
imei-359637039172891
cid-11111111
ram-768mb
emmc-samsung 2151mb 4407295 sectors
Like i said i have saved the part7backup file from the gfree method, and i have the clockwork folder saved everything else was wiped from my sd card.
I doubt i have adb set up correctly because i type a command and it says "the system cannot find the patch specified" Im slowly losing hope here i didnt think it was possible to brick a phone especially from what i did but i guess it is

Can you boot and get into the HBoot in your current status?
Did you check the MD5SUM of the download?
Sent from my HTC Glacier using Tapatalk

1 more thing that makes me mad ITS NOT BRICKED!!!!
if its a brick you cant get into Hboot or Recovery
anyways it should work also check if your SDCard is formatted to FAT32 (i think)

sounds like your SD card isn't formatted right or could be corrupted. you're not bricked if you can hboot

I am having the same issue, stating "it isn't bricked" without any explanation isn't very helpful. I have tried reformatting my SD card with no avail even tried a different SD card. as far as I am aware unless you have the eng-hboot there isn't a way to fix this since fastboot does not work

accido said:
I am having the same issue, stating "it isn't bricked" without any explanation isn't very helpful. I have tried reformatting my SD card with no avail even tried a different SD card. as far as I am aware unless you have the eng-hboot there isn't a way to fix this since fastboot does not work
Click to expand...
Click to collapse
If you can get into Fastboot or the Recovery Screen simply means just that it's not bricked. A truly bricked phone you cannot get into the engineering screen nor the recovery image.
On the HBoot screen can you get to recovery and access it? If so what comes up?

I dont understand the problem. it sounds like he got a bad download. If his sd was formated wrong it wouldnt load at all. oance you have clockwork installed it is impossabl to brick. You can pull your battery in the middle of a rom load and be fine
Sent from my HTC Glacier using XDA Premium App

When i hold the volume down and power it takes me into the hboot screen, if i have the PD15IMG.zip on my sdcard it automatically reads it then the blue status bar appears it loads then it asks if i want to start update, I press volume up and it fails. I noticed towards the bottom it says "Partition update fail" and under that "update fail"
I can go into recovery, ClockworkMod 3.0.0.5 recovery but i get a messages stating
E:cant mount ?cache/recovery/command
E:cant mount /cache/recovery/log
E:cant open /cache/recovery/log
E:cant mount /cache/recovery/last_log
E:cant open /cache/recovery/last_log
neidlinger said:
Can you boot and get into the HBoot in your current status?
Did you check the MD5SUM of the download?
Sent from my HTC Glacier using Tapatalk
Click to expand...
Click to collapse

TheHypebeast said:
When i hold the volume down and power it takes me into the hboot screen, if i have the PD15IMG.zip on my sdcard it automatically reads it then the blue status bar appears it loads then it asks if i want to start update, I press volume up and it fails. I noticed towards the bottom it says "Partition update fail" and under that "update fail"
I can go into recovery, ClockworkMod 3.0.0.5 recovery but i get a messages stating
E:cant mount ?cache/recovery/command
E:cant mount /cache/recovery/log
E:cant open /cache/recovery/log
E:cant mount /cache/recovery/last_log
E:cant open /cache/recovery/last_log
Click to expand...
Click to collapse
Read through this thread, their should be some guidance hidden with in the scroll.
Link

I read through it, same issue im having only that he was on .86.0000 and im on .85.2007 and he was able to fix and restore with PD15IMG and i get the partition fail
neidlinger said:
Read through this thread, their should be some guidance hidden with in the scroll.
Link
Click to expand...
Click to collapse

Try flashing it through clockwork recovery. Put the zip image in a folder then boot holding volume down and power. When you can chose options in hboot go to recovery hit trackball. You should no what to do from there
Sent from my HTC Glacier using XDA Premium App

Keep looking for a better answer, but if you find nothing you can try this. You'll need adb and fastboot working.
Find an only nandroid, and put the system.img, boot.img and recovery.img from it in your android sdk tools folder.
Reboot into hboot by pressing volume down and power.
Scroll to fastboot and press power.
then type
Code:
fastboot erase system -w
fastboot erase boot
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash recovery recovery.img
Then fastboot reboot and you should be ok.

lowandbehold helped me.
http://forum.xda-developers.com/showthread.php?t=992283&highlight=rom+manager+question

After the first "fastboot erase system -w" i get "erasing system..." and it just sits there i waited for about ten minutes, how long should that first one take?
option94 said:
Keep looking for a better answer, but if you find nothing you can try this. You'll need adb and fastboot working.
Find an only nandroid, and put the system.img, boot.img and recovery.img from it in your android sdk tools folder.
Reboot into hboot by pressing volume down and power.
Scroll to fastboot and press power.
then type
Code:
fastboot erase system -w
fastboot erase boot
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash recovery recovery.img
Then fastboot reboot and you should be ok.
Click to expand...
Click to collapse

TheHypebeast said:
After the first "fastboot erase system -w" i get "erasing system..." and it just sits there i waited for about ten minutes, how long should that first one take?
Click to expand...
Click to collapse
Should only take a few seconds.
You may have a hardware problem at this point.

Yeah after i waited a good ten minutes i just unplugged my phone and immediately got "FAILED <status read failed <Too many links>> finished. total time: 510.438s
option94 said:
Should only take a few seconds.
You may have a hardware problem at this point.
Click to expand...
Click to collapse
after several tries now it just fails within seconds of running "fastboot erase system -w"

How can I get my computer to recognize my phone? I can't power up and no hboot with holding down power + vol down. Please help !!

TheHypebeast said:
Yeah after i waited a good ten minutes i just unplugged my phone and immediately got "FAILED <status read failed <Too many links>> finished. total time: 510.438s
after several tries now it just fails within seconds of running "fastboot erase system -w"
Click to expand...
Click to collapse
Could the partitions be wrong somehow? I do not know how to fix that, someone else may. I know sometimes the partitions can get out of wack, or at least I have heard of it on other devices, I think I recall it for this one as well.
Also, try downloading the img file again. I believe you must extract it one time to get the proper zip file needed to flash it. I believe the version I downloaded was the pd15img.zip compressed further into a second zip file. when you look in the file you should see several img files, not a folder.
Also, make sure you are using the proper recovery for the ROM, ROM manager app tells you to update your recovery every time you start it if you are not using 3.0.0.5, if you do update, the phone will keep running but if you later flash a new froyo ROM then you will have issues.
At this point, I would try re-downloading the pd15img file and trying fresh to rule out bad downloads, or flashing a known good ROM zip, and ensuring it works with your recovery version.
zion1827 said:
How can I get my computer to recognize my phone? I can't power up and no hboot with holding down power + vol down. Please help !!
Click to expand...
Click to collapse
Sounds like you are full bricked. That means you can not fix it.
It can be fixed, but only with special equipment that can flash information straight to the internal memory chips. Meaning you need access to the internal components along with the software and equipment. So that means HTC engineering dept is about the only ones who can.
It is really hard to brick a device. Only times you can do it are anytime the Hboot file is flashed or the radio is flashed. As those two files are what boots the hardware and readies the software to boot. Thing is, you don't flash those often. Just once for Hboot, and radio firmware updates are very rare.
Dev posts on rooting need to state that flashing the engineering Hboot should be optional AND only for those experienced in flashing and rooting. First time flashers should probably avoid it for a while.
Thing is, flashing the pd15img file can brick a device as it flashes Hboot and radio.

Try this method, let me know if it works for you..
----> Try not to plug Your device on your computer , Put your image in sd card/ then Reboot into the hboot-- and the phone the automatically detects you image in the sdcard and the phone do the rest.. If you see in the upper right corner a bar thats ok its fine.. The phone loads the image and wait be patient.. the it would ask you when its done if you want those settings to be back to stock ROM. Just Click the Up Volume button , and thats it... Try Backing up after you made some changes on the phone.... <------

chipis said:
----> Try not to plug Your device on your computer , Put your image in sd card/ then Reboot into the hboot-- and the phone the automatically detects you image in the sdcard and the phone do the rest.. If you see in the upper right corner a bar thats ok its fine.. The phone loads the image and wait be patient.. the it would ask you when its done if you want those settings to be back to stock ROM. Just Click the Up Volume button , and thats it... Try Backing up after you made some changes on the phone.... <------
Click to expand...
Click to collapse
Its not Brick it just stuck on something undone....

[Q] Xoom stuck on boot screen

The other day my WiFi Xoom stopped getting past the "Motorola Dual Core" screen.
I have removed the SD card.
Android recovery mode gives me the error android with the "!"
It does this plugged in or on battery.
Not rooted.
What else should I try?

neoka said:
The other day my WiFi Xoom stopped getting past the "Motorola Dual Core" screen.
I have removed the SD card.
Android recovery mode gives me the error android with the "!"
It does this plugged in or on battery.
Not rooted.
What else should I try?
Click to expand...
Click to collapse
What were you trying to do before this hapened? Need more info to be able to help.

24348542 26
DavilaDarkness said:
What were you trying to do before this hapened? Need more info to be able to help.
Click to expand...
Click to collapse
Hadn't really done anything. Just normal use. No out of the ordinary installs. Turned it off. Next day I tried turning it on and it won't boot.

Did you ever resolve this ?? I was give one to repair for a child and it too is stuck on the red boot screen. The good thing is the person who sold it to them was a hacker and put TWRP on it of all things. I was floored when I tried to enter recovery and found teamwin.
but the problem is its still stuck on the boot screen, i did flash it 3-4 times with M604 M602 flashes and some other customs but nothing works, it completes flashing and wiping caches but always goes back to stuck on boot screen..
perhaps I have to unclock the bootloader or something for the flash to be succesfull ?

Just wanted to say I fixed it with these commands and firmware if anyone is interested. I tried everything else including flashing with twrp and wiping all caches and it didn't work, getting the stock firmware and doing it like this worked to clear boot screen endless stuck
download fastboot and adb and xoom drivers 6.4 (about 5mb) and the appropriate stock firmware. for me it was ZM604
at the command type
adb reboot bootloader
you may need to unplug and replug cable after it goes in fastboot mode.
fastboot devices
.. should return something "02a439cj0skjdke fastboot" to proceed.
fastboot oem unlock
.. look at your tablet and follow the instructions, for me it was down twice and up once to accept unlock conditions, then it reboots
on reboot press vol down 2 seconds after you see moto logo, it will enter fastboot
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash userdata userdata.img
fastboot erase cache
fastboot erase userdata
fastboot reboot
no need to relock after, you will see android logo and first boot pop up after 2-3 mins

LG GPAD 7 stuck on Fast Boot

Purchased an Lg Gpad 7 Wifi tablet (v400) 2 weeks ago. Came with preinstalled Lollipop android so i couldnt install a recovery rom to flash any other custom roms. Downgraded to Kitkat version following the instructions on Xda forums and succesfully installed Twrp. When i installed Cyanogenmod 12.1 through Twrp i got stuck in fastboot screen.
Any suggestions and / or solutions would be greatly appreciated.

I had a similar problem.. Only mine was stuck at the bootloader. Go in TWRP and repair /data and other partitions. My data partition gave me an error since F2FS is a little flaky and some ROMs corrupted it (claimed they supported it). I would recommend erasing the system, cache and data partition if you can't get into TWRP.

The problem is i cant get out of fastboot whatever i try. It says start on bootloader but the tablet just restarts on an empty screen doing nothing.

Hakalai said:
The problem is i cant get out of fastboot whatever i try. It says start on bootloader but the tablet just restarts on an empty screen doing nothing.
Click to expand...
Click to collapse
if you have an sd card, try removing that, then reboot.
if that doesnt work, try entering fastboot command, fastboot continue

Tried without sdcard and i get the same fastboot screen.
How can i give any commands? The only options i have are Restart Bootloader / Restart / Power off. Tried restarting bootloader but i get nothing in return tablet just stays on with nothing on screen.

Hakalai said:
Tried without sdcard and i get the same fastboot screen.
How can i give any commands? The only options i have are Restart Bootloader / Restart / Power off. Tried restarting bootloader but i get nothing in return tablet just stays on with nothing on screen.
Click to expand...
Click to collapse
you said it was stuck on fastboot, if thats the case, install any needed drivers on your pc, connect device to it, open a terminal in the fastboot dir (after you go get fastboot), then try those commands i gave. you could also try, fastboot reboot dont think i mentioned that before.

bweN diorD said:
you said it was stuck on fastboot, if thats the case, install any needed drivers on your pc, connect device to it, open a terminal in the fastboot dir (after you go get fastboot), then try those commands i gave. you could also try, fastboot reboot dont think i mentioned that before.
Click to expand...
Click to collapse
Did as you said but every command i gave gives me an error message in adb terminal. There are new lines in fastboot menu in tablet now. Bottom two are SECURE BOOT - enabled & LOCK STATE - locked.

Hakalai said:
Did as you said but every command i gave gives me an error message in adb terminal. There are new lines in fastboot menu in tablet now. Bottom two are SECURE BOOT - enabled & LOCK STATE - locked.
Click to expand...
Click to collapse
hmm, ok, im guessing it would have said that normally, when not broken. all the command does is try to release it past where its stuck. it doesnt actually flash, lock, unlock, or change anything.
imo, this seems good, because now we know fastboot is working.
i own lg devices, but not your specific device. i would hate to give you some bad advice and make your tablet broken more, but if it were me in this situation, i would try to flash the factory KK firmware you used to downgrade with odin or however you did it. hopefully, that will clean everything up and let it boot properly.
if for whatever reason you cant do that, we could try extracting the factory file, and just flashing recovery and system, those should be the only things that got changed putting on twrp and cm normally.

Sorry, I have the serious proplem wtih my LG pad V400, I rooted it and using <LG Flash Tool 2014> with <V40010c_00.kdz> to downgrate the firmware but their is error then my LG pad stuck in fastboot menu as with just turn off, restart and restart bootloader. if i seclect one one them the tablet just logged again the fastboot menu
it stuck on the fastboot menu and i cannot do nay think with it. I can restart with factory restore mode but when select yes to restore, it will restart and log in fastboot menu again.
I downloaded adb and fastboot program and put in one folder <Minimal ADB and Fastboot> in C:\Program Files (x86)\Minimal ADB and Fastboot
I dont have recovery image so i download file <cm-13.0-20160421-NIGHTLY-v400-recovery.img> form your link to download TWRP file
move it to folder of fastboot programe and changed its name to <recovery.img>
I turn on the tablet and it waited at fastboot menu
when i run the command <fasboot flash recovery recovery.img> and they said some thing wrong like in picture
please help me

nexus 5 softbrick

Hey,
Hopefully you guys can give me some help with the problem ive been having,
My nexus 5 is stuck in bootloop, i can get into the bootloader and the lockstate is unlocked but no custom recovery is appearing like it used to. I tried flashing using ADB but my phone doesn't show up as a device on my pc.
i have tried to wipe the cache ect and it comes up with "E:failed to mount /cache (invalid argument)
I only really know the basics of this stuff (only ever used the basic stuff to root and flash my phone)

You must use fastboot commands while being into the bootloader, not adb.

mworley1991 said:
Hey,
Hopefully you guys can give me some help with the problem ive been having,
My nexus 5 is stuck in bootloop, i can get into the bootloader and the lockstate is unlocked but no custom recovery is appearing like it used to. I tried flashing using ADB but my phone doesn't show up as a device on my pc.
i have tried to wipe the cache ect and it comes up with "E:failed to mount /cache (invalid argument)
I only really know the basics of this stuff (only ever used the basic stuff to root and flash my phone)
Click to expand...
Click to collapse
Yeah, exactly what primokorn says...
Primokorn said:
You must use fastboot commands while being into the bootloader, not adb.
Click to expand...
Click to collapse
If you use the command "fastboot devices" and your phone with a code appears in the command prompt then there's no problem with your drivers.
Just reflash the factory image, you can use the automatic process if you run "flash all". You can also flash the images manually but if you go for that option make sure you don't forget to flash the cache image, that will fix your problem with mounting the cache partition.

ADB commands are used when the phone is booted into the ROM.
Flash the latest stock ROM from here to see if it solves the issue: https://developers.google.com/android/nexus/images
If the phone still bootloops, flash the userdata.img in fastboot. After flashing the userdata.img file in fastboot, boot directly into stock recovery using the power/volume buttons, perform a factory wipe, and reboot.

Pixel 2 Magisk Bug won't take pin

Pixel 2 XL is soft bricked at the moment and I can't for the life of me think of what I need to do to recover it. I unlocked my bootloader and rooted when I switched to Pie, (I saw people we're already able to use Android pay on a rooted device again and I just couldn't help myself.) I installed twrp accidentally tried to flash TWRP not realizing I needed to temporary boot it and pushing the zip over erasing the recovery I proceeded to just fastboot it and carry on with the normal procedure with my phone. after getting Magisk installed I had my phone all set up until the next time I turned it on and back off again It said I forgot my PIN which I know I didn't I think this was because a glitch with smartlock I just setup so I go to my recovery and wipe the Dalvik cache, cache, Internal storage, and data and low and behold my phone bootloops never making past the final stage before it gets to the lockscreen. I go to Fastboot screen on my phone and my mac can't list my phone as a device in adb and now I am having issues getting back into recovery which I think might be because I am on the stock kernel my Fastboot screen on my phone says Product Name - Taimen, Variant - MSM USF:SAMSUNG(64gig) DDR:SAMSUNG, Bootloader version - TM220j, Baseband version - g899800253-1805232234, my Serial number, Serure boot - Yes, Device status - Unlocked, Vart console - Disabled, HW version - rev_10
I can't get it to stop bootlooping and just turn off.

bump

xda Zed said:
bump
Click to expand...
Click to collapse
Try flashing the stock boot.img with Fastboot. That might get you out of it. Since you did all the wiping I can't say for sure. However, when you were at the point where it wouldn't take your password, that's all that needed to be done. I ran into the same thing. It's a Magisk bug. Magisk gets flashed to the boot partition so flashing the factory boot.img will fix it. TWRP also gets flashed to the boot partition so if you flashed it too, flashing a factory boot image will get rid of that too. ADB won't see the phone while it's in fastboot mode. You need to use "fastboot devices". You can download a factory image if you don't have one and extract the boot.img from it. Put it in the folder your fastboot is in, and then open a command prompt (terminal? I'm not a MAC person) from that folder and type "fastboot flash boot boot.img" (without the quotes). Make sure you use download the factory image that's the same as what you currently have installed on the phone.

robocuff said:
Try flashing the stock boot.img with Fastboot. That might get you out of it. Since you did all the wiping I can't say for sure. However, when you were at the point where it wouldn't take your password, that's all that needed to be done. I ran into the same thing. It's a Magisk bug. Magisk gets flashed to the boot partition so flashing the factory boot.img will fix it. TWRP also gets flashed to the boot partition so if you flashed it too, flashing a factory boot image will get rid of that too. ADB won't see the phone while it's in fastboot mode. You need to use "fastboot devices". You can download a factory image if you don't have one and extract the boot.img from it. Put it in the folder your fastboot is in, and then open a command prompt (terminal? I'm not a MAC person) from that folder and type "fastboot flash boot boot.img" (without the quotes). Make sure you use download the factory image that's the same as what you currently have installed on the phone.
Click to expand...
Click to collapse
I stopped my endless bootloop! Now it says my device is corrupt and cannot be trusted and may not work properly when I tried to start it I couldn't get past the google screen. When I plug it into charge now it doesn't automatically going into a bootloop that can only be stoped by going into the fastboot mode or running out of battery, but the the charging symbol on the screen won't go away. I might have wiped system when I was in TWRP when I couldn't boot back after the first wipe. And I accidentally tried fastbooting Telstra img first. Anyway to get past this white Google screen? Also when I trey to go to recovery now it's the android laying on it's back with a red triangle and it says no command. Should I execute the flash-all script?

Downloaded the stock img files and ran the flash all .sh and now I am back in Android ready to mess something up again I could not thank you enough for your help I am so happy right now

xda Zed said:
Downloaded the stock img files and ran the flash all .sh and now I am back in Android ready to mess something up again I could not thank you enough for your help I am so happy right now
Click to expand...
Click to collapse
Glad to hear you got it working again. As for the recovery screen that say no command, that't the way it works with the stock recovery. When you see that screen, press and hold power and volume up. That will get you into recovery. If you happen to try rooting again and get stuck in a bootloop or some such thing, just flash the stock boot image.. That should get you going again.