Related
so i keep having the disappearing status bar issue on CM7 so i booted into TWRP, fixed permissions wiped cache and dalvik and hit reboot system. now my kindle will only boot into TWRP. anyone know how to get it to boot to CM7?
Sent from my SGH-T959V using xda premium
Please use the search feature, this has been discussed countless times!! You need to set your device to boot in 'normal' mode via adb. The kindle fire utility also has an option to do this....
Sent from my Kindle Fire using Tapatalk
you said "boot to recovery" in cm7 - disable this option for the future !
http://forum.xda-developers.com/showthread.php?t=1399889
or
http://forum.xda-developers.com/showthread.php?t=1428428
or
with adb:
adb shell su -c "idme bootmode 4000"
adb reboot
with fastboot:
fastboot -i 0x1949 oem idme bootmode 4000
fastboot -i 0x1949 reboot
or
fastboot -i 0x18d1 oem idme bootmode 4000
fastboot -i 0x18d1 reboot
or
fastboot oem idme bootmode 4000
fastboot reboot
b63 said:
you said "boot to recovery" in cm7 - disable this option for the future !
http://forum.xda-developers.com/showthread.php?t=1399889
or
http://forum.xda-developers.com/showthread.php?t=1428428
or
with adb:
adb shell su -c "idme bootmode 4000"
adb reboot
with fastboot:
fastboot -i 0x1949 oem idme bootmode 4000
fastboot -i 0x1949 reboot
or
fastboot -i 0x18d1 oem idme bootmode 4000
fastboot -i 0x18d1 reboot
or
fastboot oem idme bootmode 4000
fastboot reboot
Click to expand...
Click to collapse
i wish i knew how to use adb commands
Sent from my SGH-T959V using xda premium
then use the unbrick utility (second link) - extract it to c:\ - run it
use option 2 - recovery loop
b63 said:
then use the unbrick utility (second link) - extract it to c:\ - run it
use option 2 - recovery loop
Click to expand...
Click to collapse
i can't as i'm on a mac and have no access to a windows computer...
i don't know about a mac
but you should have a directory where an adb executable is located
there you should open a command shell and issue the nessesary commands
this is what i found:
Android SDK Mac: http://developer.android.com/sdk/index.html
Platform tools installed: Go to the tools folder in the sdk. Make sure fastboot and adb are there. IMPORTANT: Check fastboot by doubling clicking it (make sure it doesn't say binary doesn't execute).
Adjustments: Make sure that you are using the ./ version of the commands. When it says to input SU, input su.
FAQ: Stuck at fastboot, and adb is not connecting? Depending on circumstances, answer may vary. In my case, here is the terminal log (AMA is my computer):
AMA:~ Aidan$ cd /Users/Aidan/Android/android-sdk-mac/platform-tools
AMAlatform-tools Aidan$ ./adb devices
List of devices attached
AMAlatform-tools Aidan$ sudo ./fastboot oem idme bootmode 4000
then power off / on
update:
think you can use my previous commands:
now you need to first navigate to your platform-tools folder in your android sdk folder using terminal.
Go to utilities in the applications tab in finder. Open up Terminal.
Now type the following line to navigate to the platform-tools folder.
cd ~/androidsdk/platform-tools
for me it is this because my SDK folder is named "androidsdk", if your's is named differently, insert it's name where androidsdk is.
followed by that you can start using ADB. Instead of running things as
adb root, or adb reboot, you need to include
./ before the commands, IE: ./adb root, or ./adb push
IE THE FIRST STEP IS "adb root", rewrite this is "./adb root"
from then on, include that ./ before any command.
ok so i have both fastboot and adb working, now what do i have to type in order to get this to reboot properly (i'm sorry for asking so much, but i'm a COMPLETE adb noob).
we have look what you have available - adb or fastboot
as first:
./adb devices
get a response ?
if not:
./fastboot -i 0x1949 getvar product
it should return "kindle"
gimme the results
the first time it worked and then when i did it again as a double check, my kindle started to boot (as it always does when it's plugged in and now it is stuf at the yellow triangle....
EDIT: finally got it to turn off, so fastboot registers it, what next
what commands did you exactly enter in the terminal ?
both the adb and fastboot commands you just showed me. but everything is back to normal, what do i do know that the kindle is recognized?
please copy and paste what is in the terminal window, that i can see to which command it has responded
what do you mean with back to normal ?
normal boot to os ? or to twrp again ?
basically the commands are the same as for windows - you have just to add ./ in the front:
this are the comands to set bootmode to normal:
when you have fastboot available:
./fastboot -i 0x1949 oem idme bootmode 4000
./fastboot -i 0x1949 reboot
or
./fastboot -i 0x18d1 oem idme bootmode 4000
./fastboot -i 0x18d1 reboot
or
./fastboot oem idme bootmode 4000
./fastboot reboot
when you have adb available:
./adb shell su -c "idme bootmode 4000"
./adb reboot
fastboot is the one that responded.
Code:
Macintosh:platform-tools recardeeps317$ ./fastboot oem idme bootmode 4000
< waiting for device >
...
OKAY [ 0.201s]
finished. total time: 0.201s
Macintosh:platform-tools recardeeps317$ ./fastboot reboot
but it doesnt actually reboot the Kindle. it gets hung at the triangle still. if i get it to boot back to TWRP could i just make a back up and reflash CM7?
EDIT:
finally got it to reboot into CM7 with:
Code:
Macintosh:platform-tools recardeeps317$ ./fastboot -i 0x18d1 reboot
< waiting for device >
rebooting...
finished. total time: 0.000s
ok - now we know it is responding to fastboot without the address initialisation commands (that depends on the version of fff - the bootloader)
did you try to power it off manually (pwr button ~30sec) ?
why would you like to reflash ? is it defect or now just not starting ?
and yes you can switch it to other bootmodes as well:
normal = 4000
fastboot = 4002
recovery = 5001
now it's up to you what you will like to do ...
UPDATE: hurraaa !!! congratulations ! - glad that it's working again !
please mark the subject of the topic (edit first post) to [Solved]
Im trying to install the new CWR software and dont know how to get my kindle fire into fastboot mode or what that even really means
first you should read a bit and try to understand how it works
then you should have the necessary programs (adb.exe & fastboot.exe)
for the beginning some things to know:
driver (under android phone):
normal & recovery boot: -> android composite adb interface
fastboot: -> android adb interface
here all the possible the commands to change bootmode:
with adb:
adb shell su -c "idme bootmode 4000"
adb reboot
or
adb shell idme bootmode 4000
adb reboot
with fastboot:
fastboot -i 0x1949 oem idme bootmode 4000
fastboot -i 0x1949 reboot
or
fastboot -i 0x18d1 oem idme bootmode 4000
fastboot -i 0x18d1 reboot
or
fastboot oem idme bootmode 4000
fastboot reboot
the number is the bootmode you want to switch to:
normal boot -> 4000
fastboot -> 4002
boot to recovery -> 5001
and if you know:
normal boot -> adb commands YES -> fastboot commands NO
fastboot -> adb commands NO -> fastboot commands YES
recovery -> adb commands YES -> fastboot commands NO
then you only have to count 1 and 1 together ...
You should check out the Kindle Fire Utility. Specifically the option that changes the bootmode.
Last I checked, it also has an option to install the appropriate drivers. And if you are comfortable using the command prompt, you can use adb.exe and fastboot.exe that are included with that utility.
I was trying to change the keyboard and have converted KF to brick
The mistake that i done was that i had uploaded wrong settings.db and now KF its stuck at boot logo... i can see the animation and when i connect device to computer (Win) it makes 2x sounds (Beep-beep), the device its visible in "safely remove hardware..." and new "Removable media" its visible in My Computer, but its disabled.
I have already read&tried tons of possible things, like "Kindle Fire Utility", "fastboot ...", "adb ..."...
- http://forum.xda-developers.com/showpost.php?p=22433402&postcount=4
- http://forum.xda-developers.com/showthread.php?t=1356257&page=70
- ...
but with no luck
When i try to run commands adb or fastboot (with -i 0x1949) its just says "waiting for device" and nothing happens... not even if i reboot manually (~20s power button press) or disconnect&connect KF.
Is there still chance for my KF?
-----------------
EDIT: Solved by b63
there is always a chance - only a question of tools an effort ...
do you have fff (the yellow triangle) and twrp on the kf ?
None... i was think of instaling TWRP, but first i wanted to change the keyboard
bad decision - now you have to get to fastboot somehow
to have all tools available i would recommend to download kfu (if you not allready have), extract it to c:\ and rename to "kfu" that it is c:\kfu
all needed commands are in the tools directory of kfu (c:\kfu\tools)
open a (elevated) command prompt and cd to c:\kfu\tools
issue "fastboot -i 0x1949 oem idme bootmode 4000"
when it says <waiting for device> power off the kf by holding power button for ~20sec till it turns off
power on again
the command should be picked up and finished
power off/on again
the kf should stay at "kindle fire" static (fastboot)
check with "fastboot -i 0x1949 getvar product"
tell me if you'r gone so far ...
no luck... boot animation is in loop and fastboot is waiting for device
ok - need to try an other method
what says your device manager under "android phone" ?
do you see "kindle" or "unknown device" ?
if yes you should update the driver
which drivers do you use ? kfu or sdk ?
when you say boot animation in loop means the "kindle fire" animated - right ?
or is it boot looping ? - then you will have to charge it for some hours with the wall charger
container.mariborcan.net/datoteke/kfdm.jpg (can't add img link, because i'm new on forum )
everything worked until now...
when you say boot animation in loop means the "kindle fire" animated - right ?
Click to expand...
Click to collapse
it's animated... then disapperes for second... then animates... disappears for second... and looping again and again...
sounds like the 3-5 sec bootloop -> out of battery
in this case -> wall charger and hard power off to allow charging
or are you absolutely shure it's fully loaded ?
what about the device manager ?
b63 said:
sounds like the 3-5 sec bootloop -> out of battery
in this case -> wall charger and hard power off to allow charging
or are you absolutely shure it's fully loaded ?
Click to expand...
Click to collapse
i will try to charge it once more...
b63 said:
what about the device manager ?
Click to expand...
Click to collapse
device manager says "Android Composite ADB interface" (container.mariborcan.net/datoteke/kfdm.jpg), "safely remove hardware" recognize device as "Kindle"
sounds good - any reaction on "adb devices" ?
have made a little batch file to test adb connection
please place it in the tools directory of kfu, rename from .txt to .bat and run it from the command line
it should check if you can reach adb commands - if yes then there is a chance to switch the kf to fastboot mode - this is necessary to install fff & twrp
the batch is waiting for device - means if the output don't change for some seconds please restart the kf and check if the commands are resumed
maybe copy and paste the output
would also check the adb_usb.ini in the .android folder in your personal directory
it should include 0x1949
if you get response to "adb devices" you can follow this post:
http://forum.xda-developers.com/showpost.php?p=21803658&postcount=29
usb driver are working ok...
i have rechanged KF and now i "adb devices" recognizes KF...
C:\kfu\tools>adb devices
List of devices attached
3700002600000001 device
Click to expand...
Click to collapse
but if i run "fastboot devices" it doesnt show anything and it's still "waiting for devices" if i try to "fastboot -i 0x1949 oem idme bootmode 4002"
you'r missing point 2 of the description
first you need to switch to fastboot mode - then you can use the fastboot commands
a other option is to try to use kfu option 5 to install twrp - it should do it for you
btw. since fastboot commands only work in fastboot mode your above command wont make sense - see here:
driver (under android phone):
normal & recovery boot: -> android composite adb interface
fastboot: -> android adb interface
here all the possible commands to change bootmode:
with adb (secure kernel):
adb shell su -c "idme bootmode 4000"
adb reboot
or (twrp or unsecure kernel):
adb shell idme bootmode 4000
adb reboot
with fastboot:
fastboot -i 0x1949 oem idme bootmode 4000
fastboot -i 0x1949 reboot
or:
fastboot -i 0x18d1 oem idme bootmode 4000
fastboot -i 0x18d1 reboot
or:
fastboot oem idme bootmode 4000
fastboot reboot
the number is the bootmode you want to switch to:
normal boot -> 4000
fastboot -> 4002
boot to recovery -> 5001
and if you know:
normal boot -> adb commands YES -> fastboot commands NO
fastboot -> adb commands NO -> fastboot commands YES
recovery -> adb commands YES -> fastboot commands NO
then you only have to count 1 and 1 together and can master nearly each hanging situation !
Click to expand...
Click to collapse
My KF is stuck at the KF logo too.. windows sees adb device but when using the command "adb devices" nothing shows up. It did work when I was trying to install recovery then this happened.. I read about a "factory cable" which I am trying to make or get.. So am I correct in assuming that is my only real way of saving my device since adb won't connect?
Sent from my Galaxy Nexus using XDA App
not necessarily - your device might be in fastboot mode - only fastboot commands are working
try "fastboot -i 0x1949 getvar product" and see if something returns
if you did with kfu just select option 1 - bootmode normal
or manually:
fastboot -i 0x1949 oem idme bootmode 4000
fastboot -i 0x1949 reboot
b63 said:
not necessarily - your device might be in fastboot mode - only fastboot commands are working
try "fastboot -i 0x1949 getvar product" and see if something returns
if you did with kfu just select option 1 - bootmode normal
or manually:
fastboot -i 0x1949 oem idme bootmode 4000
fastboot -i 0x1949 reboot
Click to expand...
Click to collapse
wow THANKS where is the :doh: button... i used the KFU and option 1 and normal bootmode and it rebooted and came back.. you R the MAN!!
I can't believe i didn't do that last night with all the other stuff i tried..
I now have a fully working kindle fire AGAIN
it wont work...
i have changed driver front and back "android composite adb interface/android adb interface", tryed everything and it just wont go i can't get it in fastboot...
b63 please read my PM...
allready replied ...
b63 solved the problem
to sum up what he did... (all console commands are written with prefix >>)
transfered files from fbmode-0.9.zip (http://forum.xda-developers.com/showthread.php?t=1414832) to KF to folder /data/local/tmp
>> adb push fbmode /data/local/tmp
>> adb shell chmod 755 /data/local/tmp/fbmode
>> adb shell /data/local/tmp/fbmode
>> adb reboot
than checked device...
>> fastboot -i 0x1949 getvar product
it's should give:
product: kindle
finished. total time: 0.004s
than installed TWRP...
>> fastboot -i 0x1949 boot twrp-blaze-2.0.0RC0.img
downloading 'boot.img'... OKAY [ 2.892s]
booting... OKAY [ 0.001s]
finished. total time: 2.901s
checked again:
>> fastboot -i 0x1949 getvar product
product: kindle
finished. total time: 0.001s
than flashed bootloader...
>> fastboot flash bootloader u-boot.bin
sending 'bootloader' (211 KB)... OKAY [ 0.063s]
writing 'bootloader'... OKAY [ 0.507s]
finished. total time: 0.570s
than changed bootmode to recovery
>> fastboot oem idme bootmode 5001
... OKAY [ 0.196s]
finished. total time: 0.198s
rebooted...
>> fastboot reboot
rebooting...
finished. total time: 0.014s
checked if device is in recovery
>> adb devices
List of devices attached
37************ recovery
then we fixed settings.db file that I have f*** up ... we installed old file and rewrited permissions to system.system with 666
on the end we switched back to normal bootmode and rebooted...
>> adb shell idme bootmode 4000
<idme> write 4000 to offset 0x1000
>> adb reboot
Click to expand...
Click to collapse
Hope this helps someone...
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?
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