A500 boot loop - Acer Iconia A500

Hi All
Wondering if i could get any help from you guys
Ok so i flashed my a500 a year or so ago with a new boot loader the twrp 2.1.3 and loaded a then upto date rom, so today thought i'd update it to ROM] [A500] Android 4.3 [CM10.2 Unofficial] Build 5, Put it on to my sd card booted into recovery wiped cache and and system then flashed the rom.
So it booted into the rom but i kept getting an error msg saying somthing was stopping, the only way i could get out of it was to hold the power button to switch off. I switched it back on only to get to the boot screen and not go any further.
So this is where it gets wierd, i downloaded another rom and flashed that only to get the same problem, I've now tried 4 or 5 different roms with the same boot loop.
So i can get to recovery and flash a new rom etc but cannot get any further
Does anyone have any help they could offer as Im stuck
Many thanks

Same issue. Updated TWRP to 2.6.3, no avail. I bet if you look at the logs in TWRP you'll see you're not able to mount any partition. Also there is another thread on here that has the same issue. I believe it to be caused by the 4.3 CM Rom, haven't figured out a fix for it yet but if you format EVERYTHING, reinstall the rom you can boot once, but any reboot will put you right back where you are.
Filemanager shows the files are still present in /system /cache /data, so I'm not sure what this points to.

Does look good then :crying:
You'd think that by being still able to get into recovery there would be a chance just to flash a different rom and it would sort it
Not sure what to do next now, was just looking around and was going to reflash my recovery and try then but looks like you have tried that
Really wished I'd left alone now

You'd think, but I'm betting this has to do with the partition table getting corrupted or something of that nature.

unsivil_audio said:
You'd think, but I'm betting this has to do with the partition table getting corrupted or something of that nature.
Click to expand...
Click to collapse
if it is a corrupt partition table then babsector.rar (d/l from the root guide in my sig) will fix that.Do the wipes Then flash this rom if u want cm10, works for me...http://forum.xda-developers.com/showthread.php?t=1935582 -

dibb_nz said:
if it is a corrupt partition table then babsector.rar (d/l from the root guide in my sig) will fix that.Do the wipes Then flash this rom if u want cm10, works for me...http://forum.xda-developers.com/showthread.php?t=1935582 -
Click to expand...
Click to collapse
I;ve tried wiping everything then tried flashing that particular rom but same out come, havent tried the babsector.rar dl yet so will give that a bash, question with that though will i have to reflash to the new bootloaders again so i can run the cm10 ?
Thanks

No m8 the babsector file will auto flash v8/cwm, just be sure to follow the instructions. Run bat file, boot DIRECTLY to cwm, wipe, flash rom and reboot. There is a 2nd bat file u should run next, but most folks have found they're all good after just running the first one...so up to u...if u get any errors pls post the output
Cheers dibb
Sent from my GT-I9300 using Tapatalk 4

dibb_nz said:
No m8 the babsector file will auto flash v8/cwm, just be sure to follow the instructions. Run bat file, boot DIRECTLY to cwm, wipe, flash rom and reboot. There is a 2nd bat file u should run next, but most folks have found they're all good after just running the first one...so up to u...if u get any errors pls post the output
Cheers dibb
Sent from my GT-I9300 using Tapatalk 4
Click to expand...
Click to collapse
Your an absolute genius pal, this worked a treat when all other things failed
Follow this procedure to the letter and you can't fail
Thanks again mate you've saved my tablet
Sent from my GT-I9300 using Tapatalk 2

avenger79 said:
Your an absolute genius pal, this worked a treat when all other things failed
Follow this procedure to the letter and you can't fail
Thanks again mate you've saved my tablet
Sent from my GT-I9300 using Tapatalk 2
Click to expand...
Click to collapse
awsum dude glad you got it
dibb
EDIT: @avenger79, pls edit the title of your thread to [SOLVED] to help others having a similar issue, thanks m8

Thanks guys. This worked for me as well.

dibb_nz said:
if it is a corrupt partition table then babsector.rar (d/l from the root guide in my sig) will fix that.Do the wipes Then flash this rom if u want cm10, works for me...http://forum.xda-developers.com/showthread.php?t=1935582 -
Click to expand...
Click to collapse
Any idea if this babsector might fix this issue here?
http://forum.xda-developers.com/showthread.php?t=2456947

