Okay, here's what happened,
2 days ago, i installed ARHD ROM, works perfectly fine,
next day, i saw a kernel by franco. installed it, then after rebooting.... baamm! my unit is not working anymore, stuck in boot screen,
i tried different ways, followed different forums, like Tutorial Disaster. still to no avail,
the sad thing is, i forgot to back it up before doing the upgrades, i know its my fault..
i tried to erase everything via recovery, still not working,
Just today, went to HTC service center, i'm from the Philippines, but i bought my unit from online selling. as per HTC service center its from indonesia, they tried to re-flash something but they said its not working, so they said that they will need to change the mother board, and it will cost me 14,000 pesos or $350.. i don't want to spend that much, feels like i bought a new one..
can someone please enlighten me?
?!
You can erase everything in recovery, but you have to flash something afterwards, maybe like ARHD.
There's nothing wrong with your device, don't panic. Just do a wipe, then flash the ROM as the directions are given.
if you can still get into recovery
relock it
flash stock recovery
flash stock RUU
done
Download ARHD and CWM Recovery
Rename ARHD to update.zip and CWM to recovery.img
Place update.zip and recovery.img into a folder with fastboot and adb
Extract boot.img from update.zip and place in your fastboot folder
Put your phone into fastboot mode with unlocked bootloader
Flash boot with command 'fastboot flash boot boot.img'
Boot recovery using 'fastboot boot recovery.img' command
Use command 'adb push update.zip /sdcard/update.zip' to send ARHD to phone
Then install rom from update.zip in recovery
It's nothing serious with your phone. It is easily can be recovered. Just don't run here and there so the XDA community can assist you.
There are two ways to recover your phone.
1) flash RUU
2) push xxx_rom.zip to your device.
Already tell you about flashing RUU in the disaster thread.
well, i would like to give thanks to all of you, who answered my questions, helped a lot. trying to read more here before doing another run in fixing my device.
where can i get stock RUU? my device is from indonesia. and one more thing, how to flash RUU?
djpoe said:
Download ARHD and CWM Recovery
Rename ARHD to update.zip and CWM to recovery.img
Place update.zip and recovery.img into a folder with fastboot and adb
Extract boot.img from update.zip and place in your fastboot folder
Put your phone into fastboot mode with unlocked bootloader
Flash boot with command 'fastboot flash boot boot.img'
Boot recovery using 'fastboot boot recovery.img' command
Use command 'adb push update.zip /sdcard/update.zip' to send ARHD to phone
Then install rom from update.zip in recovery
Click to expand...
Click to collapse
very detailed instruction here
where can i get adb BTW?
wintermute000 said:
if you can still get into recovery
relock it
flash stock recovery
flash stock RUU
done
Click to expand...
Click to collapse
This and finish with: fastboot erase cache
Sent from my HTC One X using XDA
wolfraim said:
This and finish with: fastboot erase cache
Sent from my HTC One X using XDA
Click to expand...
Click to collapse
thanks man.. where can i get the stock RUU and stock recovery? and also why do we have to re lock the device?
EDIT: i almost forgot, because this problem started after installing a new kernel by franco, so i guess i need to install a stock kernel? where can i get it?
mikey0105 said:
thanks man.. where can i get the stock RUU and stock recovery? and also why do we have to re lock the device?
EDIT: i almost forgot, because this problem started after installing a new kernel by franco, so i guess i need to install a stock kernel? where can i get it?
Click to expand...
Click to collapse
I had the same problem with franco's kernel, what I did was, go to recovery and re-flash my xx_rom.zip, then it boots ok. You should try the same, provided you still have the ARHD.zip in your sdcard.
Your device from Indonesia ? I believe this is the RUU for you (same for me too):http://hoxroms.serveftp.com/RUU_END...Radio_1.1204.103.14_release_257076_signed.exe
ckpv5 said:
I had the same problem with franco's kernel, what I did was, go to recovery and re-flash my xx_rom.zip, then it boots ok. You should try the same, provided you still have the ARHD.zip in your sdcard.
Your device from Indonesia ? I believe this is the RUU for you (same for me too):http://hoxroms.serveftp.com/RUU_END...Radio_1.1204.103.14_release_257076_signed.exe
Click to expand...
Click to collapse
thanks ill try it later.. i don't have it on my sdcard, as i've said i erased everything already..
but i guess i'll try the step on top provided by "djpoe" to put the ARHD inside my SD card. hope everything will work..
1 Download ARHD and CWM Recovery
2 Rename ARHD to update.zip and CWM to recovery.img
3 Place update.zip and recovery.img into a folder with fastboot and adb
4 Extract boot.img from update.zip and place in your fastboot folder
5 Put your phone into fastboot mode with unlocked bootloader
6 Flash boot with command 'fastboot flash boot boot.img'
7 Boot recovery using 'fastboot boot recovery.img' command
8 Use command 'adb push update.zip /sdcard/update.zip' to send ARHD to phone
9 Then install rom from update.zip in recovery
For item 7 & 8, maybe you like a safe-proof guide that I posted here
Just replace "D:\HTC\One X\HTC Dev.com unlock\android-sdk\platform-tools>" to your own fastboot/adb folder path
and "recovery-clockwork-touch-5.8.3.1-endeavoru.img" to "recovery.img" if you renamed it.
and "xxx.zip" to "update.zip"
thanks, i'm downloading the files now...
quick question, if i erased all data/cache, the kernel that i installed? will it be deleted as well? because i need to have a stock kernel and i can't see one?
erase all data/system/cache will not delete the installed kernel.
As you said you will follow djpoe's guide, see no. 4 & no. 6 regarding kernel flashing.
Remember the ROM.zip that you have earlier (see Disaster thread), inside the ROM.zip there is a boot_signed.img, that is the stock kernel. But you don't really need the stock kernel, what you need is the AHRD's kernel (see. no.4).
ohhh i see! now that good to know thanks... waiting for the files to be downloaded.. will give you feedback later... fingers cross...
additional question, just wondering, why is it important to re-lock the device before flashing ruu?
i tried to copy the update.zip by doing this
adb push update.zip/sdcard/update.zip
then there are lots of command on the CMD.. see below
C:\fastboot>adb push update.zip/sdcard/update.zip
Android Debug Bridge version 1.0.29
-d - directs command to the only connected USB devic
e
returns an error if more than one USB device is
present.
-e - directs command to the only running emulator.
returns an error if more than one emulator is r
unning.
-s <serial number> - directs command to the USB device or emulator w
ith
the given serial number. Overrides ANDROID_SERI
AL
environment variable.
-p <product name or path> - simple product name like 'sooner', or
a relative/absolute path to a product
out directory like 'out/target/product/sooner'.
If -p is not specified, the ANDROID_PRODUCT_OUT
environment variable is used, which must
be an absolute path.
devices - list all connected devices
connect <host>[:<port>] - connect to a device via TCP/IP
Port 5555 is used by default if no port number
is specified.
disconnect [<host>[:<port>]] - disconnect from a TCP/IP device.
Port 5555 is used by default if no port number
is specified.
Using this command with no additional arguments
will disconnect from all connected TCP/IP devic
es.
device commands:
adb push <local> <remote> - copy file/dir to device
adb pull <remote> [<local>] - copy file/dir from device
adb sync [ <directory> ] - copy host->device only if changed
(-l means list but don't copy)
(see 'adb help all')
adb shell - run remote shell interactively
adb shell <command> - run remote shell command
adb emu <command> - run emulator console command
adb logcat [ <filter-spec> ] - View device log
adb forward <local> <remote> - forward socket connections
forward specs are one of:
tcp:<port>
localabstract:<unix domain socket name>
localreserved:<unix domain socket name>
localfilesystem:<unix domain socket name>
dev:<character device name>
jdwp:<process pid> (remote only)
adb jdwp - list PIDs of processes hosting a JDWP transport
adb install [-l] [-r] [-s] <file> - push this package file to the device and i
nstall it
('-l' means forward-lock the app)
('-r' means reinstall the app, keeping its data
)
('-s' means install on SD card instead of inter
nal storage)
adb uninstall [-k] <package> - remove this app package from the device
('-k' means keep the data and cache directories
)
adb bugreport - return all information from the device
that should be included in a bug report.
adb backup [-f <file>] [-apk|-noapk] [-shared|-noshared] [-all] [-system|-nosy
stem] [<packages...>]
- write an archive of the device's data to <file>
.
If no -f option is supplied then the data is wr
itten
to "backup.ab" in the current directory.
(-apk|-noapk enable/disable backup of the .apks
themselves
in the archive; the default is noapk.)
(-shared|-noshared enable/disable backup of the
device's
shared storage / SD card contents; the defau
lt is noshared.)
(-all means to back up all installed applicatio
ns)
(-system|-nosystem toggles whether -all automat
ically includes
system applications; the default is to inclu
de system apps)
(<packages...> is the list of applications to b
e backed up. If
the -all or -shared flags are passed, then t
he package
list is optional. Applications explicitly g
iven on the
command line will be included even if -nosys
tem would
ordinarily cause them to be omitted.)
adb restore <file> - restore device contents from the <file> backup
archive
adb help - show this help message
adb version - show version num
scripting:
adb wait-for-device - block until device is online
adb start-server - ensure that there is a server running
adb kill-server - kill the server if it is running
adb get-state - prints: offline | bootloader | device
adb get-serialno - prints: <serial-number>
adb status-window - continuously print device status for a specifie
d device
adb remount - remounts the /system partition on the device re
ad-write
adb reboot [bootloader|recovery] - reboots the device, optionally into the boo
tloader or recovery program
adb reboot-bootloader - reboots the device into the bootloader
adb root - restarts the adbd daemon with root permissions
adb usb - restarts the adbd daemon listening on USB
adb tcpip <port> - restarts the adbd daemon listening on TCP on th
e specified port
networking:
adb ppp <tty> [parameters] - Run PPP over USB.
Note: you should not automatically start a PPP connection.
<tty> refers to the tty for PPP stream. Eg. dev:/dev/omap_csmi_tty1
[parameters] - Eg. defaultroute debug dump local notty usepeerdns
adb sync notes: adb sync [ <directory> ]
<localdir> can be interpreted in several ways:
- If <directory> is not specified, both /system and /data partitions will be u
pdated.
- If it is "system" or "data", only the corresponding partition
is updated.
environmental variables:
ADB_TRACE - Print debug information. A comma separated list
of the following values
1 or all, adb, sockets, packets, rwx, usb, sync
, sysdeps, transport, jdwp
ANDROID_SERIAL - The serial number to connect to. -s takes prior
ity over this if given.
ANDROID_LOG_TAGS - When used with the logcat option, only these de
bug tags are printed.
-------------------------------
then tried to install it via CWM, apply /sdcard/update.zip
it says
finding update
opening update
E: Can't open sdcard/update.zip
(No such file or directory)
Installation aborted
It should be C:\fastboot>adb push update.zip /sdcard not C:\fastboot>adb push update.zip/sdcard/update.zip
where is your adb files ? In the fastboot folder too ? If yes, try this:
1. C:\fastboot>fastboot boot recovery-clockwork-touch-5.8.3.1-endeavoru.img
2. C:\fastboot>adb devices
enter
C:\fastboot>adb shell
enter then type after ~ # mount sdcard
3. don't close anything, open another cmd prompt
C:\fastboot>adb push update.zip /sdcard
then enter
once completed, choose install from sdcard - choose zip from sdcard, the update.zip should be there
here whats happening. see attachment
mikey0105 said:
here whats happening. see attachment
Click to expand...
Click to collapse
There is no AdbWinUsb.dll in your folder ?
GUYS!!! AT LAST!!!! I'm so happy!!! its all okay now! oh man! this is crazy! hahaha! thank you so much to all!. the feeling is really great! WOOOOOWWWWW!!!!
Hi. I did a factory reset and now I cannot get past the white HTC welcome screen. I don't have the phone rooted, hboot says S-ON. I had USB debugging disabled when doing the reset, so now I can't turn it on (since I won't get anywhere near the actual system).
Also, I don't know if this is the cause of not having USB debugging on - adb can't seem to find my device. When connected, it shows HBOOT USB PLUG, but adb devices returns an empty list..
Is there a way I can root/unlock the phone, without having debugging on, so that I can flash a recovery and a new system?
Thanks
Not too likely, adb will never work in bootloader mode but fastboot should. adb only works in os and recovery.
What you'll need to do is flash an RUU through bootloader or fastboot to get things working again. Check the development section here for a list of the latest RUUs for the vision
Sent from my Nexus 4 using XDA Premium 4 mobile app
I was swamped and got back to it by now. Thank you for your suggestion. It doesn't work though.
I downloaded the newest RUU from htcdev.com, the phone did get recognized by fastboot and the RUU installer seemed happy. However, when the actual update started, it got stuck on "Rebooting bootloader" or similar for over half an hour. That's when I decided to cancel it.
Next on, I tried steps shown here: androidforums .c o m/htc-desire-s/678126-desire-s-stuck-bootloader.html
fastboot erase cache - this got stuck on 'erasing cache', nothing happened afterwards
fastboot oem rebootRUU - this wrote "..." and nothing else happened
Is there anything else I can try?
ROOT
http://forum.xda-developers.com/showthread.php?t=2348266
http://forum.xda-developers.com/showthread.php?t=1178912
http://forum.xda-developers.com/wiki/HTC_Vision
How To Get R/W Access (Permanent Root / "Permaroot") using gfree v1.0[edit]
Prerequisites
Having the proper USB drivers installed - HTC Sync including Windows USB Drivers for the Vision
Disable auto-run or uninstall Visionary if you have it (It's important!)
adb (installed as part of the Android SDK.) See this guide on how to install/setup adb on your PC.
The HTC Desire Z with a firmware version higher than 1.34, T-Mobile G2 with a firmware version higher than 1.22 and the Desire HD with a firmware version higher then 1.32 have to be downgraded before proceeding.
Downgrading HTC Desire Z, T-Mobile G2 and Desire HD
For the 1.XX firmware HTC Desire Z follow this guide Downgrade DZ till step 12 and then come back.
For the 1.XX firmware HTC Desire HD follow this guide Downgrade HD and then come back.
For the 2.XX firmware HTC Desire Z/Desire HD and T-Mobile G2 follow this guide GUIDE Downgrade G2 2.13.531.8 (2.3.3 T-Mobile Rom w/ S-ON) & DZ 2.3.3 w/ S-ON" and come back. The history can be found in this thread New exploit works with Gingerbread! and Desire Z users see this posting of the thread Desire Z explanation.
Please use your brain when following these postings / guides. Especially make sure that you use a PC10IMG.zip for your device!
1. Necessary files
psneuter psneuter.zip (md5sum 89c2dec8d72d87b4c669f44dd31c8d17)
gfree v1.0 gfree_10.zip (md5sum 0bc9fc22bda897c765b02066f8a3c83b)
root_psn root_psn.zip (md5sum c8fe38ef55eb8951def9ff17b2eb99c1)
Superuser package su-2.3.6.2-efgh.zip (md5sum 43d9a40b63e916635d5ad7ca32433fab)
1.1. engineering hboot
Download the appropriate HBOOT for your phone:
T-Mobile G2: vision.hboot-0.76.2000.zip / Mirror (md5sum 7669AE12DC2FAA10AE555A164980EFD0)
HTC Desire Z: vision.hboot-0.84.2000.zip / Mirrors in this thread (md5sum 2CE1BDD5E4C1119CCFCECB938710D742)
HTC Desire HD: ace_glacier.hboot-0.85.2007.zip (md5sum df4fd77f44993eb05a4732210d2eddc6)
Note that the md5sums are for the actual hboot img contained within the zip file, not the for the zip file itself. Note also that the dz, g2, and dhd each use their own version of the engineering boot, as the phones are partitioned differently. (If you have previously installed the wrong HBOOT for your phone, you may need to reflash everything after partition 18)
1.2. clockwork recovery
Download the appropriate clockwork recovery for your phone:
ClockworkMod Recovery 5.0:
T-Mobile G2 and HTC Desire Z: recovery-clockwork-5.0.2.7-vision.img (md5sum 87a428549440894dbe2f96dd5efc4fb5)
HTC Desire HD: recovery-clockwork-5.0.2.0-ace.img (md5sum b8d77b9352dcbb41839e45342ea35658)
ClockworkMod Recovery 5.8 (touch):
T-Mobile G2 and HTC Desire Z: recovery-clockwork-touch-5.8.1.0-vision.img (md5sum b21aa5a0d593b6ebce880be3316ff64a)
HTC Desire HD: recovery-clockwork-touch-5.8.1.5-ace.img (md5sum fd6abfbc459663455a25b88ca7d77442)
Rename the file to 'recovery-clockwork.img'.
2. Copy the files to the phone
Before you can adb as described below you need to enable debugging in the settings on the phone. In Settings go to "Applications -> Development" and check the "USB debugging" option.
Connect the phone to the USB of your PC. The phone will stay connected during the complete procedure.
Make sure that you do NOT turn on USB storage. There has to be a sdcard in the phone and it has to be mounted to the phone!
In the commands to run below, $ or # represent the prompt and should NOT be entered as part of the commands (in Windows this will be something like C:\> instead).
Unpack all the zip files to a directory on your PC. Open a terminal (or command window) on your PC and change the current directory to where the files are on your PC and execute these commands:
$ adb push psneuter /data/local/tmp/
$ adb push gfree /data/local/tmp/
$ adb push busybox /data/local/tmp/
$ adb push hboot-eng.img /data/local/tmp/
$ adb push root_psn /data/local/tmp/
$ adb push su /sdcard/
$ adb push Superuser.apk /sdcard/
$ adb shell chmod 755 /data/local/tmp/*
2. clockwork recovery for T-Mobile G2 and HTC Desire Z
To copy your clockwork recovery execute the following command in the terminal or command window
$ adb push recovery-clockwork.img /data/local/tmp/recovery.img
3. Temporary root
In the terminal (or command window) execute these commands:
$ adb shell /data/local/tmp/psneuter
$ adb shell
after the last command you should have a root shell in adb (this is indicated by a # prompt). Leave this terminal (or command window) that contains the root shell open.
4 S-OFF, root and its friends Super-CID, SIM-unlock, engineering hboot, clockwork recovery and root
In the following section we are trying to gain write access to the emmc by power cycling it.
We recommend to install the engineering hboot as part of the gfree procedure.
In the root shell (indicated by the #) that you got in the Temporary root section execute the following commands:
# cd /data/local/tmp
# ./gfree -f -b hboot-eng.img -y recovery.img
# ./root_psn
# sync
Wait a few seconds for the changes to "take".
4.1. Automatic gfree hboot verification
As it is very important that the hboot was installed correctly gfree calculates md5sums of the partition. It will calculate the following 3 checksums
md5sum #1 - checksum of partition 18 before the installation
md5sum #2 - checksum of the hboot image that should be installed
md5sum #3 - checksum of partition 18 after the installation
gfree will check the md5sums and give you a proper success or error message. The messages are explained in detail at gfree-wiki
The messages that you want to see are either:
md5sum #1 == md5sum #2 - the hboot image is already installed -> skipping installation
or
md5sum #3 == md5sum #2 - the hboot image was successfully installed -> OK!
If you get a different error message you should run for help at #G2ROOT on Freenode.
If you got one of the two success messages described above -> You are fine, Reboot your phone by executing the following command in the root shell (indicated by the #):
# reboot
5. Verify the success of gfree
You can verify the success of gfree by using gfree_verify.
Download gfree_verify.zip from gfree_verify_v01.zip (md5sum 8e3535fd720d19fa0aec4eb711b897c4)
Unzip gfree_verify_v01.zip to a place on your PC.
Open a terminal (or command window) on your PC and change the current directory to where the files are on your PC and execute these commands:
$ adb push gfree_verify /data/local/tmp
$ adb shell chmod 755 /data/local/tmp/gfree_verify
$ adb shell
In this shell:
Remark: When you run su for the first time in the adb shell make sure the the screen of the phone is unlocked. Because when you enter the command the Superuser app will show up and ask you if you want to grant superuser access to app Unknown (2000).
Check the Remember check box and click allow.
$ su
# cd /data/local/tmp
# stop ril-daemon
# ./gfree_verify
You should see the following output:
gfree verify_cid returned:
@cid: 11111111
OK
gfree verify_secu_flag returned:
@secu_flag: 0
OK
gfree verify_simlock returned:
@simlock= 00
OK
Start the interface layer again (IN THE ADB SHELL ON YOUR PC):
# start ril-daemon
Did it work? Here's what you're looking for:
@cid: 11111111 <--- this response means you have superCID!
@simlock= 00 <--- this means your simlock is off.
@secu_flag: 0 <--- this means your radio is S-OFF.
6. Backup and cleanup
During the process gfree created backups of the partitions that it changed on your sdcard in /sdcard/
The files are called /sdcard/part7backup-.bin, part18backup-<time>.bin (if you installed hboot) and part21backup-<time>.bin. It is highly recommended that you copy these files to a save location on your PC and keep them!
You can delete the files in /data/local/tmp they are not needed anymore.
7. Next steps
Find a custom rom that you would like to install and install it using the clockwork recovery.
Enjoy the freedom of your phone.
If you like free phones and our work we would like to ask you to support the EFF.
Support the EFF[edit]
or
http://forum.xda-developers.com/showthread.php?t=1097977
I am not that tech-savvy, but I want to root my Htc-Evo-4g. It runs on a MVNO called FreedomPop. Can I get a one click installer from the computer or something easy to do? And a video showing me how to do it? And could you show me some absolutely need to get things when rooted? Thanks :laugh:
Evo4gOwner said:
I am not that tech-savvy, but I want to root my Htc-Evo-4g. It runs on a MVNO called FreedomPop. Can I get a one click installer from the computer or something easy to do? And a video showing me how to do it? And could you show me some absolutely need to get things when rooted? Thanks :laugh:
Click to expand...
Click to collapse
Some more info would be useful. Reboot to the bootloader and list your Hboot version. If you don't know how to do this, power the phone completely off. Once it's off, hold down the volume down button and the power button until the bootloader screen appears. Your Hboot version will be listed in one of the lines of info in the top left left corner of your screen. To reboot your phone, simply use the volume buttons to navigate the bootloader menu and highlight the "Reboot" option, then use the power button to select. The phone will then reboot to the Android OS.
Rooting
Evo4gOwner said:
I am not that tech-savvy, but I want to root my Htc-Evo-4g. It runs on a MVNO called FreedomPop. Can I get a one click installer from the computer or something easy to do? And a video showing me how to do it? And could you show me some absolutely need to get things when rooted? Thanks :laugh:
Click to expand...
Click to collapse
I had this whole thing written up, but my post hiccupped. My phone was originally on Sprint then switched to Ting. The carrier info was not affected by RUU or rooting. I very recently ran the RUU back to stock and re-rooted. Sorry, I don't have links, but I do have the filenames (and I do have the files so I could upload them somewhere).
The stickies here will have more background info. I'm a techie so I only take the notes I need to get by, but like to have a step-by-step so I'm fairly thourough.
There used to be a one-click sort of option, but HTC took that ability away. None of the steps are super hard but it's nice to have a techie background. The linux LiveCD may be scary for the inexperienced.
Here are my notes:
The steps to rooting this phone (any HTC are) -
Prerequisite: Android SDK (or at least fastboot and adb - when you connect your phone to the PC "adb devices" should identify it)
1. Unlock bootloader using HTCdev.com
WARNING: THIS WILL FACTORY RESET YOUR PHONE
Select Device - All Other Supported Models
Settings->Battery and uncheck Fast boot
Hold Volume Down + Power
Fastboot (Volume buttons to move, power to select)
Connect to PC
run "fastboot oem get_identifier_token"
Copy result (minus INFO) Right Click > Mark > highlight the block of text > Right click to copy (include start and end)
Copy emailed Unlock_code.bin to where fastboot.exe is
*** START HERE IF YOU ALREADY HAVE Unlock_code.bin ***
run "fastboot flash unlocktoken Unlock_code.bin"
Volume buttons to move, power to select
to relock your boot loader run "fastboot oem lock"
2. Install custom recovery (TWRP in my case)
Enable USB Debugging
Settings - More - Mobile Network Sharing - Check HTC Sync Manager
or Developer Options - Check USB Debugging ???
copy the SuperSU.zip to the SD Card
copy the UPDATE-SuperSU-v2.01.zip to the SD Card (you may be able to go straight to 2.01)
reboot to bootloader
go into fastboot
fastboot.exe flash recovery TWRP-Recovery-2.7.1.0b-jewel-CPTB.img
fastboot erase cache
go into bootloader
go into recovery
it may boot normal the first time
if it does shut down
boot into bootloader
and retry fastboot - recovery
3. Use TWRP to install SuperSU to get rooted, or just install a rooted rom.
in TWRP, choose install
navigate to your SuperSU.zip
install it
choose install
navigate to your UPDATE-SuperSU-v2.01.zip
install it
choose reboot system
4. Follow the instructions in S-Off_instruct.txt to get S-Off
--
To run the RUU (which puts your phone back into a stock build) I needed to relock the bootloader
boot into bootloader
fastboot
fastboot oem lock (in android sdk)
prerequisites:
you need to be "relocked"
set Dev Options - USB debugging is on
run the RUU as admin in Windows
RUU_JEWEL_CL_JB43_SENSE50_MR_Sprint_WWE_4.13.651.4_R…igned_one_step.exe
full name RUU_JEWEL_CL_JB43_SENSE50_MR_Sprint_WWE_4.13.651.4_Radio_1.13.11.1105_NV_3.02_003_PRL25007_release_353492_signed_one_step.exe
note: can run "adb reboot bootloader" rather than holding power and volume down to get into the bootloader
--
After running Firewater S-Off
(bootloader info)
*** TAMPERED ***
*** UNLOCKED ***
JEWEL PVT SHIP S-OFF RL
HBOOT-2.10.0000
RADIO-1.13.11.1105
OpenDSP-V33.1.0.45.1128
eMMC-boot
Mar 4 2014,14:26:40:1728
-- (Settings - About - Software info)
Android 4.3
Sense 5.0
Software 4.13.651.4
HTC API 5.45
PCI 3.02_003
PRL 24018
=============================================
contents of S-Off_Instruct.txt:
# To get S-Off on an HTC Evo 4G LTE (Jewel) with HBoot 2.10
#
# Boot a Linux 32 bit LiveCD (such as Ubuntu 12.04)
# these apps are in the Linux32BitApps folder
extract android-studio zip to ~/Downloads
extract jdk zip to ~/Downloads
copy firewater to ~/Downloads
sudo update-alternatives --install "/usr/bin/javac" "javac" "/home/ubuntu/Downloads/jdk1.8.0_05/bin/javac" 1
sudo update-alternatives --install "/usr/bin/java" "java" "/home/ubuntu/Downloads/jdk1.8.0_05/bin/java" 1
sudo update-alternatives --set "javac" "/home/ubuntu/Downloads/jdk1.8.0_05/bin/javac"
sudo update-alternatives --set "java" "/home/ubuntu/Downloads/jdk1.8.0_05/bin/java"
sudo nano /etc/profile
# add the text below to the end
JAVA_HOME=/home/ubuntu/Downloads/jdk1.8.0_05
PATH=$PATH:$JAVA_HOME/bin:/home/ubuntu/Downloads/android-studio/sdk/platform-tools
export JAVA_HOME
export PATH
ANDROID_SDK_HOME=/home/ubuntu/Downloads/android-studio/sdk
export ANDROID_SDK_HOME
# reload system-wide PATH
. /etc/profile
cd ~/Downloads/android-studio/bin
./studio.sh
# firewater
# http://firewater-soff.com/instructions/
# copies the file to the phone and runs it locally on the phone
adb reboot # <-important!!!!
adb wait-for-device push firewater /data/local/tmp
adb shell
su
chmod 755 /data/local/tmp/firewater
/data/local/tmp/firewater
#--------------------------------------------------
# Notes for installing java from a tar.gz file for normal usage
#sudo mkdir -p /usr/lib/jvm
## copy jdk zip to /usr/lib/jvm
#cd /usr/lib/jvm
#sudo tar zxvf jdk-8-linux-i586.tar.gz
#sudo rm jdk-8-linux-i586.tar.gz
#sudo update-alternatives --install "/usr/bin/javac" "javac" "/usr/lib/jvm/jdk1.8.0_05/bin/javac" 1
#sudo update-alternatives --install "/usr/bin/java" "java" "/usr/lib/jvm/jdk1.8.0_05/bin/java" 1
#sudo update-alternatives --set "javac" "/usr/lib/jvm/jdk1.8.0_05/bin/javac"
#sudo update-alternatives --set "java" "/usr/lib/jvm/jdk1.8.0_05/bin/java"
sudo nano /etc/profile
# add the text below to the end
## JAVA_HOME=/usr/lib/jvm/jdk1.8.0_05
## PATH=$PATH:$JAVA_HOME/bin
## export JAVA_HOME
## export PATH
Hello friends,
I have Kindle Fire HD 8.9. I installed CM 11 on it six months ago using this method http://forum.xda-developers.com/showthread.php?t=2128175 and have been using it without any major problem since then. But I feel sluggishness in its performance so I want to switch back to stock Amazon OS. I had made a backup of stock OS using the method described in above mention thread, i.e.
adb shell su -c "dd if=/dev/block/mmcblk0boot0 of=/sdcard/boot0block.img"
adb shell su -c "dd if=/dev/block/platform/omap/omap_hsmmc.1/by-name/boot of=/sdcard/stock-boot.img"
adb shell su -c "dd if=/dev/block/platform/omap/omap_hsmmc.1/by-name/recovery of=/sdcard/stock-recovery.img"
adb shell su -c "dd if=/dev/block/platform/omap/omap_hsmmc.1/by-name/system of=/sdcard/stock-system.img" # This will take a few minutes
adb pull /sdcard/boot0block.img
adb pull /sdcard/stock-boot.img
adb pull /sdcard/stock-recovery.img
Now I have those four files (bootblock.img, stock-boot.img, stock-recovery.img and stock-system.img) on my HDD.
If I want to go back to stock OS, I would do following steps, and I want to know if that is the proper way to proceed. and is there something I must do during the whole process in order to succeed or must be mindful of?
Plug in your fastboot cable and reboot so that you see the fastboot screen and enter the following commands:
Code:
fastboot -i 0x1949 flash boot boot.img
fastboot -i 0x1949 flash recovery recovery.img
fastboot -i 0x1949 flash system system.img # This one will take a few minutes
fastboot -i 0x1949 reboot
or should I follow instructions given here http://forum.xda-developers.com/showthread.php?t=2011126
some suggestions or instructions would be of great help. Thank you.
Both serve.
If you use your files you will return to the version that originally had in the tablet. If you use the link, you will return to the above versions (8.1.4, 8.1.3 or 8.1.2).
I do not recommend re-stock. CM11 is faster than any stock.
Yes, I did find CM11 much productive than stock Amazon OS but over time I witnessed deterioration in performance. I am in no way trying to say that it is because of CM,it could have been low hardware of Kindle.
Anyway, I used the backup made by TWRP and restored Kindle to its initial state(i.e. rooted and Google Play installed). At this moment I am on version 8.4.9. I have two questions, what if I install latest OTA? Would I loose TWRP and Root? and eventually ability to install a new ROM again? Or TWRP would be still there after OTA?
After latest OTA 8.5.1, TWRP and root permission is gone and Kindle is back to its original condition.
By Hashcode, Senior Recognized Developer on 1st February 2013, 10:57 AM over 5 years ago
STEP 1. Backup your stock partitions to your own HD for later if you need disaster recovery:
Code:
adb shell su -c "dd if=/dev/block/mmcblk0boot0 of=/sdcard/boot0block.img"
adb shell su -c "dd if=/dev/block/platform/omap/omap_hsmmc.1/by-name/boot of=/sdcard/stock-boot.img"
adb shell su -c "dd if=/dev/block/platform/omap/omap_hsmmc.1/by-name/recovery of=/sdcard/stock-recovery.img"
adb shell su -c "dd if=/dev/block/platform/omap/omap_hsmmc.1/by-name/system of=/sdcard/stock-system.img" # This will take a few minutes
adb pull /sdcard/boot0block.img
adb pull /sdcard/stock-boot.img
adb pull /sdcard/stock-recovery.img
adb pull /sdcard/stock-system.img # This will take a few minutes
with that being said here is what happens, i can see adb is working
C:\adb>adb devices
List of devices attached
B0CC060324930545 device
C:\adb>adb shell su -c "dd if=/dev/block/mmcblk0boot0 of=/sdcard/boot0block.img"
/system/bin/sh: su: not found
C:\adb>
I could go on on but, that would be more gibberish.
So, what is wrong? Did the commands change? Is my path set wrong on my pc? Is there a updated thread i just have not come across yet? Anyone?
I'll thank you now for any help
Nothing changed. If you get the device to show up with the adb devices command, then everything's theoretically set up. The only reason you're getting an error with su not being found is that you aren't rooted. Here's a quick way to get root (like actually super simple, considering you already have ADB working):
1) download the attached 8.1.4 bootloader file (this is ripped straight from my Kindle before I "upgraded" to 8.5.1 to test this out). you may consider placing it in the same folder as the adb program. Also download SuperSU and the latest TWRP build for this device.
2) shut down the kindle and make sure it's plugged in.
3) run fastboot -i 0x1949 getvar product, then power the kindle on. when you see "fastboot mode" on the kindle, you should see something in the command prompt that begins with "Jem". if you do, then it's working.
4) type fastboot -i 0x1949 flash bootloader jem_8-1-4_bootloader.img to flash the 8.1.4 bootloader. this is ESSENTIAL because the kindle won't boot custom (unsigned) images otherwise. more explanation below...
5) next, type fastboot -i 0x1949 flash recovery twrp.img, where twrp.img is the file name of the TWRP image you downloaded earlier.
6) type fastboot -i 0x1949 oem recovery to kick the Kindle into recovery mode. if all goes well, you should see "TWRP" on your device after a few moments.
7) copy the SuperSU zip you downloaded to the kindle's internal storage. then on the kindle, tap Install. Next, on the side menu to the left, swipe up from the bottom and tap "sdcard" (referring to the internal storage that you see on the computer when the kindle's plugged in). Tap the SuperSU .zip, and then swipe where indicated. Feel free to reboot the system, and then voila, you're rooted. You should be able to run those backup commands. As a bonus, you won't have to download TWRP or the bootloader image from that virus-laden d-h.st site - avoid it like the plague.
8) Because TWRP's already flashed, you can type adb reboot recovery from the stock OS to begin flashing a new ROM right away.
A couple side notes...
1) Because you've flashed TWRP, a custom recovery, there is no need whatsoever to run the stock recovery backup command. It's already been overwritten, and if you really need it (which, again, is highly doubted because it only lets you run a factory reset), you can actually extract the recovery image from the system partition. Just run adb pull /system/recovery-prod.img stock-recovery.img instead of the adb shell su... stock-recovery.img one.
2) You have to flash the 8.1.4 bootloader because the one you currently have is more than likely a newer version. Custom ROMs (and even recoveries like TWRP) rely on an exploit in the 8.1.4 bootloader in order to trick the device into running the image (and newer bootloaders have this exploit patched already). So technically, because the exploit has to be run every time, the bootloader is never "unlocked" - merely tricked. Without the older bootloader in place, you get what is referred to as the "red screen of death". It's not pretty, but it's not permanent either. (Just power off the kindle, and then run the fastboot command involving "getvar product" to get it to the bootloader so you can flash the 8.1.4 bootloader and go forward.)
Hope this helps!