Database Users

[Q] Wont boot after latest update

Hi,
Spent some time looking around the forums, but I wanted to make sure before I returned the phone for repair.
Basically I had the phone rooted to copy across a couple of library files and so than I can use nVidias Perfhud ES. The device worked perfectly, I also applied the previous update with no problems.
Today, after getting tired of receiving the update nag every few minutes I decided to update to latest firmware (4.5.91 I think). It downloaded the file, restarted, the progress bar run across and restarted again and that's where it stopped at the Moto boot logo.
After 20 minutes I decided to take the battery out and restart, same thing. I looked at the help section of Motorola's website and found the hard reset option. Booted into android recovery mode (the method for 2.2 didn't work, but 2.3 did the job - so I am guessing the boot image 2.3 installed correctly), did a wipe and restarted, again no luck.
Second try, downloaded the update file manually copied to a sd card and through recovery set to update, according to the log all was alright, but it still doesnt get past the motorola boot screen.
Anyone had this before, do I have any options here? I already contacted Motorola they said that I can send it for repair but I am situated in UK and phone was bought through a US retailer (AT&T Atrix) so they need a US address, which makes it kinda complicated. Any help/info will be much appreciated, thanks!

You can easy RSDlite the 2.3.4/4.5.91 service SBF I will look for the link and I will post it

mramirezusa said:
You can easy RSDlite the 2.3.4/4.5.91 service SBF I will look for the link and I will post it
Click to expand...
Click to collapse
I was looking at this thread just a minute ago http://forum.xda-developers.com/showthread.php?t=1182871 is this the method you are referring to? (I am still catching up with all the slag!)

skistovel said:
I was looking at this thread just a minute ago http://forum.xda-developers.com/showthread.php?t=1182871 is this the method you are referring to? (I am still catching up with all the slag!)
Click to expand...
Click to collapse
http://www.filesonic.com/file/15073...signed-ATT-US-GAS_NA_OLPSGBATTSPE_P011.sbf.gz
1FF-olympus-user-2.3.4-4.5.91-110625-release-keys-signed-ATT-US-GAS_NA_OLPSGBATTSPE_P011.sbf
MD5: 56721d893e43b814e95683a00b165555
SHA1: e00786e975b4f1d9fba2ff90c1ee6bbf95bb47b2
RSDLite 5.3.1
http://forum.xda-developers.com/attachment.php?attachmentid=634879&d=1308872277
download both files and will post instructions bellow

mramirezusa said:
http://www.filesonic.com/file/15073...signed-ATT-US-GAS_NA_OLPSGBATTSPE_P011.sbf.gz
1FF-olympus-user-2.3.4-4.5.91-110625-release-keys-signed-ATT-US-GAS_NA_OLPSGBATTSPE_P011.sbf
MD5: 56721d893e43b814e95683a00b165555
SHA1: e00786e975b4f1d9fba2ff90c1ee6bbf95bb47b2
RSDLite 5.3.1
http://forum.xda-developers.com/attachment.php?attachmentid=634879&d=1308872277
download both files and will post instructions bellow
Click to expand...
Click to collapse
1. Unzip the first file, you will ended with a file with .sbf extension
2. Install RSDlite 5.3.1
3. Turn off the Phone and Disconect from USB
4. Press and Hold VOL UP while you turn the phone hold until the tag of RSD show up in the screen
5. Connect the phone to USB/PC
6. Open RSDLite and chose file to flash go to the one on step#1 (to chose click on "...") then press Start and wait until it said PASS on the status.
Be sure the phone is charge at least 40%-50% and do not touch your pc when is doing... to make sure everything go right remove SIM card and external SD card.

Excellent thanks! I will try this tomorrow - device is at work, just to make sure, this will wipe all data and install latest firmware right?
My take on this is (after looking at the zip of the update and finding those same files I copied across a while ago in there) that for some reason it failed to copy the new ones on top of the old and is trying to call non-existing code.. Hope that method you posted works!

skistovel said:
Excellent thanks! I will try this tomorrow - device is at work, just to make sure, this will wipe all data and install latest firmware right?
My take on this is (after looking at the zip of the update and finding those same files I copied across a while ago in there) that for some reason it failed to copy the new ones on top of the old and is trying to call non-existing code.. Hope that method you posted works!
Click to expand...
Click to collapse
thats a service sbf so in data get preserve...
I think what it was wring with your OTA was that some of the files on you phone are already mod or replaced with something, so when try to do the ota a do the file checksum on each file then return with different code, so the upgrade stop automatic and get stuck in something, in that case you need to flash a SBF
NOTE: that once you are in the new 2.3.4/4.5.91 please NEVER try to downgrade with lower sbf in this case 1.83/1.57/1.26 etc....

Yes, I do remember reading something about not trying to downgrade from latest. You have been really helpful and fast to reply so thanks again!

Seems to be a big problem.

Restore finished with any problems, everything is good! Thanks for your time, I owe you a beer!

New Brazilian firmware

Hi guys!
Just saw at SBf Developers that hey have uploaded some new updates there.
AS my comes from Brazil, i saw that fastboot-ghost_retbr-user-4.2.2-13.9.0Q2.X-116-LCX-35-36-release-keys-cid12-Brasil-BR.tar.gz is avaliable. But my question is: how can i flash this kinda if files since they arent RSD lite type and are fastboot ones? Do i need unlocked bootloader?
If someone can help me, i appreciate a lot!

