Database Users

Really stuck

Hey, ive recently updated the rom on my phone from cm 6.1 (stable) to cm7 nightly (vendor ace) -
initially i did it to test it and to see if it would fix my problem were the phone screen would automatically turn off when reciveing and sending calls, which resulted in taking out the battery and turning back on(which is now randomly working again)
after i flashed the cm7(via rom mamanger) it worked fine, got back onto the phone and i didnt have market and my phone wasnt connecting to google accounts aswell, so i then installed gapps. it worked the first time and it said it was succesful.
Restarted my phone and its the same, no market..etc..
so i tried it again, same thing, then for some reason when ever i try and load into the recovery from rom manager or from the inital vol - and power, it just freezes on the HTC startup screen.
The only thing i think i may have done different was adding this file to my phone (recovery-ace-3.0.0.5.img) because someone on cm7 told me i needed it, but i have no clue what it was for nor how to load or flash it.
So my main problem is, gapps wouldnt install and now ic ant access the recovery manager either and im getting kinda bored without my precious DHD
Can someone please help me

Just to make this clear, you cannot access your recovery even through bootloader? Can you get to the bootloader?

jkoljo said:
Just to make this clear, you cannot access your recovery even through bootloader? Can you get to the bootloader?
Click to expand...
Click to collapse
i cant access the recovery manager through the boot loader either but yes i can access the boot loader

Okay, then download this file:
http://dl.dropbox.com/u/18138289/reco.img
And then download radio flash.zip from radio.img flash guide sticky, extract it, open "start here", drop reco.img to the radio flash folder and type:
fastboot flash recovery reco.img
Click to expand...
Click to collapse
Your device has to be in bootloader>fastboot mode. After that you can access recovery, do a full wipe and flash CM6.

Ill try this now and reply once its done, erm why flash cm6? or do you think the same fault will happen if i try and reinstall cm7?
do i have to be in the bootloader from the beginning?
plus is there htc sync for MACs?
Thanks alot btw

Well, you can try to flash the cwm 3.img like I described and then install CM7, but I know for sure that the recovery I linked works with CM6.
You have to be in bootloader fastboot when you issue the command, yes.
I do not have a MAC, so I am not really sure. I think that you would have to get Android SDK and forget about radio flash toolkit if you want to use a MAC.

And then download radio flash.zip from radio.img flash guide sticky, extract it, open "start here", drop reco.img to the radio flash folder and type:
right so whilst i do all of this, i need to be in the bootloader > fast boot - sorry just want to clarify, ive not done this before but i have faith!!

Yeah, it does not really matter, but I would put my phone to bootloader fastboot so it is ready. The important thing is that your device is in fastboot mode when you enter the fastboot flash command.

Kool Kool, well thanks alot im going to try this now

right so i successfully entered the recovery, thanks alot for the help with that.
I tried to reinstall cm7 -worked and gapps - said it worked, but it still wont bring up the market app, why is this?
i reinstalled a back up and everything is working again, im so confused why it wont bring up the market app in cm7

o0jaz0o said:
right so i successfully entered the recovery, thanks alot for the help with that.
I tried to reinstall cm7 -worked and gapps - said it worked, but it still wont bring up the market app, why is this?
i reinstalled a back up and everything is working again, im so confused why it wont bring up the market app in cm7
Click to expand...
Click to collapse
when you boot into recovery, not just through rom manager, does it say you have cwm 3.x installed? if so try re-flashing the gapps, if not go back into fastboot and flash cwm3.

Wow, really sorry about that, i thought the cwm was a custom firmware i thought t was optional, sorry for the inconvenience, but thank you alot this has been daunting :/
flashed the right recovery, and everything is working as it should be, thankyou both very much

[GUIDE 25/02/2012]UK ONLY /Orange/ T-mobile – ROOTING, UNLOCKING BOOTLOADER

