Database Info

[Q] Rebooting to Bootstrap

I have been trolling the forums for awhile and I never post but this is something that I have not been able to come across. Why after I used the bootstrap app and load into the recovery menu that now every time I go to reboot my phone I automatically go into the recovery menu even after a successful boot? Hope I worded that right. Please help and thank you!!
just realized I am in the theme section. Can this be moved to the appropriate board. THANKS!!

That's the way it works, it hijacks the bootloader, trust me its a good thing. Bootloop, battery pull, recovery, restore backup. Several times I've been glad it works that way.
Sent from my DROIDX using XDA App

Wait. I have a normal reboot. Maybe mine is messed up?

Yeah I got that but I thought it was only if I pulled the battery after it bootlooped. It does it every reboot except after I flashed a "rom", but I didn't like the rom so I reverted back to stock. I mean its awesome to have the security blanket but it can also be a bad thing if my 14 yo cousin gets ahold of my phone then formats my system an then reboots. Thanks for the help by the way.
Sent from my DROIDX using XDA App

The recovery works by looking for a file : /data/.recovery_mode
If it's there, then it goes into recovery mode, if not, then it allows for a normal boot.
However, if doing normal boot, it actually places the /data/.recovery_mode file and then erases it once the system is fully booted. I know this is confusing, but this is how it knows to go back into recovery if you did a battery pull (ie, the file was created, but never erased since you didn't complete the boot process).
All of this is supposed to happen automagically, but I've heard of that file sometimes getting 'stuck' and not deleted. Thus, causing you to reboot into recovery every time.
There is nothing inside the file, just an empty marker. You may want to delete that file and reboot. Should help.
-Z

If you want to remove bootstrap, you can do SBF flash, which I did several times and it perfectly works.

Zaphod-Beeblebrox said:
The recovery works by looking for a file : /data/.recovery_mode
If it's there, then it goes into recovery mode, if not, then it allows for a normal boot.
However, if doing normal boot, it actually places the /data/.recovery_mode file and then erases it once the system is fully booted. I know this is confusing, but this is how it knows to go back into recovery if you did a battery pull (ie, the file was created, but never erased since you didn't complete the boot process).
All of this is supposed to happen automagically, but I've heard of that file sometimes getting 'stuck' and not deleted. Thus, causing you to reboot into recovery every time.
There is nothing inside the file, just an empty marker. You may want to delete that file and reboot. Should help.
-Z
Click to expand...
Click to collapse
Ok I understand completely I knew the process but did not quite understand. Now the last question, is the only way to remove it to flash or can I use a file manager to remove it?
Oh and thanks for the help by the way.
UPDATE:
So I think I found it.
Unroot and Remove Recovery Via RootExplorer

jkpair said:
Ok I understand completely I knew the process but did not quite understand. Now the last question, is the only way to remove it to flash or can I use a file manager to remove it?
Click to expand...
Click to collapse
You can just delete it with a file manager (I am not sure about the permissions though .. you may need rootexplorer?)
I generally just do things like that from adb shell.
I KNOW I can delete it that way

Zaphod-Beeblebrox said:
You can just delete it with a file manager (I am not sure about the permissions though .. you may need rootexplorer?)
I generally just do things like that from adb shell.
I KNOW I can delete it that way
Click to expand...
Click to collapse
so for adb shell it would be something like:
Code:
adb shell
cd /system/bin
rm -r hijack
If thats right I won't try unless I know for sure. I don't know why but I have just got into a habit of googling after I ask. Lol I think this is it: Easy way to remove Koush's recovery?
So the logwrapper is the main file that matters not the hijack file and the original logwrapper was renamed to logwrapper.bin so I just replace Koush's recovery logwrapper with the previous one by copying over it.
Once again thanks for the help. Seems the answer is always 42.

jkpair said:
so for adb shell it would be something like:
Code:
adb shell
cd /system/bin
rm -r hijack
If thats right I won't try unless I know for sure. I don't know why but I have just got into a habit of googling after I ask. Lol I think this is it: Easy way to remove Koush's recovery?
So the logwrapper is the main file that matters not the hijack file and the original logwrapper was renamed to logwrapper.bin so I just replace Koush's recovery logwrapper with the previous one by copying over it.
Once again thanks for the help. Seems the answer is always 42.
Click to expand...
Click to collapse
I'm sorry, I misunderstood you goal here. I thought you wanted to keep the recovery, just fix it so it didn't come up on each reboot. If you are looking to completely remove the recovery, then I yes, I would follow the directions in the post you referenced, not the code section.
If you are only looking to 'fix' your reboot issues, I would suggest looking to see if /data/.recovery_mode exists on your phone. If it does, delete it. That's likely what is causing you to reboot into recovery each time.

Zaphod-Beeblebrox said:
I'm sorry, I misunderstood you goal here. I thought you wanted to keep the recovery, just fix it so it didn't come up on each reboot. If you are looking to completely remove the recovery, then I yes, I would follow the directions in the post you referenced, not the code section.
If you are only looking to 'fix' your reboot issues, I would suggest looking to see if /data/.recovery_mode exists on your phone. If it does, delete it. That's likely what is causing you to reboot into recovery each time.
Click to expand...
Click to collapse
Oh wow now I feel dumb. I thought I got it. So this would allow me to reboot and keep the recovery without it going into recovery every time I reboot. I hate asking noob questions lol

jkpair said:
Oh wow now I feel dumb. I thought I got it. So this would allow me to reboot and keep the recovery without it going into recovery every time I reboot. I hate asking noob questions lol
Click to expand...
Click to collapse
Assuming that is the problem. There may be another reason that you are getting dumped into recovery each time, but I suspect this is it. I will say that it's not 'normal' for recovery to come up each time. It should only come up if you somehow stop the boot process mid-way (Battery pull, etc) or use the Bootstrap recovery program to set it to reboot in recovery (which basically just creates the data file in question).
I would suggest you work through fixing this problem rather than just getting rid of the recovery. It's quite a powerful tool.

Zaphod-Beeblebrox said:
Assuming that is the problem. There may be another reason that you are getting dumped into recovery each time, but I suspect this is it. I will say that it's not 'normal' for recovery to come up each time. It should only come up if you somehow stop the boot process mid-way (Battery pull, etc) or use the Bootstrap recovery program to set it to reboot in recovery (which basically just creates the data file in question).
I would suggest you work through fixing this problem rather than just getting rid of the recovery. It's quite a powerful tool.
Click to expand...
Click to collapse
Yeah I really don't want to rid myself of it. I do believe I have an understanding now I am going to give it a shot when I can leave work. I will come back and post results.
Awesome It worked like a charm. Deleted the .recovery_mode file and am now happy.
Thanks for replying so quickly before I decided to just go ahead and remove the recovery menu all together.

jkpair said:
Yeah I really don't want to rid myself of it. I do believe I have an understanding now I am going to give it a shot when I can leave work. I will come back and post results.
Awesome It worked like a charm. Deleted the .recovery_mode file and am now happy.
Thanks for replying so quickly before I decided to just go ahead and remove the recovery menu all together.
Click to expand...
Click to collapse
Where is this file located? Im having the same problem.
Sent from my DROIDX using XDA App

DrewDanger said:
Where is this file located? Im having the same problem.
Sent from my DROIDX using XDA App
Click to expand...
Click to collapse
From my earlier post:
The recovery works by looking for a file : /data/.recovery_mode
If it's there, then it goes into recovery mode, if not, then it allows for a normal boot.
However, if doing normal boot, it actually places the /data/.recovery_mode file and then erases it once the system is fully booted. I know this is confusing, but this is how it knows to go back into recovery if you did a battery pull (ie, the file was created, but never erased since you didn't complete the boot process).
All of this is supposed to happen automagically, but I've heard of that file sometimes getting 'stuck' and not deleted. Thus, causing you to reboot into recovery every time.
There is nothing inside the file, just an empty marker. You may want to delete that file and reboot. Should help.
Click to expand...
Click to collapse

I went through Astro and searched "/data/.recovery_mode" but it didnt bring up that file. I guess Im just confused at what exactly Im supposed to be looking for...

Yeah I ended up using a root file manager to do this was really easy. Just go the root menu and browse to data find recovery_mode and delete then reboot.
Oh and astro will not show what is in the data folder you have to get a root explorer app I think the one I used was android mate.
Sent from my DROIDX using XDA App

Ok cool I'll check that out. When I use Astro and go under "system" and scroll down it has a "recovery from boot" folder. Any idea what that is? When I open it there is a bunch of code script in it

Ok I deleted that file and it fixed it. I think Im just gonna un-root it when I get off work. Im over all this, lol. I'll wait until the Droid has more development as far as root access and what you can do. Can I just do the un-root through the one -click-root I used?

DrewDanger said:
Ok I deleted that file and it fixed it. I think Im just gonna un-root it when I get off work. Im over all this, lol. I'll wait until the Droid has more development as far as root access and what you can do. Can I just do the un-root through the one -click-root I used?
Click to expand...
Click to collapse
Yeah it has an option to unroot, but I can't state whether or not this is the best method to remove the root. I acctually am keeping my root and bootloader. Yeah I will be glad when there is a true rom as well but progress is progress.

Anyone know how to....

Hey i was wondering if anyone knew how to change the Verizon Wireless text in the notification screen and lock screen on the Droid x!? Easy way??

MonoDraken said:
Hey i was wondering if anyone knew how to change the Verizon Wireless text in the notification screen and lock screen on the Droid x!? Easy way??
Click to expand...
Click to collapse
look here and on droidforums for modifying the eri.xml

HMmm let me look!

http://alldroid.org/default.aspx?g=posts&t=876

Thanks for that but i am wondering if there is a easier way?..

MonoDraken said:
Thanks for that but i am wondering if there is a easier way?..
Click to expand...
Click to collapse
Pay me to do it for you

Haha i would but dont have credit card or anything like that lol...
and parents wont let me use there... -.-'

MonoDraken said:
Thanks for that but i am wondering if there is a easier way?..
Click to expand...
Click to collapse
Its actually quite easy. Takes like 5 minutes.

I'm like a noon at these things :/
Sent from my DROIDX using Tapatalk

It's really not that hard and the feeling of accomplishment you will get by doing it yourself will be worth it.
Just do it.

Just used this method and it was super easy! Got rid of that stupid VZW name and replaced it with something cool. Thanks a bunch!!

Dont really wanna mess up my phone so lol.

MonoDraken said:
Hey i was wondering if anyone knew how to change the Verizon Wireless text in the notification screen and lock screen on the Droid x!? Easy way??
Click to expand...
Click to collapse
Casen said:
http://alldroid.org/default.aspx?g=posts&t=876
Click to expand...
Click to collapse
Wanted to thank MD for starting the thread and Casen for the lnk. Very cool. I now have "android droidX".
MD- how far have you got? Try downloading the android sdk and you can start experimenting with ADB (android debug bridge). If you just google "android sdk" you can go right to google's site and they have instructions there. Or maybe you have all ready messed around with ADB?
anyways, cheers for the good question.

Thanks and idk im trying to look for a easier way first. Theres a app out there it just doesnt support DX yet.

Whenever I push my changed apk back to my system I lose all of my contacts. What's up?

zehkaiser said:
Whenever I push my changed apk back to my system I lose all of my contacts. What's up?
Click to expand...
Click to collapse
I had that same problem originally. Did you follow the directions on the link exactly? If you push the framework-res.apk back to the phone while it is running "normally"- that is what happens (or it happened to me at least).
But when I booted into recovery, mounted system (it will actually read unmount when it is mounted) and then pushed the apk- I didn't have that problem.
I am not sure if that was the only step that made the difference- but is the only one I can think of.

thepolishguy said:
I had that same problem originally. Did you follow the directions on the link exactly? If you push the framework-res.apk back to the phone while it is running "normally"- that is what happens (or it happened to me at least).
But when I booted into recovery, mounted system (it will actually read unmount when it is mounted) and then pushed the apk- I didn't have that problem.
I am not sure if that was the only step that made the difference- but is the only one I can think of.
Click to expand...
Click to collapse
Thanks. I couldn't get my system to recognize the phone while in recovery. I ended up mounting the system while the phone was in Media Sync Mode, issuing the "stop" command, replacing the files and rebooting. Worked like a charm. :-D

zehkaiser said:
Thanks. I couldn't get my system to recognize the phone while in recovery. I ended up mounting the system while the phone was in Media Sync Mode, issuing the "stop" command, replacing the files and rebooting. Worked like a charm. :-D
Click to expand...
Click to collapse
That sounds easier. I am no ADB wizard. Could you type it out for me?
Code:
mount -o remount,rw -t yaffs2 /dev/block/mtdblock4 /system
etc.
Or whatever commands you issued?
Thanks.

It's much easier to use Android Terminal Emulator on the phone instead of the cable/ADB method.

dave8311 said:
It's much easier to use Android Terminal Emulator on the phone instead of the cable/ADB method.
Click to expand...
Click to collapse
A couple of things...
1. This is in no way meant as a "come back". Just my view.
2. Whether it is easier to use terminal or not - I still need the commands.
3. And for me it is easier to use a full size key board. The USB cable is less of a hassle to me then the mini touch screen keyboard.
Again- that's just me.

I need help with roms

I cannot flash roms or kernel. It won't boot recovery!!! I have stock rooted shift. How do I make a custom recovery? And install roms and kernel

Probably the easiest way is to download ROM manager from the market. The first option in the app is flash clockworkmod. Very fast and automagic. Have fun! Happy flashing.

I have that and kernel manager. Flashed it twice after it didn't work the first time. It hangs up on the HTC boot logo after I try to boot recovery

turn off your phone
power it on while holding vol down.
does the first line say S-OFF or S-ON?

S on I didn't do nand

I've tried a few more things. I used visionary to root my phone. Was that the wrong thing? It all works. But I can't flash. Lol

thronnos said:
I've tried a few more things. I used visionary to root my phone. Was that the wrong thing? It all works. But I can't flash. Lol
Click to expand...
Click to collapse
That's just a temp root. Go into the development section and use the GUI Root and recovery tool...worked for me.
Sent from my PG06100 using XDA App

Alright, is there a way to do this without a computer

thronnos said:
Alright, is there a way to do this without a computer
Click to expand...
Click to collapse
Yeah if you want you can use terminal emulator on your phone just open it up hit su get your super user permissions then start the commands the first time I rooted I did it using adb the second time I rooted I lost my adb and just chrome to phoned all the codes from my pc to root it from my phone
Sent from my PG06100 using Tapatalk

Alright!! Thank you all who have been helping. I have only a few more questions because I'm a little slow ^_^ ok, first. From the emulator I typed Su and gave permission.... now what? I looked for the commands in development and couldn't find. I'm trying to turn s off. I don't care so much about perm or temp root right now as long as I get that annoying s on to be s off. Lmao. I need commands please!!! Assume I have no access to a computer!

Check out the development subforum. It's a sticky thread by bcnice20.
i dont need a signature

Alright I have that, now its not explained there but in order to do that via the terminal do I need to dl the framework and sdk to my phone? I do not have a running computer right now. I had a crap amd system which is officially dead. It's now all spare parts. So doing the shell on a computer isn't going to work for me :/ yes, I'm difficult. Lol

thronnos said:
Alright I have that, now its not explained there but in order to do that via the terminal do I need to dl the framework and sdk to my phone? I do not have a running computer right now. I had a crap amd system which is officially dead. It's now all spare parts. So doing the shell on a computer isn't going to work for me :/ yes, I'm difficult. Lol
Click to expand...
Click to collapse
if you search that thread, there should be an answer.

thronnos said:
Alright I have that, now its not explained there but in order to do that via the terminal do I need to dl the framework and sdk to my phone? I do not have a running computer right now. I had a crap amd system which is officially dead. It's now all spare parts. So doing the shell on a computer isn't going to work for me :/ yes, I'm difficult. Lol
Click to expand...
Click to collapse
the commands given in that thread is the exact ones you would need, but since you're using a terminal emulator in your phone, you don't need adb.
do step 1
skip step 2
do step 3,4,5 via your terminal
do step 6
extra points:
once you're perma-rooted, you can go straight to installing Rom Manager, and flash clockworkrom that way.
then reboot your phone to recovery, and do a nandroid backup.
once that's done, you're all set.

Thank you dude!!!!!!! That rocks!!! I'm at work and I'm doing it right now. This is way more important than work ^_^ anyone else addicted to Android?

thronnos said:
Thank you dude!!!!!!! That rocks!!! I'm at work and I'm doing it right now. This is way more important than work ^_^ anyone else addicted to Android?
Click to expand...
Click to collapse
+1
When the perm root method was finally developed I was at work with no access to a PC. I ended up rooting via phone terminal just because I couldn't bear to wait a couple hours until I got home.
^ Shift Faced

Could someone explain step 1 and 3 for me if I'm using android terminal emulator. I tried it but nothing happened. My device is temprooted. I download the file into the download folder. I use root explorer to extract it... where?? I tried a couple places even the root folder (Its not in SD card) then once its good how do I check the md5 from the terminal. I type Su to get permission then what? The string in the post doesn't seem to do anything no matter how I type it. Or maybe I just don't know the command. I'm fairly new to this kinda thing. :/

That's awesome. I'm feeling the same way. I don't want to wait for a computer it might be a few weeks I'm impatient now lol

Wait, I got part of it. I just need to know how to save the file to the root of the SD card and then how to check the md5sum. Once I know that I'm good to go
Sent from my PG06100 using XDA App

thronnos said:
Wait, I got part of it. I just need to know how to save the file to the root of the SD card and then how to check the md5sum. Once I know that I'm good to go
Sent from my PG06100 using XDA App
Click to expand...
Click to collapse
Download root explorer and long press the file in your download folder, then back out to your sd card directory and select move. You should be able to check mdsum5 in the term app using the commands given
Sent from my PG06100 using XDA Premium App

How to replace one file when failing to boot

Hey guys
I screwed up my vold.fstab trying to get "_ExternalSD" back.
Unfortunately! I did not run a nandroid before I made the change.
Now, I can dirty flash my rom on top, or go back to a nandroid from a few days ago, but I'd really just like to recover and go on my merry way. And maybe learn something in the process.
Only thing is, I can't figure out how to access the phone other than the External SD card through CWM.
Can I mount the internal /system and access through USB? Is there some facility to copy a file from one point to another? Any other methods? I guess the phone has to be up to run ADB, right?
I don't know how to generate a flashable zip but I could extract the original version of the file from the original rom. I assume that its non trivial to create a flashable zip, but maybe someone can comment? It looks like there is signing and certificates involved..
thanks for any ideas

bluenote73 said:
Hey guys
I screwed up my vold.fstab trying to get "_ExternalSD" back.
Unfortunately! I did not run a nandroid before I made the change.
Now, I can dirty flash my rom on top, or go back to a nandroid from a few days ago, but I'd really just like to recover and go on my merry way. And maybe learn something in the process.
Only thing is, I can't figure out how to access the phone other than the External SD card through CWM.
Can I mount the internal /system and access through USB? Is there some facility to copy a file from one point to another? Any other methods? I guess the phone has to be up to run ADB, right?
I don't know how to generate a flashable zip but I could extract the original version of the file from the original rom. I assume that its non trivial to create a flashable zip, but maybe someone can comment? It looks like there is signing and certificates involved..
thanks for any ideas
Click to expand...
Click to collapse
this is why i hate it when people make those guides.
messing with the vold.fstab is dangerous (even though its only a few lines) if your trying to recover your data, give up. its not going to happen. (sorry)
when you edit the vold.fstab it messed up the partitions on your internal SD card and most likely did the equivalent of wiped your /system partition. (or another important one.) your actually lucky it did not completely brick your phone.
your post was a little vague, but if you can, just restore an older nandroid, or wipe everything and install another ROM. (you can try dirty flashing but i dont think itll work)
if you cannot access CWM, then follow the steps in This guide. it should get you back up on your feet. after you follow that guide flash a gingerbread ROM (any gingerbread rom will do fine) then you can reboot and flash any ROM you want. (it needs this to fix a quirk in that script)
Hope you get it fixed
EDIT: re read your post, if your feeling adventurous and want to give it a shot, boot into CWM and connect it via usb. you can now get into an ADB shell on your phone by typing 'adb shell' if you have adb all setup and working. (im working from memory here so dont quote me on any of this)
now, you should be able to access your /system folder from that shell. be very careful though, i dont have much experience right here, and if i remember correctly you might not be in the full root directory yet)
if you can get into it try replacing your vold.fstab with a stock one,
if you dont have a stock one lying around, make a nandroid of the current state of the rom, then flash another rom, pull the vold.fstab, then re-restore back to the broken one and restore it (id upload mine but my phone is OOC right now )
after that just reboot and hope it resolves itself, if not then just follow my advice above
and keep that guide i linked to handy, messing around in CWM has the ability to brick your phone, if it does, then just follow that guide.

Klathmon said:
this is why i hate it when people make those guides.
messing with the vold.fstab is dangerous (even though its only a few lines) if your trying to recover your data, give up. its not going to happen. (sorry)
when you edit the vold.fstab it messed up the partitions on your internal SD card and most likely did the equivalent of wiped your /system partition. (or another important one.) your actually lucky it did not completely brick your phone.
your post was a little vague, but if you can, just restore an older nandroid, or wipe everything and install another ROM.
if you cannot access CWM, then follow the steps in This guide. it should get you back up on your feet. after you follow that guide flash a gingerbread ROM (any gingerbread rom will do fine) then you can reboot and flash any ROM you want. (it needs this to fix a quirk in that script)
Hope you get it fixed
Click to expand...
Click to collapse
How bout adb and pushing the file back in? Or cant you access the phone via adb?
Sent from my LG-P970 using XDA

N00BY0815 said:
How bout adb and pushing the file back in? Or cant you access the phone via adb?
Sent from my LG-P970 using XDA
Click to expand...
Click to collapse
re read your post and updated my last post right after you posted
after dealing with noobies all day, i forget sometimes people want to try big things

Thanks guys. The info I was missing was there's no special trick to attaching adb while in CWM! Just plug in!
My phone is back up and running and partitions are fine as far as I can see after just booting up.

Hi there! I messed up with the vold.fstab filfe on my tablet – I replaced it with a downloaded file with the intention to transfer apps to my external SD card.
Now my tablet is only showing the startup logo and won’t continue loading. I can access recovery mode. Now I want to restore the original vold.fstab file.
My questions:
1. Using the Android SDK, the file explorer does not show any files, though my tablet is recognized.
2. Using adb push, it yields an error: permission denied, how to successfully push the original vold.fstab and replace the existing vold.fstab?
3. If I dump an image of my tablet and edit the dumped image, would this be easier compared to the steps above?
Thanks!

http://forum.xda-developers.com/showthread.php?t=1646108
Try this.
If this doesn't help you should ask in the section for your tablet to get more specific advice.

TwitchyEye said:
http://forum.xda-developers.com/showthread.php?t=1646108
Try this.
If this doesn't help you should ask in the section for your tablet to get more specific advice.
Click to expand...
Click to collapse
Thanks, I will try it later when I got home. My tablet is not found here. I have a Skyworth S71(3G) with RK3066 chipset.

BryanF said:
Thanks, I will try it later when I got home. My tablet is not found here. I have a Skyworth S71(3G) with RK3066 chipset.
Click to expand...
Click to collapse
You need to do an adb remount before you can push. Was it rooted before?
-- The noob says:
This just in... my IQ has increased 50 points thanks to the g2x!

Mansa_noob, yes, my tablet is rooted. I followed some instructions about adb but had an error saying access denied, and also no files are displayed at file explorer. See my posts above. I also mounted it successfully. I will post some sreenshots later.
Please if you have some instructions, I am willing to try.
---------- Post added at 07:06 AM ---------- Previous post was at 07:02 AM ----------
TwitchyEye said:
http://forum.xda-developers.com/showthread.php?t=1646108
Try this.
If this doesn't help you should ask in the section for your tablet to get more specific advice.
Click to expand...
Click to collapse
Hi twitchyEye, it did not work. It attemps to install (using the install update from ext sd card) but then says installation aborted.
Any more suggestions? Thanks

What recovery are you using? I suck with adb so I got nothing on that front.

It was the stock recovery from my Tablet. I don't have it on hand right now, I will post later. The chipset is RK3066. My problem is my tablet has no official support on the internet (maybe becaue it's still new). Model is Skyworth S71(3G).

I see. Yeah this is over my head man. I thought for sure you were running a custom recovery and it was an easy answer. I'm actually struggling right now with adb myself with a similar issue something about permissions whenever I try to do anything to my phone. So I guess right now would be a perfect time for somebody to chime in with a smarter answer!

TwitchyEye said:
I see. Yeah this is over my head man. I thought for sure you were running a custom recovery and it was an easy answer. I'm actually struggling right now with adb myself with a similar issue something about permissions whenever I try to do anything to my phone. So I guess right now would be a perfect time for somebody to chime in with a smarter answer!
Click to expand...
Click to collapse
Are you doing adb remount and still getting permission denied?
-- The noob says:
This just in... my IQ has increased 50 points thanks to the g2x!

mansa_noob said:
Are you doing adb remount and still getting permission denied?
-- The noob says:
This just in... my IQ has increased 50 points thanks to the g2x!
Click to expand...
Click to collapse
Yes, I did adb remount and still access denied

BryanF said:
Yes, I did adb remount and still access denied
Click to expand...
Click to collapse
This is strange. A properly rooted phone would adb remount to r/w system. Something is fishy. Is it rooted+
-- The noob says:
This just in... my IQ has increased 50 points thanks to the g2x!

mansa_noob said:
This is strange. A properly rooted phone would adb remount to r/w system. Something is fishy. Is it rooted+
-- The noob says:
This just in... my IQ has increased 50 points thanks to the g2x!
Click to expand...
Click to collapse
I am sure it is rooted, because I downloaded an application from Google play to check it it is rooted or not. It is really rooted. I alvo confirmed this as I can now fully backup and restore my apps using Titanium backup before the tablet is messed up.

BryanF said:
I am sure it is rooted, because I downloaded an application from Google play to check it it is rooted or not. It is really rooted. I alvo confirmed this as I can now fully backup and restore my apps using Titanium backup before the tablet is messed up.
Click to expand...
Click to collapse
OK. Odd or not, it is what it is. Is it possible for you to load a custom recovery?
-- The noob says:
This just in... my IQ has increased 50 points thanks to the g2x!

mansa_noob said:
OK. Odd or not, it is what it is. Is it possible for you to load a custom recovery?
-- The noob says:
This just in... my IQ has increased 50 points thanks to the g2x!
Click to expand...
Click to collapse
I want to try, but the stock recovery is my last hold as I have no stock ROM. If I overwrite the stock ROM, I cannot reinstall it as I don't have a copy of it.

So why not flash cwm with nvflash and then make a backup of your current stock rom? I did exactly that.
Sent from my LG-P999 using xda premium

A problem with ADB...

I tried installing the 1.4.3 ADB/Fastboot program on all three of my computers... It transfers 0 files and flashes some error message from CMD use... Anyone know why Win 7 pro shouldn't take the Install..?? I even used ADMIN to do it... Nothing... I'd love to just see if my new Chinese tablet has a bootloader or not...
Anyone..?

lentmain said:
I tried installing the 1.4.3 ADB/Fastboot program on all three of my computers... It transfers 0 files and flashes some error message from CMD use... Anyone know why Win 7 pro shouldn't take the Install..?? I even used ADMIN to do it... Nothing... I'd love to just see if my new Chinese tablet has a bootloader or not...
Anyone..?
Click to expand...
Click to collapse
How are you installing it? With a program or something? Here I'll just share mine with you.
https://drive.google.com/file/d/0B3XczzpnAnvwdlFvYURXMl8tbUk/view?usp=drivesdk
This has more than adb and fastboot, but all you have to do is extract all of these files into a folder somewhere. Then open the folder, hold SHIFT, and right click. Then select Open CMD Window Here. Then you're all set. (The apktool and smali/baksmali stuff are different tools for editing .apk files. You probably won't need them, but if you do.... already got 'em. Also, the instructions text file is for apktool. I use the same zip to help people edit apps.)
Sent from my KYOCERA-C6745 using Tapatalk

RealWelder said:
How are you installing it? With a program or something? Here I'll just share mine with you.
https://drive.google.com/file/d/0B3XczzpnAnvwdlFvYURXMl8tbUk/view?usp=drivesdk
This has more than adb and fastboot, but all you have to do is extract all of these files into a folder somewhere. Then open the folder, hold SHIFT, and right click. Then select Open CMD Window Here. Then you're all set. (The apktool and smali/baksmali stuff are different tools for editing .apk files. You probably won't need them, but if you do.... already got 'em. Also, the instructions text file is for apktool. I use the same zip to help people edit apps.)
Sent from my KYOCERA-C6745 using Tapatalk
Click to expand...
Click to collapse
I used three different exe programs... the xda one from the forum... And two others from the internet... i checked each with my norton..., then disabl;ed the anti-virus..., then it loaded fine... wouldn't deposit the four files it was supposed to have.... Thanks for your files... I'll try it next... thanks.... lentmain

RealWelder said:
How are you installing it? With a program or something? Here I'll just share mine with you.
https://drive.google.com/file/d/0B3XczzpnAnvwdlFvYURXMl8tbUk/view?usp=drivesdk
This has more than adb and fastboot, but all you have to do is extract all of these files into a folder somewhere. Then open the folder, hold SHIFT, and right click. Then select Open CMD Window Here. Then you're all set. (The apktool and smali/baksmali stuff are different tools for editing .apk files. You probably won't need them, but if you do.... already got 'em. Also, the instructions text file is for apktool. I use the same zip to help people edit apps.)
Sent from my KYOCERA-C6745 using Tapatalk
Click to expand...
Click to collapse
Real welder..., May I ask you a question..? Can you tell me how to find out if I have a bootloader and how to find out... I thank you again for your software... It worked wonders.... But the tablet still refuses to tell me more than what was on the scatter txt page...
I started reading the Beginners pages.., as recommended by another guy.... I downloaded the SDK BIG program... Along with the other programs that help it out...
I'm still not sure how to hook up my Chinese tablet to the SDK program and see what is inside...
Thanks ahead of time...,
lentmain
Do you know of a helper page to show me what to do..? Any help is greatly appreciated.....

It varies from device to device, some companies have disabled fastboot. Typically though, when powering it on if you hold vol+ it will go to recovery and vol- will go to bootloader, but not always. On a Coolpad device I have, I had to boot to recovery then it'll say No Command. Hold power and tap vol+ to bring up the menu. Then one of the menu options was reboot to bootloader.
Sent from my KYOCERA-C6745 using Tapatalk

RealWelder said:
It varies from device to device, some companies have disabled fastboot. Typically though, when powering it on if you hold vol+ it will go to recovery and vol- will go to bootloader, but not always. On a Coolpad device I have, I had to boot to recovery then it'll say No Command. Hold power and tap vol+ to bring up the menu. Then one of the menu options was reboot to bootloader.
Sent from my KYOCERA-C6745 using Tapatalk
Click to expand...
Click to collapse
Tell me..., if you know..., I just Rooted my Tablet.... Does that mean it doesn't have a locked bootloader..???? I still can't find anyone who is working on these Chinese MTK tablets...
Thanks,
lentmain

lentmain said:
Tell me..., if you know..., I just Rooted my Tablet.... Does that mean it doesn't have a locked bootloader..???? I still can't find anyone who is working on these Chinese MTK tablets...
Thanks,
lentmain
Click to expand...
Click to collapse
Not necessarily, what version of Android is it running? On KK you can root even if the bootloader is locked. Anything newer than that though, would most likely have to be unlocked first.
Sent from my KYOCERA-C6745 using Tapatalk

RealWelder said:
Not necessarily, what version of Android is it running? On KK you can root even if the bootloader is locked. Anything newer than that though, would most likely have to be unlocked first.
Sent from my KYOCERA-C6745 using Tapatalk
Click to expand...
Click to collapse
It says it's running 6.0 Marshmallow... I can see a eMMc partition on the scatter txt..., I can see lots of flashing write up but I have tried two and they both failed...
Oh well...

lentmain said:
It says it's running 6.0 Marshmallow... I can see a eMMc partition on the scatter txt..., I can see lots of flashing write up but I have tried two and they both failed...
Oh well...
Click to expand...
Click to collapse
Have you tried adb reboot-bootloader command?
Sent from my KYOCERA-C6745 using Tapatalk

RealWelder said:
Have you tried adb reboot-bootloader command?
Sent from my KYOCERA-C6745 using Tapatalk
Click to expand...
Click to collapse
It makes the tablet screen turn black and returns : * daemon not running; starting now at tcp 5037
* daemon started successfully
I'll put it in bootloader then try it again.......
lentmain

lentmain said:
It makes the tablet screen turn black and returns : * daemon not running; starting now at tcp 5037
* daemon started successfully
I'll put it in bootloader then try it again.......
lentmain
Click to expand...
Click to collapse
Tried it again with the tablet in BOOTLOADER mode...
When you push volup then power..., it goes intoa three way choice... Recovery, Bootloader ans Normal... Recovery seems to put you into the routine recovery you see on cell phone... sideload in ADB, and such...
Fastbooat seems to accept some ADB and fastboot commands...( I don't know them all..)
normal does nothing... I have to hit reset pinholr on all three to get out of them... escape doesn't seem to work...