What is the Wipe Dalvik Cache command for adb? - Hero CDMA Android Development

I was attempting to use the Wipe Dalvik-Cache command in the Recovery menu, but, it Errors out saying:
Error : Run 'wipe dalvik' via adb!
What is the point of including it in the Recovery menu if it can't be run?
Basically, what I am asking is for the several commands that may need to be used to help or run this command?
I did see this thread
apparently I can't post a URL link...
xda-developers > HTC Dream: G1 > G1 Q&A > Clear Dalvik Cache
So there is the forum tree to the thread.
However that is for the G1 and I am not sure if the commands are similar or not.
Thanks.

GH0 said:
I was attempting to use the Wipe Dalvik-Cache command in the Recovery menu, but, it Errors out saying:
Error : Run 'wipe dalvik' via adb!
What is the point of including it in the Recovery menu if it can't be run?
Basically, what I am asking is for the several commands that may need to be used to help or run this command?
I did see this thread
apparently I can't post a URL link...
xda-developers > HTC Dream: G1 > G1 Q&A > Clear Dalvik Cache
So there is the forum tree to the thread.
However that is for the G1 and I am not sure if the commands are similar or not.
Thanks.
Click to expand...
Click to collapse
Well, if you would have searched harder -- you would have also found this:
http://forum.xda-developers.com/showthread.php?t=616953&highlight=Run+'wipe+dalvik'+adb! -- This is for OUR phones (CDMA Hero)
Anyways, when trying to clear Dalvik -- make sure you don't have the phone plugged into the cable, someone had said that fixes the problem.

Related

Elaboration on "how to root"

