Hi there,
I had been umming and arring about rooting and installing a new ROM one of my familys HTC Heroes for some time now and finally after reading lots of "How to's" on lots of different forums I decided to take the plunge and give it a go using the guide on here.
Both my wifes phone and my sons phone are sim unlocked Orange HTC Heros running 2.1-Update 1.
Rooting it was easy. One press of a button and I was there. Its pretty much worked OK and I have sucessfully made three backups of the wifes Hero.
My main query and this is the bit I have not really been able to find much info about despite spending a day trawling through the forums looking for similar queries is this:
Having flashed my recovery image file, the first time I reboot I can get into the recovery mode just fine. From here I can make a backup of the current ROM after which the Hero reboots and goes back into the OS as it should.
If I then shut it down and reboot using the HOME key + POWER option It does not go into the recovery mode. I get the screen with an image of the phone next to a red triangle with an exclamation mark in it.
Using the advice from various forums whilst searching for further advice / hints I have left the phone for up to half an hour but it stays on this screen. The only way to get it out of this screen it to pull the battery.
If I then boot up the phone and reflash the recovery image, I can then get into the recovery mode once again but for ONE BOOT ONLY.
I have tried AmonRA Revcovery v1.7.01. and also the Clockwork Recovery 2.5.0.7 images and both produce the same results. I have tried flashing the images via ROM Manager and also via Android Terminal Emulator
My question is this: Do I have to flash the recovery image EVERY time I want to open the recovery mode or is there something I have missed? At present I have held back from installing a new ROM in case I go past a point of no return where I brick the phone. Neither my wife or son would be too pleased despite my son wanting a better ROM on his.
Apologies for writing "War and Peace" but I wanted to make sure I had covered all I could and hope this is a) not a query already posted elswhere which I have missed b)posted in the right place. Apologies to any forum mods if its not.
Regards
Rhinestone.
hmm look on the unlokr.com or something like that. They use some simple passes and it's the way i did it. the on;y difference is that my phone wasn't blocked on a carrier...
1.there is a program that roots the hero's rom
2.after that i recommend installing clockwork recovery mode (it doesn't need signed zips)
3.if you don't feel safe doing this, i recommend to stop... I know that the 2.1 rom is boring but you can end up with a bricked phone after this...
The official 2.1 update has a script that reflashes the stock recovery every time the phone is shut down.
Hunt about for a modified 2.1 rom, all of them have had that script removed. I'm not a huge fan of sense now, but when I did use it, I found villainrom to be a good 2.1 sense rom.
TheReverend210 said:
The official 2.1 update has a script that reflashes the stock recovery every time the phone is shut down.
Hunt about for a modified 2.1 rom, all of them have had that script removed. I'm not a huge fan of sense now, but when I did use it, I found villainrom to be a good 2.1 sense rom.
Click to expand...
Click to collapse
This, just flash a custom ROM and it will stick.
Hello,
Problem might be with rooting, possible it has not been rooted completely or anything messed up. You can try this for rooting.
http://unrevoked.com/
If you are sure its rooted completely, then check out Superuser apps, if its there, and you are rooted, if not then download terminal emulator and type "su" command, if its doesnt display any error then its rooted.
Other then this,
problem might be with the recovery images you are flashing, download droid explorer its a window application, its has an option of flashing recovery with one click, simply choose recovery image & flash it, clockmod recovery or amonr any of this you can get in xda.
Ok, i realize i have a different phone from this thread but it is close and my problems closely reflect the issues ive seen with the Galaxy S.
A little background. Im no perfect i know what im doing when it comes to rooting. I have an HTC Tbolt and rooted many of those, an older touch pro 2, and this is first time doing a samsung. I am getting the hang of ODIN (i wish everyone would just use this program instead of bouncing back and forth between heimdall and ODIn but whatever) Im liking ODIN cause it works well. I was successful at flashing a new rom into this Samsung phone. 95% of it worked, wifi i think didnt but everything else worked. While trying to fix the phones wifi somehow i have stopped the phone from booting into CMW recovery unless forced or booting into a rom. I can get into CMW but i must hold down the Vol Down button to get there, otherwise a clean basic boot takes me to the stock android system recovery screen and will not boot a rom.
I have something backwards or out of order. I am just trying to get the rom to identify the installed CMW and the installed ROM through CMW but it wont do it.
Any help would be appreciated, i dont want my GF to find out i jacked her phone lol
Which phone do you have? SGS? I can just talk about SGS+ but I guess its similiar.
Try to install CWM with Odin, normally it should replace the stock recovery (haven't heard of both running at once).
Once you have installed CWM you can install your custom ROM with CWM (look at the install instructions).
If you want to install stock ROM with Odin it will replace your CWM with stock Recovery.
Post the link of the thread/recovery you want to flash.
annqx said:
Which phone do you have? SGS? I can just talk about SGS+ but I guess its similiar.
Try to install CWM with Odin, normally it should replace the stock recovery (haven't heard of both running at once).
Once you have installed CWM you can install your custom ROM with CWM (look at the install instructions).
If you want to install stock ROM with Odin it will replace your CWM with stock Recovery.
Post the link of the thread/recovery you want to flash.
Click to expand...
Click to collapse
Its a stratosphere. Im using the root and / or stock files in the root method. I use ODIN to flash the StratCWMRecovery.tar.md5 and if i tick "reboot" then it reboots into CWM i install a rom or stock rom and it finishes. I reboot the phone and it instantly goes back to android system recovery. If you like ill make a short video to give you an idea of whats going on.
I will note that im close to making a jig but its not 100% bricked obviously. 3 button method still works (and unecessary at this point since all the phone does is go straight into the stock bootloader) and then after i install CWM i can force it in to CWM but it wont actualy boot into it.
From a programing standpoint i feel the pointers or partitions are incorrect. Its like booting a computer that has a hard drive with windows installed however getting the bios to tell it to boot from the hard drive isnt working. THats the easiest way to explain this.
One thing i want to note is the only errors i am getting are when i try to partition the SD card from CWM. I get an error saying sdparted is not found.
I am not getting a full understanding of how the root system works on this phone.
Again any help is appreciated.
Made a short video. Its uploading now. http://www.youtube.com/watch?v=tFZ5Adm5AdQ
So whatever i did i was able to fix. I think me being a very visual person and normally having access to all files i need or could use in a situation is always nice. Here, i didnt but i found them. Here's the link. Its obviously for stratosphere but i took about 10 minutes and let ODIN install all these files and it worked.
original posting but the link doesnt work for download
http://rootzwiki.com/topic/11183-eh2-full-factory-odin-restore/
where i downloaded it
http://www.fileswap.com/dl/t4D235pUTO/SCH-I405.EH2_rel.md5.html
Again this is for stratosphere. Since it really helped me return to stock and allow me to re root in about 15 minutes this thread should be moved but there is no stratosphere area
Greetings everyone,
So will not try to type out a book here, but want to try to include all the info/everything I have done do this point. I recently purchased a Galaxy S4 ( SGH-I337) ATT model. My end goal was to have it rooted with CM 11 installed on it. This is only the second phone I have attempted to root ( First was Atrix HD which went overall fine). I'm basing my end goal off of it, in that I am wanting to have it rooted with CM 11 installed. I started off by downloading Odin and used towel and was able to get the phone rooted. That seemed to have gone without too many problems. I tried to do as much reading as I could, but I'm sure I either misread or overlooked where I went wrong next. I then installed TWRP in the hopes of getting CM 11 installed. This is where the problems start. After installing TWRP ( later reading I saw I probably should have used Philz soft touch??) and restarting my phone it would only go into " Download Mode" and would forever just sit there. I did some searching and saw how to get past this simply by just restarting and holding the volume up and selecting now that I did not want to enter into Download mode. At this point I decided to go download the stock ROM and start over. I downloaded and followed the instructions from
Greetings everyone,
So will not try to type out a book here, but want to try to include all the info/everything I have done do this point. I recently purchased a Galaxy S4 ( SGH-I337) ATT model. My end goal was to have it rooted with CM 11 installed on it. This is only the second phone I have attempted to root ( First was Atrix HD which went overall fine). I'm basing my end goal off of it, in that I am wanting to have it rooted with CM 11 installed. I started off by downloading Odin and used towel and was able to get the phone rooted. That seemed to have gone without too many problems. I tried to do as much reading as I could, but I'm sure I either misread or overlooked where I went wrong next. I then installed TWRP in the hopes of getting CM 11 installed. This is where the problems start. After installing TWRP ( later reading I saw I probably should have used Philz soft touch??) and restarting my phone it would only go into " Download Mode" and would forever just sit there. I did some searching and saw how to get past this simply by just restarting and holding the volume up and selecting now that I did not want to enter into Download mode. At this point I decided to go download the stock ROM and start over. I downloaded and followed the instructions from
androidrootz.com/2014/03/how-to-unrootunbrick-at-galaxy-s4-sgh.html . From that point is where things went to hell in a hand-basket. My phone will load but whenever I try to turn on Wifi to try to re-root I get a Security Information message saying that it has blocked Wifi from turning on. Quick Google search says this is built in security "Knox"? that is causing this. Posts say that I have the wrong firmware for this phone? The bigger problem seems to be that now when I try to boot into recovery, I get a background that says "No Command" and red lettering at the top that says " Android system recovery <3e>. I have options to reboot system now, update from ADB and others. At the bottom it says #Manual Mode# Successfully applied multi-CSC. So somehow I think i have corrupted the boot loader. Of course Odin will not recognize the phone in this state to try to push any kind of firmware or boot-loader to it. At this point I truley am clueless and lost. Not at all above saying I'm above my head and need some guidence or help from someone who knows a lot more about this then I do. I really thought I had read and done plenty of research before I tried this, but non the less I have a phone I can't get into recovery and once booted, I can't get wifi to work. Thanks for your time and insight. From that point is where things went to hell in a hand-basket. My phone will load but whenever I try to turn on Wifi to try to re-root I get a Security Information message saying that it has blocked Wifi from turning on. Quick Google search says this is built in security "Knox"? that is causing this. Posts say that I have the wrong firmware for this phone? The bigger problem seems to be that now when I try to boot into recovery, I get a background that says "No Command" and red lettering at the top that says " Android system recovery <3e>. I have options to reboot system now, update from ADB and others. At the bottom it says #Manual Mode# Successfully applied multi-CSC. So somehow I think i have corrupted the boot loader. Of course Odin will not recognize the phone in this state to try to push any kind of firmware or boot-loader to it. At this point I truley am clueless and lost. Not at all above saying I'm above my head and need some guidence or help from someone who knows a lot more about this then I do. I really thought I had read and done plenty of research before I tried this, but non the less I have a phone I can't get into recovery and once booted, I can't get wifi to work. Thanks for your time and insight.
Tl,dr sure looks like a book to me. If you just got an s4 I'm sure the bootloader can't be exploited and you can't use cm. Look through this http://forum.xda-developers.com/showthread.php?p=53758227
Sent from my Nexus 9 using XDA Free mobile app
jd1639 said:
Tl,dr sure looks like a book to me. If you just got an s4 I'm sure the bootloader can't be exploited and you can't use cm. Look through this http://forum.xda-developers.com/showthread.php?p=53758227
Sent from my Nexus 9 using XDA Free mobile app
Click to expand...
Click to collapse
Thanks for the link. Very helpful info. Problem I can't seem to get around is that since any ROM i download will not pass the signature inside the recovery mode, I don't know how to get to where I can flash any kind of ROM to it. Yes sorry for the book, I just see too often people don't ever post enough info on what they have or what they have done. In essence how do i use Odin if i can't get into download mode and recovery mode will not accept any file cause it says it fails the md5 signature? Thanks for the help
bryantjb said:
Thanks for the link. Very helpful info. Problem I can't seem to get around is that since any ROM i download will not pass the signature inside the recovery mode, I don't know how to get to where I can flash any kind of ROM to it. Yes sorry for the book, I just see too often people don't ever post enough info on what they have or what they have done. In essence how do i use Odin if i can't get into download mode and recovery mode will not accept any file cause it says it fails the md5 signature? Thanks for the help
Click to expand...
Click to collapse
I don't want to give you useless information, but make sure you're using the right steps to get into download mode.
1) Power off your device
2) Remove battery for 10 seconds
3) Replace battery
4) Hold POWER + HOME + VOLUME DOWN until you see the "Warning" Screen
5) Quickly hit the VOLUME UP button.
Then you can connect to ODIN, and go from there.
Hello there,
I am having a little bit of an issue with a new Galaxy Note 4 that i got for my wife. We both bought our devices yesterday, mine from Three, and hers from EE (we are in the UK), both SM-N910F, so i proceeded to root my device and it worked all great. So earlier today i started the exact same procedure, unfortunately, my wifes Note 4 got stuck in a Recovery Boot Loop, and i genuinely don't understand what is happening.
As for the rooting method, i went with the [SM-N910*] CF-Auto-Root and choose the right .tar file, or else it wouldn't of had worked on the first device.
I have read quite a few posts, saw a few videos on youtube, but it far beyond me. I have seen a few people mention that i need to download the German (?) version of the Stock firmware, and then flash it. I seem to have found a link for it on SamMobile but it's gonna take 5 hours to finish, and i don't understand why i would download the German Stock firmware, is that the correct one for her device ?
At this point, is there any way around it ? Why did my device which is the same work perfectly, but not hers ?
I would appreciate any and all help, if you could make it quite detailed for me i would appreciate it even more.
Thank you!
Hi @Vaskie!
Can you enter in download mode?
Hello there @_mone, the following has happened since i posted:
Went ahead and flashed the following: N910FXXU1BOB4_N910FOXA1BOB4_N910FXXU1BOB4_HOME.tar and it made the device reach the home screen, from there i attempted to root using the same method which worked, but it ended installing a few extra applications, which i don't understand how. I also don't understand how flashing a new stock rom didn't make me start the device from the beginning, it already had all my information and went straight to the home screen ready to use. I feel quite confused if im honest.
On the other hand, most things seem to be working perfect, but i am having some issues with the front camera. I have two Note 4s, both bought yesterday from the same place, but one was flashed with the Stock rom (N910FXXU1BOB4_N910FOXA1BOB4_N910FXXU1BOB4_HOME.ta r) due to being stuck in a boot loop. The front camera seems to be massively over exposed compared to the other Note 4, not just a little bit either, making it almost unusable.
Would anyone be able to help ?
Vaskie said:
I also don't understand how flashing a new stock rom didn't make me start the device from the beginning, it already had all my information and went straight to the home screen ready to use. I feel quite confused if im honest.
Click to expand...
Click to collapse
That's because you "dirty" flashed a new ROM on top of the old one.. it was like an "update".
What I suggest you (because you already rooted your phone and your knox is 0x1) is to flash TeamWin Recovery Project from ODIN and then flash a TW ROM from the Galaxy Note 4 Android Development (Snapdragon) page
To do so download "twrp-2.8.7.0-trltexx.img.tar" from here, put your phone in download mode, connect it to the pc via usb, from the pc launch odin, let it recognize your phone, add the downloaded .img.tar file on the pda button, click on the "start" button and let it flash the recovery.
Now download a TW ROM like _alexndr's DevBase from here and this modem and this bootloader.
Then put the downloaded ROM (N910FXXU1POF2_DevBase_alexndr.zip) in your external SDcard. Reboot your phone in recovery mode. From TWRP go Wipe/AdwancedWipe/ and tick DalickCache, System, Data, Internal Storage, Cache and "Swipe to Wipe". After go back to the first page, hit "Install" search "N910FXXU1POF2_DevBase_alexndr.zip" in "/external_sd" and install it. Wipe Dalvick and Cache again and reboot into download mode. Again connect your phone to the PC and launch ODIN now put the downloaded modem "CP_N910FXXU1POF1.tar.md5" in the CP button and the bootloader "BL_N910FXXU1POF2.tar.md5" in the BL button and click on the "start".
Once it is done switch off and on your phone and start again with the latest samsung rom for N910F already with root, busy box and all the fixes by _alexndr
And let us know if you still have problems.
Thank you very, very much for the very well detailed reply @_mone
I will attempt to go ahead with your explanation tomorrow. Would that somehow fix the camera, and i guess the other question is.. is the front camera issue that i explained myself above to do with me "dirty flashing" ?
Is there anything inherently wrong with "dirty flashing" ?
Thank you yet again!
Nothing wrong with dirty flashing.. but sometimes doing so you can create conflicts between old and new rom or leaving "bugs" from the old to the new generating problems in your new os that may wont be there if you performed a clean install. :good:
Hi all, new to Android and Samsung, so sorry for the noob question.. and sorry if its been answered before, Ive done a HEAP of reading and Im still confused...
I recently bought an S4 GT-I9505, thinking that getting into Android and maybe tweaking it a bit would be fun..
This phone was a Warranty replacement for a Telstra "POST Paid" service and has been sitting in a cupboard for a few years, It is NOT network locked. The phone had never been used before I bought it but has since ran out of warranty,,
I can't remember what ver of Android was on the phone when I got it but Its now updated to 5.0.1 and ofcourse has KNOX.. I obviously dont care about KNOX Warranty tripping to 0x1 as its ran out anyway...
My question is though....
Every guide or thread I read about installing custom ROMs and such says "phone must have an UNLOCKED bootloader" ... So how do I "UNLOCK" the bootloader or is this something that happens when flashing a custom ROM? ... What am I missing here guys?
Thanks in advance
kingsdene
Only few devices have a locked bootloader.
Verizon and AT&T devices have a locked bootloaders.
If you're device is none of the above then you're good to go.
GDReaper said:
Only few devices have a locked bootloader.
Verizon and AT&T devices have a locked bootloaders.
If you're device is none of the above then you're good to go.
Click to expand...
Click to collapse
Hi thanks for your reply,,
That clrears things up a bit,,
I read somewhere that the international versions weren't locked.. and in another thread I read they said the I9505 is international but on that same thread someone else said that it wasn't international, only the i9500 was,, so that confused me a little...
but on wikipedia the I9505 and I9506 are listed as international.... so if thats the case I definitely should be right hey???
Also because Im from AUS and not much is listed in terms of Australian Service providers.. would it be worth me trying to contact Telstra because its a Telstra "POST Paid" phone and asking if there would be any restrictions on it???
kingsdene said:
Hi thanks for your reply,,
That clrears things up a bit,,
I read somewhere that the international versions weren't locked.. and in another thread I read they said the I9505 is international but on that same thread someone else said that it wasn't international, only the i9500 was,, so that confused me a little...
but on wikipedia the I9505 and I9506 are listed as international.... so if thats the case I definitely should be right hey???
Also because Im from AUS and not much is listed in terms of Australian Service providers.. would it be worth me trying to contact Telstra because its a Telstra "POST Paid" phone and asking if there would be any restrictions on it???
Click to expand...
Click to collapse
It might at worst have a network/carrier lock on it, but that would be it, no other locks.
See here for info/fees: https://whirlpool.net.au/wiki/phone_unlocking
I believe post paid phones are unlocked from the word go, but you may want to check...easiest way is to grab a sim from a family member/friend on another carrier and put it in and see if it registers on the network...prolly quicker than waiting on the phone to telstra...only to be told its not locked .
Here you go, more info:
http://www.acma.gov.au/theACMA/engage-blogs/engage-blogs/Telco/The-key-to-unlocking-your-mobile
Me im in Aus too, i bought my S5 i9505, a former Telstra S4, a few days back knowing it was unlocked fortunately....took it home and rooted it, debloated it and living happily on the stock 5.01 TouchWiz ROM with TWRP Recovery and Xposed , ill prolly chuck a custom one on at some point....
stylemessiah said:
It might at worst have a network/carrier lock on it, but that would be it, no other locks.
I believe post paid phones are unlocked from the word go, but you may want to check...easiest way is to grab a sim from a family member/friend on another carrier and put it in and see if it registers on the network...prolly quicker than waiting on the phone to telstra...only to be told its not locked .
Me im in Aus too, i bought my S5 i9505, a former Telstra S4, a few days back knowing it was unlocked fortunately....took it home and rooted it, debloated it and living happily on the stock 5.01 TouchWiz ROM with TWRP Recovery and Xposed , ill prolly chuck a custom one on at some point....
Click to expand...
Click to collapse
Hi mate, Thanks very much for the reply/info
Thats really good to know.. Looks like Im all set then,, I knew it wasn't networked locked, I tested with an Optus sim..
Would you mind sharing your process on how you rooted it and installed TWRP? Did you use apps or flash from Odin/Heimdal etc,, I know theres heaps of guides and different ways of doing so.... Im just curious on different peoples experiences
Oh and just thaught id let you know I noticed in your sig you've listed you device as S4 I9095
kingsdene said:
Hi mate, Thanks very much for the reply/info
Thats really good to know.. Looks like Im all set then,, I knew it wasn't networked locked, I tested with an Optus sim..
Would you mind sharing your process on how you rooted it and installed TWRP? Did you use apps or flash from Odin/Heimdal etc,, I know theres heaps of guides and different ways of doing so.... Im just curious on different peoples experiences
Oh and just thaught id let you know I noticed in your sig you've listed you device as S4 I9095
Click to expand...
Click to collapse
Nice pickup on the sig
Im the king of typos...i have a wonky brain, and it doesnt always connect my hand with the right keys Sig corrected
Heres what i did on mine, and how i remember doing it, though if some steps dont match up, let me know via PM or email, in my profile:
Required utils/files (assuming you have a standard i9505):
Odin: http://dl.sammobile.com/Odin3-v3.11.1.zip
CF Auto Root: https://download.chainfire.eu/316/CF-Root/CF-Auto-Root/CF-Auto-Root-jflte-jfltexx-gti9505.zip
TWRP: https://dl.twrp.me/jfltexx/twrp-3.0.2-0-jfltexx.img.tar.html
1) Rooting
a) Put phone into download mode - Power + Home + Vol Down, then Vol Up
b) Connect to PC via cable
c) Run Odin
d) Tick next AP
e) Press AP and browse to locate and select the CF Auto file downloaded
f) Press Start
g) It should upload to phone and phone should reboot into recovery and do its thing and then reboot
h) Unplug the phone form the cable
i) You may get, i did, a Google Play update to update SuperSU. I did this and rebooted, you may also get a prompt to update the su binary, do this using the Normal method, and reboot
2) TWRP
a) Put phone into download mode - Power + Home + Vol Down, then Vol Up
b) Connect to PC
c) Run Odin
d) Tick next AP
e) Press AP and browse to locate and select the TWRP file downloaded
f) Click options, and untick Auto Reboot - if you dont manage to catch the device using the recovery boot keys as it reboots, it may boot normally and over-write the recovery, and you'll have flash it again, so i turned this off
f) Press Start
g) When its uploaded, unplug phone,and hold down Power + Home + Vol Up until it reboots and you see the recovery boot text appear in the top left (lines of blue, yellow, red text), let go at this point, a
the device should boot to recovery and install recovery
h) Unplug the phone form the cable
i) Power down the phone (i got a cache mounting issue - discovered when i was flashing Xposed, that you may need to fix...best to do it anyways, and do it now to fix the issue before you try and flash a custom ROM in the future etc)
j) Boot to recovery again - Power + Home + Vol Up until it reboots and you see the recovery boot text appear in the top left, let go at this point, the device should boot to recovery
k) Go into Mount and see if Cache is mounted, if it is, youre fine, if it isnt, try mounting it by ticking Cache. If it wont mount:
i) Click Wipe,
ii) Click Advanced Wipe
iii) Tick Cache
iiii) Click Repair or Change File System
iv) Click Change Filesystem
v) Click Ext4
vi) Swipe to change
It may take some time to fix....
l)Reboot when done
3) Debloating (highly recommended on the stock ROM)
Theres a few pages on which apps and files to remove using a root uninstaller app, or you can Install this and tick the items you want removed: https://play.google.com/store/apps/details?id=com.adamioan.s4lollipopdebloater&hl=en
Please dont ask me what to tick or leave ticked Theres descriptions in the app, or more info on the forums. Personally i tend to decimate ROM's from all non-essential apps, but what works for me may not work for you, you may use things i dont.
When done, reboot
Optional though recommended: Boot into recovery and wipe your dalvik & cache (note: once Dalvik is wiped your next reboot will be long due to app optimising - it will be shorter than normal with less apps though)
Hope this helps
stylemessiah said:
Nice pickup on the sig
Im the king of typos...i have a wonky brain, and it doesnt always connect my hand with the right keys Sig corrected
Heres what i did on mine, and how i remember doing it, though if some steps dont match up, let me know via PM or email, in my profile:
1) Rooting
a) Put phone into download mode - Power + Home + Vol Down, then Vol Up
b) Connect to PC via cable
c) Run Odin
d) Tick next AP
e) Press AP and browse to locate and select the CF Auto file downloaded
f) Press Start
g) It should upload to phone and phone should reboot into recovery and do its thing and then reboot
h) Unplug the phone form the cable
i) You may get, i did, a Google Play update to update SuperSU. I did this and rebooted, you may also get a prompt to update the su binary, do this using the Normal method, and reboot
2) TWRP
a) Put phone into download mode - Power + Home + Vol Down, then Vol Up
b) Connect to PC
c) Run Odin
d) Tick next AP
e) Press AP and browse to locate and select the TWRP file downloaded
f) Click options, and untick Auto Reboot - if you dont manage to catch the device using the recovery boot keys as it reboots, it may boot normally and over-write the recovery, and you'll have flash it again, so i turned this off
f) Press Start
g) When its uploaded, unplug phone,and hold down Power + Home + Vol Up until it reboots and you see the recovery boot text appear in the top left (lines of blue, yellow, red text), let go at this point, a
the device should boot to recovery and install recovery
h) Unplug the phone form the cable
i) Power down the phone (i got a cache mounting issue - discovered when i was flashing Xposed, that you may need to fix...best to do it anyways, and do it now to fix the issue before you try and flash a custom ROM in the future etc)
j) Boot to recovery again - Power + Home + Vol Up until it reboots and you see the recovery boot text appear in the top left, let go at this point, the device should boot to recovery
k) Go into Mount and see if Cache is mounted, if it is, youre fine, if it isnt, try mounting it by ticking Cache. If it wont mount:
i) Click Wipe,
ii) Click Advanced Wipe
iii) Tick Cache
iiii) Click Repair or Change File System
iv) Click Change Filesystem
v) Click Ext4
vi) Swipe to change
It may take some time to fix....
l)Reboot when done
3) Debloating (highly recommended on the stock ROM)
Theres a few pages on which apps and files to remove using a root uninstaller app, or you can Install this and tick the items you want removed: https://play.google.com/store/apps/details?id=com.adamioan.s4lollipopdebloater&hl=en
Please dont ask me what to tick or leave ticked Theres descriptions in the app, or more info on the forums. Personally i tend to decimate ROM's from all non-essential apps, but what works for me may not work for you, you may use things i dont.
When done, reboot
Optional though recommended: Boot into recovery and wipe your dalvik & cache (note: once Dalvik is wiped your next reboot will be long due to app optimising - it will be shorter than normal with less apps though)
Hope this helps
Click to expand...
Click to collapse
Haha your not the only one with a wonky brain bro.....
And WOW wasn't expecting all that... Thanks very much man, your a legend.
I really appreciate your help
Ill give it a crack and see how I go..
Cheers mate
stylemessiah said:
Heres what i did on mine, and how i remember doing it
Click to expand...
Click to collapse
Hi mate,, just thaught I'd let you know I followed your guide and all was sucsessful, thanks again, I had it running for a while and I really like the stock ROM when unbloated.
Since then I've flashed a Resurrection Remix Marshmallow ROM -ver 5.6.7 and its running well except for a few glitches but nothing serious.
I have a question for you though, if you dont mind... I am planning on getting the latest RR ROM and upgrading to that to see how it runs...
But if I were to downgrade to a Lollipop version of RR, would I be ok flashing it from my current state? I have read somewhere that flashing to an earlier version of Android (Marshmallow to Lollipop) is a bit of a different process?
And also if this were true.... Than when I made a TWRP Backup of my rooted stock 5.0.1 Lollipop before I flashed RR 6.0.1 Marshmallow.. If I were to try now to restore from my backup it wouldn't work? because of the different Android versions?
I have done heaps of reading and can't seem to find a great deal on this... only when it comes to stock ROMs
Cheers
kingsdene
kingsdene said:
Hi mate,, just thaught I'd let you know I followed your guide and all was sucsessful, thanks again, I had it running for a while and I really like the stock ROM when unbloated.
Since then I've flashed a Resurrection Remix Marshmallow ROM -ver 5.6.7 and its running well except for a few glitches but nothing serious.
I have a question for you though, if you dont mind... I am planning on getting the latest RR ROM and upgrading to that to see how it runs...
But if I were to downgrade to a Lollipop version of RR, would I be ok flashing it from my current state? I have read somewhere that flashing to an earlier version of Android (Marshmallow to Lollipop) is a bit of a different process?
And also if this were true.... Than when I made a TWRP Backup of my rooted stock 5.0.1 Lollipop before I flashed RR 6.0.1 Marshmallow.. If I were to try now to restore from my backup it wouldn't work? because of the different Android versions?
I have done heaps of reading and can't seem to find a great deal on this... only when it comes to stock ROMs
Cheers
kingsdene
Click to expand...
Click to collapse
Im glad that my wonky memories of rooting/twrp and debloating worked out for you. The stock 5.01 ROM is great without the bloat. Ive since moved onto Optimised CM13, which is going well.
Im afraid i cant help you on downgrading from LP to MM, as ive never done it on this device, but i cant see how that would in any way be an issue as you have a custom recovery installed...afaik thats all thats needed...at least on the S2 it was as easy as flash what the hell you want to on it as long as you had at least a KK recovery installed..
Cant help on backups, as i literally never use them, i never carry over stuff from one ROM to the next, i clean install everything
kingsdene said:
Hi mate,, just thaught I'd let you know I followed your guide and all was sucsessful, thanks again, I had it running for a while and I really like the stock ROM when unbloated.
Since then I've flashed a Resurrection Remix Marshmallow ROM -ver 5.6.7 and its running well except for a few glitches but nothing serious.
I have a question for you though, if you dont mind... I am planning on getting the latest RR ROM and upgrading to that to see how it runs...
But if I were to downgrade to a Lollipop version of RR, would I be ok flashing it from my current state? I have read somewhere that flashing to an earlier version of Android (Marshmallow to Lollipop) is a bit of a different process?
And also if this were true.... Than when I made a TWRP Backup of my rooted stock 5.0.1 Lollipop before I flashed RR 6.0.1 Marshmallow.. If I were to try now to restore from my backup it wouldn't work? because of the different Android versions?
I have done heaps of reading and can't seem to find a great deal on this... only when it comes to stock ROMs
Cheers
kingsdene
Click to expand...
Click to collapse
The downgrading is only a problem on stock to stock ROMs. Any combination of custom to stock should work.
And TWRP has a problem with TouchWiz ROM backups. So your backup might not work either.
I mean, it will work, but you get errors.