My Phone was on 4.2.2 (12B). It was rooted.
I wanted to go to 26A bootstack.
Here's what I did:
1. Installed flashify.
2. Installed TWRP recovery and rebooted in to recovery.
3. Chose install and selected the xdabbeb_vs98026a_bootstack.zip and then rebooted.
Since then all it does is to power on - shows LG logo - a few seconds later reboots again.
What should I do now please?
FIXED IT Thanks to @undeadking for his response in another thread. I followed it and now Paranoid android running on my G2.
Glad you got it running!!! There's a few things that I ALWAYS keep in a separate folder on any phone- 12B,24A,and now 26A xdabbeb's bootstack/radio zips, ROMs that I know will boot on one or more of them, supersu 2.16 zip, TWRP 2.7.0.1/2.8.0.1 (dr87's custom builds), and a stock ROM backup... Might seem a bit excessive to some people but these items(along with the "search" option on XDA) have saved/helped me more then once and may be beneficial to you as well... Anyways glad you are up and running now- check out PlainAndy 14.2 by @Snuzzo its super smooth, stable, and more vanilla instead of customization heavy--you would like it better than Paranoid Android.
@undeadking
Good to see you helped out! Feels good? Either way, what I suggest is just keeping a backup of a rooted ota and a backup of your previous ROM. No need to switch back to a different baseband and confirmed to always boot.
Yeah ive been helped/taught a hundred times by the more experienced in the forums and I know what a panic one can get in when something goes wrong haha but yeah always try to help when I can.
Related
Hey guys,
This is my first post and first rom on my D3. I have, however flashed my D1 multiple times. So I have an idea about what i'm doing, but i'm not 100%. Anyhow, I was running 5.7 since it got released OTA. Was extremely happy with the fixes that came out in that ver. Started searching around and ended up flashing Liberty3 2.0 a few weeks ago. I noticed the battery drained somewhat fast when idling. So I did some searching and installed the speedy v7 script. Even got the "it works!" file when i looked in root browser. I also made sure to wipe data, reboot multiple times, wipe battery states and click my heels 3 times.
Battery life probably improved a bit, I still dont think its as good as stock 5.7. It is probably acceptable, but I am used to charging my phone before I go to sleep. Having around 90% battery life when i wake up, and being able to run on that one charge for almost 24 hours. This may be attributed to the surprisingly good sleep policies in the stock blur battery manager. I would love to have those built in to liberty. But I think that some of it also has to do that when I flashed liberty, my version dropped to 5.6.890.
Now after reading the entire thread for Liberty3 2.0, I see that people say to "apply hascode's patch" for 5.7. The thing is, no one links it. Did some poking around and are they talking about the second link from the bottom of this page:
hash-of-codes.blogspot.com/p/android-downloads (please add .html, i am new)
If so, do i just drop it on the SD card, boot in to safestrap and apply the zip?
Sorry this is long-winded. I just wanted to explain the extent that I have gone through before asking a question.
dtr3030 said:
If so, do i just drop it on the SD card, boot in to safestrap and apply the zip?
Sorry this is long-winded. I just wanted to explain the extent that I have gone through before asking a question.
Click to expand...
Click to collapse
Yeah, just install the rom and patch, both from clockwork recovery (cwr/safestrap). That patch is for his cm7 build I believe but I would still give it a shot if I was you, worst that happens is you have to restore a backup w/cwr and it might be what you need.
Haha again no link. It's a mystery patch!
it's there. i'm a noob and cant post links. thats why i said "someone please add .html"
but here it is again:
hash-of-codes.blogspot.com/p/android-downloads . h t m l
i looked again right now and the bottom two look like rooted stock roms. the one just above that labeled "Users of OTA 5.7.894 apply this patch (after applying main .zip) md5sum 46c140b55469ab557cd053e992142223" might be what i'm after. i'm still on 5.6 tho.
hashcodes patch will work for liberty if youre installing it on 5.7.894. Yes it is for CM7, but it works for CM9/Liberty and probably all AOSP roms. I havent tried it with a blurrred rom. http://hash-of-codes.blogspot.com/p/android-downloads.html is the link (lol)
MrJudylicious said:
hashcodes patch will work for liberty if youre installing it on 5.7.894. Yes it is for CM7, but it works for CM9/Liberty and probably all AOSP roms. I havent tried it with a blurrred rom. http://hash-of-codes.blogspot.com/p/android-downloads.html is the link (lol)
Click to expand...
Click to collapse
What does it do btw?
I'm trying to figure out how to push my system to 5.7 while running liberty. Somehow I went from stock 5.7 to liberty 5.6. I still have the verizon system update on my sd card cuz I had debloated before and needed to manually update. It was 50mb I think. I don't think that will update libery tho, will it?
I assume the hashcode patch is his own system tweaks and fixes.
Thanks for sharing this. BTW, do you know how I would go to 5.7 when I already have Liberty3 2.0 running over 5.6? I have no idea how this whole bootstrap thing works... More complicated than HTC and Samsung where you'd only get bootloader and recovery...
I'm using SafeStrap 1.6 and I'd like to not delete any settings I currently have. If that is possible...
what you should do is return to stock blur 5.6.890 (i prefer to sbf but ive received a lot of flack for it). Once on stock, root, install OTA rootkeeper from market, download the 5.7.894, install via stock recovery. Restore root from OTArootkeeper, install safestrap 1.06, install recovery from within the app, restart, hit menu during boot menu, make a backup, toggle safe system, format /system (under mounts and storage), install liberty, install hashcodes 5.7.894 patch!!!, factory reset clear data/cache, boot it up.
Obviously you would lose every settting you have. the idea behind safestrap is to leave your stock system untouched, and its about as surefire as it gets.
I know a lot of people are in this sticky situation with me.
But hey guys, XDAers, Googlers, Developers & the rest of y'all
So I have a S3 Mini (with NFC so i8190N) and I hack it a lot, I mod, I do a lot of root-y stuff on it.
Well today's objective for my phone was to flash a Custom ROM that blended together TouchWiz and KitKat since I can't get that officially for my phone, I found LostVirginity V2 from the guy who made the Virginity ROMs (I forgot his name but big ups to him, thanks for the crazy cool ROMs bro!)
So I tried to flash it in TWRP.....and it didn't work because TWRP consistently freezes when I press anything and i have to do a battery pull.
Then I used Odin to flash CWM and it flashed it but when I rebooted it my phone decides to not listen and just go back to CWM like CWM has a leash on it or something, I mean come on! TWRP replaced you for a reason and you're trying to get us all back, you're old and forgotten CWM...
So now I've got that frigging annoying TWRP/CWM loop where whatever you do it just reboots to the custom recovery, pretty much the only thing I can do is use Odin to flash another custom recovery (only ones I can switch between are (any version of) CWM, PhilZ's Advanced CWM and any version of TWRP)
I've been trying everything, some guys on redmondpie, android central and rootzwiki (I think that was the website) fixed the problem on the ASUS Transformer Pad but they installed terminal emulator, I've got that but if I could access that that'd defeat the whole point of this thread because that would mean I'd have access to the Android system.
So my question is: Now that I'm imprisoned by the claws of the custom recovery, how do I escape?
Do I flash another firmware through Odin or something?
Somebody help me, and anybody who's been through this problem or is going through this problem at the moment, tell me what you did/what you're doing so we know what to rule out and stuff
Thanks guys
I started with a CM12 ROM and everything was looking good, but I decided I wanted to try a different kernel, so I made a backup and downloaded AGK and Nuk3rn3l:
http://forum.xda-developers.com/htc-one/development/kernel-agk-lollipo-v1-0-t2945268
http://forum.xda-developers.com/showpost.php?p=56831059&postcount=3
I downloaded both, since there seemed to be mixed reviews for each of them. First I installed AGK, then when that didn't seem to work, I installed Nuk3rn3l (without any wiping in between; mistake?). They both caused the phone to boot up and stick at the CM boot animation forever. I figured I was safe with my backup, so I just wiped and restored, but that didn't fix anything. Then I wiped and installed the CM12 zip I still had on the phone. That still got stuck at the boot animation.
What's causing this? Evidence suggests this was brought on by the kernels, but I thought that the kernel was overwritten when ROMs were installed or restored. Is that not correct?
So can it be fixed? And can it be fixed without losing everything on my phone?
Now that I'm home, I have more flexibility in my options. I got the AGK kernel with the Aroma installer, which was kind enough to inform me that that kernel wasn't made for Sprint. Who knew?
I just got the Elite AOSP kernel (ostensibly for Sprint) and tried flashing that:
http://forum.xda-developers.com/sprint-htc-one/development/kernel-elite-kernels-t2961835
So far, still not looking great.
I also grabbed Nuk3rn3l from the Sprint CM12 thread:
http://forum.xda-developers.com/showpost.php?p=56833611&postcount=3
I'll give that a go in a minute.
If there's something I'm doing fundamentally wrong here, I'd love to be corrected!
No luck with Nuk3rn3l. I gotta be doing something wrong...
Q&A for [ROM][5.1.1][F-AOSP i9305] The Android Open Source Project [05.06.2015]
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [ROM][5.1.1][F-AOSP i9305] The Android Open Source Project [05.06.2015]. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
rodman01 said:
have you enabled adaptive light or brightness in settings/display? If yes try to disable it and then you can adjust the brightness.
For me 2G is working, 3G and LTE I cannot test at the moment, because not available in my home area.
Click to expand...
Click to collapse
LTE is working for me!
Edit: Device is definitely running quite hot but aside from that, haven't had any issues! Thanks rodman01! btw, is there a settings menu to adjust the battery icon, button shortcuts etc that I can't see?
Great rom thanks
All working fine only 2 bugs.
The 2g/3g/4g is not stable for me
And the sensors not workink, i cant change to landscape mode in any apps.
Can you fix this bugs ???
Thanks
Which Kernel
Hello Everybody,
I read about this Rom and it sounds really cool. I am excited to try. However, this will be the first time I will flash my S3 LTE (I have flashed other devices before). So, I dont want to brick my S3 LTE. I was confused about the Kernel. Do I need a costum kernel? There are some for Android 5.1. I am running right now a stock Android 4.4.4 rom on my device. Can i just install the Rom following the tutorial on the first page or is there something special about that?
Thank you very much for helping me,
greetings
Marc
It seems my Bluetooth is not working after flashed this rom, full wiped. The phone could not find any bluetooth device and could not be found as well.
marc-132 said:
Hello Everybody,
I read about this Rom and it sounds really cool. I am excited to try. However, this will be the first time I will flash my S3 LTE (I have flashed other devices before). So, I dont want to brick my S3 LTE. I was confused about the Kernel. Do I need a costum kernel? There are some for Android 5.1. I am running right now a stock Android 4.4.4 rom on my device. Can i just install the Rom following the tutorial on the first page or is there something special about that?
Thank you very much for helping me,
greetings
Marc
Click to expand...
Click to collapse
As long as you have rooted your phone, you can just follow the steps in the OP. The kernel is installed in the rom .zip package. You can install a custom kernel over the stock one if you want to experiment with CPU settings and governors etc, but you won't get much help on this thread if you have issues like things not working properly.
At the moment there a couple of bugs that could be fixed by using agni until the next build however
Bluetooth
Did a clean install with version 20150610. Bluetooth seems not to work. Although turned on, not finding other devices and not be seen by other devices. Is this a bug? Bluetoth was working before the flashing when using Slimkat.
Regards
rom169
[5.1.1][F-AOSP i9305] The Android Open Source Project [11.06.2015]
The mod is very good. One note: You can turn off the phone to ring. I will not ring deaf
Thanks and great work on the mod
I just want to thank you for the great mod.
I have waited for a pure (more or less) AOSP mod for the S3 LTE and here you are!
Sometimes I get forced close on the Android keyboard (mostly in Whatsapp) and one or two times FC of the SMS/MMS app. But nothing serious.
Keep up the good work.
TiggaZ
I tried the new release as of 22.06.2015 and it is pretty stable.
Bluetooth is working (connects to an BT headset) but I got some forced reboots while listening to music. Maybe it was because it was Macklemore, I don't know .
After a clean reboot everything seems to work fine. I will give some more feedback about the long term stability as I use this as daily driver now.
Anyone with problems mounting external sdcard? Already tried diferent cards and filesystems and they're only recognized on the recoveries...
With version 20150622 bluetooth is working now. Thank you!
regards
rom69
sailorpito said:
Anyone with problems mounting external sdcard? Already tried diferent cards and filesystems and they're only recognized on the recoveries...
Click to expand...
Click to collapse
Same issue here... Everything else is working great though, so thanks for that ROM :good:
The sd card appears to be working when plugged directly in my PC, and I tried formatting with no success when plugged back in my phone. It's also working when in recovery.
A problem with Gapps
Hi, I tried to install this ROM, but Gapps wouldn't install. (I'm using CWM recovery 6.0.4.7)
It says:
Code:
E:Error in /storage/sdcard1/pa_gapps-modular-micro-5.1-20150410-signed.zip
(Status 6)
Installation aborted.
Any help? It seemed that at least one another person in the main ROM thread was having the same problem.
I managed to install the ROM itself with CWM at the first time and it booted successfully, but without Gapps. Then I changed the recovery to TWRP, and it let me install Gapps (I did a clean reinstall of the ROM and Gapps), but then it stuck on a bootloop. Edit: More details: the loop animation, green, red, blue and yellow "Google spheres" swaying, just keep repeating indefinitely. I don't know if that's a "loop" exactly, but the device doesn't seem to boot further than that.
Installed CWM back, and tried to do a fresh install once again, only ROM, which worked last time. However, the it still bootloops.
I wonder what's wrong. I'm doing a clean install, so why can't I reproduce the successful boot I did the first time...?
GolDDranks said:
I managed to install the ROM itself with CWM at the first time and it booted successfully, but without Gapps. Then I changed the recovery to TWRP, and it let me install Gapps (I did a clean reinstall of the ROM and Gapps), but then it stuck on a bootloop. Edit: More details: the loop animation, green, red, blue and yellow "Google spheres" swaying, just keep repeating indefinitely. I don't know if that's a "loop" exactly, but the device doesn't seem to boot further than that.
Installed CWM back, and tried to do a fresh install once again, only ROM, which worked last time. However, the it still bootloops.
I wonder what's wrong. I'm doing a clean install, so why can't I reproduce the successful boot I did the first time...?
Click to expand...
Click to collapse
Are you sure it's a bootloop? It can take a while on the first boot. A bootloop is when the phone turns itself off and on repeatedly, if it's showing the animation, just wait (10mins?).
My install of the latest version went fine using TWRP (2.8.5 IIRC).
judorange said:
Are you sure it's a bootloop? It can take a while on the first boot. A bootloop is when the phone turns itself off and on repeatedly, if it's showing the animation, just wait (10mins?).
My install of the latest version went fine using TWRP (2.8.5 IIRC).
Click to expand...
Click to collapse
Ah, okay, then it's not bootloop. My phone just hangs indefinitely on the boot animation screen. I have waited for 30 mins, and still nothing. The strangest thing is that I tried some other ROMs ([5.1.1][Cyanogenmod 12.1][UNOFFICIAL][11.06.2015] and [UNOFFICIAL] {UBER} SlimLP 5.1.1 {-o3}), and they always hang at boot. I tried Samsung 4.4 stock ROM just a moment ago, and it booted. But it's so old, ugly and clumsy I don't want to use it. I tried installing this F-AOSP again now that the stock ROM OS booted once at least, but still no success – it always hangs on boot.
But it hardly is a fault of F-AOSP since it seems to happen with almost every ROM. I wonder if I messed something up that simple data+cache+dalvik cache wipe will not heal.
I've had the same problem and found out it's a twrp problem with recent version. Flash stock and this twrp on Odin or heimdall before flashing Rom http://forum.xda-developers.com/gal...covery-i9305-cwm-philz-twrp-versions-t2694249
Sent from my GT-I9305 using Tapatalk
sailorpito said:
I've had the same problem and found out it's a twrp problem with recent version. Flash stock and this twrp on Odin or heimdall before flashing Rom http://forum.xda-developers.com/gal...covery-i9305-cwm-philz-twrp-versions-t2694249
Sent from my GT-I9305 using Tapatalk
Click to expand...
Click to collapse
That did the trick! Thank you so much!
F-AOSP or Resurrection Remix which one is more smooth and have better battery performance for i9305?
BTW, in F-AOSP. Where is the option to delete screen shot in notification area?
Quick question. Is there any reason flashing cm13 on a 20p phone would cause issues? I had to get a refurb due to boot loop and tried to load cm13 on it but ended up with no sound card. I got that fixed by kdz to 20o and then updated to 20p but I don't really like the stock ROM much and am wary about flashing CM again because the back order on this phone is ridiculous.
forvrknight said:
Quick question. Is there any reason flashing cm13 on a 20p phone would cause issues? I had to get a refurb due to boot loop and tried to load cm13 on it but ended up with no sound card. I got that fixed by kdz to 20o and then updated to 20p but I don't really like the stock ROM much and am wary about flashing CM again because the back order on this phone is ridiculous.
Click to expand...
Click to collapse
What do you mean "because the back order on this phone is ridiculous"
OK let me revise
First, you unlock bootloader, and "unlocked bootloader" appear when you turn on your device.
Next, you installed TWRP custom recovery.
Then you boot into recovery (TWRP)
Before installing (flashing) CM you first wipe your previous OS. In TWRP you Advance wipe (delvak,system,data,cach) and internal if you already backed up your data.
After completely wiping. Now you install (flash) latest CM13.
Then, after flashing complete reboot system. Don't install Gapps yet. Every thing should be working fine.
Last but not least, Gapps you install, it might be tricky because if you try to install an app that has an alternative pre installed. some problems could appear. For me Camera and keyboard the stop working.
I'm a noob myself. But if there would be a problem between a software and a hardware. I would blame it on the kernel.
Or the CM file you downloaded is corrupted.
Re download it and check the md5.
Please keep me updated. And any further Q.
Give me a like if this was helpful.
Wolf2231 said:
What do you mean "because the back order on this phone is ridiculous"
OK let me revise
First, you unlock bootloader, and "unlocked bootloader" appear when you turn on your device.
Next, you installed TWRP custom recovery.
Then you boot into recovery (TWRP)
Before installing (flashing) CM you first wipe your previous OS. In TWRP you Advance wipe (delvak,system,data,cach) and internal if you already backed up your data.
After completely wiping. Now you install (flash) latest CM13.
Then, after flashing complete reboot system. Don't install Gapps yet. Every thing should be working fine.
Last but not least, Gapps you install, it might be tricky because if you try to install an app that has an alternative pre installed. some problems could appear. For me Camera and keyboard the stop working.
I'm a noob myself. But if there would be a problem between a software and a hardware. I would blame it on the kernel.
Or the CM file you downloaded is corrupted.
Re download it and check the md5.
Please keep me updated. And any further Q.
Give me a like if this was helpful.
Click to expand...
Click to collapse
The backorder for a refurbished is about a month. My 1st G4 was rooted and running several roms but mostly cm13. It randomly boot looped after a flash and in an attempt to fix it used the LG flash utility and a 20n kdz. When it would boot it would be so laggy that it was unusable. Managed to look at logcat and saw errors related to asound device missing. Turned that phone on for a replacement at a t-mobile store and it just arrived.
The new phone came on 20n I think and I unlocked, rooted, and flashed cm13 again. After about a day I rebooted for something and got the exact same problem. After some searching I managed to find that kdz to 20o would fix it and it did. Not really sure but was thinking that maybe some filesystem change or something might have happened between versions that didn't play nice with cm13.
Not really sure this isn't my area of expertise or anything so just guessing. I'd rather not go through all this again so figured I'd ask if anyone knew any reason that cm13 could have caused it or if I'm just unlucky.
Thanks for the response though I'll make sure to double check the md5 I'm really bad about that lol
forvrknight said:
The backorder for a refurbished is about a month. My 1st G4 was rooted and running several roms but mostly cm13. It randomly boot looped after a flash and in an attempt to fix it used the LG flash utility and a 20n kdz. When it would boot it would be so laggy that it was unusable. Managed to look at logcat and saw errors related to asound device missing. Turned that phone on for a replacement at a t-mobile store and it just arrived.
The new phone came on 20n I think and I unlocked, rooted, and flashed cm13 again. After about a day I rebooted for something and got the exact same problem. After some searching I managed to find that kdz to 20o would fix it and it did. Not really sure but was thinking that maybe some filesystem change or something might have happened between versions that didn't play nice with cm13.
Not really sure this isn't my area of expertise or anything so just guessing. I'd rather not go through all this again so figured I'd ask if anyone knew any reason that cm13 could have caused it or if I'm just unlucky.
Thanks for the response though I'll make sure to double check the md5 I'm really bad about that lol
Click to expand...
Click to collapse
I see you went through a lot. Well the possibility of one of us getting this problem is low, under same consequences. Anyways, on this page, we just try to share info between each other to find the best solution. That's what its about.
Hey, thanks for sharing your experience you just added a possible problem and solution. This will be helpful for the community. About md5 google how to check it. There are really easy ways. Checking the md5 is worth it, that's for CM ROM. I believe LGUP does check for kdz automatically, since the kdz are stock.
Good luck, and don't stop sharing.