AFAIK, RSD is only a front end for fastboot, so technically you can flash those files with fastboot, because they are stock and signed by motorola (no unlocked BL needed). You just have to know the partitions in wich you're gonna flash each file

waiflih said:
AFAIK, RSD is only a front end for fastboot, so technically you can flash those files with fastboot, because they are stock and signed by motorola (no unlocked BL needed). You just have to know the partitions in wich you're gonna flash each file
Click to expand...
Click to collapse
Thanks my friend! But do uo have the steps for this? Cause i couldnt found any specific to Moto X.
As i unzip the tar file, i have these files as attached.

I don't have the exact steps, but you can look at the flashall.bat file inside your zip
regards

waiflih said:
I don't have the exact steps, but you can look at the flashall.bat file inside your zip
regards
Click to expand...
Click to collapse
Thanks again!
Any ideas?

Do you have the phone in fastboot mode and connected to your PC while running the BAT file?

xitake said:
Do you have the phone in fastboot mode and connected to your PC while running the BAT file?
Click to expand...
Click to collapse
No,but as the programa asks, i don have a JTAG flex?

xpc21 said:
No,but as the programa asks, i don have a JTAG flex?
Click to expand...
Click to collapse
I also didn't know what a JTAG flex is. After some googling, it seems that it is a sort of cable for flashing the image directly to the memory, internally, like in the photo below (not a Moto X).
So, I assume you don't have a JTAG flex connected, right? So it should be good to go

xitake said:
I also didn't know what a JTAG flex is. After some googling, it seems that it is a sort of cable for flashing the image directly to the memory, internally, like in the photo below (not a Moto X).
So, I assume you don't have a JTAG flex connected, right? So it should be good to go
Click to expand...
Click to collapse
Have you my friend flash or know about fastboot program? Case i have in more popular android phones but Moto X is so new that i dont wanna risk doing something wrong.

Flahing stock SBF
xpc21 said:
Have you my friend flash or know about fastboot program? Case i have in more popular android phones but Moto X is so new that i dont wanna risk doing something wrong.
Click to expand...
Click to collapse
Try this maybe it'll work
1. Connect your Moto x, make sure developer options is enabled and tick usb debugging.
2. open command window on the folder including the new extracted firmware.
3. Type adb devices to confirm that Moto X is detected by your computer.
4. Type adb reboot bootloader, Moto X will reboot in fastboot mode.
5. Run the batch file flasfall.
wait until it finishes it might take sometime, and you'll see the flashing process on both computer and Moto X.

kkhadr said:
Try this maybe it'll work
...
wait until it finishes it might take sometime, and you'll see the flashing process on both computer and Moto X.
Click to expand...
Click to collapse
Is it OK to do this if the phone is rooted and modified with xposed modules?
Also, from what I can see, this is the version .35
So as it is older than .51, pwnmymoto should still work, right?

Anyone else?
[email protected]

xitake said:
Is it OK to do this if the phone is rooted and modified with xposed modules?
Also, from what I can see, this is the version .35
So as it is older than .51, pwnmymoto should still work, right?
Click to expand...
Click to collapse
If this version includes the camera patch then it won't be rooted, but I flashed TMO 4.3 the test build it's working great but off course I lost root, and I'm sure in a few days it will be rooted again, so nothing to fear.

this is the OPs 3rd post about the same topic. One under q&a, one under dev that got moved to q&a, and now one under moto x general. Someone needs to teach him a lesson because he has gotten responses on all three threads. Really frustrating. Won't be getting anymore help from me...

Looks like fastboot-ghost_retbr-user-4.2.2-13.9.0Q2.X-116-LCX-35-36-release-keys-cid12-Brasil-BR.tar.gz have the same camera app as in ATT, TMO, Sprint after OTA (with improved camera). Camera app in new Brazilian firmware have version 3.0.211 - the same as in TMO rom with OTA installed.

Kind of straight forward
You just need to unpack the tgz container. Inside the folder there is a bunch of files.
I'm my case since I'm using OSX I just ran flashall.sh and done. There is a flashall.bat that I believe is designed to work with windows.
Put your phone in bootloader mode, connect the cable, go to folder the files lies and run the command. In about 5 minutes it is done. :good:

Have anyone tried it? I was trying to wait for the official OTA update, but it's taking too long. I need to know if it's safe.
Oh, and what if I use other flashboot file like from Verizon instead of the brazilian retail one? Is there any problem?

rodrigorox said:
Have anyone tried it? I was trying to wait for the official OTA update, but it's taking too long. I need to know if it's safe.
Oh, and what if I use other flashboot file like from Verizon instead of the brazilian retail one? Is there any problem?
Click to expand...
Click to collapse
rodrigorox,
I have called motorola on friday and it seems we will be getting the update in the next week or so...
I'd hold on on flashing it if all you look for is the OTA that US got.

{OUTDATED}[Guide][Stock ROM] The original non-Prime conversion thread

