Database Users

Nexus S Official factory images for 9020t & 9023

http://code.google.com/android/nexus/images.html#yakju
https://groups.google.com/forum/?fromgroups#!topic/android-building/b50nY_onbP4

^Thanks.
This can be flashed via CWM recovery ?
(after a 'fastboot oem lock/unlock' ?)

No. They are fastboot images. If you're not sure what these are and how to use them then I would not mess with them.

^ gotcha
can someone please put up a tutorial/guide to do this.
I really want to try this.

The shell script gives you the exact fastboot commands to run if you want to do it manually. And it will restore your phone to a true factory state with 4.0.4.

if i will use the factory img the baseband version in bootloader will be change? i see now i9020xxkl1 but my nexus is i9023?

I was wondering the same .. In the zip it says :require board=herring
require version-bootloader=I9020XXJK1|I9020XXKA3|I9020XXKI1|I9020XXKL1
require version-baseband=I9020XXJK8|I9020XXKB1|I9020XXKD1|I9020XXKF1|I9020XXKI1|I9020UCKB2|I9020UCKD1|I9020UCKF1|I9020UCKJ1|I9020KRKB3|M200KRKC1
So it should be okay , because when I reboot into the bootloader of my phone it says :
Bootloader version: I9020XXKL1
Baseband version : I9020XXKI1
My phone actually is a I9023 so I gues the images are okay to flash on a I9023

Just noticed that the full ROM version for Nexus S is 4.0.4 IMM76D. Wouldn't be better to flash this complete rom instead of the partial patch OTA which is clearly giving troubles?

HELPPPPP
can someone please put up a tutorial/guide to do this.
I really want to try this.

i wrote a guide
http://forum.xda-developers.com/showthread.php?t=1572307

