I broke my CM13 installation, anyone care to assist? - ONE Q&A, Help & Troubleshooting

Hello!
Last week, I flashed CM13 nightlies from cyanogenmod.org onto my OPO, set everything up and everything was working just beautifully. Today, I was looking for a way to add the 12s camera app to my phone and came across a tutorial which told me to download an APK and replace /system/lib with a folder they provided. Immediately after replacing the lib, my screen went black. I waited for a couple of minutes and then decided to force reboot. From there it just went into a bootloop.
Now I'm agonizing of going through all of the flashing and setting up the phone all over again (several hours of work) and I was thinking if it would be possible to access the internal memory of the phone on my computer and then replace the lib file with the original? Provided someone could point me to the direction where I could acquire it I'm pretty noob at this stuff so go easy on me :silly:
EDIT: And to clarify I am able to access TWRP so the phone is not bricked
EDIT2: Even though the phone is now off, I can access the internal storage of the phone from my computer, however I can't access system folders, only /sdcard

Nevermind, got impatient and flashed again

Related

Multiple Problems

Hi,
I got a GTablet for Christmas today and I seem to have had some bad luck with it...
When I first got the tablet, it wouldn't keep any of my settings (not the wifi connection, not the development settings, nothing).
I thought I could get around this by flashing a different image (I am a novice user, though I do have a very modded N1 -- except it's still stock, sort of).
So... I did not have a MicroSD card at all (it's Christmas, all the places are closed until Monday, and I did not anticipate any problems). Still, I was able to flash the image of TNT Lite...Sort of. I had no problems upon booting, with the familiar N1 X boot animation.
I could add things to the stock Android launcher included with TNT Lite, but not remove them (as soon as I sled the icon I wanted to remove over to the 'trashcan', it force-closed the launcher, but my icon was removed nonetheless).
I did have a slightly working Market (I had the half-star issue). I did not have Titanium Backup installed, so I attempted to restore a working Market by force-closing and clearing the data of the 'Google Services Framework' and 'Market' services... Didn't work, like I thought, so I then tried to sideload Titanium Backup.
There is where my big, big problem came up. As soon as I tried to load TB onto my GTablet, I had tons of Force-Closes (and the tablet sort-of half rebooted). So, I got them to go away and tried again. Same thing.
So, I gave up and vowed to try again tomorrow. Except, I might not be able to tomorrow... As soon as I turned the tablet off, all was A-Okay for the most part... Later, I thought I'd try a little earlier than tomorrow, so when I turned it on.... I didn't get any farther than the GTablet logo before I realized I was in an infinite boot loop.
Now, I'm stuck with a boot-looping GTablet and a not working Christmas present! Help, please.
EDIT @ 3:44AM (Dec 29, 2010)- [FIXED]
FIXED!
When you get an sdcard you can do a fresh install from the external sdcard.
Yeah, I know that.
I don't know if I'll be able to rescue it or not (like I said, I'm new to this, and I was under the impression that [Power]+[Volume-UP] meant 'load recovery mode' which would look like the one I use on my Nexus One).
Do you think I should try (if I can get out of the infini-boot) flashing to TNT Lite (the latest, I think 3.1.0.1 or something similar)?
I'm wary of flashing to that one again, since it seems to have some serious problems with my particular tablet (I searched and there were no similar problems to mine that I could find).
I don't know if I'll be able to sideload Titanium Backup, are there any alternatives to that in getting a working Market (I tried anything else I could think of, but nothing was ever able to sideload onto my Tablet, ever)?
Have you installed Clockworkmod recovery?
Read the main threads (tnt lite, vegan, installing gapps) and I believe you will find someone has had the same problems you have
Hi there! I got the MicroSD card today.
So, I was looking through the guide I had previously used (http://forum.xda-developers.com/showthread.php?t=842004) and now I'm going to try to install ClockWork Mod recovery .8 (the one they said works best here).
I will update this (or maybe make a new message if you don't mind, if I can't edit my posts) if I can successfully get it working.
EDIT @ 12:47AM (Dec 29, 2010)- [Downloading the recovery mod file]
I downloaded the 'gtab-cwm-v08.zip' file to my MicroSD card, and extracted the 'update.zip' and 'recovery' folders inside (I imagine that is correct).
Then, took it out of the computer and loaded it onto my GTablet. I turned it on and did the recovery combination with [Power]/[Volume-UP].
It gave the screen that said it was loading the image and then another screen (black with 'ANDROID' and some other text on the screen).
For just a second, an error-type screen flashed on the screen (big warning icon, not sure how to describe it, but there was no text nor a loading bar).
Then, it rebooted (and then again and again, so it's not fixed yet).
Not sure what I did wrong... <
EDIT @ 1:43AM (Same Day)- [Installing recovery/Fixing boot loop]
Successfully installed Clockwork Mod Recovery .8 after downloading a 'command' file from my ROM's .rar (I modified the file so that it'll say <load-info>sdcard2<load-info> instead of <load-info>sdcard<load-info>).
Repartitioned to 2048 and 0 for the memory settings.
EDIT @ 1:55AM (Same Day) [Boot loop fixed, now just trying to figure out what to do next]
Repartitioning to 2048 and 0 in the memory fixed the boot loop. Yes!
Now, I don't know exactly what to do next... This one is still in progress right now.
Sounds like you did it right. Where you got the Clockwork file may make a difference though. There are 2 of them out there. One is from a thread that has it setup to load from an external sdcard. The other from the internal. Quick way to see what you have is to open the command file inside the recovery folder and see if it says sdcard, or sdcard2. You want it to point at whatever method you are using to load it. Sdcard for internal, sdcard2 for an external card.
If you haven't tried it already, look at this.
After that just load the rom you want.
Beware though, you may have a strange model that won't work with that, some have been floating around..... Read the full thread too
This may also be useful to you: http://forum.xda-developers.com/showthread.php?t=842000
Now, I see why it did not work... Mine had no 'command' file AT ALL (in the 'recovery' folder)!
So, how can I make one?
By the way... To address your initial issue of being in a boot loop. Get clockwork installed. Once installed go to advanced, partition sdcard. Use 2048, and 0 for the swap. That will get rid of the boot loop.
XANAVirus said:
Now, I see why it did not work... Mine had no 'command' file AT ALL (in the 'recovery' folder)!
So, how can I make one?
Click to expand...
Click to collapse
You can find one in most any of the roms. The earlier TnT roms had them, others too...
They are all the same except for the sdcard, or sdcard2 thing I talked about so don't worry about finding a specific one.
So, when I install Clockwork, do I need to leave that MicroSD in there to run it everytime (not sure where it puts the files/etc)?
XANAVirus said:
So, when I install Clockwork, do I need to leave that MicroSD in there to run it everytime (not sure where it puts the files/etc)?
Click to expand...
Click to collapse
Nope. Once it is installed you don't need the sdcard anymore. Be sure to read my post a couple above this about fixing your boot loop.
Okay, as you wrote in the first page to reformat to 2048 and 0 (in that order), I just did that (as wrote in my edit )
What should I do next?
XANAVirus said:
Okay, as you wrote in the first page to reformat to 2048 and 0 (in that order), I just did that (as wrote in my edit )
What should I do next?
Click to expand...
Click to collapse
Reboot and see where you are... It should go back to where you were before you got the boot loop. The stuff on your internal sdcard will be gone though. So I hope there wasn't anything important there.
BTW, you can hit the back button on the side of your screen to go backwards in the clockwork menus.
Nothing important. I haven't even installed anything new or changed any new settings on my current ROM (that TNT-Lite).
I'm rebooting it right now as I type this.
EDIT @ 1:58AM (Same Day)-
Your steps fixed my boot looping problem. Thanks!
Now, I don't know what next to do. I don't have Titanium Backup installed (couldn't sideload it, I kept having problems).
I don't know if the Market is fixed yet.
Did it boot?
Sent from my VEGAn-TAB-v1.0.0b4 using Tapatalk
Yes, thanks!
Awesome! Now I would boot back into clockwork and make a backup. You can rename them from a file manager too so they make sense..
Sent from my VEGAn-TAB-v1.0.0b4 using Tapatalk
I don't ever use titanium to do the market fix. I just use it to backup apps.
Sent from my VEGAn-TAB-v1.0.0b4 using Tapatalk
Okay, I made the backup like you asked. So, now should I try to fix the Market?
Is there anything else that needs tweaking?

[Q] All the sudden stuck at the ASUS animated boot screen

I'm not sure if this is in the wrong thread since my TF is rooted but I'm afraid to ask a question anywhere else at risk of being banned. I saw a few other posts about this but it wasn't clear if their circumstances matched mine so I figured I would create a new post about this.
Basically I decided to reboot last night to clean out any programs I had running and when I powered it back on I got back the first screen but when I got to the animated ASUS screen it just hangs. I see a little white circle animation at the bottom that appears and disappears randomly and it looks like the animation is restarting but it could just be how it normally looks. I let it sit all night and in the morning it was still in the same spot.
A few days ago I used the "One click" root method (Linux LiveCD with NVFlash scripted to root). Everything went fine and my TF was working great. Over the past few days I have loaded up all the apps I use and rebooted a few separate times. I have made a Titanium backup but I believe it backs it up to the internal memory so I believe the backup will be useless if I have to wipe.
The hacks I have done are below but I believe I have rebooted after all of them. I don't have clockwork installed so I installed the hacks manually using root explorer. All of the hacks have had the desired results so I believe they were done correctly.
Netflix Patch
Original Xoom menu icons
GPS calibration fix for Google Maps
I have ADB setup on a machine and I'm hoping someone can tell me how to get this working using ADB commands.
Please help.
Updated:
I was able to use ADB to restore the /system/framework/services.jar and services.odex from the backups I created. These files were replaced by me during the installation of the GPS Calibration fix that can be found here http://forum.xda-developers.com/showthread.php?t=1192617&page=4 and here http://tabletroms.com/forums/showthread.php?1731-ASUS-STOCK-3.2-and-PRIME-beta-1.7-patch-(calibration-window-fix)
The update seemed to fixed the calibration bug and i'm pretty sure I have restarted since the installation of the fix but setting the files back to stock resolved my boot loop. Anyone have any commends, observations or explanations about this?

[Q] two storage locations maybe?

I don't even have any idea how to search for this or even ask about it. I'll try!
Okay, so after having trouble with 4.2.2, I decided to flash an older rom. I had some problems with wifi logo turning white and not being able to connect to Google, so I searched for a new gapps to flash. I was having computer trouble, so I downloaded it onto my phone, it saved to the downloads folder. I also had noticed none of my other files were in there, which kinda freaked me out, but the same amount of space was being used on my internal memory (I don't have a SD card). Anyway, I went to go flash it with twrp and went to downloads and saw all my OLD files, which didn't include the new gapps download. So, I went to root explorer after rebooting and moved the gapps to my root folder, then restarted to recovery and it's not there. The only thing I can think of is when I'm in recovery, it just says sdcard, when I'm in the system, it says sdcard0.
Does anyone know what's going on and maybe something I can search for? This is weird. My files are clearly there and I just can't access them... even with full root access!
Sorry if this didn't make a lot of sense, I have no idea what's going on at all and I'm also kinda tired. Hope you can help!
------ I found the answer here: androidforums .... /verizon-galaxy-nexus-all-things-root/649940-4-2-sdcard-sdcard-0-observation.html
My tired brain finally kicked in and I searched sdcard0 and figured it out. Now, I guess I have to move stuff so I can use the old os. I'm only not deleting the post because it might helps someone. And I'm sure modifying links isn't allowed but I can't link with less than 10 posts and I wanna make sure people get the answer, so... yeah... Add com in the middle.

Hannspree 133 Titan 13.3" tablet (RK3188) Troubleshoot help and tweak help.

Ok maybe my original post was too long and wasn't read. So I started this thread in hopes I could get some help. My tablet should have 16GB storage but its only showing just over 3GB. The nand storage area on the tablet will not mount for me but is shown in the settings / storage area. when I click mount it tries to mount but less than a second later it fails to mount.
Also I was hoping either I could get help with creating a custom lolipop rom for the tablet. I will provide any of the files from the tablet needed that I can.
I've put the original post in the second post.
I got this tablet five days ago. All was going good until I used Kingoroot to root the tablet. After rooting I quickly realised that with Kingoroot installed and applied I was still not getting full root access with a few apps so I decided to try and get full root access by editing the build.prop. After editing a few settings and reboot after tweaking a setting I still wasn't getting full root access. Then I edited a wrong setting and the tablet got stuck in a boot loop.
I spent ten hours trying all kinds of tricks to push the fixed build.prop back to the tablet with no access so I asked on different forums (Including XDA) for help. Thanks to Oma over at ArcTablet (He is a member of XDA too) who helped me get CWM onto the tablet and the fixed build.prob on to the tablet I finally got the tablet to boot into the OS again. Here's a link to the forum thread where he helped me
http://www.arctablet.com/blog/forum/...-soft-bricked/
So now I have CWM on the tablet and after a few more tweaks I finally got full root access. That was all good until lastnight when I was watching a youtube video and the tablet rebooted all of a sudden for no reason. The tablet refused to boot into the OS again. So I tried applying a CWM backup I had taken earlier but it stops at SDCard/Android Secure which it says does not exist.
I finally got the tablet to boot into android OS again but some apps refuse to install and some apps close straight away. Also the Nand partition will no longer mount. It shows that it exists in the settings but when I press mount it tries to mount but fails to mount less than a second later.
So to get to why I started this thread is to see if any of you guys would be kind enough to offer help here. Also maybe we could work together and get a custom rom working on the tablet. I can't find anything for this tablet online so this is a start.
If you guys need me to supply any more details then let me know. I don't know where the best place is to upload files either.
Did you managed to fix it? I know it's been a long long time but could you detail what you've done to install cwm and root?
Hope you can help me I was thinking on using this tablet as a wall panel.

Uninstalling DictDiotek.apk stops phone booting entirely???

I just got a s5 prime from eBay and was in the process of debloating via tibackup but kept getting stuck at boot screen showing warranty kernel bit. Required a restore of system and data each time to get it going again. Through arduous process of elimination I was able to narrow the culprit down to the aforementioned seemingly innocuous apk. When it's removed the phone dies.
What's even stranger is that this page seems to indicate that it's fine to remove:
http://forum.xda-developers.com/gala...oater-t3319854
I'm just curious as to why!
Sorry for digging but people need to know! I wish I saw this post earlier. I spent whole night trying to see what causing my phone to endless boot.
After few hours I see that If you remove DictDiotek it won't boot anymore. And I thought that this is uselles dictionary and everywhere people write that it's safe to remove.
GALAXY S9+ OREO
KamilKiri said:
Sorry for digging but people need to know! I wish I saw this post earlier. I spent whole night trying to see what causing my phone to endless boot.
After few hours I see that If you remove DictDiotek it won't boot anymore. And I thought that this is uselles dictionary and everywhere people write that it's safe to remove.
GALAXY S9+ OREO
Click to expand...
Click to collapse
I remove it from all my ROM builds with NO PROBLEM...
@AFFAFXP - I believe you because I've always removed it from my S7 and It worked fine. But on S9+ it's causing endless boot for me. I think that it's ROM related or something (or maybe language related)
KamilKiri said:
@AFFAFXP - I believe you because I've always removed it from my S7 and It worked fine. But on S9+ it's causing endless boot for me. I think that it's ROM related or something (or maybe language related)
Click to expand...
Click to collapse
endless boot is from some files in the /lib I believe if you look for these from a rom that worked and replace them in the rom your installing this would work in this case as well...
This link originated here >>>> https://www.tech1xpert.com/guide-to-port-roms-android/
Fixing a Bootloop
Your Port should take less than 5-8 minutes to boot. When the screen dims during boot logo, your Rom has successfully boot.But If your waiting for like 15 minutes, and boot logo is still going, YOU HAVE A BOOTLOOP. Luckily, the fix is easy!
STEP1:
Navigate to “PORT” folder. A ROM THAT BOOTS AND WORKS for you device
STEP2:
Go to lib folder inside System folder of Base Rom.= ROM That you want to install
STEP3:
Inside lib folder of PORT search for these libs:
libandroid_runtime.so
libandroid_servers.so
libmedia_jni.so
Once you find each, copy them to the lib folder of Base Rom.= The ROM you want to install -- Right-click lib folder of Base Rom, select paste, and click the box in the lower left corner. Now “Click Move and Replace”
STEP4:
All done! Now add to a zip and flash!
This HAS WORKED in my attempts on PORTS that BOOTLOOP KUDOS
The same problem happened on my device. I took it to the mechanic before I tried to get into the recovery screen. We thought there was a power problem. The mechanic probably damaged my robust device because they didn't open it properly and handed it back to me in a broken state.
By taking a second N910C device and risking it, I repeated the same process step by step and found that the problem was caused by uninstalling the program "DictDiotek.apk". I restored my backup with Recovery. And my device turned on normally. DictDiotek is not a problem if frozen. Only uninstalling the phone does not turn on.
My phone is N910C. Custom ROM 6.0.1: Ditto ROM DN6

Categories

Resources