http://forum.xda-developers.com/showthread.php?t=701835
The EVO has just been fully rooted and we should start the discussion of using the same method here for NAND access. We need to figure out what was changed to learn more about the new methods. I do not have experience in all the new images and will be unpacking them for further review. There might be stuff here very specific to the EVO and may not be repeatable on the incredible.
Information:
** Done via an engineering SPL (custom?)
** Looks as if they flash over the misc partition with mtd-eng.img
PC36IMG.zip File List:
* android-info.txt
ModelID: PC3610000
CIDNUM: SPCS_001
MainVer: 1.17.651.1
HbootPreUpdate: 11
* boot.img
* hboot_0.76.2000.img
* microp_v04.img
* NV.img
* radio_1.36.00.04.02.img
* rcdata.img
* recovery.img
* splash1.nb0
* system.img
* tp_atmel224_16ab.img
* tp_atmelc03_16ac.img
* userdata.img
* wimax_24722.img
What files would we need for the Incredible?
1wayjonny said:
The EVO has just been fully rooted and we should start the discussion of using the same method here for NAND access.
http://forum.xda-developers.com/showthread.php?t=701835
In theory this should work just about the same for the incredible.
Click to expand...
Click to collapse
toastcfh said:
This process will allow you to unlock Nand protection on all partitions at all times via Engineering SPL.
Click to expand...
Click to collapse
Don't think it's going to help us any...
dew.man said:
Don't think it's going to help us any...
Click to expand...
Click to collapse
You might be right as I missed that specific line but this thread is needed anyways. =)
If anyone gets a chance, please unpack mtd-eng.img for further discussion working now and tied up...
I was just trying to break root on my DI with *228 when I noticed it 'unlocks' SPL to add PRL data. Can we use adb to sneak in there and replace parts of the Nand?
-------------------------------------
Sent via the XDA Tapatalk App
rynosaur said:
I was just trying to break root on my DI with *228 when I noticed it 'unlocks' SPL to add PRL data. Can we use adb to sneak in there and replace parts of the Nand?
-------------------------------------
Sent via the XDA Tapatalk App
Click to expand...
Click to collapse
Well that question gets brought up a lot and this happens on non-android phones. Could it do something that we do not know about?
Sure but most likely not
1wayjonny said:
Well that question gets brought up a lot and this happens on non-android phones. Could it do something that we do not know about?
Sure but most likely not
Click to expand...
Click to collapse
SPL - Service Programming Lock (activation)
SPL - Second Program Loader (boot-loader)
The thread is not needed, we will open one when we release nand flash. The desire method (what evo uses) won't help as we have no eng hboot. but rest assured, a solution is close if not already known.
To clarify all they were doing is using root to change the main version in misc partition thus tricking the phone into accepting a downgrade it woudn't have otherwise. you could do this to flash the 0.75/0.76 ruu's if you want.
Shadowmite said:
The thread is not needed, we will open one when we release nand flash. The desire method (what evo uses) won't help as we have no eng hboot. but rest assured, a solution is close if not already known.
To clarify all they were doing is using root to change the main version in misc partition thus tricking the phone into accepting a downgrade it woudn't have otherwise. you could do this to flash the 0.75/0.76 ruu's if you want.
Click to expand...
Click to collapse
So basically what you're saying is we basically have it pretty much done?! Just have to finish up a few things and should be done within the next week?!
Shadowmite said:
The thread is not needed, we will open one when we release nand flash. The desire method (what evo uses) won't help as we have no eng hboot. but rest assured, a solution is close if not already known.
Click to expand...
Click to collapse
Wow, nice to see things coming along so quickly. The G1/Dream didn't get a rooted .nbh for 3 months after release, and only got the engineering SPL because someone at HTC f-ed up and sent Tmo a refurbished G1 with the engineering SPL still installed (lolz on that one), so this is good news and obvious sign that people are really dedicating their time and attention to making sure the masses can run all kinds of crazy ROMs or brick their DIs at will
Related
Warning: This method hasn't been throughly tested. It could brick your HTC Click (Tattoo). In either situation, I am not responsible if your phone explodes into a portable fireworks show. Should you decide to take the risk, please make sure you have backed up your data in case of a brick. Thanks.
I found an another way to flash the HTC Tattoo via HBOOT.
What I did is name 'CLICDIAG.nbh' to 'CLICIMG.nbh' and got the following:
HBOOT said:
CLICK PVT SHIP S-ON
HBOOT-0.52.0001 (CLIC10000)
MICROP-0203
RADIO-3.35.07.20
Sep 22, 2009, 14:40:39
HBOOT
Parsing [CLICIMG.nbh]
[1] MFG_DIAG
Do you want to start update?
<ACTION> Yes
<Power> No
Click to expand...
Click to collapse
Knowing that I could possibly screw up/brick my Tattoo (and make it continuously boot into the DIAG program), I aborted the update. It goes to show that the Click/Tattoo still supports the classic way of flashing ROMs (like the way we got root on the HTC Dream/G1 via DREAIMG.nbh).
I have also heard that if you get rom.zip from the RUU (go to your temp folder in Windows while the RUU is on the "Welcome" screen and search for rom.zip) and rename it to 'CLICIMG.zip' and place it in the root of your MicroSD card, the Tattoo will also detect it as a ROM and ask if you'd like to flash it.
Opinions/Suggestions/Comments, anyone?
UPDATE: Tried to flash the ROM with SU-binary, and it bombed out with the dreaded error: "Main version is old! Update fail!". I googled for a solution, it said something about 'fixing' a perfect SPL on the Magic/Sapphire. Alas, I'm not game enough to try using a different devices' firmware.
I'm tapped for ideas.
Hi.
Did you check or try the recovery partition options?
Maybe something could be done with it...
android-dls.com/wiki/index.php?title=Replace_Recovery_Partition
Just tried flashing... sadly failed with a 'signature error'.
P
Note: I was not using a goldcard, assume it wouldn't make any difference in this instance?
P
Coburn64 said:
UPDATE: Tried to flash the ROM with SU-binary, and it bombed out with the dreaded error: "Main version is old! Update fail!". I googled for a solution, it said something about 'fixing' a perfect SPL on the Magic/Sapphire. Alas, I'm not game enough to try using a different devices' firmware.
I'm tapped for ideas.
Click to expand...
Click to collapse
Bad. RUU checking rom version to prevent downgrade.
ROM with test signed keys is one of oldest.
Need to search something new...
modaco said:
Note: I was not using a goldcard, assume it wouldn't make any difference in this instance?
P
Click to expand...
Click to collapse
Since you were willing to flash it, I think trying with a goldcard is well worth the effort. It painless to create one..
It didn't help.
Coburn and I have been chatting on IRC (#modaco on freenode) and we're kinda running out of ideas at this point...
P
Does that mean you don't see a chance getting root ever or just not that way?
Any 1 root
hi guys
any 1 successfully Root/or Flashed Via Goldcard ?
-bm- said:
Does that mean you don't see a chance getting root ever or just not that way?
Click to expand...
Click to collapse
We're trying our best. The root looks grim, unless we can somehow get a S-OFF bootloader. :/
Getting a S-OFF SPL would only be possible through HTC (who hold the keys to sign it). Either we're very lucky and someone leaks such a SPL or we're dead in the water.
Next best hope is someone finding a local root exploit on the kernel or in one of the setuid binaries that come in the Tattoo.
I have updated a rooted Tattoo with rom renamed to CLICIMG.zip and and an unrooted Magic 32a with rom.zip renamed to SAPPIMG.zip and copied to and fat32 sd followed by fastboot as described earlier in this thread - and2209
Thank you man my old dead tattoo is alive now becouse of you! thanks again
Does anyone know if this will also work on the DInc?
http://forum.xda-developers.com/showthread.php?p=6800690
supagene said:
Does anyone know if this will also work on the DInc?
http://forum.xda-developers.com/showthread.php?p=6800690
Click to expand...
Click to collapse
not a chance unless/until we get an engineering build for the incredible (they tend to be hard to come by sometimes)
NAND has already been unlocked through a patched hboot on the Incredible, we're just waiting for a possible release.
Is this what you are referring to?
"Team unrEVOked is proud to announce that we and @AndroidBruce have the first HTC Incredible with a patched bootloader." - 6:00 PM Jul 16th via web
http://twitter.com/unrevoked
supagene said:
Is this what you are referring to?
"Team unrEVOked is proud to announce that we and @AndroidBruce have the first HTC Incredible with a patched bootloader." - 6:00 PM Jul 16th via web
http://twitter.com/unrevoked
Click to expand...
Click to collapse
Yup. Of course, that doesn't mean they're going to release soon, or maybe not at all, since there's a very real risk of bricking when you're ****ing with hboot.
Noob question here. I tried to search for the answer but couldn't find one.
Why would I want to do this when it seems to me that all of the options are available when I root the phone with Unrevoked3? Is there something more we gain with this full nand unlock?
Some applications try to write to /system for example AdFree so they can modify the hosts file. Currently none of the applications can actually write on the DInc because we only have write permissions when in recovery mode only. Once NAND is fully unlocked, we'll have all the applications running as expected.
supagene said:
Some applications try to write to /system for example AdFree so they can modify the hosts file. Currently none of the applications can actually write on the DInc because we only have write permissions when in recovery mode only. Once NAND is fully unlocked, we'll have all the applications running as expected.
Click to expand...
Click to collapse
I'd love to be able to use metamorph so I don't have to update themes so much... pushing apks with the phone booted really helps me to develop themes as well. Nand unlocked is something I miss about my old android phones....
heavensblade23 said:
Yup. Of course, that doesn't mean they're going to release soon, or maybe not at all, since there's a very real risk of bricking when you're ****ing with hboot.
Click to expand...
Click to collapse
Why would they announce and never release? If the were able to make an easy root app, I hope they can release something for the nand unlock. I wonder how long it will take them to release...
Sent from my ADR6300 using XDA App
supagene said:
Why would they announce and never release? If the were able to make an easy root app, I hope they can release something for the nand unlock. I wonder how long it will take them to release...
Sent from my ADR6300 using XDA App
Click to expand...
Click to collapse
They say they don't want to release the vulnerability they exploit for the NAND flash unlock because they don't want to to go away (get "fixed" by htc).
You can read about it at their wiki if you go to their site, select the Incredible, and select "More Info?"
ok too much misinformation seems to be getting linked together. so just this once ill comment.
we do have a few completely nand unlocked devices now. we have some more experimentation to go with hboot before it will be worthy of release, ie the fastboot commands. patching it is a slower process as you are correct, its easy to brick. we will be planning a release but do not presently have a timeframe. one problem is while with recovery a error would be corrected by trying again, hboot will brick. so if we do release its going to be a slightly technical process requiring more thought and knowledge so that you have the best chance of success.
aotothemax said:
They say they don't want to release the vulnerability they exploit for the NAND flash unlock because they don't want to to go away (get "fixed" by htc).
You can read about it at their wiki if you go to their site, select the Incredible, and select "More Info?"
Click to expand...
Click to collapse
The vulnerability has already been shown... i have a copy of the zip saved on my PC and can unlock my nand at will.. You go into hboot and type in some commands and then reboot and upon reboot into android your NAND is unlocked and you can do anything you want including write to /system while in actual android... then upon rebooting your phone a second time your nand relocks by default...
The reason i know this works is that i did the nand unlock and AdFree was able to successfully install a new hosts file on my phone with no problems.. and that program needs specific /system write access while in android itself... also i can remove files in my /system folder while in android using root explorer on the phone itself, without have to do adb at all
what unrevoked is trying to do now is make it permanent where it stays unlocked after a reboot.. but for now its pretty simple, all i have to do is not turn off my phone and my nand will stay unlocked
Shadowmite and Joe92T, thanks for clearing things up for everyone. I hope nobody goes looking for that zip and bricks their device before unrEVOked's release.
mahkee said:
Shadowmite and Joe92T, thanks for clearing things up for everyone. I hope nobody goes looking for that zip and bricks their device before unrEVOked's release.
Click to expand...
Click to collapse
The whole thread it was located in has been deleted because it was a leaked file and not an official release,the only people that have it are unrevoked and the people lucky enough to download the attachment before the mods found out
I'm glad it's being worked on. Once it works running true linux on the phone will be possible as would dual booting the phone.
Oh, I didn't know that. Thanks for clearing that up!
Sent from my ADR6300 using XDA App
sorry. Edited for your protection
The Dinc is my first android phone (from blackberries), but from what I can tell, HTC seems to not be as anal about exploits found as some other Android phone makers. I like that.
Does a full NAND unlock allow deleting system apps that were previously not able to be uninstalled with the device on ?
Yes that's what it means,
Sent from my HTC Incredible using Tapatalk
This is for devs only. It's fastboot flash enabled and will allow you to fastboot flash things from bootloader. Be careful with it! You need s-off to flash this, rename accordingly. I'm not giving more instructions cause if you can't figure it out from this, you don't need it...
http://depositfiles.com/files/n6o10wtkq
(note, if you go from .92 to this, you need to fastboot flash boot boot.img to get a new kernel image on, there are some differences in storage it appears and you might not boot up without this at first)
(note2: DO NOT FLASH NV.IMG!!!!! You have been warned!)
Thanks go to stericson; he hooked us up long ago and it took till now to see what we had...
Wow Shadowmite, you guys are awesome!! I won't find much personal use from this(to be honest i'm to afraid to screw around with fastboot), but regardless. Great work! Your work is immensely appreciated.
You guys are awesome. Thanks.
Ditto awesome thanks unrevoked team!! Hmm .. are rtask commands enabled with MFG and s-off now?
please dont give us credit for this one. This is just a file leak thanks to stericson here on xda-devs... Enjoy... and don't flash nv.img...
Dang, I was looking forward to flashing nv.img.
May I ask what happens? Other than just bad things?
adrynalyne said:
Dang, I was looking forward to flashing nv.img.
May I ask what happens? Other than just bad things?
Click to expand...
Click to collapse
Very Very Very bad things, trust me. Just dont do it.
Fantastic. Just fantastic.....
How about we get a list going of all these new commands and what they do.
Code:
C:\AndroidSDK\tools>fastboot oem ?
... INFOcommand list
INFOmb
INFOmh
INFOmw
INFOew
INFOeh
INFOeb
INFOmmu
INFOram_test
INFOjump
INFOtest
INFOsdtest
INFOeraseconfig
INFOwriteconfig
INFOreadconfig
INFOwritesku
INFOreadsku
INFOrflash
INFOtflash
INFOblock_test
INFOpartition_test
INFOrbchk
INFOerasesd
INFObtrouter
INFOtick
INFOheaptable
INFOemapi
INFOemapiTest
INFOemapiCountryID
INFOemapiWlanMac
INFOemapiSetDefCal
INFOemapiReadCal
INFOlr
INFOimgcrc
INFOresetautoimage
INFOresetpreferdiag
INFOresetRUUflag
INFOwriteserialno
INFOreadserialno
INFObattcheck
INFOgotofastboot
INFOgotohboot
INFOwritemid
INFOusbtestmode
INFOeraseWifiFlash
INFOerase
INFOreadmbserialno
INFOlistpartition
INFOerasebcid
INFOwritebcid
INFOreadbcid
INFOfmrouter
INFOresetuP
INFObdaddress
INFOwMfgTp
INFOrMfgTp
INFOemptypagecheck
INFOsaveprt2sd
INFOsavemem2sd
INFOsavefb2sd
INFOemapiInit
INFOemapiChannel
INFOemapiRate
INFOemapiRateset
INFOemapiCountry
INFOemapiTXpwr1
INFOemapiPkteng_start
INFOemapiPkteng_stop
INFOemapiOut
INFOemapiFqacurcy
INFOemapiCrsuprs
INFOemapiUp
INFOemapiDown
INFOemapiMpc
INFOemapiCounters
INFOemapiVersion
INFOemapiEtheraddr
INFOemapinRate
INFOfl
INFOloaddiag
INFOlnb
INFOinit_a1026_fw
INFOgpiow
INFOgpior
INFOmddiw
INFOmddir
INFOclock
INFOi2cr
INFOi2cw
INFOulpi
INFOchangeCid
INFOpowertest
INFOread_l2_acc_fuse
INFOfdisk_emmc
INFOlist_partition_emmc
INFOset_partition_emmc
INFOload_emmc
INFOcheck_emmc
INFOerase_emmc
INFOupdate_emmc
INFOread_emmc
INFOwrite_emmc
INFOtest_emmc
INFOsector_erase_emmc
INFOkeytest
INFOheap
INFOboot
INFOreset
INFOpowerdown
INFOrebootRUU
INFOrtask
INFOtask
INFOenableqxdm
INFOgencheckpt
OKAY [ 0.425s]
finished. total time: 0.430s
can someone reupload this I seem to have accidentally deleted my copy.
This is something I have missed dearly after switching from my N1, makes it sooooo simple to recover after testing. Thanks to everyone involved
Is it just me, or is the link broken already?
http://db.tt/hWMpOWL
Do not try and flash this on a Slcd device!!!!
I have been running .77 mfg since its release and just now noticed that /dev/block/mmcblk0p1 which contains /data partition on mfg is sized 187mb and on later releases is sized 748mb all other partitions are sized the same including the total size of the emmc which is mmcblk0.
drellisdee said:
I have been running .77 mfg since its release and just now noticed that /dev/block/mmcblk0p1 which contains /data partition on mfg is sized 187mb and on later releases is sized 748mb all other partitions are sized the same including the total size of the emmc which is mmcblk0.
Click to expand...
Click to collapse
yeah .92 updated the partition for better use of memory.
doug piston said:
Do not try and flash this on a Slcd device!!!!
Click to expand...
Click to collapse
Hey doug, do you off hand know what nv.img is? I noticed it is updated with the official RUUs but I do not believe it is with the PB31IMG RUU compilations.
I mean, I assume NVRAM, but I'm interested in what exactly it does.
Thanks!
tdiman said:
Hey doug, do you off hand know what nv.img is? I noticed it is updated with the official RUUs but I do not believe it is with the PB31IMG RUU compilations.
I mean, I assume NVRAM, but I'm interested in what exactly it does.
Thanks!
Click to expand...
Click to collapse
Open up a PB31IMG of the full RUU. Lets say you open the 3.26 build, you'll find
nv_MFG_VZW_1.70_0825_PRL58006.img
So it is there. Never looked into though but by the name I will guess its the PRL?
link is dead
eljean said:
link is dead
Click to expand...
Click to collapse
Should be since it is an ancient hboot. .92 is current and is needed for gingerbread ROMS
So I haven't tried to use this yet, but it was dumped from a devkit atrix that supposedly has a bootloader that doesn't blow
http://www.mediafire.com/?d13i7uxrhw38y7o
SHA: FDA1FDBFD70628CBF1C79361525168847A00830B (motoboot.bin)
DO NOT FLASH THIS!
jimmydafish said:
this is P3Droid again,
I have all Dev phones with matching consumer phones, granted these are on VZW, but in the past placing a Dev phone bootloader on a consumer phone would result in a system that is inoperable (basically a soft bricked device). I would strongly urge you to not modify this file until you have a way to backup and restore this file.
This is just a word of caution from someone and a group that actually possesses both dev and consumer model phones and have already attempted what you are proposing here.
either way good luck, but do not return the device to ATT if you break it.
Click to expand...
Click to collapse
designgears said:
So I haven't tried to use this yet, but it was dumped from a devkit atrix that supposedly has a bootloader that doesn't blow
http://www.mediafire.com/?q053u356h5u52zd
It can be flashed with Qualcomm QPST
http://www.filecrop.com/QPST.html
Click to expand...
Click to collapse
the link is dead
Does "doesn't blow" mean unlocked/non-encrypted?
t0dbld said:
the link is dead
Click to expand...
Click to collapse
Which? I was able to get a copy of motoboot.bin (I think, anyway. designgears, could you post a md5/sha hash of the bin file for us?)
FYI, here's what I have for the file I was able to download:
Code:
$ shasum motoboot.bin
fda1fdbfd70628cbf1c79361525168847a00830b motoboot.bin
really i cant tells me file has been removed can you mirror or send ?
"Doesn't blow" should mean "lets us load our own kernels" in this context I think
now to figure out how to get the dev bootloader onto our phones..
sorry, was uploading a compressed version
designgears said:
sorry, was uploading a compressed version
Click to expand...
Click to collapse
ok now to test... this would be great esp considering they jsut anounced on twitter that zoom comes with locked/unlockable bootloader
t0dbld said:
ok now to test... this would be great esp considering they jsut anounced on twitter that zoom comes with locked/unlockable bootloader
Click to expand...
Click to collapse
damn, wish we would have gotten that.
designgears? post the SHA or MD5 checksum of the bin file please? I want to get cracking but want to ensure my downloaded file is intact first.
perdurabo2 said:
designgears? post the SHA or MD5 checksum of the bin file please? I want to get cracking but want to ensure my downloaded file is intact first.
Click to expand...
Click to collapse
already did
perdurabo2 said:
designgears? post the SHA or MD5 checksum of the bin file please? I want to get cracking but want to ensure my downloaded file is intact first.
Click to expand...
Click to collapse
LOOKS PROMISING!!! so far went through with hex editor and i see no signatures etc !!!
lol so excited cant spell or type
Slow Down Everyone...
this is P3Droid again,
I have all Dev phones with matching consumer phones, granted these are on VZW, but in the past placing a Dev phone bootloader on a consumer phone would result in a system that is inoperable (basically a soft bricked device). I would strongly urge you to not modify this file until you have a way to backup and restore this file.
This is just a word of caution from someone and a group that actually possesses both dev and consumer model phones and have already attempted what you are proposing here.
either way good luck, but do not return the device to ATT if you break it.
Not to be too dense here, but how would we make use of this? Wouldn't we still be at square one regaring not being able to get this onto the device?
Sent from my MB860 using XDA App
t0dbld said:
LOOKS PROMISING!!! so far went through with hex editor and i see no signatures etc !!!
lol so excited cant spell or type
Click to expand...
Click to collapse
You are not listening and I'm trying to help you not brick your device. DO NOT FLASH THAT BOOTLOADER or you phone will not work...there are a lot more signatures than just the bootloader, in fact if you don't hack/crack the mbr or change the signing keys and verification in the NVRAM you will just sit there with a brand new paperweight.
perdurabo2 said:
designgears? post the SHA or MD5 checksum of the bin file please? I want to get cracking but want to ensure my downloaded file is intact first.
Click to expand...
Click to collapse
smiths-MacBook-Pro:~ smith$ shasum /Users/smith/Downloads/motoboot.bin
fda1fdbfd70628cbf1c79361525168847a00830b
smiths-MacBook-Pro:~ smith$ md5 /Users/smith/Downloads/motoboot.bin
MD5 (/Users/smith/Downloads/motoboot.bin) = f3cb372a7498f175b53dc7881e4bd3c2
P3Droid, you have past experience with Dev phones and retail phones, what does this mean to the hacking efforts? Does an unsigned bootloader move us past any of the previous obstacles or is this just something to study?
t0dbld said:
LOOKS PROMISING!!! so far went through with hex editor and i see no signatures etc !!!
lol so excited cant spell or type
Click to expand...
Click to collapse
humancyborg said:
Not to be too dense here, but how would we make use of this? Wouldn't we still be at square one regaring not being able to get this onto the device?
Sent from my MB860 using XDA App
Click to expand...
Click to collapse
If you would like to brick your device I can teach you how to get it on, but it will require you to be rooted and running a custom recovery, the other method requires a fully released sbf file.
jimmydafish said:
You are not listening and I'm trying to help you not brick your device. DO NOT FLASH THAT BOOTLOADER or you phone will not work...there are a lot more signatures than just the bootloader, in fact if you don't hack/crack the mbr or change the signing keys and verification in the NVRAM you will just sit there with a brand new paperweight.
Click to expand...
Click to collapse
i am listening and i am not flashing anything yet .. .i heard ya before and i hear ya now
Could this bootloader work on Defy also?
I do have to say though with this Xoom news... gives us hope that maybe with GB release for atrix that was promised soon and to include 1080p it might also come with unlock/lock
I have an Incredible 2.3.4 with this taken from HBOOT
Incrediblec XC Ship S-On
HBOOT-0.92.0000
Microp-0417
Touch Panel-ATMEL224_16ab
Radio-2.15.10.07.07
Ok, so here is my problem, I want to be rooted and I want S-off, but I cannot get anything done. The phone wouldn't recognize the SD Card, I got that taken care of. The phone does the 5 Vibrates when turning it on unless I have the USB plugged in and I do a battery pull. (This really screws up updates/RUU fixes where updates are necessary). And along those lines I tried an RUU back to 2.1 which didn't work because of the restart issue, but then I was able to run the update after booting into HBOOT USB but the RUU failed ultimately.
I've tried to gain root access through unrevoked 3.22, it simply says failed to push recovery, terminated. I've tried rooting using zergRush, it tells me that it has found a path and that its sending zergs, then it just stops without telling me what happened and kicks me back out of adb shell. This is a recurring problem, I will be in adb shell and then randomly and for no reason it was kick me out to the root of my computer.
I'm working on a Windows 7 64 bit machine, I have been using an ADB mini download, but have also tried working through the installed ADB with equal results.
If anyone has any idea of what I could be doing wrong or different please let me know. I really need some kind of help because I am at a major loss.
2.3.4 on the Incredible has not yet been rooted, therefore the rooting software (Unrevoked) has not been updated with a root method. That would be why it's not working for you. I've never tried to downgrade to an old version using an RUU, so I can't really speak to that.
Also, this was posted in the incorrect forum. You should have posted in the Q&A section, as this has nothing to do with development.
What about the radio?
I was wondering this same thing because my wife's Incredible isn't rooted, but she's on 2.3.4. If she ever asks me to root her phone to put something on it or give her some feature not otherwise available, I'd rather be prepared if possible.
While looking over the UnRevoked site, I noticed it didn't really mention the Android versions it worked with, just the radios. I wonder if it's possible to just flash the radio to 2.15.00.07.28, which is rootable, according to the UnRevoked site, and try the UnRevoked Forever tool?
The radios are pretty easy to get here after all.
I'm not recommending this without some confirmation from someone with a lot more experience rooting than I have though, so Caveat Emptor!
Just a thought.
Cheers!
keyslapper said:
I was wondering this same thing because my wife's Incredible isn't rooted, but she's on 2.3.4. If she ever asks me to root her phone to put something on it or give her some feature not otherwise available, I'd rather be prepared if possible.
While looking over the UnRevoked site, I noticed it didn't really mention the Android versions it worked with, just the radios. I wonder if it's possible to just flash the radio to 2.15.00.07.28, which is rootable, according to the UnRevoked site, and try the UnRevoked Forever tool?
The radios are pretty easy to get here after all.
I'm not recommending this without some confirmation from someone with a lot more experience rooting than I have though, so Caveat Emptor!
Just a thought.
Cheers!
Click to expand...
Click to collapse
You can flash radios in the bootloader, but, having S-ON, the zip file may need to be signed, so i'd say NO it's not possible to flash a radio w/o root.
Yeah, flashing radios with s-on is a brick magnet.
There is thread on downgrading to 2.2 and rooting in dev. It works.
Sent from my ADR6300 using XDA App
Sorry not dev but Q & A. Also it is on android forums.
Sent from my ADR6300 using XDA App
Long night....its in general search for root 2.3.4, downgrade, and s off.
Sent from my ADR6300 using XDA App
jpjj225 said:
Yeah, flashing radios with s-on is a brick magnet.
Click to expand...
Click to collapse
Actually it just wouldn't flash, because the file wouldn't be signed by HTC, so it wouldn't (shouldn't) brick the phone.
http://androidforums.com/incredible-all-things-root/427344-2-3-4-root-downgrade-s-off.html
There is the guide my friend used to do his recently acquired inc
Sent from my ADR6300 using XDA App
jpjj225 said:
Yeah, flashing radios with s-on is a brick magnet.
Click to expand...
Click to collapse
The phone won't brick. It just won't flash.
Oh sorry, thought I read that somewhere a long time ago. Something about flashing new radios is dangerous if you do it wrong. MY BAD!!!