goldy_rocky said:
can someone please put up a tutorial/guide to do this.
I really want to try this.
Click to expand...
Click to collapse
(No time to write a full tutorial right now but...) I'd say...
Pls wait for someone experimented to confirm what I say because I couldn't try it to confirm it works right now... And also try it at your own risk...
If your bootloader is not unlocked, follow PART 1 & PART 2 of this tutorial. (you will loose data)
(Note that ADB is not in tools folder anymore but in /platform-tools so that's where the part2 cmd as to be runned from)
Then if windows (I guess you would know what to do if on Linux) use 7zip to extract (2 times) all files from the archive.
Then copy the files to the /platform-tools folder.
The open a command prompt in that folder (shift+right click>open a command prompt here).
Then use the commands provided in the .sh script to flash all files (you can read it easily with Notepad++ for instance) one by one...
Note I don't think you can run the "sleep 5" cmd manually but you can of course wait 5' manually .
Code:
fastboot flash bootloader bootloader-crespo-i9020xxkl1.img
fastboot reboot-bootloader
sleep 5
fastboot flash radio radio-crespo-i9020xxki1.img
fastboot reboot-bootloader
sleep 5
fastboot -w update image-soju-imm76d.zip
I'm not really sure if bootloader will be locked at this time but my guess is no so just reboot the bootloader ("fastboot reboot-bootloader" or shut down the device then "Boot the SNS into the Bootloader Interface, by holding Volume UP & Power button" and look for the "LOCK STATE - LOCKED" or "LOCK STATE - UNLOCKED").
If "LOCK STATE - UNLOCKED" you may want to lock the bootloader again, just follow part2 again and replace "fastboot oem unlock" by "fastboot oem lock"
EDIT :
ale.landra91 said:
i wrote a guide
http://forum.xda-developers.com/showthread.php?t=1572307
Click to expand...
Click to collapse
You just made me feel so useless ...

First of all, the credits goes to "a2b". I am only put his work here via a link.
Secondly, PLEASE KEEEP IN YOUR MIND THAT NEITHER ME OR "a2b" IS RESPONSABLE FOR ANY LOSS OF YOURS IF YOUR PHONE GET BRICKED.
The thrid, I have tried the method on my Nexus i9023. It works perfectly for me. BUT, I cannot gurentee it works for everyone.
Okay, I just flashed the factory img according to a2b's tutorial for Galaxy Nexus. But for me I just needed to change the names for few files. If you cannot figure out what to change, I suggest you follow albundy2010's advice on post #3
Good luck!
http://androidtobe.blogspot.com/2011/12/galaxy-nexus-installing-ics-402-from.html

Seems most are not familiar with doing this so here are some things you should know.
Doing this will wipe EVERYTHING off your phone. Yes, everything including /sdcard.
Do not be a fool and flash these images to the 4g.
I am not certain about this and if you it and your phone gets messed up do not blame me.
The 9020a should be able to run this factory image. Check to see what version of the bootloader you have. If it matches one of the bootloaders in the .sh script you should be fine. I would NOT flash the bootloader included in this factory image myself. Since I do not know for sure if they are the same for both GSM models. If you follow the guide minus the parts where you flash the bootloader and the radio image I believe it will work.
Again if you try this and it breaks your phone that is on you. I am not responsible for it. I do not have a 9020a to test this on and verify it. I am fairly certain it will work perfectly. If anybody tries it let me/us know the outcome.

is there any specific advantage in flashing the factory image as opposed to flashing the incremental update ? I successfully flashed 4.0.4 using CWR over a full rom installation of 4.0.3 back from December. I wonder if there may be some subtle differences that maybe make it a bit better option to install the factory image ?

mindwalkr said:
is there any specific advantage in flashing the factory image as opposed to flashing the incremental update ? I successfully flashed 4.0.4 using CWR over a full rom installation of 4.0.3 back from December. I wonder if there may be some subtle differences that maybe make it a bit better option to install the factory image ?
Click to expand...
Click to collapse
No
Sent from my Nexus S using XDA App

I used the flash-all.sh script from the factory image file and it didn't wipe the sdcard. Backed it up beforehand anyway just in case. Recovery was broken on reboot. Flashed CWM recovery and all good. i9023.

[Q][Solved] Where should I begin as a beginner?

Edit:
[Procedure] http://forum.xda-developers.com/showpost.php?p=64841837&postcount=27
Edit/
I am creating this thread dedicated for me and other beginners "noobs".
Where should I begin as a beginner?
I am looking to unlock and root with latest MM that motorola supplies.
Things you should know about me:
I have no idea how to use adb.
I have no idea how to unlock & root or even if I should but I don't like ads.
I have no idea which firmware to use.
http://forum.xda-developers.com/moto-x-style/development/pure-firmware-tuff-wip-t3224833
http://forum.xda-developers.com/mot...rom-stock-rooted-debloated-x1575-6-0-t3262242
I am completely lost.
I have not gotten my phone yet, I ordered it this morning and will be here Friday. I am just trying to compile sources and info.
Thanks a bunch guys, I really need help with this.

One piece of advice for starters just since you used the word noob. Never mod your phone on a low battery. You can mess a phone up enough to break offline charging, and without a removable battery that you can swap out or charge in a cradle that could get awkward in a hurry on this phone. I always make sure I'm >75% just in case. You can fastboot your way out of all kinds of trouble; but not if your battery is dead and your phone is so screwed up it is not offline charging.
Your phone will probably show up with Android 5.1.1 installed, at least I got mine about 3 weeks ago and it did. Once it is through initial setup it should want to apply an OTA to Android 6.0 right away; if not check for it in Settings -> About -> System updates and it should find one. Just let it update before you do any setup or app downloading.
Once you're on MM, before you do any setup you have to unlock your bootloader if you intend to root. You'll get all the warnings about voiding warranty and here there be dragons, so be prepared for that. Also, unlocking the bootloader will wipe your internal storage, so don't bother with any setup or app downloading before you do it.
Start with Heisenberg's thread. It is a great guide on how to setup your computer for adb and fastboot as well as all the syntax you need for unlocking the bootloader and installing a custom recovery. Make sure to get the 2.8.7.1 version of TWRP that is patched to work with the MM bootloader.
When you boot to TWRP recovery for the first time it will ask if you want to keep system read only. Keep system read only and make a backup immediately. I usually make one backup of boot, system, and data, and a separate one of just efs; don't worry if you don't understand, you'll figure it out when you get there. TWRP is all touch based and pretty intuitive. This way you have good, untouched system backup to fall back on just in case.
When it comes to rooting MM, don't use the old system install method. Flash a SuperSU from this experimental systemless root thread (I used this instead of the ivcarlos method linked to the Heisenberg thread because it is more automated and easier). I can vouch for the 2.62-20151210170034 version of SuperSU. I've used it to root stock MM on this phone 3 or 4x as I've restored backups and changed kernels. I've heard the 2.64 and above SuperSU versions are not working with this phone on MM, and the older traditional system root methods like the v2.49 version that is linked to the Heisenberg thread are causing bootloops on MM. Don't panic on first boot after the systemless root; it appears to bootloop once but comes up normally the second time.
One other thing, TWRP doesn't seem to be able to detect the systemless rooting method, and it really wants your phone to be rooted. If/when TWRP offers to automatically install SuperSU, don't let it - ever - it will keep asking. It must use the old method that causes bootloops on MM, not the new systemless method linked above.
Once you're all rooted and settled in, if you get sick of the unlocked bootloader warning you can fix it by reading up in this thread. Just be sure to read carefully and get the MM logo and not the LP logo.

Wow, thank you so much for the long type up.
Duly noted and this is a great start. May I continue here if I run into any problems?
I think ima have fun with this phone
I am into tinkering with devices, "sometimes linux" etc, like my PC OS win7x64 is modified big time, so I probably will catch on with unlocking rooting etc very quickly.
I got chillz and cannot wait!

Read a lot. Do a lot of reading on the topic before trying it. Basically learn all the possible errors or negative outcomes before they happen, so your not blindsided and are ready for anything that can happen.

gokart2 said:
Read a lot. Do a lot of reading on the topic before trying it. Basically learn all the possible errors or negative outcomes before they happen, so your not blindsided and are ready for anything that can happen.
Click to expand...
Click to collapse
Will do. I was reading, flashing can screw up the modem,wif and what ever else.
I hope I don't screw it up.

Hitti2 said:
Will do. I was reading, flashing can screw up the modem,wif and what ever else.
I hope I don't screw it up.
Click to expand...
Click to collapse
Good luck :good:
I just noticed one thing that might not be entirely clear in the Heisenberg thread. It says to enable adb in the Settings -> Developer Options menu, but by default you won't have a Developer Options menu.
To get one, go into Settings -> About Phone, scroll all the way to the bottom, and tap on build number about 8 or 10 times. Your phone will say something to the effect of congratulations now you're a developer, and you'll have the menu.
Edit: i just noticed it says how to enable developer options further down the page

ty, I will need it lol.
Dev options were on my S5 too. My pops showed me how to on the S5, kinda hoping it was the same way to enable them, turned out to be. Cool.

gokart2 said:
Read a lot. Do a lot of reading on the topic before trying it. Basically learn all the possible errors or negative outcomes before they happen, so your not blindsided and are ready for anything that can happen.
Click to expand...
Click to collapse
^^^This^^^
and remember what XDA is really for ...http://forum.xda-developers.com/showpost.php?p=2031989
with that, enjoy all the reading, and do not be afraid to look at other sites too, there are even videos around that can help guide you...
and there are fellow members here to help...but most questions have already been asked and answered, so search first! Cheers! :highfive:

This might sound so stupid.
So, I will begin with the recommendation of installing twrp as my first step.
http://forum.xda-developers.com/showpost.php?p=64545146&postcount=131
1) Be sure to get the newest TWRP that has been patched for M.
Click to expand...
Click to collapse
How do I go on installing this TWRP? Does it include flashing TWRP to the phone? Or is an app? I don't understand.
How many ROMs can be flashed to the phone, 2? TWRP & Marshmallow?

