[Q] Problem switching ROM - Verizon HTC One (M8)

I've got viper one rom and I'm trying to install android revolution hd. I checked the md5 and installed it with TWRP, but when the phone boots and the setup begins the first thing that appears is viper tweaks (from the viper one rom) requesting root access. Once the setup is finished a message appears saying "blinkfeed has stopped working" and then I can do absolutely nothing except power off the phone.
Shouldn't viper be removed when I wipe in TWRP?
Anyone have any idea wtf is going on?

I went from nV RLS 1.1 to RLS 2, clean flash in TWRP. When it booted my same setup was on the screen with everything force closing. I went back into TWRP attempted again, and it was still messed up. Tried to restore a backup, it failed, then TWRP started crashing. I could only get into fastboot.
Anyways, you can read my post in this section. I had to go back to stock, then restore a nandroid.
Sent from my Nexus 7 using Tapatalk

jova33 said:
I went from nV RLS 1.1 to RLS 2, clean flash in TWRP. When it booted my same setup was on the screen with everything force closing. I went back into TWRP attempted again, and it was still messed up. Tried to restore a backup, it failed, then TWRP started crashing. I could only get into fastboot.
Anyways, you can read my post in this section. I had to go back to stock, then restore a nandroid.
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
Were you able to successfully install RLS 2? If so how?

chobungus said:
Were you able to successfully install RLS 2? If so how?
Click to expand...
Click to collapse
I haven't yet. I want to know what went wrong the first time before I attempt it again.
Sent from your mom's smartphone

jova33 said:
I haven't yet. I want to know what went wrong the first time before I attempt it again.
Sent from your mom's smartphone
Click to expand...
Click to collapse
I actually just downloaded and installed nV RLS 2 with no problems at all.. My problem may related to the Android Revolution HD rom itself.. I'll have try to figure it out another time.
Thanks for your help!

For anyone who's interested I was able to successfully install ARHD to my phone after doing some research. Rather than just doing the standard wipe in TWRP (it wipes delvik, cache, and data) I had to selected "advanced wipe" and wipe system in addition to delvik, cache, and data. I believe this had to do with the htc build version on the phone being outdated but I'm not 100% sure.

chobungus said:
For anyone who's interested I was able to successfully install ARHD to my phone after doing some research. Rather than just doing the standard wipe in TWRP (it wipes delvik, cache, and data) I had to selected "advanced wipe" and wipe system in addition to delvik, cache, and data. I believe this had to do with the htc build version on the phone being outdated but I'm not 100% sure.
Click to expand...
Click to collapse
+1. I always use advanced wipe in TWRP, and wipe as you indicated. I'm thinking everyone posting here should also indicate which version of TWRP you are using, as that may be an issue as well.

xRogerxC said:
+1. I always use advanced wipe in TWRP, and wipe as you indicated. I'm thinking everyone posting here should also indicate which version of TWRP you are using, as that may be an issue as well.
Click to expand...
Click to collapse
Yes that's a good idea! I've just added TWRP version (2702) to my signature

Related

miui and CM7 keeps cycling the inital loading

