Database Users

[Kernel]1.12.605.9 kernel with adb root

This is a stock kernel, except that adb root is permanent.
Removes the need for psneuter if you lose root access for whatever reason.
Flash via fastboot, cwr appears to still not work on kernels.
Code:
fastboot flash boot boot.img
http://www.mediafire.com/?qyk3mv5gns11epg

Pure Awesomeness...LOL...Nice BUD!

still can't get adb to recognise my phone in fastboot... I tried every driver that I have found an windows says that no driver is available... windows 7/64bit

Install HTC sync 3.
Also, adb and fastboot are mutually exclusive.

I use OSX, I grabbed the fastboot for mac binaries from HTC's website. But I can't get fastboot to run and flash the image. HTC says I should place fastboot anywhere on my system and then navigate to its path to use it but that just isn't working?

vdefender said:
I use OSX, I grabbed the fastboot for mac binaries from HTC's website. But I can't get fastboot to run and flash the image. HTC says I should place fastboot anywhere on my system and then navigate to its path to use it but that just isn't working?
Click to expand...
Click to collapse
Put it in the tools folder of the sdk...

two_cents said:
still can't get adb to recognise my phone in fastboot... I tried every driver that I have found an windows says that no driver is available... windows 7/64bit
Click to expand...
Click to collapse
This driver worked for me win_x/64bit
http://forum.xda-developers.com/showthread.php?t=878786
Sent from my ADR6400L using XDA App

I'm currently trying to install your other kernal, and after I moved my Fastboot.exe file into the platform-tools folder and executed Fastboot boot boot.img my command prompt is stuck at < waiting for device >
I cannot input anything into the command prompt, but I have control over my phone in fastboot.
any advice????
nvm

installed htc sync 3... coming from unrevoked I didn't install this cause they said it interferes with the root pkg... all this adb stuff i'm starting to actually like adb commands... just got to watch the typos... fasboot doesn't do anything lol

Make sure you set fastboot-mac or fast boot as chmod 755
chmod 755 ./fastboot
Click to expand...
Click to collapse
Then you would run it like
./fastboot flash boot boot.img
Click to expand...
Click to collapse

Always add the ./ before each adb command and fastboot command when using a mac. I had to learn that the hard way back in the day.

THATTON said:
Always add the ./ before each adb command and fastboot command when using a mac. I had to learn that the hard way back in the day.
Click to expand...
Click to collapse
I had to do this in ubuntu as well
Sent from my ADR6400L using XDA App

adrynalyne said:
This is a stock kernel, except that adb root is permanent.
Removes the need for psneuter if you lose root access for whatever reason.
Flash via fastboot, cwr appears to still not work on kernels.
Code:
fast boot flash boot boot.img
http://www.mediafire.com/?qyk3mv5gns11epg
Click to expand...
Click to collapse
Shouldnt fasboot in the code up there be connected? fastboot not fast boot. noobs'll freak. lol Thanks Adryn, this makes it a lot nicer.

How does this compare to the kernal in your rom thread? Coming from a DX, I'm new to the kernal stuff. Thanks.

two_cents said:
still can't get adb to recognise my phone in fastboot... I tried every driver that I have found an windows says that no driver is available... windows 7/64bit
Click to expand...
Click to collapse
Best thing for me , win 7 32, downloaded and installed pdanet from market, downloaded drivers to SD, mount as disk , install pda stuff off SD, and bam adb worked great , don't know if this ? Has been answered yet , haven't got that far in the thread
Sent from the Swag HTC Thunderbolt - ADR6400L using XDA Premium App

ran the flash, fastboot tells me that both went ok. but all my info still tells me 1.12.605.6 for build and software number. is there anything i can see that i know it changed. kernal states
2.6.32.21-gb05544a
[email protected] 18-2 #1
tue mar 1 16:38:55 CST 2011

Instructions: How to flash boot.img via fastboot For Mac
Requirements:
Rooted Thunderbolt
Ability to boot into the bootloader. (I used "./adb reboot bootloader")
1. Download fastboot-mac.zip and the boot.img
2. unzip and place fastboot-mac into your platform-tools folder
3. Place the downloaded boot.img into your platform tools folder
4. Open terminal and cd your platform-tools folder
5. Run "chmod 755 ./fastboot-mac"
6. Now run "./fastboot-mac devices"
7. You should see "HTxxxxxxxxxx fastboot" after running previous commands
8. Now to flash just run "./fastboot-mac flash boot boot.img"
9. it should say "sending 'boot' (3008 KB)... OKAY" and "writing 'boot'... OKAY"
Your Good to Go
10. Thank adrynalyne for the kernel
Also thank you tavella for the chmod 755 part of this.
Finally team AndIRC, Jcase and all.
Enjoy!!! PM me if i have made a mistake or if you have something to add.