Hitti2 said:
This might sound so stupid.
So, I will begin with the recommendation of installing twrp as my first step.
http://forum.xda-developers.com/showpost.php?p=64545146&postcount=131
How do I go on installing this TWRP? Does it include flashing TWRP to the phone? Or is an app? I don't understand.
How many ROMs can be flashed to the phone, 2? TWRP & Marshmallow?
Click to expand...
Click to collapse
Sounds like you need to do more studying and reading
TWRP is not a ROM, it is a custom recovery image, which allows you to flash ROMs.
Start here..http://androiding.how/root-moto-x-pure/
Then go here..http://forum.xda-developers.com/mot...l-windroid-universal-android-toolkit-t3206883 for a good tool. (May have already been linked above...)

[Q] Where should I begin as a beginner?
At the beginning, of course.
Sorry couldn't resist...

Naddict said:
Sounds like you need to do more studying and reading
TWRP is not a ROM, it is a custom recovery image, which allows you to flash ROMs.
Start here..http://androiding.how/root-moto-x-pure/
Then go here..http://forum.xda-developers.com/mot...l-windroid-universal-android-toolkit-t3206883 for a good tool. (May have already been linked above...)
Click to expand...
Click to collapse
Tyvm.
Before I proceed, I need to backup, right? How do I go forth doing a backup?
Also, I am updated on MM, does those two links above work on MM?

Hitti2 said:
Tyvm.
Before I proceed, I need to backup, right? How do I go forth doing a backup?
Also, I am updated on MM, does those two links above work on MM?
Click to expand...
Click to collapse
after you unlock and install custom recovery, you use TWRP (the custom recovery) to create the backup...
as you are on MM, you cannot use the "all in one" application that I provided in the link...so you will have to manually install/flash your rom

Wow im so frustrated. I think i give up. There is no guides upto date to do exactly twrp, backup, install w/e n root for ota mm.
I'll donate 30 usd via paypal if someone can.

