Hello all, I am still fairly new to the root/Android scene and I've run into a problem.
Firstly, my Nexus' bootloader is unlocked and I'm running and older Franco.Kernel (4.0.1 and 1.4GHZ OC). Now, the problem is, my phone has notified me that a newer OS version is available. When I go to install it, the phone reboots but right after - the little Droid appears with a red caution sign and the phone stays that way until the battery is pulled.
What am I missing here? Any help is greatly appreciated.
P.S. I'm a n00b.
Try relocking bootloader then installing update. And then unlock again.
Sent from my Galaxy Nexus using Tapatalk
anton2009 said:
Try relocking bootloader then installing update. And then unlock again.
Sent from my Galaxy Nexus using Tapatalk
Click to expand...
Click to collapse
No... He's not going to be able to update just because he locked the bootloader.
---------- Post added at 08:46 PM ---------- Previous post was at 08:45 PM ----------
Redefined81 said:
Hello all, I am still fairly new to the root/Android scene and I've run into a problem.
Firstly, my Nexus' bootloader is unlocked and I'm running and older Franco.Kernel (4.0.1 and 1.4GHZ OC). Now, the problem is, my phone has notified me that a newer OS version is available. When I go to install it, the phone reboots but right after - the little Droid appears with a red caution sign and the phone stays that way until the battery is pulled.
What am I missing here? Any help is greatly appreciated.
P.S. I'm a n00b.
Click to expand...
Click to collapse
In order to properly take an OTA and have it install you're going to have to be on the stock ROM, recovery, radios, everything. You can be unlocked and rooted, but you can't have changed anything else. Because you've flashed another kernel, you're probably going to have to flash the update manually.
heifica 798.
martonikaj said:
No... He's not going to be able to update just because he locked the bootloader.
---------- Post added at 08:46 PM ---------- Previous post was at 08:45 PM ----------
In order to properly take an OTA and have it install you're going to have to be on the stock ROM, recovery, radios, everything. You can be unlocked and rooted, but you can't have changed anything else. Because you've flashed another kernel, you're probably going to have to flash the update manually.
Click to expand...
Click to collapse
Thanks! How and where would I go about doing this?
Sorry, but remember, I'm still really new to all of this.
Redefined81 said:
Thanks! How and where would I go about doing this?
Sorry, but remember, I'm still really new to all of this.
Click to expand...
Click to collapse
I'd pass that question to someone more knowledgeable than I on the subject. I wouldn't wanna give you improper guidance. Not sure how your custom kernel comes in to play when flashing.
All I know is you won't be able to take the regular OTA in your current state.
Here is your info on how to get back to stock.
http://forum.xda-developers.com/showthread.php?t=1366806
El Daddy said:
Here is your info on how to get back to stock.
http://forum.xda-developers.com/showthread.php?t=1366806
Click to expand...
Click to collapse
Is this going to un-root and/or lock my bootloader again?
You should have learned how to go back to stock before flashing anything...
El Daddy said:
Here is your info on how to get back to stock.
http://forum.xda-developers.com/showthread.php?t=1366806
Click to expand...
Click to collapse
That is overkill. Just go here: http://code.google.com/android/nexus/images.html and download the version of Android you are using. Extract the boot.img file from within, and flash that with fastboot. Now you are back to the stock kernel, and the update will install automatically (assuming of course that you did not make other changes).
EDIT: You will not lose root, your bootloader will still be unlocked, and all of your data/settings will still be there.
efrant said:
That is overkill. Just go here: http://code.google.com/android/nexus/images.html and download the version of Android you are using. Extract the boot.img file from within, and flash that with fastboot. Now you are back to the stock kernel, and the update will install automatically (assuming of course that you did not make other changes).
EDIT: You will not lose root, your bootloader will still be unlocked, and all of your data/settings will still be there.
Click to expand...
Click to collapse
Thank you so much!
I know I may seem a tad annoying, but I just don't want to mess up my phone, lol!
How do I go about installing this?
I DL Fastboot & it's drivers. Extract the IMG (just so you know, I'm currently yakjuxx, not yakju - does that matter?) to the same directory as Fastboot then enter my phone into Fastboot mode. The thing is, I'm unfamiliar with the command prompts to get it going. I'll be doing it on Windows 7. Help would be appreciated!.
I know I've asked a lot, and I thank you.
Redefined81 said:
Thank you so much!
I know I may seem a tad annoying, but I just don't want to mess up my phone, lol!
How do I go about installing this?
I DL Fastboot & it's drivers. Extract the IMG (just so you know, I'm currently yakjuxx, not yakju - does that matter?) to the same directory as Fastboot then enter my phone into Fastboot mode. The thing is, I'm unfamiliar with the command prompts to get it going. I'll be doing it on Windows 7. Help would be appreciated!.
I know I've asked a lot, and I thank you.
Click to expand...
Click to collapse
I'm not sure it matters if you are yakju or yakjuux (as I think all the stock GSM kernels for ITFL41F are the same), but just to be sure, go here and download my nandroid back up of yakjuux ITL41F. In the archive, you will find a boot.img file (which is the file you need). Extract it.
All you have to do it put the boot.img file in the same directory as your fastboot.exe file, reboot your device into fastboot mode, and plug it into your PC. Open a command prompt in that directory and type fastboot devices to make sure you PC recognizes your device. Then type fastboot flash boot boot.img
Done.
Now, obviously this assumes that you already have the drivers set up properly...
efrant said:
I'm not sure it matters if you are yakju or yakjuux (as I think all the stock GSM kernels for ITFL41F are the same), but just to be sure, go here and download my nandroid back up of yakjuux ITL41F. In the archive, you will find a boot.img file (which is the file you need). Extract it.
All you have to do it put the boot.img file in the same directory as your fastboot.exe file, reboot your device into fastboot mode, and plug it into your PC. Open a command prompt in that directory and type fastboot devices to make sure you PC recognizes your device. Then type fastboot flash boot boot.img
Done.
Now, obviously this assumes that you already have the drivers set up properly...
Click to expand...
Click to collapse
Fastboot can flash boot.imgs, awesome, I likely would've been a muppet and made a CWM zip. I learn something new that I love about my GN every day.
mudferret said:
Fastboot can flash boot.imgs, awesome, I likely would've been a muppet and made a CWM zip. I learn something new that I love about my GN every day.
Click to expand...
Click to collapse
The "fastboot flash" command is specifically for flashing full images to partitions on the device, e.g., system, userdata, boot, recovery, bootloader, radio, splash1, etc.
Related
I got the OTA update downloaded but could not install.Read somewhere if you have CWM ota update wont work.So i have downloaded the stock image for 4.0.2 and its in .tgz format
How can i upgrade to 4.0.2 using CWM or odin and not loose my data and setup.?
Please advice
Hussainally said:
I got the OTA update downloaded but could not install.Read somewhere if you have CWM ota update wont work.So i have downloaded the stock image for 4.0.2 and its in .tgz format
How can i upgrade to 4.0.2 using CWM or odin and not loose my data and setup.?
Please advice
Click to expand...
Click to collapse
Check out Chainfire's thread. He posted a no-wipe version flashable through Odin. Follow the instructions there and make sure you download the correct version for your phone (GSM/LTE)!
mbroeders said:
Check out Chainfire's thread. He posted a no-wipe version flashable through Odin. Follow the instructions there and make sure you download the correct version for your phone (GSM/LTE)!
Click to expand...
Click to collapse
hi thanks for your reply.His update you will not be updating to new bootloader am i right?
Hussainally said:
hi thanks for your reply.His update you will not be updating to new bootloader am i right?
Click to expand...
Click to collapse
Indeed, it won't touch your data, recovery or bootloader. They're all safe afaik
mbroeders said:
Indeed, it won't touch your data, recovery or bootloader. They're all safe afaik
Click to expand...
Click to collapse
thats the prob...4.0,2 has a new bootloader right?i want that.
ok what if i just want to install fresh clean stock 4.0.2...how do i do that?
Hussainally said:
thats the prob...4.0,2 has a new bootloader right?i want that.
ok what if i just want to install fresh clean stock 4.0.2...how do i do that?
Click to expand...
Click to collapse
If you want fresh clean stock then you can do two things:
1) on linux, extract the contents of the tgz package and use the sh script inside to flash.
2) since that's not possible on windows, you could use Chainfire's odin files first and next manually flash the bootloader and/or radioimage with fastboot. You can extract the bootloader and radio yourself from the tgz/tar package or look for them in the development section, someone posted them there.
mbroeders said:
If you want fresh clean stock then you can do two things:
1) on linux, extract the contents of the tgz package and use the sh script inside to flash.
2) since that's not possible on windows, you could use Chainfire's odin files first and next manually flash the bootloader and/or radioimage with fastboot. You can extract the bootloader and radio yourself from the tgz/tar package or look for them in the development section, someone posted them there.
Click to expand...
Click to collapse
You can flash it in windows using fastboot, you don't need to use odin for anything:
Extract the factory images
fastboot flash bootloader bootloader-maguro-primekk15.img
fastboot flash radio radio-maguro-i9250xxkk6.img
fastboot reboot-bootloader
fastboot update image-yakju-icl53f.zip
Thanks everyone...will give it a go.....Cheers
krohnjw said:
You can flash it in windows using fastboot, you don't need to use odin for anything:
Extract the factory images
fastboot flash bootloader bootloader-maguro-primekk15.img
fastboot flash radio radio-maguro-i9250xxkk6.img
fastboot reboot-bootloader
fastboot update image-yakju-icl53f.zip
Click to expand...
Click to collapse
Thanks. Just checking, if I would like to do this, but without a wipe, can't i just flash the bootloader and radio like you suggested, and then use Odin to flash Chainfire's no-wipe version right? Just so i fully understand, thanks!
mbroeders said:
Thanks. Just checking, if I would like to do this, but without a wipe, can't i just flash the bootloader and radio like you suggested, and then use Odin to flash Chainfire's no-wipe version right? Just so i fully understand, thanks!
Click to expand...
Click to collapse
What I posted does not wipe. There's little reason to use Odin. Using Odin you *can* easily brick your device (Ask all of the folks in the Nexus S forums that used Odin to flash the wrong package for their device).
fastboot update image-yakju-icl53f.zip <-- This does not wipe
fastboot -w update image-yakju-icl53f.zip <-- This wipes (-w wipes)
mbroeders said:
Thanks. Just checking, if I would like to do this, but without a wipe, can't i just flash the bootloader and radio like you suggested, and then use Odin to flash Chainfire's no-wipe version right? Just so i fully understand, thanks!
Click to expand...
Click to collapse
ok guys please bare with me here,Never done this before.when i run command adb-windows.exe,it works,thenwhen i run fastboot-windows.exe devices it works
then when i go to bootloader more...the green android with word start on top when i type fastboot flash bootloader bootloader-maguro-primekk15.img,nothing happens and it says on the phone bad command or something
please advice
Nevermind guys...I DID IT.Thanks so much...excellent guide
Hussainally said:
ok guys please bare with me here,Never done this before.when i run command adb-windows.exe,it works,thenwhen i run fastboot-windows.exe devices it works
then when i go to bootloader more...the green android with word start on top when i type fastboot flash bootloader bootloader-maguro-primekk15.img,nothing happens and it says on the phone bad command or something
please advice
ok i lost root after flashing to 4.0.2 using this guide and re did install superboot windows .bat and now the phone rebooted and its stuck on google screen...how long do i wait and what do i do next???
Click to expand...
Click to collapse
Hussainally said:
Hussainally said:
ok guys please bare with me here,Never done this before.when i run command adb-windows.exe,it works,thenwhen i run fastboot-windows.exe devices it works
then when i go to bootloader more...the green android with word start on top when i type fastboot flash bootloader bootloader-maguro-primekk15.img,nothing happens and it says on the phone bad command or something
please advice
ok i lost root after flashing to 4.0.2 using this guide and re did install superboot windows .bat and now the phone rebooted and its stuck on google screen...how long do i wait and what do i do next???
Click to expand...
Click to collapse
Give it some time, if it doesn't boot all is not lost. Pull the battery and restart.
Click to expand...
Click to collapse
ok..fingers crossed...how much time?
Halleluyah....Praise the lord....thanks a million...All is well
Hussainally said:
ok..fingers crossed...how much time?
Click to expand...
Click to collapse
I think that it depends on how many apps do you have...usually 2-3 minutes max. !
I have flash an aosp rom but keep seeing signal drops, so I want to revert to stock.
Can anyone give me the link?
did you create a nandroid backup ?
when you flashed a rom did it change your baseband you could probably just change the baseband there are a number available and you will probably get better reception on a different one
Goat_For_Sale said:
did you create a nandroid backup ?
when you flashed a rom did it change your baseband you could probably just change the baseband there are a number available and you will probably get better reception on a different one
Click to expand...
Click to collapse
I am too stupid that I didn't nandroid backup it.
Luckily, I flashed a newer radio.img, will see whether keep dropping.
Booker-T said:
I am too stupid that I didn't nandroid backup it.
Luckily, I flashed a newer radio.img, will see whether keep dropping.
Click to expand...
Click to collapse
yea i would spend a day or two on each radio and try to do "normal use" and see what works best for your area
these official factory images of any use to you?
http://code.google.com/intl/nl-NL/android/nexus/images.html
Could someone with jakjuzs please provide a stock recovery?
Because of a careeless mistake, I didn't create an image of the recovery partition before I flashed it to yakju.
I have images for everything (I hope) except the recovery.
I can go back and forth between yakju and yakjuzs but not sure if there is a difference between the two recoveries?
I have non-rooted zs Nexus and planed to upgrade the rom from yakjuzs to yakju.
However, my concerns is just in case if I need to bring back my phone to *** for maintenance, I have to flash it back to original non-rooted yakjuzs..etc.
Would anyone have any ideas for me to backup the current ROM first? Hence I can also share the ROM to ALUOp.
There wont be a stock image for yakjuzs. Stock image support is only for yakju and mysid devices.
yakjuzs is supported by Samsung. You should use the yakju one as its identical to yakjuzs.
Sent from my Galaxy Nexus using xda premium
zephiK said:
There wont be a stock image for yakjuzs. Stock image support is only for yakju and mysid devices.
yakjuzs is supported by Samsung. You should use the yakju one as its identical to yakjuzs.
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
We are looking for the yakjuzs rom because in case for the warranty repair.
I have unlocked non-rooted yakjuzs-build phone. If you tell me how to do this backup, I'll post it
skeve said:
I have unlocked non-rooted yakjuzs-build phone. If you tell me how to do this backup, I'll post it
Click to expand...
Click to collapse
http://forum.xda-developers.com/wiki/HTC_Eris/How-To/Nandroid
Will this help? i am currently looking for yakjuzs nandroid backup image as well...
tinyau09 said:
http://forum.xda-developers.com/wiki/HTC_Eris/How-To/Nandroid
Will this help? i am currently looking for yakjuzs nandroid backup image as well...
Click to expand...
Click to collapse
I don't think so - the prerequisites are rooted phone and custom recovery... which kills the idea of getting the original recovery
Anyway, I couldn't wait and changed the firmware to yakju
anyone locate the original yakjuzs rom yet
anyone locate the original yakjuzs rom yet?
I am looking for this so I can return my phone for warranty
Sorry for necroing but I would like to know if anyone has the factory image as From Samsung's hk facebook page they are finally going to push 4.04 to yakjuzs and I was hoping someone could post the files.
Cheers.
skeve said:
I have unlocked non-rooted yakjuzs-build phone. If you tell me how to do this backup, I'll post it
Click to expand...
Click to collapse
Since your device is unlocked, I'm going to assume you have the drivers set up properly, and you have a copy of fastboot and adb somewhere on your PC. If this is correct, here is what you have to do:
1) Download CWM from here, save it to the same directory as your fastboot.exe file, and rename it to cwm.img
2) Reboot your device into fastboot mode (by turning it off, and then holding volume up and volume down, press and hold the power button.
3) Plug your phone into your computer.
4) Open a command prompt in the same directory mentioned above and type: fastboot boot cwm.img
5) Navigate the menus in CWM on your device to backup.
6) Get the backup off your device by typing: adb pull /sdcard/clockworkmod/backup
efrant said:
Since your device is unlocked, I'm going to assume you have the drivers set up properly, and you have a copy of fastboot and adb somewhere on your PC. If this is correct, here is what you have to do:
1) Download CWM from here, save it to the same directory as your fastboot.exe file, and rename it to cwm.img
2) Reboot your device into fastboot mode (by turning it off, and then holding volume up and volume down, press and hold the power button.
3) Plug your phone into your computer.
4) Open a command prompt in the same directory mentioned above and type: fastboot boot cwm.img
5) Navigate the menus in CWM on your device to backup.
6) Get the backup off your device by typing: adb pull /sdcard/clockworkmod/backup
Click to expand...
Click to collapse
https://docs.google.com/open?id=0B3P9aOVwt43cRHBkUWEyNFNlRk0
IMM76K.ZSLE2 backed up using CWM
Enjoy.
i am unlocked and rooted but im just looking for the latest stock ICS android build (not interested in roms atm) for the galaxy nexus. im using a Fido Galaxy Nexus and its still on 4.0.1. Is 4.0.1 the lasted version for gsm nexus?
4.0.2 is the latest stock yakju build. You can get the stock image from Google:
http://code.google.com/android/nexus/images.html
thanks i appreciated. here's the cwm for those who are interested http://forum.xda-developers.com/showthread.php?t=1398800
edit: nevermind its not a cwm zip
Much safer to flash the images Google give you as opposed to something someone could've easily tinkered with
EddyOS said:
Much safer to flash the images Google give you as opposed to something someone could've easily tinkered with
Click to expand...
Click to collapse
how do i flash that image, in fastboot? do you know what command i need to use?
edit: nevermind i just noticed the commands in flash all script that was included.
Search 'Restore Galaxy Nexus V2' on here for a full guide
neotekz said:
how do i flash that image, in fastboot? do you know what command i need to use?
edit: nevermind i just noticed the commands in flash all script that was included.
Click to expand...
Click to collapse
Here is a link the the guide using fastboot command:
http://forum.xda-developers.com/showthread.php?t=1366806
Extract the components of the image and flash them like so:
Fastboot flash recovery recovery.img
Fastboot flash boot boot.img
And follow that guideline for whatever else is in there (not entirely sure myself )
I don't think order matters but I could be wrong.
joshnichols189 said:
Extract the components of the image and flash them like so:
Fastboot flash recovery recovery.img
Fastboot flash boot boot.img
And follow that guideline for whatever else is in there (not entirely sure myself )
I don't think order matters but I could be wrong.
Click to expand...
Click to collapse
follow the order presented on flash-all.sh, it matters.
bk201doesntexist said:
follow the order presented on flash-all.sh, it matters.
Click to expand...
Click to collapse
yup thats what i did and it worked without a glitch. when are you americans getting the gsm GN? hopefully 4.0.3/4 gsm will be out soon
Or just buy clockworkmod, download your image to the phone and flash through the app. Its very simple. Backup your device before
this is the stock 4.0.2 rooted, busybox and deodexed.
just rename flash-all.sh to flash-all.bat
Sent from my Galaxy Nexus
Hello, i want to change yakjuxw to yajku.
I got Galaxy Nexus Toolkit V7.3.
Which options should i use?
3.Unlock bootloader and then 9. To download and flash factory ROM
or something else except that?
Here is the guide that I used.
http://leemn.wordpress.com/2012/02/01/galaxy-nexus-upgrade-to-official-roms-yakju-build/
Scroll down to where it starts talking about Fastboot. The guide was intended to update to 4.02, but it still applies. The file names will just be a bit different.
Shows you every step, every adb / fastboot command required.
Here's where you get the image you need.
https://developers.google.com/android/nexus/images#yakju
You learn more this way. Better than one click methods.
any possibility of hard brick?
can i flash official 4.0.4 or even 4.1.1 over 4.0.2 on phone with this method?
the guide you gave me
says to flash bootloader-maguro-primekk15.img but i only have
bootloader-maguro-primela03.img - another ending, i think thats because i downloaded other rom(only 4.0.4 is on google site),
can i flash this over 4.0.2 on phone? do i have to change other names accordingly?
b_android said:
Hello, i want to change yakjuxw to yajku.
I got Galaxy Nexus Toolkit V7.3.
Which options should i use?
3.Unlock bootloader and then 9. To download and flash factory ROM
or something else except that?
Click to expand...
Click to collapse
Yes thats the only thing you need to do, to get yakju on you phone
b_android said:
the guide you gave me
says to flash bootloader-maguro-primekk15.img but i only have
bootloader-maguro-primela03.img - another ending, i think thats because i downloaded other rom(only 4.0.4 is on google site),
can i flash this over 4.0.2 on phone? do i have to change other names accordingly?
Click to expand...
Click to collapse
Like I said in my post , the file names will be different because that guide is for flashing 4.02. It's just that the same rules apply.
Aslong as you have the new radio, bootloader etc you will be fine. Just type the commands to suit the different file names.
Arthur Hucksake said:
Like I said in my post , the file names will be different because that guide is for flashing 4.02. It's just that the same rules apply.
Aslong as you have the new radio, bootloader etc you will be fine. Just type the commands to suit the different file names.
Click to expand...
Click to collapse
the easy way is to use toolkit
Arthur Hucksake said:
Like I said in my post , the file names will be different because that guide is for flashing 4.02. It's just that the same rules apply.
Aslong as you have the new radio, bootloader etc you will be fine. Just type the commands to suit the different file names.
Click to expand...
Click to collapse
Okay thank you, and about drivers - i don't have to instal them since i have installed and used Android SDK(it contains drivers, right?)
knudsen81 said:
the easy way is to use toolkit
Click to expand...
Click to collapse
But you don't really learn anything with a toolkit
Matt08642 said:
But you don't really learn anything with a toolkit
Click to expand...
Click to collapse
No whats right, i know have to use cmd to do it, but for a newbie toolkit is the best way to do it
knudsen81 said:
No whats right, i know have to use cmd to do it, but for a newbie toolkit is the best way to do it
Click to expand...
Click to collapse
I tend to feel the opposite. For someone new to doing all this (very much like I was a week ago), it's best to research and do it manually and learn exactly what's happening each step of the way.
Hello Everyone. I'm trying to downgrade the software on my Asus Zenfone 2 to version 2.19.40.20 (currently 2.19.40.20) so I can unlock my bootloader. I've heard that the way to do this is following rooting procedure 1 from the main information thread but flashing the version of the files that you want your system to be. However when I download the zip it has the system.img file broken up in some weird way (apparently you need a tool called WinRar to put it back together again but I really don't want to have to go buy a piece of software I'm only gonna need once). Does anyone know how to put the files back together again, have a put together 2.19.40.20 system.img I can use or have some alternative solution to my problem. I'm currently using a Linux system too so if at all possible I would like for any software to be compatible with Linux. If anyone has any insight I would be highly appreciative.
Don't try to flash selectively, as that is very likely to brick your phone. What you want is the correct full ROM package containing a system.img, boot.img/kernel, fastboot (droidboot.img IIRC), IFWI.zip, and some other important partitions whose names escape me. Don't try to extract parts of it (e.g. just the system.img, boot.img, or bootloader), because the components appear to be interdependent. In particular, flashing the wrong version of the bootloader without flashing the corresponding kernel/system image will more than likely brick it. You should be able to supply the full ROM to fastboot (e.g. fastboot update <package_file>). Double check everything and back up before you proceed! @Tuanies should have some pointers for you in case I missed anything, and I would wait to hear from him before you try this.
WinRAR is free. It's a very small program that takes seconds to download and install. It is very simple to put the system image components back together with WinRAR and then you will have that file plus the other three you need. Please try it, I'm sure you'll manage it.
All I suggest is to get the full firmware of 2.19.40.20 and flash the images one by one, and sideload the firmware using adb...
Hope this helps
Good luck.
I'd just download the full package from that's ~1GB and sideload that via recovery in its entirety. If this is too complicated, I'd advise against attempting it.
Seriously it is just about writing 3 lines on adb... Not that hard
Sent from my ASUS_Z008D using Tapatalk
I did finally manage to get WinRar working. I had to go install it on my brother's computer. After I had the files to flash I had no trouble.
This seems like a good place to ask this I was on .22 and tried unlocking boot loader did not seem to work so I went back into my 2.19 folder and flashed back to 2.19 but was still unable to unlock though it appears possibly unlocked on boot loader shows bootloader unk and question marks on last 2 entries, but apparently I am unable to flash over the bootloader in fastboot it says fail cmd err can anyone tell me what that means? And how to get around it, tried flashing non tethered twrp says it wrote it but won't boot to it
Sent from my ASUS_Z00AD using Tapatalk
You must have done something wrong. I had the two question marks before I unlocked mine. When your bootloader is unlocked your boot screen will be white. If you're not sure what I'm talking about then you're not unlocked.
robopilot99 said:
You must have done something wrong. I had the two question marks before I unlocked mine. When your bootloader is unlocked your boot screen will be white. If you're not sure what I'm talking about then you're not unlocked.
Click to expand...
Click to collapse
Okay so I never have gotten the white boot screen and just not sure where to go from here does not seem to want me to flash a droidboot.img and I cannot seem to figure out how to make it take the img I can go back to 4.19 from 4.22 but from there I have tried using adb and terminal emulator to give the commands and after reboot to bootloader it just sits there, so am on 4.22's bootloader and is that why it won't work and would you suggest to get the bootloader unlocked?
---------- Post added at 06:09 PM ---------- Previous post was at 05:58 PM ----------
jimchee said:
Okay so I never have gotten the white boot screen and just not sure where to go from here does not seem to want me to flash a droidboot.img and I cannot seem to figure out how to make it take the img I can go back to 4.19 from 4.22 but from there I have tried using adb and terminal emulator to give the commands and after reboot to bootloader it just sits there, so am on 4.22's bootloader and is that why it won't work and would you suggest to get the bootloader unlocked?
Click to expand...
Click to collapse
The img's I am flashing are from shakalaka, hope thats spelled right
so in fastboot and using adb i did fastboot flash droidboot droidboot.img (enter)
sending droidboot (14410 kb)
Okay (0.622s)
writing "droidboot"
FAILED < Remote: flash_cmds error !
so this is the answer I am getting when trying to flash droidboot
so any ideas would be great
jimchee said:
Okay so I never have gotten the white boot screen and just not sure where to go from here does not seem to want me to flash a droidboot.img and I cannot seem to figure out how to make it take the img I can go back to 4.19 from 4.22 but from there I have tried using adb and terminal emulator to give the commands and after reboot to bootloader it just sits there, so am on 4.22's bootloader and is that why it won't work and would you suggest to get the bootloader unlocked?
---------- Post added at 06:09 PM ---------- Previous post was at 05:58 PM ----------
The img's I am flashing are from shakalaka, hope thats spelled right
so in fastboot and using adb i did fastboot flash droidboot droidboot.img (enter)
sending droidboot (14410 kb)
Okay (0.622s)
writing "droidboot"
FAILED < Remote: flash_cmds error !
so this is the answer I am getting when trying to flash droidboot
so any ideas would be great
Click to expand...
Click to collapse
I had to flash 4 files as it appears you are trying to do. The error is definitely not good. I'm not sure what it means though. Hopefully someone else knows what to do. I'm pretty sure being on this up to date bootloader is your issue. Did you manage to somehow flash the other 3 files?
robopilot99 said:
I had to flash 4 files as it appears you are trying to do. The error is definitely not good. I'm not sure what it means though. Hopefully someone else knows what to do. I'm pretty sure being on this up to date bootloader is your issue.
Click to expand...
Click to collapse
Yep I figure that might be it, just not sure what to do next, every other file flashes whether I am going up or down thinking of trying to flash older than 19 and then hopefully able to its to 2.19, but hopefully someone knows the proper way
Sent from my ASUS_Z00AD using Tapatalk
The files that I flashed I got from here. Don't know if that's where you are getting yours.
What I did is I downgraded to version Z00A_WW_2.19.40.18 of everything (I was warned about flashing different versions of different things so be careful). I then used the bootloader unlock method detailed in section 5 of the resource thread. I think your problem is that the files you are flashing are not pre-rooted. I used the files from section 3.1, method 1 of the same thread. The system.img was broken up in some strange fashion but I can send you the put together version somehow if you would like.
robopilot99 said:
What I did is I downgraded to version Z00A_WW_2.19.40.18 of everything (I was warned about flashing different versions of different things so be careful). I then used the bootloader unlock method detailed in section 5 of the resource thread. I think your problem is that the files you are flashing are not pre-rooted. I used the files from section 3.1, method 1 of the same thread. The system.img was broken up in some strange fashion but I can send you the put together version somehow if you would like.
Click to expand...
Click to collapse
I am using the pre rooted ones from shakalaka and i can get boot, recovery and system to flash but unable to get droidboot to flash and that is what I can't figure out even when i downgrade with all the other files i can't get bootloader unlocked
I couldn't find the files you were referring too. However I really don't know enough about fastboot to really help you resolve the error message. Hopefully someone a little more experienced will come along soon.
robopilot99 said:
I couldn't find the files you were referring too. However I really don't know enough about fastboot to really help you resolve the error message. Hopefully someone a little more experienced will come along soon.
Click to expand...
Click to collapse
They are the same files that you are using from mega.nz and my fastboot knowledge is not great either, so I'll just wait around and see if anyone with more knowledge can help me out, thanks for yoyr help though it's appreciated
@jimchee you are typing the wrong command to flash droidboot. its "fastboot flash fastboot droidboot.img"
Niropa said:
@jimchee you are typing the wrong command to flash droidboot. its "fastboot flash fastboot droidboot.img"
Click to expand...
Click to collapse
Thanks Niropa, I knew there was reason this works now I really appreciate the help
Just a quick note to let everyone know that everything worked without a hitch now have unlocked bootloader and twrp installed.
Sent from my ASUS_Z00AD using Tapatalk