hi all,
Ok, I'm new to this stuff.
1. used the simple root and it worked great.
2. I then flashed CM7 and it worked great except market was not on it.
3. I downloaded and flashed gapps-hdpi-20101114-signed.zip by mistake, not realizing I had to use another gapps.
4. After I flashed it, the cm7 and android setup screens kept cycling between each other.
5. I restored to clockworkmod (sp) and then deleted the gapps and tried to then flash cm7. It didn't cycle between cm7 and android setup, but the cm7 screens kept cycling and never got past that.
6. I thought perhaps it was just cm7 now, so I tried miui and it's doing the same thing. It's cycling between the gingerbread man and MIUI with the status bar and won't do anything else.
Very frustrated. what have I done and how do I fix it?
Thanks folks,
Brett
I believe that those ROMs both require ENG S-OFF. Open simple root on your computer, click Fixes, then apply the fix there. Also, did you make sure you cleared your Dalvik cache before flashing? Always do a factory reset AND clear dalvik cache when changing ROMs.
make sure you have wifi off in your first boot
ardynine said:
make sure you have wifi off in your first boot
Click to expand...
Click to collapse
From reading the first post, he got in, rebooted to flash gapps and ended up in bootloop afterwards
EtherealRemnant said:
From reading the first post, he got in, rebooted to flash gapps and ended up in bootloop afterwards
Click to expand...
Click to collapse
Thanks ER. I'll try your method this evening.
I'll report back.
thanks!
brett
EtherealRemnant said:
I believe that those ROMs both require ENG S-OFF.
Click to expand...
Click to collapse
I can say with no doubt whatsoever, no.
id10terrordfw said:
I can say with no doubt whatsoever, no.
Click to expand...
Click to collapse
any suggestions then???????
I tried doing the ENG-off and still the same hang up on the front screen.
Any help please?
thanks,
brett
what method do you use to flash cm7? what exactly do you do.
to clarify what is your exact process for flashing the rom?
mudknot2005 said:
what method do you use to flash cm7? what exactly do you do.
Click to expand...
Click to collapse
Hi. Thanks.
I use rom manager to boot to recovery. Then I install zip from sd card. I go through the process until it says reboot. It's when I reboot that I get stuck in the bootloop. It just cycles from the CM7 circular arrow to blank and then to the arrow thing again. MIUI does the same between the gingerbread guy and the status bar and back.
I then take the battery out, take out the sdcard, down volume & power, reinsert sdcard and do a restore so I can use my phone again in clockworkmod 3.0.0.6.
thanks,
brett
sounds like your forgetting to do a full wipe/factory reset, wipe cache, and wipe dalvik..
mudknot2005 said:
sounds like your forgetting to do a full wipe/factory reset, wipe cache, and wipe dalvik..
Click to expand...
Click to collapse
actually, I did that.
it's weird. I restored a few times, did the above you suggested, and still in a loop. The first time I installed CM7 it was great, then the gapps thing seems to have screwed it up.
I'm lost.
brett
bdws1975 said:
actually, I did that.
it's weird. I restored a few times, did the above you suggested, and still in a loop. The first time I installed CM7 it was great, then the gapps thing seems to have screwed it up.
I'm lost.
brett
Click to expand...
Click to collapse
Probably a silly question but you're doing full reinstalls, right? Not using a nandroid backup? I can't think of any reason that you should be boot looping permanently from flashing the gapps if you're going into clockwork, doing a factory reset, wiping the cache, then wiping the Dalvik cache, then flashing the ROM.
EtherealRemnant said:
Probably a silly question but you're doing full reinstalls, right? Not using a nandroid backup? I can't think of any reason that you should be boot looping permanently from flashing the gapps if you're going into clockwork, doing a factory reset, wiping the cache, then wiping the Dalvik cache, then flashing the ROM.
Click to expand...
Click to collapse
hmm. I'm a little new to this, but I'm using the backup/restore option in recovery mode and am then flashing one of the backups. Could that be the problem?
If it is, how do I do a full reinstall?
thanks again for your help,
brett
mudknot2005 said:
sounds like your forgetting to do a full wipe/factory reset, wipe cache, and wipe dalvik..
Click to expand...
Click to collapse
Without a full wipe I thought it would just bootloop?
Do a full wipe then reinstall cm7 and gapps.
Sent from my HTC Inspire 4G running CyanogenMod 7 using Tapatalk.
bdws1975 said:
hmm. I'm a little new to this, but I'm using the backup/restore option in recovery mode and am then flashing one of the backups. Could that be the problem?
If it is, how do I do a full reinstall?
thanks again for your help,
brett
Click to expand...
Click to collapse
That's your problem right there. If you make a backup of a busted ROM, its still going to be busted when you restore it.
Do the factory reset, then clear the cache again just to make sure, go to advanced and clear Dalvik, then go to the main menu and use the choose install zip from sdcard option, then choose "choose zip from sdcard", find the ROM zip file and select it, then say yes to the flash and reboot when its done. If you are flashing CM7, make sure that you flash the correct gapps package after you flash the ROM or the ROM won't be very useful.
EtherealRemnant said:
That's your problem right there. If you make a backup of a busted ROM, its still going to be busted when you restore it.
Do the factory reset, then clear the cache again just to make sure, go to advanced and clear Dalvik, then go to the main menu and use the choose install zip from sdcard option, then choose "choose zip from sdcard", find the ROM zip file and select it, then say yes to the flash and reboot when its done. If you are flashing CM7, make sure that you flash the correct gapps package after you flash the ROM or the ROM won't be very useful.
Click to expand...
Click to collapse
I'll give it a shot and then get back to you.
I do believe, however, that the restore I'm doing is the backup I did right before I did the original cm7 flash. I'll try.
thanks!
If you toggle wifi on after the first boot it goes into a bootloop. This is a know bug not a hunch.
EtherealRemnant said:
That's your problem right there. If you make a backup of a busted ROM, its still going to be busted when you restore it.
Do the factory reset, then clear the cache again just to make sure, go to advanced and clear Dalvik, then go to the main menu and use the choose install zip from sdcard option, then choose "choose zip from sdcard", find the ROM zip file and select it, then say yes to the flash and reboot when its done. If you are flashing CM7, make sure that you flash the correct gapps package after you flash the ROM or the ROM won't be very useful.
Click to expand...
Click to collapse
DUDE!!!! You freaking rock. I got it!
I installed MIUI and it's amazing. Thank you very much.
Brett
Mustang302LX said:
Without a full wipe I thought it would just bootloop?
Do a full wipe then reinstall cm7 and gapps.
Sent from my HTC Inspire 4G running CyanogenMod 7 using Tapatalk.
Click to expand...
Click to collapse
thank you!!!!! I really appreciate your help!