Hitti2 said:
Wow im so frustrated. I think i give up. There is no guides upto date to do exactly twrp, backup, install w/e n root for ota mm.
I'll donate 30 usd via paypal if someone can.
Click to expand...
Click to collapse
Clearly you are impatient (not trying to be rude here), - XDA truly is not a place to pay for someone to do it for you, XDA is about learning and development, there are several places that a search will get you what you need. Many members have also posted links above to vast amount of information (specifically this post and this entire thread here http://forum.xda-developers.com/showpost.php?p=64183396&postcount=151 and here too http://forum.xda-developers.com/showpost.php?p=64311581&postcount=171) that you should take time to read and then, as you move through these things then you ask questions.
Offering to pay to have someone do it for you is really not what this site is about.
Read, do google searches...it has been done a hundred time already mate, take the time to learn what it is you are doing before actually doing it.

I dont have 400 to spare for for another phone if i brick this one because i was pointed to all kinds of mixed links. Ionno ill wait till someone comes up with a guide then.
Thanks.
Edit:
Let it be known as well, because you know how to milk a cow doesn't mean I know how to milk a cow. Or change a complete motor out of a vehicle etc.

Not being a smartarsh either. I'll prob end up like this guy https://www.reddit.com/r/MotoX/comments/3z2e6g/stuck_rooting_moto_x_pure_on_60/
And I read this, http://forums.androidcentral.com/moto-x-pure-edition/622331-6-0-marshmallow-root.html#post4899736
Dunno which one to go for.
I'm done for today, I'll come back tomorrow to upset with this.

Hitti2 said:
I dont have 400 to spare for for another phone if i brick this one because i was pointed to all kinds of mixed links. Ionno ill wait till someone comes up with a guide then.
Thanks.
Edit:
Let it be known as well, because you know how to milk a cow doesn't mean I know how to milk a cow. Or change a complete motor out of a vehicle etc.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=2031989
Hitti2 said:
Not being a smartarsh either. I'll prob end up like this guy https://www.reddit.com/r/MotoX/comments/3z2e6g/stuck_rooting_moto_x_pure_on_60/
And I read this, http://forums.androidcentral.com/moto-x-pure-edition/622331-6-0-marshmallow-root.html#post4899736
Dunno which one to go for.
I'm done for today, I'll come back tomorrow to upset with this.
Click to expand...
Click to collapse
Looks to me like several folks in there offered suggestions on how to successfully get root ...and again, as my last helpful post here...you really need to read Heisenberg's thread, that guide works, and from what I can tell, you have to use systemless root.

Ok, I will follow
Intro
This thread will serve as a location for basic how-to guides for the Moto X Pure. I'm going to start off with a couple of the more obvious ones and go from there. If anyone has any suggestions for additions please feel free to let me know.
Prerequisites:
You'll need a working adb/fastboot environment on your PC to get through some of these guides. Go here to download the Android SDK, which will give you most updated version of adb and fastboot. Scroll to the bottom of the page and find Other Download Options>SDK Tools Only, and grab the right version for your OS. While it's downloading create a folder in C:\ called SDK (C:\SDK). Once you've downloaded the zip you can extract it into your C:\SDK folder. Navigate to C:\SDK\android-sdk-windows and open SDK Manager.exe. In SDK Manager you need to install the following packages:
Tools> Android SDK Tools, Android SDK Platform-tools
Extras> Android Support Library
Once you have installed those, inside C:\SDK you should see some new folders, one of them will be called platform-tools, within that folder you should see fastboot.exe and adb.exe. I'll refer to this as your fastboot folder/directory or working folder/directory during this guide. To make sure adb is correctly installed, open a command prompt from within your fastboot folder (hold shift + right click, select open command prompt here) and issue this command:
Code:
adb version
If it returns a version number for Android Debug Bridge then you're good to go.
You'll find Motorla drivers here, download it and install, then reboot your PC.
You can test adb by connecting your device to your PC while booted into Android (making sure that adb/usb debugging is enabled in Settings>Developer Options) with the screen unlocked and issuing this command:
Code:
adb devices
It should return your device serial number, if so, adb is working.
You can test fastboot by connecting your device to your PC while booted into fastboot mode (power + volume down) and issuing this command:
Code:
fastboot devices
It should return your device serial number, if so, fastboot is working.
By attempting any of the processes listed this thread you accept full responsibility for your actions. I will not be held responsible if your device stops working, catches on fire, or turns into a hipster and claims to have been modified before it was cool.
Index
How To Unlock Your Bootloader
How To Install A Custom Recovery On Your Device
How To Make A Nandroid Backup With TWRP Recovery
How To Root Your Stock Rom
How To Install A ROM with TWRP Recovery
How To Install A Custom Kernel With TWRP Recovery
How To Make Sure You Can Pretty Much Always Recover From An Accidentally Wiped System
1. How To Unlock Your Bootloader
Go into About Phone in Settings, click on Build Number 7 or 8 times until it says you have enabled Developer Options. Go back to Settings and enter the newly opened Developer Options section, scroll and click on the Enable OEM Unlock option.
Power off your phone then boot into fastboot mode (power + volume down).
Connect your phone to your PC via usb cable.
Open a command prompt from within your fastboot folder (navigate to where you have fastboot.exe located on your PC, shift + right click anywhere within that folder, select open command prompt here).
Check your fastboot connection by issuing this command:
Code:
fastboot devices
It should return your device serial number, if not you need to make sure your drivers are installed correctly.
Once you've confirmed your fastboot connection issue this command:
Code:
fastboot oem get_unlock_data
It should return something like this:
Code:
(bootloader) 0A40040192024205#4C4D3556313230
(bootloader) 30373731363031303332323239#BD00
(bootloader) 8A672BA4746C2CE02328A2AC0C39F95
(bootloader) 1A3E5#1F53280002000000000000000
(bootloader) 0000000
Copy that code (with no spaces between the characters) and paste it somewhere for safekeeping, you'll use it in a minute.
Go to the Motorola bootloader unlocking page. You'll need to create an account with Motorola if you don't already have one. Once you're signed in you can scroll down to step 6 and paste the above code into the text field and hit the “can my device be unlocked” button.
Read the terms and conditions and accept them if you agree (you can't continue unless you accept).
Click the “request unlock key” button and an email with your unlock token will be sent to the email account that you signed up with.
Once you have retrieved the token from the email you can use it within the following command to unlock your bootloader:
Code:
fastboot oem unlock xxxxxxxxxx
(Replace the xxxxxxxx with your unique unlock token)
Your bootloader is now unlocked!
Reboot with this command:
Code:
fastboot reboot
It's now safe to disconnect your usb cable.
Please note: this will erase all user data from your device, it is best to do this before you really start using the device and installing apps or putting data on the internal storage
2. How To Install A Custom Recovery On Your Device
Prerequisites: unlocked bootloader.
Download the recovery of your choice, here's TWRP.
Make sure you check the md5 to verify its integrity (where possible).
Place the file in your fastboot folder (this is where fastboot.exe is located on your PC).
Put the phone in fastboot mode and connect it to your PC via usb cable.
Open a command prompt from within your fastboot folder (shift + right click, select open command prompt here), and enter the following commands:
Code:
fastboot flash recovery <filename>.img
(Replace <filename> with the actual filename of the recovery, the recovery filename in the command will change depending on which recovery you're flashing)
Wait for the recovery to flash, it'll only take a few seconds, you'll get a finished message in your command prompt window once it's done.
It's now safe to disconnect your usb cable.
Don't reboot the phone normally, use the volume buttons to highlight recovery and press the power button to select it. This will stop the stock OS from patching it with the stock recovery in boot. Once you've booted into TWRP like this once, you can reboot normally.
3. How To Make A Nandroid Backup With TWRP Recovery
Prerequisites: unlocked bootloader, TWRP recovery.
A nandroid backup is a very important thing to have before installing any custom software on your device. It's basically a backup of your stock system that you can fall back on if anything goes wrong or if you just want your stock ROM back. You can also use the backup tool to create a backup of your favourite ROM set up exactly the way you like it. The backup you create can be easily restored using the restore tool in TWRP recovery.
All you need to do is enter TWRP recovery, select the backup option from the TWRP home screen, check the system/data/boot boxes, and swipe to backup. The process will take a few minutes.
Click to expand...
Click to collapse
& I will follow
Hello guys!
I make my own ROOT (systemless, thanks for Chainfire) images for Moto X Style with Marshmallow (build MPH24.49-18). Its use "experimental" systemless SuperSU version 2.56 - more info on http://forum.xda-developers.com/show...35&postcount=2. No need replace bootloader or recovery. Still need unlocked booloader.
Because TWRP didn't work in this version of bootloader (0xA048), I cooked "su.img" in a Linux box and used "/data/local/tmp" as bridge (accessible by ADB).
WARNING! I am not responsible for any harm on your phone. When you're not sure if you can do it, leave it!
For use, you need
1) unlocked bootloader.
2) if your bootloader not unlocked, make sure you have copy of your data, because this process will erase your device.
3) install ADB and FASTBOOT on your pc using minimal ADB or Android SDK.
4) install ADB drivers from Motorola or Universal ADB.
5) download provided files.
6) download SuperSU ver. 2.56 from http://forum.xda-developers.com/apps...ellow-t3219344.
Steps:
1) extract files in a folder of your choice (su.img, boot.img).
2) extract Superuser.apk from SuperSU-v2.56-20151030013730.zip from common folder.
3) enable USB debugging on Android.
4) connect your device on pc.
5) open a command prompt in a new folder.
6) type "adb push su.img /data/local/tmp" without quotes.
7) type "adb install Superuser.apk" without quotes.
8) now reboot your device into fastboot mode by typing "adb reboot bootloader".
9) type "fastboot flash boot boot.img" without quotes.
10) type "fastboot reboot" without quotes.
And enjoy!
Now you have a rooted MotoX Style Marshmallow. To apply any OTAs, you only need reflash stock boot.
Click to expand...
Click to collapse
I still think its going to brick but uhwell.

So far so good, I've got it unlocked.
I apologize for my ignorance. I am gonna take it a step at a time.
Doing step one "unlocking" was scary but it went good.
Wish me luck!

Help with loss of root/twrp

