Related
I think i may have bricked my nexus 10.. I was trying to install the chainfire3d application from the market, and when it rebooted, it wouldnt go past the X logo. waited for a long time, so i tried a hard reset, and still nothing. So i figured i would try using the toolkit to help fix. tried to relock, flash, and re-unlock, and it wouldnt work..after the step where you go into factory reset/wipe, it woudlnt go further. I cant get a custom recovery to install, it wont save the file. tried doing that step separately, and it seems to stick on sending the file over. this seems to be a common issue with anything i try.
The screen says:
"sending TWRP touch recovery..
sending 'recovery' (7246 KB) ...
and is just stuck there. this seems to happen in several places, with a few different things ive tried. When trying to flash the stock image, it will get stuck in similar places, perhaps not with the recovery step, but with a portion of the stock image. Been at this for a couple of hours... any help would be greatly appreciated!.
Also, as of now... it wont boot past the google logo. I can get it into fastboot by holding down the buttons, and I can get it into the stock recovery, but thats it. I don't even think adb is detecting the device. I have a feeling that may be a major roadblock to getting this thing fixed. Does anyone know how I can get the tablet to be detected by adb if i cant even get past the google logo screen at boot?
Update 1:
Still cant unbrick my device. any time i try to transfer or flash files to it... it stalls, and if i disconnect the device, i get this error:
FAILED (data transfer failure (too many links)).
Your Device will now boot into Android and detect ADB mode.
problem is, it doesnt reboot, and even if it did, it wouldnt be able to boot into android, since it wont go past the google logo when the device turns on. in fact, i cant even turn it off. only way to turn it off would be to wait for the battery to drain.
If this helps, here is what it says on the fastboot screen:
Device Information
Product Name: manta
Variant: wifi
H/W version : 8
Bootloader Version: MANTALJ12
Carrier Info: none
Serial Number: *********** (not going to publish that, lol)
LOCK STATE: Unlocked
Reboot Mode Flag: none.
anyone have any ideas at all how I can salvage this thing? Im kindof embarrassed honestly. Ive had 5 android devices prior to this one, and have rooted, flashed, and reflashed each of them countless times, and never, ever ran into this before. I could really use the help.
Quick note:
I just noticed that when i try to flash anything to the tablet, the following appears under the rest of the info i listed above.
FASTBOOT STATUS - DATA00713800 (this text is highlighted in light blue)
Update 2:
ok, so i tried to do the factory restore, and am running into the same wall as always. here is the text from the window, perhaps that may clue you into the problem:
7-Zip (A) 9.20 Copyright (c) 1999-2010 Igor Pavlov 2010-11-18
Processing archive: put_google_factory_image_here\mantaray-jop40c-factory-0d641789.tg
z
Extracting mantaray-jop40c-factory-0d641789.tar
Everything is Ok
Size: 329369600
Compressed: 326396069
Now extracting flashable Images
7-Zip (A) 9.20 Copyright (c) 1999-2010 Igor Pavlov 2010-11-18
Processing archive: put_google_factory_image_here\mantaray-jop40c-factory-0d641789.ta
r
Extracting mantaray-jop40c
Extracting mantaray-jop40c\image-mantaray-jop40c.zip
Extracting mantaray-jop40c\flash-base.sh
Extracting mantaray-jop40c\bootloader-manta-mantalj12.img
Extracting mantaray-jop40c\flash-all.sh
Extracting mantaray-jop40c\flash-all.bat
Everything is Ok
Folders: 1
Files: 5
Size: 329358105
Compressed: 329369600
Factory Images extracted. Starting Flash Process.
Now Flashing Bootloader Image..
sending 'bootloader' (1280 KB)... OKAY [ 0.232s]
writing 'bootloader'... OKAY [ 0.113s]
finished. total time: 0.345s
rebooting into bootloader... OKAY [ 0.001s]
finished. total time: 0.001s
Now Flashing Factory Image: Boot, Cache, Recovery, System and Userdata..
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: MANTALJ12
Baseband Version.....: no modem
Serial Number........: R32CB01KDWW
--------------------------------------------
checking product... OKAY [ 0.001s]
checking version-bootloader... OKAY [ 0.002s]
sending 'boot' (4606 KB)...
Its just stuck on that last part, sending 'boot' (4606 KB)...
and under all the info on the fastboot page, the following appeared while this was happening:
FASTBOOT STATUS - DATA0047f800 (this line is highlighted in light blue)
*Bump* That's really unfortunate. I managed to fixed my soft brick after unlocking and flashing TWRP with a factory image. There was no highlighted blue text, everything went smooth. I hope your issue get fixed
P.S. I did not use the toolkit. If you can boot to your bootloader (fastboot), try running the shell/batch scripts included with the factory image? (This is just following Google's instruction on the factory image download page)
cuguy said:
*Bump* That's really unfortunate. I managed to fixed my soft brick after unlocking and flashing TWRP with a factory image. There was no highlighted blue text, everything went smooth. I hope your issue get fixed
P.S. I did not use the toolkit. If you can boot to your bootloader (fastboot), try running the shell/batch scripts included with the factory image? (This is just following Google's instruction on the factory image download page)
Click to expand...
Click to collapse
can you link it?
cuguy said:
*Bump* That's really unfortunate. I managed to fixed my soft brick after unlocking and flashing TWRP with a factory image. There was no highlighted blue text, everything went smooth. I hope your issue get fixed
P.S. I did not use the toolkit. If you can boot to your bootloader (fastboot), try running the shell/batch scripts included with the factory image? (This is just following Google's instruction on the factory image download page)
Click to expand...
Click to collapse
trying that....
so far so good... dont want to get my hopes up though... below is what ive got so far in the cmd screen:
sending 'bootloader' (1280 KB)...
OKAY [ 0.162s]
writing 'bootloader'...
OKAY [ 0.125s]
finished. total time: 0.288s
rebooting into bootloader...
OKAY [ 0.002s]
finished. total time: 0.003s
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: MANTALJ12
Baseband Version.....: no modem
Serial Number........: R32CB01KDWW
--------------------------------------------
checking product...
OKAY [ 0.001s]
checking version-bootloader...
OKAY [ 0.002s]
sending 'boot' (4606 KB)...
OKAY [ 32.528s]
writing 'boot'...
OKAY [ 0.116s]
sending 'recovery' (5106 KB)...
OKAY [ 56.840s]
writing 'recovery'...
OKAY [ 0.119s]
sending 'system' (528847 KB)...
Its been about 30 minutes now... and its still stuck on "sending 'system' (528847 KB)..." in the cmd window.... not sure what that means... it did take about a minute for the recovery to get sent over, and its about 100x larger in size, so i guess i will leave it connected like this for the next hour or so... and hope that it is just going REALLY slowly. Got my fingers crossed...
Battery died while waiting.... this is the complete text of the CMD screen while i was waiting.. forgot that it doesnt charge while in fastboot. got it plugged into an outlet for faster charging while its off.... hopefully when its charged up, i can try again and ill continue to progress
sending 'bootloader' (1280 KB)...
OKAY [ 0.162s]
writing 'bootloader'...
OKAY [ 0.125s]
finished. total time: 0.288s
rebooting into bootloader...
OKAY [ 0.002s]
finished. total time: 0.003s
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: MANTALJ12
Baseband Version.....: no modem
Serial Number........: R32CB01KDWW
--------------------------------------------
checking product...
OKAY [ 0.001s]
checking version-bootloader...
OKAY [ 0.002s]
sending 'boot' (4606 KB)...
OKAY [ 32.528s]
writing 'boot'...
OKAY [ 0.116s]
sending 'recovery' (5106 KB)...
OKAY [ 56.840s]
writing 'recovery'...
OKAY [ 0.119s]
sending 'system' (528847 KB)...
FAILED (data transfer failure (Too many links))
finished. total time: 3941.094s
Press any key to exit...
Did you try to run e2fsck on all partitions (boot, system, userdata) and check whether there are any errors?
You can run it via adb once you boot into TWRP or CWM recovery. Here is more info:
http://forum.xda-developers.com/showthread.php?p=34923662
Ps.
I also bricked my nexus 10 while transferring files on it in windows. Nothing so far helped me. e2fsck doesn't see any partitions
I believe this is something to-do with a corrupted flash memory. Your case looks about the same.
jodvova said:
Did you try to run e2fsck on all partitions (boot, system, userdata) and check whether there are any errors?
You can run it via adb once you boot into TWRP or CWM recovery. Here is more info:
http://forum.xda-developers.com/showthread.php?p=34923662
Ps.
I also bricked my nexus 10 while transferring files on it in windows. Nothing so far helped me. e2fsck doesn't see any partitions
I believe this is something to-do with a corrupted flash memory. Your case looks about the same.
Click to expand...
Click to collapse
I cant get it to load a custom recovery! any advice on how to get that going?
ltracte said:
I cant get it to load a custom recovery! any advice on how to get that going?
Click to expand...
Click to collapse
So, if you run "fastboot boot twrp-image.img" under your current bootloader it doesn't boot it?
Also, If I remember it correctly, you can also boot in to a existing recovery and then run shell commands via adb.
ltracte said:
I cant get it to load a custom recovery! any advice on how to get that going?
Click to expand...
Click to collapse
Dumb question, if using a desktop PC are you using the front or rear USB ports? I had a similar issue where it would just get stuck on the "sending system" message. Switched the USB from front port to back port on my linux box and it solved my problem.
Sent from my Nexus 10 using Tapatalk 2
jodvova said:
So, if you run "fastboot boot twrp-image.img" under your current bootloader it doesn't boot it?
Also, If I remember it correctly, you can also boot in to a existing recovery and then run shell commands via adb.
Click to expand...
Click to collapse
i got twrp to load that way! thanks... what now? i cant get the device to mount so i can put the zip file of a rom on there.
ltracte said:
i got twrp to load that way! thanks... what now? i cant get the device to mount so i can put the zip file of a rom on there.
Click to expand...
Click to collapse
What I meant was, you can now run e2fsck and check all partitions for consistency. Refer to a thread that I posted a few comments back. You can run e2fsck either via a terminal session in TWRP or via adb shell.
jodvova said:
What I meant was, you can now run e2fsck and check all partitions for consistency. Refer to a thread that I posted a few comments back. You can run e2fsck either via a terminal session in TWRP or via adb shell.
Click to expand...
Click to collapse
couldnt get the command to work via adb, so i tried it using terminal inside TWRP, and this what it spit back at me:
/dev/block/platform/dw_mmc.0/by-name/system: clean. 11/51296 files. 6651/204800 blocks
i have no idea what that means, nor what else to do....
Fixed it!!!!
ltracte said:
Fixed it!!!!
Click to expand...
Click to collapse
Glad you fixed your problem. Please post any relevant information that may help people in the same situation.
Mark.
mskip said:
Glad you fixed your problem. Please post any relevant information that may help people in the same situation.
Mark.
Click to expand...
Click to collapse
well.. i loaded it into the bootloader, unzipped the factory image, and everything inside it into the platform-tools folder in my android sdk directory on my pc so i could use ADB
then i did the following via adb
fastboot flash bootloader bootloader-manta-mantalj12.img
fastboot reboot-bootloader
fastboot -w update image-mantaray-jop40c.zip.
the first time it got stuck pushing the system.img file, i let it run for almost an hour before giving up. then the battery on the tablet died. let it charge for about an hour, plugged it back in, reran the last command from above, and for some reason, the whole thing went through without a hitch. wish i could explain why it worked that time, but I cant. hope this helps someone else that encountered the issue.
thanks again to everyone that offered any input!
Whew! So glad you finally had success & thanks for sharing. I'm reading up, research, etc. I received my N10 yesterday. I'm getting ready to unlock/root today.
Sent from my Nexus 7 using Tapatalk 2
ltracte said:
well.. i loaded it into the bootloader, unzipped the factory image, and everything inside it into the platform-tools folder in my android sdk directory on my pc so i could use ADB
then i did the following via adb
fastboot flash bootloader bootloader-manta-mantalj12.img
fastboot reboot-bootloader
fastboot -w update image-mantaray-jop40c.zip.
the first time it got stuck pushing the system.img file, i let it run for almost an hour before giving up. then the battery on the tablet died. let it charge for about an hour, plugged it back in, reran the last command from above, and for some reason, the whole thing went through without a hitch. wish i could explain why it worked that time, but I cant. hope this helps someone else that encountered the issue.
thanks again to everyone that offered any input!
Click to expand...
Click to collapse
Hmm, did you try the flash-all.bat file that comes with the factory image? It does those 3 commands, + erases all partitions automatically.
ltracte said:
well.. i loaded it into the bootloader, unzipped the factory image, and everything inside it into the platform-tools folder in my android sdk directory on my pc so i could use ADB
then i did the following via adb
fastboot flash bootloader bootloader-manta-mantalj12.img
fastboot reboot-bootloader
fastboot -w update image-mantaray-jop40c.zip.
the first time it got stuck pushing the system.img file, i let it run for almost an hour before giving up. then the battery on the tablet died. let it charge for about an hour, plugged it back in, reran the last command from above, and for some reason, the whole thing went through without a hitch. wish i could explain why it worked that time, but I cant. hope this helps someone else that encountered the issue.
thanks again to everyone that offered any input!
Click to expand...
Click to collapse
That's exactly what I did. Just followed the factory image flashing instruction on google's page(where you download the image file for N10). Did you figure out why it wassnt able to transfer the first time?
Alright Ladies and Gentlemen.
Background: (skip if you don't think it's relevant)
I just bought a xt907 with the latest OTA.
I wanted root, however after looking into it, I read that the bootloader was forever locked from the new OTA.
But, me being as stubborn as I am, and always have had a rooted phone, I tried anyways, and with my surprise, somehow, I actually achieved root using motochopper after only clearing the dalvik cache and trying it for shiggles.
No backups.
Even though I couldn't flash a new recovery or a full rom without safestap, I just decided to mod the stock rom.
Installed pimp my rom, es file explorer, some app uninstallers for bloatware (no i didn't uninstall any COM files or important things), etc etc.
Then I Installed a font, didn't like it, went to try a few others.
NOW.
After installing a font and rebooting, I was stuck at the droid boot logo with the red eye and sparks flying about.
I booted into stock recovery, cleared the cache. Nothing. Reset to factory defaults. Nothing.
I was still stuck on the boot logo.
Now, the dumb part of my actions.
I downloaded matt's utility 1.20. I tried option 1, Which failed. So I tried option 2, flashing the recovery. Which was "successful".
Tried option 1 again, it keeps saying
Code:
sending 'system' (30720 KB)...
OKAY [ 2.318s]
writing 'system'...
OKAY [ 2.798s]
sending 'system' (30720 KB)...
OKAY [ 6.569s]
writing 'system'...
OKAY [ 1.358s]
Over and over again.
Now I can not boot the phone. AP Fastboot comes up.
Code:
AP Fastboot Flash Mode
(blah)
Device is LOCKED. Code 0.
No Valid PIV block in SP for system.
PIV validation failed (system)
Fastboot reason: Flash Failure
Same thing comes up when I try to go into recovery. Every time I turn on the phone, this comes up.
I tried RSD Lite, to flash the old rom back on, it keeps failing. I keep trying to flash VZW_XT907_4.1.2-9.8.1Q-66_1FF
With no avail.
So, Anyone who can help me, I would be forever grateful. Thanks.
cheno1115 said:
Alright Ladies and Gentlemen.
Background: (skip if you don't think it's relevant)
I just bought a xt907 with the latest OTA.
I wanted root, however after looking into it, I read that the bootloader was forever locked from the new OTA.
But, me being as stubborn as I am, and always have had a rooted phone, I tried anyways, and with my surprise, somehow, I actually achieved root using motochopper after only clearing the dalvik cache and trying it for shiggles.
No backups.
Even though I couldn't flash a new recovery or a full rom without safestap, I just decided to mod the stock rom.
Installed pimp my rom, es file explorer, some app uninstallers for bloatware (no i didn't uninstall any COM files or important things), etc etc.
Then I Installed a font, didn't like it, went to try a few others.
NOW.
After installing a font and rebooting, I was stuck at the droid boot logo with the red eye and sparks flying about.
I booted into stock recovery, cleared the cache. Nothing. Reset to factory defaults. Nothing.
I was still stuck on the boot logo.
Now, the dumb part of my actions.
I downloaded matt's utility 1.20. I tried option 1, Which failed. So I tried option 2, flashing the recovery. Which was "successful".
Tried option 1 again, it keeps saying
Code:
sending 'system' (30720 KB)...
OKAY [ 2.318s]
writing 'system'...
OKAY [ 2.798s]
sending 'system' (30720 KB)...
OKAY [ 6.569s]
writing 'system'...
OKAY [ 1.358s]
Over and over again.
Now I can not boot the phone. AP Fastboot comes up.
Code:
AP Fastboot Flash Mode
(blah)
Device is LOCKED. Code 0.
No Valid PIV block in SP for system.
PIV validation failed (system)
Fastboot reason: Flash Failure
Same thing comes up when I try to go into recovery. Every time I turn on the phone, this comes up.
I tried RSD Lite, to flash the old rom back on, it keeps failing. I keep trying to flash VZW_XT907_4.1.2-9.8.1Q-66_1FF
With no avail.
So, Anyone who can help me, I would be forever grateful. Thanks.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2379833
you have this as a sure thing.
I have wondered if my restore method would work on a locked BL phone. Scroll down to near the bottom and I comment on the possibility of getting custom recovery and then root? Impossible! But you are borked already..... My wife won't let me try it on her updated & locked M.
http://forum.xda-developers.com/showthread.php?t=2391641
aviwdoowks said:
http://forum.xda-developers.com/showthread.php?t=2379833
you have this as a sure thing.
I have wondered if my restore method would work on a locked BL phone. Scroll down to near the bottom and I comment on the possibility of getting custom recovery and then root? Impossible! But you are borked already..... My wife won't let me try it on her updated & locked M.
http://forum.xda-developers.com/showthread.php?t=2391641
Click to expand...
Click to collapse
I did try that and that is how I obtained root. Didn't have a problem up until now.
Anyways, I managed to fix my issue on my own.
Long story short, RSD Lite was flashing the VZW_XT907_4.1.2-9.8.1Q-66_1FF I downloaded from droid-developers.
My phone kept rejecting the tz.mbn saying it was invalid.
Sooooo, I searched for a 98.18.78 OTA pull and I found one.
This is the one for reference.
I swapped the tz.mbn files between the two folders and it flashed it without a problem. Phone booted up as if I just unboxed it.
So, I won't delete this just as a reference for anyone who has the same problems as me.
Sorry for taking anyone's time.
cheno1115 said:
....QUOTE]
I am curious, that link is the prev OTA.
Even then could you share how an ota useful in RSD?
"I swapped the tz.mbn files between the two folders and it flashed it without a problem. Phone booted up as if I just unboxed it."
You got the file from the old OTA?
Click to expand...
Click to collapse
aviwdoowks said:
cheno1115 said:
....QUOTE]
I am curious, that link is the prev OTA.
Even then could you share how an ota useful in RSD?
"I swapped the tz.mbn files between the two folders and it flashed it without a problem. Phone booted up as if I just unboxed it."
You got the file from the old OTA?
Click to expand...
Click to collapse
Yes, I just went in my phone settings and did realize this is a previous OTA. I checked for updates and my phone wants me to update to 98.18.78.
I am curious, that link is the prev OTA.
Even then could you share how an ota useful in RSD?
Click to expand...
Click to collapse
Well, Pretty much, my phone had no rom at the time. I ruined it by trying to flash stuff.
So I downloaded the bottom rom from
sbf.droid-developers.org/scorpion_mini_xt907/list.php
and was trying to flash it onto my phone. My phone kept rejecting the tz.mbn file, it said it was invalid. So I found that old OTA and swapped the two files, and to my surprise, my phone accepted that file. I don't know why it wouldn't take the original one.
Anyways, I'm updating my phone to OTA 98.18.78 right now, so all is good.
Click to expand...
Click to collapse
Samuri HL Downgrade Tool
cheno1115 said:
Alright Ladies and Gentlemen.
Background: (skip if you don't think it's relevant)
I just bought a xt907 with the latest OTA.
I wanted root, however after looking into it, I read that the bootloader was forever locked from the new OTA.
But, me being as stubborn as I am, and always have had a rooted phone, I tried anyways, and with my surprise, somehow, I actually achieved root using motochopper after only clearing the dalvik cache and trying it for shiggles.
No backups.
Even though I couldn't flash a new recovery or a full rom without safestap, I just decided to mod the stock rom.
Installed pimp my rom, es file explorer, some app uninstallers for bloatware (no i didn't uninstall any COM files or important things), etc etc.
Then I Installed a font, didn't like it, went to try a few others.
NOW.
After installing a font and rebooting, I was stuck at the droid boot logo with the red eye and sparks flying about.
I booted into stock recovery, cleared the cache. Nothing. Reset to factory defaults. Nothing.
I was still stuck on the boot logo.
Now, the dumb part of my actions.
I downloaded matt's utility 1.20. I tried option 1, Which failed. So I tried option 2, flashing the recovery. Which was "successful".
Tried option 1 again, it keeps saying
Code:
sending 'system' (30720 KB)...
OKAY [ 2.318s]
writing 'system'...
OKAY [ 2.798s]
sending 'system' (30720 KB)...
OKAY [ 6.569s]
writing 'system'...
OKAY [ 1.358s]
Over and over again.
Now I can not boot the phone. AP Fastboot comes up.
Code:
AP Fastboot Flash Mode
(blah)
Device is LOCKED. Code 0.
No Valid PIV block in SP for system.
PIV validation failed (system)
Fastboot reason: Flash Failure
Same thing comes up when I try to go into recovery. Every time I turn on the phone, this comes up.
I tried RSD Lite, to flash the old rom back on, it keeps failing. I keep trying to flash VZW_XT907_4.1.2-9.8.1Q-66_1FF
With no avail.
So, Anyone who can help me, I would be forever grateful. Thanks.
Click to expand...
Click to collapse
I lost root after the OTA update. Inused SamuriHL Downgrade tool to roll back to the stae my phone was in before update. then it gives instructions on how to retore and keep root. then yuo tkae the update again.
THANK YOU
I thought I was doomed to a bricked phone. This fix saved me.
Important to note for any other poor suckers who find themselves in the same spot - make sure you have an updated version of RSD Lite when you do this. My first (15) attempt(s) failed flashing system.img because I was running an old version of RSD Lite, but when I updated to 6.1.4 it worked fine.
cheno1115, THANK YOU!
I had the same issue with my xt907 after rooting with "DROID_RAZR_M_Utility_1.20" and after restoring my apps (including with framework mods.. stupid, I know) from xt890 via nandroid manager.
I thought oh my god, that is an expensive brick I have now.
I have just reflashed "VZW_XT907_4.1.2-9.8.1Q-66_1FF.xml.zip" via RSD (with "tz.mbn" file raplaced from "Blur_Version.98.16.1.XT907.Verizon.en.US.zip") and it did boot up, however it booted with all my "restored" apps. The problem is that I have tried to restore my home screen via nandroid backup manager and it failed, so I got only upper status bar, soft buttons and black screen... I'm lucky that Motorola placed a settings shortcut on upper drawer, so I was able to navigate to settings and do a factory reset. So this is how I got a fresh start again.
However if I launch "DROID_RAZR_M_Utility_1.20" with option 1 again, I get the same thing - many repeating "sending system.img", have to terminate it and then - a brick. So I had to repeat RSD reflash procedure once more. BTW flashing of "system.img" takes surprisingly long, like 5 minutes or so.
So that got me thinking... Isn't this repeating "sending system" and "writing system" just doing it in pieces and one should wait?
Anyway that has solved my problem. THANKS!
Does this mean you fully rooted your XT907 that had the latest OTA updates? Can you install other ROM's?
As far as I know, once you get the latest OTA update you're screwed and can't do anything.
I have a locked xt907
nifty101 said:
Does this mean you fully rooted your XT907 that had the latest OTA updates? Can you install other ROM's?
As far as I know, once you get the latest OTA update you're screwed and can't do anything.
I have a locked xt907
Click to expand...
Click to collapse
We have SafeRoot now. See the general section.
No custom roms though.
See my xt907 stuff
Can you send me a link to each the general section and your XT907 stuff? Not sure where or what you are referencing. Thanks so much.
nifty101 said:
Can you send me a link to each the general section and your XT907 stuff? Not sure where or what you are referencing. Thanks so much.
Click to expand...
Click to collapse
You are on tapatalk or xda app?
Go here & take your punishment. Lol.
http://forum.xda-developers.com/showthread.php?t=2610531
Links
http://forum.xda-developers.com/showpost.php?p=45548210&postcount=3
SamuriHL has fix for "cannot load system img"
http://www.droidrzr.com/index.php/topic/37658-green-robot-after-using-house-of-moto/#entry400767
No valid piv
Mr hello I have this problem with no valid PIV on my motorola RARZ M can you help me?
Hi,
Just randomly after I ran my battery completely out one time on my nexus 10, I wasn't able to start the nexus 10. The only thing that happened was that it showed me the Google logo, and then the X-symbol. After that, it restarted itself over and over. In other words, it just entered a bootloop. After a while it stopped showing the X-symbol, and only the Google logo. So I wasn't able to start it at all. The only thing I was able to, was to enter the bootloader menu. But from there, I wasn't able to enter recovery mode or something like that, it just entered the bootloop with the Google logo.
When this happened, I had never tried to root it or something like that.
But then I decided I wanted to flash it back to stock with fastboot, to hopefully solve the bootloop issue. Then I followed this guide: nexus10root.com/nexus-10-unroot/how-to-unrootunbrick-nexus-10-factory-firmware/
However, when I tried to write ./fastboot-mac flash bootloader bootloader-XXX.img, I got the following error:
"writing 'bootloader'... FAILED (remote: partition table update fail!)"
Then I read some place that I could try to run several erase-command before I tried the previously mentioned command. After that, I am now not able to enter the bootloader menu any longer. The device will not turn on. The only way to get anything on the screen, is by plugging in the USB-cable and then it shows the loading-symbol. To summarize, I am not able to start my nexus 10 and I am not able to enter the bootloader menu.
Any suggestions for how I can try to solve this issue? Any help will be much appreciated
Update: Now I am able to get into bootloader/fastboot mode again. However, still get this when trying to flash:
sending 'bootloader' (1280 KB)... OKAY
writing 'bootloader'... FAILED (remote: partition table update fail!)
This really drives me crazy. Hope some of you have any suggestions
You have a solution?
IBalic said:
Update: Now I am able to get into bootloader/fastboot mode again. However, still get this when trying to flash:
sending 'bootloader' (1280 KB)... OKAY
writing 'bootloader'... FAILED (remote: partition table update fail!)
This really drives me crazy. Hope some of you have any suggestions
Click to expand...
Click to collapse
Hello find some solution? I have same problem:crying:
---------- Post added at 11:35 AM ---------- Previous post was at 10:44 AM ----------
I had this Problem, when i want to restore to Android 4.4.2 (KOT49H) Factory -> With command "flash-all.bat"
So i tryd to install an older Version, first to Android 4.2.2 (JDQ39) -> That's work! so i had again a working Android.
After i overwrite with newer version 4.4 and finaly overwrite again with 4.4.2. So that way works. (Maybe you dont need to install 4.4 fist, i dont try it.) :good::laugh:
My Razr M is in a state where all I can do is boot into fastboot. I was trying to fastboot back to stock Jellybean by using Matts Utility 1.20. I received the following when the utility ran:
[*] Simple Razr Restore
[*] Windows Version
[*] Created by mattlgroff
[*]
[*] Before continuing, ensure your Razr is in the
[*] "AP Fastboot" mode and connected via USB.
[*] WARNING: Do not do this at LOW BATTERY! You have been warned!
[*]
[*] Press any key to continue.
sending 'mbm' (512 KB)... OKAY [ 0.063s]
writing 'mbm'... INFOInvalid partition name mbm
FAILED (remote failure)
rebooting into bootloader... OKAY [ 0.008s]
< waiting for device >
sending 'mbmloader' (42 KB)... OKAY [ 0.011s]
writing 'mbmloader'... INFOInvalid partition name mbmloader
FAILED (remote failure)
sending 'mbm' (512 KB)... OKAY [ 0.056s]
writing 'mbm'... INFOInvalid partition name mbm
FAILED (remote failure)
rebooting into bootloader... OKAY [ 0.008s]
< waiting for device >
erasing 'cache'... OKAY [ 12.865s]
sending 'logo.bin' (854 KB)... OKAY [ 0.102s]
writing 'logo.bin'... INFOInvalid partition name logo.bin
FAILED (remote failure)
sending 'devtree' (512 KB)... OKAY [ 0.069s]
writing 'devtree'... OKAY [ 0.325s
Everything fails?????? My phone screen says the following.
AP Fastboot Flash Mode (S)
10.9B(#) (sha-1e9f557, 2013-02-22 09:18:22)
eMMC Info: Size 8GB
Device is UNLOCKED. Status Code:3
Battery OK
Transfer Mode:
USB Connected
Fastboot Reason: Flash Failure
usb connected
When I reboot the phone whether connected usb or not it comes back to the fastboot screen and says Flash Failure! Any Ideas of what I can do? I have a factory cable and have tried it as well as standard USB cable. I tried booting into recovery and once I press volume up, it sticks on my bootlogo and will not go into recovery?
Update: I am a complete retard and was using the wrong Utility. WOW rookie mistake. Sorry. Using the Utility for XT912 not XT907
Well, hopefully using this utility didn't mess with your bootloader. If it did, you might be out of luck. Either way, if you have a locked bootloader and you're on the latest update, you shouldn't use Matt's utility 1.20 for the M. It has the older update in it. To restore, you'll need to get the FXZ from Droid Developer's SBF and make sure you know what you're flashing, prior to flashing it.
RikRong said:
Well, hopefully using this utility didn't mess with your bootloader. If it did, you might be out of luck. Either way, if you have a locked bootloader and you're on the latest update, you shouldn't use Matt's utility 1.20 for the M. It has the older update in it. To restore, you'll need to get the FXZ from Droid Developer's SBF and make sure you know what you're flashing, prior to flashing it.
Click to expand...
Click to collapse
Thanks for the reply. I was not on the latest update and I am Unlocked. I restored with Matts Utility (the correct one this time) and flash was successful. However when I get to start up screen to select language. The screen is not responsive. I press the power button and Power off shows up but it to is not responsive to touch either. The only way I can reboot is to hold power and volume down. Any Ideas?
evocop said:
Thanks for the reply. I was not on the latest update and I am Unlocked. I restored with Matts Utility (the correct one this time) and flash was successful. However when I get to start up screen to select language. The screen is not responsive. I press the power button and Power off shows up but it to is not responsive to touch either. The only way I can reboot is to hold power and volume down. Any Ideas?
Click to expand...
Click to collapse
Okay glad you got it. The non-responsive screen makes it seem like you might have flashed the files for the wrong phone. Is it possible you used the Razr HD utility? Since the processors are the same, people have been able to get the phone to boot but they get a non-responsive screen like what you're running into.
RikRong said:
Okay glad you got it. The non-responsive screen makes it seem like you might have flashed the files for the wrong phone. Is it possible you used the Razr HD utility? Since the processors are the same, people have been able to get the phone to boot but they get a non-responsive screen like what you're running into.
Click to expand...
Click to collapse
I downloaded the VZW_XT907_4.1.2-9.8 blah blah blah FXZ. I flashed this time using RSDLite. Flash was successful, and then at the select language screen, same issue. It is unresponsive to touch. Am I screwed?
I have gone into recovery and done factory reset, wipe cache, rebooted and still nothing. Perfectly good phone prior to my screw up of using the wrong utility. Gonna be heartbroken if it is done. Bootloader still shows unlocked. Just doesn't make sense.
evocop said:
I downloaded the VZW_XT907_4.1.2-9.8 blah blah blah FXZ. I flashed this time using RSDLite. Flash was successful, and then at the select language screen, same issue. It is unresponsive to touch. Am I screwed?
I have gone into recovery and done factory reset, wipe cache, rebooted and still nothing. Perfectly good phone prior to my screw up of using the wrong utility. Gonna be heartbroken if it is done. Bootloader still shows unlocked. Just doesn't make sense.
Click to expand...
Click to collapse
Hmmm, I'm lost on this one. Hopefully, someone with more experience will chime in. I would try one more thing, though. Find a stock ROM on here or on DroidRzr and try flashing it in recovery and see if that gets you anywhere.
RikRong said:
Hmmm, I'm lost on this one. Hopefully, someone with more experience will chime in. I would try one more thing, though. Find a stock ROM on here or on DroidRzr and try flashing it in recovery and see if that gets you anywhere.
Click to expand...
Click to collapse
Well I downloaded Deadcalm rom and flashed. Booted to language screen and screen is unresponsive still. Is it done for?
A dmesg might be useful.
Maybe you could try flashing a non-stock based ROM (CM, Carbon, etc) and see if overwriting the boot.img with something completely non-stock might fix it...
It sounds like a driver (boot.img) issue, but that should be fixed with a simple reflash of a correct RSD XML...
EDIT: I really don't think you're done for, since we are booting the OS. May need some... Advanced fixing though
Sent from my Nexus 7 using Tapatalk 4
I have searched the forum, but nothing could help me.
I have Pure Nexus installed on my 6P, running great for months. Suddenly today it rebooted while I was using it and sticking in a bootloop. "No problem", I thought, and wanted to reboot into recovery - but nope, can't access it anymore. So I tried to reflash the recovery when I got home, but I only get errorors
target didn't report max-download-size
sending 'recovery' (13133 KB)...
FAILED (command write failed (Unknown error))
finished. total time: 0.000s
When using the command adb devices the line just stays blank.
Everything is working fine with my Nexus 7, I have tried probably all the drivers out there, nothing is helping.
Can somebody help me fix the problem? Or at least somehow save my data? I could RMA my device, but I have no recent backup and would lose a lot of personal information.