Related
hi to all. is anyone having issus with latest DLL7?
what i mean is that i made a clean install of LL7. after rooting with autoroot i installed TWRP 2.3.2.3 cause latest gave me only black screen.
but if i want to update from 2.3.2.3 to 2.3.3.1 it does never boot to recovery bur instead it gives broken Samsung n7100 screen.
it is the same if installing any CWM recovery. so Sammy has made some really weird changes with this update.
any other info. maybe bootloader downgrade just as in S3 thread. Advices
This is a little bit like my problems but I have random reboots instead. They occur almost immediately on a clean XLL7 install flashed from Odin without any root or apps installed.
Everything works perfectly in 4.1.1.
sorry to hear that. but this is nothing like that. to me this looks pretty serious. it seems like plus in security from Sammy.
as for you you can try re-install the stock rom for your phone using Kies.
all you have to do is open kies go to tools- and sellect the 2 or 3 option with your phone not connected.
write GT-N7100 and right after the serial number from your phone, follow instructins on screen.
bear in mind. this will wipe your phone.
mariosraptor said:
sorry to hear that. but this is nothing like that. to me this looks pretty serious. it seems like plus in security from Sammy.
as for you you can try re-install the stock rom for your phone using Kies.
all you have to do is open kies go to tools- and sellect the 2 or 3 option with your phone not connected.
write GT-N7100 and right after the serial number from your phone, follow instructins on screen.
bear in mind. this will wipe your phone.
Click to expand...
Click to collapse
I will try that and see what will happen.
Do not flash any recovery !!!!!!!!
They updated the bootloader so it is very dangers to flash untested mods and stuff.
Sent from my GT-N7100 using xda app-developers app
UtkarshGupta said:
Do not flash any recovery !!!!!!!!
They updated the bootloader so it is very dangers to flash untested mods and stuff.
Click to expand...
Click to collapse
I've flash the last ARHD rom 8.o which have last dll7 firmware and after note2core kernel 2.21 and all works fine. Now I won't install anything else until it's proved working on dll7.
JCVD_ said:
I've flash the last ARHD rom 8.o which have last dll7 firmware and after note2core kernel 2.21 and all works fine. Now I won't install anything else until it's proved working on dll7.
Click to expand...
Click to collapse
do not worry. he means with stock rom.
in ARHD and other custom roms bootloader is left ou of flash.
anyway. i think that sammy has changed the some partitions. twrp works but only 2.3.2.3
No the roms who are based on dll7 are safe.
The recovery imao needs to be updated.
Sent from my GT-N7100 using xda app-developers app
Do you mean that it is dangerous to flash the CWM recovery to the device when it runs XXDLL7?
I flashed the root and CWM package after flashing XXDLL7 and it seems to work (my random reboot problem is unrelated I guess since it happened even with just stock recovery in place).
Now, I have the new bootloader and radio and flashed BatteryPlus 0.2 from CWM without any problems. I flashed the CWM-root-package through Odin after flashing XXDLL7, also from Odin.
So the question is: is there a problem with CWM and other custom recoveries and the XXDLL7?
Or are we talking about flashing mods?
No it can be an issue. It's not recommended at this stage.
Sent from my GT-N7100 using xda app-developers app
If there is a problem with CWM and XXDLL7, that could perhaps explain my reboot problem in that case.
If so, I will hold off for a while and stay on my current configuration.
I have the new bootloader and radio already.
i have noticed that 4.1.2 isnt so friendly with custom recovery. I had cwm recovery and going into it, took a lot of time with 4.1.2 firmware. Maybe samsung is trying to make some higher security in 4.1.2 against custom recoveries and etc.
If they wanted they could have made it absolutely protected. No I don't think they actually wanted to increase security.
I just think the new bootloader isn't friendly with the old recovery.
Sent from my GT-N7100 using xda app-developers app
Anyone else have the issue of it just continuously trying to boot? I'm using the CWM auto-loki that's in the development section.
Reflashed it three more times. Now it freezes @ Samsung battery screen when charging, or if I wait long enough it'll unfreeze. Still loops at Slim Bean startup, what sucks though is that for one thing it mounts as an MTP device so it seems like it's on but just not initializing, another thing is that the original flash I was able to get to the slim bean battery charging screen (but obviously still couldn't turn it on)
Thinking it might be a kernel issue, since I installed ktoonsez's AOSP kernel when I installed it. Any recommendations of a kernel to use? I'm using the CWM recovery that has auto loki so, I could probably use ones made for 9500,9505, etc.
(Pasted this from the Slim Bean thread, haven't gotten an answer in like 5 hours and it's a little urgent xD. I'm on the AT&T S4 of course, any other information I'll be glad to provide. Hopefully this is just a simple fix)
I bet is related to the kernel. I have been using Slim Bean flawlessly, with none of the issues you mention. Using TWRP to flash and recover.
Sent from my SGH-I337 using xda app-developers app
Spunjah413 said:
I bet is related to the kernel. I have been using Slim Bean flawlessly, with none of the issues you mention. Using TWRP to flash and recover.
Sent from my SGH-I337 using xda app-developers app
Click to expand...
Click to collapse
What kernel are you on then, just stock?
Stock Kernel.
Sent from my SGH-I337 using xda app-developers app
I installed Slim Bean with Ktoon kernel and it worked fine. Just make sure to wipe system and the caches. It did take a little longer to boot the first time but after that it was all good.
Sent from my SGH-I337 using xda app-developers app
Isn't ktoonsez kernel for a Touchwiz based ROM?
Slim Bean is AOSP, therefore i'm not sure they jive correctly, which would clearly explain the OP's problem.
EDIT: Didn't realize he updated an AOSP based Kernel. In anycase OP, I would still attempt using the stock kernel to see if you problems get fixed.
Slim is already LOKI patched, so don't use the CWM that auto-patches, use TWRP
LostInMyHead said:
Slim is already LOKI patched, so don't use the CWM that auto-patches, use TWRP
Click to expand...
Click to collapse
Patching a patched kerenel changes nothing. Dan said if you run loki on a patched recovery or kernel it just send the original to the output. Nothing happens.
Sent from my AT&T S4 running an international ROM.
_Dennis_ said:
Patching a patched kerenel changes nothing. Dan said if you run loki on a patched recovery or kernel it just send the original to the output. Nothing happens.
Sent from my AT&T S4 running an international ROM.
Click to expand...
Click to collapse
Thanks for clarification.
LostInMyHead said:
Slim is already LOKI patched, so don't use the CWM that auto-patches, use TWRP
Click to expand...
Click to collapse
I know someone else clarified this already, but when I downloaded Slim it actually wasn't Loki patched for whatever reason, and I couldn't boot without reinstalling stock. I did download the one in the right thread, it just didn't have a boot.lok in it for whatever reason. Anyways, I'm gonna try reflashing and wiping /system another time, wish me luck. I don't have the original kernel backed up though because I'm an idiot, so does anyone have a link to that? If not I could probably scour it out somewhere, but just wondering for convenience's sake.
iKat said:
I know someone else clarified htis already, but when I downloaded Slim it actually wasn't Loki patched for whatever reason, and I couldn't boot without reinstalling stock. I did download the one in the right thread, it just didn't have a boot.lok in it for whatever reason. Anyways, I'm gonna try reflashing and wiping /system another time, wish me luck. I don't have the original kernel backed up though because I'm an idiot, so does anyone have a link to that? If not I could probably scour it out somewhere, but just wondering for convenience's sake.
Click to expand...
Click to collapse
In advanced restore boot is the kernel.
Download the ROM and addons again, you shouldnt have any issues... If you are currently on stock, do a comprehensive wipe, a manual format of system and data
LostInMyHead said:
In advanced restore boot is the kernel.
Download the ROM and addons again, you shouldnt have any issues... If you are currently on stock, do a comprehensive wipe, a manual format of system and data
Click to expand...
Click to collapse
No files found :/ I guess I'll reinstall stock, back stuff up, and do the comprehensive wipe like you said. I really, really want Slim, lol.
Edit: Well, ****. Reinstalled stock with Odin and now no matter how many times I reboot I only have a status bar.. phone is fairly hot too. So, now I don't even have access to recovery ;-;
iKat said:
No files found :/ I guess I'll reinstall stock, back stuff up, and do the comprehensive wipe like you said. I really, really want Slim, lol.
Edit: Well, ****. Reinstalled stock with Odin and now no matter how many times I reboot I only have a status bar.. phone is fairly hot too. So, now I don't even have access to recovery ;-;
Click to expand...
Click to collapse
Flash back to stcok with ODIN
Use the one click tool to get LOKI recovery
The ROM and addons are in the OP of the SLIM LOKI Thread
LostInMyHead said:
Flash back to stcok with ODIN
Use the one click tool to get LOKI recovery
The ROM and addons are in the OP of the SLIM LOKI Thread
Click to expand...
Click to collapse
Oh my lord, thank you good sir. Slim Bean is up and working as of right now ^^;. May be a little bit before I apply a custom kernel though o.o
Here's the problem: Every ROM I flash, except for one, Data does NOT work.
I flashed probably 7 AOSP ROMs today, not a single one my data worked..
I flashed TriForce Rom, it's a touchwiz ROM, 3g works perfect!
I decided to odin back to stock, No-Root, and my Data isnt working.. my phone isn't even rooted...
What's going on, any help? I am on sprint. My phone is currently not rooted, and data still doesn't work.
DustCrow said:
Here's the problem: Every ROM I flash, except for one, Data does NOT work.
I flashed probably 7 AOSP ROMs today, not a single one my data worked..
I flashed TriForce Rom, it's a touchwiz ROM, 3g works perfect!
I decided to odin back to stock, No-Root, and my Data isnt working.. my phone isn't even rooted...
What's going on, any help? I am on sprint. My phone is currently not rooted, and data still doesn't work.
Click to expand...
Click to collapse
Sounds like you lost your radio one way or another, if baseband/software version is unknown you need to flash the modem, MJA 4.3 if that's what you are on, also if you are using twrp or anything else I would highly recommend using Philz latest recovery, with Philz recovery prior to making a back up you need to change Nandroid settings, specifically making sure the selinux 4.3 box is checked. One more thing you need to do the modem flash while on a TW ROM. I guess now a few questions, what are you on now 4.2.2 or 4.3, did you ota yet? And what recovery are you using :thumbup:
Sent from my SPH-L720 using Tapatalk
ParkerParker said:
Sounds like you lost your radio one way or another, if baseband/software version is unknown you need to flash the modem, MJA 4.3 if that's what you are on, also if you are using twrp or anything else I would highly recommend using Philz latest recovery, with Philz recovery prior to making a back up you need to change Nandroid settings, specifically making sure the selinux 4.3 box is checked. One more thing you need to do the modem flash while on a TW ROM. I guess now a few questions, what are you on now 4.2.2 or 4.3, did you ota yet? And what recovery are you using :thumbup:
Sent from my SPH-L720 using Tapatalk
Click to expand...
Click to collapse
Hey I really appreciate you reaching out to me, I'm apologize, I'm such a noob with all of this and your reply seems very helpful.. but I'm not really familiar with most of that.
I'm unrooted right now, should I root, and then what should be my next step?
So, I'm new to the locked bootloader scene. The root & ROM threads, tutorials, and videos seem to root via a Terminal Emulator process, then install Safestrap. Those same sites and videos say that when you're flashing a ROM after selecting a new ROM Slot, you have to flash "whatever modules and packages are for your device", whatever that means. Since I can't find these packages anywhere, is it safe to assume that I can just root, install Safestrap, create a ROM Slot, and start flashing away as if nothing's up? Or do I need to worry about this boot patch and some "Loki Doki" thing I heard about. I'm sure these answers exist, and I've done my due diligence, but these threads have either been buried for good, or are such a common a knowledge subset that I can't find anything concrete. Even the videos I've seen talk about the "modules" you have to flash. I'm an experienced Androidist, tinkerer, and tweaker. The information I'm finding doesn't provide you with the big picture. It's all, "MJ2 read this, and follow these 9 steps", and "mk2 follow these 10 steps". But none of them tell you what to do in Safe strap recovery, and if you needs some Loki/module magic.
Help a brotha out? I'll return the favor 10-fold, I can promise you that much. I'll be quite active around here.
Thanks!
Sent from my Nexus 7 using XDA Premium HD app
First off you never said what baseband you were on but assuming that your on MK2 android 4.3 then let's start.
Use this method to root your device
http://forum.xda-developers.com/showthread.php?t=2569827
Since your on mk2 you can ONLY use safe strap 3.71 do not attempt to install safe strap 3.65 AND SAFE STRAP WILL BE THE ONLY RECOVERY YOU CAN INSTALL!
http://forum.xda-developers.com/showthread.php?t=2448925
And note that 3.71 is still in beta as of right now there are still bugs and YOU CAN ONLY FLASH A COUPLE OF ROMS.
From the same thread cause I know your not going to go through the forums and read, download the attmk2module.zip that ted77usa posted
http://forum.xda-developers.com/showthread.php?t=2448925
Root your device
Install safestrap after install, install recovery in safestrap apk.
There's only a few Roms you can flash
Darthstalker x in the att android development forum
Hyperdrive 12 in the Verizon android development forum download the one that says safestrap
A few have noted that some other Roms work but I haven't tested it out do some more reading.
After you download a rom
Reboot your device and go into safestrap recovery
Create a ROM slot ON ROM SLOT 1
DO NOT MESS WITH YOUR STOCK SLOT!
After creating a ROM slot go to install and install your rom.
After successfully installing a ROM reboot then go back into recovery and install the attmk2module.zip
Reboot and instead of going into recovery this time continue
It will take awhile to load its normal.
Now you should have a ROM.
Now go tinker with that.
AT&T SGH-I337 RUNNING HYPERDRIVE 12
ATTMK2kernelmodules Original Post i don't think u would like to go over 1000 post on that thread..... and at the bottom there is SHOstock_v3.0_Safestrap_Ready link that also confirmed work by several people.......hope this help u to get start it..... .
Bootloader:................Use:...................Custom Rom:
MDL/MDB.......................LOKI.....................4.2.2......4.3.....4.4 ALL WORK (....LUCKY U....)
MF3................................SS-v3.65................ONLY FLASH 4.2.2 ROM (Slot1,Slot2 and Stock ALL WORK)
MK2................................SS-v3.71................SOME 4.3 ROM WORK (Slot1,Slot2 and Stock ALL WORK (confirmed))
[email protected] said:
First off you never said what baseband you were on but assuming that your on MK2 android 4.3 then let's start.
Use this method to root your device
http://forum.xda-developers.com/showthread.php?t=2569827
Since your on mk2 you can ONLY use safe strap 3.71 do not attempt to install safe strap 3.65 AND SAFE STRAP WILL BE THE ONLY RECOVERY YOU CAN INSTALL!
http://forum.xda-developers.com/showthread.php?t=2448925
And note that 3.71 is still in beta as of right now there are still bugs and YOU CAN ONLY FLASH A COUPLE OF ROMS.
From the same thread cause I know your not going to go through the forums and read, download the attmk2module.zip that ted77usa posted
http://forum.xda-developers.com/showthread.php?t=2448925
Root your device
Install safestrap after install, install recovery in safestrap apk.
There's only a few Roms you can flash
Darthstalker x in the att android development forum
Hyperdrive 12 in the Verizon android development forum download the one that says safestrap
A few have noted that some other Roms work but I haven't tested it out do some more reading.
After you download a rom
Reboot your device and go into safestrap recovery
Create a ROM slot ON ROM SLOT 1
DO NOT MESS WITH YOUR STOCK SLOT!
After creating a ROM slot go to install and install your rom.
After successfully installing a ROM reboot then go back into recovery and install the attmk2module.zip
Reboot and instead of going into recovery this time continue
It will take awhile to load its normal.
Now you should have a ROM.
Now go tinker with that.
AT&T SGH-I337 RUNNING HYPERDRIVE 12
Click to expand...
Click to collapse
You're perfect in every way. ? Bromance FTW
You even answer threads like me. This helped a TON! I owe ya one.
Edit: last question. The instructions say to install the ROM, reboot, then install the modules. I assume that the reboot instruction means that we should reboot, boot into the ROM for the first time, then boot back into recovery and install the modules?
Or should I flash the ROM, power down, then boot into recovery (ensuring that the ROM is never booted before the modules are installed)-- I suppose I could just use the reboot recovery option in the Safestrap TWRP.
Sent from my Nexus 7 using XDA Premium HD app
ted77usa said:
ATTMK2kernelmodules Original Post i don't think u would like to go over 1000 post on that thread..... and the on the bottom is SHOstock_v3.0_Safestrap_Ready link that also confirmed work by several people.......hope this help u to get start it..... .
Bootloader:................Use:...................Custom Rom:
MDL/MDB.......................LOKI.....................4.2.2......4.3.....4.4 ALL WORK (....LUCKY U....)
MF3................................SS-v3.65................ONLY FLASH 4.2.2 ROM (Slot1,Slot2 and Stock ALL WORK)
MK2................................SS-v3.71................SOME 4.3 ROM WORK (Slot1,Slot2 and Stock ALL WORK (confirmed))
Click to expand...
Click to collapse
What's SHOStock? An alternative to the ATTMK2Module?
<3 I can see that this is a bangin' start to an awesome and new relationship, between me, my S4, and my new home...the S4 community.
Sent from my Nexus 7 using XDA Premium HD app
By the way...since the ROM selection is limited, I assume heavy XPosed use is okay, and quite common?
Which ROM do you guys prefer?
I assume that sites and articles like this one: http://www.droidviews.com/best-custom-roms-for-att-samsung-galaxy-s4-sgh-i337/
aren't reliable sources--they probably don't take into account the the ATT S4 compatibility issues. This is showing CM11, Carbon, KangaBean, Infamous...am I correct in my assumption that those are for the lucky birdies that had MDL/MDB, and didn't need Safestrap?
Has someone put together a compatibility/guide megathread? I think I will if it hasn't been done.
Sent from my Nexus 7 using XDA Premium HD app
Jamesyboy said:
What's SHOStock? An alternative to the ATTMK2Module?
<3 I can see that this is a bangin' start to an awesome and new relationship, between me, my S4, and my new home...the S4 community.
Sent from my Nexus 7 using XDA Premium HD app
Click to expand...
Click to collapse
Welcome aboard!!!! Firstable are u on MF3 firmware or MK2 frimware......? both are using SafeStrap (SS) as custom recovery as of right now. Like i said on previous post MF3 use SS-v3.65 so that u able to install only 4.2.2 TW custom rom or 4.2.2 Google Play Edition (GPE) rom. If u are on MK2 firmware u can only use SS-v3.71 and able to install some of 4.3 custom rom (SHOstock-v3.0-Safestrap-Ready) is one of them that worked......Hyperdrive-RL12 from verizon thread also seem pretty good but u need to add your APN manually if u are on ATT network. Both firmware MF3 and MK2 are use different kernel modules, so after flashing custom Rom you NEED to flash your current firmware kernel modules also, otherwise u won't be able to connect to WiFi,bluetooth,gps etc..... hope this make sense to you......i know is kinda confusing ......but the more u read is the more it would make sense.... Check this thread for list of compatible rom Official AT&T S4 Safestrap Discussion Q/A
One more thing. My S4 will be here tomorrow. Let's say I get lucky and find MDL/MDB on my device. Do I need to hurry and avoid a software update, or avoid a data connection? Or do the updates proceed only with user interaction? The rooting is the same for all 3 devices, but if I do get MDL/MDB or the next one, I'll have to update the baseband before flashing newer ROMs, right?
Sent from my Nexus 7 using XDA Premium HD app
ted77usa said:
Welcome aboard!!!! Firstable are u on MF3 firmware or MK2 frimware......? both are using SafeStrap (SS) as custom recovery as of right now. Like i said on previous post MF3 use SS-v3.65 so that u able to install only 4.2.2 TW custom rom or 4.2.2 Google Play Edition (GPE) rom. If u are on MK2 firmware u can only use SS-v3.71 and able to install some of 4.3 custom rom (SHOstock-v3.0-Safestrap-Ready) is one of them......Hyperdrive-RL12 from verizon thread also seem pretty good but u need to add your APN manually if u are on ATT network. Both firmware MF3 and MK2 are use different kernel modules, so after flashing custom Rom you NEED to flash your cureent firmware kernel modules also otherwise u won't be able to connect to WiFi,bluetooth,gps etc..... hope this make sense to you......i know is kinda confusing ......but the more u read is the more it would make sense....
Click to expand...
Click to collapse
It makes sense, I'm mostly just unfamiliar, as opposed to being completely useless, but you guys have been amazing...you've already shot me up to about 80% on a distribution curve.
Why would anyone stick with MF3? MK2 is an update for MF3, right? Why don't those users update, then safestrap 3.71 it, so they can use 4.3 roms? It'd seem kinda funky to me to be stuck with a 4-2 ROM by choice, unless they're doing it solely for the GPE ROM.
These firmware kernel modules...I'll have the same modules for each ROM I flash right? Or are these modules a .zip that I'll find in each ROM thread, for each carrier.
By the way, APN settings don't scare me. Here, you might actually appreciate this work--done right after ATT's LTE network came online (I believe the Note was the first device that utilized it?...If it wasn't, it was definitely the first to tax the network.)::
http://forum.xda-developers.com/showthread.php?p=26877683
Edit: the Q&A thread for Safe strap was reasonable...but it still talks about kernel flashes, and blown QFusee (har?)
I guess I mainly need to come to grips with the kernel situation. The Q&A says that you can't use custom kernels if you've updated to OTA, but doesn't mention factory MF3 builds, and it isn't really very clear about the module/kernel module situation.
You said I need to flags my **current** firmware kernel modules: are those different if I get a device with MF3 than those for MK2? Or are these just modules that I create myself (based upon whatever's in my stock ROM slot maybe?) in recovery?
Sent from my Nexus 7 using XDA Premium HD app
Jamesyboy said:
One more thing. My S4 will be here tomorrow. Let's say I get lucky and find MDL/MDB on my device. Do I need to hurry and avoid a software update, or avoid a data connection? Or do the updates proceed only with user interaction? The rooting is the same for all 3 devices, but if I do get MDL/MDB or the next one, I'll have to update the baseband before flashing newer ROMs, right?
Sent from my Nexus 7 using XDA Premium HD app
Click to expand...
Click to collapse
I dont think u can get MDB/MDL firmware again these days.....but if u do....damn u are pretty lucky....my suggestion is Do Not insert your ATT sim card yet ....since they can do OTA update ( On The Air ).....and check your baseband....IF u do ....root it right away....install titanium back up and freeze/uninstall ATT software update.apk......install custom recovery CWM or TWRP ..... and make sure u have auto loki recovery....if not save loki.doki patch on your Sd Card....PM me for the link and all the files .....i still have the files since i used to have MDB firmware and got replacement phone from ATT when my son broke the screen....:crying:
Jamesyboy said:
It makes sense, I'm mostly just unfamiliar, as opposed to being completely useless, but you guys have been amazing...you've already shot me up to about 80% on a distribution curve.
Why would anyone stick with MF3? MK2 is an update for MF3, right? Why don't those users update, then safestrap 3.71 it, so they can use 4.3 roms? It'd seem kinda funky to me to be stuck with a 4-2 ROM by choice, unless they're doing it solely for the GPE ROM.
These firmware kernel modules...I'll have the same modules for each ROM I flash right? Or are these modules a .zip that I'll find in each ROM thread, for each carrier.
Sent from my Nexus 7 using XDA Premium HD app
Click to expand...
Click to collapse
MDB>MDL>MF3>MJ6>Mj9>MK2.......the reason of the update is ATT trying to lock bootloader so we won't be able to install custom rom or do what ever we want to the phone.......but either way.....XDA member always found away to cracked it....so some people have to upgrade not by choice.....most of them by accident....like me ( cracked my screen ) or they install wrong recovery.....(bricked) so be careful when installing custom recovery.....like i said....we need to know what kinda firmware that u have so we can help u.....LOL now i got it why u dont know yet....since u dont have the phone yet.......... but is ok.....that's the right thing to do.....get to know your stuff first before u brick your phone.....:good: so basically u need to match your kernel modules with your firmware otherwise it won't be able to connect to Wifi,bluetooth,gps,etc it doesn't matter if u OTA to MF3 or MK2.....or it come with MF3 or MK2....
ted77usa said:
I dont think u can get MDB/MDL firmware again these days.....but if u do....damn u are pretty lucky....my suggestion is Do Not insert your ATT sim card yet ....since they can do OTA update ( On The Air ).....and check your baseband....IF u do ....root it right away....install titanium back up and freeze/uninstall ATT software update.apk......install custom recovery CWM or TWRP ..... and make sure u have auto loki recovery....if not save loki.doki patch on your Sd Card....PM me for the link and all the files .....i still have the files since i used to have MDB firmware and got replacement phone from ATT when my son broke the screen....:crying:
MDB>MDL>MF3>MJ6>Mj9>MK2.......the reason of the update is ATT trying to lock bootloader so we won't be able to install custom rom or do what ever we want to the phone.......but either way.....XDA member always found away to cracked it....so some people have to upgrade not by choice.....most of them by accident....like me ( cracked my screen ) or they install wrong recovery.....(bricked) so be careful when installing custom recovery.....like i said....we need to know what kinda firmware that u have so we can help u.....LOL now i got it why u dont know yet....since u dont have the phone yet.......... but is ok.....that's the right thing to do.....get to know your stuff first before u brick your phone.....:good:
Click to expand...
Click to collapse
Groovy! I'll check back in tomorrow! Happy New Years!
(Sent you a PM, as well.)
Sent from my Nexus 7 using XDA Premium HD app
Hey everyone, sorry if this question has been answered already. I have sifted through pages and pages in this forum and haven't found a solution for my D800.
My G2 is rooted, with TWRP installed. I was successful in flashing Paranoid Android v4 beta 4, and 5. The problem arises when I try to flash LG Stock based ROMS. After TWRP says flashing was successful and I try to reboot, the screen shows LG logo for a second and turns blank!! That's it just a clear black screen, and the ROM doesn't boot at all.
The ROMs I tried and failed to boot:
1. Aeon
2. Korean stock based rom
3. Scott's CleanROM
4. Rayglobe 3.2
5. Rayglobe Flex ROM v4
Now, I know that sometime ROMs take time to boot on the first run, so I even tried leaving it at the blank screen for 15-20 mins with no result. Since it has been the same result for multiple ROMs, it definitely isn't a bad install or a bad ROM download either. I hope not
Is there anything I am missing in the steps? All ROMs were installed after factory resetting through TWRP (no dirty flash). I am baffled with this, please let me know if I need to revert to software version "d" for these ROMs to work?
TIA
vish9 said:
Hey everyone, sorry if this question has been answered already. I have sifted through pages and pages in this forum and haven't found a solution for my D800.
My G2 is rooted, with TWRP installed. I was successful in flashing Paranoid Android v4 beta 4, and 5. The problem arises when I try to flash LG Stock based ROMS. After TWRP says flashing was successful and I try to reboot, the screen shows LG logo for a second and turns blank!! That's it just a clear black screen, and the ROM doesn't boot at all.
The ROMs I tried and failed to boot:
1. Aeon
2. Korean stock based rom
3. Scott's CleanROM
4. Rayglobe 3.2
5. Rayglobe Flex ROM v4
Now, I know that sometime ROMs take time to boot on the first run, so I even tried leaving it at the blank screen for 15-20 mins with no result. Since it has been the same result for multiple ROMs, it definitely isn't a bad install or a bad ROM download either. I hope not
Is there anything I am missing in the steps? All ROMs were installed after factory resetting through TWRP (no dirty flash). I am baffled with this, please let me know if I need to revert to software version "d" for these ROMs to work?
TIA
Click to expand...
Click to collapse
Did you factory reset after as well? If I recall correctly Paranoid Android is AOSP. What kernel are you running?
sounds like you are onn the 10o update. You will need to flash back to stock 10d with lg flash tool and then root and install recovery again. Then you should be good to go on flashing roms. I know that some of the newest versions of TWRP and Philz have issues flashing some roms too so that may also be the cause. If you downgrade the recovery you have to the version right before it may fix your issue also
joebob296 said:
Did you factory reset after as well? If I recall correctly Paranoid Android is AOSP. What kernel are you running?
Click to expand...
Click to collapse
Exactly, AOSP ROMs are booting up fine but not the Stock based ones.. I am not flashing any kernels, just the ROM, so I'm assuming it will run on either the stock kernel or the kernel included in the ROM zip?
Have you been successful in installing such ROMs? Am I missing something in the wiping part? Only been doing the factory reset in TWRP before installing any ROM.
Check m
And make sure that you are running the stock kernel. Are you on the 10o update?
Sent from my LG-D801 using Tapatalk
rquiett said:
sounds like you are onn the 10o update. You will need to flash back to stock 10d with lg flash tool and then root and install recovery again. Then you should be good to go on flashing roms. I know that some of the newest versions of TWRP and Philz have issues flashing some roms too so that may also be the cause. If you downgrade the recovery you have to the version right before it may fix your issue also
Click to expand...
Click to collapse
Oh, I hadn't thought about anything being wrong with the recovery.. Always assumed it gets the work done
How do I find previous versions of TWRP compatible with D800?
joebob296 said:
Check m
And make sure that you are running the stock kernel. Are you on the 10o update?
Sent from my LG-D801 using Tapatalk
Click to expand...
Click to collapse
Yes I am on 10o.. Does it have issues with installing other Stock ROMs? If yes, I'll try to follow the thread on using LGFlash tools, I've never done that before. Hopefully its not much difficult to follow the instructions.
That is one of the easiest guides to follow. Be sure to follow the correct set of instructions(depends on carrier) and download the the 10d version.
Sent from my LG-D801 using Tapatalk
joebob296 said:
That is one of the easiest guides to follow. Me sure to follow the correct set of instructions(depends on carrier) and download the the 10d version.
Sent from my LG-D801 using Tapatalk
Click to expand...
Click to collapse
Thanks.. I'll try to do it tonight and post my results here.
joebob296 said:
Be sure to follow the correct set of instructions(depends on carrier) and download the the 10d version.
Sent from my LG-D801 using Tapatalk
Click to expand...
Click to collapse
I'm stuck in the process! Can't change the com port number to 41. The guide is pretty easy to understand. But when I put my phone is download mode and try to change the com port number, it says I don't have the write privileges for this device's setting. I've tried it on both Win 7 and Win 8 laptops, with LG mobility drivers installed.
Is there something in the phone settings I need to enable so that I get the write privileges to change com port number?
Do you have administrator privileges?
Sent from my LG-D801 using Tapatalk
SOLVED!
joebob296 said:
Do you have administrator privileges?
Sent from my LG-D801 using Tapatalk
Click to expand...
Click to collapse
Yay!!! Finally did it!
Issue 1: If faced with write privileges for com port (tried successfully in Win 8)
Solution: After going in to com port properties, click "change settings" and there is the option to change com port number.
Issue 2: Once the port number was changed to 41, rest of the instructions are easy to follow on this thread http://forum.xda-developers.com/showthread.php?t=2633150
Once on D80010d, I rooted with ioroot22, and installed recovery using FreeGee. Just installed Rayglobe 3.2 minutes ago, and it finally booted up!!!
So, the bottomline is that go back to D80010d if you wanna play with Stock based ROMs! I flashed with TWRP 2.6.3.3, so the fault is not with the recovery. That much I can confirm
Thanks for the suggestions guys. Thread solved I guess.
Great. Glad to hear it.
Sent from my LG-D801 using Tapatalk
rquiett said:
sounds like you are onn the 10o update. You will need to flash back to stock 10d with lg flash tool and then root and install recovery again. Then you should be good to go on flashing roms. I know that some of the newest versions of TWRP and Philz have issues flashing some roms too so that may also be the cause. If you downgrade the recovery you have to the version right before it may fix your issue also
Click to expand...
Click to collapse
Thanks for the input. Before I flashed back to D80010d today, I installed older versions of Philz and TWRP but neither helped. So downgrading was sort of a compulsion, in my case at least.
and the moral of the story is, unless you are getting an android version upgrade in the update, do not take the update.