Related
I'm was using CM9 nightly and it froze, I removed the battery and tried to boot but it hangs at Google screen.
I can access bootloader and recovery but, in CWM touch recovery, I can't mount or format system, sdcard, or data but can wipe and mount/unmount cache.
And I can't mount USB in recovery
I can access through fastboot, so what would I need to go about doing to get this thing back up and running?
I don't want to try to many things and screw it up worse or something. It seems to me like the partitions got screwed up or something, but that's just a wild guess. Can anyone help me fix this or point me in the right direction?
jivetrky said:
I'm was using CM9 nightly and it froze, I removed the battery and tried to boot but it hangs at Google screen.
I can access bootloader and recovery but, in CWM touch recovery, I can't mount or format system, sdcard, or data but can wipe and mount/unmount cache.
And I can't mount USB in recovery
I can access through fastboot, so what would I need to go about doing to get this thing back up and running?
I don't want to try to many things and screw it up worse or something. It seems to me like the partitions got screwed up or something, but that's just a wild guess. Can anyone help me fix this or point me in the right direction?
Click to expand...
Click to collapse
sounds like the sd(storage) is gone bad or going bad.
simms22 said:
sounds like the sd(storage) is gone bad or going bad.
Click to expand...
Click to collapse
Any way I could test that theory, through ADB or something?
jivetrky said:
Any way I could test that theory, through ADB or something?
Click to expand...
Click to collapse
maybe a logcat while trying to access the storage? but really, if it isnt accessible, thats all the info you should need.
Wow... internal memory already gone bad? Have you tried fastboot flash the factory images for ns4g?
Sent from my Nexus S 4G using XDA
rasengan82 said:
Wow... internal memory already gone bad? Have you tried fastboot flash the factory images for ns4g?
Sent from my Nexus S 4G using XDA
Click to expand...
Click to collapse
the internal storage going bad is actually a very common problem.
I guess locking bootloader and claiming warranty is the way to go.
Sent from my Nexus S 4G using XDA
rasengan82 said:
I guess locking bootloader and claiming warranty is the way to go.
Sent from my Nexus S 4G using XDA
Click to expand...
Click to collapse
How might I go about doing that?
jivetrky said:
How might I go about doing that?
Click to expand...
Click to collapse
fastboot oem lock
with fastboot while in the bootloader. provided that fastboot sees your device(fastboot devices).
Just a warning... if you oem lock you won't be able to oem unlock again IF you internal memory is indeed corrupted.
Sent from my Nexus S 4G using XDA
rasengan82 said:
Just a warning... if you oem lock you won't be able to oem unlock again IF you internal memory is indeed corrupted.
Sent from my Nexus S 4G using XDA
Click to expand...
Click to collapse
very true. but if youre doing it to send back to samsung for a warranty repair, does it matter?
I don't know the inner workings of Android or this device specifically, but isn't there just a single bit of flash on the phone which is divided/partitioned into SD, system, etc. Is it possible that the partitions have just been corrupted or something like that? I was playing around just seeing what the phone could do and Odin3 will recognize it, but I didn't want to play around and screw anything up even more than it is.
Is it possible to use Odin to try and attempt a fix? I see there is a re-partition option, I was wondering if that could be worth a try?
Well, I guess I've given up and I'll just hope for Samsung to replace/fix it.
Google-foo has not shown me anything as far as trying to repartition just in case it was corrupted or something; couldn't find any images out there with PITs. I'm able to write the bootloaders and recovery so I just used the one-click-stock provided boot and recovery images and flashed them with fastboot then locked it.
Doesn't boot and recovery go on the same flash that is theoretically bad which is stopping SD, system, & data from being mounted?
Just for the sake, what happens now if you do fastboot oem unlock?
Do you get an error? If you don't get an error, unlock it and then download this:
https://dl.google.com/dl/android/aosp/sojus-imm76d-factory-10660f4c.tgz
Unzip everything and put it on a folder (you will find several img files). Now start the phone again in fastboot mode.
fastboot flash bootloader bootloader-crespo4g-d720sprke1.img
fastboot reboot-bootloader
fastboot flash radio radio-crespo4g-d720sprlc1.img
fastboot reboot-bootloader
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash userdata userdata.img
fastboot erase cache
fastboot reboot
rasengan82 said:
Just for the sake, what happens now if you do fastboot oem unlock?
Do you get an error? If you don't get an error, unlock it and then download this:
https://dl.google.com/dl/android/aosp/sojus-imm76d-factory-10660f4c.tgz
Unzip everything and put it on a folder (you will find several img files). Now start the phone again in fastboot mode.
fastboot flash bootloader bootloader-crespo4g-d720sprke1.img
fastboot reboot-bootloader
fastboot flash radio radio-crespo4g-d720sprlc1.img
fastboot reboot-bootloader
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash userdata userdata.img
fastboot erase cache
fastboot reboot
Click to expand...
Click to collapse
I can't unlock it now, as the bootloader pops up a screen that says to unlock it you have to wipe/factory reset. But it hangs on that probably because it can't see system/data.
I did try flashing it with fastboot though, before I locked it, and I could flash boot, recovery, and radio but it will just hang forever on flashing system. It never gives an error. I let it sit there for over an hour and it never did anything.
So I guess now that it's locked there really is nothing I can do.
Ok, I think Samsung warranty is the only thing left.
Forgot to update, sent to Samsung and they replaced the PBA, so the flash was apparently bad. Thanks for the advice, everyone!
Was only about a week turn around, just took me a while to actually get the RMA started.
They even send a UPS label to ship it to them then took a week turnaround, overall it was good service.
My MT4GS is boot looping. I can get into the bootloader, but can't get into recovery and flashing a stock image doesn't do anything. I've unlocked the phone and achieved S-OFF using the j-bear wire trick. I've ran the phone for a few weeks after getting the s-off, so I don't think it's that. When I flash a stock image from the bootloader, the software/radio versions don't change and it still boot loops. I also have a faint red light in the notification and trackpad. I'm out of ideas. Anyone have any suggestions?
well first thing id attempt is to grab an image of a recovery and try and flash it through fastboot, image HERE
fastboot command
Code:
fastboot flash recovery recovery.img
if you need any further instruction on how to use fastboot you can get some info HERE
or if this dosent work or have more questions feel free to ask
its not a brick if you can get into hboot, you may have a tough time getting your phone working again but usually its doable.
good luck!
Thanks for the quick reply. I did a recovery flash through fastboot (CWM 5.0.2.7), but still couldn't get to recovery. I was able to update hboot to the jb_hboot. That allowed me to perform some more fastboot commands, such as: erase boot, recovery, system, userdata. I then tried to flashed a signed stock image, but still got stuck at boot loop and couldn't get into recovery. I might try TWRP recovery to see if it changes anything.
what all does it say on your bootloader screen now?
It says:
= Juopunut Bear =
DOUBLESHOT PVT SHIP S-OFF RL
HBOOT-1.45.1313
RADIO-11.16.3504.20_2
eMMC-boot
Nov 21 2011, 20:20:47
Well it let you write to the emmc so that's a good sign. Did it give you an error in fastboot? Or did it say completed in .9 sec or something like that?
What happens when you choose recovery from the bootloader screen? Also have you tried adb reboot-recovery?
Sent from my Desire Z using Tapatalk 2
when you say you cant get to recovery what's basically happening when you boot to recovery? Red triangle on screen? reboot loop? black screen? or what else.
demkantor said:
Well it let you write to the emmc so that's a good sign. Did it give you an error in fastboot? Or did it say completed in .9 sec or something like that?
What happens when you choose recovery from the bootloader screen? Also have you tried adb reboot-recovery?
Sent from my Desire Z using Tapatalk 2
Click to expand...
Click to collapse
Riyal said:
when you say you cant get to recovery what's basically happening when you boot to recovery? Red triangle on screen? reboot loop? black screen? or what else.
Click to expand...
Click to collapse
I didn't get a fastboot error when I wrote to boot, it said completed and a time. When I choose recovery, I get a boot loop. I can't connect via adb. I don't think I have the right drivers setup for adb because when I type "adb remount" it says no device found.
Drivers taken from weekendsr2shorts mirror thread
it is strange that you can get fastboot working but not adb, but maybe more digging needs to be done to solve that. but it could just be from hboot screen there is no access to adb... come to think of it that sounds normal
try erasing recovery partition and flashing again, maybe there is some corruption there that stuck around even after the last flash
Code:
fastboot erase recovery
fastboot flash recovery recovery.img
fastboot reboot-bootloader
see if any of that works
Erasing and flashing recovery still resulted in a boot loop. How can I find out if there is a corruption in flash?
Not too sure a great way of telling, maybe try reformatting recovery? On a side note what exactly were the stock image you were trying to flash? I believe there is an issue when flashing certain stock setups after the radio s-off, being the way bootloader varifies the radio, recovery, Rom, etc. Sometimes things can go awry when doing this. I don't have a ds yet (still waiting on stupid parts from China) so I haven't done a whole lot of research on this phone. Maybe someone will chime in who knows more specifically what to be looking for
Sent from my Desire Z using xda premium
I tried to flash both "PG59IMG_Doubleshot_TMOUS_1.55.531.3_Radio_11.59.3504.00_11.16.3504.20_2_release_227956_signed" and "PG59IMG_Doubleshot_TMOUS_1.63.531.2_Radio_11.59.3504.00_11.16.3504.20_2_release_245247_signed". You think I should try a custom ROM instead? Is there one available to flash through the bootloader or fastboot? I tried to flash the signed stock image zips with fastboot, but it complained about not finding expected signature. Sorry to hear about your DS. Hope you get your parts soon.
rumi409 said:
Erasing and flashing recovery still resulted in a boot loop. How can I find out if there is a corruption in flash?
Click to expand...
Click to collapse
Here's a copy of my "platform-tools" files. They've always been flawless for me. You can also take the PG59IMG file and rename it to JUST PG59IMG.zip, put it in the root directory of your SD card and reboot and see if your bootloader will load it for you.
**you'll need to get a recovery operational before you can move on to custom ROMs. Edit: UNLESS you want to use Update.zip (See demkantor's post below.....)
This IS assuming that the main files you're running thru ADB have no corruption issues though.
Well you can flash roms through fastboot,
fastboot update.zip
Just change the name of the Rom to what's needed
Maybe try to format as many partitions as you can through fastboot first?
Sent from my Desire Z using xda premium
WeekendsR2Short said:
Here's a copy of my "platform-tools" files. They've always been flawless for me. You can also take the PG59IMG file and rename it to JUST PG59IMG.zip, put it in the root directory of your SD card and reboot and see if your bootloader will load it for you.
**you'll need to get a recovery operational before you can move on to custom ROMs. Edit: UNLESS you want to use Update.zip (See demkantor's post below.....)
This IS assuming that the main files you're running thru ADB have no corruption issues though.
Click to expand...
Click to collapse
I flashed this recovery image via the bootloader and fastboot. Still no luck. Is erase and format the same thing? I've erased boot, recovery and system. I checked that they were erased by doing a Image CRC, which resulted in a 0 value. Then flashed the signed DS ROMs. It still resulted in the same, boot loop.
erasing will wipe out whats in the partition, formatting will get rid of the partition and replace it with a new one. so think of it as a super eraser sorta
fastboot format recovery
but you can also see if any of this helps but im not too sure it would
fastboot format system
fastboot fromat boot
fastboot format userdata
fastboot format cache
also you can do a fastboot oem format, never done this but my understanding is it will reformat most partitions for you, and something is nagging me about this one and i just cant remember, ill do some googleing and get back on that, although im not sure if any of this will help too much in your situation
demkantor said:
erasing will wipe out whats in the partition, formatting will get rid of the partition and replace it with a new one. so think of it as a super eraser sorta
fastboot format recovery
but you can also see if any of this helps but im not too sure it would
fastboot format system
fastboot fromat boot
fastboot format userdata
fastboot format cache
also you can do a fastboot oem format, never done this but my understanding is it will reformat most partitions for you, and something is nagging me about this one and i just cant remember, ill do some googleing and get back on that, although im not sure if any of this will help too much in your situation
Click to expand...
Click to collapse
I can't seem to get any of the format commands to work. It just displays the fastboot commands and options, as if I typed something it can't understand.
Have you tried a different SD card?
mattlowry said:
Have you tried a different SD card?
Click to expand...
Click to collapse
I'm not using a micro sd card. Have been flashing through the computer.
rumi409 said:
I'm not using a micro sd card. Have been flashing through the computer.
Click to expand...
Click to collapse
have you tried placing the pg file on your sd card and let the bootloder load it itself?
HELP TO ALL THE COMMUNITY ASAP!!!
here is the deal, i had the HTC One S Rooted fine, it was working but i tried now to install a custom rom, baked black beans, but now i've downloaded the rom, set it in my HTC, accessed CMW, wiped data, installed from sd, rebooted, went to bootloader, run boot.img on cmd on computer, restarted and now i am getting the HTC Bootloader that states that "This build is for development purporses etc. etc.." now here is the deal guys... i was able to get to bootloader then to recovery, i check the sd files in clockwork recovery and nothing!! all i want now is just stock and try again.. guys.. help???
URGENT!!
therion0 said:
HELP TO ALL THE COMMUNITY ASAP!!!
here is the deal, i had the HTC One S Rooted fine, it was working but i tried now to install a custom rom, baked black beans, but now i've downloaded the rom, set it in my HTC, accessed CMW, wiped data, installed from sd, rebooted, went to bootloader, run boot.img on cmd on computer, restarted and now i am getting the HTC Bootloader that states that "This build is for development purporses etc. etc.." now here is the deal guys... i was able to get to bootloader then to recovery, i check the sd files in clockwork recovery and nothing!! all i want now is just stock and try again.. guys.. help???
URGENT!!
Click to expand...
Click to collapse
CWM cant mount SD you need TWRP for that and a RUU put you back to stock but the bootloader needs relocking. So did you even try booting the rom because the red writing is fine.
you didn't mention it, but you should wipe system and caches as well as data
Not hard brick. you can chose the correct Ruu file and flash it to your phone.... solved your case.
Darknites said:
CWM cant mount SD you need TWRP for that
Click to expand...
Click to collapse
CWM can not mount our sdcard onto your computer over USB.
But it absolutely can mount the sdcard partition onto the root filesystem.
Unless you have the 'unmountable sdcard' problem, for which there is a sticky in Q&A.
My feeling is that the OP didnt mount the sdcard partition. In that case it is normal to see the mount point as an empty folder.
Once it's mounted, you can adb push rom zips to it.
touch of jobo said:
CWM can not mount our sdcard onto your computer over USB.
But it absolutely can mount the sdcard partition onto the root filesystem.
Unless you have the 'unmountable sdcard' problem, for which there is a sticky in Q&A.
My feeling is that the OP didnt mount the sdcard partition. In that case it is normal to see the mount point as an empty folder.
Once it's mounted, you can adb push rom zips to it.
Click to expand...
Click to collapse
Oh right seems a lot work lol, I think I stick to TWRP.
Darknites said:
Oh right seems a lot work lol, I think I stick to TWRP.
Click to expand...
Click to collapse
+1, 2 & 3!
Really don't understand why anyone still uses CWM, I think its just habit with some people.
shadowch31 said:
+1, 2 & 3!
Really don't understand why anyone still uses CWM, I think its just habit with some people.
Click to expand...
Click to collapse
Habit and guides.
I thought I saw a post that mentioned cwm has not kept up to date--not sure
But, I was a slow convert too and very happy with twrp 2.2.2.0
rugmankc said:
I thought I saw a post that mentioned cwm has not kept up to date--not sure
But, I was a slow convert too and very happy with twrp 2.2.2.0
Click to expand...
Click to collapse
I not seen updates but then I not looked and I didn't move over in till it got the usb mount.
when i run the CMD Command prompt adb reboot bootloader I get error: device not found, i was able to flash the boot.img and i got the 2 OKs but i get that error now... what now?
Also, when i go to recovery mode, i don't see any files to install the .zip file of the rom i want to install
therion0 said:
Also, when i go to recovery mode, i don't see any files to install the .zip file of the rom i want to install
Click to expand...
Click to collapse
You lost SD then and best off running a RUU to recover it.
ok i'm lost.. how do i run an RUU to recover it?
therion0 said:
ok i'm lost.. how do i run an RUU to recover it?
Click to expand...
Click to collapse
Download the right RUU for your carrier and location by looking at http://forum.xda-developers.com/showthread.php?t=1543588 and you can get free download at http://www.4shared.com/folder/jKN2qjTl/HTC_Ville_RUU_Collection.html
Then plug in your phone and follow the instructions when you run the RUU .exe file.
AKToronto
but everytime i try to run it, it says it fails because the phone it is not connected to the computer but it is...
did you ever try to boot into the rom after you flashed it and boot image as in just tapping on reboot system
can you plug phone into pc and get indicator at top of screen that says you are connected. then pull down notification bar and select to mount drive
if so, does it show you your sdcard in the windows screen
you do have an S4 device and assume you are hboot .13 or higher
if you can get into os and see sdcard, you can get twrp and flash image gui and flash rom and boot image with it
i am sure you tried these things, just hard to know when reading posts
also, i don't know if you are running your commands correctly based on how i undestand your posts. you can't run adb commands from fastboot, which is what you were in to fastboot boot image. you would want to type fastboot reboot-bootloader
if you are very familiar with adb/fastboot--sorry. if not need to get up to speed on them
if i misread or misunderstood any of this, sorry for butting in--
rugmankc said:
did you ever try to boot into the rom after you flashed it and boot image as in just tapping on reboot system
can you plug phone into pc and get indicator at top of screen that says you are connected. then pull down notification bar and select to mount drive
if so, does it show you your sdcard in the windows screen
you do have an S4 device and assume you are hboot .13 or higher
if you can get into os and see sdcard, you can get twrp and flash image gui and flash rom and boot image with it
i am sure you tried these things, just hard to know when reading posts
also, i don't know if you are running your commands correctly based on how i undestand your posts. you can't run adb commands from fastboot, which is what you were in to fastboot boot image. you would want to type fastboot reboot-bootloader
if you are very familiar with adb/fastboot--sorry. if not need to get up to speed on them
if i misread or misunderstood any of this, sorry for butting in--
Click to expand...
Click to collapse
Ya he messed it up so needs RUU. He has PM me just waiting on a reply.
was flashing a rom, then a kernel.. it stopped, so i rebooted. things were fine.
tried to factory reset, flash rom.. damn thing froze again. so i rebooted.
now it bootloops. i have since fastboot flashed the boot.img from the rom, and fastboot flashed the twrp.img recovery.
can get to bootloader, can get to fastboot usb, but cannot get to recovery or back to a running phone.. bootloops
please help
can i RUU or something?
wdkingery said:
was flashing a rom, then a kernel.. it stopped, so i rebooted. things were fine.
tried to factory reset, flash rom.. damn thing froze again. so i rebooted.
now it bootloops. i have since fastboot flashed the boot.img from the rom, and fastboot flashed the twrp.img recovery.
can get to bootloader, can get to fastboot usb, but cannot get to recovery or back to a running phone.. bootloops
please help
Click to expand...
Click to collapse
So I have noticed with my phone (hboot 1.14) I have to DISCONNECT it from my computer while in bootloader to be able to boot into recovery. So I do the following:
With phone in bootloader fastboot mode:
1) fastboot reboot-bootloader
2) While the screen is black, DISCONNECT the cable
3) In bootloader, use vol keys navigate to Recovery
4) Hopefully profit
Give it a try
wdkingery said:
was flashing a rom, then a kernel.. it stopped, so i rebooted. things were fine.
tried to factory reset, flash rom.. damn thing froze again. so i rebooted.
now it bootloops. i have since fastboot flashed the boot.img from the rom, and fastboot flashed the twrp.img recovery.
can get to bootloader, can get to fastboot usb, but cannot get to recovery or back to a running phone.. bootloops
please help
Click to expand...
Click to collapse
Can you relock the bootloader? If can then download the official RUU(here is 2.20 firmware http://www.htc.com/us/support/htc-one-x-att/software-updates) and that'll probably save your phone.
oh, you can use the all in one toolkit(http://forum.xda-developers.com/showthread.php?t=1952426) to relock your bootloader if you can.. good luck
TheEmpyre said:
So I have noticed with my phone (hboot 1.14) I have to DISCONNECT it from my computer while in bootloader to be able to boot into recovery. So I do the following:
With phone in bootloader fastboot mode:
1) fastboot reboot-bootloader
2) While the screen is black, DISCONNECT the cable
3) In bootloader, use vol keys navigate to Recovery
4) Hopefully profit
Give it a try
Click to expand...
Click to collapse
GOD ALMIGHTY what in the gayness.
thanks dude. was the problem.
now i have a probably bigger problem; unable to mount SD card.. i think i have read that means a bad thing. tried to mount SD card: windows wants to format it. **** me
wdkingery said:
GOD ALMIGHTY what in the gayness.
thanks dude. was the problem.
now i have a probably bigger problem; unable to mount SD card.. i think i have read that means a bad thing
Click to expand...
Click to collapse
You probably corrupted it at some point in this process. You need to mount with your pc and reformat. It happens.
iElvis said:
You probably corrupted it at some point in this process. You need to mount with your pc and reformat. It happens.
Click to expand...
Click to collapse
you are saying if i allow windows to format it, i won't have a brick, but instead will be able to fix my problem?
wdkingery said:
you are saying if i allow windows to format it, i won't have a brick, but instead will be able to fix my problem?
Click to expand...
Click to collapse
Sweet! Glad I could help, it took me a while to figure it out too, my palms were all sweaty thinking I derped my phone. And about the un-mountable SD card:
I had the same problem with my Nexus 10 when I was unlocking the bootloader, and all I had to do was actually do a format via Recovery (TWRP). Then I was able to boot into the ROM -- although I wasn't able to mount the Nexus 10 SD card still....so thats still a mystery. But I was able to get into the installed ROM
TheEmpyre said:
Sweet! Glad I could help, it took me a while to figure it out too, my palms were all sweaty thinking I derped my phone. And about the un-mountable SD card:
I had the same problem with my Nexus 10 when I was unlocking the bootloader, and all I had to do was actually do a format via Recovery (TWRP). Then I was able to boot into the ROM -- although I wasn't able to mount the Nexus 10 SD card still....so thats still a mystery. But I was able to get into the installed ROM
Click to expand...
Click to collapse
i tried that, and it failed.
i almost had windows format it, but i don't know which format type (FAT 32?)
and i'm still not clear if it will brick if i do
NEW EDIT: it doesn't brick, use default format type.
looks like i'm out of the weeds, thanks for all the quick replies.
wdkingery said:
i tried that, and it failed.
i almost had windows format it, but i don't know which format type (FAT 32?)
and i'm still not clear if it will brick if i do
NEW EDIT: it doesn't brick, use default format type.
looks like i'm out of the weeds, thanks for all the quick replies.
Click to expand...
Click to collapse
Does your TWRP not have a "Format Data" Option in the Wipe Menu?
Edit: Just read your most recent edit, happy flashing hope everything works out. Oh and add [Solved] to your title if you don't mind
it does, but even that didn't work..
hey guys i just reverted back to stock from cm12.1 and after that my mobile is automatically booting to recovery and not booting sytem at all... But if i flash recovery with boot.img i can boot successfully... may i know the reason please.......
something probably went wrong with the boot.img flashing it to the boot partition. just do a full fastboot factory flash and you should be fine.
You should try flashing to complete stock using this guide. If you want to keep your data, ignore this line:
Code:
fastboot erase userdata
.
Same problem here, the phone starts on fastboot mode every time i turn off and turn on. My is XT1543, any help?? I got my bootloader relocked.
I found the solution for my device. Installed the Stock Rom on RSD Lite v6.2.4 and works here. Boot up into system, no more boot on Fastboot at startup. Vefore I was doing the flash over ADB commands, I think the bug was there. RSD Lite fixed it.
I have made a program recently which fully wipes the phones internal memory, and reflashes the partition table. This would fix your problem most definitely.
Il be uploading the work to my onedrive tomorrow but I cant right now as it is on my work pc which I wont have access to til tomorrow
If anyone wants the program, email me at [email protected] if you really need it now and I will reply with the file attached to it, all it means is that I have to spend 20 minutes on a slow remote desktop to retrieve the file. But I'm happy to do that if that is what makes the members of XDA happier be aware you need python 3.4 installed for it to work!
I hope this is a working solution for anyone that needs my program !