Update March 8 2017: As you can probably tell, this is very old. I have not worked on the device in several months and I have no idea if these methods are still safe. Please proceed with caution. I will be using one of these on a daily basis in the near future, so I probably will get back into development, and hope to release new content for the phone to help out the community. Please accept this as an official warning that the following is probably out of date and that you should be very careful should you decide to try it. The original post in it's entirety is spoilered below. You have been warned.
Update: A new update was released for the Prime model, V6.6, which replaces the preloader and completely breaks SPFT. If you unlocked your bootloader (so you can use fastboot) in any capacity before taking that update, there may be hope for you yet, but as of right now V6.6 is unsupported. Update: If you used this method to safely* take* the V6.6* update*, this will still work.
Update: I just checked the stats, and this has been downloaded more than 3 thousand times. I never thought my humble little conversion guide would help out so many people. I have also added a new mirror at [REDACTED], so anyone in North America who was having trouble with the Europe mirror, give that one a shot. It should be faster! I have updated all links in the guide to use the new North America mirror, and added a separate Europe mirror link after each link.
Hello! This is a tutorial for converting the Amazon Prime Edition BLU R1 HD to the OEM BLU version. This will overwrite the relevant partitions on your Amazon version of the device with the non-Amazon version. The physical model number on your device will still be a tell (obviously), but besides that, there will be no way to tell your device apart from the regular model! You can also use this method to convert non-Prime to Prime version, and undo OTAs or system modifications. This will restore a 100% out of the box image from either edition on your device.
This will work if you have software version...
V12
V6.1
V6.4
V6.5
SAFE V6.6 FROM THIS THREAD
This will NOT work on software version...
V6.6
The V6.6 update brought a new preloader that breaks our ability to use SPFT. I am currently working on ways to reverse the damage, but as of right now, there is no way to convert (or downgrade) from software V6.6
You can use this on any 16/2 R1 HD with supported software version to...
Convert to the non-Prime OEM version
Convert to the Prime version
Remove ads (via conversion to non-Prime version)
Unroot
Downgrade to V6.1
Downgrade to V12
Undo system alterations/tampers
Restore the system image to the way it was when you first opened the box
Unbrick a device (if bricked because of bad system/recovery/boot image)
There are a handful of reports about this working flawlessly on the 8/1 model as well. I have not personally tested this, so there is still some risk factor.
This only overwrites the system, recovery, and boot partitions. Any other partitions that have been altered will not be restored. In most cases, other partitions should not have been altered, so this is not a concern. I have a full system backup of all partitions, but there is currently evidence to suggest that it is not safe to flash all of the partitions, so I will not release that backup until more is known.
You *should* be able to safely pull this off without wiping your data. This does not require your phone to be rooted or have any other modifications. You can pull it straight out of the box and do this process! If your phone is rooted, you'll lose it. This will make your phone EXACTLY like the non-Prime version comes out of the box! You can also convert a non-Prime device (or a converted Prime device back) to a Prime device using the same method, but I'm not exactly sure why you would want to. I did this all on Linux, but the Windows should work fine too as long as you have drivers dealt with. If you don't have drivers dealt with, I'm not your guy. I'll just tell you to use a better operating system. You'll also need an archive program that can deal with tar.gz files, because that's how my computer zipped them.
And the standard disclaimer: If this bricks your phone or makes it become sentient and plot with other sentient phones to murder your entire family, it's not my fault. That's all on you, buddy.
Ok, without further ado, on to the tutorial!
First, you need these things. Some of the files are quire large, so it might take a while to download:
You'll need the latest version of Smart Phone Flash Tools, or SPFT for short. You can download that from this site, or from [REDACTED]. Please use the latest version for your OS.
You'll need to download the system image. If you're converting to the non-Prime version, [REDACTED]. If you're converting to the Prime version, [REDACTED]
You need the scatter file. This will tell SPFT where the partitions are. This is the same for both variants, so just download [REDACTED]
Once you have those things, you can start actually flashing your phone:
Power your phone completely OFF! This will not work if your phone is powered on. SPFT writes directly to the phone's memory, bypassing all security measures the phone has, so it requires the phone to be completely OFF to get safe and exclusive access to the memory. DO NOT PLUG IN YOUR PHONE YET!
Extract SPFT into a folder on your computer. If you can't figure out how to do that, please stop tinkering with your phone. It's only a matter of time until you break something.
Extract the system image into the same folder you put SPFT in. The three files (boot.img, recovery.img, system.img) should be in the same folder as all the other SPFT files, including the binaries.
Run SPFT. On Windows, simply double clicking the SPFT executable should do the trick. On Linux, you must run the flash_tool.sh script as root. Open a terminal emulator, cd to the SPFT folder, and run `sudo ./flash_tool.sh`. If you recieve an error about permissions, run `chmod +x flash_tool.sh` and try the first command again.
Go to the Download tab in SPFT and click the Scatter-loading button on the far right side. DO NOT click the Download Agent button. When the file picker dialog pops up, find and open the r1hd-spft-scatter.txt file you downloaded earlier.
You should see a list of partitions. Only three of them (boot, recovery, system) should be checked, and the location should point to the files you extracted from the tar.gz file earlier. If this is not the case, double-click the location block of the boot, recovery, and system partitions, and select the boot.img, recovery.img, and system.img files from your filesystem respectively. After selecting the files, the boxes should check themselves.
From the dropdown in the upper left of the partition list, make sure Download Only is selected. Any other option could damage your device.
Click the Download button in the upper left.
While your phone is OFF, plug it into your computer with a data safe USB cable. The cable that came in the box from the factory is ideal, but any good quality cable will work just fine.
SPFT should start overwriting your phone. If you receive an error from SPFT, unplug your phone, close SPFT, and repeat steps 4 through 9. The whole process takes about 10 minutes, after which you should see a window with a large green checkmark. Once you see that window, you can safely unplug your phone and start it up. You're all done!
And as a bonus, I've also included a guide for unlocking the bootloader, getting custom recovery, and rooting the device after you've done this in post #2. That makes this your one stop shop for getting a brand new Prime phone out of the box!!
HUGE THANKS TO @mrmazak FOR THEORIZING THIS METHOD AND GETTING ME THE NON-PRIME SYSTEM IMAGE TO USE!
As always, if you have any questions, just ask in a thread reply or send me a private message on XDA. And by the way, hit the Thanks button in the lower right corner of the post if my guide helps you. It motivates me to keep this up to date and write more helpful guides. If you feel like giving me even more motivation and help fund future development, [REDACTED].