I need help! Here’s the story. Sorry for the lengthy post. TL;DR at the bottom..
- Was on B32, unlocked BL, TWRP installed, rooted with SuperSU
- Updated to B35, but lost TWRP and root (I don’t know how, but I assume I must have wiped the wrong things? - system? - I’m clearly a novice)
- Now I’m on B35 with an unlocked BL, but despite days of searching and researching, I can’t for the life of me figure out how to get TWRP reinstalled. I want to have TWRP before trying Magisk (have never used Magisk before, but would like to try it this time instead of SuperSU)
- From my Mac, using terminal, adb recognizes my devices.
- “adb reboot boot loader” gets me to a list of options “power off, restart, recovery, fastboot, back to previous page”. Choosing fastboot simply restarts the phone. What should “fastboot mode” look like?
- I tried flashing TWRP via adb while on this page and terminal stopped at “waiting for any device” and did nothing
My conclusion is that I need to downgrade to whatever latest version allows fastboot commands to work properly? Is this B15? If so, is the only available B15 zip the one that is on the ZTE website? Do I just wipe data/dalvick/cache and flash this zip?
Do I not need a Bootstock and Systemstock like @DrakenFX usually posts? That’s how I’m used to doing any updates.
Thank you all for your help, both past and present!
TL;DR: Would like to downgrade from B35 to B15 so that I can install twrp and root again. What’s the best way to do this and where can I find the appropriate files?

alajoy said:
I need help! Here’s the story. Sorry for the lengthy post. TL;DR at the bottom..
- Was on B32, unlocked BL, TWRP installed, rooted with SuperSU
- Updated to B35, but lost TWRP and root (I don’t know how, but I assume I must have wiped the wrong things? - system? - I’m clearly a novice)
- Now I’m on B35 with an unlocked BL, but despite days of searching and researching, I can’t for the life of me figure out how to get TWRP reinstalled. I want to have TWRP before trying Magisk (have never used Magisk before, but would like to try it this time instead of SuperSU)
- From my Mac, using terminal, adb recognizes my devices.
- “adb reboot boot loader” gets me to a list of options “power off, restart, recovery, fastboot, back to previous page”. Choosing fastboot simply restarts the phone. What should “fastboot mode” look like?
- I tried flashing TWRP via adb while on this page and terminal stopped at “waiting for any device” and did nothing
My conclusion is that I need to downgrade to whatever latest version allows fastboot commands to work properly? Is this B15? If so, is the only available B15 zip the one that is on the ZTE website? Do I just wipe data/dalvick/cache and flash this zip?
Do I not need a Bootstock and Systemstock like @DrakenFX usually posts? That’s how I’m used to doing any updates.
Thank you all for your help, both past and present!
TL;DR: Would like to downgrade from B35 to B15 so that I can install twrp and root again. What’s the best way to do this and where can I find the appropriate files?
Click to expand...
Click to collapse
I'm not sure where you read all that BS, but if your bootloader is unlocked then you can install TWRP via EDL (Or fastboot if you have it). No need to downgrade for anything :laugh: in the past you would have needed to downgrade in order to unlock the bootloader, now it's not even needed
Download EDL Tool by djkuz and install TWRP with that one. Or you can use axon7tool by tennear, but it's much more finicky and ran entirely by commands (no UI).
And just to avoid more trouble, DO NOT LOCK THE BOOTLOADER! You do that with the system even barely modified and you brick the phone. A bunch of people tried to do something, got scared because they made a simple correctable mistake and just locked the bootloader thinking everything would get restored to stock - doesn't work that way.
Not saying you will do this, but I've seen about 4 or 5 people that started just like you and ended up doing that

Choose an username... said:
I'm not sure where you read all that BS, but if your bootloader is unlocked then you can install TWRP via EDL (Or fastboot if you have it). No need to downgrade for anything :laugh: in the past you would have needed to downgrade in order to unlock the bootloader, now it's not even needed
Download EDL Tool by djkuz and install TWRP with that one. Or you can use axon7tool by tennear, but it's much more finicky and ran entirely by commands (no UI).
And just to avoid more trouble, DO NOT LOCK THE BOOTLOADER! You do that with the system even barely modified and you brick the phone. A bunch of people tried to do something, got scared because they made a simple correctable mistake and just locked the bootloader thinking everything would get restored to stock - doesn't work that way.
Not saying you will do this, but I've seen about 4 or 5 people that started just like you and ended up doing that
Click to expand...
Click to collapse
Wow, thanks so much for responding to this. Sounds like this should be easy! A couple of questions before I go about following your advice:
1). Do I download EDL Tool to my computer or phone??
2). If I'm downloading it to my computer, does it matter that I'm using a mac?
Thanks again for your help!

alajoy said:
Wow, thanks so much for responding to this. Sounds like this should be easy! A couple of questions before I go about following your advice:
1). Do I download EDL Tool to my computer or phone??
2). If I'm downloading it to my computer, does it matter that I'm using a mac?
Thanks again for your help!
Click to expand...
Click to collapse
Oh, skipped that part. EDL Tool is a .bat. I'm pretty sure you won't be able to run it on a Mac. If you can find a Windows PC somewhere to do this, it'd be much better...
But there's another way.
Issuing "adb reboot bootloader" effectively sends you into fastboot. That list you mentioned is fastboot (if it says "Start" in green, and you can scroll that, it is fastboot). Just use fastboot from the pc: Put TWRP on the fastboot folder on the PC, then issue "fastboot flash recovery twrp.img" with "twrp.img" being whatever the twrp file name is. After that issue "fastboot reboot recovery". And as soon as you are on TWRP, DON'T GET OUT OF IT. Just wipe data, system, caches; then flash a system (e.g. b10 bootstack and stocksystem), then also flash Magisk, and THEN boot to system

