Hi there , after soft bricking my phone intentionally because i wanted to downgrade form O to MM which i thought it would be relatively easy to find a stock firmware(the full one) well ...(i was wrong), Xda is not as content rich as you may think, and no one seems to offer any advice or answer for that matter, compared to other forums it lacks a lot.
After flashing more than 5 corrupted firmwares i found one that is working perfectly fine.
Steps:
1-Enter fastboot ( power + vol up)
2- Run (flashall_AFT.cmd) , download link below.... (this is the full firmware no bull**** no missing files) .
That's it... piece of cake
First impression: the bass is more rich and vibrant as many have said so cause the O version was an absolute rubbish like it's battery life , i'm yet to see the battery performance on this MM and i'll be updating the thread with SOT SS after flashing Magisk and installing debloater module.
Download link :
<Mod edit: Link removed>
There are some other newer N full versions but i haven't tested them.
[
i already had that file which i got a few months ago but never used it. i was a noob about this zenfone.
but ur title says its mm, its not , its nougat, 7.11. its the last nougat b4 oreo was released, it uses the same base fw, iirc, as my post about manually flashing 7.11 but without the radios, https://forum.xda-developers.com/zenfone-3-zoom/how-to/manually-update-to-7-11-t3815703
my memory could be wrong though, but file name suggests its 7.11
- [firmware27]WW_ZE553KL_71.60.139.30_MR4_user_20180306173656_release.zip
long story short i eventually flashed it a couple of weeks ago, it does flash successfully, well most of the time, and looks legit, i just wish i knew its original source, i think it was someone named marco, as theres lots of files within that zip.....but it seems legit.
but why are u hosting it on the clickbait site. i might up it to androidfilehost which is a no bs hosting site.
i did create a twrp flashable full stock 6.01 mm firmware, im still testing it as it doesnt always flash completely in twrp, about 8 out of 10 times it flashes correctly. but its hard to test on a dead no display/no touch screen phone
edit: correction, not clickbait, but need to signup
vincom said:
[
i already had that file which i got a few months ago but never used it. i was a noob about this zenfone.
but ur title says its mm, its not , its nougat, 7.11. its the last nougat b4 oreo was released, it uses the same base fw, iirc, as my post about manually flashing 7.11 but without the radios, https://forum.xda-developers.com/zenfone-3-zoom/how-to/manually-update-to-7-11-t3815703
my memory could be wrong though, but file name suggests its 7.11
- [firmware27]WW_ZE553KL_71.60.139.30_MR4_user_20180306173656_release.zip
long story short i eventually flashed it a couple of weeks ago, it does flash successfully, well most of the time, and looks legit, i just wish i knew its original source, i think it was someone named marco, as theres lots of files within that zip.....but it seems legit.
but why are u hosting it on the clickbait site. i might up it to androidfilehost which is a no bs hosting site.
i did create a twrp flashable full stock 6.01 mm firmware, im still testing it as it doesnt always flash completely in twrp, about 8 out of 10 times it flashes correctly. but its hard to test on a dead no display/no touch screen phone
Click to expand...
Click to collapse
Yeah i saw your post a couple of days ago and it is legit , about the file hosting it's not clickbait it's just 4shared and this little guy is older than the xda :laugh::laugh: , i agree that the androidfilehost is faster and more convenient but i'm not the uploader , i just copied it from another source, it would be great if you re-upload it for others and i will update the link.
Now we come to testing: i tested this myself and it is 6.0.1 for sure but i don't remember which release it was cause i updated to 7.1.1 20.32.67.25 release for various reasons, mainly for battery life (spoiler: not much difference and it's still poor) and i will keep flashing / debloating apparently in (in search of incredible) but i'm quite sure this phone is hopeless without a custom ROM from scratch as the amount of services and wakelocks are enormous.
Why don't you participate and use your knowledge in the "allegedly upcoming" Lineage 15.1 hopefully we get a working build before the end of the year :cyclops: i'm sure you are aware of the situation.
And if you're into kernels then kernelwise this phone's kernel was made by noobs ,ASUS put an AMOLED display and they are not using it's features as the blacks are lit and power consumption by the screen is well above an LCD one of the same size.
Long story short buying this phone was/is a mistake.
I actually found the site firmware27 that was hosting 8 ww fw and a couple of cn and jp sku fw.
I tested all 8 ww skus, only 2 work without effort, 6.0.1 dated deb 2017, and the 7.1.1 which I had from a couple of months ago and use the img files in my other thread and which i though u linked here.
Ill be posting a thread and links to both of these files that i ul to afh, and my usage of them, I came to the conclusion that they are asus's fw given to their authorized service centers, they include everything not even available through asus's fw from their site.
Too bad he got most of the files corrupted when he ul'd them to g-drive, my guess
at least now we got 2 fw files to work with, but its a pia to make it a twrp non wipe flashable zip, beyond my skills at this point in time.
edit: i have the one u have linked here which i got a couple of months ago, WW-ZE553KL-11.40.86.71-MR0-user-20170410214554-release.zip,
but firmware27 doesnt have it, and i cant remember where i got it, and by its date youre correct it must be 6.0.1, nougat fw starts with "V20".
so there are actually 3 working fastboot flashable FW out in the wild, boy arent we lucky
i have this phone because a couple of months ago i helped my friend flash fw on it because he was getting poor data signal, i soft bricked and had to learn how to unbrick it, which i did.
its mine as a couple of weeks ago, he dropped it a few feet onto ceramic floor and the screen is dead, no display, no touch, lcd is cracked under the top glass which actually has no cracks, and thats how im using it lol.
i was going to use it as a security camera but i had to learn how to control it remotely, which i did, that was a flashing adventure w/out a working screen
vincom said:
I actually found the site firmware27 that was hosting 8 ww fw and a couple of cn and jp sku fw.
I tested all 8 ww skus, only 2 work without effort, 6.0.1 dated deb 2017, and the 7.1.1 which I had from a couple of months ago and use the img files in my other thread and which i though u linked here.
Ill be posting a thread and links to both of these files that i ul to afh, and my usage of them, I came to the conclusion that they are asus's fw given to their authorized service centers, they include everything not even available through asus's fw from their site.
Too bad he got most of the files corrupted when he ul'd them to g-drive, my guess
at least now we got 2 fw files to work with, but its a pia to make it a twrp non wipe flashable zip, beyond my skills at this point in time.
edit: i have the one u have linked here which i got a couple of months ago, WW-ZE553KL-11.40.86.71-MR0-user-20170410214554-release.zip,
but firmware27 doesnt have it, and i cant remember where i got it, and by its date youre correct it must be 6.0.1, nougat fw starts with "V20".
so there are actually 3 working fastboot flashable FW out in the wild, boy arent we lucky
i have this phone because a couple of months ago i helped my friend flash fw on it because he was getting poor data signal, i soft bricked and had to learn how to unbrick it, which i did.
its mine as a couple of weeks ago, he dropped it a few feet onto ceramic floor and the screen is dead, no display, no touch, lcd is cracked under the top glass which actually has no cracks, and thats how im using it lol.
i was going to use it as a security camera but i had to learn how to control it remotely, which i did, that was a flashing adventure w/out a working screen
Click to expand...
Click to collapse
All you need is one fw to start with and after that you can update to whichever release you want without any problem , strait forward from asus site and update via sd card even if it's rooted or bootloader unlocked, you can do anything and even get updates as FOTA app works as soon as you boot cause asus update procedure is very primitive HOWEVER it should be on stock recovery and honestly twrp is pretty much useless here and i didn't seem to need it in anything with this device!! (i use magisk to root), it's not like there's half a dozen of custom ROMs to flashed , the only possible modification is within the stock fw and that's our limit.
If you find a screen replacement under 50$ it is worth it , i knew that 2.5D glass is poor engineering and very fragile, so screen protector and case was crucial since day 1.
Notes:
Don't trust asus download center's description cause i downloaded the latest nougat release before the Oreo (as described in their section) and it turned out to be the first release of their lousy O fw.
cheapest on ebay is over $70can for aftermarket from china. cheap clone? idk
i'll stick w/my note 4 can version as my dd.
i'll upload the working fw i found for redundancy and to give users more options, 4 fw as of now.
i do have the last 7.1.1 b4 oreo
these are actual service tech fw's available to them for restoring phones. supposedly can be use by asus flash tool which i haven't used yet.
they dont change the bootloader lock status or the frp/google account status (to do that use fastboot wipe config)
since it is in a raw format the individual files can be flashed via fastboot for those that would need it.
fyi all fw are exactly the same except for the recovery, boot, system and , emmc_appsboot_8953.mbn(bootloader ?), the radios and other files are the same
i cant use the builtin updater because i cant seem to get the right button combo to work in stock recovery to flash the update and thats after i reinstall the stock recovery and remove root, flashing from bootloader is a breeze.
the only one i can't get adb enabled so i can mirror the screen is the mm 11.40.86.71, the same one you have linked here
when i try to make a custom stock flashable rom it always fails to boot, would u know why?,
vincom said:
cheapest on ebay is over $70can for aftermarket from china. cheap clone? idk
i'll stick w/my note 4 can version as my dd.
i'll upload the working fw i found for redundancy and to give users more options, 4 fw as of now.
i do have the last 7.1.1 b4 oreo
these are actual service tech fw's available to them for restoring phones. supposedly can be use by asus flash tool which i haven't used yet.
they dont change the bootloader lock status or the frp/google account status (to do that use fastboot wipe config)
since it is in a raw format the individual files can be flashed via fastboot for those that would need it.
fyi all fw are exactly the same except for the recovery, boot, system and , emmc_appsboot_8953.mbn(bootloader ?), the radios and other files are the same
i cant use the builtin updater because i cant seem to get the right button combo to work in stock recovery to flash the update and thats after i reinstall the stock recovery and remove root, flashing from bootloader is a breeze.
when i try to make a custom stock flashable rom it always fails to boot, would u know why?,
Click to expand...
Click to collapse
I would say let's find a solution to the easy problem and not the to hard one, you want to take 2 blurry steps instead of 2 obvious ones !! i can help you with stock ones just explain more what's the exact problem ? i didn't understand so correct me if i'm wrong : you have no visual indication as the screen is dead right ? or can't boot into the stock recovery at all ?
if you have the bootloader unlocked and no screen indication :
power up wait for the vibration and press volume down 4 times then press power to boot into recovery
wait 10 sec and press volume down 2 times to (update form sd card)
rename the fw .zip file to A so it can be sorted first and it should be in root directory and alone to prevent any miss hits and press volume down 1 time.
and if that didn't work just flash the fw that's provided and redo the steps if you want to update , congratulations now you have a working internals and up to date phone that you can't even boot into it's home screen cause the boot confirmation by email and password is near impossible to bypass without a working display. (there is some methods though )
I don't see the point of a phone without a display at least temporary.
This phone is a joke in it's normal condition let alone in the non , don't waste your time and sell it as parts, if you get 40$ take it.
sam.fisher190 said:
I would say let's find a solution to the easy problem and not the to hard one, you want to take 2 blurry steps instead of 2 obvious ones !! i can help you with stock ones just explain more what's the exact problem ? i didn't understand so correct me if i'm wrong : you have no visual indication as the screen is dead right ? or can't boot into the stock recovery at all ?
if you have the bootloader unlocked and no screen indication :
power up wait for the vibration and press volume down 4 times then press power to boot into recovery
wait 10 sec and press volume down 2 times to (update form sd card)
rename the fw .zip file to A so it can be sorted first and it should be in root directory and alone to prevent any miss hits and press volume down 1 time.
and if that didn't work just flash the fw that's provided and redo the steps if you want to update , congratulations now you have a working internals and up to date phone that you can't even boot into it's home screen cause the boot confirmation by email and password is near impossible to bypass without a working display. (there is some methods though )
I don't see the point of a phone without a display at least temporary.
This phone is a joke in it's normal condition let alone in the non , don't waste your time and sell it as parts, if you get 40$ take it.
Click to expand...
Click to collapse
not impossible, very doable to use a phone even with a dead screen.
after alot of trials and error ...from a new flashed stock thats was completely wiped, i can get to a remotely controlled/viewed phone in about 10mins .
i will write up a tut on that.
i can get that done with all the availabe working raw fw except with the mm 2017/04 release
yes, i have a completely dead screen, no display, no touch. all other phone functions work.
the reason for stock recovery procedure was to update to oreo, but i really dont care if i get it. just seeing if its doable.
playing with it for giggles, going to be a security camera as the cam is vg, useless as a phone that has no working screen.
i can be the sacrificial tester if need be, pretty hard to hardbrick this phone as i also have the back cover off so to disconnect the battery connector for those hard soft brick occasions and/or to make sure phone was completely off b4 doing something
I think I killed my phone please help Asus ze553kl
This was happened my phone is Asus ze553kl android Oreo NOTE: I already rooted my phone unlocked bootloader using Asus tool installed twrp and magisk...
when I was using whatapp suddenly my screen got frozen and I restarted my phone it stuck in Asus logo I tried does it goes into twrp even twrp also stuck in logo then I tried flashing using adb and fastboot while doing that I entered this COMMAND fastboot format or erase boot after I flashed everything I rebooted this time it gone worse there is no logo I see only powered by android then no hope after I saw this thread and planned to downgrade downloaded 2gb file and I made clean flashing manually no use i don't see the logo again then I went for auto flashall command when I clicked that something happens it said searching for your device but
After waited for so long I unplugged the cable try to on the phone it's fully blank no sign of power pls help guys I'm begging you all please reply and give me a solution
Nikido2930 said:
This was happened my phone is Asus ze553kl android Oreo NOTE: I already rooted my phone unlocked bootloader using Asus tool installed twrp and magisk...
when I was using whatapp suddenly my screen got frozen and I restarted my phone it stuck in Asus logo I tried does it goes into twrp even twrp also stuck in logo then I tried flashing using adb and fastboot while doing that I entered this COMMAND fastboot format or erase boot after I flashed everything I rebooted this time it gone worse there is no logo I see only powered by android then no hope after I saw this thread and planned to downgrade downloaded 2gb file and I made clean flashing manually no use i don't see the logo again then I went for auto flashall command when I clicked that something happens it said searching for your device but
After waited for so long I unplugged the cable try to on the phone it's fully blank no sign of power pls help guys I'm begging you all please reply and give me a solution
Click to expand...
Click to collapse
sounds like a hardware failure not a software/firmware problem, let it rip, time for another phone, phone not worth getting it repaired even if u do it yourself
vincom said:
sounds like a hardware failure not a software/firmware problem, let it rip, time for another phone, phone not worth getting it repaired even if u do it yourself
Click to expand...
Click to collapse
sam.fisher190 said:
Hi there , after soft bricking my phone intentionally because i wanted to downgrade form O to MM which i thought it would be relatively easy to find a stock firmware(the full one) well ...(i was wrong), Xda is not as content rich as you may think, and no one seems to offer any advice or answer for that matter, compared to other forums it lacks a lot.
After flashing more than 5 corrupted firmwares i found one that is working perfectly fine.
Steps:
1-Enter fastboot ( power + vol up)
2- Run (flashall_AFT.cmd) , download link below.... (this is the full firmware no bull**** no missing files) .
That's it... piece of cake
First impression: the bass is more rich and vibrant as many have said so cause the O version was an absolute rubbish like it's battery life , i'm yet to see the battery performance on this MM and i'll be updating the thread with SOT SS after flashing Magisk and installing debloater module.
Download link :
<Mod edit: Link removed>
There are some other newer N full versions but i haven't tested them.
Click to expand...
Click to collapse
THREAD CLOSED and download link removed. 4shared.com requires to have an account for downloading i.e. not accepted as file host on XDA.
Please advise the moderators' team when ready to provide a download link from an accepted file host.
Related
I want to perma-unlock the sim so i wont have to use sprint because they suck eggs. But using a program called autorec, i am stuck in fastboot. I have tried the download thing where you power off and plug in the usb to get download mode, but as soon as it powers on it goes directly to fastboot or download mode pops up, then is sent directly to---YOU guessed it! FASTBOOOOOOOOT
So i need to go back to square one, and start from the very stock LG G2 Ls980, help will be appreciated. I will post links of guides i tried but led me to this problem. Also, anyone who would like to post a good guide, no problem, to unlocking the phone to be used on another rom such as AT&T or Tmobile, that would be fantastic. I want to get this phone up and working to replace an old phone, but sprint is a egg sucker.
http://forum.xda-developers.com/showthread.php?t=2729370
http://forum.xda-developers.com/showthread.php?t=2655133
http://forum.xda-developers.com/showthread.php?t=2715496
http://www.droidviews.com/install-twrp-recovery-on-lg-g2-running-android-4-4-2-kitkat/
BTW it is rooted already with ioroot. like i followed in the guide.
more information
Those all say
"fastboot mode started"
udc_start
reset
then just
portchange(where i was trying the download thing)
but it all ends in fastboot: processing commands
I have seen alot of other guides
I still need help, specific instructions for my device would be great. all the info in the first post.
For the speedy reply
I really ****ed it up now due to every flash to stock from fastboot menu on this site. It is black screen cant even access anything, no stock rom ANYWHERE ON THE INTERNET WTF and i am beyond irritated with how many inaccurate threads on this site. The phone altogether is really pissing me off. **** sprint for making their phones just as ****ty as every service they have.
ShawnBrazil said:
I really ****ed it up now due to every flash to stock from fastboot menu on this site. It is black screen cant even access anything, no stock rom ANYWHERE ON THE INTERNET WTF and i am beyond irritated with how many inaccurate threads on this site. The phone altogether is really pissing me off. **** sprint for making their phones just as ****ty as every service they have.
Click to expand...
Click to collapse
I work on that phone all the time and never remember seeing any threads for restoring via fastboot...? The preferred way is via kdz and the LG FlashTool. So once you power off and leave it off for like 30 secs then hold Volume Up and plug in the phone does not get you to Download Mode? Have not seen that one before...
As far as unlocking, especially if you aren't going to use Sprint again, I prefer to use one of the roms that is based off GSM with the Sprint kernel so it'll boot. I like the Energy rom for 4.2.2. Works and looks great. Have installed it for quite a few customers and have never had a complaint (well, one wasn't a fan of the dark theme, but can't please em all...) or anyone bring it back to me. There is a newer one that is like a stock rom but 4.4.2. Haven't tried that one since I like to stick with what I know works and haven't had enough chance to test the new one.
The steps I take are:
Use LG FlashTool to go back to ZV7 update
Root with ioroot (at leave version 22 and 25 works too)
Use Flashify to install the loki-ed TWRP 2.6.3.3
Reboot to recovery
Install Energy rom and ZV8 radio (must flash radio or it will not boot)
...
Profit!
PS: If you need NFC, there's a separate zip to flash.
I have everything for this operation uploaded to my Mega account and have performed it remotely. If you're just completely stuck and you can still get into Download mode, let me know and I can help with whatever else you need.
I picked up this device from walmart for $29.99 with the intentions of learning some new development stuff.I
thought for 30 bucks there's gonna be a lot of these little "duallies" running around why not a cheap candidate?
So far as i can tell there is little info found about this device so I'm looking to collect what little is known about
it in one place in hopes to get a jump on it. First things first, I am responsible for my own actions as you are yours.
If your not sure ask or simply dont do, some of this stuff can brick your device!
*ROOT*
These are the instructions I followed to root.
http://www.androidarea51.com/all-things-root/working-root-for-lg-optimus-fuel-woot/
dont forget to install supersu
https://play.google.com/store/apps/details?id=eu.chainfire.supersu&hl=en
and busybox afterwards!
https://play.google.com/store/apps/details?id=stericson.busybox&hl=en
*RECOVERY*
Downloaded "TWRP Manager" from play store.
twrp settings, I enabled the sd card patch.
Install twrp\device name :l34c\version i instaled: openrecovery-twrp-2.8.4.0-l34c.img
click install... wait... things will pop up..... things will go away... wait some more...
finally a dialogue that states sucess.
***ISSUES HAVE BEEN REPORTED OF LOSING RECOVERY OR THE ABILITY TO ENTER IT AFTER
A WIPE AS WELL AS PROBLEMS BACKING UP AND OR RESTORING.
I have "injected" twrp manager into the system using titanium backup (link2sd will work also). This seems to
prevent any issues I have read about previously mentioned. Also I have successfully preformed backups as
well as restores, both before and after wiping. I have not figured out how to enter twrp recovery upon boot
yet, so be careful of what you do!
*SAFE TO REMOVE APPS*
yet to come
I use "titanium backup" from the play store, still trimming.I can get it down to about 230MB
available "free" ram at the moment but not consistently.
Ok had an issue with a task manager improperly reporting free available ram... true availability was
around 150mb free. There are apps that have to be replaced when removed, for example a launcher
for a launcher but some do not. Again I'm still trimming and experimenting, right now my system rom
around 244mb free. Most every thing I have done has been on the phone its self without the need of a P.C.
*STOCK BACK UP*
Yet to come
Any candidates for a true stock rom? Ive hacked the crap out of this one so far without the need of a back up... i know tisk tisk tisk!
I'm going for a debloated deodexed stock rom, hopefully!
*DRIVERS*
The only ones I could find that actually work. The Verizon drivers mentioned for the g2, not surprising since it runs on vz towers!
http://forum.xda-developers.com/showthread.php?t=2432476
*TETHERING*
using the android wifi tether 3.3beta2
https://code.google.com/p/android-wifi-tether/
all settings untouched except
device profile
lg optimus 3d
device access does work as well as encryption
*XPOSED*
Does work, im using 2.6.1.
*DPI*
The app I'm using for safe keeping to test dpi settings
https://play.google.com/store/apps/details?id=com.oumugai.densityadjuster
200 not working
170 works
160 native
150 works
140 works
130 works
120 works (looks good)
110 works
Temporarily went back to native dpi for debloating purposes. Will revisit later.
After messing with DPI settings I'm having a"contacts has stopped working " when tapping on the phone app.
DPI set to 120 when I noticed. All dpi switches affect lg home launcher
so you will need another launcher.
ok so far thats what i got. whats the nexts step to a stock AOSP rom?
questions and/or constructive comments wecome
reserved
I've got a few of these that are bootlooping. They show the LG logo, and then TracPhone Wireless splash screen infinitely in a loop.
Two questions.
1 - Is there any way to recover them? I'm hoping for some sort of a dev tool that I could flash a stock image or something (like Odin is for Samsung phones)
2- When these phones started bootlooping, I installed TWRP on the other Fuels that I have, thinking that I didn't want it to happen to them. My understanding of the TWRP that's installed from TWRP manager doesn't flash a modified boot image, so you can't enter TWRP from a powered off (or in my case, bootlooping) phone. Is that correct? I flashed a custom boot image from elsewhere that allows me to tap vol up at the LG logo to boot to TWRP. Any idea if this is enough of a safeguard to in the even of similar boot loops?
Any chance you know how to get it in diag mode? I need to connect it to DFS but can't without diag. Thanks for your help!
DrPhant0m said:
I've got a few of these that are bootlooping. They show the LG logo, and then TracPhone Wireless splash screen infinitely in a loop.
Two questions.
1 - Is there any way to recover them? I'm hoping for some sort of a dev tool that I could flash a stock image or something (like Odin is for Samsung phones)
2- When these phones started bootlooping, I installed TWRP on the other Fuels that I have, thinking that I didn't want it to happen to them. My understanding of the TWRP that's installed from TWRP manager doesn't flash a modified boot image, so you can't enter TWRP from a powered off (or in my case, bootlooping) phone. Is that correct? I flashed a custom boot image from elsewhere that allows me to tap vol up at the LG logo to boot to TWRP. Any idea if this is enough of a safeguard to in the even of similar boot loops?
Click to expand...
Click to collapse
My apologies for the delayed response. I have a lot going on in life.
As for recovering them, use the device you have closest to stock to make a backup. Do this before you attach your account or put any thing in to it after a "fresh wipe". To the best of my knowledge there isnt a tool like odin available, i could be wrong though. You can push a back up to the looping devices via adb. in order to do this you must have previously enabled usb debugging. The instructions are available on the web, i my self dont know how to do this. If you can establish an adb connection im sure you can command it to boot into twrp. For setup and testing use one of the devices that doesnt have a problem to establish adb. There is a little info on another thread i created about investigating the boot process the link is in my signature for the defy. Please be patient with me as i have two jobs and a single father, im not a hacker or developer. just a normal guy that is fascinated by my little robot willing to learn any thing. now that I know this thread is becoming active Ill monitor a little closer. Also if there is any thing i can help with ill be glad to do so. Im wanting to get a second fuel just for dev and learning purposes.
Recovery
Is there a way to access recovery on the lg fuel? I am stuck in a boot loop because I disabled the home screen service as well as other things that I did not pay attention to. I do not have a custom recovery installed.
I've never been able to boot to recovery by way of button press. Seems like there's a way to get into boot loader mode though. Just can't remember off the top of my head, I'm at work now and don't have the fuel with me. I'll see what I can figure out in a few hours when I get home. In the mean time you can try button combos upon boot to include the home button. If we can get ADB talking to it there's a chance I can send you copies of the files needed. Give me more details of what you have done just before the boot looping.
Sent from my ALCATEL A564C using XDA Free mobile app
I bought the optimus fuel a few months ago and i've been using it primarily for a music player/run keeping devices during my jogs. I turned off mobile data and i've noticed that i still see signal bars on the top notification area - does this mean that the radios are still on?
I was wondering if there was some way to completely disable the cellular radios so that i could conserve battery life inbetween days where I don't run?
Thanks!
This is a pretty cool app....
https://play.google.com/store/apps/details?id=com.latedroid.juicedefender
Airplane mode and then turn WiFi back on does the trick. "Radios off" = ton more juice
Has anyone found out anything else for this little phone? I have the LG Optimus Fuel. Had it for a few months now. I rooted it as soon as I got it and uninstalled a few system apps like the LG keyboard, the default SMS app and Chrome along with 2 or 3 other Google apps. It's still running fine.
I installed TWRP recovery and a custom boot image so I could boot into recovery by pressing the up volume button. Works great. I made a full system backup and saved it to my external SD card and saved it to my Debian laptop.
Right now I'm just looking for a custom ROM for this little phone but can't find one. I'd love to get Cyanogenmod on this phone but there are none. I'd port it myself but I'm not able to at the moment.
reemobeens19 said:
...
*ROOT*
These are the instructions I followed to root.
http://www.androidarea51.com/all-things-root/working-root-for-lg-optimus-fuel-woot/
...
Click to expand...
Click to collapse
I'll expand on the above link because no one can view all of the info in that thread w/o registering for that site [PITA].
Load towelroot (www.towelroot.com). Upon running towelroot, press "welcome to towelroot v3" 3-times (quickly). Change 1337 0 1 0 4 0 to 1337 0 0 0 4 0 (change only the ONE to a ZERO), click "make it ra1n" and you're rooted. :good:
This was verified on an L34C running Android 4.4, Kernel 3.4.0+, build KRT16S.L34CV10c, Sw ver L34CV10c.
YMMV; IANAL
My apologies for the inconvenience, I was unaware for the need to register.
What I would like to do with the L34C is find a ROM with all the phone functionality removed, and few to no Google Apps (let me just add the ones I need). I am not planning on using it as a phone (I still have my old Casio flip-phone, need nothing else). My intention was to experiment with creating a PalmPDA "replacement", something small to carry around for addresses, notes/memos, calendar (you know, the stuff you used to do on PalmOS), and in addition figure out how to do record-level synchronization **locally** (as in I don't need to send my data to some dirt-floor shack in Bangalore just to have it sent back to a device 2 feet away from my computer). Additionally, would line to use it as a basic portable media player. Essentially, trying to re-create the Palm LifeDrive on Android.
To my knowledge there are no roms available for this device. Your best bet in my opinion is to remove apps 1 by 1 after rooting. Google each and find out what the risk and severity of removing them are. I have donated my device to a less fortunate fellow employee. So as of now I'm unable to help with testing. This method is what I do for all of my devices until I'm finally happy with its performance and functionality. Think of Android as the swiss army knife of the computer world, you can do just about any thing with it, you just gotta figure out what tools are useful to you and the ones you can do with out, then you gotta ask Google witch ones Android can function with out. I hope you find what your looking for in the little robot, its a really neat world inside there!
I hate to bump an old thread but, I also don't it necessary to start a new one, at least not yet anyway but, I too am looking for a way to flash stock ROM. I have LG34Cs to use as a reference..
Where is the link to exposed framework at for this phone?
All official twrp 3 images are broken on official site. Last good working was 2.8.7.0.
Here is working twrp 3.1.1 if anyone interested:
Code:
mega.nz/#!I0lhAYAY!fRbQtQjYFI2kiJOD0FSEBPnBJm0JZxpiBaw52kyOfQE
majexuj said:
All official twrp 3 images are broken on official site. Last good working was 2.8.7.0.]
Click to expand...
Click to collapse
What does broken mean in detail? Do I risk to brick my L34C when I flash official twrp 3 images?
Mac23 said:
What does broken mean in detail? Do I risk to brick my L34C when I flash official twrp 3 images?
Click to expand...
Click to collapse
Broken as in doesn't boot into recovery. The phone will still boot into android, assuming you have a working system, and within android with root you can flash a working recovery image over a broken flash with the dd command on the twrp device info page (twrp.me/lg/lgoptimusfuel.html). So no real risk of brick, just possible inconvenience that might require a battery pull.
I built twrp 3.2.1 with same sources but I have not tested it since my battery seems to have completely died and the phone won't boot with usb power alone.
Here is link anyway in case anyone is interested:
Code:
mega.nz/#!ssExSY7S!_B3FcAmclzRwCKTX461Tl_QhpdwwK0tmvhL-6zkKLRw
---
Hi everyone,
I bought a No.1 X2 (001mobilephone) about 3 months ago, I have tried every version I can of PC > Phone rooting software and .apk's plus tried using a few similar tools that use ADB. (inc kingoroot, kingroot (chinese), SRS, oneclickroot, towel, androidroot, etc)
I cannot get the phone rooted and I do not want to wait, phone-less, for a month (at least a month to send to the manufacturer who was supposed to have rooted before it was shipped - and who knows if they will send it again without root).
the phone (may?) seams to have partial root, when i installed led manager, and have since done a wipe, the led settings seamed to have stayed with my custom email and other notification colours.
Specs/software is:
Qualcomm MSM8916
android 4.4.4
Kernal 3.10.28
[email protected] #2
Thu Jan 29 09;58:34 cst 2015
Anyone able to help?
Thanks
Markatkins said:
Hi everyone,
I bought a No.1 X2 (001mobilephone) about 3 months ago, I have tried every version I can of PC > Phone rooting software and .apk's plus tried using a few similar tools that use ADB. (inc kingoroot, kingroot (chinese), SRS, oneclickroot, towel, androidroot, etc)
I cannot get the phone rooted and I do not want to wait, phone-less, for a month (at least a month to send to the manufacturer who was supposed to have rooted before it was shipped - and who knows if they will send it again without root).
the phone (may?) seams to have partial root, when i installed led manager, and have since done a wipe, the led settings seamed to have stayed with my custom email and other notification colours.
Specs/software is:
Qualcomm MSM8916
android 4.4.4
Kernal 3.10.28
[email protected] #2
Thu Jan 29 09;58:34 cst 2015
Anyone able to help?
Thanks
Click to expand...
Click to collapse
Chinaphonearena.com: Sponsor Forums Official No.1® Forum NO.1 X-Men X2 4G LTE rugged 3-proof Smartphone
Hi, same phone, same problem. The above site might be interesting for you. No.1 supplies Qualcomm software and the phone's firmware with a tutorial to root. I succeeded in putting firmware on a bricked X2, but still did not get root access. But I am a newby, so give it a try. Good luck
UNBRICK no.1 x2 using original ROM
Thanks for this, i now have access to the ROM, and if you can understand the instructions its possible to install the ROM again.
I just did this today, however its partially rooted, as was my phone when I received the X2.
I need to now try to use kitchen and a bunch of other tools as described here to try and install Su and/or root the rom: en.miui.com/thread-21539-1-1.html
if i am sucessful i will post instructions, for now here are clear instructions on how to (should work as tested on my x2) unbrick X2 with this software.
1. download this: "ht tps: SLASH SLASH drive DOT google DOT com SLASH file SLASH d SLASH 0ByeMRyNUHsNRdGc0Qk1jQlJIb3c SLASH view" (i have less than 10 posts so cannot type full url, replace SLASH SLASH with // and DOT with .)
2. extract the rar (download trial of winrar or similar to extract (noobs))
3. launch the setup.exe from the folder you extracted too. (remember where it is installed)
4. extract the X2.rar to a folder (new folder on desktop or my docs)
5. right click (win 7, 8 10) and run as admin (the installed program from desktop called "QMSCT")
6. open the "setup" menu in QMSCT and click "configuration"
7. make settings look like the picture in: "ht tp s: SLASH SLASH drive . google . com SLASH file SLASH d SLASH 0B2M8OmUI5XS-SGtudHYwS0tLZGc SLASH view?usp=sharing"
all check boxes and fixed options must be identical, i have highlighted red
8. insert (red again) the file names shown in the picture (they will be in the original extracted rar where you launched the setup program or in the directory you installed to).
9. in the bottom field locate the folder where you extracted the x2.rar, this folder location is the folder you must browse to and select in the bottom of the settings screen. Only care about the red markings i made, i will now tell you below how to get the information you cannot change yet in the settings.
10. first SAVE, exit the settings, then exit program.
11. plug in no.1 X2 Mobile, while phone on hold power until options appear, then hit restart, before it turns off and vibrates, hold down both volume buttons and then also press and hold power... do'nt let go until phone vibrates and turns on to a blank screen... sometimes it will restart, just do it over again and again until it boots up blank (screen has lit up back/grey)
12. when screen blank windows will install driver. NB: Unfortunatly i had issues here and it took a windows 10 tech preview install 10041 build x64 to do this, however it did not get fiddly i just had to try xppro, win 10x64 on a laptop and then my desktop to work it out, also I was following chinese instructions that had been translated and were not perfect to begin with. So any win 7, xp or 8 might need to source which driver to install from no.1. Windows 10 tech preview is free and can be put on another partition easily if you search (noob) on xda or google i am sure someone will have covered it.
13. unplug phone, launch QMSCT again as admin, go into settings and click "Start setup process" then click ok on dialogue box. now plug in phone and hold vol buttons again, then power and hold all 3 down until it reboots into the blank screen. if all works a port will be found (1-8 i think i saw in my many attempts) once it has found it and you see the information on the screen look similar to my screen shot, click on save. note your port will maybe differ, and if it does not work, restart application and phone again and repeat. when it saves, exit configuration, exit application and then you need to restart application
14. if all is right, plug in phone, hold the 3 buttons in order again, and the application will start flashing it. DONT UNPLUG UNTIL RED OR GREEN shown in app.
RED=fail - go back through my instructions and the supplied "flash tutorial.docx" in the RAR (you extracted this at the begining - the pictures may help more than the instructions they gave)
GREEN=Woohoo! all done, unplug phone and do the power button combo, it will restart (might need to do combo a few times)
NB: settings stay the same once this application is set up, so you do not need to go through all again in future, just launch app and then plug in phone and do 3 button combo.
I hope this helps, if you are good with CUSTOM ROM creation, feel free to see if you can get this rom rooted and flashed and tell me/readers of this forum... if anyone wants a real challenge, root this rom, make the kernal 64bit and not 32bit and then post here.... this is what I want to do eventually if i can work it out.
good luck any bricked x2 owners
Fixed X2 boot loop and not being recognised while bricked
Mjfh said:
Chinaphonearena.com: Sponsor Forums Official No.1® Forum NO.1 X-Men X2 4G LTE rugged 3-proof Smartphone
Hi, same phone, same problem. The above site might be interesting for you. No.1 supplies Qualcomm software and the phone's firmware with a tutorial to root. I succeeded in putting firmware on a bricked X2, but still did not get root access. But I am a newby, so give it a try. Good luck
Click to expand...
Click to collapse
Ok so if you are still bricked (as I temp was) use this program: qtadb . wordpress . com SLASH download.
it fixed my x2 which was in boot loop, could not use adb or the flash program to even see it, win 10 was not recognising anything driver wise.
just extract from the x2.rar with all the boot img etc: boot.img and recovery.img
locate most recent android sdk/platform tools folder when asked for it
click on the corresponding "flash recovery" in qtadb and locate the extracted image, do the same with the boot img tab and find your boot img
that's the order i did it in, i may have reset phone between them and cleared cache by holding vol+ and power and using boot loader. I had installed an msm8916 file to root, that apparently does not... ah well we live and learn.
looking for solution to turn that x2.rar into a rom.zip as kitchen does not work with it. maybe im doing something wrong?
anyway phone on again so the search continues...
X2 missfunctions.
Markatkins said:
Thanks for this, i now have access to the ROM, and if you can understand the instructions its possible to install the ROM again.
I attached a Word Document with information and questions about this X2 device, which is too hard to recover to update ... and an buch of missfunction. ( camera error : can't connect to the camera; 4G LTE does not function, only 3g; battery life normal as 2000 mAh; )
I expect your answer or comments very soon.
Best Regards.
tomas abrego garcia.
Click to expand...
Click to collapse
X2 reset successfuly - EASY way
I attach PDF files with instructions to reset the phone X2.
I expect very soon someone help us to ROOT it !!!!
Best Regards.
help!!
Hi
This forum is the closest thing I have found which might help me in my problem to fix my 1 week old X2.
I really enjoyed using it - I got it 2 weeks ago - and it was working fine for all the week then last weekend I had a few apps running and the screen froze. I rebooted the phone but it just stayed black and never came on again. It is a stock standard phone - and it has not been rooted or modified in any way. Someone suggested removig the battery then refitting it.
How is that done?
Is that a good thing to do?
What else can I try?
Has anybody any idea on what might have caused this?
I'm stuck!
Jeff_T said:
Hi
This forum is the closest thing I have found which might help me in my problem to fix my 1 week old X2.
I really enjoyed using it - I got it 2 weeks ago - and it was working fine for all the week then last weekend I had a few apps running and the screen froze. I rebooted the phone but it just stayed black and never came on again. It is a stock standard phone - and it has not been rooted or modified in any way. Someone suggested removig the battery then refitting it.
How is that done?
Is that a good thing to do?
What else can I try?
Has anybody any idea on what might have caused this?
I'm stuck!
Click to expand...
Click to collapse
Hi,
I have one as well: it is indeed fun to play with but it is not reliable. I had multiple issues with it in the past months. Therefor my advice is: send it back and claim your guarantee (especially if you want to use it as your primary phone). Otherwise use the unbrick advice from markatkins earlier in this thread (but you have to feel secure with android)
good luck
Mjfh said:
Hi,
I have one as well: it is indeed fun to play with but it is not reliable. I had multiple issues with it in the past months. Therefor my advice is: send it back and claim your guarantee (especially if you want to use it as your primary phone). Otherwise use the unbrick advice from markatkins earlier in this thread (but you have to feel secure with android)
good luck
Click to expand...
Click to collapse
Thanks Mjfh
Looks like I have to pay a premium on the freight via courier to get it back to China. The local postal service won't take it because it contains a (non-removable) Lithium battery.. I'm not sure about unbricking it as it seems it is a very complicated process - and seeing that it seems completely dead -(not any signs of life, no lights, no screen) do you thnk it is just a matter of a firmware reset? If I attempt to unbrick it - I lose the warranty right?
So my best bet I think is to depart with several tens of dollars for the freight and demand a replacement that will not bug out inside 2 weeks.
issue, try this
Jeff_T said:
Thanks Mjfh
Looks like I have to pay a premium on the freight via courier to get it back to China. The local postal service won't take it because it contains a (non-removable) Lithium battery.. I'm not sure about unbricking it as it seems it is a very complicated process - and seeing that it seems completely dead -(not any signs of life, no lights, no screen) do you thnk it is just a matter of a firmware reset? If I attempt to unbrick it - I lose the warranty right?
So my best bet I think is to depart with several tens of dollars for the freight and demand a replacement that will not bug out inside 2 weeks.
Click to expand...
Click to collapse
Look I had this issue regarding dead and not turning on... sometimes charging it for several hours and it would just come back to life, i believe it is a battery issue, reading battery (stock rom) and when it may say 15% for example, the battery is actually empty and it dies, the charging should make display turn on but does not for a long, long time.
if this does not work, hold down vol up or vol down plus power button, this can breath life into it (sometimes both up and down plus power) remember press all at exactly same time and hold for 10 seconds at least for reset (unless it comes back before 10 seconds)
been a while since i held my phone so check top of page for my instructions as it is in there
best of luck
markatkins
toomax.mx said:
Markatkins said:
Thanks for this, i now have access to the ROM, and if you can understand the instructions its possible to install the ROM again.
I attached a Word Document with information and questions about this X2 device, which is too hard to recover to update ... and an buch of missfunction. ( camera error : can't connect to the camera; 4G LTE does not function, only 3g; battery life normal as 2000 mAh; )
I expect your answer or comments very soon.
Best Regards.
tomas abrego garcia.
Click to expand...
Click to collapse
Nice work
you need to install all ports to make this work well... i am going off memory from over 2 months ago but if you can revisit my instructions and check how many ports i have to setup, it should get you a green light, i could see an error in a photo at bottom of word... something about ports, this may confirm my theory.
I will answer all the questions soon, once I have a phone in my hand (give me 2 weeks, and tinker while you wait )
hope this helps
Click to expand...
Click to collapse
Jeff_T said:
Thanks Mjfh
Looks like I have to pay a premium on the freight via courier to get it back to China. The local postal service won't take it because it contains a (non-removable) Lithium battery.. I'm not sure about unbricking it as it seems it is a very complicated process - and seeing that it seems completely dead -(not any signs of life, no lights, no screen) do you thnk it is just a matter of a firmware reset? If I attempt to unbrick it - I lose the warranty right?
So my best bet I think is to depart with several tens of dollars for the freight and demand a replacement that will not bug out inside 2 weeks.
Click to expand...
Click to collapse
just do what I did, post and tell them battery removed (tick the plane and ship boxes - should be on form for international post)
I looked up why battery is now banned, its stupid... thanks to the more dangerous li-pol battery types, starting fires in planes and stuff like exploding, the air transport authority decided to ban the li-pol (explodes and loads of fires every year) and in that they included the more reliable (not dangerous and very few accidents worldwide) li-ion which is what is in your phone... so batterys in general.
play dum, say no battery in phone and tick that box for sea/ship shipping
remember this is a 80 degree c proof phone, pressure proof and should be able to contain the fire, but a fire wont start...
otherwise pay AUD100 (convert to GBP or USD for a similar horrific amount no one should pay)
if your phone does explode or cause a fire in transit... i am not accountable, you do this at your own risk and risk of being fined etc blah blah... read about % of fires from li-pol and li-ion, you will see the chance is slim, slimmer once sealed in a phone that will give it a heat proof case to try and get past plus minimal air to fuel a fire... good luck fixing or sending
I found an app called KINGROOT and worked like a charm. It rooted my No.1 Xmen X2 with just one click, it even fix the Kitkat SD write problem in the process.
I had to erase the SD card after the rooting process for the fix to work and after the root, had to reboot the phone 2 times. Everything is working super fine so far. Hope this work for everyone!
Kingroot V4.5
http://forum.xda-developers.com/devdb/project/dl/?id=14250
Which exact rom version do you use ?
Is GPS working?
BR
Trying new root version...
denispunk said:
I found an app called KINGROOT and worked like a charm. It rooted my No.1 Xmen X2 with just one click, it even fix the Kitkat SD write problem in the process.
I had to erase the SD card after the rooting process for the fix to work and after the root, had to reboot the phone 2 times. Everything is working super fine so far. Hope this work for everyone!
Kingroot V4.5
http://forum.xda-developers.com/devdb/project/dl/?id=14250
Click to expand...
Click to collapse
I have just tested the newest software from kingroot as advised released by denispunk, I am amazed as I only downloaded the previous version a few weeks ago, no luck with the old version of "new_kingroot...", however I may be in a slightly different position to others as my phone seams to have an issue locked in (despite flashing and wipe of partition) where it has a partial root access of some form, so trying this now......................
Tried 2 times and failed, I want to ask all reading this to please download (rename from .zip to .apk) and attempt root on their x2 or x6800. if you fail click on the huge submit button as I have been doing this for some time in the hope that they would see demand and accelerate the process of making a workaround.
For all looking (that search for root x6800 online ) this should work the same % for anyone with the no.1 x6800 and the x2 [I have the X2 and got money back from insurance claim, so I also have x6800 on the way ] because the x2 and x6800 are the same rom from what I have researched, the only difference is the micro sd capacity, the 4g bands supported and a huge 6000mha battery in the x6800. most components otherwise are identical.
All reading please have a go...
if you are reading this you have an x2 or x6800 or know someone who does...
if your not very experienced or if you are experienced in ROM work, try point 1 and then try point 2 below, but please just do point 1 if nothing else
1) email No.1 and "beg" for a android 5.0/64bit kernel ROM for the x2 and x6800 to be released - I have done this and want to encourage you all to help me force the company to meet consumer demand, by setting a consumer demand. This 64bit update would increase the phones potential as it has a 64bit CPU, it currently runs 32 bit software which is slowing it down.
once done read point 2
2) I wanted to see if some experienced persons could visit the en.no1phone.cc site and download the M2 firmware (not a spelling mistake) as this device and the x2 use the same unusual ROM's which look similar in layout. my hope is we can bind parts from the 2 ROM's together to get a 64bit android version onto the x2/x6800... please understand I do know this will need work and will most likely not work ever but with the unique rom types I figure there is no harm in trying and someone might have the ability to open them and do some magic.
now the phones are physically different but No.1 use the same basic layout in their ROM's and the most basic possible stock android with nothing but background pictures added.
my hope, from what I can see in the files of the two ROM's, is that we can merge/build the OS, kernal and some of the information from the M2 ROM into the x2 ROM (I have supplied the x2 rom in the top of this post on page 1) and hope that its basic enough to maybe work with some tweaking, I know the CPU is different and that I am explaining this simply like a drag and drop, but if it does work we can get 64 bit software for our CPU's
if all else fails we can hope No.1 release what we ask for, and you can flash the original x2 rom back onto the device until they release it or someone on here gets through the ROMS and makes us our own.
denispunk said:
I found an app called KINGROOT and worked like a charm. It rooted my No.1 Xmen X2 with just one click, it even fix the Kitkat SD write problem in the process.
I had to erase the SD card after the rooting process for the fix to work and after the root, had to reboot the phone 2 times. Everything is working super fine so far. Hope this work for everyone!
Kingroot V4.5
http://forum.xda-developers.com/devdb/project/dl/?id=14250
Click to expand...
Click to collapse
Root worked
I finally sourced a slightly newer .apk and root worked. Kingroot will root no.1 x2 or no.1 x6800. So far used it to access battery stats with Xposed and installed one power guard to lower CPU speed to gain more battery. The device is very fluid still on 533mhz in power save CPU mode with I/O scheduler in "row"
I advise anyone looking for this phone rooted to visit the official www.kingroot.net site
Great news everybody, since my post asking for us to all send kingroot requests to support our device for root access, the number of requests jumped almost 30 points and they listened! Kingroot responded and now...
Kingroot.net will root the no.1 x2!
If you just landed here looking for the software to root the X2 or X6800 from No.1, please help us make this phone better, this forum helped get kingroot.net to enable root for the X2 so help us and say thank you by sending an email to no.1 regarding getting lollipop on the X2 and X6800.
You just need to...
Email: [email protected]
Skype: quecc1989
Or MSN: [email protected]
Ask for lollipop ROM to be made for the x2 and the x6800 and say it will make the phone faster and have a better battery life. Copy that if you like
Update on this: not only will the software give the phone a bit of a boost in power, it should improve battery life and I completely failed to mention before that we will have faster app boot times as well because we will get access to ART instead of Dalvik (Currently I cannot find a way to run ART in KitKat without factory resetting to get out of the nice boot loop it sticks me in).
For those unaware of what I am going on about, Dalvik is the runtime android is moving away from because it has to decompress each installed app before it runs, ART (android run time) installs app's already decompressed (more space used on install but fast launch). I find the x2's 8GB is plenty of internal space for applications so let's harass no.1 sales email and Facebook/twitter/google+until we get lollipop.
Official no.1 site is: http://en.001phone.cn
They use a picture for contact info but feel free to click on my links above for msn, Skype etc
Sorry if this was a ramble, but power of word is going to be easier than us taking and editing ROM's or making ROM's to get lollipop... If we harras them endlessly they will fold and build it for the phones and all it takes is one email each... Maybe a followup each too
toomax.mx said:
I expect very soon someone help us to ROOT it !!!!
Best Regards.
Click to expand...
Click to collapse
I hope the same for the No.1 X6800
forum.xda-developers.com/general/help/root-1-x6800-rugged-ip-68-phablet-china-t3254950
Not much people know the No.1 smartphones (the rugged ones are awesome for the price).
Update: I rooted the No.1 X6800 with 'NewKingRoot v4.62' app and after that buy the Super-SuMe-pro' app to keep it 'trustfully rooted and with SuperSU'.
When device is off, and I press power button and volume up button. Then I get a bootloader that can boot from MicroSD card.
So place the compatible Rom on MicroSD and re flash it.
This works for me with original x6800 rom on my x6800 phablet.
Hello forum people, I need help to revive my S3 i9300, if you could help me I would really appreciate it.
I tell what I remember about the problem:
The phone was rooteado to be able to use it with any company since it was of movistar. a year ago with the rootking (we sent it to root), the phone was my dad and now has a new one, and it stopped using about 2-3 months.
Then I lent it to a friend who had just broken his cell, so I gave it to him so he has something until he buys one, but he told me that it did not work because he did not load and unload very quickly. He gave it back to me and I stopped using it until about 1 month ago, that I was left without a cell phone and I want to use it to have something.
The same thing happens as it does not load and it is very easy to download, BUT if you use the charger and cable of the Huawei ascend Mate 7 that my dad has, it charges perfectly and the cargo is not cut at all.
Well, seeing that this happened, I restarted it from the factory (I guess the root will be removed with that).
It was still branded and only loaded with the charger and the Huawei cable ...
Well now I tell what happened with what I did.
I install the samsung drivers for the compu, install odin 3.10.6 and under the recovery file that I put up, well I install everything but when I realized instead I read fast and instead of saying PDA said AP in the odin.
Well I try to turn it on and it does not turn on, I try to enter into recovery mode and it does not start.
Then I install another odin, version 1.30 and have a PDA, I do everything as I say start the phone in download mode, home odin, connect the phone to the computer, put the file in pda and give start.
He tells me that everything went well but still does not turn on and without going into recovery mode.
Say that when I do recovery mode (volume up, home and power) I see the logo of samsung and like that desinstegra, then it appears again and blinks in blue but as if it were broken and the logo moves. In short broken.
Then then install another recovery, https://dl.twrp.me/i9300/twrp-3.0.2-...0.img.tar.html
Now I want to enter into recovery mode but this appears and I want to touch some option that appears but nothing, as if the touch was dead.
And after that, it seems to me that I tried to change the Kernel and I put any but the one of my model by mistake.
Current status of the s3:
It lights normally but it takes a long time.
Enter DOWNLOAD mode (vol down, home and Power)
The screen touch does not work but it does show an image.
The buttons work, also the easy button of back and home.
DO NOT enter RECOVER mode (vol up, home and power) is frozen in the Samsung logo.
I want to make it work with any other rom that is functional except the STOCK. And that transforms into unlocekd
It does not matter if when I install a new ROM the files are deleted, I do not have anything in the phone.
Thank you very much to those who respond.
Only to get sure, that I understood you right:
after flashing the wrong kernel, your touch in twrp is not working anymore?
Will say the device is not reacting when you press a button on the screen with your fingers? If so than, I am afraid that your touch is broken. What kernel did you use? Can you post the name of the zip or tar file?
Beside of that, after flashing samsung stock, the reboot will last quite long. Maybe around 15 min till up to 25 or 30. And after flashing and before reboot, go to recovery and make a factory reset. Cross my fingers... :fingers-crossed:
rodman01 said:
Only to get sure, that I understood you right:
after flashing the wrong kernel, your touch in twrp is not working anymore?
Will say the device is not reacting when you press a button on the screen with your fingers? If so than, I am afraid that your touch is broken. What kernel did you use? Can you post the name of the zip or tar file?
Beside of that, after flashing samsung stock, the reboot will last quite long. Maybe around 15 min till up to 25 or 30. And after flashing and before reboot, go to recovery and make a factory reset. Cross my fingers... :fingers-crossed:
Click to expand...
Click to collapse
Hello, if I think that the Kernel had changed I do not remember exactly what it was because I downloaded it on a page written in Asian language by mistake and the Google translator confused the words and he said it was from the s3 but I think it was from the note 3.
The tactile does not respond exactly.
I did not understand him completely, he wants me to enter RECOVERY mode (it takes about 15-20 min to enter) and then do a factory reset?
I almost forgot to clarify that I had tried to do this from the video: https://www.youtube.com/watch?v=fA86_HFGx_w
Everything was installed perfect and I did it as is, except to delete.
Or reinstall the factory rom to see if it worked again.
If you flashed a kernel from note3 that the touch will be most probably minimum damaged and does not work proper anymore. I flashed mistakenly the kernel from the note2 and touch was broken, but maybe you were lucky and your touch is still working. No, passing into recovery should take only a few seconds, but rebooting into system after flashing samsung stock, then in recovery, then wiping and factory reset, could take a rather long time.
rodman01 said:
If you flashed a kernel from note3 that the touch will be most probably minimum damaged and does not work proper anymore. I flashed mistakenly the kernel from the note2 and touch was broken, but maybe you were lucky and your touch is still working. No, passing into recovery should take only a few seconds, but rebooting into system after flashing samsung stock, then in recovery, then wiping and factory reset, could take a rather long time.
Click to expand...
Click to collapse
Could you tell me how to do it please? I'm not an expert at all in changing ROM.
but you wrote that you already flashed something (?) via odin? I understood that you flashed samsung stock rom, beside kernel and twrp to proof, whether phone is working with original sw? If not than please check and search the i9300 forum section, there are a few of howtos and todo threads and posts which explains it even more better, that I could ever do
Edit: for example:
https://forum.xda-developers.com/galaxy-s3/general/samsung-galaxy-s3-sticky-roll-thread-t2344125 and from there for example
https://forum.xda-developers.com/galaxy-s3/help/guide-odin-flash-guide-t1671969
rodman01 said:
but you wrote that you already flashed something (?) via odin? I understood that you flashed samsung stock rom, beside kernel and twrp to proof, whether phone is working with original sw? If not than please check and search the i9300 forum section, there are a few of howtos and todo threads and posts which explains it even more better, that I could ever do
Click to expand...
Click to collapse
I used odin but I forgot how I had done and had followed the steps of a tutorial that I lost the link.
check my edited post above, now with links to guides and one of the best feature here on xda is the search button and that we have many things to read
rodman01 said:
check my edited post above, now with links to guides and one of the best feature here on xda is the search button and that we have many things to read
Click to expand...
Click to collapse
Hello, thank you very much for the links that you have passed me. They will be very useful, excuse me but I do not want to be irritating at all but I am really lost.
My only question is to know how to start reliving it?
I start installing CWN and then change the ROM?
I would recommend to start with flashing the original samsung stock sw via odin. To see that everything is working as it should. If it is so, especially your touch, than you can go ahead with routing, flashing an alternative recovery and testing custom roms, like leo or pie as you posted in the other thread. The time you are spending with writing here and in the second thread you could have already finished the sw flash and reboot to system to check the health of your device. Others than that procedure is a waste of time in my opinion. But thats your decision. On the other hand, we, or better I wouldn't spoon feed you further, because you can find almost everything for that years old device here with search, read read and read.
rodman01 said:
I would recommend to start with flashing the original samsung stock sw via odin. To see that everything is working as it should. If it is so, especially your touch, than you can go ahead with routing, flashing an alternative recovery and testing custom roms, like leo or pie as you posted in the other thread. The time you are spending with writing here and in the second thread you could have already finished the sw flash and reboot to system to check the health of your device. Others than that procedure is a waste of time in my opinion. But thats your decision. On the other hand, we, or better I wouldn't spoon feed you further, because you can find almost everything for that years old device here with search, read read and read.
Click to expand...
Click to collapse
Hello, I did the following, I had tried to re-install the stock stock a few days ago and it did not work, I did it for odin.
So what I did today was, install the recovery mode of ClockWorkMod and probe with the rom of MIUI 8 and that of Linage16, no installation. Then try with this: https://forum.xda-developers.com/galaxy-s3/development/rom-t3442868 And install correctly but it does not work, pass the Samsung logo but then when the ROM logo appears it stays there frozen and restarts ... it seems to me that officially the phone is dead.
Again: the right stock samsung sw should work if flash via odin didn't fail and, what I already mentioned, after flashing you did a factory reset in recovery. After that the reboot into system could take several minutes. Otherwise you can try it with repartition efs backup restore etc etc etc.
btw: newer custom roms, like leo-16, cannot be flashed with the old cwm recovery and cwm touch recovery, as you mentioned in the related thread, would not make much sense, if your touch is broken!?! If you do not want to go via samsung stock sw, then get a newer twrp, search for info which one is suitable, and guides how to flash custom roms, and flash the preferred one of your choice.
Hey, So yesterday I got the stupid idea to try out Android 13 QRP Beta 1.
I heard praise of Pixel-Flasher which helps out in Updating & maintaining root. Around 2 weeks ago I updated from Android 12 Stable to Android 13 Stable using ADB sideload & lost root, booting with magisk-patched img results in bootloop, So I ran the phone with my banking apps broken and without root for 2 weeks. I had enough and thought let's start fresh on QRP with proper root. So, I backed up all my data and prepared my Pixel 6 for formatting.
Finally, I tried my shot with Pixel-Flasher and read all instructions for usage, it was running pretty laggy on my M1 MBP. NOTE: I'm not Blaming the developer of Pixel-Flasher for anything, and I'm completely responsible for probably performing the wrong steps coming below.
I downloaded the factory zip for the latest Android 13 Sep Update [was running Aug], extracted and patched the boot.img using Pixel-Flasher and Magisk on my Pixel 6. Chose the option to WIPE Data and selected the patched-magisk.img and proceeded to flash. And I'm pretty sure this is where I screwed up by not selecting the stock img. The procedure went through and finally, my Phone flashed Phone is corrupted and will not boot, clicked the Power Button & it got stuck on the Google Logo. As it was stuck there I forced it to reboot and it went into fastboot d. I was sure I did something wrong so I powered it off and tried to boot into fastboot now... Black Screen no response, Connected charger... no response, Connected USB and held power + vol down for 60 secs... no response. The phone was at 95% so not battery dead by any chance.
This is where I diagnosed that I bricked the Motherboard. To add fire to the pot, I live in India & got this phone from my Uncle. No warranty in India.
Now I'm sitting here with regret and a 200g Paperweight. There is a Repair Shop called ShatterFix here in India that services Pixel 6 unofficially, and I'm considering sending in the phone for diagnosis. What I'm worried about is that the Motherboard replacement part itself costs close to ₹20,000 - ₹25,000 INR.
Any suggestions or help is welcome for a boy in misery. Had a great time with my Pixel 6 for 8 months, fell back to using my OnePlus 6T now.
Thanks, this is my first time posting a large essay thread like this. Sorry if it had useless info or if anything wasn't clear.
If you haven't tried https://flash.android.com/ then I'd suggest giving it a shot. You never know if it works..
I had the same issue on my 4a a while ago, nothing seemed to be working but then i used this, it detected the phone and flashed the latest version.
Aks said:
If you haven't tried https://flash.android.com/ then I'd suggest giving it a shot. You never know if it works..
I had the same issue on my 4a a while ago, nothing seemed to be working but then i used this, it detected the phone and flashed the latest version.
Click to expand...
Click to collapse
I did try that, as I can't even boot the phone into fastboot or ADB, the device is not detected
suhas2k said:
Hey, So yesterday I got the stupid idea to try out Android 13 QRP Beta 1.
I heard praise of Pixel-Flasher which helps out in Updating & maintaining root. Around 2 weeks ago I updated from Android 12 Stable to Android 13 Stable using ADB sideload & lost root, booting with magisk-patched img results in bootloop, So I ran the phone with my banking apps broken and without root for 2 weeks. I had enough and thought let's start fresh on QRP with proper root. So, I backed up all my data and prepared my Pixel 6 for formatting.
Finally, I tried my shot with Pixel-Flasher and read all instructions for usage, it was running pretty laggy on my M1 MBP. NOTE: I'm not Blaming the developer of Pixel-Flasher for anything, and I'm completely responsible for probably performing the wrong steps coming below.
I downloaded the factory zip for the latest Android 13 Sep Update [was running Aug], extracted and patched the boot.img using Pixel-Flasher and Magisk on my Pixel 6. Chose the option to WIPE Data and selected the patched-magisk.img and proceeded to flash. And I'm pretty sure this is where I screwed up by not selecting the stock img. The procedure went through and finally, my Phone flashed Phone is corrupted and will not boot, clicked the Power Button & it got stuck on the Google Logo. As it was stuck there I forced it to reboot and it went into fastboot d. I was sure I did something wrong so I powered it off and tried to boot into fastboot now... Black Screen no response, Connected charger... no response, Connected USB and held power + vol down for 60 secs... no response. The phone was at 95% so not battery dead by any chance.
This is where I diagnosed that I bricked the Motherboard. To add fire to the pot, I live in India & got this phone from my Uncle. No warranty in India.
Now I'm sitting here with regret and a 200g Paperweight. There is a Repair Shop called ShatterFix here in India that services Pixel 6 unofficially, and I'm considering sending in the phone for diagnosis. What I'm worried about is that the Motherboard replacement part itself costs close to ₹20,000 - ₹25,000 INR.
Any suggestions or help is welcome for a boy in misery. Had a great time with my Pixel 6 for 8 months, fell back to using my OnePlus 6T now.
Thanks, this is my first time posting a large essay thread like this. Sorry if it had useless info or if anything wasn't clear.
Click to expand...
Click to collapse
Sounds like you never flashed, at the minimum, the A13 bootloader, or the A13 image, to the other slot and when you ran into problems your phone reverted to the other slot which still had A12 on it, therefore causing you to brick your phone due to the new ARB (anti-rollback protection).
Not familiar with things in India, but I would at least try contracting Google and explaining that your phone died and you think it was because of the new anti-rollback protection they implemented in the A13 bootloader. From observations, they seem to be pretty good at either fixing or replacing devices that have run into this problem, maybe even without a warranty. Worth a shot...
suhas2k said:
I did try that, as I can't even boot the phone into fastboot or ADB, the device is not detected
Click to expand...
Click to collapse
Did you install the drivers from Google for ADB and fastboot?
Without these, the device can't be detected.
Cheers
tom1807 said:
Did you install the drivers from Google for ADB and fastboot?
Without these, the device can't be detected.
Cheers
Click to expand...
Click to collapse
Yes, for past 8 months I was updating with root using adb side load so yes, both fastboot & adb drivers are properly installed.
Lughnasadh said:
Sounds like you never flashed, at the minimum, the A13 bootloader, or the A13 image, to the other slot and when you ran into problems your phone reverted to the other slot which still had A12 on it, therefore causing you to brick your phone due to the new ARB (anti-rollback protection).
Not familiar with things in India, but I would at least try contracting Google and explaining that your phone died and you think it was because of the new anti-rollback protection they implemented in the A13 bootloader. From observations, they seem to be pretty good at either fixing or replacing devices that have run into this problem, maybe even without a warranty. Worth a shot...
Click to expand...
Click to collapse
Looks like you are right, it's ARB issue.
I did try contacting the B2X Service Centers in India and they only service now 6a but not the 6.