Related
I went from stock Froyo 2.2 to MIUI v3 using the following link.
http://forum.xda-developers.com/showthread.php?t=992251
Now when I startup my phone...
For one, it won't connect me to a network so I can't get phone calls or texts etc.
Also my volume up button is switched with my volume down button.
Trying to make a phone call it says "Mobile network not available".
Does anyone have any information to help me fix this problem? I am stuck.
Yea flash the miui version made for the vibrant in our development section
http://forum.xda-developers.com/showthread.php?t=992302
The one you flashed is for the International galaxy S
bfranklin1986 said:
Yea flash the miui version made for the vibrant in our development section
http://forum.xda-developers.com/showthread.php?t=992302
The one you flashed is for the International galaxy S
Click to expand...
Click to collapse
Ok sooo...
I downloaded
kernel-cm-7-INITIAL-Vibrant-signed.zip
renamed it to update.zip
copied the update.zip along with the MIUI 1.5.20 english pack one to the root of my SD card (internal sd root)
Went into recovery mode, and tried to flash update.zip. It gave me some assert error right away. Now my phone is in a cycle of rebooting where it reboots into the flashing thing, tries to load real quick and then reboots itself.
Any tips? I'm kinda scared.
Odin back to stock and then try again, this guide by s15274n has all the files you need and step by step instructions.
http://forum.xda-developers.com/showthread.php?p=13132341#post13132341
The vibrant files you flashed probably weren't compatible with the I900 kernel/recovery you had flashed.
GTASouthPark said:
Ok sooo...
I downloaded
kernel-cm-7-INITIAL-Vibrant-signed.zip
renamed it to update.zip
copied the update.zip along with the MIUI 1.5.20 english pack one to the root of my SD card (internal sd root)
Went into recovery mode, and tried to flash update.zip. It gave me some assert error right away. Now my phone is in a cycle of rebooting where it reboots into the flashing thing, tries to load real quick and then reboots itself.
Any tips? I'm kinda scared.
Click to expand...
Click to collapse
odin jfd, root, flash recovery then start over with the cm7 kernel then mui.
I'm having a problem following the guide...
Under 2 - Download 3 files..
Mount your phone and move the rom to the internal
AND the UPDATE.ZIP << DOWNLOAD
file if you wiped both internal/external or need to root.
Power down the phone, or pull the battery.
Click to expand...
Click to collapse
I don't know how I can get my phone mounted. Whenever I plug my phone into my computer (with the battery in), it automatically reboots itself and starts the crazy reboot thing. I also can't get back to recovery or downloading mode, it automatically goes back into the reboot thing.
And then in step 3 where it says start Odin, plug in your usb cable. With the battery out of your phone hold both volume buttons for a couple seconds and then plug in your USB cable. That doesn't take me to downloading mode.
EDIT:
Okay I figured out how to get it into downloading mode again. I need to do what it says above by holding the volume buttons with the battery out etc. Then you add the battery.
Hi guys. I got Odin to work. got back to stock.
Then got back into recovery mode to flash the cm7 kernel...
It is the same error as last time. Here's the actual error this time.
-- Installing: /sdcard/update.zip
Finding update package...
Opening update package...
Installing update...
assert failed: is_mounted("/mnt/sdcard")
E:Error in /sdcard/update.zip
(Status 7)
Installation aborted.
GTASouthPark said:
Hi guys. I got Odin to work. got back to stock.
Then got back into recovery mode to flash the cm7 kernel...
It is the same error as last time. Here's the actual error this time.
-- Installing: /sdcard/update.zip
Finding update package...
Opening update package...
Installing update...
assert failed: is_mounted("/mnt/sdcard")
E:Error in /sdcard/update.zip
(Status 7)
Installation aborted.
Click to expand...
Click to collapse
Are you going under install zip from sdcard or just pressing reinstall packages? Instructions say to select reinstall packages after you rename it update.zip
bfranklin1986 said:
Are you going under install zip from sdcard or just pressing reinstall packages? Instructions say to select reinstall packages after you rename it update.zip
Click to expand...
Click to collapse
I boot into recovery mode. It takes me to the stock recovery mode. Then (with the update.zip and the miui zip in the root) I hit reinstall packages. It takes me to the clockwork recovery. Then I do install zip from sdcard. Trying to install the update.zip or the miui at this point gives me an error and then any kind of restarting will throw it into the reboot cycle.
EDIT:
When do I remove the battery? I do reinstall packages, and then after about a second or two it goes to the clockwork recovery, and then I removed the battery like it said. After I booted into recovery again and it took me to the clockwork recovery again, and then I tried to load the miui and again an error flashing.
EDIT 2:
For some reason Odin back to stock changed my phone to 2.1.. I upgraded it to version 2.2.1 (not using keis). I was able to get much further than normal when flashing the miui.zip.
My phone tries to startup, it gets to the Samsung loading image (which says i9000 under the samsung logo).
After that the screen goes (and stays) black. When I hit any of the buttons on the bottom, they glow white so I know that it is turned on.
I can't see anything on the screen, but I must be able to get it into downloading mode because I can get it to say 'added', and get try to start loading things, but then it starts never actually connets, it just hangs. Any ideas? Getting it back to stock right now would be fine so that it is usable again.
EDIT 3:
Ok, now I can see things again. For those who are wondering...
I had downloaded the 'Galaxy One Click Root' thing to try to root my phone before installing miui like it says. Well there's also a unroot button. I clicked that and I got it to go back into this custom recovery image. Once I did that, I navigated around a little and found something that said switch to Downloading mode. I did that, and then was able to use Odin to get back to stock. The screen is working, and so does the radio. It's back to 2.1 though. hmm..
ok so lets try this from the beginning
go ahead and odin to stock jfd (2.1)
now let phone boot as normal
no worries about letting it sit 10 mins or anything.
ok so you have the cm7 initial kernel as an update.zip correct?
3 button into recovery reinstall packages twice that should load you into clockwork
(orange clockwork menu)
1 Mounts and storage menu
Format system/cache/data (do all 3)
+Go Back+
wipe data/factory reset
Pull battery Or just press and hold all vol up + down + power
back in recovery.
install zip from sd Card
Install the Miui ROM reboot system.
lemme know how it goes.
boystuff said:
ok so lets try this from the beginning
go ahead and odin to stock jfd (2.1)
now let phone boot as normal
no worries about letting it sit 10 mins or anything.
ok so you have the cm7 initial kernel as an update.zip correct?
3 button into recovery reinstall packages twice that should load you into clockwork
(orange clockwork menu)
1 Mounts and storage menu
Format system/cache/data (do all 3)
+Go Back+
wipe data/factory reset
Pull battery Or just press and hold all vol up + down + power
back in recovery.
install zip from sd Card
Install the Miui ROM reboot system.
lemme know how it goes.
Click to expand...
Click to collapse
I was back at stock (which I'm not sure is 100% stock because when I turn on my phone, it has a samsung GT-i9000 image on the screen for a second or two before saying vibrant).
I have the update.zip and the miui on my internal sd root.
To get into recovery it's just the 2 button combo (volume - and power) for me.
I only have to hit reinstall packages once, and it takes me into clockwork.
I format the things you said and did the factory reset....
Pulling the battery and then trying to get back into recovery mode put my phone into a reboot cycle. (screen where it looks like after you do wipe data/factory reset) and then I have to odin back to stock.
The three button combo does the same thing. I can't get to the next step.
EDIT:
After the reboot cycle thing. I was able to get back into recovery mode even after it started its reboot cycle deal. Then I was able to install the miui rom. My phone has been on the Samsung Cyanogenmod boot screen for about 5-10 minutes. Not sure if it is trying to boot up miui or just stuck. I'll let it sit for another 15 minutes before thinking its stuck.
EDIT2:
Yep, It's been about half an hour. My phone is stuck on the cyanogenmod boot screen. I can't get it back into recovery or downloading either.
EDIT3:
After some serious playing around. I was able to get it back into recovery mode. Wipe everything, apply the update.zip again... and then was able to get back into downloading mode and reflash it to stock.
Does anyone know how to get to true stock, so I don't have the Galaxy-S GT-i9000 Samsung boot screen. I think that this has to do with why it is failing.
After searching around a lot more...
accidentally flashing an i9000 rom flashed the boot.bin and sbl.bin.
The files to odin back to stock jfd doesn't include the boot.bin or sbl.bin so that's why I get the extra boot screen, and why I 'brick' my phone everytime I try to flash another rom.
Apparently I will brick my phone anytime I try to flash a rom from now on, and that I need to find a boot.bin and sbl.bin combo for the vibrant if I want to be able to flash anything again or get any update past 2.1.
If anybody has any info on how to get this boot.bin and sbl.bin combo could you let me know. I can't find the files anywhere.
Hi I hope someone can help me. I have searched this forum but could not find a similar situation to what I ended up in...
I tried to install a custom ROM on my Galaxy Tab 10.1 using the CWM/Odin.
This seemed succesful but was not, it did not start but was stuck in the Samsung logo.
So I tried entering the CWM and download and install an original Samsung ROM. I can get it into CWM, but CWM cannot enter the download mode only the other mode.
In this mode all options are available:
- reboot
- apply update from SD card
- wipe data/factory reset
- wipe cache partition
All options have been tried without any luck. In the update from SD card it only shows ...
or Error opening /data/media: no such file or directory
Any ideas how I could get this directory back or put a ROM on the Samsung in this situation.
Odin does see the Galaxy but as I cannot get it into Download mode I am unable to download anything to it.
All or any suggestions are very welcome!
1. CWM (Clockworkmod) =! Odin.
In the beginning, you don't have CWM installed. You install CWM, by flashing CWM on your Phone with odin.
Odin is the Windows Programm, that is used to flash Recoveries/ROM's/Kernels onto your device.
2. it seems, that you still have the default Samsung recovery installed, that meand CWM is not yet flashed on your device.
If the flashing process was succesful (I suppose it was done with odin), but you can't get past the Samsung logo, that means, you probably flashed a rom, that isn't made for your device(ex. a GTab 10.1v Rom).
If you DID flash a wrong rom, then you probably ****ed up the partition table and removed the Download Mode(Odin Mode). Strange thing is, that you still have the Stock recovery.
Could you please redirect us to the rom you downloaded?
Also, did you flash with a repartition on and/or a .pit file?
hi Kaukassus,
thanks for the reply.
OK I checked the files and what I did.
I think I totaly screwed this up. It was a theme I tried to install the AOSP_HC_v1.3_3G+KI1.
I rooted the Tab. So first when the Tab was still functioning installed it on the TAB via USB.
Than tried to install this via update from SD card.
This appeared to work initially. But hung at the start.
After that I tried (via Power Volume Up) wipe data/factory reset.
No luck.
After that I tried wipe cache partition followed by wipe data/factory reset.
And this is what I got now..
Bad news is the Tab was/is a X-mas present and I managed to screw it up even before I officially got it !-(
The valuable lesson you're learning is that you need to be aware exactly what things you're flashing and their compatibility with your device and the software it's running.
You haven't mentioned what specific device you're using or the specific things you've tried to flash (as kaukassus pointed out, direct links to threads where you got the files you tried to flash are best). Not sure if you're aware but not all GT 10.1's are equal; there are several models out there and each and every ROM is specific to a particular device. Verizon LTE GT 10.1's like mine can't take ROMs from any other device for example, it's likely that the new T-Mobile 4G one's wont be able to trade ROMs with Verizon ones . . you get the point.
When you say you installed via USB what exactly did you mean? If you simply copied a zip file via USB to the tab to flash in recovery mode that's not installing; the flashing from recovery may be but the file copy operation is not. If on the other hand you pushed things via ADB or you flash using Odin software then that's a different story.
Best thing to do at this point is to properly identify your device, look for a stock recovery image for Odin and flash that via Odin to your device. At that point you can start from scratch again to build what you want.
Thanks Muzzy996.
You are right. I was in a rush and should have taken more time.
However I am getting somewhere. Managed to get in download mode twice today, don't ask me how. This Tab just will not go into download mode!
However I did not have the stock ROM ready to be installed.
Will keep you updated.
i have the same problem. i just rooted my device was going to overclock. decided to save my rom with rom manager. saved it device went to reboot now the samsung galaxy 10.1 shows up screen goes dim then shuts off, and will cont. do this. i can get into download mode but recovery will not work. is there anyway to download my stock rom. im using verizion 4g 10.1 any help would be great, btw sorry to thread jack
Problem solved.
Managed to get it in download mode again and install stock rom via Odin.
Appeared to work fine. But kep switching off, even after full night of charging.
This morning Tab was dead after recharging whole night..
Got it back on by holding volume down and power button down.
i found a stock rom and im trying to upload it via odin, however odin does not find my tab? any ideas. btw congrats on getting ur tab back
I crashed both my I9000 (galaxy s) flashing custom roms and my tab 10.1 (editing some system files) both ended up just looping but managed to get both back. I purchased a small connector of ebay £1.59 that has just a resistor accross pins 4&5 331k I think anyway plugging this into most samsung devices boots them into download mode. Even before getting my resistor I managed to get things working I think that you'd have to be properly unlucky to really brick a samsung I've flashed both my devices with all sorts of crap with my little resistor I just reset them with ease.
Brian
h2bmess said:
i found a stock rom and im trying to upload it via odin, however odin does not find my tab? any ideas. btw congrats on getting ur tab back
Click to expand...
Click to collapse
did you ever resolve this issue? i am currently faced with the same issue.
This worked for me.
Took out battery for about 5 minutes, insert batt, Hold vol up + power to get into download mode. Use a $5 jig from ebay/amazon if you want to force download mode. This phone is almost impossible to brick. Only physical damage can brick.Since this is an old phone the issue for recovering from a soft brick is really non availability of required files.
When you have a soft brick like this ..ie., stuck in 3e recovery. Even if you odin back to stock you cannot get into recovery (stock or cwm). You are permanently hardware locked out of recovery. Once stock odin'd to eclair or froyo phone will boot up into that rom fine but you cannot get into recovery and you cannot root. At this stage odin Darky resurrection which is available in tar/pit format. It is a rooted kernel/rom combo. Since iam a new user forum did not allow me to paste any external links here. Google for "Install Darky ROM 10.2 Resurrection" and pick first link.
Now you have rooted kernel and nice rom but still no recovery. From market download some apk installer that works with darky. I just searched for apk installer and picked the first one. Just downloading rom manager may not work since rom manager does not support older versions like eclair/froyo anymore.... Google for "com.koushikdutta.rommanager.apk" and download this apk from some cyber graveyard..Install this apk, open installed rom manager and select reboot into recovery. Now finally i had working recovery and could flash any zip , wipe format etc.. Good luck.
tip: odin must be setup (select files, uncheck boxes..) before getting phone into download mode. Otherwise odin will get stuck. Just re-start all over if this happens.
Hey all
I am considering purchasing RCA Pro 10 tablet that runs Android 4.4. From the research I did on XDA for it I was able to find that it can be rooted using Kingo. But I couldn't find any mention of a custom recovery that can support it. As you know we need the custom recovery to flash ROMs and such. Anyone know of any custom recovery that will work with this tablet?
Thanks
it hasent been rooted yet the 4.4 one which is the one walmart had on black friday is differen t some how then the orginal the connectors are in different places and the modle number is different kingo does not work
I rooted mine but it was a jumbled mess of a process. First install SuperSU, then install and run iroot, afyer that using pdanet drivers plug it into your computer and use kango, open SuperSu and update your binary, finally use a root browser and remove the app iroot installed. Iroot installs the su binary but doesnt set anything up properly, kango will set everything up but cant install the files needed for some reason so you have to use them together. Its messy but it works.
I got 2of the new of the rca pro 10 edition with the 1.5 GHz quad core m/n rct6203w46 the easyist way to root it is plug it in your PC let it download the drivers download pdanet on your PC see if there's more drivers 4 it download Kingo root set tab to USB debuging open kingo root plug in tab to USB kingo root will find it click root it will go through a few steps it will ask if u have a special kernal choose other opt it will restart tab few times and it will say its rooted and install super su if not click root again then it should be rooted restart tab after it says rooted keep attached to PC it will say root status yes then should be 2 options remove root and root again hope this helps you guys who bought the new one on black Friday big plus it never deleted Aney apps app data pics music ect and you don't need SD chip for it ... as far as a custom kernal / recovery i have no idea sorry regarden that
I have my Pro10 RCT6203W46 rooted and have TWRP installed as custom recovery. Here is a link to another thread that may help: http://forum.xda-developers.com/showpost.php?p=57437408&postcount=113
Droidify said:
I have my Pro10 RCT6203W46 rooted and have TWRP installed as custom recovery. Here is a link to another thread that may help: http://forum.xda-developers.com/showpost.php?p=57437408&postcount=113
Click to expand...
Click to collapse
Cab you elaborate on how you got TWRP installed? I have it rooted via Kingo Root!
Thanks
Sargeue said:
Cab you elaborate on how you got TWRP installed? I have it rooted via Kingo Root!
Thanks
Click to expand...
Click to collapse
Sargeue,
Using the link I supplied, I downloaded (using my PC) the TWRP image from the last link PaTF provided. I copied the TWRP image over to my tablet. Then using the link mexicandroid provided to the Rashr flash tool on Google Play, I installed it and followed the instructions in the app to flash the TWRP image to my tablet and voila!, I had a custom recovery.
I can also verify everything works in TWRP, such as backup and restore, wipe menu, etc. No custom ROMS available that I know of, so did not try to flash any ROM.
Of note: If you allow an update to the RCA firmware, you will need to re-flash TWRP as the firmware update overwrites the custom recovery.
Hope this helps.
Droidify said:
Sargeue,
Using the link I supplied, I downloaded (using my PC) the TWRP image from the last link PaTF provided. I copied the TWRP image over to my tablet. Then using the link mexicandroid provided to the Rashr flash tool on Google Play, I installed it and followed the instructions in the app to flash the TWRP image to my tablet and voila!, I had a custom recovery.
I can also verify everything works in TWRP, such as backup and restore, wipe menu, etc. No custom ROMS available that I know of, so did not try to flash any ROM.
Of note: If you allow an update to the RCA firmware, you will need to re-flash TWRP as the firmware update overwrites the custom recovery.
Hope this helps.
Click to expand...
Click to collapse
Great, will try it out. Really don't need custom rom, just like having nandroid backup. Thanks for you help!
Perfect! Worked great, easiest recovery I installed to this date. Thanks for your help again Droidify.
Thanks to the thread maker. I knew a lot with this thread.
Thanks
Thanks to Patf for posting the files, Sargeue for asking Droidify to elaborate, and Droidify for elaborating I was able to do this with no problem. This wasn't my first time rooting, and I've flashed a cfw that already had a custom recovery on it which rooted a device( don't know if thats particularly considered rooting), but I think this was the first time I flashed a custom recovery. The TWRP recovery boots just fine how it should and everything works if the instructions are followed. Thanks a bunch guys. I had already got an update prior to this and I am not sure nor do I remember what it exactly was. Its the only update I've got since I had the tablet. I still attempted this, so it was risky, but never the less everything went fine.
Hi all! I somehow soft bricked my RCA tab after updating to an OTA. Anyone have a nandroid backup of the stock ROM? Thanks!
Same problem here. OTA update screwed it up looking for help.
RCA RCT6203W46 1.9.50 firmware upgrade failures
Below is the method I found to resolve the issue I had with the most recent firmware upgrade failing. Use at your own risk.
How to resolve RCA RCT6203W46 1.9.50 firmware upgrade failures (this should also unbrick your device provided you can access stock recovery):
1. Place these 1.3.51 and 1.9.50 update zip files on your external sdcard. If you can only boot into recovery, you will need to eject the sdcard and use an alternative method to transfer these files from your PC to the sdcard and then place the card back into your tablet.
2. Boot into stock recovery. You can do this from a powered off state by simultaneously depressing the power and volume buttons until the white RCA boot screen appears. Once this screen appears, release the power button but REMAIN DEPRESSING THE VOLUME BUTTON until you are in recovery.
3. Select: Wipe cache partition. (use the volume button to move selection up or down, press the power button to make selection)
*Factory reset wipes cache too in step 4, but I am cautious.
4. Select: Wipe data/factory reset. Warning: you will lose any app you had installed.
5. Select: apply update from sdcard. Select the 1.3.51 zip file. Allow it to complete.
6. Select: apply update from sdcard. Select the 1.9.50 zip file. Allow it to complete.
7. Select: reboot system now.
8. Enjoy your upgraded RCA RCT6203W46 once again!
Probable causes for issue:
Rooted system (forgot to unroot prior to upgrade)
Removed or froze any stock app (including Vudu, Walmart, etc)
Modified a system file (build.prop, etc)
Bad luck
installation aborted...
Hello! I just did this guide but it didn't work. I always get Installation Aborted with Step 5 and Step 6 both of them are Aborted. I followed carefully your guide but still no good for my tab. I uploaded the two installation aborted message from android recovery. The first photo is when i update the firmware 1.3.51.zip and the second photo is installation aborted too when i update the firmware to 1.9.50.zip... Please see those photos if you can see what it made to abort the installation process. I hope you can help Droidify. And also, when i rooted my tab pro 10, i only remove the Vudu app and another app that was included but not the Walmart app...
Did not work for me...
Droidify said:
Below is the method I found to resolve the issue I had with the most recent firmware upgrade failing. Use at your own risk.
How to resolve RCA RCT6203W46 1.9.50 firmware upgrade failures (this should also unbrick your device provided you can access stock recovery):
1. Place these 1.3.51 and 1.9.50 update zip files on your external sdcard. If you can only boot into recovery, you will need to eject the sdcard and use an alternative method to transfer these files from your PC to the sdcard and then place the card back into your tablet.
2. Boot into stock recovery. You can do this from a powered off state by simultaneously depressing the power and volume buttons until the white RCA boot screen appears. Once this screen appears, release the power button but REMAIN DEPRESSING THE VOLUME BUTTON until you are in recovery.
3. Select: Wipe cache partition. (use the volume button to move selection up or down, press the power button to make selection)
*Factory reset wipes cache too in step 4, but I am cautious.
4. Select: Wipe data/factory reset. Warning: you will lose any app you had installed.
5. Select: apply update from sdcard. Select the 1.3.51 zip file. Allow it to complete.
6. Select: apply update from sdcard. Select the 1.9.50 zip file. Allow it to complete.
7. Select: reboot system now.
8. Enjoy your upgraded RCA RCT6203W46 once again!
Probable causes for issue:
Rooted system (forgot to unroot prior to upgrade)
Removed or froze any stock app (including Vudu, Walmart, etc)
Modified a system file (build.prop, etc)
Bad luck
Click to expand...
Click to collapse
First of all Thank You for trying to help, you are doing more that Walmart & RCA combined.
I followed your instructions and this process did not work for me. I have attached pictures of my screen after using both zip files...
Also I only rooted the tablet using Kingo I didn't remove any system apps
I think a key difference in my case is that I had TWRP installed and was able to boot into the system and unroot, install stock recovery, and then perform this procedure. Seems like you guys never had TWRP installed as recovery. I have a couple other tricks I am working on, but be patient as I vet them and see if something might work. Sorry this didn't work for you guys!
Any updates on this?
Droidify said:
I think a key difference in my case is that I had TWRP installed and was able to boot into the system and unroot, install stock recovery, and then perform this procedure. Seems like you guys never had TWRP installed as recovery. I have a couple other tricks I am working on, but be patient as I vet them and see if something might work. Sorry this didn't work for you guys!
Click to expand...
Click to collapse
No didn't use TWRP.
My tab is only 20 days old & still under warranty so I'm just going to send it back to RCA.
Was hoping to fix it myself so I wouldn't have to wait 4-6 weeks.
PHug said:
No didn't use TWRP.
My tab is only 20 days old & still under warranty so I'm just going to send it back to RCA.
Was hoping to fix it myself so I wouldn't have to wait 4-6 weeks.
Click to expand...
Click to collapse
Unfortunately, I'm boned as far as returning it goes because rooting voids your warranty.
PHug said:
No didn't use TWRP.
My tab is only 20 days old & still under warranty so I'm just going to send it back to RCA.
Was hoping to fix it myself so I wouldn't have to wait 4-6 weeks.
Click to expand...
Click to collapse
Well then there is no sense for me to keep trying to resolve this considering I have no way to test fixes, especially if what I posted resolved my particular case. I did send someone a test to try and if that is successful I will share, but outside of that I tried guys.
I guess the lesson learned here is that we all have to remember to unroot and not delete the apps that came with the device, only freeze them using Titanium or similar and unfreeze them before updating.
Hi,
I have a samsung S3 and I want to update it to lollipop or above as my nexus 5 has started randomly rebooting and I need a phone to use whilst I sort a replacement.
I have been following this guide: wccftech.com/install-aosp-android-5-1-1-lollipop-on-galaxy-s3/ as I'm a bit of a noob when it comes to this custom rom business.
I have rooted the device and installed clockworkmod recovery v6.0.1.2. and copied over the rom and the gapps file to my phone.
I then booted into recovery mode and made a backup of the current setup.
I then did the factory reset and the cache wipe(s) and installed the new zip for lollipop and then the gapps.
This is where I received an error "E: Error in /sdcard/0/0/0/Download/gapps-lp-20150314.zip (status 7) installation aborted".
I figured that I should restore to my backup now but when I press it, the app says that files can't be found.
I can see that the files that I backed up do exist but they appear to have been dumped inside a new directory called /0/0/0 (I think this has got three levels because I've tried this a few times).
Now I can't boot into an OS to get any other roms on the phone and I can't edit the files on there (I googled and saw a possible fix for the gapp status 7) and I can't get clockworkmod to recognise an external SD card so I can copy over a new rom or file to try (I have googled and it's suggested the FAT32 is the format for this phone and my size of SD card (16GB)).
Can anyone offer me some advice on how to get out of this situation?
Thanks
Sounds like you're at a place where you should start exploring using your computer instead of a recovery in order to fix your system.
I recommend using the PC software Odin and installing a stock ROM of your device. (Or perhaps using fastboot)
There's plenty of guides on how to use Odin both here on XDA and on the rest of the internet if you just look around a bit
EDIT: This link contains a (possible) fix for your problem.
http://forum.xda-developers.com/showthread.php?t=2522762
Don't use cwm as it is an outdated recovery. Use twrp instead.
Sgt.Mindfudge said:
Sounds like you're at a place where you should start exploring using your computer instead of a recovery in order to fix your system.
I recommend using the PC software Odin and installing a stock ROM of your device. (Or perhaps using fastboot)
There's plenty of guides on how to use Odin both here on XDA and on the rest of the internet if you just look around a bit
EDIT: This link contains a (possible) fix for your problem.
http://forum.xda-developers.com/showthread.php?t=2522762
Click to expand...
Click to collapse
I had a look at the link you suggested and it's one of the suggestions that had come up whilst I was googling for a fix. Unfortunately, I don't have any way to get the updated script onto the phone as the phone isn't picked up by my pc whilst it's in this state, and I can't get the recovery tool to recognise the sd card so I can't put it on there either.
I'll take a look at the stock rom or fastboot option and see if I can get back into the phone. Maybe then I can apply the fix in the suggested post.
Thanks
audit13 said:
Don't use cwm as it is an outdated recovery. Use twrp instead.
Click to expand...
Click to collapse
I'll see if I can install twrp through odin.
Thanks for your help
If the phone works in download mode, try to flash a stock rom too.
Update - fixed
Hi all, just wanted to let you know that I fixed the device with the combined advice from here:
I installed TWRP after holding the volume down + power + home buttons and then pressing volume up when the message appears (I can't remember what this mode is called). I then flashed the device with the TWRP image.
After this I rebooted into the TWRP recovery mode (Volume up + home + power and then release power button when the samsung logo appears).
At this point, the device appeared on my windows machine so I could upload a new image to the internal memory.
I decided to copy on CM13 and GApps.
I then wiped the cache, system, data, and davik cache using TWRP, then I installed CM13 and GApps.
After a reboot the device came back up as a new install.
Hopefully that information may be useful to somebody.
Thanks for all your help