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
Related
I made a super stupid mistake yesterday. When I was getting all of the downloads together in preparation for flashing, I didn't notice that a link I'd followed lead me to the International forum, and now I've got a hard brick. I'm not quite sure why that's the case and I want to understand it more.
I've had a GTablet since day one so I'm familiar with the flashing process along with adb, but my experience yesterday has obviously lead me to want to be more cautious.
When I flashed the ROM from CWM it indicated that it was successful (and I'm sure from its point of view it was) but obviously the two phones have very different internals. I was under the impression that the ROM flash doesn't touch the bootloader, but obviously it did something that the phone didn't like. My best guess is that it screwed up the partition table for the emmc, but I'm concerned that that could irrevocably brick the phone. Does anyone have a technical explanation for what happened?
Second, while it was in CWM I may have had a chance of recovering, but once I rebooted it, it was over. No recovery, no download mode, no USB activity, just a brick. How can I be sure a future ROM flash is actually successful and the phone will still be able to boot properly? Is there a way of verifying other than rebooting and crossing your fingers? I don't really want to brick another one.
Yeah... MAKE SURE THE ROM IS FOR YOUR DEVICE BEFORE YOU FLASH IT!
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.
Few weeks back a friend asked me to root/put CM10 on his nook tablet, I of course said no and that he should do it himself. Anyways, about 5-6 double capt & cokes and naked pictures of his wife, he was the proud owner of a nook tablet running cm10.
Fastword to last weekend. The aforementioned wife apparently ran the thing down 0 battery. First it would only constantly loop the 'N' screen. After a night of charging it can now boot to CWM but thats it. Constant boot loop.
I was pretty drunk when I put cm on it so the exact process is what we will call 'A bit hazy'. Here is what I can tell you
* Has CWM 6.0.2.8 on emmc
* Cyanoboot
* was running a CM nightly
* I don't remember the naked pics
Failed fixes include
* MIndless wiping of cache/data
* flashing new nightly
Any thoughts? I was thinking about using AdamOutler's ubuntu recovery tool and set it back to stock..
Cheers
Can't help you much, but before using AdamOutler's method, run the repart.img to get back to stock. Easier and safer if it works. If it doesn't, well, then Adam's is waiting for you!
http://forum.xda-developers.com/showthread.php?t=1663836
Instruction in the link I provided is very detailed. Short version: Downolad the 1.42 recovery, unzip and burn an sd-card with the repart.img you will find in the extracted folder. Boot to that sd-card and a restore process will start. After a while (a few minutes?) a green checkmark hopefully appears. Pop out the card and the Tablet will reboot and finish the process and you're back to stock 1.4.0 or something like that. And then you can start over again with CWM and CM10...
asawi said:
Can't help you much, but before using AdamOutler's method, run the repart.img to get back to stock. Easier and safer if it works. If it doesn't, well, then Adam's is waiting for you!
http://forum.xda-developers.com/showthread.php?t=1663836
Instruction in the link I provided is very detailed. Short version: Downolad the 1.42 recovery, unzip and burn an sd-card with the repart.img you will find in the extracted folder. Boot to that sd-card and a restore process will start. After a while (a few minutes?) a green checkmark hopefully appears. Pop out the card and the Tablet will reboot and finish the process and you're back to stock 1.4.0 or something like that. And then you can start over again with CWM and CM10...
Click to expand...
Click to collapse
I appreciate your reply and will do that. I hve no intentions of getting him back to anything other than stock. That way when he/she breaks it, not my fault.
Thanks again .
If repart.img does not work for some reason, I'd suggest try flash_stock_1.4.2.zip posted at Succulent's SD-based recovery tool repo https://github.com/succulent/acclaim_recovery_sdcard.
@asawi
Your method worked perfectly. they are back to stock and no longer annoying me.
Cheers.
I have always been interested in playing around and modding my devices but I have never touched android because I have been scared about bricking my device and ruining a perfectly good piece of hardware. I thought I would make a post here and find out some things about android and rom development.
I have a nexus 7 2012 that I don't use a whole lot and I would love to play around with it and find out how everything works. I know how to install roms but I have never made my own. All the guides I see say stick to the instructions or you will brick your device. I did some research and found that most of the time people say bricked they mean soft bricked which can be fixed by booting into recovery mode and reflashing a stock rom. But I have also seen that you can hard brick your device and it can never be fixed.
What I wanted to know is how do I develop my own rom in a safe way that will not hard brick my nexus 7? What are the risks involved with flashing an untested rom? What is the recovery mode and is it possible to damage it while flashing a rom to the device?
I dont really mind my tablet being in an unusable state as long as I can recover it later by reflashing it.
I have just found that I can fix anything by reflashing with fastboot even if the recovery is gone.
Hi guys I want to post my experience for future reference. Bought this phone (in Athens, Greece) because it's crazy value for money. After a week or so I was really satisfied with it. Just wanted some more Marshmallow features, like multiwindow. So I did my research and ended up following a related guide : steps-to-root-moto-e-2nd ge n. Everything went well, I unlocked the bootloader, flashed twrp, the phone rebooted and I chose to flash SD card as internal, and I was able to install my apps and settings. Then again following the guide steps I tried to flash SuperSU. This resulted to an endless bootloop, where the message " YOU HAVE UNLOCKED THE PHONE S BOOTLOADER....." kept showing up. So I started reading related post from many forums, most of them reproducing the same solutions, like "find your phone's official firmware and reflash". I downloaded many firmwares, all of them appeared (to me at least) suitable for my phone, but none of them had any result. The bootloop continued. I couldn't even flash ROMS from SD card, obviously because of the internal memory format I had done the first and only time the phone booted. Two days had passed and I was really frustrated, ready to take it to service ( or throw it against the wall). Until now I didn't want anything else but the official firmware. But what the heck, after so much efforts, anger and disappointment there is nothing wrong in trying new things. So when I came across the guide about installing cyanogen 13 on my phone, I decided to give it a try. TOTAL SUCCESS!!!! Now my phone is really "flying", is really fast and the most important: is really working again. Although I went through a second flashing of cyanogen 13 because I had the lame persisting idea to flash SuperSU again, with the same frustrating results. So the bottom line, and the reason for this post is : do not flash SuperSU on this phone because you will soft brick it, and don't get caught up with a "hunt" for the right firmware, you will only loose time and some sanity. This is my advice: Go ahead and install cyanogen, it is really great and has insane features. Big thanks to all the guys developing and contributing, you really saved me big time!!!!
vagfyt said:
Hi guys I want to post my experience for future reference. Bought this phone (in Athens, Greece) because it's crazy value for money. After a week or so I was really satisfied with it. Just wanted some more Marshmallow features, like multiwindow. So I did my research and ended up following a related guide : steps-to-root-moto-e-2nd ge n. Everything went well, I unlocked the bootloader, flashed twrp, the phone rebooted and I chose to flash SD card as internal, and I was able to install my apps and settings. Then again following the guide steps I tried to flash SuperSU. This resulted to an endless bootloop, where the message " YOU HAVE UNLOCKED THE PHONE S BOOTLOADER....." kept showing up. So I started reading related post from many forums, most of them reproducing the same solutions, like "find your phone's official firmware and reflash". I downloaded many firmwares, all of them appeared (to me at least) suitable for my phone, but none of them had any result. The bootloop continued. I couldn't even flash ROMS from SD card, obviously because of the internal memory format I had done the first and only time the phone booted. Two days had passed and I was really frustrated, ready to take it to service ( or throw it against the wall). Until now I didn't want anything else but the official firmware. But what the heck, after so much efforts, anger and disappointment there is nothing wrong in trying new things. So when I came across the guide about installing cyanogen 13 on my phone, I decided to give it a try. TOTAL SUCCESS!!!! Now my phone is really "flying", is really fast and the most important: is really working again. Although I went through a second flashing of cyanogen 13 because I had the lame persisting idea to flash SuperSU again, with the same frustrating results. So the bottom line, and the reason for this post is : do not flash SuperSU on this phone because you will soft brick it, and don't get caught up with a "hunt" for the right firmware, you will only loose time and some sanity. This is my advice: Go ahead and install cyanogen, it is really great and has insane features. Big thanks to all the guys developing and contributing, you really saved me big time!!!!
Click to expand...
Click to collapse
There's an issue with SuperSU when it tries to install in systemless mode.
Flashing it this way seems to do the trick, and has been confirmed by multiple users on this board: http://androiding.how/root-moto-g-2014-marshmallow/
If you're using CM13, there is no need to flash SuperSU. CM13 has its own root pre-installed, you can turn it on in Developer Options.