I have tried to install, following instruction on this site to install ROM's. I have tried Starburst and Task650. I currently have the OTA Touchwiz installed from Samsung, and Pershoot kernel 2.6.34-4-cyanogenmod installed. Every time I try it goes through the process and successfully I reboot, it boots to the Samsung Logo (Start) and I wait like 20 minutes and it does nothing, just stay at the start Samsung logo. I have done this several times on each ROM, always having to go back to a backup I did. What am I doing wrong? Why can’t I install any ROMs? I would greatly appreciate some expert advice, because I hear so many great things about Task650 I really want to give it a shot. I am an ex-iPad owner, gave to daughter as a friend had one and let me use it; feel in love with it the moment I picked it up. I have also searched the forums, but I am doing everything to the T as outlined in instructions. Had my tab for a week, it isn’t a 10.1v or I/O series. Thanks everyone in advance for helping a complete noob when it comes to android.
Sounds like a case of missing to clear the cache.
Did you wipe the cache partition and dalvic cache in the recovery menu?
After making major changes like switching between roms or kernels thats recommended and if not done might cause such an issue.
I did
I did do those steps, did the factory wipe/reset, wiped cache, wiped dalvic. Once I did those 3 steps, installed from zip, goes through the steps successfully, but when I reboot it just stay on logo. I read, it could take 5-10 min, but I have waited up to 20 and it doesn't move past that. Just see what I am doing wrong, as the 2 roms have both done that, and I have tried several times with both. Just have the stock rom with Touchwiz OTA upgrade from Samsung, and pershoots latest kernel. Thanks in advance.
bad zip file?
Is it possible the zip files are getting corrupt? Are you downloading them on your tab or on computer and transferring them over? I would also check to see if there are any errors when you flash.
Download from computer and transfer over. How can I if there are errors as once I install a ROM it just stays at the logo. After it starts to install it end with, i cant recall exactly, but it says success. Thanks in advance
In cwm when you flash there is some text readout. That is where some error messages could be seen. That text will be there before you choose reboot on the menu.
sounds like you've had some issues bro. if you do get fed up and need some help, just let me know and we can video chat through gmail or skype to get you through it and get you a custom rom.
slice2011 said:
I have tried to install, following instruction on this site to install ROM's. I have tried Starburst and Task650. I currently have the OTA Touchwiz installed from Samsung, and Pershoot kernel 2.6.34-4-cyanogenmod installed. Every time I try it goes through the process and successfully I reboot, it boots to the Samsung Logo (Start) and I wait like 20 minutes and it does nothing, just stay at the start Samsung logo. I have done this several times on each ROM, always having to go back to a backup I did. What am I doing wrong? Why can’t I install any ROMs? I would greatly appreciate some expert advice, because I hear so many great things about Task650 I really want to give it a shot. I am an ex-iPad owner, gave to daughter as a friend had one and let me use it; feel in love with it the moment I picked it up. I have also searched the forums, but I am doing everything to the T as outlined in instructions. Had my tab for a week, it isn’t a 10.1v or I/O series. Thanks everyone in advance for helping a complete noob when it comes to android.
Click to expand...
Click to collapse
Well first...are you rooted? Do you have Clockworkmod, Superuser, and Busybox?
Oh and congrats on your switch from Apple to Android
slice2011 said:
I have tried to install, following instruction on this site to install ROM's. I have tried Starburst and Task650. I currently have the OTA Touchwiz installed from Samsung, and Pershoot kernel 2.6.34-4-cyanogenmod installed. Every time I try it goes through the process and successfully I reboot, it boots to the Samsung Logo (Start) and I wait like 20 minutes and it does nothing, just stay at the start Samsung logo. I have done this several times on each ROM, always having to go back to a backup I did. What am I doing wrong? Why can’t I install any ROMs? I would greatly appreciate some expert advice, because I hear so many great things about Task650 I really want to give it a shot. I am an ex-iPad owner, gave to daughter as a friend had one and let me use it; feel in love with it the moment I picked it up. I have also searched the forums, but I am doing everything to the T as outlined in instructions. Had my tab for a week, it isn’t a 10.1v or I/O series. Thanks everyone in advance for helping a complete noob when it comes to android.
Click to expand...
Click to collapse
Maybe try in "reverse" order
Flash kernel back to stock - flash the rom you want - if that works then flash pershoots kernel
Just a thought
hy
i installed the overcome rom on my 7500, and i'm so entusiast!
Try it it's very easy!
---------- Post added at 07:21 PM ---------- Previous post was at 07:16 PM ----------
i did it in recovery, do wipe data
Yes its is rooted, cmw, superuser, and busybox all installed. Installed both roms in recovery, hold volume down and power method. Just can't figure it out, I will do the reverse suggestion and report back later tonight or tomorrow.thanks everyone for the advice/help.
no erreor s after install, think task's says success or something to that effect.
Well it finally stuck, I knew it was going right as when it was installing system files, it took like 5 minutes, the other time I did it took like 30 seconds. As per Stinky73 went back to stock Kernel, and wipe data, clear cache partition, and wipe Dalvik Cache, Thanks a million Stinky73 u da man! HELL YEAH this Rock, it is so responsive, seems a hell of a lot smoother, and apps just snap open. Task you did one outstanding job. This is coming from a noob who has no idea how much work goes into these, I am sure a lot. So from a noob to an expert EXCELLENT JOB, love my Tab that much more!!!!! Thanks everyone for the help, I am one happy camper! Now another dilemma, I saw new versions: How do I install these now that I have Tasks650 installed and working? Do I have to do the same steps above, wipe data, cache, and Dalvik? And if so what do I do next, do I do the same: Also is the BOB_WOW_Fix installed using the same method as i read flashable, sorry for the noob question, just want to get it right.
1. install zip from sdcard.
2. choose zip from sdcard.
NEW!!!- Task650's V7.1
Once again... I forgot to add "Desktop UAstring to V7.1 so flash this update after you boot up V7.1 if you want it.
Can someone please give me the proper ateps on installing the bob_wow_fix, and the 2 7.1 updates? Thanks
slice2011 said:
Can someone please give me the proper ateps on installing the bob_wow_fix, and the 2 7.1 updates? Thanks
Click to expand...
Click to collapse
There's no complete fix for BoB and WoW, its a continuous work in progress.
bob wow fix
Are you taking about the fix task posted?
What I had to do was wipe cache first then flash the zip just like you did on the rom. And bobs your uncle.
Edit:
Oh ya I would reboot after each flash just to be sure.
So as you probably read had a hell of a time getting a rom installed, followed stink'ys advice and it worked. Installed 6.0, finally, than installed the 6.1 theme update, no issues. Than downloaded the 7.1, followed op. wiped dalvik, wiped cache, and wipe data/factory restore. No errors, but when I rebooted it got stuck once again on the Samsung logo with the Galaxy Tab 10.1 print. So i do not know what the heck I am doing wrong. I got 6.0 than 6.1 updated and now I am back to my initial problem with 7.1, no I didn't use the 7.1 update one. tried 3 times, and even downloaded the fiel again, and followed the same steps task outlined, and no go. Had to restore the 6.1 from back up.
slice2011 said:
So as you probably read had a hell of a time getting a rom installed, followed stink'ys advice and it worked. Installed 6.0, finally, than installed the 6.1 theme update, no issues. Than downloaded the 7.1, followed op. wiped dalvik, wiped cache, and wipe data/factory restore. No errors, but when I rebooted it got stuck once again on the Samsung logo with the Galaxy Tab 10.1 print. So i do not know what the heck I am doing wrong. I got 6.0 than 6.1 updated and now I am back to my initial problem with 7.1, no I didn't use the 7.1 update one. tried 3 times, and even downloaded the fiel again, and followed the same steps task outlined, and no go. Had to restore the 6.1 from back up.
Click to expand...
Click to collapse
All sounds very strange...is it definitely stuck on the boot screen? These things can take anything from 5-20 minutes on initial boot, there is no definite rule for that, seems to be device related in some strange way...how long have you left it?
I am really an OCD when it comes to upgrading and always backup (nandroid or whatever) then go back to the very start before trying something new...years of PC and Mac have taught me that even tho the manufacturers say you just apply upgrades on top of previous upgrades, sooner or later they will f**k up....
I wonder why you are passing thro all the steps you are...(going thro 6.0, 6.1 etc)
I would be inclined to try going back to stock....stock whatever it was rom when you got the tab (notice you've never stated what model you have), stock kernel, nothing installed....then go direct to Tasks 7.1 (everything needed in 6.x is incorporated in 7.1) .... then, if it boots and runs, add pershoots kernel...
What do you reckon Task?? Can you chip in on this one?
Cheers, Stinky
@ slice2011.....any news?
Drpbody said:
And bobs your uncle..
Click to expand...
Click to collapse
How'd you know Bob was my uncle?
Oh wait..everybody has an uncle bob somewhere
Related
I think I found out the cause of some bootloopings and its the "Log Switch" option in project menu.
When we try to root the rom and the the phone reboots:
A)if he reboots ok, you must go again into project menu (*#*#2846579#*#*) and "switch off" the Log.
Everyone tell us we must switch this thing on in order to root the phone but no one says that we should turn it off again after proccess completed....
B) if starts immediatly with bootlooping and never booted againd after the rooting proccess just take the battery out andenter into recovery (vol up + Power). Once there make a "Data factory reset" and reboot.
The phone will then start normally this time with no Bootloopings.
With luck you have SU installed and the phone is rooted.
If yes, just go to project menu (*#*#2846579#*#*) and "switch off" the Log.
If not just try the rooting again
But the major deal is the Log Switch.
Hope it helps anyone
I never had bootloops with 2.3 official rooted and log switch was turned on before and after
I'm happy for you!
Moved to General
Thought this may be helpful to some, it has no place in the development section.
Thanks for the contribution, i would usually close, but as it could be helpful, on this occasion i will move it.
Take it easy
O_G
yes don't close it please as I noticed that many had bootloop issues with these releases. I was one of them but this finished after switching the log of. In my caes that solved my problems.
I had thought that too but none of the combinations i tried worked.
I had tried switching off Logging,factory data reset,flashed again without rooting and after 2-3 days that everything seemed that worked normal and i had loaded all apps i wanted, bootloop appeared again and had to factory data reset again in order to use phone.
So i gave up and reverted to 2.2
I never had bootloops but if that's really what's causing it, that's a great catch!
Congrats!
well as I said with me, since I have done this the bootlooping stoped.
Before Everytime I reboot the bootlooping started and only stoped with a factory reset. Then I tried to switch Log Off again and not a single bootloop and more than 48 hours.
Flashed OC kernel, UOT Kitchen, etc etc and phone running perfect.
Look, I have flashed and tested this rom many many many times and alwas endup with bootlooping eventually. This did the trick for me and I consider it a major step as I can now use the rom freely and without being afraid.
As I said, is just 1 more Idea that people having this issue could try out and see if helps.
I just took the liberty of sharing this so that in case o dispair for some, they can have other alternatives.
Didn't help me, actually it did the opposite...my phone didn't boot loop until I went and touched the freaking "Log switch" option...should have let it ON...GRRRR....Got to taste Huawei's bad medicine again...or my own...I should have known; if it ain't broken, don't try to fix it!
lololol
Huawei's each one with own personality...
Druida69 said:
lololol
Huawei's each one with own personality...
Click to expand...
Click to collapse
Indeed!
Mine, for example, had precisely the opposite behaviour.
In order to root the phone, with the latest official GB ROM, i had to switch the logging to On. Otherwise i got bootloop with every ROM. I was also unable to root the official roms without logging On.
Well, at least it was coherent.
Question: When we flash a new ROM the logging is turned off by default, right?
If so, how can it influence negatively the ROM stability?
Druida69 said:
lololol
Huawei's each one with own personality...
Click to expand...
Click to collapse
Tell me about it.
SilveRRing said:
Indeed!
Mine, for example, had precisely the opposite behaviour.
In order to root the phone, with the latest official GB ROM, i had to switch the logging to On. Otherwise i got bootloop with every ROM. I was also unable to root the official roms without logging On.
Well, at least it was coherent.
Question: When we flash a new ROM the logging is turned off by default, right?
If so, how can it influence negatively the ROM stability?
Click to expand...
Click to collapse
You understand it opposite m8.
You must turn the Lon On to root the phone.
After root my advice is to turn it back Off again as it was from the beginning..
Ah ok, nevermind then. lol
my x5 dont have bootloop but this topic will help very people,thanks for the trick lol
---------- Post added at 09:14 PM ---------- Previous post was at 09:12 PM ----------
driuda you have a theme of UOT Kitchen??? I make one for me but failed,please help me?i dislike stock theme is for children hehehe
at the moment I only used UOT this time to change the battery icon to battery percentage circular.
Its one of those must haves that I miss from official rom, the battery percentage....
Coking a theme is very easy. You just choose all the option you want and in the end upload the framework-res.apk and SystemUI.apk files and wait for the coking.
After that pick up the file and flash it with CWM.
mhh i dont think that the log switch is the only thing that causes bootloops.
first i installed 2.3.5 and a few hours later i switched the og on. The bootloops started.
So i had to do a factory reset...
Now after the reset I quikly turned off the log switch. but just a few hours later it started again bootlooping......
any other ideas? or do i have to go back to miui? when yes can i do the following?
: 1. factory reset
2. get root
3. install cwm
4. install my backup?
let me see if I understand.
You installed the latest official release, then you switch the log on? for what?
I assume you switch it on to root. Did you root it?
Yes yes you did well by turn it off as the log is off by default.
Next step should be installing the CWM 5.0.2.7.
Unfortunatly after bootlooping start only solution is factory reset which means having the phone all wiped again which is a pain after a few hours of putting it at our taste.
I think restoring a MIUI backup through CWM won't work.
I have tried this preocedure several times with MIUI or any other custom rom.
The correct way to go gack is downgrading to an official 2.2 release, then root it, install CWM, install a MIUI rom (in your case) doing all the 3 wipes. After you confirm that the rom was installed correctly and is working you can then go to CWM and restore a backup.
Druida69 said:
let me see if I understand.
You installed the latest official release, then you switch the log on? for what?
I assume you switch it on to root. Did you root it?
Yes yes you did well by turn it off as the log is off by default.
Next step should be installing the CWM 5.0.2.7.
Unfortunatly after bootlooping start only solution is factory reset which means having the phone all wiped again which is a pain after a few hours of putting it at our taste.
I think restoring a MIUI backup through CWM won't work.
I have tried this preocedure several times with MIUI or any other custom rom.
The correct way to go gack is downgrading to an official 2.2 release, then root it, install CWM, install a MIUI rom (in your case) doing all the 3 wipes. After you confirm that the rom was installed correctly and is working you can then go to CWM and restore a backup.
Click to expand...
Click to collapse
yes i did turn it on becuase i wawnted to prepare it for rooting but since im not at home since 3 days i cant.
But after the bootlooping i turned it off, but it bootlooped later again....
thank you for the intriductions!
edit: where can i find the 2.2 stock rom for germany? and how to install it? like 2.3.5?
levibuko said:
yes i did turn it on becuase i wawnted to prepare it for rooting but since im not at home since 3 days i cant.
But after the bootlooping i turned it off, but it bootlooped later again....
thank you for the intriductions!
edit: where can i find the 2.2 stock rom for germany? and how to install it? like 2.3.5?
Click to expand...
Click to collapse
if it is to downgrade and then move forward to any other rom, custom or not, you can use any version don't loock spexifically to a german one.
Here you have a list of stock rom:
http://forum.xda-developers.com/showthread.php?t=1167882
http://wiki.modaco.com/index.php/Huawei_Firmware_U8800 (MOdaco Wiki)
http://forum.xda-developers.com/wiki/index.php?title=Huawei_U8800_IDEOS_X5 (XDA Wiki)
My galaxy 3 (apollo) came with 2.1, so I thought I would update to 2.2. I downloaded JPU from hotfile, the one that uses sampro.pl as password. Had odin set up with .ops, one package, nothing else checked. It flashes it and restarts a few times, then gets to the samsung logo which flashes, then it just freezes.
I have tried wiping the cache and factory reset. I tried JPS too (which I knew worked on my other phone - but that I upgraded from 2.2 to 2.2) but nothing seems to work.
Have I done something wrong?
I would suggest to flash your mobile once again
by following the instructions in the below link.
http://forum.xda-developewjrs.com/showthread.php?t=1372414
I hope it helps.
Somehow I got it working, I flashed Cyanogenmod and it worked, then wiped all including dalvik cache with cwm, still didn't work when I flashed froyo. So I removed sbl.bin and boot.bin from the .tar, tried and still nothing, then wiped data and cache one last time and on reboot it started up!
I had wiped the data and cache tens of times before and after flashing before, so it was either removing the bootloader or wiping the dalvik cache that made a difference. Only took all day to update my phone!
Try to get some different source for froyo....
I'm Glad you got it working again! next time you need stock firmware, use the one available in this forum by searching "stock jpu" the dev has removed the bootloaders and therefore it is much safer, and yeh as you've discovered, when it doubt, wipe the dalvik!
Hi
Yeah I did come across a thread where someone had removed the bootloaders, but all the files were either removed because they were on megaupload, or linked to JPI. I could have used that, infact I did connect it to kies at the start of the day and it said it could upgrade me to JPU. I wanted to do it by odin though! Then 12 hours later and trying countless other firmwares it worked. I just opened the .tar with 7zip and deleted boot.bin and sbl.bin, I had no idea if that would work or not!
It wasn't stuck in a boot loop so the bootloader couldn't have been corrupt? Perhaps it was the dalvik cache needed to be wiped from 2.1 to 2.2? I couldn't see anyway to wipe it with the stock samsung recovery.
Is CWM available for this phone? (without having to flash Cyanogen!)
mike_1983 said:
Hi
Yeah I did come across a thread where someone had removed the bootloaders, but all the files were either removed because they were on megaupload, or linked to JPI. I could have used that, infact I did connect it to kies at the start of the day and it said it could upgrade me to JPU. I wanted to do it by odin though! Then 12 hours later and trying countless other firmwares it worked. I just opened the .tar with 7zip and deleted boot.bin and sbl.bin, I had no idea if that would work or not!
It wasn't stuck in a boot loop so the bootloader couldn't have been corrupt? Perhaps it was the dalvik cache needed to be wiped from 2.1 to 2.2? I couldn't see anyway to wipe it with the stock samsung recovery.
Is CWM available for this phone? (without having to flash Cyanogen!)
Click to expand...
Click to collapse
CM7 is a aftermarket firmware, so it wont be available in the updates....and also, samsung wont give us this kind of good looking ROM anyways, flashing a ROM is a whole lot faster than updating through Kies or others...
J.Purungrit said:
CM7 is a aftermarket firmware, so it wont be available in the updates....and also, samsung wont give us this kind of good looking ROM anyways, flashing a ROM is a whole lot faster than updating through Kies or others...
Click to expand...
Click to collapse
Hi
I just meant is ClockworkMod available for the Galaxy 3. I noticed it was on my phone when I flashed Cyanogen Mod.
I have a Galaxy 5, the CM7 for that seems more complete, I noticed the camera doesn't work on the Galaxy 3 CM7. I thought they would both be about the same functionality.
In my case flashing a rom was slower as it gave me a bunch of problems, but yeah flashing is usually faster
mike_1983 said:
Hi
I just meant is ClockworkMod available for the Galaxy 3. I noticed it was on my phone when I flashed Cyanogen Mod.
I have a Galaxy 5, the CM7 for that seems more complete, I noticed the camera doesn't work on the Galaxy 3 CM7. I thought they would both be about the same functionality.
In my case flashing a rom was slower as it gave me a bunch of problems, but yeah flashing is usually faster
Click to expand...
Click to collapse
Camera has been mostly fixed in CM7 and Galaxy 5 has been out for longer so devs have had more time. Anyway, all custom ROM's come with CWM Recovery.
I think you can install cwm for stock Roms..I have seen similar question in some thread posted here..which says your phone should be initially rooted to do this..
I am not sure abt the process..but as far as I know..you have to follow these steps :
download an app called as z4root..search in Google..its not available in market..
root your phone..it will ask two options to either root permanently or temporarily..go permanently..(you can unroot it I think so don't worry)
and finally you can try several custom kernals.. head over to development thread for that.I prefer fugumod kernal..take the tar file and flash it via Odin (safer side wipe dalvik as well as cache and reboot)
since its a stock rom ..you will not be having dedicated option to go for recovery, use volume keys,power button and the center button together..
bit of headache..
try at your own risk..or if I am wrong, please advice
Smonic said:
Camera has been mostly fixed in CM7 and Galaxy 5 has been out for longer so devs have had more time. Anyway, all custom ROM's come with CWM Recovery.
Click to expand...
Click to collapse
Ah I didnt know the Galaxy 5 had been out longer. The camera didn't work when I used the latest CM7 for the Galaxy 3, when it took a picture it looked like a commodore loading screen But I didn't check gallery thinking about it, perhaps they came out alright
prabhuthelegend said:
I think you can install cwm for stock Roms..I have seen similar question in some thread posted here..which says your phone should be initially rooted to do this..
I am not sure abt the process..but as far as I know..you have to follow these steps :
download an app called as z4root..search in Google..its not available in market..
root your phone..it will ask two options to either root permanently or temporarily..go permanently..(you can unroot it I think so don't worry)
and finally you can try several custom kernals.. head over to development thread for that.I prefer fugumod kernal..take the tar file and flash it via Odin (safer side wipe dalvik as well as cache and reboot)
since its a stock rom ..you will not be having dedicated option to go for recovery, use volume keys,power button and the center button together..
bit of headache..
try at your own risk..or if I am wrong, please advice
Click to expand...
Click to collapse
I rooted the phone with SuperOneClick, I think it worked! Anyway I gave the phone to my brother now and hes just interested in a working phone, not messing about with roms! I may get the phone again when it comes down in price again (you can get them refurbished in brand new condition here in UK)
Thanks!
First, let me get the formalities out of the way... long time lurker, first time poster. I hope you guys can help me out!
My GS4 semi-bricked while trying to restore my phone from LiquidSmooth ROM . My phone had no MAC address nor IP address after I flashed to LiquidSmooth, so I figured I needed to restore files I may have accidentally deleted.. The phone became stuck on the splash screen so I tried pulling the battery, going into recovery, and clearing cache/dalvik. No luck.
So then I tried to restore using a backup that I had made before flashing, but then it got stuck on the AT&T screen. Tried to clear cache/dalvik, but it didn't work. I thought maybe the back up didn't work because I was flashed into a different ROM, so I downloaded this stock rom by scrosier, and tried again... but to no avail.
Now I want to try flashing the phone back to stock, but I have a early 2008 MacBook running 10.7.5 (Lion). Odin is windows only, and Heimdall doesn't work on my version of OS X (keeps crashing the moment I open it). I thought maybe updating my MacBook to Mountain Lion (10.8) might work, but Mountain Lion is not supported on my Macbook, thus cannot update OS X... and I don't have access to a PC at this moment either.
Is my only option to go out and buy windows and install on bootcamp? Does anyone know if I could flash my phone back to stock using the computer I have now?
Sorry if my post didn't make any sense. I'm in a hurry and I want to fix my phone already! Thanks in advance
EDIT:
I have TWRP 2.5.0.3 on my phone
sebbo1 said:
First, let me get the formalities out of the way... long time lurker, first time poster. I hope you guys can help me out!
My GS4 semi-bricked while trying to restore my phone from LiquidSmooth ROM . My phone had no MAC address nor IP address after I flashed to LiquidSmooth, so I figured I needed to restore files I may have accidentally deleted.. The phone became stuck on the splash screen so I tried pulling the battery, going into recovery, and clearing cache/dalvik. No luck.
So then I tried to restore using a backup that I had made before flashing, but then it got stuck on the AT&T screen. Tried to clear cache/dalvik, but it didn't work. I thought maybe the back up didn't work because I was flashed into a different ROM, so I downloaded this stock rom by scrosier, and tried again... but to no avail.
Now I want to try flashing the phone back to stock, but I have a early 2008 MacBook running 10.7.5 (Lion). Odin is windows only, and Heimdall doesn't work on my version of OS X (keeps crashing the moment I open it). I thought maybe updating my MacBook to Mountain Lion (10.8) might work, but Mountain Lion is not supported on my Macbook, thus cannot update OS X... and I don't have access to a PC at this moment either.
Is my only option to go out and buy windows and install on bootcamp? Does anyone know if I could flash my phone back to stock using the computer I have now?
Sorry if my post didn't make any sense. I'm in a hurry and I want to fix my phone already! Thanks in advance
Click to expand...
Click to collapse
If you are able to access recovery then do this:
Put Liquid Smooth and its gapps on the external card using a card reader
Go into recovery, factory reset, wipe both caches, format /system, flash the rom and gapps, reboot
Colonel Sanders said:
If you are able to access recovery then do this:
Put Liquid Smooth and its gapps on the external card using a card reader
Go into recovery, factory reset, wipe both caches, format /system, flash the rom and gapps, reboot
Click to expand...
Click to collapse
I actually tried to reflash Liquid Smooth and wiped cache / factory reset, but once it reboots, a screen pops up that says "Android is updating" and updates 120 files. However, when it finishes, it gives me an error along the lines of "Unfortunately... something something," and instantly reboots. Then it hangs on the Liquid Smooth splash screen. Couldn't get a good look at what the message said because it happens so quickly.
sebbo1 said:
I actually tried to reflash Liquid Smooth and wiped cache / factory reset, but once it reboots, a screen pops up that says "Android is updating" and updates 120 files. However, when it finishes, it gives me an error along the lines of "Unfortunately... something something," and instantly reboots. Then it hangs on the Liquid Smooth splash screen. Couldn't get a good look at what the message said because it happens so quickly.
Click to expand...
Click to collapse
Then I suggest you flash a different ROM. Try out Slim. Liquid Smooth is just a Slim ripoff.
Put Slim and the Addons on the SD, and flash it like you would when changing ROMs. A clean wipe.
Colonel Sanders said:
Then I suggest you flash a different ROM. Try out Slim. Liquid Smooth is just a Slim ripoff.
Put Slim and the Addons on the SD, and flash it like you would when changing ROMs. A clean wipe.
Click to expand...
Click to collapse
I'll give that a shot. Do you recommend the new 4.3 Google Edition Slim Rom?
sebbo1 said:
I'll give that a shot. Do you recommend the new 4.3 Google Edition Slim Rom?
Click to expand...
Click to collapse
That's not Slim, he just put Slim because it's slimmed down. I haven't personally tried it. I'm a tester for SlimRoms, so thats all I ever run. Test builds. It does look nice though, but it won't have near the customization of Slim.
Colonel Sanders said:
That's not Slim, he just put Slim because it's slimmed down. I haven't personally tried it. I'm a tester for SlimRoms, so thats all I ever run. Test builds. It does look nice though, but it won't have near the customization of Slim.
Click to expand...
Click to collapse
Are you talking about slimroms.net? If you are, which addons do I download?
EDIT: nevermind. I downloaded the AIO (all in one)
sebbo1 said:
Are you talking about slimroms.net? If you are, which addons do I download?
Click to expand...
Click to collapse
Yes, slimroms.net
It just depends on whether or not you want all of the Google apps typically in a regular gapps pkg, or a stripped down version. I use the AIO_Addons, or you could get the Aroma, so you can pick and choose. The Slim_gapps is a stripped down version.
Colonel Sanders said:
Yes, slimroms.net
It just depends on whether or not you want all of the Google apps typically in a regular gapps pkg, or a stripped down version. I use the AIO_Addons, or you could get the Aroma, so you can pick and choose. The Slim_gapps is a stripped down version.
Click to expand...
Click to collapse
One last question before I flash the rom. Is it loki'd? I don't see the answer on the website
sebbo1 said:
One last question before I flash the rom. Is it loki'd? I don't see the answer on the website
Click to expand...
Click to collapse
Last time I flashed a weekly, it wasn't loki'd, but that was a while back. I'm running test builds from black_jck, and build my own sometimes. I mentioned it to him that the weekly wasn't loki'd but that was a while back, so I can't speak for them now. The official builds are. If you're going to flash the weekly, flash loki_doki just to be safe.
Colonel Sanders said:
Last time I flashed a weekly, it wasn't loki'd, but that was a while back. I'm running test builds from black_jck, and build my own sometimes. I mentioned it to him that the weekly wasn't loki'd but that was a while back, so I can't speak for them now. The official builds are. If you're going to flash the weekly, flash loki_doki just to be safe.
Click to expand...
Click to collapse
Alright, so I flashed Slim and the AIO_addons, and rebooted the phone.
Once it was rebooting, the screen i mentioned earlier popped up, that said "Android is updating" and went through 109 files. When it was done, an error popped up quickly, saying that "Unfortunately..." and I couldn't read the rest before the phone rebooted. I let the screen hang for about 10 minutes, pulled the battery, cleared cache and dalvik, and rebooted again. No luck.
I think my best option now would be to return to stock, but I can't using my macbook. So my original question still stands.. How can I return to stock without using Odin and Heimdall?
sebbo1 said:
Alright, so I flashed Slim and the AIO_addons, and rebooted the phone.
Once it was rebooting, the screen i mentioned earlier popped up, that said "Android is updating" and went through 109 files. When it was done, an error popped up quickly, saying that "Unfortunately..." and I couldn't read the rest before the phone rebooted. I let the screen hang for about 10 minutes, pulled the battery, cleared cache and dalvik, and rebooted again. No luck.
I think my best option now would be to return to stock, but I can't using my macbook. So my original question still stands.. How can I return to stock without using Odin and Heimdall?
Click to expand...
Click to collapse
I would say so myself, Odin back to stock, but since you have a mac and I'm not sure if Heimdall support the S4 try this:
Factory Reset
Wipe Cache
Wipe Dalvik
Format /system
Format /data
Format /internal (If CWM-based recovery)
Flash ROM, addons, reboot
sebbo1 said:
Alright, so I flashed Slim and the AIO_addons, and rebooted the phone.
Once it was rebooting, the screen i mentioned earlier popped up, that said "Android is updating" and went through 109 files. When it was done, an error popped up quickly, saying that "Unfortunately..." and I couldn't read the rest before the phone rebooted. I let the screen hang for about 10 minutes, pulled the battery, cleared cache and dalvik, and rebooted again. No luck.
I think my best option now would be to return to stock, but I can't using my macbook. So my original question still stands.. How can I return to stock without using Odin and Heimdall?
Click to expand...
Click to collapse
I forgot to mention, the red LED light flashes every once in a while while on the Slim screen
sebbo1 said:
I forgot to mention, the red LED light flashes every once in a while while on the Slim screen
Click to expand...
Click to collapse
That means the battery is low... Charge it up some... Check your PM for my gmail if you need some help, posting back and forth can take a while.
Well thanks for all your help! Happy that my phone is working again without having to flash to stock.
Phone booted normally once I switched to SlimBean. Much snappier and responsive than LiquidSmooth. Fixed the problems I was having with WiFi also.
Still haven't figured out a way to flash to stock using OS X Lion since Heimdall doesn't work and Odin is Windows only... Mods please lock or close thread because I don't need help anymore
sebbo1 said:
Well thanks for all your help! Happy that my phone is working again without having to flash to stock.
Phone booted normally once I switched to SlimBean. Much snappier and responsive than LiquidSmooth. Fixed the problems I was having with WiFi also.
Still haven't figured out a way to flash to stock using OS X Lion since Heimdall doesn't work and Odin is Windows only... Mods please lock or close thread because I don't need help anymore
Click to expand...
Click to collapse
Glad you got it going man, and enjoy Slim, it's hands down the best ROM there is if you prefer minimal with tons of customization options.
Hey guys, so, i accidently took an OTA update on a rooted phone...The problem is, now the phone will only go into CWM, i've tried wiping cache, dalvik cache, factory reset, etc!! Nothing works, also even tried the "CWM Boot Loop" forum steps..Long story short, nothing works guys! When I run ADB, and i send TWRP over, my phone receives it, but then it just says "installation aborted"..SO ANY HELP IS GREATLY APPRECIATED GUYS!! Not sure if the phone is completely screwed and it's time for a new one? Or it's just an easy fix and i'm doing something wrong. Link Below from the forum i followed...
http://forum.xda-developers.com/showthread.php?t=2567493
Step 5 is where I can't get past because the phone says "Installation Aborted"^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
SOLUTION:
Hey guys, fixed the phone...Basically I had to go back to bone stock..The way i did this was by going to this link BELOW
http://forum.xda-developers.com/showthread.php?t=2432476
& then I basically just downloaded what was told to be downloaded, and then followed the instructions, now what it doesn't mention is you need to flash a stock rom, apparently the software used to flash this stock rom hates all the rooted crap, like "slim rom, beanstock, cyanogen," etc...other than that, worked like a charm! took around 10-15 minutes and there it was...UP AND RUNNING .
Let me know if ya have any questions.
So I'm pretty desperate and I apologize if similar info was posted somewhere else. I've been researching several hours but couldn't find anything.
I originally installed CM11 and decided to experiment with a different rom TriForce ROM [TouchWiz]. I put the zip file on my SD card and booted into clockworkmod it gave an error of bad zip. I tried different usb port to transfer the zip, downloaded it multiple times with no result. So I decided to try a different rom Stock_Rooted_Deodexed_MF9_Rom.zip. The installation finished but the phone would not boot.
Recently I flashed the stock rom from odin, it finished successfully but still not boot, Galaxy sreen lights up quickly and that's it.
rmngorelov said:
So I'm pretty desperate and I apologize if similar info was posted somewhere else. I've been researching several hours but couldn't find anything.
I originally installed CM11 and decided to experiment with a different rom TriForce ROM [TouchWiz]. I put the zip file on my SD card and booted into clockworkmod it gave an error of bad zip. I tried different usb port to transfer the zip, downloaded it multiple times with no result. So I decided to try a different rom Stock_Rooted_Deodexed_MF9_Rom.zip. The installation finished but the phone would not boot.
Recently I flashed the stock rom from odin, it finished successfully but still not boot, Galaxy sreen lights up quickly and that's it.
Click to expand...
Click to collapse
Restore from nandroid backup. I hope you made one. Try going into recovery do a factory reset and wipe all cache and data and what not and then install a ROM from Odin.
rmngorelov said:
So I'm pretty desperate and I apologize if similar info was posted somewhere else. I've been researching several hours but couldn't find anything.
I originally installed CM11 and decided to experiment with a different rom TriForce ROM [TouchWiz]. I put the zip file on my SD card and booted into clockworkmod it gave an error of bad zip. I tried different usb port to transfer the zip, downloaded it multiple times with no result. So I decided to try a different rom Stock_Rooted_Deodexed_MF9_Rom.zip. The installation finished but the phone would not boot.
Recently I flashed the stock rom from odin, it finished successfully but still not boot, Galaxy sreen lights up quickly and that's it.
Click to expand...
Click to collapse
Make sure you're using roms for your version of your phone. the MF9 bootloader is really old and probably wont install anymore. My phone did this before and I thought I bricked it, but I kid you not I took the battery out and removed the SIM card and rebooted and it booted up just fine. May not work for you, but I suggest you go back to update stock firmware then try again. If you're using the triband model, there's a post around here somewhere with confirmed roms that wont brick your device. I'm currently using the Google Play Edition Stock ROM and it's working GREAT.
Link for new firmware (NG5 Firmware): https://mega.co.nz/#F!0JdRkIZR!AqqKdbvba_Hpg5VrCmrbPw
i7vSa7vi7y said:
Restore from nandroid backup. I hope you made one. Try going into recovery do a factory reset and wipe all cache and data and what not and then install a ROM from Odin.
Click to expand...
Click to collapse
I restored to this stock ROM before and everything worked well. Currently I can't boot into recovery, Samsung flashes once and that's it, that's why I'm desperate the only thing I can do is boot in to download mode for odin.
silentdeath631 said:
Make sure you're using roms for your version of your phone. the MF9 bootloader is really old and probably wont install anymore. My phone did this before and I thought I bricked it, but I kid you not I took the battery out and removed the SIM card and rebooted and it booted up just fine. May not work for you, but I suggest you go back to update stock firmware then try again. If you're using the triband model, there's a post around here somewhere with confirmed roms that wont brick your device. I'm currently using the Google Play Edition Stock ROM and it's working GREAT.
Link for new firmware (NG5 Firmware):
Click to expand...
Click to collapse
Does it matter that I can't get into recovery to clear the cache first before trying new roms?
silentdeath631 said:
Make sure you're using roms for your version of your phone. the MF9 bootloader is really old and probably wont install anymore. My phone did this before and I thought I bricked it, but I kid you not I took the battery out and removed the SIM card and rebooted and it booted up just fine. May not work for you, but I suggest you go back to update stock firmware then try again. If you're using the triband model, there's a post around here somewhere with confirmed roms that wont brick your device. I'm currently using the Google Play Edition Stock ROM and it's working GREAT.
Link for new firmware (NG5 Firmware):
Click to expand...
Click to collapse
Maybe I'm doing something foolish but every time I try to download files from the link you gave I get a decryption error so I can't download them zip or original.
rmngorelov said:
I restored to this stock ROM before and everything worked well. Currently I can't boot into recovery, Samsung flashes once and that's it, that's why I'm desperate the only thing I can do is boot in to download mode for odin.
Click to expand...
Click to collapse
Just hold home power and volume up. Right when you see text at the top left let go. You have to have the right timing
i7vSa7vi7y said:
Just hold home power and volume up. Right when you see text at the top left let go. You have to have the right timing
Click to expand...
Click to collapse
After almost eight hours of troubleshooting I finally got it to work.
I've tried flashing clockworkmod several times to see if I could get into recovery with no result so I gave up on that and I flashed the newest stock rom I could find L720VPUFNG2_L720SPTFNG2_SPR and it was still not booting. Than I thought maybe twerp would make a difference and god almighty it finally booted! I felt as if I gave birth to a child after eight hours of labor!
Now I'm extremely paranoid about touching anything because it took me forever to do this. Does anyone know why flashing twerp would make such a difference? I know this sort of stuff can get extremely complicated but I'd like to try to understand.
I hope my foolish agony contributed to this community if not in any other way except by the comedic relief caused by my ignorance.
rmngorelov said:
After almost eight hours of troubleshooting I finally got it to work.
I've tried flashing clockworkmod several times to see if I could get into recovery with no result so I gave up on that and I flashed the newest stock rom I could find L720VPUFNG2_L720SPTFNG2_SPR and it was still not booting. Than I thought maybe twerp would make a difference and god almighty it finally booted! I felt as if I gave birth to a child after eight hours of labor!
Now I'm extremely paranoid about touching anything because it took me forever to do this. Does anyone know why flashing twerp would make such a difference? I know this sort of stuff can get extremely complicated but I'd like to try to understand.
I hope my foolish agony contributed to this community if not in any other way except by the comedic relief caused by my ignorance.
Click to expand...
Click to collapse
Depends what recovery you had and what version. I personally like Philz touch recovery but TWRP is good. Now wipe and flash a ROM my friend or restore a backup
rmngorelov said:
After almost eight hours of troubleshooting I finally got it to work.
I've tried flashing clockworkmod several times to see if I could get into recovery with no result so I gave up on that and I flashed the newest stock rom I could find L720VPUFNG2_L720SPTFNG2_SPR and it was still not booting. Than I thought maybe twerp would make a difference and god almighty it finally booted! I felt as if I gave birth to a child after eight hours of labor!
Now I'm extremely paranoid about touching anything because it took me forever to do this. Does anyone know why flashing twerp would make such a difference? I know this sort of stuff can get extremely complicated but I'd like to try to understand.
I hope my foolish agony contributed to this community if not in any other way except by the comedic relief caused by my ignorance.
Click to expand...
Click to collapse
im having similar issues. which version of TWRP worked for you?
thank you
fearthemarchx said:
im having similar issues. which version of TWRP worked for you?
thank you
Click to expand...
Click to collapse
I recommend flashing the newest one here using odin
http://teamw.in/project/twrp2
Then once you are able to boot into recovery go to wipe and perform both factory reset and format data. Then install whatever rom you like, I used Sprint Galaxy S4 SPH-L720 VPUFNAE (Androdi 4.4.2) found here
http://galaxys4root.com/galaxy-s4-stock-firmware/ (or maybe find a newer stock rom if this one gives you errors)
Just copy the zip file to the phone, boot into twrp, do wipe factory reset again, select install then select the zip in whatever directory and you should be good to go. Make sure you do a back up in twrp once you get the phone to boot so you can always revert to stock.
I hope I was thorough enough that some of the information was useful. Let me know if you need any more help.
only certain recoveries will stick. ive tried the most recent twrp, with no luck. only a few versions of philztouch work.
Sent from my LGL34C using XDA Free mobile app
fearthemarchx said:
only certain recoveries will stick. ive tried the most recent twrp, with no luck. only a few versions of philztouch work.
Sent from my LGL34C using XDA Free mobile app
Click to expand...
Click to collapse
Format with philztouch that works then try flashing a new stock rom with odin. That should bring everything back to stock including the recovery.
ive tried. when i flash rom via odin i only get a blue "recovery booting" at the top of boot screen. even when i only power on, not into recovery. im going to attempt to flash rom provided in previous post via philz.
Sent from my LGL34C using XDA Free mobile app
fearthemarchx said:
ive tried. when i flash rom via odin i only get a blue "recovery booting" at the top of boot screen. even when i only power on, not into recovery. im going to attempt to flash rom provided in previous post via philz.
Sent from my LGL34C using XDA Free mobile app
Click to expand...
Click to collapse
You're in download mode when you flash from odin right? If you your getting an error flashing, try a different stock rom after reformating/resetting to factory (it's crucial to clear the cache before trying a different rom). I had to try a few roms before I found one that worked.