How to install and use ADB and fastboot - Wileyfox Storm

1.
Connect your Android device to computer via USB.
2.
Ensure USB Debugging mode is ENABLED on Android device.
Settings > About Phone > Build number > Tap it 7 times to become developer;
Settings > Developer Options > USB Debugging.
3.
download adb driver
http://adbdriver.com/downloads/
download Minimal ADB and Fastboot
https://forum.xda-developers.com/showthread.php?t=2317790
4.
unzip adb driver and instal it
http://adbdriver.com/documentation/...river-installer-for-windows-xp-vista-7-8.html
http://adbdriver.com/documentation/how-to-install-adb-driver-on-windows-8-10-x64.html
5.
Extract the Minimal ADB and Fastboot Tool file to your PC
6.
Download your RecoveryFile.img file or full fastboot Rom file
and put under the extracted folder “ Fastboot or Minimal ADB and Fastboot ”
so all files will be in single folder
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
7.
open folder Minimal ADB and Fastboot
in the folder , On your keyboard press SHIFT and right click with your mouse " Shift + right click "
click on " open command window here "
8.
Now type following command
adb fastboot
Unlocking the bootloader
Note: Using the fastboot command
When the fastboot command is used on the Storm, the vendor id command option must be added.
The vendor id for the Storm is 0x2970. For example, fastboot devices, would be fastboot -i 0x2970 devices.
Enable OEM unlock in the Developer options settings on the device.
(Note: Not all devices have this setting, so continue with next step if yours does not.)
Connect the device to the computer through USB.
From a terminal on a computer, type the following to boot the device into fastboot mode:
adb reboot bootloader
Once the device is in fastboot mode, verify your PC sees the device by typing fastboot devices
If you don't see your device serial number, and instead see "<waiting for device>", fastboot is not configured properly on your machine. See fastboot documentation for more info.
If you see "no permissions fastboot", try running fastboot as root.
From the same terminal, type the following command to unlock the bootloader:
fastboot -i 0x2970 oem unlock-go
If the device doesn't automatically reboot, reboot it from the menu. It should now be unlocked.
Since the device resets completely, you will need to re-enable USB debugging on the device to continue.
fastboot reboot
Installing a custom recovery using fastboot
Open a terminal on your PC and reboot the device into fastboot mode by typing
adb reboot bootloader
or by using the hardware key combination for your device while it is powered off.
Once the device is in fastboot mode, verify your PC sees the device by typing
fastboot devices
Flash recovery onto your device by entering the following command:
fastboot flash recovery your_recovery_image.img
where the latter part is the filename of the recovery image.
fastboot reboot
full rom fastboot
adb reboot bootloader
fastboot devices
fastboot flash aboot emmc_appsboot.mbn
fastboot flash abootbak emmc_appsboot.mbn
fastboot erase DDR
fastboot flash sbl1 sbl1.mbn
fastboot flash sbl1bak sbl1.mbn
fastboot flash tz tz.mbn
fastboot flash tzbak tz.mbn
fastboot flash hyp hyp.mbn
fastboot flash hypbak hyp.mbn
fastboot flash rpm rpm.mbn
fastboot flash rpmbak rpm.mbn
fastboot flash modem NON-HLOS.bin
fastboot flash cache cache.img
fastboot erase splash
fastboot flash splash splash.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash userdata userdata.img
fastboot flash boot boot.img
fastboot reboot

