*** DISCLAIMER ***
I AM NOT RESPONSIBLE IF YOU MESS UP YOUR PHONE! OR IF YOU LOSE ANY DATA, ITS CALLED BACK IT UP BEFORE HAND!
Word to the wise if you don't know how to use RSDLite or Fastboot to restore your phone then leave this thread now please! I will not attempt to simplify this down anymore. Safestrap users you need to backup everything on your internal storage before you install this, to switch back to 4.2.2 possibly 4.4/4.4.2 you will have to RSD back to stock. This ROM has to be flashed to the STOCK SLOT in Safestrap and the 4.4.4 KitKat Kernel and Baseband has to be flashed for it to work. YOU'VE BEEN WARNED!
Okay this is a stock unmodified(3c_ota.apk is the only apk removed) rooted rom based off of the 4.4.4 KitKat SBF thanks to SamuriHL with full Safestrap functionality. You will need to have the phone's drivers installed to get this working, so click the link below to download them and install them before you start. https://motorola-global-portal.custhelp.com/app/answers/prod_detail/a_id/94931/p/30,6720,8696
Instructions to install this rom for Safestrap Users, you will need to download the ROM and my Kernel/Radio Flashing Utility, and read every step before you start...
1. Before you do anything you need to be rooted on 4.2.2 or 4.4, write protection disabled with MotoWpNoMo and Safestrap Recovery installed
2. Reboot into Safestrap Recovery
3. Factory Reset the STOCK SLOT(do not ask about another slot) in Safestrap, also DO NOT wipe or manually mount the /system it can cause symlink errors
4. Flash my ROM zip to the STOCK SLOT (this will take a couple minutes, go grab a drink or something)
5. Once the ROM has finished flashing, press the home button, then press the reboot button, then press the bootloader button to reboot to the bootloader from within Safestrap
6. Plug up your Moto X via usb cable to your computer, once plugged in the Bootloader screen should say usb connected now
7. Unzip the "Moto X Kernel and Radio Flasher.zip"
8. Open the extracted folder and find FlashMyMotoX.bat and double click on it
9. Choose option 10 within the FlashMyMotoX utility to flash the 4.4.4 KitKat Kernel
10. Once it finishes get back to the options and choose option 11 this will flash the 4.4.4 KitKat Baseband
11. Once it finishes successfully unplug your usb cable and reboot the phone
12. Enjoy 4.4.4 KitKat!
For Unlocked Users
1. Boot into TWRP 2.7.1.1 (recommended that's what I use) factory reset DO NOT wipe or manually mount the /system it can cause symlink errors, then install the ROM.
2. If you were on 4.4.4 already then reboot and enjoy if you aren't on 4.4.4 then continue to step 9.
3. Once done installing reboot to the bootloader from within TWRP.
4. Once on the bootloader screen plug your usb cable into your Moto X the screen should say usb connected.
5. Unzip the "Moto X Kernel and Radio Flasher.zip"
6. Open the extracted folder and find FlashMyMotoX.bat and double click on it
7. Choose option 11 within the FlashMyMotoX utility to flash the 4.4.4 KitKat Baseband
8. Once it finishes successfully unplug your usb cable and reboot the phone
9. Enjoy 4.4.4!
Downloads: DO NOT repost links on other forums, link them to this thread!
Safestrap ROM zip MD5: 22291bcae0f5043477a91e4d09a9bf7e
Moto X Kernel & Radio Flashing Utility MD5: b8ac849d0ba52b2d3c9563a5a2c9cb22
Unlocked ROM zip MD5: 1c214fa8e55cf22c6366c0d563a32f44
Thanks to Google for Android and their Search engine, Hashcode for Safestrap, jcase for his roots, beaups and fuses for MotoWpNoMo, TeamWin for TWRP 2.7.1.1, and the Chinese middle man for my bootloader unlock without them this wouldn't be possible!
Reserved
Awesome job! Much thanks!
"Are you asking about the stock version? The entitlement hack will be in my updated version of Krypton but not in my stock 4.4.4 rom. All you have to do is add net.tethering.noprovisioning=true to the build.prop before you flash the rom, and that will bypass the entitlement check."
Does it matter where I add this in the build prop?
Hey kryptonite, FYI titanium back says I have no root, even tho I do. Any suggestions?
Sent from my XT1060 using XDA Premium 4 mobile app
rebretz000 said:
"Are you asking about the stock version? The entitlement hack will be in my updated version of Krypton but not in my stock 4.4.4 rom. All you have to do is add net.tethering.noprovisioning=true to the build.prop before you flash the rom, and that will bypass the entitlement check."
Does it matter where I add this in the build prop?
Click to expand...
Click to collapse
Nah it shouldn't, I normally just add all my lines in the section near the top, up under the device info properties.
ghostt021 said:
Hey kryptonite, FYI titanium back says I have no root, even tho I do. Any suggestions?
Sent from my XT1060 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
What in the world, I wonder why titanium is trying to call /system/bin/su instead of /system/xbin/su hmm. Are you unlocked or safestrapped?
iKrYpToNiTe said:
Nah it shouldn't, I normally just add all my lines in the section near the top, up under the device info properties.
What in the world, I wonder why titanium is trying to call /system/bin/su instead of /system/xbin/su hmm. Are you unlocked or safestrapped?
Click to expand...
Click to collapse
Unlocked. I had this happen before on different stock rom
Sent from my XT1060 using XDA Premium 4 mobile app
ghostt021 said:
Unlocked. I had this happen before on different stock rom
Sent from my XT1060 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Hmm I just looked through TB's settings to see if there was a setting to set where su is called from but I couldn't find any. Try flashing SuperSU's zip and see if that clears up the problem. If it doesn't try uninstalling TB and reinstalling it.
ghostt021 said:
Unlocked. I had this happen before on different stock rom
Sent from my XT1060 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
that happened to me but i didn't give permission in the time allowed. just unistalled TB and reinstalled it.
Probably not your issue but worth a shot
ghostt021 said:
Unlocked. I had this happen before on different stock rom
Sent from my XT1060 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Wow. That worked. Thx bro.
Sent from my XT1060 using XDA Premium 4 mobile app
4.4.4 running very well so far with newer radio flashed. Will your 005 kernel be worth a shot or would it not be a good idea on 4.4.4?
Been running this for about six now, with no complaints what so ever no the old radio, anyone notice a difference enough to flash?
Sent from my XT1060 using XDA Premium 4 mobile app
ConstantHero said:
4.4.4 running very well so far with newer radio flashed. Will your 005 kernel be worth a shot or would it not be a good idea on 4.4.4?
Click to expand...
Click to collapse
I actually haven't tried, Moto dropped the kernel source I've just got to sync the repo and add my changes.
ghostt021 said:
Been running this for about six now, with no complaints what so ever no the old radio, anyone notice a difference enough to flash?
Sent from my XT1060 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Seems about the same to me signal strength wise, but calls seem clearer may be a placebo affect though.
iKrYpToNiTe said:
I actually haven't tried, Moto dropped the kernel source I've just got to sync the repo and add my changes.
Seems about the same to me signal strength wise, but calls seem clearer may be a placebo affect though.
Click to expand...
Click to collapse
OK. Thx. I may just wait for your modified ROM.
Sent from my XT1060 using XDA Premium 4 mobile app
Hi,
I am on 4.4.3 T-mobile XT1053.unlocked ,twrp 2.6.3.1 installed but previously i was X1052 indian variant, Should i try to flash this?
rahulcuthber91 said:
Hi,
I am on 4.4.3 T-mobile XT1053.unlocked ,twrp 2.6.3.1 installed but previously i was X1052 indian variant, Should i try to flash this?
Click to expand...
Click to collapse
So which model phone do you actually have, not what version rom your running?
@iKrYpToNiTe Should I test this on the Roger's XT1058?
XAlexander_AlexanderX said:
@iKrYpToNiTe Should I test this on the Roger's XT1058?
Click to expand...
Click to collapse
If you're unlocked try it, you might not have data with this rom though.
iKrYpToNiTe said:
So which model phone do you actually have, not what version rom your running?
Click to expand...
Click to collapse
I am using moto x XT1052 indian variant.unlocked
iKrYpToNiTe said:
If you're unlocked try it, you might not have data with this rom though.
Click to expand...
Click to collapse
Tadaaaaaaaaaaaaa
I have dataaaaaaa. Cant test speeds though as i dont have a data plan. It switches from 3G/H+ when making a call and back to LTE successfully. Data works as it loads T-Mobiles website.
Related
We've tested and can confirm this bootstrap recovery is working. Thank you to bane449 for testing. The recovery is a straight APK pull from the Droid X2. Worked thanks to the similarities between devices.
Instructions and download:
http://briefmobile.com/motorola-photon-4g-root-custom-recovery-now-available
Looks successful to me: DroidX2 Recovery GFAN.COM V2.5.1.8
And it booted back into Android properly, even
So what will this allow me to do? What are its advantages? What are the risks?
sub2k1 said:
So what will this allow me to do? What are its advantages? What are the risks?
Click to expand...
Click to collapse
CWM allows users to easily install unsigned update packages. This will open up the Photon to pseudo-ROMs, all sorts of modifications, and more.
Forgive my ignorance but what is a "pseudo-Rom"?
kennethpenn said:
CWM allows users to easily install unsigned update packages. This will open up the Photon to pseudo-ROMs, all sorts of modifications, and more.
Click to expand...
Click to collapse
Sent from my MB855 using XDA App
10 chars
I know what ROM's are, never heard anyone say psuedo-ROM.
Lokifish Marz said:
Custom ROMs (if available for the Photon) like MIUI, CM7 etc...
Click to expand...
Click to collapse
Sent from my MB855 using XDA App
mikeyinid said:
I know what ROM's are, never heard anyone say psuedo-ROM.
Sent from my MB855 using XDA App
Click to expand...
Click to collapse
Psuedo meaning "not really" a ROM. A locked bootloader will prevent true custom ROMs, but P-ROMs will be possible.
P-ROMs are based off of stock files and modifications. They don't replace the kernel or modem.
Yup i installed this and rebooted into recovery mode. It worked just fine for me. What happens if Sprint releases an OTA update? Can i recover root access or downgrade with this? Sounds like I can't because I can't modify the kernel.
Sent from my MB855 using XDA Premium App
I can't seem to get mine to reboot into CWM. I run the apk, hit install recovery, says installed sucessfully, hit recovery mode and it reboots back into system.
b-reezy said:
I can't seem to get mine to reboot into CWM. I run the apk, hit install recovery, says installed sucessfully, hit recovery mode and it reboots back into system.
Click to expand...
Click to collapse
Make sure your device is plugged into the wall charger when you do Reboot Recovery. That's the only way it'll work since it's a bootstrap recovery.
kennethpenn said:
Make sure your device is plugged into the wall charger when you do Reboot Recovery. That's the only way it'll work since it's a bootstrap recovery.
Click to expand...
Click to collapse
Can you explain why this is? I'm a little confused as to what makes a "bootstrap recovery" different from a regularly flashed "recovery.img".
brianez21 said:
Can you explain why this is? I'm a little confused as to what makes a "bootstrap recovery" different from a regularly flashed "recovery.img".
Click to expand...
Click to collapse
Caveats:
This is not a *real* recovery. The way this recovery works is by hijacking portions of your boot process during system initialization and starting into recovery instead. So, if you hose your system *COMPLETELY* you will need to SBF. Specifically, if your logwrapper, logwrapper.bin, or hijack binary are missing from /system/bin, you will be screwed.
This is from koush himself concerning droid x/2 bootstrap. I would seriously wait til an sbf surfaces before flashing any of these "psuedo-ROMS" or even just deleting any system apk's. Just my opinion.
sub2k1 said:
Yup i installed this and rebooted into recovery mode. It worked just fine for me. What happens if Sprint releases an OTA update? Can i recover root access or downgrade with this? Sounds like I can't because I can't modify the kernel.
Sent from my MB855 using XDA Premium App
Click to expand...
Click to collapse
Does the phone need to be rooted first in order to installl this recovery apk?
Is this "ClockworkMod" recovery, or something else? If it's CWM, what version?
So what specifically did this do to my phone? What files were modified to allow this to run at bootup? Anybody have any info on this (just in case I want to return my phone to stock.)
mediawiz said:
Is this "ClockworkMod" recovery, or something else? If it's CWM, what version?
Click to expand...
Click to collapse
This is CWM bootstrap. Original one was on the Droid X, created by Koushik Dutta. Then it was ported to the Defy. Then to the Atrix. Next, the Droid X2. Now, the Photon 4G.
V2.5.1.8
Sbf is gonna be your friend when it comes to unrooting and restoring. It will pop up soon.
sub2k1 said:
So what specifically did this do to my phone? What files were modified to allow this to run at bootup? Anybody have any info on this (just in case I want to return my phone to stock.)
Click to expand...
Click to collapse
Sent from my MB855 using XDA App
Once I'm in CWM, is it safe to unplug the charger or does it need to be connected until I exit and reboot?
beartrap said:
Once I'm in CWM, is it safe to unplug the charger or does it need to be connected until I exit and reboot?
Click to expand...
Click to collapse
You can unplug.
Sent from the best phone yet!
Hello I bought a rooted note 2 and when I go to flash a new rom it always fails. Do I need to unroot go srock and re root?
Sent from my SCH-I605 using xda app-developers app
phatchef1 said:
Hello I bought a rooted note 2 and when I go to flash a new rom it always fails. Do I need to unroot go srock and re root?
Sent from my SCH-I605 using xda app-developers app
Click to expand...
Click to collapse
Rooting doesn't give you the ability to flash ROMs, you have to have the bootloader unlocked and have a custom recovery such as twrp or cwm.
Thought you needed it unlocked to have a rom on it to start with. It has the cleanrom se1.5 on it now
Sent from my SCH-I605 using xda app-developers app
phatchef1 said:
Thought you needed it unlocked to have a rom on it to start with. It has the cleanrom se1.5 on it now
Sent from my SCH-I605 using xda app-developers app
Click to expand...
Click to collapse
Ok, you didn't say that you only said it was rooted.
What steps are you taking to flash a new ROM?
You said it fails, what's the failure?
Have you tried going into recovery mode? Turn off your phone, press and hold volume up+home button+and power button till u reach the boot animation then release the buttons. You will either be in cwm or twrp. If you reached this step, then you can flash a rom that is built for your specific note 2 version. From the recovery menus you can follow the necessary steps to install. Let us know what you see.
Ps make sure you do a back up just incase
Sent from my SGH-I317 using xda premium
I can get into recovery mode just when I go to install new rom it fails
Sent from my SCH-I605 using xda app-developers app
What recovery are you running?
phatchef1 said:
I can get into recovery mode just when I go to install new rom it fails
Sent from my SCH-I605 using xda app-developers app
Click to expand...
Click to collapse
What error message are you getting and what steps are you taking. Also what recovery are you using?
Sent from my SCH-I605 using Tapatalk 2
update your recovery...most likely your on the original twrp that came with adams first unlock method.
droidstyle said:
update your recovery...most likely your on the original twrp that came with adams first unlock method.
Click to expand...
Click to collapse
To do this get GooManager from the Play Store, and follow the directions in the description. I believe you press menu and then install a script.
phatchef1 said:
Hello I bought a rooted note 2 and when I go to flash a new rom it always fails. Do I need to unroot go srock and re root?
Sent from my SCH-I605 using xda app-developers app
Click to expand...
Click to collapse
I'd clean the phone up and return it to stock. Start from there.
Also, are you using a custom recovery like twrp or cwm? also, is your BL unlocked?
More info is needed to assist you further, broseph.
droidstyle said:
update your recovery...most likely your on the original twrp that came with adams first unlock method.
Click to expand...
Click to collapse
This is most likely your problem.
BennyJr said:
This is most likely your problem.
Click to expand...
Click to collapse
I didn't update twrp until last week. Prior to that I flashed carbon, rootbox, liquid, beans, eclipse, jedi, and cleanrom.
ok im running clean rom 1.5 and for recovery i have twrp. how do i update the recovery?
geoff5093 said:
To do this get GooManager from the Play Store, and follow the directions in the description. I believe you press menu and then install a script.
Click to expand...
Click to collapse
I'll bump this for you
Sent from my SCH-I605 using Tapatalk 2
ok i updated the twrp. wiped the cache and factory reset and then went to flash a rom and it says FAILED e:sigature verification failed and the next lineerror flashing zip
what did i do wrong? i flashed roms on my old s3 that was rooted this phone just doesnt want to flash roms over
phatchef1 said:
ok i updated the twrp. wiped the cache and factory reset and then went to flash a rom and it says FAILED e:sigature verification failed and the next lineerror flashing zip
what did i do wrong? i flashed roms on my old s3 that was rooted this phone just doesnt want to flash roms over
Click to expand...
Click to collapse
Did you check the md5 and what ROM are you flashing?
Sent from my SCH-I605 using Tapatalk 2
how does a person check the md5 and i have tried the beans11 and jedi10 and both have errors and fail
There is an option in TWRP that makes it look for an MD5 match... but unless you have the MD5 accessible to TWRP it will fail and not install.
Make sure the option is not checked when you go to flash.
To manually check the MD5 yourself to verify your downloads... you need an app on your PC that has the ability. Google will point you right.
Then to check the MD5, you have the app analyze the file and compare it to the MD5 provided in the ROM thread.
thanks unchecked the md5 stuff and it works thanks
I have followed all instructions for flashing carefully. I have tried going back to TWRP 2.7.0.0b I have tried putting ROM zip on internal and external storage. I have rebooted recovery after wiping also tried without wiping. Tried to flash: Beanstalk, Paranoid, Carbon, PAC. All for new partition layout. I am S-off with firewater hboot 2.10.5555. The only ROM that has flashed successfully is Omni. I keep getting this error:
See picture.
Any help or info would be much appreciated.
Sent from my Nexus 5 using XDA Premium 4 mobile app
After wiping did you reboot to recovery before trying to flash again?
HTC Jewel
HBOOT 2.10 S-OFF (rumrunner)
Android 4.3 Sense 5.5 V3
Yes.
Sent from my Nexus 5 using XDA Premium 4 mobile app
I think the ROM you want to flash doesn't seems for your device. Contact the rom developer it looks like the developer doesn't get the assert file correctly.
Try the toggle signature verification option in recovery before installing the rom. Check that the rom is for your device or not. The recovery prevent the user to install any incorrect ROM as it can hard brick your device. So make sure that ROM is for your device or not.
Sent from unnamed ROM using xda premium app
naveen6252 said:
I think the ROM you want to flash doesn't seems for your device. Contact the rom developer it looks like the developer doesn't get the assert file correctly.
Try the toggle signature verification option in recovery before installing the rom. Check that the rom is for your device or not. The recovery prevent the user to install any incorrect ROM as it can hard brick your device. So make sure that ROM is for your device or not.
Sent from unnamed ROM using xda premium app
Click to expand...
Click to collapse
Thanks but I am sure I'm flashing the right ROM for my device. This just started happening recently. I just flashed the newest Omni just posted and that flashes too. Superuser flashes as well as gapps. I thought this might have been related to updating my TWRP to 2.7.0.4b which is why I flashed back to 2.7.0.0b and I got the same errors. Backups restore with out issue as well.
Sent from my EVO using XDA Premium 4 mobile app
Could this possibly be an issue with the firewater hboot?
EVOlved human
Evolution_Freak said:
Could this possibly be an issue with the firewater hboot?
EVOlved human
Click to expand...
Click to collapse
Don't see that being an issue, unless you're on the older partition setup, which it seems you aren't. Have you tried an older version of TWRP that's built for the updated partition setup?
After looking at your picture of the failed flash, it appears that the issue is with the updater script. You can extract all the files and edit the updater script, then zip everything back up. You might also disable signature checking in TWRP if it's enabled. I've run across the same issue using CWM Touch and I usually either revert to TWRP or edit the updater script.
Sent from my EVO LTE
FinZ28 said:
Don't see that being an issue, unless you're on the older partition setup, which it seems you aren't. Have you tried an older version of TWRP that's built for the updated partition setup?
After looking at your picture of the failed flash, it appears that the issue is with the updater script. You can extract all the files and edit the updater script, then zip everything back up. You might also disable signature checking in TWRP if it's enabled. I've run across the same issue using CWM Touch and I usually either revert to TWRP or edit the updater script.
Sent from my EVO LTE
Click to expand...
Click to collapse
Thanks Fin! I will check on the signature checking. I did try going back to 2.7.0.0b but didn't try any older versions. As I said, this just started happening and is only with some ROMs.
Sent from my Nexus 5 using XDA Premium 4 mobile app
Just checked and signature checking was disabled already. I will try your other recommendations next.
EVOlved human
Are those roms that were on your device from before? Or are they all new downloads?
I really suggest rolling ball to TWRP 2.6.3, and see if you have better luck. I have had zero issues, and I have no reason to update TWRP until there's a new feature that I will actually want/need.
aarsyl said:
Are those roms that were on your device from before? Or are they all new downloads?
I really suggest rolling ball to TWRP 2.6.3, and see if you have better luck. I have had zero issues, and I have no reason to update TWRP until there's a new feature that I will actually want/need.
Click to expand...
Click to collapse
New downloads.
EVOlved human
And you are sure that you are downloading the correct files? Maybe it's just me, but it took me a while to find the correct version of numel's PAC rom.
aarsyl said:
And you are sure that you are downloading the correct files? Maybe it's just me, but it took me a while to find the correct version of numel's PAC rom.
Click to expand...
Click to collapse
Yes, I'm sure. I just reverted back to TWRP 2.6.3.1b and I'm downloading Paranoid at the moment. Will update if it flashes.
Sent from my EVO using XDA Premium 4 mobile app
I'll be waiting for your response.
aarsyl said:
I'll be waiting for your response.
Click to expand...
Click to collapse
Negative. Failed with the same error. From what I can determine, the updater script is looking for HBOOT 2.10.0000 and I have firewater 2.10.5555. I'm pretty sure this is why some ROMs are failing and others are not. I've got to learn how to edit the updater script as I've never done that before.
Sent from my EVO using XDA Premium 4 mobile app
Evolution_Freak said:
Negative. Failed with the same error. From what I can determine, the updater script is looking for HBOOT 2.10.0000 and I have firewater 2.10.5555. I'm pretty sure this is why some ROMs are failing and others are not. I've got to learn how to edit the updater script as I've never done that before.
Sent from my EVO using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Can't the script be updating in simple notepad? There is a lot of English in the updater-script file. Not entirely sure what you'll have to do, but I will surely check for you.
Update:
I re-ran the RUU to bring my HBOOT back to 2.10.0000. I remained unlocked and S-off as is well known. I installed twrp 2.7.0.0b via bootloader and I'm now about to try flashing again. Will update again after trying.
Sent from my EVO using XDA Premium 4 mobile app
aarsyl said:
Can't the script be updating in simple notepad? There is a lot of English in the updater-script file. Not entirely sure what you'll have to do, but I will surely check for you.
Click to expand...
Click to collapse
I always edit it with Root Explorer on my phone. You just have to edit out the lines dealing with the bootloader & device name. Fairly simple. It takes longer to extract the files and zip everything back up once you're done:thumbup:
Sent from my EVO LTE
FinZ28 said:
I always edit it with Root Explorer on my phone. You just have to edit out the lines dealing with the bootloader & device name. Fairly simple. It takes longer to extract the files and zip everything back up once you're done:thumbup:
Sent from my EVO LTE
Click to expand...
Click to collapse
That's what I figured, but I'm at work, so my assistance is limited.
aarsyl said:
That's what I figured, but I'm at work, so my assistance is limited.
Click to expand...
Click to collapse
No worries. The biggest thing is to make sure you don't flash the wrong ROM on the wrong device when you edit out those parts of the updater script. Could spell trouble
Sent from my EVO LTE
**********************MK2 and Newer Firmware Only*******************************
I'm back I have had time to totally rework the process. I have attached a PDF that contains the instructions as well as I link to all the files you will need.
All I ask if that if you have a problem with the process post or PM me if you dont think the instructions are clear enough please PM me so I can get it resolved first.
I have uploaded all the files that you will need and put them all in one place.
Added Screenshots of what to put in Odin!!!
Instead of using the rooted NC5 rom towards the end of the process, can I just use some other NC5 rom like HD16?
I haven't tested it yet with hd16. I would use the nc5 rooted and then make a backup in safestrap. So you can go back and forth.
Sent from my SCH-I545 using XDA Free mobile app
Good call... I'm about to start now, just downloaded everything. Thanks!
Your welcome let me know how everything works out.
Sent from my SCH-I545 using XDA Free mobile app
Made my first error on the first step... Quick notes for first timers so far::
- push UP to get in to download mode
- ODIN will not recognize your com port until you do so.
- Make sure that re-partition IS checked when you're flashing the first PIT file(the image in the pdf shows it unchecked so that's what I did)
- Whoa, totally missed when the phone turned itself off to reboot and was stuck at the Verizon logo. Unplugged phone and pulled battery then powered and pressed up to get in to recovery to wipe data/factory reset
I'll keep updating this post as I make more mistakes lol
Down went to download mode for me and your right but the image was blank without files. Just to show the version.
Sent from my SCH-I545 using XDA Free mobile app
Once you pit the pit file and the other files the repartition should be automatically checked. Also up should go to recovery.
Sent from my SCH-I545 using XDA Free mobile app
Yep, I'm on 4.3 now, going through saferoot... I clicked 'yes' on accept but I don't see it doing anything. Been sitting here for about 5 min. Going to unplug and re-plug and start saferoot again. I have my phone connected as a camera as suggested.
edit:: That worked in about 2 seconds
Installed recovery with safestrap, now installing stock rooted NC5 rom.
flashing last file (csc), phone rebooted and installing something and went directly in to recovery now. Just hit reboot and that worked.
humm... stuck at the red verizon logo now... been on here for a few min.
Really dumb question... I don't see any option to select slots or anything like that. I know that I can't select any different slots but it just flat out wasn't an option to pick where to install the rom.
Edit:: Well... that was weird. I was stuck at the Verizon logo so I went back in to SS Recovery and flashed HD16 and that worked (made sure to flash SU before rebooting). Everything is working now.
THANK YOU!!!
loudaccord said:
Yep, I'm on 4.3 now, going through saferoot... I clicked 'yes' on accept but I don't see it doing anything. Been sitting here for about 5 min. Going to unplug and re-plug and start saferoot again. I have my phone connected as a camera as suggested.
edit:: That worked in about 2 seconds
Installed recovery with safestrap, now installing stock rooted NC5 rom.
flashing last file (csc), phone rebooted and installing something and went directly in to recovery now. Just hit reboot and that worked.
humm... stuck at the red verizon logo now... been on here for a few min.
Really dumb question... I don't see any option to select slots or anything like that. I know that I can't select any different slots but it just flat out wasn't an option to pick where to install the rom.
Edit:: Well... that was weird. I was stuck at the Verizon logo so I went back in to SS Recovery and flashed HD16 and that worked (made sure to flash SU before rebooting). Everything is working now.
THANK YOU!!!
Click to expand...
Click to collapse
No ability on safestrap 3.72 for slot creation and install on a Verizon phone
sent by safestrap enabled bajarom
decaturbob said:
No ability on safestrap 3.72 for slot creation and install on a Verizon phone
sent by safestrap enabled bajarom
Click to expand...
Click to collapse
I didn't think so, I just didn't see any option mentioning slots of any sort.
3.72 only recognizes stock slot. Other slots don't work at this time
Sent from my SCH-I545 using XDA Free mobile app
worked like a charm
worked like a charm thank you for putting this together! very appreciated.
my only comments would be the aroma installer things. i was familiar with safestrap and aroma and such but to some new android rom people might get mixed up with how to use safestrap and then get mixed up with aroma as well.
AWESOME!!!!!
ok I got the 32gb version and was worried this wouldn't work but sure enough it has and I'm back to jelly bean and my 32gbs all show up.:victory::laugh::good::cyclops:
Worked like a charm got full root an now all my root apps I have are working flawlessly also if you have the 32gb version of this phone these files work fine and all the space shows up and accesses fine.
BIG THANK YOU TO TECH GUY FOR THIS!!!!!!!111!!!!!111!!!111!11 YOU'RE AWESOME IN MY BOOK!!!!1111!!!!111!!!1!!!1
So in this method there is only a stock slot available via safestrap? Is it safe to override this slot? If I wait will there be a better method?
Sorry if these are noob questions
Sent from my SCH-I545 using XDA Premium 4 mobile app
Safe strap backups,
techguy2002 said:
I haven't tested it yet with hd16. I would use the nc5 rooted and then make a backup in safestrap. So you can go back and forth.
Sent from my SCH-I545 using XDA Free mobile app
Click to expand...
Click to collapse
Might be a dumb question, but
If I have a MK2 and a NC5 nandroid backup from using safestrap can you go back and fourth between 4.3 and 4.4.2 by simply restoring your backups?
As far as I know that wouldn't be possible
Sent from my SCH-I545 using XDA Free mobile app
Great method and instructions
Thanks for posting your instructions. Other than a few of my own mis-steps this worked perfectly. Is it now possible to try other ROM's? If so, any tips to avoid problems?
I am running hyper drive 16.1. It's important you backup the roms in safestrap. I have the rooted rom and hyper drive on the same sd card and just alternate between the two by restoring.
Sent from my SCH-I545 using XDA Free mobile app
techguy2002 said:
I am running hyper drive 16.1. It's important you backup the roms in safestrap. I have the rooted rom and hyper drive on the same sd card and just alternate between the two by restoring.
Sent from my SCH-I545 using XDA Free mobile app
Click to expand...
Click to collapse
Got it, thanks.
Hey Guys
I'm a experienced flasher but I have ran into a issue with flashing roms on my Note 3. I had recently just been running stock rooted rom (basically I rooted my phone the day it came out with Sprint and never have update anything). So when I noticed that ny son's note 3 (note rooted) got an update recently, I decided to look for an updated base and broadband for my phone, which I thought I had found. So after so help with figuring out which update I needed to do, I figured NH7 was the latest. Finally got my phone updated or so it appeared.
So this week I've been trying desperately to update to MOAR S5 PORT (NE5 based I believe) I followed the instructions carefully and tried all 3 versions. All failed. So I restored my phone. Tonight I tried flashing flashing Pac-man rom. Same thing happened. Failed during install.
Can you guys take a look at my setup and tell me what may be wrong? Doing a clean install each time.
Sent from my SM-N900P using XDA Premium 4 mobile app
UPDATED 10/24/2014:
I had to reflash all the Note 3 stock tar's in order. Then root with Chainfire Auto Root. Then install Clockwork MOD Recovery. Now I can flash roms.
shaun0207 said:
Hey Guys
I'm a experienced flasher but I have ran into a issue with flashing roms on my Note 3. I had recently just been running stock rooted rom (basically I rooted my phone the day it came out with Sprint and never have update anything). So when I noticed that ny son's note 3 (note rooted) got an update recently, I decided to look for an updated base and broadband for my phone, which I thought I had found. So after so help with figuring out which update I needed to do, I figured NH7 was the latest. Finally got my phone updated or so it appeared.
So this week I've been trying desperately to update to MOAR S5 PORT (NE5 based I believe) I followed the instructions carefully and tried all 3 versions. All failed. So I restored my phone. Tonight I tried flashing flashing Pac-man rom. Same thing happened. Failed during install.
Can you guys take a look at my setup and tell me what may be wrong? Doing a clean install each time.
Sent from my SM-N900P using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Wipe wipe Wipe and when it fails to flash then restart recovery And it will flash then ....
So wipe 3 times. Then when it fails. Reboot to recovery and flash again? Do I need to wipe again before flashing?
Sent from my LGLS990 using XDA Free mobile app
shaun0207 said:
So wipe 3 times. Then when it fails. Reboot to recovery and flash again? Do I need to wipe again before flashing?
Sent from my LGLS990 using XDA Free mobile app
Click to expand...
Click to collapse
Any time you wipe the system partition, you MUST restart TWRP recovery before flashing the rom of your choice,.. or it'll fail every time.
Ok. I will try that noq
Sent from my SM-N900P using XDA Premium 4 mobile app
shaun0207 said:
Ok. I will try that now
Sent from my SM-N900P using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Sent from my SM-N900P using XDA Premium 4 mobile app
shaun0207 said:
Ok. I will try that noq
Sent from my SM-N900P using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Let us know how it goes. Happy flashing.
So I wiped everything. Tried to install and it failed. So i go to reboot to recovery and it ask me about superuser. But it doesnt install because their is no OS. REBOOT to recovery and it fails again
Do I need to format data?
Actually I dont even see a option in TWRP to format data
I wonder if I should try a dirty flash?
I would odin flash a full stock nh7. To get you all the way to nh7. I see you are still at nab on one. I had problems when they weren't all the same. I could be wrong.... I'm a noob. lol
Then, root with chanfires autoroot. Install your recovery. Then, flash your rom of choice.
NOTE: I said nh7.... but, if the rom you want to use isn't, then odin to nab or whatever the rom you want to run is. I don't know about downgrading, could make a brick.... lol
Research everything I said before you do anything! Or wait for someone to correct what's wrong with what I said! I take no responsibility for what you do to your phone!
one of your issues is you updated wrong! unless you were on nc5 you shouldnt jump right to nh7. you have to update in order to insure no issues. so if oyu were nqb or ever mi3 you need to go in order mi3>nab>nc5>nh7
Chainfires auto root.....http://download.chainfire.eu/362/CF-Root/CF-Auto-Root/CF-Auto-Root-hltespr-hltespr-smn900p.zip
Here is Supersu download.....so when you check to see if you have root.....it will all be good.......http://download.chainfire.eu/578/SuperSU/UPDATE-SuperSU-v2.14.zip
Odin v3.07.......http://forum.xda-developers.com/showthread.php?t=1738841
now you can try to go back to stock and flash whichever you are going to flash........or you can do a reflash of whatever you want....I have notice a losss of root also too.
also make sure to look into all those fixes for security patches xda has for our phone......download and scan with bluebox security and search for any open links that have a fix here on xda........
this happened to me the other weekend and it took an afternoon to dig all resources to figure out why and what i needed to do........I started rooting with a samsung moment......
I am back to stock.....no complaints.....but only did to get home before i go back to a rom.......hope we have helped....
Thanks guys. I will try all of these
shaun0207 said:
Thanks guys. I will try all of these
Click to expand...
Click to collapse
to get updates to stick via odin. remove sd card too. and when you update each version. boot to stock recovery wipe phone. flash again. what i do on each update. never had a single issue.
shaun0207 said:
Do I need to format data?
Click to expand...
Click to collapse
Yes you have to do that.. Also I believe you have to be in twrp 2.8 for kitkat I was having problems too until I installed the new Twrp!
bigkev904 said:
Yes you have to do that.. Also I believe you have to be in twrp 2.8 for kitkat I was having problems too until I installed the new Twrp!
Click to expand...
Click to collapse
I dont see a new TWRP. All I see is version 2,8
I installed all the updates back to back. I have TWRP installed and I'm on NH7 now. But I cant get root. Chainfire Auto took me back to stock recovery and I'm not rooted. So I flashed TWRP via Odin and flashed ChainFire Superuser v.2.14 and I'm still not rooted. All thought it say it worked. So WHen I reboot, what do I need to do then? I have SU installed
Ok guys. After flashing all the Roms in order via ODIN. I finally have NH7 working and rooted.
I just tried wiping system, data,dalvik and cache. Then I immediately rebooted to recovery and tried to flash MOAR V1. and Pac-man rom. Both failed.
One thing Im noticing in recovery is that the system is not mounted in when wiping. So I tried wiping with and without system being mounted and got the same result. One thing Im not sure about with flashing for the note is if the Data should be formatted before installing? However I dont see that option in TWRP.
This is the only phone Ive had this much trouble with when it came to flashing.
Any ideas?
Sent from my SM-N900P using XDA Premium 4 mobile app