So i am here with a new idea. A rescue.zip which can be used to rescue any android device which have a recovery like the famous cwm.
So here is it..
Some times we people screw up our android os like hell, and to reboot the device we usualy do a recovery flash of a new os, flash back our nandroid backup ( both on worst conditions) or even do permission fix, clean cache or dalvic cache( those in 'not that worse' conditions) . So thats are all the options we got. Rit?
Although flashing recovery backups, new roms can fix all, it will also eatup our apps, current setups, contacts, msgs, etc( in case we dont have backups) and will probably screw us. All we can do is say " WTF..WTF..WTF.."
SO here is my idea,
Find out the causes of what causes a reboot, non-boot, hang,fc etc.
And keep a zip that can be flashed through recovery, that has a solution for our problem. They may be including..
1) fix permission of system, data, and user data.
2) zipalign the apps
3) fix the default clock speed of processor
4) defragment memory
5) flash a new copy of su and busy box
6)wipe data or system or ext or cache or dalvic cache
7) flash a new copy of framework.res, system-ui.apk, settings.apk with default permissions( those files are kept in separate "custom" folder on the zip, so that end user can put their own files to that "custom" folder for flashing., the reason behind it is known to all, yap. Not all devices have them in common, every device have its own files)
These are all i got for now, pls post ur ideas and knowledge for any possible cure about any problem u faced/ cured. So that we can make it an ultimate rescue.zip that have a cure for 99% problems android os have. The rest 1% will go with a clean flash.( well we cant avoid that if we did something that bad).
So my plan is to use aroma installer( now on hard learning to find how it works). Throw in some scripts, files etc. Into the zip.
And since its not a device specific .zip file, i want to know how and why any problems are caused in any device( there are many common problems, but that is not what i ask for. I ask for device/os specific problems, and not for a problem that we can cure after booting, but for a problem that can make the device un-bootable) . So u people may help me to find those problems and cures for it. For my knowledge i have experience with wildfire and hd2.
Well i will keep this thread for a week or two, so that u can post ur knowledge, and info. after that i will release the file for u.
To the admin. Of the forum, pls keep this thread as announcement so that all can take a look.
HYPERDROID EXTREEM EDITION-THE NEW BENCHMARK ROM FOR HD2.
People could do it theirselves, but some are even stupid enough to not be able.
So it would be a good solution.
Good that you can use Aroma, but I don't think most users are able to use it, do they?
EDIT: Aroma seems quite simple... But I hope for you it's stable enough when trying to stabilise the device
Related
I have been flashing different roms made for different carriers and I keep coming across people with the same issues in every thread. I thought it would be a good idea to have a list of common problems people seem to be having while flashing along with their solutions. This will not only be an easier/faster way for the flasher to solve his problem, but a way to prevent unnecessary clutter in rom threads with questions that have been asked repeatedly.
Feel free to post any issues you com across and/or any solutions you have to offer. This post will be updated frequently to help you guys out.
Before I get started I just want to stress the importance of doing a clean wipe before flashing a new rom. I have used this analogy in another thread, but I think of roms as women. If you want a flawless transition from one to another without any drama, they must never find out about each other. This means erase all proof of the previous one's existence. Everybody's 4g/gps issues would be non-existent if they would wipe their phones properly. When switching roms, apart from the normal wipe it is also necessary to delete the "Android" folder in your internal/external storage. If you like to play it safe, wiping them both after a backup gives you best results. This is because conflicting data stored on your card from the previous rom can screw with the new one. For those of you with sdcards bigger than my bank account who don't have that much time to spare, just deleting the android folder should be enough.
Problem
My GPS doesn't work.
Solution 1: Most likely you flashed a new rom on top of another one. As said above just wiping is not enough. GPS information is stored on your internal/external storage. This can be erased by either wiping it clean before flashing the new rom or simply deleting the "android" folder.
Solution 2: If that doesn't work (which it should), many people have had success with an app called GPS Status and Toolbox from the appstore. After downloading use the settings menu to release GPS data and fix a new lock.
Solution 3: This one's my least favorite, but some have flashed an old rom that previously had GPS working, got a GPS lock, and then reflashed the new rom.
Problem
My 4g doesn't work.
Solution 1: Always check the OP in the rom thread. Find out if the rom is based on a modem other than the one you have.
Solution 2: If you are using a rom created for another carrier there are two ways you can go about fixing 4g. The easiest way is to install scott's verizon patch HERE. The harder way is to make the required changes yourself which you can learn how to do HERE.
Problem
My apps are acting weird after I restore a backup.
Solution: Most likely you are restoring from Titanium Backup. It is a known fact that restoring data using Titanium Backup can cause a number of issues. Restore only the apks of the apps you need. Restoring data (never restore old system data on a new rom!) will only cause conflicts. If you absolutely have to keep data for a particular app restore only those that you need one by one if you are sure that no system data is being brought along with it. It may be more tedious, but it will keep you from having issues.
Problem
I keep getting a text message from "6250" saying "VZWNMN: 1" or something of that nature.
Solution: This is an issue with backup assistant sending repeated queries to your phone via text message. To stop this from occuring log into your account at www.verizonwireless.com and disable backup assistant completely.
More issues and simple fixes which will be posted as I find the time. But these are the top 4 I come across about 20 times a day so they are the ones that readily stand out in my mind.
After many weeks finding all the possible means to fix my Vibrant with a non-mountable internal SD, here some hints for future users do not waste too much time, as I did, trying to fix it.
Of course there are many "PHD"Threads, regarding this topic, in the forum, but many are kinda confusing or not for this specific mobile model.
If your recovery keeps saying that it "cannot mount internal SDcard"or Cannot mount mmcblk0p2, means your internal SD is gone and you have lost all the data on it (Blame Samsung, and its cheap hardware, for that).
First of all, DO NOT WASTE TIME TRYING TO RECOVER IT.
I have seen many people that have wasted precious time trying to Lagfix, Repartition, Flashing it to stock over and over, popping out batteries and so on, and nothing worked. You can give it a try (other posts have many outcomes). But for me it was only worries and no fun.
here`s how I definitely figured it out:
- If you`re acessing the recovery (CWR, Semaphore, Overstock, or whatever kernel), you`re good to skip the flashing process. If not, Back up all your data (oops, there`s no data to back-up :silly: - So why many posts keep saying that, regarding this issue??) and flash it ODIN back to stock (links and files of how to do it can be found within the forum). I used the SGH-T959.tar and 802.pit file. No need to check any of the options (repartition, reboot,...), but no problem if you do.
- If you have stock or not, remove your external SD card from the phone and plug it into your computer DIRECTLY (do not do it remotely via USB-Phone connections). Download your preferred partitioning software (I use Mini Tool Partition) and reparation your SD card in 2 blocks (one FAT32-Primary and the other EXT(4 or 2)) - Do not need to warn you`ll lose all the data in the SDCard - Doesn`t matter the sizes, but be sure you`ll have, at least, 1gb at each side (otherwise you may not have enought memory for apps and midias). To learn how to do that, please rely on specific posts on this subject.
- Copy your preferred ROM and GApps ZIP file on your FAT32 SDCard partition. Copy also this very handy zip file from this genius guy:laugh: (It will spare you from the annoying task reedit the vold.fstab file and also the risk of screwing-up the installation process and have to start all over, and over - for me was like 200 times). Plug back the SD into the phone and turn it on recovery mode.
- Once you`re in recovery mode (see how to do it over the forum as well), choose the specific ROM for your kernell. I suggest always to use the CWM 5.2 because it handles most of the android versions. And also prefer the Cyanogen Mods, since the SlimBean rom has caused this whole issue with my phone (Yes! The ROM can ruin your device, so choose it wisely).
- Chose install from SD card and then install zip from SDcard. Install your ROM, GApps and the linked vold.fstab.zip file, in a row. If you have an error message during the installation (with a warning sign over the robot), it means you`re under an incompatible kernell and must switch to the one compatible with your Android version (see details about that in the forum as well). If everything installed correctly, reboot the phone and have fun.
- "Voilá", you now may have a fully operating phone again. The bigger the SD card capacity you choose the better.
Hope to have a simple clear summary of how to fix this not-cool-at-all Samsung bug on Vibrants.
This is what I did and it worked for me.
http://forum.xda-developers.com/showthread.php?p=44794712
And 2 posts down I explain what I did
So, after much research and trepidation, I flashed my first ROM to my i717 last week. Then I decided I didn't like that ROM and flashed another an hour later. So far it's been stable and speedy. I'm very happy. Thanks to XDA-Developers, Google, the Internet, and everyone who made this possible.
So, now, here's my simplified guide to doing what I did. This should NOT be taken as gospel. Please read as much as you can first. But, in an effort to give back, I thought a simple, step by step guide (or, more like links to the guides I found helpful) would be useful to someone. Are we sitting comfortably? Then let us begin.
1. Go here - http://rootgalaxynote.com/galaxy-no...y-note-sgh-i717-icsgingerbreadeasiest-method/ - and root your phone. It will also install ClockworkMod Recovery. Both of these need to be done before you can flash a new ROM.
NOTE: I hear that TWRP is the preferred recovery app. I've tried it and it's very nice. It just so happens that I had ClockworkMod installed when I actually decided to flash a ROM. But use whatever you like.
2. Go to the Play Store and buy Titanium Backup Pro. Well, actually, download the free version then buy the Pro key. There are other backup methods, but I like this one.
3. Backup EVERYTHING. You might never restore a particular app, but best to have it and not need it than need it and not have it. I like to use the Google Drive option in Titanium to push by backup off my phone. But you can just hook it up to your PC and copy the backup folder from your SD card to your PC. This is just in case something REALLY bad happens. Best to have an off-phone backup.
4. Find a nice ROM to settle down with. I'm using Revolt (http://forum.xda-developers.com/showthread.php?t=2288566&highlight=revolt) but do your research and find one you like. If you decide to go with something built off Android 4.2 or 4.3 then you'll lose the Samsung Touchwiz stuff (fancy SPen features, etc.), but to me that wasn't as big a deal as I though.
NOTE: Make sure you know if the ROM need an additional Google Apps package. Sometimes they're listed with the ROM, sometimes not. Read and make sure or you could lose a lot of phone features or it may not even boot. Again, READING IS YOUR FRIEND.
5. Save the ROM (and GApps file if needed) to your phone's SD card (internal or external doesn't matter)
6. Boot into recovery (Hold Vol UP+Vol DOWN then press PWR and hold all 3 until you feel a vibration, then let go of PWR). When ClockworkMod (Or TWRP) comes up, RUN A BACKUP!
7. Read 6. Make sure you actually do it. I'll know.
8. Once you're sure you have your Titanium and ClockworkMod backups, follow the instructions for installing the ROM. Usually this involves (from ClockworkMod or TWRP):
a. Factory Reset
b. Wipe Cache (this is usually a part of Factory Reset, but doesn't hurt to do again)
c. Wipe Dalvik Cache (see cyanogen's response here for what this does - http://forum.xda-developers.com/showthread.php?t=519495)
d. Flash new ROM
e, Flash Google Apps (you can also wipe cache and Dalvik cache between d and e)
9. Now the moment of truth. Reboot. Wait. This can take some time, so don't fret if it seems to be taking too long. I'd say if it's over 15 minutes then you might need to worry, but chill before then)
10. When it does boot, you'll basically have a fresh, new phone. You'll need to enter your Google account and follow all the usual stuff you did when you first got your phone.
11. Leave your phone alone now. You can click around, but don't install anything new just yet. I've seen many a post about letting things settle. So, maybe, poke around for 15-30 minutes just to see but don't change anything. Then Reboot
12. Now reinstall Titanium. You can start reinstalling your apps. DON'T reinstall standard apps or they could break (e.g. email app or its data) as the new ROM might not support the old version of the app. My rule of thumb is don't restore any data I can get back from my online accounts (Email, FB, G+, Keep, etc.). All of your pics and that should be on your SD card and should not need to be restored.
13. That's it. If you enabled a scheduled backup in Titanium you might want to disable it for a while to make sure you like what you have. That way, you can go back if you don't like it.
Hopefully that helps someone. Please forgive any mistakes or omissions and if anyone with more experience wants to give it a once over I'd appreciate it.
Thanks and good luck.
Sorry guy, but on step one there is a very high probability of someone bricking their phone.
Why? Because it has happened about 100 times over the past two years from people using that site/method. If you flash the wrong kernel you kill your precious.
You should edit your step to say in the strongest terms triple check your operating system and get the correct kernel.
And step one is unnecessary because all roms here are already rooted.
1. Flash TWRP using pc and Odin.
2. Download new rom.
3. Boot into recovery.
4. Wipe cache, system, data.
5. Flash rom. Boot and wait 10 minutes.
6. Check settings for networks.
7. Optional modem flash.
Only wipe that's needed is a factory reset within recovery. That wipes /cache too. The dalvik cache resides on the data partition and is thusly wiped as well.
The Rom will have a format /system line within the updater script.
And within titanium backup don't backup or restore system settings (anything in the list that's red.)
And as said rooting first isn't needed unless you've been using stock for awhile and have apps you'd like to backup first... the easiest way to root is simply flash the latest twrp with Odin.. boot into recovery... then when you go to reboot the system it'll see that you're not rooted and ask if you'd like to do so.
Thanks for the feedback. Like I hope I stressed, this is the method that worked for me.
I guess I have the terms mixed up in 1. I'm saying to install ClockworkMod (or TWRP) and root your phone. I want to root it here because I want Titanium installed before I change ROMS so I can go back to exactly how everything was before modding if I want. Does that make sense?
Also, can you tell me what's specifically wrong with the site I link in Step 1? I was on ICS at the time I think. Does it brick if you do it on JB?
I'll change the step to say to go here instead - http://teamw.in/project/twrp2/96
Is that better?
Also, can you explain your cache wipe suggestions. I've seen the official instructions say to Reset, then Wipe Cache, then Wipe Dalvik. I know the last 2 are included in the first, but why are we explicitly asked to do them again? Why do you think we don't?
My thinking behind adding it here is that it does no harm and if some devs think that not doing it will cause problems then why not include it to be extra safe.
If you wanted it back to the way it was before modding anything then you could flash a custom recovery and do a nandroid backup before rooting at all.
Titanium backup needs root. If you want your app data after flashing a rom then that's when it's needed.
As far as extra wiping... putting your arms over your head spinning in a circle while chanting a manta does no harm either and is just as effective.
When you flash as often as I do... you wanna streamline the process. Extra anything is just that... Extra... and is just a waste of time
His first step is correct. No one that I know has bricked their phone using those directions because that link does not install any kernels. And it never did. It works for all versions of android. Even after all this time there is so much misinformation given.
Studacris's help is as good as gold though. He has put me in my place in the past.
Thanks Everyone.
So I got given a lenovo tab the other day, i'm completely new to tablets and android software but it didn't take me long to fill up the native storage and this is where the program loophole began.
I had a few micro 32gb sdcards sitting around, so I did a speed check on them and put in the fastest one in the lenovo tab, after installing a good few programs which states they move programs to sdcards, which they do to a degree but nothing was better than the already built in move app to sdcard. I then found out about that to be able to take advantage of the sdcard fully, you need a rooted device.
This is where I found kingroot, which I then installed and started to use, after finishing up installing the standard health programs (antivirus, malware scanners etc), which flagged kinguser. After doing a bit of research about this program, I decided that I didn't feel safe using it, so I was looking around for alternatives.
I then found out, the program didn't like to be uninstalled so I started to use supersume pro, which did a good job removing kingroot but it didn't install super su as stated.
I am now in the process off trying to install twrp (which is proving to be more difficult than any other stage of this process), so i can then install super su, so i can use folder mount (this turned out to be the best program of them all imo), which in turn will allow me to use my sdcard.
This is where I am stuck, I have installed the drivers to pc, installed minimal adb and fastboot, also I have installed android studio. I have been able to use fastboot from the pc to send commands too the tablet but the bit that's confusing me is, how to tell the fastboot tablet to pull the twrp file from the sdcard ?
Or is there a vast simpler way of doing what I am trying to do, in the safest possible way.
tldr: What is the 'safest' way to root my tab for a newbie so i can use the sdcard fully at my discretion without being sent into a program loophole. Apologies for any bad grammar, it was never my strong point.
Nevermind, I managed to do it after 5 painstakingly days with hardly any sleep to rectify this issue, although I nearly bricked it in the process by installing the wrong twrp file but thankfully with all the info on this website, I have managed to undo all the problems and re root successfully and 'safely' using twrp and supersu zip as guided in another topic on this forum. So thanks to all developers and users, my tablet is now spyware and adware free for the most part.
ComatosedUser said:
Nevermind, I managed to do it after 5 painstakingly days with hardly any sleep to rectify this issue, although I nearly bricked it in the process by installing the wrong twrp file but thankfully with all the info on this website, I have managed to undo all the problems and re root successfully and 'safely' using twrp and supersu zip as guided in another topic on this forum. So thanks to all developers and users, my tablet is now spyware and adware free for the most part.
Click to expand...
Click to collapse
Can you provide a few more details? I'm trying to do the same thing here but didn't manage yet... Also didn't find any rooted roms yet. Help highly appreciated
.acy said:
Can you provide a few more details? I'm trying to do the same thing here but didn't manage yet... Also didn't find any rooted roms yet. Help highly appreciated
Click to expand...
Click to collapse
Hello... I do not know of your experience with android devices... But it probably will not help looking for "rooted roms"
Try googling "tb3-710f custom rom" or "tb3-710f stock rom" or "tb3-710f firmware".
If you are successful in finding firmware/rom then look for a guide to root. I myself have some experience, I will also see if I can assist you with more information through pm' s.
---------- Post added at 09:15 PM ---------- Previous post was at 09:09 PM ----------
.acy said:
Can you provide a few more details? I'm trying to do the same thing here but didn't manage yet... Also didn't find any rooted roms yet. Help highly appreciated
Click to expand...
Click to collapse
Actually... take a look at https://forum.xda-developers.com/android/general/tb3-710i-tb3-710f-rom-stock-rom-lenovo-t3437810. @PhatBmt009 seems to have a collection of everything you might need to root in regards to your device. I did not go through the whole thread though to see if the process is explained.
Please take a look by yourself and hit PhatBmt009's thanks button if you find the information helpful.
Good luck!!! :good:
r&xp said:
Hello... I do not know of your experience with android devices... But it probably will not help looking for "rooted roms"
Try googling "tb3-710f custom rom" or "tb3-710f stock rom" or "tb3-710f firmware".
If you are successful in finding firmware/rom then look for a guide to root. I myself have some experience, I will also see if I can assist you with more information through pm' s.
---------- Post added at 09:15 PM ---------- Previous post was at 09:09 PM ----------
Actually... take a look at https://forum.xda-developers.com/android/general/tb3-710i-tb3-710f-rom-stock-rom-lenovo-t3437810. @PhatBmt009 seems to have a collection of everything you might need to root in regards to your device. I did not go through the whole thread though to see if the process is explained.
Please take a look by yourself and hit PhatBmt009's thanks button if you find the information helpful.
Good luck!!! :good:
Click to expand...
Click to collapse
That is great advice, once you know for a fact you have the original firmware for you're device and learn how to use adb or fastboot, then you can start to play around a bit with some of the software. I probably went through about 50 websites absorbing as much info as I can and the rest comes with trial and error with a big fear off bricking the device and the only thing you can do to really brick it, is by corrupting the data to a point of not turning on, which is why I was learning on a cheap tab like the tb3, which is a great tab for the price.
In the end for me it was just a case off installing twrp, theres 3 variants here https://www.androidfilehost.com/?w=files&flid=80021 so massive props to Tzul, which then allowed me install supersu zip to root the device, how safe supersu is, I have no idea yet but so far its way safer than kinguser or one click root from what I have read.
Well now I am stuck and need professional advice, Last night, I don't remember what I was trying to do but in twrp I selected wipe davlik cache and wipe data (without knowing what it fully does, like a true noob mistake), this process took so long I fell asleep. I woke up this morning and the device was hanging on the boot screen. I did manage to take the battery out and reboot back into twrp mode which is enabling me to go back into the twrp menu and also fastboot if needed. So what can I do from here to reboot back into normal or do i need to flash the firmware ?. I don't mind losing all my data and starting from scratch but would be better if i didn't need to do that ofc, so any advice or help would be most welcome lol.
ComatosedUser said:
Well now I am stuck and need professional advice, Last night, I don't remember what I was trying to do but in twrp I selected wipe davlik cache and wipe data (without knowing what it fully does, like a true noob mistake), this process took so long I fell asleep. I woke up this morning and the device was hanging on the boot screen. I did manage to take the battery out and reboot back into twrp mode which is enabling me to go back into the twrp menu and also fastboot if needed. So what can I do from here to reboot back into normal or do i need to flash the firmware ?. I don't mind losing all my data and starting from scratch but would be better if i didn't need to do that ofc, so any advice or help would be most welcome lol.
Click to expand...
Click to collapse
Ooops... Anyway...
Did you at any point allow TWRP to make modifications to the system?? I found that when I did that on my device it totally destroyed partition structures and went into infinite boot loops.
Also while i was trying to fix any issues (pretty much like you right now though TWRP) I noticed that when I tried to flash either supersu or twrp again or something else, I was getting a ton of red system messages not being able to mount partitions.
If that is your case, unfortunately, you might need to re-flash...
You might want to also check here: https://forum.xda-developers.com/android/help/lenovo-tab-3-8-tb3-850f-unbrick-root-t3598727
After applying these steps, both superuser and TWRP have had no issues with anything!!! (fingers crossed, until today that is... )
Keep us informed, especially if you find a way to actually overcome this without flashing stock and doing everything from the beginning.
Good luck for now! :good:
Thanks I wish I saw you're thread before, it would have saved me a lot of time early on but, oh boy what a day I have had with this device today, I am not sure what I did to fix it but i basically did the same steps again to wipe the cache and clear the data within twrp then rebooted. What I didn't realize was in the process of disconnecting the battery, the case snapped off part of the sdcard (so to all noobs like me, MAKE SURE TO TAKE SDCARD OUT BEFORE TAKING CASE OFF) which in turn caused a short somewhere, the device started to get really warm and twrp was showing the cpu getting to 53c, I quickly dc the battery again and pulled the sdcard, I went and got a replacement card
After a succesful reboot, the device booted up as normal so a big phew there, now a lot of the apps/games that was previously installed and linked to the sdcard are having some difficulty re downloading and installing with a few errors, some have been succesful but now i'm wondering if a full wipe will be in order here ? as the internal storage is still showing only 1gb free but I also want to keep twrp and supersu.
The original thought process was using the least amount of internal storage as possible since I have a hi speed 64gb sdcard and some games apps was still taking up a lot off the 8gb internal space, as some didn't like a full link via apps2sd with the internal data but with the ones that was succesfull didn't have any noticable slow load times. I would like to keep the dalvik cache of all programs on the internal storage if this helps with speed ? or does that not matter.
ComatosedUser said:
The original thought process was using the least amount of internal storage as possible since I have a hi speed 64gb sdcard and some games apps was still taking up a lot off the 8gb internal space, as some didn't like a full link via apps2sd with the internal data but with the ones that was succesfull didn't have any noticable slow load times. I would like to keep the dalvik cache of all programs on the internal storage if this helps with speed ? or does that not matter.
Click to expand...
Click to collapse
Congrads on reviving the device!:good::good:
Out of the 8 Gigs, how much space does the whole system occupy? Did you try to remove bloatware? Did you use any similar app to root uninstaller to get rid of unwanted/ unused apps?
To my limited understanding it would require some extended knowledge in programming to re-assign partitions (ie cache) or making other than default partitions actually become the default partitions for any purpose.
Anyway... I can understand how 8Gigs internal storage can be limited... You can try:
1. Since you have custom recovery installed, 1st and most essential step is to make full backup of EVERYTHING! Just enter TWRP hit backup and choose EVERYTHING in the options of what to backup. This will most probably not destroy the communication between external SD and system (in regards to installed apps) the next time you might need a recovery (as long as you will not make changes to the SD card in the meanwhile).
Make the backup file to an external SD. I personally use a 16GB micro SD only for backing up purposes!!!
2. After you have everything in backup, install a program similar to root essentials or root uninstaller and try to get rid of anything you do not use. This might give the system some space to "breathe"...
Let me know. I got rid of a whole bunch of stuff out of my tb3-850f tablet and the system now 'rocks' (not to mention the extended battery life...)
You can even uninstall default apps like any default system picture viewer (that consumes space in your system) and install QuickPic from the/and to the SD card. Same with video player. Uninstall system video player and install something in the likes of MX Player from/and to the ext. SD. You can make a whole bunch of tweaks and uninstalling depending on your needs. I have even uninstalled most of Lenovo related apps.
Let me know how it goes. For some reason I think you are quite experienced and perhaps you knew all these already!?! Anyhow, let me know if I can be of more help.
This whole website has been a great help and helped me learn the process again, I do have extensive knowledge in hardware and overclocking, I'm just not so good with code, html is best i can do lol. Back in the day (almost 20 years), I dabbled a bit in unbricking (bricking) and flashing old phones, the process is fairly similar, it's just a few more programs but getting the right programs and the 'right firmware' is key here.
That's a good idea to get another sd card to save backups on and root essentials sounds like a worthy program to download. As with partition sizes and what data is stored where, is still a learning process for me atm, theres so much clutter aka bloatware, i'm not sure which is safe to uninstall, I will do a thread search to see.
I may start a new thread for this as this topic is solved now but I am also looking to get a rom or app so I can start to fine tweak the power and cpu/gpu usage but so far nothing I have noticed for the tb3 ***
If any mods come across this thread can turn it to solved, pls thanks I can't edit the header.
ComatosedUser said:
Well now I am stuck and need professional advice, Last night, I don't remember what I was trying to do but in twrp I selected wipe davlik cache and wipe data (without knowing what it fully does, like a true noob mistake), this process took so long I fell asleep. I woke up this morning and the device was hanging on the boot screen. I did manage to take the battery out and reboot back into twrp mode which is enabling me to go back into the twrp menu and also fastboot if needed. So what can I do from here to reboot back into normal or do i need to flash the firmware ?. I don't mind losing all my data and starting from scratch but would be better if i didn't need to do that ofc, so any advice or help would be most welcome lol.
Click to expand...
Click to collapse
Just factory reset because u never wipe Calvin cache remember that
Hello there!
Alright, let me walk you through my problem.
(there's a summary at the bottom)
I own a rooted Asus zenfone go (Z00VD). In the past, I kept on waiting on boots cuz of the optimizing apps thingy that android does sometimes becomes of dalvik. After some research, a guy suggested to download the app(title), so I did and it worked. And it had a obvious warning that I did not follow which is "if you wish to uninstall this app, press unfix".
Alright so here comes the real problem, I decided to install a custom rom (resurrection remix), which made me wipe everything then it always ran into bootloader because it can't delete the dalvik cache (permissions error I think). So, in a great genius manner, I renamed the arm folder to parm(from arm) which allowed the Android rom to make a new dalvik cache.
So now in internal storage, I have a parm folder that is 2.5 gb big and is absolutely undeletable, even with recovery. The folder is owned by root, and it's group is 01028 sdcard_r. I cannot change it's permissions, or move it to external. I was able to move it to DCIM, but am unable to move it back to dalvik folder to u fix. So now, I can only change it's name to profane languages. I have tried using pc(through mounting) , but it still stays(the pc shows deleting it, the phone shows another story).
TL;DR: folder undeletable due to it being grouped in 01028-sdcard_r (I think). Cannot change its place nor its permissions even with recovery.
I'm sorry if I made this a bit too long, but I wanted to show you the story of how I ended up here. You can ask me any info about anything. Thank you for the help