{OUTDATED}[GUIDE][OEM][Stock] Bootloader Unlock, TWRP, and root!
Update March 8 2017: As you can probably tell, this is very old. I have not worked on the device in several months and I have no idea if these methods are still safe. Please proceed with caution. I will be using one of these on a daily basis in the near future, so I probably will get back into development, and hope to release new content for the phone to help out the community. Please accept this as an official warning that the following is probably out of date and that you should be very careful should you decide to try it. The original post in it's entirety is spoilered below. You have been warned.
Ok, now you've converted your brand new Prime phone to the non-Prime version. How do you unlock this sucker? The conversion process actually unlocks the standard unlock method from the factory, so it's VERY simple! No hoops to jump through or anything. You'll need adb and fastboot. You can get those as part of the official Android developer kit, your distro's repos (on Linux) or Homebrew (on Mac). Of course, this guide works for the normal non-converted non-Prime version as well. This WILL wipe your phone, so make sure you back up any important data before doing this.
This guide is for the OEM (non-Prime) version. If you have the Prime version, convert it to OEM using the guide above BEFORE doing this guide.
The standard disclaimer from above still applies.
This guide is broken up into two parts. Unlocking the bootloader, and rooting the phone. If you are preparing to install Magisk, do the bootloader unlock, skip the rooting part and move on to the Magisk guide. You do not need the files above if you are only unlocking the bootloader. If your bootloader is already unlocked, skip the bootloader unlocking part and skip to rooting the phone. If you are preparing to install Magisk and your bootloader is already unlocked, you shouldn't be here. Also please note that the bootloader can sometimes re-lock itself after completing a conversion/restore from the guide above, especially to/from the Prime version, so if you're not sure, play it safe and re-unlock your bootloader.
Part 1 - Unlocking the bootloader:
Boot up your phone. If you haven't already gone through the initial setup process, go through it. The bootloader unlock process will wipe your phone, so skip as many questions as possible so you don't waste your time.
Open the Settings app, go to About device, fine the Build number (it's toward the bottom), and tap on it 8-10 times (until it says you are now a developer. If it says there's no need and you're already a developer, you can skip to the next step)
Go back to the main Settings menu. You should see a new option where About device used to be, Developer options! Click on it.
Toward the top of the long list of developer options, there is an option called "OEM unlocking". If it's switched off, switch it on. If it's switched on, switch it off and back on again. You may get a warning saying that device protection features won't work. Click Enable and proceed. You may also be prompted to enter your password/PIN/pattern lock if you have one.
Scroll down a little bit to reveal USB debugging. Switch it on if it's not already.
Connect your phone to your computer using a data safe cable. Do not disconnect it until the very end.
On your computer, open a terminal emulator (or Command Prompt with ADB access) and run `adb reboot bootloader`. If you get a message complaining about keys or authorization, check your phone. There should be a window asking for permission for your computer to access the device. Allow it and run the command again.
Your phone will reboot into fastboot mode.
On your computer, run `fastboot oem unlock`. On the phone you will get a warning message talking about the implications of unlocking the bootloader. Press Volume Up to accept them. If everything goes smoothly, your bootloader should now be unlocked. You're not ready to flash quite yet! Flashing at this stage WILL brick your phone, so it's important that you continue following the guide carefully.
On your computer, run `fastboot reboot`. Your phone should reboot anywhere from 3 to 5 times. If it reboots more than that, your phone is bricked and you need to start again by following the guide above again.
Once Android starts up again, you should see the setup wizard. Your bootloader is now unlocked!
Part 2 - rooting the phone:
BEFORE YOU PROCEED: If you want your phone to be encrypted AND rooted, it's important that you unlock the bootloader using the steps above first, then use the encryption APK to encrypt your phone BEFORE installing TWRP and rooting your device. This device is an exception to the general rule of flashing TWRP first and then rooting afterwards. Repeat, if you want your phone encrypted and rooted, unlock the bootloader FIRST, then encrypt SECOND, then flash TWRP THIRD, and root your phone LAST.
This is the guide for rooting the actual phone. You must unlock the bootloader using the steps above before doing this part.
First, you'll need these things on your computer.
The TWRP image for the R1 HD. You can download [REDACTED]).
A copy of the latest SuperSU zip from Chainfire. You can get it from the official forum post, or Chainfire's website.
Linux Users: On Linux, you must add `sudo` to the beginning of all fastboot commands, because most Linux distributions will not give you enough access to the hardware without being root.
And finally, the guide:
Hold Volume Up and Power until the phone turns on with the boot menu. Once the boot menu appears, use the volume keys to scroll to [Fastboot Mode] and press the power button to select it. It's the middle option.
On your computer, cd to the folder where you downloaded twrp-3.0.2-1-r1hd-lopestom.img and do `fastboot flash recovery twrp-3.0.2-1-r1hd-lopestom.img`.
On your computer, do `fastboot boot twrp-3.0.2-1-r1hd-lopestom.img`.
Once TWRP boots up, dismiss the prompt about mounting the system, go to Reboot, then choose Recovery. Your device will reboot back into TWRP. I know this step seems odd, but just trust me.
Make a backup if you want. It's not a bad idea, but seeing how you just unlocked your bootloader so your data is gone and we have the images in case you somehow brick the system, I doubt you actually need it.
In TWRP, go to Advanced, then ADB Sideload. Slide the confirmation slider all the way to the right to confirm.
On your computer, cd to the folder where you downloaded SuperSU and run `adb sideload [SuperSU-zip-name.zip]`, replacing the last argument with the name of the SuperSU zip you downloaded, of course. If your computer says "waiting for device" for a long time, cancel with Ctrl+C, run `adb kill-server`, then run the first command again but with `sudo` in front this time.
Reboot the phone. If everything worked correctly, you should now have a rooted phone with SuperSU, bootloader unlocked, and custom recovery! Yay for cheap phones!
As always, if you have any questions, just ask in a thread reply or send me a private message on XDA. And by the way, hit the Thanks button in the lower right corner of the post if my guide helps you. It motivates me to keep this up to date and write more helpful guides. If you feel like giving me even more motivation and help fund future development, [REDACTED].