I think this thread can eventually turn into a sticky. I am going to ask all the common / newbie questions relating to the post by toast that is quoted below. Please contribute clear answers in the thread and I'll include them here at the top:
Q: What does RUU stand for?
A: ROM Upgrade Utility. It is used when a new ROM is available by your carrier. Don't use this since it will nullify your root.
Q: Where can I find photos of the root process?
A: Right Here, thanks to pingpongboss
Q: Where can I find the details and download locations of the custom roms available?
A: ???
Q: What is a custom recovery?
A: ???
Q: What is a recovery partition?
A: ????
Q: What things are we not able to do since we don't have the ability to
toastcfh said:
Write to system or recovery while in android
- Flash a custom recovery that can be booted into by holding vol down and powering on
Click to expand...
Click to collapse
A:
1) You cannot remove unwanted applications inside of android that couldn't normally be removed. You must remove them prior to boot.
2) ???
Q: What are all those code snipbits?
A: ??
Q: What is the point of the "recovery instructions"?
A: ??
toastcfh said:
HOW TO ROOT YOUR HTC EVO
DO NOT USE A RUU FROM SPRINT IF U WANNA MAINTAIN ROOT. WAIT FOR ME OR SOMEONE HERE TO MAKE A ROOT UPDATE.ZIP.
Major thanx for those who helped:
keishou (for the rooted build. without it none of this would be possible)
maejrep (for testing and modding a recovery for the EVO)
Flipz (for hosting the files)
Paul (for his recovery work on the desire and legend)
Amon_RA (for his recovery source on github)
WHAT THIS ROOT METHOD WILL DO:
- wipe all of your data so brace for that. backup or what not
- Allow you to flash custom roms
- Boot into a custom recovery
- Write to system, boot and recovery partitions through recovery
WHAT THIS ROOT METHOD SADLY WONT ENABLE YOU TO DO:
- Write to system or recovery while in android
- Flash a custom recovery that can be booted into by holding vol down and powering on
THINGS YOU WILL NEED:
download files below:
- PC36IMG.zip
- evorecovery
INSTUCTIONS FOR ROOTING:
- Put the PC36IMG.zip on the root of your sdcard
Code:
adb push PC36IMG.zip /sdcard
- Power off the phone
- Hold volume down while powering the phone on. continue to hold volume down until you see the WHITE bootloader screen.
- After a few seconds it will begin to checking for files, and find PC36IMG.zip. while its doing this it will show a blue progress bar while its checking. (this takes 30 - 60 seconds to finish)
- It will then list all the images in the zip and ask you if want to flash. SAY YES
- When its finished it will ask you if you would like to reboot. AGAIN... SAY YES
- At this point it will boot into a rooted rom.
- YOU ARE NOW ROOT!!!
- rename the PC36IMG.zip on your sdcard:
- plug your phone into a usb port on your desktop and do:
Code:
adb shell mv /sdcard/PC36IMG.zip /sdcard/root-PC36IMG.zip
RECOVERY INSTRUCTIONS:
- Extract the evorecovery.zip to your desktop
- plug your phone into a usb port on your desktop
- In a shell:
Code:
adb reboot recovery
- this will reboot your EVO into recovery mode. at this point turn your attention to the directory u extracted the evorecovery.zip to.
Code:
For Windows XP ~~> Run recovery-windows.bat
For Vista and Windows 7 do it as Admin
- in a shell do:
Code:
For Linux ~~> ./recovery-linux.sh
- at this point turn your attention to the phone and navigate to create a Nandriod Backup. you can now flash custom roms, write, and make changes to system.
- to flash a custom rom put the rom on the root of your sdcard. wipe data, dalvic cache and chose the option to flash update.zip from sdcard.
RECOVERY NAVIGATION:
-
Code:
Volume up/down moves through the list and Power selects.
RECOVERY SOURCE:
- http://github.com/jhansche/amonra_bootable_recovery/tree/supersonic
Code:
git clone git://github.com/jhansche/amonra_bootable_recovery.git
git checkout supersonic
Click to expand...
Click to collapse
Pics of the rooting process: http://androidforums.com/htc-evo-4g/90122-root-out.html
pingpongboss said:
Pics of the rooting process: http://androidforums.com/htc-evo-4g/90122-root-out.html
Click to expand...
Click to collapse
Phenomenal. Added to the original post. Could you please help with some of the other questions if possible?
Thanks
forumsid987 said:
Phenomenal. Added to the original post. Could you please help with some of the other questions if possible?
Thanks
Click to expand...
Click to collapse
Where to find custom roms: in this subforum xD
the rest of the questions I don't know how to answer correctly. Custom recovery lets you flash custom roms and make nandroid backups?
forumsid987 said:
Q: Where can I find the details and download locations of the custom roms available?
A: ???
Q: What is a custom recovery?
A: ???
Q: What is a recovery partition?
A: ????
Q: What things are we not able to do since we don't have the ability to
A:
1) You cannot remove unwanted applications inside of android that couldn't normally be removed. You must remove them prior to boot.
2) ???
Q: What are all those code snipbits?
A: ??
Q: What is the point of the "recovery instructions"?
A: ??
Click to expand...
Click to collapse
In order top to bottom:
As they become available you will find them in this forum. I will release a fresh rom for evo once I can test on my own device. It will be posted here, as well as at http://geekfor.me like always.
The green and black screen that you see that lets you flash a custom rom and create a nandroid backup, that is a custom recovery. The problem is because of NAND protection we can't currently flash that recovery and have it stick. That's why you have to run the bat/sh script each time, to load it manually.
It's the partition that the recovery resides on (the part of the internal storage memory).
Aside from not writing to system while booted (which was answered already) all that means is that instead of being able to boot directly in to the custom recovery view power button + home button or volume down, you need to run that script to get in to recovery. That's the only thing not being able to load the custom recovery means.
Code snipbits?
Um, because how else would you know how to get in to recovery so that you can flash a rom / create a backup / etc??
Is there any chance of fixing that recovery issue? Having to run the script to access it each time is going to get old fast.
-------------------------------------
Sent via the XDA Tapatalk App
In the rooting instructions it keeps mentioning just plug phone into usb port on a pc and in shell do this.
I am on windows 7..what shell?
maybe change the thread title to FAQ on how to root rather than elaboration, might attract more attention.
i was going to answer the questions which haven't been answered but flipzmode did a great job and the 1st post hasn't been updated. once the 1st post has been updated i'll check back and add more detailed if there is anything left to help with!
MrDSL said:
In the rooting instructions it keeps mentioning just plug phone into usb port on a pc and in shell do this.
I am on windows 7..what shell?
Click to expand...
Click to collapse
good question, this would be good to add to the guide above.
the shell on windows 7 means the command prompt. never used win 7 but on win xp and vista, start->run->cmd
and it pops open the command prompt, navigate to where you extracted the zip file contents to, cd c:\evo-root\ . then run the .bat file by typing recovery-windows.bat .
on linux the terminal interface is called a shell because it actually brings up a shell binary, /bin/sh or /bin/bash . google these binaries for more detailed information. on windows the shell, is basically the command line which is now emulated in windows, where back in the days of DOS it was the actual system with windows loaded on top as a GUI...
sorry prob too much information!
Is there an alternative to reboot recovery that does not require ADB?
forceOnature said:
Is there an alternative to reboot recovery that does not require ADB?
Click to expand...
Click to collapse
an alternative way to reboot into recovery without using adb?
boot into the bootloader and select recovery? use the quick boot GUI to reboot directly into recovery? use connectbot and connect localhost, type reboot recovery?
you'll be needing ADB for a good chunk of the custom recovery process in order to load this Froyo ROM.
adb isnt too bad, just dive in and we're all here to help!
MrDSL said:
In the rooting instructions it keeps mentioning just plug phone into usb port on a pc and in shell do this.
I am on windows 7..what shell?
Click to expand...
Click to collapse
Start -> Accessories -> Right-Click on "Command Prompt" -> select "Run as Administrator".
If you don't need to run as admin, you can do
Start -> type cmd -> Enter
and it'll come up.
adb driver for windows 7
http://depositfiles.com/en/files/yd61xorii
Anyone have some solid "Adb on Mac" instructions? LIke how to get it going on a mac... Just switched from PC... Thanks
a5ehren said:
Start -> Accessories -> Right-Click on "Command Prompt" -> select "Run as Administrator".
If you don't need to run as admin, you can do
Start -> type cmd -> Enter
and it'll come up.
Click to expand...
Click to collapse
I believe Start -> type cmd -> Shift+Enter will run as admin also.
JustinChase said:
I believe Start -> type cmd -> Shift+Enter will run as admin also.
Click to expand...
Click to collapse
Simply put im on a mac and a windows at the same time.. I cannot get the bat to run correctly I see it run but it looks like a fc and then it closes.. On the mac I get asked for this..
sudo: ./adb-mac: command not found
sudo: ./adb-mac: command not found
new-host:~ GodDriven$ sudo: ./adb-mac: command not found
Please help?