icedmayhem said:
ran the flash, fastboot tells me that both went ok. but all my info still tells me 1.12.605.6 for build and software number. is there anything i can see that i know it changed. kernal states
2.6.32.21-gb05544a
[email protected] 18-2 #1
tue mar 1 16:38:55 CST 2011
Click to expand...
Click to collapse
March 1st kernel is the correct updated kernel... February is the stock kernel... You are runningthe stock .6 rom... Adryn has the .9 as a bloat free rom
Sent from my ADR6400L using XDA App

Ty
Sent from my ADR6400L using XDA App

You've done it again adryn, thanks and much appreciated as always.
Sent from my ADR6400L using XDA App

[Q]Manually updated to 4.2.2... Now locked out of adb and recovery. Help.

I'm in a bit of jam. I flashed the official zip from google to update to 4.2.2 and the flash seemed to work fine. I cleared both caches after the update
However, now I seem to be completely locked out of adb and the phone doesn't prompt me for authorization (the new feature in 4.2.2) http://www.androidpolice.com/2013/0...s-from-stealing-your-data-in-some-situations/ . I am showing connected but offline just like this article. I have tried multiple reboots (phone/computer) as well as different USB ports. I have not tried another computer yet.
When I try to go to recovery I get a red exclamation point dead robot as I assume the flash wiped TWRP and I can't reflash TWRP without adb/root.
I would like to try to avoid a complete internal memory factory reset from the rom which I'm not sure would work anyway.
Please help.

update your adb / sdk.

bodh said:
update your adb / sdk.
Click to expand...
Click to collapse
Fortunately, I was able to reflash TWRP using fastboot w/o using adb. At the bootloader, I ran
Code:
fastboot flash recovery recovery.img
which got my recovery back up and running.
I decided to do a factory wipe and even after that adb was showing as offline and not prompting. I am very confident that your suggestion of updating the platform tools is going to fix my issue.
Thank you.

Locked on 4.2.2
My Nexus 7 is locked on 4.2.2. I tried to Unlock with Nexus Root Toolkit and I get "adb offline". I did the command "adb devices" and the device showed up, but when I tried to unlock again, it gets stuck on "checking adb status". I updated SDK and copied the new adb.exe, fastboot.exe, etc into the platform-tools folder and it still doesnt work. So basically my oem is locked on 4.2.2 and I can get adb or the toolkit to work properly.. Is there a way to downgrade back to 4.2.1 or get the Wugfresh Nexus Toolkit to actually unlock my Nexus 7 on 4.2.2??

Yea, there's a way to downgrade if you have a nandroid and know what you're doing. The toolkit will need to be updated, and it helps to know how to do it manually first.

bodh said:
Yea, there's a way to downgrade if you have a nandroid and know what you're doing. The toolkit will need to be updated, and it helps to know how to do it manually first.
Click to expand...
Click to collapse
If you know the steps or can link me to a page, that would be much appreciated. I want clear steps.

Basically the same thing just happened to me. I updated to the newest android sdk then followed the steps here http://forum.xda-developers.com/showthread.php?t=2010312
I had to restore the complete stock image first, then I sideloaded the update. I made sure all of my files were in C:\Development\sdk\platform-tools (thats the directory I used, yours may be different). Open a command prompt on the platform-tools folder and run fastboot devices, if you see a number there you are good to go. Just follow the steps in the link above to flash each file.

Why cant people wait..
lol

Bronk93 said:
Basically the same thing just happened to me. I updated to the newest android sdk then followed the steps here http://forum.xda-developers.com/showthread.php?t=2010312
I had to restore the complete stock image first, then I sideloaded the update. I made sure all of my files were in C:\Development\sdk\platform-tools (thats the directory I used, yours may be different). Open a command prompt on the platform-tools folder and run fastboot devices, if you see a number there you are good to go. Just follow the steps in the link above to flash each file.
Click to expand...
Click to collapse
I'm going to try this. Can i just type "fastboot devices" in the command prompt and it'll work?
EDIT: I found a simple fix for anyone with this problem: CREATE A BACKUP FIRST, THIS WILL ERASE EVERY THING
1. Go into the platform-tools and open the command prompt by pressing Shift + Right Click.
2. Type in "adb reboot bootloader"
3. Then type in "fastboot oem unlock"
4. WALA! It'll take a while to start up, don't worry. Set up your device and that's all.

AJ Bryant said:
I'm going to try this. So would I have to copy a fastboot.exe into the platform-tools folder? Or can i just type "fastboot devices" in the command prompt and it'll work?
Click to expand...
Click to collapse
If you downloaded the new android sdk fastboot should already be in there

I found a simple fix for this problem: CREATE A BACKUP FIRST, THIS WILL ERASE EVERY THING
1. Go into the platform-tools and open the command prompt by pressing Shift + Right Click.
2. Type in "adb reboot bootloader"
3. Then type in "fastboot oem unlock"
4. WALA! It'll take a while to start up, don't worry. Set up your device and that's all.
---------- Post added at 12:05 PM ---------- Previous post was at 11:55 AM ----------
XX-RAZOR-XX said:
Why cant people wait..
lol
Click to expand...
Click to collapse
No need to wait because I found the fix, by myself.

Can't wait to get home and try this. I got stuck last night at adb offline
Sent from my Nexus 4 using xda app-developers app

But with oem unlock, you'll still be on 4.2.2. This thread should offer good info on flashing, albeit for a galaxy nexus, but it should be mostly applicable for a nexus 7. http://forum.xda-developers.com/showthread.php?t=1626895

bodh said:
But with oem unlock, you'll still be on 4.2.2. This thread should offer good info on flashing, albeit for a galaxy nexus, but it should be mostly applicable for a nexus 7. http://forum.xda-developers.com/showthread.php?t=1626895
Click to expand...
Click to collapse
That's the point; we want to be unlocked and rooted on 4.2.2. I previously thought that in order to get an unlocked and rooted Nexus, I'd have to be on 4.2.1, unlock and root, then upgrade to 4.2.2 but that's not the case. I just unlocked and rooted via ADB since the Nexus Root Toolkit wasn't working for 4.2.2. I (and probably others) kept getting the "adb offline" error even after allowing USB debugging between the device and PC. Point is, if you're on 4.2.2 with a locked bootloader, you'll need to unlock and root using ADB commands. I don't know how many people have this issue but if someone requests it, I'll just post the steps on how to unlock and root 4.2.2 jelly bean using the ADB commands.

Re: [Q]Manually updated to 4.2.2... Now locked out of adb and recovery. Help
What if I'm on 4.2.2 completely stock but with an unlocked boot loader. I get the adb offline message when I try to root using a toolkit. How would I go about rooting?
Sent from my Nexus 4 using xda app-developers app

Place su.zip on sdcard. Reboot in fastboot mode, probably volume up+down+power. In terminal on pc, fastboot boot cwm.img for your device, install zip from sdcard.

bodh said:
Place su.zip on sdcard. Reboot in fastboot mode, probably volume up+down+power. In terminal on pc, fastboot boot cwm.img for your device, install zip from sdcard.
Click to expand...
Click to collapse
What do u mean by terminal on my PC fast boot cwm.img
Sent from my Nexus 4 using xda app-developers app

Rooting Jelly Bean 4.2.2 via ADB
DowntownJeffBrown said:
What if I'm on 4.2.2 completely stock but with an unlocked boot loader. I get the adb offline message when I try to root using a toolkit. How would I go about rooting?
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
1. Download the SuperSU.zip from here: http://download.chainfire.eu/282/SuperSU/CWM-SuperSU-v0.98.zip and place it on your device in the sdcard. I'm assuming you already enabled USB debugging.
2. Download the recovery-clockwork-touch-6.0.1.0-grouper.img from here: https://www.dropbox.com/s/v4hjsb4lse3dwtc/cwm6010touch_INSTALL.zip and place it in the platform-tools folder. Assuming you know where it's located on your PC
3. Locate the "platform-tools" folder on your PC, open it, and press Shift + Right Click & Open the command prompt there.
4. Type in the command "Adb reboot bootloader"
5. Then type in the command "fastboot flash recovery recovery-clockwork-touch-6.0.1.0-grouper.img"
6. Now go to Recovery Mode on your Nexus and install the CWM-SuperSU-v0.98.zip from there.
7. Reboot the device once you're done and you have a rooted Nexus 7 via adb. Hope this helps.

AJ Bryant said:
1. Download the SuperSU.zip from here: http://download.chainfire.eu/282/SuperSU/CWM-SuperSU-v0.98.zip and place it on your device in the sdcard. I'm assuming you already enabled USB debugging.
2. Download the recovery-clockwork-touch-6.0.1.0-grouper.img from here: https://www.dropbox.com/s/v4hjsb4lse3dwtc/cwm6010touch_INSTALL.zip and place it in the platform-tools folder. Assuming you know where it's located on your PC
3. Locate the "platform-tools" folder on your PC, open it, and press Shift + Right Click & Open the command prompt there.
4. Type in the command "Adb reboot bootloader"
5. Then type in the command "fastboot flash recovery recovery-clockwork-touch-6.0.1.0-grouper.img"
6. Now go to Recovery Mode on your Nexus and install the CWM-SuperSU-v0.98.zip from there.
7. Reboot the device once you're done and you have a rooted Nexus 7 via adb. Hope this helps.
Click to expand...
Click to collapse
What about for a nexus 4. Do u know where I can get that cwm?
Sent from my Nexus 4 using xda app-developers app

