Stuck on 5.1.1 badly! - Xperia Z3 Compact Q&A, Help & Troubleshooting

Hey guys,
So I wanted to upgrade to 5.1.1 and I saw a couple of ROMs for 5.1.1 that I was interested in flashing. So I chose this one > http://forum.xda-developers.com/z3-compact/development/rom-one-solution-debloated-xposed-t3164221
When I wiped, and then went to install it gave me an error, md5 error or something, but it seems it had already wiped my stuff.
So my phone was bricked and I could not get it past the initial Sony Xperia screen AT ALL. The only solution I found was to use "Emma" and recover it by resetting to factory. In doing so however, Emma installed a Stock 5.1.1, which booted no problems at all. Fantastic. Now I am on 5.1.1, unrooted, and inability to install or boot into a recovery to flash my backup.
Here's my problem, every single time I try to downgrade my Firmware back to Lollipop 5.0.2, or KitKat even, it either freezes at random places, like this > http://puu.sh/jRHEj/f3da0dfcfa.png
OR it finishes the flash on some Firmwares I have tried, but then I'll be stuck in a boot loop. I just cannot seem to have ANY luck trying to get my recovery back!
Any ideas what I could be doing wrong to get no success at all in downgrading from 5.1.1? Are there any methods to get into recovery in 5.1.1? Mine doesn't seem to ever work.
Is there a way to flash or install a backup that I did in TWRP without a recovery menu or no? Just want it all back to normal for now, 5.1.1 can get lost for the time being, screwed me over bad.

DGJ1992 said:
Hey guys,
So I wanted to upgrade to 5.1.1 and I saw a couple of ROMs for 5.1.1 that I was interested in flashing. So I chose this one > http://forum.xda-developers.com/z3-compact/development/rom-one-solution-debloated-xposed-t3164221
When I wiped, and then went to install it gave me an error, md5 error or something, but it seems it had already wiped my stuff.
So my phone was bricked and I could not get it past the initial Sony Xperia screen AT ALL. The only solution I found was to use "Emma" and recover it by resetting to factory. In doing so however, Emma installed a Stock 5.1.1, which booted no problems at all. Fantastic. Now I am on 5.1.1, unrooted, and inability to install or boot into a recovery to flash my backup.
Here's my problem, every single time I try to downgrade my Firmware back to Lollipop 5.0.2, or KitKat even, it either freezes at random places, like this > http://puu.sh/jRHEj/f3da0dfcfa.png
OR it finishes the flash on some Firmwares I have tried, but then I'll be stuck in a boot loop. I just cannot seem to have ANY luck trying to get my recovery back!
Any ideas what I could be doing wrong to get no success at all in downgrading from 5.1.1? Are there any methods to get into recovery in 5.1.1? Mine doesn't seem to ever work.
Is there a way to flash or install a backup that I did in TWRP without a recovery menu or no? Just want it all back to normal for now, 5.1.1 can get lost for the time being, screwed me over bad.
Click to expand...
Click to collapse
Try flashing the firmware ( ftfs ) using a different computer. If that doesn't help you can consider one of two options
1) Unlock your bootloader, that way all you need to do is download a custom kernel that comes with a recovery and flash any rom you like therefore removing the need for flashtool
2) Send your phone to Sony if you prefer not to unlock the bootloader and let them fix it but it might cost you
*Also take note if you downgrade to Lollipop ( 5.0.2 ) as I know there are no methods on how to root it yet unless coming from Firmware .93 which is a Kitkat firmware.

Revontheus said:
Try flashing the firmware ( ftfs ) using a different computer. If that doesn't help you can consider one of two options
1) Unlock your bootloader, that way all you need to do is download a custom kernel that comes with a recovery and flash any rom you like therefore removing the need for flashtool
2) Send your phone to Sony if you prefer not to unlock the bootloader and let them fix it but it might cost you
*Also take note if you downgrade to Lollipop ( 5.0.2 ) as I know there are no methods on how to root it yet unless coming from Firmware .93 which is a Kitkat firmware.
Click to expand...
Click to collapse
Hey Revo, thanks a lot for your reply dude. Appreciate you taking the time out of your day. I managed to flash a .93 kit kat, when I go to install TWRP via adb fastboot, my phone boots up with no image. I can hear sound and touch screen works but I have no picture. Super weird, had to reflash again to kitkat to restore picture. My bootloader is Unlocked already, so how effectively, on kitkat .93, can I get TWRP installed to recover my old backup? What's the easiest way from here?

