Related
I'm just a new member (it's my first post in fact). I would like to ask a question directly to spyrosk (development-related thread http://forum.xda-developers.com/showthread.php?t=2020737) about the Toolkit developed by him, but as being a new member I'm not permitted to do so. Besides, I'm just an user, I'm not a developer at all, so my question below can seem stupid...
I used his toolkit installing the official ROM ICS 4.0.4 on my LG (using option 6 of the Toolkit). I want to root my phone but I have some doubts when launching its option 3, that are:
1) It says to choose one of the zip files from SU folder. There are three zip files in there. Assuming that my phone is already running ICS 4.0.4, I think that I can choose the SU313-BIN311_4ICS.zip, is that correct?
2) The procedure to put the phone on NVFlash says to press and hold both Vol- and Vol+ while plugging the micro-uSB into the phone. But until when? I mean, is it required to keep pressing both buttons during the hole process? The instructions is not very clear at this point...
3) It also says that the procedure will detect the current partition layout and ask you to choose a compatible recovery image. I don't have any idea what's talking about... What should be my choice?
In time: I used the V30A_00.kdz, obtained from the http://lg-phone-firmware.com/index.php?id_mod=3 site. The firmware is IMM76L.LG-P990-P99030a.1211302332.
Can anyone help me with these questions?
I am not Spyrosk but i have used this amazing tool...
For the option 3, simple way is to hold the buttons until the computer or your laptop recognizes your mobile.after that you can release it...it is the same for any of the procedures mentioned.
For the partition sizes i think it is in the thread and you can search. ICS requires higher partition.....but I'd you are in the ics by smart flashing or by kdz method, you are in the new boot loader and i don't think you need to change the sizes....but I'd you want the old boot loader....then you need to have the bigger partitions....but search inn the thread
Hope this helps you to start
Sent from my LG-P990 using xda premium
SREEPRAJAY said:
I am not Spyrosk but i have used this amazing tool...
For the option 3, simple way is to hold the buttons until the computer or your laptop recognizes your mobile.after that you can release it...it is the same for any of the procedures mentioned.
For the partition sizes i think it is in the thread and you can search. ICS requires higher partition.....but I'd you are in the ics by smart flashing or by kdz method, you are in the new boot loader and i don't think you need to change the sizes....but I'd you want the old boot loader....then you need to have the bigger partitions....but search inn the thread
Hope this helps you to start
Sent from my LG-P990 using xda premium
Click to expand...
Click to collapse
Hi SREEPRAJAY,
Thanks for your reply. In fact you clarified just one of my three questions above. I´ve read the hole thread but didn´t find the answer for my remaining questions... Could someone else help me with this? I don´t want to try procedures on my phone that I´m not confident to do.
Regards,
for the first question...just flash it.as you have flashed the kdz before and on 4.0.4, you have to just flash it.nothing more is required.
and if you are on 4.0.4, then you dont need to re-create the partitions.if flashed with the kdz method, then you are on the new boot loader. to check that...once you flash the SU file in the AIOT.....just enter the recovery by power+volume down key simultaneously...if you see the pink LG logo, then you are on the new one....if on the white LG logo, then you are on the old boot loader.
let me know if there is anything more
SREEPRAJAY said:
for the first question...just flash it.as you have flashed the kdz before and on 4.0.4, you have to just flash it.nothing more is required.
and if you are on 4.0.4, then you dont need to re-create the partitions.if flashed with the kdz method, then you are on the new boot loader. to check that...once you flash the SU file in the AIOT.....just enter the recovery by power+volume down key simultaneously...if you see the pink LG logo, then you are on the new one....if on the white LG logo, then you are on the old boot loader.
let me know if there is anything more
Click to expand...
Click to collapse
Hi SREEPRAJAY,
Sorry, but the more you try to help and explain to me, the more confused I got. I still have doubts. Sorry for that. Let's try again:
1) It says to choose one of the zip files from SU folder. There are three zip files in there. Assuming that my phone is already running ICS 4.0.4, which file must I choose? Can I choose any one? What's the difference between them?
2) Answered OK. Thanks for that.
3) It also says that the procedure will detect the current partition layout and ask you to choose a compatible recovery image. What will I be supposed to choose? What recovery image is the toolkit referring to?
Sorry again, but, as stated on my first post, I'm just an user (not developer) trying to get full control of my phone, and trying to learn more about all those things...
Tks,
ecarli said:
Hi SREEPRAJAY,
Sorry, but the more you try to help and explain to me, the more confused I got. I still have doubts. Sorry for that. Let's try again:
1) It says to choose one of the zip files from SU folder. There are three zip files in there. Assuming that my phone is already running ICS 4.0.4, which file must I choose? Can I choose any one? What's the difference between them?
2) Answered OK. Thanks for that.
3) It also says that the procedure will detect the current partition layout and ask you to choose a compatible recovery image. What will I be supposed to choose? What recovery image is the toolkit referring to?
Sorry again, but, as stated on my first post, I'm just an user (not developer) trying to get full control of my phone, and trying to learn more about all those things...
Tks,
Click to expand...
Click to collapse
Choose anyone for the first question.you have already mentioned the file name in your first post i think
For the third, i am using the twrp 2.5 which is the most convenient.cwm is used with volume button keys, but twrp is more convenient with touch interface and also customizable with themes.
I am on my mobile and i am unable to look into more details.sorry for that
I hope you can proceed with this.
Sent from my LG-P990 using xda premium
It's Rocking-roll!
SREEPRAJAY said:
Choose anyone for the first question.you have already mentioned the file name in your first post i think
For the third, i am using the twrp 2.5 which is the most convenient.cwm is used with volume button keys, but twrp is more convenient with touch interface and also customizable with themes.
I am on my mobile and i am unable to look into more details.sorry for that
I hope you can proceed with this.
Sent from my LG-P990 using xda premium
Click to expand...
Click to collapse
Hi SREEPRAJAY,
I have good news! I've just done the procedure to root my LG using the option 3's toolkit, and it ran fantastic! :good: But, I have some suggestions to Spyrosk. The toolkit gives you the choice to select one of the three compatible recovery:
1 - ICS-cwm-5.0.2.8e.img
2 - ICS-cwm-6.0.2.5.img
3 - ICS-twrp-2.4.1.0.img
I chose option 1, at random... I mean, I didn't have any idea at all what were the differences between those three options. Wouldn't be nice if Spyrosk give a little bit explanation about what the toolkit is asking us, I mean, giving a minimal explanation about what are cwm and twrp, and its purposes?
By the way, where I can find and learn more the basics of all this stuff, including cwm and twrp? I mean, I installed this with cross fingers and closed eyes, because I dont have any idea of what I had to choose. That's why I chose at random, option 1. Was it a good choice? I mean, what's the difference between cwm 5.0.2.8e and 6.0.2.5?
In time: now I have my phone running ICS 4.0.4 and ROOTED. I verified using the TitaniumBackup that asked for root access, I gave it, and it ran ok. Now I intend to restore some applications that were previously backup. You don't even need to install SuperOneClick or UnlockRoot to do it. This toolkit is really awesome!
Yessss!
Thanks
For the guide, you need to check and search .....if you don't want, check my signature(the big one)....have the links there
Sent from my LG-P990 using xda premium
First off, I wanna apologize if the has been discussed.
I see a lot of you broke your device by trying some form of method to fix the device in any fancy way.
I had a friend brick by trying the Cyanoboot method.
First off, assuming you have already got CWM installed via the tutorial that's been posted already.
Secondly, make sure you have some form of way to side load apps onto the device. Be it Dropbox, Google Drive, or maybe your using an ADB method.
Lastly, I have found this to be the easiest way.
So, let's begin. Please make sure you have a way of grabbing ROM Manager, back it up, download an .apk from a Google search or just port it from one device to another via an app.
Once you've found your method of getting the side loaded .apk let's make sure it's installed, any newer version will work(Older versions have been reported of not installing and allowing a proper clean reboot). So let's make sure it's a newer updated version, secondly test it and make sure the version you're using will reboot the device properly without issue. Working? Good.
Now let's use our nifty tool as soon as you have CWM installed, you should get a proper reboot!
This is good.
As a side note, I've had mine give issue and make me wait a few for a full reboot into CWM.
Now you're done!
Flashing ROMs.
It's just as easy as you'd think it'd be as long as you've got a properly packed ROM onto your device.
Note: If you're looking for a tut on porting the ROM, please check the Dev forum as there is a tut posted that is clean and simple using ADB.
Also, there are some that say you can using a cloud storage method.(Try it at your own risk!)
Once you've got your ROM onto Ouya you should check with an explorer to confirm that it was saved onto the device.(I have an issue of downloading things of the Internet with Ouya and them not showing up).
Now, using the method I first mentioned to get into CWM, do so.
You should see an option to search through your internal SD, this would be the next step as we can't/don't have any form of using an external SD, that is if you could connect a flash drive to the back and use it, though I can't confirm it would work.
Lastly, once you've scanned the internal SD and found your ROM, flash it. Sometimes this could take a bit, being my case it took 10m to install Ouya Plus.
If any issues occur, feel free to post and I shall try my best to answer anything!
Ouya-XD said:
First off, I wanna apologize if the has been discussed.
I see a lot of you broke your device by trying some form of method to fix the device in any fancy way.
I had a friend brick by trying the Cyanoboot method.
First off, assuming you have already got CWM installed via the tutorial that's been posted already.
Secondly, make sure you have some form of way to side load apps onto the device. Be it Dropbox, Google Drive, or maybe your using an ADB method.
Lastly, I have found this to be the easiest way.
So, let's begin. Please make sure you have a way of grabbing ROM Manager, back it up, download an .apk from a Google search or just port it from one device to another via an app.
Once you've found your method of getting the side loaded .apk let's make sure it's installed, any newer version will work(Older versions have been reported of not installing and allowing a proper clean reboot). So let's make sure it's a newer updated version, secondly test it and make sure the version you're using will reboot the device properly without issue. Working? Good.
Now let's use our nifty tool as soon as you have CWM installed, you should get a proper reboot!
This is good.
As a side note, I've had mine give issue and make me wait a few for a full reboot into CWM.
Now you're done!
Flashing ROMs.
It's just as easy as you'd think it'd be as long as you've got a properly packed ROM onto your device.
Note: If you're looking for a tut on porting the ROM, please check the Dev forum as there is a tut posted that is clean and simple using ADB.
Also, there are some that say you can using a cloud storage method.(Try it at your own risk!)
Once you've got your ROM onto Ouya you should check with an explorer to confirm that it was saved onto the device.(I have an issue of downloading things of the Internet with Ouya and them not showing up).
Now, using the method I first mentioned to get into CWM, do so.
You should see an option to search through your internal SD, this would be the next step as we can't/don't have any form of using an external SD, that is if you could connect a flash drive to the back and use it, though I can't confirm it would work.
Lastly, once you've scanned the internal SD and found your ROM, flash it. Sometimes this could take a bit, being my case it took 10m to install Ouya Plus.
If any issues occur, feel free to post and I shall try my best to answer anything!
Click to expand...
Click to collapse
just as an add: my Ouya did not detect a exFAT MicroSD in a USB reader. Maybe CWM only works with some formats?
glitchhawk said:
just as an add: my Ouya did not detect a exFAT MicroSD in a USB reader. Maybe CWM only works with some formats?
Click to expand...
Click to collapse
I do believe there's been a certain format to use, though I'm unaware on how this works.
Sent from my HTC One VX using xda app-developers app
glitchhawk said:
just as an add: my Ouya did not detect a exFAT MicroSD in a USB reader. Maybe CWM only works with some formats?
Click to expand...
Click to collapse
Ouya-XD said:
I do believe there's been a certain format to use, though I'm unaware on how this works.
Sent from my HTC One VX using xda app-developers app
Click to expand...
Click to collapse
FAT32 is more or less the "golden" standard for portable devices. glitchhaw, you are aware that exFAT is one of the most laughably locked down filesystems for portable devices out there, right? If you're being official at all, you have to pay royalties to Microsoft to be able to work with exFAT, and I doubt OUYA built support in for that.
Rirere said:
FAT32 is more or less the "golden" standard for portable devices. glitchhaw, you are aware that exFAT is one of the most laughably locked down filesystems for portable devices out there, right? If you're being official at all, you have to pay royalties to Microsoft to be able to work with exFAT, and I doubt OUYA built support in for that.
Click to expand...
Click to collapse
i know that I don't like exFAT and that its annoying and glitchy sometimes with android.. but I don't like the fat32 4gb limit.
i wish CWM/TWRP worked with NTFS or EXT, at least they are more reliable.
glitchhawk said:
i know that I don't like exFAT and that its annoying and glitchy sometimes with android.. but I don't like the fat32 4gb limit.
i wish CWM/TWRP worked with NTFS or EXT, at least they are more reliable.
Click to expand...
Click to collapse
NTFS support can be added at the kernel level, but I don't know of any recoveries that support it, sadly. And that's unfortunately the nature of the beast, and probably why many recoveries will break files up into multiple archives.
Go full *nix and use ext4 like a man... Unless you're a woman, then use it like a woman.
Sent from my SAMSUNG-SGH-I317 using xda premium
I am unable to get the unit to respond to Rom managers attempt at rebooting into recovery, I'll give the command via the app and it will just continue sitting there at the menu. CWM was successfully installed and I made a backup. I downloaded the app to my phone and then TB'd it and sent it to my device. did I miss something?
B4 I updated I needed SU to make the reeboot. Feature work.
Sent from my Amazon Kindle Fire using xda app-developers app
that was my thought, however I just reran the .bat for cwm and flashed that way.
Kickbut101 said:
I am unable to get the unit to respond to Rom managers attempt at rebooting into recovery, I'll give the command via the app and it will just continue sitting there at the menu. CWM was successfully installed and I made a backup. I downloaded the app to my phone and then TB'd it and sent it to my device. did I miss something?
Click to expand...
Click to collapse
I'd assume if it's not working that way then to try the ADB method instead, again, please report all issues to me.
Do you have CWM installed, on a final note?
People cry a out signatures, there's no need for one! I love my community and will stand up for it!
App: Quick Boot . reboot into fast boot, recovery, or shut down the console.
Sent from my SGH-M919G using xda app-developers app
Ouya-XD said:
First off, I wanna apologize if the has been discussed.
I see a lot of you broke your device by trying some form of method to fix the device in any fancy way.
I had a friend brick by trying the Cyanoboot method.
First off, assuming you have already got CWM installed via the tutorial that's been posted already.
Secondly, make sure you have some form of way to side load apps onto the device. Be it Dropbox, Google Drive, or maybe your using an ADB method.
Lastly, I have found this to be the easiest way.
So, let's begin. Please make sure you have a way of grabbing ROM Manager, back it up, download an .apk from a Google search or just port it from one device to another via an app.
Once you've found your method of getting the side loaded .apk let's make sure it's installed, any newer version will work(Older versions have been reported of not installing and allowing a proper clean reboot). So let's make sure it's a newer updated version, secondly test it and make sure the version you're using will reboot the device properly without issue. Working? Good.
Now let's use our nifty tool as soon as you have CWM installed, you should get a proper reboot!
This is good.
As a side note, I've had mine give issue and make me wait a few for a full reboot into CWM.
Now you're done!
Flashing ROMs.
It's just as easy as you'd think it'd be as long as you've got a properly packed ROM onto your device.
Note: If you're looking for a tut on porting the ROM, please check the Dev forum as there is a tut posted that is clean and simple using ADB.
Also, there are some that say you can using a cloud storage method.(Try it at your own risk!)
Once you've got your ROM onto Ouya you should check with an explorer to confirm that it was saved onto the device.(I have an issue of downloading things of the Internet with Ouya and them not showing up).
Now, using the method I first mentioned to get into CWM, do so.
You should see an option to search through your internal SD, this would be the next step as we can't/don't have any form of using an external SD, that is if you could connect a flash drive to the back and use it, though I can't confirm it would work.
Lastly, once you've scanned the internal SD and found your ROM, flash it. Sometimes this could take a bit, being my case it took 10m to install Ouya Plus.
If any issues occur, feel free to post and I shall try my best to answer anything!
If this was useful to you, I can only ask of a favor!
Check out my YouTube channel!
http://WWW.YouTube.com/user/TheDarkRosarySubscribe if you will! I will be covering everything Ouya and doing news soon!
Click to expand...
Click to collapse
I have to say this is probably the worst how to/tutorial I have seen on XDA.
If you're intent is to help users inexperienced with CWM, then you need to write clearly defined steps. The whole thing is vague. You don't give links to a single file or other tutorial, a how to shouldn't keep telling people to do a Google search for things. On four steps you make people search for files or another how-to.
What is the new version of Rom manager? How do you make sure it will reboot the device properly? Be specific.
You say flashing Roms is easy as long as you have a properly packed Rom. How does one go about checking that? How do you flash the Rom?
This is what a how-to is supposed to include. This is equivalent to just telling people GIYF and RTM.
Sent from my SCH-I535 using Tapatalk 4 Beta
TadeoNYC said:
I have to say this is probably the worst how to/tutorial I have seen on XDA.
If you're intent is to help users inexperienced with CWM, then you need to write clearly defined steps. The whole thing is vague. You don't give links to a single file or other tutorial, a how to shouldn't keep telling people to do a Google search for things. On four steps you make people search for files or another how-to.
What is the new version of Rom manager? How do you make sure it will reboot the device properly? Be specific.
You say flashing Roms is easy as long as you have a properly packed Rom. How does one go about checking that? How do you flash the Rom?
This is what a how-to is supposed to include. This is equivalent to just telling people GIYF and RTM.
Sent from my SCH-I535 using Tapatalk 4 Beta
Click to expand...
Click to collapse
There's no need to bash peoples thread first of all.
And secondly, you'll be reported for this.
As of how to to do this, I can't always "be specific" like you want when I post a good amount of this from my phone, so do be prepared for a tut that's not fully helpful.
Lastly, I HIGHLY doubt that you've read every tut on here, and trust me, I've seen so much worse that go down to the nick of; "If you wipe and install first, this version will fully brick the device, this version will half brick it".
So explain to me, since I've made ROM packages, I've had more tuts than just this, what do you wanna see more in a tutorial from me? Tell me and I'll try my best to help.
Don't go barging in with the intent of anger in mind and begin bashing me to the fullest.
Most people PM me and I give them what they need if they can't find it, as for you? Nuh uh, after this, NO is my final answer.
Sent from my HTC One VX using xda app-developers app
Oscar_david said:
App: Quick Boot . reboot into fast boot, recovery, or shut down the console.
Sent from my SGH-M919G using xda app-developers app
Click to expand...
Click to collapse
Thanks man, I'll make sure to add it to the OP.
Sent from my HTC One VX using xda app-developers app
Ouya-XD said:
There's no need to bash peoples thread first of all.
And secondly, you'll be reported for this.
As of how to to do this, I can't always "be specific" like you want when I post a good amount of this from my phone, so do be prepared for a tut that's not fully helpful.
Lastly, I HIGHLY doubt that you've read every tut on here, and trust me, I've seen so much worse that go down to the nick of; "If you wipe and install first, this version will fully brick the device, this version will half brick it".
So explain to me, since I've made ROM packages, I've had more tuts than just this, what do you wanna see more in a tutorial from me? Tell me and I'll try my best to help.
Don't go barging in with the intent of anger in mind and begin bashing me to the fullest.
Most people PM me and I give them what they need if they can't find it, as for you? Nuh uh, after this, NO is my final answer.
Sent from my HTC One VX using xda app-developers app
Click to expand...
Click to collapse
You reported me for what? That your feelings are hurt?
Ostensibly you created this tutorial to prevent people from bricking their OUYAs. That is why I was expecting a detailed walkthrough and was very disappointed. You created a tutorial on your phone that is lacking vital info that I have already detailed. I did not bash you to the fullest. You admit that your tut is not fully helpful, and I've seen other comments on another tut of yours that were a great deal harsher than mine about your motivation to post a poorly written tut.
I apologize for the severity of my opening line. I was and am annoyed that the "how-to" does not provide any info vital to users so that they don't brick their OUYA. Every time they are sent elsewhere for a file or info there is a risk of getting bad info or a malicious or corrupt apk. I outlined a lot of the information I think should be included. If I had all the answers I'd have included those as well, but I am here because I thought I could learn something. Maybe I still will.
Edit: I see now what type of person you are and how helpful you can be. http://forum.xda-developers.com/showthread.php?p=43031832 so the next time you see me ask for help go ahead and flame me. Don't worry I have a thick skin, so I won't feel the need to cry to the mods you hypocrite.
Sent from my GT-P3113 using Tapatalk 4 Beta
TadeoNYC said:
You reported me for what? That your feelings are hurt?
Ostensibly you created this tutorial to prevent people from bricking their OUYAs. That is why I was expecting a detailed walkthrough and was very disappointed. You created a tutorial on your phone that is lacking vital info that I have already detailed. I did not bash you to the fullest. You admit that your tut is not fully helpful, and I've seen other comments on another tut of yours that were a great deal harsher than mine about your motivation to post a poorly written tut.
I apologize for the severity of my opening line. I was and am annoyed that the "how-to" does not provide any info vital to users so that they don't brick their OUYA. Every time they are sent elsewhere for a file or info there is a risk of getting bad info or a malicious or corrupt apk. I outlined a lot of the information I think should be included. If I had all the answers I'd have included those as well, but I am here because I thought I could learn something. Maybe I still will.
Edit: I see now what type of person you are and how helpful you can be. http://forum.xda-developers.com/showthread.php?p=43031832 so the next time you see me ask for help go ahead and flame me. Don't worry I have a thick skin, so I won't feel the need to cry to the mods you hypocrite.
Sent from my GT-P3113 using Tapatalk 4 Beta
Click to expand...
Click to collapse
Don't worry, this morning I was frustrated.
I'm sorry, tell me what you think I'm missing and I'll add the quote to the OP.
I plan on doing a video tut though.
Sent from my HTC One VX using xda app-developers app
worst
this is the worst tutorial I've ever read on xda. mods please take down this how to brick your ouya tutorial before people start downloading wrong files and bricking there ouya.
Okay where is your full proof method of rooting and installing cwm on the ouya?
Sent from my Vivid 4G using xda premium
Going by the threads opened/posts by this fellow, maybe a sticky to let people know who to avoid is needed.
OP, maybe your're over-enthusiastic over your new Ouya, but XDA prides itself on people who actually KNOW what they're doing to help, not rambling nonsense.
guys ive been trying to use kffa to revert kindle fire hd 7 to 7.2.3 for like a week now and it just don't work
i followed the steps laid down in this form and inevitably it stops at some point through the process and says
ether, cant find path specified , waiting for device, cant find file /RIC, something always stops the posses
im using a kindle fire hd 7 v7.4.6 and yes ive followed the post rooting the 7.4.6 and yes it is rooted i know
this because i have super user windows when i enter root file in es file explorer. i have got as far as kffa
told it to option 3 revert version to 7.2.3 it gos through two of the three steps fethes files 3 of 3 tries to
load recovery on last step, stays on "waiting for device" and never does nothen.
this tread is prity old does it still aply or no WHAT AM I DOING WRONG plz help Dane AZ.
ps if anyone has time i have two computers so i can read post on one wile working on the other
so someone could go through step by step with me . also have all related files already downloaded
thanks
Red brick screen solved!
thelz said:
guys ive been trying to use kffa to revert kindle fire hd 7 to 7.2.3 for like a week now and it just don't work
i followed the steps laid down in this form and inevitably it stops at some point through the process and says
ether, cant find path specified , waiting for device, cant find file /RIC, something always stops the posses
im using a kindle fire hd 7 v7.4.6 and yes ive followed the post rooting the 7.4.6 and yes it is rooted i know
/QUOTE/]
I've been through the same mill as you this past week. Tried everything.
Just about to give up when member galearned on here pointed the way. It worked!!
Files a bit big - 1,1GB. My mobile modem got pretty hot It's surrounded by oriental symbols, too.
I can't provide the link (I'm too new on here) but I think you'll find galearned ok. The filename is:
KFHD_SRT_v1.3.0
Cheers, Bill.
Click to expand...
Click to collapse
Here, you beat make to it, I'll just post the link: http://forum.xda-developers.com/showthread.php?t=1951254
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
stunts513 said:
Here, you beat make to it, I'll just post the link: http://forum.xda-developers.com/showthread.php?t=1951254
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Click to expand...
Click to collapse
im afraid im past that point recovery tool simply says waiting for device it stuck in twrp with no data in
anything check through all options cant find any data in any of them what now. wait ive tried the recovery options found data
im tring now
thelz said:
im afraid im past that point recovery tool simply says waiting for device it stuck in twrp with no data in
anything check through all options cant find any data in any of them what now. wait ive tried the recovery options found data
im tring now
Click to expand...
Click to collapse
didnt work still boots back to TWRP flash screen tried all 8 bottons what do i do now plz anyone?
in twrp what buton do i pick and witch folder after that plz help anyone
Oh you have twrp, you could just "adb push" a stock rom on there from the development section, but if you're going to take the kffa or kfsrt route with flashing stock, just go into twrp, hit reboot, then hit bootloader, it should go into fastboot. It will probably restore stock recovery though, not sure i haven't use either of the tools mentioned before, so you might have to reinstall that.
just pulled it back from the FIRE
Ok just got it back working, followed your advice and started looking for post about using the sideloading option in the TWRP to push stock OS 7.4.6 to the SD card, found one that gave the adb code to push, im new so i dont know stuff like that "adb sideload C;/desktop/kfhd7-amizon-os-kfhd7.4.6.zip"
Don't know why all the file locations were empty when i tried to use TWRP consol the instructions in the post said reboot after everything else
when i did it would not reboot into system and if i tried to install a zip could not find a file in there anywere witch is wieard because all file came back when i pushed the kfhd7.zip to the sd card even the disk img on my sd card?
anyway all's good that ends well ..........
dont think ill try it again soon on my 7hd
maybe one more time on the one im sending back to amizon its dead i should have a cable by tus so ill try and bring it back to life if only to make sure theres nothing there for techs to refuse my warenty just a big blank space.:good:
Hello, I have a Kindle Fire HD 7" running the downgraded 7.2.3 from KFFA. Then I used Hash's TWRP 2.6.3.1 + 2nd Bootloader thread to get Stock with TWRP but for whatever reason I can't seem to install a ROM that will boot past the "Blue" Logo.
My screen doesn't do the "White haze" that others have mentioned.
Still boots into recovery allowing for wipes + installs.
I have reverted back to 100% stock then made my way back to stock + TWRP three times now, and have looked rather extensively through any threads even somewhat relative to my own problem.
I've been using the Factory fastboot cable to get into fastboot if that makes any difference.
I have downloaded the GAPPs and ROM twice, and I have a very stable connection that hasn't given me issues before.
ROM is the same as from Hash's thread for TWRP + 2nd Bootloader. (cm-10.2-20131115-UNOFFICIAL-tate)
Have tried my cable from my Note 2, Captivate, Epic 4G Touch, and stock KFHD 7" cable as well as the factory fastboot cable.
Kinda stuck, have gone round like this for about 4 hours + now and I must say, the KFHD 7" has been the biggest pain out of any of my Androids by far xD Great tab though.
Any help would be much appreciated. I could always just run stock, but, I'd really like to have CM 4.3 or 4.4 based on my device.
Thanks!
If I left out anything, please, let me know and I will respond ASAP.
veladem said:
Any help would be much appreciated. I could always just run stock, but, I'd really like to have CM 4.3 or 4.4 based on my device.
Thanks!
Click to expand...
Click to collapse
You need to enter TWRP and sideload a ROM. Use this tutorial here http://forum.xda-developers.com/showthread.php?t=2459498
LinearEquation said:
You need to enter TWRP and sideload a ROM. Use this tutorial here http://forum.xda-developers.com/showthread.php?t=2459498
Click to expand...
Click to collapse
Not to be an arse but I don't know how that is going to help 0.o?
My recovery works just fine . . .
veladem said:
Not to be an arse but I don't know how that is going to help 0.o?
My recovery works just fine . . .
Click to expand...
Click to collapse
You have no OS and that's why it won't boot past TWRP. Go into TWRP and adb sideload a ROM onto TWRP and flash it and boot into system. You should probably read a bit before just posting. The link answered your question.
LinearEquation said:
You have no OS and that's why it won't boot past TWRP. Go into TWRP and adb sideload a ROM onto TWRP and flash it and boot into system. You should probably read a bit before just posting. The link answered your question.
Click to expand...
Click to collapse
If I restore my stock rooted OS via TWRP it boots up just fine . . .
The problem I have is after flashing any ROM's I can't get past the blue logo.
But I'll try what you are saying just for kicks.
veladem said:
If I restore my stock rooted OS via TWRP it boots up just fine . . .
The problem I have is after flashing any ROM's I can't get past the blue logo.
But I'll try what you are saying just for kicks.
Click to expand...
Click to collapse
You need to check the zip and make sure it did not get corrupted during the download. Goo.img is updating their servers and downloads can be corrupted. Try downloading from the crackflasher mirror. Make sure it is the ROM for your year and model Kindle Fire HD. You also need to update your TWRP to 2.6.3.1 right away, http://forum.xda-developers.com/showthread.php?t=2128848 Before you flash, factory "swipe" then flash ROM then wipe Dalvik/CACHE then boot into OS. Just drag and drop ROM onto internal SD card before booting into TWRP.
LinearEquation said:
You never said you could access an OS. You simply said you could not get past TWRP. You need to check the zip and make sure it did not get corrupted during the download. Goo.img is updating their servers and downloads can be corrupted. Try downloading from the crackflasher mirror. Make sure it is the ROM for your year and model Kindle Fire HD. You also need to update your TWRP to 2.6.3.1 right away, http://forum.xda-developers.com/showthread.php?t=2128848 Before you flash, factory "swipe" then flash ROM then wipe Dalvik/CACHE then boot into OS.
Click to expand...
Click to collapse
Oh boy lol, let me just correct everywhere you went wrong, cause I've tried to be nice, but I can't let you get away with not even reading the OP.
"You never said you could access an OS." ---> "I could always just run stock"
"You simply said you could not get past TWRP" ---> "Then I used Hash's TWRP 2.6.3.1 + 2nd Bootloader thread to get Stock with TWRP but for whatever reason I can't seem to install a ROM that will boot past the "Blue" Logo." (PS: Being stuck at the "Blue logo" is much different then not being able to boot and being booted into TWRP.)
"You need to check the zip and make sure it did not get corrupted during the download." ---> "I have downloaded the GAPPs and ROM twice, and I have a very stable connection that hasn't given me issues before."
"Goo.img is updating their servers and downloads can be corrupted. Try downloading from the crackflasher mirror." ---> That was where I downloaded from the second+ time I downloaded the ROM.
"Make sure it is the ROM for your year and model Kindle Fire HD." ---> "ROM is the same as from Hash's thread for TWRP + 2nd Bootloader. (cm-10.2-20131115-UNOFFICIAL-tate)"
"You also need to update your TWRP to 2.6.3.1 right away," ---> "Then I used Hash's TWRP 2.6.3.1 + 2nd Bootloader thread to get Stock with TWRP"
So, I just copied and pasted all that from you post, and my OP.
So, let me quote you again from another post you made in my thread.
"You should probably read a bit before just posting." READ THE OP BEFORE TRYING TO HELP MIGHT BE A GOOD IDEA!!! x'D
Thanks for attempting to help though, much appreciated.
veladem said:
Oh boy lol, let me just correct everywhere you went wrong, cause I've tried to be nice, but I can't let you get away with not even reading the OP.
"You never said you could access an OS." ---> "I could always just run stock"
"You simply said you could not get past TWRP" ---> "Then I used Hash's TWRP 2.6.3.1 + 2nd Bootloader thread to get Stock with TWRP but for whatever reason I can't seem to install a ROM that will boot past the "Blue" Logo." (PS: Being stuck at the "Blue logo" is much different then not being able to boot and being booted into TWRP.)
"You need to check the zip and make sure it did not get corrupted during the download." ---> "I have downloaded the GAPPs and ROM twice, and I have a very stable connection that hasn't given me issues before."
"Goo.img is updating their servers and downloads can be corrupted. Try downloading from the crackflasher mirror." ---> That was where I downloaded from the second+ time I downloaded the ROM.
"Make sure it is the ROM for your year and model Kindle Fire HD." ---> "ROM is the same as from Hash's thread for TWRP + 2nd Bootloader. (cm-10.2-20131115-UNOFFICIAL-tate)"
"You also need to update your TWRP to 2.6.3.1 right away," ---> "Then I used Hash's TWRP 2.6.3.1 + 2nd Bootloader thread to get Stock with TWRP"
So, I just copied and pasted all that from you post, and my OP.
So, let me quote you again from another post you made in my thread.
"You should probably read a bit before just posting." READ THE OP BEFORE TRYING TO HELP MIGHT BE A GOOD IDEA!!! x'D
Thanks for attempting to help though, much appreciated.
Click to expand...
Click to collapse
You are screwing up some where. Your doing something wrong. N00bs coming in here and don't read and try and complain about the information posted. Every question you have has been answered a dozen times. Try Google or TMFSE. Quit being lazy.
LinearEquation said:
You are screwing up some where. Your doing something wrong. N00bs coming in here and don't read and try and complain about the information posted. Every question you have has been answered a dozen times. Try Google or TMFSE. Quit being lazy.
Click to expand...
Click to collapse
Well, now you're just flat out being an ass. I've been rooting my phone ever since my G1, definitely not a noob, and I wouldn't have asked for help if I didn't need it and if I hadn't already searched a ton.
I've been here longer then you, just an FYI. Also, your grammar is horrid.
I really wish trolls like you weren't allowed on XDA but man, can't control you guys.
PS: Don't get mad and call me a noob just cause you can't read x'D
EDIT: Linear has been added to my ignore list so if he does reply I don't have an urge to argue with him some more.
Biggest problem here Linear is that you really, really need to learn how to read an OP before posting help.
Thanks!
veladem said:
Well, now you're just flat out being an ass. I've been rooting my phone ever since my G1, definitely not a noob, and I wouldn't have asked for help if I didn't need it and if I hadn't already searched a ton.
I've been here longer then you, just an FYI. Also, your grammar is horrid.
I really wish trolls like you weren't allowed on XDA but man, can't control you guys.
PS: Don't get mad and call me a noob just cause you can't read x'D
EDIT: Linear has been added to my ignore list so if he does reply I don't have an urge to argue with him some more.
Biggest problem here Linear is that you really, really need to learn how to read an OP before posting help.
Thanks!
Click to expand...
Click to collapse
Like I said, do some searching first and you'll get there if you implement some reading skills. For being here so long, you still act like a n00b.
As to the troll comment. I have received 169 thanks in a few short months and you have 17 yet you have been on here here almost 3 years. Way to give back to the community, take a bow.
LinearEquation said:
Like I said, do some searching first and you'll get there if you implement some reading skills. For being here so long, you still act like a n00b.
As to the troll comment. I have received 169 thanks in a few short months and you have 17 yet you have been on here here almost 3 years. Way to give back to the community, take a bow.
Click to expand...
Click to collapse
I give back to the community by offering free Android and iPhone modding in my area, and free support via text and email.
Plus I make sure to tell them to check out the Dev's thread or website and to consider donating to the people who make the magic happen.
The only service I make people pay for is electronic repairs which is a flat rate of $20 + customer buys the parts.
So I think I give back to the community at least a little seeing as I have at the least 20+ people a month asking for help cause some idiot installed a unstable ROM on their phone and 4G vanished or other problems.
By the way, since we are laying our d*cks on the table, might I add that boasting about how many "Likes" you have or "Thanks" isn't something to be proud of, you earned them yes, but don't shove that in other peoples faces, that's just childish.
Thanks again for trying to help.
OK before this turns into a flame war, lemme ask something. Did you factory reset and wipe the system partition before flashing the cm ROM?
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
stunts513 said:
OK before this turns into a flame war, lemme ask something. Did you factory reset and wipe the system partition before flashing the cm ROM?
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Click to expand...
Click to collapse
I did try that yes.
Thank you for helping btw.
It's water under the bridge for me. Would be funny if that were the case though because asking him if he swiped was one of my initial responses to him.
Sent from Nexus 7 flo running SinLess ROM 4.2.2 using xda app-developers app
OK I'm going to reiterate some of what linear said, but in a different way, did you checknthe md5sum of the ROM before you flashed it to make sure it matched up with the one given?
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
stunts513 said:
OK I'm going to reiterate some of what linear said, but in a different way, did you checknthe md5sum of the ROM before you flashed it to make sure it matched up with the one given?
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Click to expand...
Click to collapse
Yes sir I did.
OK now for the stupid question, I saw you said it runs a 7.x.x os, just wanted to verify that you are sure of this. I know that kinda a noob question but I have to ask to double check things. Also have you tried flashing cm 11?
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Reiterate
You have a 2012 kfhd
You can get into twrp
Nothing will flash
Odd
We have another person that can't get a restore to take. I've always wondered if it was a formatting issue for him...
But if you were to hand me this kindle I would restore from the restore tool not kffa then I would follow hash codes install 2nd boot loader + twrp thread .
If you've tried that I'm at a loss
Forgive me I read the entire thread but I got lost somewhere in post 3
Sent from my XT907 using xda app-developers app
Sucess! Kinda :/
stunts513 said:
OK now for the stupid question, I saw you said it runs a 7.x.x os, just wanted to verify that you are sure of this. I know that kinda a noob question but I have to ask to double check things. Also have you tried flashing cm 11?
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Click to expand...
Click to collapse
I did verify that it is on stock, rooted, de-self updater-ed, 7.2.3. It was on 7.3 something originally.
Hellfire flashed over just fine, CM 10.1 (I think) Flashed it, booted KindleFire (Orange) then (Blue) then Boot logo Booted pretty fast too.
mrkhigh said:
Reiterate
You have a 2012 kfhd
You can get into twrp
Nothing will flash
Odd
We have another person that can't get a restore to take. I've always wondered if it was a formatting issue for him...
But if you were to hand me this kindle I would restore from the restore tool not kffa then I would follow hash codes install 2nd boot loader + twrp thread .
If you've tried that I'm at a loss
Forgive me I read the entire thread but I got lost somewhere in post 3
Sent from my XT907 using xda app-developers app
Click to expand...
Click to collapse
Yes, 2012 KFHD 7" (Tate)
Yes, TWRP works fine.
No, I got Hellfire to flash, but so far nothing else will flash 0.o :/
Also, I did all my restores from KFFA, BUT, I did do a original backup via ADB and did a restore via Fastboot thinking it might have been KFFA but no go still.
And yes, the thread kinda goes to poop cause I was already kinda upset cause this has been the most frastrating Android to work with, and then the pressure got compounded just cause I decided to ask for help :/
If any of this info helps, please let me know, I believe Hellfire is CM 10.1 . . . I believe, that's off the top of my head though.
Thanks!
To be honest I've only installed kinology... Wife won't let me get rid of the kindle os. I didn't really needed kinology but I wanted to update and did not want to reset it up again. He basically ran a neater version of what I was doing.
Is there an error when you flash the ROM and what ROM are you flashing
Sent from my XT907 using xda app-developers app
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.