Related
As I've seen a few people around having some checksum erros, I decided to write a small HOWTO.
!!!
The most important information needed to recover from a bricked device is the UID
If your device is not bricked and you read this thread ensure that you have saved your UID!
!!!
Because some people do not read big red text, here it is once again:
GET YOUR UID even if your device is not bricked.
If you need help please contact me with PM or ask for help in this thread.
If your device does not boot anymore it may display the following checksum erros:
"LNX checksum error" - when trying to boot into normal mode
"SOS checksum error" - when trying to boot into recovery (VOL- + Power pressed)
<CASE 1> SOS checksum error
Steps:
- Switch off your device by pressing power for ~8sec
- Switch on your device and boot into normal mode
- If LNX checksum error is displayed, stop here and see <CASE 3>
- Download itsmagic (see this thread). Extract "itsmagic" to the tools folder of android sdk.
- Connect your device to your PC (Windows: drivers can be obtained from Acer website)
- If not already done, get your UID using Method 1 of "How to get the UID"
- If not already done, get a dump of mmcblk0_start (see "How to get a dump of mmcblk0_start")
- In the command window type:
Code:
adb push itsmagic /data/local
adb shell
su -
chmod 755 /data/local/itsmagic
/data/local/itsmagic
exit
- If everything went fine you should see some output of itsmagic
- Reboot and check if you can boot again
- Store your UID and mmcblk0_start to some safe place
Possible reasons for this error
- You tried to install a new recovery without calling itsmagic before
- You have not remove /system/etc/install-recovery.sh
- Your recovery partition is corrupt
<CASE 2> LNX checksum error
Steps:
- Switch off your device by pressing power for ~8sec
- Switch on your device and boot into recovery by pressing VOL- + Power
- If SOS checksum error is displayed, stop here and see <CASE 3>
If you have stock recovery:
- If not already done, get your UID using Method 2 of "How to get the UID"
- Apply an official OTA, see this thread
If you have thor's CWR:
- If not already done, get your UID using Method 1 of "How to get the UID".
- Select "reboot system now"
If you have any other recovery (that does not have itsmagic integrated):
- If not already done, get your UID using Method 1 of "How to get the UID". If Method 1 does not work, try Method 2
- DO NOT apply any official update.zip . Otherwise you will end up in <CASE 3>
- send me a PM or ask for help in this thread.
Possible reasons for this error
- You tried to install install a new kernel / stock update.zip without calling itsmagic (will not occur with thor's CWR)
<CASE 3> SOS and LNX checksum error
- If available, upload the "mmcblk0_start" dump to some file hoster (e.g. dropbox)
- Send me a PM with your UID and a link to "mmcblk0_start"
- If you do not have your UID: DO NOT connect your device to your PC:
- Pray that you are able to recover the UID from a PC the Iconia was already connected once.
- Windows: Try Method 2 of "How to get the UID" but DO NOT connect your device to your PC.
- Linux/Mac: Check old syslogs for messages where your device was connected to your PC (normally some "usb " kernel messages)
Possible reasons for this error
- You tried to install a new kernel athough you already have a SOS checksum error
- You tried to install a new recovery altough you aleady have a LNX checksum error
How to get the UID
Method 1
- If not already done, follow the instruction "Howto install ADB" below
- In the command shell, type:
Code:
adb devices
and press RETURN
This will output something like this:
Code:
List of devices attached
370014740c00594 device
The number is your UID.
- Save this number somewhere it won't get lost
Method 2
- Connect your device to your PC and ensure that drivers are properly installed (Windows: Can be downloaded from Acer website)
Windows:
Download this tool (download link is nearly at the end of the page):
- Open the tool
- Sort after VendorID
- Find all devices with VendorID = 0502 and ProductID = 3325. Check the "Serial number" column for these devices.
Linux:
Call (as root) and see the iSerial field for Iconia.
Code:
lsusb -v
Mac:
- Should be visible in system profiler. Sadly I don't own a mac. So if anyone can help me out with this?
How to get a dump of mmcblk0_start
- If not already done, follow the instruction "Howto install ADB" below
- In the command shell, type:
Code:
adb shell
su -
dd if=/dev/block/mmcblk0 bs=512 count=13312 of=/sdcard/mmcblk0_start
exit
exit
adb pull /sdcard/mmcblk0_start .
- This will create a file "mmcblk0_start" in the tools folder of your android-sdk.
- Copy this file to some safe place
How to install ADB
1. Download android SDK from here. Windows: Download the .zip file instead of the exe file.
2. Extract android SDK somewhere
3. Open a command shell:
- Windows: Press Winkey+R . Some small window appear. Enter "cmd" and click ok. A black command promt window will open.
- Linux/Mac: Open a terminal window
4. "cd" to the "tools" folder of the android sdk by typing the following in the command shell:
- Windows:
Code:
cd "<path to tools folder>"
Sample:
Code:
cd "c:\android\android-sdk-windows\tools"
- Linux/Mac:
Code:
cd /path/to/tools/folder
5. Ensure that your device is connected, that drivers are installed and that USB debugging is enabled (on Iconia: Settings->Applications->Development->USB Debugging)
reserved for me
Im just asking, in case3 u need dump of mmcblk0_start ,but what if dont have it, only UID?
Should i make dump of mmcblk0_start just in case to be insured that evrything will be ok if smth happens?
Any way thks fo tutorial)
Glebaka said:
Im just asking, in case3 u need dump of mmcblk0_start ,but what if dont have it, only UID?
Should i make dump of mmcblk0_start just in case to be insured that evrything will be ok if smth happens?
Any way thks fo tutorial)
Click to expand...
Click to collapse
Having a dump in <case 3> makes everything easier. But it is not mandatory. Nevertheless it's generally a good idea to backup mmcblk0_start.
btw: thor's CWR will backup mmcblk0_start since version 1.2 if you do a nandroid backup.
sc2k said:
How to get a dump of mmcblk0_start
- If not already done, follow the instruction "Howto install ADB" below
- In the command shell, type:
Code:
adb shell
dd if=/dev/block/mmcblk0 of=dd if=/dev/block/mmcblk0 bs=512 count=13312 of=/sdcard/mmcblk0_start
exit
adb pull /sdcard/mmcblk0_start .
- This will create a file "mmcblk0_start" in the tools folder of your android-sdk.
- Copy this file to some safe place
Click to expand...
Click to collapse
Hi there,
after i typed "dd if=/dev/block/mmcblk0 of=dd if=/dev/block/mmcblk0 bs=512 count=13312 of=/sdcard/mmcblk0_start" in the adb shell i got an invalid argument error:
Code:
if: illegal argument combination or already set
What i should do?
when i get a SOS checksum error and a LNX checksum error,can i copy files from pc to a500 device? how?
dmue said:
Hi there,
after i typed "dd if=/dev/block/mmcblk0 of=dd if=/dev/block/mmcblk0 bs=512 count=13312 of=/sdcard/mmcblk0_start" in the adb shell i got an invalid argument error:
Code:
if: illegal argument combination or already set
What i should do?
Click to expand...
Click to collapse
Sorry, there was a typo. Should be correct now
Thanks for the hint.
kimycai said:
when i get a SOS checksum error and a LNX checksum error,can i copy files from pc to a500 device? how?
Click to expand...
Click to collapse
The procedure for this case is much more complex. If you do something wrong, it is getting even more complicated.
I will not publish details currently, sorry. If you get this error, contact me.
As soon as some tools are finished i will update the OP.
Sent from my HTC Desire using XDA App
sc2k said:
Sorry, there was a typo. Should be correct now
Thanks for the hint.
Click to expand...
Click to collapse
Ah ok, thx.
thank you sc2k!
sc2k said:
The procedure for this case is much more complex. If you do something wrong, it is getting even more complicated.
I will not publish details currently, sorry. If you get this error, contact me.
As soon as some tools are finished i will update the OP.
Sent from my HTC Desire using XDA App
Click to expand...
Click to collapse
really？
waiting……
Hi
After I typed "dd if=/dev/block/mmcblk0 bs=512 count=13312 of=/sdcard/mmcblk0_start" in adb i got: "dd if=/dev/block/mmcblk0 bs=512 count=13312 of=/sdcard/mmcblk0_start /dev/block/mmcblk0: cannot open for read: Premission denied"
What i done wrong?
Raphaello said:
Hi
After I typed "dd if=/dev/block/mmcblk0 bs=512 count=13312 of=/sdcard/mmcblk0_start" in adb i got: "dd if=/dev/block/mmcblk0 bs=512 count=13312 of=/sdcard/mmcblk0_start /dev/block/mmcblk0: cannot open for read: Premission denied"
What i done wrong?
Click to expand...
Click to collapse
You need to be root
Type
Code:
su -
before.
I will update the guide
Thanks but it's doesn't work yet. I have root access. I tried type "su-" but it is the same message "cannot open for read: Premission denied". I install usb drivers and the others think from guide hmmmm....
Raphaello said:
I tried type "su-" but it is the same message "cannot open for read: Premission denied".
Click to expand...
Click to collapse
Did you type su- or su - (notice the space between su and -)?
Also you'll have to confirm su permissions on the tablet.
I typed "su -" with space between su and -
I have USB debugging turn on
When i type "su -" it say "Premission denied"
I really sorry for problem and thanks you for trying to help me
Is your device rooted? Because it has to be.
And if it's rooted did you notice a superuser app popping up after you run the command.
What a shame, I did not notice a superuser app popping up :/ Now it's ok. Thank You very much. I must learn a lot. Only think was taht I can't pull this file to my computer via "adb pull /sdcard/mmcblk0_start" but i copy it directly from device Now I feel safe.
Thanks a lot guys
Well, actually you should be able to dump directly to adb without copying to device to save some time.
like dd if=/dev/mmcblk0p1 count=X bs=Y
but without specifying of= or using of=-
and don't forget to redirect it to file. like "adb shell "dd if ..." > dump_p1". Not sure it will work fine, but I used it once on another device to dump block device image.
i download the android sdk zip file, but is seems that the "tools" folder doesn't include the adb executable file , how should i do?
Ok, so I did something stupid, I tried to install a slider lock theme on my kindle and probably screwed up the Framework-Res. I did not have TWRP or a backup of any kind.
Now the kindle just sits at the boot splash screen.
The device was running on 6.2.2 and most tutorials seem to be made for 6.2.1
I have tried a few manual commands but remount is just say "Operation Not Permitted" (I cant figure out how to fix this either.
Running automated programs like Unbrick Utility just don't work, it says it has completed but you can see a bunch of errors saying it could not copy or not permitted etc...
At this point I just want my kindle fire back even if that means a complete restore, can someone please try to help or point me in the right direction I am about to go insane.
Added Info: To be more exact, I tried to use metamorph to install a slider lock theme, nothing seemed to happen so I closed the app. I thought everything was fine so I put the kindle to sleep, but I could not wake it up. I tried restarting it and that's how I got to were I am now.
Update:
Thanks to b63 I was able to get this fixed, I cant thank him enough.
Ok here is how I got it fixed
First I followed the directions given to me below by b63
he told me to refer to this http://forum.xda-developers.com/show...8&postcount=29 which I did, however When I got to 8 I did something different, I did not need to re install the whole Rom because I had only messed up the Framework-res.apk
So instead I pulled the Framework-res.apk from /system/framework in the official kindle 6.2.2 update.zip
I then used these commands to replace the broken apk on the device and restart in normal boot mode.
4. "adb remount"
5. "adb push framework-res.apk /system/framework/framework-res.apk"
6. "adb shell chown root /system/framework/framework-res.apk"
7. "adb shell chmod 644 /system/framework/framework-res.apk"
8. "adb shell idme bootmode 4000"
9. "adb reboot"
I know that this explanation is not super descriptive but most of what you need can be found below in the thread.
This problem is rather specific to my situation so if you are having the same problem and you can't figure it out send me a PM or reply to this thread.
Anyone? I'm starting to think i should just try to return it.
would need some more concrete information:
is it rooted only ?
what is the boot splash screen "kindle fire" (static or animated) or yellow triangle ?
do you have kfu available ?
moved and renamed so that it is at c:\kfu ?
patched the run.bat of kfu ?
what are the 3 status lines of kfu when you just start it ? - please don't do any option at the moment
os/bit of computer ?
driver status in device manager ?
b63 said:
would need some more concrete information:
is it rooted only ?
what is the boot splash screen "kindle fire" (static or animated) or yellow triangle ?
do you have kfu available ?
moved and renamed so that it is at c:\kfu ?
patched the run.bat of kfu ?
what are the 3 status lines of kfu when you just start it ? - please don't do any option at the moment
os/bit of computer ?
driver status in device manager ?
Click to expand...
Click to collapse
Thank you for the response, I'm not at my normal Computer now, but I will answer what I can from here.
Yes I believe it is rooted only, no roms or anything installed.
The Splash screen is Kindle Fire, It is static (no shine animation). I also never installed TWRP or firefirefire so I don't think it should be yellow. (I tried though)
I do have KFU available, but I'm getting operation not permitted errors
No I did not move/rename it (maybe that's the not permitted issue?)
Three Lines: ADB Status: Online ADB Rooted: No (it was rooted) Boot Status: 4000
Vista 32 Bit
Cant check at the moment (however I believe the drivers are working properly)
Thank you for the response Ill try to help the best I can, Im pretty techy but Ill admit I'm a noob at ADB
Damieok said:
Thank you for the response, I'm not at my normal Computer now, but I will answer what I can from here.
Yes I believe it is rooted only, no roms or anything installed.
The Splash screen is Kindle Fire, It is static (no shine animation). I also never installed TWRP or firefirefire so I don't think it should be yellow. (I tried though)
I do have KFU available, but I'm getting operation not permitted errors
No I did not move/rename it (maybe that's the not permitted issue?)
Three Lines: ADB Status: Online ADB Rooted: No (it was rooted) Boot Status: 4000
Vista 32 Bit
Cant check at the moment (however I believe the drivers are working properly)
Thank you for the response Ill try to help the best I can, Im pretty techy but Ill admit I'm a noob at ADB
Click to expand...
Click to collapse
ok i see a lot out of this - thanks
would recommend to do the move/rename of kfu to sort out any additional problems
you should have adb commands available and the kf is in normal boot mode
now the ultimate test is to issue:
"adb shell"
- if it goes into the shell ($ or # prompt) you can resume
- if it responds something like <exec "system/bin/sh": No such file or directory> then there is no possibility to get to fastboot mode to install fff and twrp which is necessary to install a fresh rom - if this is the case your only solution is to build or buy a "factory cable" - look at this thread :
http://forum.xda-developers.com/showthread.php?t=1392693
b63 said:
I would recommend to do the move/rename of kfu to sort out any additional problems
you should have adb commands available and the kf is in normal boot mode
now the ultimate test is to issue:
"adb shell"
- if it goes into the shell ($ or # prompt) you can resume
- if it responds something like <exec "system/bin/sh": No such file or directory> then there is no possibility to get to fastboot mode to install fff and twrp which is necessary to install a fresh rom - if this is the case your only solution is to build or buy a "factory cable" - look at this thread :
http://forum.xda-developers.com/showthread.php?t=1392693
Click to expand...
Click to collapse
Ok so I renamed the "Kindle Fire Utility" folder to "kfu" moved it to C:\
(if this is incorrect please let me know.)
And good news, adb shell responds with $, were should I go next. (also I have access to my normal computer now)
Thanks again for helping me out with this.
great !!! - simply try to follow this post starting at point 2:
http://forum.xda-developers.com/showpost.php?p=21803658&postcount=29
place the downloaded files in the tools folder of kfu since you are doing the commands from there
b63 said:
great !!! - simply try to follow this post starting at point 2:
http://forum.xda-developers.com/showpost.php?p=21803658&postcount=29
place the downloaded files in the tools folder of kfu since you are doing the commands from there
Click to expand...
Click to collapse
Im a little confused at this guide are the commands being entered into adb or in kfu? Were does kfu come into play?
Sorry the guide is a little hard to understand
it' not so complicated as it sounds ...
open a elevated command prompt and cd to c:\kfu\tools
here are all commands you need and where kfu comes in play
- you don't need kfu itself - only the tools folder
- leave the command window open all the time
i managed to get ICS_Root to run under Linux (Ubuntu 14). It claims Root achieved but Titanium Backup says "no root".
I found http://forum.xda-developers.com/showthread.php?t=1823421 but I'm stuck.
0) Have your CPUID and/or SBK to hand, along with the A500 APX Flash Tool downloaded. <<=== I don't know how to get the CPUID
If you have your CPUID but not your SBK, go generate it now with http://a500bootloaderflash.tk/sbkcalc/
1) Download the root zip from http://www.blackthund3r.co.uk/hostedfiles/CWM_ICSRoot and copy it to the device's internal storage over USB
2) Load the A500 APX Flash Tool and enter the bundle market. View the bundles for the default repo (a500bootloaderflash.tk) ,<=== the Tool unpacks as a .exe. I'm on LInux.
I searched for how to get the CPUID and found this: http://forum.xda-developers.com/showthread.php?t=1624645
This item
(2) From your device using Terminal Emulator App
looked promising but didn't say _how_ (or which Terminal Emulator app)
Pointers or links would be nice.
Help?
vlbrown said:
i managed to get ICS_Root to run under Linux (Ubuntu 14). It claims Root achieved but Titanium Backup says "no root".
I found http://forum.xda-developers.com/showthread.php?t=1823421 but I'm stuck.
0) Have your CPUID and/or SBK to hand, along with the A500 APX Flash Tool downloaded. <<=== I don't know how to get the CPUID
If you have your CPUID but not your SBK, go generate it now with http://a500bootloaderflash.tk/sbkcalc/
1) Download the root zip from http://www.blackthund3r.co.uk/hostedfiles/CWM_ICSRoot and copy it to the device's internal storage over USB
2) Load the A500 APX Flash Tool and enter the bundle market. View the bundles for the default repo (a500bootloaderflash.tk) ,<=== the Tool unpacks as a .exe. I'm on LInux.
I searched for how to get the CPUID and found this: http://forum.xda-developers.com/showthread.php?t=1624645
This item
(2) From your device using Terminal Emulator App
looked promising but didn't say _how_ (or which Terminal Emulator app)
Pointers or links would be nice.
Help?
Click to expand...
Click to collapse
Scroll down a bit further m8...
(2) Retrieve your CPUID from your Tab using Terminal Emulator from the market
Code:
dmesg | grep androidboot.serialno
some have reported this did not work for them but that this one did when they tried it:
Code:
dmesg > /mnt/external_sd/dmesg.txt
Run these commands AFTER you have rebooted your Tab..
NOTE: HC Bootloaders who are running an ICS build:
adb reports your device ID as your serial no. and we need your HC CPUID.
Click to expand...
Click to collapse
Sent from my HTC_PN071 using Tapatalk
READ THIIS!
*this thread is for m9. it will NOT work on m7,or any older device. please check the general forum for your particular device for a similar thread.
this thread will let you unlock your bootloader without htcdev,or let you change your hboot watermark from relocked or locked back to stock.
advantages
-no hassle with htcdev,tokens,or unlock codes
-no submitting your phones personal info to htc
-the ability to get back to 100% stock without any visual traces or records of having been s off or unlocking your bootloader.
you do NOT need to downgrade your hboot. this simple adb command works without any scary hboot downgrades.
*you must be s off.
*you must have superuser installed
read this:
this will not work if your s on. its not a way to magically unlock
the usual disclaimers:
use this info at your own risk. if it melts your phone into a little pile of aluminum goo,its not my fault.
credits
-beaups for schooling me on echo comand protocol
-strace for originally discovering the location of the lock status flag(check out this thread for more info)
- @Mutasek24 for fearlessly testing all commands
IF you are an advanced user with adb/fastboot set up and some basic knowlede of the cmd window,you can skip to #2
1)set up adb(windows 7 and older)
-download this file
-install drivers: if you have htc sync installed,you should allready have drivers. if not,you can install htc sync,or install these modified htc drivers from revolutionary (driver mirror)
-unzip your miniadb_v1031.zip file. this is native funtionality in windows 7. you otherwise may need a utility such as "7-zip" to extract,or unzip it. place the unzipped folder onto the root of your C drive on your PC. root means the top level,not inside any folders. so just copy and paste,or drag and drop the folder onto C with everything else that is there. you may want to rename it to "miniadb_m7" since youll be putting some device specific files in here.
-open a command window. on windows 7,click the start bubble in the lower left and type "command" in the search box. xp i believe is similar or the same. doing this should open a small black command window.
-change to your miniadb_m7 directory. type the following at the prompt in your cmd window:
cd c:\miniadb_m7
your command promt should change to "c:miniadb_m7>" provided you: 1)unzipped the miniadb_v1031 zip file,and 2)put the folder on your c drive,and 3)entered the name of the folder correctly ("miniadb_m7" in this case)
-now make sure usb debugging is checked in developer options(you will need to turn it on first),and plug your phone into your PC with a usb cable
-make sure your phone is being recognized- type:
adb devices
if your drivers are installed correctly,this should return your phones serial number. you should hear the "found device" noises when you plug your phone in. if it starts installing drivers,wait for it to finish before typing the adb devices command.
if you get your serial number back,then enter this command:
adb reboot bootloader
this should take your phone to the "fastboot" screen,wich is white with colored letters. this is one mode of your bootloaders interactive modes. at the top youll see fastboot devices as confirmation youre in fastboot.
now enter:
fastboot devices
again,this should return your phones serial number. you should hear the "found device" noises when you plug your phone in. if it starts installing drivers,wait for it to finish before typing the adb devices command.
if you get your serial number back,you can enter the following to boot back to the phones OS:
fastboot reboot
and now,youve installed adb/fastboot and tested youre phones drivers. if at either spot,you have trouble and dont get your serial number back,there is some sort of connection issue. use these steps to troubleshoot:
troubleshooting connectivity issues:
-try a reboot of the PC
-try different usb cables and ports
-dont use a usb hub
-dont use usb 3.0
-make sure nothing capable of comunicating with the phone is enabled and running. htc sync,pdanet,easy tether,and even itunes have all been known to cause issues.
-windows 8 has been known to have issues. try a windows 7 or older machine
failing the above,
-i use these drivers for fastboot and adb(donwload and run as admin): http://downloads.unrevoked.com/HTCDriver3.0.0.007.exe (mirror)
failing that,try manually updating the drivers in the following manner:
-put the phone in fastboot mode(select fastboot from the hboot menu)
-open device manager on the PC
-plug in phone,watch for it to pop up in device manager.
-update drivers with device manager,pointing the wizard to the extracted
driver download folder from above
note that you can check the connectivity of the phone,and make sure drivers are working by in the following manner:
-open cmd window. change to directory containing adb/fastboot utilities
-adb with the phone in the booted OS,usb debug enabled,enter:
adb devices in a cmd window
-fastboot with phone in fastboot,enter:
fastboot devices in cmd window
in either case,a properly connected phone with working drivers installed should report back the phones serial number.
Click to expand...
Click to collapse
this process,in your cmd window,should look something like this:
Code:
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\Scott>[COLOR="red"]cd c:\miniadb_m7[/COLOR]
c:\miniadb_m7>adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
FAxxxxxxxxxx device
c:\miniadb_m7>[COLOR="red"]adb reboot bootloader[/COLOR]
c:\miniadb_m7>[COLOR="red"]fastboot devices[/COLOR]
FAxxxxxxxxxx fastboot
c:\miniadb_m7>[COLOR="red"]fastboot reboot[/COLOR]
rebooting...
finished. total time: 0.037s
c:\miniadb_m7>
2)reset your "lock status flag"
to LOCK your bootloader,enter the following:
adb devices
adb shell
su (if needed to get a # prompt)
echo -ne '\x00\x00\x00\x00' | dd of=/dev/block/mmcblk0p2 bs=1 seek=33796
(i would very strongly recomend you copy/paste this)
exit
(exit a second time if you need to to get back to a normal > prompt)
adb reboot bootloader
verify you are now locked
_____________________________________________________________________________________________
to UNLOCK your bootloader,enter the following:
adb devices
adb shell
su (if needed to get a # prompt)
echo -ne "HTCU" | dd of=/dev/block/mmcblk0p2 bs=1 seek=33796
(i would very strongly recomend you copy/paste this)
exit
(exit a second time if you need to to get back to a normal > prompt)
adb reboot bootloader
verify you are now unlocked
other useful threads:
restore software status: original banner: http://forum.xda-developers.com/one-m9/general/how-to-restore-software-status-original-t3092882
change mid: fastbooot oem writemid xxxxxxxxx
change cid: fastboot oem writecid xxxxxxxx
mine
scotty1223 said:
mine
Click to expand...
Click to collapse
Thanks a lot for your very useful information. I have 2 questions??
1) When I am s-on and need to get s-off, then I need to be unlocked and rooted, so to do these still I need to use HTC-dev to unlock and root.
2) Does this method wipe data like when we use HTC-dev?
Nima78600 said:
Thanks a lot for your very useful information. I have 2 questions??
1) When I am s-on and need to get s-off, then I need to be unlocked and rooted, so to do these still I need to use HTC-dev to unlock and root.
2) Does this method wipe data like when we use HTC-dev?
Click to expand...
Click to collapse
1)yes. the first time you root,you will need to use htcdev to unlock the bootloader. the biggest benefit of this is the ability to return to a locked status for warranty. while s on,the best youll be able to do is relocked.
2)no,it will not wipe your data. it just changes the flag that hboot checks in order to decide if its locked,or not.
scotty1223 said:
1)yes. the first time you root,you will need to use htcdev to unlock the bootloader. the biggest benefit of this is the ability to return to a locked status for warranty. while s on,the best youll be able to do is relocked.
2)no,it will not wipe your data. it just changes the flag that hboot checks in order to decide if its locked,or not.
Click to expand...
Click to collapse
Thanks a lot mate. Appreciate for your replying
anyway to get "modified" back to "official" in boot loader?
Thanks @scotty1223. Used your threads for the m7 and m8. Happy to see this here too.
an0ther said:
anyway to get "modified" back to "official" in boot loader?
Click to expand...
Click to collapse
Flash your device RUU.
I am a little confused. How do I unlock my boot loader without root? I have s-off and i'm just messing around with trying to get rid of modified status but how does the "su" work without root?
an0ther said:
I am a little confused. How do I unlock my boot loader without root? I have s-off and i'm just messing around with trying to get rid of modified status but how does the "su" work without root?
Click to expand...
Click to collapse
You don't. This method requires s-off and root. It does say that in the OP BTW.
Behold_this said:
Thanks @scotty1223. Used your threads for the m7 and m8. Happy to see this here too.
Flash your device RUU.
Click to expand...
Click to collapse
I did, it still says modified in boot loader. Do I need to lock boot loader first?
an0ther said:
I did, it still says modified in boot loader
Click to expand...
Click to collapse
Use Sdcard method
Behold_this said:
Use Sdcard method
Click to expand...
Click to collapse
Mine is 64 gig, guess i'll have to get a 32 gig to make it fat32. Dang. Thanks for your help
Thanks for your very important knowledge.This question is not related to this thread, do you know which adb commands we can use to remove tampered flag as such in M7 and M8? I wonder mmcblk0p blocks might be different.
Thanks!
Enviado desde mi HTC One M9
coolberry said:
Thanks for your very important knowledge.This question is not related to this thread, do you know which adb commands we can use to remove tampered flag as such in M7 and M8? I wonder mmcblk0p blocks might be different.
Click to expand...
Click to collapse
The block where the tampered flag is write protected,so it cannot be written to with adb and have the change "stick". We know the command,it just doesn't work.
An ruu won't be available for all variants,so there will still be a work around,it will just be a bit more complicated. I just need to make sure it works and try to make it as user friendly as possible.
an0ther said:
Mine is 64 gig, guess i'll have to get a 32 gig to make it fat32. Dang. Thanks for your help
Click to expand...
Click to collapse
What does 64gb have to do with anything? Just back it up and reformat
scotty1223 said:
What does 64gb have to do with anything? Just back it up and reformat
Click to expand...
Click to collapse
Not possible. Only cards up to 32gb can be formatted as fat32, it's because above 32gb cards are not SDHC anymore but SDXC and this doesn't work..
devatxda said:
Not possible. Only cards up to 32gb can be formatted as fat32, it's because above 32gb cards are not SDHC anymore but SDXC and this doesn't work..
Click to expand...
Click to collapse
Did a little bit of searching and found a couple references to this:
http://mympx.org/Downloads/p13_sectionid/2/p13_fileid/13
And
http://m.download.cnet.com/EaseUS-Partition-Master-Home-Edition/3000-2248_4-10863346.html
Have you tried either?
Sent from my HTC One max
Behold_this said:
Use Sdcard method
Click to expand...
Click to collapse
im a little confused on what methods reset the flag,and which dont
could someone clarify the results of
-flash 0PJAIMG.zip via download mode from sd card
-flash 0PJAIMG.zip via RUU mode from pc
-run .exe from windows machine
-any other methods??
thanks
scotty1223 said:
im a little confused on what methods reset the flag,and which dont
could someone clarify the results of
-flash 0PJAIMG.zip via download mode from sd card
-flash 0PJAIMG.zip via RUU mode from pc
-run .exe from windows machine
-any other methods??
thanks
Click to expand...
Click to collapse
Ruu.exe worked for me.
Sdcard worked for @Mutasek24, but download mode manual flash did not (as reported in your other thread).
Because all methods are flashing the exact same SIGNED zip, and exe flashes through RUU mode, it's likely that flashing zip manually from RUU mode would reset the flag while using download mode does not. That needs to be tested tho.
I have a 3rd Gen fire hdx 8.9 on 14.3.2.6. Safestrap is installed. I want to roll back and unlock my bootloader to install the nexus rom.
Is there a tutorial available? Do I need to uninstall safestrap first?
Check page 1 of this thread, basically it's all there, so read the info & the linked threads. Any questions ask first, i.e. before you brick your kindle.
Note that you can NOT use the rollback images, nor edit the build number. You must use the procedure described in post 1 of the thread and download the rollback zip I linked in post 4, you need to scroll down to get to the 3.2.5/3.2.6 procedure.
Cl4ncy said:
Check page 1 of this thread, basically it's all there, so read the info & the linked threads. Any questions ask first, i.e. before you brick your kindle.
Note that you can NOT use the rollback images, nor edit the build number. You must use the procedure described in post 1 of the thread and download the rollback zip I linked in post 4, you need to scroll down to get to the 3.2.5/3.2.6 procedure.
Click to expand...
Click to collapse
I followed the procedure but I'm not clear that I downgraded correctly. No when I look at my system update, it says I am on 14.3.0.0_user_300079820. I thought I was supposed to be on 14.3.1.0_user_310079820? The file I downloaded from the thread is indeed "update-kindle-14.3.1.0_user_310079820.bin". Is there something else I need to do to downgrade before updating the bootloader?
rootnooby said:
I followed the procedure but I'm not clear that I downgraded correctly. No when I look at my system update, it says I am on 14.3.0.0_user_300079820. I thought I was supposed to be on 14.3.1.0_user_310079820? The file I downloaded from the thread is indeed "update-kindle-14.3.1.0_user_310079820.bin". Is there something else I need to do to downgrade before updating the bootloader?
Click to expand...
Click to collapse
I checked the rollback.zip for Apollo, it seems to be in the build.prop file, so nothing to worry about.
Now you should install TWRP via adb, update the 3.2.3.2 bootloader in TWRP, and finally unlock the bootloader.
Be sure to root and disable OTA via HDXToolkit, and enable USB debugging in Fire OS, before you flash TWRP.
And be sure to create a backup of Fire OS in TWRP before you flash any custom ROM.
Thanks. Is there a link outlining the steps to install twrp via add? Sorry for the need to have my hand held through this!
rootnooby said:
Thanks. Is there a link outlining the steps to install twrp via add? Sorry for the need to have my hand held through this!
Click to expand...
Click to collapse
You must have Minimal ADB and Fastboot installed, download the Apollo TWRP Image here, copy it to the root of the sdcard (i.e. the directory you see in Explorer when you connect the HDX to your PC, so don't open any directory there),then you open a DOS box, change dir to the adb directory (enter cd\adb), then execute the commands mentioned in the TWRP thread with the correct file name for the Apollo TWRP image.
Thanks so much. I'll give it a go tonight.
rootnooby said:
Thanks so much. I'll give it a go tonight.
Click to expand...
Click to collapse
looks like I got through everything except the last remaining step of unlocking the bootloader. I confirmed that I am rooted and OTA is blocked. Not sure how to get this unlocked so I can finally have a real ROM!
rootnooby said:
looks like I got through everything except the last remaining step of unlocking the bootloader. I confirmed that I am rooted and OTA is blocked. Not sure how to get this unlocked so I can finally have a real ROM!
Click to expand...
Click to collapse
OK, so you have Minimal ADB and Fastboot installed, unlocking the bootloader is really simple (with a little knowledge about command prompts), so download these drivers you need to install when the good ol' "waiting for device" issue occurs (check device manager then, the HDX probably has a yellow exclamation mark there).
You must download the software and the Python script mentioned here, and then follow the path outlined there, or (after installation of the required software) also here. Basically you just need to open a couple of command prompts (DOS boxes), change dir to the adb directory (enter cd\adb - or cd\python27 to go to the Python directory), then get the ID and serial, use the Python script with them, and finally execute the fastboot commands to unlock the bootloader.
That's it - and it's a no brainer, you can't mess up anything, if the unlock code is incorrect, it just won't flash (well, you must enter the fastboot commands correctly of course).
Cl4ncy said:
OK, so you have Minimal ADB and Fastboot installed, unlocking the bootloader is really simple (with a little knowledge about command prompts), so download these drivers you need to install when the good ol' "waiting for device" issue occurs (check device manager then, the HDX probably has a yellow exclamation mark there).
You must download the software and the Python script mentioned here, and then follow the path outlined there, or (after installation of the required software) also here. Basically you just need to open a couple of command prompts (DOS boxes), change dir to the adb directory (enter cd\adb - or cd\python27 to go to the Python directory), then get the ID and serial, use the Python script with them, and finally execute the fastboot commands to unlock the bootloader.
That's it - and it's a no brainer, you can't mess up anything, if the unlock code is incorrect, it just won't flash (well, you must enter the fastboot commands correctly of course).
Click to expand...
Click to collapse
Thanks. Running into an error creating the unlock file. I installed python, but I don't think i installed gmpy2-2.0.7-cp27-none-win_amd64.whl (md5) properly. The error I'm getting when I run the following command "python.exe cuberHDX.py 0xmmssssssss" "is "no module named gmpy2". I am using my correct code in the previous command. When I downloaded the gmpy2-2.0.7-cp27-none-win_amd64.whl (md5), I copied into the Python27 directory. Not sure if this is correct.
rootnooby said:
Thanks. Running into an error creating the unlock file. I installed python, but I don't think i installed gmpy2-2.0.7-cp27-none-win_amd64.whl (md5) properly. The error I'm getting when I run the following command "python.exe cuberHDX.py 0xmmssssssss" "is "no module named gmpy2". I am using my correct code in the previous command. When I downloaded the gmpy2-2.0.7-cp27-none-win_amd64.whl (md5), I copied into the Python27 directory. Not sure if this is correct.
Click to expand...
Click to collapse
Try to use the exe installer for 2.0.6 from here. If it still fails, PM me your ID and serial, I'll create the .unlock file for you then.
Cl4ncy said:
Try to use the exe installer for 2.0.6 from here. If it still fails, PM me your ID and serial, I'll create the .unlock file for you then.
Click to expand...
Click to collapse
Thanks. It worked. I now have an unlock code. I'm not clear where my fastboot directory is? It says I need to "copy that file to your fastboot directory" before i run the commands. Would that just be the root of the kindle itself? Sorry for the question.
rootnooby said:
Thanks. It worked. I now have an unlock code. I'm not clear where my fastboot directory is? It says I need to "copy that file to your fastboot directory" before i run the commands. Would that just be the root of the kindle itself? Sorry for the question.
Click to expand...
Click to collapse
If you installed Minimal ADB and Fastboot, it's the adb directory (e.g. C:\adb), you should have fastboot.exe in there as well. Just copy/move the .unlock file in the adb directory, open two DOS boxes, enter cd\adb in both,
then enter adb reboot-bootloader in the first one,
and the fastboot commands
fastboot -i 0x1949 devices
fastboot -i 0x1949 flash unlock 0xmmssssssss.unlock (mm=your ID, ssssssss=your serial)
fastboot -i 0x1949 reboot
in the second (again: if you see "waiting for device" on the fastboot prompt, install these drivers in device manager for the HDX (probably sitting there with a yellow exclamation mark).
Cl4ncy said:
If you installed Minimal ADB and Fastboot, it's the adb directory (e.g. C:\adb), you should have fastboot.exe in there as well. Just copy/move the .unlock file in the adb directory, open two DOS boxes, enter cd\adb in both,
then enter adb reboot-boorloader in the first one,
and the fastboot commands
fastboot -i 0x1949 devices
fastboot -i 0x1949 flash unlock 0xmmssssssss.unlock (mm=your ID, ssssssss=your serial)
fastboot -i 0x1949 reboot
in the second (again: if you see "waiting for device" on the fastboot prompt, install these drivers in device manager for the HDX (probably sitting there with a yellow exclamation mark).
Click to expand...
Click to collapse
Wow. I think it all worked! Assuming that's it. I can go ahead and load ROMs!
rootnooby said:
Wow. I think it all worked! Assuming that's it. I can go ahead and load ROMs!
Click to expand...
Click to collapse
If it looked like this, i.e. unlock code is correct, then yes.
Enjoy your "free" HDX.
yes, it does look like that so I have unlocked successfully! I ran a backup using twrp, and that worked well. One problem I'm having now is that my computer doesn't seem to recognize the Kindle when connected via USB any more. I'm getting a message that says some candles are not compatible and a separate file needs to be downloaded. When I go to the Kindle support website, this is applicable for older systems running Windows XP. Have you seen this problem before? Now that I have a backup I want to move it over to my PC so I don't use all that storage.
rootnooby said:
yes, it does look like that so I have unlocked successfully! I ran a backup using twrp, and that worked well. One problem I'm having now is that my computer doesn't seem to recognize the Kindle when connected via USB any more. I'm getting a message that says some candles are not compatible and a separate file needs to be downloaded. When I go to the Kindle support website, this is applicable for older systems running Windows XP. Have you seen this problem before? Now that I have a backup I want to move it over to my PC so I don't use all that storage.
Click to expand...
Click to collapse
Yes, it seems that the drivers required for fastboot cause such a problem, remove them in device manager (select to delete the driver files), then dis- and re-connect the HDX, so the original HDX drivers will be re-installed. Should do the trick in this case.