Develop Bugs

Convert to yakju questions

I have 2 questions now,
I saw this guide: http://forum.xda-developers.com/showthread.php?t=1626895
But I did understand it but isn't a guide with a Galaxy Nexus Root Toolkit? I saw that in this guide: http://webtrickz.com/guide-to-updat...oid-4-0-4-and-get-future-updates-from-google/
It looks like the same, only is this with a gui, so I won't type things wrong, would this be wrong to use?
And...
If I change to yakju and lock the bootloader ( I just want to have everything stock again after that ), can you see then anywhere if you changed to yakju? So if I send it in for warrenty they won't know it?

Marc. said:
I have 2 questions now,
I saw this guide: http://forum.xda-developers.com/showthread.php?t=1626895
But I did understand it but isn't a guide with a Galaxy Nexus Root Toolkit? I saw that in this guide: http://webtrickz.com/guide-to-updat...oid-4-0-4-and-get-future-updates-from-google/
It looks like the same, only is this with a gui, so I won't type things wrong, would this be wrong to use?
And...
If I change to yakju and lock the bootloader ( I just want to have everything stock again after that ), can you see then anywhere if you changed to yakju? So if I send it in for warrenty they won't know it?
Click to expand...
Click to collapse
1) use the first link you posted. dont use the toolkit. http://forum.xda-developers.com/showthread.php?t=1626895
2) no, they wont be able to really tell anything.

Zepius said:
1) use the first link you posted. dont use the toolkit. http://forum.xda-developers.com/showthread.php?t=1626895
2) no, they wont be able to really tell anything.
Click to expand...
Click to collapse
Why not use the toolkit? It looks much easier.
And do I have to do all the optional things also?
Then it would be this?
1) Make sure your computer recognizes your device by typing: fastboot devices
2) Unlock your bootloader (if you have not already done so): fastboot oem unlock
3) You will see a prompt on your device. This will wipe your entire device (including the /sdcard folder). Accept.
4) Reboot by typing: fastboot reboot-bootloader
9) Flash the system partition: fastboot flash system system.img
10) Flash the data partition: fastboot flash userdata userdata.img Note: this command will wipe your device (including /sdcard), EVEN if your bootloader is already unlocked.
11) Flash the boot partition: fastboot flash boot boot.img
12) Optional (but recommended) -- Flash the recovery partition: fastboot flash recovery recovery.img
13) Erase the cache partition: fastboot erase cache
15) Reboot: fastboot reboot
16) Done! The first boot will likely take quite a bit longer than you are used to, as Android builds the Dalvik cache.

Marc. said:
Why not use the toolkit? It looks much easier.
And do I have to do all the optional things also?
Then it would be this?
1) Make sure your computer recognizes your device by typing: fastboot devices
2) Unlock your bootloader (if you have not already done so): fastboot oem unlock
3) You will see a prompt on your device. This will wipe your entire device (including the /sdcard folder). Accept.
4) Reboot by typing: fastboot reboot-bootloader
9) Flash the system partition: fastboot flash system system.img
10) Flash the data partition: fastboot flash userdata userdata.img Note: this command will wipe your device (including /sdcard), EVEN if your bootloader is already unlocked.
11) Flash the boot partition: fastboot flash boot boot.img
12) Optional (but recommended) -- Flash the recovery partition: fastboot flash recovery recovery.img
13) Erase the cache partition: fastboot erase cache
15) Reboot: fastboot reboot
16) Done! The first boot will likely take quite a bit longer than you are used to, as Android builds the Dalvik cache.
Click to expand...
Click to collapse
if something happens in the middle of you doing it the way in the link i mentioned, its easier to figure out how to fix items when you're on a certain step.
the toolkit is easier, but if something messes up, its hard to tell where since you have no idea what it is doing
the only other step is once everything is booted back up on yakju and is working properly, go back to fastboot and relock the bootloader with fastboot oem lock

