Related
I have no clue how this started. Last thing I did was flash Amon_RA 2.3 recovery on FEB 9th then the newest CM7 nightly, 32 I believe. Everything was fine with my phone up until an hour ago. I was on the phone with Sprint, they screwed up my sign-up date. But thats a whole other story. My phones battery was getting low during the call. Once I ended the call I set my phone down then noticed it started going into a boot cycle. Now all it will do is boot to the splash screen then reboot again, and again, and again. I tried to pull the battery and boot to recovery. It does the same thing. It will let me get to the bootloader and select recovery. Once I select recovery, it starts its damn boot loop. Any ideas? PLEASE HELP!
Well since you can't get into recovery, try pushing a recovery via adb or fastboot...
teh roxxorz said:
Well since you can't get into recovery, try pushing a recovery via adb or fastboot...
Click to expand...
Click to collapse
Its been soo long since I had to do any adb. Actually since launch using toasts root methods. Can you explain the commands please? On another note I do not have any recovery.img's saved to my pc. I dl'd them directly to my phone and flashed from a terminal app.
http://forum.xda-developers.com/showthread.php?t=705026
this thread can help you out especially the OP
download the amon-ra p36img.zip and place it onto your sdcard somehow, pull the battery, boot into bootloader, flash the pc36img and then reboot. they you'll have recovery and can load any rom you want again
t3project said:
download the amon-ra p36img.zip and place it onto your sdcard somehow, pull the battery, boot into bootloader, flash the pc36img and then reboot. they you'll have recovery and can load any rom you want again
Click to expand...
Click to collapse
^ Do exactly that [basically what I was saying/] But take out the battery and put the SD card in your computer via adapter to put the file on there.
Ok, the PC36IMG.ZIP is on the root of my sd and the bootloader is not seeing it? Now what?
if you're using windows make sure to not have the file as PC36IMG.zip.zip
mich11128 said:
if you're using windows make sure to not have the file as PC36IMG.zip.zip
Click to expand...
Click to collapse
Ok, I got it to see it. I ran the update, once it rebooted I selected recovery. It first asked me if I want to delete data? Or something on those terms. I chose no, and it will not let me boot to recovery still.....Back to the boot loops
Edit: First time I must have selected clear storage by mistake. Anyway I hit no at that point. I just re-dl'd the pc36img.zip file to make sure. It does run in the boot loader but will not reboot to recovery. Still endless loop????
splink7007 said:
Ok, I got it to see it. I ran the update, once it rebooted I selected recovery. It first asked me if I want to delete data? Or something on those terms. I chose no, and it will not let me boot to recovery still.....Back to the boot loops
Click to expand...
Click to collapse
Considering you can't get into recovery still, I would suggest reflashing the recovery and erasing the data when prompted.
Did you do a nandroid backup? I only ask cause once you get back into recovery you can just restore that.
so the bootloader read the file, then you ran the update and then it asked you to delete data? I don't remember that being a part of the process. Try it again and as soon as it's done updating try to get into the recovery again. If not then try to use adb.
sekigah84 said:
Considering you can't get into recovery still, I would suggest reflashing the recovery and erasing the data when prompted.
Did you do a nandroid backup? I only ask cause once you get back into recovery you can just restore that.
Click to expand...
Click to collapse
Ya I hit clear storage at first by mistake. I believe if I hit that it will wipe my entire sd card and will loose my nand backup?
mich11128 said:
so the bootloader read the file, then you ran the update and then it asked you to delete data? I don't remember that being a part of the process. Try it again and as soon as it's done updating try to get into the recovery again. If not then try to use adb.
Click to expand...
Click to collapse
Re-ran the update and still loops. The first time I ran it I hit clear storage instead recovery by mistake. Im sitting at the bootloader screen. I cant remember the adb commands. Can you refresh my memory? Thanks
Copy recovery-RA-supersonic-v2.3.img to the root of your sdcard
start the terminal app or launch adb shell
su(press enter)
flash_image recovery /sdcard/recovery-RA-supersonic-v2.3.img(press enter)
reboot recovery(press enter)
I find it strange that all this happened after getting off the phone with Sprint lol.
Does it still say S-OFF at the top of your bootloader?
I copied this from the amon ra recovery thread
Copy recovery-RA-supersonic-v2.3.img to the root of your sdcard
start the terminal app or launch adb
su(press enter)
flash_image recovery /sdcard/recovery-RA-supersonic-v2.3.img(press enter)
reboot recovery(press enter
now whenever I am about to start adb I use the command "./adb devices" without quotations of course, to make sure adb recognizes my evo oh and ignore the ./ that's just for mac users. When you enter that command you should see the serial number for your evo. after that I use
./adb shell
that should lead to
#
Then you type
su
and then you enter the rest of the commands. Sorry I didn't really organize it but that's pretty much it.
sekigah84 said:
Copy recovery-RA-supersonic-v2.3.img to the root of your sdcard
start the terminal app or launch adb shell
su(press enter)
flash_image recovery /sdcard/recovery-RA-supersonic-v2.3.img(press enter)
reboot recovery(press enter)
I find it strange that all this happened after getting off the phone with Sprint lol.
Does it still say S-OFF at the top of your bootloader?
Click to expand...
Click to collapse
lol you beat me to it and I was also about to ask if the phone was still rooted. READ MY MIND hahaha
sekigah84 said:
Copy recovery-RA-supersonic-v2.3.img to the root of your sdcard
start the terminal app or launch adb shell
su(press enter)
flash_image recovery /sdcard/recovery-RA-supersonic-v2.3.img(press enter)
reboot recovery(press enter)
I find it strange that all this happened after getting off the phone with Sprint lol.
Does it still say S-OFF at the top of your bootloader?
Click to expand...
Click to collapse
I totally agree!! Crazy....Yes it still says S-OFF. How do I launch adb shell from the bootloader? Im sorry, I havent used adb or fastboot since launch rooting using toasts method.
Wish I could help you there but I haven't ran adb on a windows since my G1 lol I'll see if I find a thread with some help for adb and windows.
EDIT: Maybe this will help. http://forum.xda-developers.com/showthread.php?t=694250
Ok, if I run fastboot devices, it sees my device. But if I run adb devices, it doesnt see my device anymore. Im soo lost now.
sorry I forgot adb runs through recovery, what you have to use I believe is fastboot flash to flash the recovery image
here try this page better...I used this when I had to root my nexus one the hard way (before that crappy 1-click method was devised) this is the best guide I'd ever used as far as adb/fastboot commands.
http://forum.xda-developers.com/showthread.php?t=694250
Hi!
I think my /data partition is corrupt. Anytime I flash a new ROM, a handlful of apps I've previously installed are preloaded when then ROM first boots up. I've wiped my dalvik cache, superwiped multiple times, and did a factory reset multiple times, but no matter what ROM i install (JB, CM7, MIUI, Original Sense [Liberation]), those apps are still there, and causes forces closes.
So I went into CWM, and tried to manually format the /data partition and I get the "Error formatting /data" For that matter, this same error happens when I try to format /cache.
I've trired multile ROMs, multiple kernels. I've triend Amon Ra, (I couldn't install TWRP because of a status 7 error). I've deleted the /data folder through adb/fastboot (and it reappears afterwards).Like I said, I've done factory resets, tried formatting each partition (both with the partitions mounted and unmounted), superwipe, fixed permissions..I'm at a complete loss on what to do next. I'm willing to erase everything entirely from the phone and start from scratch if I have to, but I have no access to do anything. Did I brick my phone? I had previously used the EXT4 mod, but I've ran the zips to revert to normal already.
Leshy01 said:
Hi!
I think my /data partition is corrupt. Anytime I flash a new ROM, a handlful of apps I've previously installed are preloaded when then ROM first boots up. I've wiped my dalvik cache, superwiped multiple times, and did a factory reset multiple times, but no matter what ROM i install (JB, CM7, MIUI, Original Sense [Liberation]), those apps are still there, and causes forces closes.
So I went into CWM, and tried to manually format the /data partition and I get the "Error formatting /data" For that matter, this same error happens when I try to format /cache.
I've trired multile ROMs, multiple kernels. I've triend Amon Ra, (I couldn't install TWRP because of a status 7 error). I've deleted the /data folder through adb/fastboot (and it reappears afterwards).Like I said, I've done factory resets, tried formatting each partition (both with the partitions mounted and unmounted), superwipe, fixed permissions..I'm at a complete loss on what to do next. I'm willing to erase everything entirely from the phone and start from scratch if I have to, but I have no access to do anything. Did I brick my phone? I had previously used the EXT4 mod, but I've ran the zips to revert to normal already.
Click to expand...
Click to collapse
First off, i am unaware of a script that reverts the ext4 mods, where did you get it from? First i would try an ruu, if that dosent fix it, i would try fastboot flashing the misc partition, and then do the froyo ruu and reroot. Are you s-off? What radio and hboot version?
cmlusco said:
First off, i am unaware of a script that reverts the ext4 mods, where did you get it from? First i would try an ruu, if that dosent fix it, i would try fastboot flashing the misc partition, and then do the froyo ruu and reroot. Are you s-off? What radio and hboot version?
Click to expand...
Click to collapse
Thanks for the quick reply! I guess I should clarify regarding ext4. I used the "no_data_limit_dalvik_moved" mod to move the unused datadata partition for my /data/dalvik-cache folder. Seeing as how the ext4 modifies the /data AND /cache partitions, and those are the only two that are giving me trouble, I'm thinking that might be the cause of my troubles.
Haven't tried an ruu yet so that'll be my next step. But what do you mean by flashing the "misc" partition? I'm at work so I'll have to try that when I get home. Might have to look up how to flash the ruu too. It's been a while. lol
Am I s-off? Yes.
Radio? 2.15.10.07.07
hboot: 0.92.0000
Edit: So I tried flashing both RUUs (PB31IMG version) Gingerbread AND froyo found here. With both instances, the phone would freeze on the boot image. (Where is says DROID, then those little red dots circle the middle camera twice).It reset and continues to bootloop over and over.
Leshy01 said:
Thanks for the quick reply! I guess I should clarify regarding ext4. I used the "no_data_limit_dalvik_moved" mod to move the unused datadata partition for my /data/dalvik-cache folder. Seeing as how the ext4 modifies the /data AND /cache partitions, and those are the only two that are giving me trouble, I'm thinking that might be the cause of my troubles.
Haven't tried an ruu yet so that'll be my next step. But what do you mean by flashing the "misc" partition? I'm at work so I'll have to try that when I get home. Might have to look up how to flash the ruu too. It's been a while. lol
Am I s-off? Yes.
Radio? 2.15.10.07.07
hboot: 0.92.0000
Edit: So I tried flashing both RUUs (PB31IMG version) Gingerbread AND froyo found here. With both instances, the phone would freeze on the boot image. (Where is says DROID, then those little red dots circle the middle camera twice).It reset and continues to bootloop over and over.
Click to expand...
Click to collapse
Ok do you have adb and fastboot setup on a pc, you will need it to flash the misc partition? It sounds like your partition tables may have gotten messed up. The misc partition is where this info is stored. If or when you have adb fastboot and their drivers installed, i will tell you how to flash misc. Also in the meantime, try flashing this ruu just for kicks http://dinc.does-it.net/Stock_Images/4.08.605.15/PB31IMG.zip.
cmlusco said:
Ok do you have adb and fastboot setup on a pc, you will need it to flash the misc partition? It sounds like your partition tables may have gotten messed up. The misc partition is where this info is stored. If or when you have adb fastboot and their drivers installed, i will tell you how to flash misc. Also in the meantime, try flashing this ruu just for kicks http://dinc.does-it.net/Stock_Images/4.08.605.15/PB31IMG.zip.
Click to expand...
Click to collapse
Thanks! I have adb/fastboot on my home pc, yea. So you can tell me what to do, then I'll get home and try it, and then post results. I'll try that ruu as well and let you know. I tried following some direction online usin parted, but I couldn't make heads or tails of which partition was which.
Leshy01 said:
Thanks! I have adb/fastboot on my home pc, yea. So you can tell me what to do, then I'll get home and try it, and then post results. I'll try that ruu as well and let you know. I tried following some direction online usin parted, but I couldn't make heads or tails of which partition was which.
Click to expand...
Click to collapse
After you run that ruu i posted, your hboot version should be updated to 1.07. You will then need to go to http://www.htcdev.com/bootloader, and follow the steps to unlock your bootloader. Skip the first couple parts where it has you set up fastboot and skip the bootloader update part (ruu) and start where it has you get a code from your phone (Unlock token). Finish the rest, of the unlock steps and you will see at the top of hboot it now says unlocked.
Once unlocked download this file http://dinc.does-it.net/Guide_Root_New_Hboot/mtd0.img, and place it on your pc in the same folder as the fastboot.exe file. Then boot the phone to hboot, and connect it to the pc, and select fastboot from the hboot menu, so that it says fastboot plug in red at the top. Open a cmd prompt on your pc to where fastboot.exe is, and type the folowing:
Code:
fastboot devices
It should show a string of numbers. If it says no devices found, something is wrong with the connection between the phone and pc, or the adb drivers are not setup right on the pc.
If the connections fine and it found your device then type :
Code:
fastboot flash misc mtd0.img
Now download this ruu http://dinc.does-it.net/Stock_Images/3.26.605.1/PB31IMG.zip, and flash it thru hboot. Once it compleets reboot, and hopefully it boots up like it should.
If it does boot and all is well, then reroot by flashing cwm http://dinc.does-it.net/Recoveries/CWM_5.0.2.0/PB31IMG.zip thru hboot, and then flash superuser http://dinc.does-it.net/Superuser/SuperUser_3.1.1.zip, thru recovery. From there you can flash a rom of your choosing.
cmlusco, you get thanks for being so willing to help other members with their issues. I think you deserve more than I gave you today but I think it's cool how you're always trying to help people with potential bricks and when you tested out kernels and such for me.
tiny4579 said:
cmlusco, you get thanks for being so willing to help other members with their issues. I think you deserve more than I gave you today but I think it's cool how you're always trying to help people with potential bricks and when you tested out kernels and such for me.
Click to expand...
Click to collapse
Thanks tiny, you do great work yourself. I like helping people and i love technical stuff. Knowledge is everything, and its good to pass it on.
cmlusco said:
After you run that ruu i posted, your hboot version should be updated to 1.07. You will then need to go to http://www.htcdev.com/bootloader, and follow the steps to unlock your bootloader. Skip the first couple parts where it has you set up fastboot and skip the bootloader update part (ruu) and start where it has you get a code from your phone (Unlock token). Finish the rest, of the unlock steps and you will see at the top of hboot it now says unlocked.
Once unlocked download this file http://dinc.does-it.net/Guide_Root_New_Hboot/mtd0.img, and place it on your pc in the same folder as the fastboot.exe file. Then boot the phone to hboot, and connect it to the pc. Open a cmd prompt on your pc to where fastboot.exe is, and type the folowing:
Code:
adb devices
It should show a string of numbers. If it says no devices found, something is wrong with the connection between the phone and pc, or the adb drivers are not setup right on the pc.
If the connections fine and it found your device then type :
Code:
fastboot flash misc mtd0.img
Now download this ruu http://dinc.does-it.net/Stock_Images/3.26.605.1/PB31IMG.zip, and flash it thru hboot. Once it compleets reboot, and hopefully it boots up like it should.
If it does boot and all is well, then reroot by flashing cwm http://dinc.does-it.net/Recoveries/CWM_5.0.2.0/PB31IMG.zip thru hboot, and then flash superuser http://dinc.does-it.net/Superuser/SuperUser_3.1.1.zip, thru recovery. From there you can flash a rom of your choosing.
Click to expand...
Click to collapse
Curiously, I've only gotten as far as "adb devices" Although I can perform "fastboot reboot" and "fastboot devices" I try "adb devices" and the list is blank. I've used the drivers included in the android sdk. I've also used the drivers from htc sync. I don't know why I can't find my device in adb though. To be clear, my phone says "HBOOT USB PLUG" while I'm trying this.
thank you so much by the way for all your help. And you too tiny. I feel like I'm standing on the shoulders of giants here!
Also, is there some irc channel or something with a bit less idle time between forum posts?
Leshy01 said:
Curiously, I've only gotten as far as "adb devices" Although I can perform "fastboot reboot" and "fastboot devices" I try "adb devices" and the list is blank. I've used the drivers included in the android sdk. I've also used the drivers from htc sync. I don't know why I can't find my device in adb though. To be clear, my phone says "HBOOT USB PLUG" while I'm trying this.
thank you so much by the way for all your help. And you too tiny. I feel like I'm standing on the shoulders of giants here!
Also, is there some irc channel or something with a bit less idle time between forum posts?
Click to expand...
Click to collapse
Oops, i ment to put for you to type fastboot devices not adb devices in those instructions, that was just a mistake on my part. I dont think you can even access adb from hboot. As long as fastboot devices works your good to go. Also you will want to select fastboot from the bootloader menu after connecting the phone. So it should say fastboot plug in red not usb plug in blue when entering the commands.
I do not know of an irc channel, and i like to keep the conversation here so that the instructions and common issues and fixes can be seen and learned from by others.
cmlusco said:
Oops, i ment to put for you to type fastboot devices not adb devices in those instructions, that was just a mistake on my part. I dont think you can even access adb from hboot. As long as fastboot devices works your good to go. Also you will want to select fastboot from the bootloader menu after connecting the phone. So it should say fastboot plug in red not usb plug in blue when entering the commands.
Click to expand...
Click to collapse
Oh well in that case I get an entirely different issue. "Fastboot devices" works but when I try the flash command you suggested:
Code:
sending 'misc' (640 KB)...
OKAY [ 0.119s]
writing 'misc'...
FAILED (remote: not allowed)
finished. total time: 0.129s
Man, talk about frustrating.
Leshy01 said:
Oh well in that case I get an entirely different issue. "Fastboot devices" works but when I try the flash command you suggested:
Code:
sending 'misc' (640 KB)...
OKAY [ 0.119s]
writing 'misc'...
FAILED (remote: not allowed)
finished. total time: 0.129s
Man, talk about frustrating.
Click to expand...
Click to collapse
Did you unlock the bootloader with htc dev? Does it say unlocked at the top of hboot?
cmlusco said:
Did you unlock the bootloader with htc dev? Does it say unlocked at the top of hboot?
Click to expand...
Click to collapse
Yep. *** Unlocked *** in pink at the top.
HBOOT 1.07.000
And my screen says FASTBOOT USB in red. When I enter "fastboot devices" I get HT0B2HJ05729 fastboot, so I know that works. As does commans like reboot.
Leshy01 said:
Yep. *** Unlocked *** in pink at the top.
HBOOT 1.07.000
And my screen says FASTBOOT USB in red. When I enter "fastboot devices" I get HT0B2HJ05729 fastboot, so I know that works. As does commans like reboot.
Click to expand...
Click to collapse
Hmm thats strange having the boooader unlocked should allow remote. Mabey thats not allowed, i thought it was. Sorry let me dig up some info i believe there is another way.
---------- Post added at 12:44 AM ---------- Previous post was at 12:17 AM ----------
Ok download this http://dinc.does-it.net/Guide_Root_New_Hboot/recovery.img and place it on your pc where fastboot.exe is and open the cmd prompt and type:
Code:
fastboot flash recovery recovery.img
And then reboot the phone to the bootloader again and go to recovery and flash this http://dinc.does-it.net/Superuser/SuperUser_3.1.1.zip. Just for kicks see if you can mount data or cache from the mounts and storage menu. If you can your issue is probably fixed, if not try this. Download and unzip these files http://dinc.does-it.net/Guide_Root_New_Hboot/flash_mtd.zip and place both of them in the same folder on your pc as adb.exe. Then while in recovery with the phone connected open a cmd promt to where adb is and type the following hitting enter after each line:
Code:
adb push flash_image /system/
adb push mtd0.img /sdcard/
adb shell (you should get a prompt with a # sign)
cd /system
chmod 0755 /systeml/flash_image
cd /system
./flash_image misc /sdcard/mtd0.img
exit
adb reboot recovery
In recovery go to mounts and storage and mount usb storrage and place this ruu http://dinc.does-it.net/Stock_Images/3.26.605.1/PB31IMG.zip on the sdcard. Then in your cmd prompt type:
Code:
adb reboot bootloader
Once in hboot, select bootloader from the menu amd wait a few secs for it to find the ruu and pronpt you to flash it.
cmlusco said:
Hmm thats strange having the boooader unlocked should allow remote. Mabey thats not allowed, i thought it was. Sorry let me dig up some info i believe there is another way.
---------- Post added at 12:44 AM ---------- Previous post was at 12:17 AM ----------
Ok download this http://dinc.does-it.net/Guide_Root_New_Hboot/recovery.img and place it on your pc where fastboot.exe is and open the cmd prompt and type:
Code:
fastboot flash recovery recovery.img
And then reboot the phone to the bootloader again and go to recovery and flash this http://dinc.does-it.net/Superuser/SuperUser_3.1.1.zip. Just for kicks see if you can mount data or cache from the mounts and storage menu. If you can your issue is probably fixed, if not try this. Download and unzip these files http://dinc.does-it.net/Guide_Root_New_Hboot/flash_mtd.zip and place both of them in the same folder on your pc as adb.exe. Then while in recovery with the phone connected open a cmd promt to where adb is and type the following hitting enter after each line:
Code:
adb push flash_image /system/
adb push mtd0.img /sdcard/
adb shell (you should get a prompt with a # sign)
cd /system
chmod 0755 /systeml/flash_image
cd /system
./flash_image misc /sdcard/mtd0.img
exit
adb reboot recovery
In recovery go to mounts and storage and mount usb storrage and place this ruu http://dinc.does-it.net/Stock_Images/3.26.605.1/PB31IMG.zip on the sdcard. Then in your cmd prompt type:
Code:
adb reboot bootloader
Once in hboot, select bootloader from the menu amd wait a few secs for it to find the ruu and pronpt you to flash it.
Click to expand...
Click to collapse
So I was able to complete all your steps without getting any errors. After flashing superuser, I still couldn't format /data or /cache (mounting was never an issue - or at least I wasn't given any errors about it before) However however after flashing the stock ROM, I am still getting the bootloop. I can't check the /data and /cache partition since its no longer running CWM though, but this is the same scenario I was in previously. I'm sure I'm giving you a challange here. Is there a way to manually re-partition everything manually, instead of just formatting?
So like I said, I ran the steps provided above, and still got the bootloop. So I flashed CWM and same as before, I am unable to format the /data and /cache partitions.:/
Leshy01 said:
So I was able to complete all your steps without getting any errors. After flashing superuser, I still couldn't format /data or /cache (mounting was never an issue - or at least I wasn't given any errors about it before) However however after flashing the stock ROM, I am still getting the bootloop. I can't check the /data and /cache partition since its no longer running CWM though, but this is the same scenario I was in previously. I'm sure I'm giving you a challange here. Is there a way to manually re-partition everything manually, instead of just formatting?
So like I said, I ran the steps provided above, and still got the bootloop. So I flashed CWM and same as before, I am unable to format the /data and /cache partitions.:/
Click to expand...
Click to collapse
Im not sure. If there is a program or a way to manually fix the partitions, i am unaware and it is probably over my head.
Flashing the misc partition should have fixed any errors with the partition table. The fact that it didnt fix it leads me to believe that the partitions are fubar.
One thing bugs me though, you said earlier that you never had an issue mounting the partitions, just formating them. So can you mount data in recovery, and then view its contents or pull and push with adb?
Leshy01 said:
So I was able to complete all your steps without getting any errors. After flashing superuser, I still couldn't format /data or /cache (mounting was never an issue - or at least I wasn't given any errors about it before) However however after flashing the stock ROM, I am still getting the bootloop. I can't check the /data and /cache partition since its no longer running CWM though, but this is the same scenario I was in previously. I'm sure I'm giving you a challange here. Is there a way to manually re-partition everything manually, instead of just formatting?
So like I said, I ran the steps provided above, and still got the bootloop. So I flashed CWM and same as before, I am unable to format the /data and /cache partitions.:/
Click to expand...
Click to collapse
Parted. It already exists in recovery and can be run in adb in recovery. Try that. I can't give directions but be careful. I think I tried to help someone before with this but can't recall the thread. It'd b a good starting point.
Sent from my Galaxy Nexus using Tapatalk 2
cmlusco said:
Im not sure. If there is a program or a way to manually fix the partitions, i am unaware and it is probably over my head.
Flashing the misc partition should have fixed any errors with the partition table. The fact that it didnt fix it leads me to believe that the partitions are fubar.
One thing bugs me though, you said earlier that you never had an issue mounting the partitions, just formating them. So can you mount data in recovery, and then view its contents or pull and push with adb?
Click to expand...
Click to collapse
Well... I'm sketchy on the exact terms here, but In CWM, I can mount the drives without getting any errors, but whenI try to format I get errors. I haven't actually "done" anything with those partition besides that.
However. I ran through ALL the steps you had me to. Flash the stock ROM w/ recovery, unlocked bootloader from HTC, pushed all the filies you had me through adb. After all that, I flashed CWM, then I flashed CM7, and then I booted up my device. As if my /data partition was not touched, all my apps were still there (titanium backup, my google accounts were still setup, app data and settings were untouched). So on a whim, I ran titanium backup, and uninstalled every single user app (since the android native uninstaller force closes). I ran it successfully, rebooted, and every other app was still there.
So it can READ the /data partition, but I have no abilities to MODIFY that partition. Through any recovery or formatting.
tiny4579 said:
Parted. It already exists in recovery and can be run in adb in recovery. Try that. I can't give directions but be careful. I think I tried to help someone before with this but can't recall the thread. It'd b a good starting point.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
I'm willing to try anything because at this point nother else works, but I don't know where to start. And even if I find some documentation about other devices' partition table setup, I'm assuming the Incredible is different. Way I see it, I can't mess it up any more than it already is.
I'm hoping you guys have some sort of answer, but I'm looking around elsewhere, and I really appreciate everything you guys have contributed to this thread, and the community. Thanks!!!!!
Hi guys,
I have the same issue (with a galaxy s2 though), anything related to the partition /data is causing me troubles since I first tried to wipe it when I wanted to install CM9.1. (and I had stock ICS 4.0.4 at the time...)
Do you think it is the mmc bug ?
I can enter DL mode but when I try to flash stock rom, it just remains at the animated boot logo for hours...
Tried also to flash rom (with CODE, MODEM, CSC) and Odin stays stuck when starting DATA...
Any luck on your side ?
megosu said:
Hi guys,
I have the same issue (with a galaxy s2 though), anything related to the partition /data is causing me troubles since I first tried to wipe it when I wanted to install CM9.1. (and I had stock ICS 4.0.4 at the time...)
Do you think it is the mmc bug ?
I can enter DL mode but when I try to flash stock rom, it just remains at the animated boot logo for hours...
Tried also to flash rom (with CODE, MODEM, CSC) and Odin stays stuck when starting DATA...
Any luck on your side ?
Click to expand...
Click to collapse
I don't think the mmc bug has anything to do with the Droid Incredible or even affects it. I thought the mmc bug led to a fully bricked phone.
This isn't really the thread for this but have you tried the full Odin Factory reset for your device which includes the /data partition? I think the method that uses a PIT file is the most thorough but most risky. I recommend posting any questions in your device's thread but I've had a few samsungs and am somewhat familiar with that process.
My Galaxy Nexus reboots a few seconds after starting up. I don't have anything other than stock installed and I've tried following several guides here trying to flash it myself since the built-in recovery mode wipe data/factory reset does nothing.
I did notice something strange which following a guide, when I oem unlock and reboot the fastboot mode it locks itself again like I didn't do anything at all. This was a problem when I was using the Android Toolkit too but I managed to over ride my own fastboot oem unlock commands in between its batch file commands and got to an error "FAIL Exceed Buffer Size"
I believe if I can fix or know what to do with that error I can successfully bring my phone back to factory defaults I just don't know what to do! I tried looking for the error on this forum and it came up with 0 results and google isn't helping much either.
I'd appreciate any help regarding this, even if it means my phone is beyond repair I just want to know!
Thanks guys!
celeadyne said:
My Galaxy Nexus reboots a few seconds after starting up. I don't have anything other than stock installed and I've tried following several guides here trying to flash it myself since the built-in recovery mode wipe data/factory reset does nothing.
I did notice something strange which following a guide, when I oem unlock and reboot the fastboot mode it locks itself again like I didn't do anything at all. This was a problem when I was using the Android Toolkit too but I managed to over ride my own fastboot oem unlock commands in between its batch file commands and got to an error "FAIL Exceed Buffer Size"
I believe if I can fix or know what to do with that error I can successfully bring my phone back to factory defaults I just don't know what to do! I tried looking for the error on this forum and it came up with 0 results and google isn't helping much either.
I'd appreciate any help regarding this, even if it means my phone is beyond repair I just want to know!
Thanks guys!
Click to expand...
Click to collapse
best advice,flash back to stock,root the phone,and use bootunlock on your phone to unlock it,it wont wipe your data,then download a recovery.img and flash it with the flashify app,almost everything done with apps and no data loss.
pattyboi:) said:
best advice,flash back to stock,root the phone,and use bootunlock on your phone to unlock it,it wont wipe your data,then download a recovery.img and flash it with the flashify app,almost everything done with apps and no data loss.
Click to expand...
Click to collapse
I can't flash the phone to stock because of that FAIL error, and I can't root the phone because it reboot loops before I can enable USB debugging in the OS.
celeadyne said:
I can't flash the phone to stock because of that FAIL error, and I can't root the phone because it reboot loops before I can enable USB debugging in the OS.
Click to expand...
Click to collapse
i mean not using toolkit,using actual fasboot. BTW: do you have a custom recovery? if so you could just adb sideload & if you can get the phone into fastboot mode and just flash a recovery then adb sideload after wiping all partitions && did you try using odin to flash back to stock (i dunno if there are odin images available,i apoligize if not)
My new Asus Zenfone 2 stacked in wiping cache screen in recovery...
unable to do recovery, normal boot
and i think i cant even charge it in this situation...:crying:
manager21 said:
My new Asus Zenfone 2 stacked in wiping cache screen in recovery...
unable to do recovery, normal boot
and i think i cant even charge it in this situation...:crying:
Click to expand...
Click to collapse
My ZenFone 2 also got stuck at wiping case for 10 min or more I thought I should interrupt the process but luckily I left for some more minutes and got unstuck, it takes a lot of time for this phone to wipe case.
try holding power plus volume up for 15 sec to do a hard shut down and open it again.
if it doesn't work try volume down.
It wasn't stuck. The wiping process is just extremely slow compared to your experience with TWRP or CWM. If yours is bricked Asus will likely replace it for you.
"I'd Totally Hug You, If That Was Something I Did"
Ace42 said:
It wasn't stuck. The wiping process is just extremely slow compared to your experience with TWRP or CWM. If yours is bricked Asus will likely replace it for you.
"I'd Totally Hug You, If That Was Something I Did"
Click to expand...
Click to collapse
no. it was stack because i wasnt patient and i stop it... but i fixed it with ADB Fastboot and the command "fastboot erase cache"
then i did a factory reset also very slow at wiping data, formatting data but i take my lesson and i was patient this time!
It's really slow, I bricked mine by updating while rooted accidentally and go stuck in fastboot with no ROM or recovery for a while however I managed to fix it. Patience is key in most cases
Pilz said:
It's really slow, I bricked mine by updating while rooted accidentally and go stuck in fastboot with no ROM or recovery for a while however I managed to fix it. Patience is key in most cases
Click to expand...
Click to collapse
I brick my phone like you. Now I can use fastboot but not ADB and don't have unlocked bootloader. How can I fix my zenfone?:crying:
Eruz said:
I brick my phone like you. Now I can use fastboot but not ADB and don't have unlocked bootloader. How can I fix my zenfone?:crying:
Click to expand...
Click to collapse
If you can enter fastboot, I think you can also enter recovery.
- If you don't care about your data enter recovery and do a wipe data (it may take very very long so please wait). When it reboots, if it's not working flash the original image from Asus site (the same version you have installed) via ADB Sideload in recovery.
- If you have to save your data run tethered TWRP, do a full backup on your microsd, use the TWRP file manager to copy all your internal memory on microsd. For recover apps data, use Titanium backup for recover apps from nandroid backup after you wiped everyting.
marcof93 said:
If you can enter fastboot, I think you can also enter recovery.
- If you don't care about your data enter recovery and do a wipe data (it may take very very long so please wait). When it reboots, if it's not working flash the original image from Asus site (the same version you have installed) via ADB Sideload in recovery.
- If you have to save your data run tethered TWRP, do a full backup on your microsd, use the TWRP file manager to copy all your internal memory on microsd. For recover apps data, use Titanium backup for recover apps from nandroid backup after you wiped everyting.
Click to expand...
Click to collapse
I don't care about data, I'll try first method. But before I bricked my phone, I have firmware version 2.18. Now I update boot and recovery images to version 2.19 by fastboot: I have to downgrade them before wipe data or it's not important?
Eruz said:
I don't care about data, I'll try first method. But before I bricked my phone, I have firmware version 2.18. Now I update boot and recovery images to version 2.19 by fastboot: I have to downgrade them before wipe data or it's not important?
Click to expand...
Click to collapse
Enter fastboot and connect your phone to pc. If you have adb installed and intel drivers, after connect your phone to pc while in fastboot, open cmd and type: Fastboot erase cache
It will go back to normal after
It stuck on the boot animation with animated ring by 40 minutes. I have to wait more? Is there another way to fix it (like flashing with Odin as a couple of years ago)?
I have already wipe cache, data and all wipeable things
Thanks guys
Eruz said:
It stuck on the boot animation with animated ring by 40 minutes. I have to wait more? Is there another way to fix it (like flashing with Odin as a couple of years ago)?
I have already wipe cache, data and all wipeable things
Thanks guys
Click to expand...
Click to collapse
Just press power button until phone turns off. After that enter fastboot and do what I told you
sirsomething said:
Just press power button until phone turns off. After that enter fastboot and do what I told you
Click to expand...
Click to collapse
I know that but what will I do? I already try to wipe that partitions and the phone is still bricked. Sorry for my bad english, dude.
Eruz said:
I know that but what will I do? I already try to wipe that partitions and the phone is still bricked. Sorry for my bad english, dude.
Click to expand...
Click to collapse
Did you get stuck on bootloader after wiping the cache?
sirsomething said:
Did you get stuck on bootloader after wiping the cache?
Click to expand...
Click to collapse
Yep, for 40 minutes. I wiped it again and restart but nothing changes.
Eruz said:
Yep, for 40 minutes. I wiped it again and restart but nothing changes.
Click to expand...
Click to collapse
Can you enter Recovery or only fastboot?
sirsomething said:
Can you enter Recovery or only fastboot?
Click to expand...
Click to collapse
I can enter stock recovery and fastboot, but not ADB
Eruz said:
I can enter stock recovery and fastboot, but not ADB
Click to expand...
Click to collapse
ADB is installed on your computer and you enter via command line. How can you not acess it? It is just opening the command line and write the code i told you
sirsomething said:
ADB is installed on your computer and you enter via command line. How can you not acess it? It is just opening the command line and write the code i told you
Click to expand...
Click to collapse
ADB doesn't recognize my device, fastboot does. I enabled USB debugging mode and ADB always worked before I updated Zenfone this morning, but now don't. Is it possible enable 'Update zip from SDCard' instead ADB? Maybe I can fix it in this way
PS before Zenfone I had a Galaxy Nexus and I have a bit of confident with ADB, fastboot, ROM and other stuff, so I know what they are and how work
Eruz said:
ADB doesn't recognize my device, fastboot does. I enabled USB debugging mode and ADB always worked before I updated Zenfone this morning, but now don't. Is it possible enable 'Update zip from SDCard' instead ADB? Maybe I can fix it in this way
PS before Zenfone I had a Galaxy Nexus and I have a bit of confident with ADB, fastboot, ROM and other stuff, so I know what they are and how work
Click to expand...
Click to collapse
Sorry for the misunderstanding then. I don't think i can help you in that case :x have you tried to reinstall intel drivers or something?
sirsomething said:
Sorry for the misunderstanding then. I don't think i can help you in that case :x have you tried to reinstall intel drivers or something?
Click to expand...
Click to collapse
Yep, unistalled all Intel, Asus or Google driver and then reinstalled Intel driver. I think if I can installed custom bootlader ADB will be enabled.
Btw thanks man :highfive::highfive:
since this fone was having this issue i decided to try and restore from a working backup:
http://forum.xda-developers.com/g4/help/unable-to-make-phone-calls-dialer-t3278827
i am starting to think that this fones hardware is broken/defective somehow. the key combo to boot into recovery never works.
its supposed to be power+volume-down but it just boots normally.
power+vol-down/release power for 1 second goes into the erase all data: yes/no screen.
whether using android-5.1 or cyanogenmod, adb devices returns nothing; we tried on both windows and fedora; we enabled developer options/adb debugging/oem unlock.
so to test whether the original os could make fone calls i did a twrp wipe/restore of a previous backup. when it booted up it was very unstable/unusable; took a few minutes to respond to touches sometimes; process system has quit errors; random restarts; ...
no apps could launch so that meant i couldnt use quick boot to reboot recovery. adb and key combos dont work so there was no way to get back into recovery.
i put the fone in download mode (volume-up while plugging in usb) and we used LGUP_8994_DLL_Ver_0_0_3_23.msi/LGUP_Store_Frame_Ver_1_14_3.msi to install H81120i_00_0201.kdz which is the lg version of googles version of android-6.0. and we were able to make a fone call. we wanted to boot into twrp to backup but quick boot said that we are no longer rooted. ironically, adb devices now shows the serial-number of the fone so i did sudo adb reboot recovery but when it rebooted instead of going to twrp it showed a green android with a spinning blue cube thingy and rebooted into lg/google-android-6.0 where i had to sign/register for the first time and all our apps/settings were gone.
we origianlly installed twrp using the send_command.exe command on windows awhile back but it no longer works. we installed LGUnitedMobile_Win_Driver_Ver_3.14.1.exe; i run ports.bat and it tells me that the diag port is on COM5; i run Send_command \\.\COM5; it shows me the linux su prompt: #, but when i type in ENTER, it exits back to the windows-dos prompt (i also tried without first typing ENTER, if i try to run something like ls or whoami, it will display: fail).
do all these models have adb/recovery disabled or is this particular unit fubar in that regard ?
any alternative ways to install twrp/ cyanogenmod ?
It is my understanding according to autoprime's thread that you must reinstall twrp after you install the kdz as it wipes that partition as well.
bbenz3 said:
It is my understanding according to autoprime's thread that you must reinstall twrp after you install the kdz as it wipes that partition as well.
Click to expand...
Click to collapse
thanks, how does one install twrp without using send_command.exe.