reserved 3

reserved 4

reserved 5

Can you verify the image you uploaded for the non-Prime version? I'm getting unexpected EOF errors when extracting in Windows using 7Zip and TarTool, and I'm also getting an "operation not permitted" error when extracting using the built in Archive Utility in OS X.

abs0lute said:
Can you verify the image you uploaded for the non-Prime version? I'm getting unexpected EOF errors when extracting in Windows using 7Zip and TarTool, and I'm also getting an "operation not permitted" error when extracting using the built in Archive Utility in OS X.
Click to expand...
Click to collapse
Yeah, that's because the image isn't fully uploaded. My internet is very slow, so it's taking a while to upload. Sorry about that. I was hoping it would be finished by the time I finished writing this, but alas, nope. I will have all files uploaded by tomorrow, along with .md5 files so you can verify the checksums, so come back then. Again, sorry. I guess I should have posted this _after_ I got those uploaded. Oh! And I have North America mirrors coming within the next couple months. It seems a little oxy-moronic to host files for a US only device on an EU server, but unfortunately, servers in the US are significantly more expensive.

ColtonDRG said:
Yeah, that's because the image isn't fully uploaded. My internet is very slow, so it's taking a while to upload. Sorry about that. I was hoping it would be finished by the time I finished writing this, but alas, nope. I will have all files uploaded by tomorrow, along with .md5 files so you can verify the checksums, so come back then. Again, sorry. I guess I should have posted this _after_ I got those uploaded. Oh! And I have North America mirrors coming within the next couple months. It seems a little oxy-moronic to host files for a US only device on an EU server, but unfortunately, servers in the US are significantly more expensive.
Click to expand...
Click to collapse
No problem - thanks for your work on this!

abs0lute said:
No problem - thanks for your work on this!
Click to expand...
Click to collapse
Just finished uploading the non-Prime version. I will start the other upload before sleeping and update the post removing the warning when I awaken, assuming everything has gone well. You're free to attempt a non-Prime conversion now. Just don't do it the other way around yet.
Sent from my LG G4 using XDA Labs

Can't wait to give this a shot. Well, at least after someone else reports success first...

followed post 1 convert to non prime steps on windows, did not do the bootloader unlock steps.
phone booted up ok, followed by android is upgrading x of 37.
phone working and no ad's on lock screen
the amazon apps are still there but appear to be disabled, causing errors at first boot.
disabled or uninstall the apps. - used cleanmaster
everything seems ok now

Hello, I have now finished uploading the files, so you can now safely flash away! Enjoy! @abs0lute

bupkis said:
Can't wait to give this a shot. Well, at least after someone else reports success first...
Click to expand...
Click to collapse
I report success. Of course I did everything in the guide here before posting it. I'm not irresponsible. It's completely safe. I just finished uploading the files, so please go ahead and give it a shot.

ColtonDRG said:
I report success. Of course I did everything in the guide here before posting it. I'm not irresponsible. It's completely safe. I just finished uploading the files, so please go ahead and give it a shot.
Click to expand...
Click to collapse
ok, away we go! :laugh:
When I try to download the scatter file it just opens the file in a new browser window.
>nevermind, figured it out...success!
...on to bootloader unlock, TWRP, root...