Bootloop after Trickdroid tweaks

Hello Forum,
I have a problem with my Htc One S today i installed Trickdroid 8.0 and it worked fine so i wanted to install the tweaks too. So i selected what i wanted and when the phone started it got stuck at the bootloader screen. I thought it just needed some time but after 15 minutes i gave up and turnt it off. Then i went into the recovery to install the rom newly but it always says it can't mount the sd card. Already relocked the bootloader and tried to install the europe ruu 1.78 but i got error 131 i have read that might be, beacause mine was branded by T-Mobile (but no simlock or else)
Really need help appreciate any answer
Really no one knows how i can fix this ? Need to fix it pretty soon because i need my phone :/ I can't even turn mine off, so i just let the battery die don't think that's to good either
Boot into recovery and ref lash. What tweak did you do? Not all work with 8.0. Tweaks have not been updated for this version. Make sure to do a full wipe.
j0hnh0lmes said:
Boot into recovery and ref lash. What tweak did you do? Not all work with 8.0. Tweaks have not been updated for this version. Make sure to do a full wipe.
Click to expand...
Click to collapse
I can't reflash in recovery, because it always says "can't mount sd card"
Don't remember all of the tweaks i did but i did the nova launcher, remove sense, some apps, all of the tweaks on the first page and some other.
Okay now I did a "clear storage" and a "reset to factory defaults" with a stock recovery and after that i reinstalled the custom recovery again. Now I can access the sdcard again but it's empty of course. Then i bootet in recovery and tried to push the trickdroid zip on to the sdcard via adb like this "adb push Trickdroid_v8.0.0.zip /sdcard/Trickdroid_v8.0.0.zip" but then it says:
daemon not running starting it now on port 5037
daemon started successfully
protocol failure
and simply ends. How can I push the Rom really need help, because my phone has no rom at all right now ?
ah okay needed to use the adb in the android sdk folder not in the little fastboot folder i had it just worked
Not at home to double check your command line--sounds like that is issue
But, you can type adb devices first to see if phone is recognized
I usually cd to the directory I have adb/fastboot files in, put zip on C: root
and type: adb push C: "then the rest"
rugmankc said:
Not at home to double check your command line--sounds like that is issue
But, you can type adb devices first to see if phone is recognized
I usually cd to the directory I have adb/fastboot files in, put zip on C: root
and type: adb push C: "then the rest"
Click to expand...
Click to collapse
Thanks for your help but as i have written i already got it back working thread can be closed
Sorry,
I posted before your edit showed up--
Glad to hear.
steps for next time
Hi, just before the thread is locked.
What has helped me in more of these occassions:
1. Make sure you read the install instructions of the ROM builder (I overlooked the 'flash Boot.img' which was added after some version)
2. Make sure you don't 'custom' work your memory (no partitioning etc).
3. First install the ROM and do REQUIRED afterwork (most often: Data/factory reset. Which doesn't wipe your photo's or just your account information and saved settings that will interfere with new rom options)
4. after making sure it boots and it reboots.
5. If this is the case, make sure you get the tweak package pointed out by the rom builder.
6. If all else fails, first read up on XDA and rom builder's site (often community on XDA) THEN start actions well informed.