So you say these steps will be right?
1) Make sure your computer recognizes your device by typing: fastboot devices
2) Unlock your bootloader (if you have not already done so): fastboot oem unlock
3) You will see a prompt on your device. This will wipe your entire device (including the /sdcard folder). Accept.
4) Reboot by typing: fastboot reboot-bootloader
5) Flash the system partition: fastboot flash system system.img
6) Flash the data partition: fastboot flash userdata userdata.img Note: this command will wipe your device (including /sdcard), EVEN if your bootloader is already unlocked.
7) Flash the boot partition: fastboot flash boot boot.img
8) Optional (but recommended) -- Flash the recovery partition: fastboot flash recovery recovery.img
9) Erase the cache partition: fastboot erase cache
10) Reboot: fastboot reboot
11) Done! The first boot will likely take quite a bit longer than you are used to, as Android builds the Dalvik cache.
12) Lock bootloader again with: fastboot oem lock
And how could I see when its finished flashing for example system.img?
And this would work on doesn't matter what firmware you're on?

Marc. said:
I have 2 questions now,
I saw this guide: http://forum.xda-developers.com/showthread.php?t=1626895
But I did understand it but isn't a guide with a Galaxy Nexus Root Toolkit? I saw that in this guide: http://webtrickz.com/guide-to-updat...oid-4-0-4-and-get-future-updates-from-google/
It looks like the same, only is this with a gui, so I won't type things wrong, would this be wrong to use?
And...
If I change to yakju and lock the bootloader ( I just want to have everything stock again after that ), can you see then anywhere if you changed to yakju? So if I send it in for warrenty they won't know it?
Click to expand...
Click to collapse
Yes, if they check build.prop (unlikely that they will if you relock bootloader), they will be able to see the yakju fingerprint.
Marc. said:
So you say these steps will be right?
1) Make sure your computer recognizes your device by typing: fastboot devices
2) Unlock your bootloader (if you have not already done so): fastboot oem unlock
3) You will see a prompt on your device. This will wipe your entire device (including the /sdcard folder). Accept.
4) Reboot by typing: fastboot reboot-bootloader
5) Flash the system partition: fastboot flash system system.img
6) Flash the data partition: fastboot flash userdata userdata.img Note: this command will wipe your device (including /sdcard), EVEN if your bootloader is already unlocked.
7) Flash the boot partition: fastboot flash boot boot.img
8) Optional (but recommended) -- Flash the recovery partition: fastboot flash recovery recovery.img
9) Erase the cache partition: fastboot erase cache
10) Reboot: fastboot reboot
11) Done! The first boot will likely take quite a bit longer than you are used to, as Android builds the Dalvik cache.
12) Lock bootloader again with: fastboot oem lock
And how could I see when its finished flashing for example system.img?
And this would work on doesn't matter what firmware you're on?
Click to expand...
Click to collapse
Why don't you download yakju factory image from Google? It has a bash script that can flash everything for you, in the right order. If you edit flash-all.sh, you'll see the fastboot commands it runs. That's the order you need to run them.
Sent from my i9250

[Q] killed my one x need help tried loads of stuff

as title says ive tried loads of stuff and seem to have hit a brick wall.
tried to root phone and thats when it went wrong
system info is
3.14.206.27 version
s on
boot is hboot 1.36.0000
boot loader unlocked
tried recovery from and it comes up with errors it wont flash files over can mount sd card and stuff like that
last night when i was tired i had formated all the storage in the phone got clockworkmod recovery 5.8.3.1 on it
wont recover the O2_001 3.14 Stock JB comes up with errors tried through adb and get an error about a buffer stack.
im running windows 7 any help would be great or if some one near nottinginham i can take the phone too and ither buy drinks or cash to sort it

First flash cwm 5.8.4.0
http://db.tt/Krlm4dPs
Put the file in the fastboot folder and rename it to recovery.img
Put the phone in the bootloader and open a command prompt inside the fastboot folder. Point in the folder, hold shift and right click the mouse - select open command window here
Then type
Fastboot erase cache
Fastboot flash recovery recovery.img
Fastboot erase cache
Then download a rom of your choice, open the rom.zip and copy the boot.img file to the fastboot folder.
Flash that too
Fastboot flash boot boot.img
Fastboot erase cache
Then enter the recovery and mount the sdcard as a mass storage device and copy the rom.zip to it.
Then make a full wipe....
factory reset
Wipe cache partition
Advanced - wipe dalvik cache
Mounts and storage - format cache,data,system
Then install the rom.zip