[Q] Stuck on bootscreen after flashing [JB]Unoffical MIUI 2.9.14 Skyrocket[PORT]

Hello Pros! First post, semi-noob here.
I tried flashing the newest [JB][CM10Based]Unoffical MIUI 2.9.14 Skyrocket 9/14/12[PORT] today. I followed all instructions; I wiped wiped wiped, factory and Dalvik, and flashed the kernel.
But I am always stuck on the MIUI bootscreen, and can never fully load up the ROM. I've tried wiping and re-flashing several times, to no avail. I have not had any problems flashing roms before this. Any help or ideas of what causes this would be greatly appreciated.
Thanks so much!
shentheory said:
Hello Pros! First post, semi-noob here.
I tried flashing the newest [JB][CM10Based]Unoffical MIUI 2.9.14 Skyrocket 9/14/12[PORT] today. I followed all instructions; I wiped wiped wiped, factory and Dalvik, and flashed the kernel.
But I am always stuck on the MIUI bootscreen, and can never fully load up the ROM. I've tried wiping and re-flashing several times, to no avail. I have not had any problems flashing roms before this. Any help or ideas of what causes this would be greatly appreciated.
Thanks so much!
Click to expand...
Click to collapse
Couple things.... did u format data/system? Also what recovery are u using?
Deliberate said:
Couple things.... did u format data/system? Also what recovery are u using?
Click to expand...
Click to collapse
Yes, I formatted both system and data. And I'm using the recovery that was recommended in the rom thread, Sk8er's Cwm v13.
Thanks for your reply!
shentheory said:
Yes, I formatted both system and data. And I'm using the recovery that was recommended in the rom thread, Sk8er's Cwm v13.
Thanks for your reply!
Click to expand...
Click to collapse
Try reflashing. But when u get into recovery go to extras/darkside tool. And click on the super wipe(idr what's its called but there's only two options.) When that's done factory reset format data/system 3x if u want.( Couldn't hurt) then flash ROM! All should be good... if not keep this thread open. Lol and well try something else. But hopefully that works. Good luck!
Deliberate said:
Try reflashing. But when u get into recovery go to extras/darkside tool. And click on the super wipe(idr what's its called but there's only two options.) When that's done factory reset format data/system 3x if u want.( Couldn't hurt) then flash ROM! All should be good... if not keep this thread open. Lol and well try something else. But hopefully that works. Good luck!
Click to expand...
Click to collapse
Thanks for the steps, but unfortunately I'm still staring at this dang MIUI bootscreen...:crying:
I ran the darkside superwipe, factory reset 3x, and formatted both data/system 3x, flashed the rom, and I'm still staring at this dang MIUI bootscreen... waaa waaaaaaa, what's the DEALIO?
shentheory said:
Thanks for the steps, but unfortunately I'm still staring at this dang MIUI bootscreen...:crying:
I ran the darkside superwipe, factory reset 3x, and formatted both data/system 3x, flashed the rom, and I'm still staring at this dang MIUI bootscreen... waaa waaaaaaa, what's the DEALIO?
Click to expand...
Click to collapse
Really? Damn. Are u on the latest recovery? If not try flashing the newest. Then do the steps again in my last post. Can't believe your having all these troubles!
Oh also u could try fixing permissions. After doing all the wipes and after flashing. Go to dark side tools again and do the cashe wipe! Then go back to advanced and fix permissions again.
Can you boot into recovery or not? If you can, just flash the rom. If you can't, yank the battery, replace it. Then, hold down both volume buttons, the press the power button, release all the buttons, you should be able to get into recovery.
Deliberate said:
Really? Damn. Are u on the latest recovery? If not try flashing the newest. Then do the steps again in my last post. Can't believe your having all these troubles!
Oh also u could try fixing permissions. After doing all the wipes and after flashing. Go to dark side tools again and do the cashe wipe! Then go back to advanced and fix permissions again.
Click to expand...
Click to collapse
Wow, still stuck on the boot screen even after the darkside cache wipe. I flashed CWMR Touch v6.0.1.3 by sk8erwitskil which is the newest CWM recovery as far as I believe, and the recommended recovery for this ROM. I EVEN flashed TWRP 2.2 just for the heck of it and flashed MIUI with that and still the same result; stuck on bootscreen. So I'm pretty sure it's not the recovery.
I did a darkside superwipe, and a darkside cache wipe, along with factory reset & format data/system 3x. The rom installs in recovery just fine. It's just once i reboot, i get the MIUI splash loading screen indefinitely. I'm not sure what could be causing this since I do all the important wipes (plus the darkside wipes now) each time. I think I have BAD LUCK!
You'll have to use odin, and reroot your phone.
Have you checked the MD5 of the ROM? If it's a bad DL it could flash just enough of it to loop you.
shentheory said:
Wow, still stuck on the boot screen even after the darkside cache wipe. I flashed CWMR Touch v6.0.1.3 by sk8erwitskil which is the newest CWM recovery as far as I believe, and the recommended recovery for this ROM. I EVEN flashed TWRP 2.2 just for the heck of it and flashed MIUI with that and still the same result; stuck on bootscreen. So I'm pretty sure it's not the recovery.
I did a darkside superwipe, and a darkside cache wipe, along with factory reset & format data/system 3x. The rom installs in recovery just fine. It's just once i reboot, i get the MIUI splash loading screen indefinitely. I'm not sure what could be causing this since I do all the important wipes (plus the darkside wipes now) each time. I think I have BAD LUCK!
Click to expand...
Click to collapse
I had the same problem, but while my phone was stuck on the MIUI boot screen i pulled the batter, got into recovery again and simply did a factory data reset just once and then it booted up, but my issue is that i get no data at all no mater what version of MIUI I try to flash.
mimart7 said:
You'll have to use odin, and reroot your phone.
Click to expand...
Click to collapse
Even if my stock rom is already rooted? I'm not against trying it, I'm just curious to how that could affect it. Thanks for your help!
hechoen said:
Have you checked the MD5 of the ROM? If it's a bad DL it could flash just enough of it to loop you.
Click to expand...
Click to collapse
I will do this and update when I do, Thanks for your help!
hechoen said:
Have you checked the MD5 of the ROM? If it's a bad DL it could flash just enough of it to loop you.
Click to expand...
Click to collapse
Ya I agree try downloading it again. Check the md5 and flash that ROM again. If it doesn't work your gonna have to Odin!
There were a lot of complaints of boot loops when flashing, so I pulled the DL link. I actually stopped using miui and moved back to CM or AOKP, depending on which one is most stable at the moment. Every once in a while I give miui a try, but I never stick with it. If you want miui, I suggest you follow Lithium's thread. His version is the officially supported miui rom.
I can confirm heres what i did to fix i had the boot loop.. all i did was run DARKSIDE Superwipe x2 Times. Then i installed MIUI Rom. Then i Factory Reset. Try booting wait a little bit. If still not going threw remove battery and boot to recovery and factory reset one more time then reboot. So once again.
1. DARKSIDE SUPERWIPE x2++ 2. Install MIUI Rom. 3. Factory Reset. 4. Boot. 5. (If still looping) Remove battery Then recovery. and Factory Reset and boot again. Your welcome
Can we move this to q and a?
Sent from my XT894 using Tapatalk 2

