[Q] I have searched enough: Recovering Backup with CWMOD - G Tablet Q&A, Help & Troubleshooting

OK:
Briefly, Running fine on VEGAn 7 RC 1 with Pershoot's latest. When the Tab was running and booting, I made a full backup in CWMod.
Screwed around with some permissions and once I rebooted, ended up at VEGAn Tab pulsating Boot Screen. It would do its thing for a minute or so, screen would go blank and then return immediately to the same VEGAn Tab screen (i.e., not a full boot).
Not a problem, right? I just booted into CWMod, cleared out everything and restored my earlier backup.
No go. Same loop at the VEGAn screen.
I searched the forums a lot, so either I am not very good at searching or this has not been addressed.
Advice would be appreciated, as this is not the first time I have been here and want to learn if there is a way to repair it (obviously, I can reflash ROM+Kernel) restore via Titanium and only have a little manual recovery left to do.
Thanks!

I had the same thing happen to me while i was changing around roms. I know its not the exact thing but regardless. Anyways, try mounting your tab in cwm as USB and pull your back up off the tabs memory. Go back to cwm and wipe everything, then repartition to advised settings. Remount your tab as usb and put the back up back on your drive and restore again. It may work.
Sent from my VEGAn-TAB using Tapatalk

iamjakecali said:
Not a problem, right? I just booted into CWMod, cleared out everything and restored my earlier backup.
No go. Same loop at the VEGAn screen.
Click to expand...
Click to collapse
If its something simple, clearing the Dalvik Cache in CWM might fix it.

I appreciate the ideas. Unfortunately i have tried then all. One of the times this has happened i was messing around with the old two taps xoom. Of i knew anything about the really technical stuff i might speculate something to do with boot loader.
Oh for anyone here who bricks, Don't freak... sometimes i do several times a day and have always come back from it ... mostly using the advice of all the brilliant people here, occassipnaly by messing around with adb, and once i let my monkey push random keys since he had already managed to compose a sonata...

Related

[Q] 1st day with Vibrant lots of questions need some OCLF ROOT help

