I followed this thread : http://forum.xda-developers.com/showthread.php?t=726258 and run into serious problems that i can't seem to fix.
To be exact I am refearing to a user in that thread that mentioned he has a black screen, since version 0.33 of bootloader doesn't work for "lcd" (?)
However, since I had the same problem i followed his suggestion to use PASSIMG_Passion_KT_KR_2.15.1010.2_FRF91_release_si gned.zip from shipped-roms to get stuff working again. And it did - except the side effect that since then i have a red trackball as soon as the phone finished booting up.
I've tried all, followed the exact instruction for back to stock, formated sdcard, didn't succeed either, so now I'm stucked with this battery draining red light and researches on google gave a lot of hints in terms of moisture or overheat, no solution though.
Any help is highly appreciated.
I think the issue is in the misc partition, something might not be right there...
You currently have the misc img of a desire on your N1...
Maybe you could try to flash a default N1 misc image and PASSIMG of a non korean N1 that matches your current hboot?
Amon_RA said:
I think the issue is in the misc partition, something might not be right there...
You currently have the misc img of a desire on your N1...
Maybe you could try to flash a default N1 misc image and PASSIMG of a non korean N1 that matches your current hboot?
Click to expand...
Click to collapse
I did use the original stock image provided by modaco, unzipped it and fastbooted all the images like system, recover and so on.
Now my current boot is:
NEXUSONE PVT SHIP S-ON
HBOOT-0.35.0017
MICROP-0b15
RADIO-4.06.00.12_7
jUN 14 2010, 12:02:27
So could it be that there's a conflict in a "protected area" that can't be solved, except by the approach you suggested?
You did follow the thread in your first post and flashed the Desire misc image (mtd0.img), right? I would try to :
1. unlock your bootloader so S=OFF (fastboot oem unlock)
2. get hold of an N1 mtd0.img dump with S=OFF and flash it
Amon_RA said:
You did follow the thread in your first post and flashed the Desire misc image (mtd0.img), right? I would try to :
1. unlock your bootloader so S=OFF (fastboot oem unlock)
2. get hold of an N1 mtd0.img dump with S=OFF and flash it
Click to expand...
Click to collapse
You are the man! thank you so much!!! Time to read about mtd0.img and fire up the hex editor
Unless I find a website that generates or a file that is good enough.
But really great, I was about to wave goodbye to my Nexus
RunTimeWorld said:
You are the man! thank you so much!!! Time to read about mtd0.img and fire up the hex editor
Unless I find a website that generates or a file that is good enough.
But really great, I was about to wave goodbye to my Nexus
Click to expand...
Click to collapse
Maybe you can just ask someone to dump his N1 mtd0 partition for you...
Amon_RA said:
Maybe you can just ask someone to dump his N1 mtd0 partition for you...
Click to expand...
Click to collapse
That would be awesome, mind giving it a shot?
Don't wanna stretch your patience though..
Btw.. why don't you make a GUI to RA and sell it on the market? ;-)
RunTimeWorld said:
That would be awesome, mind giving it a shot?
Don't wanna stretch your patience though..
Btw.. why don't you make a GUI to RA and sell it on the market? ;-)
Click to expand...
Click to collapse
Try this : http://dl.dropbox.com/u/4481275/misc.img
Maybe there will be a GUI one day...
Thanks you Amon!!!
off-topic I know... But rarely do u see "popular dev's" responding to people questions/needs and for that I just wanted to pop in and say AMON_RA you are awesome!!! Thanks for everything u do that makes this community GREAT!!
/nohomo guys, just appreciation!!!
I absolutely agree and appreciate to get such a response from a pro!However, I am new to Android and trying to figure out a few things.
[Edit]I figured out about the misc partition and guess what? IT WORKS!!!![/Edit]
Amon, you helped me a big deal, thank you so much, you've triggered a dude to contribute. Big time!
I have the same problem and I tried to do the same method as Amon_Ra posted. But I get the following error message when flashing misc.img:
Code:
remote: signature verify fail
so I was wondering if I am suposed to rename the file as mtd0 and flash it trough adb shell as:
Code:
adb push mtd0.img /data/mtd0.img
adb shell
misc /data/mtd0.img
thanks!
I know that this post is too old, but i have the same problem and the link doesn't works
Amon_RA said:
Maybe you can just ask someone to dump his N1 mtd0 partition for you...
Click to expand...
Click to collapse
your link is doesnt work anymore,can you frop it again!
Seriously anyone have that image?
towfurious said:
Seriously anyone have that image?
Click to expand...
Click to collapse
What do i need do get you? I havev nexus one unlocked with br and cm7. It is slcd version. Just tell me the command
I think that it's poosible to dump the misc partition with
Code:
dump_image misc /sdcard/misc.img
(as root)
I'm not sure i dumped it correct, file is an attachment.
It's a vodafone nexus one with AMOLED.
Header2k thank you but i need dump from nexus slcd
Race55 can you dump it for me?
towfurious said:
Race55 can you dump it for me?
Click to expand...
Click to collapse
Just to confirm, there is no personal info in the misc partition right?
I looked into my dump with an hex editor. The only readable part is something like "Google" and the stock firmware version number. Don't think that there's anything personal
Edit:
In order to flash this try the "flash_image" command.
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
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
I finally successfully recovered my BootLooped Incredible after i incorrectly updated the NV item of my phone. My situation was a little different than most bootloop error because no matter which stock rom or recovery image I flash nothing would stop it from rebooting because the NV items weren't overwritten during the flash. Then I came across a solution for the EVO by cutthroatamft on how he recovered his EVO from the same Mistake but unfortunately all his files were geared toward the EVO. After much searching I accidentally came across a single comment that posted a link for the ENG-HBOOT for the incredible. Now i manage to replace all the EVO specific files with the Dinc equivalent. Below is the link to the files and instructions compile by cutthroatamft but I updated it for the Dinc. Hopefully this helps someone else that has this problem. can't post a live link but I think you can figure it out
update:
Since megaupload is down and Had some people asking for a re-up here's a mediafire link to the file
http://www.mediafire.com/?cu7hu6pu75zvskh
Also as mentioned below by eljean this should work on the SLCD as well it's just your screen will be blank during the process. For those who has this Dinc I found that if the screen is blank wait a few minutes for it to fully boot then test to see if you can execute any ADB command. If you can the just type "adb reboot oem-78" this will reboot it and put it in fastboot mode which will allow you to execute the commands in the document.
update 2:
Nevermind what I said about the ADB... this worked for me on another phone but I realize you'll probably won't get to a point where you can execute the command because your phone in a loop LOL. So I guess getting to fastboot blind folded is your only option
dknlght said:
I finally successfully recovered my BootLooped Incredible after i incorrectly updated the NV item of my phone. My situation was a little different than most bootloop error because no matter which stock rom or recovery image I flash nothing would stop it from rebooting because the NV items weren't overwritten during the flash. Then I came across a solution for the EVO by cutthroatamft on how he recovered his EVO from the same Mistake but unfortunately all his files were geared toward the EVO. After much searching I accidentally came across a single comment that posted a link for the ENG-HBOOT for the incredible. Now i manage to replace all the EVO specific files with the Dinc equivalent. Below is the link to the files and instructions compile by cutthroatamft but I updated it for the Dinc. Hopefully this helps someone else that has this problem. can't post a live link but I think you can figure it out
www megaupload . com /?d=RCZBCDDA
Click to expand...
Click to collapse
That's a great find and good little zip/guide to get it set up.
The engineering HBOOT can be quite useful for many things besides flashing/erasing certain partitions. The inc community just hasn't used it that much.
tdiman said:
That's a great find and good little zip/guide to get it set up.
The engineering HBOOT can be quite useful for many things besides flashing/erasing certain partitions. The inc community just hasn't used it that much.
Click to expand...
Click to collapse
.77 Will not work on a Slcd Inc, if on Slcd we have no eng
HELP, I am having this problem with my incredible with an SLCD i put the .77 hboot on and then put the other zip in. I couldnt see the screen so i put it in fastboot by memory. I got remote failed errors the entire time.
Should I try putting the evo Hboot on this. I have no idea what else to do.
mattjt21 said:
HELP, I am having this problem with my incredible with an SLCD i put the .77 hboot on and then put the other zip in. I couldnt see the screen so i put it in fastboot by memory. I got remote failed errors the entire time.
Should I try putting the evo Hboot on this. I have no idea what else to do.
Click to expand...
Click to collapse
DO NOT USE EVO HBOOT
I don't know how to help you but I'm almost 100 percent sure that will brick it
Sent from my DROIDX using XDA App
mattjt21 said:
HELP, I am having this problem with my incredible with an SLCD i put the .77 hboot on and then put the other zip in. I couldnt see the screen so i put it in fastboot by memory. I got remote failed errors the entire time.
Should I try putting the evo Hboot on this. I have no idea what else to do.
Click to expand...
Click to collapse
The guy above you kinda said .77 won't work with SLCD... I honestly don't know how to fix that, but do NOT flash an Evo HBOOT.
I don't wanna come back and see you saying you flashed it anyways lol.
Sent from my Droid Incredible running CM7.0.3.
im sorry to revive an old thread but I cant seem to do this everytime I try to execute a command it responds with
FAILED (Remote: Not allowed)
any help?
Boot poop?
Sent from my Synergy Rom
masully1984 said:
Boot poop?
Sent from my Synergy Rom
Click to expand...
Click to collapse
ummm what?
OMFG MAN I LOVE U SO MUCH !!! I FIXED IT !!
The error I was making is that the Hboot you provided is within a .zip file but I didnt know and then I saw. It turned the screen all black because I have a SLCD Incredible but then I just did everything basically blind folded. You just saved me $200 !!! I EFFIN LOVE U MAN, WHENEVER U COME TO NYC WE PARTYIN BRO !!!!
GRATZ
+1
I forwarded this to Eljean but apparently they found this thread first.
Way to go. I never even imagined my write-up helping the Incredible people.
New Method
I got bored and created a more streamlined version of this fix.
I hope it works, I don't have an Incredible to test with.
http://www.multiupload.com/XS5SQL8Q9K
it includes everything needed (even ruu) and it does it for you
Also if anyone has this issue for an HTC Evo I posted this same method at
http://forum.xda-developers.com/showpost.php?p=16133086&postcount=54
cutthroatamft said:
I got bored and created a more streamlined version of this fix.
I hope it works, I don't have an Incredible to test with.
it includes everything needed (even ruu) and it does it for you
Also if anyone has this issue for an HTC Evo I posted this same method at
Click to expand...
Click to collapse
Hey there, I think this is a solution to my problem... I have an Incredible S. Would it work with it, if not what would I have to change? Can you re-upload the file somewhere, all of the links are down.
Thanks, Ned
cutthroatamft said:
I got bored and created a more streamlined version of this fix.
I hope it works, I don't have an Incredible to test with.
http://www.multiupload.com/XS5SQL8Q9K
it includes everything needed (even ruu) and it does it for you
Also if anyone has this issue for an HTC Evo I posted this same method at
http://forum.xda-developers.com/showpost.php?p=16133086&postcount=54
Click to expand...
Click to collapse
Same here. This might fix a problemed dinc I have but the links are broken.
Sent from my ADR6300 using XDA App
same here it might fix my problem plz someone update the links
link
Can anyone provide a new link to this? my incredible just keeps booting up to the white screen and then rebooting. its an slcd.
I do have this file! It didn't work for me because I'm s-on bit I held on to it. Don't know how or where I could upload...mayb I can email it??..
Can you please attach it to a post in this thread? I have the same thing going on with my amoled incredible.
Thanks.
Sent from my ADR6400L using XDA Premium App
smtom said:
Can you please attach it to a post in this thread? I have the same thing going on with my amoled incredible.
Thanks.
Sent from my ADR6400L using XDA Premium App
Click to expand...
Click to collapse
it wont upload? i think the file may b too big....
strive53 said:
it wont upload? i think the file may b too big....
Click to expand...
Click to collapse
How big is it? I have an Inc that could REALLY use it. Do ya need a place to upload it to other than here?
I got notification just now that there was a 191M update to Android 5.0 on my Nexus 6. I wasn't thinking about TWRP when I tapped ok to install and of course it wouldn't since it's not the stock recovery. I flashed the stock recovery and tried to repeat the install but now the handset tells me I'm up to date.
I look at the factory image for the N6 (Shamu) and the build on Google's dev site is LRX21O but the build on the handset is LNX07M.
TWRP couldn't side load it with interaction and since the stock bootloader wasn't there .. anyone have a clue why the factory image and the installed image differ in build?
Very odd and I see nothing about an update in any thread here.
-Ben
aergern said:
I got notification just now that there was a 191M update to Android 5.0 on my Nexus 6. I wasn't thinking about TWRP when I tapped ok to install and of course it wouldn't since it's not the stock recovery. I flashed the stock recovery and tried to repeat the install but now the handset tells me I'm up to date.
I look at the factory image for the N6 (Shamu) and the build on Google's dev site is LRX21O but the build on the handset is LNX07M.
TWRP couldn't side load it with interaction and since the stock bootloader wasn't there .. anyone have a clue why the factory image and the installed image differ in build?
Very odd and I see nothing about an update in any thread here.
-Ben
Click to expand...
Click to collapse
An update hit mine the moment I took it out of the box (had to charge it). Did yours? I seem to remember it being around that size and I'm on LRX210 with mine. Yours probably just hadn't had the "day 1" update yet so you probably need that.
youareme7 said:
An update hit mine the moment I took it out of the box (had to charge it). Did yours? I seem to remember it being around that size and I'm on LRX210 with mine. Yours probably just hadn't had the "day 1" update yet so you probably need that.
Click to expand...
Click to collapse
I more or less have the same issue, my update didn't show up though until after i had unlocked/rooted/TWRP. So now i have a update noti that wont go away because i cant actually update it. I am just going to wait for a flashable ZIP for TWRP to be posted though
youareme7 said:
An update hit mine the moment I took it out of the box (had to charge it). Did yours? I seem to remember it being around that size and I'm on LRX210 with mine. Yours probably just hadn't had the "day 1" update yet so you probably need that.
Click to expand...
Click to collapse
I'll just flash the img files individually to the current Factory and reroot.
Thanks!
TacoLord187 said:
I more or less have the same issue, my update didn't show up though until after i had unlocked/rooted/TWRP. So now i have a update noti that wont go away because i cant actually update it. I am just going to wait for a flashable ZIP for TWRP to be posted though
Click to expand...
Click to collapse
I just booted into the bootloader and did the following ... and it all worked fine.
/usr/local/android/platform-tools/fastboot flash bootloader bootloader-shamu-moto-apq8084-71.05.img
/usr/local/android/platform-tools/fastboot flash radio radio-shamu-d4.0-9625-02.55.03a.img
/usr/local/android/platform-tools/fastboot flash boot boot.img
/usr/local/android/platform-tools/fastboot erase system
/usr/local/android/platform-tools/fastboot flash system system.img
./fastboot boot CF-Auto-Root-shamu-shamu-nexus6.img
The proper commands are in the 2 very short shell scripts included with the factory tarball. It was easy. It took maybe 10 minutes. The above .imgs are all you need. Do not do cache.img or userdata.img if you want to keep your apps and their data. The list above is correct in order that they need to be flash in and the commands are there. Have at it.
but this all still doesn't answer the op's original question...what is LNX07M? this is a new build different from the factory image just posted...
indianajonze said:
but this all still doesn't answer the op's original question...what is LNX07M? this is a new build different from the factory image just posted...
Click to expand...
Click to collapse
A quick google would suggest that LNX07M is the lollipop developer preview
so he was just pushed to his retail device the developer preview build?
Sounds like his phone came with the developer preview installed, and the initial update just took a few days to appear for him which he didn't manage to install so is still on the preview.
aergern said:
I just booted into the bootloader and did the following ... and it all worked fine.
/usr/local/android/platform-tools/fastboot flash bootloader bootloader-shamu-moto-apq8084-71.05.img
/usr/local/android/platform-tools/fastboot flash radio radio-shamu-d4.0-9625-02.55.03a.img
/usr/local/android/platform-tools/fastboot flash boot boot.img
/usr/local/android/platform-tools/fastboot erase system
/usr/local/android/platform-tools/fastboot flash system system.img
./fastboot boot CF-Auto-Root-shamu-shamu-nexus6.img
The proper commands are in the 2 very short shell scripts included with the factory tarball. It was easy. It took maybe 10 minutes. The above .imgs are all you need. Do not do cache.img or userdata.img if you want to keep your apps and their data. The list above is correct in order that they need to be flash in and the commands are there. Have at it.
Click to expand...
Click to collapse
Thanks! Im not great with ADB commands, but I gave it a shot. After the first line, I got "cannot open 'bootloader-shamu-moto-apq8084-71.05.img'"
Any suggestions on that! Really appreciated!
TacoLord187 said:
Thanks! Im not great with ADB commands, but I gave it a shot. After the first line, I got "cannot open 'bootloader-shamu-moto-apq8084-71.05.img'"
Any suggestions on that! Really appreciated!
Click to expand...
Click to collapse
It's a pathing issue most likely. I put all .img's into the same directory as the fastboot binary.
Sorry if I wasn't clear. I sometimes forget I've been doing ops like this since 2008.
TacoLord187 said:
Thanks! Im not great with ADB commands, but I gave it a shot. After the first line, I got "cannot open 'bootloader-shamu-moto-apq8084-71.05.img'"
Any suggestions on that! Really appreciated!
Click to expand...
Click to collapse
Phantom Shadow said:
A quick google would suggest that LNX07M is the lollipop developer preview
Click to expand...
Click to collapse
Searched Google for that build # .. I got a lot of references to the Nexus 5 which my tired brain refused to click on. I would have never imagined a dev. preview would ship on a prod new handset. I usually am pretty good at GTMFing.
aergern said:
It's a pathing issue most likely. I put all .img's into the same directory as the fastboot binary.
Sorry if I wasn't clear. I sometimes forget I've been doing ops like this since 2008.
Click to expand...
Click to collapse
Mind if I send a PM? Would rather not feel like im cluttering things!
(I have never actually updated this way before, haha)
TacoLord187 said:
Mind if I send a PM? Would rather not feel like im cluttering things!
(I have never actually updated this way before, haha)
Click to expand...
Click to collapse
Sure.
Hit me up. :good:
aergern said:
Sure.
Hit me up. :good:
Click to expand...
Click to collapse
It doesn't look like my messages went through (at least they are not showing up in my sent mail)
So just incase,
1. Where are the downloaded .img files stored
2. Where is the folder that I need to move them too?
3. EDITED OUT. Misread something
Thank you so much for your help!
Answers inline.
TacoLord187 said:
It doesn't look like my messages went through (at least they are not showing up in my sent mail)
So just incase,
1. Where are the downloaded .img files stored
You download the factory image tarball from Google's Android dev site. You then untar it wherever you like. I would probably untar it as root in /tmp/ then you can just mv the files to where you need them.
2. Where is the folder that I need to move them too?
The SDK is a zip file. You can unzip it wherever you like. I do this in /usr/local/ and then do a softlink to the directory it makes.
example: ln -s /usr/local/android <sdk directory>
I then cd into the tools directory and do this .. ./android which starts the UI so you can download the rest of the SDK. Do not bother with anything older than 4.4.4 packages.
I then move the img files from the factory image directory in /tmp to /usr/local/android/platform-tools/
You can then use the commands from the other post.
You can cat the install scripts for any syntax you might need but I think you'll find the commands I put in the other post to work for you.
3. Do I need to reroot/TWRP after? I can if needed, just want to be prepared!
Indeed you do. You can also move the CF img to the platform-tools directory. I would keep the tgz of the factory image somewhere else than /tmp in case you need it again.
Click to expand...
Click to collapse
aergern said:
Answers inline.
Click to expand...
Click to collapse
Looks like I got it all (rebooting now)! It just wasn't liking the paths as you said.
Thanks so much for your help!
TacoLord187 said:
Looks like I got it all (rebooting now)! It just wasn't liking the paths as you said.
Thanks so much for your help!
Click to expand...
Click to collapse
Awesome.
Well, with your ability to unzip the SDK and untar the factory image wherever you like ... I figured it was a pathing issue.
aergern said:
Awesome.
Well, with your ability to unzip the SDK and untar the factory image wherever you like ... I figured it was a pathing issue.
Click to expand...
Click to collapse
I have my adb set so I dont have to type the paths always. It just reads from a folder called android on my desktop (im on a mac). It normally works, but it wanted the paths for this one. Oh well. No big deal! Its updated and working!
Thanks again
aergern said:
Searched Google for that build # .. I got a lot of references to the Nexus 5 which my tired brain refused to click on. I would have never imagined a dev. preview would ship on a prod new handset. I usually am pretty good at GTMFing.
Click to expand...
Click to collapse
His phone might have been shipped that way as some people phones where shipped with Android 4.4.4.
HOW TO get your HTC One M8S back to Factory / stock.
Attention 1: This is NOT for the regular HTC One M8.
Attention 2: This is for the HTC One M8S also known as the M8_QL_UL
(The One M8S does not have a separate subforum on XDA.)
Hi everyone! I saw that many people who have a HTC One M8S have problems with restoring the stock HTC RUU. It is a little bit difficult. So here I'll supply you again with steps that worked for me.
Most of this is a copy from a post I made earlier. But I saw that many of you still have some problems. So here is a dedicated thread.
I have used this method multiple times to restore my phone back to factory defaults. I hope it works for you too!
Warning. You will lose your settings. Everything will be reset to the defaults.
Read these important notes before you begin!
When you need fastboot: only HTC's own fastboot program will work. You will use fastboot, for example, when you want to flash a custom recovery.
Other fastboot applications will not work correctly in my experience! So be sure you use HTC's.
If you need it: HTC will send you a link when you unlock your bootloader. But you can also find fastboot via the same page as where you can find the RUUs.... see below.
Do you have an SDCard ready? You must have one to get this to work and it must be big enough. ADB sideload will NOT work!
Is your phone relocked? It must be! If not, relock it, then come back.
Most of the problems happen because people read too fast. This stuff just takes a long time.. so don't do it if you are in a hurry. And do read carefully.
Are you ready? Ok! Here we go.
Download the RUU zip you want to use. I have used ...HTC_Europe_1.16... BUT later I found this did not allow the newest OTA update (as of august 30th, 2015). Maybe I will test 1.11 some day later.
However, I think that 1.11 is the right version. Not sure where to download the RUU or fastboot? Click the button.
For me, I downloaded the RUU zip via the generous hosting by @El-Conkistador. You can find it via his post here. On his page there is a directory called Firmware (Expert). In there is a directory called Firmware Crypted (Original HTC). In that directory are multiple directories containing RUUs. Choose one for your device, download it, then come back here.
Open your sdcard. It must be fat32 or exFAT formatted.
Copy the RUU zip file onto the root of the sdcard. Do NOT extract it. Just copy it.
You must now rename it to: 0PKVIMG.zip. The first character is the number 0 (zero), not the letter O!
If you know how to do this, take the md5sum from the RUU zip on your computer, and 0PKVIMG.zip on your SDcard. They must be the same! If not, there can be a problem with your SDCard.
Safely unload and remove the SDCard from your computer.
Power off your phone.
Are you sure you want to continue? Then insert the SDCard into the phone..
Take a deep breath..
Boot the phone to the bootloader: hold Volume Down. Press the power button. Release both buttons when you are inside the bootloader.
When you are in the bootloader, press power once to enter fastboot mode.
The restoration process should will now start. Confirm on the screen when it's asked. Then wait patiently, it takes a long time!
Nice detail: there is a small sidebar at the top right side of the screen that will show you progress. Sometimes it will go back to 0; it will fill up more than once.
In case of failure
In my case it failed the first time. Probably because a sector on my SDCard was faulty. I found out by verifying the md5sum of the file on the sdcard, it was not the same as the RUU zip on my computer, but it has to be.
To fix it, I copied the RUU zip to the sdcard for the second time, *then* deleted 0PKVIMG.img, and *then* renamed the RUU zip to 0PKVIMG.zip. Then I looked at the md5sum again. Now it was the same as on my computer... and then the restoration worked.
Still need help?
If you have questions, ask and wait patiently. I am not on this page 24/7, no one is. Just don't panic. Don't demand help. Maybe read this stuff again and see if you made a mistake somewhere.
It is logical that you are annoyed if this stuff doesn't go how you want, sure, it is not the easiest thing to do. I have tried to make it easier, but again, if it still fails, just ask your questions and wait patiently. Treat others like how you want to be treated yourself. :angel:
Good luck!
-voidzero.
(reserved)
voidzero said:
(reserved)
Click to expand...
Click to collapse
Exactly what RUU do you need and when i click hboot in the bootloader it fails finding the 0PKVIMG.zip. so idk what to do
Alex-M8 said:
Exactly what RUU do you need and when i click hboot in the bootloader it fails finding the 0PKVIMG.zip. so idk what to do
Click to expand...
Click to collapse
The exact filename of the RUU I used:
Code:
0PKVIM[email protected]50311_15.00_016_F_release_430101_signed.zip
Do you see a few green lines that say "searching for 0pkvimg.zip" when you go to hboot? They disappear pretty quickly.
voidzero said:
The exact filename of the RUU I used:
Code:
0PKVIM[email protected]50311_15.00_016_F_release_430101_signed.zip
Do you see a few green lines that say "searching for 0pkvimg.zip" when you go to hboot? They disappear pretty quickly.
Click to expand...
Click to collapse
Yeah i saw the green lines but nothing happend after they disappear
Alex-M8 said:
Yeah i saw the green lines but nothing happend after they disappear
Click to expand...
Click to collapse
Is it a fat32 or exfat sdcard? Is the md5sum for 0pkvimg.zip correct? It should be 70eece34781f0b1449f98f03e842f249
voidzero said:
Is it a fat32 or exfat sdcard? Is the md5sum for 0pkvimg.zip correct? It should be 70eece34781f0b1449f98f03e842f249
Click to expand...
Click to collapse
i checked and it is fat32 and i still don't get where the md5sum is located and where i should put it .-.
the md5sum is a long string of characters called a checksum. It scans a file and calculates what number it should get. Other types of checksums are SHA-1, SHA-256, RIPE-MD160 and so on.
MD5 is fairly lightweight so that's why we usually choose md5 for files.
md5sum itself is a program that you can run from the command line. If you use linux, it should be on your computer already, so just do 'md5sum 0pkvimg.zip'. On windows, well, you need md5sum.exe and run that from a command line. But I have not used Windows in so many years that I don't know where to find md5sum.exe. I'm sure you can find it easily... I would google for this, but you can do that too so I'll leave that part up to you.
So: you don't put the md5sum anywhere.. you calculate an md5sum and compare it with the number I gave you previously. Hope this makes sense, keep asking if you need more help.
Hi guys,
Im new to all this I just want to ask for little help here my m8s has unlocked bootloader and modified (unofficial) software (says in bootloader)
Im running 5.0.2 soft ver
Soft number 1.16.401.10
Custom recovery TWRP
Phone is rooted but i need to send it back to htc as its dropping calls randomly within 25secs. All i need is the right ruu so its stock again and says relocked (i know how to relock) official soft and that OTAs would work.
Also do i leave this custom recovery there or before the ruu will i put in the stock one, relock the BL and then the ruu?
Any help is much appreciated.
Sent from my HTC One M8s using XDA Free mobile app
Just relock. The Ruu does the rest! I used 1.11, the exact filename is in my OP. If you have a vendor phone I'm not sure but I think you can still use the same RUU as I have; if not, you will be notified from hboot. Does that answer your question?
Yes thank you.
Sent from my HTC One M8s using XDA Free mobile app
Tried on windows twice then got a blue screen (on the pc) did the 1.11 on my macbook and phone is now back to official and relocked!
I owe you a pint of beer sir. Thank you!
Sent from my HTC One M8s using XDA Free mobile app
Great! Glad to hear.
Cyanogenmod is still in the works. I have finally gotten a preliminary version to boot, so to those of you who are interested, head over to the CyanogenMod 12 on M8s thread...
HTC One M8S: Cyanogenmod 12 Discussion
hi all,
I give up, downloaded three zips from this link:
http://forum.xda-developers.com/htc-one-m8/help/make-custom-recovery-htc-one-m8s-t3114245
1.03
1.11
1.11 - combined signed
and every time I get error "no image or image wrong....no gift file....loading image 0Pkvidiag.zip - No image! loading 0PKVIDIAG.nbh...no image or wrong image"
...inside the zip file there is no 0PKVIMG.img file so dont realy know what to rename . . .
...yes checked md5 sum and they are OK
...sd card is fat32 (tried copying zip file from two different laptops , no difference)
...Custom recovery TWRP
this is m8s european version which was rooted , fastboot shows now RELOCKED and this images just dont work ,
this phone is giving all sort of issues, no custom roms with updates, SIM_Card error sometimes 10+ times a day causing call disconnections and reboots, cant update to lates htc soft as on custom rom it just dont work.....
what I am doing wrong here? probably something stupid easy :laugh: help please
Thanks in advance !
new-noob said:
what I am doing wrong here? probably something stupid easy :laugh: help please
Click to expand...
Click to collapse
Hiya. Ugh I get how frustrating this can be!! But you're close, so we'll get you sorted out. FYI on saturday and sunday I'm not around much (family comes first ), so replies might take me a while... but we'll figure it out.
You need this exact file:
Code:
0PKVIM[email protected]50311_15.00_016_F_release_430101_signed.zip
Copy that to the sdcard and rename it to 0PVKIMG.zip, don't extract it just rename it. The md5sum should be:
Code:
70eece34781f0b1449f98f03e842f249
If that won't work, we need to figure out why. That comes next. :good:
voidzero said:
Hiya. Ugh I get how frustrating this can be!! But you're close, so we'll get you sorted out. FYI on saturday and sunday I'm not around much (family comes first ), so replies might take me a while... but we'll figure it out.
You need this exact file:
Code:
0PKVIM[email protected]50311_15.00_016_F_release_430101_signed.zip
Copy that to the sdcard and rename it to 0PVKIMG.zip, don't extract it just rename it. The md5sum should be:
Code:
70eece34781f0b1449f98f03e842f249
If that won't work, we need to figure out why. That comes next. :good:
Click to expand...
Click to collapse
HI voidzero and thanks for taking the time and replaying!
I ended up installing Android Pandora 1.2 and ...waiting on feedback re: SIM errors, hopeful they are gone with new ROM,
I'll post quick update tomorrow.
Thanks again and enjoy ur weekend !
new-noob said:
HI voidzero and thanks for taking the time and replaying!
I ended up installing Android Pandora 1.2 and ...waiting on feedback re: SIM errors, hopeful they are gone with new ROM,
I'll post quick update tomorrow.
Thanks again and enjoy ur weekend !
Click to expand...
Click to collapse
You should use Cyanogenmod, not Pandora. Pandora is old, is not updated, and contains a very problematic security issue with libstagefright. Use cyanogenmod for your own good!
voidzero said:
You should use Cyanogenmod, not Pandora. Pandora is old, is not updated, and contains a very problematic security issue with libstagefright. Use cyanogenmod for your own good!
Click to expand...
Click to collapse
hey, yeap, pandora gives same SIM card error!
Thanks for advise, I will definitely try Cyanogenmmod, think this is the link : http://forum.xda-developers.com/htc-one-m8/general/htc-m8s-cyanogenmod-t3142668
?
Thank you!
hello.
i need help. my htc m8s is relock, my sd card is format fat 32, md5sum match, but still not recognize when i restart in fastboot.