[Q] Failed upgrade - now soft bricked

Hi all...
I tried to upgrade by Tab 2 7" to KitKat today and failed. I installed Clockworkmod successfully, but then started getting error 7's. I discovered this was because it was outdated. I've tried to install updated clockwork mod which it says has been successful - but doesn't change the original.
I did a backup of my original rom, but this has failed to reinstall. I've tried to put an old version of cyanogen on it, which also has failed, and re-downloaded the stock rom from samsfirmware which passes through ODIN, resets but then the tab 2 hangs on the Samsung screen - flashing.
I can't seem to resolve it.
Has anyone got any ideas? I can't access anything other than clockworkmod - so if you think you know of a way I can successfully upgrade it I may stand half a chance.....
Thanks
Tim
sheltont said:
Hi all...
I tried to upgrade by Tab 2 7" to KitKat today and failed. I installed Clockworkmod successfully, but then started getting error 7's. I discovered this was because it was outdated. I've tried to install updated clockwork mod which it says has been successful - but doesn't change the original.
I did a backup of my original rom, but this has failed to reinstall. I've tried to put an old version of cyanogen on it, which also has failed, and re-downloaded the stock rom from samsfirmware which passes through ODIN, resets but then the tab 2 hangs on the Samsung screen - flashing.
I can't seem to resolve it.
Has anyone got any ideas? I can't access anything other than clockworkmod - so if you think you know of a way I can successfully upgrade it I may stand half a chance.....
Thanks
Tim
Click to expand...
Click to collapse
Use Odin to restore to the stock ROM. Download the stock rom from samfirmware.com and flash it in Odin as PDA. Then, use the latest recovery (either TWRP, CWM, OR PhilZ) from @Android-Andi's recovery thread in the Dev section. You should now be able to flash any ROM you want to. Make sure you do a backup and a wipe system, cache, Dalvik, data, and android secure (if it's an option.)
Sent from my SGH-T989
thanks and....
Thanks so much, does it matter that it won't boot with the stock Roma which I've installed from sams? Will the recovery program still work?
sheltont said:
Thanks so much, does it matter that it won't boot with the stock Roma which I've installed from sams? Will the recovery program still work?
Click to expand...
Click to collapse
What do you mean? Did you flash the stock ROM in Odin?
Sent from my SGH-T989
yep
jrc2 said:
What do you mean? Did you flash the stock ROM in Odin?
Sent from my SGH-T989
Click to expand...
Click to collapse
Yes, I did twice and it's still hung after apparent success installation according to Odin. I've tried it twice.
No success
Thanks
What I've done tonight is reflashed the original Rom - this time it blew away Clockworkmod. It still wouldn't boot. I then put a recovery solution on from your link, which has flashed well. However I've then tried three ROMS and each have hung after installation on the initial boot.
I'll try them again tomorrow night - but do you have any idea why three ROMS plus the stock keep failing?
Thanks
Tim
sheltont said:
Thanks
What I've done tonight is reflashed the original Rom - this time it blew away Clockworkmod. It still wouldn't boot. I then put a recovery solution on from your link, which has flashed well. However I've then tried three ROMS and each have hung after installation on the initial boot.
I'll try them again tomorrow night - but do you have any idea why three ROMS plus the stock keep failing?
Thanks
Tim
Click to expand...
Click to collapse
Did you wipe system, cache, Dalvik cache, and data before flashing and wipe cache and dalvik after flashing? And your tablet will bootloop after a reinstallation in Odin because Odin does not wipe before installation. After flashing in Odin, reboot recovery (make sure tablet is unplugged,) and wipe data, cache, and dalvik cache. Reboot and you should be good to go.
Sent from my SGH-T989
good idea but still no success....
jrc2 said:
Did you wipe system, cache, Dalvik cache, and data before flashing and wipe cache and dalvik after flashing? And your tablet will bootloop after a reinstallation in Odin because Odin does not wipe before installation. After flashing in Odin, reboot recovery (make sure tablet is unplugged,) and wipe data, cache, and dalvik cache. Reboot and you should be good to go.
Sent from my SGH-T989
Click to expand...
Click to collapse
Hi, I've retried all that this morning-i must admit that I didn't know about wiping cache after install, however it's not made any difference, and still hangs on first boot...
Any other ideas? Thanks for all your help.
Happy success
Hi all
Thanks for all your help,especially rcj! I have managed to recover my device using cynagodmod 9 - it wont run 10 or 11 but at least its up and working - even if it's a downgrade from the Android version I was on Really don't care as I can use it again with a lot more memory.
Thanks - without you I would never have found Phils ROM which enabled me to get this far.
Tim
sheltont said:
Hi all
Thanks for all your help,especially rcj! I have managed to recover my device using cynagodmod 9 - it wont run 10 or 11 but at least its up and working - even if it's a downgrade from the Android version I was on Really don't care as I can use it again with a lot more memory.
Thanks - without you I would never have found Phils ROM which enabled me to get this far.
Tim
Click to expand...
Click to collapse
Which version of PhilZ? And I have found that TWRP 2.7.1.0 works better than other versions for KK.
Sent from my SGH-T989
Use latest Philz touch recovery. And use the rom and gapps compatible to your tab. Don't forget to reset to factory setting, clear cache and wipe dalvic cache before flashing the rom and gapps ☺
Sent from my GT-P3100 using XDA Free mobile app