[Q&A] [HOW-TO] ADB Push a ROM to your phone

Q&A for [HOW-TO] ADB Push a ROM to your phone
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [HOW-TO] ADB Push a ROM to your phone. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
brwetz said:
Hello all,
I've seen multiple people who recently, by one way or another, have a phone that have the bootloader unlocked, device rooted, and a recovery flashed...but for some reason you don't have a ROM flashed and your phone won't boot up past the bootanimation. If you're in that situation, this will hopefully help solve that issue.
What this thread is designed to do is inform you how to flash a ROM.zip file onto your seemingly bricked HTC One S device that you can't boot up. As you know, usually if your phone boots up, you just plug it into your computer, mount it, and just drag and drop the file. Well, for those of you that have no way to do that, I hopefully have a fix for you!
Requirements:
Unlocked Bootloader/Rooted Device
CWM Recovery flashed from fastboot.
Basic knowledge of adb/fastboot commands
Steps:
- Download your ROM of choice (referred to as ROM.zip) and place it wherever your ADB is on computer's harddrive (referred to as c:\AndroidSDK\tools)
- Boot your phone into Recovery and select the "Mounts & Storage" screen
- Plug your phone into your computer using USB Data Transfer Cable
- Ensure in Recovery that your phone shows "Unmount /sdcard/" and "Unmount /system/" (If they do not show this automatically, just press each one once respectively as pressing just toggles Mount and Unmount)
- Open Command Prompt on your computer by doing Start -> Run -> cmd
- In Command Prompt, type "cd c:\AndroidSDK\tools" replacing AndroidSDK\tools with wherever your adb and ROM are located.
- This is probably the most important part - Still in Command Prompt, type "adb push ROM.zip /sdcard/ROM.zip" replacing ROM with the EXACT name of the ROM file and including the .zip piece on both ends. This may take a minute or two...or four, but you will see a message in Command Prompt saying something like <12345678kb to 1234567kb>. That is just telling you that the file was pushed properly. (I did not include that message in the picture below)
- Once this has completed, unplug your phone from your computer and close the Command Prompt window
- Back in Recovery, go to Recovery's main screen and Do a "Factory Reset", "Wipe Cache Partition", and "Wipe Dalvik Cache [which is in the Advanced menu of Recovery]"
- When these are all done, from Recovery's main screen, select "Install ZIP from SD Card" and then "Choose file from SD Card" and select the ROM.zip file you just pushed from your computer to the SD Card. If you do not see the file, go back to Mounts and Storage and toggle them to say "Mount /sdcard/" and "Mount /system/" and then go back and try to fine the ROM.zip file. If you still do not see it, it was not pushed correctly...go back and ensure you were letter for letter with the name and the file path.
- Once the screen in Recovery says "Install from SD Card Complete.", go back to Recovery's main screen yet again and select "Reboot system now" - If your device fails to Install the ROM.zip, I had this happen to me. You must push the CWM SuperSU ZIP (the .zip file is found at the end of this thread)file as outlined before and Install THAT .zip file in Recovery, then reboot Recovery and Install the ROM.zip from SD Card.
- Let your phone have some time to boot up...initial boot from installing a new ROM have histories of taking a couple minutes.
- You should now be on a working HTC One S running whatever ROM you decided to flash.
Conclusion:
I hope you got your phone working again and I hope this helped. Please feel free to critique this guide as I am quite new to the HTC One S, but not new to rooting phones at all. If you have questions, please comment and ask or don't hesitate to shoot me a PM...I'm more than willing to help.
I hope this helped all of you who may be in the situation I was in and the situation I've seen a couple of people in.
Thanks for this information goes out to doktortaru, strker45, and torxx.
Click to expand...
Click to collapse
Hey i'm in a similar situation. Tried flashing a ccustom rom on my Lg Optimus G. Everything went fine but phone stucked on LG logo. Thought factory reset will fix it so I did the factory reset. But unfortunately it didnt and my Backup was erased by the factory reset. I have a copy on my laptop but cant conenct my phone to pc in cwm. Mount USB storage doesnt works..
+1
MC DEV V7 is out... Check it
Galaxy GT-S7582 dous 2 problem
i got this kind of Galaxy I cant use download mod and recovery mod .. !!!
how can i fix my phone without these steps ???
thank you very much sir...
this post was very useful .. with the help of adb i flashd new rom i my xperia .. as otherwise i was very hopeless as my previous rom was not booting and i was stuck in a bootloop situation ....
but before flashing a new rom , wipe the previous os... it works ..
...and after, how can erase the ROM?
Excellent guide .. thank you very much, it helped me a lot. Now I have a question. How do I delete the ROM? can not find the folder where it is stored .. do not know if it's within the system. Do not know how to delete it. Thank you!