Choose an username... said:
Oh, skipped that part. EDL Tool is a .bat. I'm pretty sure you won't be able to run it on a Mac. If you can find a Windows PC somewhere to do this, it'd be much better...
But there's another way.
Issuing "adb reboot bootloader" effectively sends you into fastboot. That list you mentioned is fastboot (if it says "Start" in green, and you can scroll that, it is fastboot). Just use fastboot from the pc: Put TWRP on the fastboot folder on the PC, then issue "fastboot flash recovery twrp.img" with "twrp.img" being whatever the twrp file name is. After that issue "fastboot reboot recovery". And as soon as you are on TWRP, DON'T GET OUT OF IT. Just wipe data, system, caches; then flash a system (e.g. b10 bootstack and stocksystem), then also flash Magisk, and THEN boot to system
Click to expand...
Click to collapse
"adb reboot bootloader" takes me to the start up screen that says "your device software cannot be checked for corruption..." etc. and gives you 5 sec to either press up or down on volume keys to get to list: “power off, restart, recovery, fastboot, back to previous page”, but the list is all white. If I select "fastboot" it reboots the phone and starts that cycle over again at the "your device software cannot be checked for corruption..." etc page.
Nowhere am I given a chance to use fastboot commands. I'm never on the page with the green "Start".
..This all seemed a lot simpler on my Nexus 5..
Thanks for your help/patience.

alajoy said:
"adb reboot bootloader" takes me to the start up screen that says "your device software cannot be checked for corruption..." etc. and gives you 5 sec to either press up or down on volume keys to get to list: “power off, restart, recovery, fastboot, back to previous page”, but the list is all white. If I select "fastboot" it reboots the phone and starts that cycle over again at the "your device software cannot be checked for corruption..." etc page.
Nowhere am I given a chance to use fastboot commands. I'm never on the page with the green "Start".
..This all seemed a lot simpler on my Nexus 5..
Thanks for your help/patience.
Click to expand...
Click to collapse
I thought you had fastboot since you described the 5 seconds screen and both are very similar. It's normal not to have it though.
I think there's some version of axon7tool for Linux but I'm not sure at all. The best way would be to find a Windows computer.
I wonder how you actually installed TWRP the first time? Via fastboot?
As soon as you get TWRP you should be able to run a few commands to get fastboot back just to have it around.

Choose an username... said:
I thought you had fastboot since you described the 5 seconds screen and both are very similar. It's normal not to have it though.
I think there's some version of axon7tool for Linux but I'm not sure at all. The best way would be to find a Windows computer.
I wonder how you actually installed TWRP the first time? Via fastboot?
As soon as you get TWRP you should be able to run a few commands to get fastboot back just to have it around.
Click to expand...
Click to collapse
I have adb and fastboot installed on my Mac and I can't remember how I got it working on my phone in the first place, but I've only ever used a Mac for all this. Terminal recognizes my device and responds to commands until I try "fastboot flash recovery twrp.img" then it says "<waiting for any device>" and does nothing.
Thanks again for the help. I'll keep hunting though. I don't have access to any Windows computer.
Cheers

100003562 Onn 10.1 Android 11 (Bootloader Unlock, Magisk Root)

