Related
So last night my phone was acting up and i for some reason thought it would be a brilliant idea to wipe the cache in clockworkmod recovery, well the battery died midway when it was wiping the cache, and now I receive an infinite boot loop. Also when i go into fastboot on the phone i receive this message "e: can't mount /cache/recovery/log" I was reading on another thread and was thinking my partitions were deleted? I'm honestly not sure what's wrong or if i've bricked my phone beyond repair. Any help would be greatly appreciated!
cvrkickercomp said:
So last night my phone was acting up and i for some reason thought it would be a brilliant idea to wipe the cache in clockworkmod recovery, well the battery died midway when it was wiping the cache, and now I receive an infinite boot loop. Also when i go into fastboot on the phone i receive this message "e: can't mount /cache/recovery/log" I was reading on another thread and was thinking my partitions were deleted? I'm honestly not sure what's wrong or if i've bricked my phone beyond repair. Any help would be greatly appreciated!
Click to expand...
Click to collapse
you have flashing stock with pit via odin as an option...
samersh72 said:
you have flashing stock with pit via odin as an option...
Click to expand...
Click to collapse
Where are the stock files located? (not sure if i should specify that my nexus is verizon)
Thank,
Tyler
cvrkickercomp said:
Where are the stock files located? (not sure if i should specify that my nexus is verizon)
Thank,
Tyler
Click to expand...
Click to collapse
Look in verizon forum, you should find odin package
sent from my Galaxy
samersh72 said:
Look in verizon forum, you should find odin package
sent from my Galaxy
Click to expand...
Click to collapse
So I've tried two different things, I've used galaxy nexus toolkit to try and return to stock that way, and i've also tried downloading the odin pda file and phone file and flashing through odin and neither has gotten rid of the boot loop.
What is the error output of the fastboot commands, that's what I would like to know. "I've used a toolkit" means nothing to me.
a manta wrote this.
beekay201 said:
What is the error output of the fastboot commands, that's what I would like to know. "I've used a toolkit" means nothing to me.
a manta wrote this.
Click to expand...
Click to collapse
Pardon my ignorance but i'm not sure how to find/look for the error output.... I'm not educated at all on using the ADK/SDK which i believe might be a problem in me fixing this phone (if it's possible).
I'll elaborate on what i've tried to do to fix the problem. I've downloaded the stock toro 4.2.2 image from
HTML:
https://developers.google.com/android/nexus/images#mysid
I realized that didn't work so i tried to flash back to stock using odin from this tutorial
HTML:
http://www.galaxynexusforum.com/forum/rescue-squad/4707-how-return-stock-using-odin-vzw-lte-only.html
that didn't work so i thought maybe my partitions were messed up so i flashed the pit file from here
HTML:
http://www.usofttech.com/t51448.html
And that still hasn't helped so that is where i am at with trying to trouble shoot the problem.
Sorry i didn't answer your original question but i thought maybe if you knew what i have tried it might give you a better idea of what i'm doing wrong or right
Thanks,
Tyler :good:
cvrkickercomp said:
Pardon my ignorance but i'm not sure how to find/look for the error output.... I'm not educated at all on using the ADK/SDK which i believe might be a problem in me fixing this phone (if it's possible).
I'll elaborate on what i've tried to do to fix the problem. I've downloaded the stock toro 4.2.2 image from
HTML:
https://developers.google.com/android/nexus/images#mysid
I realized that didn't work so i tried to flash back to stock using odin from this tutorial
HTML:
http://www.galaxynexusforum.com/forum/rescue-squad/4707-how-return-stock-using-odin-vzw-lte-only.html
that didn't work so i thought maybe my partitions were messed up so i flashed the pit file from here
HTML:
http://www.usofttech.com/t51448.html
And that still hasn't helped so that is where i am at with trying to trouble shoot the problem.
Sorry i didn't answer your original question but i thought maybe if you knew what i have tried it might give you a better idea of what i'm doing wrong or right
Thanks,
Tyler :good:
Click to expand...
Click to collapse
Why didn't the factory images flash perfectly? What error? It's just that it's extremely difficult to troubleshoot when there's no output errors from commands, and this is why newbies using toolkits is never a good idea.
Please follow the procedure described here, first post. It will allow us to see which part of the flash is failing..and the corresponding error message.
beekay201 said:
Why didn't the factory images flash perfectly? What error? It's just that it's extremely difficult to troubleshoot when there's no output errors from commands, and this is why newbies using toolkits is never a good idea.
Please follow the procedure described here, first post. It will allow us to see which part of the flash is failing..and the corresponding error message.
Click to expand...
Click to collapse
So i followed the tutorial you said to and i still have a bootloop... nothing failed to flash correctly... I'm so lost
I just redownloaded the package and tried again, followed the tutorial exactly and still nothing. Everything flashed perfectly with no error messages whatsoever...
cvrkickercomp said:
I just redownloaded the package and tried again, followed the tutorial exactly and still nothing. Everything flashed perfectly with no error messages whatsoever...
Click to expand...
Click to collapse
paste the commands you used and their correspondent output please
erase and format partitions from fastboot, reflash
let it boot, it can take a few minutes
beekay201 said:
paste the commands you used and their correspondent output please
erase and format partitions from fastboot, reflash
let it boot, it can take a few minutes
Click to expand...
Click to collapse
Will do after work :good: Thanks for the help/guidance
so i'm trying to format all my partitions before i flash anything this time and this is what happened
C:\Users\Tyler\Desktop\adt\sdk\platform-tools>fastboot devices
0149CC3816013004 fastboot
C:\Users\Tyler\Desktop\adt\sdk\platform-tools>fastboot format bootloader
formatting 'bootloader' partition...
FAILED (remote: Invalid Argument)
FAILED (remote: Invalid Argument)
finished. total time: 0.016s
C:\Users\Tyler\Desktop\adt\sdk\platform-tools>fastboot format system
erasing 'system'...
OKAY [ 0.016s]
formatting 'system' partition...
Creating filesystem with parameters:
Size: 685768704
Block size: 4096
Blocks per group: 32768
Inodes per group: 6976
Inode size: 256
Journal blocks: 2616
Label:
Blocks: 167424
Block groups: 6
Reserved block group size: 47
Created filesystem with 11/41856 inodes and 5443/167424 blocks
sending 'system' (12488 KB)...
writing 'system'...
OKAY [ 3.062s]
finished. total time: 3.078s
C:\Users\Tyler\Desktop\adt\sdk\platform-tools>fastboot format bootloader
formatting 'bootloader' partition...
FAILED (remote: Invalid Argument)
FAILED (remote: Invalid Argument)
finished. total time: 0.016s
C:\Users\Tyler\Desktop\adt\sdk\platform-tools>
Am i typing the right command to format the bootloader?
So I believe I have a problem with my internal memory. I just tried "fastboot oem lock" and it works, and the phone switches to "lock state - locked" but then when i select reboot bootloader, the phone says "lock state - unlocked" again. Is there any way to fix that?
Anyone? Please help!!
bump:good:
cvrkickercomp said:
bump:good:
Click to expand...
Click to collapse
There's no point locking your bootloader if it's all messed up. Leave it unlocked.
I don't think i can help you much but try this one
Make sure to follow this steps for a clean install. Hope it helps!
http://forum.xda-developers.com/showpost.php?p=44077732&postcount=5
My M9 suddenly hang und went off... so ok i rebooted. but after boot animation off again.
i can boot into recovery and bootloader and download, but nothing else. ruu fails on pc and on sd. twrp shows system partition as 0Mb. i think something fckd up partition tables or so. i think i need a real pro to get this baby running again or at least to make it look like stock for return. if i try to flash stock recovery in download mode it says finished but still twrp on it. please please help me.
I was running Leedroid rom plus kernel.
device ist supercid and soff
nobody?? :'(
Sashtheflash said:
My M9 suddenly hang und went off... so ok i rebooted. but after boot animation off again.
i can boot into recovery and bootloader and download, but nothing else. ruu fails on pc and on sd. twrp shows system partition as 0Mb. i think something fckd up partition tables or so. i think i need a real pro to get this baby running again or at least to make it look like stock for return. if i try to flash stock recovery in download mode it says finished but still twrp on it. please please help me.
I was running Leedroid rom plus kernel.
device ist supercid and soff
Click to expand...
Click to collapse
Weird. Since you have TWRP, flashing a new ROM sounds like the best option. Maybe a full wipe beforehand? As long as you use a ROM that matches your firmware, it should work.... in theory, at least.
computerslayer said:
Weird. Since you have TWRP, flashing a new ROM sounds like the best option. Maybe a full wipe beforehand? As long as you use a ROM that matches your firmware, it should work.... in theory, at least.
Click to expand...
Click to collapse
since my phone cant find an internal memory i cant flash anything... i think partition tables are ****ed up or so. fastboot flash recovery ends in old state locking bootloader via fastboot results in bootloader still open.
Never had a problem like that and im here since the g1
Yikes. I'm afraid I don't have any further advice. Are there any threads around the M9 forums that talk about corrupted partitions?
Hello, please see my answer on pm regarding help.
Until then, please boot into TWRP and connect to adb and run cat /proc/emmc to get a listing of partitions and their sizes.
Then head over to my firmware thread, find the link to my partition table document and compare with yours. Output should be 100% identical, if not, you're right about your suspicion.
I rather assume you've got a permission / security issue which renders some partitions inaccessible. I doubt they're actually broken.
Please also make sure you always leave precise and concise info on what steps you tried and what the outcome was. This will help keep this short and helpful for others too.
Sneakyghost said:
Hello, please see my answer on pm regarding help.
Until then, please boot into TWRP and connect to adb and run cat /proc/emmc to get a listing of partitions and their sizes.
Then head over to my firmware thread, find the link to my partition table document and compare with yours. Output should be 100% identical, if not, you're right about your suspicion.
I rather assume you've got a permission / security issue which renders some partitions inaccessible. I doubt they're actually broken.
Please also make sure you always leave precise and concise info on what steps you tried and what the outcome was. This will help keep this short and helpful for others too.
Click to expand...
Click to collapse
unfortunately my device wont let me boot in recovery again... now it states: Failed to boot to recovery mode Press Volume up to back to menu.
seems my tries to flash single parts of firmware messed this up
Ok please keep it safe now. Don't do anything else to it for the time being. I can try to connect to it via team viewer tomorrow if you allow me into your machine.
What is your time zone? Will you be having time tomorrow afternoon/evening my time? I'm located in GMT +1 (Germany).
Sneakyghost said:
Ok please keep it safe now. Don't do anything else to it for the time being. I can try to connect to it via team viewer tomorrow if you allow me into your machine.
What is your time zone? Will you be having time tomorrow afternoon/evening my time? I'm located in GMT +1 (Germany).
Click to expand...
Click to collapse
Im from Germany, too ( Heilbronn) Ok i leave my fingers from it until tomorrow. Thank you a lot for trying !!!
im have also m9 dead after flash now my phone read on pc qload any one have idea to rework my phone again ?
logy122 said:
im have also m9 dead after flash now my phone read on pc qload any one have idea to rework my phone again ?
Click to expand...
Click to collapse
Yeah yours is a real brick while the OP's phone is more likely damaged NAND. Two very different things.
QHUSB on your PC when you connect it means you've managed to actually brick it.
For this, you'll need to open the phone and connect it to some special tool like the riff jtag box and rewrite the corrupted bootloader.
@Tecardo can do this for you in Germany. I'm not sure where you are but Tec has all the equipment and skills needed to fix that.
Sneakyghost said:
Yeah yours is a real brick while the OP's phone is more likely damaged NAND. Two very different things.
QHUSB on your PC when you connect it means you've managed to actually brick it.
For this, you'll need to open the phone and connect it to some special tool like the riff jtag box and rewrite the corrupted bootloader.
@Tecardo can do this for you in Germany. I'm not sure where you are but Tec has all the equipment and skills needed to fix that.
Click to expand...
Click to collapse
im also can open phone and replace emmc |> im only need boot file to write to phone and back to work
Yes you need to rewrite aboot. That's only possible with a jtag box and maybe, maybe, under Linux because the qhusb connection has no stable functioning driver on Windows. It's almost impossible to flash anything via qhusb on Windows. It could work in Linux though. I remember having had a half-stable connection to my HTC One S this way, back in 2012. I managed to rewrite the hboot back then. But afaik that never worked on the M7,8,9...
Gesendet von meinem HTC 10 mit Tapatalk
I don't want to start a new thread. I have a similar problem. I have an HTC one M9 S-OFF Unlocked. I returned my phone to stock after doing a nandrod backup. I realised I had a sms backup in the nandroid that I need so I thought I would install twrp and do a restore the nandroid. I installed twrp and afterward it bootlooped when I went to recovery mode. It goes from white HTC screen to black screen an back. I tried to go to download mode to do a fresh install but it bootloops there as well. It also bootloops if I try to turn it off with it connected to power. I have tried installing different version of twrp but I get the same problem. If I install a stock recovery it says failed to boot to recovery mode and stays on the white HTC screen. Does anyone know of a solution
Best way is to flash a RUU.
after, for your nandroid backup, flash twrp (same version you have made the backup) and don't accept supersu at the end if proposed...
bzhmobile said:
Best way is to flash a RUU.
after, for your nandroid backup, flash twrp (same version you have made the backup) and don't accept supersu at the end if proposed...
Click to expand...
Click to collapse
I get the following when I fastboot flash rom "fastboot flash rom /Users/.../Android/OPJAIMG.zip
target reported max download size of 536870912 bytes
Invalid sparse file format at header magi
error: write_sparse_skip_chunk: don't care size 1546750189 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 1013258477 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 474585325 is not a multiple of the block size 4096
sending sparse 'rom' (521267 KB)...
error: write_sparse_skip_chunk: don't care size 1546750189 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 1546750189 is not a multiple of the block size 4096
OKAY [ 15.122s]
writing 'rom'...
FAILED (remote: partition table doesn't exist)
finished. total time: 15.140s"
Sneakyghost said:
Yes you need to rewrite aboot. That's only possible with a jtag box and maybe, maybe, under Linux because the qhusb connection has no stable functioning driver on Windows. It's almost impossible to flash anything via qhusb on Windows. It could work in Linux though. I remember having had a half-stable connection to my HTC One S this way, back in 2012. I managed to rewrite the hboot back then. But afaik that never worked on the M7,8,9...
Click to expand...
Click to collapse
It was also possible w/Linux on the One XL. I too have never heard of it working on the M7 and later phones, though I've seen the odd post here claiming it is possible. No examples of anyone having done it, however.
copy the OPJAIMG.zip on the root of your Sdcard and reboot in the booloader and follow the instructions (vol +)...
or
with htc_fastboot
download Htc_fastboot.exe et copy it in your fastboot folder with the OPJAIMG.zip
fastboot oem lock , not needed if you're S-OFF
fastboot oem rebootRUU , to reboot
htc_fastboot flash zip OPJAIMG.zip
fastboot reboot
don't forget to unlock again youre device
djkfree said:
I get the following when I fastboot flash rom "fastboot flash rom /Users/.../Android/OPJAIMG.zip
target reported max download size of 536870912 bytes
Invalid sparse file format at header magi
error: write_sparse_skip_chunk: don't care size 1546750189 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 1013258477 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 474585325 is not a multiple of the block size 4096
sending sparse 'rom' (521267 KB)...
error: write_sparse_skip_chunk: don't care size 1546750189 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 1546750189 is not a multiple of the block size 4096
OKAY [ 15.122s]
writing 'rom'...
FAILED (remote: partition table doesn't exist)
finished. total time: 15.140s"
Click to expand...
Click to collapse
bzhmobile said:
copy the OPJAIMG.zip on the root of your Sdcard and reboot in the booloader and follow the instructions (vol +)...
or
with htc_fastboot
download Htc_fastboot.exe et copy it in your fastboot folder with the OPJAIMG.zip
fastboot oem lock , not needed if you're S-OFF
fastboot oem rebootRUU , to reboot
htc_fastboot flash zip OPJAIMG.zip
fastboot reboot
don't forget to unlock again youre device
Click to expand...
Click to collapse
I get bootloop when I fastboot oem rebootRUU
So,
go to download mod (option in the bootloader ) and apply the fastboot command
htc_fastboot flash zip OPJAIMG.zip
Hey, I haven't rooted my phone in years, and thought I'd try it to goof around with some stuff. When thinking of backing it up, I thought I had everything off of it that I cared about, only to realize afterwards that I don't have my recent videos of my child backed up.
1. I allowed for unlocking in dev options
2. Boot into fastboot mode
3. Flashed recovery TWRP 3.0.2 bullhead
4. Boot into recovery
TWRP asked me for my pattern to unlock my phone. I gave it the correct pattern, and it keeps saying that it's wrong and can't unencrypt. I gave up on flashing superSU since I couldn't boot, and now my phone won't boot.
I've tried flashing an older TWRP on (2.8.7.2) to try to get things back up and running, but no. Any help would be appreciated!
spierce7 said:
1. I allowed for unlocking in dev options
2. Boot into fastboot mode
Click to expand...
Click to collapse
Did you forget to list a step you did like
fastboot oem unlock
That step usually warns you that it is wiping your user data.
If you want to get it to boot, I would do
fastboot erase user
fastboot format user
fastboot erase cache
fastboot format cache
Although I wouldn't do that until you are sure what happened in case there is a remote chance your stuff is still there.
sfhub said:
Did you forget to list a step you did like
fastboot oem unlock
Click to expand...
Click to collapse
I ran
Code:
fastboot flashing unlock
In TWRP, in the backup option it still shows that I have several 26 GB in my data partition. I'm having a hard time finding it's location in the adb shell though so I can pull the files.
So that will get my device booting again? What if I wanted to get it booting again rooted?
spierce7 said:
I ran
Code:
fastboot flashing unlock
Click to expand...
Click to collapse
And you don't recall it warning you on the phone that your user data would be erased, forcing you to accept the prompt on the phone?
spierce7 said:
In TWRP, in the backup option it still shows that I have several 26 GB in my data partition. I'm having a hard time finding it's location in the adb shell though so I can pull the files.
So that will get my device booting again? What if I wanted to get it booting again rooted?
Click to expand...
Click to collapse
If TWRP says you have 26GB in your data partition available, then your data partition is probably empty.
I can't tell you 100% that will get you booting because I'm unsure of your exact problem.
I can tell you that one reason for the boot hang is if your user partition is erased but not formatted properly. What I suggested would fix that potential problem.
It doesn't seem like you'll lose any additional data you haven't already lost from the fastboot flashing unlock so it is worth a try.
I think the videos you were trying to retrieve are gone though from the fastboot flashing unlock forced factory reset.
BTW are you working with Android N or Marshmallow (6.0.1)? TWRP decryption doesn't work with Android N.
sfhub said:
And you don't recall it warning you on the phone that your user data would be erased, forcing you to accept the prompt on the phone?
Click to expand...
Click to collapse
Honestly I don't remember at this point. If you're saying that it happens, then it must have happened, and I must be an idiot.
sfhub said:
If TWRP says you have 26GB in your data partition available, then your data partition is probably empty.
Click to expand...
Click to collapse
On the backup screen it says by data partition is 26019MB. I was interpreting that it was saying thats' how much data I have to back up. I guess your right, that it's not confirming that the data is there.
sfhub said:
BTW are you working with Android N or Marshmallow (6.0.1)? TWRP decryption doesn't work with Android N
Click to expand...
Click to collapse
Stock Android 6.0.1
sfhub said:
fastboot erase user
fastboot format user
fastboot erase cache
fastboot format cache
Click to expand...
Click to collapse
I gave up and decided the data probably wasn't there.
I'm trying to get my phone working again as root. I'm seeing 2 messages: a orange one that says my data might be corrupt, that's more of a warning, and a red one after running the super user script provided by twrp. I see the red one every time I try to boot.
After that I ran the commands you gave me. Here are the results:
Code:
spierce7-mbp:~ spierce7$ fastboot erase user
erasing 'user'...
FAILED (remote: Partition table doesn't exist
)
finished. total time: 0.020s
spierce7-mbp:~ spierce7$ fastboot format user
Formatting is not supported for file system with type ''.
spierce7-mbp:~ spierce7$ fastboot erase cache
******** Did you mean to fastboot format this ext4 partition?
erasing 'cache'...
OKAY [ 0.076s]
finished. total time: 0.076s
spierce7-mbp:~ spierce7$ fastboot format cache
Creating filesystem with parameters:
Size: 100663296
Block size: 4096
Blocks per group: 32768
Inodes per group: 6144
Inode size: 256
Journal blocks: 1024
Label:
Blocks: 24576
Block groups: 1
Reserved block group size: 7
Created filesystem with 11/6144 inodes and 1422/24576 blocks
target reported max download size of 536870912 bytes
erasing 'cache'...
OKAY [ 0.063s]
sending 'cache' (5688 KB)...
OKAY [ 0.232s]
writing 'cache'...
OKAY [ 0.061s]
finished. total time: 0.355s
Two questions:
1. How do I get my phone working again?
2. How do I get my phone rooted properly so that this all wasn't for nothing?
There is no partition labeled "user", type "userdata" instead.
przemcio510 said:
There is no partition labeled "user", type "userdata" instead.
Click to expand...
Click to collapse
Code:
spierce7-mbp:~ spierce7$ fastboot format userdata
Creating filesystem with parameters:
Size: 27283927040
Block size: 4096
Blocks per group: 32768
Inodes per group: 8176
Inode size: 256
Journal blocks: 32768
Label:
Blocks: 6661115
Block groups: 204
Reserved block group size: 1024
Created filesystem with 11/1667904 inodes and 148720/6661115 blocks
target reported max download size of 536870912 bytes
erasing 'userdata'...
OKAY [ 0.426s]
sending 'userdata' (138993 KB)...
OKAY [ 3.819s]
writing 'userdata'...
OKAY [ 1.333s]
finished. total time: 5.578s
Good call.
So I'm still seeing the red "Your phone is corrupted", however my phone tries to boot again, however it still seems to be stuck on the boot animation. Not sure where to go from here.
Flash stock boot and vendor images, then in TWRP flash latest SuperSU.
przemcio510 said:
Flash stock boot and vendor images, then in TWRP flash latest SuperSU.
Click to expand...
Click to collapse
How do I do that? Where do I get the stock boot and vendor images from?
You can get latest image from here: https://dl.google.com/dl/android/aosp/bullhead-mtc19z-factory-9f649f91.tgz (this is stock Google firmware labeled MTC19Z from July)
After downloading, extract the archive, and run flash-all.bat (this script will flash all of the images for you, including data wipe, which can be disabled by removing -w parameter from the script).
Then, flash TWRP, boot into it and from there flash SuperSU zip.
przemcio510 said:
You can get latest image from here: https://dl.google.com/dl/android/aosp/bullhead-mtc19z-factory-9f649f91.tgz (this is stock Google firmware labeled MTC19Z from July)
After downloading, extract the archive, and run flash-all.bat (this script will flash all of the images for you, including data wipe, which can be disabled by removing -w parameter from the script).
Then, flash TWRP, boot into it and from there flash SuperSU zip.
Click to expand...
Click to collapse
I was able to boot into my phone following your instructions. Thank you very much. I'll try rooting my phone again after all the apps are restored.
It also seems that the auto backup on Google's "Photos" app saved all my pictures and videos. Thank you very much for your help. I really appreciate it
przemcio510 said:
There is no partition labeled "user", type "userdata" instead.
Click to expand...
Click to collapse
Thanks for correcting. Going by memory but it isn't what it used to be.
Thanks everyone . I was able to get phone back in working order with root.
Hi, hoping to get some help here. I did some quick google searching and didn't see anything specific to the pixel.
I used Skipsoft android toolkit to unlock and root my pixel xl. Shortly after I started to have some issues and was forced to do a factory reset which I believe removed root (and I'm not sure if it screwed something up with the bootloader or not) but I've never been able to get to stock recovery. For other reasons I was shipped a replacement pixel and now I need to ship this one back. I needed to revert it back to stock before I send it back. Since it didn't have root, i used Skipsoft toolkit to relock the bootloader. I was presented with a screen on the pixel asking if I wanted to relock the bootload (i had to use vol. buttons to move between yes and no and use power to select).. I selected Yes and hit the volume button. Now my phone won't boot any longer. I can get to the bootloader.. or if I try starting the phone I get a message saying my device is corrupt. It can't be trusted and may not work properly. (if its plugged into my computer or whatever I see a battery charging icon for about 10 seconds then the screen goes blank) if the phone isn't plugged into anything after the corruption notice it just goes to a blank screen.
I'm not a complete noob as I've been around rooting my devices for years but at the same time, I am no expert. Does anyone know or can anyone offer any suggestions how I can get the device back up and running stock?
Thanks in advance for any suggestions or tips!
Will it not boot into recovery from the bootloader menu?
Edit: just realised you said you've relocked the bootloader! Might have been a big nail in the coffin.
Sent from my Pixel XL using Tapatalk
Popped, hopefully Google charges you for your fraudulent warranty claim
ko0ky said:
Hi, hoping to get some help here. I did some quick google searching and didn't see anything specific to the pixel.
I used Skipsoft android toolkit to unlock and root my pixel xl. Shortly after I started to have some issues and was forced to do a factory reset which I believe removed root (and I'm not sure if it screwed something up with the bootloader or not) but I've never been able to get to stock recovery. For other reasons I was shipped a replacement pixel and now I need to ship this one back. I needed to revert it back to stock before I send it back. Since it didn't have root, i used Skipsoft toolkit to relock the bootloader. I was presented with a screen on the pixel asking if I wanted to relock the bootload (i had to use vol. buttons to move between yes and no and use power to select).. I selected Yes and hit the volume button. Now my phone won't boot any longer. I can get to the bootloader.. or if I try starting the phone I get a message saying my device is corrupt. It can't be trusted and may not work properly. (if its plugged into my computer or whatever I see a battery charging icon for about 10 seconds then the screen goes blank) if the phone isn't plugged into anything after the corruption notice it just goes to a blank screen.
I'm not a complete noob as I've been around rooting my devices for years but at the same time, I am no expert. Does anyone know or can anyone offer any suggestions how I can get the device back up and running stock?
Thanks in advance for any suggestions or tips!
Click to expand...
Click to collapse
trying to use the toolkit to download and install google factory stock image and I'm getting the following errors..
Flashing update image..
target reported max download size of 536870912 bytes
archive does not contain 'boot.sig'
archive does not contain 'recovery.img'
archive does not contain 'system.sig'
archive does not contain 'vendor.sig'
wiping userdata...
Creating filesystem with parameters:
Size: 26663190528
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 32768
Label:
Blocks: 6509568
Block groups: 199
Reserved block group size: 1024
Created filesystem with 11/1630208 inodes and 146354/6509568 blocks
--------------------------------------------
Bootloader Version...: 8996-012001-1608281716
Baseband Version.....: 8996-012511-1609150631
Serial Number........: H*
--------------------------------------------
checking product...
OKAY [ 0.050s]
checking version-bootloader...
OKAY [ 0.050s]
checking version-baseband...
OKAY [ 0.050s]
sending 'boota' (26481 KB)...
OKAY [ 0.842s]
writing 'boota'...
(bootloader) Flashing active slot "_a"
FAILED (remote: partition [boota] doesn't exist)
finished. total time: 1.296s
An error occured when flashing the image
DaveHTC200 said:
Will it not boot into recovery from the bootloader menu?
Edit: just realised you said you've relocked the bootloader! Might have been a big nail in the coffin.
Sent from my Pixel XL using Tapatalk
Click to expand...
Click to collapse
i've managed to use the toolkit to unlock the bootloader again. I can get the phone to boot again to android. But I'd like to revert it back to stock. I cannot get it to boot to recovery though.
cwalker0906 said:
Popped, hopefully Google charges you for your fraudulent warranty claim
Click to expand...
Click to collapse
WTF are you talking about? I'm not the guy who was doing warranty claims. Nice try. RMA isn't WARRANTY mister clueless.
You can try "fastboot set_active _a" prior to running the script again and see if it'll actually write to slot A
Sent from my Pixel XL using Tapatalk
ko0ky said:
WTF are you talking about? I'm not the guy who was doing warranty claims. Nice try. RMA isn't WARRANTY mister clueless.
Click to expand...
Click to collapse
Sure, either way since I'm so clueless...if you read the toolkit thread you would have seen it doesn't work flashing factory images. Multiple people including myself have had this issue, so read and you will find your answers, also if RMA isn't warrant then what is it, you are exchanging a defective device for a new one... warranty lol have a good day buddy
ko0ky said:
Hi, hoping to get some help here. I did some quick google searching and didn't see anything specific to the pixel.
I used Skipsoft android toolkit to unlock and root my pixel xl. Shortly after I started to have some issues and was forced to do a factory reset which I believe removed root (and I'm not sure if it screwed something up with the bootloader or not) but I've never been able to get to stock recovery. For other reasons I was shipped a replacement pixel and now I need to ship this one back. I needed to revert it back to stock before I send it back. Since it didn't have root, i used Skipsoft toolkit to relock the bootloader. I was presented with a screen on the pixel asking if I wanted to relock the bootload (i had to use vol. buttons to move between yes and no and use power to select).. I selected Yes and hit the volume button. Now my phone won't boot any longer. I can get to the bootloader.. or if I try starting the phone I get a message saying my device is corrupt. It can't be trusted and may not work properly. (if its plugged into my computer or whatever I see a battery charging icon for about 10 seconds then the screen goes blank) if the phone isn't plugged into anything after the corruption notice it just goes to a blank screen.
I'm not a complete noob as I've been around rooting my devices for years but at the same time, I am no expert. Does anyone know or can anyone offer any suggestions how I can get the device back up and running stock?
Thanks in advance for any suggestions or tips!
Click to expand...
Click to collapse
Anyone else having this issue I was able to flash my device using directions from this page. (directly from google). https://developers.google.com/android/images You might have to accept their terms before everything gets displayed. I downloaded the image and ran flashall.bat on my windows box - rebooted the device, then got back to bootloader and ran the cmd to lock the bootloader. Everything is STOCK and good to be returned.
cwalker0906 said:
Sure, either way since I'm so clueless...if you read the toolkit thread you would have seen it doesn't work flashing factory images. Multiple people including myself have had this issue, so read and you will find your answers, also if RMA isn't warrant then what is it, you are exchanging a defective device for a new one... warranty lol have a good day buddy
Click to expand...
Click to collapse
He very clearly said that it was being returned for "other" reasons. Not the flashing fiasco.
wtherrell said:
He very clearly said that it was being returned for "other" reasons. Not the flashing fiasco.
Click to expand...
Click to collapse
You are right, I jumped the gun ,all apologies
wtherrell said:
He very clearly said that it was being returned for "other" reasons. Not the flashing fiasco.
Click to expand...
Click to collapse
thanks for being courtesy and helpful! much appreciated!
ko0ky said:
trying to use the toolkit to download and install google factory stock image and I'm getting the following errors..
Flashing update image..
target reported max download size of 536870912 bytes
archive does not contain 'boot.sig'
archive does not contain 'recovery.img'
archive does not contain 'system.sig'
archive does not contain 'vendor.sig'
wiping userdata...
Creating filesystem with parameters:
Size: 26663190528
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 32768
Label:
Blocks: 6509568
Block groups: 199
Reserved block group size: 1024
Created filesystem with 11/1630208 inodes and 146354/6509568 blocks
--------------------------------------------
Bootloader Version...: 8996-012001-1608281716
Baseband Version.....: 8996-012511-1609150631
Serial Number........: H*
--------------------------------------------
checking product...
OKAY [ 0.050s]
checking version-bootloader...
OKAY [ 0.050s]
checking version-baseband...
OKAY [ 0.050s]
sending 'boota' (26481 KB)...
OKAY [ 0.842s]
writing 'boota'...
(bootloader) Flashing active slot "_a"
FAILED (remote: partition [boota] doesn't exist)
finished. total time: 1.296s
An error occured when flashing the image
Click to expand...
Click to collapse
Did you solve this problem, I'm getting the same thing. Stuck in bootloop, but somehow managed to get it started, now stuck in "checking for updates"
dabadoo said:
Did you solve this problem, I'm getting the same thing. Stuck in bootloop, but somehow managed to get it started, now stuck in "checking for updates"
Click to expand...
Click to collapse
To flash use the instructions from the Google page :
https://developers.google.com/android/images
Paolo
The other thing is make sure you're using the latest Fastboot. Old fastboots do not have support for the slot system.
Let this be a huge lesson not to go running to tool kits, the one you used is nice for installing the drivers but ultimately simply using the flash-all.bat is infinitely easier to do at this point if adb/fastboot is configured.
Also don't lock the bootloader if you have modified the system at all =/
Edit: You should probably add your solution to the OP to help anyone else that maybe have done something similar.
I am having a similar issue. All I have done is u lock the bootloader through fastboot. No toolkits involved or anything. Simply plugged in, booted bootloader mode then fastboot OEM unlock and rebooted. I am unlocked but noticed I cannot boot stock recovery. It goes to the dead Android icon and simply says no command below it. No amount of pressing the volume keys or anything changes it. Holding power eventually reboots back to Android. Anyone else experiencing this or have a fix , or better yet a reason for this occurring?
powdered_donuts said:
I am having a similar issue. All I have done is u lock the bootloader through fastboot. No toolkits involved or anything. Simply plugged in, booted bootloader mode then fastboot OEM unlock and rebooted. I am unlocked but noticed I cannot boot stock recovery. It goes to the dead Android icon and simply says no command below it. No amount of pressing the volume keys or anything changes it. Holding power eventually reboots back to Android. Anyone else experiencing this or have a fix , or better yet a reason for this occurring?
Click to expand...
Click to collapse
When on the no command screen, have you pressed and held the power button, then the volume up button?
Never fails for me! Trying to press them together I didn't have any luck.
Sent from my Pixel XL using Tapatalk
DaveHTC200 said:
When on the no command screen, have you pressed and held the power button, then the volume up button?
Never fails for me! Trying to press them together I didn't have any luck.
Sent from my Pixel XL using Tapatalk
Click to expand...
Click to collapse
Maybe I didn't do it in the correct manner, I'll give it a go and report back
Update: successful! Power first then volume then release.
Thanks!!
ko0ky said:
i've managed to use the toolkit to unlock the bootloader again. I can get the phone to boot again to android. But I'd like to revert it back to stock. I cannot get it to boot to recovery though.
Click to expand...
Click to collapse
How did you manage to unlock bootloader and reboot phone trough toolkit, im in the same situation here . the phone is locked on verizon. Thankyou
Hello,
After a few years of having ultimate hd on my arc s, I'm playing again with my old loved xperia arc s, the one that I've unlocked bootloader and installed so many many custom roms in the past.
Now I want to test this rom:
https://forum.xda-developers.com/xp...v-2011-android-source-project-builds-t3053170
...Just to change ultimate hd for a long time.
But it's necessary that I'd installed before the latest ftf (4.0.4_4.1.B.0.587). As I am not sure after such a long time, I want to make it again, because the installation of this custom rom failed the first time I'd tried...
Using flashtool version 0.9.18.6 as recommended here, I'm getting error "ERROR - Processing of system.sin finished with errors." ... the other .sin files in the FTF file are flashing ok...
I've also tried to flash, first everithing except system.sin, then only system.sin, but it gives me the same error.
I've also tried to flash system.sin with fastboot:
fastboot flash system system.sin
but I get error "FAILED (remote: Download size too large)"
To overcome this, if I try to run instead this:
fastboot flash -S 256M system system.sin
Then I get a series of messages:
Invalid sparse file format at header magic
error: write_sparse_skip_chunk: don't care size 90299761 is not a multiple of the block size 4096 (it repeats it multiple times)
OKAY [ 32.292s]
writing 'system' 1/2...
(bootloader) Flash of partition 'system' requested
(bootloader) S1 partID 0x00000004, block 0x000002f4-0x00000f73
(bootloader) Erasing block 0x00000300...
Erase operation complete, 589 bad blocks encountered
(bootloader) Flashing...
...
(bootloader) Flash operation complete
OKAY [ 17.994s]
finished. total time: 107.983s
Despite the errors, (they are RARE, as I'd NEVER had problems with defective nand on my phone, and I'd installed LOTS of custom roms in the past) It seems to be flashed... But android does not start (SONY) logo appears, and then, an exclamation sign and a little 'seems-to-be-dead' phone icon appears.
I've also tried to reinstall twrp first and do a total wipe. it continues to fail.
The other versions I've tried for flashtool are
0.9.1.0
0.9.2.6
0.9.2.8
0.9.18.2
None of them worked, ... 0.9.18.6 is supposed to work, but it does not. The drivers for this version are installed (disabling that reference integrity stuff in windows 10)
I've also tried to test different firmware files, but they give me always the same error:
XPERIASITE.PL_Arc_S_LT18i_4.0.4_4.1.B.0.587_CentralEurope.ftf
LT18i_4.1.B.0.587_Customized_FR.ftf
LT18i_4.1.B.0.587_Customized MEA_1254-2284_R1I.ftf
LT18i_4.1.B.0.587 (1254-2716).(MMUG).ftf
What can I do ?
Thanks in advance,
Obsy
Hey there, did you ever manage to solve your issue ? I'm having an extremely similar problem with my Xperia Ray...
After some digging, I suspect that the number of bad sectors/bad blocks on the internal memory (more specifically on the /system partition) is big enough to make a significant part of the memory unusable... As a consequence, flashing of any rom or kernel is impossible due to insufficient space... Indeed, I looked at the "dmesg" output after trying to flash a rom in recovery, and I saw a lot of "bad blocks" mentioned and then a crash with "No space left on the device" as an error message :-(
Thanks in advance !
yugobosss said:
Hey there, did you ever manage to solve your issue ? I'm having an extremely similar problem with my Xperia Ray...
After some digging, I suspect that the number of bad sectors/bad blocks on the internal memory (more specifically on the /system partition) is big enough to make a significant part of the memory unusable... As a consequence, flashing of any rom or kernel is impossible due to insufficient space... Indeed, I looked at the "dmesg" output after trying to flash a rom in recovery, and I saw a lot of "bad blocks" mentioned and then a crash with "No space left on the device" as an error message :-(
Thanks in advance !
Click to expand...
Click to collapse
Hi,... Unfortunately I no longer have this phone, I broke it to simplify my life . Good luck with that !
Oh well... thanks for the quick reply !
If anyone else has any idea about all this, I'm open to suggestions !