Although I only had the phone for a day now, I've been reading the forum for a month trying to get the info I needed so that when it arrived, I'd be able to load up froyo, wifi calling and be done quickly. I set it all up and downloaded ryan's OCLF, ran it, rooted, installed the ext files, then the v2 lag fix it said to. Everything was great.
Later I downloaded a few apps and titanium backup, but didn't back up yet. I ran the battery down low. Went into the clockwork app that I downloaded and did a backup restore.
About an hour later the battery finally died. I read that you should turn it on until it won't anymore before finally plugging in to charge and wiping the battery settings. Problem is it wouldn't boot up again. Hung on the Galaxy S screen with the shining S.
I could still reboot into recovery and into download. Was going to ODIN back, but my PC was giving me trouble. I pulled the micro sim and thre the ASOP 2.2 rom on it from another laptop dragged it to card removed and popped it back in. I tried to reboot to recovery which worked, then reinstall, nothing. Tried to get to the SD card, but it doesn't find it.
Finally gave up and went back into recovery and did a factory data wipe reset or whatever it is called. When the phone rebooted it all booted fine, no problems at all however I lost every setting account etc..
So here's where I'm at now, i mounted it as USB and looked at the phone from the PC, in the clockwork folder is my backup I just can't get it to load.
I went back to the market and redownloaded the ryan OCLF and removed the lag, ext and root and I'm back to stock. Phone will turn off and back on.
What now? Where did I go wrong, it doesn't make any sense, I followed every instruction exactly as it was written.
I'm a little concerned to root again, but I want to backup settings, accounts etc.. in case this happens again.
first...welcome to XDA...the baddest forum on the planet...
second....this is the wrong section for this topic....should be in Q & A section...but a Mod will take care of that....
third....read this.....http://forum.xda-developers.com/showthread.php?t=849028
the author worked hard on this to become a sticky so noobs will see it first...if u need more info....there is another sticky in the general section...good luck!!
Thanks, I'll read through it now. I thought I had a good idea to drag the new rom to the sd card and fire it up from there, but it failed. Happy I didn't brick the phone. I saw a lot of posts saying ODIN was the only way back, guess I got lucky with the data wipe.
I've had iphones for 2 years and when this happened it would be a conflict with programs, is there a list like that for android like there was for cydia in the iphone info?
I don't know.... but make sure you read carefully before you flash... in a nutshell the steps for ROM flashing is.
1. Root
2. Download and install ROM Manager from market
3. Flask clockwordmod recovery
4. Nandroid (backup)
5. Backup SD card to pc(just in case)
6. Flash your ROM from clockworkmod recovery.
Sent from my XDA app cuz I'm stalking your mom....
Here's a question I don't think is answered after reading the post. So rooting via OCLF without installing the lag fix v2 is exactly the same as rooting by dragging and dropping.
Rooting in itself can't cause the phone to not reboot, but if you flash incorrectly or apply lag fix and flash over them you could run into trouble. I just can't seem to figure out where the error was. I didn't delete the update zip after rooting, thats the only error I see.
Other issue I noticed is that on mounting to USB after booted I can see the backups, but I can't locate the ROM zip I put on the SD card or the SD card at all.
So let me get this straight... you rooted via OCLF.. but did not apply the lagfix?
Edit: oh I see... u tried to flash a froyo Rom then go back to stock?...
Sent from my XDA app cuz I'm stalking your mom....
No I rooted then applied the lag fix it had available which was version two I believe
Sent from my SGH-T959 using XDA App
Ok... try ODIN back to stock...make sure you have the correct drivers
Sent from my XDA app cuz I'm stalking your mom....
Let me correct what I'm saying, the phone went into the stuck glowing S screen when trying to turn it back on after I ran the battery down to nothing. It wouldn't boot past that point. I tried reinstall, reboot, etc..from the menu in clockwork recov in recov screen as that was all i could get to. When that failed I tried just loading a 2.2 ROM to the sd card direct from my laptop, thought I could just flash from that screen right over everything, didn't work either. Thats when I tried delete all info as a last effort, but then it magically booted back 100% stock, but still rooted. So i reloaded OCLF and unrooted because I don't know what caused the phone to be stuck in the S screen, I didn't flash anything, just did the root and oclf all from ryan's OCLF app
I tried to reroot manual, didn't work, lots of issues, wouldnt root. Went back for OCLF gone. Went for the z4 gone. Found links for both, tried the z4 didnt' work, superuser continiously popping up for permissions, went back removed that and reloaded oclf from web, ran and fixed boot and rerooted, all good. Went back and downloaded and flashed Vibrant AOSP ish JK2 1.1 Official FROYO. Absolutely love it so far. I've been waiting for wifi calling for a long time, it actually works. Problem is I'm not really sure if I rebackup everything now or leave the backups I have from clockwork for stock. I keep reading everything and feel like I'm missing something. I have Vibrant AOSP ish JK2 1.1 Official FROYO saved so I guess if it crashes I just reflash that and don't need a backup, but should titanium backup the whole thing instead now? Sorry if no one replies i get it. Two years of iphone jailbreaking is a waste, nothing like this at all! I will say I never bricked an iphone, feel like i'm gonna brick this thing.
I want to run the OCLF v2, but concerned it's going to cause issues as it's running so smooth right now.
It works fine
Sent from my SGH-T959 using XDA App
version 2 isn't an option, i'm running lag fix one, seems ok I'm having some other issues, but its running
If your still having problems odin back to stock and start over it always safer and will cause less problems
Sent from my SGH-T959 using XDA App
All my issues were because busy box was messed up, all good now
Sent from my SGH-T959 using XDA App
Just to throw it in there... you should always backup your current ROM and all apps using both ROM Manager AND Titanium Backup. It makes it THAT much easier if you do, by chance, have to use ODIN or run a recover, to get your settings, apps, saved data, etc. back without much hassle.
I run a Titanium backup on all of my apps I have loaded (NOT SYSTEM APPS as they are backed up by ROM manager I believe) once a month or so, just to keep fairly recent. It makes it to where, if it does need to be restored, the apps all get re-installed at once including saved data within the app (saved game progress, etc.). This is handy because you don't have to remember what all you had installed and you don't have to go searching through marketplace to get those apps back.
If you are running a custom homescreen (Launcher Pro, etc.), you should also use their backup option to save your homescreen settings.
In short, backup everything you can... it makes 3 hours worth of reloading things condense into a nice little 10-15min "install", "ok" button pressing fiesta!
And, to let you know, I've (as just about 100% of XDA users) flashed, and ODIN'd nearly a thousand times and have yet to brick a phone. These things are crazy indestructible. There's 3 or 4 different ways to get into Download Mode if you get the computer!phone screen... so don't worry about it. The only thing you really lose is time spent getting things back to normal if you screw up. But read up on everything, which it sounds like you already do, before you even attempt anything that could kill the phone. I don't post much on here because just about everything is already answered... you just have to search a little bit.