Hey folks I spent some time working on this yesterday (dumping Rom, Patching etc) so I thought I'd share. I am including the files I used to get this work.
This is for 100003562 Walmart Onn Tablet
I can't comment on other Onn models because I don't have any.
If your tablet goes into meltdown mode, I'm not responsible. I'm sharing the process that worked for me.
*These files are from:
*Android 11, Security Update 5AUG21 --> They probably won't work with any other version so I can't answer questions related to using them for that.
I don't recommend you try these on any other model unless you do it at you own risk.
*Strangely enough, this update doesn't have any of the Walmart apps installed or the bottom button on the taskbar. It asks if you want to install them when you are setting up the tablet*
I chose no.
Steps:
1. Enable USB Debugging, (while in Dev Options go to OEM Unlocking a tick that, (don't know if 100% necessary but I did it in my process)
and fire up a CMD or Powershell Window.
2. ADB:
adb devices (to make sure you are connected)
adb reboot bootloader
~boots to bootloader~
3. FASTBOOT
fastboot devices (to make sure you are connected)
(WARNING: the next command will factory reset the tablet)
fastboot flashing unlock
(follow volume key prompt to unlock and then device will reboot and bootloader is unlocked.)
You will see "orange state" as it boots if it worked properly. I don't have any interest in removing this message so you'll have to go elsewhere if you do.
4. Repeat steps 1-2 and get back into bootloader.
FASTBOOT:
fastboot devices
fastboot flash vbmeta <path to vbmeta.img>
fastboot flash boot <path to migisk patched.img>
fastboot reboot
5. Done
Notes:
I use Magisk Manager to do a direct install patch after I get root. (also don't know if 100% necessary, but it makes me feel better)
I'm including the stock boot.img in case you want to create your own patch with Magisk Manager. I used 24.1 (24100)
I'll answer what I can if you run into issues.
Cheers!

Reserved.

hey i was actually just about to go into the rabbit hole of pulling the boot.img, then i saw this. my tablet is stuck on the 5jan21 patch and wont update. could you tell me how you dumped the rom? also did you have to modify the vbmeta file? thanks

Mayday_Channel said:
hey i was actually just about to go into the rabbit hole of pulling the boot.img, then i saw this. my tablet is stuck on the 5jan21 patch and wont update. could you tell me how you dumped the rom? also did you have to modify the vbmeta file? thanks
Click to expand...
Click to collapse
i used sp flash and wwr. you can prob pull the boot.img pretty easily, but if you tried to take an OTA and it got corrupted, that might not work anyway. the vbmeta an empty one. this boot.img is from the most up to date ota which i got yesterday. i ordered a refurb version of this tablet and started messing with it yesterday. i have a copy of the full ROM dump as well. let me know if you need pieces and I can get them to you. you might be able to flash a few of the partitions and get it running again. can you get into fastboot?

which sp flash version? im on the latest 5.2152, every time i try to dump the full rom, it hangs on 0% readback. same with trying the boot.img. what was the full rom length, just to confirm? i got 0x750000000 from wwr

Mayday_Channel said:
which sp flash version? im on the latest 5.2152, every time i try to dump the full rom, it hangs on 0% readback. same with trying the boot.img. what was the full rom length, just to confirm? i got 0x750000000 from wwr
Click to expand...
Click to collapse
I used 5.1524. i had this issue as well and had to update the com port drivers. i used Iobit driver booster for this and it found the right driver. and yes thats the correct length for the one i dumped. i have the full thing on mega if you just want to flash it with sp flash tool.

that would be very nice. please post. thank you

Mayday_Channel said:
that would be very nice. please post. thank you
Click to expand...
Click to collapse
File folder on MEGA
mega.nz

goldensun1893 said:
File folder on MEGA
mega.nz
Click to expand...
Click to collapse
i got rid of userdata and cache to shrink it some.

thanks man

Mayday_Channel said:
thanks man
Click to expand...
Click to collapse
let me know how it works

could i please get the cache & userdata partitions? id like to keep a complete rom for archive. it seems to have flashed ok, but it broke wifi and its still stuck on january 5 patch. oh well, thats why i have 2 of these

ill drop them on there. be warned the userdata.img is something like 28GB. If you have the NV RAM Warning: ERR 0x10, there are a few tuts on here to fix that. Its common with SP Flash and MTK chips.

I think I figured out why it doesn't work. Spft isn't flashing super.img. even if I edit the scatter file to add super.img. I'll do some more trouble shooting at lunch

alright lets goooo. fixed it. just needed to change a few things in the scatter file and change the vbmeta files to img. next ill start experimenting on patching lk.bin to remove the ORANGE STATE text. thanks for the rom dump

NICE! I took a leap of faith and did this on my Oct 5th 2021 Security update build and it appears to have worked and Im rooted with magisk!!! I added a few additional steps to your commands just in case
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
fastboot erase cache
fastboot flash boot magisk_patched-24100_w97F6.img
fastboot reboot
I found a USB ADB fastboot driver that was signed and worked on my windows 10 x64 system but I had to go through the "Have Disk" manual driver install and installed even though it wasnt supposedly designed for my hardware. So insane the hoops to do this...
MT65XX-USB-VCOM-drivers\MT65XX USB VCOM drivers\Google_USB_Driver_rev4
Had trouble updating to Magisk to 24.3 however, not sure what pitfall I hit.
Wondering if I should be happy with root or try and flash TWRP and try a different ROM.

Iam in need of some help i am not sure if i have to install something to the tablet or pc but when i do the command "fastboot flashing devices" on my tablet just says on the bottom left =>FASTBOOT mode... and it doesnt change and on my pc it says <waiting for device> idk what am doing wrong can someone help me

beachmiles said:
NICE! I took a leap of faith and did this on my Oct 5th 2021 Security update build and it appears to have worked and Im rooted with magisk!!! I added a few additional steps to your commands just in case
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
fastboot erase cache
fastboot flash boot magisk_patched-24100_w97F6.img
fastboot reboot
I found a USB ADB fastboot driver that was signed and worked on my windows 10 x64 system but I had to go through the "Have Disk" manual driver install and installed even though it wasnt supposedly designed for my hardware. So insane the hoops to do this...
MT65XX-USB-VCOM-drivers\MT65XX USB VCOM drivers\Google_USB_Driver_rev4
Had trouble updating to Magisk to 24.3 however, not sure what pitfall I hit.
Wondering if I should be happy with root or try and flash TWRP and try a different ROM.
Click to expand...
Click to collapse
Followed the same steps and managed to get it working on my tablet that was on the same secpatch. However I also ran into an issue updating magisk. It acts like it worked fine and then when it reboots it asks to patch again.

Had to patch boot file manually and flash via fastboot. Still get an annoying popup when opening magisk but it's now updated to the latest 25.0.
To update run the following:
Root using ops method
Start your device and make sure that everything is rooted and working
adb reboot bootloader
fastboot flash boot [PATH TO MAGISK PATCHED 25000]
fastboot reboot
Tested on Oct521 SecPatch on a devices already rooted with OPs method. Do this at your own risk. Make backups, etc etc.​

hi nice work. sorry for my english. but i have a problem on mi onn tablet 1000035652 android 11. i try to root whit our method on fastboot no problem the tablet is unlock a message appears of the erase all data if unlock bootloader and press up volume then restart tablet so configure again and proced to fourt 4 point to flash vbdata and boot and in fastboot window okay flash then reboot and the tablet power on to the config screen then appear a message of controller apps stop then reboot and reboot infinite loop and i try to lock bootloader gain or reflash boot.img stock but no solution and i search for a alast update.zip or way to reinstal stock firmware can anyone help me ?

MSM and "the current image have been destroyed and can not boot"

Hey,
so yesterday I tried to install TWRP recovery.
While trying I assume that I hard bricked the phone and got the message that the current image has been destroyed and cant boot.
I've tried using MSM but the device wasnt recognized, I installed the qualcomm usb drivers and it worked for some time but still wasnt recognized in MSM.
Now I have the problem that when I plug it in, it only shows the above mentiond message. When I shut it off and press vol +/- it then goes into fastboot but cycles through it and is still only shown as android device in the device manager.
I'm using the usb 2.0 and original OP cable. Build number was IN2023...c.36, A12 and OOS12
ADB does not work, fastboot commands still work while it is in the fastboot cycle.
Does someone have any solutions for that?
Thanks

How did you "install" twrp?
via fastboot? or through booted twrp? Because from what i read, twrp or orangefox likes to patch boot image instead of flashing recovery partition.
So my suggestion is to flash via fastboot original boot.img and recovery.img

I watched a tutorial for that. I tried to get it running through fastboot but as I mentioned it didnt work out that well.
Do you know where I can get the original boot.img and recovery.img? I found other versions but not the one that I had

w4rdl0rd said:
I watched a tutorial for that. I tried to get it running through fastboot but as I mentioned it didnt work out that well.
Do you know where I can get the original boot.img and recovery.img? I found other versions but not the one that I had
Click to expand...
Click to collapse
You need to download EU OOS12 C36 FULL Package (i found it in this forum here), extract it via payload dumper and after that you will have every .img which is used to flash. Then you will need to go to folder where you have fastboot.exe, click shift+right mouse button and click open command prompt here.
Next: fastboot commands.
First (it's optional, but you will know that your device is "connected" via fastboot)
fastboot devices
you should have output, and if it's that then:
fastboot flash boot <drag boot.img file>
by dragging file, system automatically fill location of this boot file, next
fastboot flash recovery <drag recovery.img file>
and then
fastboot reboot
If you have questions, then ask

Thank you, it finally works

ShadoV90 said:
You need to download EU OOS12 C36 FULL Package (i found it in this forum here), extract it via payload dumper and after that you will have every .img which is used to flash. Then you will need to go to folder where you have fastboot.exe, click shift+right mouse button and click open command prompt here.
Next: fastboot commands.
First (it's optional, but you will know that your device is "connected" via fastboot)
fastboot devices
you should have output, and if it's that then:
fastboot flash boot <drag boot.img file>
by dragging file, system automatically fill location of this boot file, next
fastboot flash recovery <drag recovery.img file>
and then
fastboot reboot
If you have questions, then ask
Click to expand...
Click to collapse
I'm now somehow stuck in recovery. So after I select the language I get the message "system error, after select language, please select Online update". When I try to format data I'm getting back to recovery. Maybe you can tell me how to proceed since I don't really know what to search for

w4rdl0rd said:
I'm now somehow stuck in recovery. So after I select the language I get the message "system error, after select language, please select Online update". When I try to format data I'm getting back to recovery. Maybe you can tell me how to proceed since I don't really know what to search for
Click to expand...
Click to collapse
Wait... system can't boot up?

ShadoV90 said:
Wait... system can't boot up?
Click to expand...
Click to collapse
yeah, it goes always back to recovery

Hmm... Then i'm afraid that MSM is now your only option. Sincerely, i never used that, so i found thread with guide how to do it.
Look please here, read carefully, and i hope you will be able to recovery your device.
I guess it will rollback your system to OOS11.
PS. Give feedback if it was succesfull (or not).

Right now I tried to do again the steps you mentioned. When I dragged the boot file into command prompt I got the message that the .img file is damaged. Maybe that is the reason for not booting up. When I first did it I also received the message but after dragging it a second time over it was still installed.
I also tried downloading the firmware from the op website, extracting everything via the payload dumper and installing everything as you mentioned. Like that I was stuck in fastboot.
Thanks for your help, maybe it will work

w4rdl0rd said:
Right now I tried to do again the steps you mentioned. When I dragged the boot file into command prompt I got the message that the .img file is damaged. Maybe that is the reason for not booting up. When I first did it I also received the message but after dragging it a second time over it was still installed.
I also tried downloading the firmware from the op website, extracting everything via the payload dumper and installing everything as you mentioned. Like that I was stuck in fastboot.
Thanks for your help, maybe it will work
Click to expand...
Click to collapse
I hope it will work.
BTW, next time when you will try recovery like twrp or orangefox, don't flash it but boot it via fastboot.
fastboot boot <drag file of twrp/orangefox>
If it will work, and everything will work, then use fastboot flash recovery <drag file of twrp/orangefox>
Don't flash it via twrp/orangefox, because like i said, it will probably try to patch boot partition and in result boot will be unusable.

thanks for the advice, I'll try it next time or when I get it running again

w4rdl0rd said:
thanks for the advice, I'll try it next time or when I get it running again
Click to expand...
Click to collapse
I have one more idea. I thought about changing active slots in fastboot. Normally on inactive slot is fully working rom before update to c36. With proper boot etc. So when you change active slot, you should have fully working ROM. Problem is that you must figure out which slot is your active now.
Normally this command is fastboot getvar all and it should show you wall of text and information (bootloader) current_slot: a (or b)
then you can switch active slots (if you see other slot is bootable).
There are two methods:
1. Checking active slots and if current active slot is A then in fastboot type this
fastboot set_active b otherwise fastboot set_active a
2. Idk if it will work here, but there is a command fastboot set_active other which just switch active slot no matter what it was earlier.
But sincerely idk what will happen if you will switch to unpopulated slot. I think if you upgrade your phone normally or didn't erase this inactive slot, it should be populated with previous version of ROM.
When i installed OOS12 and due to destroying my boot image i switched slots i was able to run A11 xD

ShadoV90 said:
I have one more idea. I thought about changing active slots in fastboot. Normally on inactive slot is fully working rom before update to c36. With proper boot etc. So when you change active slot, you should have fully working ROM. Problem is that you must figure out which slot is your active now.
Normally this command is fastboot getvar all and it should show you wall of text and information (bootloader) current_slot: a (or b)
then you can switch active slots (if you see other slot is bootable).
There are two methods:
1. Checking active slots and if current active slot is A then in fastboot type this
fastboot set_active b otherwise fastboot set_active a
2. Idk if it will work here, but there is a command fastboot set_active other which just switch active slot no matter what it was earlier.
But sincerely idk what will happen if you will switch to unpopulated slot. I think if you upgrade your phone normally or didn't erase this inactive slot, it should be populated with previous version of ROM.
When i installed OOS12 and due to destroying my boot image i switched slots i was able to run A11 xD
Click to expand...
Click to collapse
I tried/am trying to get MSM working. It connected now in edl, in MSM it still freezes. No matter what I do it has the status "waiting for communication".
If I remember correctly then there was somethin with ..._b. But since I've closed the command prompt I can't look it up anymore.
I'll try to change slots and let you know if there will be a result.

With MSM there is one problem. After succesful operation your phone will be locked. I mean bootloader will be locked.

I did as you wrote...it works fine now. I think. There is still A12 and OOS12 installed but it is lagging a bit.
I attached a screenshot of the terminal with the slots. Does having switched them pose some problem? Do I have to switch them back?

Just check if you have an update. If you have, then install it via system update. For now, you have working system. Now you have much more possibilities to use. Like if you don't have update you can apply manually one which you downloaded. In system ofc.

There are no updates, there is the most recent version installed.
Thank you for the help in solving it

w4rdl0rd said:
There are no updates, there is the most recent version installed.
Thank you for the help in solving it
Click to expand...
Click to collapse
So, this is C36 installed?

yeah there is c36 installed