Please help to unbrick

Hi,
I am looking for some help as I did something stupid...
I came across some posting that explained that the moto has an unused partition under /cache that could be used for the dalvik-cache.
So I tried to move the dalvik-cache there and link /data/dalvik-cache to this new location.
Now the problem is that I get an "unfortunately the location-service has stopped" message all the time that makes the device unusuable (as soon as I press ok the same warning appears again).
When I try to boot into recovery I get a "dead android robot".
I can however access the device via adb, unfortunately I am not able to get a root shell. My device is rooted, but su in an adb-shell just hangs.
If I could only get a root-shell I could undo my changes and hopefully my device will work again, but I have to idea on what to try...
Can anone help me here?
morgonhed said:
Hi,
I am looking for some help as I did something stupid...
I came across some posting that explained that the moto has an unused partition under /cache that could be used for the dalvik-cache.
So I tried to move the dalvik-cache there and link /data/dalvik-cache to this new location.
Now the problem is that I get an "unfortunately the location-service has stopped" message all the time that makes the device unusuable (as soon as I press ok the same warning appears again).
When I try to boot into recovery I get a "dead android robot".
I can however access the device via adb, unfortunately I am not able to get a root shell. My device is rooted, but su in an adb-shell just hangs.
If I could only get a root-shell I could undo my changes and hopefully my device will work again, but I have to idea on what to try...
Can anone help me here?
Click to expand...
Click to collapse
The dead android bot is normal for stock recovery, if you didn't install a custom one. You can always flash a custom recovery using fastboot, and wipe the dalvik-cache and regular caches. Or, in the "dead android bot" screen, you can press the Vol+ key for about 15 secs, then tap the Power button, then scroll using the Vol buttons to something that says wipe cache. You might have to wipe dalvik-cache as well, if you can. I forget where the options are, since I haven't used the stock recovery in so long, sorry!
Ok, I managed to get beyond the "dead android" and from the menu I did a "wipe cache parition". That ran for some minutes, then it rebooted.
But after that I still have the same problem. The continuous "unfortunately the location-service has stopped" messages still persist.
Any other ideas?
Do you have an unlocked bootloader? If you do, the simplest solution may be to flash back to a stock ROM.
audit13 said:
Do you have an unlocked bootloader? If you do, the simplest solution may be to flash back to a stock ROM.
Click to expand...
Click to collapse
Yes my bootloader is unlocked. But I don't want to loose too much...
I believe the problem is only a permission-problem in my new /cache/dalvik-cache directory (/data/dalvik-cache now links there).
So all I would need is a way to get a root-shell (the device is rooted).
I can do a "adb shell" as normal user but that does not have the permissions to even look into /cache and for whatever reason when I type "su" I don't get an error nor do I become root but the command simply hangs...
The system as such still seems to work, e.g. my Moto still connects to my hotspot and I can ping it from there.
The even seems to be an "adb root" command, but that does not work on my adb. Is there a version of adb somewhere that would honor adb root?
Anyone with another idea on how to get a root-shell in my situation
Sorry, I don't know enough about adb commands to change the directory back to the default.
I assume you have usb debugging enabled and your computer is a trusted machine?
USB debugging is definitely enabled, whether or not I've set up my PC as trusted I don't remember.
If I didn't could that explain why I can get a shell but not as root or would you without a trusted computer not even get a shell?
Ok, issue resolved.
I've flashed clockworkmod recovery and cleared the dalvik-cache with that. That did the trick.
And moving my 300MB dalivk-cache to /cache seems to have worked and frees up memory for me, even better.
Finally the reason I could not get root in the adb shell was that when I type su in the adb-shell a superuser-request pops up on the phone that you have to acknowlege. But with constant warnings poping up I did not even see that...
Thanks for all support.
For the Developer options, look under Root access. Did you grant root access to ADB and apps?
When you type su, look at the phone's screen. Are you prompted to grant root access to ADB?

