Related
Hi all,
I purchased the Rom Manager, and flashed the new clockworkmod recovery, but like this I cannot acces my older nand backups.
I have a few, older backups, and maybe i will need them ! What can I do?
thx
legycsapo said:
Hi all,
I purchased the Rom Manager, and flashed the new clockworkmod recovery, but like this I cannot acces my older nand backups.
I have a few, older backups, and maybe i will need them ! What can I do?
thx
Click to expand...
Click to collapse
If you made your older backups with AmonRA recovery you won't be able to use them in CWM recovery. You will have to flash AmonRA to use them. That is pretty simple, thanks to ciaox who shared flashable recovery zips here.
borrow thread awhile,
just now i root my phone using gingerbreak 1.2
after root,then download rom manager free version from market
then i choose flash clockwork Mod recovery,and choose lg optimus one as my device
and wait it to load finish the bar
after finish,it shows this :
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
so now what should i do ??
XeactorZ said:
borrow thread awhile,
just now i root my phone using gingerbreak 1.2
after root,then download rom manager free version from market
then i choose flash clockwork Mod recovery,and choose lg optimus one as my device
and wait it to load finish the bar
after finish,it shows this :
so now what should i do ??
Click to expand...
Click to collapse
Are you sure you granted ROM Manager superuser privileges?
22VIN said:
Are you sure you granted ROM Manager superuser privileges?
Click to expand...
Click to collapse
just now don't have
so i root my phone again,and its work already
but after i flash clockworkMod recovery,and reboot into recovery
then i use the guide that u last time teach me at my thread
22VIN said:
1. root your phone
2. install a custom recovery (the easiest way is to install ROM Manager from Market and select "flash cwm recovery"
3. download a custom kernel (I'm using franco's) and copy it on your sdcard
4. boot into custom recovery: turn off your phone and then press vol down + home + power and release at lg logo
5. make a nand backup
6. wipe dalvik cache (in cwm recovery it's in advanced menu)
7. select install zip from sdcard, select your kernel from the sdcard and flash it.
8. start your phone and install setcpu; use max 729mhz
That's it
Click to expand...
Click to collapse
so after finish flash franco kernel
i choose reboot,then my phone stuck at LG logo
i wait very long,then unplug the battery and put it back
and turn on phone as usual,same also stuck at there
i do it a lot times
so i give up,and do a Nand restore,but its also stuck at LG logo ==
then the only way is i go emergency mode and use kdz updater to flash back
luckily my phone no problem
so now got other way to flash custom recovery instead using rom manager ??
because i google it quite a lot people also got the same case as me,stuck at LG logo after reboot ~
XeactorZ said:
so after finish flash franco kernel
i choose reboot,then my phone stuck at LG logo
i wait very long,then unplug the battery and put it back
and turn on phone as usual,same also stuck at there
i do it a lot times
so i give up,and do a Nand restore,but its also stuck at LG logo ==
then the only way is i go emergency mode and use kdz updater to flash back
luckily my phone no problem
so now got other way to flash custom recovery instead using rom manager ??
because i google it quite a lot people also got the same case as me,stuck at LG logo after reboot ~
Click to expand...
Click to collapse
Well I also got stuck at lg logo on some occasions when flashing kernels/themes, it happens. But I can't understand why you got stuck after restoring backup.
When did you make your backup? Did you make a backup before flashing stuff on your ROM?
And what do you mean by "got stuck"? Sometimes it takes longer to boot after you flash something. How much did you wait to consider that your phone is stuck?
To install a custom recovery the classic way check out step 3 here.
By the way, your problems aren't related to the recovery's installation. You're saying you rebooted into recovery, so the instalation of CWM with ROMmanager was succesful.
22VIN said:
Well I also got stuck at lg logo on some occasions when flashing kernels/themes, it happens. But I can't understand why you got stuck after restoring backup.
When did you make your backup? Did you make a backup before flashing stuff on your ROM?
And what do you mean by "got stuck"? Sometimes it takes longer to boot after you flash something. How much did you wait to consider that your phone is stuck?
To install a custom recovery the classic way check out step 3 here.
By the way, your problems aren't related to the recovery's installation. You're saying you rebooted into recovery, so the instalation of CWM with ROMmanager was succesful.
Click to expand...
Click to collapse
i also duno why after i restore from the nand backup that i do yesterday night still stuck at LG logo
the backup i make at yesterday night,which before flashing franco kernel
yes i got a backup before flashing franco kernel,and i no flash any ROM coz i wan use stock rom
erm,my phone stuck at LG logo more than 10minutes already,its too long than normal
i know sometime will take longer time,but sure won't over 10minute
so now i gonna try another method to flash custom recovery
thanks for ur link ~
(Sorry if you guys don't like me using the term soft brick :S)
Phone version: Samsung Galaxy S II I9100
Problem: Rooted phone using [galaxys2root's method] (Odin + Jeboo Kernel + Clockworkmod) and then installed CyanogenMod using [WiredMash's method] (sorry can't post youtube links)
Followed the procedure and everything was working perfectly. Afterwards, I messed a few settings up so I thought it would be easy to simply do the process above again to start with a clean slate.
I don't particularly remember the order in which I messed things up, but I went back to Clockworkmod, cleared literally everything (including the internal SD, meaning I lost CyanogenMod) and then went back to Odin and tried to flash Jeboo Kernal on again.
Current Status of Phone:
Stuck at the Loading Screen with the Yellow Exclamation Mark.
Downloading mode states I've done Binary Flash 8 times (woops)
CyanogenMod no longer initiates.
Still able to access CWM, but can't flash any Zips on because there's nothing on the memory
What should I do? Would this simply be fixed by popping down to the store to grab a MicroSD and going on my computer, putting CyanogenMod on it and then flashing it using CWM?
If it works, would I have screwed up anything? Would I have to clear some stuff using CWM? Would it be like nothing happened? (I have a weird obsession that requires everything to be perfect)
Ok....it's not *really* a brick....it's not even a bootloop.....it's (as you said) a lack of os.
You have an accessible CWM, which basically puts you in the clear.
You suggested your solution.....buying a microSD card, copying a rom to it and using cwm to flash it.
I basically was in the same situation as you, and if I'd had a microSD card that my laptop recognised, that is the solution I'd have used. My issue was that my XP laptop doesn't like high capacity memory cards (mine is 32Gb)....if you are running XP, it might be a good idea to get a (maximum) 4Gb card.
The above method will also require you to flash GApps as well......
Sent from my rooted, de bloated, stock JB powered S2 via PhilZ kernel and XDA developers app
No need to buy an external sd-card. Your phone has an internal storage which can be accessed / mounted via CWM. Just boot the phone in recovery mode (ClockworkMod) and head over to 'mounts and storage > mount USB storage'. Now use your cable to connect your device to your computer. It should only take a few seconds until your phone pops up in Windows Explorer. Then you're able to put your ROM .zip file onto the card. Choose to 'unmount USB storage' and install the ROM. Don't forget to wipe before Much luck,
experience7
Dude...you learn something new every day.....if I'd have known that when I had my issue (similar to the OP) I wouldn't have had to f**t around with odin installing a firmware in order to get at least *something* back on my phone to get it to boot again.....thanks for the share....gonna have to remember this tip
Sent from my rooted, de bloated, stock JB powered S2 via PhilZ kernel and XDA developers app
No, always go stock.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from...this is not even my S2
Why should he go to stock if he desires his phone to run a custom ROM? Sounds like he accidentally formatted the system partition plus the internal storage. As soon as he flashes the CM zip file his phone has a working system directory and he should be able to. boot it up again
I was trolling keith.
Sent from...this is not even my S2
I guess the only reason for your inappropriate posts is to push your post count to its limit. Well done, sir.
That's so funny, why would anyone do that?
I want you to tell me, you got 2 min to make something up.
Be creative.
Sent from...this is not even my S2
Off-topic, 'nuff said. Now stop it please
Thought so
Be good now.
Sent from...this is not even my S2
experience7 said:
No need to buy an external sd-card. Your phone has an internal storage which can be accessed / mounted via CWM. Just boot the phone in recovery mode (ClockworkMod) and head over to 'mounts and storage > mount USB storage'. Now use your cable to connect your device to your computer. It should only take a few seconds until your phone pops up in Windows Explorer. Then you're able to put your ROM .zip file onto the card. Choose to 'unmount USB storage' and install the ROM. Don't forget to wipe before Much luck,
experience7
Click to expand...
Click to collapse
So I''ve done the USB storage method, shoving CyanogenMod, SuperSU and GApps onto the internal. I installed SuperSU and now I'm trying to install CyanogenMod and I'm getting the (Status 7, Installation Aborted) message. Am I missing anything required?
Re download the ROM, the files might be corrupted.
Sent from...this is not even my S2
No need to copy over SuperSU. There's a superuser app coming with CM Alternatives are in Google Play Store
Well, you're running Jeboo kernel. Stock based kernels sometimes cause errors when you try to install a custom ROM. Don't get me wrong, CM comes with its own kernel anyways, but there's still the chance that the installation fails like in your case. To solve your problem flash a custom kernel (I'd choose dorimanx - you can grab a copy here: dorimanx.shine.sk <- 8.x is for stock based ROMs, 9.x is for custom ROMs) So pick 9.35 and flash it. Then reboot the phone in recovery mode again. You've got a different Recovery system now. This time it will allow you to install CM followed by GApps
Edit: Don't forget that Dorimanx will be overwritten by CM kernel as soon as you flash CM. But if you're new to CM I recommend this kernel anyways
experience7 said:
No need to copy over SuperSU. There's a superuser app coming with CM Alternatives are in Google Play Store
Well, you're running Jeboo kernel. Stock based kernels sometimes cause errors when you try to install a custom ROM. Don't get me wrong, CM comes with its own kernel anyways, but there's still the chance that the installation fails like in your case. To solve your problem flash a custom kernel (I'd choose dorimanx - you can grab a copy here: dorimanx.shine.sk <- 8.x is for stock based ROMs, 9.x is for custom ROMs) So pick 9.35 and flash it. Then reboot the phone in recovery mode again. You've got a different Recovery system now. This time it will allow you to install CM followed by GApps
Edit: Don't forget that Dorimanx will be overwritten by CM kernel as soon as you flash CM. But if you're new to CM I recommend this kernel anyways
Click to expand...
Click to collapse
Hmm I seem to be getting the Status 7, Installation aborted problem with Dorimanx too :S I even tried 9.34 and redownloading 9.35
EDIT: Managed to get back to CyanogenMod. Thank you
Nice one mate. ...now if you want to go back to stock there's a handy little app called Mobile Odin. ...look for the thread here on XDA......
Sent from my rooted, de bloated, stock JB powered S2 via PhilZ kernel and XDA developers app
I am having issues flashing my phone with Odin, Odin says it is starting to write Nand but it just stays like that for a minute or so then it says it failed to write Nand. I have tried Odin 3.07 and 3.09 but get the same error each time. My phone is a UK model (from Amazon UK GT-I9205ZKABTU). I am attempting to flash Kitkat BTU, not sure what versions I was on before!.
To cut a long story short a while back I attempted to root it, I flashed CWM with Odin, this seemed to flash fine so and I rooted. The phone never didn't appear to be fully rooted as I could root apps that required root access but apps like Skygo said the phone was rooted!. The other night I was on my phone and it crashed, when I went to power it back on it would only boot as far as the white writing that states model number then it would switch itself off, when I connected the charger the phone would display the battery image but didn't appear to charge and I also could get into recovery. I them attempted to re-flash custom recovery, flashed but now the phone says something like software update failed and I cannot access recovery but I can access download mode.
A couple of questions if I may;
1. Would I get the Nand Write fail error if I am flashing the incorrect firmware for the phone?
2. Would I get the Nand Write fail error if the charger port is not working as it should?
3. Where is the best place to download stock roms?, even if I get an older version I don't mind.
Any ideas guys?
newgen2005 said:
-cut-
A couple of questions if I may;
1. Would I get the Nand Write fail error if I am flashing the incorrect firmware for the phone?
2. Would I get the Nand Write fail error if the charger port is not working as it should?
3. Where is the best place to download stock roms?, even if I get an older version I don't mind.
Any ideas guys?
Click to expand...
Click to collapse
1. Yes - you have to choose firmware for your model of phone
2. Yes - try to change USB cable (for original) and use USB port on the back of your PC (from Main Board). No hubs between phone and PC.
3. HERE or HERE
In such state the best way is to flash by Odin stock firmware for your model. Then with functionality restored you can try once more to install custom ROM.
Thanks for your help trurl3, I will try again when I get home.
I have tried on another PC and I getting the same nand write error. I am searching for stock firmware but I am not sure if my phone is LTE!, when I go into download mode is says the product name is GT-I9205. I am trying to flash this I9205XXUDOA1_I9205BTUDOA1_I9205XXUDOA1_HOME.tar.md5, is this the correct firmware?. I purchased the phone from Amazon.co.uk direct (sim free). Is it possible I may have a none GT-I9205?
Even tried Kies, I put in model and serial number, Kies is happy, Kies downloads the relevant firmware 100% but fails then comes up with an error message!. The only issue I can think of with Kies is that I am unable to get the phone in recovery, only download mode!, phone also won't connect to Kies!
Hmmm... let's try to install custom recovery for beginning... I recommend to try Philz touch recovery. HERE is tutorial for instalation. If it succeed you will have first outpost for further moves. Although tutorial is meant for Galaxy S4 and (no offence) dummies, installation is the same for all Samsung phones. Only IMPORTANT DIFFERENCE is version of recovery file - it should be meant for Mega which code name is 'meliuslte" so you have to download CWM recovery file from HERE. You will need to download newest file with .tar extension.
Thanks for your help, very much appreciated. I will look at installing custom recovery tonight, will custom recovery still install even if the phone firmware is corrupt/incomplete?.
Yes it should. Only reflashing full stock firmware reverts all custom changes. Of course it depends of character of corruption. Recovery it is one of partitions of Android's file system. If get corrupted then will not work.
Official firmware contains whole sytem and flashing stock firmware you replace all Android's partitions in your phone so you have to use 'download mode' and Odin on PC to flash, because recovery is delted and reinstated during upgrade. Flashing custom ROM's replace not all partiions ( i.e not replace bootloader or recovery). For that you can install custom ROM's from custom recovery, but not stock recovery as them have not all needed functions. Having custom recovery is a must for modding your phone . Using custom recovery you can root it and then install custom ROM.
As we talk about custom ROM I can recommend for you very good custom ROM bult on base stosk TWRP from @megalomanic14. You can find information from link in my sig. There is MegaFire on baze Android 4.2 and MegaKat on baze 4.4. Both ROMs are prerooted already.
trurl3 said:
Yes it should. Only reflashing full stock firmware reverts all custom changes. Of course it depends of character of corruption. Recovery it is one of partitions of Android's file system. If get corrupted then will not work.
Official firmware contains whole sytem and flashing stock firmware you replace all Android's partitions in your phone so you have to use 'download mode' and Odin on PC to flash, because recovery is delted and reinstated during upgrade. Flashing custom ROM's replace not all partiions ( i.e not replace bootloader or recovery). For that you can install custom ROM's from custom recovery, but not stock recovery as them have not all needed functions. Having custom recovery is a must for modding your phone . Using custom recovery you can root it and then install custom ROM.
As we talk about custom ROM I can recommend for you very good custom ROM bult on base stosk TWRP from @megalomanic14. You can find information from link in my sig. There is MegaFire on baze Android 4.2 and MegaKat on baze 4.4. Both ROMs are prerooted already.
Click to expand...
Click to collapse
Hopefully the custom recovery will flash without any errors, I will post back tonight with the outcome.
I also have a Galaxy Note running a custom rom. I installed that last year through custom recovery that I flashed. For some reason the Note seems to be more root and custom recovery friendly .
Once I have custom recovery on the Mega I will be happy, I will have a little confidence that my Mega is not completely broken.
I hope so. I had not any problem with flashing custom ROMs on my Mega. Yesterday flashed CM12.1 to the test how it looks Lollipop on Mega . But wasn't satisfyied... so went back to my 4.2 with MegaFire. Although there is new 4.4 for Mega I am not eager to upgrade...
trurl3 said:
I hope so. I had not any problem with flashing custom ROMs on my Mega. Yesterday flashed CM12.1 to the test how it looks Lollipop on Mega . But wasn't satisfyied... so went back to my 4.2 with MegaFire. Although there is new 4.4 for Mega I am not eager to upgrade...
Click to expand...
Click to collapse
I am hoping to get my Mega up and running again so I can check out how a custom rom works on it. I love the phone but the internal storage is a nightmare. Ideally I want to be able to at least root and be able to install apps to SD and remove some of stock Samsung stuff. I am always getting low on storage warnings, really annoying when I got a 64gb SD card in the phone!
IMHO the best for Mega is to install MegaFire ROM from @megalomanic14. This custom rom is unbranded, prerooted and heavily improved by developer. There is too version X which is debloated from most unnecessary aps.
Not having much luck, now Odin doesn't even attempt to write anything as it is stuck at "initialization". I tried it on 3 different computers, it seems to being doing this since Kies was used last night!. Reinstalled usb drivers etc .Any ideas?
I have tried an older of Odin (3.06) and I get this when trying the custom recovery and stock rom!
PHP:
<ID:0/006> Added!!
<ID:0/006> Odin v.3 engine (ID:6)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Get PIT for mapping..
<ID:0/006> There is no PIT partition.
<OSM> All threads completed. (succeed 0 / failed 1)
Is this a connection issue or am I really lacking the pit partition and do I need to include a GT-I9205 pit file with the stock firmware or custom recovery I am flashing?. I have done a little research regarding the pit file but I am a little confused on what I need to do, I don't want to mess things up even more!. If I need to include a pit file can I just download one someone else has created?.
Thanks
I downloaded a pit file and tried to flash it with stock rom and custom recovery but it didn't work.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I am sorry, it's above me... i can not help you any more. Unfortunately it looks like hardware issue, byt maybe I'm wrong... hopefully...
Thanks for all your help. I a real shame it won't flash!
please re install your usb driver samsung.
and make sure debugging enable before install
use another odin. 1.85 or 3.09
right click odin, run as administrator
Hi, so i need some help regarding an issue i'm currently facing ( and have been facing for about a month now).
I'll give you the full story of my device and what i did:
First, when i got the phone. First thing i did was unlock bootloader and install custom recovery + rom (sultanXDA rom)
Then, when the android 7.1 ROMs started coming out, i installed one of those, worked great.
After a while i got bored, and decided to actually try the stock ROM, so i used a tool which took the phone back to 100% stock.
After this, i wanted to install a custom recovery so i could root and install xposed, i unlocked bootloader and tried installing THIS recovery.
It seems to install just fine via fastboot, but when try to go into the recovery, it tries to boot into it, then it just boots into the system instead. And after this, i have no recovery at all. I tried going back to stock again (which also got me the recovery back). But once again, when i try to install the recovery it doesnt work.
Anyone got any idea why this is?
Any help would be appreciated
Shpped said:
Hi, so i need some help regarding an issue i'm currently facing ( and have been facing for about a month now).
I'll give you the full story of my device and what i did:
First, when i got the phone. First thing i did was unlock bootloader and install custom recovery + rom (sultanXDA rom)
Then, when the android 7.1 ROMs started coming out, i installed one of those, worked great.
After a while i got bored, and decided to actually try the stock ROM, so i used a tool which took the phone back to 100% stock.
After this, i wanted to install a custom recovery so i could root and install xposed, i unlocked bootloader and tried installing THIS recovery.
It seems to install just fine via fastboot, but when try to go into the recovery, it tries to boot into it, then it just boots into the system instead. And after this, i have no recovery at all. I tried going back to stock again (which also got me the recovery back). But once again, when i try to install the recovery it doesnt work.
Anyone got any idea why this is?
Any help would be appreciated
Click to expand...
Click to collapse
That recovery is only for Oxygen OS 3.1.3 and ROMs based on it.
I take it you flashed Oxygen OS 2.x that's why it didn't boot.
Joshwin Aranha said:
That recovery is only for Oxygen OS 3.1.3 and ROMs based on it.
I take it you flashed Oxygen OS 2.x that's why it didn't boot.
Click to expand...
Click to collapse
Thanks for your reply
Unfortunately (see image below) i am on OOS 3.X
EDIT: sorry about the large image, i dont know how to make it smaller
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Don't think anything wrong with that recovery but you could also try Sultans twrp or blu sparks V41 twrp.
Exodusche said:
Don't think anything wrong with that recovery but you could also try Sultans twrp or blu sparks V41 twrp.
Click to expand...
Click to collapse
I tried different Recoveries too, (i know i tried both Sultan and Blu Spark's Recoveries). I tried all i could find on Android Development page.
The issue does seem very weird, i dont know where i messed up in the process. It seems like when i try to install the new recovery, it does replace the old one but never boots.
Shpped said:
I tried different Recoveries too, (i know i tried both Sultan and Blu Spark's Recoveries). I tried all i could find on Android Development page.
The issue does seem very weird, i dont know where i messed up in the process. It seems like when i try to install the new recovery, it does replace the old one but never boots.
Click to expand...
Click to collapse
What recovery did you use to install 3.1.3? I think it has to be old stock recovery from 2.X.X or won't work. When I used the new stock recovery from 3.x.x had issues myself.
Exodusche said:
What recovery did you use to install 3.1.3? I think it has to be old stock recovery from 2.X.X or won't work. When I used the new stock recovery from 3.x.x had issues myself.
Click to expand...
Click to collapse
Thanks for your reply
I used the stock rom to install 3.1.3 from 2.x.x (don't remember exactly which version i was on). Anyways, the issue right now is the fact that i cannot install any custom recoveries.
Shpped said:
Thanks for your reply
I used the stock rom to install 3.1.3 from 2.x.x (don't remember exactly which version i was on). Anyways, the issue right now is the fact that i cannot install any custom recoveries.
Click to expand...
Click to collapse
What it tells after flashing in fastboot?
cva_kabil said:
What it tells after flashing in fastboot?
Click to expand...
Click to collapse
Hi, this is what it shows me on install. After installing when i try to go into the recovery it stays on the oneplus logo :/
Okay so this is weird.
After installing adb drivers on my work pc (im currently at work) and flashing, it for some reason works!
Thanks for all the help guys
For anyone facing the same issue: Try using a different pc with different adb and fastboot drivers, dont know why it worked for me, but it did!
Shpped said:
Okay so this is weird.
After installing adb drivers on my work pc (im currently at work) and flashing, it for some reason works!
Thanks for all the help guys
For anyone facing the same issue: Try using a different pc with different adb and fastboot drivers, dont know why it worked for me, but it did!
Click to expand...
Click to collapse
Glad it worked
So I've successfully rooted my phone (S6 Edge G925F) using CF-Auto-Root and I've been using it for the past few days. Looking to install a custom ROM, but I can't get TWRP to work without getting "recovery is not seandroid enforcing". If I try to use it through the app, I get a bootloop. If I do it with SkipSoft Android Toolkit, it boots fine but I can't get into the recovery menu. Same error as above.
I feel like I'm missing something really simple here... But I can't quite put my finger on it. I feel like it has something to do with unlocking the bootloader, but I can't seem to find any guides on it. The one I did find had a dead link to a download, and 20+ minutes of searching for a replacement left me with nothing.
Losing my mind here...
ProdigyThirteen said:
So I've successfully rooted my phone (S6 Edge G925F) using CF-Auto-Root and I've been using it for the past few days. Looking to install a custom ROM, but I can't get TWRP to work without getting "recovery is not seandroid enforcing". If I try to use it through the app, I get a bootloop. If I do it with SkipSoft Android Toolkit, it boots fine but I can't get into the recovery menu. Same error as above.
I feel like I'm missing something really simple here... But I can't quite put my finger on it. I feel like it has something to do with unlocking the bootloader, but I can't seem to find any guides on it. The one I did find had a dead link to a download, and 20+ minutes of searching for a replacement left me with nothing.
Losing my mind here...
Click to expand...
Click to collapse
The "recovery is not seandroid enforcing" message can be just ignored.
There are 2 easy ways to get twrp to work.
Flash twrp through odin in AP.
https://dl.twrp.me/zerolte/
You need the .img.tar
Or
Download flashify
https://play.google.com/store/apps/details?id=com.cgollner.flashify
From flashify it gives you the option to download and flash twrp directly from the app.
callumbr1 said:
The "recovery is not seandroid enforcing" message can be just ignored.
Click to expand...
Click to collapse
Can't exactly ignore it, it's all I get when booting into the recovery menu after installing twrp.
ProdigyThirteen said:
Can't exactly ignore it, it's all I get when booting into the recovery menu after installing twrp.
Click to expand...
Click to collapse
Can the phone boot up?
Can you boot to recovery?
Flash a permissive kernel and the message will dissapear.. You can flash custom roms from flashify or flash fire also
callumbr1 said:
Can the phone boot up?
Can you boot to recovery?
Flash a permissive kernel and the message will dissapear.. You can flash custom roms from flashify or flash fire also
Click to expand...
Click to collapse
It boots into android, but not the recovery menu.
If I install through the twrp app, it won't even boot to android, it just gets stuck in a bootloop
ProdigyThirteen said:
It boots into android, but not the recovery menu.
If I install through the twrp app, it won't even boot to android, it just gets stuck in a bootloop
Click to expand...
Click to collapse
Try to install twrp through flashify!
callumbr1 said:
Try to install twrp through flashify!
Click to expand...
Click to collapse
I am, but I'm getting some error while trying to download it
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
ProdigyThirteen said:
I am, but I'm getting some error while trying to download it
Click to expand...
Click to collapse
What error?
callumbr1 said:
What error?
Click to expand...
Click to collapse
Added screenshot
I get the error on WiFi and 4g
ProdigyThirteen said:
Added screenshot
I get the error on WiFi and 4g
Click to expand...
Click to collapse
I cant see the screen shot? I would suggest start from scratch. Do a full wipe/ stock flash.
Flash twrp first then cf auto root.
Aaaand now I feel like a complete moron. Went to unroot my phone through SuperSU, it finished doing its thing, I rebooted my phone, and now I'm stuck in a bootloop. Every damn link I find to a stock ROM has a pathetic download speed, so I'm now having to wait 6 hours for something that may or may not work. Beginning to regret rooting my phone.
ProdigyThirteen said:
Aaaand now I feel like a complete moron. Went to unroot my phone through SuperSU, it finished doing its thing, I rebooted my phone, and now I'm stuck in a bootloop. Every damn link I find to a stock ROM has a pathetic download speed, so I'm now having to wait 6 hours for something that may or may not work. Beginning to regret rooting my phone.
Click to expand...
Click to collapse
Aslong as you have the correct stock firmware it should work. And if it works save the firmware somewhere safe. Then if you ever mess up again just needs a re flash.
Flashed stock ROM, phone working again. Tried to flash TWRP, but still getting recovery is not seandroid enforcing and nothing else.
ProdigyThirteen said:
Flashed stock ROM, phone working again. Tried to flash TWRP, but still getting recovery is not seandroid enforcing and nothing else.
Click to expand...
Click to collapse
Try to root first, then flash twrp. My note 4 did the same the other day after flashing stock ROM mm update. So I did full wipe, flashed cf auto root then twrp. Works fine