DGJ1992 said:
Hey Revo, thanks a lot for your reply dude. Appreciate you taking the time out of your day. I managed to flash a .93 kit kat, when I go to install TWRP via adb fastboot, my phone boots up with no image. I can hear sound and touch screen works but I have no picture. Super weird, had to reflash again to kitkat to restore picture. My bootloader is Unlocked already, so how effectively, on kitkat .93, can I get TWRP installed to recover my old backup? What's the easiest way from here?
Click to expand...
Click to collapse
If you have your bootloader unlocked, you can just flash custom kernel via Flashtool, that would be AndroPlus kernel and you'll have a custom recovery

Cirra92 said:
If you have yout bootloader unlocked, you can just flash custom kernel via Flashtool, that would be AndroPlus kernel and you'll have a custom recovery
Click to expand...
Click to collapse
Nice, got that done and just finished restoring my own backup, AHHHHHHHHHH my phone is back. Technology is freaky as hell man. Crazy crazy world we live in.
I really wish I could click one button and donate money evenly amongst all you insane people that write awesome awesome tutorials for what I assume is like, non-profit? It's mental. Wouldn't have my phone back right now if it wasn't for this forum. It's just unreal. SO happy right now.
So if anyone knows at all, million dollar question. What's now the safest possible option, if ANY, to get from 5.0.2 rooted, to 5.1.1 rooted? To keep all my data I am obviously going to have to backup up all my photos/music/contacts/sms etc onto my PC or online in a mysterious cloud, but what's the best steps now to safely get to 5.1.1 rooted, with no hassle? Or is it even worth it at this point?

DGJ1992 said:
What's now the safest possible option, if ANY, to get from 5.0.2 rooted, to 5.1.1 rooted?
Click to expand...
Click to collapse
Now you just have to download a prerooted 5.1.1 rom and flash it through recovery and that is all. Full wipe is recommended before that of course (data, cache, dalvik, system)

Related

[Q] HTC One (64GB Dev Edtn) keeps crashing even after flashing new roms

