Database Info

Reflashing May Not Be Enough....

I'm not expert enough to say this is the answer to a lot of people's problem -- but I'm going to throw it out anyway and hopefully some of the "really expert" people will jump in.
Several times when I have had major problems, I have found that the file structure/files/etc. on my tablet were messed up. Before I could reinstall, I had to re-partition, wipe caches, etc.
I read a lot of posts about people having major lockups or loops and then just trying to reload and reload software assuming that is the only problem -- and not getting good results.
It seems to me that if there is a serious enough malfunction to have to nvflash or do a major recovery -- it would be good to re-partition, wipe caches, etc. in case there is corruption or other structure problems.
What I think we need is for one of the gurus to make us a procedure for "Rebuilding the /sdcard File Structure" (or something like that. Repartition to 2048 and 0 --- and then what else? Which things need to be wiped, formatted, etc.
I'm pretty good a discerning what's wrong -- and I think some of these rebuilds are failing because of this problem.
Right? Wrong? Other ideas? Procedure?
Rev
P. S. -- Enough folks are having these problems right now that this could be an important help for them if I am right......

I PM'd, but the short version for the forum.
I've obviously seen a lot of issues with the TNT Lite 5.0.0, and I've whittled it down to two major problems. First off, not everyone reads instructions. This was fine pre-TNTL 5.0.0 as the instructions really were the same for every version preceding it. But 5.0.0 changed the playing field drastically. Which leads me to the my second point....
I think that some of us have been using mods for so long now that stock was no longer an option without an nvflash. Viewsonic, for example, had a bootloader update in December and I believe a recovery change with 3588. But since a lot of us have been using mods for months, we never got those updates. So, when the time came to revert back to stock, there were problems.
In some ways, TNT Lite 5.0.0 is almost like a tablet cleanup - it's the first update I've had where a stock pre-req was required, and the first one in a very long time where I added a stock bootloader and recovery.

nvflash and tnt 5.0
I tried to go 5.0 after i did nvflash and it instantly did an update ota so when I tried tnt 5.0 it got stuck at the birds for like 15mins, so I nvflashed again.
What am I doing wrong?

Charles77 said:
I tried to go 5.0 after i did nvflash and it instantly did an update ota so when I tried tnt 5.0 it got stuck at the birds for like 15mins, so I nvflashed again.
What am I doing wrong?
Click to expand...
Click to collapse
Not sure -- sounds like you did it correctly. nvflash to 2967, OTA to 3588 and then TNTL 5.00. You didn't install clockworkmod, correct? You need 3588 recovery for this to work.

oops yes I did. ok

Charles77 said:
oops yes I did. ok
Click to expand...
Click to collapse
That would do it. The reason why 3588 recovery is needed is because it updates the bootloader, whereas I believe clockwormod does not.

I'm kinda stuck here, and need some help...
A co-worker has this G-tablet, and gave it to me for the weekend, to load a custom ROM on it so she can watch Hulu and other videos on it.
I did my homework prior to touching ANYTHING, so I made sure it was at 3588 stock, then downloaded the TnT 5 images, along with nvflash and the stock image in case anything went wrong.
Got Tnt 5 up and running, but ran into the issue where it wouldn't sleep (required a reboot to work again). This wouldn't do, so I decided to downgrade to TnT 4.25. The hell started from there...
After flashing TnT 4.20, it got stuck on the birds boot screen. No worries I thought, just run nvflash and everything will be out-of-box new 'n fresh.
I have nvflashed this damned thing about 18 times now, and keep getting the problem where it will flash fine, then reboot fine. But if the unit is powered off or reboots, it gets stuck in APX mode, and won't do anything until it's nvflashed again.
Please help! At this point, I'll be happy just with getting back to status quo ante...
UPDATE: I forgot to mention: I'm accessing this G-tablet from a Win 7 laptop, to which I installed the nVidia USB driver.

darthbubba said:
I'm kinda stuck here, and need some help...
A co-worker has this G-tablet, and gave it to me for the weekend, to load a custom ROM on it so she can watch Hulu and other videos on it.
I did my homework prior to touching ANYTHING, so I made sure it was at 3588 stock, then downloaded the TnT 5 images, along with nvflash and the stock image in case anything went wrong.
Got Tnt 5 up and running, but ran into the issue where it wouldn't sleep (required a reboot to work again). This wouldn't do, so I decided to downgrade to TnT 4.25. The hell started from there...
After flashing TnT 4.20, it got stuck on the birds boot screen. No worries I thought, just run nvflash and everything will be out-of-box new 'n fresh.
I have nvflashed this damned thing about 18 times now, and keep getting the problem where it will flash fine, then reboot fine. But if the unit is powered off or reboots, it gets stuck in APX mode, and won't do anything until it's nvflashed again.
Please help! At this point, I'll be happy just with getting back to status quo ante...
UPDATE: I forgot to mention: I'm accessing this G-tablet from a Win 7 laptop, to which I installed the nVidia USB driver.
Click to expand...
Click to collapse
Hi,
I would hold off doing anything else until someone more knowledgeable posts some help, or maybe get on the irc channel.
There was another user, tcrews, who had what sound like the same problem. I don't know if he's still posting, but he had a thread "need some guidance", and I don't think he ever resolved it.
Sorry if this is not much help.
Jim

Deleted dupe

FIXED IT!
jimcpl said:
Hi,
I would hold off doing anything else until someone more knowledgeable posts some help, or maybe get on the irc channel.
There was another user, tcrews, who had what sound like the same problem. I don't know if he's still posting, but he had a thread "need some guidance", and I don't think he ever resolved it.
Sorry if this is not much help.
Jim
Click to expand...
Click to collapse
I FOUND A FIX!!!!
Link here: http://forum.xda-developers.com/showpost.php?p=12030351&postcount=14
I got my wish, now I'm back to status quo ante...
I sent tcrews a PM with this link, hopefully it'll fix his too...

darthbubba et all,
The files from otreblada that are in this download are the same files roebeet and others have provided -- just packaged together in one set.
To nvflash you have to have:
1. the files for the program nvflash
2. the .img, boot, etc. files
3. the USB driver files.
All of these are referenced and available in several places.
I am glad, however, that this might be a solution for some of you who seem to
have recurring problems.
Rev

[GUIDE] To Asking Questions! (Have a problem? Start Here!)

How to Ask Questions!​
If your messing with your phone, eventually you will have a problem you cant solve on your own. We have all been there, its just part of modding your phone. but if you give some time and a little patience, most of the time its easy to get fixed.
FIRST: SEARCH!!!​​This means try searching a thread if its too long, or searching the entire G2X Section of the forum. (and we can tell if you really searched or if you just say you did to get rid of the people yelling at you) If you see nothing that relates to you, or you have tried all of that, then you can make a post, BUT FIRST...
Stuff to Try Before Posting:​​So... your having a problem with your phone... well there are a few things you can do to help fix most issues:
Go into CWM and clear Cache
try this first, it really does help solve most issues from within a rom
Make a Nandroid Backup and clear data
just do this as a test, make a backup and clear data. check to see if the problem still exists, if it fixes it then its something you installed/did to the rom that caused the problem.
if not then...
Try flashing a new ROM
even if you don't like it, even if you can never go back to gingerbread after ICS just try it to see if it fixes your problem. If it does then you can decide if ICS is worth the issue your having.
Clear App data/Reinstall App
If you having an issue related to a specific app, try going into settings and clearing that app's cache and data. if the issue still exists try uninstalling it then reinstalling it after a reboot.
If none of these things helped you, then its time to make a post.
Things to Include in your post:​​If your having an issue, many of us are willing to help to get it resolved, but first, you need to give us some useful information.
A good checklist to include in your post is the following:
Current Rom
Current kernel
If you have done ANY undervolting or overclocking.
If you had this problem before (either on other ROM's or previously on your current ROM)
If you wiped Cache
If you wiped Data
If you tried installing another ROM
Any other things you already tried (BE SPECIFIC!)
the more you include in the first post the better, too much information is MUCH better than not enough.
If you think the issue is related to a specific ROM, try posting in that ROM's thread in the development section, but please don't spend too much time there. If nobody can find a simple fix, move your discussion to a new thread in the Q and A section, don't clog up the Developer's thread with a single issue.
Once again, the more information you give us the better, and if you don't post the above, someone will most likely ask you those questions, or tell you to do those things first (or they just might ignore the question).
If you see any typos, or think of anything i could add or improve on please let me know.

t mobile lg g2x reeboting issue
Hey guys i recently tried flashing a new kernal to my lg g2x in xda development forum installation procedure went well but at the very end when you have to reebot in recovery it never rebooted back properly just got a blank screen with a notification buttons flashing at buttom of screen....... i just rooted my device so i was still running my stock rom and kernal....... what should i do to get my phone back working please help???

p999dw six digit spc code
Sorry about my weak English
i almost searched entire forum and i only get spc must be 000000. But it's not works. I live in Turkey. At first i can send spc 000000 in QPST but after when i bought the unlock code from ebay, i can't access anymore. Does anyone have an idea?
Thanks

My screen not reading my finger
Im not sure if this is the place i had to ask my question. My cell used to read my finger all the time but now it only does when i turn it on, afther it sleeps n i press the top botten to used it it wont read my finger no more. If i turn it of by taking the battery out and on again it reads my finger until it locks then it dosent. right now i have EB on the phone i cleard cache, system, dalvikcache, format/data. Ive restore basic rom then back to EB but nothing work it only reads my finger till it sleeps then it wont read it no more
PLEASE, WHAT CAN I DO??...

Oskar20022 said:
Im not sure if this is the place i had to ask my question. My cell used to read my finger all the time but now it only does when i turn it on, afther it sleeps n i press the top botten to used it it wont read my finger no more. If i turn it of by taking the battery out and on again it reads my finger until it locks then it dosent. right now i have EB on the phone i cleard cache, system, dalvikcache, format/data. Ive restore basic rom then back to EB but nothing work it only reads my finger till it sleeps then it wont read it no more
PLEASE, WHAT CAN I DO??...
Click to expand...
Click to collapse
I have the same problem and I can't find any way to fix it I am going to post a new thread about the problem.

Hi all...
I was watching, reading and was excited about cm 14.1 for my LG g2 which was running on lollypop.
What a mess I created for myself. Will explain step by step. I I would be thankful if anyone can teach me get out with it and back to LG rom lollypop.
1. I rooted my phone with one click tool.
2. Then I installed Twrp through play store app.
3. Download cm 14.1 for lg g2. The as well as open gaps.
4. Next thing I did rebooted to twrp recovery and clean it after taking back up. But was not able to flash cm 14.1. Also loaded gapps7. 1.
5. After so many trials nothing happened I even updated twrp to 2.8
6. Then I found twrp 3.0 and tried to flash it.
7. Suddenly my phone came to a stage Fastboot.
8. My computer stopped detecting it.
9. Then I re plugged it into the USB of my computer.
10. I found the partitions are there. But no system is there.
11. Even I don't know to sideload it.
12. Lg flash tool is not able to flash it.
I request if someone know the way to flash it with lg roam. I L be thankful.
Can anyone email me steps to do to get out of it.
My email is [email protected]
Thanks
Regards
Harpreet Singh

Hs-india said:
Hi all...
I was watching, reading and was excited about cm 14.1 for my LG g2 which was running on lollypop.
What a mess I created for myself. Will explain step by step. I I would be thankful if anyone can teach me get out with it and back to LG rom lollypop.
1. I rooted my phone with one click tool.
2. Then I installed Twrp through play store app.
3. Download cm 14.1 for lg g2. The as well as open gaps.
4. Next thing I did rebooted to twrp recovery and clean it after taking back up. But was not able to flash cm 14.1. Also loaded gapps7. 1.
5. After so many trials nothing happened I even updated twrp to 2.8
6. Then I found twrp 3.0 and tried to flash it.
7. Suddenly my phone came to a stage Fastboot.
8. My computer stopped detecting it.
9. Then I re plugged it into the USB of my computer.
10. I found the partitions are there. But no system is there.
11. Even I don't know to sideload it.
12. Lg flash tool is not able to flash it.
I request if someone know the way to flash it with lg roam. I L be thankful.
Can anyone email me steps to do to get out of it.
My email is [email protected]
Thanks
Regards
Harpreet Singh
Click to expand...
Click to collapse
This isn't the LG G2 forum.
http://forum.xda-developers.com/lg-g2

[Q] Question concerning Dragonzkiller's Droid x2 CM9 Rom

Alright, so here goes. I've searched the thread for the issue I'm having, but have come up empty handed. I'm not Droid noob, especially not when it comes to flashing roms. But, here are the details I have.
I had been following dragonzkiller's development on his ICS rom. I hadn't really put forth any effort looking lately until yesterday, and saw that he had the wifi and camera fixed, which were really my two biggest issues, so when I saw that, I was excited. I began working on getting it all running. I've had the x2 for about 5 months or so, and usually, the first thing I do, as soon as I get a new phone, is root it. Back in April, I rooted with GingerBreak. Worked good, no issues there. Back in June, apparently I still received the OTA update taking it to 2.3.5-418, which I found out last night had kinda broken my root. So, I went back to find a way to re-root. I did that, with a desktop .exe that went in, and was supposed to flash BSR to my phone also. After I ran that, all my root permissions started asking for options again, so I was relieved. Now, for the issues I'm having.
I downloaded an app in the play store called Online Nandroid Backup. For some reason, and I think this may be a dev issue with the app, it won't run a backup, and tells me that it wasn't able to be granted superuser permissions, even though it is prompting and I'm allowing. Issue number two is this. I've tried 3 different ways to get this working. I used ROM Toolbox Lite, selected the rom I wanted to flash, and wipe data and cache, no delvik. I've selected to run a backup of my current rom. When it boots into recovery, I only have 4 options. Reboot your phone, something about installing the rom from sdcard, wipe data, and wipe cache. I'm not given the backup option on the recovery. Furthermore, when I kinda just decided that since I hadn't had any trouble flashing a rom to any of my other phones I've had, I would just try to flash the rom, it gives me a prompt about 25% through the rom package saying E: signature could not be verified, or something to that extent.
Even though it has said not to use Rom Manager, I did download that and try that, and got pretty much the same outcome of no rom, just a bit different scenario going through. Rom Manager won't reboot into recovery, and when I select to do a backup, it reboots the phone straight up. I also used the manual entrance into recovery, volume up, but it tells me something about starting RSD protocol, and sticks at that forever.
My real questions are this... I've always ever used CWM. All of my previous phones have been supported by Rom Manager nicely, so when it came to downloading and flashing a rom on them, no problems at all. I have never used BSR, to my knowledge, so I'm not sure if the recovery screen I'm seeing is the actual BSR recovery, or if it's some other recovery. If it's not BSR, do I just flash it like I would a rom, then re-run into that? And does the signature issue that I'm running into mean that I have to wait for a signed version of the rom in order to work it? Is there any way to fix this issue, or am I basically SOL right this moment? Any information on how I can fix all of this would be greatly appreciated. Thank you.

[Q] Variety of issues (unlocking bootloader, randomly rebooting phone, etc) [Resolved

Hi! I realise this if my first post I'd like to tread lightly; but I'm about 4 days into solving my issues and I just want to finish it...
I've had my Nexus i9020a (bought from Koodo) since ~May 2012. I upgraded to ICS sometime in the summer and sometime in the last few weeks it has started rebooting. I hadn't been installing new apps, etc. I'm not sure what the cause is. I 'Factory Reset' today in an attempt to resolve the issue, thinking it may be a program gone AWOL; but it has rebooted a few times since. I *just* looked through rebooting FAQ on this site and have edited the first few features listed there. I'm not sure if it has worked yet, but I'll get back to you on that. For the record, the only programs I have installed now are Swiftkey 3, Handcent and Beats (DDR simulator, updated in November).
In the meantime, before I found the solutions here, I decided to take another shot at unlocking the bootloader and try installing... probably CyanogenMod.
Specs: Windows 7 64 bit with Nexus S I9020a (Koodo) running 4.0.4 (4.1.1/2 OTA haven't come through, despite dozens of attempts at clearing the GSF cache, etc)
So I've been using the Nexus S: Full Update Guide found at:
hxxp://wiki.cyanogenmod.org/wiki/Nexus_S:_Full_Update_Guide
(It won't let me post the link)
I've followed the guide for installing the Android SDK, gone to CMD and typed 'adb devices' and had it show up. Theoretically, the SDK should be running fine.
Next, I turned on the USB debug mode. Then I booted up the bootloader, plugged the NS into the PC... and despite not having issue when the it's turned on (driver installed properly) windows says drivers have not been found for the device. Thus, when I type fastboot devices, it comes up with nothing.
I've been, and will continue perusing forums for this, but so far I haven't seen anyone with this specific problem.
Edit: I have also gone to the directory with fastboot/adb and used cmd to reboot into the bootloader, only to have windows 'ding ding ding' an unrecognised device.
2nd Edit.
I've gotten a stage further! I'll keep the thread open because I may come across something and it's nice to write my issues down. Seems my head can wrap around the problem a bit better. Anyway, I installed PDAnet and BAM, it works. Onto getting CWM installed! Thanks for the, uh, help!
3rd Edit.
CyanogenMod 10.0 stable is booting for the first time!! It's taking a while... but I appear to be on the home stretch! Also, my phone didn't reboot for a few hours before I installed CM. So if I don't end up somehow bricking it... and I mean, this first boot is taking a heck of a long time... The animation sets me at least a bit at ease... maybe 4.0.4 will work out...
Edit 4
I forgot to clear the app and cache data before flashing the ROM to the phone and thus the issue... after a VERY tension filled moment of pulling the battery during first boot... I rebooted, cleared said data and reflashed the ROM. After a boot, I realised I forgot the GAPPS zip and fixed that. Now I'm running CM10 Stable!! I'm stoked that after months of putting it off cuz last time I did it I didn't get anywhere after many days, but now it's done!! Thanks again for such an awesome site!

Thanks for sharing your experience instead of just saying "Mods please delete this i solved my own problem" :good:

[Q] HELP - Nexus 7 & Beats

okay, where to start.
I've a Nexus 7, and im running P.A 2.54, with twrp.
i got an article from one of my news apps about getting better volume for my nex 7 BeatsLouder, followed the link and downloaded, didn't do any information gathering and consequently i believe i've flashed the beatslouder for android 4.2 it was BeatsLouder v3b8 i believe.
Either way now, my tablet just hangs at the P.A splash screen/boot logo.
needless to say, with my lack of forward planning into researching what i was flashing i didnt make a back up either..
Are there any solutions that don't even a fresh wipe?
edit: so i had a back up in twrp, when i had the forethought to do a backup prior to installing something unknown, however i'm not certain if the back up is of data or system files or both, anyway to find out? the restoring of the back up seemed to happen almost instantaneously, making me think it didnt work?
oh, also i made a backup of everything (in its current broken state) in the hopes i might be able to recover my data?
would love some responses, anything to get the ball rolling

Try dirty flash your ROM then gapps in recovery again. No wipe needed.