Related
Ok, so after using clockwork rom manager on my nook color and seeing how convenient it was, I thought, "hey maybe this would be good on my milestone." WRONG. I flashed the clockwork recovery (they even had an option for milestone) and when I rebooted into recovery from the software (either in rom manager or the reboot power option) it just rebooted straight into android. When I held the power and camera keys, it just took me to bootloader.
Under rom manager, there was also an option to flash the RA recovery, but that didn't seem to help (exact same behavior as clockwork recovery).
I'm currently running the CM7 mod and prior to this fiasco, I was using RA 1.7 (pretty sure). edit: RA 1.7 was my girlfriend's HTCmagic, I just remembered that I would have had some version of openrecovery on this phone.
So, I guess my question is, what are my next steps here? I'd really like to stop flying without a recovery. My only shred of an idea was to flash a stock image from rsdlite and set my milestone all the way back to stock and then reroot and re everything, but if someone has a better idea, I'd be very open to that as my plan seems like a big hassle.
A) not really the place for this post but anywa
B) you should beable to just flash the Vulnerable recovery http://android.doshaska.net/rootable then you can install a recovery from this forum thats for our phone!
Apologies, I didn't mean to step on any toes. Could a mod please recategorize this thread.
I will check out that link and report back if I need further assistance. Although, if that's a surefire way to fix my problem, I should be fine. Thank you for your fast (and succinctly informative) reply.
Tyfighter said:
Apologies, I didn't mean to step on any toes. Could a mod please recategorize this thread.
I will check out that link and report back if I need further assistance. Although, if that's a surefire way to fix my problem, I should be fine. Thank you for your fast (and succinctly informative) reply.
Click to expand...
Click to collapse
Quite alright if you have any more problems feel free to just PM me
Check this thread:
http://forum.xda-developers.com/showthread.php?t=1139120
Well, the good news is, that I flashed the vulnerable recovery and I'm able to boot into recovery. The bad news is, it only lasts for a few seconds. I see the standard recovery icon and then a bar fills up and then my phone reboots into android. From what you said, I take it that there's another step in here where I take another file from the forums and then install that as well. Is that just through RSD lite then?
Tyfighter said:
Well, the good news is, that I flashed the vulnerable recovery and I'm able to boot into recovery. The bad news is, it only lasts for a few seconds. I see the standard recovery icon and then a bar fills up and then my phone reboots into android. From what you said, I take it that there's another step in here where I take another file from the forums and then install that as well. Is that just through RSD lite then?
Click to expand...
Click to collapse
Ok so you need to take an open recovery for example http://forum.xda-developers.com/showthread.php?t=1091787 and extract it to the root of your sdcard so you have a update.zip file and openrecovery folder.
Then boot into recovery and press the volume up and camera button and a menu should come up.
Then select the 'flash update.zip' and this should 'boot' you into the custom recovery, sadly because of the looked bootloader we must do this everytime we wish to boot into recovery
Okay, I have that file, or one similar, from when I originally had started using custom roms (and updated/changed them etc.).
The problem is that before, when I'd go into recovery, it would have the icon of the phone out of the box with the exclamation mark or whatever, and it would stay there indefinitely.
Now, it only stays for a few seconds before rebooting into android. A little bar appears, fills up, then reboot. Doing the volume up + camera combo only serves to expedite this process (i.e. reboots as soon as I press it).
zacthespack said:
Ok so you need to take an open recovery for example http://forum.xda-developers.com/showthread.php?t=1091787 and extract it to the root of your sdcard so you have a update.zip file and openrecovery folder.
Then boot into recovery and press the volume up and camera button and a menu should come up.
Then select the 'flash update.zip' and this should 'boot' you into the custom recovery, sadly because of the looked bootloader we must do this everytime we wish to boot into recovery
Click to expand...
Click to collapse
what your doing (power + camera) is meant to put you into the bootloader mode... to get into recovery, hold 'x' on the physical keyboard and then hold the power button. This will get you into recovery. Hope this helps.
~D
are you sure that you did in fact flash the vulnerable bootloader, and not a newer, non-vulnerable one? sounds like that.. exploit fails, system reboots. also, if you are running an original rom right now, it does check the bootloader every reboot and flashes the non-vulnerable one!
Tyfighter said:
Okay, I have that file, or one similar, from when I originally had started using custom roms (and updated/changed them etc.).
The problem is that before, when I'd go into recovery, it would have the icon of the phone out of the box with the exclamation mark or whatever, and it would stay there indefinitely.
Now, it only stays for a few seconds before rebooting into android. A little bar appears, fills up, then reboot. Doing the volume up + camera combo only serves to expedite this process (i.e. reboots as soon as I press it).
Click to expand...
Click to collapse
I'm a bit confused with how you're getting into Recovery mode, but the way to enter recovery is to hold Power + X, then Camera + Vol Up when you see the Motorola Logo.
I'm getting into recovery the same way I always have Power+camera then volumeup+camera. Power+DpadUp is how I've been getting into bootloader. Power+X actually yields nothing, just a regular boot.
Unless the file hosted on the site that was linked earlier in the thread is a newer, nonvulnerable recovery then, yes, I'm sure I flashed vulnerable recovery. I'm going to attempt to flash again. Just to see if maybe that's the issue.
I'm pretty sure I'm seeing it at least attempt to enter recovery, which is a step up from before (before being that it just went to bootloader). Because I'm seeing the image that displays in the recovery menu, but then it brings up a progress bar (which I never saw before) and when that fills up (in about 2.5 seconds), that's it. Reboot.
Thanks everyone, for all the help though.
EDIT: Despite RSD lite saying that the process as a success, the reflash did nothing.
Tyfighter said:
I'm getting into recovery the same way I always have Power+camera then volumeup+camera. Power+DpadUp is how I've been getting into bootloader. Power+X actually yields nothing, just a regular boot.
Unless the file hosted on the site that was linked earlier in the thread is a newer, nonvulnerable recovery then, yes, I'm sure I flashed vulnerable recovery. I'm going to attempt to flash again. Just to see if maybe that's the issue.
I'm pretty sure I'm seeing it at least attempt to enter recovery, which is a step up from before (before being that it just went to bootloader). Because I'm seeing the image that displays in the recovery menu, but then it brings up a progress bar (which I never saw before) and when that fills up (in about 2.5 seconds), that's it. Reboot.
Thanks everyone, for all the help though.
Click to expand...
Click to collapse
Where did you get the VR sbf? android.doshaska.net/rootable ?
Yep, that's the one.
EDIT: Finally got up the guts to load the official Telus sbf into RSD lite and pull the trigger. It seems like this is probably beyond salvage now. Once again, many thanks to everyone, and if all goes well, I hope to only be in the ranks of the unrooted/unmodded for a few minutes.
EDIT the second: Okay, so flash to stock went perfectly. Everything works, including recovery, but not openrecovery. I can get to the menu to flash the .zip, but it fails the esignature check. Which I'm assuming points to Vulnerable recovery not flashing correctly or perhaps my file is corrupt, or maybe something more exotic and exciting. I flashed SHOLS_U2_03.11.0 if that's relevant.
For those interested, everything is up and functional again.
I had to first flash back to stock, then flash the vulnerable recovery located at http://modmymobile.com/forums/downloads.php?do=file&id=28089 , then the standard, boot to recovery, blah blah blah, install a new rom.
Let this be a lesson to the rest of you; Clockwork Rom Manager does not, I repeat, does NOT seem to work on our milestones. Which is a real shame...
I realize this is a double post, but I'm just so darned jubilant to be able to update my rom again.
Q&A for [RECOVERY] TWP 2.7.1.0 for One Mini 2
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [RECOVERY] TWP 2.7.1.0 for One Mini 2. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
new twrp's won't work
Hi there,
I just tried to root my htc mini 2 with and it says that it is tampered now and I can't reboot my recovery. So I tried the newest twrp and some in between because I've read in this forum that somebody had the same problem and he just got the newest twrp but that didn't work for me at all.
Is there any way to undo the whole thing by replacing the twrp with the original one or do I have to wait till there is gonna be a root for the htc mini 2?
When I try to recover everything it says that this build is for development purpose only...
Does somebody have an idea?
I would appreciate it a lot if somebody has an idea.
Hornochse7958 said:
Hi there,
I just tried to root my htc mini 2 with and it says that it is tampered now and I can't reboot my recovery. So I tried the newest twrp and some in between because I've read in this forum that somebody had the same problem and he just got the newest twrp but that didn't work for me at all.
Is there any way to undo the whole thing by replacing the twrp with the original one or do I have to wait till there is gonna be a root for the htc mini 2?
When I try to recover everything it says that this build is for development purpose only...
Does somebody have an idea?
I would appreciate it a lot if somebody has an idea.
Click to expand...
Click to collapse
When the bootloader says "tempered" means that it was unlocked. when you see " this build is for development purpose only" its referring to TWRP because you now using a custom recovery. Not sure the nature of your problem but to undo, simply boot into boot loader and flash original recovery.img you can find in the forum.
I can't you open TWRP?
kativiti said:
When the bootloader says "tempered" means that it was unlocked. when you see " this build is for development purpose only" its referring to TWRP because you now using a custom recovery. Not sure the nature of your problem but to undo, simply boot into boot loader and flash original recovery.img you can find in the forum.
I can't you open TWRP?
Click to expand...
Click to collapse
Thank you for the quick respond and I wanted to try and undo everything but no my problem is that my phone completely froze in the twrp screen. I can't do anything, I can't unlock it nor shut down my phone or start the bootloader... that kind of sucks. Any suggestions now? Is it possible to open the htc one mini 2 and take out the battery? or do I have to wait till it runs out by it self and than start it again?
Hornochse7958 said:
Thank you for the quick respond and I wanted to try and undo everything but no my problem is that my phone completely froze in the twrp screen. I can't do anything, I can't unlock it nor shut down my phone or start the bootloader... that kind of sucks. Any suggestions now? Is it possible to open the htc one mini 2 and take out the battery? or do I have to wait till it runs out by it self and than start it again?
Click to expand...
Click to collapse
Read this tread. Someone had the same problem
http://forum.xda-developers.com/one-mini-2/help/rooting-htc-one-mini-2-t2880936
Unresponsive after boot up from dead battery
THanks to U-ra I get the enjoy my fav DSP Viper!!!
Cheers Man,
I have a small niggling problem that I can't work out, My battery tends to die alot, once I place the phone on charge after a flat battery, the phone auto boots to Twp, I am really cool with that but the annoying thing is buttons and screen are unresponsive? I can't do a thing, just have the Twp menu. The power of button does turn the screen off/on but thats its. Tried doing factory resets, reboots holding down power, vol buttons. Just nothing.
only way around it is to use adb and reboot command.
Is anyone else experiencing this problem.
http://forum.xda-developers.com/one...recovery-twp-2-7-1-0-one-mini-2-t2801370/page 4 here's the answer, so far
@u-ra is there any clue about getting official twrp support? (I was thinking about that problem of the self-booting recovery when phone is off and plugged in)
gibihr said:
@u-ra is there any clue about getting official twrp support? (I was thinking about that problem of the self-booting recovery when phone is off and plugged in)
Click to expand...
Click to collapse
I'll try to get to it this weekend.
HELP TWRP stuck at swipe to unlock
Hello all,
for unknown reason the phone restarded and now is stuck at swipe to unlock but it is not working. I try to hold power+volume down, but no way to turn it off. What can I do?
Thanks in advance
PS: well, it restarted... I don't know what happend but now it's ok
sorry for sounding like a newb
i have the verizon htc one remix, which i believe is the same as the one mini 2 . will this work on it?
akubenz said:
i have the verizon htc one remix, which i believe is the same as the one mini 2 . will this work on it?
Click to expand...
Click to collapse
you can try but i think someone here couldn't unlock bootloader trough HTC Dev.
Help: Stock rom updated between boots, TWRP non responsive, fastboot doesnt recognise
Hello to anyone that can help or in a similar situation,
Have brand new HTC one mini 2, rooted. Am trying to install cyanogenmod and followed the instructions on their page. All went well and was ready to flash the rom from TWRP. Decided to do a backup to SD first and then apply super user. Forced to reboot and accidentally let it boot to android (stock rom). Didnt notice the last time i had it booted wifi downloaded a system update which was automatically applied next time i booted into the stock rom after backup and Superuser in TWRP. Rebooted to recovery (TWRP) as soon as i could, but TWRP is no longer responding to touch. I realise i have probably updated the phone to a point where TWRP is no longer working, and i have to use something else to flash my rom. Am trying to flash an updated TWRP or Clockworkmod recovery, but fastboot/adb no longer recognise the device when booted into the stock rom, and when i boot into TWRP (non-responsive) it also doesnt recognise the device attached, even if i catch it before the screen goes black from inactivity. Any suggestions greatly appreciated....
snorglamp said:
Hello to anyone that can help or in a similar situation,
Have brand new HTC one mini 2, rooted. Am trying to install cyanogenmod and followed the instructions on their page. All went well and was ready to flash the rom from TWRP. Decided to do a backup to SD first and then apply super user. Forced to reboot and accidentally let it boot to android (stock rom). Didnt notice the last time i had it booted wifi downloaded a system update which was automatically applied next time i booted into the stock rom after backup and Superuser in TWRP. Rebooted to recovery (TWRP) as soon as i could, but TWRP is no longer responding to touch. I realise i have probably updated the phone to a point where TWRP is no longer working, and i have to use something else to flash my rom. Am trying to flash an updated TWRP or Clockworkmod recovery, but fastboot/adb no longer recognise the device when booted into the stock rom, and when i boot into TWRP (non-responsive) it also doesnt recognise the device attached, even if i catch it before the screen goes black from inactivity. Any suggestions greatly appreciated....
Click to expand...
Click to collapse
A kind member replied to me in another post indicating that fastboot commands only work in the bootloader, and that adb commands only work in TWRP which is why I am having problems re-flashing TWRP (requiring the "fastboot flash recovery TWRP.img" command). However I thought TWRP replaced the bootloader, so I seem to be locked out of re-flashing TWRP because i have TWRP. This seems not to make a lot of sense, can anyone else confirm or otherwise explain what I have misunderstood about that? As stated neither adb nor fastboot recognises the device is attached to the computer any more, so commands are not executing...
snorglamp said:
Hello to anyone that can help or in a similar situation,
Have brand new HTC one mini 2, rooted. Am trying to install cyanogenmod and followed the instructions on their page. All went well and was ready to flash the rom from TWRP. Decided to do a backup to SD first and then apply super user. Forced to reboot and accidentally let it boot to android (stock rom). Didnt notice the last time i had it booted wifi downloaded a system update which was automatically applied next time i booted into the stock rom after backup and Superuser in TWRP. Rebooted to recovery (TWRP) as soon as i could, but TWRP is no longer responding to touch. I realise i have probably updated the phone to a point where TWRP is no longer working, and i have to use something else to flash my rom. Am trying to flash an updated TWRP or Clockworkmod recovery, but fastboot/adb no longer recognise the device when booted into the stock rom, and when i boot into TWRP (non-responsive) it also doesnt recognise the device attached, even if i catch it before the screen goes black from inactivity. Any suggestions greatly appreciated....
Click to expand...
Click to collapse
I think I have found the solution for myself: I went back into the stock rom and did a factory reset (from within android booted up as normal), which after completion rebooted me into TWRP which now works fine (is responding to touch again, and i can flash the Cyanogen image now). Hopefully this helps someone else in this situation one day, or maybe I am the only idiot that needed to ask hehe. I should clarify that after flashing TWRP I lost access to the fastboot screen and could not push anything over ADB or fastboot commands from windows (plugged in via USB). Holding down volume down and power booted directly into TWRP, and i had no way to get to fastboot screen. After doing factory resent from within the Android OS, holding volume down and power booted me to the fastboot screen, and only when I selected "Recovery" did it take me to TWRP, and I was again able to run fastboot and ADB commands from PC. Weird (or maybe not if you know more than me), but there it is...
snorglamp said:
A kind member replied to me in another post indicating that fastboot commands only work in the bootloader, and that adb commands only work in TWRP which is why I am having problems re-flashing TWRP (requiring the "fastboot flash recovery TWRP.img" command). However I thought TWRP replaced the bootloader, so I seem to be locked out of re-flashing TWRP because i have TWRP. This seems not to make a lot of sense, can anyone else confirm or otherwise explain what I have misunderstood about that? As stated neither adb nor fastboot recognises the device is attached to the computer any more, so commands are not executing...
Click to expand...
Click to collapse
Sorry, but it seems to me that you don't know the difference between bootloader and recovery. I apologize if you do. If not, search in CM wikis or ask here for explanations.
corbeau56 said:
Sorry, but it seems to me that you don't know the difference between bootloader and recovery. I apologize if you do. If not, search in CM wikis or ask here for explanations.
Click to expand...
Click to collapse
I do indeed know the difference between the bootloader and recovery, its just that the bootloader (Hboot) was not longer accessible in my situation and TWRP (the recovery) was imposing itself when you would normally expect to find the bootloader (i.e. my bootloader was for all intents and purposes replaced by my recovery, while I am sure this is not true in fact, it was in effect). As I say, doing a factory reset from within the OS restored the bootloader (HBoot) and I was able to continue modding. I am today extremely happy with my fully secured cyanogenmodded HTC One Mini 2 via TWRP recovery method. I hope that is somewhat clearer.
Can you enter bootliader now? I got stuck in a bootloop once and couldn't enter bootloader because I continued pressing power and Volume down like I did on my One S. For Mini 2, we have to hold the Volume UP and Power buttons until HBOOT appears, then release the buttons.
corbeau56 said:
Can you enter bootliader now? I got stuck in a bootloop once and couldn't enter bootloader because I continued pressing power and Volume down like I did on my One S. For Mini 2, we have to hold the Volume UP and Power buttons until HBOOT appears, then release the buttons.
Click to expand...
Click to collapse
That may well have been an alternative solution to my problem, however it was fixed by the factory reset and volume down and power then took me to HBoot (this would appear to contradict what you have said above, but maybe volume down and power does different things depending on how what you have done to the phone, not sure), so I cannot confirm whether or not that also would have worked for me. Good suggestion though, especially if you are not in a position to do a factory reset. and it would certainly be easier if it worked...I am convinced my problem was the result of a conflict between the TWRP version i installed (downloaded from here) and the android update that occurred between boots.
I am indeed able to get into bootloader/hboot and successfully flashed cyanogenmod from TWRP. I can confirm post flashing TWRP and Cyanogenmod, holding volume down and power takes me to HBoot (and then the option to go to fastboot or recovery).
Holding power up and power just loads cyanogenmod for me now as if I had just pressed power.
I thought I should confirm whether or not holding volume up vs volume down with power results in bootloader vs recovery loading. For me, they both took me to TWRP.
Also, TWRP doesnt seem to work on HTC One Mini 2 after you do anything to set up your phone. It just doesnt recognise touch input any more so you cant do anything with it. However the fix i noted earlier (factory reset) even works with other roms installed, confirmed for cyanogenmod 11 and 12 nightlies as at the date of this post. After factory reset TWRP works again, but if you go through the setup steps and start installing apps, TWRP goes unresponsive again. I hope we might get an official TWRP update soon!
It's bootloader unlocked, but can't get into bootloader. I wand Cyanogenmod on it.
I'll give remote access to my computer / device, and even talk on the phone. I have all files I can find downloaded, but none will root the device or roll back, etc. I can't access the bootloader in any way (power / volume down or power / volume up just result in a normal boot).
I will pay via PayPal. I need this ASAP. I don't know what I did wrong, but hope you're the person than can fix it and install CM (or any other way to wifi tether on T-Mobile / Simple Mobile).
Serious offer. Can you do it? If so make some quick cash.
Thanks,
-Joe
[email protected]
this should help you
http://forum.xda-developers.com/tmo...ck-guide-h811-20-o-bootloader-unlock-t3421589
Yes, this should help resolve your issues. What you wanna do is get ADB on your computer. Download the file in this link. It will get everything running, system wide. I did this, personally, because I'm a lazy mofo. Also, you want a custom recovery, not your bootloader
http://forum.xda-developers.com/showthread.php?p=48915118#post48915118
Next up, you wanna enable developer setting on the phone.
-Settings....about phone....software info.....click on "build number" until you are granted developer settings (it'll say it.)
Click back, twice and you'll see Developer Settings. Go there and make sure developer options is toggled ON, up top.
Make sure "Enable OEM unlock" is checked. Scroll down and make sure "USB debugging" is checked on.
Grab all your files (cyanogenmod and gapps) Put that in a folder. and recovery img, you'll need that.
Plug your phone into your computer....Make sure you allow USB connection! Your phone will prompt you about this.
Now, within the folder,with all your files, including your recovery img, hold shift and right click. Click on "open terminal here"
Type in "adb reboot bootloader"
Your phone will boot to a black screen with some writing on the top. Since you said it's bootloader unlocked, let's move on.
type in "fastboot boot twrp-3.0.2-0-h811.img" (FYI, please have this downloaded, and in the same folder as you opened the terminal window)
Your phone should now be in TWRP recovery! Your phone should still be recognized by your computer, so open up the device, so you can browse the files of the phone.
Windows start menu....file explorer....this PC....click on your phone.
For the sake of simplicity, transfer all your files, including the recovery img, to the phone.
Once all files are on, click on "install" click "install IMAGE"...look for your twrp file and select it. THIS IS SO IMPORTANT! FLASH IT AS RECOVERY!!
Swipe to confirm...done.
Hit the home button....click "reboot"....click "recovery".
This is just gonna boot you back into recovery, so you know that you have a permanent recovery!
Next step is to backup...click it. Just swipe to backup. The three important things are checked (system, data and boot.
Once that is done, "wipe" (click it) swipe now. The recovery will do everything for you. Factory reset, basically. It doesn't wipe your internal storage, so your CM and Gapps are still gonna be there. ALWAYS BACKUP. Everybody knows that a backup can really save your ass!
Once done, "install"....click on CM then click "add another zip". Click on gapps. Now, swipe to flash the files
The recovery will do it's thing, and will confirm when it's done and successful! "Reboot system now".
The phone will take a bit to boot up, get apps ready, etc etc.
Welcome to Cyanogen mod.
If for any reason you get red errors and are panicking , just "wipe" again, then click on "restore" and swipe. Once that is done, you can reboot into stock and still have a functional phone.
seetru said:
http://forum.xda-developers.com/tmo...ck-guide-h811-20-o-bootloader-unlock-t3421589
Click to expand...
Click to collapse
csimo said:
It's bootloader unlocked, but can't get into bootloader. I wand Cyanogenmod on it.
I'll give remote access to my computer / device, and even talk on the phone. I have all files I can find downloaded, but none will root the device or roll back, etc. I can't access the bootloader in any way (power / volume down or power / volume up just result in a normal boot).
I will pay via PayPal. I need this ASAP. I don't know what I did wrong, but hope you're the person than can fix it and install CM (or any other way to wifi tether on T-Mobile / Simple Mobile).
Serious offer. Can you do it? If so make some quick cash.
Thanks,
-Joe
[email protected]
Click to expand...
Click to collapse
Maybe try installing these drivers before using the "adb reboot bootloader" command inside of LG Root folder.
-install "LGUnitedMobile_Win_Driver_Ver_3.14.1"
Download:
https://www.androidfilehost.com/?fid=24052804347823763
-install: "adb-setup-1.4.3.exe" to get adb and fastboot drivers etc.
Download:
http://forum.xda-developers.com/show...8#post48915118
-you may want to restart your computer.
I did what was suggested in post #2. It got to 98% and never finished. The phone shut off and has never restarted again. Completely dead. I sent it back to LG since it had a s/n starting with 505 and see if they'll replace it.
Dead phone, dead issue.
-Joe
csimo said:
It's bootloader unlocked, but can't get into bootloader. I wand Cyanogenmod on it.
I'll give remote access to my computer / device, and even talk on the phone. I have all files I can find downloaded, but none will root the device or roll back, etc. I can't access the bootloader in any way (power / volume down or power / volume up just result in a normal boot).
I will pay via PayPal. I need this ASAP. I don't know what I did wrong, but hope you're the person than can fix it and install CM (or any other way to wifi tether on T-Mobile / Simple Mobile).
Serious offer. Can you do it? If so make some quick cash.
Thanks,
-Joe
[email protected]
Click to expand...
Click to collapse
These guys did the deed for me. https://www.oneclickroot.com I screwed around for DAYS before I just had them do it in a few minutes.
I had a similar problem, took out my micro SD card and redo everything over and it finally rooted.
This one is history. It won't power on under any circumstances (with or without battery). Like I said it was a 505 s/n and LG did give me a return number and even paid the shipping. They know of the 505 problem and what I was doing probably put it over the edge.
I was going to put CM on it to see if I could get wifi tethering to work on T-Mobile. FoxFi nor any of the other tricks seemed to work and I was hoping CM would allow wifi tethering. Anyone know the answer?
As for me, I accidentally flashed a lower fw version and screwed it up, filed a repair ticket through LG, told them it died and wouldn't come back on after the T-mobile ota, they replaced the board, no cost, due for delivery tomorrow, didn't need a receipt or proof of purchase either.
I used every fix in a combo.. fixed without lg help.. someone need to clean up my post and repost as a thread for a cheap permanent fix.. the problem starts from the rubber resistor in the battery.. the phone doesn't get the right amount of power from the stock battery so the phone gets hot from over compensation. Then the CPU/GPU will get so hot that the contacts to the main board get a little faulty.. when I bought the phone it bootloop bad and never got pass the LG boot screen.. tried the freezer trick which made the phone moist for a better connection but only boot to home screen then bootloop again cause it also has bad thermal contact.. then I did the heat gun I fix with a blow-dryer. It ran perfect until I ran an app. I then followed a guild and added a thermal pad directly on CPU and GPU. Then added thermal paste between the metal frame and the metal that cover CPU/GPU. Ran for 15 to 30 mins before bootloop.. all the time I need. I then followed a guide for bootloader unlock. fastboot boot TWRP. Flash TWRP via TWRP. Then reboot into TWRP ( if you try to fastboot flash it will fail and you will have no recovery) to make sure it stuck. Flash supersu and thermal mod from xda. Rebooted and downloaded BusyBox.. now stable but running hot. Flashed a nougat ROM.. running perfect but got 43° average instead of 63°. Used kernel editor to disable 2 big cores and thermal throttle and set everything to enable on boot. Perfect and stable no matter what in doing. Temp stay between 23° & 33°. I plan on using better thermal paste, pads and getting the TOTHL battery for better stability without a mouth full of mods.. who needs lg help? Not me.. good luck guys. There's a debate about what the real issue is. Simple.. every answer is correct which made it fixable for me with sending anything to lg. The processor is very powerful and the battery resistor is the source. I also tried a more powerful battery before any mods. When the processor needed more power I got a pop-up message about use an LG ( original) battery before it bootloop. Also with the more powerful battery, I'd get a message if I tried changing it with the phone off saying not compatible but since using a custom ROM it work fine. Lg has something in the stock software to make people think paying them extra for warranty or tech fix is the only solution. That is your only option if you bone stock. That's why they still sending patches.. to the g4.. to block root meaning you will have to pay them for fix..
Solved - Plz try my way, if does't work, I will change the Title
Gentleman, Please try the following and don't forget the bounty $s lol.
I hope you have all the files and pc is reading your phone in adb.
Keep the downloaded twrp file in your adb folder with dwonloaded name (Ex:1234twrp.img)
Copy the same twrp file and keep in phone internal storage with named recovery.img
adb reboot bootloader (wait for phone to boot in bootloader ofcourse)
fastboot boot 1234twrp.img (whatever your twrp img file name would be in your adb folder)
Now you are in twrp recovery page in your phone.
Tap Install (STOP) > Images (bottom right) > select recovery >
Now you are in next screen where options to select recovery or boot
Tap recovery and swipe you will see [image flash complete]
Now twrp is permeant. You can restart in recovery without PC. (Tested)
Download this rom (Stock of 81120o with root access supersu installed from
https://forum.xda-developers.com/tm...om-mm-lg-g4-h811-20o-stock-debloated-t3412394
or
https://forum.xda-developers.com/tmobile-g4/development/tm-h811-genisys-rom-3-7-1-t3313173
in twrp install and select your downloaded rom zip file. I prefer the second link. You have options to remove all LG junks.
Don’t run this rom with temporary trwp (which can start with pc only) then your will lose twrp and your OS and you have to do download mode and kdz thing.
Good Luck and please let me know.
Solved
csimo said:
It's bootloader unlocked, but can't get into bootloader. I wand Cyanogenmod on it.
I'll give remote access to my computer / device, and even talk on the phone. I have all files I can find downloaded, but none will root the device or roll back, etc. I can't access the bootloader in any way (power / volume down or power / volume up just result in a normal boot).
I will pay via PayPal. I need this ASAP. I don't know what I did wrong, but hope you're the person than can fix it and install CM (or any other way to wifi tether on T-Mobile / Simple Mobile).
Serious offer. Can you do it? If so make some quick cash.
Thanks,
-Joe
[email protected]
Click to expand...
Click to collapse
Solved - Plz try my way, if does't work, I will change the Title
Gentleman, Please try the following and don't forget the bounty $s lol.
I hope you have all the files and pc is reading your phone in adb.
Keep the downloaded twrp file in your adb folder with dwonloaded name (Ex:1234twrp.img)
Copy the same twrp file and keep in phone internal storage with named recovery.img
adb reboot bootloader (wait for phone to boot in bootloader ofcourse)
fastboot boot 1234twrp.img (whatever your twrp img file name would be in your adb folder)
Now you are in twrp recovery page in your phone.
Tap Install (STOP) > Images (bottom right) > select recovery >
Now you are in next screen where options to select recovery or boot
Tap recovery and swipe you will see [image flash complete]
Now twrp is permeant. You can restart in recovery without PC. (Tested)
Download this rom (Stock of 81120o with root access supersu installed from
https://forum.xda-developers.com/tmo...oated-t3412394
or
https://forum.xda-developers.com/tmo...3-7-1-t3313173
in twrp install and select your downloaded rom zip file. I prefer the second link. You have options to remove all LG junks.
Don’t run this rom with temporary trwp (which can start with pc only) then your will lose twrp and your OS and you have to do download mode and kdz thing.
Good Luck and please let me know.
Hello,
I hope I'm in the right section here, and if not, please move this thread, thank you very much.
After unlocking the bootloader on my new OnePlus 3t with Android 7.0, I tried to flash twrp-3.0.3-1-beta1-oneplus3t.img using a guide which I apparantly can't post here. I hope I can put the link in a comment if you ask for it.
However, after I typed in the second of the two commands: fastboot boot recovery.img, the TWRP logo appeared on my phone for several minutes. Maybe I was too unpatient but because I was worried, I pressed and held the power button and the volume up button, so my phone would boot up normally.
So to sum it up, the steps I did were:
1. Unlock the bootloader
2. After changing all the settings (OEM, USB-debugging and so on), I booted my phone into fastboot mode
3. Then in adb I typed in: fastboot flash recovery recovery.img while recovery.img is the same file I've mentioned earlier.
4. After that, I typed in the second command: fastboot boot recovery.img
5. Finally, my problem happened. Or was I waiting not long enough? I haven't measured the time obviously, but I've waited a few minutes. So the only thing my screen was showing was the TWRP logo.
Then I've pressed the button combination and my phone booted up normally.
Now, I don't know how to proceed, as I still want to root my device. I'm not sure if the steps I've done until now worked so that I can just move on by flashing SuperSU, or if I have to reverse the steps and just wait a little bit longer. I don't want to do this until you guys tell me to do, because I'm not sure if flashing something twice might break my device.
If my post was unclear or information were missing, please just ask and I'll answer. Thanks a lot for any help!
Hi !
Booting into TWRP after flashing it takes a long time , something like 2 minutes maximum due to encryption , known bug long story , Oneplus must release sources ect ...
Put the supersu 2.79 stable version into your phone and flash it via recovery or , from recovery / sideload type " adb sideload supersu.zip(exact name of the zip) and reboot , you should have root access
This long boot time only happens if you have your data partition formatted as F2FS instead of EXT4, and takes longer depending on how much data you have filled up your data/internal storage partitions with. If you backup everything on PC and then reformat using EXT4 TWRP boots up without delays.
Thank you both guys,
I've made it. It was just my fault because I wasn't waiting long enough. When I redid the step, it was working and booting up even faster. If a mod can close this thread, feel free to do so.
Good! No need to close the thread but I would ask you to edit the title and add [solved] at the beginning of it for others to find it easier, thanks!
Sent from my Darkside of Oneplus 3T
Hi,
Please indulge me if this it a bit silly, but I am confused about installing magisk from recovery. I flashed the patched image to recovery partition, as per the github guide (https%3A//topjohnwu.github.io/Magisk/install.html%23boot-image-patching, sorry for the encoding, system forbids me to post link cuz I am new). Yet at this point I am unsure about what to do next. This is what I see now when I boot my phone to recovery using key combo:
- Reboot system now
- Apply update from ADB
- Apply update from internal storage
- Wipe data/factory reset
- Wipe cache partition
- Mounts a storage
If I select "Reboot system now", nothing seem to happen and it all looks like a normal startup.
In short, I would like to know how to run to a ystem with Magisk enabled.
Thanks in advance!
You're not actually supposed to boot to recovery. You need to release the key combo once you see the splash screen. Reference:
https://topjohnwu.github.io/Magisk/install.html#magisk-in-recovery
Edit: and don't worry... Everyone's a noob at some point or another.
Didgeridoohan is right: It sounds like you're booting into your phone's stock recovery, instead of your custom recovery.
Forgive my presumptions, or if I sound condescending, but if you happened to have patched and flashed your partition mods with a PC, you might want to check if you even have a custom recovery installed. (I know that some phones aren't capable of having a custom recovery flashed, so your situation might be different.) If you don't have one, that would be the first step (most folks use TWRP). Once you can boot into your custom recovery, though, you should be good.
Sent from my LG V20 (VS995), Alpha Omega ROM, Oreo 8.0, rooted (Magisk 20.4), using Tapatalk
Didgeridoohan said:
You're not actually supposed to boot to recovery. You need to release the key combo once you see the splash screen. Reference: ...install.html#magisk-in-recovery
Edit: and don't worry... Everyone's a noob at some point or another.
Click to expand...
Click to collapse
Right, this is the part where I get confused. I did follow the link you mentioned. After pressing [power] & [volume up] for about 8 seconds, I feel a vibration and the screen lights up, thats when i released the keys. I ended up getting that menu i describe above...(tears)...
Ideally, what should I see if things go right?
NeoHiPPy1980 said:
Didgeridoohan is right: It sounds like you're booting into your phone's stock recovery, instead of your custom recovery.
Forgive my presumptions, or if I sound condescending, but if you happened to have patched and flashed your partition mods with a PC, you might want to check if you even have a custom recovery installed. (I know that some phones aren't capable of having a custom recovery flashed, so your situation might be different.) If you don't have one, that would be the first step (most folks use TWRP). Once you can boot into your custom recovery, though, you should be good.
Sent from my LG V20 (VS995), Alpha Omega ROM, Oreo 8.0, rooted (Magisk 20.4), using Tapatalk
Click to expand...
Click to collapse
No worries. Any suggestion is much ppreciated. Just to be sure (correct me if i m wrong), I thought that patching an image file is an independent way of installing magisk in case custom recovery is not available. So that s my case.
Anyhow, I would really like to learn a bit more about the situation where recovery partition contains both the stock recovery and custom recovery/patched image. There doesnt seem to be any difference whether i release the key combo or not once I see a splash screen. I always end up with that blue menu in recovery.
Wubwubdubdub said:
No worries. Any suggestion is much ppreciated. Just to be sure (correct me if i m wrong), I thought that patching an image file is an independent way of installing magisk in case custom recovery is not available. So that s my case.
Anyhow, I would really like to learn a bit more about the situation where recovery partition contains both the stock recovery and custom recovery/patched image. There doesnt seem to be any difference whether i release the key combo or not once I see a splash screen. I always end up with that blue menu in recovery.
Click to expand...
Click to collapse
If you don't mind my asking, which model of phone do you have? Most phones have a similar button combo, but are a bit quirky to get into the recovery.
Ex: On my LG V20, I have to hold Vol-, and Power, but release the power button at the splash screen for 0.5-1 seconds (while still holding Vol-) and then press/hold the Power button again...
As a suggestion, you may want to see if your phone has a similar quirk, depending on the make /model.
Sent from my LG V20 (VS995), Alpha Omega ROM, Oreo 8.0, rooted (Magisk 20.4), using Tapatalk
[Solved] by flashing boot image instead of recovery image
I am still puzzled by the complications with booting into recovery mode. To work around it, I attemped installing Magisk using boot image patch and succeeded. Objective achieved yet question remains. Anyways, a big thanks to Didgeridoohan and NeoHiPPy1980. Knowing that someone will provide help is what stopped me from giving up.
NeoHiPPy1980 said:
If you don't mind my asking, which model of phone do you have? Most phones have a similar button combo, but are a bit quirky to get into the recovery.
Ex: On my LG V20, I have to hold Vol-, and Power, but release the power button at the splash screen for 0.5-1 seconds (while still holding Vol-) and then press/hold the Power button again...
As a suggestion, you may want to see if your phone has a similar quirk, depending on the make /model.
Sent from my LG V20 (VS995), Alpha Omega ROM, Oreo 8.0, rooted (Magisk 20.4), using Tapatalk
Click to expand...
Click to collapse
I have a Ulefone, not sure if you ve heard of it
But that won't matter. I managed to get it working another way (see to my last post). I should probably have done that before making this post. Thanks for your assistance!
Great to hear you got things working, but why did you think you needed to use the recovery image for your device? Was any of the installation instructions unclear and in need of improvement (I'm just trying to learn for future reference)?
Didgeridoohan said:
Great to hear you got things working, but why did you think you needed to use the recovery image for your device? Was any of the installation instructions unclear and in need of improvement (I'm just trying to learn for future reference)?
Click to expand...
Click to collapse
Frankly, I find the Magisk Installation Guide to be one of very few documentation that is concise, coherent and user-friendly for both regular user and developer. So a big thumb up for you all! For your reference, here is the process of how I was lead to believe I needed the recovery img:
1.
I followed the instruction on "know your device" (https%3A//topjohnwu.github.io/Magisk/install.html#knowing-your-device). The first command returns nothing and the seconde comand returns true. Naturally, I assumed this means that my device is using system-as-root on a non-A/B device.
2.
I then read:
If your device is NOT A/B, but IS using system-as-root, then you will have to install Magisk to the recovery partition of your device. Follow the instructions in Boot Image Patching, but instead of using your boot image, use your recovery image. "
Click to expand...
Click to collapse
(https%3A//topjohnwu.github.io/Magisk/install.html#getting-started)
I am not sure if I misunderstood sth. At this point I still believe that according to the instruction I should have patched my recovery image. I do not know what system-as-boot actually is...
Yes, it does seem like your device is A-only system-as-root, which would normally mean you need to use the recovery image.
Unfortunately, with the Android ecosystem being as fractured as it is there will always be exceptions...
Thanks for the detailed response.
Hi Guys
Wubwubdubdub, I have got a question for you. I followed the same instructions as you mentioned in first post and ran into problems as well. How did you get around this problem? What is the difference between the two ways you mentioned here? (I believe I used the first way).
Wubwubdubdub said:
I flashed the patched image to recovery partition, as per the github guide
Click to expand...
Click to collapse
Wubwubdubdub said:
To work around it, I attemped installing Magisk using boot image patch and succeeded. Objective achieved yet question remains.
Click to expand...
Click to collapse
Thanks in advance!
MM