[Q] G tablet stuck in bootloop permanently

Sorry guys, this thread could go on and on for a long time explaining what all has happened so I'll put the current problem here and all the junk that led up to it below in case anyone wants to troubleshoot.
First of all my MOST thanks to Roebeet the best most patient person I have worked with. I wish I could give 1000 thanks at once.
The current problem is that I am stuck in a bootloop that not even nvflash will recover. No matter what I do even Vol+/Pwr just leads to big triangle exclamation. Because I nvflashed it back to stock and tried to (stock security wipe/factory). Viewsonic/Gtablet boot loop over and over. Vol-/Pwr allows access to APX mode works, but flashing nvflash, result bootloop.
How did I get here?
- March 10th z4root, vegan 5.1, perfect. No issues, great!
- March 15th got a bright idea to run ubuntu on it. Followed steps perfectly, no go.
Magic Value Mismatch. Panic (flashed with nv flash, got tnt 5.00)
- March 16th Worked great but wouldn't copy any apps to sd. Got titanium backup to
move user apps to sd. Titanium crashed and I lost all my user apps. Frustrated so
decided to flash nv again and go back to Vegan. No go.
- Tried several different ways to run nv, update to 3885, z4root, cw.08 no go
- Tried nv, stock, wipe, cw.08 no go
- Tried nv, 3885, no cw, pwr/vol+, bootloop permanent.
- Apx linux install successful, bootloop permanent
i'm stuck in bootloop too.
I'm no expert, but just out of curiosity, have you tried to get back into CW and format your SD to 2048/256? Maybe the partition is hosed?
1st, try to FORMAT with this tools: http://forum.xda-developers.com/showthread.php?t=974422
you can change the image #9 with CW, once format done, when it reboot, you will have a message error in RED just power it off and on again, you will be in recovery mode, now follow the NVFLASH here:
http://forum.xda-developers.com/showthread.php?t=861950
also you can change image#9 to CW this will get you back to the base of stock VS rom
good luck
Wysdym said:
Sorry guys, this thread could go on and on for a long time explaining what all has happened so I'll put the current problem here and all the junk that led up to it below in case anyone wants to troubleshoot.
First of all my MOST thanks to Roebeet the best most patient person I have worked with. I wish I could give 1000 thanks at once.
The current problem is that I am stuck in a bootloop that not even nvflash will recover. No matter what I do even Vol+/Pwr just leads to big triangle exclamation. Because I nvflashed it back to stock and tried to (stock security wipe/factory). Viewsonic/Gtablet boot loop over and over. Vol-/Pwr allows access to APX mode works, but flashing nvflash, result bootloop.
How did I get here?
- March 10th z4root, vegan 5.1, perfect. No issues, great!
- March 15th got a bright idea to run ubuntu on it. Followed steps perfectly, no go.
Magic Value Mismatch. Panic (flashed with nv flash, got tnt 5.00)
- March 16th Worked great but wouldn't copy any apps to sd. Got titanium backup to
move user apps to sd. Titanium crashed and I lost all my user apps. Frustrated so
decided to flash nv again and go back to Vegan. No go.
- Tried several different ways to run nv, update to 3885, z4root, cw.08 no go
- Tried nv, stock, wipe, cw.08 no go
- Tried nv, 3885, no cw, pwr/vol+, bootloop permanent.
- Apx linux install successful, bootloop permanent
Click to expand...
Click to collapse
Can you get back to a state where you can at least get into CWM, even if it is still bootlooping? If so, go into the advanced settings and perform a fix partition (use the settings 2048 / 0). Please note, this will wipe any data you have on your /SDCARD folder (which is the flash card disk installed on your gtab, not the microSD card you may be using)
I agree with butch1326.
You can't move on to other roms until you know the G-Tablet is working right.
I would try to either nvflash or load the regular way CWM and just get CWM working right.
If CWM seems to be working right, then I would re-partition -- but to 2048 and 0 (not what was given above). Then I would do a factory data wipe.
Once that is done, then I would nvflash the bekit image as is described in a bunch of threads. That will get you all the way back to one of the old, stock setups.
If you get that far successfully, the get on wifi and the OTA should update you to
3588.
Once there, you can take a deep breath, do a bunch of studying on what has been working and what has not, and then move ahead.
Rev
P. S. --- Changing too much too fast is poison in the IT world.
butchconner said:
I agree with butch1326.
If CWM seems to be working right, then I would re-partition -- but to 2048 and 0 (not what was given above). Then I would do a factory data wipe.
QUOTE]
I was under the impression that 2048/256 was the default for the Gtab and that 2048/0 was used primarily for TnT Lite builds. Was I mistaken on this? I'd hate to be giving out the wrong suggestions.
Click to expand...
Click to collapse
From what I gather android in general is 2048 0. I believe stock gtab may have come with something else but never saw a reason why.
I'm pretty sure what jasco13 said is right.
I think way back last year when we started it may have been the other -- but ever since I can remember, the standard advice has been 2048 and 0.
Rev
butchconner said:
I'm pretty sure what jasco13 said is right.
I think way back last year when we started it may have been the other -- but ever since I can remember, the standard advice has been 2048 and 0.
Rev
Click to expand...
Click to collapse
Damn....I must be getting old. 2048/0 it is. My apologies.
Ronin916,
No need for an apology. It was what it was and someone improved it and it is what it is.
Enjoy.
Rev
SOLVED
For the replies and more, No.. cwm was wiped out and did not exist any longer so that was not an option.
This took a LOT of doing. I'm talking about over 4 hours of nvflash, replacing parts of nvflash with other parts of cwm .8 and more. I was walked step by step through by a few devs. Because they tell me that mine had "other" issues, it would be specific to my machine alone and probably not help anyone else to post all of it. (However, I did find an IRC for the dev chat and that made all of the difference) Thank you to all of you Roebeet, EJ, Bad, and all the rest!
I was told that you haven't bricked it until you pitch it in the water, so keep your heads up.
Thank you to EVERYONE who replied to me.
You are a great community of helpful gents.
i have the same problem as you! I need help=(
Come on man you gotta close a thread like this out! It leaves everyone else stranded by not doing so. Glad you got this fixed though.
I'm STUCK in the same spot.. are you ablet to post your fix? PLLLLEEEAAASEEE
HELP!! HELP!! Stuck in bootloop for days!!
Hello all,
I have been stuck in boot loop for two days now!! I have nvflashed about 50 times (even used the format utility too in the mix) no luck!! I want to flash back to stock, then update to 3588 and use either Illuminate or Roebeets Honeycomb rom.
If some one has had this problem, can you help with some steps to fix??
Please please help!! I am ready to throw the G-tab out the window!!
THANKS!!
Anthony
Have you tried repartitioning?
Try installing clockworkmod and fixing permissions?
Sent from my Droid using XDA Premium App
I would love to be able to re-partition or install CWM, but I can't get by the boot screen.
Is there another method other than NVflash??
Thanks for responding!!
You need to nvflash...
1) Use bekit's 1105 nvflash image
2) replace part9.img with the recovery.img from clockworkmod install zip
3) type in the command to nvflash but hold down the volume up key on the tablet while you press the return key to start it. Continue holding the volume up while the nvflash starts.
4) When the flash ends you should enter CWM recovery mode. Repartition and wipe everything
5) swap part9.img back into the nvflash image and nvflash one more time.
If you are still looping after that you'll need to force the tablet to load a stock update. It will require a little more tinkering with nvflash. Let me know if you need the additional steps.

