Hello guys,
Long time reader, first time poster over here.
I'm having a serious problem and wouldn't bother you with it, but i've scrolled through hundreds of forumposts, tried serveral things but haven't find the solution yet. (because the problems in those posts are only a part of my problem :s)
So I hope, by posting and explaining it myself, you guys can help me fixing my HTC One S (wouldn't want to lose it this way -.- )
Here it goes: my phone has been rooted for more than a year now, i've used several ROMs, been through some problems but no big deal and was able to solve them myself).
A couple of months ago, I decided to try the newest Cyanogen (11) mod based on Android 4.4, needed a new recovery but got it installed and working fine.
After a while I installed a Nightly update, and after that the trouble started and went from bad to worse to nearly death
first of all the phone kept rebooting at total random moments, enormously frustrating!
so I decided to do another update, after this update, I wasn't able to turn my Wi-Fi on
No big deal i thought, but after a while it began to annoy me, so another Nightly update was incoming
After this update **** really got messy, the message "com.android.systemui has stopped" kept popping up and the only thing I could do was click OK, then it popped back up -> OK -> and so on and so on
so my phone was as good as useless at this point
At this point I've had it with this ROM, so I put another one on my internal SD card (via coupling with my PC): Beanstalk 4.4 STABLE
This new ROM actually was installed as an update of the previous one, so the damned message "com.android.systemui has stopped" was still popping up constantly.
At that point I totally had it with 4.4 and decided to put an older ROM on it with which i've had had a good experience.
And that's where **** got fcked up:
When I go into recovery (CMW 6.0.4.5) and want to access my internal storage, it says "E: can't mount /storage/sdcard0"
So I wanted to connect to my pc to flash a new ROM to my device using Fastboot, but my pc isn't recognizing my phone and neither is Fastboot.
In fastboot, when I try "fastboot device" it keeps searching and doesn't find my device.
My PC however sees my phone, cause I hear the usbconnection sound when they're coupled, but it isn't showing up as a Removable Storage Device.
So to summarize:
once my phone is booted, i can't do anything apart from clicking OK on the "com.android.systemui has stopped" alert
in recovery, i can't mount my internal storage
when 'connected' to the PC, the PC and fastboot can't detect the device.
Other info:
i've tried it on a pc running W7 and W8
phone is HTC One S S4
I hope you guys can help me out here!
PC connection
DieterW91 said:
Hello guys,
Long time reader, first time poster over here.
I'm having a serious problem and wouldn't bother you with it, but i've scrolled through hundreds of forumposts, tried serveral things but haven't find the solution yet. (because the problems in those posts are only a part of my problem :s)
So I hope, by posting and explaining it myself, you guys can help me fixing my HTC One S (wouldn't want to lose it this way -.- )
Here it goes: my phone has been rooted for more than a year now, i've used several ROMs, been through some problems but no big deal and was able to solve them myself).
A couple of months ago, I decided to try the newest Cyanogen (11) mod based on Android 4.4, needed a new recovery but got it installed and working fine.
After a while I installed a Nightly update, and after that the trouble started and went from bad to worse to nearly death
first of all the phone kept rebooting at total random moments, enormously frustrating!
so I decided to do another update, after this update, I wasn't able to turn my Wi-Fi on
No big deal i thought, but after a while it began to annoy me, so another Nightly update was incoming
After this update **** really got messy, the message "com.android.systemui has stopped" kept popping up and the only thing I could do was click OK, then it popped back up -> OK -> and so on and so on
so my phone was as good as useless at this point
At this point I've had it with this ROM, so I put another one on my internal SD card (via coupling with my PC): Beanstalk 4.4 STABLE
This new ROM actually was installed as an update of the previous one, so the damned message "com.android.systemui has stopped" was still popping up constantly.
At that point I totally had it with 4.4 and decided to put an older ROM on it with which i've had had a good experience.
And that's where **** got fcked up:
When I go into recovery (CMW 6.0.4.5) and want to access my internal storage, it says "E: can't mount /storage/sdcard0"
So I wanted to connect to my pc to flash a new ROM to my device using Fastboot, but my pc isn't recognizing my phone and neither is Fastboot.
In fastboot, when I try "fastboot device" it keeps searching and doesn't find my device.
My PC however sees my phone, cause I hear the usbconnection sound when they're coupled, but it isn't showing up as a Removable Storage Device.
So to summarize:
once my phone is booted, i can't do anything apart from clicking OK on the "com.android.systemui has stopped" alert
in recovery, i can't mount my internal storage
when 'connected' to the PC, the PC and fastboot can't detect the device.
Other info:
i've tried it on a pc running W7 and W8
phone is HTC One S S4
I hope you guys can help me out here!
Click to expand...
Click to collapse
I've had success getting a connection to Windows just be using a different USB port, the ones at the back are best. Then at least you get fastboot access...But I also still have the problem with the sdcard, still working on that, trying to figure out a way to fix it from fastboot...
any progress yet rosanna? I was also able to make the connection with my pc, by using the usb ports on the back (thanks for that!). But I haven't been able to mount my sd card yet. I tried with another recovery but that didn't do the trick.
I got into the UI of my current ROM, and then my pc said I needed to format the SD before I could use it.
But I wasn't sure this is a good idea to do in windows.
Anyone know if it is save to format your internal sd card when prompted to do so in windows?
Have a look here
Sent from my ElementalXed One S
Try using a Linux live cd (try Ubuntu). You'll need a blank DVD to burn the iso to. Reboot your computer and see if it recognizes your device (no drivers needed). If it does try a more stable build this time.
benJX said:
Have a look here
Sent from my ElementalXed One S
Click to expand...
Click to collapse
I did read through that thread and tried it.
But i'm not quite sure everything went as plannend.
I even think it went wrong on the first step, flashing back to the stock recovery. This one isn't included in the all in one toolkit right?
So I started searching for one myself (I have an S4 VLE version of the phone) but I haven't downloaded one yet, although I've seen links that bring me to new links and so on and so on, I wasn't quite sure which link to trust.
If you could help me further I would really appreciate it
DieterW91 said:
I did read through that thread and tried it.
But i'm not quite sure everything went as plannend.
I even think it went wrong on the first step, flashing back to the stock recovery. This one isn't included in the all in one toolkit right?
So I started searching for one myself (I have an S4 VLE version of the phone) but I haven't downloaded one yet, although I've seen links that bring me to new links and so on and so on, I wasn't quite sure which link to trust.
If you could help me further I would really appreciate it
Click to expand...
Click to collapse
1 minute - downloadlink is on the way
Here you are: http://forum.xda-developers.com/attachment.php?attachmentid=2622663&d=1394422408
You can flash it with the toolkit selecting "Custom recovery".
When you're Storage is back alive and kickin' you can flash a custom revovery again.
My favourites are
TWRP 2.7.0.0 - http://techerrata.com/file/twrp2/ville/openrecovery-twrp-2.7.0.0-ville.img
and
PhilZ advanced CWM - http://goo.im/devs/philz_touch/CWM_Advanced_Edition/ville
In my opinion TWRP is easiest to handle and PhilZ has some more features.
DieterW91 said:
I even think it went wrong on the first step, flashing back to the stock recovery. This one isn't included in the all in one toolkit right?
Click to expand...
Click to collapse
Another direct link here, I personally flashed it manually trough fastboot, for me the easiest and fastest way to do it. Then proceed to the clear storage and flash your custom recovery (like @LS.xD I recommend TWRP but this is your choice )
THX Guys! :victory:
Thanks to your links to the stockrecovery, my phone is back alive and kicking.
I feared for a while for my phone, but on the other hand I knew the xda community would help me fix it!
1000 times thanks :good::laugh:
DieterW91 said:
THX Guys! :victory:
Thanks to your links to the stockrecovery, my phone is back alive and kicking.
I feared for a while for my phone, but on the other hand I knew the xda community would help me fix it!
1000 times thanks :good::laugh:
Click to expand...
Click to collapse
Feel free to hit the "thanks" button
Related
I have been following similar threads, but there seems to be just enough that is different with my Gtab I thought I would try a new one in my last ditch effort.
I have most been runnung Tnt lite and everything worked fine. Then curisoity got to me and I installed the Cyrogen 7. I was having issues with gapps and followed instructions until it wouldn't boot past the BitTrix presents....
I was able to get into CM but after all the formarts and such from the intructions on gapps I no longer had any backs or recovery files.
Then I tried the NVflash. First problem is that I could never confirm I was in APX mode. My Linux CentOS machine could see the gtab but the NVFlash would not run. So a pal of mine who is really good with Linux grabbed tnt lite and was able to directly transfer it to the SD card.
Everything looked hopefull until just before the home screen should appear it powers down. then I when into CM and re-installed tnt. Same problem so I go back to CM and try to mount data. I get an error that it doesn't exisit. then it powers down in CM. Each time I go into CM it shuts down sooner and sooner.
I opend the device up and completed a manual reset to no sucess. I hear people say its really heard to brick these things. PLEASE someone help show me that I am not that talented!
no help?
17 views and no replies? Someone has to have something for me right?
Hi
OK, i am no expert here but have you tried just putting a new ROM zip file onto your SD card and rebooting into recovery mode Power & Volume + and choosing the zip file you just copied over?
Works for me everytime but then mine has never died.
Ian
Ianmrr said:
Hi
OK, i am no expert here but have you tried just putting a new ROM zip file onto your SD card and rebooting into recovery mode Power & Volume + and choosing the zip file you just copied over?
Works for me everytime but then mine has never died.
Ian
Click to expand...
Click to collapse
My main issue now is that the power wont even stay on long enough to get to that point.
Instructions if you have a brick.
http://forum.xda-developers.com/showpost.php?p=11230514&postcount=1
mkuzminov said:
Instructions if you have a brick.
http://forum.xda-developers.com/showpost.php?p=11230514&postcount=1
Click to expand...
Click to collapse
These are the instructions I followed when I opened it up. This did not work for me. You can see I posted in that thread as well.
Through all the message boards I read, not one single person including myself thought of the most basic answer.......The battery was dead
I work on computers for a living and this is yet just another example of starting with the basics, no matter what you think your skill level is.
Once charged, I was able to read the zip off of the card. Flashed and everything was great. Until I dropped it, literally minutes afte I got it working.
I am starting to think I wasn't meant to use this tablet.
I guess we all ASSUMED that you had charged it, or at least were trying w the adaper plugged in... I know that was what I assumed ...
Jim
Following various threads here how to successfully unlocking and rooting their device, I've failed on so many levels.
At the moment I think my xoom is semi-bricked because its just stuck on the M screen. I've think I got the recovery screen working last night as I was able to go into recover mode but after updates through wifi I think it possibly stopped it.
So when i reboot and go into recovery mode, I get an exclamation mark over an android. I've tried rebooting and just got it to mount back on Fastboot but when I've tried to wipe it and reflesh it to (recovery-Tiamat-R4c-100611-1150-cwm.img) its not doing what its suppose to do and giving me "unknown partition, Failed to process command error (0x300003)
Any ideas what I need to do?
Btw, I can reboot, voldown and then volup to choose the 3 options but like I said I can't get into the recovery mode properly.
Schizophonic said:
Following various threads here how to successfully unlocking and rooting their device, I've failed on so many levels.
At the moment I think my xoom is semi-bricked because its just stuck on the M screen. I've think I got the recovery screen working last night as I was able to go into recover mode but after updates through wifi I think it possibly stopped it.
So when i reboot and go into recovery mode, I get an exclamation mark over an android. I've tried rebooting and just got it to mount back on Fastboot but when I've tried to wipe it and reflesh it to (recovery-Tiamat-R4c-100611-1150-cwm.img) its not doing what its suppose to do and giving me "unknown partition, Failed to process command error (0x300003)
Any ideas what I need to do?
Btw, I can reboot, voldown and then volup to choose the 3 options but like I said I can't get into the recovery mode properly.
Click to expand...
Click to collapse
Could I ask what steps in rooting you completed successfully and where exactly it went wrong?
Then, what exactly have you done to try to move forward?
Also, which guide did you use?
Don't worry, you're not bricked if you can get to fastboot.
okantomi said:
Could I ask what steps in rooting you completed successfully and where exactly it went wrong?
Then, what exactly have you done to try to move forward?
Also, which guide did you use?
Don't worry, you're not bricked if you can get to fastboot.
Click to expand...
Click to collapse
Last night I followed this videolinked in http://www.youtube.com/watch?v=OYc1lVWm7ks to Unlock OEM my device
I think that worked fine because it didn't throw up any hiccups.
I then followed this http://forum.xda-developers.com/showthread.php?t=1242241 to root it. It didn't have superuser so I downloaded it and installed it and then tried Terminal on the "SU" command. Said I did not have 'permissions'
This morning, I then followed this Youtbue link http://www.youtube.com/watch?v=ZsVpY0PDwtQ and after the first reboot of puting the new .img, it failed to reboot. Now I'm stuck on the M screen.
I think I managed to get my computer to pick up the device in adb fastboot because it responds to that. However when I type in adb devices it doesn't pick up anything...
Next after messing around I managed to flash it to the boot.img on this, http://forum.xda-developers.com/showthread.php?t=1049901
It flashed it ( I think) and worked without errors unlike the other flash I tried today, and its still stuck in M screen.
BTW, this is a UK Wifi Zoom.
Little update - I've downloaded and flash this boot: boot_3.1_insecure.zip from http://forum.xda-developers.com/showthread.php?t=1049901 and now boots up. However my Wifi has now disappeared. I'm in the process of doing a factory reset but will this work?
Still no avail - need to get this wifi working again soon. Think I've finally got access to superuser
Schizophonic said:
Little update - I've downloaded and flash this boot: boot_3.1_insecure.zip from http://forum.xda-developers.com/showthread.php?t=1049901 and now boots up. However my Wifi has now disappeared. I'm in the process of doing a factory reset but will this work?
Still no avail - need to get this wifi working again soon. Think I've finally got access to superuser
Click to expand...
Click to collapse
It sounds like you are on the right track. Hang in there, you'll make it!
Do you have access to an Ubuntu OS? when you connect an android device to a PC running Ubuntu it will mount the internal memory to the PC which makes it much easier to browse the partitions. Also, Go ahead and reflash the CWM recovery through Rom manager (if thats available to UK users) so that hopefully youll get a fresh recovery.img to work with. As far as ADB not noticing the xoom, you probably erased the adb drivers, and is the usb cord youre using 100% data transferable type? I about pulled my hair out a few times because adb wouldnt recognize my phone but realised I was using an older micro usb cable that only allowed electrical current for charging, not data transfer capable. You might also be able to find a clean nandroid backup file from a fellow UK xoom owner, that you trust, and see if they dont mind sending you their backed up boot-img and system-img. Just some guesses, but sounds like you got it pretty well figured out
Hello all, after a bit of self taught ADB and etc and understanding the mechanics how to successfully flash a Xoom, I managed to follow another guide from stratch (unlock oem, etc) and flashes it to the US stock 3.2.2 rom. It picked up wifi but couldn't connect for some reason - maybe different frequency?
Anyway since then I've installed one of the custom Roms here Team Tiamat Xoom Rom 2.2.2 and all is well now Got my Xoom back up and running with superaccess.
Thanks for all the info on this forum, great place for resource
Mind you, coming from a background with no experience with ADB, it was a bit mind boggling but I managed to get there in the end. Just a bit of feedback for those authors with the guides - maybe put a little subsection on the basics of how to get things prepared and up and running. This I think will help a lot of people who cannot sit for hours on end to trouble shoot something if it goes wrong. Most of the guides here are very useful and handy but at time I just kept saying to myself "wtf, what, where, huh?"
Schizophonic said:
Hello all, after a bit of self taught ADB and etc and understanding the mechanics how to successfully flash a Xoom, I managed to follow another guide from stratch (unlock oem, etc) and flashes it to the US stock 3.2.2 rom. It picked up wifi but couldn't connect for some reason - maybe different frequency?
Anyway since then I've installed one of the custom Roms here Team Tiamat Xoom Rom 2.2.2 and all is well now Got my Xoom back up and running with superaccess.
Thanks for all the info on this forum, great place for resource
Mind you, coming from a background with no experience with ADB, it was a bit mind boggling but I managed to get there in the end. Just a bit of feedback for those authors with the guides - maybe put a little subsection on the basics of how to get things prepared and up and running. This I think will help a lot of people who cannot sit for hours on end to trouble shoot something if it goes wrong. Most of the guides here are very useful and handy but at time I just kept saying to myself "wtf, what, where, huh?"
Click to expand...
Click to collapse
My guide, which is highlighted in the Xoom Heaven thread has a large section on setting up your adb files etc.
http://forum.xda-developers.com/showthread.php?t=1249798
Rooted 3.2 Xoom FAIL
Hi All,
Not the best way to join the boards but I am in deep....
I have a canadian wifi xoom on 3.2. I followed these instructions (How to root 3.2 on US WiFi & Verizon 3G XOOM! (Windows and Mac)) to root my xoom and was having issues with a wifi error.
I decided to use the Canadian boot.img file and when I rebooted the xoom got stuck on the moto logo and is no longer recognized by my computer.
I have tried resetting through the android recovery (I dont have anything 3rd party installed) but no luck. I am afraid that this thing is a total write off.
Any thoughts? Thanks
Blair
Hello all
So I thought I bricked my phone not too long ago but I think there may still be hope left. I had the 3.18 version of AT&T and Android 4.1.1 installed on my phone and wanted to root it. Found out the new process and after a couple of hours got to root it. I attempted to get S-Off multiple times but I couldn't do it (difficulties with failed: 99 error but I had CID = 111111). So I was attempting to get the new Cyanogenmod on my phone but stupid, stupid, newb me downloaded and tried to get the HTC One X version on my phone instead of HTC One XL. I was reflashing it over and over again because I thought it wasn't working but found out how much of a dunce I was.
Now I am stuck in a continuous load with sticking at the HTC screen with red writing saying "this build is for development purposes only...." It turned off and wouldn't turn on again so I thought I bricked it but later today I was able to start it up again. I can get into bootloader and I can get into my recovery mode. I have TWRP 2.3.3.1. However what I can't do is mount my SD card. So when I plug in my phone to my computer the USB sound goes off but my SD card doesn't appear. Also on TWRP, in the mount option, I cannot mount the SD card as it won't let me click it. So I can't download things from my computer and put it on my phone
If there is anyone out there that can save my phone (and save me another $300) it would be much, much appreciated. I know I'm a sucky newb, and I know you guys get tired of this but I promise you I thought I read enough. I'm just trying to learn.
UPDATE:
Also I believe I've narrowed the problem down more. I can issue commands using the terminal. Tried to reboot RUU and boot oem from there but still didn't work. Think phone is not recognizing SD card
you give this a try. http://forum.xda-developers.com/showthread.php?t=1942519
nik92990 said:
you give this a try. http://forum.xda-developers.com/showthread.php?t=1942519
Click to expand...
Click to collapse
THANK YOU VERY MUCH
You don't know how much I appreciate this. You have saved my phone. :good: :highfive:
no problem
This post doesn't seem to match others asked before.
I had a perfectly working rooted/rom'd HTC One (M8). Unfortunately, screen cracked so I sent it off to the insurer to sort. It came back looking great. However, I was now unable to access any of the internal storage. Everytime I tried to download a photo, voice clip or Mod Edit: removed mention of warez it would say 'unable to download', 'cannot save' or something along those lines.
I checked to see the device was still rooted. It was. Nevertheless, I perhaps in ignorance, ran through all the steps over again and spent 3.5 hrs doing so! I now have a wonderful adb file on my desktop and I was fiddling around doing fast reboots etc and trying to flash a customrom in the hope that this would fix the storage invisibility/lack of permissions. I tried fixing with busybox etc but I couldn't even install busybox as it didn't recognise that there was any internal storage whatsoever! I also could not load onto my storage (for the same reason!) the latest SuperSU zip to flash as a rom.
In the end, through fiddling about, I was able to find my old storage pack. It was all there and I located an old SuperSU from when I had previously rooted about 6 months ago (an old version now I assume). Flashed this and rebooted. I was still adb connected so ran a fastboot and chose to run the TeamWin Recovery Wipe (standard setting, not advanced).
When wiped, I tried to get my phone to turn back on thinking it would be factory reset and I could start again but now I literally cannot get my phone on!! It is plugged into the computer via USB (i've tried disconnecting it too) and no matter what I try I cannot get this phone to do anything now - it's just a black screen that doesn't look completely off if I look closely it looks like it is on somehow....? Tried holding down vol down and power - nothing. It has flatlined!
Any help PLEASE!!!!! ?????
Hi, thank you for using XDA Assist. The best place to get help is in your device's specific forum here, http://forum.xda-developers.com/htc-one-m8 To get help on your specific problem try asking here, http://forum.xda-developers.com/htc-one-m8/help/help-thread-htc-one-m8-questions-t2897783
Hi all hope someone can help. My oneplus 1 was playing up a bit just lately so I thought I would give is a wipe and fresh install of a Sultan Rom that I had been using. Backed up using Titanium and Twrp to play it safe. Then like a complete novice (not the next stage up which is where I would put myself) I ticked all the check boxes and wiped. I now have no Operating System on the phone :crying: although I have a version of Twrp sitting on there.
So, off to google I trawled to find numerous posts threads and ways to get back up and running using fastboot, ADB sideloading etc. So after a day and a half of trying these methods and various images to download and flash I am no where near having a working phone.
I need help if one kind soul can help and walk me through the process of getting this phone back up and running.
Thanks for any help that comes this way.... Foz
TWRP is present, just copy paste a rom and gapps into the phone. Go into twrp, flash the rom and gapps and reboot.
Did you try this?
hi thanks for replying.
I've not been able to do as you suggest as the phone is not showing up in explorer where I copy/paste Rom/Gapps. The laptop is "seeing" the phone as there is an audible sound when it gets plugged into the USB socket and when using the fastboot command prompt, it throws a serial number at me. this is why I've tried to go down the ADB/Fastboot options of installing a Rom/IMG with no success
Install the drivers of ur phone on ur pc, download the stock rom cm13.1 from xda, and flash it.
---------- Post added at 11:44 PM ---------- Previous post was at 11:42 PM ----------
Or the other option is, get otg drive. Put rom there and flash.
I'm not having any luck with the first suggestion you gave. Every image that i am trying to flash results in some kind of error. I've even tried to put the most up to date version of Twrp on (3.2.1-0-bacon) but I'm not getting any joy with that. Even though I can "talk" to the phone in Fastboot mode I'm getting no joy. I'm thinking of re installing all the ADB set up again just to make sure
Your second suggestion is not an option for me at the minute as i don't have the kit to try it.
Thanks for you input though.
Try using a OTG cable with a thumb drive
adamfoz said:
hi thanks for replying.
I've not been able to do as you suggest as the phone is not showing up in explorer where I copy/paste Rom/Gapps. The laptop is "seeing" the phone as there is an audible sound when it gets plugged into the USB socket and when using the fastboot command prompt, it throws a serial number at me. this is why I've tried to go down the ADB/Fastboot options of installing a Rom/IMG with no success
Click to expand...
Click to collapse
maybe I missed something but you have to connect your phone to the PC when it is in recovery mode (when OPO is turned off press and keep pressed vol down + power button until you see TWRP logo). The pc should see your phone as an external drive, then you can move a ROM and Gapps and flash with TWRP.
-Pepe said:
maybe I missed something but you have to connect your phone to the PC when it is in recovery mode (when OPO is turned off press and keep pressed vol down + power button until you see TWRP logo). The pc should see your phone as an external drive, then you can move a ROM and Gapps and flash with TWRP.
Click to expand...
Click to collapse
You're not missing anything, I don't think. The phone is booted up and the TWRP screen is on. The phone is connected to the laptop and I can hear an audible noise, but there is nothing in the explorer folders that looks like A001 which is what the phone usually looks like when plugged in. If it was I'd like to think it would be straight forward.
se7enlyn said:
Try using a OTG cable with a thumb drive
Click to expand...
Click to collapse
Any recommendations? never used one so I wouldn't want to get the wrong one or one that crap it only lasts 5 minutes. Thanks
EDIT... just ordered this cheap effort https://www.ebay.co.uk/itm/Micro-US...565007?hash=item3af91d86cf:g:y0MAAOSw6VRZ5mtz . Hopefully it will get me back up and running.
should be ok but if not try this https://www.ebay.co.uk/itm/2x-Micro...475501&hash=item25bec575e8:g:z~YAAOSwPkJafy8v its what i buy
afternoon all. right, the postie has turned up with my thumb drive.Could someone advise as to the procedure to get me up and running?
Thanks Foz
ok ... I've now got an OS on the phone...
Thanks to all who have helped.
just as an add on to this thread in case someone has a similar problem.
The phone still wasn't running right and I hadn't installed Gapps so I decided to re flash and start again. Now when I booted into twrp to reflash, it couldn't read the files on the SD card in the thumb drive. I ended up having to re flash a different version of twrp on the phone which miraculously could see the files on the SD card which I installed. The issue I now have is that I don't think there is an area on the phone to store stuff. Whenever I take a pic the camera can't see or access the SD card. When the phone is connected to the laptop, there are no folders within explorer to view so I can't drag n drop files etc to the phone. any ideas/suggestions as to get this sorted?
Thanks in advance... Foz
OK we're sorted. After trying (nearly) every help guide with no luck, I found a similar problem on a YouTube video. In the comments, someone suggested trying to use a Bacon Root Toolkit by WugFresh. after a few minutes setting it up, I've have finally flashed 12.1-YOG4PAS3JL. It has given back my internal SD card. Going to do a back up in a moment and I'm off to flash a more recent ROM
I hope this info helps someone out.
Cheers all