Stock LG build JDQ39B.V50010A US + BusyBox + Root + TWRP
for LG G Pad 8.3 V500 ONLY!
Android 4.2.2
Disclaimer:
I am not responsible for anything you do to your device but I will do my best to assist if something goes wrong!
Purpose:
My purpose for making this is that I wanted a easy way to go back and forth between 50020B and 50010A. I have tested this a few times and it works well. much easier than flashing the kdz. Also aosp roms dont play well with the 4.4.2 bootloader but they work great with 4.2.2. so if anyone decides to use this let us know how it goes
Features:
Official Stock 4.2.2 LG build JDQ39B.V50010A US + Stock 4.2.2 Kernel
NO Data Wipe (you get to keep: data/media Ex. photos, music and such)
flashes over existing Recovery and ABOOT (you get the right TWRP for this firmware)
SuperSU 1.94 + su binary Installed
BusyBox 1.22.1-Stericson Installed
Wipes Dalvik-Cache and Cache partition
Download
LG-V500_JDQ39B.V50010A_US_Stock-BB-Rooted.zip
Install:
Boot into TWRP recovery.
Wipe --> factory reset
Make a Full backup before proceeding. (optional)
Flash .zip file in TWRP recovery.
Go take a walk, make some coffee, pace around nervously. Keep Calm... this will take a while! Be patient!!
Reboot device.
now restore or flash your favorite AOSP rom
Credits:
@id10terror as this is based on his rom zips so please stop by one of his threads and thank him
@Jessooca for supplying the KDZ this is based off of http://forum.xda-developers.com/showpost.php?p=51468259&postcount=8
@autoprime - for 4.4.2 initial root method
@Chainfire - for SuperSU and install script
@jazzruby - BusyBox install script
one more for me
Thanks for putting this together! This will help a lot of people! :good:
Blessed be thy name! Flashed and now I don't have that crappy dimming issue now. Thank you so much! :thumbup::thumbup::thumbup::thumbup:
Thanks a lot!
it works very fine here!
Do we have to wipe everything and do a factory reset...? But the discription says we keep data? A bit confused....
Sent from my LG-V500 using XDA Free mobile app
magnum73 said:
Do we have to wipe everything and do a factory reset...? But the discription says we keep data? A bit confused....
Sent from my LG-V500 using XDA Free mobile app
Click to expand...
Click to collapse
If you are using twrp then in wipe tab go to advanced and choose data, system, cache and dalvik. That's what i did. Then flash the LG rom.
As you wiped data your apps will be restored from play store. It would be wise to make backups with titanium and saved them on your PC so you can restore some/all user app data. Don't restore any system data.
So having 4.2.2 bootloader back on my device I'm restoring nandroid of my last clean flash which was SlimKat 4.8. Then I'll flash 4.9 over it to have access to sd card until tomorrow when I'll clean flash incoming SlimKat 5.0
I'm a Slim man as you can see from my signature.
@Drgravy, this 4.2.2 flashable zip is a life saver for those who like me experimented with LG 4.4.2 but want to come back to 4.2.2 bootloader to get rid of the dimming. Thank you so much!
Since now I'm going to call you Profesor Gravy
magnum73 said:
Do we have to wipe everything and do a factory reset...? But the discription says we keep data? A bit confused....
Sent from my LG-V500 using XDA Free mobile app
Click to expand...
Click to collapse
all that means is you get to keep your data/media
Ex. photos,music and such
if you dont do a factory reset you will probably end up in a boot loop
Natakranta said:
If you are using twrp then in wipe tab go to advanced and choose data, system, cache and dalvik. That's what i did. Then flash the LG rom.
As you wiped data your apps will be restored from play store. It would be wise to make backups with titanium and saved them on your PC so you can restore some/all user app data. Don't restore any system data.
So having 4.2.2 bootloader back on my device I'm restoring nandroid of my last clean flash which was SlimKat 4.8. Then I'll flash 4.9 over it to have access to sd card until tomorrow when I'll clean flash incoming SlimKat 5.0
I'm a Slim man as you can see from my signature.
@Drgravy, this 4.2.2 flashable zip is a life saver for those who like me experimented with LG 4.4.2 but want to come back to 4.2.2 bootloader to get rid of the dimming. Thank you so much!
Since now I'm going to call you Profesor Gravy
Click to expand...
Click to collapse
HAHA be sure to thank @id10terror also this is based on his flashable roms
anyways glad it helped you out
The version of TWRP that comes with this ROM please?
yawako said:
The version of TWRP that comes with this ROM please?
Click to expand...
Click to collapse
2.7.0.0 IIRC
Sent from my Nexus 5 using Tapatalk
Natakranta said:
If you are using twrp then in wipe tab go to advanced and choose data, system, cache and dalvik. That's what i did. Then flash the LG rom.
As you wiped data your apps will be restored from play store. It would be wise to make backups with titanium and saved them on your PC so you can restore some/all user app data. Don't restore any system data.
So having 4.2.2 bootloader back on my device I'm restoring nandroid of my last clean flash which was SlimKat 4.8. Then I'll flash 4.9 over it to have access to sd card until tomorrow when I'll clean flash incoming SlimKat 5.0
I'm a Slim man as you can see from my signature.
Click to expand...
Click to collapse
I'm currently on Cm11 coming from 4.4.2 stock with brightness issue...
If I do a nandroid backup first of my current CM11, then I flash this one to go back to 4.2 and then restore my CM11 nandroid backup, will it work?
As far as I understood, the brightness issue is just bootloader related, so I don't know if my nandroid backup will erase the bootloader or not...
El Montezuma said:
I'm currently on Cm11 coming from 4.4.2 stock with brightness issue...
If I do a nandroid backup first of my current CM11, then I flash this one to go back to 4.2 and then restore my CM11 nandroid backup, will it work?
As far as I understood, the brightness issue is just bootloader related, so I don't know if my nandroid backup will erase the bootloader or not...
Click to expand...
Click to collapse
Nandroid never backs up bootloader. So it should work as good for your CM as it worked for my SlimKat.
Though there is now easier method. See this thread:
[HOWTO][V500] Flashable zips to change between 4.2.2 and 4.4.2 Base and flash 4.2.2 base.
Natakranta said:
Nandroid never backs up bootloader. So it should work as good for your CM as it worked for my SlimKat.
Though there is now easier method. See this thread:
[HOWTO][V500] Flashable zips to change between 4.2.2 and 4.4.2 Base and flash 4.2.2 base.
Click to expand...
Click to collapse
Great! Sounds good, will try it.
Many thanks
Ok, just to confirm that it works.
My tab was on 4.4.2 out of the box. I install CM11 directly without reading a little (my mistake), and I discover brightness dimmer issue... I play with Lux to try to find a solution during a week but no success...
So, the solution is to revert back to 4.2.2 stock (or to a rom based on 4.2.2 stock) to install the correct bootloader and then restore your 4.4.2 Nandroid backup.
Here the steps:
-Nandroid backup of your tab
-Titanium backup (in case of, double protection)
-Copy the zip into the internal memory of the tab
-Reboot in recovery mode
-Do a factory reset (wipe system, cache, data (except data/media))
-Flash the zip
-Wipe dalvik/cache (not mandatory but...)
-Reboot into recovery mode FROM recovery (do not reboot system at this point)
-Restore your Nandroid backup
-Reboot system
-Enjoy
Cheers
its flashing for about 3 hours now and is still going on.. was that meant with to be patient or is there something wrong? Having brightness issues on CM rom and have 4.4.2 base... that's why im trying to flash this.
Extracting busybox...
Done.
Extractiong images to flash...
Hi,
The OP is nice... but the problem when you want to downgrade from 4.4.2 to 4.2.2 is that in 4.4.2 it's difficult to boot into recovery.
And I'm looking for a way to root, unlock and install a recovery on my LG G Pad 8.3 with FW 1020D installed.
I am able to root it, that's not a problem.
But when I install a Recovery using Flashify and then reboot, I end up with a LG screen with two lines at the top saying that boot is void because of security check failure.
Isn't there a simple way to flash this beast ?
And why on earth are those stupid [email protected] at LG forcing us to use their stupid, inefficient and BUGGY software ?
Regards.
I've been flashing this to my GPad, and it keeps booting into TWRP, and ONLY TWRP. I sold my GPad on eBay, and I need to ship it out soon since the buyer paid, and I'm sure he'd want it in hand sooner rather than later. What am I doing wrong? I'm in process of trying this again, but I dunno if it'll matter since it failed twice already....
Suggestions?
EDIT: Also if there's a way to relock the bootloader and unroot that'd be great too. Thanks.
EDIT 2: I know that you can use the LG Mobile Support Tool but it needs a native (apparently won't work in a VM too well) Windows install, of which I do not have at the moment. Is there a way to do it on Mac OS X 10.9?
Shiggity said:
I've been flashing this to my GPad, and it keeps booting into TWRP, and ONLY TWRP. I sold my GPad on eBay, and I need to ship it out soon since the buyer paid, and I'm sure he'd want it in hand sooner rather than later. What am I doing wrong? I'm in process of trying this again, but I dunno if it'll matter since it failed twice already....
Suggestions?
EDIT: Also if there's a way to relock the bootloader and unroot that'd be great too. Thanks.
EDIT 2: I know that you can use the LG Mobile Support Tool but it needs a native (apparently won't work in a VM too well) Windows install, of which I do not have at the moment. Is there a way to do it on Mac OS X 10.9?
Click to expand...
Click to collapse
It worked for me few moths ago when I needed to come back to 4.2.2 base to get rid of dimming bug on AOSP KitKat ROMs.
Did you wipe in TWRP cache, data, system, dalvik? All 4 of them need to be wiped/formatted. Do it in TWRP Wipe: Advanced menu.
Natakranta said:
It worked for me few moths ago when I needed to come back to 4.2.2 base to get rid of dimming bug on AOSP KitKat ROMs.
Did you wipe in TWRP cache, data, system, dalvik? All 4 of them need to be wiped/formatted. Do it in TWRP Wipe: Advanced menu.
Click to expand...
Click to collapse
Okay I'll try that, but yeah. Not having any high hopes.
---------- Post added at 07:12 PM ---------- Previous post was at 06:55 PM ----------
@ Natakranta: nope. Still only boots to TWRP.
---------- Post added at 07:37 PM ---------- Previous post was at 07:12 PM ----------
It's imminent that I have this tablet working since the person paid, and I don't know if he's tech savvy enough to flash a different ROM if I was to put an AOSP/AOKP ROM onto it....
Someone please help.
Shiggity said:
Okay I'll try that, but yeah. Not having any high hopes.
---------- Post added at 07:12 PM ---------- Previous post was at 06:55 PM ----------
@ Natakranta: nope. Still only boots to TWRP.
---------- Post added at 07:37 PM ---------- Previous post was at 07:12 PM ----------
It's imminent that I have this tablet working since the person paid, and I don't know if he's tech savvy enough to flash a different ROM if I was to put an AOSP/AOKP ROM onto it....
Someone please help.
Click to expand...
Click to collapse
Maybe there's something wrong with your recovery.
Download TWRP 2710 zip and flash it in recovery. Them reboot recovery. Try flashing stock ROM again.
Maybe it will work.
Related
Hello, Here is my little story, i hope you can help me:
I was testing ROMs and having fun doing this, but i have an issue. At first i had this config:
Mobile : Samsung galaxy S2 - I9100
Base band : I9100XXMS2
Rom : Jelly bean 4.1.2 I9100XWLSW
Kernel : Siyah v6.0 beta5+
I did a nandroid backup using CWM 6.x and then stored the backup on external SD.
I then flashed cyanogenmod, latest nightly from 24/06/2013. Then i did wipe data/wipe cache.
Cyano was working, no issue. I decided to go backup to the stock rom (because i was only testing cyanogen, i dont want to stay with it). So i go back into CWM and do "restore" and then choose my jelly bean backup. Restore is sucessfull!
But after the boot, i'm now stucked in a bootloop at the moment of the samsung animation logo.
I tried another thing, did the wipe data/cache and THEN restore the jelly bean backup. I had the same result: BOOTLOOP.
Do you have any idea what's going on?
I have to mention that i did lots of backup/restore with CWM without issue.
Another thing to mention, i've reseted the flash counter with triangle away during the evening (i dont think there is a link, but i prefer mention it).
Also, i tried to restore the nandroid backup of cyanogenmod (i did one backup for this rom as well), and it's restoring well, so it's not bricked.
Thank you for your help!
Jellybean firmwares use a partition called preload.....I'd say with certainty that cwm didn’t backup this partition.....you have to enable the option before you make the nandroid.....
Without the preload backup, any firmware restore will bootloop.....
Sent from my rooted, de bloated, stock JB powered S2 via PhilZ kernel and XDA developers app
Hi keith have deleted that post. Lol far to slow. Have you seen that thread for firmware in cwm format. Iv read it and its good but I cant find it now if you cone across it could you pm me a link. Many thanks and have a good day.:thumbup:
I vaguely remember reading something about that too......
I'll have to have another look. ..
Sent from my rooted, de bloated, stock JB powered S2 via PhilZ kernel and XDA developers app
Dont put yourself out mate just if you come across it :thumbup:
I am also in this situation, I made a backup of stock ROM using Philz recovery. Then did a wipe to install new rom. Flashed new westcrip RR zip. Played with it (still on it now...) Then decided I want to go back. Wiped EVERYTHING (data,cache,delvik & fixed permissions.)
Retored backup successfully.
Boot loop.
So now I've had to reflash the RR zip so I can write this!
There is a way round this but it involves being at my computer and I'm out. ..
1.download the official stock firmware from sammobile again (unless u have it already) .
2.Put firmware and latest cwm/philz recovery zip on you phone.
3.Flash firmware with mobile odin (enable everroot).
4.Then goto stock recovery & flash cwm.
5.Then in that recovery find 'advanced restore', then you have the ability to only flash the DATA from your 'bootlooping' backup!
I will probably end up doing this but I'm not home so I'm still looking for a possible way to avoid this long method.
Holla back if anyone finds a quick way...
Sent from my GT-I9100 using XDA Premium HD app
keithross39 said:
Jellybean firmwares use a partition called preload.....I'd say with certainty that cwm didn’t backup this partition.....you have to enable the option before you make the nandroid.....
Without the preload backup, any firmware restore will bootloop.....
Sent from my rooted, de bloated, stock JB powered S2 via PhilZ kernel and XDA developers app
Click to expand...
Click to collapse
Hello keithross39 and ty for your help.
Are you sure there is an option related to this into CWM? I've never seen this. And i wonder why i have this problem now although i restored jelly bean with sucess in the past? It's weird.
match_stick said:
I am also in this situation, I made a backup of stock ROM using Philz recovery. Then did a wipe to install new rom. Flashed new westcrip RR zip. Played with it (still on it now...) Then decided I want to go back. Wiped EVERYTHING (data,cache,delvik & fixed permissions.)
Retored backup successfully.
Boot loop.
So now I've had to reflash the RR zip so I can write this!
There is a way round this but it involves being at my computer and I'm out. ..
1.download the official stock firmware from sammobile again (unless u have it already) .
2.Put firmware and latest cwm/philz recovery zip on you phone.
3.Flash firmware with mobile odin (enable everroot).
4.Then goto stock recovery & flash cwm.
5.Then in that recovery find 'advanced restore', then you have the ability to only flash the DATA from your 'bootlooping' backup!
I will probably end up doing this but I'm not home so I'm still looking for a possible way to avoid this long method.
Holla back if anyone finds a quick way...
Sent from my GT-I9100 using XDA Premium HD app
Click to expand...
Click to collapse
hello match_stick, ty for your help as well,
I still wonder how to troubleshoot this issue, it's common issue , i've google many things about this.
I dont understand why you have to do all those things, (which i dont want to do), to restore a simple backup, it's supposed to be reliable. I fear nothing's reliable in Android world...
Definitely the 'preload problem'.
I've found the setting by flashing Philz stock kernel (still bootloop). It's inside:
PhilZ Touch 5 CWM Base version: 6.0.3.2
Philz settings=>Custom backup & restore=>Misc Nandroid Settings=> and then tick "Include/preload"
I did the backup with Siyah CWM, and it didnt ask me about this at the backup moment, so i dont know if it's saving this partition automatically/transparently.
I will try now.
Try it out and let me know you break the boot loop!
Sent from my GT-I9100 using XDA Premium HD app
match_stick said:
Try it out and let me know you break the boot loop!
Sent from my GT-I9100 using XDA Premium HD app
Click to expand...
Click to collapse
Bad news, it didn't work. During the advanced restore i saw a message "the preload partition was not saved into this backup"....So i guess the nandroid i did didnt include it automatically! I wonder why. I will try to restore another Jelly bean backup i have on my HDD.
In the meantime i tried to restore an old ICS 4.0.4 nandroid backup and it's ok with this one.
The problematic nandroid backup was done with JB+Siyah 6 beta5+ and it's associated CWM recovery. Is there any special backup settings to tell it to backup the Preload partition? I've never enable/disable such a thing...
EDIT: in the meantime i've read this:http://forum.xda-developers.com/showthread.php?t=2099292&nocache=1
Conclusion, CWM from Siyah is broken for jelly bean. Philz CWM is ok for jelly bean.
As i understand Cyanogen overwrite my /preload partition that was not backed up by CWM from Siyah. This is really bad. Now i'm kinda ****ed.
I have to find a working CWM nandroid done with Philz CWM, then i can restore it properly with Philz CWM. Then i can backup the /preload partition using the cwm script from [email protected] Then i can restore it and remove the bootloop maybe?
God knows....
Sent from my GT-I9100 using XDA Premium HD app
---------- Post added at 04:06 PM ---------- Previous post was at 03:32 PM ----------
I used Philz and I'm still boot loop...
Sent from my GT-I9100 using XDA Premium HD app
In philz you have to set the option to save preload. Why because more phone models dont use preload. Philz isnt just working on i9100. Cwm from dori and siyah dont restore or bk up preload even if you save on philz and restore on cwm 6. Whatever I Was on dori. But you can save with hawkerpauls bkup preload and restore scripts. Reason why you other jb nandroids are restore is because there not using preload.
---------- Post added at 04:24 PM ---------- Previous post was at 04:18 PM ----------
So if no preload was made when nandroid was made on either with siyah dori or philz you will get boot loop. If you did bkup preload and have problems format data system cache and preload. Then wipe dalv cache in advanced restore nand wipe cache and dalv cache and reboot. Still problem wipe/factory reset but nit on or going to any were near ics 4.0.4 :thumbup:
Keith I found it that thread :thumbup:
andrewwright said:
In philz you have to set the option to save preload. Why because more phone models dont use preload. Philz isnt just working on i9100. Cwm from dori and siyah dont restore or bk up preload even if you save on philz and restore on cwm 6. Whatever I Was on dori. But you can save with hawkerpauls bkup preload and restore scripts. Reason why you other jb nandroids are restore is because there not using preload.
---------- Post added at 04:24 PM ---------- Previous post was at 04:18 PM ----------
So if no preload was made when nandroid was made on either with siyah dori or philz you will get boot loop. If you did bkup preload and have problems format data system cache and preload. Then wipe dalv cache in advanced restore nand wipe cache and dalv cache and reboot. Still problem wipe/factory reset but nit on or going to any were near ics 4.0.4 :thumbup:
Keith I found it that thread :thumbup:
Click to expand...
Click to collapse
Questions:
1)Where can i get the package for CWM 6.0.3.2 that is included into Philz, but i want it as standalone! I saw it exists only for galaxy s4, will the package from S4 work on S2?
2)I've tried tons of things to restore the CWM nandroid (the one from backed up with Siyah CWM WITHOUT /preload), with no luck. Finally i used the solution gave by match_stick member (ty dude):
I did the wipes, i flash stock ROM, and went into CWM and advanced restore, restore DATA partition.
What will happen if i just restore DATA without restoring /System? What is exactly into /system?
int0x13 said:
Questions:
1)Where can i get the package for CWM 6.0.3.2 that is included into Philz, but i want it as standalone! I saw it exists only for galaxy s4, will the package from S4 work on S2?
2)I've tried tons of things to restore the CWM nandroid (the one from backed up with Siyah CWM WITHOUT /preload), with no luck. Finally i used the solution gave by match_stick member (ty dude):
I did the wipes, i flash stock ROM, and went into CWM and advanced restore, restore DATA partition.
What will happen if i just restore DATA without restoring /System? What is exactly into /system?
Click to expand...
Click to collapse
I am not sure about the standalone version for that particular version but standalone recovery is available just keep searching harder.
If you just restore /data you're restoring only the apps you installed, /system contains all the core files which makes the OS function. /preload acts as an extension for /system partition, as /system for the S2 is too small to hold all the necessary system files, therefore absence of /preload in a nandroid can cause a bootloop.
Try using the apps "Nandroid Manager" and "Online Nandroid Backup" both by the same developer, these app's will make the life of noobs as well as flashaholics easier, and yeah the backup script of Online Nandroid Backup takes backup of all the usual default cwm partitions and also includes /preload and /efs also.
Sent from my GT-I9100 using xda app-developers app
king_below_my_lord said:
I am not sure about the standalone version for that particular version but standalone recovery is available just keep searching harder.
If you just restore /data you're restoring only the apps you installed, /system contains all the core files which makes the OS function. /preload acts as an extension for /system partition, as /system for the S2 is too small to hold all the necessary system files, therefore absence of /preload in a nandroid can cause a bootloop.
Try using the apps "Nandroid Manager" and "Online Nandroid Backup" both by the same developer, these app's will make the life of noobs as well as flashaholics easier, and yeah the backup script of Online Nandroid Backup takes backup of all the usual default cwm partitions and also includes /preload and /efs also.
Sent from my GT-I9100 using xda app-developers app
Click to expand...
Click to collapse
Ok. /system is read only partition. So if i install the stock ROM /system should be the same than the /system i had from my nandroid backup, is it right? So if i install the stock and rom and do advanced restore and select the /data partition, it should be the same than restoring the entire nandroid backup. Right or wrong? That's what i did and it's working. Install the stock rom didnt restore the /preload partition, but maybe it's creating one with default parameter. Anyway, not restoring /preload doesn't seem to be an issue with /data restore.
About CWM 6.0.3.2 standalone package,i found this:
http://forum.xda-developers.com/showthread.php?t=2201860
I ask about that CWM version, because i know only the latest version customized by Philz supports the /preload backup (as non default option). As Philz say it's the only recovery that is supporting full JB migration/restore.
Thanks .. Now will always remember to keep Include Preload checked before Nandroid
match_stick said:
I am also in this situation, I made a backup of stock ROM using Philz recovery. Then did a wipe to install new rom. Flashed new westcrip RR zip. Played with it (still on it now...) Then decided I want to go back. Wiped EVERYTHING (data,cache,delvik & fixed permissions.)
Retored backup successfully.
Boot loop.
So now I've had to reflash the RR zip so I can write this!
There is a way round this but it involves being at my computer and I'm out. ..
1.download the official stock firmware from sammobile again (unless u have it already) .
2.Put firmware and latest cwm/philz recovery zip on you phone.
3.Flash firmware with mobile odin (enable everroot).
4.Then goto stock recovery & flash cwm.
5.Then in that recovery find 'advanced restore', then you have the ability to only flash the DATA from your 'bootlooping' backup!
I will probably end up doing this but I'm not home so I'm still looking for a possible way to avoid this long method.
Holla back if anyone finds a quick way...
Sent from my GT-I9100 using XDA Premium HD app
Click to expand...
Click to collapse
Thanks this Helped!!
hi i have the cyanogenmod 10 build from july 1st 2013.
its installed with the clockwork mod
even put the patch in during clockwork mod
and the google apps during clockwork mod.
the biggest issue im having is that when i click the camera it says no external storage avaiable and to insert an sd card before using the camera.
i cant transfer any pictures to my phone or files.
if i plug the phone into my computer it says turn usb storage on and i try that but cant get into the phones files to fix what i need.
i also can do a mtp mode but it only shows whats on the micro sd card that is it.
i really want to use my phone but this issue is tough to fix.?
what can i do?
What version of cm are you running your title says 10.1 but your post says 10 which one is it? Did you read the op on the Rom. Mainly the what works and what doesn't? Not sure if that's the cm but extsd is broke on one of them I think.
I'm running cm10.1 20130701, unofficial. And my camera works. If this is the cm your on try a full wipe and reflash
I.e. wipe data
Wipe cache
Wipe dalvik
Then reflash
hey
ghost582 said:
Did you read the op on the Rom. Mainly the what works and what doesn't? Not sure if that's the cm but extsd is broke on one of them I think.
I'm running cm10.1 20130701, unofficial. And my camera works. If this is the cm your on try a full wipe and reflash
I.e. wipe data
Wipe cache
Wipe dalvik
Then reflash
Click to expand...
Click to collapse
thanks for your helpful reply but u can provide me the link where u got yours?
what do u mean reflash? i do a boot image, whipe all the data everything, and install from zip.
should i actually go do a boot image again?
http://goo.im/devs/Sportsstar89/Ruby/CM-10.1
Here's the link I'm successfully running the 701 zip. However I'm running 4ext recovery not cwm. I think it's recommended maybe required to use 4ext recovery. Google it, if so Google how to flash 4 ext. I can't give y instructions don't know that well. And I just meant wipe then install from zip.
ghost582 said:
http://goo.im/devs/Sportsstar89/Ruby/CM-10.1
Here's the link I'm successfully running the 701 zip. However I think it's recommended maybe required to use 4ext recovery. Google it, if so Google how to flash 4 ext. I can't give y instructions don't know that well. And I just meant wipe the install from zip.
Click to expand...
Click to collapse
ok so heres what i will do
get that zip again
and have the patch
and the google apps
unzip the 7.01 build and copy that boot and run the fastboot devices
go in with clockwork mod
clean wipe data
clea wipe cache
battery status
delvik cache
format data
format cache
format sd ext
format sd card
all that
then install 7.01 build from zip
install patch from zip
install camera from 4.3 libs zip
and then what? u said something about reflashing?
K your out of my knowledge. I've never had to unzip and flash anything also I'm not sure what patch your talking about. So rather than doing what I said post here http://forum.xda-developers.com/showthread.php?t=2217075
I don't want you to mess your phone up from my advice so yeah post toot question there. More advanced users will be able to help you. Mine I just flashed in 4ext and it worked no unzipping no patching,
---------- Post added at 11:12 PM ---------- Previous post was at 11:02 PM ----------
Did you flash the camera lib on your current Rom? If so why? If it didn't directly say that in the instructions for that Rom that may have broke your camera. Also why are you using fast boot, then cwm. What are you using fastboot for?
For the Rom I linked I don't believe you need a patch I haven't read anything about it I didn't need one. If you want to switch to 4ext go to 4ext.net and download recovery updater, it will flag 4ext for you then do exactly this
Wipe data factory reset
Wipe cache /dalvik
Install from zip
Flash the Rom
Install from zip
Flash the gapps package. Thus Rom is JB make sure you have the JB gapps. If not Google it
ghost582 said:
K your out of my knowledge. I've never had to unzip and flash anything also I'm not sure what patch your talking about. So rather than doing what I said post here http://forum.xda-developers.com/showthread.php?t=2217075
I don't want you to mess your phone up from my advice so yeah post toot question there. More advanced users will be able to help you. Mine I just flashed in 4ext and it worked no unzipping no patching,
---------- Post added at 11:12 PM ---------- Previous post was at 11:02 PM ----------
Did you flash the camera lib on your current Rom? If so why? If it didn't directly say that in the instructions for that Rom that may have broke your camera. Also why are you using fast boot, then cwm. What are you using fastboot for?
For the Rom I linked I don't believe you need a patch I haven't read anything about it I didn't need one. If you want to switch to 4ext go to 4ext.net and download recovery updater, it will flag 4ext for you then do exactly this
Wipe data factory reset
Wipe cache /dalvik
Install from zip
Flash the Rom
Install from zip
Flash the gapps package. Thus Rom is JB make sure you have the JB gapps. If not Google it
Click to expand...
Click to collapse
flash the rom means what again? i thought flash the rom means to install it from zip.
Yeah that's what it means. I was referring to the options you select in recovery. Make sense? In that post though I was sharp talking about flashing a recovery if you wanted that's different I put some basic instructions in there
Here's one guide on flashing 4ext recovery
http://androidforums.com/desire-hd-all-things-root/631481-4ext-recovery-how.html
ghost582 said:
Yeah that's what it means. In that post though I was sharp talking about flashing a recovery if you wanted that's different I put some basic instructions in there
Here's one guide on flashing 4ext recovery
http://androidforums.com/desire-hd-all-things-root/631481-4ext-recovery-how.html
Click to expand...
Click to collapse
where did u get your google apps?
http://goo.im/gapps (wrong link sorry)
Can't post within five minutes
Sorry
Download the one for cm10.1 bookmark the page in case you need a different one later on in life.
Honestly a simple Google search for gapps got that page in two seconds. No one will help you in here if you ask for everything. You've ask me for a link to everything I've said. So I have to spend my time to find your link. I don't mind helping but when all you have to do it search you need to do it yourself
ctdan713 said:
where did u get your google apps?
Click to expand...
Click to collapse
i am in 4ext recovery touch and following your instrctions but it says it cant mount sd card?
If possible try another sd card.
Are you referring to the internal or external?
ghost582 said:
If possible try another sd card.
Are you referring to the internal or external?
Click to expand...
Click to collapse
i did what u said and got stuck with 4ext starting over and over and over again
so i switched back to clockwork mod and will see what happens.
i hope your right because u have a 7.01 build and no issues and i cant seem to get past this.
You didn't answer my question what sd card won't mount? And before you stay just doing things research your problem if 4ext went find sd you should have Googled that issue before you went back to cwm, jumping without knowing is what's going to Mess things up. So stop changing things and do some research.
ctdan713 said:
i did what u said and got stuck with 4ext starting over and over and over again
so i switched back to clockwork mod and will see what happens.
i hope your right because u have a 7.01 build and no issues and i cant seem to get past this.
Click to expand...
Click to collapse
seriously! thank you for all your help! IT WORKS!
ctdan713 said:
i did what u said and got stuck with 4ext starting over and over and over again
so i switched back to clockwork mod and will see what happens.
i hope your right because u have a 7.01 build and no issues and i cant seem to get past this.
Click to expand...
Click to collapse
What do you mean starting over and over. In the previous post you said it was working but couldn't mount sd. What happened to make it go from working to boot looping. Exactly what did you do? How far does it go before restarting? Is the recovery that's bootlooping or the Rom? I need way more info than your posting
Sent from my Amaze 4G
---------- Post added 7th July 2013 at 12:00 AM ---------- Previous post was 6th July 2013 at 11:55 PM ----------
Hit the thanks button
Sent from my Amaze 4G
---------- Post added at 12:37 AM ---------- Previous post was at 12:00 AM ----------
What recovery finally worked for you? And if everything is running well make a backup before you start tweaking it that way if something goes wrong you can just restore your backup instead of having to stay over from scratch
Personally
I make a backup after a clean install then after I restore my apps then after mods then final. And I delete the post one when I have a working newer one. That way my sd isn't full of backups
Sent from my Amaze 4G
tetakpatak said:
Please quote my post and copy&paste whole text into some help thread for your phone, it is better idea as we are now getting off topic here. I'll try to help you there.
Format /system is done in recovery mode under "mount and storage" then after that you can restore your nandroid if it is done with the same recovery you use now. If you're on PhilZ 6, it usually can restore also CWM 6 backups.
Click to expand...
Click to collapse
What does format system do? And please help me load sentinel rom. That's the one I was gonna do.
Okay now for the question... I was running stock 4.1.2 with siyah kernel 6.0 b5. Then I decided to install philz kernel, but ended up in bootloop. Then I tried flashing dorimanx but still in bootloop. All the while I wiped everything before flashing.
Now im stuck as I can boot into recovery via any kernel but ultimately phone is stuck.
What to do?
And can anyone give me steps to install sentinel rom from this stage?
Sent from my Nexus 4 using xda app-developers app
AndroidReborn said:
What does format system do? And please help me load sentinel rom. That's the one I was gonna do.
Okay now for the question... I was running stock 4.1.2 with siyah kernel 6.0 b5. Then I decided to install philz kernel, but ended up in bootloop. Then I tried flashing dorimanx but still in bootloop. All the while I wiped everything before flashing.
Now im stuck as I can boot into recovery via any kernel but ultimately phone is stuck.
What to do?
And can anyone give me steps to install sentinel rom from this stage?
Click to expand...
Click to collapse
Mate, sorry for waiting, I was out of home. We will get your ROM back as soon as the phone boots again.
Don't worry, it doesn't sound serious so far. We have recovery and download mode (so topic name "nothing works" isn't really correct)
Formatting /system wipes all data from the system partition (so your system will be gone then) and it is important to do before installing new ROMs (essencially important for KitKat). It can't do any harm. As you have tried to install other kernels and didn't work we should check first what did you try to flash so far and it didn't boot? Is that what you wrote all what you have tried?
Now let me know please which recovery do you have now and is it the same version like when you have created your nandroid backup? If the recovery is the same, I would indeed try to restore nandroid backup right after wiping /system. Before you wipe the system just let me know: can you use ADB? If yes, check do you have ADB connection in the recovery mode?
tetakpatak said:
Mate, sorry for waiting, I was out of home. We will get your ROM back as soon as the phone boots again.
Don't worry, it doesn't sound serious so far. We have recovery and download mode (so topic name "nothing works" isn't really correct)
Formatting /system wipes all data from the system partition (so your system will be gone then) and it is important to do before installing new ROMs (essencially important for KitKat). It can't do any harm. As you have tried to install other kernels and didn't work we should check first what did you try to flash so far and it didn't boot? Is that what you wrote all what you have tried?
Now let me know please which recovery do you have now and is it the same version like when you have created your nandroid backup? If the recovery is the same, I would indeed try to restore nandroid backup right after wiping /system. Before you wipe the system just let me know: can you use ADB? If yes, check do you have ADB connection in the recovery mode?
Click to expand...
Click to collapse
Will it wipe the internal memory? Or the rom in the phone?
I have cwm based recovery v. 6.0.1.2. Yes I used it to make the backup.
Checking for adb.. How do I do it? .
Sent from my Nexus 4 using xda app-developers app
AndroidReborn said:
Will it wipe the internal memory? Or the rom in the phone?
I have cwm based recovery v. 6.0.1.2. Yes I used it to make the backup.
Checking for adb.. How do I do it?
Click to expand...
Click to collapse
Hi! Internal memory usually shouldn't get wiped by formatting /system, as it is "storage", not part of the system. I would give a try, wipe all: data/factory reset, cache, dalvik cache (advanced) and format /system (mounts and storage). Then back to the main menu --> backup & restore --> restore from (internal or external memory where your nandroid is saved) and choose your backup. It should reboot normally then.
tetakpatak said:
Hi! Internal memory usually shouldn't get wiped by formatting /system, as it is "storage", not part of the system. I would give a try, wipe all: data/factory reset, cache, dalvik cache (advanced) and format /system (mounts and storage). Then back to the main menu --> backup & restore --> restore from (internal or external memory where your nandroid is saved) and choose your backup. It should reboot normally then.
Click to expand...
Click to collapse
Thanks for helping, but I ended up downloading the stock rom and flashing it. Everything was normal. Then I installed cm10.2 so everything's great now. Thanks!
Sent from my Nexus 4 using xda app-developers app
Cool, @AndroidReborn! Now you can install your old ROM again and restore nandroid. Keep that stock FW saved on your PC, so if your phone gets ever again soft-bricked, no problem to revive it again.
I am wondering how nobody here responsed your help prompt, we have in i9000 help threads always handfull people of experience and skills who are ready to help in need. And there are double amount of the SGS2 units sold around the world.... strange.
tetakpatak said:
Cool, @AndroidReborn! Now you can install your old ROM again and restore nandroid. Keep that stock FW saved on your PC, so if your phone gets ever again soft-bricked, no problem to revive it again.
I am wondering how nobody here responsed your help prompt, we have in i9000 help threads always handfull people of experience and skills who are ready to help in need. And there are double amount of the SGS2 units sold around the world.... strange.
Click to expand...
Click to collapse
No idea. The people seem pretty 'busy'. Thanks for helping. Just one teeny tiny last question.. How do I install cm11 or any kitkat rom over this? Cwm is 6.0.4.5 so it's compatible...
Sent from my Nexus 4 using xda app-developers app
If you want to flash kitkat, the first thing you need to do is flash a kitkat compatible CWM (v6.0.4.7). If you try to flash KK with an 'older' CWM, you'll get 'installation aborted....error status 7' or something similar........
I'm currently running @infected_s KK build, and in the OP, you will find download links for the correct CWM, ROM and GApps files.......
Sent from my Infected KitKat bar.....
keithross39 said:
If you want to flash kitkat, the first thing you need to do is flash a kitkat compatible CWM (v6.0.4.7). If you try to flash KK with an 'older' CWM, you'll get 'installation aborted....error status 7' or something similar........
I'm currently running @infected_s KK build, and in the OP, you will find download links for the correct CWM, ROM and GApps files.......
Sent from my Infected KitKat bar.....
Click to expand...
Click to collapse
6.0.4.5 is compatible? I think so ......
Sent from my Nexus 4 using xda app-developers app
I've always read....not.....
In any case, probably best not to risk it......
6.0.4.7 is DEFINITELY KK compatible.... and it'd take a couple of seconds to flash.........
Sent from my Infected KitKat bar.....
AndroidReborn said:
No idea. The people seem pretty 'busy'. Thanks for helping. Just one teeny tiny last question.. How do I install cm11 or any kitkat rom over this? Cwm is 6.0.4.5 so it's compatible...
Click to expand...
Click to collapse
Yes, mate, CWM 6.0.4.5 is capable of flashing KitKat.
It is usually always the same:
download your ROM zip and compatible Gapps
check in the phone (or PC) if the zips are corrupted through download (if they open after clicking them, they are fine)
move the zips to the folder you will flash it from (if you use PC to flash zips with ADB sideload, put them in the sdk/platform-tools folder)
make nandroid backup of your presently used ROM
wipe data/factory reset
wipe cache
wipe dalvik cache (advanced)
format /system (under mount and storage)
flash ROM.zip
flash Gapps
reboot
It is in general always good to read in the development thread of the ROM you attend to flash in the opening post which Gapps are recommended, or if there is some unusual order of flashing (sometimes, developers recommend reboot system after flashing ROM, and after that going to recovery and flash Gapps zip.
Some KitKat ROMs struggle with root access by using Superuser, so SuperSU should be flashed. If SuperSU app from Play Store gives errors by updating binary, you should uninstall SuperSU app then, find in the Chainfire's thread the compatible UPDATE-SuperSu.zip (version for your phone), flash its zip in the recovery, install SuperSU app, update binary (either "normal" or "through CWM/TWRP")
Hi,
When i woke up this morning my phone was attempting to boot, but was stuck on my boot animation. So i pulled out the battery and rebooted, since then it has been turning on for a couple mins than rebooting the phone its self is slightly warmer than usual, but it has been hotter before. I have attempted to back up my data using cwm, but the reboot still happens, im unsure if its on the same file that causes the reboot. Im trying to back it up to completely wipe it and see if that makes a difference.
I would be grateful for any help in the matter.
ads2996 said:
Hi,
When i woke up this morning my phone was attempting to boot, but was stuck on my boot animation. So i pulled out the battery and rebooted, since then it has been turning on for a couple mins than rebooting the phone its self is slightly warmer than usual, but it has been hotter before. I have attempted to back up my data using cwm, but the reboot still happens, im unsure if its on the same file that causes the reboot. Im trying to back it up to completely wipe it and see if that makes a difference.
I would be grateful for any help in the matter.
Click to expand...
Click to collapse
Hi,
i would boot into CWM or TWRP and then i would do a wipe cache / dalvik, and flash your "rom.zip" from internal or external sd card. If that does not work then do a factory reset and flash "rom.zip". If the problem still exists what i do not hope for you, then you have to wipe all your data without doing a nandroid backup and then flashing again. Do you have a stock rom installed or what rom do you have and what kind of kernel?
But try to flash your rom and kernel again . Hope it will help your "Diva" ?!
Sounds to me ur power button is stuck.
Sent from my GT-I9300 using xda app-developers app
DrEVILone81 said:
Hi,
i would boot into CWM or TWRP and then i would do a wipe cache / dalvik, and flash your "rom.zip" from internal or external sd card. If that does not work then do a factory reset and flash "rom.zip". If the problem still exists what i do not hope for you, then you have to wipe all your data without doing a nandroid backup and then flashing again. Do you have a stock rom installed or what rom do you have and what kind of kernel?
But try to flash your rom and kernel again . Hope it will help your "Diva" ?!
Click to expand...
Click to collapse
im running the stock rom with siyah kernal and jkay framework.Well i wiped the /data and it seemed to work then i did the foolish thinng of trying to flash a /system backup i had. So m back to where i started. I'm downloading the latest stock rom for my network and am gonna try and flash via odin. Hopefully that fixes it.
When falshing with odin does it wipe /sdcard?
JellyYogurt said:
Sounds to me ur power button is stuck.
Sent from my GT-I9300 using xda app-developers app
Click to expand...
Click to collapse
When ever i do get booted into my phone i am still able to use my power button as normal. And the power options box odesnt appear before it reboots either.
JellyYogurt said:
Sounds to me ur power button is stuck.
Sent from my GT-I9300 using xda app-developers app
Click to expand...
Click to collapse
This could be the easiest solution.....:laugh::good:
But i love flashing and so it was my proposal:angel:
DrEVILone81 said:
This could be the easiest solution.....:laugh::good:
But i love flashing and so it was my proposal:angel:
Click to expand...
Click to collapse
I take it the only way to fix a stuck power button is by taking it apart?
ads2996 said:
im running the stock rom with siyah kernal and jkay framework.Well i wiped the /data and it seemed to work then i did the foolish thinng of trying to flash a /system backup i had. So m back to where i started. I'm downloading the latest stock rom for my network and am gonna try and flash via odin. Hopefully that fixes it.
When falshing with odin does it wipe /sdcard?
Click to expand...
Click to collapse
No i meant you should flash your rom.zip, but when you have istalled a stock rom then you dont have a zip file of it on your sd-card, which you can flash. But a normal odin flash of your stock will solve your problem, and then you can do a custom nandroid backup in CWM (EFS, DATA partition etc). I hope odin will do a complete delete of your /system, /data/media, /data partition. But try it
DrEVILone81 said:
No i meant you should flash your rom.zip, but when you have istalled a stock rom then you dont have a zip file of it on your sd-card, which you can flash. But a normal odin flash of your stock will solve your problem, and then you can do a custom nandroid backup in CWM (EFS, DATA partition etc). I hope odin will do a complete delete of your /system, /data/media, /data partition. But try it
Click to expand...
Click to collapse
I jhave managed to restore /system and /boot so can now enter my phone after being stock reset. When i try to format /data through cwm it reboots and when i open appalications manger it also crashes it is filled with apps that arent installed on the phone
Wait a moment man.....sounds not pretty good...but we can manage it
---------- Post added at 07:00 PM ---------- Previous post was at 06:49 PM ----------
We should do a full wipe of your phone.....:laugh:
1. Load a rom xyz.zip file on your external sd card (i would recommend not a stock rom)
2. Reboot into CWM (what version do you have ??? etc. It is very important for your new rom what you want to install instep 6)
3. Do a full wipe (wipe cache / wipe dalvik cache)
4. Factory Reset
5. Delete /data and /data/media i mean everything (so your internal sd card has to be empty and empty)
6. Install zip file from sdcard1 (external sd card)
so a new rom will be flashed dont forget it, its your phone
7. REBOOT
8. Now you have a newly fresh installed ROM on your S3 :good::laugh:
All your data is lost.....but your phone works
---------- Post added at 07:23 PM ---------- Previous post was at 07:00 PM ----------
When you flashed with odin?! Havent you?! Then these are the apps of the bloated stock-firmware......
DrEVILone81 said:
Wait a moment man.....sounds not pretty good...but we can manage it
---------- Post added at 07:00 PM ---------- Previous post was at 06:49 PM ----------
We should do a full wipe of your phone.....:laugh:
1. Load a rom xyz.zip file on your external sd card (i would recommend not a stock rom)
2. Reboot into CWM (what version do you have ??? etc. It is very important for your new rom what you want to install instep 6)
3. Do a full wipe (wipe cache / wipe dalvik cache)
4. Factory Reset
5. Delete /data and /data/media i mean everything (so your internal sd card has to be empty and empty)
6. Install zip file from sdcard1 (external sd card)
so a new rom will be flashed dont forget it, its your phone
7. REBOOT
8. Now you have a newly fresh installed ROM on your S3 :good::laugh:
All your data is lost.....but your phone works
---------- Post added at 07:23 PM ---------- Previous post was at 07:00 PM ----------
When you flashed with odin?! Havent you?! Then these are the apps of the bloated stock-firmware......
Click to expand...
Click to collapse
I'm just back from hockey and have managed to restore the phone to what i had before. So im on 4.1.2 and the random apps have disappeared, and the internal sd card has been wiped so lost a few fb photos nothing serious, well that i can remember.
I am either goign to go with the latest firmware from my carrier which is 4.3 or a newer rom, i would really like to try dual booting android and ubuntu. Any suggestions?
FLASH and TRY
ads2996 said:
I'm just back from hockey and have managed to restore the phone to what i had before. So im on 4.1.2 and the random apps have disappeared, and the internal sd card has been wiped so lost a few fb photos nothing serious, well that i can remember.
I am either goign to go with the latest firmware from my carrier which is 4.3 or a newer rom, i would really like to try dual booting android and ubuntu. Any suggestions?
Click to expand...
Click to collapse
I am happy about that your S3 is working well, its one of the best devices and xda support for our device is nice.....
I use fusion kitkat rom with the stable boeffla kernel in it......YOU must try it. I appreciate it:good:
There are two dualboot kernel for our devices: googymax2 (development of siyah kernel and devil2.....i tried both
naturally with dualboot installed. but im also waiting for a stable version of ubuntu touch and then ........:crying::laugh: there is
also a thread here or you must "google" man you will find sth. But in my opinion try sth different from the stock-rom......OUR XDA-DEVELOPERS
are GREAT......CM11, SLIM or sth like that.......try
---------- Post added at 10:08 PM ---------- Previous post was at 09:51 PM ----------
DrEVILone81 said:
I am happy about that your S3 is working well, its one of the best devices and xda support for our device is nice.....
I use fusion kitkat rom with the stable boeffla kernel in it......YOU must try it. I appreciate it:good:
There are two dualboot kernel for our devices: googymax2 (development of siyah kernel and devil2.....i tried both
naturally with dualboot installed. but im also waiting for a stable version of ubuntu touch and then ........:crying::laugh: there is
also a thread here or you must "google" man you will find sth. But in my opinion try sth different from the stock-rom......OUR XDA-DEVELOPERS
are GREAT......CM11, SLIM or sth like that.......try
Click to expand...
Click to collapse
Ithink the development of ubuntu touch is discontinued. Its a thread also.....
But running ubuntu on your device is possible as an arm version...... linux deploy apk.....and then you can have a look on whats
possible. But its not a real dualboot..... It runs from your external / internal sd card...
DrEVILone81 said:
I am happy about that your S3 is working well, its one of the best devices and xda support for our device is nice.....
I use fusion kitkat rom with the stable boeffla kernel in it......YOU must try it. I appreciate it:good:
There are two dualboot kernel for our devices: googymax2 (development of siyah kernel and devil2.....i tried both
naturally with dualboot installed. but im also waiting for a stable version of ubuntu touch and then ........:crying::laugh: there is
also a thread here or you must "google" man you will find sth. But in my opinion try sth different from the stock-rom......OUR XDA-DEVELOPERS
are GREAT......CM11, SLIM or sth like that.......try
---------- Post added at 10:08 PM ---------- Previous post was at 09:51 PM ----------
Ithink the development of ubuntu touch is discontinued. Its a thread also.....
But running ubuntu on your device is possible as an arm version...... linux deploy apk.....and then you can have a look on whats
possible. But its not a real dualboot..... It runs from your external / internal sd card...
Click to expand...
Click to collapse
Thank you very much for all your help in sorting out my phone it is greatly appreicated
ads2996 said:
Thank you very much for all your help in sorting out my phone it is greatly appreicated
Click to expand...
Click to collapse
I dont want to sort out "our" phone.....i ve the same one...... I am not very convinced about the stock roms....but the SIII is great
and is developed in a positive way....in a kind of future development to improve the ram and so on through the kernel.....
ads2996 said:
When ever i do get booted into my phone i am still able to use my power button as normal. And the power options box odesnt appear before it reboots either.
Click to expand...
Click to collapse
It doesnt if the power button is stuck continuously as when u press and hold the power button, it hard reboots so no menu is given. Go google search 'gs3 power button stuck'. Trust me. All of their cases are similar to urs.
Sent from my GT-I9300 using xda app-developers app
Self-explanatory really.
I updated my phone a few weeks ago to Omnirom 4.4.4, one of the nightly builds and everything was going well.
Today I installed a couple of apps, and tonight the screen started flickering and the phone reset, however when it started again, it went into a bootloop.
How do I get it working again without losing the files that are on the internal memory? (I don't know which resets in CWM delete personal data)
Thanks
septimoose said:
Self-explanatory really.
I updated my phone a few weeks ago to Omnirom 4.4.4, one of the nightly builds and everything was going well.
Today I installed a couple of apps, and tonight the screen started flickering and the phone reset, however when it started again, it went into a bootloop.
How do I get it working again without losing the files that are on the internal memory? (I don't know which resets in CWM delete personal data)
Thanks
Click to expand...
Click to collapse
Flash latest (6.0.4.7) CWM or latest TWRP (2.7.1.0 if Im not wrong) and reflash the rom.
Wiping data, and formatting partitions doesnt get you wiped internal memory files; but apps and things installed.
NaminatoR1254jaime.sier said:
Flash latest (6.0.4.7) CWM or latest TWRP (2.7.1.0 if Im not wrong) and reflash the rom.
Wiping data, and formatting partitions doesnt get you wiped internal memory files; but apps and things installed.
Click to expand...
Click to collapse
I did this, and I'm still stuck in a bootloop, it gets as far as the "Omni" animation, and then reboots
Any advice?
septimoose said:
I did this, and I'm still stuck in a bootloop, it gets as far as the "Omni" animation, and then reboots
Any advice?
Click to expand...
Click to collapse
Flash stock ROM via Odin
verny94 said:
Flash stock ROM via Odin
Click to expand...
Click to collapse
I'm sorry for my ignorance, but would you happen to know of a guide for flashing the stock ROM?
Would it fix by flashing a different ROM, such as Cyanogenmod which I have in the download folder on the phone?
If like you said you don't want to lose data don't flash stock rom this will wipe your data fist thing you need to do is install PhilZ recovery then look here >> http://forum.xda-developers.com/galaxy-s3/orig-development/i93xx-philz-touch-t2002953 << then look at the special features section here >> http://forum.xda-developers.com/showthread.php?p=39433728#post39433728 << look for the aroma file manager and how to use.
You will then be able to boot into recovery browse your internal files with aroma and move and copy/backup what you need,once you have done all that you will then be able to return to stock with odin.
Edit
Guide for flashing stock rom here >> http://forum.xda-developers.com/galaxy-s3/general/samsung-galaxy-s3-sticky-roll-thread-t2344125 <<
---------- Post added at 11:21 AM ---------- Previous post was at 11:10 AM ----------
septimoose said:
I'm sorry for my ignorance, but would you happen to know of a guide for flashing the stock ROM?
Would it fix by flashing a different ROM, such as Cyanogenmod which I have in the download folder on the phone?
Click to expand...
Click to collapse
If you don't want to lose your data then no because you need to wipe your data....Did you reboot into recovery and wipe cache advanced delvik cache? Also read my suggestions above