Develop Bugs

[ROOT] Wont Trip Flash Counter (Bell Canada I747M)

Hey Everyone!
This is my first time doing an official ROM repact by injecting Root into the ROM itself so as to not trip the flash counter!
This is for Bell's Canadian S3 SGH-I747M firmware: I747MVLALE8
I know this has recently already been done by MrRobinson for the Canadian carriers but I have done mine slightly differently.
Most of you im sure know of Chainfire and his amazing work, well I love the work he does and it is my opinon that his Root app SuperSU is better then the Superuser one, this may be very minor or non exisist to some people and it all really boils down to Personal perference but as such I perfer SuperSU and love it and want to support his work!
I have tested this myself on my own S3 works great, counter does not increase, and flash time only took me 6 minutes! (some people were complaining about the other root injected roms taking 10 minutes and upwords to 20 to complete)
IMPORTANT NOTE:
This rom has been injected with Chainfires CF root but it is only his SuperSU root app and does not contain any custom CWM recovery or Manager app. Chainfire custom builds his CWM manager app specific to certain devices and is not compatible with the North American varients.
To get the North American LTE version of CWM Recovery please see team epics website at:
http://www.epiccm.org/2012/06/cwm-recovery-on-all-sgs3-lte-variants.html
To install this recovery without tripping the counter you will need to manually copy it over to the memory card block which contains the recovery section of your phone. Once downloaded extract the recovery.img file out of the tar and place it into your sdcard.
Either through ADB shell or using a terminal emulator app on the phone run the following commands:
Code:
su
dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p18
Remember to do "su" first to grand root access to the ADB shell or terminal emulator otherwise you will not be given the permissions to do the recovery copy on the 2nd command as mentioned above.
1 final note, like all the other root injected roms for the S3, these root methods currently do have not busybox built into them so it is highly recommended for you to download and install the busybox app off the play store [the one by Stephen (Stericson)] to get even more functionality for your rooted device.
~~Link Removed~~
My apologies in advance for uploading to filefactory as they are known to be slow sometimes on downloads. If anyone is able to host it for faster speeds that would be awesome.
EDIT:
For some reason the cache file doesn't properly install and so you are left with a blank CSC. Currently trying to figure out why this is happening as I havn't done anything to the CSC file to begin with. In the mean time I have taken down the link. I recommend getting the one made by MrRobinson for flashing Bells Rom
View the sticky post for his here:
http://forum.xda-developers.com/showthread.php?t=1739426

There is already a thread for this under stickies, but thanks for your contribution anyways.
Sent from my SAMSUNG-SGH-I747 using xda premium

jthrasher47 said:
There is already a thread for this under stickies, but thanks for your contribution anyways.
Sent from my SAMSUNG-SGH-I747 using xda premium
Click to expand...
Click to collapse
I am aware of this, I actually made a point of saying so in my post but I guess you skimmed it and didn't see that part?.
I also explain that mine is a bit different and why.

Correct me if I'm wrong, but SuperSu and Superuser and interchangable via. the Play Store. No need to redo the whole rooting process just to change the app.

dbzgod said:
It took me longer because I had to do it without a Linux box, funny enough I manage to do it using my Rooted S2 phone lol.
Click to expand...
Click to collapse
Am I understanding correctly that this method doesn't use odin, and you somehow used another android phone to do it?

danny6514 said:
Correct me if I'm wrong, but SuperSu and Superuser and interchangable via. the Play Store. No need to redo the whole rooting process just to change the app.
Click to expand...
Click to collapse
Yeah they can be changed out, but I released this anyways because I had started work on it right away when the firmware was released and even though MrRobinson had put out root injected roms before me I still wanted to complete what I started and not leave it half done.
I would of had this out at about the same time if not before the others but because of time contraints on my part as well as running into a few problems via doing the whole repack and inject a unique way on my rooted S2 Android phone. Instead of a Linux box I figured out how to do almost all of the repacking steps on an Android phone and then I was delayed trying to figure out 1 important step that required a full Linux box, but discovered an alternate means to do so on Windows.
At any rate I just wanted to post my work (even though late coming) and offer people this alternate root injection Rom.
qwer777 said:
Am I understanding correctly that this method doesn't use odin, and you somehow used another android phone to do it?
Click to expand...
Click to collapse
No you still need to use Odin to flash the firmware. I see your misunderstanding though, I was just trying to explain in my post that since I dont have a Linux box I had to do the repact and inject process over ADB shell via my Rooted Galaxy S II phone for a Linux eviroment.

dbzgod said:
No you still need to use Odin to flash the firmware. I see your misunderstanding though, I was just trying to explain in my post that since I dont have a Linux box I had to do the repact and inject process over ADB shell via my Rooted Galaxy S II phone for a Linux eviroment.
Click to expand...
Click to collapse
Damn! I was really excited! Oh well. I'll need to find me a windows pc.

[How-To][tutorial] Bootloader Unlock, Custom Recovery Razr M