Mr Hofs said:
First flash cwm 5.8.4.0
Put the file in the fastboot folder and rename it to recovery.img
Put the phone in the bootloader and open a command prompt inside the fastboot folder. Point in the folder, hold shift and right click the mouse - select open command window here
Then type
Fastboot erase cache
Fastboot flash recovery recovery.img
Fastboot erase cache
Then download a rom of your choice, open the rom.zip and copy the boot.img file to the fastboot folder.
Flash that too
Fastboot flash boot boot.img
Fastboot erase cache
Then enter the recovery and mount the sdcard as a mass storage device and copy the rom.zip to it.
Then make a full wipe....
factory reset
Wipe cache partition
Advanced - wipe dalvik cache
Mounts and storage - format cache,data,system
Then install the rom.zip
Click to expand...
Click to collapse
thank you so much i got viper on the phone then copyd the o2 nandroid backup to the phone and it recoverd ok

Good !
CASE CLOSED !

(V-510 GPE) - Return to Stock using Fastboot

Hi, I would like to get a verification that the following procedure would work on the GPAD GPE V-510 to return back to Stock if ever needed. I am used to Nexus devices and using Factory images with Fastboot when needed and would like to have the same ability on the GPAD.
1st step was I made a TWRP backup when the device was pretty much stock (no root, standard recovery and kernel) and copied the files back to my PC.
Since then I have flashed custom recovery (TWRP) and Kernel (SleekAI)
Now if I enter Bootloader / Fastboot mode (Vol-Down + Power), would it be possible commands to return back to this state if for some reason TWRP recovery was no longer available and I wanted to restore back this image:
Check Tablet is visible in Fastboot mode:
fastboot devices
Restore Backups using Fastboot:
fastboot flash recovery recovery.emmc.win
fastboot flash boot boot.emmc.win
fastboot flash system system.ext4.win
fastboot flash userdata data.ext4.win
fastboot erase cache
fastboot reboot
Also do we need to restore / flash userdata or could we just issue the following command to format (erase) the data and it would return to its original state?
fastboot format userdata
If someone can confirm that this would work it would be appreciated, also do you think the backup images from 1 device could be used on other v-510 devices? If so I could post them and this procedure for anyone else needed to use this to return to Stock.
Thank you for your help,
Shaun

Phone Decryption - Need Help

After installing of Paranoid /AOSPA 6.0.2 ROM I got message saying "To start Android, Enter your password" that mean my phone has been encrypted by itself, I did factory reset and still getting the same, Can you please help me !?

gotta flash a non-encrypting boot.img usually coming in the form of SuperSU systemless or custom kernel or there's some other OP3 specific solutions floating around here somewhere.
After that format /data in twrp. (format, not wipe.)

Boot in fastboot mode and use the command "fastboot format userdata". This will decrypt the device but also erase all data except system partition.

1.Properly Install ADB & Fastboot drivers for One Plus 3
2.Download Minimal ADB & fastboot http://forum.xda-developers.com/showthread.php?t=2317790
3.Boot into FASTBOOT mode [Power + Volume UP]
4.Connect Device via USB
5.Open CMD promt On Minimal ADB & FASTBOOT folder (Installed Folder)
6.Check Connection
Code:
fastboot devices
(If Returning response, Then Device is Connected)
7.Run The Following Command.
Code:
fastboot format userdata
6.Reboot device
Code:
fastboot reboot
NOTE: This will Erase all User data (Installed apps, games etc.)
NOTE: Check Encryption status in Settings > Security > Encrypt Phone [If Showing "Encrypt Phone" button at bottom, Then device is decrypted successfully]

Unable to boot into ROM after flashing

Hey guys! Need some help.
I've been trying to flash a Android Pie ROM on my device and I have no success.
The problem is, after flashing the rom and TWRP Zip the device reboots twice then boots back into TWRP.
Then all the files on the device has random letters and numbers (i.e. ckjrdh574o0hmdu749y7nv)
Why can't I flash a Android Pie rom successfully?
I am on the latest Android Pie update. (Flashed on both slots)
Here is my steps:
Flash stock rom on both slots
Boot up in stock rom. (no set up, no password, no pin, nothing totally skipped setup)
Place files on device (Rom and twrp.zip)
Reboot into Bootloader
Boot into latest TWRP using fastboot
Once in Twrp, slide slider to allow modification to system parition
Factory reset/wipe data (and all that)
Flash rom (I tried Carbon Rom 7 and lineage os 16)
Flashed twrp zip
reboot
After the system reboots twice I am back in twrp and all the files and folder have numbers and letters as files names.
Any idea as to why this keeps happening?
How can I fix this?