NapalmDawn said:
Any idea if this babsector might fix this issue here?
http://forum.xda-developers.com/showthread.php?t=2456947
Click to expand...
Click to collapse
Well it certainly won't hurt...but first do full a format data, cache, system via fastboot so myt wanna do nandroid backup b4 hand.
Then "fastboot boot recovery" and flash yr rom of choice...
I do know some have had issues with latestv twrp, not sure if there's a fix yet or not. ..
Sent from my GT-I9300 using Tapatalk 4

dibb_nz said:
Well it certainly won't hurt...but first do full a format data, cache, system via fastboot so myt wanna do nandroid backup b4 hand.
Then "fastboot boot recovery" and flash yr rom of choice...
I do know some have had issues with latestv twrp, not sure if there's a fix yet or not. ..
Sent from my GT-I9300 using Tapatalk 4
Click to expand...
Click to collapse
I'm baaaacckkkk :good: Looks like a lot of bricks while I was gone.

Moscow Desire said:
I'm baaaacckkkk :good: Looks like a lot of bricks while I was gone.
Click to expand...
Click to collapse
Haha welcome home MD, trust your sufficiently rested and ready to help out, lol! !
First off, is there a stock 501 update.zip or EUu around or can the 501'ers jyst use evil alex instead...any issues at all with alex? And would it run ok on the a500?
Babsector.rar file is becoming the goto for unbricking. Not sure if you've looked at it or know how it works but there are 2 bat files to run. Of late folks have just run the first one then wiped and flashed a rom without running the 2nd. With no adverse affects. Would u know the reasoning behind running the 2nd bat. Hate to think I've been putting folks wrong...eeek...
Its gr8 to see the 500's still popular as ever, judging by the flurry of 'help I'm bricked' posts lately. Unfortunately as u know I am no dev, so I haven't been able to help out with rom issues...hence my question earlier re: evil alex!
Anyways MD awsum to have u back helping out an keeping an eye on us all
Cheers n thanx again
dibb
Sent from my GT-I9300 using Tapatalk 4

dibb_nz said:
if it is a corrupt partition table then babsector.rar (d/l from the root guide in my sig) will fix that.Do the wipes Then flash this rom if u want cm10, works for me...http://forum.xda-developers.com/showthread.php?t=1935582 -
Click to expand...
Click to collapse
Just FYI, this fixed both of my friends tablets (his and is his wifes ended up soft bricked after reboot). I'm suspecting this is TWRP's (2.1.3) fault but can't be sure. Even reinstalled the CM 10.2 rom and put it through several reboots, no problem now.

unsivil_audio said:
Just FYI, this fixed both of my friends tablets (his and is his wifes ended up soft bricked after reboot). I'm suspecting this is TWRP's (2.1.3) fault but can't be sure. Even reinstalled the CM 10.2 rom and put it through several reboots, no problem now.
Click to expand...
Click to collapse
Fantastic! Which 10.2 are u running?
Sent from my GT-I9300 using Tapatalk 4

This one, the same one that bricked both of them in the first place.
We put hers on the CM 4.1.2 Flex you recommended. Both running like a champ again.:good:

unsivil_audio said:
This one, the same one that bricked both of them in the first place.
We put hers on the CM 4.1.2 Flex you recommended. Both running like a champ again.:good:
Click to expand...
Click to collapse
Some folks have reported playstore probs with Flex so interesting you haven't. When u ran babsector, did u use both bat files? And what wipes did u do in cwm?? I'm just trying to nail down why some are having probs
Sent from my GT-I9300 using Tapatalk 4

I'll have to ask my buddy today if he's had any play store problems.
I did, but I just figured I probably better follow the instructions to the T. I don't really get whats different about the 2nd file 501 b.bat, seemed like it did the same thing.

dibb_nz said:
if it is a corrupt partition table then babsector.rar (d/l from the root guide in my sig) will fix that.Do the wipes Then flash this rom if u want cm10, works for me...http://forum.xda-developers.com/showthread.php?t=1935582 -
Click to expand...
Click to collapse
You SIR are a LIFE SAVER! :good:
I used your babsector.rar and was able to get my A500 working again!
Thank you very, very, very much!! :laugh:

Related

[HELP] Need help getting my Tab backup and running [verizon]

I have a Verizon Tab and to tell the truth I seem to be having more problems than its worth.
After rooting, installing CwM, installing a Kernel and running KhasMek's K-leanMod v2.
I keep running in to problems, wifi problems, market problems, and now it just wont get booted up.
So I would like a start from scratch list.
Also, I am not able to do much from the CwM recovery. I am not able to wipe any thing or clear any thing.
Thanks for the help, this is my 3rd weekend with the Tab and it seems every friday I break the thing and spend the weekend fixing it.
Maybe a stock rom will help you back on track. I've been on stock for 2 months now. Only change I've done is wpa_supplicant and root.
msg on mobile
Mfloresg said:
Maybe a stock rom will help you back on track. I've been on stock for 2 months now. Only change I've done is wpa_supplicant and root.
msg on mobile
Click to expand...
Click to collapse
Where is a pure stock room? I only see 2 roms for the VGT and both dont seem to be stock, also wont I need a stock kernel?
Here
Check this link out should be the answer to your issues...
http://www.droidforums.net/forum/sa...84-how-restore-vzw-galaxy-tab-stock-dj11.html
jschmid698 said:
Check this link out should be the answer to your issues...
http://www.droidforums.net/forum/sa...84-how-restore-vzw-galaxy-tab-stock-dj11.html
Click to expand...
Click to collapse
Thanks, latter tonight when I have time I will try this out and if it works I will take screen shots and post a how to with the files on here so others can use it.
Good luck my friend hope all works out
Sent from my GT-P1000 using XDA App
Once you start over i found when switching to boushh's kernel and rom do a full wipe, wipe cache and dalvik cache. Install the v3 kernel do a full wipe all over again, install rom do one more full wipe as stated above. Then boot normally this seemed to fix all my issues.
Sent from my SCH-I800 using Tapatalk
That was worked for me, I was able to get my Tab back to Stock.
I fallowed the steps and it worked for me so I downloaded the files and copied steps fro, the droid form so we cah have it here as well.
So if you are looking to get your Tab back to stock this should do it.
http://forum.xda-developers.com/showthread.php?p=11601647#post11601647

[Q] Anyone knows where my storagespace went after upgrading to 4.3?

