Database Info

Return to Stock Kernel

Here is the deal. Got my wifi only on launch day. Soon there after rooted. Installed bigdogrush 1.3 kernel. Tried to update to sdcard support. Each time I tried it would screw up my wifi....so I eventually gave up. Here is the real problem. Now I can't install recently released 3.1 update. Can anyone explain to me how to return to the stock kernel? I understand this will allow me to install the 3.1 update. Thanks for any help.

xhuck1 said:
Here is the deal. Got my wifi only on launch day. Soon there after rooted. Installed bigdogrush 1.3 kernel. Tried to update to sdcard support. Each time I tried it would screw up my wifi....so I eventually gave up. Here is the real problem. Now I can't install recently released 3.1 update. Can anyone explain to me how to return to the stock kernel? I understand this will allow me to install the 3.1 update. Thanks for any help.
Click to expand...
Click to collapse
try this, i just did it and works great. you basically need to download the stock images and use adb to push them. btw i assume you have a us version wifi only xoom. i would skip the last step about relocking it, if you plan to upgrade your kernel after your on 3.1.
http://developer.motorola.com/products/software/
once your back to stock everything, you can safely update to 3.1

I appreciate your help. Problem is I don't know how to do the things you are talking about. I've downloaded the images and the sdk. I'm not sure where I should put them on my zoom. Also when I try to run fastboot I get a device not found message. I also get a AdbWinApi.dll not found. I have no idea how to fix any of this. Yes I have a U.S. WIFI. I used the one click rook method. Is there a one click method out there that would help me?

If you're using windows, open the SDK folder and browse to the tools folder. Copy the img files to that folder.
Now open a command prompt and browse to the SDK Folder\tools folder (this folder as the fastboot.exe file that we're going to use and now the img files are also here!)
Now reboot your XOOM into fastboot mode (turn off the xoom, then turn the XOOM back on and while at the "Dual Core" logo, start pressing volume down until you see "--> Fastboot" up on the top left corner then press volume up to start the fastboot protocol).
Once you're in fastboot mode, in the command prompt, type fastboot devices to make sure your xoom is listed on there. If not, check to make sure your system isn't missing drivers, if so, download the xoom drivers again or if you have the Motorola Mobile Drivers installed already, open the Motorola Mobile Driver Installer and do an update to make sure you have the latest drivers).
Once you've confirmed that fastboot can talk to your xoom, run this commands:
Code:
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash userdata userdata.img
fastboot erase cache
fastboot oem lock
Your xoom will then relock itself, format, and reboot.
This is as clear as I can be.
If need to, re-run the SDK Manager and make sure you have the correct packages installed needed.

xhuck1 said:
Here is the deal. Got my wifi only on launch day. Soon there after rooted. Installed bigdogrush 1.3 kernel. Tried to update to sdcard support. Each time I tried it would screw up my wifi....so I eventually gave up. Here is the real problem. Now I can't install recently released 3.1 update. Can anyone explain to me how to return to the stock kernel? I understand this will allow me to install the 3.1 update. Thanks for any help.
Click to expand...
Click to collapse
I'm betting the reason your wifi isn't working is because you didn't push the .ko files. Think of those as driver files. You probably just flashed the boot partition.

Nexus S i9020A radio and factory image questions