[Q] Problems with GB based ROMS

So this time I'm going to be a little preemptive. I ordered a GTab like a week ago, spent the time waiting for it to get here doing a ton of reading so I could go ahead and get it flashed right away. It got here and I immediately ran into problems. I got CWM on there no problem and first flashed [ROM-AOSP]G-Harmony Gingerbread 2.3.3 with Honeycomb elements(UPDATED 4/17) with no problem. Didn't like it so tried to flash the CM7 nightly (which I have running on my evo and hero) and it kept getting stuck on the black screen with that just had "android" written on it really small. Since I hadn't anticipated running into something like that, I did even more reading. Decided to try some more roms and see if I had similar problems. Ran into similar problems with the vegan GB except it would hang on the powered by the "gtabdevs" screen or whatever it said. Vegan 5.1 or whatever the other Vegan one is I could get booted up fine though. So I read some mroe since I really wanted CM7. Discovered that I might need to re-partition, so went into CWM and repatitioned to what everyone was saying was the correct settings. Still a no go and got stuck on android screen. So after even more reading I kept seeing everyone saying NVFlash. So I found it, downloaded everything, read the sticky post on how to do it like 4 times before trying it, then gave it a shot. Put the tab into APX mode (vol- and power) and flashed everything and then when it was done, it was stuck in the APX mode. Very irritating considering I had only had it for about 6 hours. Anyways, sent it back and am getting a new one. It will be here tomorrow morning.
Sooooo, after that long winded explanation of everything, here is my question... How the **** can I get CM7 on my tab without wrecking it again? I did a ton of reading, and nothing I had seen helped at all. Everyone says wipe this and wipe that, or mount these then wipe those, or nvflash then do it and so basically I'm just not sure what to do. I WILL NOT use the nvflsh again and risk getting the APX loop, so any good advice would be most appreciated.
Thanks in advance
I just email walked my sister through installing CM7 on her new gtablet.
Have CM7harmony7.02.zip (or whatever.....7.02 is latest stable release....there is a newer nightly though if you prefer that), the gapps.zip on your computer.
install Clockworkmod recovery on your tablet like you did before.
Boot into CWM and partition sd card, 2048 for first partition and 0 for the second one.
attache via USB to your computer, mount usb option in CWM and copy the ROM.zip and the Gapps.zip to your tablet. Eject tablet from computer (USB eject) and unmount in CWM.
- wipe data/cache (factory reset)
- advanced, - wipe davlik cache
install .zip from sd card
(install the ROM, then choose to install .zip from sd card again and install gapps).
Reboot.
Make sure your tablet is NOT running OS 3991 (very unlikely) or 4349 (possible though unlikely) before doing any of this. (ie...boot tablet out of box and check it's OS version in settings).
Thanks for the walk through. Hopefully it will go smoothly this time around. I'll post back tomorrow after it gets here on if it worked out or not.
If it does have one of those 2 versions on it, I assume I just use the down grader from the thread taking about those 2 versions?
Sent from my PC36100 using XDA App
ix3u said:
Thanks for the walk through. Hopefully it will go smoothly this time around. I'll post back tomorrow after it gets here on if it worked out or not.
If it does have one of those 2 versions on it, I assume I just use the down grader from the thread taking about those 2 versions?
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
Correct, downgrade and then proceed.
Even though I'm 100% sure that at some point of me trying last time that I did in fact do all of those steps, it was a no go.....But this time, I'm sitting here watching the CM7 boot screen
Thanks a ton

Vegan Ginger Edition - Endless Reboot

I had Vegan Ginger Edition running and it was working great. I decided to Factory Reset the tablet. I used Settings|Privacy|Factory Reset.
But it went into endless reboots, I think. What it was doing is that the screen that says Vegan Tab Ginger Edition comes and it does the animation (shocking and flashing), and it does this like 3 times and then the screen goes blank for a second or so and then the animation starts again, and so on, and it keeps on repeating forever and then it would turn off automatically.
I booted into recovery Clockwork Recovery, and tried to do wipe data/factory reset, wipe cache partition, etc, but nothing helped.
I eventually ended up in doing Wipe Dalvik Cache. Now it does not even get to that Vegan Tab animation. It now gets stuck at "Powered by G-TABDEVS" screen.
Any suggestions? Do I need to re-install? If so I guess I will have to copy the zip to SDCARD and then install it, since I can't boot at all. Is there any other option?
Ya, just reflash vegan ginger.
I reflashed it. It now moves on and does not stop at G-TABDEVS screen, but it is exhibiting the same problem. Repeated VEGAN-TAB GingerEdition screens.
What do I do?
I just flashed CyanogenMod, and even that exhibits the same issue. I even went in and did mounts and storage>format system as well as format data. And then flashed it. But still the same.
More bad news. I nvflashed bekit's original image. It now is showing the original big eliptical g-tablet logo as it boots up, but it continues to cycle between the birds and the gtablet logo.
CWM is also gone. When I try to go into recovery all it displays is the big triangle with exclamation sign for a second or so and then restarts the tablet going back into the endless cycle.
I am now totally stuck. Please help.
have you ever repartitioned your device using Clockworkmod Recovery?
I've seen the tablet just bootloop on the bootanimiation if you have never repartitioned. Mine did it and so did a friends of mine. Tablet working great for weeks, installed different ROMs then one day a reboot and it just loops the bootanimation. Repartitioned in CWM (2048/0) and the problem never returned.
Of course you need to get CWM back on. Read the threads on NVFlash and you should be able to just nvflash the clockwork image to the device to boot in to CWM. Repartition and reinstall your ROM.
http://viewsonic-gtablet-for-dummies.webs.com/starthere.htm
tcrews said:
have you ever repartitioned your device using Clockworkmod Recovery?
I've seen the tablet just bootloop on the bootanimiation if you have never repartitioned. Mine did it and so did a friends of mine. Tablet working great for weeks, installed different ROMs then one day a reboot and it just loops the bootanimation. Repartitioned in CWM (2048/0) and the problem never returned.
Of course you need to get CWM back on. Read the threads on NVFlash and you should be able to just nvflash the clockwork image to the device to boot in to CWM. Repartition and reinstall your ROM.
Click to expand...
Click to collapse
Thank you so much. I got out of this mess. I clearly remember repartitioning 2048/0, but looks like Android Factory Reset corrupted it or something.
For the record, this post helped:
http://forum.xda-developers.com/showpost.php?p=10951417&postcount=1
shah123 said:
Thank you so much. I got out of this mess. I clearly remember repartitioning 2048/0, but looks like Android Factory Reset corrupted it or something.
For the record, this post helped:
http://forum.xda-developers.com/showpost.php?p=10951417&postcount=1
Click to expand...
Click to collapse
Hahaaha, and for the record, my start here page code double red takes care of your problem. Not only that, I've also provided nvflash files with cwm pre-installed.
I swear, it's like people don't read the directions properly anymore.
goodintentions said:
Hahaaha, and for the record, my start here page code double red takes care of your problem. Not only that, I've also provided nvflash files with cwm pre-installed.
I swear, it's like people don't read the directions properly anymore.
Click to expand...
Click to collapse
Hey goodintentions, I know you have good intentions , but I have been working with gtablet mods for quite some time now. Usually when you have a bricked gtablet, you are desperately looking for a solution. That's why I hopped from Vegan to Cyanogen to stock etc within an hour or so. And when you have been working on things for some time, you tend to not look at anything that says "start here". Honestly I had never seen your page before, which by the way is pretty good and would have been a life saver if I had known it.
I wonder... what should I name the page as?
I promise you, my instructions work for 99% of the problems people encounter.
goodintentions said:
I promise you, my instructions work for 99% of the problems people encounter.
Click to expand...
Click to collapse
I have no doubt.

[Q] New to posting, not new to the forum

Hi everyone,
I have been frequenting XDA for quite a while. Hugely into android and custom roms and things of the sort, but have never had a real reason to post. I have either been lucky enough to be able to find what I need by searching, or figured it out myself. This time however, I am pretty stumped.
I did a fair amount of research before starting this, and am now seeing that I did not do quite enough. If I am in the wrong place please direct me to a better one.
Here is my issue:
I have an LG g2 that I recently picked up used. Phone has never been rooted or worked on...until now. Decided I would spend my weekend working on it. Successfully rooted, and installed TWRP. Decided to flash a rom, downloaded my rom as I have always done, put it on the sdcard, made a couple of nandroids, and flashed it. Everything seemed ok, booted back up, got the correct boot animation, but it bootlooped. No big deal Im thinking, go back into recovery and wipe a couple times. Still wont boot. Go back in and restore my nandroids, and they wont boot either.
So now I am worried. Try it a coulple more times, and somehow get it to reboot to the setup screen. Wont go past there. Do the trick to avoid it and cant get it to activate. Double check everything, power off, wipe, power back on and now it wont even load to there. I tried sideloading a different rom as well as what seems to be the stock software and nothing. Im lost, I need help. Any advice?
skizzyp said:
Hi everyone,
I have been frequenting XDA for quite a while. Hugely into android and custom roms and things of the sort, but have never had a real reason to post. I have either been lucky enough to be able to find what I need by searching, or figured it out myself. This time however, I am pretty stumped.
I did a fair amount of research before starting this, and am now seeing that I did not do quite enough. If I am in the wrong place please direct me to a better one.
Here is my issue:
I have an LG g2 that I recently picked up used. Phone has never been rooted or worked on...until now. Decided I would spend my weekend working on it. Successfully rooted, and installed TWRP. Decided to flash a rom, downloaded my rom as I have always done, put it on the sdcard, made a couple of nandroids, and flashed it. Everything seemed ok, booted back up, got the correct boot animation, but it bootlooped. No big deal Im thinking, go back into recovery and wipe a couple times. Still wont boot. Go back in and restore my nandroids, and they wont boot either.
So now I am worried. Try it a coulple more times, and somehow get it to reboot to the setup screen. Wont go past there. Do the trick to avoid it and cant get it to activate. Double check everything, power off, wipe, power back on and now it wont even load to there. I tried sideloading a different rom as well as what seems to be the stock software and nothing. Im lost, I need help. Any advice?
Click to expand...
Click to collapse
would really like someone to chime in...running linux.
Bump. Can anyone give me any advice?
skizzyp said:
Bump. Can anyone give me any advice?
Click to expand...
Click to collapse
Sounds like you need to restock and start over. I'd give you links but how to do so varies by which version or carrier the phone is from.

Categories

Resources