So I am able to flash dynamickat, hyperdrive, & jovy's deodex stock perfectly fine and they boot up normal and everything. However, when I try darthstalker or skyfall I get bootloops on both. They flash fine but I never make it past the boot animation. It'll be on for a few minutes and then reboot itself. I tried wiping data afterwards but nothing happens. I've downloaded the roms on different pcs, my phone, the md5 was correct, I flashed from my internal sd & external, I formatted everything (even my internal sd to see if that would help for some odd reason), I flashed a different kernel & I also odin'd back to stock and I still have no luck. I am on a t-mobile note 4 & twrp 2.8.1.1. I have no clue what to do anymore & this is becoming pretty frustrating
re: try this
xoxo_xdagirl91 said:
So I am able to flash dynamickat, hyperdrive, & jovy's deodex stock perfectly fine and they boot up normal and everything. However, when I try darthstalker or skyfall I get bootloops on both. They flash fine but I never make it past the boot animation. It'll be on for a few minutes and then reboot itself. I tried wiping data afterwards but nothing happens. I've downloaded the roms on different pcs, my phone, the md5 was correct, I flashed from my internal sd & external, I formatted everything (even my internal sd to see if that would help for some odd reason), I flashed a different kernel & I also odin'd back to stock and I still have no luck. I am on a t-mobile note 4 & twrp 2.8.1.1. I have no clue what to do anymore & this is becoming pretty frustrating
Click to expand...
Click to collapse
I have read your posts in the development thread about the issue you are having.
Give this a try
#1: Do a full wipe including Wipe System, Data, Cache, Dalvik and
last but not least to a factory reset in twrp recovery.
#2: Flash Jovy23's, stock rooted deodexed rom again.
#3: Copy Darthstalker zip file rom to your computer's desktop.
#4: Open Darthstalker zip file rom and remove/delete "boot.img"
from the zip file using winrar or winzip (or other archiver).
#5: Once "boot.img" is no longer in the Darthstalker zip file rom
copy it back to your phone's internal sdcard.
#6: Flash the Darthstalker zip file rom but do NOT wipe anything this time.
If this works for you then that means that for whatever reason your
phone has issues with the original kernel file (boot.img) which was in
the darthstalker zip file before you removed/deleted it,.
Doing it using the above step by step you will be using the kernel (boot.img)
from jov23's stock rooted rom.
If it works for you can open jovy23's stock rooted zip file rom and copy
the boot.img from it to your desktop then close the zip file.
Then open darthstalker zip file rom and copy jovy23's stock boot.img
from your desktop into darthstalker zip file rom.
The darthstalker zip file rom which has no boot.img in it since you have
already deleted and removed it.
Then copy the modified darthstalker zip file rom into your internal sdcard
over-writing the one already there.
Then if you like you can do a full wipe again and flash the modified
darthstalker zip file rom which has jovy23's kernel (boot.img) in it
and it should work fine.
Good luck!
xoxo_xdagirl91 said:
So I am able to flash dynamickat, hyperdrive, & jovy's deodex stock perfectly fine and they boot up normal and everything. However, when I try darthstalker or skyfall I get bootloops on both. They flash fine but I never make it past the boot animation. It'll be on for a few minutes and then reboot itself. I tried wiping data afterwards but nothing happens. I've downloaded the roms on different pcs, my phone, the md5 was correct, I flashed from my internal sd & external, I formatted everything (even my internal sd to see if that would help for some odd reason), I flashed a different kernel & I also odin'd back to stock and I still have no luck. I am on a t-mobile note 4 & twrp 2.8.1.1. I have no clue what to do anymore & this is becoming pretty frustrating
Click to expand...
Click to collapse
When I built the N4 rom, I was having serious qmg boot animation issues, I disabled them, and the rom booted normal, we may have a issue with the new roms and the animations. Just a thought.
re:
AxAtAx said:
When I built the N4 rom, I was having serious qmg boot animation issues, I disabled them, and the rom booted normal, we may have a issue with the new roms and the animations. Just a thought.
Click to expand...
Click to collapse
If that's the case then perhaps it might be a good idea for her to
remove all the qmg files in the system/media folder just to see
if it resolves her bootloop issues before trying anything else.
(I have not had any bootloop issues)
But then why don't all the users of the rom have the bootloop issue?
Misterjunky said:
If that's the case then perhaps it might be a good idea for her to
remove all the qmg files in the system/media folder just to see
if it resolves her bootloop issues before trying anything else.
(I have not had any bootloop issues)
But then why don't all the users of the rom have the bootloop issue?
Click to expand...
Click to collapse
Thanks for trying to help! I did what you said and flashed the stock rom but got an error when flashing darthstalker afterwards when I removed the boot.img but I still went ahead and added the boot.img from the stock rom to to the darthstalker zip and that didn't work. Still bootloops. And that's what I don't understand how it works fine on everyone else's phone and not mine I mean it's not all roms but it's still very weird and I want to know why it's happening. On another note when I do flash the stockrom, hyperdrive, & dynamickat right before it boots I get android system upgrading.. optimizing app 200 out of 200 or so, does that happen with anyone else? is that suppose to happen? does that happen on darthstalker or skyfall?
re: updating apps
xoxo_xdagirl91 said:
Thanks for trying to help! I did what you said and flashed the stock rom but got an error when flashing darthstalker afterwards when I removed the boot.img but I still went ahead and added the boot.img from the stock rom to to the darthstalker zip and that didn't work. Still bootloops. And that's what I don't understand how it works fine on everyone else's phone and not mine I mean it's not all roms but it's still very weird and I want to know why it's happening. On another note when I do flash the stockrom, hyperdrive, & dynamickat right before it boots I get android system upgrading.. optimizing app 200 out of 200 or so, does that happen with anyone else? is that suppose to happen? does that happen on darthstalker or skyfall?
Click to expand...
Click to collapse
The upgrading apps is NOT supposed to happen or appear at all unless you have NOT done a FULL
and complete wipe before flashing.
It's normal for it to upgrade a lot of apps during boot if you decided or have not done a full and
complete wipe which includes Factory Reset, Wipe System, Data, Cache and Dalvik cache.
In your case you need to do a full and complete clean flash and the only way to do that is by doing
a full and complete wipe.
If you keep seeing the "updating apps" after flashing any rom it means you have not done a full wipe.
When you have finally done a full and complete wipe before flashing you will no longer see the
phone doing the "upgrading apps" counting the number of apps to be upgraded during bootup
at all when the phone is actually wiped clean before flashing any roms.
(I am assuming that you're using twrp recovery to wipe and flash roms).
Good luck!
Misterjunky said:
The upgrading apps is NOT supposed to happen or appear at all unless you have NOT done a FULL
and complete wipe before flashing.
It's normal for it to upgrade a lot of apps if you decided or have not done a full and complete wipe
including Factory Reset, Wipe System, Data, Cache and Dalvik cache.
In your case you need to do a full and complete clean flash and the only way to do that is by doing
a full and complete wipe.
If you keep seeing the "updating apps" after flashing any rom it means you have not done a full wipe.
When you have finally done a full and complete wipe before flashing you will no longer see the
phone doing the "upgrading apps" counting the number of apps to be upgraded during bootup
at all when the phone is actually wiped clean.
Good luck!
Click to expand...
Click to collapse
I am doing a full wipe though?
Related
Hi, I have installed seeARMS ROM and followed his instuction. I have kept the JL2 modem and speedmod kernell (I was already on speedmod). I have tried 2 methods to install. The seeARMS.UGJL2.v0.4.zip with the seearms file and the CWM.
Both install went OK and I even had a congratulations screen. The problem is when the phone reboot it stays on the boot animation and get stuck there. I have tried 2 different boot animation and the same happen.
I have no problem to restore my data since I had backup but I would like to have the seearms ROM. Any idea?
Also a side question, can we get the new CK1 modem with seearms?
Richard
Have you been wiping your phone before flashing the rom? I have been having issues like you describe only when i flashed a rom w/o wiping.
(In CWM Recovery: wipe data/factory reset, wipe cache and advanced -> wipe dalvik cache)
No. I did not wipe. I am not interested in the new ROM if it mean wiping. I made a test by downloading a boot animation app. I trying 2 different boot animation and had the same result. The boot animation play with no sound but I have a vibration during boot and then nothing. Eventually it go back to the animation, vibrate and this repeat until I restore the backup.
I am wondering if tehre is something special about the Bell Canada boot animation?
Can I use the seearms without any boot animation folder?
I don't think it's a problem about the boot ani in particular.
I am not very familiar with the rom, since i have another device. In the seearms rom thread the dev mentioned two versions of the rom, one that requires wiping and one that does not.
So i guess it could be working out to flash the latter w/o wiping. But in my expirience those things rarely work out that way.
There might be incompabilities with the config data left behind by the rom installed before, or other possible issues.
Only way to be sure that those things aren't blocking anything is to wipe the phone and do a clean flash.
Personally i always do it that way. And if i like the rom, and choose to use it, it is always possible to get back all the apps and settings back with titanium backup and/or syncing them back.
But as always before wiping, if you choose to do so, please be sure to have a full nandroid backup, in case you want to go back, or something goes wrong.
I will try the wipe version
What rom were u on before seearms
Sent from my GT-I9000 using XDA Premium App
I was still on stock (froyo 2.2). Actually still on it today
You were right. The wipe version worked fine. I have now to decide to keep it or not...lol
ROM is awasome was worth well the trouble.
Glad it worked out for you - have fun with the rom
Sent from my Desire Z
Hi all,
So after I flash a new ROM (MIUI MGv2/RC8vC/MGv1) I always hang at the Galaxy S GT-I9000 screen - the first boot screen.
I am wondering what this means? is it a corrupt file, something wrong with my internal sdcard, ROM not installed properly?
Please help,
Thanks.
some times a wipe from recovery will help and goes back to normal boot
many issues may cause this problem for instance if framework.jar or android.policy.jar or... have some bugs , will happen like that
Hi,
By wipe you mean clearing the formatting system, data, cache, dalvik cache and a factory reset? I ask this because the MIUI roms are not are non-wipe and the instructions recommend you to format those places before install (which I did).
I mean wipe cache partition from recovery. just try it and ley us know if it works
Well I just tried again but it doesn't work because I can't access recovery mode. It hangs at the Galaxy S screen and doesn't move from there so I'm wondering why because if I can't fix the bad install then I can't access the recovery mode and can only flash.
if recovery dont work BUT download mode does,
start the whole process again, flash back to stock froyo with froyo bootloader.
did you come to MIUI from Gingerbread ??
Well i've done the process like 10 times, nearly every single time from froyo (JPU,JS5,Ezbase 2.0) and I also went from 2.1 to 2.2 and then to MIUI. The other times I have tried coming from CM7 as CM7 works.
well i have a similar issue but in my case i just wiped my data thru cwm on darky v8 xxjpy..
now i get boot loops,any idea what should i do??
i know this is not exactly the thread but if i get my answer it'll save me from starting a new one..
When I got bootloops i normally reflashed. If you don't have data it will probably work?
I assume you have data as your on Dark v8 when V9 is out?
i dont understand by have data??
i flashed v9.5 but went back to v 8 few months ago..
today i just wiped/factory reset my phone using cwm and it was succesful but now its bootloops and vibrations..
i never wiped my phone before and only have flashed using cwm,never used odin for flashing roms!!
OH I see, by data i meant personal data that you might want to back up...I'm not to most knowledgeable but I know how to flash roms. I reckon you should try to flash V8 it again if you can enter recovery.
I'm following this tutorial on how to root my Orange UK GT-I9305 LTE Unlocked phone running 4.1.2.
Everything goes fine with Odin the phone reboots, then I unplug and turn off my phone, and boot into recovery mode only to find it hasn't installed and Android system recovery 3e is still there.
Any ideas what I'm doing wrong?
synthecypher said:
I'm following this tutorial on how to root my Orange UK GT-I9305 LTE Unlocked phone running 4.1.2.
Everything goes fine with Odin the phone reboots, then I unplug and turn off my phone, and boot into recovery mode only to find it hasn't installed and Android system recovery 3e is still there.
Any ideas what I'm doing wrong?
Click to expand...
Click to collapse
Not flashing as instructed is the usual .Like unzipping the file or wrong file faulty file download .
Try another recovery.
jje
JJEgan said:
Not flashing as instructed is the usual .Like unzipping the file or wrong file faulty file download .
Try another recovery.
jje
Click to expand...
Click to collapse
I did follow them to the letter, does installing CWM Recovery actually root the phone or is "rooting" the phone a different process entirely that's required for installing CWM Recovery?.
:laugh:
Phone: Samsung Galaxy S3 LTE
Model Number: GT-I9305
Build Number: JZO54K.I9305XXBMF1
synthecypher said:
I did follow them to the letter, does installing CWM Recovery actually root the phone or is "rooting" the phone a different process entirely that's required for installing CWM Recovery?.
:laugh:
Phone: Samsung Galaxy S3 LTE
Model Number: GT-I9305
Build Number: JZO54K.I9305XXBMF1
Click to expand...
Click to collapse
All depends upon the package but most CWM are root and recovery .
TRYhttp://forum.xda-developers.com/showthread.php?t=2002953
Ended up using Auto-Root which seemed to work no problem.
synthecypher said:
Ended up using Auto-Root which seemed to work no problem.
Click to expand...
Click to collapse
I initially had a rooted stock ROM that i was using for ages then upgraded to a custome ROM but for personal reasons decided to go back to stock.
Loaded stock ROM with intention of rooting only to get rid of bloatware, but not one of the ODIN Flash recoveries work at all, not one, so like you ended up using CF Auto and that worked but now im still stuck with Stock Recovery. I dont understand why none of the recoveries flash when they did before.
Cheers
trouble with cwm/ twrp
Hi all. Yes I'm a noob and I wouldn't ask If hadn't tried a plethora of ways to install either cwm or twrp.
It took me a good hour to find this thread so hope I'm in the right place.
Ok I used odin to root and cwm didn't stick so still on stock rec. However I used framaroot to get super su working and titanium says I'm all rooted up. Other apps only for root also work.
I've since tried using goo manager and Rom manager to install cwm or twrp and both say unsupported.
I've searched these here threads and found a few with same problem namely when using odin cwm wont stick and android reinstalls stock recovery.
So I'm a bit stuck, I'm rooted but have no cwm or twrp.
Any help would he much appreciated.
Try Philz recovery .
I have never used a custom recovery on this phone but i think i read somewhere that when flashing by odin the thing to do is not let odin reboot the phone. untick the reboot option. then when odin is done flashing and says pass shut down the phone . dont let it boot up.once phone is off you can boot into recovery by vol up+hom+power Here is the tricky part. as soon as you see the white samsung start to load aka bootloader screen release the power button but continue to press volume up and home. you should see the circle with the hat symbol. and enter into clockworkmod once in clockwork mod you will need to wipe data cache and dalvick DO NOT WIPE SYSTEM then flash a custom rom zip that you have previously copied to either your extsdcard or sdcard0 at the same time you probably will want to flash gapps as well. the thing is if you boot up before entering recovery . the default native recovery from samsung will take its place back. maybe it is easier to just flash rom manager in the play store. flash clockworkmod and then boot into recovery from the app itself. I9300 is supported . dont know about I9305
thanks !
ashraf sharif said:
I have never used a custom recovery on this phone but i think i read somewhere that when flashing by odin the thing to do is not let odin reboot the phone. untick the reboot option. then when odin is done flashing and says pass shut down the phone . dont let it boot up.once phone is off you can boot into recovery by vol up+hom+power Here is the tricky part. as soon as you see the white samsung start to load aka bootloader screen release the power button but continue to press volume up and home. you should see the circle with the hat symbol. and enter into clockworkmod once in clockwork mod you will need to wipe data cache and dalvick DO NOT WIPE SYSTEM then flash a custom rom zip that you have previously copied to either your extsdcard or sdcard0 at the same time you probably will want to flash gapps as well. the thing is if you boot up before entering recovery . the default native recovery from samsung will take its place back. maybe it is easier to just flash rom manager in the play store. flash clockworkmod and then boot into recovery from the app itself. I9300 is supported . dont know about I9305
Click to expand...
Click to collapse
Thats exactly how I understood the cwm not sticking problem. I have tried rom manager and said not compatable with my device as did goo manager for twrp. I think odin is the only way I get it to stick. So il flash in odin and il try to get into cwm as it boots and wipe those two files you mentioned.
But then can I just boot up as normal ? or will android try to reflash its stock rom ? Damn my phone for being so difficult
I only ask because I haven't decided what CR to use yet (or even looked for any). I was gonna get it all ready first then learn how to install a CR - 1 thing at a time i thought.
Anyway thanks for your help :good:
JJEgan I found Philz thread to be helpful but something I feel Im just not ready for. Im new to this and although the updated cwm looked cool there were just to much going on, maybe for a later day.
Thanks all the same :good:
wiping data plus cache plus dalvick cache is done to prepare your phone for the custom rom that you are going to flash. the wiping is to clean those partitions because if they are not erased you will have problems. especially if you go from one android version to another or touchwiz to aosp. it is done so you get a clean install with minimal issues. if it is not done you will most likely bootloop. effectively it is a factory reset. all of your apps and app data will be gone so you do not want to do that unless you have backed up your apps . however sometimes google automatically installs them after you sign in.
I am not sure why clockwork mod does not stick but if you copy the rom you want to your phone install clockworkmod with odin and then use clockwork mod to flas the rom and gapps package then factory reset you will not have the stock recovery anymore. but this has to be done without booting into android stock . PLEASE FOLLOW THE FLASHING INSTRUCTIONS TO THE BEST OF YOUR ABILITY. AND UNDERSTAND ANYTIME YOU FLASH OR MODIFY YOUR PHONE YOU VOID YOUR WARRANTY AND POSSIBLY CAN CAUSE IRREPARABLE DAMAGE. BEST OF LUCK!
---------- Post added at 04:28 PM ---------- Previous post was at 04:24 PM ----------
Also philz recovery is highly recommended
HERE IS SOME VERY GOOD READING http://forum.xda-developers.com/showthread.php?t=2362743&highlight=philz+recovery http://forum.xda-developers.com/showthread.php?t=2344125
think I got it lol
Ok that's sounds good. However I've just read the threads you linked and now I've got to back up my imei and NV files first or il loose them when flashing. The procedure is all there and seems doable for a noob but i read some peeps are having trouble just doing that. I really wanted to root/install a CR regardless of the troubles cos I want full access and more importantly want to learn all the ins and outs so I can get the best use from my phone so glad I found this forum cause I'm sure I would have bricked my phone otherwise.
Might I ask if I've got this right tho?
1: backup imei/NV files
2: use odin to get cwm to stick using your method
3: boot into cwm to wipe data/dalvick cache and gapps
4:use cwm to flash a CR
5:factory reset
I think that's right?
CLOSE
1 BACKUP EFS FOLDER(IT CONTAINS imeiAND SERIAL NUMBER AND OTHER NETWORK SETTINGS) MAKE AT LEAST 2 BACKUPS ONE FOR EXTERNAL SDCARD AND ONE TO KEEP ON YOUR PC
2 INSTALL CWM RECOVERY USING ANY WORKING METHOD. byTHE WAY PHILZ CAN BACKUP EFS.
3 IN CWM RECOVERY MAKE A NANDROID BACKUP OF YOU CURRENT ROM. I FORGOT TO TELL YOU THAT ,THIS IS IN CASE YOUR FLASH FAILS YOU CAN RESTORE CURRENT ROM FROM BACKUP. ALWAYS BACKUP BEFORE A FLASH
4 IN CWM RECOVERY WIPE DATA, CACHE , AND DALVIK CACHE
5 IN CWM RECOVERY FLASH ZIP FOR ROM AND FLASH ZIP FOR GAPPS "GOOGLE APPS"
6 BOOT ANDROID THIS MAY TAKE UP TO 10 MINUTES FOR THE INITIAL BOOT. BE PATIENT. IF IT BOOTS YOU ARE DONE
7 IF PHONE DOES NOT BOOT THEN IN RECOVERY WIPE DATA AND CACHE AND DALVIK AGAIN
8 STILL NOT BOOTING FLASH ROM ANG GAPPS AGAIN
NOT BOOTING? RESTORE NANDROID
FACTORY RESET=WIPE DATA AND CACHE
DONT EVER WIPE SYSTEM UNLESS YOU HAVE A RECENT NANDROID. NANDROID IS GOOD BUT THE OLDER IT IS THE MORE LIKELY IT IS TO GET CORRUPTED
ALSO IF YOU GET FORCE CLOSES FIXING PERMISSIONS USUALLY WORKS FOR THAT.
SOME ROMS ARE FLASHED IN DIFFERENT WAYS .ALWAYS FOLLOW THE DEVELOPERS INSTRUCTIONS
i had the same Problem before.
I Just disassembled the battery after a full-wipe for few minutes and it works... i don't know y, but that was the only way... ?!
brilliant thanks!
ashraf sharif said:
CLOSE
1 BACKUP EFS FOLDER(IT CONTAINS imeiAND SERIAL NUMBER AND OTHER NETWORK SETTINGS) MAKE AT LEAST 2 BACKUPS ONE FOR EXTERNAL SDCARD AND ONE TO KEEP ON YOUR PC
2 INSTALL CWM RECOVERY USING ANY WORKING METHOD. byTHE WAY PHILZ CAN BACKUP EFS.
3 IN CWM RECOVERY MAKE A NANDROID BACKUP OF YOU CURRENT ROM. I FORGOT TO TELL YOU THAT ,THIS IS IN CASE YOUR FLASH FAILS YOU CAN RESTORE CURRENT ROM FROM BACKUP. ALWAYS BACKUP BEFORE A FLASH
Am I backing up to ext SD card?
4 IN CWM RECOVERY WIPE DATA, CACHE , AND DALVIK CACHE
5 IN CWM RECOVERY FLASH ZIP FOR ROM AND FLASH ZIP FOR GAPPS "GOOGLE APPS"
Are these seperate zips?
6 BOOT ANDROID THIS MAY TAKE UP TO 10 MINUTES FOR THE INITIAL BOOT. BE PATIENT. IF IT BOOTS YOU ARE DONE
7 IF PHONE DOES NOT BOOT THEN IN RECOVERY WIPE DATA AND CACHE AND DALVIK AGAIN
8 STILL NOT BOOTING FLASH ROM ANG GAPPS AGAIN
NOT BOOTING? RESTORE NANDROID
FACTORY RESET=WIPE DATA AND CACHE
DONT EVER WIPE SYSTEM UNLESS YOU HAVE A RECENT NANDROID. NANDROID IS GOOD BUT THE OLDER IT IS THE MORE LIKELY IT IS TO GET CORRUPTED
ALSO IF YOU GET FORCE CLOSES FIXING PERMISSIONS USUALLY WORKS FOR THAT.
SOME ROMS ARE FLASHED IN DIFFERENT WAYS .ALWAYS FOLLOW THE DEVELOPERS INSTRUCTIONS
Click to expand...
Click to collapse
Thank-you for all that,I really appreciate it.
Can I ask the difference between the apps nandroid manager and titanium? I've backed up with both and wondered if i really needed to? The nandroid backup was nearly 3gb!
Also I was gona backup with qpst for imei and NV files but then read its only for US versions? Will the backup of efs folder include those?
honestly i really dont know what the differences are. l do not use custom recoveries or custom roms. i dont use titanium backup .Any rom I flash i get from sammobile.com. one reason i do not use custom roms is that none can support mhl. I use a monitor and bluetooth mouse and keyboard . without mhl I cant mirror my screen so i always stay with stock roms. i use Xposed framework for modifications.
ashraf sharif said:
I have never used a custom recovery on this phone but i think i read somewhere that when flashing by odin the thing to do is not let odin reboot the phone......
Click to expand...
Click to collapse
thx you so much. this was the secound s3 that had this issue. deactivating auto reboot did the job!!!!
So I've been attempting to install a rom, ANY rom on my phone and the results always seem to be the same. I boot into TWRP, wipe then install the rom. On reboot, the phone loads up the initial (black) samsung screen. Then buzzes twice and reboots. It will do this infinitely. It happens with any rom I've tried flashing. It has to be something I am missing or doing wrong. Does anyone have an idea what it is? I've even gone as far as completely wiping, odin in a stock image and then adding TWRP again. I just can't seem to figure it out.
re: bootloops
Tharkys said:
So I've been attempting to install a rom, ANY rom on my phone and the results always seem to be the same. I boot into TWRP, wipe then install the rom. On reboot, the phone loads up the initial (black) samsung screen. Then buzzes twice and reboots. It will do this infinitely. It happens with any rom I've tried flashing. It has to be something I am missing or doing wrong. Does anyone have an idea what it is? I've even gone as far as completely wiping, odin in a stock image and then adding TWRP again. I just can't seem to figure it out.
Click to expand...
Click to collapse
You need to ODIN flash the stock original official COG2
firmware & odin flash cf-autoroot and the twrp recovery
before flashing the zip file rom.
Once that's done you can flash any N910T zip file rom in
twrp recovery without any issues.
Make sure to do a full wipe in twrp before you flash any
zip file rom to avoid bootloops and or getting stuck on
the samsung boot logo screen and be sure to do a full
and complete wipe which includes:
"System, Data, Cache, Dalvik Cache and last but not
least do a factory reset.
Good luck,
Have a great day!
Tharkys said:
So I've been attempting to install a rom, ANY rom on my phone and the results always seem to be the same. I boot into TWRP, wipe then install the rom. On reboot, the phone loads up the initial (black) samsung screen. Then buzzes twice and reboots. It will do this infinitely. It happens with any rom I've tried flashing. It has to be something I am missing or doing wrong. Does anyone have an idea what it is? I've even gone as far as completely wiping, odin in a stock image and then adding TWRP again. I just can't seem to figure it out.
Click to expand...
Click to collapse
i dont know if we are having the same problem but try installing the original firmware via odin and see if that works. if it does not then we have the same problem and i dont know how to fix it, now i am stuck with my S4 wait for help from someone to help me fix my note 4
I'm on twrp 2.8.7, using rapture rom 5.1.1 great but I wanted to fix my dpi settings so I installed the xposed apk and flashed the wanam zip as instructed here.
http://forum.xda-developers.com/showpost.php?p=63028102&postcount=3826
Now the weird part is sometimes it will boot but I have to take out the battery let it sit for a few min and it will boot. It will bootloop but sometimes I can get it to boot to recovery twrp. Then I'll flash rapture rom or try my backup but the same thing happens. I've wiped cache/davlik/system/data a few times.
Tried flash xposed recovery disable zip but it says it can't find anything to disable.
jedisurfer said:
I'm on twrp 2.8.7, using rapture rom 5.1.1 great but I wanted to fix my dpi settings so I installed the xposed apk and flashed the wanam zip as instructed here.
http://forum.xda-developers.com/showpost.php?p=63028102&postcount=3826
Now the weird part is sometimes it will boot but I have to take out the battery let it sit for a few min and it will boot. It will bootloop but sometimes I can get it to boot to recovery twrp. Then I'll flash rapture rom or try my backup but the same thing happens. I've wiped cache/davlik/system/data a few times.
Tried flash xposed recovery disable zip but it says it can't find anything to disable.
Click to expand...
Click to collapse
I would start over. Backup! Everything. Wipe internal, external, cache, dalvik, everything.
Odin stock firmware. The entire thing, not just base and bootloader.
Then odin recovery, root. Wipe again. Everything. Flash rom. Win.
ctrlaltdeln said:
I would start over. Backup! Everything. Wipe internal, external, cache, dalvik, everything.
Odin stock firmware. The entire thing, not just base and bootloader.
Then odin recovery, root. Wipe again. Everything. Flash rom. Win.
Click to expand...
Click to collapse
It's been so long I've had to flash it via the computer but every time I plug the usb cable to my charger or to a computer the phone starts rebooting. How can I get to adb to flash the recovery again? I can get to download mode but I'm not sure my computer actually "sees" my phone.
Most likely a bad download. Did you check md5 to make sure it was good? Try over with a clean download.