Completed the following successfully on my Wildfire S 510c:
Unlocked
Installed CWM v5.0.2.6
Rooted
I wanted to find a way to either move the whole system to the SD card or to increase the Internal memory using the SD card.
I found a guide here explaining how to increase the internal memory using SD card, but after following the instructions to the T my phone hangs up on the white screen with HTC logo every time.
To make matters worse, the partitioned portion of the SD card cannot be seen in windows explorer when I try to access the SD via CWM, only the portion that was left over. I fear that since this problem occurred right after I installed cm-7-20120717-UNOFFICIAL-marvel recovery over the previous CWM I had and the Data2SDInstallerNXE2 I'm speculating 1 of 2 things have occurred: Either the Unofficial CWM is corrupted (All functions work properly inside recovery) or an error occurred where the system files were not properly copied into the newly created partition and so it tries to boot system from empty space.
I'm at a total loss where to go from here. I don't know of any free programs that can see all the partitions of the SD card where Windows cannot, let alone unpartition it, and even then how to set it back up to where it boots up where it needs to. I've tried to reinstall the previous CWM I had via zip installer but it give an "Installation Aborted".
Someone plz halp! lol
Ok, I found that under SD partition in CWM if you select different partition size it will remove the old partition, this still doesn't fix the hangup though.
Now it doesn't hang up, but keeps going back to bootloader screen. I think I should stop before it get worse and wait for a response. XD
Tried flashy method in an attempt to set phone back to locked and unrooted status. Only thing it did was set phone in relocked status. I'm taking a break for awhile, spent too many hours on this ><
LyleVertigo said:
Completed the following successfully on my Wildfire S 510c:
Unlocked
Installed CWM v5.0.2.6
Rooted
I wanted to find a way to either move the whole system to the SD card or to increase the Internal memory using the SD card.
I found a guide here explaining how to increase the internal memory using SD card, but after following the instructions to the T my phone hangs up on the white screen with HTC logo every time.
To make matters worse, the partitioned portion of the SD card cannot be seen in windows explorer when I try to access the SD via CWM, only the portion that was left over. I fear that since this problem occurred right after I installed cm-7-20120717-UNOFFICIAL-marvel recovery over the previous CWM I had and the Data2SDInstallerNXE2 I'm speculating 1 of 2 things have occurred: Either the Unofficial CWM is corrupted (All functions work properly inside recovery) or an error occurred where the system files were not properly copied into the newly created partition and so it tries to boot system from empty space.
I'm at a total loss where to go from here. I don't know of any free programs that can see all the partitions of the SD card where Windows cannot, let alone unpartition it, and even then how to set it back up to where it boots up where it needs to. I've tried to reinstall the previous CWM I had via zip installer but it give an "Installation Aborted".
Someone plz halp! lol
Ok, I found that under SD partition in CWM if you select different partition size it will remove the old partition, this still doesn't fix the hangup though.
Now it doesn't hang up, but keeps going back to bootloader screen. I think I should stop before it get worse and wait for a response. XD
Tried flashy method in an attempt to set phone back to locked and unrooted status. Only thing it did was set phone in relocked status. I'm taking a break for awhile, spent too many hours on this ><
Click to expand...
Click to collapse
Instead of the Data2sd provided in the tutorial, try using INT2EXTV2+(You can easily find it using the search function).....Do remember to flash it after the flashed rom has booted once
Also, you can not see the second partition of the SDCard on Windows...........Windows doesn't support it(EXT partitions)
csoulr666 said:
Instead of the Data2sd provided in the tutorial, try using INT2EXTV2+(You can easily find it using the search function).....Do remember to flash it after the flashed rom has booted once
Also, you can not see the second partition of the SDCard on Windows...........Windows doesn't support it(EXT partitions)
Click to expand...
Click to collapse
Ok, so as the current state of the phone, do I just wipe everything and then run CWM, reboot it then when it comes up again install Int2extv2+ from zip, that's it? Does the relock prevent me from taking the steps neccessary from getting back into the phone? and if so what would I need to do to unlock it again when I only have access to fastboot/bootloader/CWM?
LyleVertigo said:
Ok, so as the current state of the phone, do I just wipe everything and then run CWM, reboot it then when it comes up again install Int2extv2+ from zip, that's it? Does the relock prevent me from taking the steps neccessary from getting back into the phone? and if so what would I need to do to unlock it again when I only have access to fastboot/bootloader/CWM?
Click to expand...
Click to collapse
Unlock the Bootloader, get into CWM, wipe, flash the rom of your choosing, let it boot once, then go back to CWM and flash INT2EXTV2+
csoulr666 said:
Unlock the Bootloader, get into CWM, wipe, flash the rom of your choosing, let it boot once, then go back to CWM and flash INT2EXTV2+
Click to expand...
Click to collapse
Ok, so here is what I've done:
Re-unlocked √
Wipe date/Factory Reset √
Wipe Cache Partition √
Flashed cm-10.1-20130703-4.3-F-NIGHTLY-marvel √
Reboot System Now (Hangs on HTC white screen) - pulled battery out to turn off
Went back into bootloader -> CWM and installed INT2EXTV2+ via zip installer (selected no for SWAP2INT) √
Reboot - Hangs on HTC white screen. X
Here is a question, would S-ON affect this in any way? I've done the partial S-off procedure (which was recommended to me) but the bootloader still says S-On. If it needs to be completely off and shown as S-off would you show me a proper procedure link for me get that taken care of (but only if absolutely necessary)?
I really appreciate your help so far.
LyleVertigo said:
Ok, so here is what I've done:
Re-unlocked √
Wipe date/Factory Reset √
Wipe Cache Partition √
Flashed cm-10.1-20130703-4.3-F-NIGHTLY-marvel √
Reboot System Now (Hangs on HTC white screen) - pulled battery out to turn off
Went back into bootloader -> CWM and installed INT2EXTV2+ via zip installer (selected no for SWAP2INT) √
Reboot - Hangs on HTC white screen. X
Here is a question, would S-ON affect this in any way? I've done the partial S-off procedure (which was recommended to me) but the bootloader still says S-On. If it needs to be completely off and shown as S-off would you show me a proper procedure link for me get that taken care of (but only if absolutely necessary)?
I really appreciate your help so far.
Click to expand...
Click to collapse
Is there a chance you have a 2012 model of the WFS??? If so, see if the rom is compatible with the 2012 WFS.......some roms, like the OWL project(CM10.1) is compatible
csoulr666 said:
Is there a chance you have a 2012 model of the WFS??? If so, see if the rom is compatible with the 2012 WFS.......some roms, like the OWL project(CM10.1) is compatible
Click to expand...
Click to collapse
No go, Owl project roms are for GSM only. Mine does not have SIM card.
LyleVertigo said:
No go, Owl project roms are for GSM only. Mine does not have SIM card.
Click to expand...
Click to collapse
Why didn't you tell that before!! Look for roms with "marvelc" in them........ That's why it doesn't go past the HTC screen
csoulr666 said:
Why didn't you tell that before!! Look for roms with "marvelc" in them........ That's why it doesn't go past the HTC screen
Click to expand...
Click to collapse
The only one I was able to find that specifically called for CDMA that had a working dl link so far is cm-9.1.0-CRYPTOMILK-ALPHA9-marvelc.zip .
I tried to flash it but got this:
Installing update...
assert failed: getprop("ro.produ
ct.device") == "marvelc" || getp
rop("ro.build.product") == "marv
elc"
E:Error in /sdcard/cm-9.1.0-CRYP
TOMILK-ALPHA9-marvelc.zip
(Status 7)
Installation Aborted.
I did all the clearing and formatting required prior.
LyleVertigo said:
The only one I was able to find that specifically called for CDMA that had a working dl link so far is cm-9.1.0-CRYPTOMILK-ALPHA9-marvelc.zip .
I tried to flash it but got this:
Installing update...
assert failed: getprop("ro.produ
ct.device") == "marvelc" || getp
rop("ro.build.product") == "marv
elc"
E:Error in /sdcard/cm-9.1.0-CRYP
TOMILK-ALPHA9-marvelc.zip
(Status 7)
Installation Aborted.
I did all the clearing and formatting required prior.
Click to expand...
Click to collapse
Look for the ones with CDMA written in the thread, here are some CDMA roms I found
http://forum.xda-developers.com/showthread.php?t=2245617
http://forum.xda-developers.com/showthread.php?t=1861623
http://forum.xda-developers.com/showthread.php?t=2274173
Click to expand...
Click to collapse
csoulr666 said:
Look for the ones with CDMA written in the thread, here are some CDMA roms I found
Click to expand...
Click to collapse
I tried all those roms and same error, which leads me to believe that the rom isn't the problem.
However, all of that is irrelevant now, as I gave it to someone who said they knew how to fix it and they bricked it completely, so I just told him to keep it. lol
LyleVertigo said:
I tried all those roms and same error, which leads me to believe that the rom isn't the problem.
However, all of that is irrelevant now, as I gave it to someone who said they knew how to fix it and they bricked it completely, so I just told him to keep it. lol
Click to expand...
Click to collapse
U have marvelc no marvel mobile
Try with fastboot flash custom rom (boot.img,system.img, and recovery.img)
But dont forgot before factory reset.
U will have custom rom mobile, and worked mobile
If u can change rom, u must find marvelc roms, and first try cm7 rom
I too start with this rom (cm7)
Related
I had rooted my phone and updated the radio to 1.47.651.1 when I tried to update a custom rom I accidently re-ran PC36IMG.zip and it rebooted quick NOW the radio says 1:39:00:04:26
and in the options below I now have
FASTBOOT
RECOVERY
CLEAR STORAGE
SIMLOCK
HBOOT USB
I tried putting the phone on FASTBOOT then connected it to the USB and began a stock rom not rooted and it boots my phone into an HTC Black screen Boot mode and begins to update until it comes to the signatures and it gives me an error.
I run windows 7
I went and tried this, connected sd card to Computer with adapter and transferred stock rom rooted and renamed it to sdcard.zip
booted Evo to bootloader and chose recovery.
I as usual got the black background with EVO Icon and red triangle with exclamation mark.
There I click on hold Volume Up and Power until I get the following error:
E:Can't open /cache/recovery/command
Then I click volume up and the following title and menu appear:
Android system recovery <2e>
reboot system now
apply sdcard:update.zip
wipe data/factory reset
wipe cache partition
When I choose the sdcard:update option the following message is displayed
----Install from Sdcard ------
Finding Update package
Opening update package
verifying update package
E:signature verification failed
instalation aborted
After, I downloaded tha froyo 2.2 file and placed it on the sd and rename it to update.zip
and when I ran Update.zip from bootloader it ran half way but then stopped saying the following error
failed to verify whole-file signature
So now I load any PC36IMG and I get NO QUESTION to update just puts me onto the bootloader screen….
Not bricked, just stuck. Download stock ruu, plug phone into computer and install. Or put pc136.img on rot of sd, boot into fast boot, it should install automatically. If none of the above, go to a sprint store, tell them it won't boot and you don't know why, and they will flash or replace.
Sent from my PC36100 using Tapatalk
What I would do from here if I were you is put that sd card back in the computer and erase everything on it.
while your at it shut down the phone. Hold down the volume down button and press power. When that comes up post what version of Hboot you have please.
And I'll be better able to help out.
WOw
did you try to reinstall another ROM?
if you still see the RECOVERY menu item, go there and then go where it says update from zip on sdcard. then using up/down buttons highlight the .zip file of the ROM then push the power button to make it run.
this hoping you got a ROM on your sdcard. if not just get one at the forum and download.
i got clockworkmod but im sure the other recovery tools have similar options.
@ adelaney Stock Ruu begins to update and gives me an error when signatures are being installed. I tried three Stock ROMS
RUU_Supersonic_1.32.651.1_Radio_1.39.00.04.26_release_171253
RUU_Supersonic_1.32.651.6_Radio_1.39.00.05.31_release_171253_signed
RUU_Supersonic_1.47.651.1_Radio_2.05.00.06.10_release_CL195459
@ rjmjr69
Hboot information is:
SUPERSONIC EVT2-3 SHIP S-ON
HBOOT-0.79.0000
MICROP-041F
TOUCH PANEL-ATMWLC03_16ac
RADIO-1.39.00.04.26
@mogul420
Recovery gives me an error
E:Can't open /cache/recovery/command
Then I click volume up and the following title and menu appear:
Android system recovery <2e>
reboot system now
apply sdcard:update.zip
wipe data/factory reset
wipe cache partition
When I choose the sdcard:update option the following message is displayed
----Install from Sdcard ------
Finding Update package
Opening update package
verifying update package
E:signature verification failed
instalation aborted
Ok here's the deal. If you have nan unlock, fully rooted then you should have a nandroid back. If you do then boot into recovery and no a nandroid restore. This should boot you to one of your pervious backup/ system state.
Please note.
If you are fully rooted u should always do a nandroid backup before you flash any update, that way u can do a restore in the even something goes wrong.
http://WWW.rootznculture.com
Thank you for the information but it was a step I did not do... The tutorial that I went with did not speak about that when I rooted my phone...
EDIT: I even tried mixing files that I have downloaded with various PC36IM.zip and nothing triggers the update question.
Would they be able to notice if its rooted?
adelaney said:
Not bricked, just stuck. Download stock ruu, plug phone into computer and install. Or put pc136.img on rot of sd, boot into fast boot, it should install automatically. If none of the above, go to a sprint store, tell them it won't boot and you don't know why, and they will flash or replace.
Sent from my PC36100 using Tapatalk
Click to expand...
Click to collapse
Most likely NOT bricked if it boots!
Sounds like you re-applied root but glitched somewhere?
Try root again - may still work?
http://forum.xda-developers.com/showthread.php?t=706411
Another helpful post
http://forum.ppcgeeks.com/showthread.php?t=123714
What version is your hboot - press power and volume down WITHOUT pc36img.zip, update, etc on your sd - i.e. rename it or remove it, i.e. with adb or sd card slot on pc.... See if you can still access recovery?
I've been hammering on these things for a bit and if I can get into the boot screen, it's pretty much good to go...
Hboot-0.79.0000
Also the error that began all of this was running the wrong PC36IMG to begin with... I had 1.4 radio and I think that the one I used had the 1.3 radio so the only thing that helped me boot up again was that 1,2,3 step flashing so I thought that I had to take the second step and that placed in on booter, I have not been able to boot again ever since.... That was yesterday been trying for about 9 hours lol
lwarranty said:
sounds like you re-applied root but glitched somewhere?
Try root again - may still work?
http://forum.xda-developers.com/showthread.php?t=706411
another helpful post
http://forum.ppcgeeks.com/showthread.php?t=123714
what version is your hboot - press power and volume down without pc36img.zip, update, etc on your sd - i.e. Rename it or remove it, i.e. With adb or sd card slot on pc.... See if you can still access recovery?
I've been hammering on these things for a bit and if i can get into the boot screen, it's pretty much good to go...
Click to expand...
Click to collapse
Yes your just not rooted anymore. Run whatever process worked for you the first time
Try whitslack's method.
EDIT: Nevermind, no can do.
What happens is that my phone DOES read the PC36IMG.zip but it does not give me update option as it used to before. Any suggestions?
rjmjr69 said:
Yes your just not rooted anymore. Run whatever process worked for you the first time
Click to expand...
Click to collapse
xx1479 said:
Try whitslack's method.
Click to expand...
Click to collapse
latinsbest said:
What happens is that my phone DOES read the PC36IMG.zip but it does not give me update option as it used to before. Any suggestions?
Click to expand...
Click to collapse
Like he said
Make sure you delete all the files off your sdcard first
Do you have a link? I made a quick search and could not find a direct link...
xx1479 said:
Try whitslack's method.
Click to expand...
Click to collapse
I have several times even formatted (fat32) various times too
rjmjr69 said:
Like he said
Make sure you delete all the files off your sdcard first
Click to expand...
Click to collapse
latinsbest said:
I have several times even formatted (fat32) various times too
Click to expand...
Click to collapse
Reroot your phone using toast method! That is all! If you are on 1.47 then use simple root!
Seems you have un-rooted the boot me thinks but also read something about mixing radio's causing grief, someone more in the know could answer that... If you can get to hboot usb and try the RUU from your PC? Sometimes taking the battery out and restarting, if communication fails, try it again, rebooting the pc, hell I have no procedure, I just hammer till it makes sense, however 9 hours - holy crap, I'd be foaming at the face!
Ok will do right away and post update
novanosis85 said:
Reroot your phone using toast method! That is all! If you are on 1.47 then use simple root!
Click to expand...
Click to collapse
I have done that via PC and the only thing that works with that are the stock roms since they come in EXE they manage to reboot my phone and everything but when the update gets to the signature part it says it fails in the signatures and aborts... any other custom roms that have EXE?
lwarranty said:
Seems you have un-rooted the boot me thinks but also read something about mixing radio's causing grief, someone more in the know could answer that... If you can get to hboot usb and try the RUU from your PC? Sometimes taking the battery out and restarting, if communication fails, try it again, rebooting the pc, hell I have no procedure, I just hammer till it makes sense, however 9 hours - holy crap, I'd be foaming at the face!
Click to expand...
Click to collapse
Hey, My phone was working fine till yesterday. N when i tried to flash dk froyo .i had to change the kernel and i guess the bootscreen(htc logo) freezed because of that. I tried flashing hcdr and other kernels and even changed rom back to cm 7.But nothing seems to help.Only cwm is working on my phone. CAn someone help me please
btw its a wildfire
Your best bet Is to try run a ruu as that would reset the phone back to stock, bootloader and kernal, but depending on how you s-offed you may lose the ability to root.( untill you s-off again.) Good luck
sent from my steroid powered, cyanogenmod filled wrecking machine! using xda app.
Perform a full wipe (In CWM, Select "Data Wipe / Factory Reset", then, staying in CWM, go to Mounts and Storage, Select "Format /system". After this, flash a ROM (any) and check if it boots.
Tried. Its still not working. Can any1 post a nandroid backup file of any rom for wildfire. Please. I formatted my sd card too by mistake.
and while flashing a ruu. it always shows a error E:Failure at line 65 and something. Its different everytime
Connect your Wildfire to your PC, In CWM, Go to Mounts and Storage, and Select "Mount USB Storage". This will activate Mass Storage Mode and you can access your SDCard on your PC as normal. (I don't think anyone would upload a Nandroid backup of his own, it contains personal stuff like contacts and all. But, if someone does, good for you)
i mount usb storage n then do wat..? i tried flashing every rom possible. But its still not working. Is it the kernel's problem or what??
I am pretty certain performing a full wipe (Following options in CWM - 1: Data Wipe - Factory Reset, along with 2: Wipe Cache Partition, 3: Format /cache, 4: Format /system, 5: Format /data, 6: Wipe cache partition, 7: Wipe Dalvik Cache) in CWM and flashing a fresh ROM will fix your issue, UNLESS your phone is not bricked due to bad flash, but since you already claim that you have done that, I can't help you any further on this.
EDIT - Also one more thing - When you flash the kernel / ROM, do you get a confirmation message "Installation Complete"? What is your CWM version?
Yes i do.it says installation comple and its v3.0.0.6
Sense ROM's like DK will not work on CWM versions above 2.x.x.x. Anyway, since you tried CM7 already, One last suggestion in that case would be to try flashing the RUU via the bootloader.
Steps -
1: Download the RUU you want to install
2: Extract the rom.zip from the RUU. Procedure here
3: Once you have that rom.zip, Rename it to PC49IMG.zip
4: Transfer this to the root of your SDCard (i.e. - Not in any folders / sub-folders)
5: Restart device in HBoot Mode (Press Vol Down + Power simultaneously)
6: It will scan for the file, and ask to install. Follow On-Screen instructions.
Ill give it a try.
owe you big time man..Thanx a lot..
Return of the Jedi, Yoda is the man.
" once its gone,its GONE."
stuck at htc logo
cRo77y said:
Hey, My phone was working fine till yesterday. N when i tried to flash dk froyo .i had to change the kernel and i guess the bootscreen(htc logo) freezed because of that. I tried flashing hcdr and other kernels and even changed rom back to cm 7.But nothing seems to help.Only cwm is working on my phone. CAn someone help me please
Click to expand...
Click to collapse
search for syed zain ahmed on utube and see his video.. i cant post a link to the video coz i am new , after 10 post i will be able to post the link ... it helped me alot.. do try that method.
syed_786 said:
search for syed zain ahmed on utube and see his video.. i cant post a link to the video coz i am new , after 10 post i will be able to post the link ... it helped me alot.. do try that method.
Click to expand...
Click to collapse
Are you him by any chance?
Sent from my locked, tampered ville
wow, this is quite the thread revival, 2011 was ages ago....
help
Help?
or can anyone help me when I tried to install Custom MTD Partitions I'm stuck whit htc screen all to me erase what to do now when I want to install a new room again stuck please help I already tried all I do not have nor restore any deleted by mistake help
So, I recently acquired an Incredible, the second one I've owned. The first one I rooted, turned S-off and installed CM7 with zero difficulties, after that I rooted/flashed my Xperia Play CDMA with all the issues that accompany that device. (after the ease with which I modded my first DINC, the hoops through which I had to jump to unlock my bootloader blew my mind)
This DINC, though, refuses to clear user data. Even after multiple wipes via CWM, and multiple updates using the PB31IMG method, user data remains. Attmepts to preform a factory reset via HBOOT result in a balck screen with a red triangle and exclamation point.
I tried to install MIUI, thinking maybe a fresh rom would fix it, but it gets stuck at the room splash screen.
I've even tried recovering a clean CM7 install from my old incredible, but it gets stuck in a bootloop at the rom splash, same story trying to flash the .zip in recovery.
I've seen a few threads that deal with a few of these symptoms, but not the issue as a whole
Thanks in advance for any answers you guys have!
Cheers
I found a solution, finally. Admittedly, it was a bit drastic, but it worked, nonetheless.
I ended up disassembling both DIncs and putting the motherboard of the working device (with the smashed screen) into the device that was unable to format /data.
It was a bit touch and go for a bit, but my new DIY refubished phone is up and running.
Thanks for the help guys!
What error do you get? Can you upload the logs from /cache/ recovery after trying to wipe?
Sent from my Galaxy Nexus using Tapatalk 2
I'm still a bit of a noob, if you could point me towards some basic instructions on how to do that, I'll post a log when i get back to the house.
Last time I tried to logcat something in recovery, I nearly bricked my phone somehow.
Edit: It either gives me the red error triangle/exclamation point if i use HBOOT, or it gives me an error when trying to format the data partition on a recovery attempt.
mattdubuc said:
I'm still a bit of a noob, if you could point me towards some basic instructions on how to do that, I'll post a log when i get back to the house.
Last time I tried to logcat something in recovery, I nearly bricked my phone somehow.
Edit: It either gives me the red error triangle/exclamation point if i use HBOOT, or it gives me an error when trying to format the data partition on a recovery attempt.
Click to expand...
Click to collapse
Re-flash CWM recovery. The red triangle is a problem with recovery most likely. You can flash the latest CWM for the incredible from the app.
If that doesn't work then pull all the files from /cache/recovery location, use a file explorer app that can read it and copy it to the /sdcard location and upload it in a zip.
tiny4579 said:
Re-flash CWM recovery. The red triangle is a problem with recovery most likely. You can flash the latest CWM for the incredible from the app.
If that doesn't work then pull all the files from /cache/recovery location, use a file explorer app that can read it and copy it to the /sdcard location and upload it in a zip.
Click to expand...
Click to collapse
The red triangle happens when you try to do a factory reset from hboot wile on cwm recovery. If you really need to do a factory reset, you will need to flash to the stock recovery first. http://dinc.does-it.net/Recoveries/Stock_4.08.605.15/PB31IMG.zip Then if it works or even if not flash back to cwm recovery http://dinc.does-it.net/Recoveries/CWM_5.0.2.0/PB31IMG.zip.
The weird thing is, that even after flashing PBG31IMG via HBOOT I'm retaining all the previous user data. I've tried formatting the internal drive, using a few different versions of the image, even manual formatting of /data via CWM, which only gives me an error. the same error as when I tried to restore a nandroid from my functioning DINC.
tiny4579 said:
If that doesn't work then pull all the files from /cache/recovery location, use a file explorer app that can read it and copy it to the /sdcard location and upload it in a zip.
Click to expand...
Click to collapse
So do i just make a .zip file out of the contents of /cache/recovery or is there something more to it?
mattdubuc said:
So do i just make a .zip file out of the contents of /cache/recovery or is there something more to it?
Click to expand...
Click to collapse
That should be fine. Try to wipe data in cwm again just so it logs it.
Sent from my Galaxy Nexus using Tapatalk 2
I'm having the same issue, even after reflashing a rom or hard reset my system is as it was before, but most apps don't work. After turning on device instantly shows many errors such as error in com.android.phone etc... While trying factory reset in Recovery (5.0.2.0) the only error that logs is "no app2sd partition found. Skipping format of /sd-ext ". What can you advise? Please help, tomorrow I'm going to another country and in this moment working phone is very needed Device S-OFF Rooted HBoot 0.92
zslashy said:
I'm having the same issue, even after reflashing a rom or hard reset my system is as it was before, but most apps don't work. After turning on device instantly shows many errors such as error in com.android.phone etc... While trying factory reset in Recovery (5.0.2.0) the only error that logs is "no app2sd partition found. Skipping format of /sd-ext ". What can you advise? Please help, tomorrow I'm going to another country and in this moment working phone is very needed Device S-OFF Rooted HBoot 0.92
Click to expand...
Click to collapse
Same error if you flash stock GB sense and factory reset from recovery? You have the errors when booting and the apps are still there?
Sent from my Nexus 7 using Tapatalk 2
Thank you for reply, I solved reset issue by installing Amon Ra recovery. But the problem with apps still exists, it looks like system is restoring back up after reboot, I can do everything with system but after reboot it's like it was before with no changes made. Additionally, it seems that the problem is with emmc, just because when I delete EVERYTHING on it, after restart all files appear again!
I'm also getting an error when I try to manually format the data partition under >mounts and storage in CWM, I'm assuming that may be to blame for retained user data?
When I run show log after running only a manual /data format it displays:
6 black groups
32768 blocks per group. 32768 fragments per group
8112 inodes per group
superblock backups stored on blocks:
32768. 98304. 163840
The filesystem already has a journal,
tune2fs 1.41.6 (30-May-2009)
Setting current mount count to 1
Failure while running mke2fs
Error formatting /data!
mtd: succesfully wrote block at 0
I:Set boot command ""
I have no idea what that means really, or even if it's pertinent.
I had to remove the user info (owner data, phone number, etc) from my inc after canceling my contract with verizon. After about 25 different attempts to wipe it, I finally found something that worked (at least for me)
Tried running the RUU, could not reboot into HBOOT (version error)
Tried the RUU again, this time starting it after manually booting the phone to HBOOT. Got a little farther than before, but still errored out. Did not work. Disconnected phone, pulled battery, rebooted to HBOOT.
Factory reset in HBOOT got me stuck on the stock recovery screen. Battery pulled, could not boot.
Flashed CWM in HBOOT (by renaming to PB31IMG.zip), was able to get into CWM recovery.
Tried to flash the 2nd GB OTA in CWM, did not take. Every option I clicked in CWM gave me about 7 errors after sitting on the logo for a moment. Battery pull, reboot. Boots into CM9. >.<
Booted to my rom, saw about 300 force closes. Tried to reflash CWM from Rom Manager, got a bunch of force closes. Updated Rom Manager from market, reflashed CWM, and this time it worked.
Rebooted to CWM, wipe data/cache/dalvik, reboot.
This time I booted in CM9, but to the initial ICS set up (click next to begin, wireframe pic of Andy)
After skipping thru initial setup, I checked Settings>About Phone>Status. My phone number was removed, network is Unknown, and all my data was removed. Activation prompt appears on each boot.
Not sure if this will help, but worth a try. I think that the HBOOT factory reset is what cleared my data, and then I just needed to fix CWM so I could get back to a working ROM.
Yeah that's what I did in june except I just got service on mine but I would think that would help getting your data out forever. If that does not work I wouldn't know what to tell u besides grab a magnet. Lol
Sent from my Droid Incredible using xda premium
Hi,
I have a Droid Incredible (Verizon) that won't boot. I think it's toast, but wanted to list the things that I've done to see if there are any folks out there that think I may have another option besides selling it for parts.
***History***
1. I had no intention of ever rooting the phone, but the stupid "phone storage low" issue caused me to install clockworkmod and superuser so that I could resize the partitions for data/data (or so I believed at the time). In hindsight I never actually got S-OFF, and it's possible that this is where things went wrong.
2. Anyways, one day a few weeks ago after an OTA update from VZW and a reboot, the phone started looping and has never since booted back into the OS. I'd get the black and white "htc Incredible" screen, then the loud "DROID" sound, rinse and repeat. The behavior would change somewhat depending on whether I had the external SD installed or not, but regardless, the phone would never boot up. I tried a bunch of things I found on various forums, but nothing has worked. The current behavior is that the device just sits at the black/white "htc Incredible tm" screen upon boot .
***Things I've Tried***
1. I can get into HBOOT and managed to unlock the bootloader, but from there, I can't get it to factory reset and I can't get it to load any other firmware (likely because I'm still S-OFF). I've got clockworkmod installed, and when I try to install any new Roms from there, I get a bunch of errors:
E: Invalid command or argument
E: Can't mount /cache/recovery/log
E: Can't open /cache/recovery/log
E: Can't mount /cache/recovery/last_log
E: Can't open /cache/recovery/last_log
Anything I try to do in Clockworkmod errors out (wipe data, show log, install zip from SD, etc.). Either I get an error that the dir can't be mounted or the file can't be found.
2. I've also re-deployed the RUU (PB31IMG.zip), but it didn't work. I got to the "Loading… [PB31IMG.zip]" screen where it hung for a few minutes as the blue bar crept up, but then it flashed a message saying "No image or wrong image!" and kicked me back to the HBOOT menu again without asking me if I want to upgrade. I then go to FASTBOOT and hit REBOOT, and then it sent me back to the black/white "htc incredible" screen where it once again hangs and won't boot the OS.
3. Oddly, whenever I load anything on the external SD card and then put it on the phone, the phone will read the SD card once, but then seems to corrupt the file. If I put the SD card back in my Win7 machine, it always tells me the card needs to be formatted again. I re-format it to Fat32 and try again, but the cycle just repeats. I've tried 4-5 different SD cards that work fine in other devices, but the behavior is always the same. So I'm sure the SD cards are not the issue.
***Help!***
Does anyone have any ideas on what I can do to troubleshoot from here? I've spent hours on this and am about to give up and declare this phone no longer worthy of my time, but I figured I'd check here first.
This could all stem from the fact that I'm still S-ON, but I thought I'd at least be able to flash back to factory.
Here's what my HBOOT screen displays (notice that the bootloader is unlocked, but I'm still S-ON)
*** UNLOCKED ***
INCREDIBLEC XD SHIP S-ON
HBOOT-1.02.0000
MICROP-0417
TOUCH PANEL ATMELCO3_16ac
RADIO-2.15.10.07.07
Dec 21 2011, 23:37:16
Thanks!
BigEdgar said:
Hi,
I have a Droid Incredible (Verizon) that won't boot. I think it's toast, but wanted to list the things that I've done to see if there are any folks out there that think I may have another option besides selling it for parts.
***History***
1. I had no intention of ever rooting the phone, but the stupid "phone storage low" issue caused me to install clockworkmod and superuser so that I could resize the partitions for data/data (or so I believed at the time). In hindsight I never actually got S-OFF, and it's possible that this is where things went wrong.
2. Anyways, one day a few weeks ago after an OTA update from VZW and a reboot, the phone started looping and has never since booted back into the OS. I'd get the black and white "htc Incredible" screen, then the loud "DROID" sound, rinse and repeat. The behavior would change somewhat depending on whether I had the external SD installed or not, but regardless, the phone would never boot up. I tried a bunch of things I found on various forums, but nothing has worked. The current behavior is that the device just sits at the black/white "htc Incredible tm" screen upon boot .
***Things I've Tried***
1. I can get into HBOOT and managed to unlock the bootloader, but from there, I can't get it to factory reset and I can't get it to load any other firmware (likely because I'm still S-OFF). I've got clockworkmod installed, and when I try to install any new Roms from there, I get a bunch of errors:
E: Invalid command or argument
E: Can't mount /cache/recovery/log
E: Can't open /cache/recovery/log
E: Can't mount /cache/recovery/last_log
E: Can't open /cache/recovery/last_log
Anything I try to do in Clockworkmod errors out (wipe data, show log, install zip from SD, etc.). Either I get an error that the dir can't be mounted or the file can't be found.
2. I've also re-deployed the RUU (PB31IMG.zip), but it didn't work. I got to the "Loading… [PB31IMG.zip]" screen where it hung for a few minutes as the blue bar crept up, but then it flashed a message saying "No image or wrong image!" and kicked me back to the HBOOT menu again without asking me if I want to upgrade. I then go to FASTBOOT and hit REBOOT, and then it sent me back to the black/white "htc incredible" screen where it once again hangs and won't boot the OS.
3. Oddly, whenever I load anything on the external SD card and then put it on the phone, the phone will read the SD card once, but then seems to corrupt the file. If I put the SD card back in my Win7 machine, it always tells me the card needs to be formatted again. I re-format it to Fat32 and try again, but the cycle just repeats. I've tried 4-5 different SD cards that work fine in other devices, but the behavior is always the same. So I'm sure the SD cards are not the issue.
***Help!***
Does anyone have any ideas on what I can do to troubleshoot from here? I've spent hours on this and am about to give up and declare this phone no longer worthy of my time, but I figured I'd check here first.
This could all stem from the fact that I'm still S-ON, but I thought I'd at least be able to flash back to factory.
Here's what my HBOOT screen displays (notice that the bootloader is unlocked, but I'm still S-ON)
*** UNLOCKED ***
INCREDIBLEC XD SHIP S-ON
HBOOT-1.02.0000
MICROP-0417
TOUCH PANEL ATMELCO3_16ac
RADIO-2.15.10.07.07
Dec 21 2011, 23:37:16
Thanks!
Click to expand...
Click to collapse
I would fastboot flash the stock recovery, do a factory reset from hboot, fastboot flash back to cwm recovery, and then see if you can get cwm to work correctly. Or try the ruu again after the factory reset.
cmlusco said:
I would fastboot flash the stock recovery, do a factory reset from hboot, fastboot flash back to cwm recovery, and then see if you can get cwm to work correctly. Or try the ruu again after the factory reset.
Click to expand...
Click to collapse
Thanks for the thoughts. I thought I'd already tried fastboot flashing the stock recovery with no success, but maybe I did something wrong?
Here's what I did:
1. Downloaded a recent copy of PB31IMG.zip
2. Via my Win7 machine, loaded PB31IMG.zip onto an SD card formatted as Fat32
3. Put the SD card in my Dinc
4. Boot into HBOOT
5. Select Fastboot
6. Fastboot finds the image, spends a few minutes loading it, but then errors out with "No image or wrong image!" message. Boo.
FWIW, I've only been able to get adb to recognize my device intermittently so adb isn't really an option (unless I can figure out
Am I doing something wrong?
BigEdgar said:
Thanks for the thoughts. I thought I'd already tried fastboot flashing the stock recovery with no success, but maybe I did something wrong?
Here's what I did:
1. Downloaded a recent copy of PB31IMG.zip
2. Via my Win7 machine, loaded PB31IMG.zip onto an SD card formatted as Fat32
3. Put the SD card in my Dinc
4. Boot into HBOOT
5. Select Fastboot
6. Fastboot finds the image, spends a few minutes loading it, but then errors out with "No image or wrong image!" message. Boo.
FWIW, I've only been able to get adb to recognize my device intermittently so adb isn't really an option (unless I can figure out
Am I doing something wrong?
Click to expand...
Click to collapse
That will only work if your s-off. With an unlocked bootloader you need to take that stock recovery pb31img.zip and extract the recovery.img file out with 7zip or the like. Place the img in the same folder on your pc as adb.exe and fastboot.exe. Boot to the bootloader and then on your pc open a cmd prompt to where fastboot.exe is. At the prompt type without quotes " fastboot flash recovery recovery.img ". Do the same thing to flash back to cwm.
cmlusco said:
That will only work if your s-off. With an unlocked bootloader you need to take that stock recovery pb31img.zip and extract the recovery.img file out with 7zip or the like. Place the img in the same folder on your pc as adb.exe and fastboot.exe. Boot to the bootloader and then on your pc open a cmd prompt to where fastboot.exe is. At the prompt type without quotes " fastboot flash recovery recovery.img ". Do the same thing to flash back to cwm.
Click to expand...
Click to collapse
Thanks again for the help - I really appreciate it.
I was able to get the recovery.img loaded:
\miniadb_inc>fastboot flash recovery recovery.img
sending 'recovery' (3514 KB)... OKAY [ 0.531s]
writing 'recovery'... OKAY [ 1.059s]
finished. total time: 1.604s
I then clicked on FASTBOOT --> RECOVERY and the phone rebooted. After reboot, I see the green arrows for a minute or so, and then... the red triangle with the exclamation point. Is that normal?
BigEdgar said:
Thanks again for the help - I really appreciate it.
I was able to get the recovery.img loaded:
\miniadb_inc>fastboot flash recovery recovery.img
sending 'recovery' (3514 KB)... OKAY [ 0.531s]
writing 'recovery'... OKAY [ 1.059s]
finished. total time: 1.604s
I then clicked on FASTBOOT --> RECOVERY and the phone rebooted. After reboot, I see the green arrows for a minute or so, and then... the red triangle with the exclamation point. Is that normal?
Click to expand...
Click to collapse
Ok, quick update. After getting the red triangle with the exclamation point, I did the following:
- Power button + Up Volume to get to the System Recovery menu.
- Selected "Wipe cache partition"
- Selected "Wipe data/factory reset"
The factory reset just errored out all over the place (see attached image). It's almost like the boot partition is the only partition that is readable on this phone, and the partition that contains the OS is completely hosed. This is pretty consistent with everything else I've seen. Anytime I try to factory reset or do anything else, the phone just throws a bunch of errors basically telling me it can't mount drives and can't find directories.
Upon reboot, the phone still just hangs at the black/white "htc Incredible" screen.
Any thoughts on where to go from here?
BigEdgar said:
Ok, quick update. After getting the red triangle with the exclamation point, I did the following:
- Power button + Up Volume to get to the System Recovery menu.
- Selected "Wipe cache partition"
- Selected "Wipe data/factory reset"
The factory reset just errored out all over the place (see attached image). It's almost like the boot partition is the only partition that is readable on this phone, and the partition that contains the OS is completely hosed. This is pretty consistent with everything else I've seen. Anytime I try to factory reset or do anything else, the phone just throws a bunch of errors basically telling me it can't mount drives and can't find directories.
Upon reboot, the phone still just hangs at the black/white "htc Incredible" screen.
Any thoughts on where to go from here?
Click to expand...
Click to collapse
This post seems to echo my current situation: http://forum.xda-developers.com/showthread.php?t=1487675 (unfortunately no solution). I'll do some more investigating to see if there's a way to confirm that the partition is borked...
BigEdgar said:
This post seems to echo my current situation: http://forum.xda-developers.com/showthread.php?t=1487675 (unfortunately no solution). I'll do some more investigating to see if there's a way to confirm that the partition is borked...
Click to expand...
Click to collapse
Instead of doing the factory reset from the recovery menu, try it right from the main hboot screen. If that dosent work it sounds like the data partition is is fubar.
Are you able to use adb now? If you can, i have another sugestion i came across in another thread. A guy said he could not access, format, or use his data partition. He claims he fixed it by adb pulling the file system from a working inc, and adb pushing the files to the borked inc, fixing it. If you can get adb to stay connected long enough to push the files it might be worth a try.
cmlusco said:
Instead of doing the factory reset from the recovery menu, try it right from the main hboot screen. If that dosent work it sounds like the data partition is is fubar.
Click to expand...
Click to collapse
Thanks again for the suggestions.
I tried that but it's pretty much the same results.
HBOOT--> Factory Reset --> Screen with green arrows --> Red triangle with Exclamation point --> - Power button + Up Volume to get to the System Recovery menu --> Reboot:
Phone hangs on the black/white "htc Incredible" splash screen
One other odd note - if I do this same factory reset process with the USB cable *unplugged*, the instead of hanging on the black/white splash screen, it just goes into an infinite loop (black/white splash screen --> HTC quietly brilliant screen --> droid eye --> back to the black/white splash screen). FWIW this isn't new behavior, I just forgot to mention it earlier. In fact this is what the phone started doing once Verizon pushed the OTA update that screwed up the phone in the first place (there are a number of threads on this over at HTC and VZW forums, but their solutions aren't working for me).
I think this thing is a brick. If anyone has any recommendations for tools that can be used to analyze the partitions on a phone that won't boot, let me know. Otherwise this thing is getting sold for parts : )
Ok, some more progress. Most importantly, I learned that adb has a shell! I obviously didn't RTFM well enough.
Anyways, with the shell I was able to verify that the partitions on the phone are accessible (at least from a Windows machine) and I can, in fact, write files to the device (using "adb push" to push files to /sdcard, for example). That's great as it proves that the storage on the device *is* accessible, but just not from CWM. I followed some instructions that I followed partially before (http://androidforums.com/incredible...ow-unlock-downgrade-achieve-s-off-htcdev.html) in an attempt to see if I could get S-OFF. This tutorial is nice because most of the actions are via adb and fastboot instead of using the UI on the phone, which I couldn't get to. I was able to do most of the work I needed to get S-OFF via adb instead of using CWM or some other recovery tool, which was key, since CWM always tells me that it can't read or write any partitions.
I was actually able to get Froyo installed and boot into it! That's the first time this POS has booted into anything in almost a month!!
Now to my current problem - the last few steps of the tutorial linked above require that I install superuser and unrevoked, and suggest that this be done via CWM. Unfortunately, CWM can't read any of my data partitions, so this doesn't work for me. Not many others seem to have this problem, so googling it doesn't turn up any help.
Is there any way I can use ADB to install superuser and unrevoked forever? I also have access to the UI via Froyo and could conceivably install apks as well.
Here are the instructions from the tutorial that don't work for me, as they rely on CWM:
******************
use the recovery menu on your phone to:
-wipe cache
-wipe dalvik cache
-install zip from sd card(chose your superuser file)
-install zip from sd card(chose your forever file)
******************
Those last two steps - install zip from sd card - are the ones that completely fail for me. CWM just gives me a bunch of "E:can't mount /sdcard/" errors.
If anyone has any ideas on how to install superuser and unrevoked using ADB, I'm all ears : )
Thanks!
So I know you have been going in circles but at least you can boot into froyo! Do you have a spare SD card though? If not try reformatting your current SD again. It could be that your SD card has just gone bad though so it might be worth borrowing one from a friend to find out. If you're booting into froyo though that should mean you have access to /data now so I think those troubles are behind you. You don't really need to flash superuser.zip if you're just planning on flashing a new rom though. Unrevoked forever is the s-off tool and since you're already on froyo (with the froyo radio) that is all you need!
Sent from my ADR6300 using xda app-developers app
nschiwy said:
So I know you have been going in circles but at least you can boot into froyo! Do you have a spare SD card though? If not try reformatting your current SD again. It could be that your SD card has just gone bad though so it might be worth borrowing one from a friend to find out. If you're booting into froyo though that should mean you have access to /data now so I think those troubles are behind you. You don't really need to flash superuser.zip if you're just planning on flashing a new rom though. Unrevoked forever is the s-off tool and since you're already on froyo (with the froyo radio) that is all you need!
Sent from my ADR6300 using xda app-developers app
Click to expand...
Click to collapse
Thanks for the thoughts. I've got like 5 SD cards, and I've been able to validate with my other Android phone that they are all good.
I agree that it's good to be on Froyo, but to be able to swap to a different ROM, I still need S-OFF. And the only way I can see to get S-OFF is to install unrevoked forever. And the only method that I can find for installing unrevoked forever is via Recovery, and CWM just doesn't appear to be able to see any of my disks, so I need a different option for installing unrevoked forever besides CWM. Maybe it's time to ditch CWM and try a different recovery tool. I suppose I'll give amon_ra a try and see if that changes anything. Or is there some other way to install unrevoked?
BigEdgar said:
Thanks for the thoughts. I've got like 5 SD cards, and I've been able to validate with my other Android phone that they are all good.
I agree that it's good to be on Froyo, but to be able to swap to a different ROM, I still need S-OFF. And the only way I can see to get S-OFF is to install unrevoked forever. And the only method that I can find for installing unrevoked forever is via Recovery, and CWM just doesn't appear to be able to see any of my disks, so I need a different option for installing unrevoked forever besides CWM. Maybe it's time to ditch CWM and try a different recovery tool. I suppose I'll give amon_ra a try and see if that changes anything. Or is there some other way to install unrevoked?
Click to expand...
Click to collapse
Try using unrevoked 3.22 pc program instead of the forever zip.
Download unrevoked http://dinc.does-it.net/Unrevoked/Unrevoked_3.22.exe, to your pc. Boot the phone and enable usb debugging if its not already. Do not plug the phone in yet. Run unrevoked, when it opens click file at the top and select custom recovery. Then download and select this file http://dinc.does-it.net/Guide_Root_New_Hboot/recovery.img, as the custom recovery. Then plug in the phone and continue by following the prompts. If all goes well, it will reflash the recovery and install su. You can then install busybox from the market.
cmlusco said:
Try using unrevoked 3.22 pc program instead of the forever zip.
Download unrevoked http://dinc.does-it.net/Unrevoked/Unrevoked_3.22.exe, to your pc. Boot the phone and enable usb debugging if its not already. Do not plug the phone in yet. Run unrevoked, when it opens click file at the top and select custom recovery. Then download and select this file http://dinc.does-it.net/Guide_Root_New_Hboot/recovery.img, as the custom recovery. Then plug in the phone and continue by following the prompts. If all goes well, it will reflash the recovery and install su. You can then install busybox from the market.
Click to expand...
Click to collapse
Thanks for the suggestion. I tried this a few times and while Unrevoked is reporting success, I'm still S-ON and BusyBox and ROM Manager report that I'm not rooted. Back in CWM, CWM still reports errors mounting all drives and is basically crippled. In addition to the "can't mount SD card" errors, I'm also seeing "E:cant mount /dev/block/mmcblk0p2" and "E:Can't mount /cache/recovery/command". Weird. Can't tell if the mount errors are causing my inability to root or my inability to root is causing the mount errors.
(I also tried using AmonRa and got the same "can't mount" blah blah issues). Time for a drink : )
There's a fix. I have a thread on it but the xda app is acting up. Tell u later once I'm home
Sent from my ADR6300 using xda app-developers app
---------- Post added at 10:05 PM ---------- Previous post was at 09:51 PM ----------
Here you go man
http://forum.xda-developers.com/show...php?p=14440621
And thats for amoled screens, if you have the newer SLCD you would have to do it blindfolded basically because the screen will go off
eljean said:
There's a fix. I have a thread on it but the xda app is acting up. Tell u later once I'm home
Sent from my ADR6300 using xda app-developers app
---------- Post added at 10:05 PM ---------- Previous post was at 09:51 PM ----------
Here you go man
http://forum.xda-developers.com/show...php?p=14440621
And thats for amoled screens, if you have the newer SLCD you would have to do it blindfolded basically because the screen will go off
Click to expand...
Click to collapse
Eljean - that link's a 404...
I'm viewing it right now...
Sent from my ADR6300 using xda app-developers app
---------- Post added at 04:03 PM ---------- Previous post was at 04:02 PM ----------
http://forum.xda-developers.com/showthread.php?t=14440621
Try again
Sent from my ADR6300 using xda app-developers app
eljean said:
I'm viewing it right now...
Sent from my ADR6300 using xda app-developers app
---------- Post added at 04:03 PM ---------- Previous post was at 04:02 PM ----------
http://forum.xda-developers.com/showthread.php?t=14440621
Try again
Sent from my ADR6300 using xda app-developers app
Click to expand...
Click to collapse
Thanks, but that link still fails for me. Is the title of the thread [HOW-TO] Fix 5 vibrate and black screen? This one works for me: http://forum.xda-developers.com/showthread.php?p=14440621 (p= instead of t= in the URL).
If that's the thread you're pointing to, then I read through the thread earlier today and was hoping that the fix for the SD card would help (running fastboot oem enableqxdm 0), but that didn't. I don't seem to have the problem about not being able to communicate with the phone using USB - USB connectivity is working when the phone boots into Froyo and I'm also able to use ADB in Froyo and Recovery.
Unfortunately CWM (or any other Recovery tool) still can't read any of my drives, and while Unrevoked claims to be successful, I'm still S-ON.
I'm still poking around for a solution, I'll reply back if I discover anything.
BigEdgar said:
Thanks, but that link still fails for me. Is the title of the thread [HOW-TO] Fix 5 vibrate and black screen? This one works for me: http://forum.xda-developers.com/showthread.php?p=14440621 (p= instead of t= in the URL).
If that's the thread you're pointing to, then I read through the thread earlier today and was hoping that the fix for the SD card would help (running fastboot oem enableqxdm 0), but that didn't. I don't seem to have the problem about not being able to communicate with the phone using USB - USB connectivity is working when the phone boots into Froyo and I'm also able to use ADB in Froyo and Recovery.
Unfortunately CWM (or any other Recovery tool) still can't read any of my drives, and while Unrevoked claims to be successful, I'm still S-ON.
I'm still poking around for a solution, I'll reply back if I discover anything.
Click to expand...
Click to collapse
But it also fixes the usb problem. Trust me I went thru the exact same thing and this fixed it
http://forum.xda-developers.com/showthread.php?t=695243
eljean said:
But it also fixes the usb problem. Trust me I went thru the exact same thing and this fixed it
http://forum.xda-developers.com/showthread.php?t=695243
Click to expand...
Click to collapse
I appreciate the thoughts, but I think we're talking about different issues here. One of your issues seemed to be that you couldn't access the device at all via USB. I don't have that problem. My USB connection has always been fine. My problem is that CWM can't mount the SD card (or any other drives, for that matter). Everything mounts fine in Froyo, so I'm guessing it has to do with the way the drives are mounted in Recovery vs. Froyo.
The thread you referenced stated that the fix for not being able to access the SDcard was the fastboot oem enableqxdm 0 fix. I tried that a few times but it didn't make any difference.
Thanks for the thoughts!
Hello,
I have done days worth of research in my spare time, before finally caving in and asking for help. I'm still kinda new to the custom rom scene, and somewhere I must've messed up.
I was updating my ViperX rom to a newer version, but got an error code during the install, which rendered the OS useless. So decided to wipe and reinstall the older version again, which failed. So I tried to install CM 11, which also failed... Somewhere a long the line my SD Card stopped being detected by the phone AND my PC. So now I don't know how to get an OS on it.
Here's some info I might need to share.:
**** UNLOCKED ***
ENDEAVOUR PVT / S-ON
HBOOT - 1.39.0000
(Bought in Sweden, before moving to the UK)
I have access to bootloader
I have access to recovery which is CWM 6.0.4.8.
My SD card WONT MOUNT (I think), so I don't think I could do "side loading", since it's not recognized in ADB . If I reboot the system, it bootloops at the CM update logo forever. I've tried reinstalling it several times, but it only installs for a few seconds, then restarts. (I'm guessing it's corrupt?)
(Edit: Earlier today it ran out of battery, and despite charging it for hours, it's not turning on and the little LED on the top is blinking RED... What's that all about?)
Is there ANYTHING I've missed, or can do to fix this? I don't care what kind of ROM I have to use at this point, I just want a WORKING phone.
Cheers // Vic
Vicarate said:
Hello,
I have done days worth of research in my spare time, before finally caving in and asking for help. I'm still kinda new to the custom rom scene, and somewhere I must've messed up.
I was updating my ViperX rom to a newer version, but got an error code during the install, which rendered the OS useless. So decided to wipe and reinstall the older version again, which failed. So I tried to install CM 11, which also failed... Somewhere a long the line my SD Card stopped being detected by the phone AND my PC. So now I don't know how to get an OS on it.
Here's some info I might need to share.:
**** UNLOCKED ***
ENDEAVOUR PVT / S-ON
HBOOT - 1.39.0000
(Bought in Sweden, before moving to the UK)
I have access to bootloader
I have access to recovery which is CWM 6.0.4.8.
My SD card WONT MOUNT (I think), so I don't think I could do "side loading", since it's not recognized in ADB . If I reboot the system, it bootloops at the CM update logo forever. I've tried reinstalling it several times, but it only installs for a few seconds, then restarts. (I'm guessing it's corrupt?)
(Edit: Earlier today it ran out of battery, and despite charging it for hours, it's not turning on and the little LED on the top is blinking RED... What's that all about?)
Is there ANYTHING I've missed, or can do to fix this? I don't care what kind of ROM I have to use at this point, I just want a WORKING phone.
Cheers // Vic
Click to expand...
Click to collapse
Flash Philz 5.15.9 recovery and you have working sd card mount there copy what you want to your sd card and if you want to install kitkat rom flash lates CWM or TWRP or Philz and inatall it
Thant said:
Flash Philz 5.15.9 recovery and you have working sd card mount there copy what you want to your sd card and if you want to install kitkat rom flash lates CWM or TWRP or Philz and inatall it
Click to expand...
Click to collapse
You must've missed the part where I said neither my Phone nor my PC can detect the SD card, so can't put anything on it. :/
Vicarate said:
You must've missed the part where I said neither my Phone nor my PC can detect the SD card, so can't put anything on it. :/
Click to expand...
Click to collapse
NO I not missed nothing you don't listen me. flash Philz 5.15.9 recovery after this go in recovery connect the phone to computer and choice mount sd card after 1-2 min you will see your sd card and if you think not do this I will stop help you. It is your choice to flash revovery you dont need sd card only fastboot commands, use exactly the same recovery where I write you not newer not older have shears from me on googledrive use search function and download it take the recovery.img from zip archive then place in your fastboot folder the connect the phone in fastboot and run the command fastboot flash recovery recovery.img. Simple thing to do