I have spent a couple days searching for an answer to my question and although I found some, they were not exactly what I was looking for so sorry for a new thread.
I bought the i9020A for my niece and it was running 2.3.4. I tried to force the 4.0.4 OTA update but after some reading I came to the conclusion that I needed to be on a different version and it would not work on 2.3.4. After messing around I gave up and did this.
http://forum.xda-developers.com/showthread.php?t=1653713
She is having issues with dropping signal, and very slow messaging. She also reported that a couple of times she received an error that said "relaunch Me". I have never heard of that issue. What I want to do is just use the factory image to put her on 4.0.4 and in line to get the OTA in the future. She doesn't need a custom recovery anyway. I want her on stock. I have the SDK and everything, bootloader unlocked, fastboot installed. I download the image from Google Which I believe should be "Factory Images "sojua" for Nexus S (850MHz version, i9020a)" because her model is the i9020A and using it on ATT. At this point is where Im a little lost. I think it should be easy at this point but i cant find a good how-to on exactly what to do. I used this one
http://forum.xda-developers.com/showthread.php?t=1572307
but the english is kind of broken and frankly dont understand it enough as a somewhat noob. Really 2 is what I dont understand. I extract the files and move them in the entirety to android-sdk/platform-tools/. I get that. But then he says "run a cmd and moves in "platform-tools" folder"...what?? Is he saying change directory? Thats what I assumed but again, didnt want to break something.
Finally, do I need to flash KB3 radio or is the radio with 4.0.4 on this device fixed for proper hspa+ like speeds? Basically from a 200k to a 1.5meg average. I have read people complaining about the radio and dropped signal as well, but havent found any that talk about it after running on stock 4.0.4. Shes a teenager and doesnt need bleeding edge, but if the speeds are that different than Ill happily give her a better radio if possible.
Anything other suggestions would be great so that I can give her a tip top device. Thanks again!

