Database Develop

[GUIDE]Factory Images (JB) [grouper][tilapia]

Hello everyone,
i decide to write this guide and to collect all the future Factory Images for Nexus7 (grouper WiFi, tilapia GSM/HSPA+).
Once installed them you retourn 100% stock.
This is usefull in case you don't want to wait official OTA or you have to use warranty for some problem or you like a really clean install.
Since Android 4.0 IceCreamSandwich you can't install OTA via update.zip method in stock recovery because is no more possible. If you try via stock recovery you get "error status 7" (this problem is corrected only if you use ClockWorkMod Recovery).
Then is necessary to use Factory Image provided by Google.
Factory Images:​
JDQ39 Android 4.2.2 Factory Image "nakasi" for Nexus7 (grouper WiFi)
MD5 Checksum b869c77ba7e2929b3ca00804bf64b945
JZO54K Android 4.1.2 Factory Image "nakasi" for Nexus7 (grouper WiFi)
MD5 Checksum d906b505ccae0d439839d3c5fafb137a
JDQ39 Android 4.2.2 Factory Image "nakasig" for Nexus7 (tilapia GSM/HSPA+)
MD5 Checksum ee8db1ed6ff1c007fe12136d4bc65cd8
NOTICE: If you have any GSM/HSPA+ Nexus7 you can only flash "nakasig" factory images. If you have a WiFi Nexus7 size doesn't matter (8,16,32gb)​
How to install:​
Requirements:
-Android SDK
-Java JDK
-Platform-Tools
-Unlocked bootloader ("fastboot oem unlock" pay attention, wipes everything, also your data)
-experience with adb and fastboot​
NOTICE: If you never used the sdk, the jdk, fastboot and adb, before installing the factory image YOU HAVE TO FOLLOW some guide here on XDA in order to get sdk and unlocked bootloader.
Now you can proceed to install the Factory Image
On Windows:​
1) copy the ecxtracted files (two times with 7zip) on android-sdk/platform-tools/ (this is important, if you dont unzip it, dont complain about "radio couldnt be loaded")
2) run a cmd and moves in "platform-tools" folder
3) write those command:
4A) If you are coming from a custom rom, this wipe your data/cache:
adb reboot bootloader
fastboot flash bootloader bootloader-grouper or tilapia-********.img
[fastboot reboot-bootloaderTo do only on Nexus7 GSM/HSPA+
fastboot flash radio radio-tilapia-********.img]To do only on Nexus7 GSM/HSPA+
fastboot reboot-bootloader
fastboot -w update image-********.zip
if you want relock the bootloader (not necessary, only for warranty) do also these two step:
fastboot reboot-bootloader
fastboot oem lock
4B) If you are coming from another stock rom (official older OTA unrooted), this doen't wipe your data/cache:
adb reboot bootloader
fastboot flash bootloader bootloader-grouper or tilapia-********.img
[fastboot reboot-bootloaderTo do only on Nexus7 GSM/HSPA+
fastboot flash radio radio-tilapia-********.img]To do only on Nexus7 GSM/HSPA+
fastboot reboot-bootloader
fastboot update image-********.zip
if you want relock the bootloader (not necessary, only for warranty) do also these two step:
fastboot reboot-bootloader
fastboot oem lock
On Linux, Mac:​
1) copy the ecxtracted files (two times with 7zip) on android-sdk/platform-tools/ (this is important, if you dont unzip it, dont complain about "radio couldnt be loaded")
2) run a terminal and moves in "platform-tools" folder
3) write those command:
chmod +x flash-all.sh
./flash-all.sh
"flash-all.sh" wipes your data (it contains fastboot -w update, if you want to remove/change it edit with notepad++)
"flash-base.sh" flashes only the bootloader and the radio.
NOTICE:
1) Instead of ******** you have to put the name of the files you download.
2) somebody is aking why "adb reboot bootloader" each passages. Is not essential, but some people think it is better because you use the updated bootloader, maybe is only a superstition.​
PLEASE LEAVE ME A THANKS ​
WARNING! DON'T DO THESE THING IF YOU DON'T KNOW WHAT YOU ARE DOING. I'M NOT RESPONSIBLE OF BRICKED NEXUS7 OR SIMILAR​

Updated!

Is it possible to do it without wiping? I tried flashing system, boot, and recovery but the device just bootloops

Worked great, thanks for the info

Thanks a lot buddy! After hours of reading, I found your solution and it worked like a breeze! Really appreciate it :good:

[GUIDE] Update to Lollipop without losing apps/settings