To start off, I'll write down a history of my phone's problem. It had me scratching my head for over 1 week already and I still can't resolve it. I've been non-stop searching all over the net for solutions, and unfortunately it's still problematic.
Before the problems started, this is the state of my phone:
Stock HTC Rom 4.1.2 ver. 1.29.1540.3, rooted, custom recovery TWRP.
My phone initially hanged after receiving a text message. So I thought it just crashed and just needs a simple reboot. But unfortunately, after a reboot, it was just stuck at the "HTC quietly brilliant" splashscreen. But it could go into bootloader. So I went into recovery to restore from a backup point. But the restoring process failed, and worse, it wiped my current OS off.
So I went over the net to search for a copy of the stock HTC rom. then I found the specific RUU, from bugsylawson's, for my phone. And, at last I thought, the phone was back to normal. But unfortunately again, when I tried to re-download all my apps from google play store, after installing a few apps, my phone crashed again. the crash would reboot and enter into the OS but after a few seconds, it would hang again and reboot until it doesn't get into the OS anymore.
I went further research and studying about android terminologies to better understand the state and problem of my phone, and I came up with the idea to try to install a famous and stable custom Rom. I chose Android Revolution HD 13.3, which runs a custom 4.2.2 jelly bean. After successfully flashing the rom, I was so happy that everything went back to normalcy. So again I tried to reinstall the apps from play store. and everything worked fine. then after about approx. 18hrs, the problems started to show up again. My phone would hang while I was using it. And it would restart. sometimes it would just force close an app that i was using (in this case, I was using the "Internet" app and camera app). And after rebooting by itself a couple more times, it would get stuck in the "HTC quietly brilliant" splashscreen. again.
I tried several times to re-flash the custom Rom, and it would flash successfully everytime. And just to make sure i did the correct steps before flashing a new rom, I would like to enumerate what I did:
-wiped data, system, cache and dalvik cache partitions
-flashed custom rom via TWRP.
After everything I've tried. I'm starting to wonder if my phone has factory defects. I'm pointing to three parts of the hardware: processor, flash drive or cache. I'm wondering if the cache is a hardware or software based, and if it is a hardware, could it possibly be damaged physically and can't be repaired? How do I checkdisk the flash drive to make sure that i don't have bad sectors in it? How could i also try a diagnostic test of the processor to make sure that it is not faulty and does not overheat?
I'm new to android debugging. I would gladly take any logical solutions to help solve my problem. I'm pinning my hope on this forum before I finally contact HTC to claim a warranty or anything.
Hi can you download TeamViewer so that I can flash the latest 4.3 firmware on your device, after S-Offing
Matt said:
Hi can you download TeamViewer so that I can flash the latest 4.3 firmware on your device, after S-Offing
Click to expand...
Click to collapse
Hi Matt,
First of all, thanks for the very quick reply.
Uhn matt, I don't mean to annoy you with questions. But are there any other solutions without S-offing my device? And if possible and if it's not a hassle for you, may I ask what your possible might be? (Could you please enumerate it?)
I would greatly appreciate it if we could discuss the procedures first before actually trying to fix the issue.
You'll need to S-Off to flash the 4.3 firmware, and you want to be S-Off now as you can't use the exploit on the newer hboots. I will S-Off, flash 4.2.2 firmware, flash 4.3 firmware, then flash 4.3 Sense stock rom, then you can s-on if you want
Matt said:
Hi can you download TeamViewer so that I can flash the latest 4.3 firmware on your device, after S-Offing
Click to expand...
Click to collapse
Matt said:
You'll need to S-Off to flash the 4.3 firmware, and you want to be S-Off now as you can't use the exploit on the newer hboots. I will S-Off, flash 4.2.2 firmware, flash 4.3 firmware, then flash 4.3 Sense stock rom, then you can s-on if you want
Click to expand...
Click to collapse
I see. How is the new Hboot different from the old hboot? And if anything goes wrong, could I still go back to the old hboot?
To what firmware version is it going to be upgraded to? Will it have the same radio?
Just to clarify, we're CHANGING firmware version, not UPGRADING right? Is it because we're changing to different region's firmware so that i could just download an OTA update of newer stock roms? Correct me if I'm wrong.

[Q] I messed up the RADIO on my i8190L and now stuck in bootloop