MichaelDrakeMS said:
Hey guys! Need some help.
I've been trying to flash a Android Pie ROM on my device and I have no success.
The problem is, after flashing the rom and TWRP Zip the device reboots twice then boots back into TWRP.
Then all the files on the device has random letters and numbers (i.e. ckjrdh574o0hmdu749y7nv)
Why can't I flash a Android Pie rom successfully?
I am on the latest Android Pie update. (Flashed on both slots)
Here is my steps:
Flash stock rom on both slots
Boot up in stock rom. (no set up, no password, no pin, nothing totally skipped setup)
Place files on device (Rom and twrp.zip)
Reboot into Bootloader
Boot into latest TWRP using fastboot
Once in Twrp, slide slider to allow modification to system parition
Factory reset/wipe data (and all that)
Flash rom (I tried Carbon Rom 7 and lineage os 16)
Flashed twrp zip
reboot
After the system reboots twice I am back in twrp and all the files and folder have numbers and letters as files names.
Any idea as to why this keeps happening?
How can I fix this?
Click to expand...
Click to collapse
Flash stock
finish setup
before doing anything else

MichaelDrakeMS said:
Hey guys! Need some help.
I've been trying to flash a Android Pie ROM on my device and I have no success.
The problem is, after flashing the rom and TWRP Zip the device reboots twice then boots back into TWRP.
Then all the files on the device has random letters and numbers (i.e. ckjrdh574o0hmdu749y7nv)
Why can't I flash a Android Pie rom successfully?
I am on the latest Android Pie update. (Flashed on both slots)
Here is my steps:
Flash stock rom on both slots
Boot up in stock rom. (no set up, no password, no pin, nothing totally skipped setup)
Place files on device (Rom and twrp.zip)
Reboot into Bootloader
Boot into latest TWRP using fastboot
Once in Twrp, slide slider to allow modification to system parition
Factory reset/wipe data (and all that)
Flash rom (I tried Carbon Rom 7 and lineage os 16)
Flashed twrp zip
reboot
After the system reboots twice I am back in twrp and all the files and folder have numbers and letters as files names.
Any idea as to why this keeps happening?
How can I fix this?
Click to expand...
Click to collapse
Not sure if Carbon / Lineage has special install instructions or not, but you can follow the initial 9x setup in the link in my sig, then follow cust Rom installation process.

parakleet said:
Flash stock
finish setup
before doing anything else
Click to expand...
Click to collapse
Yup I did. I just didn't sign in my account or do the security pin/pixel imprint. I skipped everything untill I was at the home/launcher.

Az Biker said:
Not sure if Carbon / Lineage has special install instructions or not, but you can follow the initial 9x setup in the link in my sig, then follow cust Rom installation process.
Click to expand...
Click to collapse
Nothing to special from the norm. I didn't everything the forums told me to do.
Okay definitely, I'll check that out and try those steps.
Also do you think I have a phone that twrp can't decrypt? I remember a while back doing one of the twrp updates that some phones won't decrypt because it used the older encryption method or something like that and TWRP was only able to decrypt then phones using the new method or something like that.

Oh and another question, do you guys think I should root the stock image with magisk then boot into twrp using fastboot and install the room then the twrp.zip?