It is assumed that you are on Kitkat with unlocked bootloader and rooted. Here is what I did (this is on Linux, but for Windows the instructions remain the same):
0. Backup first.
a. Use TWRP to do a full back up of your current ROM. Use 2.8.2.0 from Luca here: http://forum.xda-developers.com/mot...recovery-twrp-2-8-2-0-touch-recovery-t2979149
b. Use titanium backup to back up all your apps and their data.
Just as a precaution. This guide will keep your data and apps intact...
1. Get the Lollipop OTA
a. After the OTA download was complete, I kept on postponing the install. The downloaded ZIP was in /cache folder, which I could read when rooted. So, the first step was to adb pull it onto my PC to save it for eternity.
OR
b. If you don't have the OTA in your cache folder, download it from forums here. Left as an exercise for the reader....
2. Go back to stock Kitkat as much as you can without destroying the data partition and losing apps and settings.
a. Get your current stock ROM and unzip it in a folder
b. adb reboot bootloader, and change directory to the folder where you unzipped the stock files.
c. restore to stock without losing the /data
fastboot flash partition gpt.bin
fastboot flash motoboot motoboot.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 modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
3. Sideload the OTA ZIP.
a. adb reboot recovery - this will put you into stock recovery. Press Vol UP while Power is pressed. It will be give you a menu. Vol Down to "Install from ADB" and Power (or Vol Up, don't remember, I think this changed with Lollipop) to select.
b. Once the phone is in sideload mode ("Install from ADB" mode), do 'adb sideload <ZIP NAME>'
c. Wait....wait some more. It will take quite a bit.
4. Boot back. It should start upgrading your apps you had before the upgrade with "Android upgrading..." dialog.
5. Go on and try other OTA updates (which don't work right now). Or load your favorite root method and/or TWRP, and create another backup point for your Lollipop install with all your apps and settings.
For me, I am at 22.11.6 (5.0.0 with 2 OTAs missing), rooted and TWRP. Once new OTAs arrive, I will do the same thing again...

Wow, great !
It worked like a charm for me, I even stopped before 3) to reboot and do the ota automatically, succesfully and I didn't lose any data.
Fyi I hat a rooted/xposed xt1032 running 4.4.4 and I installed the 5.0.1 OTA this way (210.12.40 to 220.27.1).
Thanks a lot !

flash which ROM ?

Hello, my watch R has 5.1.1 (LDZ22D) stock ROM and it has some problems. I tried factory reset, still not ok. I would like to try flashing again the stock ROM. I have found this thread: http://forum.xda-developers.com/g-watch-r/development/stock-boot-recovery-g-watch-r-t2956964 , i downloaded boot.img, recovery.img and system.img, checked SHA1 but i don't know which version should i try? 5.1.1 (LDZ22D), 5.1.1 (LCA44B), 5.0.2: ??? Are there limitations for downgrade / upgrade ?
And as a guide to flashing...
1. i start watch, swype 11 to 5, so now in fastboot mode i connect to PC, the PC detect the watch as what ?
2. adb devices and if watch is detected i continue.
3. fastboot flash boot boot.img
4. fastboot flash recovery recovery.img
5. fastboot flash system system.img
6. restart
is that ok ?
How long does it take to flash each of those imgs ?
thank you

intersectRaven said:
Notes/FAQ:
1.) I re-mkbootimg-ed them since I'll be uploading 2 x 20+MB files if I didn't. Still has the same SHA1 checksums as the ones being checked by stock ROM so it's safe to flash.
2.) If you're confused on how to download click on the box marked in this pic.
3.) The commands for flashing are as follows:
Boot: fastboot flash boot boot.img
Recovery: fastboot flash recovery recovery.img
System: fastboot flash system system.img
*replace boot.img, recovery.img and system.img with their respective filenames
**how to obtain the fastboot executables and drivers are explained in a separate thread
4.) The system.img provided above are stock and NOT ROOTED. If you want to go completely stock, just flash ALL the 5.0.1 images above.
*only for 5.0.1 since I didn't make a system image for 4.4W.2 or below
Click to expand...
Click to collapse
took that from the link you posted, just conect the watch to the dock while in fastboot mode, search for 15 second adb/fastboot installer, after installing that and the computer detects your watch just follow those steps using cmd and navigating to the directory where the files are at first, remember to install fastboot and adb system wide on the 15 second adb installer

when in fastboot mode the watch is not detected:
C:\Users\user>adb devices
List of devices attached
when i chose "recovery" in fastboot mode (android robot on back with door open and red exclamation mark) i get:
C:\Users\user>adb devices
List of devices attached
410KCHserialnr888 sideload
but the watch says he waits "adb sideload <filename>"
what i am doing wrong ? something else had to be done ?
thank you

you can use adb to boot watch on bootloader, but it is not needed since you can boot into fastboot already, problem is the watch is not detected on fastboot mode, try finding some drivers or something, what i usually do is download cydia impactor and select usb then let it do the driver stuff for me, quote me next time so i can get notified when you respond

TWRP 3.0.2 for Acer Predator 8 ported by Ruben.