bupkis said:
...
When I try to download the scatter file it just opens the file in a new browser window.
...
Click to expand...
Click to collapse
Yeah, that's a problem with my server configuration. I'll fix it later. For now, you can save the file by opening it in a browser window and pressing Ctrl+S

I have completed the process successfully-TWRP, root, no ads but do still have all the Amazon apps so something is screwy but not the end of the world.

bupkis said:
I have completed the process successfully-TWRP, root, no ads but do still have all the Amazon apps so something is screwy but not the end of the world.
Click to expand...
Click to collapse
Nope, it's not screwy. The non-Amazon version does include a lot of the Amazon apps. You can uninstall some of them the normal way (they're pre-installed user apps), and others you can either disable or uninstall using your favourite system app remover.

Anyone else missing Encrypt section in Settings > Security after converting to non-prime?

When I try to load the scatter, SPFT says "Error: Initializing scatter file failed. Please check the name of scatter file which you load is legal." I downloaded it from both the primary link and your mirror, same error. Any ideas? Thanks.
EDIT: Looks like I downloaded the oldest version, not the newest version of SPFT. Whoops! I'll leave my mistake on here to help others who may assume the first link is the right one.

notfix said:
Anyone else missing Encrypt section in Settings > Security after converting to non-prime?
Click to expand...
Click to collapse
It is missing. How peculiar. I will attempt to implement a workaround in a little bit. Sorry about that.
Update: The Encryption activity exists on the phone, we just can't get to it from the settings menu. You can launch it by manually launching com.android.settings.Settings$CryptKeeperSettingsActivity using your preferred method for launching arbitrary activities. I will release an app that will launch this activity for you ASAP!

LG V20 H910 Root attempt fail, any plan of recourse?

Hi. I'm just gonna say this first: I didn't know entirely what I was doing when beginning this operation. I was just trying to do something fun and new, and it didn't pan out. I fully acknowledge that I am an idiot.
Now, the story. I was attempting to root my LGV20 with this guide: https://forum.xda-developers.com/v20/how-to/root-h910-v10m-t3664500 .
I have read over this thread more times than countable and thought I was doing everything correctly. I got to the "STEP3.BAT" portion of the guide and long story short, my phone crashed during it and somehow got foobarred.
It *kinda* works (as in it will boot for around a minute) and then blue/black screen into a reboot.
Is there any way I can save this phone? Hard resets, going into software, more dumb computer stuff, anything. I don't *need* to get this phone working again but it would be really preferable.
Simultaneously I fully accept the responsibility in failing the operations. I know that somewhere I must have messed up. If no-one wants/ can help me, tell me so. Just means new phone time.
If any more detail on what happened is needed, tell me.

First off: that guide is ONLY for the H910 (AT&T) variant, so make sure with your model
and also, when you said a "blue or black screen" it also has very small writings too, right? If so, then you may have faced a kernel/bootloader panic
Technically your phone is *still* alive, and your best method is to start over again, assuming if you read the whole guide carefully then you have backed up your firmware and can still access download mode.
Flash your stock firmware back (or use the H915 firmware provided by the guide), wipe and setup your phone again, then root the phone again.
I also suggest replacing the TWRP recovery inside the provided Dirtysanta folder cuz that's what i did when i faced the kernel panic

MEMO#22 said:
First off: that guide is ONLY for the H910 (AT&T) variant, so make sure with your model
and also, when you said a "blue or black screen" it also has very small writings too, right? If so, then you may have faced a kernel/bootloader panic
Technically your phone is *still* alive, and your best method is to start over again, assuming if you read the whole guide carefully then you have backed up your firmware and can still access download mode.
Flash your stock firmware back (or use the H915 firmware provided by the guide), wipe and setup your phone again, then root the phone again.
I also suggest replacing the TWRP recovery inside the provided Dirtysanta folder cuz that's what i did when i faced the kernel panic
Click to expand...
Click to collapse
Thanks so much. Freaked out over this for a good bit. Came back, did what you said and we're back at that step fully working. Life saver.
Now my first guess as to why step3 failed is that i didn't have the latest version of TWRP. How can I set that up?

