Database Develop

nexus one "radio v2 - fail-pu" help needed

Hi all,
I need help to install any rom or something else with my nexus one.
I have attached picture.
When I starting the device I get 7 vibrations but I can see the fastboot screen.
I have tried to put passdiag file on the sd card and this is what I can get.
i have AT&T device with AMOLED
and also S-ON (so i cannt run adb).
Thanks Yaron.

You meant PASSIMG and not PASSDIAG. But it doesn't matter much. Unfortunately, your Nexus One is dead.
"Fail-PU" means "Failed Partition Update", which means - your NAND chip died and can't be recovered. Since it died on Radio partition, you can't do anything with it.
Time to move to a better phone, I guess.

Exact problem.. very precise
Jack_R1 said:
You meant PASSIMG and not PASSDIAG. But it doesn't matter much. Unfortunately, your Nexus One is dead.
"Fail-PU" means "Failed Partition Update", which means - your NAND chip died and can't be recovered. Since it died on Radio partition, you can't do anything with it.
Time to move to a better phone, I guess.
Click to expand...
Click to collapse
yrone said:
Hi all,
I need help to install any rom or something else with my nexus one.
I have attached picture.
When I starting the device I get 7 vibrations but I can see the fastboot screen.
I have tried to put passdiag file on the sd card and this is what I can get.
i have AT&T device with AMOLED
and also S-ON (so i cannt run adb).
Thanks Yaron.
Click to expand...
Click to collapse
same problem all hboot radio versions are same as well... very exact .. did you solve it yet.. if so can you tell me how to solve it.. i can actually get into fastboot.. thats all i can say now.. can you help me solve ths problm..
and my nexus one stuck with boot screen..

And I thought my reply explains the situation very well...
Read it again, several times, until you understand the meaning of "dead phone".

Jack_R1 said:
And I thought my reply explains the situation very well...
Read it again, several times, until you understand the meaning of "dead phone".
Click to expand...
Click to collapse
yea i understood. still i can just change that logic board by buying some old used working parts from ebay.
i think that will work.. :laugh: :cyclops:

Yes, you can, of course. But this is the main board with the CPU, it might cost almost as much as a complete N1.

[Q] Lumia 630 - is it dead ?

Hi, yesterday I was trying to downgrade OS version in Lumia 630. I used Nokia Software Recovery Tool. But unfortunately I got an error and red screen with Nokia logo. I was panic and removed battery. Now my phone is a brick. I tryied this tutorial but it failed. What should I do at this moment? Can I fix it at home or should go to service ? Sorry for my english. Regards, MaPa.

mlotek01 said:
Hi, yesterday I was trying to downgrade OS version in Lumia 630. I used Nokia Software Recovery Tool. But unfortunately I got an error and red screen with Nokia logo. I was panic and removed battery. Now my phone is a brick. I tryied this tutorial but it failed. What should I do at this moment? Can I fix it at home or should go to service ? Sorry for my english. Regards, MaPa.
Click to expand...
Click to collapse
Hi,
Lol, the red screen is quite normal...
You say you got an error message, what as error?

anaheiim said:
Hi,
Lol, the red screen is quite normal...
You say you got an error message, what as error?
Click to expand...
Click to collapse
I do not remember, but it was error of Nokia Software Recovery Tool.

mlotek01 said:
I do not remember, but it was error of Nokia Software Recovery Tool.
Click to expand...
Click to collapse
Should never do what you did, that is to say, never disconnect the phone during a flashing process.
If you are unable to retrieve with different software available to you, then it is hard bricked.
We must change the physical ROM, that is to say change the motherboard, or do so in a specialized repair service.

anaheiim said:
Should never do what you did, that is to say, never disconnect the phone during a flashing process.
If you are unable to retrieve with different software available to you, then it is hard bricked.
We must change the physical ROM, that is to say change the motherboard, or do so in a specialized repair service.
Click to expand...
Click to collapse
I think it is a last question. Now, when I connect Lumia via usb cable to my pc I get message "unknown device". Will specialized repair service know what I do with Lumia ? Will be warranty considered ?

mlotek01 said:
I think it is a last question. Now, when I connect Lumia via usb cable to my pc I get message "unknown device". Will specialized repair service know what I do with Lumia ? Will be warranty considered ?
Click to expand...
Click to collapse
If it is still under warranty, so it's good.
If you need provide an explanation, provide the simplest, such as "When I turn on my phone, I discovered like this", or "I made an update and reboot, I discovered like this, " etc.
As it is currently, the specialized services can not see that you tried to flash.

anaheiim said:
If it is still under warranty, so it's good.
If you need provide an explanation, provide the simplest, such as "When I turn on my phone, I discovered like this", or "I made an update and reboot, I discovered like this, " etc.
As it is currently, the specialized services can not see that you tried to flash.
Click to expand...
Click to collapse
Thank you so much. Regards from Poland

