Hi,
I was wondering how to unroot the nokia 1. Would someone be able to give me a pointer please?
Many thanks
Beepbopboop.
To unroot make sure you're in the stock system,boot & vendor then you'll have to go to fastboot
>fastboot erase userdata
>fastboot flash recovery recovery.bin (you can go to the other thread to dowload the stock recovery)
>fastboot flashing lock_critical
This will make your phone go stock and lock bootloader thus unrooting the device.
Related
I tried to flash a downgrade image to my moto e 2nd gen. Now Im stuck in bootloader and a warning message for unlocked bootloder. Ive tried to flash logo.bin, and other images aswell with no luck. It keeps asking me to install a valid signed images, I don't know where to find these images. Please help!
You need to do exactly what it's asking you to do - flash valid signed images. Which model do you have (XT152x)? Which region are you in? Which version were you downgrading from?
Just so you know, downgrading the stock ROM is very highly discouraged as it can cause bricking in certain circumstances. In particular, never try to downgrade the stock ROM when the bootloader is locked. You can try flashing back the upgraded images and seeing if your phone accepts them. Be aware that the signed images must match your model number and region.
squid2 said:
You need to do exactly what it's asking you to do - flash valid signed images. Which model do you have (XT152x)? Which region are you in? Which version were you downgrading from?
Just so you know, downgrading the stock ROM is very highly discouraged as it can cause bricking in certain circumstances. In particular, never try to downgrade the stock ROM when the bootloader is locked. You can try flashing back the upgraded images and seeing if your phone accepts them. Be aware that the signed images must match your model number and region.
Click to expand...
Click to collapse
Thanks for reply.
I don't have these images, where to get them? My model is xt1524reteuall, I'm in europe/sweden and I downgraded from stock Lollipop 5.0.2
I did unlock the bootloader via motorolas site.
pemhak said:
Thanks for reply.
I don't have these images, where to get them? My model is xt1524reteuall, I'm in europe/sweden and I downgraded from stock Lollipop 5.0.2
I did unlock the bootloader via motorolas site.
Click to expand...
Click to collapse
Hmm, so you went from a newer 5.0.2 build to an old 5.0.2 build? What were you downgrading to?
Go to this folder: https://mega.nz/#F!rMIhDLgR!oq5Cz_XbgZLEEysmqoYtcA
Navigate to Surnia ->5.0.2
Look for the file XT1524_RETEUALL_MOTOE2... (it's near the middle of the list)
Download and try flashing everything it in using fastboot.
squid2 said:
You need to do exactly what it's asking you to do - flash valid signed images. Which model do you have (XT152x)? Which region are you in? Which version were you downgrading from?
Just so you know, downgrading the stock ROM is very highly discouraged as it can cause bricking in certain circumstances. In particular, never try to downgrade the stock ROM when the bootloader is locked. You can try flashing back the upgraded images and seeing if your phone accepts them. Be aware that the signed images must match your model number and region.
Click to expand...
Click to collapse
Thanks for reply.
I don't have these images, where to get them? My model is xt1524reteuall, I'm in europe/sweden and I downgraded from stock Lollipop 5.0.2
I did unlock the bootloader via motorolas site.
I got my device back!! I did succeed to flash it with this rom "surnia_stock_5.0.2.zip" with TWRP. I did not have the patience to wait at the Motorola logo when booting, I have to wait 2-3 min and 2-3 min for services to start. for the device to boot. But now it doesn't register any sim card when at desktop?!?
squid2 said:
Hmm, so you went from a newer 5.0.2 build to an old 5.0.2 build? What were you downgrading to?
Go to this folder:
Navigate to Surnia ->5.0.2
Look for the file XT1524_RETEUALL_MOTOE2... (it's near the middle of the list)
Download and try flashing everything it in using fastboot.
Click to expand...
Click to collapse
I was downgrading to kitkat 4.4.4 due to poor battery in lollipop 5.0.2. I'm downloading a xt1524reteuall rom right now but ir is going slowly.
pemhak said:
I was downgrading to kitkat 4.4.4 due to poor battery in lollipop 5.0.2. I'm downloading a xt1524reteuall rom right now but ir is going slowly.
Click to expand...
Click to collapse
Oh, you must have flashed something really wrong then. There are no 4.4.4 ROMs for this device. You would have flashed something totally incompatible and highly risky if you flashed 4.4.4 from somewhere. That may have wrecked your modem software too. Download and flash the proper XT1524-specific software with the correct modem. If you are unhappy with the performance of the stock ROM, you can flash scritch007's CM12.1.
squid2 said:
Oh, you must have flashed something really wrong then. There are no 4.4.4 ROMs for this device. You would have flashed something totally incompatible and highly risky if you flashed 4.4.4 from somewhere. That may have wrecked your modem software too. Download and flash the proper XT1524-specific software with the correct modem. If you are unhappy with the performance of the stock ROM, you can flash scritch007's CM12.1.
Click to expand...
Click to collapse
Ok, thanks. I will wait for download to complete and flash that image.
pemhak said:
Ok, thanks. I will wait for download to complete and flash that image.
Click to expand...
Click to collapse
Hi! Did you solve your problem? I'm kind of stuck on same problem and with no working solution yet.
EDIT: I tried the @squid2 with no success. Maybe I will send the phone to waranty....
Noeljunior said:
Hi! Did you solve your problem? I'm kind of stuck on same problem and with no working solution yet.
EDIT: I tried the @squid2 with no success. Maybe I will send the phone to waranty....
Click to expand...
Click to collapse
I did solve the problem with these steps.
1. Find and download the files for your region.
2. Unzip files to a folder with fastboot and adb.
3. Create stock.bat with these commands and run stock.bat within the same folder as above files.
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot erase customize
fastboot oem config carrier vzw
fastboot oem fb_mode_clear
fastboot reboot
(4. I needed to reunlock my Moto E 2nd Gen at Motorolas site, because i did relock it.)
5. Get into bootloader menu and flash this TWRP image (i can email it to you) within the same folder and flash it with fastboot.
6. Restart phone. Wait 2-3 minutes so it boots into android.
7. Hope I made it clear enough to follow the instructions, if you got questions please reply and I try to answer them. Sorry for my poor english.
pemhak said:
I did solve the problem with these steps.
1. Find and download the files for your region.
2. Unzip files to a folder with fastboot and adb.
3. Create stock.bat with these commands and run stock.bat within the same folder as above files.
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot erase customize
fastboot oem config carrier vzw
fastboot oem fb_mode_clear
fastboot reboot
(4. I needed to reunlock my Moto E 2nd Gen at Motorolas site, because i did relock it.)
5. Get into bootloader menu and flash this TWRP image (i can email it to you) within the same folder and flash it with fastboot.
6. Restart phone. Wait 2-3 minutes so it boots into android.
7. Hope I made it clear enough to follow the instructions, if you got questions please reply and I try to answer them. Sorry for my poor english.
Click to expand...
Click to collapse
And I'm back with my Moto E! Thank you! I wasn't doing some of those commands and with all those commands it works! Thank you!
So I relocked my bootloader after upgrading to marshmallow and forgot that I did that..... I tried to flash a stock boot img so I could utilize the ota, and it sort of bricked my tablet. Being a total dumbass I didn't realize that was the problem. Having had a similar issue before on my galaxy s4 where I follow a similar solution. I already have twrp installed, and it was asking for encryption for which there was none. So I wiped data and formatted to get past the encryption. On my s4 I was then able to reinstall the stock firmware and software. However when I tried to push the bootloader to my nexus I got this weird error.. can someone pleeeeeeease spare me and help me out. This tablet is my lifeline for college...
Don't get me in trouble for posting this image please lol, I just don't have enough posts. http ://i67.tinypic.com/v80vwl.jpg[/B][/B]
I figured it out, I was just being dumb. I just needed to use the fastboot commands and not try to use twrp
tdct12 said:
So I relocked my bootloader after upgrading to marshmallow and forgot that I did that..... I tried to flash a stock boot img so I could utilize the ota, and it sort of bricked my tablet. Being a total dumbass I didn't realize that was the problem. Having had a similar issue before on my galaxy s4 where I follow a similar solution. I already have twrp installed, and it was asking for encryption for which there was none. So I wiped data and formatted to get past the encryption. On my s4 I was then able to reinstall the stock firmware and software. However when I tried to push the bootloader to my nexus I got this weird error.. can someone pleeeeeeease spare me and help me out. This tablet is my lifeline for college...
Don't get me in trouble for posting this image please lol, I just don't have enough posts. http ://i67.tinypic.com/v80vwl.jpg[/B][/B]
I figured it out, I was just being dumb. I just needed to use the fastboot commands and not try to use twrp
Click to expand...
Click to collapse
If your able to access the bootloader menu or the fastboot menu, you could flash the stock and would fix the brick,soft brick or boot-loop.
Head to Google developer nexus image. Download the factory image of your devices on your devices. Extract all the files and copy paste the fastboot and adb files. Head to your devices and open the fastboot menu.
Type the following commends to restore your devices if the flashall did not work.
Fastboot oem unlock
Fastboot flash bootloader bootloader....
Fastboot reboot-bootloader
Fastboot erase boot
Fastboot flash boot boot.img
Fastboot erase recovery
Fastboot flash recovery recovery.img
Fastboot erase system
Fastboot flash system system.img (this could take up to 15 minutes, don't do anything to stop the process you can make your devices and a worst state)
Fastboot erase cache
Fastboot flash cache cache.img
Fastboot erase vendor
Fastboot flash vendor vendor.img
Fastboot reboot
This should fix your devices. I did not and it save each time I broke my device or anything similar.
If you want after all that. You can enter the following commends to relock your devices but don't make the same mistake you did before. If you want to avoid that same mistake just don't enter the commends.
What the guy above me said, also pro tip, some times not all the files will extract just keep extracting till all the image files are there.
Hey guys, I have a quick question about my warranty and root with the Elemental recovery. I rooted my tablet and loaded the recovery and now am having some issues UNRELATED to the modding of my tablet. Now I am going to send it in for repair and want to make sure they don't receive a modded tablet. Do I just need to do a factory reset or are there some other steps I need to take to make sure that when they receive my tablet, they can't tell it was ever modified? I read about a flash counter somewhere, so I'm not sure if I have to do anything with that, or if it really is as easy as a factory reset. I would love any and all help and look forward to hearing back.
Thanks a bunch,
Chris
ChrispyChris said:
Hey guys, I have a quick question about my warranty and root with the Elemental recovery. I rooted my tablet and loaded the recovery and now am having some issues UNRELATED to the modding of my tablet. Now I am going to send it in for repair and want to make sure they don't receive a modded tablet. Do I just need to do a factory reset or are there some other steps I need to take to make sure that when they receive my tablet, they can't tell it was ever modified? I read about a flash counter somewhere, so I'm not sure if I have to do anything with that, or if it really is as easy as a factory reset. I would love any and all help and look forward to hearing back.
Thanks a bunch,
Chris
Click to expand...
Click to collapse
I would say to do a back up if possible. After what I did is a flash the factory image and I relock the bootloader. If you don't flash the factory image and you don't relock the bootloader , they would just send it back.
Here are the commends for the flashing of recovery images.
Fastboot flash bootloader bootloader...
Fastboot reboot
Fastboot erase boot
Fastboot flash boot boot.img
Fastboot erase recovery
Fastboot flash recovery recovery.img
Fastboot erase system
Fastboot flash system system.img (this can take up to 15 minutes do not cancel process)
Fastboot erase cache
Fastboot flash cache cache.img
Fastboot erase vendor
Fastboot flash vendor vendor.img
Fastboot reboot bootloader
After you finish that, you must type the following command.
Command to relock your devices
Fastboot oem_lock
I hope this was helpful.
I don't see why you can't just use the "flash all" batch file. Does the batch file do something different?
whowatchlist said:
I don't see why you can't just use the "flash all" batch file. Does the batch file do something different?
Click to expand...
Click to collapse
Yes but must of the time it says the it could found files. Try it and if it doesn't flash all do the steps that I posted before
Just wanted to thank you jonny, I'm fresh on the newest factory image.
Its no problem
After successfully rooting using the recovery method, I figured I'd try re-locking the bootloader on this phone.
I have no idea why it was so difficult, but if you're looking to do the same, here's what you'll need to do:
You can obtain your firmware by using Lenovo assistant. Download speeds are good.
Ok, now I'm going to focus on the part where you've gone back to stock, unrooted of course and just want your bootloader locked, with no N/A at boot or how you're not able to receieve updates because you're such a bad person.
Enable hidden files if not already. You'll find your firmware in C:\ProgramData\LMSA\Download\RomFiles\*your firmware folder* if you used the assistant. Open power shell in your firmware folder obviously.
****MAKE SURE YOU ARE FLASHING THE CORRECT FIRMWARE FILES****
DO NOT DO THIS WHILE ROOTED. MAKE SURE TO BE STOCK... everything... with just the bootloader in the unlocked state.
Of course this will reset the device so don't forget to back up/save any important data
Obviously you'll need to have USB debugging enabled prior to flashing. Let's begin!
1) enter fastboot mode
2) check to make sure things are good (device properly detected and showing serial#) with fastboot devices command
3) Now Type (flash) ONLY these commands (files) and yes you need to do that first part THREE times:
fastboot oem lock
fastboot oem lock
fastboot oem lock
fastboot flash boot boot.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash system system.img_sparsechunk.9
fastboot flash vendor vendor.img
fastboot flash oem oem.img
fastboot oem lock
Then your powershell window should say:
(bootloader) Lock complete! Flash signed images after reboot if needed
OKAY [ 0.099s]
finished. total time: 0.101s
PS C:\ProgramData\LMSA\Download\RomFiles\SURFNA_your device firmware_DEFAULT_regulatory_DEFAULT_CFC.xml>
Your phone is now rebooting
If you are having difficulty locking a different device, then perhaps this may help...
In order to lock your bootloader, you must do it immediately after unlocking it.
Hello - it's been about 10 years since I played with any XDA stuff or custom roms. I have a stock Motorola G Power that bricked itself. It will not boot and recovery mode just gives me "No Command". Only option seems to be factory data reset.
Can anyone suggest a procedure to allow me to either re-install the stock software to get into the phone or recover my data? Sadly I had not backed anything up since last summer.
Should I just try to reflash a stock rom to see if i can get in? Will flashing the rom kill the onboard storage?
Cant find the exact same version either:
SOFIA10/QPMS30.80-63-6-8-5
I found 63-6-8-10 and 63-6-8-3 but not the exact same. Phone is Retail US.
Any help would be appreciated.
Ok found the stock rom that matches 63-6-8-5. Do I just try to flash that back to get back into the phone with my existing data?
Uberhare said:
Ok found the stock rom that matches 63-6-8-5. Do I just try to flash that back to get back into the phone with my existing data?
Click to expand...
Click to collapse
You can try flashing the stock from and just skip the erase userdata step.
The firmware contains a file named flash_file.xml contains the flash commands
You can use Online FlashFile Converter to convert the .XML to simple fastboot commands.
You also should check if getvar is-userspace
Code:
fastboot getvar is-userspace
if yes you need to switch between fastboot and fastbootd
If it's no you don't need to worry about fastbootd
[Guide] Using Fastboot.exe with Motorola devices
Guide: Using Fastboot.exe with Motorola Devices If your device has its own section please post in that section. You can ping me with @sd_shadow MediaTek or Qualcomm Chip? Do I have a MediaTek Device? see post #26 Info: If you have a MediaTek...
forum.xda-developers.com
sd_shadow said:
You can try flashing the stock from and just skip the erase userdata step.
Click to expand...
Click to collapse
Do I need to unlock the bootloader for flashing an original file?
Uberhare said:
Do I need to unlock the bootloader for flashing an original file?
Click to expand...
Click to collapse
No, you shouldn't need to but it's easier if the bootloader is unlocked.
Unlikely, you can unlock the bootloader now anyways.
Unless you enabled OEM Unlocking in Dev Options already.
If you did enable OEM Unlocking, I would Unlock the bootloader.
[Guide]Un/locking Motorola Bootloader
UnLocking and ReLocking Motorola Bootloader https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-a Moto Bootloader Unlocking site Re-Locking see Post #4 More about bootloader UnLocking Post #2 Can my...
forum.xda-developers.com
Are the steps any different if the bootloader is locked? You mention it is easier if it is unlocked.
Thank you for the tutorial.
Uberhare said:
Are the steps any different if the bootloader is locked? You mention it is easier if it is unlocked.
Thank you for the tutorial.
Click to expand...
Click to collapse
Easier may not be the right word.
If the bootloader is unlocked, you are less likely to have issues flashing.
ADB devices - does not return any devices, although I can see the phone is connected with the Motorola recovery tool.
fastboot getvar is-userspace returns:
is-userspace: no
Finished. Total time: 0.002s
I found where fastbootd is.
C:\Android>fastboot getvar is-userspace
is-userspace: yes
Finished. Total time: 0.002s
Uberhare said:
ADB devices - does not return any devices, although I can see the phone is connected with the Motorola recovery tool.
Click to expand...
Click to collapse
adb devices will not work if the device is in fastboot mode.
Use fastboot devices when it's in fastboot mode.
sd_shadow said:
adb devices will not work if the device is in fastboot mode.
Use fastboot devices when it's in fastboot mode.
Click to expand...
Click to collapse
adb devices does not show anything in either mode. That is why I looked for fastboot mode. Should I trouble shoot that first?
This is what I want with the erase commands deleted at the end? The erase commands are what will kill my data or is there something else I need to remove?
fastboot getvar max-sparse-size
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash vbmeta vbmeta.img
fastboot flash radio radio.img
fastboot flash bluetooth BTFM.bin
fastboot flash dsp dspso.bin
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash dtbo dtbo.img
fastboot flash recovery recovery.img
fastboot flash super super.img_sparsechunk.0
fastboot flash super super.img_sparsechunk.1
fastboot flash super super.img_sparsechunk.2
fastboot flash super super.img_sparsechunk.3
fastboot flash super super.img_sparsechunk.4
fastboot flash super super.img_sparsechunk.5
fastboot flash super super.img_sparsechunk.6
fastboot flash super super.img_sparsechunk.7
fastboot flash super super.img_sparsechunk.8
fastboot flash super super.img_sparsechunk.9
fastboot flash super super.img_sparsechunk.10
fastboot flash super super.img_sparsechunk.11
fastboot flash super super.img_sparsechunk.12
fastboot flash super super.img_sparsechunk.13
fastboot flash super super.img_sparsechunk.14
fastboot flash super super.img_sparsechunk.15
fastboot erase carrier
fastboot erase ddr
fastboot oem fb_mode_clear
echo Press any key to restart the phone!
pause
fastboot reboot
exit
Looks like phone doesn't respond to commands in fastbootd only normal.
I successfully ran the batch file, but the phone still doesn't boot. What is my next step? (besides throwing it against the wall!)
Phone accepts all the files for the current version of software, as well as commands to clear some of the labels. So the userdata is still there, I just can't get to it. Can you read these with a jtag like the older phones?
What if I try to roll it forward to Android 11 through the stock roms?