Related
I am at my wits end to try to repair my phone. It is softbricked and responds to download mode only.
I've had chat with xda members and read threads on it:
http://forum.xda-developers.com/chef-central/android/nand-write-start-fail-odin-soluction-t2851096
http://forum.xda-developers.com/galaxy-note-10-1/help/help-help-unbricking-galaxy-note-10-1-t2872125
and many others. in the end, my phone is still stuck with the NAND Write Start error with odin.
I know it happened after i tried creating a backup of my phone in recovery mode (phone was rooted with cf auto root and had a version of CWM on it). CWM gave me a warning about possibly bricking the phone, i agreed to the warning beacuse it always worked in the past, but when i rebooted, it was bricked this time.
this phone is not dead but samsung won't fix it beacuse it is rooted. I refuse to throw it away. I have read many people have it this error since kitkat 4.4 so surely there is a fix somewhere. I am hoping somebody will be more resourceful/experienced than i am.
I have tried changing to several different USB ports, without a hub, using original cables (bunch of different ones too) in many many different order and fashion. I tried enough variation to be convinced it is statistically impossible that all my hardware that was previously working for flashing has stopped working all at once. aka - it is not a usb port or data cable problem
may be related to data charging port on the phone though I highly suspect it given how it started.
I tried different roms, different versions of odin, i tried depackaging and repackaging roms, i simply do not know what to do anymore.
i tried reflashing with kies but kies just dies on me.
i tried flashing it with adb but adb won't even connect. when i plug the phone windows recognizes it and usb driver seems to work ok (not getting an error)
I have uninstalled and reinstalled drivers several times, rebooting in between installs. no difference.
i tried flashing different bootloaders as well as entire roms, no difference
I tried changing the pit file but that failed as well (odin couldn't even write the pit so my phone is not dead even if i failed pitting it)
i have access to both windows and ubuntu linux if it makes a difference.
Here are the terms of the bounty:
Price : 100$ (payable by paypal from eniac0 @ "some google mail domain starting with gm"
goal : find a fix that works on the latest firmware for SGH-i317M (Rogers, Canada)
how : i don't know but i need to be able to reproduce it. I am not new to flashing but anything advanced will need to be explained clearly.
I don't really know how this sorts of request usually turns out but i am serious. you even got my google mail address to bill me up if i fail to pay.
have you given a look at this thread? http://forum.xda-developers.com/showthread.php?t=2711825 it might give you some ideas to help you out. also did you try flashing a new recovery to see if you could at least get it to boot to that?
dont care about the bounty just trying to toss something out there that may help you
Did you ever try flashing the stock recovery - JUST the stock recovery - through Odin?
If not, grab the recovery.img and make your own tarball for Odin in Linux.
Hopefully that will flash and get you closer.
eniac0 said:
I am at my wits end to try to repair my phone. It is softbricked and responds to download mode only.
...
i have access to both windows and ubuntu linux if it makes a difference.
Click to expand...
Click to collapse
Since you mentioned Ubuntu, you can also try using heimdall instead of odin... http://glassechidna.com.au/heimdall/ . Unfortunately, I think it may be a hardware problem?
Since you are willing to pay to have it fixed, if all else fails, you can always send it off to http://mobiletechvideos.mybigcommerce.com/samsung-galaxy-note-jtag-brick-repair/. It will actually be cheaper than what you are offering to pay ~$40 + shipping
good luck
Thanks all for your help, I've messed around and gotten no closer. I'm beginning to lean on a hardware failure, perhaps from the usb data port either that or the way bootloaders are packaged in kitkat 4.4 is different. which is why initially this thread gave me hope: http://forum.xda-developers.com/chef-central/android/nand-write-start-fail-odin-soluction-t2851096 but i tried far too many times now to believe I'm going to succeed. In fact, I've gotten confused as to what i tried, in which order, with which rom. I'm basically trying anything and that's a recipe for bricking the phone for good. so i've stopped.
I'll also thank kozmo21 for the link to the repair shop. i was unaware this existed, as a last resort I'll be sending them my phone. If it turns out they are able to repair it, I'll honor my word and give you something for having been part of the solution.
eniac0 said:
I am at my wits end to try to repair my phone. It is softbricked and responds to download mode only.
I've had chat with xda members and read threads on it:
http://forum.xda-developers.com/chef-central/android/nand-write-start-fail-odin-soluction-t2851096
http://forum.xda-developers.com/galaxy-note-10-1/help/help-help-unbricking-galaxy-note-10-1-t2872125
and many others. in the end, my phone is still stuck with the NAND Write Start error with odin.
I know it happened after i tried creating a backup of my phone in recovery mode (phone was rooted with cf auto root and had a version of CWM on it). CWM gave me a warning about possibly bricking the phone, i agreed to the warning beacuse it always worked in the past, but when i rebooted, it was bricked this time.
this phone is not dead but samsung won't fix it beacuse it is rooted. I refuse to throw it away. I have read many people have it this error since kitkat 4.4 so surely there is a fix somewhere. I am hoping somebody will be more resourceful/experienced than i am.
I have tried changing to several different USB ports, without a hub, using original cables (bunch of different ones too) in many many different order and fashion. I tried enough variation to be convinced it is statistically impossible that all my hardware that was previously working for flashing has stopped working all at once. aka - it is not a usb port or data cable problem
may be related to data charging port on the phone though I highly suspect it given how it started.
I tried different roms, different versions of odin, i tried depackaging and repackaging roms, i simply do not know what to do anymore.
i tried reflashing with kies but kies just dies on me.
i tried flashing it with adb but adb won't even connect. when i plug the phone windows recognizes it and usb driver seems to work ok (not getting an error)
I have uninstalled and reinstalled drivers several times, rebooting in between installs. no difference.
i tried flashing different bootloaders as well as entire roms, no difference
I tried changing the pit file but that failed as well (odin couldn't even write the pit so my phone is not dead even if i failed pitting it)
i have access to both windows and ubuntu linux if it makes a difference.
Here are the terms of the bounty:
Price : 100$ (payable by paypal from eniac0 @ "some google mail domain starting with gm"
goal : find a fix that works on the latest firmware for SGH-i317M (Rogers, Canada)
how : i don't know but i need to be able to reproduce it. I am not new to flashing but anything advanced will need to be explained clearly.
I don't really know how this sorts of request usually turns out but i am serious. you even got my google mail address to bill me up if i fail to pay.
Click to expand...
Click to collapse
Have you tried going to sammobile and download the newest firmware and only flashing that in odin?
Use CF auto root. Put the phone in download mode and flash it in Odin. I soft bricked my phone and it fixed it.
Also this guy had great walk through videos on how to do everything you need.
http://www.rootjunky.com/samsung/samsung-galaxy-note-2/
If it works to fix your phone. Keep your money. I'll take the karma points for putting you on the correct path.
Sent from my SHIELD Tablet using XDA Free mobile app
ShrekOpher said:
Use CF auto root. Put the phone in download mode and flash it in Odin. I soft bricked my phone and it fixed it.
Also this guy had great walk through videos on how to do everything you need.
http://www.rootjunky.com/samsung/samsung-galaxy-note-2/
If it works to fix your phone. Keep your money. I'll take the karma points for putting you on the correct path.
Sent from my SHIELD Tablet using XDA Free mobile app
Click to expand...
Click to collapse
More than likely its a bootloader issue my phone did that and all i did was flash the bootloader then it worked again but hes done so much idk what he needs now that's y i said to try a firmware to see if that helps
Download toolkit and select option to push file into phone.
Download a ROM of your choosing, push it into your phone, restart in recovery mode and select file.
Update?
Did you get it fixed? Just my two cents, in case you didnt, I had a similar problem and alll I did to fix it was flash the JediMasterX2 ROM with CWM and everything worked out.
i have my friends phone and he's galaxy s3 is stuck on download mode and its looping there everytime
it happened out of nowhere, he wasn't playing around with it it just happened
now its stuck on downloading and wont go to recovery for me to initialize the device through kies or smartswitch
NO ACCESS TO RECOVERY MODE AT ALLL
i tried numerous ways to retrieve the phone into working condition but no success at all
thru odin i get the pit error and when i place a pit to repartititon with the stock tar file or the cwm recovery tar i failed
it says complete write operation failed and it takes a long time to set up connection with the device before showing me the fail
its a tmobile sgh-t999 prob 16 gb
any genius here got any ideas?
What firmware build was on the device and what build did you try to flash using Odin?
Did you try different versions of odin?
Different driver versions?
Different USB cable?
Different USB port?
If kies is installed on the computer, get rid of it. It interferes with Odin.
If none of that helps it may be a hardware failure.
Sent from my SGH-T999 using Tapatalk
The same thing has happened to my wife's phone and I have done almost the same steps to fix it with similar results.
If you tried everything I mentioned and are sure you weren't flashing an older firmware build (only after 4.3), then theres a good chance it's a hardware failure, probably with the memory.
Sent from my SGH-T999 using Tapatalk
DocHoliday77 said:
If you tried everything I mentioned and are sure you weren't flashing an older firmware build (only after 4.3), then theres a good chance it's a hardware failure, probably with the memory.
Sent from my SGH-T999 using Tapatalk
Click to expand...
Click to collapse
OK, uninstalled Kies and tried to flash T999UVUEOH1_T999TMBEOH1_TMB rom with odin again and got there is no pit partition error. Would post some pictures of the boot screen and a screenshot of the odin program but need 10 posts. Well not sure what version was on phone before all this happened.) Also the ODIN bootloader screen says SYSTEM STATUS: NONE Warrenty Bit: 0 BOOTLOADER AP S?AEV: 1 among other things...forgot to mention I used ODIN v3.10.6 because v3.10.7 gave me a win32 error when I tried to run it on my Windows XP PC.
Here's my suggestion to at least get the phone running a ROM:
download Odin 3.07 from here: https://www.google.ca/url?sa=t&rct=...5QWImOPDJboTA_V3D5S9eA&bvm=bv.107763241,d.dmo
download the tar version of TWRP 2.8.6.0 from here: https://dl.twrp.me/d2tmo/
download the latest cm12.1 for the phone from here and save it to a micro SD card: https://download.cyanogenmod.org/?device=d2tmo&type=nightly
place the micro SD card into the phone;
boot the phone into download mode;
open Odin 3.07 and uncheck everything except f. reset time;
click on PDA and browse to the tar TWRP file and select it;
connect the phone and it should show up as a com port in Odin;
flash TWRP;
when you see the word RESET in the status window, remove the USB cable, remove the battery, replace the battery, use the button combination to get into recovery which should now be TWRP;
perform a full wipe of system, data, and cache;
flash CM12.1 from the micro SD card;
reboot the phone.
Hopefully, the above steps will get the phone booted so you can confirm the installed bootloader and modem.
Followed your guide step by step but flash failed in odin Get Pit for mapping..
There is no PIT partition.
All threads completed. (succeed 0 / failed 1):crying: BTW thank for all your help.
You got the pit error flashing twrp in Odin? Any other errors? What model number is shown at the top of the screen when the phone is in download mode?
The only times I've encountered this type of behavior it turned out to be a hardware failure (memory). If that is indeed the case here, I'm afraid there won't be much you can do for it. Don't get me wrong, I'm not saying you should just give up, but you should probably at least start looking at other options.
The main reasons I believe this to be the case are
1. It just died while nothing was being done (not being used)
2. Pit errors indicate either the partition table has been corrupted, or the partitions themselves have. Because it cannot detect any system (SYSTEM STATUS: NONE), it's more likely to be the partitions them selves, not the partition information table (pit).
Something else that doesn't look good, (but that I've never seen before) is the S?AEV. It should be SWREV. (Software Revision). It may mean nothing, but I've never seen it before so I thought I'd point it out.
As I said, I'm not saying you should give up yet. I've been wrong before and I'd hope to be again in this case. But I wouldn't put too much more time and effort into it as I've never seen one of these types of failures restored. They are pretty rare, but they do happen.
My best suggestion at this point is to start looking into replacing either the motherboard or the device. Motherboards can be found for reasonable prices, but you do have to be careful when buying one. (Let us know if you want to do this and we'll give you some tips on what to look for).
I'm sorry that this happened and that there doesn't seem to be much I can do to help. If you had any important data (pics or whatever), there's a small chance it can still be recovered. Don't get your hopes up too much for it, but using ADB while in download mode MIGHT allow you to copy your stuff to the computer. I can't remember if this can be done from download mode though, and if the data partition is also hosed you'd be out of luck there anyway.
If i think of anything else you can try, I'll certainly let you know. Audit13 might have a few ideas you can try too. As I said though, you should also start looking into other options. Let us know what you want to do and we'll continue to help as best as we can!
Sent from my SGH-T999 using Tapatalk
DocHoliday77 said:
The only times I've encountered this type of behavior it turned out to be a hardware failure (memory). If that is indeed the case here, I'm afraid there won't be much you can do for it. Don't get me wrong, I'm not saying you should just give up, but you should probably at least start looking at other options.
The main reasons I believe this to be the case are
1. It just died while nothing was being done (not being used)
2. Pit errors indicate either the partition table has been corrupted, or the partitions themselves have. Because it cannot detect any system (SYSTEM STATUS: NONE), it's more likely to be the partitions them selves, not the partition information table (pit).
Something else that doesn't look good, (but that I've never seen before) is the S?AEV. It should be SWREV. (Software Revision). It may mean nothing, but I've never seen it before so I thought I'd point it out.
As I said, I'm not saying you should give up yet. I've been wrong before and I'd hope to be again in this case. But I wouldn't put too much more time and effort into it as I've never seen one of these types of failures restored. They are pretty rare, but they do happen.
My best suggestion at this point is to start looking into replacing either the motherboard or the device. Motherboards can be found for reasonable prices, but you do have to be careful when buying one. (Let us know if you want to do this and we'll give you some tips on what to look for).
I'm sorry that this happened and that there doesn't seem to be much I can do to help. If you had any important data (pics or whatever), there's a small chance it can still be recovered. Don't get your hopes up too much for it, but using ADB while in download mode MIGHT allow you to copy your stuff to the computer. I can't remember if this can be done from download mode though, and if the data partition is also hosed you'd be out of luck there anyway.
If i think of anything else you can try, I'll certainly let you know. Audit13 might have a few ideas you can try too. As I said though, you should also start looking into other options. Let us know what you want to do and we'll continue to help as best as we can!
Sent from my SGH-T999 using Tapatalk
Click to expand...
Click to collapse
Wow, thanks Doc for replying. I was hopeful for a better result. BTW it does say SWREV I just couldn't quite make out the W at the time so I put ? to indicate that. I do have a little experience working on these phones (replaced the entire LCD/screen and USB port on my Note2) The model of the phone is listed as SGH-T999 in ODIN mode and it is a T-mobile phone. How much is motherboard and what should I look for as far as part number?
Found this with a quick ebay search: http://m.ebay.com/itm/Samsung-Galax...Board-Motherboard-s3-/221940485670?nav=SEARCH
I searched for "galaxy s3 T999 motherboard". That one is 68.50 obo.
It's been a while since I've looked, and it looks like there's a lot fewer of them available now. (Used to get tons of results).
You can also look for an I747 (AT&T) board. The I747 and T999 are fully compatible. No other models will fit into the case. (The T999V and I747M would probably also work. I'm not sure about the T999L or T999N models though. I'm guessing they would, but really have no idea for sure.)
Some terms to search for would be: Galaxy S3 T999 motherboard, I747 motherboard, mainboard, etc.
Also search for the same models with broken screens. Many times people sell these cheap and everything inside works perfectly. Might be cheaper too.
Watch out for certain words and phrases in the listing though. Some sellers will try a little wordplay to make it sound better than it is. If i find an example, I'll post it. Stuff like cracked screen won't power on can be changed to sound like it's only the screen won't come on, when it's really the whole device. Either ask for clarification, or move on.
I like the ones that are very specific, like cracked screen, but does appear to boot up and gives boot sounds.
Ask the seller for the imei number and check it yourself on swappa. I'd also call t-mobile and verify with them.
I hope that helps. Feel free to ask if you're wondering about a specific listing or anything else.
Oh and if buying from an eBay store, make sure they've got very good ratings. Individual people often won't have many ratings, but can sometimes be more trustworthy and more willing to give specifics. Sometimes....
You can also check places like Swappa and Craigslist.
Sent from my SGH-T999 using Tapatalk
The simplest way to get a replacement motherboard would be to look in the used market for a t999 that has smashed or defective screen with working internals.
If it is not too expensive, a jtag repair centre may be able to force flash a rom.
Hello, first timer here. I have never tried rooting or anything, but today I finally decided to... and messed it up.
Verizon Samsung Note 2 SCH-i605 (yes, still.)
Got it on July 2nd, 2013, so I believe it was build 4.1.1 kernel 3.1? Not too sure on the legalities
Completely unrooted and unmodded
I was using kingo root and everything was fine until it hit about 52% on the rooting process when my computer lost connection with my phone. Since, it gave me the "Firmware upgrade encountered an issue" problem. So then I google-fu'd and followed directions of:
http://forum.xda-developers.com/showthread.php?t=2040264
http://forum.xda-developers.com/showthread.php?t=2120726
http://forum.xda-developers.com/showthread.php?t=2582290
http://forum.xda-developers.com/showthread.php?t=2024207
etc.
and used Odin 3.10.7 (and 3.10.0 just in case, both on and off admin mode cause why not) on every single md5 available in all those links and the one from sammobile.com for sch-i605.
And each time, I would either received failure on "sboot.bin" or receive the "System Software Not Authorized" error if succeeded (it was stuck in bootload? too, kept flashing the logo then the error message). The VERY first time, however, it actually brought me to that page where I'm allowed to press things like erase cache, factory reset, or reboot my phone. There, I chose all those options in the order I've listed them. And ever since I haven't seen that screen again.
My issue seems to be every problem I can find put together, and can't seem to resolve it with my skills alone. I honestly don't care about recovering my data (which I believe is impossible now anyway) or rooting my phone. I just want it to turn on again.
Thanks in advance.
p.s. getting a new phone isn't an option currently
-edit-
Checked my verizon wireless software upgrade assistant for some info, and it says "Up to date" and "Version ND3" if that means anything to you pros out there.
jk1982 said:
Hello, first timer here. I have never tried rooting or anything, but today I finally decided to... and messed it up.
Verizon Samsung Note 2 SCH-i605 (yes, still.)
Got it on July 2nd, 2013, so I believe it was build 4.1.1 kernel 3.1? Not too sure on the legalities
Completely unrooted and unmodded
I was using kingo root and everything was fine until it hit about 52% on the rooting process when my computer lost connection with my phone. Since, it gave me the "Firmware upgrade encountered an issue" problem. So then I google-fu'd and followed directions of:
http://forum.xda-developers.com/showthread.php?t=2040264
http://forum.xda-developers.com/showthread.php?t=2120726
http://forum.xda-developers.com/showthread.php?t=2582290
http://forum.xda-developers.com/showthread.php?t=2024207
etc.
and used Odin 3.10.7 (and 3.10.0 just in case, both on and off admin mode cause why not) on every single md5 available in all those links and the one from sammobile.com for sch-i605.
And each time, I would either received failure on "sboot.bin" or receive the "System Software Not Authorized" error if succeeded (it was stuck in bootload? too, kept flashing the logo then the error message). The VERY first time, however, it actually brought me to that page where I'm allowed to press things like erase cache, factory reset, or reboot my phone. There, I chose all those options in the order I've listed them. And ever since I haven't seen that screen again.
My issue seems to be every problem I can find put together, and can't seem to resolve it with my skills alone. I honestly don't care about recovering my data (which I believe is impossible now anyway) or rooting my phone. I just want it to turn on again.
Thanks in advance.
p.s. getting a new phone isn't an option currently
-edit-
Checked my verizon wireless software upgrade assistant for some info, and it says "Up to date" and "Version ND3" if that means anything to you pros out there.
Click to expand...
Click to collapse
Greetings,
Thank you for using XDA Assist. To get you the best possible assistance, I'm going to move this thread to your device's Q&A forum. Good luck!
install kies and try flashing rom. do you have rom from i.e. sammobile? use different odin versions and do not mark repartition
yaro666 said:
install kies and try flashing rom. do you have rom from i.e. sammobile? use different odin versions and do not mark repartition
Click to expand...
Click to collapse
KIES is unable to read my phone (tried the bottom 3 versions of it), and I've tried running Odin 3.07 and unchecked repartition for every stock and restore md5s I had for my phone... the ones that didn't fail sboot.bin are still giving me unauthorized error.
I'll keep trying all the combinations, but it seems moot at this point.
I've tried searching around here for an answer, but I haven't really been able to find anything solid regarding the issue that I'm experiencing. The other day I popped my sim card into my sgh-i467, as I do from time to time, to check for any OTA updates. This device is usually mounted in my vehicle, so I don't regularly check for updates. Sure enough, an OTA update was available. Tablet was at maximum charge, so I went ahead and chose to do the update. Unfortunately, the update failed at around 93% and went into a boot loop. There was nothing crucial on the device, so I figured it'd be no big deal to just re-flash the firmware if need be. However, I can only seem to find a KIES image for 4.1.2, and while I didn't think to verify exactly what version I was on before the bootloop/brick, I'm fairly certain I was on 4.2.xx.
From what I understand, the bootloader updates with 4.4, correct? With the bootloader getting updated, downgrading to 4.1.2 isn't possible or feasible, right? I didn't think to confirm this before I attempted to flash the KIES image for 4.1.2 via odin (kies never seems to actually see my device), which fails every attempt. I was originally able to get into recovery, but I kept seeing that /system wasn't found. I'm assuming that the OTA update partially installed, before failing, and either corrupted the partition scheme or updated the bootloader but not the system?
I'm dead in the water at this point, and AT&T is obviously no help. Plus, I don't the device on contract with them anyway, so I'm starting to think that my only option is to contact Samsung. However, I really don't want to have to send the unit in, and given it's age, I don't think it's worth investing anything in it if the repair isn't covered somehow. Plus I enjoy tinkering, I'm not new to the scene, and I'd really like to come up with a solution that doesn't require Samsung.
I don't suppose any kind people out there have any suggestions, similar experiences, etc. do they? I'd really like to hear from anyone who's got something to offer! Thanks in advance for your help!
pbrady5 said:
I've tried searching around here for an answer, but I haven't really been able to find anything solid regarding the issue that I'm experiencing. The other day I popped my sim card into my sgh-i467, as I do from time to time, to check for any OTA updates. This device is usually mounted in my vehicle, so I don't regularly check for updates. Sure enough, an OTA update was available. Tablet was at maximum charge, so I went ahead and chose to do the update. Unfortunately, the update failed at around 93% and went into a boot loop. There was nothing crucial on the device, so I figured it'd be no big deal to just re-flash the firmware if need be. However, I can only seem to find a KIES image for 4.1.2, and while I didn't think to verify exactly what version I was on before the bootloop/brick, I'm fairly certain I was on 4.2.xx.
From what I understand, the bootloader updates with 4.4, correct? With the bootloader getting updated, downgrading to 4.1.2 isn't possible or feasible, right? I didn't think to confirm this before I attempted to flash the KIES image for 4.1.2 via odin (kies never seems to actually see my device), which fails every attempt. I was originally able to get into recovery, but I kept seeing that /system wasn't found. I'm assuming that the OTA update partially installed, before failing, and either corrupted the partition scheme or updated the bootloader but not the system?
I'm dead in the water at this point, and AT&T is obviously no help. Plus, I don't the device on contract with them anyway, so I'm starting to think that my only option is to contact Samsung. However, I really don't want to have to send the unit in, and given it's age, I don't think it's worth investing anything in it if the repair isn't covered somehow. Plus I enjoy tinkering, I'm not new to the scene, and I'd really like to come up with a solution that doesn't require Samsung.
I don't suppose any kind people out there have any suggestions, similar experiences, etc. do they? I'd really like to hear from anyone who's got something to offer! Thanks in advance for your help!
Click to expand...
Click to collapse
You need to upgrade to keis 3.0 and reboot, then start kies, then boot note into download mode and have kies detect and reload the update.
Too bad you let the Note update to Kit Kat, Jellybean is better, on the LTE Note.
gooberdude said:
You need to upgrade to keis 3.0 and reboot, then start kies, then boot note into download mode and have kies detect and reload the update.
Too bad you let the Note update to Kit Kat, Jellybean is better, on the LTE Note.
Click to expand...
Click to collapse
Thank you very much for the information! Unfortunately, I've tried Kies 3.0. It notifies me that my device isn't compatible with Kies 3.0. With the other version of Kies, 2.6 maybe(?), it never ends up being able to connect. I've tried manual initialization, but when after I enter my model number, it won't accept my serial.
Take it to a BEST BUY with a Samsung Experience Center (Kiosk (Most all of them in larger cities have them) and they will fix your SGH-i467 for free. I did almost the same exact thing as you (trying to solve a EFS problem) and was stuck. I have posted about it on here before. They will not charge you BUT you may run into a clueless rep now and then. If you do, ask them to call for help and they will get you fixed up in a hurry. Hope this helps.
Hello all,
I've run into an issue with my new head unit. I was just trying it out before installing it, got it powered up from my bench supply to test, and as soon as I installed a couple of apps (Plex and Google Play Music) it started bootlooping on me.
I figured I would go ahead and install a CFW since I do that for all my android devices anyway, but I've gotten myself into a pickle now. I can prompt the unit to attempt a firmware update, but all of the firmware releases I've found are in nupdate.img format, and the recovery is looking for a "kupdate.zip" format. I did try using the SD_Firmware_Tool to build an sdcard for this, but it seems to just be getting ignored.
The current behavior is that I get the "Pumpkin" bootloader logo, then it reboots. It no longer even shows the "android" loading screen as It did before I tried using the SD_Firmware_Tool.
For reference, I was trying to use the Hal9k rom from here
Getting to the onboard update menu works by holding the power button (pushing down the volume wheel) and hitting the reset button. I haven't been able to get it to boot into any other recovery modes yet, but if anyone happens to know of another button combo that should be working, please let me know.
I've put in an email to pumpkin support but I have a feeling they'll take a while to get back to me with the firmware, so hoping someone else might have something I can use in the meantime.
Well apparently I was mistaken about what CPU is under the hood of this thing (was going by a user review on the amazon page where I purchased it.)
According to the recovery it's loading into, this has an RK3368 rather than the RK3188 I expected
Little Update:
I'm trying out this unbrick for the PX5 to see if I can get it to use a more robust recovery. The current one keeps trying to mount a nonexistant drive location to run the kupdate.zip, and most of the pictures I've found of people's recoveries floating around on here have had the option to choose update files from different locations, so I think the recovery on this needs an update.
It's so far booting to a black (backlight on) screen and not progressing, so I hope the firmware update is going in the background and I just need to wait it out. Anyone know how long that firmware update process should take?
well I think my unit may just be new or different somehow, as none of the unbrick metbods seem to be working at the moment.
I've attached some pics of the unit's internals to see if that can help find a solution
How have you ascertained it to be an MTC(D/E) - it isnt
marchnz said:
How have you ascertained it to be an MTC(D/E) - it isnt
Click to expand...
Click to collapse
I suppose there were some assumptions made based on what's already available on the market.
If it's not an MCT(#) then what is it?
Pyr0ball said:
I suppose there were some assumptions made based on what's already available on the market.
If it's not an MCT(#) then what is it?
Click to expand...
Click to collapse
An XDA search for [kupdate] yeilds the information.
Made some progress on figuring this module out