mlotek01 said:
I think it is a last question. Now, when I connect Lumia via usb cable to my pc I get message "unknown device". Will specialized repair service know what I do with Lumia ? Will be warranty considered ?
Click to expand...
Click to collapse
Were you able to solve the issue? I've got exactly the same problem.
Was trying to rollback from windows 10 technical preview, got the error message on windows phone recovery tool.
Snapped the cable in a hurry and now stuck with a dead phone.

https://sujitintel.wordpress.com/2015/05/08/lumia-520-bricked-here-is-100-working-fix-for-all/
I know it's been a long time but it's always good to learn greetings from Argentina

Don't panic
Hi,
please plug your device to your computer. Will it be discovered in Device Manager? If so, is it Nokia Bootmanager or Qualcomm USB Somewhat?
If it is showing the Nokia logo, just retry flashing with WDRT.
Otherwise, look for Lumia Flash Tools. Switch device on holding vol-up or connect it holding vol-up to your computer. When it shows flash and cog wheel, you can flash it with Lumia Flash Tools. You have to select the .ffu file which was downloaded by WDRT.
If the device is recognized as Qualcomm somewhat, I experienced, that after a night without battery it got back to the red Nokia screen and I could retry flashing it with WPInternals.
Best whishes!
Joachim

Tablet dead after booting from Windows 10 pen drive

I've inserted my pen drive with Win10, and a keyboard, onto a hub with the OTG cable that came with the tablet. I opened the BIOS with Esc, booted from the pen drive. It was stuck with the teclast chinese letters logo for about 2-3mins before displaying a Windows error message / blue screen with a face and the following error code: ACPI_BIOS_ERROR. I turned it off by pressing the power button for 8 seconds, then tried to boot again. Nothing. Zero. No reaction. I've plugged it into the charger and it's still dead. What the actual hell? What have I done that I can't even power the tablet on? I hope I didn't hardbrick it.... What happened and what can I do?
EDIT: I mean what the actual hell I bought a tablet, I boot from a pen drive, and it goes dead?? Doesn't even power on even when I plug it into the wall?? Guys what the f**, what happened? I'm freaking out a bit.
EDIT 2: I completely forgot: the tablet is an Air III (m5c5). Thanks for any help!

Sounds like you tried to boot from a x64 edition image and hardbricked the device.

cscz23 said:
Sounds like you tried to boot from a x64 edition image and hardbricked the device.
Click to expand...
Click to collapse
Okay, so what do I do now? How do I recover it?

Your BIOS has been corrupted as you've tried to boot an x64 image from an x86 EFI.
You'll have to replace/reprogram the BIOS chip on your device to unbrick.

cscz23 said:
Your BIOS has been corrupted as you've tried to boot an x64 image from an x86 EFI.
You'll have to replace/reprogram the BIOS chip on your device to unbrick.
Click to expand...
Click to collapse
Well, I didn't know that merely attempting to boot a x64 image hardbricked the tablet... :S Anyways, thanks. Do you have any guide on how to do that? I assume you need an EEPROM programmer, right? Also any guides on how to open up the tablet? Thanks.
Isn't there any other way to do it, that doesn't involve opening the tablet and buying a reprogrammer?

andrepd said:
Well, I didn't know that merely attempting to boot a x64 image hardbricked the tablet... :S Anyways, thanks. Do you have any guide on how to do that? I assume you need an EEPROM programmer, right? Also any guides on how to open up the tablet? Thanks.
Isn't there any other way to do it, that doesn't involve opening the tablet and buying a reprogrammer?
Click to expand...
Click to collapse
you can buy a ch341a on ebay or use an arduino or raspberry pi if you have one of those to reprogram the bios. The three of them will work. If you want the easiest method, go for the ch341a

iscle said:
you can buy a ch341a on ebay or use an arduino or raspberry pi if you have one of those to reprogram the bios. The three of them will work. If you want the easiest method, go for the ch341a
Click to expand...
Click to collapse
I have a raspberry pi. But apparently it works at 3.3V while the BIOS chip works at 1.8V. Is this a problem?

andrepd said:
I have a raspberry pi. But apparently it works at 3.3V while the BIOS chip works at 1.8V. Is this a problem?
Click to expand...
Click to collapse
no, it shouldn't be. the ch341a works on 3v3 also and it has worked for everybody. I think in XDA there is a tutorial for using the rpi as a bios flasher for the teclast.

iscle said:
no, it shouldn't be. the ch341a works on 3v3 also and it has worked for everybody. I think in XDA there is a tutorial for using the rpi as a bios flasher for the teclast.
Click to expand...
Click to collapse
There is, but someone was mentioning on that thread that the rpi GPIO working at 3.3V was a problem, that's why I asked just to make sure. Thanks!

andrepd said:
There is, but someone was mentioning on that thread that the rpi GPIO working at 3.3V was a problem, that's why I asked just to make sure. Thanks!
Click to expand...
Click to collapse
try it and tell us how it went!

Pumpkin KD-C0346 flashed with MTCD. Now black screen

