I'm not positive where this should be posted it can be moved as needed but i am beyond lost right now. I have looked through hundreds of pages of forums for help and cant fix my phone yet.
I have a good amount of experience with android, adb, rooting, etcs and usually have been able to solve my problems. I was running CM7.0.3 on my droid incredible fine for months without problems and then out of no where i went to turn it on and it got stuck at the splash screen. I was away from my computer on vacation so i started trying to figure it out on my own. I could still access CWM via Hboot but when i loaded CWM it couldnt mount /data and /cache. Last time i had a problem similar to this i just flashed a RUU through Hboot and rerooted my phone afterwards so i thought this might work. I flashed it and phone booted up and i thought it was fixed.
This is where things started getting confusing. The internal storage in my phone has completely disappeared and theirs only 149MB available under phone memory which is suppose to be at 748MB. I tried to run unrevoked so i could reroot, get CWM back, and try to figure out what happened but it cant run because the internal storage it missing.
I have been reading for hours and trying to figure what to do next but i have no clue. i really need some help anything would be appreciated.
UPDATE: After more work on my phone i tried reflashing the RUU and then doing a factory data reset through hBoot and couldnt complete it because internal storage having problems mounting. im trying to get a logcat right now to post showing what it is. i believe it is the /dev/block/mmcblk0p1, CACHE:recovery/log, and poart of the mtdblock
Have you tried a brand new flash of CM7? Do a Full Wipe, Format System and anything else you deem necessary to format and flash CM7 from your SD. Then you can begin to work from there, because at least you'll have a working phone.
I'm a little confused as to why you would immediately run the RUU after getting a Bootloop instead of Restoring a Nand or Wiping Cache or Data?
I could get it to boot into clockwork but /data couldnt mount. i could not do a wipe or flash from inside CWM. i tried to do a fresh install but it wouldnt let me. I couldnt restore a NAND for the same reason. Now because of the RUU i dont have CWM anymore or root access. unrevoked wont work to reroot because in the internal storage is all messed up.
Related
I have been passed a HTC Desire to try and fix after a friend of mine ran into issues trying to put Froyo on it. It was originally with Virgin (Virgin boot screen) but was not locked as other sims were usable.
I've tried various different methods to get it up and running but suspect something he has done with his attempts has caused serious issues - also he is not all that clued up and cannot remember exactly what he did - he did mention that RUU update failed, and also an image he had tried to flash from his sd card had got part way through and then locked up on the radio update.
With the original sim and memory card in, the phone will constantly reboot or just stick at the HTC logo. Take the memory and sim cards out, the phone will boot but system wont launch properly so cant get into settings to enable debugging so I can access the device via ADB. I can get to the fastboot screen, and to the Vol Down-Power screen on start, but if I select recovery it stays on HTC logo and goes nowhere.
I have managed to get HBOOT downgraded to 0.8, but when trying to put on original Virgin RUU it says the main version is older (probably because I'm trying to install an older version over a newer one). The stock Froyo RUU fails and tells me wrong HBOOT and sometimes gives a CID error. Although the phone is not locked, I suspect it will still need a goldcard, but cant create one as I cant get ADB access to the phone.
Sorry if this is a bit of a mess but at work and trying to take calls as well as write this and fix the darned phone. I;m not unfamiliar with methods used to get the phone rooted, but not well up on troubleshooting or working around these issues I have.
Any help would be appreciated.
You should be able to restore it by installing this RUU with a working goldcard:
http://shipped-roms.com/shipped/Bra...3.00.32U_5.09.00.20_release_140022_signed.exe
If you get a CID error your goldcard isn't working. There should be no version error with this.
Thanks for the reply....however how can I create a goldcard when I cant get the phone to a point where I can get my pc to recognise it? All the goldcard methods I have seen/tried involve having the usb plugged in and debugging enabled - cant get to that stage as phone wont boot - reboot loop most of the time and when I do occassionally get to the os it doesnt last, it will reboot after a few seconds. Anything else I could do? Or, could I use the card in other phone and create the goldcard in that and transfer over? I do have my own working Desire handset.
Don't know much about this but have read that a goldcard is unique to the SD card not the phone so you could create one on your phone and then use it in your mates. Also, from what I've read it would be worthwhile wiping your mates SD card (make sure he's not added a partition to it), copying a Rom to it, and try to install it using Rom manager (or whatever recovery program which was used to root the phone)
Ok, I used my own phone to sort out the goldcard and currently trying that out now...will keep you posted. Just started the RUU Stock Froyo and seems to have got further so far. Wish me luck!
Mmmmm....ok the RUU worked, but when it restarted (with original goldcard/memory card in, it kept rebooting. It did start once, got to initial setup then promptly rebooted. I swapped out the memory card (no sim in at all by the way at any point up to now) to my own card and after one final reboot it did start up. It doesnt seem stable at all with the original memory card, and still not entirely stable with my card. Could this be a phone fault? Im assuming if the RUU got through all its stages then all areas and files on the phone have been updated correctly and are all correct? Could past failures at updates etc have caused an issue elsewhere?
Have you wiped the various caches? As far as I can make out you need to make sure everything is wiped. I read a post on the OpenDesire thread which suggested that clockworkrom, if that is the recovery program you have installed, may not wipe one of the caches (possibly the dalvik cache) correctly. They recommended another recovery program called something like AmonRu. Although I can't really help you it might be worthwhile saying how the phone was rooted.
Ok, none of this was to root the phone. It was to debrand and put on the HTC Desire Froyo build. Not a custom rom, the standard RUU.
As far as I was aware, an RUU restore of the phone would wipe the appropiate caches, but correct me if I'm wrong. The phone now starts with the standard HTC startup and sound and for all intents and purposes is working, but just cant explain the random reboots. These seem to be worse with the 8GB card that my mate gave me with it. Although, after trying mine and putting the original one back in it seems to have stayed stable up to now. I'm beginning to wonder if there may be an issue with the memory card slot - another swap of the memory card again will probably trigger the reboots once more.
We will see how it goes anyway.
You've got a hardware fault. The RUU will completely reflash the phone, so if it flashed successfully but is still rebooting randomly, it can't be software.
Your probably right. Just started to try and do a downgrade, and after putting the PB99.IMG file on the gold card I made earlier, then starting the downgrade I noticed it stuck at about 98% on the radio update (second item in the list). I'm going to leave it a while to see if I get an error but I suspect it will not move or do anything.
Having gone through this process before on my own handset, I know it doesn't take anywhere near this long. Thing that confuses me though is that the RUU process I went through before went through with no issues - so why would that be able to successfully install a radio update and not this downgrade process? Anyone else had this happen to them?
Update: Ok, leaving this now as I've exhausted all avenues and its obvious the phone is not going to play ball. On another RUU flash it failed (and looking at the logs it was at the radio section and mentioned a partition update failure). A subsequent RUU flash was successful, so at least I've got it back to stock (although it doesnt stay booted long enough to even get the initial setup wizard done now). Passing it back to my friend tomorrow and hope he can get a warranty repair. Just a shame I couldn't get it back to the Virgin firmware. Thanks all those that helped anyway, much appreciated.
Hello All,
My wife just recieved a refurbished phone through best buy. I tried to root her phone with unrevoked. When i went through with the process i got a error code through unreoked about firmware being too new. So after reading around I found out that it has the OTA FW and cannot be rooted yet. So after the root failed I cleared the storage on the phone. So now everytime she uses the phone it begins to boot loop when she begins to make a call. This is not my first time rooting I have done this plenty of times. Any Ideas?
Sounds like you've done what you can with the phone. Without s-off you cant flash the custom recovery to get more access to the file system so you're fairly stuck. You might try going into the phone settings and doing a full restore, just save any pics and whatnot she may have taken onto a computer so you can wipe the sd card for good measure as well. If that doesn't fix it then just take it to BB and tell them the refurb isn't working.
ok i will try erasing everything first and see what happens
How did everything work out?
I was running MIUI 1.9.2..hadnt updated in a few weeks.
Randomly today, I stated getting a crazy amount of force closes.. (framework, google voice, browser, messaging, etc.)
Went to go restart the phone and got stuck in bootloops.. Pulled the battery and tried it again, same thing.
Than I tried to boot into CWM recovery...noo good..stuck on splash screen. No idea what the problem is or how to go about fixing it.
Any ideas?
Thanks guys
If you can get into fast boot, but not recovery, try flashing the recovery from fast boot, or running an RUU to get back to stock, then reroot, but that means losing all your data. Try just recovery first.
Edit: I'm a firm believer of it's not bricked till it doesn't power on.
Yeah that sounds like a good idea. How exactly should I go about flashing recovery?..Via adb or can I put it in the root of the sd and flash it in fastboot
SD card must be fat 32. Put the recovery zip in the root of your sd card. Should be a file named PB31IMG.zip dougpiston.com (I think) is the site that has most of them, and you flash it from fast boot.
Oh yeah I remember him, hes over on the incredibleforum. Thank man, appreciate it
Got recovery working, tried re-flashing the ROM without a full wipe. Still stuck with bootloops. Is my only option to do a full wipe and lose everything?
Try wiping cache, dalvik, and boot, reflash ROM, then fix permissions. That doesn't work, do the above steps again, but right after, flash another kernel (I use incredikernel). If that still doesn't work, you might have to do a full wipe.
Yeah, I tried all that, no luck. Thanks anyway man. I don't even know why this happened in the first place. Very random.
Try reformatting you SD card. Save everything to your PC first of course, then copy everything back on and then reflash your Rom. This has worked for some.
Hi all, Strange thing happening to me. I was running Tweaked Rom for the longest time, then I decided to try Liquid Rom (as it does not update my bootloader), flashed as always and when it booted I had no signal, IMEI,etc. quick heart attack then decided to use my Tweaked nandroid. Which worked fine was back in action. Now when I go into recovery I get all kinds of errors saying cannot mount DATA,CACHE,DALVIK,INTERNAL. I tried updating my TWRP to the latest ... No Luck. they still wont mount and show 0mb space. Phone is still working. Anyone have any input or guidance for me.
Much Appreciated
Sorta Fixed, switched to CWM recovery and all is well, although if I go back to twrp it still shows cant mount internal sd, data,dalvik etc...
Thanks for Looking and maybe this will help others that run into this problem
rail205 said:
Hi all, Strange thing happening to me. I was running Tweaked Rom for the longest time, then I decided to try Liquid Rom (as it does not update my bootloader), flashed as always and when it booted I had no signal, IMEI,etc. quick heart attack then decided to use my Tweaked nandroid. Which worked fine was back in action. Now when I go into recovery I get all kinds of errors saying cannot mount DATA,CACHE,DALVIK,INTERNAL. I tried updating my TWRP to the latest ... No Luck. they still wont mount and show 0mb space. Phone is still working. Anyone have any input or guidance for me.
Much Appreciated
Sorta Fixed, switched to CWM recovery and all is well, although if I go back to twrp it still shows cant mount internal sd, data,dalvik etc...
Thanks for Looking and maybe this will help others that run into this problem
Click to expand...
Click to collapse
I got the same thing on my Samsung Galaxy s3.
Hello all!
This is my first foray into the world of custom Android systems, and I'm having a hell of a time with it... if somebody would be able to help me out, I would greatly appreciate it.
First off, the situation:
I am on Sprint, and I recently bought a Samsung Galaxy S3 (SPH-L710) from Sprint to use as a backup phone, I used it for a while on Stock, then deactivated it so I could give it to my wife. First though, I wanted to put a custom ROM on it, and experiment/play around a bit and see what this world of options could do for me. Long story short, I ended up flashing an AICP ROM, and everything seemed to go smoothly, but when I went to activate the phone on my account again and it would not work no matter what I tried (details below). I figured maybe I could activate on the stock setup then just restore my custom setup, so I tried to revert to my stock ROM backup and I couldn't do anything because I was constantly getting messages that various programs had closed... Then I tried to wipe and restore my custom ROM backup and I get stuck in a boot loop... so I tried to flash a stock recovery and I get stuck in a boot loop... I'm out of ideas here, and now I'm stuck with a phone I can't use or do anything with, and I can't activate.
Details:
The initial rooting/install process seemed to work ok, and was fairly straightforward. I followed various guides on http://galaxys3root.com/ to get my phone rooted and backed up (Don't recall which ones now, but I've read through so much by now I don't know if it matters...).
My phone:
Samsung Galaxy S3 (Sprint) SPH-L710
Modem: L710SPRDNJ2
My Desktop:
Debian Linux
Here's the steps I performed:
Rebooted phone in Odin mode
Downloaded CWM S3 Sprint Recovery from the http://galaxys3root.com/ website (can't find the link any more)
Flashed the CWM recovery using Heimdall then rebooted phone into CWM
Installed SuperSU through CWM, then rebooted
Checked that the phone was rooted successfully (it was), then ran Titanium Backup on the whole device to my SD card, then copied the backup files to my desktop computer
Rebooted into CWM, and performed a backup through CWM, then rebooted and copied the CWM backup to my desktop.
Downloaded AICP Rom for my phone from here: http://downloadandroidrom.com/file/GalaxyS3Sprint/roms/AICP/aicp_d2spr_lp-10.0-RELEASE-20150707.zip, put it on my SD card, then installed it through CWM and rebooted
At this point, I was happy with how everything was working, so I did some minor theme customizations then made another backup through CWM, and copied it to my computer, but I did NOT run Titanium this time...
After all of this, I tried to go ahead and activate it through the Sprint web service. This process failed continuously with an unhelpful error message of "Sorry, this device can't be activated right now". I then got on Chat to see if they could activate it manually, and then the problems began. They did their thing activating the phone, but when I booted up I got no data connectivity, and couldn't make calls, and the SIM was not changing over to the new number. I was on the chat with them for over an hour trying to get the situation resolved, but that finally ended when they started asking me to punch in ## codes, because I discovered that none of them worked on my custom ROM. Some quick research told me that this was non-trivial to get around so I had them switch everything back and I started researching the issue.
I found this thread: http://forum.xda-developers.com/showthread.php?t=1626638&highlight=sph-l710 that looked like it would let me do what I needed from the custom ROM, but I couldn't tell if it would fix my problem for sure, so I figured "I'll just restore my stock setup from that backup I took, activate it and update, then start over". This is when things got really frustrating...
First I rebooted into CWM, went to 'backup/restore', and restored my stock backup
Rebooted, and as soon as I got past the lock screen, I get inundated with messages of various apps being closed unexpectedly.
I researched a bit, discovered the issue may be caused by stale dalvik cache, so I rebooted into CWM, cleared the dalvik cache, formatted the /cache partition, then tried to restore the stock backup again, but this time I get stuck in a boot loop.
I then rebooted into CWM, tried to restore the backup of my AICP ROM, only to be stuck in a boot loop as well.
Trying to get into any usable system, I rebooted to CWM, cleared dalvik cache, then formatted /cache, /data, and /system just to be sure, and re-flashed the base AICP ROM I started with. This worked fine, and before long I had stock AICP back
Since I still couldn't get the phone to activate in the custom ROM, and my backups are apparently completely useless, I rebooted into CWM, wiped dalvik, /cache, /data, and /system again and tried to install a different stock ROM I found in the XDA forums (here: http://forum.xda-developers.com/galaxy-s3-sprint/development/stock-rom-4-4-2-t3010642) only to be greeted by another bootloop
At this point I've spent well over 24 man-hours trying to get this to work, reading, researching, flashing, etc all to no avail. Nothing I do seems to work, and it seems like every article, tutorial, or forum thread I read either has nothing to do with my device, is too old, or doesn't describe my problem.
I'm at wits end, and am so frustrated I'm ready to just give up and smash this device and buy a new one... My questions to the community are as follows:
I know I screwed up on a couple of things, but in my initial research of doing this there was no indication that these were even things I needed to watch out for... Is there any more organized sources of information for doing this sort of thing?
Does anybody else out there use Sprint on a custom ROM, and if so how you you pull this off
Where else have I screwed up, and how can I fix this situation? (My end goal is still to get the S3 onto Sprint with a custom ROM)
What can I do differently next time? I would like to figure this out and do it to other phones and devices I have, but if it's this much trouble every time, I just don't have the time to mess with it.
Thank you in advance, and I appreciate any information that the community can provide.
This sounds like a CWM problem to me. If I were you, I'd boot the phone into Odin Mode and flash TWRP ( www.twrp.me ) then try flashing the latest aicp nightly downloaded from the official site ( www.aicp-rom.com ). Check the md5sums on everything! Then maybe try flashing a touchwiz ROM and activating your phone. Remember that you need to wipe the internal storage when you go between KitKat and lollipop.
I'm fairly certain you have to do activation with the stock Touchwiz roms -- once the phone is activated you can flash a custom.
You should go into recovery and wipe everything (System/data/etc) EXCEPT for the External SD Card
Power off - pull the battery for a few - power on directly into download mode
Odin NJ2 back onto the phone and reboot and activate it (skip through most of the setup since you'll flash a custom after)
Once you know it's activated and working under the stock Touchwiz, then again power off and Odin TWRP recovery
Then you can go back into recovery, wipe everything except External SD, and flash the custom rom back on.
Looks like swapping CWM for TWRP did the trick.
Flashed TWRP no problems, and put CleanBean on there to get the phone activated. Still wouldn't work automatically over the Sprint website, but I got on chat with them and they fixed me right up. Downloading a fresh copy of AICP now...
Is it worth it to keep the CWM backups I made earlier, or should I just go ahead and flush them? I figured just get rid of them since restoring them wasn't working anyway, but I figured I would ask.
Now to move all the data over to the new phone. Thanks so much for your help guys!
afarris01 said:
Looks like swapping CWM for TWRP did the trick.
Flashed TWRP no problems, and put CleanBean on there to get the phone activated. Still wouldn't work automatically over the Sprint website, but I got on chat with them and they fixed me right up. Downloading a fresh copy of AICP now...
Is it worth it to keep the CWM backups I made earlier, or should I just go ahead and flush them? I figured just get rid of them since restoring them wasn't working anyway, but I figured I would ask.
Now to move all the data over to the new phone. Thanks so much for your help guys!
Click to expand...
Click to collapse
Get rid of them. TWRP can't restore CWM even if the backup is good