So my Moto Z died again, and this time the PC wont even detect the phone as QUSB_BULK device so i cannot even run the blankflash file. And i know there are lot of people who are facing the same problem.
So the last time my PC detected the device and i ran the blnkflash file, it gave me the following error, which makes it clear that the eMMC is unreachable.
Motorola qboot utility version 3.37
[ 0.000] Opening device: \\.\COM6
[ 0.003] Detecting device
[ 0.007] ...cpu.id = 2375 (0x947)
[ 0.007] ...cpu.sn = 1125564604 (0x4316c0bc)
[ 0.007] Opening singleimage
[ 0.035] Loading package
[ 0.037] ...filename = singleimage.pkg.xml
[ 0.039] Loading programmer
[ 0.041] ...filename = programmer.elf
[ 0.041] Sending programmer
[ 0.117] Handling things over to programmer
[ 0.118] Identifying storage type
[ 0.119] Waiting for firehose to get ready
[ 60.122] Could not determine storage type. Assuming eMMC...
[ 60.122] Identifying CPU version
[ 60.122] Waiting for firehose to get ready
[ 63.136] WriteFile() failed, GetLastError()=0
[120.126] Waiting for firehose to get ready
[123.141] WriteFile() failed, GetLastError()=0
Click to expand...
Click to collapse
So i tried looking on the internet, and the closes thing that i found were 2 option:
1 - You replace your eMMC (Which is not an easy job)
2 - YOU CAN BOOT YOUR DEVICE WITH A MICRO SD CARD
But i dont have an SD Card so i have ordered it from Amazon and it'll arrive in few days. By that time, if anyone contribute anything or has a micro SD Card then they can try flashing their firmware on it and give a feedback then it'll be really appreciated.
Try whit the last blankflash
https://forum.xda-developers.com/attachment.php?attachmentid=4378225&d=1514981126
Manish54 said:
So my Moto Z died again, and this time the PC wont even detect the phone as QUSB_BULK device so i cannot even run the blankflash file. And i know there are lot of people who are facing the same problem.
So the last time my PC detected the device and i ran the blnkflash file, it gave me the following error, which makes it clear that the eMMC is unreachable.
So i tried looking on the internet, and the closes thing that i found were 2 option:
1 - You replace your eMMC (Which is not an easy job)
2 - YOU CAN BOOT YOUR DEVICE WITH A MICRO SD CARD
But i dont have an SD Card so i have ordered it from Amazon and it'll arrive in few days. By that time, if anyone contribute anything or has a micro SD Card then they can try flashing their firmware on it and give a feedback then it'll be really appreciated.
Click to expand...
Click to collapse
I was stuck in the same, but a couple of days ago I found blankflash version commented above and I managed to back my device back.
there is one thing that I dont know if relevant, but I couldnt recovery using my notebook and desktop PCs on windows 10. Only in another machine with Windows 8 I got it.
Any luck with SD CArd
Any luck with memory card?? My phone is in 9008 mode, but doesn't show up in disk drives. @Manish54
makefriends85 said:
Any luck with memory card?? My phone is in 9008 mode, but doesn't show up in disk drives. @Manish54
Click to expand...
Click to collapse
My phone died years ago and i buried it somewhere.
Tried everything for months and years, nothing worked. And now i have stopped rooting phones.
Related
Hi.
Dexter tell us: "Rename downloaded patch to update.zip and install using recovery.", but i know how to make a update,however how do i make an installation using recovery?
I only would like to know all the steps to install FolioMod v1.4 correctly.
Please tell me the steps like i was fool
Thanks a lot.
Help please
It's quite clear in the TXT attached in the mod, but if you prefer there are two alternative procedures in the #1 post of the thread. The update is not particulary difficult to execute, if you need more info please post a printscreen or better explain what's failling.
Rename downloaded patch to update.zip and install using recovery.
Click to expand...
Click to collapse
That's not true when you downloaded Foliomod 1.4
In the Foliomodv14.zip is a file called update.zip, the file update.zip should be copied to a SDCard and the follow the given instructions.
Today I wanted to install Modfolio 1.4 and after preparing my SDcard I had those weird messages Can't mount SD-card can't find update.zip while attempting to upgrade from a Modfolio 1.3d ...
I read alot and here is how I solved the issue... If fact I applied all the recommanded methods ...
First I prepared a new SD-card I took my SD-CARD under linux mint I used disk remove the partition and made a 1GB new partition utility.
Formated it in FAT32 and put on it the update.zip file on it.
I started my folio tablet and activated in settings > applications> usb debugging ( not sure this has anyeffect)
- I installed Android SDK + Google usb driver
- I updatate the android_winusb.inf
- I copyed to $android_sdk/tools the recovery.img from dexter's update-recovery.zip
- I rebooted my folio and put it in fastboot mode (3 time pow then vol+). I plugged my folio 100
with usb to my desktion computer.
- In windows, CMD.EXE I navigated to $android_sdk/tools and I used
fastboot erase recovery
fastbot flash recovery recovery.img
fastboot console output was:
sending 'recovery' (4964 KB)... OKAY [ 0.325s]
writing 'recovery'... OKAY [ 0.733s]
finished. total time: 1.058s
- I rebooted my folio100 entered the recovery mode (pow +, pow -, pow +) and the install of the Modfolio 1.4 started smoothly. 5 minutes later it was all done...
Which method was the one really effective ? I don't know but it was fun to try them all at once . I think changing the recovery.img isn't a bad thing and resizing the SD-card to 1 GB isn't a bad thing too... And it can be reverted anytime.
Thank you dexter for your hard work ! So far this Modfolio 1.4 is waaaaaay better anything else. I will never understand lazy companies wasting awesome hardware with cheap port of android OS...
Want to root but don't have a microsd card reader? Is the 8 failed boot trick leaving you tired and bloated? Have you had nightmares of Winimage drinking all your beer and stealing your car?
Help is on the way.
This pile of utilities, images, and scripts will boot your Nook into CWM recovery entirely over USB. Your eMMC can be trashed and SD card missing, but you can still get into recovery. This is kinda rough, and Linux only for now, but a Windows version is in the works.
Need:
-PC running Linux (x86 or x86-64 with 32 bit compatibility libs)
-Nook Color plugged in w/ USB
-this archive unpacked: nc-usb-recovery-0.1.tar.bz2
Do:
-turn off NC
-sudo ./booty
-turn on NC
-wait
This is awesome, gonna try it but I'm sure it will help people out. Now just make an android os boot from computer
Awesome work!
I would love to make something like unrEVOed's GUI for simple rooting/cm7 installations.
Does this just grab a kernel + ramdisk from usb? Any chance of any larger storage? (or use adb + /media?)
nice idea. Im pretty sure it will help other. It would have helped me if it was out about 5 months ago...
nemith said:
Awesome work!
I would love to make something like unrEVOed's GUI for simple rooting/cm7 installations.
Does this just grab a kernel + ramdisk from usb? Any chance of any larger storage? (or use adb + /media?)
Click to expand...
Click to collapse
It doesn't really matter what you send since after the kernel gets booted it doesn't matter how it and the initrd got loaded into memory. Ultimately we're running almost the same u-boot as we do off of mmc media and booting using almost the same boot scripts.
In this case, I'm sending CWM as my payload. CWM lets you share out /sdcard over usb, which isn't the most convenient way to make a "one click" solution. You could pretty easily hack up CWM to look to the initrd for one or more update files. Or like you said, use adb. You could even replace the kernel/ramdisk payload with one of the *nooters for a simple stock root.
-Deleted-
Any chance of this getting updated to a newer cwm/twrp version?
Sent from my NookColor using Tapatalk
Any ideas?
Not much has been added to this thread lately, but I am hoping someone may have some ideas about my problem with this method. Pasted below is as far as I get and it hangs at < waiting for device >:
waiting for OMAP3/OMAP4 device...
sending get asic id message to target...
05010501443007041302010012150102FFFFFFDE540E0A4C61FFFFFF9B6FFFFFFFC72360FFFFFFD9583411FFFFFFF31CFFFFFFC403142101305219FFFFFF8D6FFFFFFF9313FFFFFFBEFFFFFF93FFFFFFFF48FFFFFFC6FFFFFFE101FFFFFFC1FFFFFFEBFFFFFFF0FFFFFFF31AFFFFFFB62920FFFFFFCDFFFFFFF07D45FFFFFFD1FFFFFFE812102B21150901FFFFFF9C66FFFFFF9AFFFFFFD9682AFFFFFFDCFFFFFFCF
Device OMAP4430 found
sending 2ndstage to target...
waiting for 2ndstage response...
unexpected 2ndstage response
creating boot image...
creating boot image - 3678208 bytes
< waiting for device >
The error seems to be "unexpected 2ndstage response". A few things about my Nook; first tried it registered and than I did the reset.., same thing. Version 1.4.2. Thanks ahead of time for any assistance!
You have to have it off and plugged in and then hit power about 3 seconds after it says "waiting for device." I also have never tried it with the stock boot loader so that might be the problem.
Sent from my 2013 Kindle Fire HD with Tapatalk
Thanks for the input, will try that later on. When you say stock boot loader, you mean from the factory as is? It was my impression this was intended to avoid using a SD to root. Is there something else that I need to do before this method?
Galaxy S3 running Eclipse 4.3
http://rootzwiki.com/topic/38786-tpdebrick-v004/
Jcsullins did it again, and has provided the touchpad community with a complete toolset and guide to fix a bricked touchpad. Hit it up if your touchpad has been bricked or your facing the dreaded questionmark of death.
jlc0312 said:
http://rootzwiki.com/topic/38786-tpdebrick-v004/
Jcsullins did it again, and has provided the touchpad community with a complete toolset and guide to fix a bricked touchpad. Hit it up if your touchpad has been bricked or your facing the dreaded questionmark of death.
Click to expand...
Click to collapse
Ran it on mine yesterday after having the damn question mark. Took about 5 minutes, and now I am back in business!
USB Symbol after use tpdebrick
Hi:
My touchpad was working fine, after turn it off and after vibrate to turn it OFF suddenlly appear the USB on screen. To erase it, I did a reset with power bottom and home button and turn that off. Now, after trying more than. 3 times with J C Sullins tpdebrick, go ALL DOME but just appear the USB symbol on screen, from there I have used webOS doctor and after finish, it say can not reboot and again, the USB Symbol on screen.
Any idea to work with this?
Thanks for all help.
Does any one know if this script can be run via mac terminal
Sent from my SCH-I545 using Tapatalk
One of my touchpad is 100% dead. It couldn't even show anything on screen. not sure if this can save it...
64 GB tpdebrick??
I used the TP Debrick on my 64 GB Touchpad. I notice that the process runs "ebr32.bin", "mbr32.bin". The contents of tpdebrick have what looks to be files specific for 16 gb, 32 gb and 64 gb. I have run the command correctly for a 64 gb version but I think there is a possible programming error since it executes the 32gb version of ebr and mbr.
The process went all the way through and ended in "All Done" but I still cant revive this thing
Just an assumption based on what I have seen, can anyone correct me or look into this?
Unbricked one touchpad with this. Awesome. Please donate.
64GB
davo89 said:
I used the TP Debrick on my 64 GB Touchpad. I notice that the process runs "ebr32.bin", "mbr32.bin". The contents of tpdebrick have what looks to be files specific for 16 gb, 32 gb and 64 gb. I have run the command correctly for a 64 gb version but I think there is a possible programming error since it executes the 32gb version of ebr and mbr.
The process went all the way through and ended in "All Done" but I still cant revive this thing
Just an assumption based on what I have seen, can anyone correct me or look into this?
Click to expand...
Click to collapse
Hey Davo89, you figure yours out? My 64GB is bricked as well. I used the debricker, and I can't get past 8% on the webOS. I obviously need to re-do the partitions, but can find no info on how to do this for a 64GB.
dharmastation3 said:
Hey Davo89, you figure yours out? My 64GB is bricked as well. I used the debricker, and I can't get past 8% on the webOS. I obviously need to re-do the partitions, but can find no info on how to do this for a 64GB.
Click to expand...
Click to collapse
No, mine is still bricked, I think the TPdebrick program is meant to work on the 64, but I am pretty sure when the script runs it is referencing the 32 gb files.
I have tried everything I could find, now the damn thing wont take a charge.
Hopefuly jscullins sees these comments and looks into the code for us.
I check here all the time to see if anyone knows an answer. Do me a favor and let me know if you figure yours out. Good luck
dharmastation3 said:
Hey Davo89, you figure yours out? My 64GB is bricked as well. I used the debricker, and I can't get past 8% on the webOS. I obviously need to re-do the partitions, but can find no info on how to do this for a 64GB.
Click to expand...
Click to collapse
By the way, I agree, there is nothing on the net for re-doing the partitions on a 64gb. I looked for days
netchip mode not found
Hi!
I tried to debrick my Touchpad 32GB, but the script stops when waiting for netchip mode.
I also saw that the "Qfprom Fuse List: Blowing FAILED". Is this normal?
Code:
MSG: Qfprom Fuse List: Blowing FAILED
MSG: Failed Fuse addr:
MSG: 0x00000000
MSG: Error Status:
MSG: 0x00000000
I used a Ubuntu 12.04.
Any ideas that may bring life back to my Touchpad?
BR
Martin
mavogs said:
Hi!
I tried to debrick my Touchpad 32GB, but the script stops when waiting for netchip mode.
I also saw that the "Qfprom Fuse List: Blowing FAILED". Is this normal?
Code:
MSG: Qfprom Fuse List: Blowing FAILED
MSG: Failed Fuse addr:
MSG: 0x00000000
MSG: Error Status:
MSG: 0x00000000
I used a Ubuntu 12.04.
Any ideas that may bring life back to my Touchpad?
BR
Martin
Click to expand...
Click to collapse
No good news for that:
http://forum.xda-developers.com/showthread.php?t=2734057
shumash said:
No good news for that:
http://forum.xda-developers.com/showthread.php?t=2734057
Click to expand...
Click to collapse
Hmm, the error does not look simular to mine.
It does not stop at "open multi", but much later when waiting for the net chip mode.
here the last few lines I receive:
Code:
Sending CloseFlush...
Done writing files.
Reseting device...
Requesting Reset...
Waiting for fastboot mode...
Loading TPToolbox-Headless ...
sending 'bootmem' (13200 KB)...
OKAY [ 0.829s]
writing 'bootmem'...
OKAY [ 2.889s]
finished. total time: 3.730s
Waiting for netchip mode... (may take 3+ mins)
netchip mode not found
Aborted.
error when running
I am getting this error when running this:
[email protected]:~/Downloads/tpdebrick-v004$ sudo ./tpdebrick 32
checking doc files ...
could not find ../webosdoctorp305hstnhwifi.jar or ../webosdoctorp305hstnhatt.jar
Aborted
I do have this file, webosdoctorp305hstnhwifi.jar Where does it need to be placed so the script can find it? I have it in the same folder as the script. Any help would be appreciated. Thanks
Need webosdoctorp305hstnhwifi.jar file
jtornone said:
I am getting this error when running this:
[email protected]:~/Downloads/tpdebrick-v004$ sudo ./tpdebrick 32
checking doc files ...
could not find ../webosdoctorp305hstnhwifi.jar or ../webosdoctorp305hstnhatt.jar
Aborted
I do have this file, webosdoctorp305hstnhwifi.jar Where does it need to be placed so the script can find it? I have it in the same folder as the script. Any help would be appreciated. Thanks
Click to expand...
Click to collapse
Hi,
All the links to the WebOS doctor (webosdoctorp305hstnhwifi.jar) are dead. Can you please upload it somewhere and send me the link?
Thanks.
IbarJar said:
Hi,
All the links to the WebOS doctor (webosdoctorp305hstnhwifi.jar) are dead. Can you please upload it somewhere and send me the link?
Thanks.
Click to expand...
Click to collapse
https://www.dropbox.com/s/vpamv0m6che6cc2/webosdoctorp305hstnhwifi.jar?dl=0
Here you go.
jtornone said:
Here you go.
Click to expand...
Click to collapse
Thank you!
IbarJar said:
Thank you!
Click to expand...
Click to collapse
glad i could help.
One of my touchpads just bricked. I was running Lollipop 12.0 on it that had been installed via tptoolbox after removing Webos. I am attempting to use tpdebrick and Ubuntu keeps looking for ADB and fastboot. Any help would be greatly appreciated.
Help - Here is the scrip from running tpdebrick-v004 on my TP32:
Writing 1024 bytes to 0x2a027c00; 2180 bytes left.
Writing 1024 bytes to 0x2a028000; 1156 bytes left.
Writing 1024 bytes to 0x2a028400; 132 bytes left.
Writing 132 bytes to 0x2a028800; 0 bytes left.
Executing file...
Checking QDL mode...
Writing file tz.mbn ...
Sending MAGIC...
MSG: Qfprom Fuse List: Blowing FAILED
MSG: Failed Fuse addr:
MSG: 0x00000000
MSG: Error Status:
MSG: 0x00000000
Sending secureMode...
Sending openMulti ...
MSG: Open multi failed, unknown error
ERROR: Open multi failed, unknown error
Invalid openMulti response.
Cannot write file tz.mbn
Aborted.
Hello. Currently I'm using Pantech IRON(IM-A870L) and he is having a Error that is known as Hardbrick or QHSUSB_DLOAD.
Before he was having a critical error, he had some symptoms and I've made some modifications that may be non-secured.
Symptom: No mountable partitions. Unable to get through directories.
Because I had an access to the recovery I have made some partition command on terminal, but it seemed to do nothing.
And I installed Lewa OS (Similar to MIUI ?) and it just stopped at bootscreen(bootanimation) for a-lot-of minutes, so I just removed my battery.
Then he got that mode.
Fortunately the device has HEX and MBN files online and I used QPST to recover it. Also Unlimited IO's PblClear.
The conclusion is this:
First, PblClear doesn't work. I noticed that my device is not connected as eMMC, but Gobi Wireless or something.
Seconed, I connected and did a download for 5 days with QPST, and one day it just stopped.
Yes, It stopped. It is not like no received cookie(?) error or connection error. No error messages, no succeed message. It just stopped and no more mouse loading ico. It was not a problem with "Program not responding". I was able to click few buttons.
I was monitoring debug file (.dbg). It was real big file(20GB or more). And found it stopped and didn't proceeded after like this code.
Code:
Writing Address 0xBlaBla...
I'm quite confused but posted for additional discussion. I wish I have a extra recommnedations that may be a cure. Any recommendation will be appreciated.
I will be changing my board after some weeks, maybe, If my phone will be dead forever..:angel:
nkk71, here, was good enough to extract and upload the zip from the T-Mo US RUU.exe so that I could update my M7 to what is the latest and prolly last OEM RUU for the M7.
For whatever reason, I was failing when I tried myself under BootCamp W7 on my MBA.
Here's the link for same hosted by the good folks at Android File Manager.
And here's some info on how I flashed it with OSX Mavs running BC and W7.
One caveat here.
As far as I recall, one needs to already be on this version of the firmware to accomplish this feat.
That would mean you are already on 7.18.531.2 or thereabouts.
My M7 is rooted, unlocked and S-Off.
I'm just a user.
I make no promises. There may be extra steps here you don't need, but I am not a developer of any kind and the only code I know is Morse.
Proceed at your own risk.
there are no guarantees by me, or XDA, or nkk71, or the universe.
some of this will involve using a Windows browser of your choice.
I used Firefox and/or Chrome.
So many of the links via Windows connect to malware, porn, ads and other crap.
The back button worked most of the time, but there were occasions where I just had to quit and find another way.
YMMD.
Good Luck!
from within Bootcamp, download htc-fastboot.exe from here to bootcamp Downloads folder.
https://www.htcdev.com/process/legal_fastboot_win
conventional fast boot will not work with this update.
download USB drivers and adb from here to Downloads folder. 64b for Windows 7 and a modern Mac.
https://www.theandroidsoul.com/download-htc-one-m7-drivers-windows-usb-adb/
or here
https://basketbuild.com/filedl/devs?dev=squabbi&dl=squabbi/m7/toolkit/HTCOneToolkit-3.3+-+EoL.exe
or here
https://freeandroidroot.com/download-htc-usb-drivers/
download RUU 7.18.531.35.zip from here to Downloads folder. This is the RUU.zip that was extracted by nkk71.
Its' sources is 7.18.531.35.exe from HTC web page.
The result is RUU 7.18.531.35.zip which one should save a copy of and rename for ease of use. RUU.zip works well.
Plug in M7 via USB.
It should show up when connected which indicates your drivers are good.
You can also check your M7 drivers by opening a command window inside the folder where your RUU.zip is saved.
Shift-right click on Downloads folder where adb, htc_fastboot and RUU.zip are located.
In the resulting Command window Enter: adb devices
which should return the serial number of your M7
If it doesn't. Enter: adb kill-server
Then unplug your M7, wait a few and replug the USB.
Try: adb devices :again
If that works:
In the Command window Enter: adb reboot-bootloader
you should now be in fastboot USB on the phone.
Now enter:
fastboot devices
You should see the serial of your M7.
Now enter:
fastboot reboot
Unplug the M7 briefly.
Replug and wait for BootCamp to recognize again. A couple minutes depending on your Mac and OS.
Open your Downloads folder in Bootcamp.
On the left sidebar of folders, drives, etc., Shift click the Downloads folder and select "open command window here". This step is very important and will prevent your from tearing your hair out.
In the resulting Command window Enter: adb devices
see your device serial as before.
Enter: htc_fastboot oem rebootRUU
you should see the gunmetal colored screen with the HTC logo on it.
Enter: htc_fastboot flash zip RUUM7v35.zip
you should see ......... the green progress bar
the 1st pass of the process took my 2013 MBA (running BC) just shy of 7 mins.
then the green progress bar stalls about 3/4 thru on the M7.
Don't fret. That's normal (who knows why). There may be and error at the end, or there may not. Very exacting science here.
again Enter: htc_fastboot flash zip RUUM7v35.zip
The 2nd pass took about 5 mins before it stalled about 3/4 again.
perhaps I was impatient waiting for a restart as some places have indicated the M7 should do.
Instead I typed: fastboot reboot.
After a minute, the process of "updating Android" begins on the M7.
Depending, it might take 5-10 mins to complete.
Other reading:
https://www.htcdev.com/devcenter/opensense-sdk/download-install/android-quickguides/
any questions or concerns, feel free to post here and I'll do my best.
I'm just a user. There may be extra steps here you don't need, but I am not a developer of any kind and the only code I know is Morse.
I make no promises.
Proceed at your own risk.
there are no guarantees by me, or XDA, or nkk71, or the universe.
My M7 is quite stable after this update.
Thanks nkk71 and AFH.
Not for Windows users?
Hi, I want to know if there's a topic with the installation process for Windows users... I've got the .zip on my phone but the twrp does not install it so I'm trying from my laptop using the steps you described but I've got the following error on the command window:
target reported max download size of 1514139648 bytes
Invalid sparse file format at header magi
error: write_sparse_skip_chunk: don't care size 101322718 is not a multiple of t
he block size 4096
sending sparse 'zip' (1478648 KB)...
error: write_sparse_skip_chunk: don't care size 101322718 is not a multiple of t
he block size 4096
error: write_sparse_skip_chunk: don't care size 101322718 is not a multiple of t
he block size 4096
OKAY [ 82.711s]
writing 'zip'...
(bootloader) zip header checking...
FAILED (remote: 32 header error)
finished. total time: 82.899s
How can You Help me?
this thread should get you too some answers or help from others. dunno windows.
Good Luck!
download the file but when you unzip it, it says that there are damaged files, some can upload it to another platform or pass it to the email [email protected]