Hey guys,
i noticed something weird after ugrading to android 4.3 (official images).
After the upgrade and setting up my n4 i noticed that my available storagespace was only 6gb, but i have a 16gb model so it must be around 12gb user available space(????) at minimum i guess.
Somebody noticed this too or is there some explaination for this??
I clean flashed the sh*t out of it so that shouldn't be the problem i think.
Cheers
Sgace said:
Hey guys,
i noticed something weird after ugrading to android 4.3 (official images).
After the upgrade and setting up my n4 i noticed that my available storagespace was only 6gb, but i have a 16gb model so it must be around 12gb user available space(????) at minimum i guess.
Somebody noticed this too or is there some explaination for this??
I clean flashed the sh*t out of it so that shouldn't be the problem i think.
Cheers
Click to expand...
Click to collapse
I don't recall the exact cause of this. But if you flash the factory images with the bat file it will be back to normal.
That will also wipe your phone though so keep that in mind.
albundy2010 said:
I don't recall the exact cause of this. But if you flash the factory images with the bat file it will be back to normal.
That will also wipe your phone though so keep that in mind.
Click to expand...
Click to collapse
THNX m8,
gonna try asap!! Will report back.
Really??? So flashing the img one by one isn't the best way to do it, tought it was the right way.
Cheers.
Sgace said:
THNX m8,
gonna try asap!! Will report back.
Really??? So flashing the img one by one isn't the best way to do it, tought it was the right way.
Cheers.
Click to expand...
Click to collapse
I'm sure it can be done no problem flashing them one by one. Just can't recall what causes it. Whether you need to fastboot erase things or what. Maybe don't flash the userdata. Img Had it happen to me on the original nexus 7.
I'm pretty sure if you look around in the how to threads its probably mentioned and explained. Or a Google search. I just don't care. Since the flashing script fixes it / doesn't cause it.
I think it mostly comes up from erasing cache instead of formatting it. I ran into it the other day too when going back to stock. You can try wiping cache if you installed a custom recovery, otherwise a factory reset (formatting data/cache) cleared out up for me
Sent from my Nexus 4 using Tapatalk 4 Beta
Sgace,
I have the same problem.
Did you manage to solve it?
albundy2010,
Do you mean the file named flash-all.bat?
If yes, what should I do with it? enter the bootloader and double click on the file? I mostly used toolkits by now...
Thanks!
Edit: Nevermind, it seems a factory reset (from the phone settings, not recovery) fixed the problem. Wierd.
It will return to phone to a clean full stock 4.3. It will be exactly like how a device would ship from Google with 4.3 on it. Except that the boot loader will still be unlocked.
To use the bat file its fairly simple.
1. Unpack the file you get from Google. Do not extract the files you end up with any further.
2. Depending on how your system is set up it can vary. So just do this to make to be sure. Move everything that was extracted to whatever directory has the fastboot executable ( fastboot exe)in it. Toolkit folder maybe ( I don't use those awful things so no idea where it puts things.). Or the platform tools folder in the SDK if that's installed.
3. Yes the phone needs to be in the bootlader. Once you're in the boot loader just click on the bat from within the folder with the fastboot.exe from step 2.
All this is assuming your computer has the proper drivers / working fastboot etc.
Still lost or can't figure it out, follow the flash factory images guide.
For me also a factoryreset from settings did the job.
Thnx for the help Guys!!
Cheers
Sent from my Nexus 4 using xda app-developers app

[Q] Galaxy s4 Rooted and Custom Rom Problems

I have a Canadian S4 and rooted using the twrp method and then installed the vigin google play edition rom. Everything worked fine at first when I installed it but i was fiddling around after in twrp and thought i should format the internal storage and start completely fresh and now if I install any rom including my original backup the device will boot up into the system fine for the first time but if the device resets after that it just hangs on the galaxy S4 logo and i have to reboot into recovery and flash again. Any ideas on how i could fix this? Thanks!!!
Try this, in twrp go into advanced wipe and wipe dalvik cache, cache, system, data and android secure. Then flash your nandroid.
I don't have a nandroid I have a twrp backup
Jaygrippa said:
I don't have a nandroid I have a twrp backup
Click to expand...
Click to collapse
That is a nandroid.
Dont use TWRP for the S4
From what I have experience and I believe others have as well, if you used TWRP to format where you had to type yes, you are pretty much screwed trying to get things working properly again. Maybe it is certain phones, sd cards, roms, who knows, but after I typed yes in TWRP to format everything, I could flash a rom but couldnt restart and things were buggy. I had to use odin to flash back to stock, re-root and flash the rom again. Now everything is 190% considering my battery life went from 6 hours to 28 with medium usage.
I have always loved TWRP on my other phones, but for the S4, its more frustration and using with caution than its worth.
Another word of caution, use windows to fix your phone. Im on linux and its too much of a pain in the ass to use odin/heimdall to go back to stock for newbs. On windows I went to stock and rooted again in no time.
Good luck!
jd1639 said:
That is a nandroid.
Click to expand...
Click to collapse
After doing that stuff in twrp should I flash right back to my backup of stock touch wiz or straight into the ROM of my choosing? Whenever I would have to reflash I would have to format he internal memory or it wouldn't work
Ya I did the thing where I typed yes... Crap ya its my first time doing all this stuff so you suggest I Re do all of the rooting stuff and then flash my backup I made?
Jaygrippa said:
Ya I did the thing where I typed yes... Crap ya its my first time doing all this stuff so you suggest I Re do all of the rooting stuff and then flash my backup I made?
Click to expand...
Click to collapse
You might have to. I had the same problem today where if the phone rebooted I would just get a black screen. I ended up using Odin with the stock rom, reinstalling twrp and then restoring my backup. I'm pretty sure it was a rom I flashed that caused the initial problem and only Odin would clear things up.
Start Over
Jaygrippa said:
Ya I did the thing where I typed yes... Crap ya its my first time doing all this stuff so you suggest I Re do all of the rooting stuff and then flash my backup I made?
Click to expand...
Click to collapse
Actually its going back to stock, then rerooting. All I did was follow androidrootz guide here:
http://www.androidrootz.com/2013/06/how-to-unroot-unbrick-galaxy-s4.html
After that, motochopper back to get root and followed this guide to install OUDHS recovery:
http://forum.xda-developers.com/showthread.php?t=2291956
This worked for me, at least for now. Hope it can help you out.
ericchaffey said:
Actually its going back to stock, then rerooting. All I did was follow androidrootz guide here:
http://www.androidrootz.com/2013/06/how-to-unroot-unbrick-galaxy-s4.html
After that, motochopper back to get root and followed this guide to install OUDHS recovery:
http://forum.xda-developers.com/showthread.php?t=2291956
This worked for me, at least for now. Hope it can help you out.
Click to expand...
Click to collapse
Hey thanks a bunch ill try that out later. I am at work right now and i can still use my phone on the rom i have just as long as i dont reset it. Ill try all of this out when i get home and see if that works. Thanks for everyones help
Now the only problem is i have to find a Fido ROM
Jaygrippa said:
Hey thanks a bunch ill try that out later. I am at work right now and i can still use my phone on the rom i have just as long as i dont reset it. Ill try all of this out when i get home and see if that works. Thanks for everyones help
Click to expand...
Click to collapse
A couple other notes, to avoid other possible problems, use the original samsung cord when connecting to your computer. Switching USB ports can help if there are transfer or other issues. Its pretty easy and straight forward if everything works out well, but there are so many gawt dayum variables that minor issues can cause problems, though may never manifest.
Hopefully this works and please post some results to help the same in need.
ericchaffey said:
A couple other notes, to avoid other possible problems, use the original samsung cord when connecting to your computer. Switching USB ports can help if there are transfer or other issues. Its pretty easy and straight forward if everything works out well, but there are so many gawt dayum variables that minor issues can cause problems, though may never manifest.
Hopefully this works and please post some results to help the same in need.
Click to expand...
Click to collapse
Ya thinks i will, now im just in the process of finding a rom for Fido, they are owned by rogers so im not sure if the rogers rom will work, This android stuff is so stressful its my first android phone so i hope all goes well!
Jaygrippa said:
Ya thinks i will, now im just in the process of finding a rom for Fido, they are owned by rogers so im not sure if the rogers rom will work, This android stuff is so stressful its my first android phone so i hope all goes well!
Click to expand...
Click to collapse
I get firmware from sammobile.com. You have to register but it's free. You'll download a zip. Use 7-zip to extract the .tar.md5 file from it. Use that in Odin, PDA.
jd1639 said:
I get firmware from sammobile.com. You have to register but it's free. You'll download a zip. Use 7-zip to extract the .tar.md5 file from it. Use that in Odin, PDA.
Click to expand...
Click to collapse
ya even they dont have a specific "Fido" firmware...
Anyone know if I can just use the Rogers ROM its pretty much the same company
Jaygrippa said:
Anyone know if I can just use the Rogers ROM its pretty much the same company
Click to expand...
Click to collapse
It'll work. It'll just put their bloatware on and the boot animation will be theirs
Reflashed
Ok so i reflashed to the stock rom using odin and bam it works again, im just wondering what is a good way now too root, and install the same rom i had
This will have everything you need http://forum.xda-developers.com/showthread.php?p=42320391
Thanks everyone for your help, I got my phone back up and running stock, then i rooted using CF- Autoroot and installed twrp again. I then reinstalled the rom i wanted to use and everything is in tip top order
Jaygrippa said:
Thanks everyone for your help, I got my phone back up and running stock, then i rooted using CF- Autoroot and installed twrp again. I then reinstalled the rom i wanted to use and everything is in tip top order
Click to expand...
Click to collapse
Glad to here it. Have fun.

[Q] STRANGEST ROM Flashing Symptoms and Issues. CALLING Flash, Recovery, EXPERTS!!!

Dear Friends,
I just bought a Sprint S4, and despite my half a decade experience of flashing custom ROMs and such, I seem to run into a whole lot of issues with this phone that I cannot solve or get past.
So some background first, on what's happened and been done to the phone:
1. Bought the phone (don't recall the original firmware), but Rooted it via the QBKing method.
2. Flashed TWRP 6.1 something from the GooManager
3. Have a Class 10 SD 64Gig SD Card that I formatted via S4, so I assume it's in the ExFat format?
4. Downloaded Sacs, put the ZIP on the SD
5. Booted into TWRP, Wiped, Data, Dalvik, Cache, and System
6. Tried Flashing Sacs ZIP from SD, Errored out: Something like: Flash failed, unable to read the Zip file. And some verbiage for Partition
7. I can't Mount my SD or INTERNAL via Recovery. Can read them from the Recovery file Manager, but nothing shows up on the computer, unrecognized drivers (worked fine for the same phone, later, when it was on, so I know it was the drivers that was the issue)
8. Ran straight for Odin after that, but after trying SEVERAL TARs and etc, the phone would NOT begin flashing with Odin even :'(! (Could still enter Download Mode)
9. After HOURS of trying VARIOUS Odin versions and TARs, I found a One-Click EXE with Odin Packaged with the MDC Rooted firmware this FINALLY brought the phone back to life!!
Now the issues remaining that I need your expert help and advice on:
1. Since the phone coming back to life, I went STRAIGHT for Sacs ROM again! MD5 checked it, everything looked good. Put it both on SD and Internal.
2. Made Backups of the MDC ROM
3. Tried Flashing and ran into the similar error that you saw in Step 6 from the Backgroun
4. Downloaded Stock, DeOdexed MF9 ZIP, downgraded TWRP to a stable version, and tried Flashing again and Step 6 repeated. Tried VARIOUS ROMs this way, same issue. Error flashing, something about Partition, and Couldn't read Zip. All these Zips were MD5 Sum CHECKED!
5. The lack of mounting issue as USB drives from Recovery continues
6. Then a FREAK discovery was, when the ZIP failure occurred, I opted for Flash Dalvik and Cache and tried Installing right after that, and BOOM! Sacs starts Flashing !!!
7. I broke Sacs quick, restoring things from Titanium Backup, and when I tried restoring my latest MDC Backup, it recovered with a black screen and bootloops, and NO recovery entry AGAIN :'(!! (I think I may have backed up Recovery with that Nandroid and restored)
8. So I repeated the One-Click again, the phone restored again... this time in FACTORY MODE :-/?? I ignored, and restored to an older MDC backup, which worked!
9. I downloaded TriForce MF9, this time, tried flashing and failure again with Failed Flashing, error reading Zip. And on and on it goes :'(! I can't run Odins with MF9, I can't flash ROMs, I can't mount my INTERNAL AND SD in Recovery and am just straight bummed :'(!!
I have a few hunches:
- Format SD Card as Fat32, using this one app. But I think you lose 32 gig space from your card, right? Also, why doesn't Internal storage mount from Recovery :-/?
- Maybe a I just have bad or corrupted sectors in my Internal AND External storage devices?
In either case, please treat me as a NOOB, and chime in with your thoughts and experience on what you think could be happening? I appreciate ALL your help in advance, thanks for your time !
I would try a new recovery, I have always had problems with the newer TWRPs, I recommend 2.5.0.2 or CWM
^ that, and do you have to update to mf9 before flashing an mf9 rom? That might be helpful. Are you just dirty flashing rom over rom in your attempts, that could be an issue. Wiping and factory resetting before flashing the Rom may help.
Just tossing out random ideas.
Edit: just realized I missed #5 in the first half. Sorry, and missed the stock deodexed part lol.
Sent from my SPH-L720
xchampx13 said:
I would try a new recovery, I have always had problems with the newer TWRPs, I recommend 2.5.0.2 or CWM
Click to expand...
Click to collapse
Yes Sir, I sure did downgrade TWRP, including the version you mentioned.
HPferoxCraft said:
^ that, and do you have to update to mf9 before flashing an mf9 rom? That might be helpful. Are you just dirty flashing rom over rom in your attempts, that could be an issue. Wiping and factory resetting before flashing the Rom may help.
Just tossing out random ideas.
Edit: just realized I missed #5 in the first half. Sorry, and missed the stock deodexed part lol.
Sent from my SPH-L720
Click to expand...
Click to collapse
Also a yes, Sir. MF9 kept failing, that is, it wouldn't be read by Recovery. Odin would fire the Tar either . No dirty flashing... almost EVER !
Any other ideas, guys ? Desperately need help here !
ProFragger said:
Yes Sir, I sure did downgrade TWRP, including the version you mentioned.
Also a yes, Sir. MF9 kept failing, that is, it wouldn't be read by Recovery. Odin would fire the Tar either . No dirty flashing... almost EVER !
Any other ideas, guys ? Desperately need help here !
Click to expand...
Click to collapse
Why dont you just go to stock mdc and download the update and just do a normal ota?
Take your sd card out and try flashing it from your phones storage
Sent from my SPH-L720 using XDA Premium 4 mobile app
ROMANTiC KiD said:
Why dont you just go to stock mdc and download the update and just do a normal ota?
Click to expand...
Click to collapse
That's one of my plans RomanticKid, but I'm flashed to Page Plus, wondet if the OTA will still work? I get notifications for the updates though, next time I Odin EXE, assuming that also leaves me with stock recovery, I will give it a shot. Thanks for your idea...
churchey thanks for your idea as well, tried it, I get the Zip and fail flash error ! Appreciate all the help guys, keep it coming !
churchey360 said:
Take your sd card out and try flashing it from your phones storage
Sent from my SPH-L720 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I just ran into a bunch of problems. Man.. You need to be careful what you flash. Not everything is on the up and up. Steer clear of this website and their firmware. ------> http://galaxys4root.com/galaxy-s4-stock-firmware/ Unless you are intrigued by complex remote spyware. You'll be amazed with the phoney updates that inject things like a note 3 keyboard, Android device manager, and a bogus samsung hub. All of which will show AT THE BOTTOM, NOT THE TOP of your google play "all" list as installed apps.... but not in your installed apps list. They show as installed, but incompatible with your device. Go figure. Somebody had complete control of my device. It took me a minute to figure it out. Then finding a legit source of firmware here. ----->http://samsung-updates.com/device/?id=SPH-L720 I was able to get legit again. But not after encountering the problems you are having. I had to go in and manually delete a few partitions that did not belong and stayed after flashing anything. Once I did that... I flashed the MF9 firmware from samsung.updates.com (the second site I just listed above) and everything is legit now. No phoney updates. No bogus apps. Everything is perfect just like it came when I took it out of the box. Beware.... MANY of these ROM's have b.s. injected into them, and so do some of the firmwares. Take caution bro. I'd be happy to answer any questions if there are any.
Sleepycloud said:
I just ran into a bunch of problems. Man.. You need to be careful what you flash. Not everything is on the up and up. Steer clear of this website and their firmware. ------> http://galaxys4root.com/galaxy-s4-stock-firmware/ Unless you are intrigued by complex remote spyware. You'll be amazed with the phoney updates that inject things like a note 3 keyboard, Android device manager, and a bogus samsung hub. All of which will show AT THE BOTTOM, NOT THE TOP of your google play "all" list as installed apps.... but not in your installed apps list. They show as installed, but incompatible with your device. Go figure. Somebody had complete control of my device. It took me a minute to figure it out. Then finding a legit source of firmware here. ----->http://samsung-updates.com/device/?id=SPH-L720 I was able to get legit again. But not after encountering the problems you are having. I had to go in and manually delete a few partitions that did not belong and stayed after flashing anything. Once I did that... I flashed the MF9 firmware from samsung.updates.com (the second site I just listed above) and everything is legit now. No phoney updates. No bogus apps. Everything is perfect just like it came when I took it out of the box. Beware.... MANY of these ROM's have b.s. injected into them, and so do some of the firmwares. Take caution bro. I'd be happy to answer any questions if there are any.
Click to expand...
Click to collapse
Sorry to hear of your problems brother, indeed, such a pain and disappointing to go through this crap when all you want to do is enjoy the custom ROM goodness . ..
I think the key thing for me to do and understand is cleaning and or deleting partitions that you spoke of... but you'll see, I have so many issues that I keep hitting the wall one way or another . ..
I would LOVE your help if you can make some GTALK time for me?
My address is [email protected]
Appreciate your help in advance!
I just hit you up on hangouts bro.
Sent from my SPH-L720 using Tapatalk
---------- Post added at 01:11 AM ---------- Previous post was at 01:05 AM ----------
I will say this... Your problem could be entirely different than mine. There are other choices besides firmware that will fix many problems. Remapping yhe partitions with PIT files which are also flashed with odin. I wanted to be sure, so I manually deleted partitions, then flashed the good firmware I mentioned above.
Sent from my SPH-L720 using Tapatalk
Sleepycloud said:
I just hit you up on hangouts bro.
Sent from my SPH-L720 using Tapatalk
---------- Post added at 01:11 AM ---------- Previous post was at 01:05 AM ----------
I will say this... Your problem could be entirely different than mine. There are other choices besides firmware that will fix many problems. Remapping yhe partitions with PIT files which are also flashed with odin. I wanted to be sure, so I manually deleted partitions, then flashed the good firmware I mentioned above.
Sent from my SPH-L720 using Tapatalk
Click to expand...
Click to collapse
Hey bro... thanks for your request. .. I actually don't like Hangouts and still use Talk so I didn't get any requests . ..
Can I send you a request somewhere? Appreciate your help!
Just send it from talk. I'll get it. Its the same thing. I see you on there and it says message delivered.
Sent from my SPH-L720 using Tapatalk
Sleepycloud said:
Just send it from talk. I'll get it. Its the same thing. I see you on there and it says message delivered.
Sent from my SPH-L720 using Tapatalk
Click to expand...
Click to collapse
I never got it man... may I have your Gmail to message you? Thanks!

Custom 4.3 to Custom 4.4 request Tutorial

Guys,
This is driving me nuts. I want to update from PAC 4.3 rom to custom 4.4 (probably purity rom). I have been looking aroung for a tutorial to ensure i dont miss any steps and bugger up the phone (call me a newb) but i just cant, for the life of me, find a tut for that.
The devOP suggests your normal Wipe Data> wipe cache> wipe dalvik> Flash ROM> flash Gapps> flash Kernel and reboot.
Whats confusing me is
1. whether i also need to flash radios?
2. whether I need to be on CWM (coz some threads saying TWRP wont work)
3. whether i need to do do anything else out of the ordinary.
Im not one to start a thread unnecessarily, believe me I have searched the forums, and gotten answers too, but I just cant seem to reach a unanimously agreed way to do it. Would love to have a Tutorial, but for the meantime if someone could please help me by just clearing up my doubts.
Thanks a lot.:good:
P.S. i really didnt know where to put this. Moderators, hope its okay.
Just try it out. if you flash it like any other ROM, there is nothing to worry about. If your signal is acting up. Fastboot flash the new radio. If it doesn't flash, use CWM instead of TWRP.
Sent from my Nexus 4 using Tapatalk
SMillerNL said:
Just try it out. if you flash it like any other ROM, there is nothing to worry about. If your signal is acting up. Fastboot flash the new radio. If it doesn't flash, use CWM instead of TWRP.
Sent from my Nexus 4 using Tapatalk
Click to expand...
Click to collapse
Thanks buddy.. So just to be sure, i can still restore a nandroid backup yes? I mean Im all for tinkering with it, just wanna ensure i wont be hitting a wall.
Thanks again.
deathw15h said:
Thanks buddy.. So just to be sure, i can still restore a nandroid backup yes? I mean Im all for tinkering with it, just wanna ensure i wont be hitting a wall.
Thanks again.
Click to expand...
Click to collapse
If you make one beforehand that is.
That's actually a valid point there, since I don't know if the 2 backup types are compatible (although I would suspect that they are) make a backup after you flashed the new recovery as well. Just to be safe.
Good luck, and enjoy 4.4!
Sent from my Nexus 4 using Tapatalk

Categories

Resources