Ok first, I did a lot of research into the topic and spent more than a few months in thinking it over and seeing if I wanted to attempt this. In a day long research fest, I finally decided to just try rooting and installing my daily-driver Nexus 7 2013 Wi-Fi with CyanogenMod. I chose a method that wasn't too daunting, using the Nexus Root Tools to push the CM rom and finally into working... I used RootJunkie on YouTube, "How to Flash a rom with the Nexus Root Tool Kit plus make a Backup with one click" as a refrence, watchign and rewatching the video and all he referenced over and over.
I loaded the zips into the "Flash Zips" section (It loaded the GApps zip in first and then the CM image). It seemed to install without a hitch except the GApps weren't there. Figuring that it installed the GApps first and then wiped them, I redid the flash with the CM first and the GApps second. Now I'm stuck in the Cyanogenmod loading screen. Problem is, since it's hit the point where it installed everything and hasn't let me into the device, I haven't been able to enable USB debugging. Now the computer isn't able to recognize the device at all and I cannot push just the CM image to fix it nor can I restore factory since the computer doesn't recognize it.
I've attempted to boot into recovery mode, which just results in the android laying on its back with a red ! in a triangle over it. I'm sorry if this makes no sense but I'm slightly panicked because I can't afford to have this thing professionally fixed nor replace it at the moment and I use this tablet daily. Is there something I'm missing? I'm going to lay down for now and try to calm myself, letting the thing sit at the loading screen, hoping that it'll let me in after a while. What options do I have, I'm sorry if this is the wrong place, the wrong crowd... I've just browsed quietly and used XDA as my source for information for everything from rootig my first device to this and it seems I've overstepped my abilities in this.
Problem solved
I stepped away from my computer and tablet for an hour or two to calm down from a panic I was in and found that it let me into the bootloader finally where I flashed the stock image and then restarted the process.
I discovered my problem in trying to use the 'stock' level of GApps from opengapps when the Cyanogenmod wiki pointed directly for the 'nano' version. Sorting out a silly wizard crash later and my tablet is happy, healthy and working much better than the stock at the moment aside some setup I need to do.
Thread closed as OP solved his issue
Related
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
First thing...greetings! Yes, I am a n00b (loved the video, though) and have searched for quite a while to hopefully resolve the issue I am currently burdened with. A thousand pardons if there is already another thread like mine, but I just couldn't find anyone with the same issues I am having.
First off, I started with rooting my phone. No problems.
Got my hands on ClockworkMod's ROM Manager. Downloaded Cyanogenmod 9 to my PC, and any other necessary programs to get this flashing underway. Opened up ROM Manager and proceeded to boot in recovery. This is where I think the problem originated. I wiped all that I needed (or so I think). It's entirely possible that I may have missed something. Not sure. After wiping it clean, I then went on to install the zip of cyanogenmod. All went well. Then the reboot. It starts up and gets to the loading screen with the really cool animation. 5 minutes. 10 minutes. It's constantly loading. I head on to google and search some possible culprits and solutions. There were suggestions to go back into recovery mode, but the thing is, when I try to get to that menu, it doesn't seem to pop up and goes right back to attempting to boot.
So, all things said...is there any possible solution? Any help would be greatly appreciated. And again, if there were any threads with my specific issue, many many apologies!
Thanks again!
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:
tl;dr - TWRP touch screen won't work after installing custom ROM, much hassle to unbrick, looking for a "bumped" (still not actually sure what that term means) or otherwise modified version of TWRP that won't go haywire when installing a custom ROM.
tl;dr 2 - Also interested in the LATEST "stock-based" ROM recommendations anyone may have... G3 backports or whatever. She needs her Camera to work well but older 4.4.x and 5.0.x OS is missing a lot of new functionality and compatibility with new apps.
I'll just start out by saying that I've figured out just about every way to brick and subsequently un-brick this device that is feasibly possible, and am considering starting a thread specific to those various methods... but that's not what this is for.
This is an issue I've encountered a few times now, definitely on my girlfriend's T-Mobile LG G2 D801 with Lollipop (30B and now again on D801 30C), and iirc, also on KitKat.
I'll explain what I can remember, most of this has been done in the middle of the night after many frustrating hours of attempting various methods... I have to say, this phone has been much more difficult to mod compared to my previous experiences with Samsung and Nexus devices.
I had gotten this device all the way through to CM12 or 13 a year or so ago but recent issues made us decide to attempt to revert back to a Stock-based ROM.
Steps:
1. Root (ioroot / Autorec, can't remember which or for what reason, I have multiple versions of each)
2. Install TWRP Custom Recovery (most recently and successfully using a modified version of the "30B Freedom Tool", although I haven't tried that on 30C - yet.
3. Transfer custom ROM & Kernel to SDCard.
4. Boot into TWRP and install custom ROM & Kernel - most recently GoogleEdition 1.5 and then DorimanX 12.0 Kernel
5. Clear Cache / DALVIK Cache.
6. Reboot device. This is where the trouble begins...
Results: Won't boot into OS at all, instead I end up at the text-based "fastboot" screen, which after multiple tries I can eventually get back into TWRP or into Download Mode.
Once in TWRP after installing custom ROM, the bottom ~1" of the screen won't respond and all other touches aren't accurate... playing with it, I can usually eventually get into some of the TWRP screens, but for most purposes it's about useless.
I managed to restore a backup of the original 30B system image via command line over MTP using ADP TWRP commands, but that bricked the phone in an entirely separate manner where I couldn't access Recovery anymore and the system wouldn't boot at all... I ended up using the LG Update tool to get it up to 30C, and was surprised to find that it still had the restored backup data (apps, pictures, settings, etc), and the phone is now working again, albeit back to stock recovery.
Now, as I mentioned, this isn't the first time I've run into this "phantom touch" issue in TWRP on this device, although the circumstances seem to be a little backwards this time vs when I was taking the device over to CM12/13. I think I remember something about a "bumped" or otherwise modified version of TWRP being out there, but I can't find it now or put my finger on what the changes were.
Has anyone else run into this? I am hoping I've just overlooked something, but days of digging through threads hasn't turned up much.
/edit/ To give you an idea, attached is the folder I've got files stored in... with tons more in Archive and Stock-Based... I've used them ALL at some point. I'd like to get enough info in here to write a Step by Step guide for new owners who are picking these devices up on the cheap, and would appreciate if anyone wants to help out with this!
Hi all, I do not understand your magic and really hope I don't have to learn too much of it. I have never rooted a device, so please bear with me. I just purchased a used Galaxy Note Pro 12.2 off eBay. I did my research and planned to just follow instructions to root it and upgrade to Android 10. However, I had a few issues and when I tried to boot to recovery mode, I get an android on its side with a red triangle. In the upper left hand corner, it says
Android System Recovery <3e>
KOT49H.P())XXUANB2
Volume up/down to move highlight
power button to select
reboot system now
apply update from ADB
apply update from external storage
wipe data/factory reset
wipe cache partition
apply update from cache
Power-Volume down takes me to a screen that says
WARNING!
A custom OS can cause critical problems in phone and installed applications
If you want to download a custom OS press the volume up key
Otherwise, press the volume down key to cancel
When I press Volume up, I get a screen with the green android and the message
Downloading...
Do not turn off target
In the upper left hand corner it says
ODIN MODE
PRODUCT NAME: SM-P900
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Official
KNOW WARRANTY VOID: 1
AP SWREV A1
It then is stuck there. It seems like I cannot turn it off for a while like it is timing out.
It has Android 4.2.2. When I go the update in settings, it downloads a file but will not install it.
So I did some more research, and I believe that the device is already rooted with Odin (not quite sure what that is). If my hunch is correct, a lot of the work has already been done. The device was restored to version 4.2.2. By the way, an upgrade in settings downloads a new version, but it will not install.
If anyone could walk me through the process from where I am to install Android 10, I would be ever so grateful. I need a stable version, so if Android 10 is not finished, whatever version makes sense. Right now, it will not install things like Hulu or Outlook.
Although I do not know much about Android, I can follow instructions. And I know very well that I proceed at my own risk.
Thanks!
Bubble-burst here...
First and foremost... you can't get Android 10 on the SMP-900. This is an older device and is no longer supported/updated by Samsung, so the binary blobs that connect the hardware to the operating system are stuck at Android 5.0.2 (I think - the numbers AFTER the decimal may be off by a few, but point is that Samsung's last supported update was for Android 5.xxx). There are some later ROMs (what you're trying to load) that were made by some great developers that shimmed those binary blobs into a newer version of Android (AOSP) or LineageOS that makes the tablet quite usable and enjoyable.
I personally am running LineageOS and OpenGapps (the OpenGapps project is an open source version of Google's proprietary framework that makes things like Gmail, Calendar, Play Store, etc, work) and it works great. That at least gets you a more up-to-date tablet that runs better than Samsung's last update.
It sounds like you got a corrupted op/sys or bootloader and a corrupted (or missing) recovery image. The reference to Odin is the mode it is currently sitting in - Odin is the software that Samsung uses to load the images onto the device. You are basically holding a 'raw' SMP-900.
You are going to need to:
1) Download a copy of Odin for whatever operating system you use, i.e., Windows/Mac/Linux
2) Download a copy of an official Samsung Android 5.xx ROM (to get the new bootloader you'll need to upgrade to LineageOS later - trust me, you want this!)
3) Use Odin to load the official Samsung ROM on the device
4) Once you have the device booting up on the official Samsung ROM, you're back in business
5) Download TWRP recovery for this device (v1awifi) and use Odin to install it
6) Root the tablet
7) Install LineageOS
8) Install OpenGapps
9) Install the LineageOS root app (or install Magisk... your choice)
10) finish up the installation with whatever software you want to install from Play Store
Since most, if not all, of this is well documented in various places on this site... the search box can be your best friend. Most everyone here will offer help if you run into trouble, but please search this site first - there are some really, really good instructions and videos of just about everything you will need to do to get the SMP-900 to an nice, usable tablet. Oh, and remember that this is a 32-bit device, so when you go to OpenGapps, make sure you select the 32 bit version.
Good Luck, and remember to read/watch stuff twice, THEN do it.
Thank you so much, friend. This is exactly what I was looking for. I am quite capable of searching and I have been a lifelong of measure twice, cut once.
I have downloaded Odin for Windows, and it recognizes the SMP-900, so that is something. I really appreciate the heads up about Android 10. I wondered about it. Double thanks for the 32 bit warning. I downloaded the 64 bit.
You have given me a clear road map, and I no longer feel lost. I completely understand about searching before asking questions and will try to make any questions I ask focused. People here have been very generous with their time in the past, and as you said there is a lot of wisdom for the asking here.
I think I will track my progress and perhaps put up a post detailing my experience for comic relief if nothing else.
Your reference to Lineage is new to me, but if I understand you, it will serve my purposes.
I will upgrade the SMP-900 to the latest Samsung ROM as you indicated. That makes sense, and I tried earlier, but it would not install.
Again, I cannot thank you enough.
You da bomb!
Thanks again for your help. I am not at Android 5.0.2 and ready to move on with TWRP, boot and lineage. You have made a terrifying process understandable.
Mission Accomplished I think
I followed your instructions carefully and had to do some research along the way. I did not find an official lineageos file for the P900, but did find files here for 14.1 and 17.1. I ended up installing TWRP from Google Play, and once I figured out how to start it, things seemed to go well. Took a while for me to understand not to unzip the zip file. I downloaded
lineage-17.1-20200412-UNOFFICIAL-viennalte
lineage-14.1-20200523-UNOFFICIAL-v1awifi
open_gapps-arm-10.0-stock-20200523
open_gapps-arm-7.1-pico-20200523
to my SD Card. Then, in TWRP, I wiped everything and tried to install lineage-17.1-20200412-UNOFFICIAL-viennalte and open_gapps-arm-10.0-stock-20200523. That did not work. I got some kinds of error or reset message. I wondered if 17.1 was pushing things, so I tried again with lineage-14.1-20200523-UNOFFICIAL-v1awifi and open_gapps-arm-7.1-pico-20200523. That time, it went very smoothly. The device now boots up with LineageOS. It seems to have Android 7.1.2.
My purpose for the table was to watch Hulu, Netflix, Amazon Prime video and Youtube basically. Maybe play games if I ever have the desire. Nothing would loan on 4.4.2. This time, I was able to install everything from Google Play except for Netflix. I kept getting a message that my device was not compatible, but a little searching took me to a Netflix page with a direct download, and now everything seems to working great.
I cannot think of any Android advances after 7.1.2 that I really want or need. It seems to suit my purposes as is, so unless I discover a reason to throw caution to the wind, I think I will leave it as-is.
You took a task that seemed impossible and gave me the guidance I needed to figure it out. I am sure that you saved me at least 20 hours of searching that may not even have been successful. It is so wonderful to encounter people like you who will take a few minutes to help people you don't know. I will always be grateful, and I will think of you every time I start the device. Thank you.