Inside the root package folder you can see an .img file named twrp 3.0.2-1- us996.img
What i did was downloaded a later version
(not latest cuz my phone won't boot at the latest version for some reason), copied the name of the original twrp and renamed it, paste it to the folder, overwrite the old one, and try to root it again

MEMO#22 said:
Inside the root package folder you can see an .img file named twrp 3.0.2-1- us996.img
What i did was downloaded a later version
(not latest cuz my phone won't boot at the latest version for some reason), copied the name of the original twrp and renamed it, paste it to the folder, overwrite the old one, and try to root it again
Click to expand...
Click to collapse
Alright, i've done that now too. Thanks. Is there anything else i should/need to keep in mind to ensure failure is not going to happen? I want to make 100% sure I get everything right this time.

reptarien said:
Alright, i've done that now too. Thanks. Is there anything else i should/need to keep in mind to ensure failure is not going to happen? I want to make 100% sure I get everything right this time.
Click to expand...
Click to collapse
No i don't think there is more things to do, the guide you're following is pretty much straightforward already.
100% guarantee is always a stretch here in XDA. But if you're still facing problems you can ask for help on that guide's thread.

MEMO#22 said:
No i don't think there is more things to do, the guide you're following is pretty much straightforward already.
100% guarantee is always a stretch here in XDA. But if you're still facing problems you can ask for help on that guide's thread.
Click to expand...
Click to collapse
I really want to give up on this. This time I successfully made it through all Step 3, but I also noticed that my screen was kind of glitched and not rendering properly at that stage. After it rebooted, I unplugged my micro usb cable and it gave me an angry green warning message I will attach here.
If you/someone can tell me what to do with this message from here or instruct me on how to flash stock H910 10 q back onto the phone without doing TWRP (since i'm evidently incapable of installing it) I would be most appreciative.

Slightly better picture without anything cut off.

reptarien said:
I really want to give up on this. This time I successfully made it through all Step 3, but I also noticed that my screen was kind of glitched and not rendering properly at that stage. After it rebooted, I unplugged my micro usb cable and it gave me an angry green warning message I will attach here.
If you/someone can tell me what to do with this message from here or instruct me on how to flash stock H910 10 q back onto the phone without doing TWRP (since i'm evidently incapable of installing it) I would be most appreciative.
Click to expand...
Click to collapse
The screen glitching is normal, the green text after boot however is somehow not.
Sad to hear that it still didn't work, there something seems to be interrupting the process of rooting your phone. I dunno if it has something to do with ARB (anti rollback) preventing you to root
If you want to go back to your stock firmware that you backed up, you can:
-Carefully flash each file of your backed up firmware through adb and fastboot mode
-build a zip file of your firmware and flash through TWRP (since it didn't succeed tho)

MEMO#22 said:
The screen glitching is normal, the green text after boot however is somehow not.
Sad to hear that it still didn't work, there something seems to be interrupting the process of rooting your phone. I dunno if it has something to do with ARB (anti rollback) preventing you to root
If you want to go back to your stock firmware that you backed up, you can:
-Carefully flash each file of your backed up firmware through adb and fastboot mode
-build a zip file of your firmware and flash through TWRP (since it didn't succeed tho)
Click to expand...
Click to collapse
Could you reply with any links with a tutorial on how to do the first thing? Or describe it. Sorry for being so dumb i'm a total newbie lol

reptarien said:
Could you reply with any links with a tutorial on how to do the first thing? Or describe it. Sorry for being so dumb i'm a total newbie lol
Click to expand...
Click to collapse
Unfortunately i can't find any guides when it comes to flashing the back up.
I did read something back then on turning it into a zip file, but even if you can build one you still need TWRP, in which case you haven't successfully installed, so that's no option
Flashing the backup files requires specific commands, especially to the part on what partition should it be flashed to
When LGUP backs up your phone's firmware, you can see a vast number of files(i can't remember how were they named, I'll look up a reddit post about it)
The files where named based on what partition it came fom (H910_modemxx_COM12, H910_system_COM12 or something like that)
These are image files, what i did as far as i can remember was rename these files by adding an IMG extension for ADB to recognize
Flash them according to it's partition name:
"Fastboot flash system H910_system_COM12.img"
"Fastboot flash recovery H910_recovery_COM12.img'
Etc.
To go to fastboot, turn off your phone and hold the volume down button , then plug your phone to the PC.
But i really cannot guarantee this, because for all i know, in order to flash this you need fastboot, and to get fastboot you need to root your phone, because only the engineering bootloader has it (i'm sorry if it's wrong tho), and flashing these files to fastboot might be a bit dangerous because it will not verify the files, there may be chances that you might flash a corrupted file. so flashing via LGUP is the safest option so far if you don't know what you're doing

For anyone having issues changing from CN to NA ROM on the 5S

There's a little story i needed to rant about before i wrote this guide so read if you'd like if not tldr; will be down below
NO ROOT OR BOOTLOADER OR ANY FORM OF CODING NEEDED FOR THIS FIX, THIS METHOD WE WILL BE USING OTG AND THE RENAMED STOCK NA 8.07 ROM FOR THE 5S GOING FROM CN 6.23
Requirements​ - NA 8.07 rom from the official redmagic website
- A Computer/laptop
- USB stick (mine was usb2.0)
- OTG adapter (if you have any old samsung phone boxes look in them there's usually one)
Hey guys! First of all im terrible with technology, i havent touched a computer in over 15 years before 4 days ago.. So i bought this phone 4 days ago as i needed a decent phone with a snapdragon soc (samsung uses trash exynos in Australia). The shop i bought it from didnt tell me it was the cn version and thought he would just have NA version as thats what it says australians will recieve on the official site.
So i did some research and found out we can easily change roms using the local update thingy so i dl'ed the 8.07 NA rom and it would load to 25% then freeze, reset and nothing would happen.
So i tried the OTG method, same thing again, 25% then crash and reset. So at this point im starting to get pissed, i downloaded the latest 5G NA rom and tried to otg method that rom to the phone. It loaded to 80%, crashed and hard bricked my phone to the point of where it was corrupt, couldnt get into recovery and couldnt factory wipe,
I was however, happy to see the boot logo had changed to english though so i didnt give up, 3 days, 3 f##ing days i was trying to research flash guides, recovery guides, root guides, downloaded about 100 usb drivers because i wasnt updating to the right drivers at the right times when plugging in and unplugging my phone, i tried unbrick tools and when trying to fastboot it was saying the password was incorrect (fastboot oem nubia_unlock NUBIA_NX659J is what worked for me to unlock fastboot. all the guides i read said the fastboot cmd was
fastboot oem nubia_unlock NUBIA NX659J) nothing worked. Luckily i had gone into dev options after reading a guide and unlocked oem unlocking and usb debugging before the phone bricked as this is what helped unbrick my phone. I had to individually flash each .img file from the CN rom back to the phone.
I didnt know how to code or do cmd thingys before i bought this phone. Now i could f## join anonymous im that good LOL but yeah i managed to unbrick, wipe, and flash the NA 8.07 rom to my CN 5S using OTG. You wanna know what i did to make it work? I can tell you right now it didnt need a f##ing 4 day crash course on hacking and coding.
TLDR; bought CN rom 5S brand new from shotty phone shop, i couldnt get the NA rom to load past 25% on the local update so i went through hell and back.
I highly highly recommend unlocking developer options in your phone, turn on oem unlocking and usb debugging before doing any updates or experiments with this phone, just incase anything goes wrong with any updates
Solution:
- Always back up your phone before anything you will need to do a factory wipe after doing this
- Change the name of the NA 8.07
NX659J-update.zip folder you downloaded to "update"
- Copy that update.zip folder to a freshly formatted fat32 USB stick, do not unzip and copy. It has to be the zipped folder then safely eject the usb from the PC
- Hold the Volume up button and the power button until the screen turns on, once the screen turns on release the power button and you should reach a blue screen with 2 language selection buttons, use the volume keys to navigate and the power button to interact.
- After choosing language you will see "choose a package" and some other buttons, this is recovery mode.
- select "choose a package" and plug in your OTG adaptor and USB stick
- Select OTG method
- Find your "update.zip" folder it should be right there
- Start update and keep an eye on the phone incase any errors pop up it should take about 5 minutes to update and it will stop at certain points (stopped at 80% for a good 30 seconds for me) for bigger files so dont stress if the numbers aren't moving. I was tapping the screen so fast with anxiety at 80% hahah
- After the update go back to recovery and wipe data/cache partition and reboot
- Enjoy your goog apps

unlocking dev options and using the oem unlock option is not necessary for our device.
Unlocking the bootloader also corrupts the fingerprint sensor data, making fingerprint break.
when you need to flash a rom and the normal method does not work, flashing though recovery normally works.
as you have a CN variant of the phone. note you cannot use the NFC function. as there is no NFC chip on CN variant devices.

Patrick Morgan said:
unlocking dev options and using the oem unlock option is not necessary for our device.
Unlocking the bootloader also corrupts the fingerprint sensor data, making fingerprint break.
when you need to flash a rom and the normal method does not work, flashing though recovery normally works.
as you have a CN variant of the phone. note you cannot use the NFC function. as there is no NFC chip on CN variant devices.
Click to expand...
Click to collapse
Oh i didn't know that! I was unable to flash the na rom through recovery until i renamed the zip folder lol but i wish i knew i had to rename it before i bricked my phone.
Im not sure how to relock my bootloader and fix the fingerprint sensor, i read somewhere theres a number to dial #xxx# for the calibration but i cant find it

Brae2 said:
Oh i didn't know that! I was unable to flash the na rom through recovery until i renamed the zip folder lol but i wish i knew i had to rename it before i bricked my phone.
Im not sure how to relock my bootloader and fix the fingerprint sensor, i read somewhere theres a number to dial #xxx# for the calibration but i cant find it
Click to expand...
Click to collapse
fastboot flashing lock or fastboot oem lock I think are the commands to relock your bootloader. which after a wipe should restore your fingerprint.
you can then follow my TWRP and ROOT guide on XDA here for the 5S and not have flashing problems again.

Patrick Morgan said:
fastboot flashing lock or fastboot oem lock I think are the commands to relock your bootloader. which after a wipe should restore your fingerprint.
you can then follow my TWRP and ROOT guide on XDA here for the 5S and not have flashing problems again.
Click to expand...
Click to collapse
Thanks for the help! Im wondering if i should just return this phone and just buy the na version from the website, i find it a little annoying that the shop didnt mention it was the cn version, i dont know what else im missing apart from NFC aswel so im stressing

Brae2 said:
Thanks for the help! Im wondering if i should just return this phone and just buy the na version from the website, i find it a little annoying that the shop didnt mention it was the cn version, i dont know what else im missing apart from NFC aswel so im stressing
Click to expand...
Click to collapse
all 3 regions had the exact same hardware.
with the exception of the NFC chip on the CN units.
if you can live without NFC the phone should be the same and function correctly with any of the roms once you're able to flash them.
its just that there will be an NFC option in the rom, it just wont activate, since you dont have the actual hardware.
if you were to give the phone back look into buying it from redmagic directly. as Nubia's Warranty only covers direct sales, it does not cover any 3rd party website this includes places like Nubia store on Aliexpress. you won't get official warranty from there.
only the redmagi.gg or nubia homepage which normally directs you to redmagic.gg will support official warranty so this is something to consider.
but also, as you've unlocked the bootloader, flashed things and what not. if the seller knows or finds this out they can refuse a refund as you've modified the system.
good luck either way.

corrupt