Thanks for the great step by step tutorial.
I've tried to instal the Fastboot Image via the above guidem
1. Connect your Android device to computer via USB.
2. Ensure USB Debugging mode is ENABLED on Android device.
3. download adb driver
4. unzip adb driver and instal it
5. Extract the Minimal ADB and Fastboot Tool file to your PC
6. Download your RecoveryFile.img file or full fastboot Rom file and put under the extracted folder “ Fastboot or Minimal ADB and Fastboot ” so all files will be in single folder. (Which I've done with TOS319I Fastboot Image file)
7. open folder Minimal ADB and Fastboot, click on " open command window here "
8. Now type following command
adb fastboot
Unlocking the bootloader
adb reboot bootloader
fastboot reboot
Then, adb reboot bootloader
fastboot devices
*** But when I use the fastboot flash recovery TOS319I.img and to use the downloaded and renamed recover image, it says unable to load file TOS319I.img
Can you please let me know what should I do?
Thanks in advance

sellfy said:
Thanks for the great step by step tutorial.
I've tried to instal the Fastboot Image via the above guidem
1. Connect your Android device to computer via USB.
2. Ensure USB Debugging mode is ENABLED on Android device.
3. download adb driver
4. unzip adb driver and instal it
5. Extract the Minimal ADB and Fastboot Tool file to your PC
6. Download your RecoveryFile.img file or full fastboot Rom file and put under the extracted folder “ Fastboot or Minimal ADB and Fastboot ” so all files will be in single folder. (Which I've done with TOS319I Fastboot Image file)
7. open folder Minimal ADB and Fastboot, click on " open command window here "
8. Now type following command
adb fastboot
Unlocking the bootloader
adb reboot bootloader
fastboot reboot
Then, adb reboot bootloader
fastboot devices
*** But when I use the fastboot flash recovery TOS319I.img and to use the downloaded and renamed recover image, it says unable to load file TOS319I.img
Can you please let me know what should I do?
Thanks in advance
Click to expand...
Click to collapse
i know that you should use cyanogen os version rom of wileyfox storm (FIRST)
then you can flash custom rom or upgrade to official android 7 rom
that means , first you should downgrade to cyanogen 13

Again bootloop
ghertas said:
1.
Connect your Android device to computer via USB.
2.
Ensure USB Debugging mode is ENABLED on Android device.
Settings > About Phone > Build number > Tap it 7 times to become developer;
Settings > Developer Options > USB Debugging.
3.
download adb driver
http://adbdriver.com/downloads/
download Minimal ADB and Fastboot
https://forum.xda-developers.com/showthread.php?t=2317790
4.
unzip adb driver and instal it
http://adbdriver.com/documentation/...river-installer-for-windows-xp-vista-7-8.html
http://adbdriver.com/documentation/how-to-install-adb-driver-on-windows-8-10-x64.html
5.
Extract the Minimal ADB and Fastboot Tool file to your PC
6.
Download your RecoveryFile.img file or full fastboot Rom file
and put under the extracted folder “ Fastboot or Minimal ADB and Fastboot ”
so all files will be in single folder
7.
open folder Minimal ADB and Fastboot
in the folder , On your keyboard press SHIFT and right click with your mouse " Shift + right click "
click on " open command window here "
8.
Now type following command
adb fastboot
Unlocking the bootloader
Note: Using the fastboot command
When the fastboot command is used on the Storm, the vendor id command option must be added.
The vendor id for the Storm is 0x2970. For example, fastboot devices, would be fastboot -i 0x2970 devices.
Enable OEM unlock in the Developer options settings on the device.
(Note: Not all devices have this setting, so continue with next step if yours does not.)
Connect the device to the computer through USB.
From a terminal on a computer, type the following to boot the device into fastboot mode:
adb reboot bootloader
Once the device is in fastboot mode, verify your PC sees the device by typing fastboot devices
If you don't see your device serial number, and instead see "<waiting for device>", fastboot is not configured properly on your machine. See fastboot documentation for more info.
If you see "no permissions fastboot", try running fastboot as root.
From the same terminal, type the following command to unlock the bootloader:
fastboot -i 0x2970 oem unlock-go
If the device doesn't automatically reboot, reboot it from the menu. It should now be unlocked.
Since the device resets completely, you will need to re-enable USB debugging on the device to continue.
fastboot reboot
Installing a custom recovery using fastboot
Open a terminal on your PC and reboot the device into fastboot mode by typing
adb reboot bootloader
or by using the hardware key combination for your device while it is powered off.
Once the device is in fastboot mode, verify your PC sees the device by typing
fastboot devices
Flash recovery onto your device by entering the following command:
fastboot flash recovery your_recovery_image.img
where the latter part is the filename of the recovery image.
fastboot reboot
full rom fastboot
adb reboot bootloader
fastboot devices
fastboot flash aboot emmc_appsboot.mbn
fastboot flash abootbak emmc_appsboot.mbn
fastboot erase DDR
fastboot flash sbl1 sbl1.mbn
fastboot flash sbl1bak sbl1.mbn
fastboot flash tz tz.mbn
fastboot flash tzbak tz.mbn
fastboot flash hyp hyp.mbn
fastboot flash hypbak hyp.mbn
fastboot flash rpm rpm.mbn
fastboot flash rpmbak rpm.mbn
fastboot flash modem NON-HLOS.bin
fastboot flash cache cache.img
fastboot erase splash
fastboot flash splash splash.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash userdata userdata.img
fastboot flash boot boot.img
fastboot reboot
Click to expand...
Click to collapse
I've exactly followed your instructions for *"full rom fastboot"*, and all was done 'OK'. But Still the device is in bootloop and not going into recovery OR andriod system

ghertas said:
"full rom" was a zip file of cyanogen version
cyanogen realised two files of each rom
recovery version and fastboot version
if you want to install a custom rom on your device
Yes, I've download cyanogen Fastboot version, The only problem i've got is that my phone doesn't go into recovery mode although I've flashed TWRP also cn 13, but still the device only boots in fastboot only
When I select Recovery mode in Fastboot menu the device goes into bootloop.
Click to expand...
Click to collapse

idforpc said:
ghertas said:
"full rom" was a zip file of cyanogen version
cyanogen realised two files of each rom
recovery version and fastboot version
if you want to install a custom rom on your device
Yes, I've download cyanogen Fastboot version, The only problem i've got is that my phone doesn't go into recovery mode although I've flashed TWRP also cn 13, but still the device only boots in fastboot only
When I select Recovery mode in Fastboot menu the device goes into bootloop.
Click to expand...
Click to collapse
"fastboot reboot"
after boot the device , "Power off" the device and press volume down and power at the same time until you see the recovery on screen
"TWRP" is a custome recovery for install custom rom s
did you do all of those on " lineage wiki " ?
https://wiki.lineageos.org/devices/kipper/install
download the last version of twrp recovery
https://androidfilehost.com/?fid=1395089523397922500
Click to expand...
Click to collapse

Related

[Q] Stuck in FIrefox OS.

So I moved my Android zips off of my phone to make some extra room for Firefox OS. And when I was done playing with it I found out that the USB connection to get into the SD card does not work (another reason to have removable storage). I have Google_Nexus_4_ToolKit_v2.0.0 and tried everything I could think of in there. I dont know how to ADB except to put the phone into sideload mode and you use command prompt. I have CWM recovery on it. So any help would be awesome. I will take a good link or some step by step stuff. Thank you.
jaed.43725 said:
So I moved my Android zips off of my phone to make some extra room for Firefox OS. And when I was done playing with it I found out that the USB connection to get into the SD card does not work (another reason to have removable storage). I have Google_Nexus_4_ToolKit_v2.0.0 and tried everything I could think of in there. I dont know how to ADB except to put the phone into sideload mode and you use command prompt. I have CWM recovery on it. So any help would be awesome. I will take a good link or some step by step stuff. Thank you.
Click to expand...
Click to collapse
Calm down, there's solution.
1. Download Google Factory Image from here(4.3)
2. Extract it in your adb directory. You should see some files, but we oly need the radio.img, bootloader.img and image-occam-blabla.zip
3. Open a command window in your adb directory.
4. Reboot into bootloader and write the following code:
Code:
> fastboot erase boot
> fastboot erase cache
> fastboot erase recovery
> fastboot erase system
> fastboot erase userdata
> fastboot flash bootloader bootloader-blablabla.img
> fastboot reboot-bootloader
> fastboot flash radio radio-blablabla.img
> fastboot reboot-bootloader
> fastboot -w update image-blablabla.zip
5. The phone will reboot. Now u can use the toolkit to flash a recovery again (select 4.2.2 firmware) and starting rooting and flashing roms again.
Good luck! If u need any help just quote my comment so I get notified
luiseteyo said:
Calm down, there's solution.
1. Download Google Factory Image from here(4.3)
2. Extract it in your adb directory. You should see some files, but we oly need the radio.img, bootloader.img and image-occam-blabla.zip
3. Open a command window in your adb directory.
4. Reboot into bootloader and write the following code:
Code:
> fastboot erase boot
> fastboot erase cache
> fastboot erase recovery
> fastboot erase system
> fastboot erase userdata
> fastboot flash bootloader bootloader-blablabla.img
> fastboot reboot-bootloader
> fastboot flash radio radio-blablabla.img
> fastboot reboot-bootloader
> fastboot -w update image-blablabla.zip
5. The phone will reboot. Now u can use the toolkit to flash a recovery again (select 4.2.2 firmware) and starting rooting and flashing roms again.
Good luck! If u need any help just quote my comment so I get notified
Click to expand...
Click to collapse
Ok. So what I did was kinda following your setup here. I had to get the Android SDK first. Then extract that into C:/. Then I got the 4.3 like you said and extracted that C:\adt-bundle-windows-x86_64-20130917\sdk\platform-tools. Then because of the new SDK I put the phone into the first 3-button mode. I then ran flash-all. And after a minute I had stock 4.3.

Error on Android 5.0.2 OTA Update

Well i'm trying to update my Nexus 7 2012 to Android 5.0.2, after receiving the OTA update but keep getting an error.
I rooted my Nexus 7, and been thinking that's the problem, since it restarts to install the OTA update but goes to Recovery mode, and when i try to manually install the file get the following error :
https://www.dropbox.com/s/dqjc2ztzfbkvnuy/IMAG0897.jpg?dl=0
Any tips or solution for the problem?
Thanks in advance
Go here and flash the full image: https://developers.google.com/android/nexus/images
Skeetch79 said:
Go here and flash the full image: https://developers.google.com/android/nexus/images
Click to expand...
Click to collapse
Didn't want to do that, because means i'm going to loose everything
lmcmil said:
Didn't want to do that, because means i'm going to loose everything
Click to expand...
Click to collapse
Thought you would say that! .
You can always:
- download the image for your device from the google nexus website I gave you
- unzip the tgz file
- Find the resulting tar file and unzip it
- you will now have a folder
- inside the folder will be a bootloader-grouper-4.23.img file, image-nakasi-lrx22g.zip file, flash-all.bat file and two .sh files
- unzip the zip file to the same directory as the bootloader-grouper-4.23.img file
- reboot your nexus into bootloader mode
- plug the nexus into your PC
- open a command prompt in the same directory as the image, sh and bat files (on windows 7 hold the shift key and right click on an empty space within the folder and choose open command window here)
- in the command window type fastboot devices, make sure device is recognized
- if not, set up your pc for adb and fastboot, if so, continue
- type in the command prompt:
fastboot erase boot <hit enter>
fastboot erase cache <hit enter>
fastboot erase recovery <hit enter>
fastboot erase system <hit enter>
fastboot flash bootloader bootloader-grouper-4.23.img <hit enter>
fastboot reboot-bootloader <hit enter>
fastboot flash boot boot.img <hit enter>
fastboot flash recovery recovery.img <hit enter>
fastboot flash system system.img <hit enter>
fastboot reboot <hit enter>
This will preserve your app and data settings.
If you had custom recovery installed just reboot into fastboot and flash the recovery of your choice. example: fastboot flash recovery ,recovery image name>
If you want to reroot, download a superuser zip file to your device, reboot back into your custom recovery and then install the SuperUser zip of your choice (i.e. chainfire's SuperSu)
Hopefully this is straightforward and self explanatory
Thanks for the tip and explanation Skeetch79, will try to do like you wrote.
lmcmil said:
Thanks for the tip and explanation Skeetch79, will try to do like you wrote.
Click to expand...
Click to collapse
Np. Keep me posted
Sent from my XT1096 using Tapatalk
Skeetch79 said:
Thought you would say that! .
You can always:
- download the image for your device from the google nexus website I gave you
- unzip the tgz file
- Find the resulting tar file and unzip it
- you will now have a folder
- inside the folder will be a bootloader-grouper-4.23.img file, image-nakasi-lrx22g.zip file, flash-all.bat file and two .sh files
- unzip the zip file to the same directory as the bootloader-grouper-4.23.img file
- reboot your nexus into bootloader mode
- plug the nexus into your PC
- open a command prompt in the same directory as the image, sh and bat files (on windows 7 hold the shift key and right click on an empty space within the folder and choose open command window here)
- in the command window type fastboot devices, make sure device is recognized
- if not, set up your pc for adb and fastboot, if so, continue
- type in the command prompt:
fastboot erase boot <hit enter>
fastboot erase cache <hit enter>
fastboot erase recovery <hit enter>
fastboot erase system <hit enter>
fastboot flash bootloader bootloader-grouper-4.23.img <hit enter>
fastboot reboot-bootloader <hit enter>
fastboot flash boot boot.img <hit enter>
fastboot flash recovery recovery.img <hit enter>
fastboot flash system system.img <hit enter>
fastboot reboot <hit enter>
This will preserve your app and data settings.
If you had custom recovery installed just reboot into fastboot and flash the recovery of your choice. example: fastboot flash recovery ,recovery image name>
If you want to reroot, download a superuser zip file to your device, reboot back into your custom recovery and then install the SuperUser zip of your choice (i.e. chainfire's SuperSu)
Hopefully this is straightforward and self explanatory
Click to expand...
Click to collapse
This method works great! I was in the same boat. I analyzed the updater script and then analyzed the ro.build.fingerprint from my system, and it doesn't contain the weird one that it errors out on. I debated just removing the build prop check and repackaging it as an update, but decided against it.
@lmcmil - per chance, did you flash a different kernel and/or switch to F2FS before this happened? If so, that might correlate to mine, since I did do that....
Either way, I'm gonna run stock again for a while and see how it feels.
EDIT:
I think these lines:
Code:
mount("ext4", "EMMC", "/dev/block/platform/sdhci-tegra.3/by-name/APP", "/system", "max_batch_time=0,commit=1,data=ordered,barrier=1,errors=panic,nodelalloc");
getprop("ro.build.fingerprint") == "google/nakasi/grouper:5.0/LRX21P/1570855:user/release-keys" ||
getprop("ro.build.fingerprint") == "google/nakasi/grouper:5.0.2/LRX22G/1649326:user/release-keys" ||
abort("Package expects build fingerprint of google/nakasi/grouper:5.0/LRX21P/1570855:user/release-keys or google/nakasi/grouper:5.0.2/LRX22G/1649326:user/release-keys; this device has " + getprop("ro.build.fingerprint") + ".");
are what causes it to explode. First, it tries to mount ext4 instead of F2FS, which makes sense, but would cause the system partition to be unreadable if you converted it to F2FS. That COULD explain the odd "deestroy" build prop it thinks it got when it pulled ro.build.fingerprint, since when my system was fully booted mine matched the stock LRX21P using getprop from adb.
toastido i tryied to load the OTA using the Nexus Root Toolkit and the error i got was regarding missing calculator, wich i removed after installing "Calculator ++" app
Still haven't had time to try this method, i'm working this weekend so only next week i can give it a try and post the result.
Skeetch79 said:
Thought you would say that! .
You can always:
- download the image for your device from the google nexus website I gave you
- unzip the tgz file
- Find the resulting tar file and unzip it
- you will now have a folder
- inside the folder will be a bootloader-grouper-4.23.img file, image-nakasi-lrx22g.zip file, flash-all.bat file and two .sh files
- unzip the zip file to the same directory as the bootloader-grouper-4.23.img file
- reboot your nexus into bootloader mode
- plug the nexus into your PC
- open a command prompt in the same directory as the image, sh and bat files (on windows 7 hold the shift key and right click on an empty space within the folder and choose open command window here)
- in the command window type fastboot devices, make sure device is recognized
- if not, set up your pc for adb and fastboot, if so, continue
- type in the command prompt:
fastboot erase boot <hit enter>
fastboot erase cache <hit enter>
fastboot erase recovery <hit enter>
fastboot erase system <hit enter>
fastboot flash bootloader bootloader-grouper-4.23.img <hit enter>
fastboot reboot-bootloader <hit enter>
fastboot flash boot boot.img <hit enter>
fastboot flash recovery recovery.img <hit enter>
fastboot flash system system.img <hit enter>
fastboot reboot <hit enter>
This will preserve your app and data settings.
If you had custom recovery installed just reboot into fastboot and flash the recovery of your choice. example: fastboot flash recovery ,recovery image name>
If you want to reroot, download a superuser zip file to your device, reboot back into your custom recovery and then install the SuperUser zip of your choice (i.e. chainfire's SuperSu)
Hopefully this is straightforward and self explanatory
Click to expand...
Click to collapse
Good Man !!!
Thanks Very Much for that one,
I got stuck on the boot after performing the advised but a quick Cache Wipe sorted that out.
Once again Much Obliged !!!
Yeah forgot to mention the above. if you are stuck in a boot loop: shut down. reboot to recovery. wipe cache and dalvic. Reboot. Profit.
Sent from my XT1096 using Tapatalk
Skeetch79 said:
Thought you would say that! .
You can always:
- download the image for your device from the google nexus website I gave you
- unzip the tgz file
- Find the resulting tar file and unzip it
- you will now have a folder
- inside the folder will be a bootloader-grouper-4.23.img file, image-nakasi-lrx22g.zip file, flash-all.bat file and two .sh files
- unzip the zip file to the same directory as the bootloader-grouper-4.23.img file
- reboot your nexus into bootloader mode
- plug the nexus into your PC
- open a command prompt in the same directory as the image, sh and bat files (on windows 7 hold the shift key and right click on an empty space within the folder and choose open command window here)
- in the command window type fastboot devices, make sure device is recognized
- if not, set up your pc for adb and fastboot, if so, continue
- type in the command prompt:
fastboot erase boot <hit enter>
fastboot erase cache <hit enter>
fastboot erase recovery <hit enter>
fastboot erase system <hit enter>
fastboot flash bootloader bootloader-grouper-4.23.img <hit enter>
fastboot reboot-bootloader <hit enter>
fastboot flash boot boot.img <hit enter>
fastboot flash recovery recovery.img <hit enter>
fastboot flash system system.img <hit enter>
fastboot reboot <hit enter>
This will preserve your app and data settings.
If you had custom recovery installed just reboot into fastboot and flash the recovery of your choice. example: fastboot flash recovery ,recovery image name>
If you want to reroot, download a superuser zip file to your device, reboot back into your custom recovery and then install the SuperUser zip of your choice (i.e. chainfire's SuperSu)
Hopefully this is straightforward and self explanatory
Click to expand...
Click to collapse
Does this also work if I want to go back to Kitkat? I am asking, because I've tried the following:
Code:
@echo off
echo. listing devices:
fastboot devices
echo. To continue press Enter
pause
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
REM adopt the following line according to the bootloader image filename
fastboot flash bootloader bootloader-flo-flo-04.02.img
fastboot reboot-bootloader
fastboot flash boot boot.img
fastboot flash cache cache.img
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot reboot
And no matter, if I do a wipe cache afterwards or not, I end up in a boot-loop.
Do you know a way to keep apps and settings while going back to Kitkat?
nieroster
lmcmil said:
toastido i tryied to load the OTA using the Nexus Root Toolkit and the error i got was regarding missing calculator, wich i removed after installing "Calculator ++" app
Still haven't had time to try this method, i'm working this weekend so only next week i can give it a try and post the result.
Click to expand...
Click to collapse
lmcmil said:
Well i'm trying to update my Nexus 7 2012 to Android 5.0.2, after receiving the OTA update but keep getting an error.
I rooted my Nexus 7, and been thinking that's the problem, since it restarts to install the OTA update but goes to Recovery mode, and when i try to manually install the file get the following error :
https://www.dropbox.com/s/dqjc2ztzfbkvnuy/IMAG0897.jpg?dl=0
Any tips or solution for the problem?
Thanks in advance
Click to expand...
Click to collapse
TWRP is incompatible with 5.x OTA: it uses its own moronic default.prop instead of importing the device build.prop (or something like that) . It needs to be fixed.
You have to bother flashing the full image (minus the wiping eventually) and reinstall root & TWRP with every update, just like the rest of us
Got an Failed error at fastboot flash bootloader bootloader-grouper-4.23.img <hit enter>.
So now i don't have a valid bootloader and also can't enter recovery because it was erased at fastboot erase recovery <hit enter> step
And also typing fastboot devices my Nexus 7 isn't detected, what can i do now?
lmcmil said:
Got an Failed error at fastboot flash bootloader bootloader-grouper-4.23.img <hit enter>.
So now i don't have a valid bootloader and also can't enter recovery because it was erased at fastboot erase recovery <hit enter> step
And also typing fastboot devices my Nexus 7 isn't detected, what can i do now?
Click to expand...
Click to collapse
Well decided to use the Nexus Root Kit and flash the full image LRX22G, doing it now.
Will post how it went.
lmcmil said:
Got an Failed error at fastboot flash bootloader bootloader-grouper-4.23.img <hit enter>.
So now i don't have a valid bootloader and also can't enter recovery because it was erased at fastboot erase recovery <hit enter> step
And also typing fastboot devices my Nexus 7 isn't detected, what can i do now?
Click to expand...
Click to collapse
I had the 2012 Nexus 7 WiFi before I picked up the 2013 model. I had the same issue with that bootloader. Seems to be a common issue. Here are articles discussing the issue and fixes.
http://android.stackexchange.com/qu...t-flash-bootloader-failed-remote-invalidstate
https://code.google.com/p/android/issues/detail?id=62198&
http://forum.xda-developers.com/showthread.php?t=2573015
I remember flashing a modified bootloader to resolve the issue, since as you can see the bootloader packaged with the images is borked.
EDIT: try flashing the appropriate bootloader from this thread: http://forum.xda-developers.com/showthread.php?t=2417097
lmcmil said:
Well decided to use the Nexus Root Kit and flash the full image LRX22G, doing it now.
Will post how it went.
Click to expand...
Click to collapse
So my Nexus 7 is now running with 5.0.2, and did not loose any apps since i chose the "No wipe mode"
Going to root it again, and install latest TWRP Recovery
lmcmil said:
So my Nexus 7 is now running with 5.0.2, and did not loose any apps since i chose the "No wipe mode"
Going to root it again, and install latest TWRP Recovery
Click to expand...
Click to collapse
So i have now a Nexus 7 running 5.0.2, already rooted again and with TWRP 2.8.4.1.
Thanks a lot!
Skeetch79 said:
Thought you would say that! .
You can always:
- download the image for your device from the google nexus website I gave you
- unzip the tgz file
- ...
This will preserve your app and data settings.
If you had custom recovery installed just reboot into fastboot and flash the recovery of your choice. example: fastboot flash recovery ,recovery image name>
If you want to reroot, download a superuser zip file to your device, reboot back into your custom recovery and then install the SuperUser zip of your choice (i.e. chainfire's SuperSu)
Hopefully this is straightforward and self explanatory
Click to expand...
Click to collapse
Thanks for the great tutorial! Used it yesterday on my rooted Nexus 7 to upgrade to 5.0.2, worked like a breeze! :good:
Afterwards I used WugFresh's Nexus Root Toolkit to regain root.
Skeetch79 said:
Thought you would say that! .
You can always:
- download the image for your device from the google nexus website I gave you
- unzip the tgz file
- Find the resulting tar file and unzip it
- you will now have a folder
- inside the folder will be a bootloader-grouper-4.23.img file, image-nakasi-lrx22g.zip file, flash-all.bat file and two .sh files
- unzip the zip file to the same directory as the bootloader-grouper-4.23.img file
- reboot your nexus into bootloader mode
- plug the nexus into your PC
- open a command prompt in the same directory as the image, sh and bat files (on windows 7 hold the shift key and right click on an empty space within the folder and choose open command window here)
- in the command window type fastboot devices, make sure device is recognized
- if not, set up your pc for adb and fastboot, if so, continue
- type in the command prompt:
fastboot erase boot <hit enter>
fastboot erase cache <hit enter>
fastboot erase recovery <hit enter>
fastboot erase system <hit enter>
fastboot flash bootloader bootloader-grouper-4.23.img <hit enter>
fastboot reboot-bootloader <hit enter>
fastboot flash boot boot.img <hit enter>
fastboot flash recovery recovery.img <hit enter>
fastboot flash system system.img <hit enter>
fastboot reboot <hit enter>
This will preserve your app and data settings.
If you had custom recovery installed just reboot into fastboot and flash the recovery of your choice. example: fastboot flash recovery ,recovery image name>
If you want to reroot, download a superuser zip file to your device, reboot back into your custom recovery and then install the SuperUser zip of your choice (i.e. chainfire's SuperSu)
Hopefully this is straightforward and self explanatory
Click to expand...
Click to collapse
I followed this tutorial yesterday and everything went great I now have 5.0.2 working on my Nexus 7 2013, with no problems I can detect at the moment. Thank you, because I was just frustrated I saw the OTA notification without being able to do anything.
Cheers.
I try it too 5.0.2 ota update and nothing still on 4.4.4 I guess on Lollypops for me

[Q] How to recover Yureka from Qualcomm HS-USB QDLOADER 9008?

Hi There,
I wonder if anyone can help to recover Yureka?
I was trying to update rom using fastboot rom on the phone and it has broken the phone.
I am now getting Qualcomm HS-USB QDLOADER 9008.
Can anyone please me to recover my phone?
Thanks in advance.
Samir
flash stock rom using ADB
thearjunraju said:
flash stock rom using ADB
Click to expand...
Click to collapse
I guess ADB access only possible when you have working phone.
so I think not possible using ADB.
I can't go to bootloader either.
so not possible using fastboot either
if you can boot into the bootloader mode, do so.
to boot into the bootloader mode:
>switch off the phone
>press and hold the volume up button
>while pressing the volume up button, plug in the usb cable. (needless to say, the other end should be attached to your computer, and the required drivers should be installed)
prerequisites:
download the stock zip from here htt p:// builds.cyngn. c om/factory/tomato/cm-11.0-XNPH52O-tomato-signed-fastboot. zip
download the fastboot tools
make a *.bat file of the following code:
<code>
 @ECHO off
echo Flashing kernel
fastboot -i 0x1ebf flash boot boot.img
echo Flashing system
fastboot -i 0x1ebf flash system system.img
echo Wiping Data
fastboot -i 0x1ebf flash userdata userdata.img
echo Flashing recovery
fastboot -i 0x1ebf flash recovery recovery.img
echo Flashing model
fastboot -i 0x1ebf flash modem NON-HLOS.bin
fastboot -i 0x1ebf flash rpm rpm.mbn
echo Flashing bootloader
fastboot -i 0x1ebf flash sbl1 sbl1.mbn
fastboot -i 0x1ebf flash tz tz.mbn
fastboot -i 0x1ebf flash aboot emmc_appsboot.mbn
echo Flashing complete. Disconnect device and reboot
</code>
extract both the zips in the same folder and run the bat file while your phone is plugged in in the bootloader mode.
cheers!
My Yu Yureka is Hard Bricked
My Yu Yureka is Hard Bricked .....can anyone help me to unbrick it
my phone is not start in Fastboot Mode and Normal Mode
In QPST it always shows download mode
please help me out
I want 8916_msm.mbn,MPRG8916.hex files

Zui to Cyanogen

Is there any way to convert ZUI to Cyanogen
Download the modified recovery image - DOWNLOAD (ROMraid)
Download the stock (re-signed) Cyanogen OS system image - DOWNLOAD (ROMraid)
Ensure you have fastboot and adb on your machine
If you are using Windows, install the drivers from this topic
Enable the developer menu (tap ZUI version several times) and enable USB debugging in the developer menu
Type 'adb reboot bootloader' to put your device in bootloader mode
Type 'fastboot -i 0x2b4c oem get-device-info' and check your bootloader is unlocked - if it is not, use 'fastboot -i 0x2b4c oem unlock'
Type 'fastboot -i 0x2b4c boot z1.recovery.testkeys.img' to boot the custom recovery image
Select the option to wipe the device (important!)
Select the install update / from USB option
Type 'adb sideload z1.cyanogen.convert.signed.zip'
Wait for this to complete then reboot
i trying to do with your steps, above steps are passed, but on step adb sideload z1.cyanogen.convert.signed.zip I have error message show " loading: 'z1.cyanogen.convert.signed.zip' error: device '<null> not found" how can i do? help me please ...
Well I also couldn't follow this guide but I finally managed to solve the issue with the help of a friend!
Put the ROM on the storage of the zuk!
Do all steps and unlock the bootloader.
I mean do all this:
Download the modified recovery image - DOWNLOAD (ROMraid)
Download the stock (re-signed) Cyanogen OS system image - DOWNLOAD (ROMraid)
Ensure you have fastboot and adb on your machine
If you are using Windows, install the drivers from this topic
Enable the developer menu (tap ZUI version several times) and enable USB debugging in the developer menu
Type 'adb reboot bootloader' to put your device in bootloader mode
Type 'fastboot -i 0x2b4c oem get-device-info' and check your bootloader is unlocked - if it is not, use 'fastboot -i 0x2b4c oem unlock'
Type 'fastboot -i 0x2b4c boot z1.recovery.testkeys.img' to boot the custom recovery image
Select the option to wipe the device (important!)
Boot into cm recovery and make a factory reset! Don't wipe media!
Now flash the rom.zip as usual! The same way you flash any rom via recovery!
Now reboot system.
You will have cyanogen! No need for any sideload or push commands in adb!
Once cyanogen boots, make a full factory reset from within the settings!
Enjoy!
Recovery img cannot load when i flash it
Hello if i may ask why cant i get recovery to flash i did follow all steps. But stuck at recovery flashing .. says it cannot load. What am i missing here pls help tnx
codding said:
Is there any way to convert ZUI to Cyanogen
Download the modified recovery image - DOWNLOAD (ROMraid)
Download the stock (re-signed) Cyanogen OS system image - DOWNLOAD (ROMraid)
Ensure you have fastboot and adb on your machine
If you are using Windows, install the drivers from this topic
Enable the developer menu (tap ZUI version several times) and enable USB debugging in the developer menu
Type 'adb reboot bootloader' to put your device in bootloader mode
Type 'fastboot -i 0x2b4c oem get-device-info' and check your bootloader is unlocked - if it is not, use 'fastboot -i 0x2b4c oem unlock'
Type 'fastboot -i 0x2b4c boot z1.recovery.testkeys.img' to boot the custom recovery image
Select the option to wipe the device (important!)
Select the install update / from USB option
Type 'adb sideload z1.cyanogen.convert.signed.zip'
Wait for this to complete then reboot
i trying to do with your steps, above steps are passed, but on step adb sideload z1.cyanogen.convert.signed.zip I have error message show " loading: 'z1.cyanogen.convert.signed.zip' error: device '<null> not found" how can i do? help me please ...
Click to expand...
Click to collapse
How do i get rid of the watermark?

Moto G6 Plus - No bootable A/B slot, device not detected with adb.

Hi,
I installed the PPW29.116-20 FIRMWARE for pie 9, it was working fine until I uninstalled magisk and now it will only boot to Fastboot mode saying "No bootable A/B slot".
The problem however it the device it no longer detected in adb to reinstall. adb devices returns no devices. This is odd as it was working fine before.
I have tried with both moto and universal adb drivers, changed cables and even changed computers - nothing it making it appear.
Any help would be much appreciated
Use Fastboot!
Ezcorpia said:
Hi,
I installed the PPW29.116-20 FIRMWARE for pie 9, it was working fine until I uninstalled magisk and now it will only boot to Fastboot mode saying "No bootable A/B slot".
The problem however it the device it no longer detected in adb to reinstall. adb devices returns no devices. This is odd as it was working fine before.
I have tried with both moto and universal adb drivers, changed cables and even changed computers - nothing it making it appear.
Any help would be much appreciated
Click to expand...
Click to collapse
Requirements:
Fastboot (because you're in Fastboot mode, lol) download links for Windows, Linux, Mac.
fastboot images for your ROM e.g. from this thread
fastboot flash file (contains flash commands, see in thread above)
Just unpack the zip file then open cmd/terminal, navigate to that folder and enter:
Code:
fastboot devices
When output looks like this your phone is detected:
Code:
XXXXXXXXX fastboot
'XXXXXXXXX' is your phone's serial number.
Unpack and copy the images and flash file into the same folder as fastboot. The folder contains following files:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
On Windows double-click 'flashfileNoErase.bat' (ROM thread).
Check for errors, press enter and the phone will reboot.
had the same issue before
i had the same issue happen to me i about freaked out because i thought i had really jacked my phone up but i found this app called Lenovo Moto Smart Assistant it is a life saver trust me. if this happens to you then just download this app and it will walk you through the rest it has a upgrade and a rescue option the rescue option reinstalls the stock rom and and restores evrything back to normal on your phone. definite must have when flashing roms to your phone. :good:
lassemacchiato said:
Requirements:
Fastboot (because you're in Fastboot mode, lol) download links for Windows, Linux, Mac.
fastboot images for your ROM e.g. from this thread
fastboot flash file (contains flash commands, see in thread above)
Just unpack the zip file then open cmd/terminal, navigate to that folder and enter:
Code:
fastboot devices
When output looks like this your phone is detected:
Code:
XXXXXXXXX fastboot
'XXXXXXXXX' is your phone's serial number.
Unpack and copy the images and flash file into the same folder as fastboot. The folder contains following files:
On Windows double-click 'flashfileNoErase.bat' (ROM thread).
Check for errors, press enter and the phone will reboot.
Click to expand...
Click to collapse
I just want to thank you for this, I have been crying all night because I bricked my phone just a few hours before buying it, please know that you helped a stranger greatly-
#Starlord37# said:
i had the same issue happen to me i about freaked out because i thought i had really jacked my phone up but i found this app called Lenovo Moto Smart Assistant it is a life saver trust me. if this happens to you then just download this app and it will walk you through the rest it has a upgrade and a rescue option the rescue option reinstalls the stock rom and and restores evrything back to normal on your phone. definite must have when flashing roms to your phone. :good:
Click to expand...
Click to collapse
Phone of a friend suddenly died without any reason and wouldn't boot anymore. Tried this software out and it worked straight away. Requires a quick account registration however, but no biggie.
Thank you so much!
lassemacchiato said:
Requirements:
Fastboot (because you're in Fastboot mode, lol) download links for Windows, Linux, Mac.
fastboot images for your ROM e.g. from this thread
fastboot flash file (contains flash commands, see in thread above)
Just unpack the zip file then open cmd/terminal, navigate to that folder and enter:
Code:
fastboot devices
When output looks like this your phone is detected:
Code:
XXXXXXXXX fastboot
'XXXXXXXXX' is your phone's serial number.
Unpack and copy the images and flash file into the same folder as fastboot. The folder contains following files:
On Windows double-click 'flashfileNoErase.bat' (ROM thread).
Check for errors, press enter and the phone will reboot.
Click to expand...
Click to collapse
I dont finding the flashfilenoeraser.bat
But i found...
see bellow
echo off
fastboot getvar max-sparse-size
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot flash bluetooth BTFM.bin
fastboot flash dsp dspso.bin
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system_b system_other.img
fastboot flash oem oem.img
fastboot flash oem_b oem_other.img
fastboot flash vendor vendor.img_sparsechunk.0
fastboot flash vendor vendor.img_sparsechunk.1
fastboot erase modemst1
fastboot erase modemst2
fastboot erase carrier
fastboot erase ddr
fastboot flash fsg fsg.mbn
fastboot flash bluetooth BTFM.bin
fastboot oem fb_mode_clear
echo -------------------------------------------------------------------------
echo please scroll up and check your flash for any errors
echo -------------------------------------------------------------------------
pause
fastboot reboot
exit
flashfileNoErase.bat
chptr0 said:
I dont finding the file "Flashfilenoeraser". Can u help me?
Click to expand...
Click to collapse
It's an attachment to the ROM thread I linked to.
Here's the direct link (download G6PlusFlashPieOfficial_NoErase.zip, just unpack and you have the right file):
G6PlusFlashPieOfficial.zip
G6PlusFlashPieOfficial_NoErase.zip
lassemacchiato said:
It's an attachment to the ROM thread I linked to.
Here's the direct link (download G6PlusFlashPieOfficial_NoErase.zip, just unpack and you have the right file):
G6PlusFlashPieOfficial.zip
G6PlusFlashPieOfficial_NoErase.zip
Click to expand...
Click to collapse
Thanks for your help!!!

Categories

Resources