How to create a TWRP flashable zip to wipe system partition and reboot to bootloader?

I'm working on a tool app for windows and I need a small script that the user can sideload in TWRO and the script would format the system partition and reboot to bootloader. I'm not as good at making TWRP scripts so I would be happy if someone could help me with this.
The main reason I need this is because the `fastboot erase system` command doesn't work anymore on the phone I'm making this tool for. It gives a strange error "Permission Denied". I have no idea why maybe the OEM disabled the use of this command.
SnoopDoggyStyleDogg said:
I'm working on a tool app for windows and I need a small script that the user can sideload in TWRO and the script would format the system partition and reboot to bootloader. I'm not as good at making TWRP scripts so I would be happy if someone could help me with this.
The main reason I need this is because the `fastboot erase system` command doesn't work anymore on the phone I'm making this tool for. It gives a strange error "Permission Denied". I have no idea why maybe the OEM disabled the use of this command.
Click to expand...
Click to collapse
You can just wipe reformat system partition as ext4 and reboot to bootloader then flash ur image
plus i dont remember that you can force device to reboot to fb with openrecoveryscript
SnoopDoggyStyleDogg said:
I'm working on a tool app for windows and I need a small script that the user can sideload in TWRO and the script would format the system partition and reboot to bootloader. I'm not as good at making TWRP scripts so I would be happy if someone could help me with this.
The main reason I need this is because the `fastboot erase system` command doesn't work anymore on the phone I'm making this tool for. It gives a strange error "Permission Denied". I have no idea why maybe the OEM disabled the use of this command.
Click to expand...
Click to collapse
You can wipe system using TWRP alone, no script needed. Just choose the "Wipe" option in TWRP, then choose "advanced wipes" then you will see a list of partitions, select the system partition then swipe the slider to perform the wipe and you're done.
The, go back to home screen in TWRP and choose the "Reboot" option, then choose to reboot bootloader, done.
Sent from my SM-S767VL using Tapatalk
Droidriven said:
You can wipe system using TWRP alone, no script needed. Just choose the "Wipe" option in TWRP, then choose "advanced wipes" then you will see a list of partitions, select the system partition then swipe the slider to perform the wipe and you're done.
The, go back to home screen in TWRP and choose the "Reboot" option, then choose to reboot bootloader, done.
Sent from my SM-S767VL using Tapatalk
Click to expand...
Click to collapse
I know all of this but the idea was to actually do this automatically which I've found the solution by using adb shell and mkfs.f2fs to format the system partition which works just great.
oneboiwithRosy said:
You can just wipe reformat system partition as ext4 and reboot to bootloader then flash ur image
plus i dont remember that you can force device to reboot to fb with openrecoveryscript
Click to expand...
Click to collapse
Yep, I've found my solution by using adb shell and mkfs.f2fs to format the system then simply adb reboot to reboot to bootloader. So now my tool does 95% of the job automatically.
SnoopDoggyStyleDogg said:
I know all of this but the idea was to actually do this automatically which I've found the solution by using adb shell and mkfs.f2fs to format the system partition which works just great.
Click to expand...
Click to collapse
Why use adb when TWRP can do it directly from the device? The point of giving TWRP the ability to do this was so that adb is not necessary. Besides, you better get used to using TWRP instead of adb, the word is that Google will be dropping support for adb at some point, adb will be a thing of the past at that point.
You can run scripts using the terminal emulator that is built into TWRP also, instead of using adb to run it.
Sent from my SM-S767VL using Tapatalk
Droidriven said:
Why use adb when TWRP can do it directly from the device? The point of giving TWRP the ability to do this was so that adb is not necessary. Besides, you better get used to using TWRP instead of adb, the word is that Google will be dropping support for adb at some point, adb will be a thing of the past at that point.
Sent from my SM-S767VL using Tapatalk
Click to expand...
Click to collapse
Looks like I have to explain myself better.
I'm working on a tool for my specific device and the idea is for the user that uses the app to not warp around his head doing all of this that's where the automation comes in and this is the main reason I was looking for an way to do it.
SnoopDoggyStyleDogg said:
Looks like I have to explain myself better.
I'm working on a tool for my specific device and the idea is for the user that uses the app to not warp around his head doing all of this that's where the automation comes in and this is the main reason I was looking for an way to do it.
Click to expand...
Click to collapse
Again, using the terminal emulator that is built into TWRP or even a terminal emulator app while booted into system to run a script would achieve the same automation without the need for an external PC.
The point is, there is a more efficient way to do this from the device itself without an external device. Would that not be more simplified and more automated than having to include booting a PC, opening adb and connecting your device in order to run the script?
Besides, the title of your thread was for a using a TWRP flashable zip to do this, if that is the case, why use adb instead of TWRP as your title suggests?
Sent from my SM-S767VL using Tapatalk
oneboiwithRosy said:
You can just wipe reformat system partition as ext4 and reboot to bootloader then flash ur image
plus i dont remember that you can force device to reboot to fb with openrecoveryscript
Click to expand...
Click to collapse
This method isn't working in my case! I tried to wipe system, also to change its file format it didn't change instead gave me an error that unable to mount system. Also, when I check partition in Orange fox it is nowhere! Anyone help me...I accidentally corrupted my system partition. I want to erase it but even adb failed to erase it.

Categories

Resources