Installed Cloudy G3 through TWRP, receivint system ui not responding error

Hi guys!
I got a G3 yesterday and decided to root it. I installed TWRP and decided to install Cloudy G3.
Immediately on boot, all services stop responding. There's a loop of popups saying things like "System UI has stopped responding." The same with download manager and other things. So I figured the rom didn't install properly. I went to my backup to restore it and TWRP doesn't have it listed. I looked in all directories I could (saved it initially to /sdcard/) but it's not there. The weird part is that when you click the restore button going into the list of your backups, my backup pops up for like a quarter of a second and goes away.
I decided to use TWRP's wipe function to do a system restore. It completed and now my android version is "Cloudy g3 2.5." So... System restore installed the rom? I'm just really confused at all of this. Anybody have any insight to the stuff I've mentioned?
it0ken said:
Hi guys!
I got a G3 yesterday and decided to root it. I installed TWRP and decided to install Cloudy G3.
Immediately on boot, all services stop responding. There's a loop of popups saying things like "System UI has stopped responding." The same with download manager and other things. So I figured the rom didn't install properly. I went to my backup to restore it and TWRP doesn't have it listed. I looked in all directories I could (saved it initially to /sdcard/) but it's not there. The weird part is that when you click the restore button going into the list of your backups, my backup pops up for like a quarter of a second and goes away.
I decided to use TWRP's wipe function to do a system restore. It completed and now my android version is "Cloudy g3 2.5." So... System restore installed the rom? I'm just really confused at all of this. Anybody have any insight to the stuff I've mentioned?
Click to expand...
Click to collapse
Did you use wipe before flashing the rom? If not that's Why you had the issue you didn't wipe. You MUST wipe when flashing a rom.
hyelton said:
Did you use wipe before flashing the rom? If not that's Why you had the issue you didn't wipe. You MUST wipe when flashing a rom.
Click to expand...
Click to collapse
Did not know that, and no I didn't. But I appreciate you letting me know that, probably some volatile information I should've been aware of.
May I ask why the device fixed the CloudyG3 rom when I did wipe it? I thought wiping through TWRP sends the phone back to factory settings, but it just fixed the rom and booted fine.
it0ken said:
Did not know that, and no I didn't. But I appreciate you letting me know that, probably some volatile information I should've been aware of.
May I ask why the device fixed the CloudyG3 rom when I did wipe it? I thought wiping through TWRP sends the phone back to factory settings, but it just fixed the rom and booted fine.
Click to expand...
Click to collapse
Your welcome
It wiped your current install, current rom being cloudy it reset it to factory settings. Doing a wipe won't put you back to stock.
hyelton said:
Your welcome
It wiped your current install, current rom being cloudy it reset it to factory settings. Doing a wipe won't put you back to stock.
Click to expand...
Click to collapse
Ah, so flashing the stock lg firmware would be the only way to send a device back to factory settings? I'm enjoying this learning process for sure.
it0ken said:
Ah, so flashing the stock lg firmware would be the only way to send a device back to factory settings? I'm enjoying this learning process for sure.
Click to expand...
Click to collapse
Correct

