Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, broken hearts,
* thermonuclear war, you getting fired because the alarm app failed, or
* unfulfilled sexual partners. Please do some research if you have any
* concerns about features included in this Recovery before flashing it! YOU are
* choosing to make these modifications, and if you point the finger at me
* for messing up your device, I will point that finger back at you and laugh.
* Then I will put it in your eye.
*/
By using the Recovery you agree with the above terms!
== General ==
Very soon, this recovery is going to violently change. The new name will be TeamAcid Recovery.
The SGH-I717 is the first in a series of phones to get this recovery.
Obviously it is based on CWM 6.0.1.4 for JellyBean. But things will change very soon.
Since I'm not able to get the code for CWM Touch, I'll just have to do something new.
As for now, this recovery was built with CyanogenMod 10 with this local_manifest.xml. The TARGET_BUILD_VARIANT is eng.
I didn't test flashing GB or ICS roms with this recovery. YMMV!
I have an AT&T SGH-I717 and have tested this on my own device.
I've flashed a few roms with it, flashed back and forth between twrp and this recovery, tested adb and usb mounting, and have signed it with my own cert.
If you find a bug, please let me know! If you can also provide a log, I will respond faster!
If someone can point me at where to get the vendor/koush/recovery stuff, I can add touch support. Until then, I think that code is proprietary to koush and I'm stuck with this.
As I said above, this recovery will be changing quite a bit in the future. Stay tuned.
== Download ==
v6.0.1.4 - 2012/10/02
Changes:
Initial build. Totally stock JB cwm.
CWM
ODIN
== Credits ==
The CyanogenMod Team
Koushik (koush) Dutta and everyone else that has contributed to CWM!
cool thanks will test later
Nice. I'll check this out. Ty
Sent from my SAMSUNG-SGH-I717 using xda app-developers app
Thank You For Continuing To Support The SGH-I717.
downloading thankyou
Sent from my SAMSUNG-SGH-I717 using xda premium
I had a problem with cmupdate on 10/03 with this recovery. I'm looking into it. It was trying to update from /emmc//cmupdate/cm-10...
Update: cmupdate worked just fine for 10/04. Guessing it was a cmupdate problem.
Related
I’m having problems with the vibrant and am hoping people on the forum could help me with it. I have tried to research on the xda and also android forums but I haven’t come across anyone with similar problems I have encountered.
I first got the vibrant last December and did one upgrade through the software update on the phone. Since then I have rooted the phone (with the tips posted on the sticky board on xda forum) and flashed a custom rom once with ease (Eugene – Ginger clone final R2). I was on Ginger clone for a month and was pretty happy about it.
I recently tried to flash new roms (Eugene – Vibrant 4G and TW – Bionix Frost 2.2.1) without success. I kept getting the error about “signature verification failed”. After several attempts, I brick the phone.
I was able to get to download mode, used Eugene’s no brick, and odin it back. Now the phone is running on Éclair; JFD and kernel 2.6.29. I was able to flash Eugene Vibrant 4G, but not TW Bionix Frost. I even odin it back to stock JFD, but I still got the same signature verification error. Do you know why I keep getting this? I remember reading from the forum that TW rom is based on Éclair and there shouldn’t be any problem flashing TW rom if I’m on Éclair.
Then I went back to Eugene Ginger clone final R2. After several days, the stuff on the main screen were disappeared, i.e. clock, date, and widgets/icons. I odin it back to JFD, but this time I can’t even root the phone!! I tried the three button method and also SuperOneClick, but it didn’t work. The SuperOneClick said the phone was successfully rooted, but Titanium Backup said I didn’t have root right. Below is the message on the screen when I applied the three buttons method:-
Installing update…
assert failed: getprop(“ro.product.device”) == “GT-I5800” || getprop(”ro.build.product”) == “GT-I5800” || getprop(“ro.product.device”) == “GT-I9000” || getprop(”ro.build.product”) == “GT-I9000”
E:Error in /sdcard/update.zip
(Status 7)
Installation aborted.
Also I have tried to odin the phone to JI6 but it went dead at the booting screen.
Can you please advice on getting the phone rooted and getting through the signature verification failed issue? I have seen a post relating to solving signature verification failed on the forum, but believe it’s not for Éclair. I’m now on JFD and the phone is so slow.
Any helps are much appreciated.
Does your phone turn on, if yes, its not bricked, if nothing happens at all when you try to turn it on then your are bricked...
Another question, why are you flashing all these roms, I understand if you want to try them out but by the looks of it you don't know what you are doing... provide some links as to what you've flashed for reference
Sent from my GT-I9000 using XDA App
Thanks for your response, Stefan. The phone is working now. What I’m trying to do now is to get the phone rooted and solve the signature verification fail issue; maybe go back to Ginger clone rom that I had used for over a month. I wanted to try these roms as their performances and options are different.
Here’s the links to the roms:-
Eugene – Ginger clone http://eb-productions.proboards.com/index.cgi?board=samsungsgs&action=display&thread=144
TW – Bionix Frost http://forum.xda-developers.com/showthread.php?t=966688
Team Win Recovery Project 2.3, or twrp2 for short, is a custom recovery built with ease of use and customization in mind. It’s a fully touch driven user interface – no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
Phone look:
Tablet look:
CHANGELOG for 2.3.1.0:
-Unmount system after boot to prevent some status 7 symlink failed errors on zip install
-USB Mass Storage code improvements
-Better handling of mounting storage during boot for some devices
-Fixed a problem with sizes of images (boot & recovery) after resetting defaults
-Fixed size errors during backup for some devices on recovery, etc.
-Fixed a problem with restoring backups when multiple archives were present
CHANGELOG for 2.3.0.0:
-Rebased onto AOSP Jelly Bean source code
-Rewrote backup, restore, wipe, and mount code in C++ classes for easier maintenance going forward
NOTE: backups from prior versions of TWRP are still compatible with 2.3
-ADB sideload functionality from AOSP is included in 2.3, see this link for more info
-Re-wrote fix permissions entirely in C++ and runs in a few seconds instead of a few minutes (thanks to bigbiff)
-Improvements to zip finding in OpenRecoveryScript (should be a lot fewer GooManager automation issues)
-Faster boot times
-Added charging indicator while in recovery (only updates once every 60 seconds)
While this update may not bring a host of new must-have features, this update is a significant re-write of much of the core TWRP code. AOSP Jelly Bean recovery source moved to mostly C++ code and now all of the "TWRP" code is fully rewritten into C++ as well. Now that we've laid this groundwork, we're in a much better position to pull in future AOSP recovery updates as well as implementing more great new features.
Since TWRP 2.3 is based on AOSP jelly bean sources, TWRP now uses recovery API 3 instead of 2. Some zips may no longer work if the developer is using an out-of-date update-binary. This API change should not be a problem on newer devices, but older devices will probably encounter several zips that need to be updated. If needed, you can try using this update-binary that was compiled with current sources. It goes in your zip file in the META-INF/com/google/android folder.
DOWNLOAD:
The fastest and easiest way to install TWRP is to use the GooManager app:
Play Store Link
Direct Download
1) Install GooManager from the Play Store
2) Open GooManager and provide root permissions
3) Hit Menu (or the button with the 3 dots on your screen) and then Install OpenRecovery
OR:
You can find more information and download links on our website!
BUGS:
If you have found a bug, please consider posting it to our github issues log. It's pretty much impossible for us to keep up with the more than 30 threads that we have for the devices that we "directly" support. If you have a significant problem that cannot be answered in this thread, your best bet is to PM me directly, contact us via our website, or find us in our IRC channel below. If you see someone that's struggling, feel free to point it out to us. We need your help to help us keep track of all of our devices! Thanks!
SUPPORT:
Live support is available via #twrp on Freenode with your IRC client or just click this link.
Two thumbs
Flashes fine and boots into recovery and can flash files as well. On aokp 35.1 for the record.
Sent from my SCH-I500 using Tapatalk
I will warn you all to use care with this, it does not play well with other recoveries and roms, and sometimes even with Odin. I used it a lot trying to test things for steve and we decided to put it on the back burner, it is cool but causes trouble sometimes. Basically, it's awesome to use and has lots of handy features (zip queue ftw) but try not to flash anything with it if you aren't near a computer that you can Odin with just in case.
Sent from my SCH-I500 using Tapatalk 2
Thanks for the heads up. I did go ahead and flash to play around with it. You are right. There are a bug or two in there. Is there a easy way to get the reg cwm back on like Odin or flashing, or do I need to Odin back to stock first. Its no biggy, just didn't want to waste time when I get home tonight. It is very responsive and easy to navigate though and looks very promising
edit:so odin back to stock and then restore is the way to go. I still like it a lot either way.
Sent from my SCH-I500 using Tapatalk
shelby04861 said:
Thanks for the heads up. I did go ahead and flash to play around with it. You are right. There are a bug or two in there. Is there a easy way to get the reg cwm back on like Odin or flashing, or do I need to Odin back to stock first. Its no biggy, just didn't want to waste time when I get home tonight. It is very responsive and easy to navigate though and looks very promising
edit:so odin back to stock and then restore is the way to go. I still like it a lot either way.
Sent from my SCH-I500 using Tapatalk
Click to expand...
Click to collapse
Reflashing AOKP glitched version should work? Unless TWRP messes with the way it handles scripting.
tonu42 said:
Reflashing AOKP glitched version should work? Unless TWRP messes with the way it handles scripting.
Click to expand...
Click to collapse
yeah it changes some boot stuff and tries to reinject itself when you flash kernels. Which is handy if you want it but if you don't it causes problems. I was able to flash a glitch kernel from twrp but then it would just keep rebooting to glitch (cwm) recovery as though I had done three finger reboot. I flashed cm7 which put me back on blue older cwm5 and after flashing it again the phone booted so then I flashed back to ics.
Sent from my SCH-I500 using Tapatalk 2
It is really a 50/50 as to which way to go, a bunch of flashing or a bunch of Odin and then restore. Time difference is not to much. Were you able to do any backups and restores with it. I didn't have time to try that out yet. I also didn't have time to check to see if the problems made the bug report or not
Sent from my SCH-I500 using Tapatalk
Things I would like tested before I include it in AOKP.
1) data wipe. You can flash the ROM again boot and if all is well go back and restore.
2) flash the ROM or Efpophis kernel and tell me what recovery you have. It should be blue or red not twrp.
If those are good I'll look into including it.
Sent from my Glitched AOKP Unicorn.
Stephen, I have not tried those due to time. I can tell you I tried flashing the cwm fixed for cm7 twice and I still remained on twrp. I tried once with the injection button checked and once with it unchecked. Same result but no boot loop issues at all from that or any other flashing. This recovery is a tricky one for sure. When I get more time I will try some of your requests. I have limited time at my home computer lately because of work and studying for a test for work.
Sent from my SCH-I500 using Tapatalk
shelby04861 said:
Stephen, I have not tried those due to time. I can tell you I tried flashing the cwm fixed for cm7 twice and I still remained on twrp. I tried once with the injection button checked and once with it unchecked. Same result but no boot loop issues at all from that or any other flashing. This recovery is a tricky one for sure. When I get more time I will try some of your requests. I have limited time at my home computer lately because of work and studying for a test for work.
Sent from my SCH-I500 using Tapatalk
Click to expand...
Click to collapse
How did you flash the CWM CM7? If you (or the zip) used flash_image, then you might need to use erase_image first. flash_image checks the first 2KB of the image against what's already in boot. If it matches then it refuses to flash. The 2KB approach works fine for "normal" Android kernels because the first 2KB contains a "unique signature" but it doesn't always work well for Samsung SGS1 kernels because they are packed differently. I've found that I sometimes had to use erase_image in order to get flash_image to work. I've thought about submitting a patch to CM to fix this issue but haven't gotten around to it yet.
TWRP has been tested on the Epic 4G here:
http://forum.xda-developers.com/showthread.php?t=1622947
And there's a zip here that should re-inject CWM. It would need to be modified slightly to work with the Fascinate, but someone could use this as a base if they wanted:
http://forum.xda-developers.com/showthread.php?t=1651012
I think most of the issues that you'll experience will be due to the "injection process". If your kernel or ROM developer already includes TWRP in their builds then you don't need to try to reinject TWRP every time and we do make it optional. The recovery itself should be pretty solid because we use the same code across all devices (except for the optional injection code) so there's nothing that's specific to the SGS1 devices. Also, for the record, because sk8 loaned me his Fascinate, I was able to add /datadata support to TWRP, so that issue gone now too.
If you do run into any issues, please let me know. It's best to PM me, submit a bug report on github, or catch me in #twrp on Freenode. With over 20 devices to support I can't frequent the threads on the forums or I won't get any coding done.
Dees_Troy said:
How did you flash the CWM CM7? If you (or the zip) used flash_image, then you might need to use erase_image first. flash_image checks the first 2KB of the image against what's already in boot. If it matches then it refuses to flash. The 2KB approach works fine for "normal" Android kernels because the first 2KB contains a "unique signature" but it doesn't always work well for Samsung SGS1 kernels because they are packed differently. I've found that I sometimes had to use erase_image in order to get flash_image to work. I've thought about submitting a patch to CM to fix this issue but haven't gotten around to it yet.
TWRP has been tested on the Epic 4G here:
http://forum.xda-developers.com/showthread.php?t=1622947
And there's a zip here that should re-inject CWM. It would need to be modified slightly to work with the Fascinate, but someone could use this as a base if they wanted:
http://forum.xda-developers.com/showthread.php?t=1651012
I think most of the issues that you'll experience will be due to the "injection process". If your kernel or ROM developer already includes TWRP in their builds then you don't need to try to reinject TWRP every time and we do make it optional. The recovery itself should be pretty solid because we use the same code across all devices (except for the optional injection code) so there's nothing that's specific to the SGS1 devices. Also, for the record, because sk8 loaned me his Fascinate, I was able to add /datadata support to TWRP, so that issue gone now too.
If you do run into any issues, please let me know. It's best to PM me, submit a bug report on github, or catch me in #twrp on Freenode. With over 20 devices to support I can't frequent the threads on the forums or I won't get any coding done.
Click to expand...
Click to collapse
Looks good both issues look fixed. I'll play with it a bit more. But I think you did a great job.
Sent from my Glitched AOKP Unicorn.
I guess you have your answers. I was flashing the zip version, but I do not ha e the further details you want.
Sent from my SCH-I500 using Tapatalk
Yeah everything looks great I made the changes needed to build it in aokp as soon as I get server access back up I'll test some builds with it in there. Great job dees looks great.
Stephen.k.spear said:
Yeah everything looks great I made the changes needed to build it in aokp as soon as I get server access back up I'll test some builds with it in there. Great job dees looks great.
Click to expand...
Click to collapse
ill fershur test this after it gets outta alpha stage, i dont wanna screw up my phone
Okay so far I'm loving this recovery, still have more testing, but I'm insanely impressed!
~~~~There is no spoon~~~~
After serious testing on this recovery last night I have come to the following conclusions:
1 This is the ONLY recovery that will let me backup/restore my device correctly on this phone
2 USB Mount doesn't seem to work, but if I had to trade USB Mount for working backups it is NOT a hard choice.
3 This recovery is one of the simplest to use and most functional recoveries I have used on ANY phone
4 This recovery is extremely responsive, full featured and beautiful to look at with the theme I have on it. Oh yeah, did I mention you can THEME THE RECOVERY?!?! WIN!
5 Any more bacon packed in this package would cause massive coronary problems.
6 If you are scared to try it, don't be. I am using ONLY TWRP recovery from this point on. I'm sold.
So if any of you are on the edge about this recovery, take the plunge. I promise you will not regret it.
my only problem is that i cant restore my CWM backups with TWRP
ztotherad said:
my only problem is that i cant restore my CWM backups with TWRP
Click to expand...
Click to collapse
This is definitely worth starting fresh and making a new backup.
~~~~There is no spoon~~~~
Honestly? I used TWRP on my Acer & it was okay, but I did definitely have problems, but I'll try it
Can I go back to CWM if I don't like it?
ztotherad said:
Honestly? I used TWRP on my Acer & it was okay, but I did definitely have problems, but I'll try it
Can I go back to CWM if I don't like it?
Click to expand...
Click to collapse
I haven't tried that yet, I was waiting for the next kernel it ROM release before flashing just to see if I could get cwm back on.
~~~~There is no spoon~~~~
Hello, XDA family. This is my issue today. I didn't read all that there was to know about rooting and flashing in the EVO LTE, because I did my share of flashing on the OG. However, when I couldn't boot into AOSP roms, I started my research and found out different stories about how to go about doing so.
I saw somewhere that I had to flash a specific boot image first, then flash the Rom. That didn't work, and it also crashed my WiFi.
After even MORE research, I found that the phone has to be S-Off, and I am not.
After trying to flash an updated IMG to save my WiFi, the phone didn't boot to the animation. It showed the splash screen, then went blank. And this happened for all of the custom roms that I tried to flash. It only booted to a rooted version of the stock Rom.
It also corrupted my TWRP 2.1 recovery, and the recovery kept restarting. I solved the issue by flashing TWRP 2.3
I even tried flashing the stock recovery and.installing the OTA update, and it did nothing but perform a data reset, and cleaned my internal sd. So I'm stuck on the software version that doesn't have a remappable Multitasking button.
What do I do?
______________________________
HTC Evo 4G LTE
Did you try using Flash image GUI to flash the kernel first?
Sent from my EVO using xda app-developers app
Yes, and I suspect that it was the incorrect kernel altogether. Not was one from Komodo...rls one, I believe. My phone did a factory reset, so I can't tell you.
ASUS Transformer TF300T
Stock Rom - Unrooted/Unlocked Bootloader
Okay, so I found a thread on themikmik that has a boot img for the rom that I am using.
http://themikmik.com/showthread.php...oted-Based-on-Latest-OTA-(Odexed-and-Deodexed)
Let's hope that this works out in my favor.
ASUS Transformer TF300T
Stock Rom - Unrooted/Unlocked Bootloader
Quick update: Wifi doesn't work. I'm going to try flashing a custom rom and see what happens
ASUS Transformer TF300T
Stock Rom - Unrooted/Unlocked Bootloader
I forgot to mention in my first post that when I flash custom sense roms, I wouldn't see the disclaimer in red letters with the splash screen, and then the phone would go blank.
Now, after flashing the new img, and flashing a custom rom (Sinister LTE V4), I STILL didn't see the red letters, which I thought that it would fail. HOWEVER, it actually DID boot, with Wifi working and everything. So...what the he'll happened? I don't really care at this point...but I'm laying of flashing for a little bit until I do a lot more research, since my new EVO different in subtle ways from its predecessor, but those same "subtle" differences almost bricked my phone. I blame it on my negligence.
ASUS Transformer TF300T
Stock Rom - Unrooted/Unlocked Bootloader
I don't think you nearly bricked your phone. You don't need to be s-off buy it does make things easier. The fact that your Wi-Fi was not working probably means you flashed a version of komodo that wasn't up to date with your rom or visa versa.
My advice would be to read the "don't panic" thread stickied in the Q&A section
Sent from my EVO using xda premium
Here's exactly how I flash my ROMs. Haven't had an issue since I started using this method:
Download ROM I want, adb push it to my INTERNAL sd card.
Open Flash Image, select "flash kernel" and select the entire .zip of the ROM I downloaded. It will find the kernel file for me.
Flash the kernel.
Reboot into TWRP.
Select "Wipe System" and wipe the whole system.
Flash ROM.
Boot.
Once my phone has booted, go into TWRP again and flash gapps, then reboot.
I ALWAYS ALWAYS ALWAYS have an issue if I try and flash ROM and GAPPS without booting in between. Or if I try and flash the rom and my TiBu update.zip at the same time. I have to flash ROM, reboot, then reboot again into recovery and flash GAPPS/update.zip.
Hope that helps.
Ahhh...interesting. As I mentioned before, I am not S-off. I am not sure if I will become S-off at some point, but right now, I am very happy to be on Sense 4. That's the main reason I chose this phone over the GS3 when I was upgrading from my OG Evo.
I like Sense roms, and when the ONE series was released, my entire theme became Sense 4.
However, if I ever decide to begin flashing AOSP roms, I will certainly keep your advice in mind.
______________________________
HTC Evo 4G LTE
Cyanogenmod 10.2 unofficials here. These are not nightlies, they are unofficials. Totally not responsible for your device imploding, exploding, taking control of your car and re-enacting Tokyo Drift, causing thermonuclear war, running away with your SO, or any other hilarious but unfortunate events.
Requirements:
1. An unlocked TF201 (Plenty of guides to show you)
2. The jellybean (4.1) bootloader. If you are coming from Androwook 1.51+ or Energy, you are not on the 4.1 bootloader, please refer to their threads on downgrading back to a TF201 bootloader. Upgrading to the 4.1 bootloader may require flashing the entire stock 10.4.2.15 image + compatible recovery at the same time.
3. A decent recovery
4. (Optional but recommended) NVFlash blobs and images retrieved from device and backed up, see second post.
Installation:
1. Download zip from sources below (Usually the latest should be good)
2. Either copy to your device and install in recovery, or adb sideload zip.
3. Enjoy?
Downloads:
cm-10.2-20130816-UNOFFICIAL-tf201 Notes: External storage should work now, forgot to make folders to mount to in the init.cardhu.rc
cm-10.2-20130831-UNOFFICIAL-tf201
cm-10.2-20130910-UNOFFICIAL-tf201
cm-10.2-20130918-UNOFFICIAL-tf201
cm-10.2-20130923-UNOFFICIAL-tf201
cm-10.2-20131103-UNOFFICIAL-tf201 Notes: The touchpad button. Thanks Jorge Ruesga.
cm-10.2-20131211-UNOFFICIAL-tf201
Sources:
Androidroot team
TF700T contributors
Device overlay: https://github.com/namidairo/android_device_asus_tf201/tree/cm-10.2
Kernel: https://github.com/namidairo/android_kernel_asus_tf201/tree/cm-10.2
Donations:
To your favourite charity?
Before even contemplating installing, please make some backups with nvflash.
http://forum.xda-developers.com/showthread.php?t=2455920 - For those on Jellybean bootloader already (Yes, you can make nvflash blobs with jellybean now. Glorious.)
http://forum.xda-developers.com/showthread.php?t=1774352 - For those on ICS bootloader (Then afterwards remember to upgrade the bootloader before)
This roms runs on the current jellybean bootloader. (ie. The one that comes with the 4.1 stock rom, if you are coming from another rom such as Energy or Androwook which flash either TF300/TF700 bootloaders, remember to downgrade first.)
Nice job
Does this also have problem with data2sd like pa?
I'm v2.2 Androwook ROM. Do I need to downgrade my bootloader to 4.1.1?
Awesome
aznflawless said:
I'm v2.2 Androwook ROM. Do I need to downgrade my bootloader to 4.1.1?
Click to expand...
Click to collapse
Indeed. I'll probably never condone flashing the TF300 bootloaders because of the support nightmare it creates.
Just flashed. So far so good :good:
Thx v much Namidairo
Ahhh damnit... flashed and it gave the dreaded ASUS boot logo of death...
Was previously running the 10.1 Official so I'm not exactly sure why this nuked on me. Time to see if I can bring this thing back from the dead... or not.
Flashed with success and works great for me !!!!
Still trying to figure out what went wrong for me... that poor thing was hard bricked like no other.
Nothing a little nvflash love didn't fix up so I'm back to running stock at the moment while I try to figure out an odd side effect before getting back to testing.
Anyone ever get everything all back up and running from an nvflash restore and have the device *NOT* state ' device is unlocked ' on first boot?
Just curious.
tsvortex said:
Still trying to figure out what went wrong for me... that poor thing was hard bricked like no other.
Nothing a little nvflash love didn't fix up so I'm back to running stock at the moment while I try to figure out an odd side effect before getting back to testing.
Anyone ever get everything all back up and running from an nvflash restore and have the device *NOT* state ' device is unlocked ' on first boot?
Just curious.
Click to expand...
Click to collapse
OK, all set... I also figured out what happened the first time I flashed this....
In my infinite wisdom (read: my own stupidity) after my last restoration using NVFlash I forgot to go back after upgrading to JB and update TWRP. I inadvertently flashed the ROM with the ICS TWRP and caused my own demise on this one.
Anyway, got the unlocked thing resolved with redoing the restore... re-flashed pt 7 with the unlock-token.img, normal ICS blobs then the bricksafe, rebooted, upgraded, re-flashed twrp and all is good now. I think I just really pissed it off this time...
I'll gather up the nerve to make another go at this when I get home. Thanks for all your work on these ROMs!
Flashed this over 10.1 unofficial... Got the dreaded Signature mismatch. Help?
Wiped the 10.1 and then flashed this rom. It is very smooth. Thanks !
No sound thru HDMI connection, is it a known problem ?
mujo32 said:
Flashed this over 10.1 unofficial... Got the dreaded Signature mismatch. Help?
Click to expand...
Click to collapse
What's the exact error you're seeing?
---------- Post added at 08:39 PM ---------- Previous post was at 07:58 PM ----------
So, gave it another go... correct version of everything this go around...
JB bootloader (OEM)
Verified unlocked bootloader.
TWRP 2.6.0.0 JB
On boot:
'no certificate to inject'
Signature mismatch
Booting failed
Unrecoverable bootloader error (0x00000008).
No bueno.
On the positive side though... I'm getting pretty efficient with nvflash... 10 minutes to recover this go around, haha.
demercie said:
No sound thru HDMI connection, is it a known problem ?
Click to expand...
Click to collapse
The sound threw hdmi is working for me.
bergoulle said:
The sound threw hdmi is working for me.
Click to expand...
Click to collapse
Which video player are you using ?
I am using MXPlayer.
bye.
So far good to me. Everything working fine at the moment.. I just miss the option to wake the device with a keyboard key.. thanks for the rom!
Enviado desde mi EPAD usando Tapatalk 4
demercie said:
Which video player are you using ?
I am using MXPlayer.
bye.
Click to expand...
Click to collapse
Ok guys, it now works, I just touch the volume rocket and it is now ok, software volume change was not having any effect
Nice and stable ROM, thx again !
BEFORE I EVEN BEGIN TO POST THIS, READ MY DISCLAIMER!
Your warranty is now void.
I am not responsible for bricked devices, dead SD cards,
thermonuclear war, or you getting fired because the alarm app failed. Please
do some research if you have any concerns about features included in this ROM
before flashing it! YOU are choosing to make these modifications, and if
you point the finger at me for messing up your device, I will laugh at you.
Submitting bug reports on nightly builds is the leading
cause of male impotence.
Ok, Lets begin!
So here is my story. I tried to sell off my Sprint LG G3 with a recovery of TWRP on it. I was able to trade with a nice woman for a Sprint Samsung Galaxy S5 in a nice shimmering blue color. About an hour past and she messaged me saying that the stock rom it was running had an update and she tried to update it and it booted into the recovery installed and then when she clicked the reboot tab it said '' NO OS INSTALLED''. I thought she was pulling my leg and then i went to meet up with her and she was serious. so we tried to install CM13(latest) and it keept only booting into recovery so we had to trade back untul i could fix it... Well i did, and i have found out this is a problem for many users. A soft brick and i found a way to fix it. AS LONG AS YOU CAN BOOT INTO TWRP AND USE IT, MY METHOD WILL WORK.
Step 1: Download these files
Recovery Fixer: http://www.mediafire.com/file/m4jzsb2qo4vnuy4/LGG3UNIVERSALFIXRECOVERY.zip
ROM: Coming When i get home
Step 2: Copy to an external SD Card or use the mtp function in the recovery to copy to the phone
Step 3: First Flash LGG3UNIVERSALFIXRECOVERY.zip
Step 4: Flash ROM
DONE