Hi,
i did it.
i flash since i got my first android device(Tmobile G1).
The first time i brick is 8 years since then.
i was so angry at the org. software yesterday that i went straight to xda and downloaded the first Firmware that i found.
It was the MTCD version.
Now i have a black screen. There are still some noises in the background and i think that the ResetButton is still working.
Can i unbrick my device?

slickyboy said:
Hi,
i did it.
i flash since i got my first android device(Tmobile G1).
The first time i brick is 8 years since then.
i was so angry at the org. software yesterday that i went straight to xda and downloaded the first Firmware that i found.
It was the MTCD version.
Now i have a black screen. There are still some noises in the background and i think that the ResetButton is still working.
Can i unbrick my device?
Click to expand...
Click to collapse
You will need to find out what MTC the unit is. Simply saying Pumpkin will not assist as they are a reseller. If you are able to get into recovery, you should be able to flash the stock firmware or aftermarket firmware to get you running again. Holding the power button and pressing reset works for mine to get into recovery.
http://www.autopumpkin.com/forum/viewtopic.php?f=18&t=14&p=17&hilit=KD+C0346#p17

I just tried to update my Xtrons PF75AA4A with the firmware on their site. Now my unit is black and i dont see any recovery! Wife is going to be pissed!!! Why put firmware on your site if it is not compatible! Please let me know any updates on this as i will do the same!

shawndak said:
I just tried to update my Xtrons PF75AA4A with the firmware on their site. Now my unit is black and i dont see any recovery! Wife is going to be pissed!!! Why put firmware on your site if it is not compatible! Please let me know any updates on this as i will do the same!
Click to expand...
Click to collapse
As above, what MCU version was it? MTC? Why would you install firmware on your device without checking its compatibility. If it is MTCB or D or even C, it is compatible. Perhaps if you had done your research prior to flashing you would not have this problem.

You're absolutely right. No idea, it was on their website for my model. Didn't think it would be an issue. Is there a way to flash from a computer?

Take a look over here, just un-bricked my Xtrons device. Make sure to flash the proper firmware. http://forum.xda-developers.com/and...d-kgl-unit-t3457538/post68656680#post68656680

slickyboy said:
Hi,
i did it.
i flash since i got my first android device(Tmobile G1).
The first time i brick is 8 years since then.
i was so angry at the org. software yesterday that i went straight to xda and downloaded the first Firmware that i found.
It was the MTCD version.
Now i have a black screen. There are still some noises in the background and i think that the ResetButton is still working.
Can i unbrick my device?
Click to expand...
Click to collapse
I think you should post in this thread for help :
http://forum.xda-developers.com/and...-mtcb-units-tested-courtessy-t3389906/page125
flashing the firmeware from this post may help restore your unit :
http://forum.xda-developers.com/showpost.php?p=68469248&postcount=877

Kindle 5th Gen Hard Bricked !!!

I have a 5th gen Fire and I tried downgrading to 5.12 from 5.32.x...it didn't work... I now have a tablet which doesn't show any signs of power... I've tried different software I.e. KFU and the Kindle Unbrick tool but no luck....anyway when I connect it to the PC I hear the sound of when I plug in a USB but then about 3 seconds after then it disconnects and then reconnects and so on but never shows anything on the screen it is completely black. My problem is that it won't stay on long enough to do any significant reflash or any kind of fix. If anyone can help me in keeping it on long enough then I could flash with its stock update. I may even have to solder some points on the board but that's fine so long as I can fix it....
Thanks in advanced any help is appreciated

willie018 said:
I have a 5th gen Fire and I tried downgrading to 5.12 from 5.32.x...it didn't work... I now have a tablet which doesn't show any signs of power... I've tried different software I.e. KFU and the Kindle Unbrick tool but no luck....anyway when I connect it to the PC I hear the sound of when I plug in a USB but then about 3 seconds after then it disconnects and then reconnects and so on but never shows anything on the screen it is completely black. My problem is that it won't stay on long enough to do any significant reflash or any kind of fix. If anyone can help me in keeping it on long enough then I could flash with its stock update. I may even have to solder some points on the board but that's fine so long as I can fix it....
Thanks in advanced any help is appreciated
Click to expand...
Click to collapse
This section is for the 1st generation Fire
see
Fire Index: Which Amazon (Kindle) Fire Do I have?
for correct forum links
Sent from my XT1254 using Tapatalk
Edit: thread moved to Fire forum

I have ended up in the exact same spot after attempting a downgrade to 5.1.1.
I downgraded to try and fix an odd problem. I recently wiped my CM version back to stock, but when registering the device it forced me into Kid's Edition - I did the downgrade in an attempt to bypass that. Now it's just a paperweight/doorstop.

dixonge said:
I have ended up in the exact same spot after attempting a downgrade to 5.1.1.
I downgraded to try and fix an odd problem. I recently wiped my CM version back to stock, but when registering the device it forced me into Kid's Edition - I did the downgrade in an attempt to bypass that. Now it's just a paperweight/doorstop.
Click to expand...
Click to collapse
Sorry for your loss; device is unrecoverable. Contact Amazon for a courtesy replacement is still under warranty.