Let's start with a little background as to how I got into this mess
- I had a perfectly working i8190L running SlimBean 4.3 from Maclaw (and I should've left it alone since its the wife's phone)
- I wanted to try out the new SlimKat 4.4 (http://get.novafusion.pl/?id=955)
- After a clean flash of slimkat, the new ROM was running fine after I completed setup EXCEPT baseband was 'xxxx'
- I rebooted into recovery and flashed GT-I8190_modem.bin-XXAMJ3-update2.zip because it was in my sdcard. I thought flashing a new radio would change the baseband except now I'm stuck in a bootloop with NO ABILITY TO BOOT TO RECOVERY!!!!
- I can only boot into Download mode, so I can still ODIN flash the system
Can someone suggest how/if I can fix this? I'm just kicking myself for turning a fully working phone into a brick with my wife breathing down my shoulders
my working setup was TWRP 2.7, SlimBean 4.3 and I had no idea which radio the i8190L came with default
I created a nandroid before all this mess, but I just need a way to get back into Recovery
You downloaded the wrong modem file. You need the one for the I8190L, but you flashed one for the I8190.
Sent from Tapatalk on my GT-I8190 running Novafusion's Carbon 4.4.2
chan1628 said:
Let's start with a little background as to how I got into this mess
- I had a perfectly working i8190L running SlimBean 4.3 from Maclaw (and I should've left it alone since its the wife's phone)
- I wanted to try out the new SlimKat 4.4 (http://get.novafusion.pl/?id=955)
- After a clean flash of slimkat, the new ROM was running fine after I completed setup EXCEPT baseband was 'xxxx'
- I rebooted into recovery and flashed GT-I8190_modem.bin-XXAMJ3-update2.zip because it was in my sdcard. I thought flashing a new radio would change the baseband except now I'm stuck in a bootloop with NO ABILITY TO BOOT TO RECOVERY!!!!
- I can only boot into Download mode, so I can still ODIN flash the system
Can someone suggest how/if I can fix this? I'm just kicking myself for turning a fully working phone into a brick with my wife breathing down my shoulders
my working setup was TWRP 2.7, SlimBean 4.3 and I had no idea which radio the i8190L came with default
I created a nandroid before all this mess, but I just need a way to get back into Recovery
Click to expand...
Click to collapse
Sorry but you are going to sleep on the couch tonight I suggest this:
You must download the original rom from SamMobile, install it through Odin and then install again through Odin the Recovery and through Recovery your "old" new Rom. When you are in the new Recovery check for the nandroid backup that you made . If it isnt there look for the couch because the phone is with the "old" new Rom without any of the past data.
Btw if you want you can upgrade your baseband from here:http://forum.xda-developers.com/showthread.php?t=2526831
Good luck
No recovery at all or bootloop in recovery as well?
Sent through time and space from my s3mini/CM11
chan1628 said:
Let's start with a little background as to how I got into this mess
- I had a perfectly working i8190L running SlimBean 4.3 from Maclaw (and I should've left it alone since its the wife's phone)
- I wanted to try out the new SlimKat 4.4 (http://get.novafusion.pl/?id=955)
- After a clean flash of slimkat, the new ROM was running fine after I completed setup EXCEPT baseband was 'xxxx'
- I rebooted into recovery and flashed GT-I8190_modem.bin-XXAMJ3-update2.zip because it was in my sdcard. I thought flashing a new radio would change the baseband except now I'm stuck in a bootloop with NO ABILITY TO BOOT TO RECOVERY!!!!
- I can only boot into Download mode, so I can still ODIN flash the system
Can someone suggest how/if I can fix this? I'm just kicking myself for turning a fully working phone into a brick with my wife breathing down my shoulders
my working setup was TWRP 2.7, SlimBean 4.3 and I had no idea which radio the i8190L came with default
I created a nandroid before all this mess, but I just need a way to get back into Recovery
Click to expand...
Click to collapse
Don't bother trying to flash it if nothing happens, drain the battery, return to seller and get replacement. I got free replacement from Amazon with my bricked rooted S3 mini.
jstath1972 said:
Sorry but you are going to sleep on the couch tonight I suggest this:
You must download the original rom from SamMobile, install it through Odin and then install again through Odin the Recovery and through Recovery your "old" new Rom. When you are in the new Recovery check for the nandroid backup that you made . If it isnt there look for the couch because the phone is with the "old" new Rom without any of the past data.
Btw if you want you can upgrade your baseband from here:http://forum.xda-developers.com/showthread.php?t=2526831
Good luck
Click to expand...
Click to collapse
just to clarify... what is consider "the original rom from SamMobile"? There are plenty of versions and country codes to choose from... I just wanted to make sure I'm downloading the correct one.... i've done enough of using the wrong files already
KoolKid98189 said:
Don't bother trying to flash it if nothing happens, drain the battery, return to seller and get replacement. I got free replacement from Amazon with my bricked rooted S3 mini.
Click to expand...
Click to collapse
its not going to be that easy for me... i've had this phone for almost 2yrs already
tys0n said:
No recovery at all or bootloop in recovery as well?
Sent through time and space from my s3mini/CM11
Click to expand...
Click to collapse
no recovery at all... it bootloops if i power on normally
chan1628 said:
just to clarify... what is consider "the original rom from SamMobile"? There are plenty of versions and country codes to choose from... I just wanted to make sure I'm downloading the correct one.... i've done enough of using the wrong files already
Click to expand...
Click to collapse
It depends on what country you're in and if the phone is locked to any specific carrier.
If it's not locked then I believe any i8190L firmware will do, just to get the phone running again.
chan1628 said:
its not going to be that easy for me... i've had this phone for almost 2yrs already
no recovery at all... it bootloops if i power on normally
Click to expand...
Click to collapse
It was a tough decision for me, it was either stick to a ****ty BlackBerry or get a free replacement and sacrifice the data. Some of it should be synced to your Google account
tys0n said:
It depends on what country you're in and if the phone is locked to any specific carrier.
If it's not locked then I believe any i8190L firmware will do, just to get the phone running again.
Click to expand...
Click to collapse
ok, i will give all this a try and hope for the best
thanks everyone for the quick responses :good:
You could also try to reflash just recovery thru Odin and see if it works.
Sent through time and space from my s3mini/CM11
chan1628 said:
just to clarify... what is consider "the original rom from SamMobile"? There are plenty of versions and country codes to choose from... I just wanted to make sure I'm downloading the correct one.... i've done enough of using the wrong files already
Click to expand...
Click to collapse
You are in Canada but the L version is for the Latin America countries. So the firmware must be from one of that countries. Which one i can't tell you. You should ask your seller.
[problem solved]
Ok, I was able to restore the phone with /u/jstath1972's suggestion
1. I went to http://www.sammobile.com/firmwares/ and downloaded the latest 'L' firmware
2. I used ODIN to flash the firmware
3. the phone REBOOTED!!!
(once the phone rebooted, the rest was easy)
4. powered off and ODIN flashed the lastest TWRP
5. powered off and booted into recovery
6. RESTORED NANDROID so wife would stop giving me the look
7. updated baseband as suggested: http://forum.xda-developers.com/show....php?t=2526831
THANK YOU THANK YOU :good:
side note: i wish my work was this effective in resolving technical issues (just my 2 cents)
chan1628 said:
Ok, I was able to restore the phone with /u/jstath1972's suggestion
1. I went to http://www.sammobile.com/firmwares/ and downloaded the latest 'L' firmware
2. I used ODIN to flash the firmware
3. the phone REBOOTED!!!
(once the phone rebooted, the rest was easy)
4. powered off and ODIN flashed the lastest TWRP
5. powered off and booted into recovery
6. RESTORED NANDROID so wife would stop giving me the look
7. updated baseband as suggested: http://forum.xda-developers.com/show....php?t=2526831
THANK YOU THANK YOU :good:
side note: i wish my work was this effective in resolving technical issues (just my 2 cents)
Click to expand...
Click to collapse
Good sleep tonight, my friend ! :good:

[Q] Is it a good idea to flash a rom on a "somewhat" rooted phone?

Hi, I'm running Benny's 4.3 (build number 3.04.651.2) Deodexed (because i do not see any .odex files in the system folder, right?) and I want to flash the update which keeps popping up in the notifications every 24 hours after clearing app data.
I tried doing the OTA update but my phone goes into TWRP. My biggest concern is flashing the stock rooted update because my phone really isn't rooted. I have SuperSu on the phone and sometimes I get "SuperSu has been granted permission" or something like that but Root Checker app says the phone does not have proper root access. I don't really know what is going on because I took my phone to a repair center to get it unlocked shortly after i got the official OTA 4.3 update. I read that you need to downgrade to 4.1 and then unlock the phone through SimUnlockHelper apk. When I got my phone back everything was working as it should and my phone is indeed unlocked.
My biggest concern is flashing a stock rooted rom because of the fact that my phone does not have proper root access. Would you recommend doing this and are there any precautions I should be aware of because I had nothing to do with rooting or tweaking android before since this is my first phone that runs android officially.
Thanks!
Andza195 said:
Hi, I'm running Benny's 4.3 (build number 3.04.651.2) Deodexed (because i do not see any .odex files in the system folder, right?) and I want to flash the update which keeps popping up in the notifications every 24 hours after clearing app data.
I tried doing the OTA update but my phone goes into TWRP. My biggest concern is flashing the stock rooted update because my phone really isn't rooted. I have SuperSu on the phone and sometimes I get "SuperSu has been granted permission" or something like that but Root Checker app says the phone does not have proper root access. I don't really know what is going on because I took my phone to a repair center to get it unlocked shortly after i got the official OTA 4.3 update. I read that you need to downgrade to 4.1 and then unlock the phone through SimUnlockHelper apk. When I got my phone back everything was working as it should and my phone is indeed unlocked.
My biggest concern is flashing a stock rooted rom because of the fact that my phone does not have proper root access. Would you recommend doing this and are there any precautions I should be aware of because I had nothing to do with rooting or tweaking android before since this is my first phone that runs android officially.
Thanks!
Click to expand...
Click to collapse
use the backup feature in twrp to make a nandroid and flash a stock rooted 4.3 rom. if it doesn't work restore your backup. if u need any info the sticky thread at the top of this section by bd19 will really help. read thoroughly. fyi you cannot ota with a custom recovery (twrp) you need stock recovery.
jblaze10 said:
use the backup feature in twrp to make a nandroid and flash a stock rooted 4.3 rom. if it doesn't work restore your backup. if u need any info the sticky thread at the top of this section by bd19 will really help. read thoroughly. fyi you cannot ota with a custom recovery (twrp) you need stock recovery.
Click to expand...
Click to collapse
^This is the safest option @Andza195
BTW, imo, it should work, but just backup just in case. Also, if something doesn't work, the real best method is just to download the newest version of the ROM, back (everything that's important to you) up, wipe everything in TWRP except Internal Storage (because this is where the flashable .zip is at!) and flash the ROM fresh.
jblaze10 said:
use the backup feature in twrp to make a nandroid and flash a stock rooted 4.3 rom. if it doesn't work restore your backup. if u need any info the sticky thread at the top of this section by bd19 will really help. read thoroughly. fyi you cannot ota with a custom recovery (twrp) you need stock recovery.
Click to expand...
Click to collapse
Okay, thanks!
StormyNight said:
^This is the safest option @Andza195
BTW, imo, it should work, but just backup just in case. Also, if something doesn't work, the real best method is just to download the newest version of the ROM, back (everything that's important to you) up, wipe everything in TWRP except Internal Storage (because this is where the flashable .zip is at!) and flash the ROM fresh.
Click to expand...
Click to collapse
Just flashed the stock rooted kitkat rom and everything is working as it was before, thank you all for your help!

Confused on upgrading to Lollipop

I have read several post on how to root my ATT n900a and using safestrap. I have rooted tons of androids all have used CWM , twrp , and such. This phone seems to be a little more difficult to install custom roms. When I got the phone it was on 4.4.4 so I downgraded wot 4.4.2 added root and safestrap and all was good. I then booted into safestrap and installed 4.4.4 with root. this was succesfull as well, but when ever i go to safestrap app and press reboot to recovery it does nothing. i tried installing and reinstalling. NO go. What i was going to do was boot to safestrap and then flash lollipop, but cant get into bootstrap. My question is would it just be easier to go from 4.4.2 straight to lollipop or what is the easiest way to get their. Also Im a fan of aosp, but im not to sure that this would be best route because of spen and what not. Is there a TW lollipop version and if so what is the best way to get it? I tried to update OTA before i flashed anything and it said i was on most recent at 4.4.4. Sorry for newb questions, but this phone has really confused me. Android was so much easier to root and flash when they first came out and it seems like the newer phones are getting harder.
pitmanr2003 said:
I have read several post on how to root my ATT n900a and using safestrap. I have rooted tons of androids all have used CWM , twrp , and such. This phone seems to be a little more difficult to install custom roms. When I got the phone it was on 4.4.4 so I downgraded wot 4.4.2 added root and safestrap and all was good. I then booted into safestrap and installed 4.4.4 with root. this was succesfull as well, but when ever i go to safestrap app and press reboot to recovery it does nothing. i tried installing and reinstalling. NO go. What i was going to do was boot to safestrap and then flash lollipop, but cant get into bootstrap. My question is would it just be easier to go from 4.4.2 straight to lollipop or what is the easiest way to get their. Also Im a fan of aosp, but im not to sure that this would be best route because of spen and what not. Is there a TW lollipop version and if so what is the best way to get it? I tried to update OTA before i flashed anything and it said i was on most recent at 4.4.4. Sorry for newb questions, but this phone has really confused me. Android was so much easier to root and flash when they first came out and it seems like the newer phones are getting harder.
Click to expand...
Click to collapse
If you are still on 4.4.4 then you need this Kernel Flasher http://forum.xda-developers.com/note-3-att/development/nc2-flasher-app-unsafe-t2989141 just install as an app. When you run it grant Supersu and then tap, tap to boot (Pic 1) that will get you to Safestrap. If you are just flashing and not going to flash Lollipop you will need the NL1 Kernel from here http://forum.xda-developers.com/note-3-att/general/wip-getting-note4-norma-n9005-running-t2978346 (Pic 2) put in on your sd card and flash it with Safestrap to get your Rom to boot back up. If you want Rooted Lollipop http://forum.xda-developers.com/showpost.php?p=59666958&postcount=2 it's the easiest way I seen. Thanks @benwaffle @carl1961 @Walter.White
Rooted i747 said:
If you are still on 4.4.4 then you need this Kernel Flasher http://forum.xda-developers.com/note-3-att/development/nc2-flasher-app-unsafe-t2989141 just install as an app. When you run it grant Supersu and then tap, tap to boot (Pic 1) that will get you to Safestrap. If you are just flashing and not going to flash Lollipop you will need the NL1 Kernel from here http://forum.xda-developers.com/note-3-att/general/wip-getting-note4-norma-n9005-running-t2978346 (Pic 2) put in on your sd card and flash it with Safestrap to get your Rom to boot back up. If you want Rooted Lollipop http://forum.xda-developers.com/showpost.php?p=59666958&postcount=2 it's the easiest way I seen. Thanks @benwaffle @carl1961 @Walter.White
Click to expand...
Click to collapse
thanks im a fan of lollipop have it on my s4. The method you show was the one i was trying to do, but couldnt get to safestrap. im back at 4.4.2 now can i just flash right to lollipop from there and not have to deal with going 4..4.4 first? Also is this a TW lollipop?
pitmanr2003 said:
thanks im a fan of lollipop have it on my s4. The method you show was the one i was trying to do, but couldnt get to safestrap. im back at 4.4.2 now can i just flash right to lollipop from there and not have to deal with going 4..4.4 first? Also is this a TW lollipop?
Click to expand...
Click to collapse
Yea you can just flash it right from 4.4.2 and it's just the stock lollipop just rooted with tw.

Easiest Way Back to Stock (rooted)

So I have been looking around in the Development forum and there are so many ROM options out there now. I have been on CM 12 nightlies for so long now I am out of the loop on stock builds and all. I am looking to just go back to a completely stock build (with root). Can anyone point me in the right direction for the files I need?
I have a Google Store bought N6 and I am currently on Verizons network.
Thanks!
EDIT: I would also like to be on the latest (and greatest) build.
djmend said:
So I have been looking around in the Development forum and there are so many ROM options out there now. I have been on CM 12 nightlies for so long now I am out of the loop on stock builds and all. I am looking to just go back to a completely stock build (with root). Can anyone point me in the right direction for the files I need?
I have a Google Store bought N6 and I am currently on Verizons network.
Thanks!
Click to expand...
Click to collapse
sure.. https://developers.google.com/android/nexus/images?hl=en
the only way back to stock isnt by flashing roms via twrp, its by flashing a factory image. on top of that, this is a basic element that you HAVE TO learn before ever rooting your phone.
simms22 said:
sure.. https://developers.google.com/android/nexus/images?hl=en
the only way back to stock isnt by flashing roms via twrp, its by flashing a factory image. on top of that, this is a basic element that you HAVE TO learn before ever rooting your phone.
Click to expand...
Click to collapse
Okay... I guess that makes sense, and to obtain root I would simply flash the SuperSU.zip from Recovery after I have completed the factory image restore? Do I need to re-flash Recovery?
djmend said:
Okay... I guess that makes sense, and to obtain root I would simply flash the SuperSU.zip from Recovery after I have completed the factory image restore? Do I need to re-flash Recovery?
Click to expand...
Click to collapse
after, you would need to flash twrp recovery, then flash supersu from twrp. so yes.
but, if you really dont have to, dont relock your bootloader
djmend said:
So I have been looking around in the Development forum and there are so many ROM options out there now. I have been on CM 12 nightlies for so long now I am out of the loop on stock builds and all. I am looking to just go back to a completely stock build (with root). Can anyone point me in the right direction for the files I need?
I have a Google Store bought N6 and I am currently on Verizons network.
Thanks!
EDIT: I would also like to be on the latest (and greatest) build.
Click to expand...
Click to collapse
Right, no re-lock, so, I have, 1) Flash Factory Image 2) Flash TWRP 3) Flash SuperSU = Back to Stock (Rooted). Got it, thanks again.
What SImms said
We have a lot of people in panic state over trying to relock their bootloader, and to further emphasize what Simms said, DO NOT ATTEMPT TO RELOCK BOOTLOADER, there are specific procedures to do that but locking it just isn't necessary

Categories

Resources