Related
Hi i was wondering if there was anyone out there who was kind enough to explain in detail how to install this Rom because by the looks of the pictures and the reviews, it is a great Rom. OH and if there is an answer to this already, please direct me to it because i have searched for hours and cannot find anything.
Thanks in advance
How far is your knowledge when it comes to custom ROMs? Do you have your phone unlocked?
If your phone isn't unlocked, go here:http://forum.ppcgeeks.com/showthread.php?t=20370
I could use a little help to. My phone is unlocked and I have flashed another rom before but when I download the rom file I can't do anything with it. I seem to remember using another program to handle the rom file before flashing but I have looked and looked and have come up empty handed. Someone pointing in the right direction would be great.
Basically I am stuck between getting the file on the computer and starting to flash. I can get my phone to the color screen and all.
Terms you should know before-hand, haha:
-The color RGB color screen is called the Bootloader mode (you get to it by holding the power button + camera button, and sticking you stylus in the slot at the bottom of you phone to reset.)
-Hard-reseting: Flashing the phone to default state of the flashed ROM. (Hold talk key + end call key, and sticking you stylus in the slot at the bottom of you phone to reset.)
-Soft-reseting: Simply restarting your phone. (Sticking you stylus in the slot at the bottom of you phone to reset.)
-------------------------------------------------------------------------
0. Unlock Phone. (http://forum.ppcgeeks.com/showthread.php?t=20370)
1. Go in to Boot-loader mode. (Text towards the bottom of the screen
should read "Serial" if you phone isn't connected to the PC.)
2. Connect phone to PC. ("Serial" text should change to "USB")
3. Extract the files from .rar file you download. (Use Winrar.)
4. Run ROMUpdateUtility.exe and follow the on screen instructions.
- Your phone will start showing a progress bar when the flashing starts.
- Once done, the phone will restart. (Should reset and windows should boot, but still do step 5.)
5. Hard-reset the phone.
6. Dance in place.
-------------------------------------------------------------------------
*pants* Hope that helps!
Stickfigure, thanks a bunch for your summary of the ROM loading process! My Sprint Touch has been giving me lots of problems (freezing on incoming calls, data connection stops working randomly, phone not wanting to get out of roam and back into EV mode, and many many more). Needless to say, it is frustrating and I want to throw it at a wall. I'm sure my reset button is going to fail since I've poked it so many times.
Anyways, I've been wanting to install a custom ROM and finally have the chance during my spring break from classes, but I wasn't quite sure how to do it. Your post definitely helps.
One more question...is the process basically the same if I want to install a different custom ROM? If you know of any other tutorial or noob info pages that might help me I'd appreciate it too.
Thanks again!
Stickfigure, thanks for the instructions. Winrar was the piece that I was missing. Once I installed that I had the new rom installed the the phone was working fine in a bout 15 minutes.
hapa_dude said:
Stickfigure, thanks a bunch for your summary of the ROM loading process! My Sprint Touch has been giving me lots of problems (freezing on incoming calls, data connection stops working randomly, phone not wanting to get out of roam and back into EV mode, and many many more). Needless to say, it is frustrating and I want to throw it at a wall. I'm sure my reset button is going to fail since I've poked it so many times.
Anyways, I've been wanting to install a custom ROM and finally have the chance during my spring break from classes, but I wasn't quite sure how to do it. Your post definitely helps.
One more question...is the process basically the same if I want to install a different custom ROM? If you know of any other tutorial or noob info pages that might help me I'd appreciate it too.
Thanks again!
Click to expand...
Click to collapse
There are some great tutorials out there for beginners, one of the best of which is Dharvey's "UPDATED- CONSOLIDATED Rev A./GPS TUTORIAL" found on PPCGeeks; it is no longer available for some reason, but you may be able to find a repost somewhere.
Thanx
Thankx every one who contributed to this thread because it really helped.
Hi all, many users have this issue and no solution was found up till now.
When you replace your Galaxy Grand Duos I9082 screen, most of replacement screens will cause a problem, making the phone enter SAFE MODE every time you start it. There is no possible way to fix it using button combinations, battery out/in again, power off/on, etc etc etc.
The problem of having the phone into SAFE MODE is that it only shows system apps, not downloaded ones.
That is really annoying !!
I am requesting help with two possible solutions:
Solution Request 1:
I assume SAFE MODE functionality could be disabled by someone with ROM programming knowledge. This would be of much help for all the users having the same issue than me.
Solution Request 2:
I have rooted my phone and as part of the process, the SuperSU app was installed and is now showing on my device.
Is there a way to set other apps as SYSTEM APPS? (remember I can't install any apk from market or any other place.
I am trying to install apk's directly from RECOVERY MODE (like SuperSU) but couldn't find a way up till now.
I tried to rename Whatsapp.apk to .zip and tried to install it from SD card in RECOVERY MODE but I get a Signature error.
Any help on this?
Thanks all for the help !!!!
Gerardo
31-03-2014 UPDATE: Finally, I flashed a new ROM and this FIXED the issue of the SAFE MODE !!
I used @k2wl firmware: http://forum.xda-developers.com/showthread.php?t=2279005
Even though, I am now having issue to enable 3G but it works fine in 2G (when enabling 3G, the operator signal comes in and out continuously).
glovagnini said:
Hi all, many users have this issue and no solution was found up till now.
When you replace your Galaxy Grand Duos I9082 screen, most of replacement screens will cause a problem, making the phone enter SAFE MODE every time you start it. There is no possible way to fix it using button combinations, battery out/in again, power off/on, etc etc etc.
The problem of having the phone into SAFE MODE is that it only shows system apps, not downloaded ones.
That is really annoying !!
I am requesting help with two possible solutions:
Solution Request 1:
I assume SAFE MODE functionality could be disabled by someone with ROM programming knowledge. This would be of much help for all the users having the same issue than me.
Solution Request 2:
I have rooted my phone and as part of the process, the SuperSU app was installed and is now showing on my device.
Is there a way to set other apps as SYSTEM APPS? (remember I can't install any apk from market or any other place.
I am trying to install apk's directly from RECOVERY MODE (like SuperSU) but couldn't find a way up till now.
I tried to rename Whatsapp.apk to .zip and tried to install it from SD card in RECOVERY MODE but I get a Signature error.
Any help on this?
Thanks all for the help !!!!
Gerardo
Click to expand...
Click to collapse
Its happening coz something is causing problem in u r mobile in normal mode so for safety its booting in SAFE MODE...Uninstall some apps which is not working properly or causing a conflict with normal operation and see if it works format u r external SD card...
If that doesnt work try to flash a ROM and see.. U can't just change the extension and make it a flashable zip..There are procedured to make a app has CWM flashable directly if u do it u will get signature error has u r getting..
Try pushing apps apk into system through ADB. But this is only a temporary measure and you will soon run out of space
Sent from my GT-I9082 using xda app-developers app
Solution found at last
Solution is here
So don't worry guys anymore
It's not a big deal as some of you guys say
I had my touch replaced n had the same trouble
I simply switched it off n interchange both sims with each other (means put sim 1 into the slot of sim 2 n vice versa.)
It became OK
U can also try removing Sim 1 n letting the slot empty n using only sim2 in its slot
Ok, so lets start with hello you wonderful smart people
I did something very stupid and I'm really hoping there is a solution to my foolishness.
I have an LG G3 LS990, I had previously rooted and all was well. However, I decided I would flash a custom ROM after staying up all night. And in doing so I managed to take the steps terribly wrong, and I formatted the phone completely.
Along with this, I didn't realize at that moment that the phone was being it's finicky self, and had decided not to register as connected through ADB, and only connect enough to charge...
So, I've looked at pretty much everything that has to do with unbricking an LG G3 and it seems that without USB connectivity, I am pretty much boned. But I still have hope.
Basically where I'm at now is, I can turn the phone on, but all I see is the LG loading screen and nothing else happens until the battery dies, if unplugged.
I can use the volume up + plug in micro USB to reach the firmware upgrade screen, but I am unable to make either of my computers (windows 8.1 laptop/windows 10 desktop) register that it's connected through USB.
From what I can tell, the volume down + power, release at loading screen, repress volume down + power method doesn't seem to do anything besides turn on the phone and freeze at the loading screen.
So what I'm asking, essentially, is: Is there a magic method of making my computer recognize my shell of a phone that I haven't seen? because once I can do that, the firmware upgrade stock flash option becomes viable.
Thanks in advance for any help you guys and gals can give.
xSandmanx59 said:
I have an LG G3 LS990, I had previously rooted and all was well. However, I decided I would flash a custom ROM after staying up all night. And in doing so I managed to take the steps terribly wrong, and I formatted the phone completely.
Along with this, I didn't realize at that moment that the phone was being it's finicky self, and had decided not to register as connected through ADB, and only connect enough to charge...
So, I've looked at pretty much everything that has to do with unbricking an LG G3 and it seems that without USB connectivity, I am pretty much boned. But I still have hope.
Basically where I'm at now is, I can turn the phone on, but all I see is the LG loading screen and nothing else happens until the battery dies, if unplugged.
I can use the volume up + plug in micro USB to reach the firmware upgrade screen, but I am unable to make either of my computers (windows 8.1 laptop/windows 10 desktop) register that it's connected through USB.
From what I can tell, the volume down + power, release at loading screen, repress volume down + power method doesn't seem to do anything besides turn on the phone and freeze at the loading screen.
So what I'm asking, essentially, is: Is there a magic method of making my computer recognize my shell of a phone that I haven't seen? because once I can do that, the firmware upgrade stock flash option becomes viable.
Thanks in advance for any help you guys and gals can give.
Click to expand...
Click to collapse
Hah! I did this once not too long ago on another LG device. Easy to make a mistake when you're tired.
You'll need to use the key combo to get to TWRP (should be Power + Down). TWRP is capable of transfer through ADB and it will also recognize an external SD card if you put one in it. That would eliminate a few steps with checking drivers and such. So you can then move the ROM and Gapps to the internal SD card and install from there.
epidenimus said:
Hah! I did this once not too long ago on another LG device. Easy to make a mistake when you're tired.
You'll need to use the key combo to get to TWRP (should be Power + Down). TWRP is capable of transfer through ADB and it will also recognize an external SD card if you put one in it. That would eliminate a few steps with checking drivers and such. So you can then move the ROM and Gapps to the internal SD card and install from there.
Click to expand...
Click to collapse
Thank you for the response. It's a surprisingly easy error indeed. Since I posted this, I figured out the key press you mentioned and have been trying ROM after ROM intended for my phone specifically, yet all of them will end one of 3 ways.
I get a black screen with itty bitty little text saying fastboot mode and restart.
I get everything ready and I boot up, it loads until about the wifi set up and then it will either freeze for a couple seconds and go to a black screen which requires a battery pull.
Or, I get a bsod with the options of volume up = dload and volume down = reboot.
So far I've tried candy5, CM 12.1/11, blisspop, paranoid android, cloudy, and dirty unicorn.
Not sure what I'm doing wrong with these. I use TWRP to wipe everything except external sd, install from there, reboot, and repeat.
I fixed it!! thanks to http://forum.xda-developers.com/sprint-lg-g3/development/rom-stock-zv6-base-odex-deodex-t2949087
this ROM is the only one I could find that worked. I'd still love to be able to upgrade to L but it seems like all of the 5.x roms crash during setup. Not sure what this is due to, but I have a working phone, so I'm not too upset by it.
If anyone has any info on why all the lollipop ROMs are having trouble on here I would appreciate it much.
Well it WAS fixed.... All was fine and well until there was a software update, I clicked install, it tried to reboot, and now I'm stuck in a custom recovery boot loop. I still can't connect to either of my PCs by USB and using my SD card to flash ROMs isn't doing anything now, just boots straight into TWRP every time, after full wiping and re-flashing several times now I'm really not sure how to fix this one.
Update:
Got past the bootloop from another thread on here which had a flashable fix. Now that I did that I'm actually able to use 5.x ROMs it seems. Currently working on Blisspop 3.5, once I get GAPPS to flash correctly, I think I aughta have a working Lollipop phone
Make sure you are using the correct TWRP for your device, having Bumped, as needed. Also, make sure you use the correct version of Gapps; it matters based on the version of Android your ROM is based upon.
Good luck and enjoy!
Good points. From what I can tell I have gotten everything to remain stable now. Blisspop 3.5 and the CM 12.1 GAPPs from http://wiki.cyanogenmod.org/w/Google_Apps seem to be the winning combo. The GAPPs that was listed in the Blisspop thread as the "best" seems to be the reason that my previous flash attempts were crashing upon boot. It might be one of the 86 different apps that were included in there rather than the simple 12 of the CM 12.1 GAPPs.
Either way. I've had no issues now except for the previous issue of USB debugging simply refusing to work. I have installed the latest drivers for LG devices and have tried every article's suggestions I could find on how to make my phone be recognized. I've also tried a few different root required apps that are supposed to fix issues of USB connections. None of them seem to do anything. I've also tried different cords, different plugs and different computers. But it seems like the only kind of USB recognition for my phone is when it's off it can charge. It won't charge while it's on unless I've charged it a minimum of 2% while it was off (regardless of the current battery level) and it can't be recognized as a USB device at all.
Any advice for this? Thanks in advance.
xSandmanx59 said:
Good points. From what I can tell I have gotten everything to remain stable now. Blisspop 3.5 and the CM 12.1 GAPPs from http://wiki.cyanogenmod.org/w/Google_Apps seem to be the winning combo. The GAPPs that was listed in the Blisspop thread as the "best" seems to be the reason that my previous flash attempts were crashing upon boot. It might be one of the 86 different apps that were included in there rather than the simple 12 of the CM 12.1 GAPPs.
Click to expand...
Click to collapse
It seems like the trend with ROM publishers is to not update some of those details in the threads; in the VZW variant, I know the BlissPop title still reads 5.0.x when they have been on 5.1 for some time.
I have tried a bunch of packages and have been using the Slim Gapps zero package + the DPI mod for a while now. They work great; there is even a tutrorial on how to roll your own if you like to have somewhere between 12-86.
xSandmanx59 said:
Either way. I've had no issues now except for the previous issue of USB debugging simply refusing to work. I have installed the latest drivers for LG devices and have tried every article's suggestions I could find on how to make my phone be recognized. I've also tried a few different root required apps that are supposed to fix issues of USB connections. None of them seem to do anything. I've also tried different cords, different plugs and different computers. But it seems like the only kind of USB recognition for my phone is when it's off it can charge. It won't charge while it's on unless I've charged it a minimum of 2% while it was off (regardless of the current battery level) and it can't be recognized as a USB device at all.
Any advice for this? Thanks in advance.
Click to expand...
Click to collapse
Some troubleshooting questions:
I think your OS may not supported for Android SDK. Have you ever had it recognized on these machines through ADB before? Windows takes like 5 years to get to the point where most of the drivers work.... I know it's possible in Win7 at this point, but I wouldn't expect it to work in 8.1 or Win10. Someone else who uses it may be able to help with that.
What are the driver's requirements? These are more variables associated with Windows...
Have you enabled USB debugging in the ROM, via the Developer menu? Many ROMs still have this hidden by default.
What version of the Android SDK/Studio are you running?
Have you added the platform-tools to the SDK, as required?
Can you get ADB to recognize the device when you connected and are in TWRP?
epidenimus said:
It seems like the trend with ROM publishers is to not update some of those details in the threads; in the VZW variant, I know the BlissPop title still reads 5.0.x when they have been on 5.1 for some time.
I have tried a bunch of packages and have been using the Slim Gapps zero package + the DPI mod for a while now. They work great; there is even a tutrorial on how to roll your own if you like to have somewhere between 12-86.
Some troubleshooting questions:
I think your OS may not supported for Android SDK. Have you ever had it recognized on these machines through ADB before? Windows takes like 5 years to get to the point where most of the drivers work.... I know it's possible in Win7 at this point, but I wouldn't expect it to work in 8.1 or Win10. Someone else who uses it may be able to help with that.
What are the driver's requirements? These are more variables associated with Windows...
Have you enabled USB debugging in the ROM, via the Developer menu? Many ROMs still have this hidden by default.
What version of the Android SDK/Studio are you running?
Have you added the platform-tools to the SDK, as required?
Can you get ADB to recognize the device when you connected and are in TWRP?
Click to expand...
Click to collapse
Thank you for the response. I have noticed that a few small things are not so frequently updated in the copy/paste updates of the ROM threads. But that's to be expected =P Anyways, to answer your questions:
What are the driver's requirements? These are more variables associated with Windows...
I'm not entirely sure about this one. I know I found the drivers on the LG website for my LS990 model and I also installed a few others including older/latest/various models to test if any of them would work. I'm running windows 8.1 currently and the ls990 seems to have a little less support as the PC suite for LG doesn't include this model in their driver list.
Have you enabled USB debugging in the ROM, via the Developer menu? Many ROMs still have this hidden by default.
Yes, it's been a long running issue on stock, stock rooted, and blisspop all with debugging on. I was able to connect to both of my computers for a long while until one day it just stopped. It was much worse than it is now. For a few days, then it decided to charge up to about 4% when I plugged it in with no battery and then put the battery back and waited for about 3-4 hours. Then I could turn it on long enough to selectively power down and it would then charge while powered off. Over the past couple days I've been able to plug it in and reboot to get it charging again... So bothersome. As for USB debugging, not sure when it stopped exactly but I assume it was around the same time (2 months ago)
What version of the Android SDK/Studio are you running?
I have the latest version of android studio from their website.
Have you added the platform-tools to the SDK, as required?
Yes, I believe so. I'm not 100% on the SDK stuff.
Can you get ADB to recognize the device when you connected and are in TWRP?
No. There is no response from my computer at all during any of the stages of driver and twrp and studio installations. Nothing is listed in my device menu either.
Beyond this, today my phone ran out of battery while I was out and about and then has refused to charge by any method. Then I finally got it to turn on to power down etc so it would charge about 3 hours later. Once I was able to boot back up I went out to smoke and came back to my phone somehow automatically flashing a different version of blisspop that had something about user_modified in the file name which then unloaded all of my saved layouts and whatnot. After about 20 minutes of reorganizing it went black, and has since been locked in a bootloop which has survived full wipes and re-installations of the previous version of blisspop I had been using. I just downloaded the latest version for ls990 once more, and I'll report back with whether or not that fixed the issue at hand.
Need desperate help with a MediaTek clone of S4
Hi everyone,
I will try and keep it short but last night I was badly scammed by a wonderful specimen of the human race, who wanted to sell his old Samsung S4. Turns out:
1. Its a mediatek clone
2. It has more issues than anticipated but all buttons work.
3. Seem to be soft bricked
Now I am facing nothing but patience to try and fix it. What works:
1. All buttons seem functional.
2. The phone boots into normal mode where I have only empty screen with a Phone app. The Phone app opens I can enter digits but cannot dial.
3. I can reboot into Factory mode - I performed all the tests of the device and all were a PASS. I heard the sounds, checked the cam, everything seems to be perfectly working. Touch scree, camera, sound etc. Even noticed it had FM.
I tried booting in Download Mode - no success. I get the dead Android image and it just hangs there. I can easy reboot though.
My PC recognizes the device and opens a media (empty) device folder.
I tried thus far to use SP Flash but....I dont know how to. Nothing is happening.
Of course I spent 6 hours waiting on different stock ROMs for S4 before realizing its a MediaTek device.
And now, here I am desperately asking if anyone could help me, if there is a chance to remedy that situation of mine. I dont need the phone to do anything special. The closer it is to a Samsung Android ROM - awesome. If its other, I dont mind at all. So long as it works and has access to Google Play Store.
Thank you geniuses and wonderful people for any hint you might have.
Hi
I had a similar issue couple of yrs ago with an S3 clone.
First thing u need to knw is the mtk version, memory details (RAM & ROM) and screen resolution to find a suitable OS version.
If ur lucky, ull get the stock ROM from the manufacturer on Google or else ull hafta search on xda, needrom, or the Chinese forums. Most of such devices don't have a lot of development so ull hafta port ROMs so a custom recovery will b helpful
Hope these points help
Sent from my YU5510 using Tapatalk
Ok.
So I need:
Device RAM
Device ROM
Mtk Version
I think I can extract these from the Factory Mode. Will check.
Then I need to get the stock ROM (hopefully) or search for a custom ROM. (Manufacturer I suppose we talk about MediaTek and not Samsung?)
Custom Recovery - yeah, usually this is the first thing I install but how do I do this on a cloned mtk? I suppose ODIN wont work. Can you lastly point me to a link or name of software to use instead of ODIN? (or will it work with ODIN?)
Hello all,
I have a hard bricked S4 mini i9195
I did try a few debrick.img I found in the internet, but nothing worked for me. The phone itself shows on PC with the known QHSUB_DLOAD and it also vibrated, when I loaded the battery. I think the vibration was a sign "battery fully charged".
So I think (and hope) that it is possible to revive it.
As far as I know, you can extract the debrick image from a dump-file using a corresponding, working phone. (with the 'dd'-file and then create the debrick.img). The version of the debrick has to be a perfect match to the former installed version on the smart phone.
Unfortunately I don't have a second corresponding phone. So I wonder, whether it is possible to build a debrick image from an original stock-rom. So that I could - step by step - go through all the different versions and see what works for me.
Does anyone of you guys know, how this works?
Regards,
Andreas
I would also like to know. Anyone?
Andreas-87 said:
Hello all,
I have a hard bricked S4 mini i9195
I did try a few debrick.img I found in the internet, but nothing worked for me. The phone itself shows on PC with the known QHSUB_DLOAD and it also vibrated, when I loaded the battery. I think the vibration was a sign "battery fully charged".
So I think (and hope) that it is possible to revive it.
As far as I know, you can extract the debrick image from a dump-file using a corresponding, working phone. (with the 'dd'-file and then create the debrick.img). The version of the debrick has to be a perfect match to the former installed version on the smart phone.
Unfortunately I don't have a second corresponding phone. So I wonder, whether it is possible to build a debrick image from an original stock-rom. So that I could - step by step - go through all the different versions and see what works for me.
Does anyone of you guys know, how this works?
Regards,
Andreas
Click to expand...
Click to collapse
I may have figured out how to make your debrick.img from your stock ROM. Please see this link. Let me know if it works: http://forum.xda-developers.com/showpost.php?p=66593246&postcount=2