Please, I hope somebody doesn't start berating me for not reading XDA posts about my Verizon Galaxy Note II more thoroughly. I have read many over recent years and been saved by quite a few during the hacking of my SCH-I605. Furthermore, I've been working in software development and network administration for decades now, so please don't somebody suggest I not mess with rooting my phone, custom recoveries, et cetera. I am here asking questions to make sure I don't hard brick my phone. Not asking resulted, about two months ago, in almost succeeding at Kobol's very interesting "short the tiny resistor" mode of getting out of a boot loop. I have a fully functioning phone now running rooted Kitkat and it's a sturdy platform, runs really great after I melted most of the bloatware and froze the rest (in case I ever need it), but I'd still like to move on to Lollipop and there is only one means for doing so which I know of (CyanogenMod), which I think may be problematic unless I am able to reflash an earlier ROM with unlocked bootloader.
The basic question I need verified is multi-part but basically boils down to this:
1. Is it or is it not true that if one is at baseband version I605VRUFND7, the bootloader is locked and one cannot install a custom recovery? (I think I read that in a few places anyhow.)
2. Is it or is it not possible to flash back to I605VRALJB from rooted I605VRUFND7?
3. Is flashing back to I605VRALJB, then installing TRWP or CWM, then using custom recovery to flash the latest CM12.x the best and only way to get from rooted Kitkat to rooted Lollipop?
4. I know there are some functional improvements in Lollipop but are they really that significant? I like the whole "material" thing which comes with Lollipop, but not at the price of loss of functionality.
Anyhow, here's my little sob story, which has a happy ending -- perhaps some of these details will elucidate my situation and lead to better answers:
I got tired of waiting around for Lollipop and had been unrooted by Kitkat for almost a year when I rooted again back in July 2015. I had wanted to go with the latest CyanogenMod Lollipop version, but ran into problems first using Heimdall (which refused to properly connect and write) and then trying Odin (against best advice post-root) to install a custom recovery (preferred TWRP but would go with CWM). Always led to that "unauthorized software" boot screen, which then necessitated reinstalling stock Kitkat and rerooting (I found the Ghettoroot .BAT file worked okay.) All was well, I was too busy to think about Lollipop but I woke up one morning about a month after I rooted Kitkat to find my Note II was stuck on red Verizon book splash-screen. Found a great article and YouTube showing all the keypress sequences which might exit a Note II from been stuck in boot -- but unfortunately not until after my further finagling just left me with a dead no-display-at-all device. I undertook Kobol's method, which requires partially reassembling the Note II's electronics outside its case and attempt to reboot with a very tiny screwdriver shorting a minute resistor on the motherboard right adjacent to the CPU -- I did in fact see the screen flash on briefly -- but I held my little screwdriver down too hard, accidentally gouged out the tiny resistor, and ended up buying a refurbished motherboard which very likely may have been scavenged from a stolen phone before going on sale on eBay. New motherboard worked great, I erased the original owner's info and data and proceeded to reinstall and root Kitkat. (Motherboard was already at I605VRUFND7) when I received it.
Anyhow, I also tried to install a custom recovery after I had new motherboard and rooted Kitkat. Using the TWRP Manager app put me back on the "unauthorized software" boot failure screen from Verizon, but I was able to Odin back Kitkat easily enough without losing my apps and configuration data. I believe I tried to use ROM Manager and Flashify as well -- but didn't find those apps very cooperative (though I didn't bother to upgrade to "pro" level on any of these in cast that matters). Unless I am mistaken, all these apps just place a zipped update file in the root of my internal SD card and then just hand it over to the Note II's stock recovery. I figured I just needed to stop and regroup later. That was a few weeks now.
Honestly, after the ordeal of having to replace a broken motherboard, and also -- after having looked at Verizon, Sprint and AT&T and the new Galaxy devices with no removable back and cracking the phone open necessary to replace the battery or upgrade the hidden microSD card and not liking that one would have to pay $600 over two years for a smartphone even further crippled at the cell carriers' requests -- it's even more important to me to be careful not to damage my Note II. (In fact, my Note II had turned out to be irreparable, I might even have even bought a refurbished unlocked Note 2 or 3 or 4 -- Samsung has made a real error on their latest generation of phones with their sealed backs and no user-accessible microSD reader.)
Yet, perhaps naively, I really do want to move on to Lollipop and even Marshmallow when CyanogenMod makes that available. So I really would appreciate it if you guys can verify whether what I intend to do (downgrading to pre-Kitkat in order to install custom recovery and then CM12.x) is workable? Or if there's a better solution? Or if I should just be content to have Kitkat rooted with all the fat cut off?
Many thanks. Hope my digression was not too long. Please don't anybody yell at me. XDA Developer's web forum is so full of very useful write-ups but unfortunately also some incorrect information and a lot of just plain useless posts -- it's really difficult sometimes to tell posts by guys who are actually experts from post by well-meaning folks with a lot of ideas but not so much expertise specific to SCH-I605 and VRUFND7. And I really need to get this right. (Granted that nobody on the forum can be held culpable should on mess up my phone based on their advice.)
Thanks once again!
Related
I used Oden to flash a Samsung Galaxy S II rom to it and now, it only shows the Samsung logo at bootup. No recovery menu. If I try to access the recovery menu, it kicks me out and reboots. Samsung galaxy player 5.0 All Touch Buttons including home.
If you can get into download mode by holding volume down at boot, you can just reflash stock.
Sent from my YP-G70 using Tapatalk
Um, okay, for future reference NEVER FLASH ANYTHING NOT SPECIFICALLY MADE FOR YOUR DEVICE! I learned that the hard way, so not saying your stupid, just think a little more before you try to flash a rom for a dual core phone that's only resemblence to a Galaxy player is the word Galaxy. I find that for some reason, each phone has to have a different strain of android, and their roms never, NEVER, mix. So, I am stating this just to warn others new to android, not to make you look bad (I made a similar mistake of trying to flash cwm that someone assured me couldn't possibly brick my device, what a noob I was!).
Yup... NEVER flash something not designed for your device unless you know EXACTLY what the hardware differences are and how to deal with them, or you've been given specific instructions on how to port firmwares to your device.
(I9100 ROMs are so easy to run on I777 that they can be autoported with a CWM-flashable package now, but that's because the I777 is 95% identical to I9100. There will be nothing that can be "hellraised" to the Players, except possibly being able to creat "common" ROMs that target both International and US with a small zip file containing the differences flashable in CWM.)
Mate, I'm in the same boat where you used to be. Just a little worse.
Long story short: flashed, by mistake, the entire i9000 rom, including boot loaders, through Odin. Got a "black screen", "no reaction" brick. Computer won't detect no matter what button combo I throw at it.
Samsung Galaxy Wi-Fi 5.0"
YP-GB70CWXAZ (8GB) brazilian edition
I need some details about jtag and the micro-usb port. Also, in the current state, can I try to format a sd card & see if the player recovers from it? Like the Samsung Development Board? When everything is screwed, the usb pins can be used as a jtag port to avoid opening the device, even though I already did it.
PS: I've already located the 12 pins (jtag) & another 4 points on the main board. Just don't know how to check if the second ones are also jtag. The blue coating is also scrapped & ready.
Thanks.
Peace.
You might want to try AdamOutler oneclickrecovery before messing with JTAG. You can find it here.
This will upload a bootloader so you can re-flash the device with odin.
I have tried to recover my YP-GB70 (32gb korean version) with AdamOutler tools with 80% success.
Anyway thanks a lot for the tool and your great help.
What I did:
under odin I flashed original YP-GB70 32gb PIT plus the provided "AdamOutler bootloader and the latest korean firmware (pb is the same with any earlier FW version)
The result i got is almost perfect, i passed SAMSUNG logo, the boot ring tone and went the GALAXY sky where it stay looping. (All wipes where done before.)
My questions are:
-What is missing in this Flash process?
-Is the bootloader specific for US version or device related?
-Any idea of what I should do to succeed?
You are welcome to expertize this issue because a solution will be a good tool for many imprudent guys like me.
attached picks of 3 diferent trials done lately.
best regards from France
Lolo9393
Mind you I temporary bricked them, but I've yet to this day tried rooting a phone, and never had things go smoothly.
Any guide I try to follow just so happens to be the wrong one, or isn't thorough enough in its directions... Theres always some missing software, or missing details on what to do when you hit a road block, so here is my story so someone can point me in the right direction...
I bought this LG Optimus G LS970 on eBay, and apparently it was already rooted, and it had some sprint apps on it so I guess its the sprint version of the phone. Anyways I notice there are some photos on the phone, so start plugging in the the phone to my pc only to find that i cant access files.... I google some questions, start holding buttons trying to get into whatever boot or recovery mode or some mode i dont understand.
Turns out I got something called Team Win Recovery Project v2.6.0.0 flashed on my phone.... I don't quite get what all these options are, but all I see are wipe options and I'm thinking "Hey this will get me back to factory settings and maybe i can flash a barebones android jellybean whatever (I dont know what os is called on a phone) So I start checking boxes and wiping things...
I soon find out that my device is telling me I don't have an OS. Of ****ing course it doesn't. I realized I just deleted it, because it told me I deleted it.
Well atleast I still have this recovery dohicky so not all is lost.
I start reading unbick guides, and of course I dont know what they mean, I just download every link they tell me to and run them. I install "drivers" and even then, when I plug the phone into my PC, I still get "Did not install" popups even if "LGUnitedMobileDriver_S4981MAN38AP22_ML_WHQL_Ver_3.8.1" said it installed correctly....
I open up this Original LG Firmware thing, and asks for my phone's model and serial number... Just what the hell is my phone's model? eBay listing said E973, the back of the phone says LS970, that useless mobile tool that wont let me download additional drivers says its called LG-LS970, and google results call it LGLS970....
And of course I don't know my phones serial or whatever a "imeieieie" is because I don't have an os to tell me that (guides don't tell me how to get this on a bricked phone and google result is useless)...
So I cand download this thing called a kdz because #1 it wont let me, and #2, and google just doesnt have a download link for it.
All I wanted was a rooted lg optimus g with a nexus-like experience on it without bloatware, and I somehow manage to brick my device within minutes of owning it, what do you think I should do.
I did hold down Vol - to get into some black screen that says "SERIAL" with a number, but that number doesnt seem to work with that lg firmware downloader thing. What do?
Super easy fix. Get an external sd card. Put a ROM on it. I recommend one of these http://forum.xda-developers.com/showthread.php?t=2067871 the latest version is Stock Jellybean of our phones. OR is you want CM10 use this http://forum.xda-developers.com/showthread.php?t=2411406 . Be sure to download ROM+GAPPS for CM10. I recommend those since you probably don't know if your phone has the updated partitions.
Anyway put whichever you want on the External SD card. Reboot back into recovery TWRP (Team Win Recovery). Wipe Data/Cache/Dalvik. Go back then Install the files you put on the External SD card.
Ls970 is sprint version. Only att version has external SD.
Sent from my Optimus G using XDA Premium 4 mobile app
DeathmonkeyGTX said:
Ls970 is sprint version. Only att version has external SD.
Sent from my Optimus G using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Oh wow I read that some many times and it just didn't click. Well it's much hard now. To OP, you should ask in your designated forum. This one is for the AT&T model. The easiest way is to find out how they restore their phones to stock. Probable LGNPST or something similar. Or install ADB, then push a ROM file to the internal, then flash in recovery. You're gonna have to do some research. But it's still easily do-able. As for the issues with the drivers, someone over there should have a link to alternative ones. But you can google "universal ADB drivers" and those should work.
I used LGNPST with a positive result. The hardest ****ing part was finding whatever-necessary file I was supposed to flash to the device. It took me hours to find it (not much help from XDA) and I was never clear if the file I washed, was indeed the stock rom the device came with.
The device now has startup and shutdown animation and jingles I wasn't familiar with (Different from what I got the phone with)
What I know is, the ebay Listing was for a E973 from West Virginia with abunch of Sprint apps on it.
But E973 is said to be a Canadian model? But Canada doesnt have sprint? And the phone says LS970?
I don't know whats this phones origins are, I just know I flashed a file called LS970ZV7_02.SV7_02.P25006.tot which told me to rename to bin, it flashed an outdated, possibly mismatched version of android, and from update to update I eventually got back to 4.1.2 but had new animation startup stuff...
My phone came pre-rooted and pre-recovery, but this recent flash killed those and now im looking to get back to that point. I'm unaware if my radios or whatever are jacked up or not because I never intended to use the device with a service as I get by just fine on Wifi only.
I found something called GAIO but the original page is offline and i cant download it.
Chocolina said:
I used LGNPST with a positive result. The hardest ****ing part was finding whatever-necessary file I was supposed to flash to the device. It took me hours to find it (not much help from XDA) and I was never clear if the file I washed, was indeed the stock rom the device came with.
The device now has startup and shutdown animation and jingles I wasn't familiar with (Different from what I got the phone with)
What I know is, the ebay Listing was for a E973 from West Virginia with abunch of Sprint apps on it.
But E973 is said to be a Canadian model? But Canada doesnt have sprint? And the phone says LS970?
I don't know whats this phones origins are, I just know I flashed a file called LS970ZV7_02.SV7_02.P25006.tot which told me to rename to bin, it flashed an outdated, possibly mismatched version of android, and from update to update I eventually got back to 4.1.2 but had new animation startup stuff...
My phone came pre-rooted and pre-recovery, but this recent flash killed those and now im looking to get back to that point. I'm unaware if my radios or whatever are jacked up or not because I never intended to use the device with a service as I get by just fine on Wifi only.
I found something called GAIO but the original page is offline and i cant download it.
Click to expand...
Click to collapse
Well, by your own admission, you said you needed to flash the LS970 tot file, which wouldn't be in this forum, the AT&T LG Optimus G is the E970, it's distinct in that the back glass has the AT&T logo, for one. On the bottom center on the back glass it also says "LG-E970"
On the left side of the device, with the volume buttons, below them is a tab that pops open for the micro SDCARD and SIM card.
If the phone you hold in your hands doesn't have these distinctions, and you start flashing stuff from THIS forum and not the LS970 (aka Sprint LG Optimus G) You very well might brick, temporary or not, all over again.
That being said, with the correct kernel, MANY of our roms work just fine for your phone, but research and reading is a prerequisite for such.
sprint lgog forum: http://forum.xda-developers.com/forumdisplay.php?f=1928
Welcome to the mobile world, where everyone does whatever the **** they want when developing a phone, and people in their free time struggle to fix it!
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
---
Hiya
I have an Alcatel Onetouch Pop C1 4015D (and for the record, I'm never buying this brand or similar junk again). I just got it un-bricked after a few months thanks to the online USB firmware updater. It's currently in pretty much its factory-default state again, preinstalled crapware and all.
What I'd like to do is install a custom ROM on it, to have a clean system I can actually enjoy owning, e.g. AOSP (if that is what I think it is: the basic, clean Android system). The problem is that I'm getting a little overwhelmed with information, tutorials linking to more tutorials, tutorials linking to downloads for which I have to "complete a survey" and such (abort abort abort), 2 different tutorials for the same thing stating different ADB commands, a few outright scams, etc etc etc. There's tons of information out there, but 90% of it seems wrong, irrelevant, device-specific or otherwise unusable. I've already spent hours on this and still haven't gotten anywhere.
I'd be very grateful if someone actually reliable could walk me through the entire, correct process, please. :fingers-crossed:
I'm just going to write down the bits and pieces of info I already have:
I've already rooted it with Framaroot; no problems there, superuser works.
I've found this site that lists several ROMs, presumably specifically for the C1, including the standard ROM and a cleaned version: tinyurl dot com/o24wqoe. The AOSP one strikes my fancy and is on my SD card already.
The same site says I can just put the provided ROMs on my SD and install them as updates via stock recovery, but I highly doubt that because I read everywhere you specifically can't do that. Sounds like fake advice to me.
I'm told I'd need to unlock my bootloader, but once in fastboot/bootloader mode none of the offered fastboot unlock commands really do anything. The "..." appears in my console and then nothing.
I've tried installing TWRP and CWM recoveries, but you know, "your device is not supported". There's this video of a C1 with a custom recovery (watch?v=_TGgXIp3fWM) and the comments claim it's CTRecovery, but I can't even find anything about that. I already submitted requests for a fix for my device to twrp and cwm half a year ago before I bricked this thing, and one person promised he was gonna make a build for me, but nothing came from any of that.
I think that's just about all the useful things I can extract from this whole mess of information I have...
Please help me make sense of this overload of info and device-specific shenanigans, and walk me through what seems to be such a simple process for everyone with a mainstream device?
For the record, I'm back down to barely being up-to-date on what is what anymore. I'm more than familiar enough with the theoretical side (bootloaders, partitions, bios, etc) because of my heavy computer usage (professional programmer), but once I get into Android I'm just lost. All that fancy terminology nobody seems to bother to explain, things that are taken for granted but aren't really obvious (like a guy demonstrating the installation of a custom ROM, and only mentioning 10 minutes into the excessively long video that you need to install a custom this and custom that first), so many alternative methods for the same thing that have different dependencies (unlocking bootloader vs custom recovery), etc... I don't know anymore what's device-specific and what isn't, who is telling the truth, what a given tutorial is actually making me achieve in the end, etc. TL;DR I'm lost, I'm not stupid but I'm not gonna pretend to know anything about Android's subsystems anymore at this point.
wow u wrote a full post and u speaked for me as have the same problem
Custom recover
i have made a recovery for the 4015x
and got one of the roms to work
(and a fixed stock recovery)
there are 6 versions of this phone and at least two different partition tables that ive seen
but getting it back from softbrick id use the "mobile upgrade s 4.1.1" from the alcatel site
alcatel,mobiles,all mobiles, pop c1, support and on the right hand side down load the program and follow
this forces a stock rom back on the phone (no root and all data wiped)
im waighting on the mods to let me post links so i can host the roms and recoverys
but if you want to mess with the roms your self you can edit the partition tables and get the roms to install.
id use the app "diskinfo" to check what partitions your system and data etc etc are useing and chainge this in the roms.
hope this helped
p.s. if not i could poss look at editing the aosp rom for you and host if for a bit
just waighting on beeing able to post links :s
Alcatel onetouch c1 pop
MY PHONES flash light or led light comes on but it wont come on at all jus remains black wont start ....i tried restoring rom but ,it was useless ,well i used the upgrade tool and there wasnt the right models for my phone what should i do now .oh and also my phone has no stock rom from nowhere on google im so in need of getting back my phone .how can i fix a bricked or whatever phone its a alcatel one touch pop c1 4015a
What is the online USB firmware updater? Mine is also bricked
Alright, so I did a bit of a stupid thing and I acknowledge it. Anyway, here's my steps for what I did:
1). KingRooted the phone, SuperSUme'd to remove KingRoot's stuff
2). Flashed a deodexed ROM through FlashFire for OF1 using a how to list to upgrade and keep root(This is where I think I went wrong, I should have stuck with OC1 to begin with but I was curious ), the flash was successful
3). Because one of my apps(Greenify) requires the Xposed framework for many of the useful settings, I tried flashing a version of the framework designed for non-MDK bootloaders(Arter97's unofficial TouchWiz) through FlashFire, since it seems to be the only way to flash custom stuff on 5.0+ stuff at the moment
4). After this(Just like when I tried Arter's framework with regular OC1), my phone's Google apps started their mass crashing and force closing, which I tried to combat with factory resets but no dice
Unlike before, however, something along the line in my steps disabled the ability to go to stock recovery mode(I think it was KingRoot itself but it might have been the deodexed ROM) and after a bit I couldn't factory reset. Before, I was able to simply Odin flash the stock OC1 ROM. Now, however, Odin won't work either to restore the firmware. I always get the "fail" messages(This I'm not sure why, though it happens with both OC1 and OF1 ROMs so I don't think it's a matter of downgrading). This leaves me with very few options to recover from, especially because I've even tried Verizon's repair program(Stops at 83% and disconnects) and Kies' emergency recovery(Phone isn't recognized and upon manual recovery the result is the same).
The biggest thing that grinds my gears is that my phone isn't even bricked...technically. It started, it went to the Setup Wizard, but then the Setup Wizard crashed once the Gmail portion of the setup was supposed to start in an infinite loop....a "setup loop" rather than a boot loop. I have been working for hours to try and find a solution but so far nothing is working. My phone only starts to the "Software update failed, please use the Verizon Repair etc." message now but no program can recognize it.
Is this a form of hard-bricking? Just not having any method of recovery work even if it turns on? I will admit I'm not the most advanced user but I've been flashing ROMs and custom stuff(Using guides and the like, I'm not fluent enough to go freestyle) for years through a couple of different phones so I'm not a completely new user either. This is the most FUBAR'd I've gotten a phone so far though and I honestly can't afford a new one...that's why I'm going through all the paces I possibly can. Is there any possible way to salvage this? I've been wanting to go to the LG G3 anyway(Despite the G4 being out, the G3's cheaper and still miles better than any Samsung phone, my old one got stolen) but right now it's just not possible. Any suggestions?
Edit: After switching USB ports(Mine are notoriously bad for connections being gained and lost, my memory is bad but I can't see why I didn't think this was the issue), the Verizon repair method has made the phone able to start up. Everything seems to be in order now, more or less. I will say the custom Samsung screen(The unlocked one) came up which makes me think I still have the deodexed ROM installed. If so, then cool beans.