I have done searches and come up with nothing, I also cant post links so any help in that regard (post links for me etc) would be helpful until I hit 10 posts.
Ok so I started reading the "[GUIDE] Fix Mainver Error" Thread and I followed theses instructions.
1.Connect phone to computer, enable charge mode
2.Open adb cmd and type : adb shell
3.Type su
4. if you get # symbol continue
5.Type : dd if=/dev/block/mmcblk0p24 of=/sdcard/misc.img (YOU CAN COPY THE IMG TO EITHER sdcard, which is internal memory, or sdcard2, which is removal card)
6. Switch to USB mode
7.copy misc.img from the root of the sdcard to your computer
8.Open misc.img with HeX Editor XVI32
9.Find the version and change it. it will be the first area in the the upper right in the screen of the app
10.change the number in whatever you want. (has to be in the form of.. x.xx.xxx.x
11.Save it and upload it to the root of the sdcard with miscnew.img name
12. Switch to charge mode
13.Type adb shell, su dd if=/sdcard/miscnew.img of=/dev/block/mmcblk0p24
14.Reboot and you are READY TO ROLL!
This all worked with NO problems. However after following these next steps.
Once your done. And you wanna flash the new radio and hboot and all that fun stuff. Do a backup of your Rom (deleted since I cant post links)(Was a link to ph98img) click that. Then relock your hboot, then flash that file in hboot and you let it update.
This is the part I am now, My phone is stuck at the HTC screen and I can no longer reboot using ADB and if I try holding vol down + power then it simply goes straight to HBOOT to try and update the ph98img again and I can not get to fastboot OR use adb commands.
Id be happy to buy someone a beer to fix this mistake
then unlock once done installing. Then reflash your recovery.. and restore your Rom and your golden
I had the same problem. Put your SD card in another android device, go to a file manager and delete the ph98img. It should work, try it!
polovash said:
I have done searches and come up with nothing, I also cant post links so any help in that regard (post links for me etc) would be helpful until I hit 10 posts.
Ok so I started reading the "[GUIDE] Fix Mainver Error" Thread and I followed theses instructions.
1.Connect phone to computer, enable charge mode
2.Open adb cmd and type : adb shell
3.Type su
4. if you get # symbol continue
5.Type : dd if=/dev/block/mmcblk0p24 of=/sdcard/misc.img (YOU CAN COPY THE IMG TO EITHER sdcard, which is internal memory, or sdcard2, which is removal card)
6. Switch to USB mode
7.copy misc.img from the root of the sdcard to your computer
8.Open misc.img with HeX Editor XVI32
9.Find the version and change it. it will be the first area in the the upper right in the screen of the app
10.change the number in whatever you want. (has to be in the form of.. x.xx.xxx.x
11.Save it and upload it to the root of the sdcard with miscnew.img name
12. Switch to charge mode
13.Type adb shell, su dd if=/sdcard/miscnew.img of=/dev/block/mmcblk0p24
14.Reboot and you are READY TO ROLL!
This all worked with NO problems. However after following these next steps.
Once your done. And you wanna flash the new radio and hboot and all that fun stuff. Do a backup of your Rom (deleted since I cant post links)(Was a link to ph98img) click that. Then relock your hboot, then flash that file in hboot and you let it update.
This is the part I am now, My phone is stuck at the HTC screen and I can no longer reboot using ADB and if I try holding vol down + power then it simply goes straight to HBOOT to try and update the ph98img again and I can not get to fastboot OR use adb commands.
Id be happy to buy someone a beer to fix this mistake
then unlock once done installing. Then reflash your recovery.. and restore your Rom and your golden
Click to expand...
Click to collapse
dude this is not a brick, please read before making these threads!!!
andybones said:
dude this is not a brick, please read before making these threads!!!
Click to expand...
Click to collapse
Thanks derp, been reading derp, havent found any answers derp, possible brick doesnt imply a true brick derp.
Can only remove the card, dont have any other devices that can be used to read my sd card. Can get into fastboot without the sd card but from there I am stuck, custom recovery is removed and I am relocked. Looking for information on re unlocking is a little god damn frustrating.
Take your SD card out
Get into h boot, if you can, then go to recovery.
Then, pull back the battery just enough so you can slip your sd card into the phone, make sure the 4 golden sensors (don't know what they are called) are in contact so the phone is still on.
This tricks your phone, or being sneaky. Try that.
polovash said:
Thanks derp, been reading derp, havent found any answers derp, possible brick doesnt imply a true brick derp.
Can only remove the card, dont have any other devices that can be used to read my sd card. Can get into fastboot without the sd card but from there I am stuck, custom recovery is removed and I am relocked. Looking for information on re unlocking is a little god damn frustrating.
Click to expand...
Click to collapse
maybe if you had read more before unlocking your phone, then you wouldn't be in this situation...
Gotta love noobs who complain when someone tells you to read.
con247 said:
What you can do is put the card in almost all the way. Then hold the battery at an angle pressing the contacts on the device so it can get power, but you can still move the memory card. Then (you might need a 2nd person to help you with this) boot into hboot. Since the card is partially slid out, it won't see the PH98 image on there. Once it does it's check, push the card the rest of the way in then snap the battery the rest of the way in. It can be done. I have done it several times while I was attempting to change my cid so HTC Dev.com unlock would work before it did officially.
Click to expand...
Click to collapse
I posted this in several other threads before.. hopefully it helps you. I don't expect you to find it via a search lol so I am posting it here.
Related
Post moved to appropriate area.
zachy1029 said:
Hey everyone, just a quick question that I hope can be answered fairly simply. I have an Eris running Evil Eris 3.0 that I'd like to flash back to 2.1 (via PB00IMG). I know there's a tutorial, but I'm not very good with SDK. I downloaded the SDK and put the misc.img and flash files in the SDK/tools folder but I have no idea where to go from there. I'm trying to get my phone replaced, but I doubt Verizon would like me having anything other than the official releases on the phone, lol. Any help would be greatly appreciated! And I feel inclined to say, "sorry for being a n00b lololol," but I feel that's a little cliché. Thanks guys. Zach
Click to expand...
Click to collapse
Make sure before you do this, your phone is plugged into your computer with the Charge Only option and USB debugging ON.
Enter these commands using command prompt (assuming you have your sdk folder on the root of the C: drive)...
cd C:\android-sdk-windows\tools
adb push PB00IMG.zip /sdcard(will take a few moments)
Click to expand...
Click to collapse
Once that is done boot up into recovery, then select flash zip from sdcard and flash the PB00IMG file.
it's giving me "error: device not found." ??
zachy1029 said:
it's giving me "error: device not found." ??
Click to expand...
Click to collapse
Do you have all your phones drivers installed and everything?
Your wasting your time... If your just going to flash the original pb00img file, you can mount your phone so your sd card pops up on your computer screen, and drop the pb00img file on to your sd card. Then boot in to your hboot by powering your phone off abd then powering back on by holding down volume down and power at the same time and the phone will find the file and then just accept the update by pressing the track ball to confirm.... Thats it your good to go! Your phone will be original 2.1 root or leak whichever version of the pb00img file you use to downgrade..
This seems like a silly question, but I put the PG05IMG.zip on my SD card, reboot into clockwork, pick my file from the SD card and it fails to flash.
I dug around in some of the RUU threads but didn't see anything tutorials. Any tips on how to flash it?
I'm trying to flash just the radio by the way. Thanks!
Put it on the root of your sdcard, boot into the bootloader. It will load the .zip and ask if you want to update radio.
Sent from my ADR6400L using XDA Premium App
Wrong section. And wrong method. Clockwork has nothing to do with it. You do it in bootloader
Put the file on your SD card...don't put it in any folders, and reboot into the bootloader (not cwm), it'll find the update and ask you to install it.
oops - didnt see that someone already told you how..now I'll probably get yelled at by some of the cranky people here on XDA..lol
don't ever flash with CWM, Hboot only, dunno what happens but its probably not good
Deltaechoe said:
don't ever flash with CWM, Hboot only, dunno what happens but its probably not good
Click to expand...
Click to collapse
nothing really happened when I first did that by mistake, I don't think CMW can use the file anyway.
If you haven't figured out how to do it already, this is how.
1. Put the .IMG file in SD card main directory and then reboot to bootloader. ( use ./adb reboot bootloader on your command terminal or some other voodoo method you can think of)
2. While in bootloader, navigate up/down using volume buttons. Select with power button. Choose Bootloader (default option I believe) and I think it should flash.
3. Wait for it to be done (The screen should tell you something like that) and then choose reboot option
4. DONE
Thanks fellas. I wish the posts I kept reading that said "hboot" would have said bootloader instead. Update is flashing right now.
Great development thread!!!!!
hello
First time, Long time. Just managed to install twrp2.2 and it is a nice ui for any sytem. But my issue is rough.
I was going to install a new rom with a Merto pcs service flashed over from Sprint. Unlocked S-om with rom manager on it
when I received it back. Read alot and many peple claim it is ok to stay with 1.50 so-on, others say to go back to 1.40.
I managed to root the device per maxs evo hacks and until I installed and accidently wiped kel/cashe, System by accident,
Anyways I even tried removing the 8 gig sd card and used a fully backed up same card to try and get recovery img file to boot into.
No luck because it goes into a screen that says (Parsing...[SD ZIP under that it says [1] RECOVERY . Then , Do you want to update
up=yes , down = No. Tried yes and continues bootloop.
Then I tried putting back the other sd card and that allows me to go onto the twrp ui but no ofixes that I know of or can do.
Can anyone help me, I will look out for you, really.
Thanks in advance. D-ACman Florida.
If I read correctly, you need to take out your SD card and put into a PC to remove the pg86100.zip img off of it. Put it back then go back to the bootloader and go to recovery. After that, flash a rom.
Sent from my PG86100 using Tapatalk 2
I cannot get anyrom to install
Cetus Corr said:
If I read correctly, you need to take out your SD card and put into a PC to remove the pg86100.zip img off of it. Put it back then go back to the bootloader and go to recovery. After that, flash a rom.
Sent from my PG86100 using Tapatalk 2
Click to expand...
Click to collapse
Ok I can try that but believe me I tried to do just that when thigs went crazy. So I though I should reinstall stock ruu after accidentally
wipeing my system along with cashe/kalvik/ and complete wipe, I somehow wiped the bootdrive of what it is telling me is the is no OS
installed si I'm at a loss and I k now if I can get into trwp recovery I can get a Rom either stock or other to be read and installed.
Each time I get bootloops and what I'm thinking is I should have take fastboot off when try to install an ICS rom, but that is still not the issue
I just believe I wiped eveything because of the statement on twrp ui that there is no OS installed.
I really appreciate whatever feedback and instructions you can give me. Just tell me what to try or do and I will
Thanks very much.
Download twrp recovery.img file. Put into your adb platform tools folder.
With phone off hold volume down & power.
Once in the bootloader, select fastboot.
Open a command from your platform tools folder. Then type..
fastboot boot recovery.img
Then just flash another ROM. If your sdcard is wiped , just toggle USB mass storage in recovery & transfer from computer.
Hope that helps
Sent from my PG86100 using xda premium
SketchyStunts said:
Download twrp recovery.img file. Put into your adb platform tools folder.
With phone off hold volume down & power.
Once in the bootloader, select fastboot.
Open a command from your platform tools folder. Then type..
fastboot boot recovery.img
Then just flash another ROM. If your sdcard is wiped , just toggle USB mass storage in recovery & transfer from computer.
Hope that helps
Ps...remove that PG86IMG.zip from your sd card.
If you don't & its asks...select NO
Sent from my PG86100 using xda premium
Click to expand...
Click to collapse
Sent from my PG86100 using xda premium
No Go
SketchyStunts said:
Sent from my PG86100 using xda premium
Click to expand...
Click to collapse
Ok woke up early today and I had seen this type of fix on another page on Q&A. SO first I had to get the file but you cant just
open prompt and type a command but I k now I had to go to the tools folder after inserting the .img file. Ok did that.
Since I have always kept my SDk in the root of my C:dr it's easier to hold shift down and right click on the tools folder then I placed the commands and brother, for lack of a better word or terminology,--- Absolutlely nothing happens.
Now am I using the right syntax commands? maybe not but the way you gave me the advice I thought it might get the img file onto the internal
drive of the phone.
Man I tried to even put the trwpzip file onto the sdcard and install it, unfortunetly that did'nt work either. So when I use the file manager
in TWRP2.2 I can see the files in the root of the phone and when I go and tap on the inner usb dr I have no files that I can see.What I might
have to do is to take snapshots of the actual menus I am seeing and perhaps I can get help that way.
I know it is difficult when you can't see exactly what is on my phone screen.
What about the DUMLOCK method within the ui of twrp. I have to digest some info on that section for I have'nt a clue about what the
dumlock does but if it's in the twrp UI it must be of some importance.
I really appreciate what you guys are doing for me and wether I get it fixed with or without your methods I will definately give U points for
taking time out to read my issues. I have not mentioned that I also have a duplicate phone (My 1st EVO) and that one came with 1.40 H-Boot
as opposed to this one with 1.50. nevertheless it is a good feeling, I know, when you can get ur **** running and installing Roms like if it was
a candy store. Im an old school type guy, as far as age is concerned and I am a Self employed Sub HVAC/R TECH and I Love to play with
ANdroid and all that goes with Flashing. I just wish I would have went to school for Computer Programming instead of AC.
But it is what it is. Sorry for the long life history and thanks again, If U can figure something else out please reply. Thanks
D-ACman
Still on Bootloop
dacman55 said:
Ok woke up early today and I had seen this type of fix on another page on Q&A. SO first I had to get the file but you cant just
Ok here I'll try again.
Phone is Evo3d Flashed to Metro PCS
phone is unlocked and S-ON
TWRP 2.2 recovery
when noticed I was low on space on my micro sd card I then replaced it witha pny 32 gig class 4 sd card
It comes already formatted 32 fat but I did another clean format on the computer
I replaced or copied everything onto the new card then installed it the working evo 3-d
I was on mikV for a few days but once I got into leedroid tweeks I then decided to just flash my nandroid recovery and go
back to stock.
At that time I was on CWM 4040 or something to that affect.
I noticed the beautiful UI for the TWRP 2.2 and decided to use that recovery.
As soon as I decided to use another custom rom the **** hit the fan.
So now I'm back where I started and I am reading many posts where I think I need to go and relock the phone
then install the stock rom and hopefully that will work.
What I need is to get step by step on the command prompts and computer to recognize the phone
when I try to place the image thats necessary to do the "fastboot lock commands and that it is seen working.
That's where I'm stuck at and am going from this dell laptop computer to my desktop and start the ADK/SDK download
put it in the C: drive and hopefully In the cprompt it will communicate to the phone.
I there a nooby guide to the step by step command procedure to do this?
Click to expand...
Click to collapse
Hello everyone,
I have been searching in vain for a while now to find a solution to my problem and I fear that I may have done something daft to my phone.
I am using a HTC One X+ that was unlocked, s-off and rooted for about a year, i had TWRP and stock android 4.1.1. For ages I have been getting an update alert saying a software update is ready and i think it was some Vodafone update (1.17.161.7). Whenever i accepted and tried to install this it would obviously reboot into TWRP and then the update would fail. This was fine until last night when I decided to install it through TWRP, it said it failed again and i rebooted to find that WiFi wouldnt turn on, my phone was no longer rooted or s-off and that I get no signal. I tried to re-root it but command prompt on the computer or HTC Sync wouldnt recognise my device however it was appearing as HTC One X+ in My Computer and i could access the internal storage.
I restarted into recovery and managed to flash a new root using twrp and the root file using the unlockr.com - how to root the htc one x
Then thinking it was a ROM issue i downloaded and installed InsertCoin Evolution ONE X+ 5.0-6 Sense 5 Android 4.2.2.
This all went through ok however when i reboot from this install it just sticks at the HTC Quietly Brilliant screen. I wiped everything using twrp beforehand.
When i restart into bootloader, it says unlocked, S-On and HBOOT -1.30.0000
Not sure what else to do as now i have no ROM, i read that you have to partition the SD card for InsertCoin to work but the option to partition SD card isnt there in my TWRP (ver. 2.3.3.0)
Any help to even reset my phone back to basic stock everything would be amazing, i have a Titanium Backup of most of my stuff saved btw.
Thanks to anyone who can help.
Did you flash the insert coin boot.img?
Sent from my HTC One X+ using Tapatalk
AndroHero said:
Did you flash the insert coin boot.img?
Sent from my HTC One X+ using Tapatalk
Click to expand...
Click to collapse
No I just copied the whole zip file to the SD card section and installed it from there - ive encountered a new problem now in the fact that my computer no longer can recognise the phone via USB - it still appears in device manager but cant access the sd card and the sd card got wiped by twrp so now i dont have any way of getting things onto the phone that i know of. It just says - failed to open usb master mode in the bootloader. How could i get the computer to recognise the phone again so i can transfer it back onto it and try installing insertcoin again? Really hoping i havent managed to make my phone useless as ive had to dig out the old Nokia 6230 from the drawer haha!
Thanks.
EDIT - Now seen the instruction to flash the boot.img - what a fool i am. Now i need to get it recognised by USB again so i can transfer the zip file to it and go again.
maxwell689 said:
No I just copied the whole zip file to the SD card section and installed it from there - ive encountered a new problem now in the fact that my computer no longer can recognise the phone via USB - it still appears in device manager but cant access the sd card and the sd card got wiped by twrp so now i dont have any way of getting things onto the phone that i know of. It just says - failed to open usb master mode in the bootloader. How could i get the computer to recognise the phone again so i can transfer it back onto it and try installing insertcoin again? Really hoping i havent managed to make my phone useless as ive had to dig out the old Nokia 6230 from the drawer haha!
Thanks.
Click to expand...
Click to collapse
Now seen the instruction to flash the boot.img - what a fool i am. All I need now is to get it recognised by USB again so i can transfer the zip file back and go again.
maxwell689 said:
Now seen the instruction to flash the boot.img - what a fool i am. All I need now is to get it recognised by USB again so i can transfer the zip file back and go again.
Click to expand...
Click to collapse
Without a rom installed you're not able to acces the internal memory of your phone directly. You have to use "adb sideload" command to transfer a rom onto your phone. Look in the General and/or Q&A forum of this device, there are enough guides or topics on how to solve this "problem".
maxwell689 said:
Now seen the instruction to flash the boot.img - what a fool i am. All I need now is to get it recognised by USB again so i can transfer the zip file back and go again.
Click to expand...
Click to collapse
Hi use this link..may be useful (http://forum.xda-developers.com/showthread.php?t=2066390) by the way reaper90 is right you need to sideload the rom..
In TWRP:
1-wipe everything
2-goto advance in twrp
3-select sideload
4-navigate to the folder where you have adb.exe, adbwinapi.dll, adbwinusbapi.dll and fastboot.exe. and make sure to keep the rom and its image; bootimg there.
5-then in command prompt write (adb sideload *name of the rom*.zip) make sure the name is a letter.
6- also make sure to keep the screen alive and not let it goto sleep while adb sideload is working.
7- rom will start setup once sideload is 100%.
Hope this helps. Goodluck.
Optimus said:
Hi use this link..may be useful (http://forum.xda-developers.com/showthread.php?t=2066390) by the way reaper90 is right you need to sideload the rom..
In TWRP:
1-wipe everything
2-goto advance in twrp
3-select sideload
4-navigate to the folder where you have adb.exe, adbwinapi.dll, adbwinusbapi.dll and fastboot.exe. and make sure to keep the rom and its image; bootimg there.
5-then in command prompt write (adb sideload *name of the rom*.zip) make sure the name is a letter.
6- also make sure to keep the screen alive and not let it goto sleep while adb sideload is working.
7- rom will start setup once sideload is 100%.
Hope this helps. Goodluck.
Click to expand...
Click to collapse
Hi, thanks very much for the responses - its much appreciated.
Nothing happens when i type that command, a load of text appears in cmd prompt showing all the adb commands and thats it, i have searched for this problem and found this on twrp website as a possible solution "You will need version 1.0.29 or higher. You can find your current version by typing "adb version" at the command line" My version says 1.0.26 I have tried to update this but cant seem to find a way to do it, would that be an issue?
I think once ive managed to sideload the zip i should be good to go its just getting to that point that seems to be stumping me at the moment.
maxwell689 said:
Hi, thanks very much for the responses - its much appreciated.
Nothing happens when i type that command, a load of text appears in cmd prompt showing all the adb commands and thats it, i have searched for this problem and found this on twrp website as a possible solution "You will need version 1.0.29 or higher. You can find your current version by typing "adb version" at the command line" My version says 1.0.26 I have tried to update this but cant seem to find a way to do it, would that be an issue?
I think once ive managed to sideload the zip i should be good to go its just getting to that point that seems to be stumping me at the moment.
Click to expand...
Click to collapse
Dont sweat it. They understood you wrong.
Guys what he wants to do is copy the file FROM the SDCARD TO the PC.
First you will need to know where the location of your rom then type in the following commands:
Code:
adb devices
If you device is not detected then try to run the CMD as an administrator and try again
then:
Code:
adb pull {location without the curly brackets}
For example if its on the SDCard then:
Code:
adb pull /sdcard/rom.zip
It will paste the file to the folder where the adb is found
Then just open the zip file and get out the boot.img and flash it using fastboot
Hope this helps you out.
Ghand0ur said:
Dont sweat it. They understood you wrong.
Guys what he wants to do is copy the file FROM the SDCARD TO the PC.
First you will need to know where the location of your rom then type in the following commands:
Code:
adb devices
If you device is not detected then try to run the CMD as an administrator and try again
then:
Code:
adb pull {location without the curly brackets}
For example if its on the SDCard then:
Code:
adb pull /sdcard/rom.zip
It will paste the file to the folder where the adb is found
Then just open the zip file and get out the boot.img and flash it using fastboot
Hope this helps you out.
Click to expand...
Click to collapse
Hey, thanks.
No they got me correctly, there is absolutely nothing on my phone at all and I need to get my new ROM zip file from the PC to the phone so that I can install it. I am currently downloading SDK manager to try and update my adb to 1.0.29 or higher and will see if that works.
maxwell689 said:
Hey, thanks.
No they got me correctly, there is absolutely nothing on my phone at all and I need to get my new ROM zip file from the PC to the phone so that I can install it. I am currently downloading SDK manager to try and update my adb to 1.0.29 or higher and will see if that works.
Click to expand...
Click to collapse
Ok, i downloaded the hasoon toolkit and select ADB Sideload a ROM and it says "error device not found" in the command prompt. I am in ADB Sideload mode in TWRP with it plugged in via USB so dont know what to try next.
maxwell689 said:
Ok, i downloaded the hasoon toolkit and select ADB Sideload a ROM and it says "error device not found" in the command prompt. I am in ADB Sideload mode in TWRP with it plugged in via USB so dont know what to try next.
Click to expand...
Click to collapse
Lol.. Well, as i said try to run the Toolkit/cmd as administrator and try different usb ports.. It took me 5 minutes on windows 8 for the adb to properly read the device , had to try different usb ports, unplug , replug, and so on..
maxwell689 said:
Ok, i downloaded the hasoon toolkit and select ADB Sideload a ROM and it says "error device not found" in the command prompt. I am in ADB Sideload mode in TWRP with it plugged in via USB so dont know what to try next.
Click to expand...
Click to collapse
Hi goto htcdev n download the latest sdk
Sent from my HTC One X+ using xda app-developers app
---------- Post added at 09:08 PM ---------- Previous post was at 09:07 PM ----------
I will try to send I over the files for command prompt tomorrow.
Sent from my HTC One X+ using xda app-developers app
Optimus said:
Hi goto htcdev n download the latest sdk
Sent from my HTC One X+ using xda app-developers app
---------- Post added at 09:08 PM ---------- Previous post was at 09:07 PM ----------
I will try to send I over the files for command prompt tomorrow.
Sent from my HTC One X+ using xda app-developers app
Click to expand...
Click to collapse
Right ive manged to download the latest sdk and then after much unplugging and plugging and right clicking things in device manager its recognised my phone enough to sideload and install the ROM. I have also managed to fastboot the boot.img file as well after 3 attempts but it finally worked so i have a phone back again!! Thanks everyone here!!! Now to upload my titanium backup of apps, sadly i think ive lost all my photos thou
But thanks again to all. Sorry if ive been a bit noob but its been a good learning curve for me as i never had these issues with my HTC desire
maxwell689 said:
Right ive manged to download the latest sdk and then after much unplugging and plugging and right clicking things in device manager its recognised my phone enough to sideload and install the ROM. I have also managed to fastboot the boot.img file as well after 3 attempts but it finally worked so i have a phone back again!! Thanks everyone here!!! Now to upload my titanium backup of apps, sadly i think ive lost all my photos thou
But thanks again to all. Sorry if ive been a bit noob but its been a good learning curve for me as i never had these issues with my HTC desire
Click to expand...
Click to collapse
Thats great news that all is well now..feel free to post.. and dont forget to press the Thanks button
Another fine TEAM CODEFIRE release :victory:
This thread is for:
A. Those with TWRP already installed but wish to update their rom to stock pre-rooted ZVB.
B. Those on stock unmodified LS990 ZVB/ZVC and want root.
METHOD A
Prerequisite: TWRP already installed and working.
1. Click and download the pre-rooted stock ZVB and modem zips below and place them on internal or external sdcard.
2. Flash zip from step #1 in TWRP (while in twrp.. Install > select zvb rom > swipe slider to confirm and flash)
3. Reboot out of TWRP and back into system. Finished.
If TWRP says "no OS" (after step #3) just ignore and continue with the reboot.
If phone hangs at bootup (after step #3) for more than 5 minutes you may have to boot into TWRP and do a factory reset.
Unplug phone from USB cable > pull battery then put battery back in > hold volume down + power to boot into TWRP > select "Wipe" > swipe slider to confirm.
DOWNLOAD FLASHABLE ZIPS HERE
You will see 2 zip files... one containing system/boot and the other containing modem/rpm/tz. I'd suggest flashing both zips... but some people may not want to update modem which is why I split them into 2 zips.
Click to expand...
Click to collapse
METHOD B
Prerequisite: USB Debugging enabled, Windows computer, LG USB drivers installed and reading comprehension. Have a mac or linux?... use a virtual machine.
USB drivers - CLICK HERE to download
There is no need to pack this into a 1-click bat file. It's a few simple commands... all laid out for you step-by-step below. 1-click roots can fail... but doing everything manually and properly should have a 100% success rate. Plus you're seeing how the entire process works and maybe learning a thing or two. Don't be a lazy 1-click zombie.. this is XDA not androidcentral.
Thanks to:
blog.lvu.kr for the Send_Command.exe - LINK HERE
Unjustified Dev for his original English Guide - LINK HERE
l33tlinuxh4x0r for his idea on swapping the old LAF partition - LINK HERE
thecubed, IllegalArgument (the other members of TEAM CODEFIRE) and jcase for the LG G4 root - LINK HERE
Me, myself and I have have taken all of the above ideas and formed 'em like Voltron to bring root to the the latest LS990 updates (ZVB/C). I have written the directions below so that any n00b who can read should be able to follow along. For those that know what you're doing already... the main thing to pay attention to are the commands themselves.
1. Download THIS ZIP FILE HERE. Unzip it on your windows computer. Location of folder is not important.. just make sure you know where to find it.
2. Open the folder you just unzipped and inside should be a bunch of loose files. Hold the "Shift" key then right-click someone in the folder and select "Open command window here". A command prompt window should open.
If confused, CLICK HERE for a link with a more detailed explanation.
3. While phone is booted up normally (and usb debugging enabled).. click on the command prompt window then type: "adb devices" without the quotes and hit enter/return. You should see your phone listed in the output.
If no device is found.. make sure USB Debugging is enabled - CLICK HERE
If output says "Device Offline" check your phone's screen.. you may still have to accept the RSA prompt. Check the box then hit OK. CLICK HERE for example.
4. Once you see your phone listed after "adb devices" command it's time to begin... copy the entire command below and paste it into the command prompt windows (right-click > paste.. not control + v) then hit enter/return to send the command. Be sure to copy the ENTIRE command below.. it's a long one. Command may take 10-15 seconds to complete.
Code:
adb.exe push busybox /data/local/tmp/ && adb.exe push lg_root.sh /data/local/tmp/ && adb.exe push UPDATE-SuperSU-v2.46.zip /data/local/tmp/ && adb.exe push lafzv6.img /sdcard/
5. Reboot into Download Mode. There are multiple ways to do this.. but since you already have the command prompt windows open and adb connected simply type the following command into command prompt then hit enter/return. AS SOON as you hit enter/return hold he volume up button on your phone. Might be easier to have the phone in your hand ready to press volume up before hitting enter/return. When the phone reboots you should be in Download Mode.
Code:
adb reboot
6. Once in Download Mode (Should say Firmware Update on phone screen) find out the COM port your phone is using. LG drivers must be installed for COM port to show up. Easiest way to find your COM port number... double-click the "ports.bat" file from the zip you extracted in step #1. You want to make note of the COM port # next to "LGANDNETDIAG1". For example - on my computer it said \Device\LGANDNETDIAG1 REG_SZ COM4... so my COM port would be COM4. Make sure you use YOUR COM port #. It could be any number.
7. You may have 2 command prompt windows open... click on the first one you opened.. the window you opened in step #2. Copy/paste the following command to enter into the "Download Mode Shell" then hit enter/return... remember to substitute the COM port number with YOUR OWN COM #
Code:
Send_Command.exe \\.\COM4
You should now see the following output in your command prompt window...
Author : blog.lvu.kr
SPECIAL COMMAND : ENTER, LEAVE
#
This confirms you're in "Download Mode Shell". Now type "id" without quotes then hit enter/return and you should see the following output...
uid=0(root) gid=0(root) context=u:r:kernel:s0.. which will confirm that you are now successfully talking to your phone. Continue on to step #8.
If the "id" command just sits there hanging... or you just get a # as a response you are NOT talking to your phone. To fix this... hit ctrl + c which will exit the "Download Mode Shell". Redo step #7.. resending the "Send_Command" command... then once you are back in the "Download Mode Shell" type "id" without quotes then hit enter/return again... this time you should see uid=0(root) gid=0(root) context=u:r:kernel:s0
If you still do not see uid=0(root) gid=0(root) context=u:r:kernel:s0 after trying a seconds time it is possible you are using the wrong COM port number.
8. Now it's time to backup your current LAF partition then write the older ZV6 LAF to the phone. This step uses some of the G4 root tricks to bypass the latest root method blocks from LG and allows us to then use the older root method since you'll end up with an older ZV6 LAF partition. Copy/paste the following command into the command prompt window then hit enter/return...
Code:
dd if=/dev/block/mmcblk0 bs=8192 skip=24576 count=4096 of=/data/media/0/lafOG.img
In a second or two you should see # on the next line... which means the command you just sent has finished. Current LAF is now backed up. Now you need to write the older ZV6 LAF to the phone. It's already on your internal SD card (you did this in step #4). Copy/paste the following command into command prompt then hit enter/return.
Code:
dd if=/data/media/0/lafzv6.img bs=8192 seek=24576 count=4096 of=/dev/block/mmcblk0
In a second or two you should see # on the next line... which means the command you just sent has finished. Now you need your phone to exit download mode... boot up.. then reboot back into Download Mode. This process loads the ZV6 download mode you just flashed. In the command prompt window type the following command then hit enter/return (be sure to use all caps!)...
Code:
LEAVE
This will reboot your phone. Now you need to reboot into Download Mode again... type the following command in command prompt then hit enter/return...
Code:
adb reboot
And again.. as soon as you send the command hold the phone's volume up button so that you reboot into Download Mode. You may see a error on the screen... ignore.. a few seconds later it should show the Firmware Update screen. Time to move on to step #9...
9. Once in Download Mode you need to send the "Send_Command" command you used in step #7.. COM port # should still be the same. Remember the following command is just an example.. you MUST use your own COM port #. Copy/paste the command below.. enter your own COM port number then hit enter/return..
Code:
Send_Command.exe \\.\COM4
And again you should see the following output..
Author : blog.lvu.kr
SPECIAL COMMAND : ENTER, LEAVE
#
And just like in step #7 you need to confirm you're able to talk to your phone... type "id" without the quotes then hit enter/return. You should see uid=0(root) gid=0(root) context=u:r:kernel:s0 if it worked. When you get the uid=0(root) gid=0(root) context=u:r:kernel:s0 output it's time to move to the final step... #10.
If the "id" command just sits there hanging... or you just get a # as a response you are NOT talking to your phone. To fix this... hit ctrl + c which will exit the "Download Mode Shell". Redo step #9.. resending the "Send_Command" command... then once you are back in the "Download Mode Shell" type "id" without quotes then hit enter/return again... this time you should see uid=0(root) gid=0(root) context=u:r:kernel:s0
10. Copy/paste the following command then hit enter/return. This command flashes the supersu zip and is what is putting root into ZVB (or whichever sw version you're using). Make sure you copy the ENTIRE command. Command will take 15-20 seconds after sending before you start seeing anything happen.
Code:
sh /data/local/tmp/lg_root.sh dummy 1 /data/local/tmp/UPDATE-SuperSU-v2.46.zip /data/local/tmp/busybox
You should see some output from the zip flashing. when the output stops and you get the # it has finished. You should now have root.
BUT before you exit Download Mode, we should put back the original LAF [unless you plan on installing TWRP(with autorec for example).. then you can leave it skip the restoring LAF command. If you ONLY want a rooted rom and do NOT want TWRP I suggest you run the command]
To restore LAF copy/paste the following command then hit enter/return...
Code:
dd if=/data/media/0/lafOG.img bs=8192 seek=24576 count=4096 of=/dev/block/mmcblk0
When that finishes and you see the # you are all done! Type the following command (all caps!) then hit enter/return to exit Download Mode and boot into your rooted rom..
Code:
LEAVE
10 easy steps.. that wasn't bad was it?
The only way the above steps won't work is if you skipped/missed a step or didn't follow along properly.
This isn't a race... take your time and understand what's going on.
It take's me about 2 minutes to do this myself. But reading everything and learning the first time maybe takes... 10 minutes... yes, a whole 10 minutes!
Example of command prompt (click to enlarge)
Click to expand...
Click to collapse
Enjoy your freedom!
Donations are cool.. but never expected. But at least hit that thanks button if this thread helped you root. :good:
reserved to be annoying
ZV4/6 rpm,tz partitions
https://www.androidfilehost.com/?fid=95916177934529082
Just in case the ZVB ones cause us issues also.
Haha. You know someone is going to make a 1 click directly from your 10 steps. thanks!
Sent from my LGLS990 using XDA Free mobile app
Used method A. Not coming out of boot screen at all. Did a factory reset. Help!
Sent from my Nexus 7 using XDA Free mobile app
YellaHayes said:
Used method A. Not coming out of boot screen at all. Did a factory reset. Help!
Sent from my Nexus 7 using XDA Free mobile app
Click to expand...
Click to collapse
*edit*
issue was found.. I forgot an ".img" in the flash script. new zip being uploaded now for all future downloaders. for those who already downloaded.. you can extract the bootZVB.img from the zip and flash it through twrp (press install.. press "images" button rather than finding zip > then select the bootZVB.img > then select boot) or you can download engine95's updated script below.. replacing the one in your current zip. Or you can just redownload the fixed zip Sorry about the typo.. fortunately it was harmless.
Still no go. Should we be doing s full system wipe? Internal and external wipe as well?
Sent from my Nexus 7 using XDA Free mobile app
Success with Method A
I came from BarePapa v2. Installed both zip files and rebooted. 10 minutes later, everything seems just fine, except for the very minor annoyance that I have to manually disable the annoying Sprint apps. I hesitated to even mention that.
Great work on this, and thanks again on behalf of the entire Sprint LG G3 community.
Hold off on installing this. The ZVB kernel isn't getting installed.
I should have a quick fix for it shortly.
Edit/Update
To install the ROM, you need to replace the updater-script under META-INF.
Using 7zip, or another zip program, Open the ROM zip.
Drill through META_INF until you see "updater-script" and replace it with THIS ONE
MAKE SURE YOU REMOVE THE .txt on the file!!! It's the only way I could upload it.
Close the zip and flash away!
ahh woops.. I typo'd and put bootZVB instead of bootZVB.img. Uploading corrected zip now. I put the zip together after I wrote up the root method.. guess my eyes were tired. Thanks for pointing out the error @engine95 . I'll pull the file now.. when you guys see it return.. it'll be the fixed one.. prob 30min.
fixed zip is up. everything should be perfect now.
i expect nothing but praise for the remainder of this threads lifespan
lol
autoprime said:
ahh woops.. I typo'd and put bootZVB instead of bootZVB.img. Uploading corrected zip now. I put the zip together after I wrote up the root method.. guess my eyes were tired. Thanks for pointing out the error @engine95 . I'll pull the file now.. when you guys see it return.. it'll be the fixed one.. prob 30min.
Click to expand...
Click to collapse
So since im already stuck at the bootscreen should i just flash the new zip and be good? im kinda confused
YellaHayes said:
So since im already stuck at the bootscreen should i just flash the new zip and be good? im kinda confused
Click to expand...
Click to collapse
multiple fixes have been pointed out.. please read the entire first page. or flash the new zip (it's up now).
autoprime said:
fixed zip is up. everything should be perfect now.
i expect nothing but praise for the remainder of this threads lifespan
lol
Click to expand...
Click to collapse
Except when I installed it, TWRP said "No OS found", but it flashed just fine.
Thanks again for doing this. :highfive::good:
autoprime said:
multiple fixes have been pointed out.. please read the entire first page. or flash the new zip (it's up now).
Click to expand...
Click to collapse
Thanks. downloading now. Dont be mad at me but I put the new zip on my sdcard, flash in twrp, and then flash the modem zip as well correct?
---------- Post added at 01:58 PM ---------- Previous post was at 01:33 PM ----------
engine95 said:
Except when I installed it, TWRP said "No OS found", but it flashed just fine.
Thanks again for doing this. :highfive::good:
Click to expand...
Click to collapse
is it safe to flash the modem zip as well?
YellaHayes said:
Thanks. downloading now. Dont be mad at me but I put the new zip on my sdcard, flash in twrp, and then flash the modem zip as well correct?
---------- Post added at 01:58 PM ---------- Previous post was at 01:33 PM ----------
is it safe to flash the modem zip as well?
Click to expand...
Click to collapse
Yes to your first question. But...
Herein lies a possible issue for us.
If you rooted from ZV4, then I would remove the rpm, tz partitions and then flash it.
If you rooted ZV8, then you probably want the rpm, tz partitions.
I'm still on the ZV4 bootloader so I can't say what to do if your on fully rooted ZV8. Most of us are still on, or are using ZV4 bootloader.
engine95 said:
Yes to your first question. But...
Herein lies a possible issue for us.
If you rooted from ZV4, then I would remove the rpm, tz partitions and then flash it.
If you rooted ZV8, then you probably want the rpm, tz partitions.
I'm still on the ZV4 bootloader so I can't say what to do if your on fully rooted ZV8. Most of us are still on, or are using ZV4 bootloader.
Click to expand...
Click to collapse
what problems happen for those on zv4 bootloader? I'm using zv6 aboot/laf... and zvb everything else and it's been just fine. zv6 still allows bump and seems fully compatible with zvb.. maybe those on zv4 should update to zv6 if thats the case? modem.img pairs with tz.img due to some tz apps contained inside the modem... so they should always be joined when possible. and rpm is usually paired with tz which is why those 3 are usually grouped together.
it's all about options and user preference of course. just reporting what's working for me.
Ok so I'm finally up and running. Didn't flash the modem at first so I def was struggling but flashed it and looks like I'm all good. Amazed that I didn't have to completely wipe my internal storage but I'm pretty much stock with root. I really appreciate all the help. It's what I get for being annoyed with the android update notification.
Sent from my Nexus 7 using XDA Free mobile app
autoprime said:
what problems happen for those on zv4 bootloader? I'm using zv6 aboot/laf... and zvb everything else and it's been just fine. zv6 still allows bump and seems fully compatible with zvb.. maybe those on zv4 should update to zv6 if thats the case? modem.img pairs with tz.img due to some tz apps contained inside the modem... so they should always be joined when possible. and rpm is usually paired with tz which is why those 3 are usually grouped together.
it's all about options and user preference of course. just reporting what's working for me.
Click to expand...
Click to collapse
And those partitions seem to work for all but Sprint. We get random reboots and freezes if we use anything but ZV4/6 rpm, tz partitions on the ZV4 bootloader. That's why I posed so early in your thread for those partitions. Just in case.
I can't remember if ZV4 and ZV6 are the same ones now. But I'm assuming they were the same as that's how I have them listed.
People using CM/AOSP have had the same issue, yet when they install the ZV4/6 rpm, tz partitions, a lot of their issues go away.
It doesn't make sense, and the only thing I can think of, is it has something to do with CDMA. Since Sprint's about the only player mainly using it. IDK
@autoprime Thanks for giving credit.. Question though... Why use bs= count= and skip=? Are they really necessary?
Also to everyone else... I am going to try to make a "One Click" method for this. Probably a Linux script first and a Windows script to follow. I have to work tonight but I'm thinking that I will be able to get them wrote by Tuesday.
EDIT: I got the windows version up. You can find it here.
l33tlinuxh4x0r said:
@autoprime Thanks for giving credit.. Question though... Why use bs= count= and skip=? Are they really necessary?
Also to everyone else... I am going to try to make a "One Click" method for this. Probably a Linux script first and a Windows script to follow. I have to work tonight but I'm thinking that I will be able to get them wrote by Tuesday.
Click to expand...
Click to collapse
yes, needed due to selinux.
booo 1-clicks I'm sure many will appreciate the automation tho. :good: