KINDLE FIRE HD ONLY!!! USE AT YOUR OWN RISK!!
I put together this tool for those that have tried to modify their system unsuccessfully and bricked their device. You must be able to get your device into fastboot for this to work. The easiest way is to purchase a factory cable or make your own(a $15 purchase or a little bit of your time is better than a bricked device).
The .img's in this tool were made from a rooted device w/ the su binary in place. There is no need to re-root your device, however if you choose to erase cache and user data(not necessary but may be a good idea) you will need to re-install Superuser.apk to gain root.
Instructions:
1.) Download the version you want to use from the link below and unzip.
2.) Enable fastboot mode. Turn off your device then plug into your pc using a factory cable. If the device is recognized by adb then you can use this command:
Code:
adb shell su -c "reboot bootloader"
3.) Run the SR Tool.bat and follow the instructions. If you wish to downgrade system versions see instructions at the bottom of the post.
Downloads:
KFHD_SRT_v1.3.5- 7.3.0 (seperate option for restoring factory recovery)
KFHD_SRT_v1.3.0- 7.2.3 (separate option for restoring factory recovery)
KFHD_SRT_v1.2.3- 7.2.3
KFHD_SRT_v1.2- 7.2.1
KFHD_SRT_v1.0- 7.1.5
I apologize for the size of this tool. The .img files used are rather large. If you want to use your own backup .img then download the lastest version of this tool from here. Just place your system.img inside images folder. It must be named system for option 1 or system2 for option 2
UPDATES:
4/20/13
-separate option to restore factory recovery and boot now on v1.3.0
4/17/13
-KFHD_SRT_v1.3.5
-flashing boot and recovery images now a separate option
3/21/13
-KFHD_SRT_v1.3.0
-boot and recovery images inlcuded
-SuperSU and GoogleServicesFramework now included as system apk's
12/22/12
-KFHD_SRT_v1.2.3
-System v7.2.3
-New option for installing Googleservicesframework.apk
12/17/12
-downgrade method instructions(confirmed)
12/1/12
-KFHD_SRT_v1.2
-new system partition backups for software v7.2.1
-vending.apk to phonesky.apk for newest version of play store
Instructions for downgrading to 7.2.1:
1.) Download boot and recovery imgs(these are backus from 7.2.1) from this LINK and place in the folder where you have access to fastboot or inside the KFHD_SRTool_v1.2 folder
2.) Use KFHD_SRTool_v1.2 to flash system.img.
3.) Erase userdata and cache
4.) Open a cmd prompt from the folder where you placed the previously downloaded .img's.
Use these cmds:
Code:
fastboot -i 0x1949 flash boot boot.img
fastboot -i 0x1949 flash recovery recovery.img
5- Reboot.
Those who deserve our thanks:
kinfauns for the how to on backing up and restoring system software.
bazm60 for confirming the method above works.
hellocali626 for bringing to my attention the need to flash boot and recovery images for downgrade.
Amazing tool ... a must of you are into tinkering with your kindle
samio2 said:
Amazing tool ... a must of you are into tinkering with your kindle[/QUOT
I tried this using my system.img and the one embedded in the tool.
I keep getting this:
fastboot -i 0x1949 flash system system.img
sending 'system' (907264 KB)...
FAILED (remote: data too large)
finished. total time: 0.052s
Help?
Click to expand...
Click to collapse
Worked like a charm
I think I love you. ;-* Thank you very much.
omegamind said:
I think I love you. ;-* Thank you very much.
Click to expand...
Click to collapse
Is there a special way to install fadtboot drivers?? I don't think I'm setup right.
Can someone report what the device drivers say when in fast boot mode??
Thanks
Sent from my Galaxy Nexus using xda app-developers app
http://forum.xda-developers.com/showthread.php?t=1890413
I used the exe in the zip. Its a closed thread but it worked for me.
onemeila said:
To anyone who has downloaded or will download this update- The backups were made from software v7.2.1_user_2030320. A couple of days after I made this backup amazon sent out a second update to 7.2.1_user_2040020. That said if you use this tool with the images included, your device will update to the new version. You will lose root, launchers, and phonesky.apk. It will not cause any problems and will still restore the system but you will have to re-root. Sorry for any inconvenience and I will try to load new backups as soon as I can.
Click to expand...
Click to collapse
FWIW, I rerooted my KFHD after v7.2.1_user_2030320 was pushed. Oddly it did not lose root after it was updated to 2040020. Only change I noticed was the reappearance of ads in the start-up/lock screen. Anyone else experience the same?
RustedRoot said:
FWIW, I rerooted my KFHD after v7.2.1_user_2030320 was pushed. Oddly it did not lose root after it was updated to 2040020. Only change I noticed was the reappearance of ads in the start-up/lock screen. Anyone else experience the same?
Click to expand...
Click to collapse
Think you've gotten lucky, i've flashed mine a couple times with the 2030320 backup and when it updates it loses root every time.
Same thing happened to me. Everything worked including root.
Sent from my KFTT using Tapatalk 2
how hard would it be to add the HD 8.9 sofware into this tool?
mdblaze said:
how hard would it be to add the HD 8.9 sofware into this tool?
Click to expand...
Click to collapse
Working on it now.
onemeila said:
Working on it now.
Click to expand...
Click to collapse
How long do you expect it to take?
FroyoShark said:
How long do you expect it to take?
Click to expand...
Click to collapse
Uploading now, sorry got distracted over the holidays.
onemeila said:
Uploading now, sorry got distracted over the holidays.
Click to expand...
Click to collapse
@onemeila, have you confirmed that a factory cable works on the KFHD to put it into Fastboot? Thanks
SkOrPn said:
@onemeila, have you confirmed that a factory cable works on the KFHD to put it into Fastboot? Thanks
Click to expand...
Click to collapse
Yes it works on the KFHD 7" and KF2 7", It does not work on the 8.9" version however it is not needed because you can use a fastboot command with product id while powering on and works everytime, even when no adb and in bootloop(confirmed personally all of the above)
Hope you don't mind I've directed a few people to your link for factory cables.
onemeila said:
Yes it works on the KFHD 7" and KF2 7", It does not work on the 8.9" version however it is not needed because you can use a fastboot command with product id while powering on and works everytime, even when no adb and in bootloop(confirmed personally all of the above)
Hope you don't mind I've directed a few people to your link for factory cables.
Click to expand...
Click to collapse
No I do not mind, lol... However, I do not own any of these devices and yet people keep asking me if it will work on their device. I keep seeing different reports on the subject and do not want to be giving out false hope. I will update my list of confirmed devices.
Thanks for all the work you do to help the Kindle community :good: and thanks for the positive endorsement on my Factory Cable...
Best Regards
SkOrPn
SkOrPn said:
No I do not mind, lol... However, I do not own any of these devices and yet people keep asking me if it will work on their device. I keep seeing different reports on the subject and do not want to be giving out false hope. I will update my list of confirmed devices.
Thanks for all the work you do to help the Kindle community :good: and thanks for the positive endorsement on my Factory Cable...
Best Regards
SkOrPn
Click to expand...
Click to collapse
Thank you for making such high quality cables at such a reasonable price. I would order one myself but had already made mine before I saw your post and now have upgraded to the 8.9 which scared me when my cable wouldn't work on it, haha Amazon was prolly trying to lock it down more but managed to make it easier
If I have the 7.2.2 update on KFHD 7", Can this be used to revert back to 7.2.1 so that we can root again?
DssTrainer said:
If I have the 7.2.2 update on KFHD 7", Can this be used to revert back to 7.2.1 so that we can root again?
Click to expand...
Click to collapse
im testing that out right now. i'll get back to u...
Any news about downgrade from 7.2.2 to 7.2.1 using ths tool?!
Thx
Related
I know there have been similar threads, and I'm sorry that I'm raising another one. But reading to all those old topics didn't help me.
It's a friend's i9020T, bought in the US, so returning it back would be a real problem. He never unlocked bootloader, never applied any custom ROMs or Recovery, always updated it over OTA, and sometime in November, after reboots, phone started to hang on Google logo. Usually, it helped to remove the battery and wait some time, but it doesn't any more. We tried to remove it for a full day, didn't helped.
I tried going into recovery and doing full wipe and cache wipe - didn't help
I tried to unlock the bootloader, can select 'Yes', apply it via Power button, but the phone hangs.
If I want to flash anything with fastboot (boot, system img), it complains about locked bootloader
I tried Odin as well, but can't trick the phone into download mode with both volume up and down, again reports to unlock the bootloader
Is there any way to and how to fix this? I cannot transfer anything to internal memory, have stock recovery?
Thanks a lot to all of those who are willing to help, and I've really want to somehow fix the phone, because I don't have here in Serbia where to repair it. Several mobile providers only imported i9023, so they can't fix i9020T
I'm having the exact same problem with a GT-i9020 so would be interested in any help on this!
May need to format phone. Basically reflash latest update via boot loader. Wipe system to factory. And wipe sd
Sent from my Full Android on Crespo using Tapatalk
RANDYRKELLY said:
May need to format phone. Basically reflash latest update via boot loader. Wipe system to factory. And wipe sd
Sent from my Full Android on Crespo using Tapatalk
Click to expand...
Click to collapse
but I downloaded 2.3.6 stock from here, unpacked in the same folder where adb and fastboot are, and tried to do fastboot flash boot boot.img and so, and didn't work, was bugging me that bootloader isn't unlock
Highl1 said:
but I downloaded 2.3.6 stock from here, unpacked in the same folder where adb and fastboot are, and tried to do fastboot flash boot boot.img and so, and didn't work, was bugging me that bootloader isn't unlock
Click to expand...
Click to collapse
That's the problem dude u don't unpack it. U need to leave as a update zip. Look on xda for the stock 4.0.3 update zip or wait till I provide link. U go thru stock recovery if unrooted, and flash with it. To unlock boot loader u need to be in fastboot and type fastboot oem unlock. But u wait first. Lets get it booted. I'll find link.
Sent from my Full Android on Crespo using Tapatalk
Read here
http://www.androidcentral.com/how-manually-update-your-gsm-nexus-s-ice-cream-sandwich
Sent from my Full Android on Crespo using Tapatalk
RANDYRKELLY said:
That's the problem dude u don't unpack it. U need to leave as a update zip. Look on xda for the stock 4.0.3 update zip or wait till I provide link. U go thru stock recovery if unrooted, and flash with it. To unlock boot loader u need to be in fastboot and type fastboot oem unlock. But u wait first. Lets get it booted. I'll find link.
Sent from my Full Android on Crespo using Tapatalk
Click to expand...
Click to collapse
I'll wait for your link and instructions, it's obvious that I am doing something wrong
Thanks mate!
RANDYRKELLY said:
Read here
http://www.androidcentral.com/how-manually-update-your-gsm-nexus-s-ice-cream-sandwich
Sent from my Full Android on Crespo using Tapatalk
Click to expand...
Click to collapse
But I have stock recovery and can't copy anything to internal memory, since my phone doesn't boot
Highl1 said:
I know there have been similar threads, and I'm sorry that I'm raising another one. But reading to all those old topics didn't help me.
It's a friend's i9020T, bought in the US, so returning it back would be a real problem. He never unlocked bootloader, never applied any custom ROMs or Recovery, always updated it over OTA, and sometime in November, after reboots, phone started to hang on Google logo. Usually, it helped to remove the battery and wait some time, but it doesn't any more. We tried to remove it for a full day, didn't helped.
I tried going into recovery and doing full wipe and cache wipe - didn't help
I tried to unlock the bootloader, can select 'Yes', apply it via Power button, but the phone hangs.
If I want to flash anything with fastboot (boot, system img), it complains about locked bootloader
I tried Odin as well, but can't trick the phone into download mode with both volume up and down, again reports to unlock the bootloader
Is there any way to and how to fix this? I cannot transfer anything to internal memory, have stock recovery?
Thanks a lot to all of those who are willing to help, and I've really want to somehow fix the phone, because I don't have here in Serbia where to repair it. Several mobile providers only imported i9023, so they can't fix i9020T
Click to expand...
Click to collapse
First download this : http://www.4shared.com/zip/2L09-JyW/Root_Nexus_S.html
Just unpack , connect your device and click run.bat - that will root your phone and installed new ClockWordMod Recovery
After that you need : remove install-recovery.sh just in .....
run in windows-> Start->at the search bar write cmd and navigate into your android sdk is installed
For me :
C:/"Programs and Files (x86)"/Android/android-sdk/tools/>adb shell
# rm /system/etc/install-recovery.sh
#exit
or with Root Explorer into system/etc/install-recovery.sh just renam it (ex. : .sh.old)
surdu_petru said:
First download this : http://www.4shared.com/zip/2L09-JyW/Root_Nexus_S.html
Just unpack , connect your device and click run.bat - that will root your phone and installed new ClockWordMod Recovery
After that you need : remove install-recovery.sh just in .....
run in windows-> Start->at the search bar write cmd and navigate into your android sdk is installed
For me :
C:/"Programs and Files (x86)"/Android/android-sdk/tools/>adb shell
# rm /system/etc/install-recovery.sh
#exit
or with Root Explorer into system/etc/install-recovery.sh just renam it (ex. : .sh.old)
Click to expand...
Click to collapse
Same thing mate, I ran it, click two times in console, can't unlock the bootloader, I always get stuck on it
Trying to update the drivers for Nexus S : http://www.4shared.com/rar/_bgEMHqk/Nexus_S_Drivers_x86__x64.html
and after that try to run.bat...Good luck!
I'll try today, but my problem is that adb cannot find the device, fastboot can
I would try downloading the full OTA from this thread, rename it to update.zip (for easy typing), place it in a directory where you can run fastboot, then use the command:
Code:
fastboot update update.zip
I got an error
archive does not contain 'android-info.txt'
archive does not contain 'android-product.txt'
error: update package has no android-info.txt or android-product.txt
Should I create android-info.txt (how?) and place it into the zip (where?)
Thanks.
<edit> I saw this topic http://forum.xda-developers.com/showthread.php?t=1131588 and followed this http://forum.xda-developers.com/showthread.php?t=884416&highlight=STOCK but that as well complains about a locked bootloader </edit>
Is the problem solved？
szk5230 said:
Is the problem solved？
Click to expand...
Click to collapse
Not so far, I'm still having trouble with the phone, and no solution so far helped
Highl1 said:
I got an error
archive does not contain 'android-info.txt'
archive does not contain 'android-product.txt'
error: update package has no android-info.txt or android-product.txt
Should I create android-info.txt (how?) and place it into the zip (where?)
Thanks.
<edit> I saw this topic http://forum.xda-developers.com/showthread.php?t=1131588 and followed this http://forum.xda-developers.com/showthread.php?t=884416&highlight=STOCK but that as well complains about a locked bootloader </edit>
Click to expand...
Click to collapse
Sorry my bad, haven't tried that before either...
If it bugs you the bootloader isn't unlcoked before flashing can't you just use
fastboot oem unlock
then commence with flashing your stock image?
Edit - Nevermind...I see you tried that.
any other suggestion? I'm out of ideas
I had this problem in December. I tried everything you tried without any luck so eventually took it back for warranty repair. Unfortunately I had some water damage from 9 months before so they wouldn't touch it. Luckily I got it replaced on my phone insurance but they said it couldn't repaired.
As far as I know it's a hardware fault. With CWM it looked like I could transfer files into the sd but they would disappear! I was able to use Fastboot and Odin but no joy. I had the same errors when trying to apply update using fastboot and never found answers about the "missing" files.
Sorry to come with bad news and good luck! I'm worried it'll happen to my replacement handset so keen to know if you resolve it.
Introducing.... Superboot!
Superboot is a boot.img that when booted, will root your device the first time you boot (installing su and the superuser APK). No need to flash any partitions, no need to mess around with ADB, no messing with the contents of your data partition, no overwriting the shipped ROM on your device, just boot the boot image using the instructions below and you're done!
APPLY THIS AT YOUR OWN RISK!
Superboot r4 - DOWNLOAD - MD5: f53825a2df09277f899b6738b3a059d5
How to use Superboot - Windows, Linux and OSX
- Download the Superboot zip file above and extract to a directory
- Put your device in bootloader mode - Turn off the phone then turn on with the 'volume up' and 'volume down' buttons both pressed to enter the bootloader (as pictured below)
- WINDOWS - double click 'superboot-windows.bat'
- MAC - Open a terminal window to the directory containing the files, and type 'chmod +x superboot-mac.sh' followed by './superboot-mac.sh'
- LINUX - Open a terminal window to the directory containing the files, and type 'chmod +x superboot-linux.sh' followed by './superboot-linux.sh'
Note: If you are using a retail device, you may need to unlock the bootloader first, using './fastboot-windows oem unlock' (or the appropriate version for your machine, included in this zip). Note that the OEM unlock sequence wipes your device, so consider doing an 'adb backup' beforehand if required!
Enjoy!
P
Awesome!!!!! Can't wait for my nexus 7 :thumbup::beer:
Sent from my SAMSUNG-SGH-I717 using xda app-developers app
glad to see u here Paul. any plans on a cwm or are you using the one available in the other root thread? I see u porting superboot everywhere, awesome!
I'll probably just use the CWM already made, unless there's a good reason to make a new one?
P
paulobrien said:
I'll probably just use the CWM already made, unless there's a good reason to make a new one?
P
Click to expand...
Click to collapse
I just wasn't sure who even made the other n I prefer using stuff by well known devs that's all. when I get mine I'll try porting our cannibal touch recovery from the kfire with sblood86 n drew.
Sent from my Amazon Kindle Fire using xda premium
This is outstanding news. Im ready for my nexus 7 to hit my door. Believe it or not this will be my first nexus device and I cant wait. Thanks paul o brian :thumbup::beer:
Sent From A Rotary Phone
Download Counter
Does SuperBoot change the download counter from 0 to "Custom Downloads 1"?
Glenn
weltwon said:
Does SuperBoot change the download counter from 0 to "Custom Downloads 1"?
Glenn
Click to expand...
Click to collapse
There is no custom download counter on the N7 is there?
P
So does this unlock the bootloader?
Bilge656 said:
So does this unlock the bootloader?
Click to expand...
Click to collapse
paulobrien said:
Note: You need to unlock the bootloader in order to use this Superboot. Note that the OEM unlock sequence wipes your device.
Click to expand...
Click to collapse
Reading carefully before flashing helps reduce frustration. (old chinese proverb)
paulobrien said:
I'll probably just use the CWM already made, unless there's a good reason to make a new one?
P
Click to expand...
Click to collapse
Twrp is a good enough reason
Makes flashing Roms on my prime effortless.
I need a hand. Can't seem to get the USB drivers to work. I keep getting device not found
Sent from my Nexus 7 using Tapatalk 2
tried this 3 times... no joy.. no root. the ota jb update was applied before i did this..............would that screw it up??
patterone said:
tried this 3 times... no joy.. no root. the ota jb update was applied before i did this..............would that screw it up??
Click to expand...
Click to collapse
No...
P
Sent from my GT-I9300 using Tapatalk 2
patterone said:
tried this 3 times... no joy.. no root. the ota jb update was applied before i did this..............would that screw it up??
Click to expand...
Click to collapse
See if you have any luck with wugfresh that's how I got rooted
Sent from my Nexus 7 using Tapatalk 2
I was having trouble with the other two methods once inside CWM (something to do with the Windows driver), but this worked flawlessly. I can live without CWM for now.
Mogster said:
I was having trouble with the other two methods once inside CWM (something to do with the Windows driver), but this worked flawlessly. I can live without CWM for now.
Click to expand...
Click to collapse
Awesome, enjoy!
P
I've got a question I hope won't bother you to answer, Paul.
My goal with my Nexus 7 when it arrives is to be able to load up Titanium Backup Pro and restore some of my Games (App+Data). I' d like to know if I understand the process right to get to that point and still be able to receive OTA updates.
The first thing I should do when I turn on my device is boot into the bootloader and oem fastboot unlock.
Next, I should follow your instructions to chmod and install the superboot package.
When my device reboots after this, should I be able to update to 4.1.1 and retain root so I can install TBpro?
Brigaid said:
I've got a question I hope won't bother you to answer, Paul.
My goal with my Nexus 7 when it arrives is to be able to load up Titanium Backup Pro and restore some of my Games (App+Data). I' d like to know if I understand the process right to get to that point and still be able to receive OTA updates.
The first thing I should do when I turn on my device is boot into the bootloader and oem fastboot unlock.
Next, I should follow your instructions to chmod and install the superboot package.
When my device reboots after this, should I be able to update to 4.1.1 and retain root so I can install TBpro?
Click to expand...
Click to collapse
Upgrade first then unlock and root 4.1.1
Worked for me
MB860, CM7.2.0, Faux 026b1 1Ghz
Thanks, I'm happy to hear it works.
Brand new user here! So much info on this site; truly amazing
I have read so much, but still can't seem to figure out the best, error free method to root the TF700.
- New tablet that I bought 5 days ago.
I understand how to unlock as that's simple.
I understand I need to install TWRP.
After reading a website on androidcentral, I got the impression I need to start the Fastboot tool in Windows, and boot tablet into Fastboot mode, connect to PC...ect.
XDA forums suggests downgrading the firmware and using MOTOCHOPPER
Also, someone said to just install Scott's recovery install tool and rooting will be an option.
Any help would be great as I don't want to mess up my new toy!!!!!
Bryan480 said:
Any help would be great as I don't want to mess up my new toy!!!!!
Click to expand...
Click to collapse
Very understandable!
Downgrading to .8 and using Motochopper is useless by now. That was the easiest method to get TWRP on your tab. You would root and use GooManager to install TWRP. But Goo doesn't support flashing recoveries anymore - so root doesn't get you any closer to getting a custom recovery and a custom rom.
You have to use the fastboot method now (and need to be unlocked for that).
If you are new to this, you may want to read this:
http://forum.xda-developers.com/showthread.php?t=2277112
Scott's tool is a possibility but hasn't been updated or supported in quite a while. I would recommend the Minimal ADB Fastboot Tool:
http://forum.xda-developers.com/showthread.php?t=2317790
Or you go for the whole enchilada and install the SDK Developer tool on your PC.
http://developer.android.com/sdk/installing/index.html
Which is kinda overkill if you don't want to develop stuff for Android. What you really need out of that package is the Platform Tools.
Either way - get the correct drivers installed on your PC and fastboot TWRP 2.6.1 or 2.6.3.1 (I prefer the earlier version) onto your tab.
Then flash away :cyclops:
berndblb said:
Downgrading to .8 and using Motochopper is useless by now. That was the easiest method to get TWRP on your tab. You would root and use GooManager to install TWRP. But Goo doesn't support flashing recoveries anymore - so root doesn't get you any closer to getting a custom recovery and a custom rom.
Click to expand...
Click to collapse
While it is true that GooManager downloads no longer work, it is still possible to install a recovery from a rooted Android using dd to mmcblk0p4. But it is a good idea to do it via fastboot, just to learn how that works in case one really needs it.
Hello
Thank you so much for the reply!!
So I basically need to install the ADB fastbood on my PC and connect my TF700 to my PC via USB?
Do I need to install it on my TF700 also?
Bryan480 said:
Hello
Thank you so much for the reply!!
So I basically need to install the ADB fastbood on my PC and connect my TF700 to my PC via USB?
Do I need to install it on my TF700 also?
Click to expand...
Click to collapse
No you put your TF700 into fast boot mode by booting into the bootloader by holding down power and Volume Down when powering on.
First make sure you have downloaded the correct TWRP recovery blob file for your device from the TeamWin webpage. Use their search to find and choose the blob image for JB4.2 for the TF700T.
Rename it to twrp.blob and put it into the same folder as the fast boot.exe file
Then with it connected to your PC via USB, open a command window in the fastboot.exe folder (shift, right click, open command window here) and type or paste the following one line at a time. Wait for each line to finish:
Code:
TWRP:
fastboot -i 0x0B05 flash recovery twrp.blob
fastboot -i 0x0B05 reboot bootloader
When it reboots back into the bootloader pressing the volume down on ECK will now load TWRP
Hello
Think I understand most of this...
Do I need to do anything with USB debug?
When I open command window, due I include TWRP: in each line, or is that not needed?
And what is volume down on ECK?
Sorry If I sound like an idiot; this is all new to me.
Thank you so much!
Bryan480 said:
Hello
Think I understand most of this...
Do I need to do anything with USB debug?
When I open command window, due I include TWRP: in each line, or is that not needed?
And what is volume down on ECK?
Sorry If I sound like an idiot; this is all new to me.
Thank you so much!
Click to expand...
Click to collapse
Omit the TWRP ahead of the fastboot command. I think sbdags meant to write that outside of the code marks.
He's a busy man....
ECK is a typo. Supposed to be RCK, the icon for your recovery in the bootloader menu. And you have to push Volume UP on the flashing icon to enter it. Volume Down let's you cycle through the icons.
He's a busy man
Sent from my DROID4 using Tapatalk
berndblb said:
Omit the TWRP ahead of the fastboot command. I think sbdags meant to write that outside of the code marks.
He's a busy man....
ECK is a typo. Supposed to be RCK, the icon for your recovery in the bootloader menu. And you have to push Volume UP on the flashing icon to enter it. Volume Down let's you cycle through the icons.
He's a busy man
Sent from my DROID4 using Tapatalk
Click to expand...
Click to collapse
Oops yep ignore the TWRP: bit and also ECK should be RCK
Ok great
I'm going to try this and will report back!
Thanks again
Hello,
I just want to make sure I have the correct bootloader before I do this, as I don't want to break my new toy!!
My tablet is new...just bought about a week ago.
Thank you so much!!
You guys are great!
Well, if you have a 10.6.1.14.x bootloader, you're good to go.
Sent from my DROID4 using Tapatalk
ok so this has been such a pain!
I can't unlock the tab!
All I want to do it install TWRP via fastboot( i have the TWPR file, and installed fastboot onto my WIN 7 PC) and install a custom rom!
Please help I will donate
I'm and work and plan on trying again tonight.
Bryan480 said:
ok so this has been such a pain!
I can't unlock the tab!
All I want to do it install TWRP via fastboot( i have the TWPR file, and installed fastboot onto my WIN 7 PC) and install a custom rom!
Please help I will donate
I'm and work and plan on trying again tonight.
Click to expand...
Click to collapse
What happens when you try to unlock? Need more info.
Bryan480 said:
ok so this has been such a pain!
I can't unlock the tab!
All I want to do it install TWRP via fastboot( i have the TWPR file, and installed fastboot onto my WIN 7 PC) and install a custom rom!
Please help I will donate
I'm and work and plan on trying again tonight.
Click to expand...
Click to collapse
My recent experience with unlocking:
http://www.transformerforums.com/fo...ent/40226-my-recent-unlocking-experience.html
Dave
ok I finally got it to work after at least 15 attempts. Maybe because I bought on ebay?
Flash time.
I flashed TWRP
I put the reboot code...how long does it take?
Bryan480 said:
I flashed TWRP
I put the reboot code...how long does it take?
Click to expand...
Click to collapse
Less than a minute - are you unlocked now?
Success!!
FINALLLY got everything to work; so easy once I figured it out.
I installed _that's v4, didn't disable fsync....to scared!!
Any other ideas for a first time user?
I'm looking to conserve battery, but also would like good performance.
Oh yeah and how can I get rid of the 5 home screens?!?!
Thanks for everything
Bryan480 said:
Success!!
FINALLLY got everything to work; so easy once I figured it out.
I installed _that's v4, didn't disable fsync....to scared!!
Any other ideas for a first time user?
I'm looking to conserve battery, but also would like good performance.
Oh yeah and how can I get rid of the 5 home screens?!?!
Thanks for everything
Click to expand...
Click to collapse
Well done and welcome aboard. If you want to change the launcher settings you should flash Apex or Nova launcher from the installer and then you can mess with all sorts of things The stock launcher can't be changed.
Bryan480 said:
Success!!
FINALLLY got everything to work; so easy once I figured it out.
I installed _that's v4, didn't disable fsync....to scared!!
Any other ideas for a first time user?
I'm looking to conserve battery, but also would like good performance.
Oh yeah and how can I get rid of the 5 home screens?!?!
Thanks for everything
Click to expand...
Click to collapse
When you have your system up and running the way you want, go back to your TWRP and do a nandroid backup. After the backup, you can disable your Fsync. The worse case is to restore your back or reinstall your rom but you will enjoy your tablet more with Fsync off...
Hi there,
A while ago I got a OnePlus One which came with ColorOS loaded. I of course googled my way to get the Cyanogenmod and followed these instructions.
http://www.youtube.com/watch?v=QDKOEtN9pbo
I'm currently on the 25R firmware and I know there are some updates after that but the phone doesnt detect any update release. I would like to know why the OTA updates are not being picked up from the phone. Was it simply the easy method mentioned above?
I also thought of reflashing it properly and found some instructions on the web.
Code:
Install Android tools (and drivers if you use Windows-crap). You need the fastboot and adb tools
Get http://dist01.slc.cy...ed-fastboot.zip and unpack it
Enable USB debugging on the phone
Run adb reboot-bootloader
Once bootloader started run: fastboot oem unlock
After automatic reboot, do steps 3 & 4 again
In the directory where you unpacked it, run in a console
fastboot flash modem NON-HLOS.bin
fastboot flash sbl1 sbl1.mbn
fastboot flash dbi sdi.mbn
fastboot flash aboot emmc_appsboot.mbn
fastboot flash rpm rpm.mbn
fastboot flash tz tz.mbn
fastboot flash LOGO logo.bin
fastboot flash boot boot.img
fastboot flash cache cache.img
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot flash userdata userdata_64g.img (or userdata.img for 16G version)
fastboot oem lock
fastboot reboot
These instructions will somehow get the OTA updates working, am I right to assume that this method would rewrite everything and I would lose the recovery software of the ColorOS? Also are the Android tools these?
http://developer.android.com/sdk/index.html
Fastboot and ADB, I can use this one right?
http://forum.xda-developers.com/showthread.php?t=2588979
I appreciate the help and a few explanations.
Cheers.
Just download this
http://builds.cyngn.com/fota/incremental/bacon/cm-bacon-ac1ccf7921-to-5fa8c79c0b-signed.zip
Sent from my A0001 using XDA Premium 4 mobile app
scabbie1980 said:
Just download this
http://builds.cyngn.com/fota/incremental/bacon/cm-bacon-ac1ccf7921-to-5fa8c79c0b-signed.zip
Sent from my A0001 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Hi scabbie, from the looks of the file its an incremental update. Do I just run it from the OPO with Cyanogenmod? If this is a long tedious method, I would rather do a fresh install and get the OTA updates to work. Also part of the reason I want a clean install is because the phone is acting up and my screen goes black when I call someone and then when I want to hang up the screen is still black and I cant hang up. and physical buttons dont respond either.
I dont know if this incremental update will fix this kind of problem, so hence my option to do some clean install.
Cheers
dude777 said:
Hi scabbie, from the looks of the file its an incremental update. Do I just run it from the OPO with Cyanogenmod? If this is a long tedious method, I would rather do a fresh install and get the OTA updates to work. Also part of the reason I want a clean install is because the phone is acting up and my screen goes black when I call someone and then when I want to hang up the screen is still black and I cant hang up. and physical buttons dont respond either.
I dont know if this incremental update will fix this kind of problem, so hence my option to do some clean install.
Cheers
Click to expand...
Click to collapse
If you're looking for a completely fresh install, just go to my guide thread (link in signature) and follow section 8.
Transmitted via Bacon
OK, for a clean download you need to download this in fastboot mood
https://www.copy.com/s/hMXtmkJAbDhjxQyC
Sent from my A0001 using XDA Premium 4 mobile app
---------- Post added at 02:01 PM ---------- Previous post was at 01:56 PM ----------
scabbie1980 said:
OK, for a clean download you need to download this in fastboot mood.
https://www.copy.com/s/hMXtmkJAbDhjxQyC
Look on YouTube on how to use this toolbox and it will completely wipe your phone then flash clean.
Sent from my A0001 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Sent from my A0001 using XDA Premium 4 mobile app
scabbie1980 said:
OK, for a clean download you need to download this in fastboot mood
https://www.copy.com/s/hMXtmkJAbDhjxQyC
Sent from my A0001 using XDA Premium 4 mobile app
---------- Post added at 02:01 PM ---------- Previous post was at 01:56 PM ----------
Sent from my A0001 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
A toolbox is completely unnecessary, and they're more trouble than they're worth. Plus, nobody learns anything even using a toolbox, and that knowledge is crucial for when things go wrong.
Transmitted via Bacon
DON'T use a toolbox please
Learn as you go by doing things properly, I speak from my own experience. These skills and knowledge that you gain will help if you ever run into any issues
Go here to install the adb drivers computer wide so you can flash from any folder on your computer, it makes your life so much easier
http://forum.xda-developers.com/showthread.php?t=2588979
Then follow timmaaa guide on how to start fresh with a complete 44s ROM
Sent from my A0001 using XDA Free mobile app
Thanks guys for the effort here, really like your guides timmaaa very clear and non confusing. Yes I would like to avoid shortcuts as I took the easy route and now the phone goes in hiatus moment when calling. I'll get around this in the weekend and see how that goes.
Cheers.
@ timmaaa
Love the guide you put up, I was having a read through this and I'm slightly confused on your comments. http://forum.xda-developers.com/one...-to-guides-t2839471/post56731494#post56731494
You mentioned just go straight to Section 8, but in the link above you mentioned go through 1-4 then go to 8. I dont think I need to root on section 4 but for 1, 2 and 3, I would like to know, particularly in section 2 and 3 if you can explain to a novice like me. As I'm understanding this, I think the ColorOS phone has some recovery software, thats how I did the easy flashing method thing, so for section 2 your instructions will overwrite the ColorOS one?
For Section 3 the nandroid backup seems like a snapshot of the phone (which includes recovery, phone OS and other things) before installing custom rom?
Please let me know if my interpretation is correct and correct me along the way, I am here to learn what I can, so that I can successfully flash the OPO phone.
Cheers.
dude777 said:
@ timmaaa
Love the guide you put up, I was having a read through this and I'm slightly confused on your comments. http://forum.xda-developers.com/one...-to-guides-t2839471/post56731494#post56731494
You mentioned just go straight to Section 8, but in the link above you mentioned go through 1-4 then go to 8. I dont think I need to root on section 4 but for 1, 2 and 3, I would like to know, particularly in section 2 and 3 if you can explain to a novice like me. As I'm understanding this, I think the ColorOS phone has some recovery software, thats how I did the easy flashing method thing, so for section 2 your instructions will overwrite the ColorOS one?
For Section 3 the nandroid backup seems like a snapshot of the phone (which includes recovery, phone OS and other things) before installing custom rom?
Please let me know if my interpretation is correct and correct me along the way, I am here to learn what I can, so that I can successfully flash the OPO phone.
Cheers.
Click to expand...
Click to collapse
I was assuming that because you're on the 25R build of CM11S that you've already unlocked your bootloader and installed TWRP recovery, if this isn't the case then you will need to follow sections 1, 2, and 3 before moving on to section 8.
The phone definitely already has some kind of recovery on it (every phone does), but you do need to install a custom recovery in order to make a backup of your current ROM. It will overwrite the existing recovery when you install it, and then later on when you flash the fastboot images (in section 8) the stock recovery will overwrite the custom recovery. So why bother flashing the custom recovery if it'll just be overwritten? Because insurance. It'll allow you to make a nandroid backup of your current setup to fall back on just in case something goes wrong.
A nandroid is like a snapshot of the phone, but it doesn't include your recovery partition, it includes the /system partition (where the os resides), the /data partition (where your apps and settings reside), and the /boot partition (the kernel). You should always have at least one nandroid on your phone at all times. Personally, I make one before I flash anything, that way if I don't like whatever I'm flashing or if something goes wrong, I can just restore my backup and boot the phone up, and it's exactly how I left it.
After you've made your backup make sure you transfer it to your PC (and anything else important on the phone), because flashing the fastboot images is going to wipe your whole phone, including all of your user data.
If you have any other questions please don't hesitate to ask.
Transmitted via Bacon
timmaaa said:
I was assuming that because you're on the 25R build of CM11S that you've already unlocked your bootloader and installed TWRP recovery, if this isn't the case then you will need to follow sections 1, 2, and 3 before moving on to section 8.
The phone definitely already has some kind of recovery on it (every phone does), but you do need to install a custom recovery in order to make a backup of your current ROM. It will overwrite the existing recovery when you install it, and then later on when you flash the fastboot images (in section 8) the stock recovery will overwrite the custom recovery. So why bother flashing the custom recovery if it'll just be overwritten? Because insurance. It'll allow you to make a nandroid backup of your current setup to fall back on just in case something goes wrong.
A nandroid is like a snapshot of the phone, but it doesn't include your recovery partition, it includes the /system partition (where the os resides), the /data partition (where your apps and settings reside), and the /boot partition (the kernel). You should always have at least one nandroid on your phone at all times. Personally, I make one before I flash anything, that way if I don't like whatever I'm flashing or if something goes wrong, I can just restore my backup and boot the phone up, and it's exactly how I left it.
After you've made your backup make sure you transfer it to your PC (and anything else important on the phone), because flashing the fastboot images is going to wipe your whole phone, including all of your user data.
If you have any other questions please don't hesitate to ask.
Transmitted via Bacon
Click to expand...
Click to collapse
I see, so even if my phone doesnt have much inside it should still be recommended, because of the listed above are operational and if something were to happen on the newly flashed phone, I have no way of retracing my steps.
So in a hypothetical situation I unlocked the bootloader and proceed to section 2. The recovery software provided when I first got the phone will be overwritten by the TWRP recovery and I will have lost the old one. I will then perform a nandroid backup where I can preserve a last known working configuration as an insurance, if future flashes fail. I assume you restore nandroid backup through the TWRP recovery? Also the nandroid backup is made on the phone? so I will need to transfer that to my PC before flashing?
At this stage all I changed is the bootloader and recovery partition with custom recovery. When I jump to section 8 it should be smooth sailing, provided I follow them clearly and the drivers work on the PC.
I apologise for being a pain in the butt! I just like to clarify before I do something horrible and have no idea what to do next.
Cheers
dude777 said:
I see, so even if my phone doesnt have much inside it should still be recommended, because of the listed above are operational and if something were to happen on the newly flashed phone, I have no way of retracing my steps.
So in a hypothetical situation I unlocked the bootloader and proceed to section 2. The recovery software provided when I first got the phone will be overwritten by the TWRP recovery and I will have lost the old one. I will then perform a nandroid backup where I can preserve a last known working configuration as an insurance, if future flashes fail. I assume you restore nandroid backup through the TWRP recovery? Also the nandroid backup is made on the phone? so I will need to transfer that to my PC before flashing?
At this stage all I changed is the bootloader and recovery partition with custom recovery. When I jump to section 8 it should be smooth sailing, provided I follow them clearly and the drivers work on the PC.
I apologise for being a pain in the butt! I just like to clarify before I do something horrible and have no idea what to do next.
Cheers
Click to expand...
Click to collapse
You do indeed restore a nandroid backup with the recovery that you made the backup with. And yes it is saved on the phone so you will need to transfer it to your PC. You're not being a pain in the butt, you're doing the right thing and researching before attempting something.
Transmitted via Bacon
Yeah I agree users like you that research crap before attempting something are much preferred over users that blindly use a toolbox then come complaining cuz they messed something up but dunno how to fix it. I always do my research before flashing just like you are doing. Just make sure you install the drivers I linked to computer wide on your windows computer and you should have no problems, no need to install separate SDK for android and copy the files you're flashing into a special folder, etc
info update
Hey guys, noob here. I wanted to update to the most recent version and I am running version: XNPH25R atm.
Anyone could be so kind to tell me what's the easiest way to to this? I have a 64gb chinese version.
If you follow timmaaa's guide you should be good to go. I'm a noob myself and just did it over the weekend and its a blast. Good luck
Cheers
maeishoj said:
Hey guys, noob here. I wanted to update to the most recent version and I am running version: XNPH25R atm.
Anyone could be so kind to tell me what's the easiest way to to this? I have a 64gb chinese version.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2839471
Transmitted via Bacon
maeishoj said:
Hey guys, noob here. I wanted to update to the most recent version and I am running version: XNPH25R atm.
Anyone could be so kind to tell me what's the easiest way to to this? I have a 64gb chinese version.
Click to expand...
Click to collapse
Lol really? Did u completely ignore reading the thread that you just posted in??
[emoji15] [emoji58]
I signed up for a beta test on centernode and received a smartphone to test. The phone is so new that I cannot find any information about it on the internet. The bootloader is unlocked on it. I was reading that you can use magisk to root any device with an unlocked bootloader and system image. Since the phone is so new I cannot find a system image. Is it still possible to root the device? Is there a way I can backup the stock ROM and create a system image that way? Is there something else that will work? I really want to root the device because it came with a preinstalled app which is a system booster type app. It will not let me uninstall it, disable it, or force stop it. When I install my app for my alarm clock it keeps killing the app and the alarm will not go off. I have went through all of the app settings and cannot get it to stop. It also keeps interfering with my VPN. I would also like to root th device to remove some of the bloatware and to have access to the HOST file. Could someone please help me this? I would greatly appreciate it. Thanks guys!
I'm not known for giving good advice but if I was in your situation I would try to install the lastest version of Magisk and hope for the best. Knowing how I am it would be driving me nuts wondering if it would work.
That booster app, have you tried uninstalling it with adb?
Gregbmil1 said:
I'm not known for giving good advice but if I was in your situation I would try to install the lastest version of Magisk and hope for the best. Knowing how I am it would be driving me nuts wondering if it would work.
That booster app, have you tried uninstalling it with adb?
Click to expand...
Click to collapse
Hey, thanks for your reply. I am really eager to root it. I almost just went for it. However, then I thought about it. If something went wrong I would not have any way to recover the phone since there is not a system image available yet. I have not given adb removal a try yet as I figure it would just be easier to go with rooting since it will help me with everything I am trying to achieve. If I cannot root it then I will go the adb route. Hopefully someone will come along and help me out. Fingers crossed
Let us know what you end up doing. Are you expected to send the phone back after the beta testing? If you are responsible for any damages done to it, I would not try it.
You could send it back bricked and say you have no idea what happened to it, lol. That or say you were "testing" the security of the device and that it passes
bigroc2223 said:
I signed up for a beta test on centernode and received a smartphone to test. The phone is so new that I cannot find any information about it on the internet. The bootloader is unlocked on it. I was reading that you can use magisk to root any device with an unlocked bootloader and system image. Since the phone is so new I cannot find a system image. Is it still possible to root the device? Is there a way I can backup the stock ROM and create a system image that way? Is there something else that will work? I really want to root the device because it came with a preinstalled app which is a system booster type app. It will not let me uninstall it, disable it, or force stop it. When I install my app for my alarm clock it keeps killing the app and the alarm will not go off. I have went through all of the app settings and cannot get it to stop. It also keeps interfering with my VPN. I would also like to root th device to remove some of the bloatware and to have access to the HOST file. Could someone please help me this? I would greatly appreciate it. Thanks guys!
Click to expand...
Click to collapse
If you have the firmware then you're in luck (especially if it's the full one)
Download a program for windows called "Payload Dumper"
Open the zip (firmware) and copy out the payload.bin file.
Copy this to the input folder from payload dumper.
Run the exe for payload dumper
It'll output a bunch of files to output folder
You'll see a boot.img file this is essentially the file you use to boot your phone and also where magisk would reside too.
Copy this to your phone.
Install the latest Magisk then open it
Click install and then patch a file, navigate to the boot.img
Click the boot.img and it'll output a file to "SDcard\Downloads" usually called magisk_patched.img
Copy this to your fastboot folder on your computer and open a CMD / Powershell command to that location.
Then boot to fastboot / bootloader mode
Then type:
fastboot boot "name of patched boot.img"
eg:
fastboot boot magisk_patched.img
The phone will boot
From this point you are rooted but you need to make it permanent as you haven't flashed the boot sector at this point, you're only booting an image, if you were to reboot you'd lose it.
Open Magisk again then click install again.
Now instead of just seeing patch a file you'll see "Install Directly" + "Install after an OTA"
Click Install directly, allow it to finish, then reboot.
You're now fully rooted.
Heres my guides for the oneplus 8 pro, don't use the images there as they're for the 8 pro, you also can download payload dumper from there too.
(ROOT) Android 11 / Latest stock and patched img's / payload dumper / magisk_patched guides
Hi all, Have seen a lot of requests for patched boot images on these threads so thought i'd share a guide on how to get it yourself as well as all the files required, plus the patched boot.img if you just want to go ahead and boot/flash it...
forum.xda-developers.com
IT's easy.
Good luck
dladz said:
If you have the firmware then you're in luck (especially if it's the full one)
Download a program for windows called "Payload Dumper"
Open the zip (firmware) and copy out the payload.bin file.
Copy this to the input folder from payload dumper.
Run the exe for payload dumper
It'll output a bunch of files to output folder
You'll see a boot.img file this is essentially the file you use to boot your phone and also where magisk would reside too.
Copy this to your phone.
Install the latest Magisk then open it
Click install and then patch a file, navigate to the boot.img
Click the boot.img and it'll output a file to "SDcard\Downloads" usually called magisk_patched.img
Copy this to your fastboot folder on your computer and open a CMD / Powershell command to that location.
Then boot to fastboot / bootloader mode
Then type:
fastboot boot "name of patched boot.img"
eg:
fastboot boot magisk_patched.img
The phone will boot
From this point you are rooted but you need to make it permanent as you haven't flashed the boot sector at this point, you're only booting an image, if you were to reboot you'd lose it.
Open Magisk again then click install again.
Now instead of just seeing patch a file you'll see "Install Directly" + "Install after an OTA"
Click Install directly, allow it to finish, then reboot.
You're now fully rooted.
Heres my guides for the oneplus 8 pro, don't use the images there as they're for the 8 pro, you also can download payload dumper from there too.
(ROOT) Android 11 / Latest stock and patched img's / payload dumper / magisk_patched guides
Hi all, Have seen a lot of requests for patched boot images on these threads so thought i'd share a guide on how to get it yourself as well as all the files required, plus the patched boot.img if you just want to go ahead and boot/flash it...
forum.xda-developers.com
IT's easy.
Good luck
Click to expand...
Click to collapse
So it sounds like since this is a beta device and I cannot find a firmware image in out of luck?
I guess the only other option I have is finding someone who can port twrp for my device. Then I can just root via TWRP. However, from what I have read that might not even be an option as Android 11 mostly has to be rooted the hard way which you have gave instructions on above.
Can anyone think of anything else I can try?
bigroc2223 said:
So it sounds like since this is a beta device and I cannot find a firmware image in out of luck?
I guess the only other option I have is finding someone who can port twrp for my device. Then I can just root via TWRP. However, from what I have read that might not even be an option as Android 11 mostly has to be rooted the hard way which you have gave instructions on above.
Can anyone think of anything else I can try?
Click to expand...
Click to collapse
You can also extract the boot image... Can't remember the commands for this via ADB, Google ADB extract boot.img
dladz said:
You can also extract the boot image... Can't remember the commands for this via ADB, Google ADB extract boot.img
Click to expand...
Click to collapse
Awesome this is exactly what I was trying to figure out in my original post. Since there is no stock firmware available yet (beta unit) what is the best way to backup the device so I do not get a brick in the process? Thanks again for your help.
bigroc2223 said:
Awesome this is exactly what I was trying to figure out in my original post. Since there is no stock firmware available yet (beta unit) what is the best way to backup the device so I do not get a brick in the process? Thanks again for your help.
Click to expand...
Click to collapse
An actual back up? Probably twrp if available.
If not then you'd need a recovery method.
So providing you have a recovery solution you should be fine.
dladz said:
An actual back up? Probably twrp if available.
If not then you'd need a recovery method.
So providing you have a recovery solution you should be fine.
Click to expand...
Click to collapse
Ahhh okay since it is a beta device no one has made TWRP for it yet. What do you think the risk is of manually pulling the boot img, patching, and flashing is? If I can get that to work I will try to port twrp to the device. Thanks again for the help.
bigroc2223 said:
Ahhh okay since it is a beta device no one has made TWRP for it yet. What do you think the risk is of manually pulling the boot img, patching, and flashing is? If I can get that to work I will try to port twrp to the device. Thanks again for the help.
Click to expand...
Click to collapse
You're very welcome.
Chances of it not booting after doing that? Absolutely zero.
It's a copy not a cut, so you're fine.
The only problem you may encounter is the ability to access the device on that level.
Just turn on usb debugging and make sure ADB works as it should be checking on ADB devices.
Then go ahead with the pull.
You'll be fine.
Also once you have the boot.img if the patched one doesn't work then just reboot and you're back to normal.
I would advise against flashing it, just boot it.
dladz said:
Just turn on usb debugging and make sure ADB works as it should be checking on ADB devices.
Then go ahead with the pull.
You'll be fine.
Also once you have the boot.img if the patched one doesn't work then just reboot and you're back to normal.
Click to expand...
Click to collapse
You can't simply run
Code:
adb devices
adb pull boot.img > C:\boot.img
to clone phone's boot.img to PC.
The correct way is described here
Extract Boot.img Directly from Device Without Downloading Firmware
In this tutorial, we will show you the steps to extract the boot.img file directly from your device without downloading the firmware.
www.droidwin.com
jwoegerbauer said:
You can't simply run
Code:
adb devices
adb pull boot.img > C:\boot.img
to clone phone's boot.img to PC.
The correct way is described here
Extract Boot.img Directly from Device Without Downloading Firmware
In this tutorial, we will show you the steps to extract the boot.img file directly from your device without downloading the firmware.
www.droidwin.com
Click to expand...
Click to collapse
I did not say that you could?? I said pull it.
Before that I said look it up / Google it
Thanks for your help guys I appreciate it greatly. I am going to give this a try today. I will report back and let you guys know how it goes.
One last question. Since this beta unit I got is a tracfone branded unit with an unlocked bootloader is it possible that they could push a firmware which will lock the bootloader at some point? If so is there any way to prevent that from happening? Thanks again for all your help.
bigroc2223 said:
Thanks for your help guys I appreciate it greatly. I am going to give this a try today. I will report back and let you guys know how it goes.
One last question. Since this beta unit I got is a tracfone branded unit with an unlocked bootloader is it possible that they could push a firmware which will lock the bootloader at some point? If so is there any way to prevent that from happening? Thanks again for all your help.
Click to expand...
Click to collapse
Possible yes, but I doubt they would do that.
Is it an ambassador phone? Or for testing?
Locking the bootloader wipes the phone so I wouldn't imagine they'd do that without forewarning.
Plus locking a bootloader comes with its risks too, so you could say that it broke from the update.
But it won't come to that, I've had several ambassador phones myself and honestly they're fire and forget for the most part, I wouldn't worry about it
dladz said:
Possible yes, but I doubt they would do that.
Is it an ambassador phone? Or for testing?
Locking the bootloader wipes the phone so I wouldn't imagine they'd do that without forewarning.
Plus locking a bootloader comes with its risks too, so you could say that it broke from the update.
But it won't come to that, I've had several ambassador phones myself and honestly they're fire and forget for the most part, I wouldn't worry about it
Click to expand...
Click to collapse
It's a phone for testing which I am allowed to keep.
dladz said:
Possible yes, but I doubt they would do that.
Is it an ambassador phone? Or for testing?
Locking the bootloader wipes the phone so I wouldn't imagine they'd do that without forewarning.
Plus locking a bootloader comes with its risks too, so you could say that it broke from the update.
But it won't come to that, I've had several ambassador phones myself and honestly they're fire and forget for the most part, I wouldn't worry about it
Click to expand...
Click to collapse
It is a phone for testing which I am allowed to keep. Specs are Snapdragon 750g, Adreno 619, and 4gb of ram. Not too shabby for a free phone. It is a lot snappier than the moto e6 I was previously using.
dladz said:
I did not say that you could?? I said pull it.
Before that I said look it up / Google it
Click to expand...
Click to collapse
This method requires TWRP. So this will not work.
bigroc2223 said:
Nvm
Click to expand...
Click to collapse
dladz said:
Again!!!? What's your problem??
You're just trying to (for whatever reason) prove me wrong and yet again I wasn't being descriptive of an ADB pull!!!
You're pulling the boot.img off the device by whatever means.
To be clear for the final time, I'm not stating to use twrp, a script or anything else I said look it up / Google it!
Now if you've helped the chap then that's great, looking at what I said and attempting to put me straight when you clearly don't have to, is no help to you or the chap needing help it's just making you look like you're on a power trip.
Click to expand...
Click to collapse
I'm just trying to get some help here guys that's it. I appreciate everyone's efforts and opinions. Let's all try to work together and try to find a solution peacefully please.
So far I have adb installed and working. I have tried to use the commands I was able to locate via google. So far nothing works. I have also tried uninstalling some programs using adb which did not work. I think I am going to have to find someone who could port twrp for me
bigroc2223 said:
I'm just trying to get some help here guys that's it. I appreciate everyone's efforts and opinions. Let's all try to work together and try to find a solution peacefully please.
So far I have adb installed and working. I have tried to use the commands I was able to locate via google. So far nothing works. I have also tried uninstalling some programs using adb which did not work. I think I am going to have to find someone who could port twrp for me
Click to expand...
Click to collapse
Sorry I got the wrong end of the stick, I thought you was a second person posting..
Forget what I said