So if anybody's been reading the news, you may know that the bootloader for the Razr M has finally been unlocked!
So here's a how-to on unlocking and flashing a custom recovery.
A couple notes:
This essentially makes the phone behave like an unlocked dev edition. You can flash any firmware, recovery, etc that you want. Be careful, don't flash stuff for other devices, etc etc...
FOLLOW THE INSTRUCTIONS...
Future OTAs may (will) disable this exploit. Do it while it can be done! Also, beware OTAs! They could disable this, or do bad things... Don't update unless you know it won't disable the bootloader exploit
You need to be rooted, have the motorola drivers installed (link here - sorry, it's device manager, but they do have all the drivers in a nice package...)
First, root if you haven't already...
Next, download Motopocalypse.zip by Dan Rosenberg from here: http://vulnfactory.org/blog/2013/04/08/motorola-bootloader-unlocking/
extract the zip and run
Run through the entire process, until it tells you you have a bootloader unlock.
Make sure that AP Fastboot indicates "Unlocked, status code 3"
Also, when you reboot, you will get a warning screen about an unlocked bootloader.
Next, choose your recovery. There are 2 options, TWRP (Touch Win Recovery Project) and CWM (ClockworkMod)
either works, and each has benefits and downsides, choose whichever one you want.
Follow the instructions for your flavor of recovery:
CWM:
Download the .img file here: http://goo.im/devs/Hashcode/scorpion_mini/cwm-recovery--scorpion_mini.img
Move it to the same place you extracted the .zip above.
Open a command prompt/terminal/command interpreter at that location (Windows short-cut: shift-right click, command window here)
type the following (filename is the name of the file you downloaded, probably "cwm-recovery--scorpion_mini.img" unless you renamed it): fastboot flash recovery filename
and press Enter. Let it flash, then reboot.
The first time you use CWM, it will ask you if you want to disable something that would cause CWM to stop working. You do want to, so say "yes". Othewise, you'll have to reflash CWM every time you want to use it
TWRP:
Download the .img file here: http://d-h.st/QGe
Move it to the same place you extracted the .zip above.
Open a command prompt/terminal/command interpreter at that location (Windows short-cut: shift-right click, command window here)
type the following (filename is the name of the file you downloaded, probably "twrp2.4-recovery-scorpion_mini.img" unless you renamed it):
fastboot flash recovery filename
and press Enter. Let it flash, then reboot.
Now, you need to disable the automatic re-flashing of stock recovery.
Reboot directly into recovery, and allow TWRP to disable the re-flashing.
Now, you have TWRP running on your Razr M
Please consider donating to Dan Rosenberg here for all the work he's done for our phones!
Congrats! You now have a custom recovery on your Razr M
Reboot into recovery, and you're done!
----IMPORTANT NOTE:----
IF you are on the latest OTA and have NOT unlocked, it is impossible at this time to unlock. It may be possible in the future if someone finds another exploit, but not likely. Basically, if you updated without researching (that's why you shouldn't do that) or got a new one after the OTA, you're SOL for right npw

sloosecannon said:
So if anybody's been reading the news, you may know that the bootloader for the Razr M has finally been unlocked!
So here's a how-to on unlocking and flashing a custom recovery.
A couple notes:
This essentially makes the phone behave like an unlocked dev edition. You can flash any firmware, recovery, etc that you want. Be careful, don't flash stuff for other devices, etc etc...
FOLLOW THE INSTRUCTIONS...
Future OTAs may (will) disable this exploit. Do it while it can be done! Also, beware OTAs! They could disable this, or do bad things... Don't update unless you know it won't disable the bootloader exploit
You need to be rooted, have the motorola drivers installed (link here - sorry, it's device manager, but they do have all the drivers in a nice package...)
First, root if you haven't already...
Next, download Motopocalypse.zip by Dan Rosenberg from here: http://vulnfactory.org/blog/2013/04/08/motorola-bootloader-unlocking/
extract the zip and run
Run through the entire process, until it tells you you have a bootloader unlock.
Make sure that AP Fastboot indicates "Unlocked, status code 3"
Also, when you reboot, you will get a warning screen about an unlocked bootloader.
Next, choose your recovery. There are 2 options, TWRP (Touch Win Recovery Project) and CWM (ClockworkMod)
either works, and each has benefits and downsides, choose whichever one you want.
Follow the instructions for your flavor of recovery:
CWM:
Download the .img file here: http://goo.im/devs/Hashcode/scorpion_mini/cwm-recovery--scorpion_mini.img
Move it to the same place you extracted the .zip above.
Open a command prompt/terminal/command interpreter at that location (Windows short-cut: shift-right click, command window here)
type the following (filename is the name of the file you downloaded, probably "cwm-recovery--scorpion_mini.img" unless you renamed it): fastboot flash recovery filename
and press Enter. Let it flash, then reboot.
The first time you use CWM, it will ask you if you want to disable something that would cause CWM to stop working. You do want to, so say "yes". Othewise, you'll have to reflash CWM every time you want to use it
TWRP:
Download the .img file here: http://goo.im/devs/Hashcode/scorpion_mini/twrp2.4-recovery-scorpion_mini.img
Move it to the same place you extracted the .zip above.
Open a command prompt/terminal/command interpreter at that location (Windows short-cut: shift-right click, command window here)
type the following (filename is the name of the file you downloaded, probably "twrp2.4-recovery-scorpion_mini.img" unless you renamed it):
fastboot flash recovery filename
and press Enter. Let it flash, then reboot.
Now, you need to disable the automatic re-flashing of stock recovery.
Run adb shell from the same info and run the following commands (you can copy-paste and press enter):
su
mount -o remount,rw /system
mv /system/etc/install-recovery.sh /system/etc/install-recovery.sh.bak
mount -o remount,ro /system
Now, you have TWRP running on your Razr M
Please consider donating to Dan Rosenberg here for all the work he's done for our phones!
Congrats! You now have a custom recovery on your Razr M
Reboot into recovery, and you're done!
Click to expand...
Click to collapse
I followed the instructions, ran the .bat, but my Razr M is still being shown as locked 1. Am on 4.1.1 stock rom. Do I need to uninstall SafeStrap?
Edit- Found my answer, the phone needed to be unlocked so it could ask me for SU permissions. Hope this helps someone else so I don't feel like the only idiot.

As long as we do this first, future OTAs can't relock our bootloaders, can they?

Awesome!!!! Hopefully this will spark up some dev activity. I know this is huge I just hope its not too little too late.

BoredKender said:
I followed the instructions, ran the .bat, but my Razr M is still being shown as locked 1. Am on 4.1.1 stock rom. Do I need to uninstall SafeStrap?
Edit- Found my answer, the phone needed to be unlocked so it could ask me for SU permissions. Hope this helps someone else so I don't feel like the only idiot.
Click to expand...
Click to collapse
Nope, don't need to uninstall safestrap, and yep, you do need SU.
sujaanj said:
As long as we do this first, future OTAs can't relock our bootloaders, can they?
Click to expand...
Click to collapse
That's really not known... advise you steer clear of OTAs for the time being... until we can determine if it will actually relock or not...

sloosecannon said:
That's really not known... advise you steer clear of OTAs for the time being... until we can determine if it will actually relock or not...
Click to expand...
Click to collapse
Well, from what I read from Dan's explanation on his website, we are essentially blowing a fuse that can not be reset. So I'm leaning towards rejecting OTAs from now on but according to my limited understanding, we will be safe.

trouble installing recovery
Thanks! I successfully unlocked the bootloader following the awesome instructions AP Fastboot indicated "Unlocked, status code 3"
I then let the device reboot.
I'm trying to install CWM following the instructions and I get <waiting for device>
This makes me think i need to not have the phone booted into the OS
What am I doing wrong.
Please excuse my newbness
Regards,
Darryl

dnoren said:
Thanks! I successfully unlocked the bootloader following the awesome instructions AP Fastboot indicated "Unlocked, status code 3"
I then let the device reboot.
I'm trying to install CWM following the instructions and I get <waiting for device>
This makes me think i need to not have the phone booted into the OS
What am I doing wrong.
Please excuse my newbness
Regards,
Darryl
Click to expand...
Click to collapse
You need to be in fast boot mode for it to flash recovery.
Turn off your device, hold Power + Vol Up + Vol down then select fast boot and plug your phone into your computer.
Sent from my XT907 using xda premium

new roms
Thanks for the write up, worked flawlessly. So I did this with safestrap installed, can I just wipe the phone and install a rom made for safestrap like you normally would with CWM?

CaptainElwood said:
Thanks for the write up, worked flawlessly. So I did this with safestrap installed, can I just wipe the phone and install a rom made for safestrap like you normally would with CWM?
Click to expand...
Click to collapse
Yes, as long as you mount your /system first. Found that out the hard way too...

Does this wipe our phone
Sent from my XT907 using xda app-developers app

Nope

ifrankie10 said:
Does this wipe our phone
Sent from my XT907 using xda app-developers app
Click to expand...
Click to collapse
No, everything is the same except I get a warning every boot that my phones bootloader is unlocked
Has anyone flashed a dev edition rom yet? If so what one, I wanted to try but the cm10 thread has broken links. Can I get that somewhere else?

Also say my screen cracks and I call Motorola and they say send it out and they see that it is unlocked does that mean they will not repair it
Sent from my XT907 using xda app-developers app
---------- Post added at 03:11 AM ---------- Previous post was at 03:07 AM ----------
and can we rsd back to stock if we can't get into the recovery but into fastboot
Sent from my XT907 using xda app-developers app

I'm trying to help unlock my friends razr m, but his device was updated to 4.1.1 in the Verizon store by one of the sales associates. Does the root method (required for bootloader unlock) work on 4.1.1?
Sent from my SCH-I535 using Tapatalk 2

mindflayyer said:
I'm trying to help unlock my friends razr m, but his device was updated to 4.1.1 in the Verizon store by one of the sales associates. Does the root method (required for bootloader unlock) work on 4.1.1?
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
If I recall correctly, 4.1.1 is fine, just use the JB root method. 4.1.2 is an issue, but that has not been pushed yet (on Verizon that is).

Floundering with recovery
I've tried both methods cwm and twrp it says writing recovery, okay, and finished but when i try to go into recovery I just get the Green robot
Any ideas on what I'm doing wrong?
Thanks

Cant get this to work and I can't get safestrap off my phone
Sent from my cm_tenderloin using Tapatalk HD

Hmm..
Also say my screen cracks and I call Motorola and they say send it out and they see that it is unlocked does that mean they will not repair it
Click to expand...
Click to collapse
If they are able to discover that the phones system files have been tampered with in anyway, including unlocking, rooting, installing custom recoveries, roms, modems etc.. most likely they will not fix your phone. Quoted off the Motorola website "Unlocking your DEVELOPER EDITION's bootloader voids all warranties" (Naturally this goes for retail edition even more so). I have however hear of people getting unlocked phones repaired under warranty, just make sure that you RSD back to stock, unrooted before you send it.
pjf626 said:
Cant get this to work and I can't get safestrap off my phone
Sent from my cm_tenderloin using Tapatalk HD
Click to expand...
Click to collapse
Gonna need a tad more detail.. Are you sure that you're rooted? If not, that would cause both of your problems. You also need to uninstall safestrap through the safestap app, and then remove the app.

sujaanj said:
Well, from what I read from Dan's explanation on his website, we are essentially blowing a fuse that can not be reset. So I'm leaning towards rejecting OTAs from now on but according to my limited understanding, we will be safe.
Click to expand...
Click to collapse
Yes unlocking is blowing a fuse but that's beside the point, there is a separate piece of software that looks at that fuse and decides whether to allow the system to boot an unsigned system or not. If the OTA changes this piece of software to use another fuse instead (there might be many of them) then your device will be locked again and we will be back at square one, no fuse need to actually be reset for this to happen.

Original stock firmware?

Would anyone know where to find the original stock rom and flashing method?

Why would you need it if there is no alternative right now? Stock is all you can have so do a factory reset if required.
Sent from my SGH-I337 using xda app-developers app

For example you need a stock rom to unroot your device. Factory reset doesn't work for unrooting. So the questions from @ekolb123 is very good. I agree to the question.

You can unroot from within the supersu app under settings.
Sent from my LG-V500 using Tapatalk 4

LG has posted the source for the G Pad: https://www.lg.com/global/support/opensource/opensourceList?types=NAME&search=LGV500
However until now there isn't any way to unlock/hack the bootloader, and so you cant flash it.

Most of us rooted with Kingoroot. Can't you just unroot with that and then factory reset in the stock recovery?

I'm currently working on a stock, rooted ROM but as I'm very new at this, I'm having quite a bit of difficulty.
Once I'm able to actually get it to build, then I can work on figuring out our new LOKI support and get CWM up and running.

what buttons do i press upon booting up to get to recovery to factory reset my device. i already unrooted. thanks.
edit: nevermind, figured it out. it's in system settings, and you can also press and hold Volulme Down + Power and then when you see LG let go of Power and press and hold it again.

mustbepbs said:
I'm currently working on a stock, rooted ROM but as I'm very new at this, I'm having quite a bit of difficulty.
Once I'm able to actually get it to build, then I can work on figuring out our new LOKI support and get CWM up and running.
Click to expand...
Click to collapse
Good news.
I tried to get CWM working and although it built i only achieved to brick my tablet.
The good news is that now i've found tutorials to unbrick it (in fact any recent LG smartphone or tablet).
To download the rom: http://forum.xda-developers.com/showthread.php?t=1073827
model is v500
Go to download mode by pressing volume+ and keeping it pressed connect your usb cable to your pc (the tablet must be off)
To flash the rom : http://forum.frandroid.com/topic/167696-tuto-flasher-une-rom-officielle-en-kdz/ (translated by google: http://translate.google.fr/translate?sl=fr&tl=en&js=n&prev=_t&hl=fr&ie=UTF-8&u=http%3A%2F%2Fforum.frandroid.com%2Ftopic%2F167696-tuto-flasher-une-rom-officielle-en-kdz%2F&act=url)
This method saved my tablet.

Also check this:
http://lg-phone-firmware.com/index.php?id_mod=39

obiwan86300 said:
Good news.
I tried to get CWM working and although it built i only achieved to brick my tablet.
The good news is that now i've found tutorials to unbrick it (in fact any recent LG smartphone or tablet).
To download the rom: http://forum.xda-developers.com/showthread.php?t=1073827
model is v500
Go to download mode by pressing volume+ and keeping it pressed connect your usb cable to your pc (the tablet must be off)
To flash the rom : http://forum.frandroid.com/topic/167696-tuto-flasher-une-rom-officielle-en-kdz/ (translated by google: http://translate.google.fr/translat...to-flasher-une-rom-officielle-en-kdz/&act=url)
This method saved my tablet.
Click to expand...
Click to collapse
Good to know. How did you flash the recovery? Did you work LOKI into it?

mustbepbs said:
Good to know. How did you flash the recovery? Did you work LOKI into it?
Click to expand...
Click to collapse
adb push loki_flash /data/local/tmp/loki_flash
adb push loki_patch /data/local/tmp/loki_patch
adb push recovery.img /data/local/tmp/recovery.img
adb shell
su
dd if=/dev/block/platform/msm_sdcc.1/by-name/aboot of=/data/local/tmp/aboot.img
cd /data/local/tmp
chmod 755 loki_patch
chmod 755 loki_flash
./loki_patch recovery aboot.img recovery.img recovery.lok
./loki_flash recovery recovery.lok
I can't say for sure this method works as i still havent managed to compile a working CWM but at least it flashes without error.

obiwan86300 said:
adb push loki_flash /data/local/tmp/loki_flash
adb push loki_patch /data/local/tmp/loki_patch
adb push recovery.img /data/local/tmp/recovery.img
adb shell
su
dd if=/dev/block/platform/msm_sdcc.1/by-name/aboot of=/data/local/tmp/aboot.img
cd /data/local/tmp
chmod 755 loki_patch
chmod 755 loki_flash
./loki_patch recovery aboot.img recovery.img recovery.lok
./loki_flash recovery recovery.lok
I can't say for sure this method works as i still havent managed to compile a working CWM but at least it flashes without error.
Click to expand...
Click to collapse
Excellent. So since that works without an error, once we get a working CWM we should be set.

mustbepbs said:
Excellent. So since that works without an error, once we get a working CWM we should be set.
Click to expand...
Click to collapse
Hello guys, wednesday I will have in my hands the G Pad..
I practiced a lot of modding on my N7000, but I've never created anything personal on my smartphone.
I wanted to know what is missing, until now, in order to start modding our G Pad.
LG has released the firmware or am I wrong? What is missing to create custom rom starting from the stock firmware?
thanks :victory:

Palux said:
Hello guys, wednesday I will have in my hands the G Pad..
I practiced a lot of modding on my N7000, but I've never created anything personal on my smartphone.
I wanted to know what is missing, until now, in order to start modding our G Pad.
LG has released the firmware or am I wrong? What is missing to create custom rom starting from the stock firmware?
thanks :victory:
Click to expand...
Click to collapse
We're missing recovery. We've got a bootloader workaround with LOKI and we've got the stock source. We just need a working recovery.

thank you for the reply,
so, for example, if coming out a version of CWM you could do it all, in total security (because now you can do the root but do not go back, right?) ?

Palux said:
thank you for the reply,
so, for example, if coming out a version of CWM you could do it all, in total security (because now you can do the root but do not go back, right?) ?
Click to expand...
Click to collapse
.. Not quite sure what you mean.
We've already got a way to restore stock even if we manage a soft brick.

mustbepbs said:
We've already got a way to restore stock even if we manage a soft brick.
Click to expand...
Click to collapse
ok, I'd missed this step.
so just missing a good recovery worthy of note. hopefully good
thanks

LS980ZVA - All you need to know!

Thanks to @Shelnutt2 if you took the ZVA ota and you want a custom recovery, FreeGee from the play store now supports automatically downgrading your bootloader and installing a recovery!
If you want a ZVA radio on an AOSP ROM, you can use the latest AOSP builds of dr87's kernel or Furnace to work.
No more downgrading radio to ZV8 for AOSP ROMs
Before I step into the details, here's a little history..
WARNING: If you don't understand adb or root, then you shouldn't even be here, you probably shouldn't have even rooted. Make sure you COMPLETELY understand this post before doing ANYTHING. I'm using caps like a wild maniac because if you do something out of order or you do something wrong you WILL brick your device, and you have to use a .tot to bring yourself back to stock. The kind of brick you could create here kills your boot and recovery partitions. Be careful.
Code:
LS980ZV7 (Initial Release)
LS980ZV8 (Security Update)
LS980ZVA (Sprint Spark and loki-killer)
Loki: Our device uses a bootloader called an "aboot" which must validate the boot and recovery partitions before they can be booted.
We are allowed to use custom boot images (ROMs + Kernels) and recoveries because of loki. Loki is a program that patches our "Unoffical" boot or recovery images before they are installed, this is usually done in the .zip during flash, which is why most people don't worry about it.
LS980ZVA (Spark Update)
This update does 2 major things, patch loki, and add tri-band capabilities.
If you take the update, you will NOT loose the ability to ever use a custom ROM. We just need to downgrade the "aboot" to the exploitable ZV7 aboot.
You can find that "aboot" here -> zv7-aboot
After rooting, (use ioroot21) you can put the zv7-aboot.img on your sdcard, and open terminal emulator. Issue this command:
Code:
dd if=/path/to/your/zv7-aboot.img of=/dev/block/platform/msm_sdcc.1/by-name/aboot
(You can also use adb if you prefer)
After you have downgraded your aboot, you will need a custom recovery. Download Flashify off the Google Play market (or use FreeGee to make the process faster) and place this file on your sdcard. twrp_2.6.3.3_loki-ls980.img
Open flashify, select recovery image, and find that .img, I have already loki'd this image, so you don't need to worry about it not working. Just be sure that you have downgraded your aboot first!
At the moment, the ZVA radio that came with your ota has completely broken compatability with all other non-ZVA ROMs, so if you want to install CM/PA/AOKP/DerpG2/OptimusDE, you will need to downgrade your radio to non-Spark ZV8/7, just flash this file in your newly installed recovery.
Now you're safe to flash any ROM!
AOSP/LS980ZV8/7
If you want to try the new radio (Spark), there's some things you need to be aware of, (when available) flashing youdug's stock ZVA ROM will NOT give you spark out of the box. You will need the new ZVA radio for this. You can find that here
You can only use twrp to install this radio. And it will ONLY work on ZVA ROMS. Do NOT install this radio over CM/PA, you will brick.
After you have verified that you are running a ZVA ROM, you have flashed the radio, and you notice no errors, you may boot.
Notice, your bootloader is now loki-proof, and your recovery will no longer work. if you wan't to go back to AOSP or any other non-ZVA ROM, you MUST first flash the ZV8 Radio so that your ROM will boot.
Also, do not flash a ZV8 radio over a ZVA radio if you have already booted into a ZVA ROM. Only install the ZV8 radio before flashing a ZVA ROM or before switching to a non-ZVA ROM.
Devs working on the ZVA update: If you're including a custom kernel that modify's the official ZVA boot.img, you will need to include a few lines in your updater-script that patches the ZV7 aboot over the ZVA aboot. Then you can add the lines to loki your boot.img. We have to assume that the user is flashing your ROM on either radio. If you don't patch the aboot, the ZVA radio that the user "may" flash will not pass the boot.img from your ROM and the boot will fail, followed by the custom recovery. If you aren't careful, you WILL brick users.
Again, do NOT flash the radio before flashing the ZVA ROM, you WILL brick if you try to boot. Flash the ZVA ROM, verify that it boots, then flash the ZVA radio. If you want to go back to AOSP, follow the Spark guide above.
Thanks for help figuring this one out to @autoprime @garwynn @Shelnutt2 @Dougie2187​
Click to expand...
Click to collapse

So if u don't have spark in ur area what's the benefits? Thanks

Did you really need to quote the whole OP? I don't think it's worth it if you are not in a Spark area.
Sent from my LG-LS980 using xda app-developers app

chazglenn3 said:
Did you really need to quote the whole OP? I don't think it's worth it if you are not in a Spark area.
Sent from my LG-LS980 using xda app-developers app
Click to expand...
Click to collapse
I've seen much longer quotes quoted. Anyway so there's no benefit...cuz its only launched in 11 cities. although I'm getgi g late from band 25 and 41 not 26 though. I enables them.....

Good job at explaining these issues, thanks.
Sent from my LG-LS980 using Tapatalk

If you're not in a Spark area, don't even bother. You're temporarily flashing to a non-exploitable aboot and you have to downgrade to go back to any other non-ZVA rom.
What I like to do is flash the ZV8 radio and then the ZVA ROM, that way I don't need to mess with my aboot and I can go flash AOSP whenever I want.

Savoca said:
If you're not in a Spark area, don't even bother. You're temporarily flashing to a non-exploitable aboot and you have to downgrade to go back to any other non-ZVA rom.
What I like to do is flash the ZV8 radio and then the ZVA ROM, that way I don't need to mess with my aboot and I can go flash AOSP whenever I want.
Click to expand...
Click to collapse
Perfectly said and Thank you (in words, not just XDA thanks) for this.
Sent from my LG-LS980 using Tapatalk

Savoca said:
After rooting, (use ioroot21) you can put the zv7-aboot.img on your sdcard, and open terminal emulator. Issue this command:
Code:
dd if=/path/to/your/zv7-aboot.img of=/dev/block/platform/msm_sdcc.1/by-name/aboot
(You can also use adb if you prefer)
After you have downgraded your aboot, you will need a custom recovery. Download Flashify off the Google Play market (or use FreeGee to make the process faster) and place this file on your sdcard. twrp_2.6.3.3_loki-ls980.img
Open flashify, select recovery image, and find that .img, I have already loki'd this image, so you don't need to worry about it not working. Just be sure that you have downgraded your aboot first!
Click to expand...
Click to collapse
Was just curious if these instructions work for adb to flash zv7-aboot.img on your PC. Can you confirm if this works? I just think its just easier to flash the zv7-aboot.img on your PC since you can copy and paste the command into command prompt than have to type it manually on the terminal emulator on your phone. I think its less prone for error.
Alternative method to flash zv7-aboot.img using ADB method for Windows users. Should be similar steps for Mac users using a terminal window.
Download the zv7-aboot.img file and place the zv7-aboot.img in the ioroot 21 folder location.
Hold shift and right click in a blank area of the ioroot 21 folder on your PC and select "open command window here"
Type adb push zv7-aboot.img /sdcard/
Type adb shell
(If you do not see a # type su and hit enter so that you see the #)
Type dd if=/sdcard/zv7-aboot.img of=/dev/block/platform/msm_sdcc.1/by-name/aboot

Stock Rooted with TWRP
I am so sorry if this is a noob question but can I take this Spark update on my stock rooted with TWRP and then use this method to restore root and recovery. And will my phone still have all my apps. I will make a backup and transfer it to the PC though Thanks

UCLA1 said:
I am so sorry if this is a noob question but can I take this Spark update on my stock rooted with TWRP and then use this method to restore root and recovery. And will my phone still have all my apps. I will make a backup and transfer it to the PC though Thanks
Click to expand...
Click to collapse
You're good. But if you've ever uninstalled a system app the OTA will fail.

Savoca said:
You're good. But if you've ever uninstalled a system app the OTA will fail.
Click to expand...
Click to collapse
Just wondering if update fail do you have to go back to stock.
In the other thread right by this one their are two updates that what im talking about.
Thanks
Sent from my LG-LS980 using xda premium

Need help
i had a stock rom with twrp rooted and ran the update but it sent me to TWRP. I tried doing a nandroid restore but after i reboot the system it still sends me back to TWRP what can i do?

rvalenzuel9 said:
i had a stock rom with twrp rooted and ran the update but it sent me to TWRP. I tried doing a nandroid restore but after i reboot the system it still sends me back to TWRP what can i do?
Click to expand...
Click to collapse
Which did you flash update
Sent from my LG-LS980 using xda premium

i clicked the notification that said to install the VZA update

rvalenzuel9 said:
i clicked the notification that said to install the VZA update
Click to expand...
Click to collapse
if you tried to take the ota and it failed you wouldn't have needed to restore a nandroid. You could have just rebooted and nothing would have changed.
you'll have to sideload a new rom.

i tried it again and it went back to TWRP, im not sure why
can you please help me with that?

rvalenzuel9 said:
i tried it again and it went back to TWRP, im not sure why
can you please help me with that?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=49812199&postcount=58

WORKEDDD!! Thanks alott!

Hello so I also was stock rooted took the ota and it's been stuck on the Sprint boot logo with the fancy spark emblem all day I don't know what to do because I do not any longer have a recovery some help ,direction prayer all that would be much apreciated thanks.

Geezio said:
Hello so I also was stock rooted took the ota and it's been stuck on the Sprint boot logo with the fancy spark emblem all day I don't know what to do because I do not any longer have a recovery some help ,direction prayer all that would be much apreciated thanks.
Click to expand...
Click to collapse
Geez.... Did you read any of the posts right above yours? Need to try somethings out that others have and look in other threads.
Sent from my LG-LS980 using Tapatalk

[Q] Rooting on 4.3

Hello all,
I recently got my hands on a Note 2 running Android 4.3 on the MK6 bootloader. I have done a bit of research, but am still somewhat confused about how to root the phone. If I am correct, I just use Odin to flash this:
http://forum.xda-developers.com/showthread.php?t=2589891
Onto the phone to have root access, correct?
Next, if I want to have CWM, I flash this:
http://forum.xda-developers.com/showthread.php?t=2159652
If there are any steps I am missing, please let me know. I would like to procede with as much knowledge as possible to avoid bricking the phone. I am aware that doing this will trip the Knox e-fuse, and I am ok with that.
Thanks in advance!

Luigiman765 said:
Hello all,
I recently got my hands on a Note 2 running Android 4.3 on the MK6 bootloader. I have done a bit of research, but am still somewhat confused about how to root the phone. If I am correct, I just use Odin to flash this:
http://forum.xda-developers.com/showthread.php?t=2589891
Onto the phone to have root access, correct?
Next, if I want to have CWM, I flash this:
http://forum.xda-developers.com/showthread.php?t=2159652
If there are any steps I am missing, please let me know. I would like to procede with as much knowledge as possible to avoid bricking the phone. I am aware that doing this will trip the Knox e-fuse, and I am ok with that.
Thanks in advance!
Click to expand...
Click to collapse
#1 is a full ROM like you have but rooted.
Try this
http://download.chainfire.eu/280/CF...uto-Root-t0lteatt-t0lteatt-samsungsghi317.zip
#2 is good. You need to do that before doing number 1.
http://goo.im/devs/philz_touch/CWM_Advanced_Edition/t0lteatt
philz_touch_6.15.4-t0lteatt.tar.md5
Flash via ODIN http://d-h.st/N1V

dicksteele said:
#1 is a full ROM like you have but rooted.
Try this
http://download.chainfire.eu/280/CF...uto-Root-t0lteatt-t0lteatt-samsungsghi317.zip
#2 is good. You need to do that before doing number 1.
http://goo.im/devs/philz_touch/CWM_Advanced_Edition/t0lteatt
philz_touch_6.15.4-t0lteatt.tar.md5
Flash via ODIN http://d-h.st/N1V
Click to expand...
Click to collapse
Alright, thanks!
So I flash the CF Auto Root via Odin, then CWM, and then I can flash any ROM, right?
Thanks for the help

Luigiman765 said:
Alright, thanks!
So I flash the CF Auto Root via Odin, then CWM, and then I can flash any ROM, right?
Thanks for the help
Click to expand...
Click to collapse
Yes. For now stick with ROMs in here.
http://forum.xda-developers.com/galaxy-note-2-att/development
Here's a guide for TWRP recovery
http://www.addictivetips.com/android/what-is-twrp-how-to-install-use-it-on-android-devices-guide/
Download is here to flash in ODIN
http://goo.im/devs/OpenRecovery/t0lteatt/openrecovery-twrp-2.6.3.1-t0lteatt.img.tar
It's a little easier to use to start.
Always make backups !!!

So, today I tried to root my phone, and as soon as I was finished flashing CF Auto Root, Knox blocked the root and said that "Unauthorized access to a secured area has been blocked."
Does that mean I cannot root my phone?

Luigiman765 said:
So, today I tried to root my phone, and as soon as I was finished flashing CF Auto Root, Knox blocked the root and said that "Unauthorized access to a secured area has been blocked."
Does that mean I cannot root my phone?
Click to expand...
Click to collapse
No you're fine. Go to Google Play, Download the Update for SuperSU. Update it, it will pop up a window and ask if you want to disable Knox.
SAY YES !

dicksteele said:
No you're fine. Go to Google Play, Download the Update for SuperSU. Update it, it will pop up a window and ask if you want to disable Knox.
SAY YES !
Click to expand...
Click to collapse
Thanks for the answer, but there is no option to update SuperSU from Google Play, and I can't uninstall it either.
Is there a direct link where I can download the file to update the SuperSU to disable Knox?

Luigiman765 said:
Thanks for the answer, but there is no option to update SuperSU from Google Play, and I can't uninstall it either.
Is there a direct link where I can download the file to update the SuperSU to disable Knox?
Click to expand...
Click to collapse
Login to Google on your PC.
Try going here.
https://play.google.com/store/apps/details?id=eu.chainfire.supersu&hl=en
It should say Installed. Click the Installed button, make sure phone is listed. See if it will install from there.

dicksteele said:
Login to Google on your PC.
Try going here.
https://play.google.com/store/apps/details?id=eu.chainfire.supersu&hl=en
It should say Installed. Click the Installed button, make sure phone is listed. See if it will install from there.
Click to expand...
Click to collapse
Hmm, unfortunately it says that it is already installed on the phone I am trying to root, and I can't install it again

Luigiman765 said:
Hmm, unfortunately it says that it is already installed on the phone I am trying to root, and I can't install it again
Click to expand...
Click to collapse
It should say installed. When you click it another window pops up. It should list your phone. Just click install button.
If that does not work go to Application Manager and try and remove it.

dicksteele said:
It should say installed. When you click it another window pops up. It should list your phone. Just click install button.
If that does not work go to Application Manager and try and remove it.
Click to expand...
Click to collapse
Yeah, I clicked the "Installed," but I cannot click on the phone that I have this on, it says already installed
And I can't uninstall it from Appilcation Manager, just "Force Stop" or "Turn Off"
I am very stuck unfortunately ):

Luigiman765 said:
Yeah, I clicked the "Installed," but I cannot click on the phone that I have this on, it says already installed
And I can't uninstall it from Appilcation Manager, just "Force Stop" or "Turn Off"
I am very stuck unfortunately ):
Click to expand...
Click to collapse
Interesting. I've never seen that before. And I really just saw it because mine is doing the same thing.....
Try flashing via ODIN
http://download.chainfire.eu/280/CF...uto-Root-t0lteatt-t0lteatt-samsungsghi317.zip
Or is that the one you did?
EDIT:
I just uninstalled my updates and flashed this. Worked for me.
http://download.chainfire.eu/382/SuperSU/UPDATE-SuperSU-v1.93.zip
Not saying it's going to work, should really. It's the lastest.

dicksteele said:
Interesting. I've never seen that before. And I really just saw it because mine is doing the same thing.....
Try flashing via ODIN
http://download.chainfire.eu/280/CF...uto-Root-t0lteatt-t0lteatt-samsungsghi317.zip
Or is that the one you did?
EDIT:
I just uninstalled my updates and flashed this. Worked for me.
http://download.chainfire.eu/382/SuperSU/UPDATE-SuperSU-v1.93.zip
Not saying it's going to work, should really. It's the lastest.
Click to expand...
Click to collapse
Thanks for the research, so I should try flashing that via recovery?

Yes. That's the latest version
Sent from my stuff using xda app-developers app

dicksteele said:
Yes. That's the latest version
Sent from my stuff using xda app-developers app
Click to expand...
Click to collapse
Agh, still nothing - I can't uninstall SuperSU and flashing did not help; Knox still is working.
Should I just wipe from recovery first?

Luigiman765 said:
Agh, still nothing - I can't uninstall SuperSU and flashing did not help; Knox still is working.
Should I just wipe from recovery first?
Click to expand...
Click to collapse
Whole lotta WTF. I'm now running into the same issue with the Note2_lte_e250_R7. 2 ROM I flashed.
Everything I have tried is not getting root to stick. I will kick it's a$$.
Trying a couple more things. I'll let you know when I succeed.
---------- Post added at 12:46 PM ---------- Previous post was at 12:08 PM ----------
May have found something....
Koushik Dutta
https://plus.google.com/u/0/110558071969009568835/posts/YsXBtjuD6rD
Superuser installation issues after installing over SuperSU
It seems SuperSU is writing a file that is confusing Superuser installation on stock builds. If you want to install Superuser over SuperSU, you will need to manually remove the /system/etc/.has_su_daemon file.
I have the /system/etc/.has_su_daemon file.l I'm creating a CWM zip to remove it.
Hopefully that's the solution.

dicksteele said:
Whole lotta WTF. I'm now running into the same issue with the Note2_lte_e250_R7. 2 ROM I flashed.
Everything I have tried is not getting root to stick. I will kick it's a$$.
Trying a couple more things. I'll let you know when I succeed.
---------- Post added at 12:46 PM ---------- Previous post was at 12:08 PM ----------
May have found something....
Koushik Dutta
https://plus.google.com/u/0/110558071969009568835/posts/YsXBtjuD6rD
Superuser installation issues after installing over SuperSU
It seems SuperSU is writing a file that is confusing Superuser installation on stock builds. If you want to install Superuser over SuperSU, you will need to manually remove the /system/etc/.has_su_daemon file.
I have the /system/etc/.has_su_daemon file.l I'm creating a CWM zip to remove it.
Hopefully that's the solution.
Click to expand...
Click to collapse
And it wasn't ..... I created a flashable zip that deleted them and it didn't work.
But I did kick it's a$$.
Like I said earlier I running the 【ROM】【March 01】【4.3】Note2_lte_e250_R7. 2 . It's a N7105 port for the ATT.
So I knew there was something called a Multitool in the N7105 threads from Dr Ketan.
I flashed that in TWRP, it's an aroma install type flash, so I only choose Root and install Busybox.
Like all of our other flash installs it looked like it completed successfully.
Every flash or ODIN I've done or most today, I've gotten into adb shell and did
ls -l /system/xbin/su. never saw the file.
After flashing root and busybox I finally saw
[email protected]:/ $ ls -l /system/xbin/su
-rwxr-xr-x root root 100452 2008-08-01 05:00 su
Woo Hoo !
Got into phone, ran supersu, still said no binary.
Not sure why I did this really buy I typed su while in adb shell, Supersu window popped up on my phone, I clicked accept and all root stuff is working.
I have no clue why this worked. But it did, for me anyways. Hopefully it'll work for you, Luigi.

dicksteele said:
And it wasn't ..... I created a flashable zip that deleted them and it didn't work.
But I did kick it's a$$.
Like I said earlier I running the 【ROM】【March 01】【4.3】Note2_lte_e250_R7. 2 . It's a N7105 port for the ATT.
So I knew there was something called a Multitool in the N7105 threads from Dr Ketan.
I flashed that in TWRP, it's an aroma install type flash, so I only choose Root and install Busybox.
Like all of our other flash installs it looked like it completed successfully.
Every flash or ODIN I've done or most today, I've gotten into adb shell and did
ls -l /system/xbin/su. never saw the file.
After flashing root and busybox I finally saw
[email protected]:/ $ ls -l /system/xbin/su
-rwxr-xr-x root root 100452 2008-08-01 05:00 su
Woo Hoo !
Got into phone, ran supersu, still said no binary.
Not sure why I did this really buy I typed su while in adb shell, Supersu window popped up on my phone, I clicked accept and all root stuff is working.
I have no clue why this worked. But it did, for me anyways. Hopefully it'll work for you, Luigi.
Click to expand...
Click to collapse
Thanks for all the info!
So, let me get this straight:
I don't need the ROM you're running on my phone. What I should do is find the Multitool, flash it via recovery, and root and Busybox. Then, connect my phone to my computer to run adb (which I don't really know how to do, so I'll have to look that up), type in su, and then from there everything should work as normal.
Also, an extra piece of information I forgot to mention earlier that you might find useful: SuperSU does NOT start at all; it just immediately closes when I click the icon, and then the Knox warning comes up. Did this happen for you?

Luigiman765 said:
Thanks for all the info!
So, let me get this straight:
I don't need the ROM you're running on my phone. What I should do is find the Multitool, flash it via recovery, and root and Busybox. Then, connect my phone to my computer to run adb (which I don't really know how to do, so I'll have to look that up), type in su, and then from there everything should work as normal.
Also, an extra piece of information I forgot to mention earlier that you might find useful: SuperSU does NOT start at all; it just immediately closes when I click the icon, and then the Knox warning comes up. Did this happen for you?
Click to expand...
Click to collapse
Really have no clue.All I know is it worked for me.
For me SuperSU opened all he way. It told me I didn't have the su binary, do a manually install. Everything I did, did not work until my last post. 99% sure it will work for you.
For ADB use this....
http://four-nineteen.com/veronica/XDA Developers/Nook Tablet/DRIVERs/ADB + Fastboot + Drivers.zip
Unzip and save only the files that start with ADB. Create a directory like ADB under C:\.
Copy all the ADB files to C\ADB
Go to command prompt in windows, cd to c:\adb directory (whatever you created)
Type adb devices. Make sure it has a device listed
C:\xUltimate-v2.4.2\jar>adb devices
List of devices attached
8675309JennieJennie device
If so, type adb shell
C:\xUltimate-v2.4.2\jar>adb shell
[email protected]:/ $
_______________________________________________________________________________
Just found something else that works.... I've tried it also.
Flash the AGNI kernel. (Awesome addition to a ROM)
https://app.box.com/s/9wlk6y1o50gbhmhvjp2u
Credit to @mjohnson4580 for fix.
Then flash the root update.
http://download.chainfire.eu/382/SuperSU/UPDATE-SuperSU-v1.93.zip
See what that does.
Here's info in the kernel
http://forum.xda-developers.com/showthread.php?t=2602053
Aweome work by psndna88