My question would be do you have other details you might have overlooked? For example, at the end of flashing, TWRP would usually ask whether you want to install their app. Did you install it or did you skip it?
Also, what was your exact procedure in flashing stock rom to both slots? I have also messed around with custom roms and reverted back to stock using the following:
Return to Stock:
Source of this knowledge is Method 2 of this video.
#flashing bootloader to slot A and slot B
Code:
fastboot reboot-bootloader
fastboot flash bootloader_a bootloader[...].img
fastboot reboot-bootloader
fastboot flash bootloader_b bootloader[...].img
#flashing radio to slot A and slot B
Code:
fastboot reboot-bootloader
fastboot flash radio_a radio[...].img
fastboot reboot-bootloader
fastboot flash radio_b radio[...].img
#set active slot to B, flash system image
Code:
fastboot --set-active=b
fastboot reboot-bootloader
fastboot --skip-reboot --skip-secondary update image[...].zip
#set active slot to A, flash system image [different command!!!]
Code:
fastboot --set-active=a
fastboot reboot-bootloader
fastboot --skip-reboot update image[...].zip
Now straight from the bootloader, boot into recovery.
Wipe data/factory reset.
Let it reboot back into android.
Then, I followed the install instructions in the twrp thread to get custom recovery back onto my device. (If you want rooted stock android, flash it from twrp and then install the latest magisk manager apk.)
Now just find another custom rom and follow the install directions from that thread.

amartolos said:
My question would be do you have other details you might have overlooked? For example, at the end of flashing, TWRP would usually ask whether you want to install their app. Did you install it or did you skip it?
Also, what was your exact procedure in flashing stock rom to both slots? I have also messed around with custom roms and reverted back to stock using the following:
Return to Stock:
Source of this knowledge is Method 2 of this video.
#flashing bootloader to slot A and slot B
Code:
fastboot reboot-bootloader
fastboot flash bootloader_a bootloader[...].img
fastboot reboot-bootloader
fastboot flash bootloader_b bootloader[...].img
#flashing radio to slot A and slot B
Code:
fastboot reboot-bootloader
fastboot flash radio_a radio[...].img
fastboot reboot-bootloader
fastboot flash radio_b radio[...].img
#set active slot to B, flash system image
Code:
fastboot --set-active=b
fastboot reboot-bootloader
fastboot --skip-reboot --skip-secondary update image[...].zip
#set active slot to A, flash system image [different command!!!]
Code:
fastboot --set-active=a
fastboot reboot-bootloader
fastboot --skip-reboot update image[...].zip
Now straight from the bootloader, boot into recovery.
Wipe data/factory reset.
Let it reboot back into android.
Then, I followed the install instructions in the twrp thread to get custom recovery back onto my device. (If you want rooted stock android, flash it from twrp and then install the latest magisk manager apk.)
Now just find another custom rom and follow the install directions from that thread.
Click to expand...
Click to collapse
Now that's all the steps j took to flash the roms.
I do not install twrp app I skip that.
My first methond to flash stock on both slots is set slot to a then flash stock using the flash all bat file in from the stock images (google directions to flashing images)
Then it would reboot. Then I would set to slot b and flash the stock images the same way using the bat file.
Then I found out that wasn't really the best way to do it so I used deuces (I believe that was the users name) bat file to flash the stock images on both slots the correct way and that's what I've been doing since.
But your steps have a different step then what I do. It seems it does the same as deuces bat file however once it's done I just boot straight into stock rom. I dont boot into stock recovery and factory wipe. But I will definitely try that as well.

Finally fixed it!
I flash both slots and followed everyone's directions.
The problem was I wasn't wiping all the things I needed too.
I read in another roms steps to not only do the factory reset thin in TWRP, but to also manually wipe system, data, dalvik/art cache. Then flashed the room and TWRP.zip.
I did this and BOOM, I booted up into the room! Thanks again for everyone's help!