I have updated this guide as I have a new replacement from t-mobile. This guide was based on my previous atrix which was running froyo (2.2.2) This time I have applied OTA 45.21.2.Mb860.T-mobile.en.gb and everything works perfect so if you have updated your phone to 2.3.4 then you can use this guide as well
I have decided to create this thread as I have seen many people confused about the difference between At&t phones and their UK ones. This thread will help you make the decision whether you want to hack your phone or not. I own T-mobile UK Atrix and whatever I have done worked perfectly for me. I’m not responsible for any bricks. You doing this on your own risk – good news is that no one (UK) had their mobile bricked. ALL CREDITS GOES TO DEVELOPERS AND OTHERS THAT CREATED SIMILAR THREATS – THANKS
ROOTING – If you running froyo (2.2.2) I have used gingerbreak method which is very easy:
Code:
1. Download Gingerbreak.exe from here: [url]http://api.viglink.com/api/click?format=go&drKey=1359&loc=http%3A%2F%2Fforum.xda-developers.com%2Fshowthread.php%3Ft%3D1046626&v=1&libid=1311795059566&out=http%3A%2F%2Fbandbinnovations.com%2Fxda%2FGingerBreak.exe&ref=http%3A%2F%2Fforum.xda-developers.com%2Fforumdisplay.php%3Ff%3D997%26order%3Ddesc%26page%3D4&title=%5BHOWTO%5D%20Easy%20Root%201.5.7%20%26%201.83%20using%20GingerBreak%20-%20xda-developers&txt=http%3A%2F%2Fbandbinnovations.com%2Fxda%2FGingerBreak.exe[/url]
2. Make sure you have got debugging mode ON(settingsApplications Development) and you have installed drivers for your atrix
3. Run Gingerbreak.exe on your pc
4. In your phone you will find new app called gingerbreak – run it and select root. Mobile will reboot itself once is done.
5. Congratulation you are rooted.
NOTICE: You need to have External SD Card and also be aware that rooting this way will format your internal storage.
ROOTING – If you running gingerbread (2.3.4) use superoneclick (http://forum.xda-developers.com/showthread.php?t=803682) and fallow the instructions on the original thread. Very easy way.
If you want to try ANY Custom ROM you need to Unlock your Bootloader:
Code:
1. You need to download and install RDS lite on your PC: [url]http://forum.xda-developers.com/attachment.php?attachmentid=634879&d=1308872277[/url]
2. Download and extract IHOP_Bell.rar: [url]http://diamantephoto.com/IHOP_Bell.rar[/url]
3. Download and extract Fastboot tools [url]http://gititbit.ch/FAST[/url]
4. Power down your Motorola Atrix
5. Take out your microSD card and SIM card for the flashing process
6. While turning the phone on, hold the Volume Up button until it acknowledges RSD
7. Your device will say “Starting RSD protocol support”
8. Run “RSD Lite” on your computer
9. Press the “. . .” button next to the box labeled “Filename”
10. Load up the SBF file – IHOP_Bell.sbf
11. Plug your device into your computer
12. RSD Lite should recognize your device and say “Model: NS Flash Olympus” and “Connected…”
13. Press the “Start” button
14. Be patient while the phone reboots. It will take a long time.
15. Open and extract the Fastboot package from above
16. Open a command prompt window
a. On Windows, press Start and type “cmd” then press the enter button
17. Type the following command. Your directory will be the folder where you extracted the Fastboot package.
(Example: cd C:\Users\Kenneth\Desktop\fastboot-package)
a. cd your directory here
18. Power down your Atrix device
19. Hold the power button and the downward volume button until you see “Fastboot”
20. Let go of the buttons and press the upward volume button once
21. You will now see “Starting Fastboot protocol support”
22. Plug your device into a USB port in the back slot of your computer
a. Front slots sometimes do not have enough power to stay connected to the device.
23. Type the following command:
a. fastboot oem unlock
24. You will now receive a warning along with a unique device ID
25. Type the following commands using your unique device ID in place of the ####:
a. fastboot oem unlock ####
b. fastboot reboot
26. Wait for your device to reboot. Congratulations! You now have an unlocked bootloader!
I recommend to install romracer's Recovery : http://forum.xda-developers.com/showthread.php?t=1204500.
Instalation:
Code:
$ fastboot devices
TA20700KXH fastboot
$ fastboot erase recovery
erasing 'recovery'... OKAY [ 0.741s]
$ fastboot flash recovery recovery.img
sending 'recovery' (4780 KB)... OKAY [ 0.490s]
writing 'recovery'... OKAY [ 0.544s]
The reason I recommend this recovery is because the official clockwork recovery doesn't support external sdcard (bug?). If this doesn't bother you then you can download Rom manager from market and install official recovery.
Most of the roms have unified kernel which means you don't need to apply anything after installation. This includes roms like aura, the dark side, cyanogen mod.
However if you do have issues with memory then download kernel from this thread: http://forum.xda-developers.com/showthread.php?t=1156040

Thanks for this - thats my night sorted

Very useful and thorough guide. Thanks a lot Mr Foka. I left you a "thanks" btw.

thank you so much! just going to unlock my orange atrix
Sent from my MB860 using XDA Premium App

Jibraldor said:
Very useful and thorough guide. Thanks a lot Mr Foka. I left you a "thanks" btw.
Click to expand...
Click to collapse
That's very kind. Thanks

Hi there,
sorry, a quick question regards to the custom ROMS, you mentioned if I am going to apply the AT&T ROMs, I need to apply custom kernels,
Foka002 said:
You can now install ANY Custom ROM. However if you want to install ROM That is designed for AT&T you will have to apply FIXED Kernel for international (faux’s or eveal kernels working excellent for our devices - http://forum.xda-developers.com/showthread.php?t=1169409 or http://forum.xda-developers.com/showthread.php?t=1156040)
Click to expand...
Click to collapse
but in eval-'s thread, he mentioned:
I suspect these boot.img will 'fix' RAM for unlocked internationals on any Gingerbread 2.3.x build (only), but this as faux123 helpfully points out, your modules must match (important for wifi, vpn) ! So for now, these boot.img with quick & dirty RAM fix are only for this Orange FR 2.3.4 system.img!! (Unless you want to copy around dhd.ko and parts of /system/lib/hw between /systems...)
Click to expand...
Click to collapse
So can I just apply his kernel on the AT&T firmware?
Cheers,

Well I tried eval kernel few times and long time ago. For every rom I had it I used faux kernel so it's safer to use it with recent roms.
Sent from Motorola Atrix

Hi thanks for the time and effort but I was hoping someone could help me.Trying to follow the guide but having trouble with two parts.Firstly when running pudding through rsd how long exactly do you leave it?It says to leave it at android lockscreen but rsd dhows as not finished like 38% rebooting at this time/Also when to connect or disconnect is confusing as I read a guide previously to yours am not sure if phone gets disconnected after rsd?Lastly and I think my most serious problem is that I cant get the fastboot command to work.It will either say unable to find the path specified or no command on internal or external etc.Any ideas?Thanks

Great guide! Thanks for putting this together.

So correct me if im wrong but I can follow this guide, and put on gingerbread on my orange ATRIX and it will work fine?!?!?!?
Also once the official update hits UK can I just install that?
Great work btw
Sent from my MB860 using XDA App

Just to ask / add
There is going to be an official Orange OTA update isnt there? I could do it this way but for a change want to try it the offical way

scotty7910 said:
Hi thanks for the time and effort but I was hoping someone could help me.Trying to follow the guide but having trouble with two parts.Firstly when running pudding through rsd how long exactly do you leave it?It says to leave it at android lockscreen but rsd dhows as not finished like 38% rebooting at this time/Also when to connect or disconnect is confusing as I read a guide previously to yours am not sure if phone gets disconnected after rsd?Lastly and I think my most serious problem is that I cant get the fastboot command to work.It will either say unable to find the path specified or no command on internal or external etc.Any ideas?Thanks
Click to expand...
Click to collapse
In order to use fastboot you need to have motorola drivers installed. Im not sure about eds but if your device is recognised then it is fine. Im not sure about waiting time in rsd but if you did fallow this guide step by step you shouldn't have any problems.
Roberts56
Yes you will be able to flash gingerbread but you won't be able to use official OTA unless you downgrade to 2.2.2 using fruitcake method. The thing is if you want to play with custom roms then there is no point in waiting for official release because its not going to be any better than any rom we've got now. Just keep in mind once you unlock your bootloader you will lose warranty.
Uk OTA is coming for sure but I have no idea when. Rumours says in sep/oct

Boot screen
Hi
After flashing IHOP_BELL, everytime I reboot I get a menu instead of Motorola Logo at beginning. Is that normal?? When I leave it there it will boot Android and will show the Motorola Logo.
It looks like this:
http://2.bp.blogspot.com/-dPOywn12xbg/Th6albF5xPI/AAAAAAAAAGw/BStIYOa7B_A/s1600/11.JPG
Thanks for your help

R3wt3d said:
Hi
After flashing IHOP_BELL, everytime I reboot I get a menu instead of Motorola Logo at beginning. Is that normal?? When I leave it there it will boot Android and will show the Motorola Logo.
It looks like this:
http://2.bp.blogspot.com/-dPOywn12xbg/Th6albF5xPI/AAAAAAAAAGw/BStIYOa7B_A/s1600/11.JPG
Thanks for your help
Click to expand...
Click to collapse
Strange...I've never seen this before. Can anyone tell why is that ?

hmm it's not normal then?
Any idea if I could overwrite with IHOP_BELL again downloaded freshly from xda?
I downloaded it from here.
http://diamantephoto.com/IHOP_Bell.rar
thanks

R3wt3d said:
hmm it's not normal then?
Any idea if I could overwrite with IHOP_BELL again downloaded freshly from xda?
I downloaded it from here.
http://diamantephoto.com/IHOP_Bell.rar
thanks
Click to expand...
Click to collapse
Notice of on your photo it says that your phone is unlocked! Is that right?
Did you flash a recovery? Romracer's I hear is good at the moment.
Then did you flash a rom? As says no OS DETECTED!
Can recommend http://forum.xda-developers.com/showthread.php?t=1169409
But you can use fruitcake s
Swyped from "Mount" Olympus

nitrox1 said:
Notice of on your photo it says that your phone is unlocked! Is that right?
Did you flash a recovery? Romracer's I hear is good at the moment.
Then did you flash a rom? As says no OS DETECTED!
Can recommend http://forum.xda-developers.com/showthread.php?t=1169409
But you can use fruitcake s
Swyped from "Mount" Olympus
Click to expand...
Click to collapse
yeah it's unlocked. and after that menu I flashed ORFR boot system webtop
U guys never seen that menu? I got it right after flashing sbf...well during sbf flashing.

R3wt3d said:
yeah it's unlocked. and after that menu I flashed ORFR boot system webtop
U guys never seen that menu? I got it right after flashing sbf...well during sbf flashing.
Click to expand...
Click to collapse
Did you flash the rom with it too, as webtop is a separate part?
Never seen that menu, but never tried to boot just after ihop either though, as has no rom as party of it, check out size of the file, and size of a normal sbf.
Swyped from "Mount" Olympus

I think this is soft brick...Is this UK atrix ??

Noob questions
Do I need to root before I flash this ROM? Because I don't have an SD card I'm a bit confused if I can do this or not. Once flashed to Orange France 2.3.4, if the OTA comes through what should I do? Accept? Decline? I'm very doubtful that Motocrap will update us to ICS, so can we update to ICS manually if I flash right now? Finally, if I do Brick, what can I do? I don't have insurance. Can I backup to a PC? I want something that no matter what happens I can restore to. Thanks for the answers ( if I get any )
Kartik

LG G2 Fastboot

Everything I found on this says volume + and power, which kicks me into download mode, not fastboot.
I've gone into adb and typed adb reboot bootloader, but that just restarts the phone and turns in on like normal.
I google the how to enter fastboot mode on LG G2 and can find plenty of post about being stuck in fastboot, but nothing on how to get into fastboot in the first place.
Found a tutorial here about setting up and using fastboot and thought I was set until I got to the part about "and using fastback", where it just says:
Make sure you have android debugging turned on in your phone (not really needed for fastboot but you do need for ADB), plug it into your computer and boot into fastboot mode...
I felt like watching "Much ado about nothing" when Denzel says; "The learned constable is too cunning to be understood"
Any direction is appreciated.

Hmm, I may have written that guide... Just checked and yeah should have been more clear I'll change that up. It should have read the USB debugging was needed for adb (not for fastboot) so when you can issue
adb reboot bootloader
But after that I did mention to check device specific forum for answers on how to get into fastboot/bootloader and being I've never held an lg g2 I took a quick look around.
Unfortunately the only way that I found that people said works every time is to wipe recovery to get into bootloader mode as the recovery you guys currently have disables something due to a patch getting custom recoveries to work
So yeah, I would advice to speak with someone knowledgeable about your specific device before you just wipe recovery
Out of curiosity, is there something specific you need to do with fastboot or are you just curious about your phone?
Sent from my Nexus 7 using XDA Premium 4 mobile app

demkantor said:
Out of curiosity, is there something specific you need to do with fastboot or are you just curious about your phone?
Click to expand...
Click to collapse
the current thing I've been trying to straighten out is that despite being rooted and installing TWRP, I can't install ROMS. I tried CM 11 and Hellfire so that I could put kitkat on, but gave the following:
Error executing updater binary zip.
One of the answers I found said that I had to go back to TWRP 2.3 (I'm using 2.6) and I believe that's where the whole bootloader thing came into play, because it was the way to 'downgrade' -
So then I found Philz touch 6 (as I understand it a mode of CM 11), but here he talked about fastboot and lokifying items. Here's the link:
http://forum.xda-developers.com/showthread.php?t=2554053
In the end it still comes back to the "can't load ROMs" issue. Just want a completely stripped down Kitkat that I can add the stuff I want without the bloatware.
Thanks in advance.(and the thanks button was hit on your reply)

For KitKat you should need a newer recovery with SELinux support which I believe is 2.6.x and newer for twrp, 2.3 I doubt would work if there even is one for your phone
But yes fastboot is often the best way to change recoveries but not the only way.
If there is a flashable.zip you could install new recovery from old
If your current ROM supports the flash image binary you can use a terminal emulator
You can use adb to install
Or even apps from the market
I would look for the latest recovery for your device, twrp, cwm, shouldn't matter so long as its new and then find what way works best changing for your phone.
The update-binary issue is often a sign that you need to change recoveries
Unfortunately without having your device I don't know if I can give you the best answers but feel free to ask
Best of luck!
Sent from my Nexus 4 using XDA Premium 4 mobile app

demkantor said:
Unfortunately without having your device I don't know if I can give you the best answers but feel free to ask
Best of luck!
Click to expand...
Click to collapse
Thanks again. I have adb and the script for loading TWRP 2.6.xx. I unrooted and rerooted the phone, because I wasn't sure how to replace the recovery... Now I think I realize that I could just find another recovery image and place it in the same file as the loki flash and that will flash it (At least that's what I understand at present).
If that's the case, then downloading the Philz touch 6 would work... but not wanting to brick it, I'm still asking and reading.

Hello Guys.
I am having a similar issue. I have a new ROM that will not run because of a faulty lg set up wizard that always force closes and I can not get passed it and a nandroid that for some reason is corrupted. So. This fastboot seems to be a dead end it looks like a quick learning curve of ADB is the only viable answer. I have installed all SDK Manager with ADB Tools and also the required Jarva JDK and LG drivers. The phone is turned on (at the beginning of the faulty setup wizard) In CMD my device is found when typing in 'adb devices' So. I am already to push a new ROM over to the phone.
Do either of you guys know the adb command?
Help would be appreciated.
Thanks

You can't actually flash a new ROM with adb, but you can either push it phone with adb and then flash in recovery. Or if your recovery has an option for adb sideload then use this.
Also setup wizard crashing is usually the fault of wrong gapps or not wiping before flashing a rom
Sent from my Nexus 4 using XDA Premium 4 mobile app

I found that the best way was to load flashify, that did the trick so I could start trying out ROMs... so no on to the next step - finding a 4.4.2 stripped down stock and the LG stuff I actually like.... thanks again.

demkantor said:
You can't actually flash a new ROM with adb, but you can either push it phone with adb and then flash in recovery. Or if your recovery has an option for adb sideload then use this.
Also setup wizard crashing is usually the fault of wrong gapps or not wiping before flashing a rom
Sent from my Nexus 4 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Thanks for the reply!
I know it's not possible to flash a ROM via ADB. I have everything set up, ADB etc, etc. My phone is turned on and adb is seeing it but I can not work out the command to push. Every time I try to push I just get a long list of ADB instructions (I think they are) but nothing gets pushed. I have read lots of instructions on how to make the command but I still must be doing something wrong.
Here are my parameters;-
adb push/C:\Users\dene\Desktop/cm-11-20140210-SNAPSHOT-M3-d802.zip/sdcard
Am I missing some spaces I am not aware of? Are all my slashes the right way round and in the right places? Is my 'sdcard' destination designation correct seeing as there is only internal storage on the G2?
Another problem I am having is that ADB has no problem seeing my sevice EXCEPT when I boot in to recovery (TWRP). When in recovery I lose coms between my device and pc. Hence I can no do TWRP ADB side load (I have tried). I have all the correct LG drivers loaded. Except MTP keeps failing to install? Any ideas?
Not to be mardy about it or hassle you but I am fairly house bound and live out in the country and really require my mobile phone. I have spent many hours trying to figure this out. Any help with the above would be much appreciated?
PS. I did a very thorough wipe, I always do. The gapps are built in to this ROM!
Thanks

dodge3003 said:
Thanks for the reply!
I know it's not possible to flash a ROM via ADB. I have everything set up, ADB etc, etc. My phone is turned on and adb is seeing it but I can not work out the command to push. Every time I try to push I just get a long list of ADB instructions (I think they are) but nothing gets pushed. I have read lots of instructions on how to make the command but I still must be doing something wrong.
Here are my parameters;-
adb push/C:\Users\dene\Desktop/cm-11-20140210-SNAPSHOT-M3-d802.zip/sdcard
Am I missing some spaces I am not aware of? Are all my slashes the right way round and in the right places? Is my 'sdcard' destination designation correct seeing as there is only internal storage on the G2?
Another problem I am having is that ADB has no problem seeing my sevice EXCEPT when I boot in to recovery (TWRP). When in recovery I lose coms between my device and pc. Hence I can no do TWRP ADB side load (I have tried). I have all the correct LG drivers loaded. Except MTP keeps failing to install? Any ideas?
Not to be mardy about it or hassle you but I am fairly house bound and live out in the country and really require my mobile phone. I have spent many hours trying to figure this out. Any help with the above would be much appreciated?
PS. I did a very thorough wipe, I always do. The gapps are built in to this ROM!
Thanks
Click to expand...
Click to collapse
I HAVE SOLVED THE ISSUE! Thanks for your assistance mate but in the end I just went back to stock using this amazing thread:-
http://forum.xda-developers.com/showthread.php?t=2432476
in conjunction with this amazing video;-
http://www.youtube.com/watch?v=IixQjo_hyz8
So! I am now un rooted and back to stock. Time to start the rooting ana ROMing all over again.lol
Thanks

Glad to here!
You need a space after push
But it usually easier not to enter the location of a file while pushing so cd to the directory first like
cd C:\Users.....
Then once there adb push /nameoffile /locationonphone
But if you don't want to cd, I see you have widows, depending on version you can just right click in the folder your file is located and choose open cmd here
Sent from my Nexus 7 using XDA Premium 4 mobile app

Need Help
As I thought I bought LG G2 D-802, but it was D-800 and I accidentally install the lollipop of D802 and now it's in bootlap.... I can only get into fastboot and whenever I try to flash .img of D-800 or D-802 it just stuck at "writing .img"
What to do to unbrick the phone and bring it back to live. I tired the adb and fastboot cmd method on windows 10 and windows 7 but no success. It's just stuck at writing .img file.

Root H830 running 20A and 20C [Nougat] AutoMagically (Custom Easy Recowvery Script)

I posted this as a reply originally. Then thought it probably should be a thread so it can help as many people as possible! Let's get the custom kernels and ROMs going for this beautiful device!
You will need to already have Android 20A (C should be fine as well) stock image installed, and the bootloader unlocked [Plenty of easy help via Google won't cover that here]
You can use the Recowvery Method on 20A (Nougat) (again this should be the same for 20C) with the H830. Below is the script I used with supersu and no-verity script included. Plug-in the device to your Windows machine. Install LG drivers, and remember to unlock screen and authorize the computer via the Device's screen so ADB commands can run (unnecessary tech note: you could open command prompt cd to where this is and use it's ADB to run adb devices (if you don't understand that no worries skip it)). After that just run the script and follow the menus. Answer yes when asked if you're sure you wish to continue, and done. I hope you find my work helpful .
I used this guy's script [Easy Recowvery ALL CREDITS TO THE AUTHOR I'M JUST SUPPLYING AN H830 SPECIFIC PACK WITH NEEDED FILES THAT I VERIFIED FULLY WORK. PLEASE GO RATE HIS THREAD AND CLICK THANKS IF THIS WORKS FOR YOU!]: http://forum.xda-developers.com/v20/development/h918-recowvery-unlock-v20-root-shell-t3490594
DON'T FORGET
This should work granted you have the drivers installed, and Windows has finished installing them, you tapped the prompt on your device screen to allow the adb connection, and you run script as administrator, and you restart the computer if you run adb commands yourself and aren't comfortable checking task manager to kill any and all running adb instances (could also issue the stop server command too), but if unsure of any or all of that last statement, restart
Of note answer yes when it says this isn't a V20 are you sure you wish to continue?. Also, as stated in notes I had to actually run it twice for it to stick for me (I'm sure I rushed the first time or something).
I took the time to create an H830 package of the script version with the files that worked for me. Out of respect I changed nothing aside from adding the needed files and throwing quick notes in the readme.md (bottom of file) file. (PLEASE read it, if you have issues read it you missed something). You will also still need to type yes when it states this is not a V20; Do you wish to continue? <Yes>.
. I used this package to root my H830 after the Nougat OTA killed my root access so
SHOULD WORK ON ANY H830 RUNNING STOCK 20A (should work with 20C) [NOUGAT] Read the following paragraph if you skip the rest
Read the readme.md file found in root of archive (see bottom of file).
Start it up hit like 5 for TWRP and supersu (or there's another menu option for just supersu or just TWRP whatever you desire).
Answer yes to the prompt to continue.
Now wait for the magic (again not mine this is the authors work)).
Once done you can download a reboot to recovery app or widget (or root checker) and verify that you're good to go.
If it doesn't take the first time you may need to run it again. DON'T FREAK OUT, RUN SCRIPT AGAIN IT CAN TAKE MULTIPLE RUNS.
Don't forget to install BusyBox (Stericson installer recommended and I use /su/bin personally (/su/xbin should also be fine) Since we're talking stock here generally I like to minimize any changes to /system if it can be helped personally; so I haven't tried running BusyBox from any /system mount) as this is a stock ROM.
Kernel Adiutor works and yes I recommend leaving thermald enabled as your thermal governor unless you flash a custom kernel (not included)
Manual Boot to Recovery:
Start With phone off (pinch battery button and re-insert battery if you can't otherwise shut it down or are lazy like me )
Hold both Power AND Volume Down at same time
1-2 seconds in to seeing LG Logo release and hold power button while continuing to hold volume down the entire time...
Release once you see white screen prompting yes or no to wipe user data (don't freak) ¹
use volume key to highlight yes
Hit Power key (think enter)
¹(If you have factory recovery this WILL format all user data and settings you've been warned. Only way to boot to stock recovery is to use app, widget, or terminal/adb command (reboot recovery). I don't know of any manual physical button methods to access stock recovery directly.).
You should now see TWRP Loading and can release any keys if you're holding any down still (once white wipe screen is seen you should release the keys)
Sweet, the file is small enough to be attached to this post directly, Enjoy! Also it's a 7-zip archive. It's available for every OS. For Android if you use ES File Explorer the first time you try to use a 7z file it'll offer to download plug-in, and you're good to read/write 7z archives (best compression almost always imho).

It doesn't seem to work for me, it reboots and the little android says No Command. Any suggestions?

well I ran the script ,Im afraid what was happening earlier is happening here to,when the script tries to flash Supersu it reboots to Firmware Update screen,Im fairly certain thats not right...am I correct? Gonna try to pull out (lol) before that screen loads like I did with the other method...

Ahhh I miss being able to root without a PC. I don't own one ?

Can anyone confirm this works fine? I won't have time for troubleshooting if it doesn't..

Jonathanpeyton said:
well I ran the script ,Im afraid what was happening earlier is happening here to,when the script tries to flash Supersu it reboots to Firmware Update screen,Im fairly certain thats not right...am I correct? Gonna try to pull out (lol) before that screen loads like I did with the other method...
Click to expand...
Click to collapse
Sounds like your hope would be if someone made a tot with root for 20A

shaneg79 said:
Sounds like your hope would be if someone made a tot with root for 20A
Click to expand...
Click to collapse
unfortunatley, I think that may be the only way Ill ever get my oddball device to accept TWRP....

WiiR0cKz said:
It doesn't seem to work for me, it reboots and the little android says No Command. Any suggestions?
Click to expand...
Click to collapse
same issue i turned off integrety check and ran it again it worked fine

Alpha_wolf said:
same issue i turned off integrety check and ran it again it worked fine
Click to expand...
Click to collapse
Where did you find integrety check
Sent from my LG-H830 using Tapatalk

Hi, thanks you for this post. I tried to use this script and I got an error saying that I am missing files in the "exploit" directory...please see the attached screenshot. Any ideas? Thanks.

famous145 said:
Where did you find integrety check
Sent from my LG-H830 using Tapatalk
Click to expand...
Click to collapse
hit 5 in the main screen it should be there

Can someone please help me unlock my bootloader now that I am running nougat! TIA fellow peeps!

Is this working for everyone / anyone? Most posts so far seem to have issues...

Alpha_wolf said:
hit 5 in the main screen it should be there
Click to expand...
Click to collapse
I did this but am still getting the no command issue

This method worked for me after about 5 failed attempts. The OP guide is not very clear, I might write my own and post it today.

aanonymoushuman said:
This method worked for me after about 5 failed attempts. The OP guide is not very clear, I might write my own and post it today.
Click to expand...
Click to collapse
Please!
When you say failed, did you get the no command issue as well,or something different?

Dumboguy03 said:
Please!
When you say failed, did you get the no command issue as well,or something different?
Click to expand...
Click to collapse
I did get the no command issue in recovery, the first time I did it, disabling integrity verification solved the problem when I did my next time, but I got some other issues before this solution worked.

My problem is, i am on Mac in parallels i can't list my phone in adb devices command. it shows as empty. Installed every possible app scenarios but still looks empty

Check out my guide on rooting Nougat, https://forum.xda-developers.com/lg-g5/how-to/guide-root-stock-n-using-jcadduonos-t3529093

Can confirm this does work. Took me 30 tries but it worked!

Stock ROMs Factory v6.1 , v8.3 , v8.4 , v8.5 , v8.7, V9.0, V9.2-patch : v21

CAUTION TO NOT LOOSE TWRP
I read two posts that say v21, now again on V8.5, put the stock recovery back instead of twrp. This is probably a side effect of a fresh stock /system and wipe of /data.
As a preventive step, when done flashing and wiping reboot to recovery FIRST, before booting the system It will allow recovery to handle removing the recovery-from-boot.p that flashes stock recovery.
I just patched the modified V7.4.2 up to the newly released 8.3 now 8.4. 8.5, 8.7,9.0 -V9.2 Patch
New update has been made from V17 to V21 of the non prime version of R1-HD, Non prime is behind on security patch (2017-05-05)
Copied ROM from phone and made twrp install ROM from it.
* No preloader change (official updates change the preloader to block your ability to use sp flash tools for rom flashing)
* No lk.bin change __ this part is what allows you to choose boot options(boot menu when power and volume pressed together)
* No "FOTA" app Fota has now been left in to make it easier to get next update, if that ever happens.
* No opera browser
* No adds (removed in the modified 7.4.2)
* Custom boot logo (only done on v8.3, there was no interest in this so abandoned)
--Newer versions of rom left stock, Leaving mods up to user.
** while it is not necessary to do a wipe with this ROM, I still recommend it.
**Thanks:
** @vampirefo needed his patched v7.4.2 in order to apply this new 8.3 patch and again for 8.4
** @ColtonDRG OR @jasonmerc I do not remember which one made it: For the image used in the custom logo
and the modified zip is here .
Roms are rootable with SuperSU, flashed in twrp after install. Must be done in systemless mode. In order to patch system veridy in boot.img
Logo update did not work on original rom changing link to updated version
BLU rolled v8.3 back to v7.4.2 because of app compatability issues. V8.4 is there fixed release. Both 8.3 and 8.4 are modified prime roms with ads stripped
V21 is the non prime update.
Unmodified V6.1
==>NON-ROOTED-logo-not-replaced-modified-V8.3
==>Fixed Logo modified NON_ROOTED V8.3
==>>modified V8.4
==>>modified V8.5
==>>Full with Ads V8.7
==>>Full with Ads V9.0
==>>Patch For V9.2 must be flashed on top of fresh V9.0
****Run debloat ==>script to remove ads if you need/ want to, or remove from zip before flashing ****
alt. manual example: before reboot, while still in twrp. Select mount and put checkmark next to system. Then run these two commands in adb terminal
Code:
adb shell rm /system/priv-app/com.amazon.*/com.amazon.*.apk
adb shell rm /system/app/Adups*/*.apk
==>>Modified V21
** stand alone logo installs

I flashed this but I didn't get the custom boot logo.

mendelgordon said:
I flashed this but I didn't get the custom boot logo.
Click to expand...
Click to collapse
I had that happen to my second phone too.
I don't have an explanation yet.
I even made a separate update.zip , that one didn't make the logo change either. I did eventually change it with sp flash tool.
I tried with both recoveries.
and multiple /dev location formats. and for whatever reason my one phone did not accept the logo change from recovery.
And the other test phone it worked.

mendelgordon said:
I flashed this but I didn't get the custom boot logo.
Click to expand...
Click to collapse
Neither did I but it all seems to be working fine

Been using this for about a day now, likewise no custom boot logo, but that's fine. Otherwise, it's been running super well. A lot better than the previous mostly stock version did for me with the bloatware APKs removed after the install. A lot of the general idiosyncrasies of the previous version of the stock rom seem to have gone away for me. It seemed to have weird storage management issues, errors moving to SD, broken symlinks that prevent apps from moving or being reinstalled, and a lot of other little non-storage issues, but so far, none off that here.
Long story short, good work! I hope we eventually see proper 7.x roms through some of the efforts going on, but in the meanwhile, your work here has made life a little bit better on 6.

It seems that I was able to get the logo.bin to update when I applied the original update patch, but not when I used the same line in the rom install.
It is no big deal that it did not work, I was just trying to make it look different at boot time.
edit:
I think i found the problem with the logo not updating.
i used the update-binary from the official patch update. (the one that allowed the logo to change the first time)
and it changes . so since the ROM seems to install the way it is , only the logo didn't flash I put it in a separate update.zip if anyone is interested in it.
EDIT 2:
clarification.
It was not so much the binary allowing the logo to change but the format of the partition location I had been using that needed that binary.
Further test had shown me that I could have used the binary I was using but just change the partition naming line
Code:
package_extract_file("logo.bin", "/dev/block/mmcblk0p9")
the above code works with the same update-binary as rom install
But I was using
Code:
package_extract_file("logo.bin", "/dev/block/platform/mtk-msdc.0/11230000.msdc0/by-name/logo")
Taken straight from the official patch, and thats why it needed the update-binary also.
I dont know what is different in the binary other than , major size difference.
The powered by me logo was just a test file to see changes in the logo.
**logo-update is same as composite but with alt updater-binary
**composite-logo screenshot is in op
**stock logo will return to original BLU logo

mrmazak said:
It seems that I was able to get the logo.bin to update when I applied the original update patch, but not when I used the same line in the rom install.
It is no big deal that it did not work, I was just trying to make it look different at boot time.
edit:
I think i found the problem with the logo not updating.
i used the update-binary from the official patch update. (the one that allowed the logo to change the first time)
and it changes . so since the ROM seems to install the way it is , only the logo didn't flash I put it in a separate update.zip if anyone is interested in it.
EDIT 2:
clarification.
It was not so much the binary allowing the logo to change but the format of the partition location I had been using that needed that binary.
Further test had shown me that I could have used the binary I was using but just change the partition naming line
Code:
package_extract_file("logo.bin", "/dev/block/mmcblk0p9")
the above code works with the same update-binary as rom install
But I was using
Code:
package_extract_file("logo.bin", "/dev/block/platform/mtk-msdc.0/11230000.msdc0/by-name/logo")
Taken straight from the official patch, and thats why it needed the update-binary also.
I dont know what is different in the binary other than , major size difference.
The powered by me logo was just a test file to see changes in the logo.
Click to expand...
Click to collapse
Hahaha the scribbled "ME" is hilarious. Your work is awesome, I don't think anyone using this rom will have an issue with the boot image but thanks for being so helpful and explaining.
P. S. Do you have any plans with the Nougat update?

Serenitybs said:
Hahaha the scribbled "ME" is hilarious. Your work is awesome, I don't think anyone using this rom will have an issue with the boot image but thanks for being so helpful and explaining.
P. S. Do you have any plans with the Nougat update?
Click to expand...
Click to collapse
Nougat is going to take a full build from scratch. We don't have 100% identical hardware with any other nougat device to my knowledge. We might have the same MTK chipset, but there are several other differences. All we really need is an official device overlay and the vendor files released by BLU themselves. We can then apply those to the latest Lineage or AOSP (I prefer AOSP myself) and build. Then the only problem we'll run into is anything that has changed in 7.x that isn't compatible with our kernel we use in 6.0. It'd be a slight chance our current kernel would work without some patches on 7.x We can't even get our official sources for anything else, so I'm almost certain we'll not find any patches to for the kernel to work properly with Nougat, at least not from BLU or any similar devices. None The less Nougat has been well thought of, and we have been trying to debug issues with a broken Port. But a broken port from a different device is just that - Broken. We need a team of knowledgeable devs to build Nougat + Kernel from scratch and then we'll have it working. I can't do it alone with the old computer I have, the R1HD would be long forgot of by the time I got Android Compiled haha.
Mr. Mazak I flashed your rom it went smooth, I was hoping the newest update was for 6.0.1. But I didn't lose any functionality, hopefully on my Cricket Service this update has patched some things to the radio device that will retain connection more steadily. I experienced a lot of coming and going with the 7.4.2 rom. None The Less you did a good job with this update Mr. My suggestion is find the same MTK chipset with a fully working 7.x rom and just port the /System but keep all our libs and inits from this release just for a test starter. And don't replace the camera app thats in AOSP 7.x. )

linuxsociety said:
Nougat is going to take a full build from scratch. We don't have 100% identical hardware with any other nougat device to my knowledge. We might have the same MTK chipset, but there are several other differences. All we really need is an official device overlay and the vendor files released by BLU themselves. We can then apply those to the latest Lineage or AOSP (I prefer AOSP myself) and build. Then the only problem we'll run into is anything that has changed in 7.x that isn't compatible with our kernel we use in 6.0. It'd be a slight chance our current kernel would work without some patches on 7.x We can't even get our official sources for anything else, so I'm almost certain we'll not find any patches to for the kernel to work properly with Nougat, at least not from BLU or any similar devices. None The less Nougat has been well thought of, and we have been trying to debug issues with a broken Port. But a broken port from a different device is just that - Broken. We need a team of knowledgeable devs to build Nougat + Kernel from scratch and then we'll have it working. I can't do it alone with the old computer I have, the R1HD would be long forgot of by the time I got Android Compiled haha.
Mr. Mazak I flashed your rom it went smooth, I was hoping the newest update was for 6.0.1. But I didn't lose any functionality, hopefully on my Cricket Service this update has patched some things to the radio device that will retain connection more steadily. I experienced a lot of coming and going with the 7.4.2 rom. None The Less you did a good job with this update Mr. My suggestion is find the same MTK chipset with a fully working 7.x rom and just port the /System but keep all our libs and inits from this release just for a test starter. And don't replace the camera app thats in AOSP 7.x. )
Click to expand...
Click to collapse
Somebody already tried this out

linuxsociety said:
Nougat is going to take a full build from scratch. We don't have 100% identical hardware with any other nougat device to my knowledge. We might have the same MTK chipset, but there are several other differences. All we really need is an official device overlay and the vendor files released by BLU themselves. We can then apply those to the latest Lineage or AOSP (I prefer AOSP myself) and build. Then the only problem we'll run into is anything that has changed in 7.x that isn't compatible with our kernel we use in 6.0. It'd be a slight chance our current kernel would work without some patches on 7.x We can't even get our official sources for anything else, so I'm almost certain we'll not find any patches to for the kernel to work properly with Nougat, at least not from BLU or any similar devices. None The less Nougat has been well thought of, and we have been trying to debug issues with a broken Port. But a broken port from a different device is just that - Broken. We need a team of knowledgeable devs to build Nougat + Kernel from scratch and then we'll have it working. I can't do it alone with the old computer I have, the R1HD would be long forgot of by the time I got Android Compiled haha.
Mr. Mazak I flashed your rom it went smooth, I was hoping the newest update was for 6.0.1. But I didn't lose any functionality, hopefully on my Cricket Service this update has patched some things to the radio device that will retain connection more steadily. I experienced a lot of coming and going with the 7.4.2 rom. None The Less you did a good job with this update Mr. My suggestion is find the same MTK chipset with a fully working 7.x rom and just port the /System but keep all our libs and inits from this release just for a test starter. And don't replace the camera app thats in AOSP 7.x. )
Click to expand...
Click to collapse
It was just wishful thinking. I have no idea how all of this is done. All I know is @mrmazak has helped me to fall in love with my phone again with this V8.3. The 7.4.2 did seem a bit buggy for my phone but this update works beautifully and I didn't even root it. If this remains true I will be happy with this phone for awhile even on 6.0

Really confused right now.
I was browsing through the settings menus. And found in the Settings-security- menu a toggle labeled "quick boot" ( not to be confused with "fastboot") . I enabled it then rebooted to see if it booted quicker. Didn't seem to make much if any difference. So I went back to turn it back off. And it wasn't there. I checked in my other phone , it wasn't there on that one either.
Did any body see this menu item, and if so where is is it?
Edit 1:
Few more power off , power on cycles to compare times. With other phone and defiantly seems to have turned on some faster boot option.
This phone goes from off to on in 5-6 seconds other phone takes about 20.
Edit 2:
OK , I panicked for a minute.
Couldn't find the setting and thought that it was another way to block sp flash tool by preventing you from ever being fully powered off.
But the setting was in accessibility not security.

Mrmazak, first of all, thanks for the ROM, installed it yesterday. But I have a problem with SELinuxModeChanger app. First, I'm getting a security warning when installing it, then - when running it. And another message, with this app running - "can't obtain root", although SuperSU shows its status with green #, like every other app it gives root privileges to. On my other Prime phone, running 6.1 out of the box stock ROM, FM radio works just fine with SELinuxModeChanger app behaving flawlessly (no security warnings whatsoever). Any ideas?

detroitredwings said:
Mrmazak, first of all, thanks for the ROM, installed it yesterday. But I have a problem with SELinuxModeChanger app. First, I'm getting a security warning when installing it, then - when running it. And another message, with this app running - "can't obtain root", although SuperSU shows its status with green #, like every other app it gives root privileges to. On my other Prime phone, running 6.1 out of the box stock ROM, FM radio works just fine with SELinuxModeChanger app behaving flawlessly (no security warnings whatsoever). Any ideas?
Click to expand...
Click to collapse
The mode changer app is technically a security issue. I did have that warning a few times when using mode changer app from the XDA thread of the developer, then when I used the app downloaded from f-droid it worked with systemless root and didn't give the security warning.

The app downloaded from f-droid worked for me as well, many thanks!

Big thanks for getting this out, updated from previous debloated, rooted version to this modified 8.3 stock rom, rooted with SU v2.79 SR3, all is good - only App that won't show up nor install, even tried the ones off APK Mirror site - is my Dunkin Donuts App, LOL. Play Store now said it's not compatible and the APK started to install then failed - any ideas or suggestions on what to do ??
Otherwise, it's all good - I will survive without DD App, just run that from another device when I need my caffeine fix.

Letitride said:
Big thanks for getting this out, updated from previous debloated, rooted version to this modified 8.3 stock rom, rooted with SU v2.79 SR3, all is good - only App that won't show up nor install, even tried the ones off APK Mirror site - is my Dunkin Donuts App, LOL. Play Store now said it's not compatible and the APK started to install then failed - any ideas or suggestions on what to do ??
Otherwise, it's all good - I will survive without DD App, just run that from another device when I need my caffeine fix.
Click to expand...
Click to collapse
I also had an app that previously work, say is not compatible now.
Maybe has to do with apps that have links to pay accounts. And that has something to do with trustzone. (Tee1 & tee2)
Those sections I left out of the update. I will add it back in and test. Update when I do. It is also possible this problem is why Blu rolled back there update.
**EDIT**
well that didn't go well at all.
I flashed the new trustzone.bin files from the official update. Now phone no longer turns on and no longer connects to flash tool
**EDIT 2**
After much persistence and many failed attempts to get phone recognized in pc again. Finnaly got to a point that phone was cycling between "preloader" driver and "usb serial device", and with careful timing was able to start sp flash tool at just right time and the flashing back to original trustzone files seems to have recovered phone.
for the record i am not sure what steps made it work. But I was shifting back and forth between leaving phone sit on charge, then on charge with rubber band wrapped around power button, then not plugged in , and not plugged in with rubber band on power button.

Okay... persistence is key in customization, i guess! I am getting somewhere here!
mrmazak said:
The first link is needed to get phone unlocked so you can install twrp.
Click to expand...
Click to collapse
Finally got thru the steps in order (1-2-3-4) then Step (5) and sub-step 1. I can also boot to TWRP.
Now this brings me to this thread, 8.3 Stock ROM. The thread assumes one knows how to install it and I suspect this could be as easy as uploading it to a folder in the phone then booting to TWRP and INSTALLING the ZIP file? Could someone clarify the steps to install this 8.3 ROM?
Thanks!

OldSkewler said:
Okay... persistence is key in customization, i guess! I am getting somewhere here!
Finally got thru the steps in order (1-2-3-4) then Step (5) and sub-step 1. I can also boot to TWRP.
Now this brings me to this thread, 8.3 Stock ROM. The thread assumes one knows how to install it and I suspect this could be as easy as uploading it to a folder in the phone then booting to TWRP and INSTALLING the ZIP file? Could someone clarify the steps to install this 8.3 ROM?
Thanks!
Click to expand...
Click to collapse
Yes. You are correct
Either put the zip file on external sd card , put card into phone boot into recovery mode and install , or put file directly onto phone .
Many ways to do that.
Easiest is to copy to phone while phone is connected to PC.
Cam also download file from internet with your phone.
Bottom line is get zip file to the phone boot to recovery and install

Anyone else having wifi issues after upgrading? While watching videos it seems the internet cuts out. The phone says it's still connected but I have to turn wifi off and back on for anything to work. Could be my router also but it didn't seem to be doing this until I installed 8.3

mrmazak said:
Yes. You are correct
Either put the zip file on external sd card , put card into phone boot into recovery mode and install , or put file directly onto phone .
Easiest is to copy to phone while phone is connected to PC.
Bottom line is get zip file to the phone boot to recovery and install
Click to expand...
Click to collapse
Right on man! I am officially running 8.3 ROM with April 5th 2017 Security Patch Level! Geez.. it was not easy but I got this working!
MrMazak, I followed all your instructions on both links, so could you tell me what exactly I have on my phone? Is it rooted? Bootloader Unlocked? The phone seems to be working fine but I don't know what level of access I have. Honestly I don't even know exactly what the differences between all these terms are.
Also, do I have or not SU? One of the steps under the .bat I believe install it. How do I access it?
Thanks again!
---------- Post added at 10:19 PM ---------- Previous post was at 10:18 PM ----------
Weasel0 said:
Anyone else having wifi issues after upgrading? While watching videos it seems the internet cuts out. The phone says it's still connected but I have to turn wifi off and back on for anything to work. Could be my router also but it didn't seem to be doing this until I installed 8.3
Click to expand...
Click to collapse
My install is pretty fresh, couple of hours, but as far as I can tell all is working fine with Wifi, As a matter of fact this is a new device only connected with Wifi and no SIM Card.... internet works fine.