DowntownJeffBrown said:
What about for a nexus 4. Do u know where I can get that cwm?
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
For the Nexus 4 use this cwm image instead: http://download2.clockworkmod.com/re...0.2.3-mako.img
When youre doing the fastboot recovery, put in the name of this img file at the end. "fastboot flash recovery [name of the download file].img

[Q] N7, 4.3 "signature verification fail" (previously rooted device.

Hello, my name is noob. I have an addiction...
...to my Nexus 7! Unfortunately, I have not been able to update to 4.3!
My device was previously rooted (it no longer is) and I have tried everything I know and more. When it was rooted, I did not install a custom ROM or anything. I essentially just used root capabilities to get some apps and mess around with some apps a little.
When I try to update to 4.3 automatically as Google has me do it, I get the "signature verification failure".
I also tried to update it manually by downloading the update from androidpolice.
Then, I disabled system verification and tried to install the update and got a different error:
"Warning: No file_contextsVerifying current system... assert failed: apply_patch_check("/system/lib/libSR_AudioIn.so", "9c386ff759d8553e312e5ffc5773449ae6634748", "bcc09f67f497c6a6edece202942bc4c45f712f62"
E: Error in /sdcard/0/ab67ca07c4b2e03eca795ada10ff041b77fbb7bf.signed-nakasi-JWR66V-from-JDQ39.ab67ca07.zip
(Status 7)
Installation aborted.
What can/should i do?
Any help is greatly appreciated! Also, given my noob status, the simpler you can put things, the better. I am good at following step by step instructions, but give me some acronyms and use fancy language and I might fail.
Thank you!
Edit 1: I forgot to mention that I also did a factory reset and tried to update to 4.3, but that didn't help either.

I am also having the same problem. an error like this. any ideas why and how to fix it? and after it aborted when my n7 booted up and i check for updates it says ur n7 is up to date, but then the version is stil 4.2.2 not 4.3. so any solution guys? is it because i'm using custom kernel? i'm using franco kernel rite now.

There are many threads dealing with these problems ... Please use the search function before starting a new thread.
To answer your question: you have a non stock system so the OTA update is failing. You need either return to stock or do the update manually. Btw. in my blog there is an article how to do so.
Sent from my Nexus 7 using xda app-developers app

AndDiSa said:
There are many threads dealing with these problems ... Please use the search function before starting a new thread.
To answer your question: you have a non stock system so the OTA update is failing. You need either return to stock or do the update manually. Btw. in my blog there is an article how to do so.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Well, I did search the forums and didn't find anything that helped. And, like I said, I tried doing it manually and it didn't work.
Tomorrow I will check out your blog though and see if the instructions are any different than what I found elsewhere. Maybe i did a step wrong or something?

Success! I had to incorporate some steps from a slightly different method of updating, but it finally worked!
Thank you!

ItsDare said:
Success! I had to incorporate some steps from a slightly different method of updating, but it finally worked!
Thank you!
Click to expand...
Click to collapse
Hi! I am having the same problem and getting Status 7 error in CWM Touch.
Can you please let me know as well which method did you use? Thanks

ItsDare said:
Success! I had to incorporate some steps from a slightly different method of updating, but it finally worked!
Thank you!
Click to expand...
Click to collapse
Could you provide the detailed step-by-step instruction? I'm on the same (noob) level as you were just before you started this thread.

pawelzielak said:
Could you provide the detailed step-by-step instruction? I'm on the same (noob) level as you were just before you started this thread.
Click to expand...
Click to collapse
http://anddisa.blogspot.de/
You can use the instructions here (although he left a bit out)
1. install http://www.droid-life.com/2013/04/08/koush-releases-universal-adb-driver-for-windows/
2. install https://docs.google.com/file/d/0B1S0LCuXCnnmSWh6NGJmSE1BUWc/edit
3. install http://www.7-zip.org/download.html
4. download https://developers.google.com/android/nexus/images#nakasijwr66v
5. open the folder fastboot/adb installed to
6. open the image (#4) with 7zip (#3)
7. extract bootloader.img, boot.img and system.img into fastboot folder(#5)
8. run fasboot (should be in start menu), brings up command prompt)
9. type at command prompt "fastboot flash bootloader bootloader-*********.img" *** = use the file name that you extracted (#7)
10. type at command prompt "fastboot reboot-bootloader"
11. type at command prompt "fastboot flash boot boot.img"
12. type at command prompt "fastboot flash system system.img"
13. type at command prompt "fastboot reboot"
14. enjoy 4.3

gallahad2000 said:
You can use the instructions here (although he left a bit out)
1. install
....
14. enjoy 4.3
Click to expand...
Click to collapse
Oh, so you did it via PC.
I still would like to try with OTA. My problem is checksum on build.prop. I modified it and now I reverted changes but there still may be some white character difference. Could anyone attach build.prop file (along with its checksum) of stock n73g a4.2.2? I'll give it one more try.
With N73G

What I found most helpful in fixing my issue was this thread!
http://forum.xda-developers.com/showthread.php?t=1907796
It is a guide to flashing the factory image to return it to stock, but can be used to update to 4.3 as well!
What I did to fix my specific problem was:
Download the 4.3 update files from androidpolice.
Extracted these three files from it as suggested on AndDiSa's blog:
bootloader-grouper-4.23.img
boot.img
system.img
Plugged my N7 into my computer and since my device doesn't show up in my computer in MTP mode, but does in PTP, I switched to PTP and typed the following code into a command window:
> adb reboot-bootloader
I personally found it necessary to erase boot, cache, recovery, system and userdata to get my update to work. However, if it works without erasing those, that is definitely preferable, and you can skip these commands:
> fastboot erase boot
> fastboot erase cache
> fastboot erase recovery
> fastboot erase system
> fastboot erase userdata
Then type these commands:
> fastboot flash bootloader bootloader-grouper-4.23.img
> fastboot reboot-bootloader
> fastboot flash boot boot.img
> fastboot flash system system.img
Then I rebooted my N7 and Voila, I was using 4.3!

Verification fail on 4.3 update
I am using the galaxy nexus, i had rooted it and was using another custom ROM - ParanoidAndroid 3.60. I currently have the 4.2.2 and i'm trying to update it through my system update but it loads and then gives the error message "verification failed"
I've tried it using the OTA RootKeeper procedure too but the same error turns up. Please help!

[GUIDE]Nexus 9 back to stock guide - Unbrick - Restore factory firmware

The aim of this thread is to make an easy guide to flashing stock firmware. Owners of previous nexus devices already know all this stuff, this thread is aimed at making the process as simple as possible for new users. This will work regardless of what modifications you've done to your device. Remember to backup all your important data and do this with the knowledge that all flashing activity carries some risk.
Download
Factory image here
(for windows users) Minimal adb & fastboot
(for mac users) adb & fastboot for mac
Follow the instructions to install adb on your computer.
Prepare your tablet
Enable developer options in settings > about tablet and tapping build number 7 times
Open developer options and enable usb debugging. (If you haven't unlocked your bootloader yet, tick enable oem unlock)
Extract images
Place the downloaded factory image inside your adb folder and extract with 7zip.
A new folder will be there called something like volantis-lrx21. Open and extract "image-xxxxx-zip" to your adb folder. We are interested in these files:
bootloader-flounder-xxxxxx.img
boot.img
recovery.img
cache.img
system.img
vendor.img
Place these files directly into your adb folder.
# I recommend renaming the 'bootloader-flounder-xxxxxx.img' to just 'bootloader.img' to make it easier to type.
Now that everythings set up, we can start flashing
Plug in your device. Open the adb folder, hold shift and right click and select open command window here
(if your having driver issues try using Pdanet)
Run these commands one at a time
Code:
adb devices
adb reboot bootloader
if you haven't unlocked the bootloader yet run
Code:
fastboot oem unlock
and follow the instructions using the volume keys to scroll through the menu. This procedure will wipe all data.
Run the following commands one at a time
Code:
fastboot flash bootloader bootloader-flounder-xxxxxxx.img
[B] [I](replace 'bootloader-flounder-xxxxx.img' with full name of bootloader image[/I])[/B]
fastboot reboot-bootloader
fastboot -w
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash cache cache.img
fastboot flash system system.img
fastboot flash vendor vendor.img
(OPTIONAL) At this stage you can relock the bootloader if you want by running the command
Code:
fastboot oem lock
finally reboot the device by running
Code:
fastboot reboot
Thats it. Enjoy your tablet in factory condition

Great. Is it possible to make a batch file to run all the commands at once?

albsat said:
Great. Is it possible to make a batch file to run all the commands at once?
Click to expand...
Click to collapse
There is already a flash all batch script that comes with the firmware files but I've noticed that some people have problems with it so I decided not to include it. It should work fine most of the time.

i am long-time familiar with htc,but new to nexus. i was looking thru a couple downloaded factory image files and having noticed that "rebootRUU" is an oem command,and that "image-xxxxx-zip" contains an android info document,i am curious if anyone has tried flashing image-xxxxx-zip as a zip file,in ruu mode?

Cool, thanks for the information.

Thanks for creating this! Will come in handy. Saving this for later

This has been useful as the update from 5.0.1 to 5.0.2 kept failing on my rooted device. It was successful and educational.

scotty1223 said:
i am long-time familiar with htc,but new to nexus. i was looking thru a couple downloaded factory image files and having noticed that "rebootRUU" is an oem command,and that "image-xxxxx-zip" contains an android info document,i am curious if anyone has tried flashing image-xxxxx-zip as a zip file,in ruu mode?
Click to expand...
Click to collapse
I indeed tried this as a last chance hoping it would bypass bootloader lock protection. It didn't work since I think the factory image is not signed by HTC as RUU are . It also lead to a fastboot crash. Now sending my nexus 9 for RMA
Sent from my HTC One using XDA Free mobile app

remedya said:
This has been useful as the update from 5.0.1 to 5.0.2 kept failing on my rooted device. It was successful and educational.
Click to expand...
Click to collapse
Same here. The manual flash method worked very well. Here's hoping that Google doesn't muck 5.1

cant flash stock rom
I'm trying to downgrade my nexus 9 from DU rom 5.1.1 to stock for everything. I'm running the flash-all.sh on linux while my tablet is in bootloader mode. Tab makes and few checks and reboots automatically in bootloader mode. I reboot tablet and still has the DU rom. Any tips

nyasha1935 said:
I'm trying to downgrade my nexus 9 from DU rom 5.1.1 to stock for everything. I'm running the flash-all.sh on linux while my tablet is in bootloader mode. Tab makes and few checks and reboots automatically in bootloader mode. I reboot tablet and still has the DU rom. Any tips
Click to expand...
Click to collapse
The flash all script doesn't seem to work on linux. You shouldn't have a problem if you write the commands out manually.

nyasha1935 said:
I'm trying to downgrade my nexus 9 from DU rom 5.1.1 to stock for everything. I'm running the flash-all.sh on linux while my tablet is in bootloader mode. Tab makes and few checks and reboots automatically in bootloader mode. I reboot tablet and still has the DU rom. Any tips
Click to expand...
Click to collapse
Art Vanderlay said:
The flash all script doesn't seem to work on linux. You shouldn't have a problem if you write the commands out manually.
Click to expand...
Click to collapse
As indicated, the flash all script doesn't work very well on any system. Flash each .img separately via fastboot.

cam30era said:
As indicated, the flash all script doesn't work very well on any system. Flash each .img separately via fastboot.
Click to expand...
Click to collapse
Problem is that the tgz is too big for the device's buffer, so it craps out before it actually writes the images. Its been this way for a while over several different nexus devices. Kind of like nobody at google ever even bothered to test the process.

doitright said:
Problem is that the tgz is too big for the device's buffer, so it craps out before it actually writes the images. Its been this way for a while over several different nexus devices. Kind of like nobody at google ever even bothered to test the process.
Click to expand...
Click to collapse
I agree.

I also used Linux but I executed the commands individually rather than using the script. It worked.

remedya said:
I also used Linux but I executed the commands individually rather than using the script. It worked.
Click to expand...
Click to collapse
I cant flash system.img I get error
sending 'system' (1108544 KB)...
FAILED (remote: data length is too large)
finished. total time: 0.105s

nyasha1935 said:
I cant flash system.img I get error
sending 'system' (1108544 KB)...
FAILED (remote: data length is too large)
finished. total time: 0.105s
Click to expand...
Click to collapse
Update your Android SDK.

These instructions also worked with 5.1.1

im trying to install back to facctory i erased my system and recovery and data and now when i try to flash bootloader i get error cannot open bootloader someone please im stuck in bootloader mode

maxtcee said:
im trying to install back to facctory i erased my system and recovery and data and now when i try to flash bootloader i get error cannot open bootloader someone please im stuck in bootloader mode
Click to expand...
Click to collapse
Are you writing the full name and file path for the bootloader img?

TMo, Pixel Dust, EX kernel issues.

Hopefully this makes sense.
OK, here's what I did.
Yesterday I was on June 19 Bootleggers (19) ROM. I decided to go to a Android 10 ROM. I picked Pixel Dust (March 2020). I clean flashed with (-w) fastboot from Google/Android v29.6. I extracted
developer-tools to the root of my C drive on my Win10 HP laptop. I extracted the factory image from Google (March 2020) and put it in developer-tools folder. I used a 3.0 USB cable.
I fastbooted, but I flashed TWRP image then flashed through TWRP Pixel Dust, TWRP installer then rebooted system so I could flash Magisk. Then I flashed EX kernel.
No problems yet.
Later in the day I got an update notice for EX to be updated. I flashed thru the EX app the update. Now a lack of phone function. SMS works both ways. No MMS though. No LTE, VVM, WiFi calling, no outbound calls, inbound works.
I flashed another EX kernel update thru TWRP this morning. Same issues.
I went to T-Mobile to swap out SIM cards. No difference. TMo says my phone is on the network. I'm missing my phone number from the screenshot.
After posting this I'm thinking I just need my phone number back.
Any thoughts from the Brain Trust?

I'd suggest redoing the factory flash, but straight from the Factory image instead of "putting in the developer-tools folder". This will erase your device, including internal storage. Keep in mind if you want to be able to decrypt in TWRP, you'll need to do a factory flash of April '19 images first, boot the device and setup a pin, then follow the outline below.
If willing, give this a try:
Download latest factory image: https://developers.google.com/android/images
Extract Zip
In Terminal on your computer, navigate to the unzipped directory (You want to flash to both slots...)
In a Terminal window run: fastboot --set-active=b
Then run: fastboot reboot-bootloader
Run flash-all (this will flash everything on slot B) (edit the file removing the -w if you flashed April '19 images and set a pin to enable TWRP decryption)
Let device boot, then reboot to bootloader again (don't need to setup the device)
In a Terminal window run: fastboot --set-active=a
Then run: fastboot reboot-bootloader
Then run flash-all.sh (this will flash everything on slot A) (edit the file removing the -w if you flashed April '19 images and set a pin to enable TWRP decryption)
Boot device and setup as normal unless you want to run a custom ROM
If you want to run a custom ROM, boot device but don't set it up yet:
Reboot to bootloader
"fastboot boot" to TWRP.img
Factory reset and install custom ROM (don't wipe system)
Boot and setup device
If desired, flash Magisk after first boot
Hope this helps!

MrBrady said:
I'd suggest redoing the factory flash, but straight from the Factory image instead of "putting in the developer-tools folder". This will erase your device, including internal storage. Keep in mind if you want to be able to decrypt in TWRP, you'll need to do a factory flash of April '19 images first, boot the device and setup a pin, then follow the outline below.
If willing, give this a try:
Download latest factory image: https://developers.google.com/android/images
Extract Zip
In Terminal on your computer, navigate to the unzipped directory (You want to flash to both slots...)
In a Terminal window run: fastboot --set-active=b
Then run: reboot-bootloader
Run flash-all (this will flash everything on slot B) (edit the file removing the -w if you flashed April '19 images and set a pin to enable TWRP decryption)
Let device boot, then reboot to bootloader again (don't need to setup the device)
In a Terminal window run: fastboot --set-active=a
Then run: reboot-bootloader
Then run flash-all.sh (this will flash everything on slot A) (edit the file removing the -w if you flashed April '19 images and set a pin to enable TWRP decryption)
Boot device and setup as normal unless you want to run a custom ROM
If you want to run a custom ROM, boot device but don't set it up yet:
Reboot to bootloader
"fastboot boot" to TWRP.img
Factory reset and install custom ROM (don't wipe system)
Boot and setup device
If desired, flash Magisk after first boot
Hope this helps!
Click to expand...
Click to collapse
Is it a bad idea to just fastboot/flash the radio?

Scottay5150 said:
Is it a bad idea to just fastboot/flash the radio?
Click to expand...
Click to collapse
I don't think it would be a bad idea, just be sure to flash to both slots. You can use the command: fastboot flash radio --slot all nameofradio.img.

MrBrady said:
I don't think it would be a bad idea, just be sure to flash to both slots. You can use the command: fastboot flash radio --slot all nameofradio.img.
Click to expand...
Click to collapse
The flashing worked. Didnt fix the issue. I am attempting to flash factory again.

Scottay5150 said:
The flashing worked. Didnt fix the issue. I am attempting to flash factory again.
Click to expand...
Click to collapse
WTH, this is happening now.
C:\platform-tools>FastBoot --set-active=b
Setting current slot to 'b' OKAY [ 0.010s]
Finished. Total time: 0.013s
C:\platform-tools>flash-all
'flash-all' is not recognized as an internal or external command,
operable program or batch file.
C:\platform-tools>reboot-bootloader
'reboot-bootloader' is not recognized as an internal or external command,
operable program or batch file.
Ideas?

Scottay5150 said:
WTH, this is happening now.
C:\platform-tools>FastBoot --set-active=b
Setting current slot to 'b' OKAY [ 0.010s]
Finished. Total time: 0.013s
C:\platform-tools>flash-all
'flash-all' is not recognized as an internal or external command,
operable program or batch file.
C:\platform-tools>reboot-bootloader
'reboot-bootloader' is not recognized as an internal or external command,
operable program or batch file.
Ideas?
Click to expand...
Click to collapse
I'm guessing your on Windows, which I'm not familiar with. Also guessing the Windows executable would be flash-all.bat, which is in the Factory Images folder. On Linux / Mac you open a terminal window, CD to the factory image directory where the zip was extracted and run: ./flash-all.sh (Including the period. Again, that's on Linux / Mac - Windows is probably different).
For the reboot, the command should be: fastboot reboot-bootloader
Edited my instructions above

MrBrady said:
I'm guessing your on Windows, which I'm not familiar with. Also guessing the Windows executable would be flash-all.bat, which is in the Factory Images folder. On Linux / Mac you open a terminal window, CD to the factory image directory where the zip was extracted and run: ./flash-all.sh (Including the period. Again, that's on Linux / Mac - Windows is probably different).
For the reboot, the command should be: fastboot reboot-bootloader
Edited my instructions above
Click to expand...
Click to collapse
Yes, I am on Win10. I am able to set active b, see my device info, reboot bootloader. What am I doing wrong?
C:\platform-tools>flash-all.bat
'flash-all.bat' is not recognized as an internal or external command,
operable program or batch file.
I did these in case I did not put the files in the right place.
C:\platform-tools\taimen-qq2a.200305.002>flash-all
C:\platform-tools\taimen-qq2a.200305.002>flash-all.bat

Scottay5150 said:
Yes, I am on Win10. I am able to set active b, see my device info, reboot bootloader. What am I doing wrong?
C:\platform-tools>flash-all.bat
'flash-all.bat' is not recognized as an internal or external command,
operable program or batch file.
C:\platform-tools\taimen-qq2a.200305.002>flash-all
C:\platform-tools\taimen-qq2a.200305.002>flash-all.bat
Click to expand...
Click to collapse
One of the following should work:
fastboot flash all
fastboot flash-all
fastboot flash-all.bat
Or you could just double click the flash-all.bat file as well :good:

Badger50 said:
One of the following should work:
fastboot flash all
fastboot flash-all
fastboot flash-all.bat
Or you could just double click the flash-all.bat file as well :good:
Click to expand...
Click to collapse
I attempted all of those, no dice. I rebooted laptop, no dice.

Scottay5150 said:
I attempted all of those, no dice. I rebooted laptop, no dice.
Click to expand...
Click to collapse
Are you using powershell or command prompt?
Command prompt always works best :good:

Scottay5150 said:
I attempted all of those, no dice. I rebooted laptop, no dice.
Click to expand...
Click to collapse
CMD all day long. What are your thoughts now?

Scottay5150 said:
CMD all day long. What are your thoughts now?
Click to expand...
Click to collapse
Interesting. Even double clicking the flash-all.bat file didn't work either?? About the only other thing I can suggest is to download platform-tools again and start over, and/or try another USB A to C cable or a different USB port.

Scottay5150 said:
CMD all day long. What are your thoughts now?
Click to expand...
Click to collapse
flash-all.bat as well as the files you want to flash (all images and the taimen-qq2a.200305.002.zip) got to be in same folder as your fastboot.exe, not in a further subfolder.
Sent from my Pixel 4 XL using XDA Labs

Badger50 said:
Interesting. Even double clicking the flash-all.bat file didn't work either?? About the only other thing I can suggest is to download platform-tools again and start over, and/or try another USB A to C cable or a different USB port.
Click to expand...
Click to collapse
Exactly, interesting. It is making me mental. I have used different cables/ports. No avail. I will re DL platform tools.
Is there any kind of permission setting I need to do with Win10?

5m4r7ph0n36uru said:
flash-all.bat as well as the files you want to flash (all images and the taimen-qq2a.200305.002.zip) got to be in same folder as your fastboot.exe, not in a further subfolder.
Sent from my Pixel 4 XL using XDA Labs
Click to expand...
Click to collapse
Like in this screenshot?

Scottay5150 said:
Exactly, interesting. It is making me mental. I have used different cables/ports. No avail. I will re DL platform tools.
Is there any kind of permission setting I need to do with Win10?
Click to expand...
Click to collapse
Scottay5150 said:
Like in this screenshot?
Click to expand...
Click to collapse
Yep, that looks correct. This is how I use CMD with platform-tools now on W10. Maybe it'll help.
https://android.gadgethacks.com/how-to/open-adb-fastboot-command-window-platform-tools-0195269/

Scottay5150 said:
Like in this screenshot?
Click to expand...
Click to collapse
Yes exactly.
Sent from my Pixel 4 XL using XDA Labs

5m4r7ph0n36uru said:
Yes exactly.
Sent from my Pixel 4 XL using XDA Labs
Click to expand...
Click to collapse
Now I don't feel stupid. The flash all bat was without text!! OMFG.
I am back to stock, for the moment. I'll attempt PD again in a few.

Scottay5150 said:
I attempted all of those, no dice. I rebooted laptop, no dice.
Click to expand...
Click to collapse
I'm no expert but what works for me is
Fastboot flash on both slots bootloader, radio then vendor one by one rebooting bootloader after each flash.
Then fastboot update (drag and drop extracted taimen folder)
Let it boot stock before flashing any roms