IMPORTANT NOTE ABOUT ROOTING:
After flashing TWRP 3.0.2, use the SuperSU 2.46 flashable zip, do NOT use latest version or will result in a bootloop. Good Luck and have fun with rooting.
REQUIREMENTS
1- Unlocked Bootloader (search on google if you dont know how to unlock)
2- Drivers and Adb/Fastboot commands knowledge
--------------------------------------------------------------------------------------------------------------------------------
New TWRP bugfix update! Now you can flash stock rom on TWRP without bricking! Download Page updated!
Bugs:
1- adb shell command needs to be sent before system partition is mounted or it will give an error, after doing adb shell you can mount system and do all the modifications you need.
2- You cant flash any img on twrp it gives an error, im trying to fix.
3- Backups do work, but everytime twrp restarts, the serial number folder seems to change (which means that on /TWRP/BACKUPS/serialnumber/backupsinside/ changes every reboot so you have to go get the backup inside the old serialnumber folder and put on the new serialnumber folder).
Im leaving an unsecured boot image because system does not boot android if anything seems changed. So please if system does not boot after flashing twrp/rooting, flash the unsecured boot img on fastboot
Steps to Install TWRP and root
1. Download and extrct the files: https : // drive. google . com/file/d/0BxzG5iupOOSKNTdlRC1Wd0VmTlk/view
2. Power off the tablet.
3. Enter fastboot mode by pressing the power button while holding down Vol -
4. Open up command prompt and navigate to the directory where fastboot.exe is located.
5. Pass the following commands:
fastboot flash boot unsecuredboot.img
fastboot flash recovery TWRP.img
6. Reboot into recovery (TWRP) and install SuperSU v2.46.zip ---
Continuation 6. Step by Step of Step 6 since people seem to have been running into issues with it:
After rebooting to TWRP and having SuperSU.zip in the tablet storage. Go on Install tab and press the supersu file and install/flash it then reboot the device.

[SOLVED] Flash image as "System"

I'm trying to flash an image as system
But OrangeFox, PBRB and TWRP don't let me (it doesn't even show me the option)
Is there any other way to do that?

Hi @ax0 what do you mean? Flashing from recovery gives the zip access to all system files...

traman124 said:
Hi @ax0 what do you mean? Flashing from recovery gives the zip access to all system files...
Click to expand...
Click to collapse
Yeah but I wanna flash a GSI (.img) and when I select the IMG , on the flash menu there isnt no "System"
Should I try to rename the image to "system.img" and then zip it and perhaps flash that?

is there an "install image" at the bottom of the screen in the zip select screen? Are you on the latest TWRP?

Ig he is saying that there is no system partition to flash the GSI image to.
Redmi 9C device has system-as-root partition, meaning that it has Super partition (which is IIRC a combination of system, product and vendor) rather than System partition

noob_developerdfd said:
Redmi 9C device has system-as-root partition, meaning that it has Super partition (which is IIRC a combination of system, product and vendor) rather than System partition
Click to expand...
Click to collapse
All devices shipped with Android 9 must have a system-as-root (SAR) layout. But it's not the same as a super partition.
The SAR configuration merged the root file system into system.img and then mount system.img as the root file system (rootfs).
This was published in connection with "Project Treble" to optimize the update process for vendor related files. Those files are no longer part of /system and now stored on /vendor.
Super: Here the partitions /system, /vendor and /product are dynamic logical partitions within /super (block device) and are managed in userspace. Fastboot access is also handled in userspace (recovery) by the fastbootd mode (fastboot reboot fastboot).

ax0 said:
I'm trying to flash an image as system
But OrangeFox, PBRB and TWRP don't let me (it doesn't even show me the option)
Is there any other way to do that?
Click to expand...
Click to collapse
As mentioned before that's related to /super. Use
Code:
fastboot reboot fastboot
when in fastboot mode to switch into fastbootd mode.
Then you should be able to run
Code:
fastboot flash system <PATH TO IMAGE>
To switch back into bootloader mode use
Code:
fastboot reboot bootloader
Take care using a newer version of the Platform Tools for full support of fastbootd mode.

WoKoschekk said:
As mentioned before that's related to /super. Use
Code:
fastboot reboot fastboot
when in fastboot mode to switch into fastbootd mode.
Then you should be able to run
Code:
fastboot flash system <PATH TO IMAGE>
To switch back into bootloader mode use
Code:
fastboot reboot bootloader
Take care using a newer version of the Platform Tools for full support of fastbootd mode.
Click to expand...
Click to collapse
For some reason when I run fastboot reboot (partition) it always just shows me the usage menu!
No matter what the partition is!

can you try getting fastboot through nexustools? I've had tons of problems with 15-second ADB in the past

traman124 said:
can you try getting fastboot through nexustools? I've had tons of problems with 15-second ADB in the past
Click to expand...
Click to collapse
What is NexusTools?
oh nvm https://github.com/corbindavenport/nexus-tools

that... actually worked!
i can reboot to fastbootd!
and WoKoschekk's guide worked!
thanks yall!