amartolos said:
My question would be do you have other details you might have overlooked? For example, at the end of flashing, TWRP would usually ask whether you want to install their app. Did you install it or did you skip it?
Also, what was your exact procedure in flashing stock rom to both slots? I have also messed around with custom roms and reverted back to stock using the following:
Return to Stock:
Source of this knowledge is Method 2 of this video.
#flashing bootloader to slot A and slot B
Code:
fastboot reboot-bootloader
fastboot flash bootloader_a bootloader[...].img
fastboot reboot-bootloader
fastboot flash bootloader_b bootloader[...].img
#flashing radio to slot A and slot B
Code:
fastboot reboot-bootloader
fastboot flash radio_a radio[...].img
fastboot reboot-bootloader
fastboot flash radio_b radio[...].img
#set active slot to B, flash system image
Code:
fastboot --set-active=b
fastboot reboot-bootloader
fastboot --skip-reboot --skip-secondary update image[...].zip
#set active slot to A, flash system image [different command!!!]
Code:
fastboot --set-active=a
fastboot reboot-bootloader
fastboot --skip-reboot update image[...].zip
Now straight from the bootloader, boot into recovery.
Wipe data/factory reset.
Let it reboot back into android.
Then, I followed the install instructions in the twrp thread to get custom recovery back onto my device. (If you want rooted stock android, flash it from twrp and then install the latest magisk manager apk.)
Now just find another custom rom and follow the install directions from that thread.
Click to expand...
Click to collapse
I stumbled across this post after having several issues trying to get my Pixel 2 XL flashed with a custom ROM (constantly resulting in boot-loops), and the steps worked perfectly.
I've ended up running these steps several times today, but I like keeping all of my stock images in sub-folders by release date. I'm not the greatest Powershell guru, but I've written a script that will search sub-directories in a folder for dates, and select the latest date and automatically flash the radio, bootloader, and image from that directory using your steps.
Code:
clear;
# Execution Policy must be adjusted in order to obtain the current executing directory of the script. This is a one-time command that must be run separately.
# Set-ExecutionPolicy RemoteSigned
# To reverse the command set the execution policy to restricted:
# Set-ExecutionPolicy Restricted
# The root directory which contains date sub-folders in the format yyyy-MM-dd representing an extracted OTA zip.
$startingDirectory = split-path -parent $MyInvocation.MyCommand.Definition;
# Alternatively, hard code a starting directory.
# [System.String]$startingDirectory = 'D:\Flashing\Roms\Taimen\Stock\';
[System.String]$targetFolder = (Get-ChildItem $startingDirectory | Select-Object -Property @{Name='Date';Expression = { Get-Date $_.Name -Format 'yyyy-MM-dd' }}, @{Name='FullName';Expression= {$_.FullName}} | Sort Date -Descending | Select -First 1).FullName;
if (-not $targetFolder) {
throw 'No folders are located in directory ''' + $startingDirectory + ''' with the date format yyyy-MM-dd.';
}
[System.String]$bootloader = Get-ChildItem $targetFolder -Name 'bootloader-*.img';
[System.String]$radio = Get-ChildItem $targetFolder -Name 'radio-*.img';
[System.String]$image = Get-ChildItem $targetFolder -Name 'image-*.zip';
# Validate all files have been successfully located.
[System.Collections.Generic.List[System.String]]$messages = [System.Collections.Generic.List[System.String]]::new();
if (-not $bootloader) {
$messages.Add('The bootloader file was not located.');
}
if (-not $radio) {
$messages.Add('The radio file was not located.');
}
if (-not $image) {
$messages.Add('The image file was not located.');
}
if ($messages.Length -gt 0) {
throw 'Unable to locate files in path ''' + $targetFolder + ''':' + [Environment]::NewLine + [System.String]::Join([Environment]::NewLine, $messages);
}
$bootloader = [System.IO.Path]::Combine($targetFolder, $bootloader);
$bootloader;
$radio = [System.IO.Path]::Combine($targetFolder, $radio);
$radio;
$image = [System.IO.Path]::Combine($targetFolder, $image);
$image;
#adb reboot bootloader;
function Reboot-Bootloader {
fastboot reboot-bootloader;
sleep 5;
}
#flashing bootloader to slot A and slot B
'Flashing bootloader to slot A.'
Reboot-Bootloader;
fastboot flash bootloader_a $bootloader;
'Flashing bootloader to slot B.'
Reboot-Bootloader;
fastboot flash bootloader_b $bootloader;
#flashing radio to slot A and slot B
'Flashing radio to slot A.'
Reboot-Bootloader;
fastboot flash radio_a $radio;
'Flashing radio to slot B.'
Reboot-Bootloader;
fastboot flash radio_b $radio;
#set active slot to B, flash system image
'Flashing system image to slot B.'
fastboot --set-active=b;
Reboot-Bootloader;
fastboot --skip-reboot --skip-secondary update $image;
#set active slot to A, flash system image [different command!!!]
'Flashing system image to slot A.'
fastboot --set-active=a;
Reboot-Bootloader;
fastboot --skip-reboot update $image;