new guy thread help for fulmics g3

HI i installed fulmics rom and it did not work , now it will not allow me to install a rom because twrp says "done" almost instantly , how can i delete fulmics. I have 855 international version. THanks
stupify007 said:
HI i installed fulmics rom and it did not work , now it will not allow me to install a rom because twrp says "done" almost instantly , how can i delete fulmics. I have 855 international version. THanks
Click to expand...
Click to collapse
When you boot to TWRP, choose the "Wipe" option, on the next screen, choose "Advanced Wipe", then on the next screen, choose "system" and "data" partitions(do not choose any of the other partitions). Then slide the slider at the bottom to wipe, then tap the home button in TWRP and choose the "Install" option and flash your RIM like you normally would, then after it flashes, wipe cache and Dalvik/ART cache, after it wipes the caches, select reboot and you're done.
Sent from my SCH-I535 using Tapatalk
Didn't Work
hi, that didn't work, it says it has done but then it boots straight back up into fulmics. Any other ideas.
Droidriven said:
When you boot to TWRP, choose the "Wipe" option, on the next screen, choose "Advanced Wipe", then on the next screen, choose "system" and "data" partitions(do not choose any of the other partitions). Then slide the slider at the bottom to wipe, then tap the home button in TWRP and choose the "Install" option and flash your RIM like you normally would, then after it flashes, wipe cache and Dalvik/ART cache, after it wipes the caches, select reboot and you're done.
Sent from my SCH-I535 using Tapatalk
Click to expand...
Click to collapse
hi, that didn't work, it says it has done but then it boots straight back up into fulmics. Any other ideas.
stupify007 said:
hi, that didn't work, it says it has done but then it boots straight back up into fulmics. Any other ideas.
Click to expand...
Click to collapse
There is probably something wrong with your recovery. They flashing an older or newer version of TWRP for your model number, then try flashing a different ROM.
If your recovery was working correctly then the steps to wipe that I told you about should have wiped your system partition, if it had done that properly then you wouldn't have anything to boot to at this point if your new ROM didn't flash. Since you booted to the ROM you tried to wipe then it didn't wipe.
Also, make sure that you still have root before you flash another recovery, use the root checker app, if you don't have root, try flashing SuperSU.zip in TWRP, then try flashing the new ROM.
Droidriven said:
There is probably something wrong with your recovery. They flashing an older or newer version of TWRP for your model number, then try flashing a different ROM.
If your recovery was working correctly then the steps to wipe that I told you about should have wiped your system partition, if it had done that properly then you wouldn't have anything to boot to at this point if your new ROM didn't flash. Since you booted to the ROM you tried to wipe then it didn't wipe.
Also, make sure that you still have root before you flash another recovery, use the root checker app, if you don't have root, try flashing SuperSU.zip in TWRP, then try flashing the new ROM.
Click to expand...
Click to collapse
I never faced this issue before, I had installed roms before and was able to flash a new rom , so could the recovery really be the issue.
stupify007 said:
I never faced this issue before, I had installed roms before and was able to flash a new rom , so could the recovery really be the issue.
Click to expand...
Click to collapse
Just try another recovery and eliminate that possibility, you're not gonna cause any issues with the new recovery unless you use the wrong one.
Sent from my SCH-I535 using Tapatalk
stupify007 said:
I never faced this issue before, I had installed roms before and was able to flash a new rom , so could the recovery really be the issue.
Click to expand...
Click to collapse
Try advanced wipe including everything. then flash stock rom or any official ones. If you got qualcomm device then use QFIL or Qualcomm Flash Tool
hi i just tried that and it didn't do anything, once again it says done but it didn't do anything, I think it may be the recovery as suggested by Droidriven. I am going to try and flash a different version of TWRP or maybe clockworkmod recovery , I will keep you updated. But do you guys have any suggestions to what may have caused this, Fulmics never worked for me.
Droidriven said:
Just try another recovery and eliminate that possibility, you're not gonna cause any issues with the new recovery unless you use the wrong one.
Sent from my SCH-I535 using Tapatalk
Click to expand...
Click to collapse
[[QUOTING MY POST SO YOU CAN SEE]]
.hi i just tried that and it didn't do anything, once again it says done but it didn't do anything, I think it may be the recovery as suggested by Droidriven. I am going to try and flash a different version of TWRP or maybe clockworkmod recovery , I will keep you updated. But do you guys have any suggestions to what may have caused this, Fulmics never worked for me.
Also guys , i installed TWRP using my OS and now it doesnt work so what is the alternative, I have all pc drivers?
stupify007 said:
Also guys , i installed TWRP using my OS and now it doesnt work so what is the alternative, I have all pc drivers?
Click to expand...
Click to collapse
It sounds to me like you flashed something that was not made for your model number. Find the correct stock firmware and flash that, then start over and find something different for your device this time.
Sent from my SCH-I535 using Tapatalk
quick story. I reinstalled of the same version (2.8) and the problem is still here, I am going to try to install a different version.
Sorry to keep posting but I tried a factory reset using TWRP and it says failed. Could that mean something.
Actually guys, IT says failed underneath for everything but in the console it shows no signs of failure.
SOrry guys for being a noob, this can now be shut down as i have fixed the problem by unchecking simulate actions.
stupify007 said:
SOrry guys for being a noob, this can now be shut down as i have fixed the problem by unchecking simulate actions.
Click to expand...
Click to collapse
How in the world did that setting get changed, it should have been set to what you needed by default.
Sent from my SCH-I535 using Tapatalk

Categories

Resources