Related
First off, let me explain what's happening. Just by my post title you are probably thinking, use the search button. I have and will, but my situation might be a little different.
I had unlocked my phone, rooted it and installed cwm in the past. A friend of mine came over this past weekend and offered to install a custom rom on my Atrix as he did with his and he would show me what to do to update it, restore, or try different roms later. Well I had to leave for a hour and while I was gone he messed something up. He had then essentially returned my phone to stock. It's no longer rooted and when I start my phone it no longer says unlocked. Do I need to go through the unlock process again or can I just root and install cwm? Can anyone tell me where I should start?
Sent from my MB860 using xda premium
JohnnyDanger said:
First off, let me explain what's happening. Just by my post title you are probably thinking, use the search button. I have and will, but my situation might be a little different.
I had unlocked my phone, rooted it and installed cwm in the past. A friend of mine came over this past weekend and offered to install a custom rom on my Atrix as he did with his and he would show me what to do to update it, restore, or try different roms later. Well I had to leave for a hour and while I was gone he messed something up. He had then essentially returned my phone to stock. It's no longer rooted and when I start my phone it no longer says unlocked. Do I need to go through the unlock process again or can I just root and install cwm? Can anyone tell me where I should start?
Sent from my MB860 using xda premium
Click to expand...
Click to collapse
Have to flash pudding again. Then install cwm and play from there. Most ROMs here are pre-rooted, so no need to root anything.
Thank you. That's what I will do.
Sent from my MB860 using xda premium
So here is what happened. I made a backup of a stock atrix firmware and copied the backup to my atrix on deodexed 2.3.4. I tried to install the backup but it stops somewhere along the line and says error formatting data.
now the phone wont connect to the computer. when i opened rsdlite however it shows that the device is connected.the phone bootloops and I cant copy anything to the phone cause i cant connect to the phone except through rsd sorry if i posted in the wrong section cause this is the only one i can post in. and i searched for solutions but no one has this same problem. PLEASE HELP
then if you CAN use rsd lite place phone in rds lite mode then use "stock sdk from motorola and flash it back i went all the way ro 1.26 then over rhe air updated to 1.83
but i also continued on to unlocked bootloader and flashed gigerbread build (alien ) after installing cwm
im also on usa at&t fyi
ltdanno360 said:
then if you CAN use rsd lite place phone in rds lite mode then use "stock sdk from motorola and flash it back i went all the way ro 1.26 then over rhe air updated to 1.83
but i also continued on to unlocked bootloader and flashed gigerbread build (alien ) after installing cwm
im also on usa at&t fyi
Click to expand...
Click to collapse
I tried to flash the official 2.3.4 found here http://forum.xda-developers.com/showthread.php?t=1181932 but now i just have a locked bl. and it still bootloops. Can you give me little more detailed instructions on what you did. I'm not too experienced.
Morpheaous said:
I tried to flash the official 2.3.4 found here http://forum.xda-developers.com/showthread.php?t=1181932 but now i just have a locked bl. and it still bootloops. Can you give me little more detailed instructions on what you did. I'm not too experienced.
Click to expand...
Click to collapse
Did u do factory reset after the flash
Sent from my MB860 using xda premium
My atrix wont even boot to the RSD etc selection screen
So i had my phone rooted and wanted to unlock the bootloader so i followed the steps from pudding but it did not work. everyone has a NS version of the phone in RSD Lite but mine was SE not sure why. So i tried a few times to flash the new image and clear everything out to no avail. now i don't even get to the menu that gives me 5 seconds to select what method i want to use to fix it.
all i get is a flash of this on the screen before it goes black again
SVF:105:1:2
Failed to boot 0x1000
(stays for a second)
Entering NWFlash Recovery Mode
(Flashes under the other text but really fast before the screen goes blank)
windows wont even recognize that its plugged in. but what else is odd is that while plugged in it seems to be charging as the green notification light stays on.
any help would be great. thank you
voidlogik said:
Failed to boot 0x1000
Click to expand...
Click to collapse
isnt that a hard brick? it's over.
sanriver12 said:
isnt that a hard brick? it's over.
Click to expand...
Click to collapse
really?? no way to unbrick it?
Morpheaous said:
I tried to flash the official 2.3.4 found here http://forum.xda-developers.com/showthread.php?t=1181932 but now i just have a locked bl. and it still bootloops. Can you give me little more detailed instructions on what you did. I'm not too experienced.
Click to expand...
Click to collapse
Bootloops means soft bricks which is not really a problem. When your phone Boots up, press the down key along worth the power button. Then keep pressing down button until you see Android Recovery. Do a factory reset or flash another room once in there.
Sent from my MB860 using XDA App
voidlogik said:
really?? no way to unbrick it?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1165154
voidlogik said:
really?? no way to unbrick it?
Click to expand...
Click to collapse
Sounds like a hard brick indeed. At this moment in time hard bricks are incurable but some people said that taking their battery out and putting it back into their phones solved their problem. You might want to give it a shot.
A guy also claimed thay its possible to unhardbrick your phone using the jtag technique. You might want to read up on it.
Sent from my MB860 using XDA App
aIf it says failed to boot x1 its real bad but i got a failed to boot x2 and got it fixed but x1 tragic
Sent from my MB860 using xda premium
ltdanno360 said:
aIf it says failed to boot x1 its real bad but i got a failed to boot x2 and got it fixed but x1 tragic
Sent from my MB860 using xda premium
Click to expand...
Click to collapse
English plz.
Sent from my MB860 using Tapatalk
me too
There's soo many forums and different avenues to go down! after about 9 hours trying various things to make my atrix (running normal 2.3.4 rooted with no other cm7 or rom or any other mod) i am left with my atrix at the boot screen OR if i leave it to boot it just makes the logging on noises then shows the white screen, then nothing.
I stupidly followed the list to freeze using bloatfreezer. Not the updated list where it reads next to HOME (make sure you have another launcher) so i have frozen 'home' and i am stuck.
i cannot do a recovery because it has that fail message x2 everytime i do the power volume - and + on the android recov.
I am completely lost. i do not understand what hard/soft/adw/ push email/ or other jargon means. If you have any solutions i'd be more than grateful.
I hope i haven't bricked my phone, cos a 2year contract and no new phone is gonna push me near that ledge lol
atrixuk said:
There's soo many forums and different avenues to go down! after about 9 hours trying various things to make my atrix (running normal 2.3.4 rooted with no other cm7 or rom or any other mod) i am left with my atrix at the boot screen OR if i leave it to boot it just makes the logging on noises then shows the white screen, then nothing.
I stupidly followed the list to freeze using bloatfreezer. Not the updated list where it reads next to HOME (make sure you have another launcher) so i have frozen 'home' and i am stuck.
i cannot do a recovery because it has that fail message x2 everytime i do the power volume - and + on the android recov.
I am completely lost. i do not understand what hard/soft/adw/ push email/ or other jargon means. If you have any solutions i'd be more than grateful.
I hope i haven't bricked my phone, cos a 2year contract and no new phone is gonna push me near that ledge lol
Click to expand...
Click to collapse
I'd recommend starting a new thread w/ your issue. It's more likely to be seen and answered by someone who could help.
atrixuk said:
There's soo many forums and different avenues to go down! after about 9 hours trying various things to make my atrix (running normal 2.3.4 rooted with no other cm7 or rom or any other mod) i am left with my atrix at the boot screen OR if i leave it to boot it just makes the logging on noises then shows the white screen, then nothing.
I stupidly followed the list to freeze using bloatfreezer. Not the updated list where it reads next to HOME (make sure you have another launcher) so i have frozen 'home' and i am stuck.
i cannot do a recovery because it has that fail message x2 everytime i do the power volume - and + on the android recov.
I am completely lost. i do not understand what hard/soft/adw/ push email/ or other jargon means. If you have any solutions i'd be more than grateful.
I hope i haven't bricked my phone, cos a 2year contract and no new phone is gonna push me near that ledge lol
Click to expand...
Click to collapse
If you're on AT&T - get RSD lite and find the proper sbf file and flash it. If you were using Gingerbread, make SURE you have a GINGERBREAD sbf file - or else you'll permanently brick your phone. If you're on Bell - you'll need the appropriate file for Bell to flash, same rules apply - If your on gingerbread, make SURE its a gingerbread file you're flashing.
atrixuk said:
There's soo many forums and different avenues to go down! after about 9 hours trying various things to make my atrix (running normal 2.3.4 rooted with no other cm7 or rom or any other mod) i am left with my atrix at the boot screen OR if i leave it to boot it just makes the logging on noises then shows the white screen, then nothing.
I stupidly followed the list to freeze using bloatfreezer. Not the updated list where it reads next to HOME (make sure you have another launcher) so i have frozen 'home' and i am stuck.
i cannot do a recovery because it has that fail message x2 everytime i do the power volume - and + on the android recov.
I am completely lost. i do not understand what hard/soft/adw/ push email/ or other jargon means. If you have any solutions i'd be more than grateful.
I hope i haven't bricked my phone, cos a 2year contract and no new phone is gonna push me near that ledge lol
Click to expand...
Click to collapse
you need to have an unlocked bootloader to flash Any custom rom PM me ill show ya how its not too hard
a pc a atrix and a few files and you will
be up n running in no time at all
Sent from my MB860 using Tapatalk
Hi guys,
I recently bought an Ideos X5 that was 2 months in use and it seems like I can't boot into stock recovery with it.
My device is definitely not rooted (Checked it with the app RootChecker). When I got it, I did a factory reset right after in stock recovery. I was able do get there with VOL+, HomeButton and Power. Neither this nor VOL+/VOL- and Power works now. I do not just reboot but boot when the phone is turned off. Android-Version is 2.3.5, Kernel 2.6.35.7, Build-Number ...B522... All I did so far was the factory reset.
Sorry I'm still not used to all this stuff although I read a lot, but seems like the more I read the more I get confused. Maybe it's totally easy but I tried a lot of things and none worked
Thanks a lot.
Try first holding down vol+ then power and then hold both of them until it either gets into recovery or its fully booted, depending if it works or not.
Sent from my U8800 using Tapatalk 2
MrTeflon said:
Hi guys,
I recently bought an Ideos X5 that was 2 months in use and it seems like I can't boot into stock recovery with it.
My device is definitely not rooted (Checked it with the app RootChecker). When I got it, I did a factory reset right after in stock recovery. I was able do get there with VOL+, HomeButton and Power. Neither this nor VOL+/VOL- and Power works now. I do not just reboot but boot when the phone is turned off. Android-Version is 2.3.5, Kernel 2.6.35.7, Build-Number ...B522... All I did so far was the factory reset.
Sorry I'm still not used to all this stuff although I read a lot, but seems like the more I read the more I get confused. Maybe it's totally easy but I tried a lot of things and none worked
Thanks a lot.
Click to expand...
Click to collapse
Should locked bootloader cause this? Because 522 has a locked bootloader. Atleast try to unlock the bootloader. There was a tutorial about this, search the forum
Sent from my U8800
I already found this tutorial,
http://forum.xda-developers.com/showthread.php?t=1457490
but the phone has to be rooted to do that or you have to get to stock recovery, so it didn't work obv.
I tried VOL+/Power, didn't work as well.
Thanks though. Any more ideas?
MrTeflon said:
I already found this tutorial,
http://forum.xda-developers.com/showthread.php?t=1457490
but the phone has to be rooted to do that or you have to get to stock recovery, so it didn't work obv.
I tried VOL+/Power, didn't work as well.
Thanks though. Any more ideas?
Click to expand...
Click to collapse
By did not work, do you mean it booted Android instead? If you don't want to root your device, you should reflash the firmware, but back up your things first.
Yes it booted normally. Maybe I'm gonna do that... Weird thing is that I did nothing but a factory reset and 3 or 4 apps like games and whatsapp.
aaaahhhh I got it. Had to untick "fast boot" in settings. Didn't really know that this is activated... anyway, thanks.
MrTeflon said:
aaaahhhh I got it. Had to untick "fast boot" in settings. Didn't really know that this is activated... anyway, thanks.
Click to expand...
Click to collapse
Looo
Sent from my U8800pro using xda premium
A few days back, my wife got me a shiny new nexus 10. This thing is cool for sure. However the one I'm using now isn't the one from a few days back. It is in fact, a replacement because after I hooked into my WiFi and loaded up the apps I have on my GNex off of Google backup, I got a notification for an android update. So I said "SHURE... I need that stuff" so I pushed the item in the notification and it said "push OK to restart...", so I did.... And it did restart to a DEAD ANDY ICON AND A "NO COMMAND" under him! I did a factory reset three times and never got further than the boot animation. The dude at google play support was a bit flummoxed but beyond a reset... Well... He pronounced it mostly dead. So rather than screw up the warranty, I took it back to where we bought it and got a new one.
So here I am again... I'm at JVP15P... And I've got a pending update downloaded and ready to fry my second N10! I've heard 4.2 has some kind of update issue just like this on the N10.... Is that true? What should I do? If this is true how do I get past this... I sure as s**t don't want to return anther one! Any suggestions are most appreciated.
Sent from my Nexus 10 using xda app-developers app
A short time ago, I was unable to update to 4.2.1 from 4.2, either from the automatic update, or from adb sideload. This was because I was using some older factory image (not sure what was wrong with it), but after downloading the latest factory image from Google and flashing it, I was then able to update without any issue
I finally did my updates.
Thankfully all went smooth. Although, my N10 ran as cool as ice before the updates. I could play games for a long time and it would barely get warm. Now it seems to run extremely warm. I wouldn't say hot, but it is noticeably a lot warmer and that is doing nothing but surfing the web.
Not sure what was in that first update, but it changed the way it runs. No other issues though.
What procedure did you use to flash? When you tried the ota updates, did your update attempts brick your tablet?
Sent from my Nexus 10 using xda app-developers app
I'm seeing the term "brick" used to lightly these days, but rest assured, the dead Android recovery is completely recoverable.
FYI for anyone reading, as it's becoming a pet peeve of mine ... "brick" means your device is TOTALLY dead, and as useful as a brick, if you get something (anything) on the screen, it's not a brick.
I think we should start lining up and shooting the people who throw that term around too lightly.
Anyway, back on topic, dead android screen with "no command" means the reboot to recovery flag is still set, but the device has no commend for recovery to perform, there are several ways out of it.
Worst comes to worst, and you want an easy way out, get the factory images from the dev site, flash them and you're golden.
alias_neo said:
I'm seeing the term "brick" used to lightly these days, but rest assured, the dead Android recovery is completely recoverable.
FYI for anyone reading, as it's becoming a pet peeve of mine ... "brick" means your device is TOTALLY dead, and as useful as a brick, if you get something (anything) on the screen, it's not a brick.
I think we should start lining up and shooting the people who throw that term around too lightly.
Anyway, back on topic, dead android screen with "no command" means the reboot to recovery flag is still set, but the device has no commend for recovery to perform, there are several ways out of it.
Worst comes to worst, and you want an easy way out, get the factory images from the dev site, flash them and you're golden.
Click to expand...
Click to collapse
Okay.... Soft-brick.... I stand corrected
I tried to do that using Wug's toolkit... But it didn't take. Did I need to unlock the boot loader first?
Sent from my Nexus 10 using xda app-developers app
Doctor Dedroid said:
Okay.... Soft-brick.... I stand corrected
I tried to do that using Wug's toolkit... But it didn't take. Did I need to unlock the boot loader first?
Sent from my Nexus 10 using xda app-developers app
Click to expand...
Click to collapse
It's a boot-loop, technically, but now I'm just being a pedant
I'm not too sure about the toolkits because I don't use them, but yes, you have to unlock to flash stock images.
Easiest way it do download the zip from the dev site, unlock manually, then just double click the flash-all script, that will take care of the rest, then just relock after and happy days.
I know it's a bit nerve racking when it won't boot, but that will get you out of most sticky situations, in the case of boot loops, a wipe/factory reset from recovery should normally solve the issue, if it doesn't just flash the images again as above.
Pesonally, if I'm messing i'll make sure my device is up to date and working, then fastboot boot TWRP (without unlocking or modifying my device) and backup to a USB drive, then, you can restore your system as is at any stage later if things mess up.
fastboot boot is fantastic because it lets you temp boot a custom recovery, and do all your usual stuff (including rooting etc) without replacing the stock recovery, and without unlocking, soon as you reboot, it's gone, cause it just boot the reovery into RAM.
Doctor Dedroid said:
What procedure did you use to flash? When you tried the ota updates, did your update attempts brick your tablet?
Sent from my Nexus 10 using xda app-developers app
Click to expand...
Click to collapse
If you are talking to me, mine is stock and used regular updates that were DL and ready.
I talk to anyone willing to listen to my drivel! I have heard of similar issues on this device ... Not many to be sure but my concern is if is an endemic issue going from the JVP15P... to JRO... 4.2 . it's good to know that this works for some if not most folks.
Sent from my Nexus 10 using xda app-developers app
Doctor Dedroid said:
I talk to anyone willing to listen to my drivel! I have heard of similar issues on this device ... Not many to be sure but my concern is if is an endemic issue going from the JVP15P... to JRO... 4.2 . it's good to know that this works for some if not most folks.
Sent from my Nexus 10 using xda app-developers app
Click to expand...
Click to collapse
It was only a particular issue that caused the update problem from 4.2 to 4.2.1, due to different filesystem formats in the factory images presented by google dev site. You *should* only have experienced it if you had flashed stock images before they updated to fix them.
I havn't seen cases of it happening otherwise. Unlocking will however boot loop you device because it doesn't do the full factory reset like it used to on the XOOM et al. Simple factory reset from stock recovery, after an unlock gets you booting again on the N10.
alias_neo said:
It was only a particular issue that caused the update problem from 4.2 to 4.2.1, due to different filesystem formats in the factory images presented by google dev site. You *should* only have experienced it if you had flashed stock images before they updated to fix them.
I havn't seen cases of it happening otherwise. Unlocking will however boot loop you device because it doesn't do the full factory reset like it used to on the XOOM et al. Simple factory reset from stock recovery, after an unlock gets you booting again on the N10.
Click to expand...
Click to collapse
Got it! To be sure when I tried to update I was around 60% on the battery level... Hopefully my issue was a fluke or due to a low battery.
Update: all updated and good to go. Thanks one and all!
Sent from my Nexus 10 using xda app-developers app
A little background info:
ATT GS4, rooted and on stock firmware
Had TWRP 2.6.0.0 on my phone
Tried to flash Illusion 7|15 or 7|16?
---------------------------------------------------
In the past, I've tried to flash illusion, with some success. I was able to get to the homescreen, but when I flashed my data backup. The phone wouldn't boot, so I reverted to stock. A few weeks later, I decide to take another spin at the rom and get it working. I wiped the data/cache/dalvik, and flashed the rom with gapps, rebooted the phone, and nothing happens. The phone keeps vibrating, but there is nothing happening past that.
After a significant amount of research, I've found a few tools/advice. I've downloaded ODIN and the (disgustingly large) tar file, but it doesn't have any use if the phone cannot be recognized by the computer since I am unable to enter download mode or recovery mode.
I found another tool that is supposed to "resurrect" the phone provided by legija. The only unfortunate part is there are no instructions provided, and once again, my computer isn't recognizing the phone as a device, as if it wasn't plugged in to the usb port at all. The application asks for a port number, but I have no clue what relevance a port number has, or at least that a usb port has a numerical value.
Anyway, is there anything left for me to do or is this a fancy new paperweight?
Excuse me for any poor grammar, I'm a little antsy about this
Gfrt94yn said:
A little background info:
ATT GS4, rooted and on stock firmware
Had TWRP 2.6.0.0 on my phone
Tried to flash Illusion 7|15 or 7|16?
---------------------------------------------------
In the past, I've tried to flash illusion, with some success. I was able to get to the homescreen, but when I flashed my data backup. The phone wouldn't boot, so I reverted to stock. A few weeks later, I decide to take another spin at the rom and get it working. I wiped the data/cache/dalvik, and flashed the rom with gapps, rebooted the phone, and nothing happens. The phone keeps vibrating, but there is nothing happening past that.
After a significant amount of research, I've found a few tools/advice. I've downloaded ODIN and the (disgustingly large) tar file, but it doesn't have any use if the phone cannot be recognized by the computer since I am unable to enter download mode or recovery mode.
I found another tool that is supposed to "resurrect" the phone provided by legija. The only unfortunate part is there are no instructions provided, and once again, my computer isn't recognizing the phone as a device, as if it wasn't plugged in to the usb port at all. The application asks for a port number, but I have no clue what relevance a port number has, or at least that a usb port has a numerical value.
Anyway, is there anything left for me to do or is this a fancy new paperweight?
Excuse me for any poor grammar, I'm a little antsy about this
Click to expand...
Click to collapse
Do you have AT&T insurance? Maybe the phone can have an accident? I would know of no other way to fix it if Odin isn't recognizing it. ):
Gfrt94yn said:
A little background info:
ATT GS4, rooted and on stock firmware
Had TWRP 2.6.0.0 on my phone
Tried to flash Illusion 7|15 or 7|16?
---------------------------------------------------
In the past, I've tried to flash illusion, with some success. I was able to get to the homescreen, but when I flashed my data backup. The phone wouldn't boot, so I reverted to stock. A few weeks later, I decide to take another spin at the rom and get it working. I wiped the data/cache/dalvik, and flashed the rom with gapps, rebooted the phone, and nothing happens. The phone keeps vibrating, but there is nothing happening past that.
After a significant amount of research, I've found a few tools/advice. I've downloaded ODIN and the (disgustingly large) tar file, but it doesn't have any use if the phone cannot be recognized by the computer since I am unable to enter download mode or recovery mode.
I found another tool that is supposed to "resurrect" the phone provided by legija. The only unfortunate part is there are no instructions provided, and once again, my computer isn't recognizing the phone as a device, as if it wasn't plugged in to the usb port at all. The application asks for a port number, but I have no clue what relevance a port number has, or at least that a usb port has a numerical value.
Anyway, is there anything left for me to do or is this a fancy new paperweight?
Excuse me for any poor grammar, I'm a little antsy about this
Click to expand...
Click to collapse
I've seen the repeated vibrating issue before from flashing the wrong file. Download mode was still accessible. Try again by hooking up the phone to the USB slot without the battery in it. Hold Vol Down + Home while inserting the battery. See if download mode will come up. If it does, Odin may not fix it, and you may end up using KIES, and that's if it does go into Download mode.
Phone is toast, fortunately the phone is still under warranty and they couldn't even get it to turn on so they replaced it
Still lost data, but it's not the end of the world. Thanks for the help though!
Gfrt94yn said:
Phone is toast, fortunately the phone is still under warranty and they couldn't even get it to turn on so they replaced it
Still lost data, but it's not the end of the world. Thanks for the help though!
Click to expand...
Click to collapse
Good deal man, glad you got a new one.
I have another question for somebody knowledgeable in rooting/rom flashing:
I think this was because the s4 bootloader is locked (through an update), would this cause the phone to hard brick? I've had nasty experiences in the past with locked bootloaders!
If it is locked, is there a way to unlock it? Or does it even need to be unlocked to flash a rom?
Thanks!
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
Gfrt94yn said:
I have another question for somebody knowledgeable in rooting/rom flashing:
I think this was because the s4 bootloader is locked (through an update), would this cause the phone to hard brick? I've had nasty experiences in the past with locked bootloaders!
If it is locked, is there a way to unlock it? Or does it even need to be unlocked to flash a rom?
Thanks!
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
Click to expand...
Click to collapse
The bootloader is locked yes, but Loki is there to workaround that. What is the build version on your replacement?
JDQ39.I337UCUAMDL
Is Loki on xda? I haven't found anything like that yet, although I've heard many references to that
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
Update:
Maybe I should open my eyes lol, found it in about 30 seconds
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
One more update:
I ran the casual root and now have my root and recovery. A couple of questions:
Does this also unlock the bootloader?
Somebody said that twrp flashes roms as if the bootloader is unlocked, so it wouldn't matter if it was or not. Is this true?
I guess really my question is, once I run casual root, is my phone ready to flash?
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
Gfrt94yn said:
One more update:
I ran the casual root and now have my root and recovery. A couple of questions:
Does this also unlock the bootloader?
Somebody said that twrp flashes roms as if the bootloader is unlocked, so it wouldn't matter if it was or not. Is this true?
I guess really my question is, once I run casual root, is my phone ready to flash?
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
Click to expand...
Click to collapse
Your phone is ready to flash, just make sure the ROM you flash has been Lokied or you'd have to flash a Loki kernel/LokiDoki after flashing the ROM (but before rebooting).
Gfrt94yn said:
One more update:
I ran the casual root and now have my root and recovery. A couple of questions:
Does this also unlock the bootloader?
Somebody said that twrp flashes roms as if the bootloader is unlocked, so it wouldn't matter if it was or not. Is this true?
I guess really my question is, once I run casual root, is my phone ready to flash?
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
Click to expand...
Click to collapse
If you are going to use TWRP, make sure the ROM has LOKI applied, and if it doesn't, flash the Loki_Doki patch last before rebooting.
If you use OUDHS recovery, it will Auto-Loki whatever you flash.
Ladies and Gentlemen, I am proud to announce that I've successfully flashed a rom without bricking my phone! *applause*
I thank(ed) you all for the help!
GS4 running slimbean and kanged key lime pie theme.
GiantBallSack said:
If you are going to use TWRP, make sure the ROM has LOKI applied, and if it doesn't, flash the Loki_Doki patch last before rebooting.
If you use OUDHS recovery, it will Auto-Loki whatever you flash.
Click to expand...
Click to collapse
What happens if one accidentally reboots before flashing Loki? Just need to reboot back into recovery and flash it?
godefroi said:
What happens if one accidentally reboots before flashing Loki? Just need to reboot back into recovery and flash it?
Click to expand...
Click to collapse
Yes
Sent from my SAMSUNG-SGH-I727 using xda app-developers app