https://developers.google.com/android/nexus/images
the instruction are on the same page ..
all you need is fastboot (make sure it is in your path, meaning : if you type -just- fastboot in a command -or terminal - you don;t get "command not found" -or somthing simimilar-. there is a script in the zip tat will do all (flashall.sh, on mac and linux it works just fine, On windows I don;t know, worst case open if in notepad and see what it does -- if I remmeber it is 3 -4 lines long- and tyupe the commands yourself )
do know that this will erase anything and everything on the device.
--
PS: flashall.sh does this :
fastboot flash bootloader bootloader-crespo-i9020xxkl1.img
fastboot reboot-bootloader
fastboot flash radio radio-crespo-i9020uckj1.img
fastboot reboot-bootloader
fastboot -w update image-sojua-imm76d.zip
Click to expand...
Click to collapse
if fastboot is not in your path, just copy it in the folder where you extracted the factory image file (should be "sojua-imm76d") and replace "fastboot" above with "./fastboot" if you're on a mac/linux or "fastboot.exe" if your on windows.

Do what he said
Hit the thanks button

I'm on Windows so I'll try what your saying. My fast bot is in the tools folder, should it not be? So basically I have to be at that directory for it to work but have used it.
Sent from my Galaxy Nexus using Tapatalk 2

kenshin33 said:
https://developers.google.com/android/nexus/images
the instruction are on the same page ..
all you need is fastboot (make sure it is in your path, meaning : if you type -just- fastboot in a command -or terminal - you don;t get "command not found" -or somthing simimilar-. there is a script in the zip tat will do all (flashall.sh, on mac and linux it works just fine, On windows I don;t know, worst case open if in notepad and see what it does -- if I remmeber it is 3 -4 lines long- and tyupe the commands yourself )
do know that this will erase anything and everything on the device.
--
PS: flashall.sh does this :
if fastboot is not in your path, just copy it in the folder where you extracted the factory image file (should be "sojua-imm76d") and replace "fastboot" above with "./fastboot" if you're on a mac/linux or "fastboot.exe" if your on windows.
Click to expand...
Click to collapse
So wait, im supposed to replace "fastboot" with fastboot.exe so fastboot flash bootloader bootloader-crespo-i9020xxkl1.img would look like fastboot.exe flash bootloader bootloader-crespo-i9020xxkl1.img? That doesnt seem right.

TheIowaKid said:
So wait, im supposed to replace "fastboot" with fastboot.exe so fastboot flash bootloader bootloader-crespo-i9020xxkl1.img would look like fastboot.exe flash bootloader bootloader-crespo-i9020xxkl1.img? That doesnt seem right.
Click to expand...
Click to collapse
yes, assuming that the file "fasboot.exe" is in the same directory as all those other files (img files) just open a cmd window change to where you extracted the files ( cd path_where_you_extracted_the files, or in some wversion of windows in the explorer, witgh click and open cmd here --or something like that-, and type the commands one bye one (after rebooting the on bootloader mode -- turn it off and press vol up while still pressing vol up press power and hold it,-- )

So I actually put the .exe in the command line after the word fastboot? This may explain why it didn't work for me the first time! Also on a side not do I need to worry about cache or dalvik in this scenario or can I just take her phone, enable debugging, and do this knowing it will wipe everything?
Sent from my Galaxy Nexus using Tapatalk 2

TheIowaKid said:
So I actually put the .exe in the command line after the word fastboot? This may explain why it didn't work for me the first time! Also on a side not do I need to worry about cache or dalvik in this scenario or can I just take her phone, enable debugging, and do this knowing it will wipe everything?
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
yes, after "fastboot" --fastboot.exe--
this will wipe everything (it will put the phone in the same state you first got it it, except the bootloader, which will stay unlocked --

Happy to report back that everything worked as planned. I didn't have to add the .exe I simply made sure everything was in the same folder; adb, fastboot, and all the extracted files from the download. Took like a minute total. A follow up though, she still seems to have issues with the radio. I would need to put a custom recovery on in order to flash a radio, correct?
Sent from my Galaxy Nexus using Tapatalk 2

TheIowaKid said:
Happy to report back that everything worked as planned. I didn't have to add the .exe I simply made sure everything was in the same folder; adb, fastboot, and all the extracted files from the download. Took like a minute total. A follow up though, she still seems to have issues with the radio. I would need to put a custom recovery on in order to flash a radio, correct?
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
not if you get the img file. one the steps you just performed was flashing a radio img
"fastboot flash radio radio-crespo-i9020uckj1.img" <-- this one to be precise.
there should be a thread in one of the forums that has of all the official Roms (with radios and everything, full and incremental), I think it is in the general section, there should be instructions on how to flash a radio image.
I can't find the thread in question but the link you provided in your first post has 2 of them, the one you just flashed and the previous one (UCKF1)
just download the the factory image you want do exactely what you did b4 except flash only the radio img (ie : fastboot flash radio some_radio_image.img)
you can find some here too : http://www.randomphantasmagoria.com/firmware/nexus-s/i9020a/

KB3 is the radio that I keep seeing pop up. Is that the good one?
Sent from my Galaxy Nexus using Tapatalk 2

frankly I wouldn;t know, I'm using the latest one (From the last OTA I think) I've never had any problems with it. try and see, you can always flash an other one.

Boot Issues, Trying to Go Back To Stock

So I got a pixel recently. I unlocked the bootloader, installed TWRP, and rooted it. However, it's been a few years since I had an unlocked and rooted phone so I forgot that the OTA updates can't be applied. So I decided to go back to the factory image. A quick google search lead me to an article where they said I could select the Full Unroot option in the settings of SuperSU and it would attempt to restore the stock boot image and recovery image. So I did that, and ended up in a boot loop.
Well, then I decided to try flashing the entire factory images from google, using the flash-all.bat file they provide. It seems to flash the bootloader and the radio fine, but when it comes to the part where it flashes everything in the "image-sailfish-nde63l.zip" (I picked this build because it was the one I was on when the pixel arrived) folder it says "Error: failed to load 'image-sailfish-nde63l.zip': not enough space."
I can still get to the TWRP recovery, and I can get to the bootloader, but currently nothing else seems to work. Please, can anyone help me?
UPDATE: The issue was outdated adb and fastboot. I had 1.0.32, once I had the latest versions (1.0.36 right now) I could fix everything.
UPDATE: So I extracted boot and system from the zip file and manually flashed those. It boots now, but when it does it says there are errors with the device and to contact the manufacturer, also a lot of dialog boxes pop up saying various processes have stopped.
I think that if I manually flash the rest of the contents of the zip folder it will work, but there are a lot of files and I'm not sure which partition to flash them too, or which one's are needed. Does anyone know how to manually do what the flash-all.bat script does? Flashing bootloader, radio, system, and boot are not enough it seems. If you read the script it's just doing a 'fastboot -w update' on the zip file.
I hope what I'm saying makes sense. Thanks.

Did you try flashing the stock boot.img to both slots before going back to stock?
fastboot flash boot_a boot.img
fastboot flash boot_b boot.img
This is what chainfire recommended in his supersu post when he was talking about flashing twrp. Maybe try doing that and then try using the flashall script. Also make sure your download is not corrupt or something. https://plus.google.com/+Chainfire/posts/CBL8pnKtA8F

Evo_Shift said:
Did you try flashing the stock boot.img to both partitions before going back to stock?
fastboot flash boot_a boot.img
fastboot flash boot_b boot.img
This is what chainfire recommended in his supersu post when he was talking about flashing twrp. Maybe try doing that and then try using the flashall script. Also make sure you download is not corrupt or something.
Click to expand...
Click to collapse
No, I didn't do any flashing myself before going back to stock. I selected the "Full unroot" option in SuperSU, based on the first result when googling "unroot pixel".
As soon as I did that I was stuck in a bootloop and I tried to restore the factory images according to the google webpage, but that's when I get the error.
Doing what you said doesn't work either, not even redownloading the image.

Actually, now it's worse. When I select recovery from fastboot menu it shows "No command" with a broken android. So twrp is gone now too.
If anyone can help me at all, that would be amazing, thanks.

UPDATE: So I extracted boot and system from the zip file and manually flashed those. It boots now, but when it does it says there are errors with the device and to contact the manufacturer, also a lot of dialog boxes pop up saying various processes have stopped.
I think that if I manually flash the rest of the contents of the zip folder it will work, but there are a lot of files and I'm not sure which partition to flash them too, or which one's are needed. Does anyone know how to manually do what the flash-all.bat script does? Flashing bootloader, radio, system, and boot are not enough it seems. If you read the script it's just doing a 'fastboot -w update' on the zip file.
I hope what I'm saying makes sense. Thanks.

th3p3r50n said:
Actually, now it's worse. When I select recovery from fastboot menu it shows "No command" with a broken android. So twrp is gone now too.
If anyone can help me at all, that would be amazing, thanks.
Click to expand...
Click to collapse
This happened to me too. That's my current situation. Have adb and fastboot still but can't figure out what steps to fix it.

I think you should focus on why the flash all didn't work. Do you have the latest fastboot? Did you check the md5 of the downloaded rom image? What OS it's your computer running?

How do we verify latest fastboot. I thought that was my issue but don't see where this can be found. I have latest minimal adb and fastboot installed.

fracman said:
How do we verify latest fastboot. I thought that was my issue but don't see where this can be found. I have latest minimal adb and fastboot installed.
Click to expand...
Click to collapse
The commands <adb version> and <fastboot --version> seem to return version numbers. My setup returns:
Android Debug Bridge version 1.0.36
Revision fd9e4d07b0f5-android
and
fastboot version fd9e4d07b0f5-android
respectively

Thank you cntryby429. I assumed I was using the latest versions because I had just installed them through the SDK Manager, turns out I was using version 1.0.32. I found the latest version of Minimal ADB and Fastboot and the flash-all script worked fine. I still had a few issues though, so I did a factory reset and then ran the flash-all script again. Now everything works perfectly again. Thanks so much!

Mi mix 3 Global ROM bootloop

I'll start by apologizing if this has been solved elsewhere I have searched but found no answers.
I have the global variant and was rooted with twrp. I wanted the ota update so I unrooted and updated. Today I had some time so I flashed twrp wiped and entered bootloop. I attempted a full factory reset through twrp but still bootlooped. I have fastboot rom and have attempted to use miflash to fix it but get the "cannot found lock.bat" error though when first starting miflash I get the "can't find flash script" error. The drivers are properly installed yet the error persists. I cannot get adb to sideload which is, I'm guessing because of the wipe removing debugging mode? Is there any way to get the ROM image to the phone(I tried adb push command but says no device. Yet flashing recovery works so I know it's connected and recognized) so I can flash it via TWRP or the stock recovery img to flash and work from there? I'm kind of at a loss here. Am I now the proud owner of a very neat paper weight? I seriously hope not as I'm not exactly made of money and I've only owned the phone for a couple months.
Any and all help is greatly appreciated.

Update
I have managed to get adb push to start sending global v10.2.2.0 to the root folder. I'm hoping this will allow me to flash from twrp.
Mota420 said:
I'll start by apologizing if this has been solved elsewhere I have searched but found no answers.
I have the global variant and was rooted with twrp. I wanted the ota update so I unrooted and updated. Today I had some time so I flashed twrp wiped and entered bootloop. I attempted a full factory reset through twrp but still bootlooped. I have fastboot rom and have attempted to use miflash to fix it but get the "cannot found lock.bat" error though when first starting miflash I get the "can't find flash script" error. The drivers are properly installed yet the error persists. I cannot get adb to sideload which is, I'm guessing because of the wipe removing debugging mode? Is there any way to get the ROM image to the phone(I tried adb push command but says no device. Yet flashing recovery works so I know it's connected and recognized) so I can flash it via TWRP or the stock recovery img to flash and work from there? I'm kind of at a loss here. Am I now the proud owner of a very neat paper weight? I seriously hope not as I'm not exactly made of money and I've only owned the phone for a couple months.
Any and all help is greatly appreciated.
Click to expand...
Click to collapse

Update 2 phone working but still confused.
Pushing the ROM via ADB did indeed allow me to flash from twrp and restore the phone. My question now is why did it happen? Is the new OTA MIUI 10.3... update incompatible with twrp or did something anomalous happen with the flash? I flashed exactly the same method I used with the 10.2.2 ROM a few weeks ago....

OTA's should only be used when completely stock! Even though you uninstalled root, there were still system modifications that more than likely caused your issues. The fastboot version of the firmware is different than the TWRP image. You can not flash a TWRP image via fastboot, hence the missing scripts and bat files. If you had actually downloaded the fastboot image, you would have had a flash_all.bat file that would have returned your device completely to stock with a single run of that file.

Thanks for the reply and information. I actually expected my issues to begin upon installing the ota update and was quite surprised that it updated without error. What confuses me is how flashing twrp after the update caused the issues. I went through the normal process when flashing twrp and still ended up bootlooped. I made the mistake of thinking boot.img was the old stock recovery i renamed when i first rooted and flashing that as recovery. Obviously this was not the recovery file but fastboot. It was then that panic mode kicked in and things went from bad to worse. I formatted planning to flash the stock rom via adb which didn't work. Given that I never touched the fastboot image on the phone I'm confused on how the bat files and scripts weren't found.
I'll admit I'm not extremely well versed in this area.
Is it possible that the ota update contained different bat files and scripts than the previous rom had? Which would cause miflash to not recognize them when attempting to flash an older rom? I'm sorry if my questions are ignorant lol. I'm a process guy and a troubleshooter by nature which means even though I've resolved the issue, I need to figure out what caused it.
Would flashing fastboot to the phone as the recovery image have screwed up the bat and scripts? Having two instances of boot.img on the partition messed it up maybe? Was it the formatting even though I was still able to boot into fastboot after? Or was it something that happened during the unrooting and updating that messed it up and it didn't manifest until I flashed twrp? Like I said the update worked fine and the phone was fully functional until I tried to reroot.
Thanks again for taking the time to help. It's definitely appreciated.

Mota420 said:
Thanks for the reply and information. I actually expected my issues to begin upon installing the ota update and was quite surprised that it updated without error. What confuses me is how flashing twrp after the update caused the issues. I went through the normal process when flashing twrp and still ended up bootlooped. I made the mistake of thinking boot.img was the old stock recovery i renamed when i first rooted and flashing that as recovery. Obviously this was not the recovery file but fastboot. It was then that panic mode kicked in and things went from bad to worse. I formatted planning to flash the stock rom via adb which didn't work. Given that I never touched the fastboot image on the phone I'm confused on how the bat files and scripts weren't found.
I'll admit I'm not extremely well versed in this area.
Is it possible that the ota update contained different bat files and scripts than the previous rom had? Which would cause miflash to not recognize them when attempting to flash an older rom? I'm sorry if my questions are ignorant lol. I'm a process guy and a troubleshooter by nature which means even though I've resolved the issue, I need to figure out what caused it.
Would flashing fastboot to the phone as the recovery image have screwed up the bat and scripts? Having two instances of boot.img on the partition messed it up maybe? Was it the formatting even though I was still able to boot into fastboot after? Or was it something that happened during the unrooting and updating that messed it up and it didn't manifest until I flashed twrp? Like I said the update worked fine and the phone was fully functional until I tried to reroot.
Thanks again for taking the time to help. It's definitely appreciated.
Click to expand...
Click to collapse
OTA's are not a complete image. It is a partial update that only replaces what it has to replace. If MiFlash dis not recognize the image, it was either the wrong image or a corrupt image.
Sometimes updates to the system and recovery partitions fix exploits that things like root and TWRP take advantage of.
Fastboot isn't something you flash to the phone. It is a command line used to flash a dull factory image to the device properly. You do not need MiFlash to flash a fastboot factory image. All you do is extract the full image to your ADB folder unless it is system wide, boot your device into the bootloader, connect ir to your PC, and run the flash_all.bat command contained in the folder you extracted. A command prompt window will open, everything will complete after about a few minutes the window will close, and your phone will reboot.

So the "fastboot" rom is a rom designed to be flashed using fastboot? The miflash error was given because the rom I was trying to flash was corrupted. That makes sense as I'd never known of a fastboot rom before. But it has been a few years since I rooted and romd my phone. I always did the typical flash from the rom image from twrp. I'm still not sure how I got myself in a boot loop unless when I wiped after flashing twrp I accidentally selected another option that erased more than I wanted.. Which makes perfect sense. I knew it had to be an ID10T error lol.
Thanks for the explanation.

System partition not found

This is just a quick post to document an issue & solution I had when updating my Pixel 5 to the latest OTA and trying to re-root.
I had installed the latest OTA via system update, then downloaded the matching image from the Factory Images Page, pulled the boot.img out of there, transferred it to my Pixel, and used Magisk to patch it.
I then transferred it back to my computer and tried to flash it to the phone using fastboot flash boot boot_patched.img. At this point the phone entered a bootloop.
I booted into the bootloader menu and tried to flash the latest clean system image (without wiping data), when I ran into the following system errors causing the flash to fail when trying to flash the system partition:
Code:
FAILED (remote: Partition system not found)
(and later...)
FAILED (remote: Partition should be flashed in fastbootd)
I initially panicked but the way around this should you ever encounter these errors, is to literally just update your fastboot and adb binaries on your computer. You can grab the latest standalone binaries from here, and throw them where your PATH will find them. After running the flash script again, it worked without a hitch and my phone was up and running without issue.

CarteNoir said:
I initially panicked but the way around this should you ever encounter these errors, is to literally just update your fastboot and adb binaries on your computer. You can grab the latest standalone binaries from here, and throw them where your PATH will find them. After running the flash script again, it worked without a hitch and my phone was up and running without issue.
Click to expand...
Click to collapse
Just wanted to say thanks. I had this issue with my Pixel 6, and updating my ancient ADB/fastboot binaries resolved it!

It's always important to ensure your platform tools are updated! Glad you figured this out!

Thank you!
I had the latest universal ADB/Fastboot drivers installed... but this didn't make a difference
I downloaded latest platform tools, ran the flash-all.bat from there and BOOM, sorted
Thank you so much

Thank you so much. Can't believe the solution is so simple lol