Related
Ok, after messing around with 3.2 I decided to fix the rooting issues without downgrading. The problem with downgrading is it requires a SDCard and requires you to install a couple of programs and then to install an update.zip from the sdcard. I could not get half my ACER's to read and mount a sdcard, and some ACER's I have located in a remote office and trying to walk someone through the process was too painful. I tweaked the the downgrade tool's images to install 3.2 with root instead of downgrading it and jumping through hoops. All I did to the stock image is to copy the ash shell over to /system/xbin/su and set the sticky bit. Everything else is stock.
Update posted here, read thead http://forum.xda-developers.com/showpost.php?p=20654298&postcount=129
New version V4
-- The instructions are in a PDF document inside the download --
== Version V4 ==
-- Added /system/subin/su which is a backup (backdoor) root in case an OTA deletes the /system/xbin/su
-- Set permissons on the su root(#) tool so OTA's shouldn't be able to break it.
-- Added drivers for XP
Summary:
Version V4 is the same as V3 with the only difference being that there is a NEW backdoor script which has some additional features to protect root(#) from getting broken when you do an OTA. I also applied these to this flash image so you wouldn't have to add the additional protection yourself. V4 also has the drivers for XP included. However, when taking an OTA you should also install the backdoor for additional protection. However, you cannot leave the backdoor installed as it turns off sound. So having a little more protection just might save your root in case you take an OTA and forget to install the backdoor.
Download it here: http://www.multiupload.com/NS0X5TK4D1
Alternative download location:
http://depositfiles.com/files/c6pr69ri6
http://www.fileserve.com/file/s2wCQpN/root-3.2.1-V4.7z
http://www.filesonic.com/file/jTA7AMN
http://www.filejungle.com/f/vRnfK5/root-3.2.1-V4.7z
Which 3.2 update is it ? Fully working, no issues ? Good job. Is it power + volume down or volume up to go into recovery ? And is it possible to flash a custom kernel like Honeyvillain on this stock ROM ?
Thx
Has anybody ( including OP) tried this method?
It is the 3.2 OTA for WiFi that my Tablet picked up. It is total stock other than making a SU from the ash shell and putting it into /system/xbin.
Fully works, no issues, have used it on 8 ACER 500's with no issues.
To enter recover it is the left side of the volume button which is volume (-) oopps NOT (+) as I indicated.
Hah, saying Vol +/- is not intuitive on this device since when in landscape, Vol + is the "right" side, but in portrait mode Vol + is the "top" side.
no go
Hi, i can see my iconia uid from adb ( already installed in my pc) but
not from test.cmd, in the extracted package. Any ideas?
REPEATED STEPS 1-4 ( PER INSTRUCTIONS) ON 2 PC'S RUNNING W XP. SO FAR "NO GO" TEST.CMD CANNOT FIND PATH.... AND DOTNETDETECTER, THEREFORE, DOES NOT WORK.
will this wipe all the data on the tablet?
---------- Post added at 04:19 PM ---------- Previous post was at 03:40 PM ----------
JUGOMAN said:
Hi, i can see my iconia uid from adb ( already installed in my pc) but
not from test.cmd, in the extracted package. Any ideas?
Click to expand...
Click to collapse
same here i run the setup file and it installs but after i run test.cmd and it cant find it
Sorry about the test.cmd not working. The script just calls adb.exe to make sure it is working and I have it installed in another directory that I did not include. I posted, to the original message an attachment, it is called fix-Test.7z that fixes the test.cmd. You should be able to just unzip it into the directory you created and run the test. The archive includes the adb.exe and dll's so the test.cmd should work. If you have adb.exe working you really don't the test.cmd, but I found out when talking someone through it (over the phone) this made sure that adb.exe was installed and they had the tablet USB Debugging turned on.
And it is a quick and easy way to get the serial number which you need to flash it.
Thanks,
Let me know if you have any more issues.
does anyone know if flashing it this way will delete all your data on the tablet?
NO GO2
The attchment does fix the test.cmd "problem" but the next step, Dotnetdetecter, does not work. It re-installs the driver (?) then error "adb is old" or something like that. All packages in my computer's ADB are up to date. I think that the "target" directory in the DONETDETECTER IS NOT CORRECT. ANY IDEAS? btw GOOD WORK!!!!!
Many thanks for this. It is really easy like this. Keep up the great work.
UPDATE
Installed, booted, but no root. Previous rom( acer update) was3.2 Gen 2, now 3.2 Gen 1. was worth a try.. Thank you... tablet is working just fine, just no root
jimmkd84 said:
does anyone know if flashing it this way will delete all your data on the tablet?
Click to expand...
Click to collapse
Yea. I've never done this before so I'm wondering the same thing.
Also
Idk about this test thing but if u type 'adb devices' it'll show you which devices (if any) are connected. I always use that as a test when i use the adb to install apks.
bad adb
NO GO2 WROTE
The attchment does fix the test.cmd "problem" but the next step, Dotnetdetecter, does not work. It re-installs the driver (?) then error "adb is old" or something like that. All packages in my computer's ADB are up to date. I think that the "target" directory in the DONETDETECTER IS NOT CORRECT. ANY IDEAS? btw GOOD WORK!!!!!
Not sure what that would be. I just use the adb.exe and dlls that are in the fix.zip. Maybe you have a different version loaded?
ROOT IS NOT in the apps. It is in the adb shell.
What this does is allows you to connect to the device using adb.exe shell and you will get the $ prompt.
at the $ prompt type su and press enter. You will get # and be in su mode.
Now you can do whatever you would like. What would that be, you might ask? Well you could do the following:
1. mount system as rw
2. Push your favorite su tools to the device so they are listed in the apps (busybox etc).
Again this gets you to 3.2 with the ability to have a SU when connected via the adb shell. I left the building of the tools and custom CW to you guys to do as you wish. Here's something else you could do.
1. Shell to it, and issue the SU
2. Mount system as rw
3. Push your favorite tools to where you want (busybox etc)
4. Take the recovery.img (in the zip) and dd dump it to the recovery partition. This will put clockwork on the device (1.5).
a. You should probably run itsmagic too.
5. Get everything the way you want it.
6. Reboot to recovery and CW will load.
7. Now with CW 1.5 loaded, you can build and make copies of your ACER and make them available to anyone you like. CW 1.5 does NOT require an external SDCARD.
Sorry, if I did not make it clear that this is just a SU that you have to use from the command line. If someone wants to give me the links to a SU apk, busybox, etc they'd like included I'd do it. It would only take a few minutes as I got hundreds of these ACER's to flash for our company. I just wanted to get SU, but what the heck, I could build it out if someone would like it that way. ACER really pee'd me off with this, and guess what? They left the ability to gain root in the 3.2 100. Why the 'Sam Heck' did they change the 500 3.2 so you cannot get root?
So, anything I can do to help let me know. Also, If you never want ACER to send you another update I can tell you how to fix that too. All you have to do is the following:
1. Get to the adb shell $
2. type su to get the # prompt
3. Now mount system as rw by doing the following:
a. mount -t rfs -o remount,rw system /system
4. Now rename the update tool by doing the following:
a. mv /system/app/FDUpdater.apk /system/app/FDUpdater.apk.old
mv /system/app/FWupdateService.apk /system/app/FWupdateService.apk.old
5. To get OTA then just reverse the process if you ever want ACER and their OTA to break your fleet of ACER Tablets by pushing silly updates that they think you want then you can undo it. The last I knew, I owned these ACER Tablets and I don't take kindly to them changing something that I do NOT WANT CHANGED. They should be sued, matter of fact, I think they are violating federal laws by destroying data on MY tablets. Anyway, off my soapbox.
i have re run the new test.cmd and is working now, and have successfully run dotnetdetector but i dont want to proceed until someone can confirm if doing this will wipe all data on the tablet
appreciate it, great work btw dev!
---------- Post added at 05:05 PM ---------- Previous post was at 04:39 PM ----------
did this wipe the data on it?
Hello, may i use this procedure on my A501?
Thanks
I did NOT test on the 501 so I do not know. If it was me, I would take the 501 stock images and put them in the kitchen and root them and then replace the ones in my zip with those or better yet, use CW to flash it in.
I think the ACER 501 has cell phone data connection doesn't it? I don't think the stock for WiFi only would be a good idea.
What ACER did on the 3.2 update (my opinion) was removed the Gingerbreak exploit and they removed the adb root exploit (they left the adb root exploit in on the 100). This is what many OEM's did, however many allow you to flash your own easier than ACER seems to want to let us. So if you got 3.2 NON-ROOTED loaded then there is no way to 'hack' out a root (just yet).
So how do you root it? You have to make a custom ROM and flash it. Now ASUS/Motorola/Samsung/Toshiba all allow you to flash your own ROM if you know what you are doing.
ACER seems to hide how to put the tablet into flash mode (if someone knows please let me know). Even if you did flash it they do want those ROMS running so they take each partition and calculate the MD5Sum and write it to, I think, partition #7. Therefore, if you do figure out how to flash in a new boot image or system image the tablet will not boot because the MD5Sums will not match (if you brick your tablet this way you are fubar). Fortunately, someone wrote a tool called itsmagic which you can run to tell the tablet to rebuild these. But if you fubar brick it before you get itsmagic run, I don't know how you get into flash mode using the keys so you'd be up a creek.
So, the 411 skinny on rooting an ACER with 3.2 is to get 3.2 off the device. Fortunately, they made an earlier flashing tool to flash in 3.0. I would guess this leaked out as a way for people to reflash to stock when they have issues.
Once you are on 3.0, you now can use Gingerbreak or the adb root exploit to root it. Once rooted, you can get CW loaded. CW allows you to install your own ROM's. Without CW you can only install ROM's signed by ACER and without ROOT you cannot install CW.
So, if you flash to the 3.0 now you are 'back to the future' in 3.0, you can root and install CW so you can now install a custom ROM from your SDCard.
What I would do is go get the STOCK ROM from ACER for your 501 device.
Once you have the stock ROM, you can use the kitchen tools to unzip the ACER ROM and root it to your liking. Now, re-zip it, but you cannot sign it with an ACER certificate so it will only install using CW. No, big deal because you got 3.0 loaded with CW. You boot to recovery CW and then run the update from your SDCard that you built in your kitchen.
This isn't really that hard to do if you're willing to read some documentation.
I have no idea if it wipes it clean totally. It does walk you through the setup again (like it was new out of the box) so I would assume most things would be wiped. I would back it up and not take the chance because it is best to be backed up.
Just a note here. It says fully stock execpt root? i don't think that's entirely accurate. I believe that it's still downgrading the bootloader, otherwise you'd never be able to get CWM to run, as itsmagic doesn't work with the new bootloader. So your left with stock 3.2 ROM with adb/su abilities and pre 3.2 bootloader.
On another note, I believe step 17 is not needed. CWM run's itsmagic automatically on every boot. So just booting CWM and then rebooting to android should suffice.
EDIT:
Now you can follow the same process into rogro82's kernel, thanks to Forzaferrarileo. Note that you can just flash the kernel, if you already put it to work with sp3dev's kernel. There's no need to repeat all process.
I've, also, changed some structures for better visualization.
This tutorial is using the sp3dev's precompiled kernel from here or rogro82's precompiled kernel from here. If you want to use rogro82's from scratch or from internal storage, please look, also, some instructions at here. Please note that you will have to build that kernel from sources before proceed. You should be able to use internal storage also, with some changes into this tutorial.
I used a phisical usb keyboard into this tutorial, but bodhi offers an onscreen keyboard into tablet profile. To change into this profile, look at here.
It's partially based into this tutorial. I'll refer to number of steps on that, so please open it. Please read everything before doing anything, and make sure you have no doubts about the process before doing anything. I'm not responsable if it damages your tablet!
First of all, download the Bodhi rootfs from here.
Then, run the first 3 steps from the tutorial above. Please note that if you'll run the rogro82's kernel, the step 2 should be flashing that kernel. For infos about how to flash the second kernel image, please read this thread's first post.
After, extract the Bodhi rootfs into the ext4 partition from your sdcard (I needed to be logged as root or use sudo for doing this step). Make sure to extract directly into the root of the partition (the result of a ls into the root of the partition should be just like running ls /).
Now, you need to donwload the zip file from step 6 from the tutorial. Note that it's not needed to install the packages asked by the step 6, just extract the donwloaded files and copy them into your sdcard's /lib/firmware folder. I just copied the brcm folder into /lib/firmware/brcm and it worked.
Now you are able to boot into the image. Put sdcard into the tablet and then boot from second kernel (hold VOL UP while powering on until it shows bootmenu and select boot into second kernel).
After complete booting, you should have the E17 home screen. For tutorials about this interface, please look into Bodhi website.
For being able to connect into wifi, I needed to open terminology (terminal application into bodhi) and run, as root, the following. Please note that it may not be necessary, but recommended:
- rfkill unblock all
- ifconfig
Now please see what number your wifi got loaded, for me, it was wlan2. I'll call it wlanx, so just change x for the number you got.
- ifconfig wlanx up
To make sure it worked, run "iwlist wlanx scan". It should bring some network details into terminology.
Now open wicd, open preferences and make sure the wifi network is correctly set into wlanx. The default value is wlan0. Then, close preferences and click into reload. Now you should be able to select your network, set up the network preferences and then connect into it.
Now you should be able to install everything you want. As I read, bodhi uses a debian base for armhf version, so you can install anything you can install from debian. Chromium web browser is broken, and firefox is named iceweasel. The default midori web browser works fine, but I personally prefer iceweasel.
Thanks:
sp3dev, rogro82, Kevin Roscom, Forzaferrarileo (if I forgot someone, please tell me, I'll put your name here!)
i'd love to try this! does this run fairly well?:good:
For me it does. I have a class 10 sdcard.
guimendes said:
For me it does. I have a class 10 sdcard.
Click to expand...
Click to collapse
root password?
Tautvaldas said:
root password?
Click to expand...
Click to collapse
Please take a look at here: http://jeffhoogland.blogspot.nl/2012/12/bodhi-linux-armhf-rootfs.html
You can use sudo bash to root access. The password is bodhilinux. Then you can set root password.
Hey this is my first time installing linux on a tablet. Ive got the partitioned sd card, rootfs, kernel ready to go. just not famaliar with how to flash the kernel. Could you maybe give me an idea of those steps? For a first timer as far as android is concerned, the instructions can be a little vague. Thanks
adrock74 said:
Hey this is my first time installing linux on a tablet. Ive got the partitioned sd card, rootfs, kernel ready to go. just not famaliar with how to flash the kernel. Could you maybe give me an idea of those steps? For a first timer as far as android is concerned, the instructions can be a little vague. Thanks
Click to expand...
Click to collapse
Please, first, make sure you're using this bootloader for dualboot. Into the thread there are all instructions for flashing the kernel into secboot, on dualboot section, into first post.
Ive been on v8 unlbootloader for awhile. Just never flashed a sec kernel before.
adrock74 said:
Ive been on v8 unlbootloader for awhile. Just never flashed a sec kernel before.
Click to expand...
Click to collapse
download the fastboot package ( from xda , or search on google ) , next connect the tablet with usb to the pc , reboot the tablet with the bootloader menu and select fastboot ...... the pc will install drivers , when it finish , go in the fastboot folder click SHIFT + right click and select "open command window here " and type this :
fastboot flash secboot <nameofkernel> ex : fastboot flash secboot boot.img
Forzaferrarileo said:
download the fastboot package ( from xda , or search on google ) , next connect the tablet with usb to the pc , reboot the tablet with the bootloader menu and select fastboot ...... the pc will install drivers , when it finish , go in the fastboot folder click SHIFT + right click and select "open command window here " and type this :
fastboot flash secboot <nameofkernel> ex : fastboot flash secboot boot.img
Click to expand...
Click to collapse
Thanks for the reply! Ive flashed this tablet seven ways to sunday within android, but this is kinda new to me. Recently installed 12.04 on my desktop as my intro to linux without a hiccup. I cant seem to get the tablet to respond to my computer. Have the sd card setup ready to go, terminal only says file does not exist ( in regards to secboot) should sd be in tablet or usb? Ive been at it all day. Should i rename anything? Thanks again.
---------- Post added at 04:43 PM ---------- Previous post was at 04:35 PM ----------
I Simply cant seem to get the kernel flashed. Once i get past that, i believe its smooth sailing..
adrock74 said:
Thanks for the reply! Ive flashed this tablet seven ways to sunday within android, but this is kinda new to me. Recently installed 12.04 on my desktop as my intro to linux without a hiccup. I cant seem to get the tablet to respond to my computer. Have the sd card setup ready to go, terminal only says file does not exist ( in regards to secboot) should sd be in tablet or usb? Ive been at it all day. Should i rename anything? Thanks again.
---------- Post added at 04:43 PM ---------- Previous post was at 04:35 PM ----------
I Simply cant seem to get the kernel flashed. Once i get past that, i believe its smooth sailing..
Click to expand...
Click to collapse
Please look if fastboot recognized your tablet. Run fastboot devices. If there's an answer, then your tablet was recognized. It can be missing drivers. From acer site it's possible to find the correct drivers.
ok. so not having the acer drivers seems to be my issue. But, Im trying to do this using my pc running ubuntu, and I'm not sure how to get the acer drivers installed on it. I'm sure there is a trick, but the downloads are for windows. And also the downloads are for honeycomb and ics and im running 4.2.2.
Well I cannot help you installing drivers into ubuntu, I made it into Windows.
on android terminal emulator:
cat /proc/mounts
make sure that data is on /dev/block/mmcblk0p8 not p7
if so then:
dd if=your_second_boot.img of=/dev/block/mmcblk0p7
do it within android, not within linux or initial ramdisk console on you tablet, because linux recognize data as /dev/mmcblk0p7. sorry for bad English.
Tautvaldas said:
on android terminal emulator:
cat /proc/mounts
make sure that data is on /dev/block/mmcblk0p8 not p7
if so then:
dd if=your_second_boot.img of=/dev/block/mmcblk0p7
do it within android, not within linux or initial ramdisk console on you tablet, because linux recognize data as /dev/mmcblk0p7. sorry for bad English.
Click to expand...
Click to collapse
thanks for the response, what will this be doing??
adrock74 said:
thanks for the response, what will this be doing??
Click to expand...
Click to collapse
It'll flash the kernel into the correct partition, via android.
guimendes said:
It'll flash the kernel into the correct partition, via android.
Click to expand...
Click to collapse
ok gotcha. Sorry to be a bother, but i want to do this. Right now ive got my kernel and rootfs on a partitioned sd card in my extsd slot. If I flash the kernel using terminal, where should it be?
adrock74 said:
ok gotcha. Sorry to be a bother, but i want to do this. Right now ive got my kernel and rootfs on a partitioned sd card in my extsd slot. If I flash the kernel using terminal, where should it be?
Click to expand...
Click to collapse
If you follow strict what Tautvaldas said, it'll be placed in the right place for dualbooting, the same if you use fastboot tool.
Thanks for your help guys. But mixing and matching this and that, i give up. Ive flashed the sh*t out of this tab, but without a unified tutorial, i cant make sense of this. Ive been running linux on my pc and laptop, so this isnt foreign to me, but i need a more straight forward tutorial. Thanks though again. We all have to learn sometime:good:
I ran a dist-upgrade on it and my wifi now seems broken - rfkill can unblock it but ifconfig returns SIOsomething something error, permission denied. Ideas?
So I was randomly flying around on Google today, and I noticed that someone had claimed to root the Kobo Arc, and gave written instructions here -- http : // www . mobileread . com / forums / showthread.php?p=2584491 (Remove the spaces, XDA won't let me post an actual link, since I don't have 10 posts yet). After running through this myself, I went on the Google Play store and used root checker. Much to my surprise, it worked, and my device now has root access. I even tested with Root Explorer, and mounted the system partition as R/W, and I can move things in and out of it. I'm currently working on trying to get a custom ROM working, but I'm worried that I will cause a brick, since Cyanogen doesn't support the Arc. (yet...)
ThunderBird2678 said:
So I was randomly flying around on Google today, and I noticed that someone had claimed to root the Kobo Arc, and gave written instructions here -- http : // www . mobileread . com / forums / showthread.php?p=2584491 (Remove the spaces, XDA won't let me post an actual link, since I don't have 10 posts yet). After running through this myself, I went on the Google Play store and used root checker. Much to my surprise, it worked, and my device now has root access. I even tested with Root Explorer, and mounted the system partition as R/W, and I can move things in and out of it. I'm currently working on trying to get a custom ROM working, but I'm worried that I will cause a brick, since Cyanogen doesn't support the Arc. (yet...)
Click to expand...
Click to collapse
confirmed, was just going to post this but was beaten to it.
http://www.mobileread.com/forums/showthread.php?t=218928
ive attached the file but please go to that website and pay homage to whoever did this work...now to the next stop, a ROM
Device now has a working custom recovery see post 15
Sent from my Arc using xda app-developers app
dazza9075 said:
confirmed, was just going to post this but was beaten to it.
http://www.mobileread.com/forums/showthread.php?t=218928
In terms of a ROM do we not need a compatible boot loader that will allow unsigned ROMs?
ive attached the file but please go to that website and pay homage to whoever did this work...now to find a man about a ROM
Sent from my Arc using xda app-developers app
Click to expand...
Click to collapse
i have absolutely no idea what im doing but I think I have dumped 12 partitions using
dd if=/dev/block/mmcblk0p10 of=/sdcard/p10.img
is there anyone around that fancies a challenge? im in a position where bricking this thing isn't really much of a problem so if someones up for a challenge and wants to help im willing to lend myself and the device to this
Warning : Block of Text Ahead.
dazza9075 said:
confirmed, was just going to post this but was beaten to it.
In terms of a ROM do we not need a compatible boot loader that will allow unsigned ROMs?
ive attached the file but please go to that website and pay homage to whoever did this work...now to find a man about a ROM
Sent from my Arc using xda app-developers app
Click to expand...
Click to collapse
Haha. As soon as I found a thread called "root the Kobo Arc" on Google, I posted it here right away. Sorry if I deprived you of the satisfaction! *troll*
Joking aside, I'm not too sure about the bootloader. I think it's pretty locked down (since I put a nexus 7's cyanogenmod onto the data partition and rebooted. It tried to updated, but said validation failed, or something of that sort). I can't install any custom recoveries either, since I have no idea how to do it in the first place, and there's none made for the Arc.
Also, I analyzed the Arc with the "Droid Examiner" App from the play store (That is a really great app, just so you know), and found that it uses a board called "zeus". The funny thing, though, is that one of Sony's Xperia phones, also has a board called "Zeus", and there's Cyanogenmod for that (albiet not the latest version). However, these two devices have nothing in common. The closest thing to an Arc that has Cyanogenmod is the Nook HD/HD+, which uses the exact same chip (OMAP TI 4470).
If someone is smart enough (not me) to analyze the Cyanogenmod files for the Nook, and see how they work, that may lead into flashing the Arc.
Anyway, I'm resetting the Arc, since I'm having weird cases where the Arc would freeze after booting it from sleep mode, and I'd have to turn it off and on again. I think that was something else I did, since it happened before the root, but neh, I might as well try this all from factory default settings.
Sorry for the block of text, guys!
P.S. Using the stock Jelly Bean boot animation on the Arc looks amazing!:laugh:
Haha, its cool, like yourself I just happened to Google kobo arc root and for once my googe fu was up to the task and the root appeared
I've been looking at starting my own recovery mod branch but its no simple task by the looks of it, if their are similar devices we can use all their data and tweak it to ours which would help a lot!
Oh I think we have fast boot, I held vol down and pushed power on, it just sat at the kobo arc screen, I used the nexus 7 driver from the universal adb/fastboot driver I found on here and it connected up http://forum.xda-developers.com/showthread.php?t=2263822
I stumbled on some to good to be true program on Xda dev that apparently can root anything and unlock any bootloader once your in fastboot mode. I have tried that part and it said it was successful but i have no idea how to test this out yet, the program does a bunch of other stuff too, the adb stuff worked as did apk sending, and the rooting options knew i was rooted, it also has flashing functions, I'll be damed if I can find it now I'm at home though , I'll have another look.
I don't mind doing leg work but if someone can read the map it would be very helpful!
Edit, found it
http://forum.xda-developers.com/showthread.php?t=2399385
http://www.mediafire.com/?vwxpq62pa927s9c
Sent from my Arc using xda app-developers app
dazza9075 said:
Haha, its cool, like yourself I just happened to Google kobo arc root and for once my googe fu was up to the task and the root appeared
I've been looking at starting my own recovery mod branch but its no simple task by the looks of it, if their are similar devices we can use all their data and tweak it to ours which would help a lot!
Oh I think we have fast boot, I held vol down and pushed power on, it just sat at the kobo arc screen, I used the nexus 7 driver from the universal adb/fastboot driver I found on here and it connected up http://forum.xda-developers.com/showthread.php?t=2263822
I stumbled on some to good to be true program on Xda dev that apparently can root anything and unlock any bootloader once your in fastboot mode. I have tried that part and it said it was successful but i have no idea how to test this out yet, the program does a bunch of other stuff too, the adb stuff worked as did apk sending, and the rooting options knew i was rooted, it also has flashing functions, I'll be damed if I can find it now I'm at home though , I'll have another look.
I don't mind doing leg work but if someone can read the map it would be very helpful!
Edit, found it
http://forum.xda-developers.com/showthread.php?t=2399385
http://www.mediafire.com/?vwxpq62pa927s9c
Sent from my Arc using xda app-developers app
Click to expand...
Click to collapse
Um... Okay. I've installed the drivers (I think I installed them correctly), and I booted my device using "volume down + power". I have it connected to my System, but whenever I try to use one of the options in the Android Root Toolkit, it tells me it's waiting for the device. I don't know what I did wrong, but something's clearly not working.
As far as the recovery goes, I think that looking at the Nook Tablet from TWRP would work quite nicely. It runs on a similar processor ( I believe it's a OMAP TI 4430 ), and it seems to be quite similar in specs to the Arc. If only I was a bit better at programming...
ThunderBird2678 said:
Um... Okay. I've installed the drivers (I think I installed them correctly), and I booted my device using "volume down + power". I have it connected to my System, but whenever I try to use one of the options in the Android Root Toolkit, it tells me it's waiting for the device. I don't know what I did wrong, but something's clearly not working.
As far as the recovery goes, I think that looking at the Nook Tablet from TWRP would work quite nicely. It runs on a similar processor ( I believe it's a OMAP TI 4430 ), and it seems to be quite similar in specs to the Arc. If only I was a bit better at programming...
Click to expand...
Click to collapse
im usig the generic android adb driver and the bootloader driver for fast boot
im dumped all partitions and mapped them all out, see below for file system details
But again I'm blindly stabbing in the dark and most tutorials are a bit lacking in depth or not relevant to the kobo :/
Sent from my Arc using xda app-developers app
127|[email protected]:/ # blkid
/dev/block/dm-2: UUID="57f8f4bc-abf4-655f-bf67-946fc0f9f25b" TYPE="ext4"
/dev/block/dm-1: UUID="57f8f4bc-abf4-655f-bf67-946fc0f9f25b" TYPE="ext4"
/dev/block/dm-0: UUID="57f8f4bc-abf4-655f-bf67-946fc0f9f25b" TYPE="ext4"
/dev/block/mmcblk0p12: UUID="57f8f4bc-abf4-655f-bf67-946fc0f9f25b" TYPE="ext4"
/dev/block/mmcblk0p11: UUID="57f8f4bc-abf4-655f-bf67-946fc0f9f25b" TYPE="ext4"
/dev/block/mmcblk0p10: UUID="57f8f4bc-abf4-655f-bf67-946fc0f9f25b" TYPE="ext4"
/dev/block/mmcblk0p4: UUID="57f8f4bc-abf4-655f-bf67-946fc0f9f25b" TYPE="ext4"
[email protected]:/ #
Okay, so I can't even push apps to the Arc using ADB. I think you have to boot into recovery (power + volume up). I don't know how to use the terminal at all (I'm lost, I know D: ), so I don't have that installed on the Arc. I remember being able to do ADB even with my Sony Reader (First gen, PRST1), so I'm not sure why the Arc isn't quite working. I have both drivers installed, BTW.
As for the recovery, I can't even find a method to flash it. I'm still trying everything I can, though. :\
Sent from my Arc using xda app-developers app
ive mapped out the following partitions and any info ive found about each of them, im not in a position to help at the moment, got a big day at work tomorrow, as mentioned above ive used several tools,
SuperSU,
ROM toolbox pro
busybox
remount
Below is a list of all the available partition names and numbers
/dev/block/mmcblk0p1 xloader
/dev/block/platform/omap/omap_hsmmc.1/by-name/xloader
348KB
/dev/block/mmcblk0p2 bootloader
/dev/block/platform/omap/omap_hsmmc.1/by-name/bootloader
1.50MB
/dev/block/mmcblk0p3 cypto
/dev/block/platform/omap/omap_hsmmc.1/by-name/crypto
Completely empty
64KB partition size
/dev/block/mmcblk0p4 EFS
Mounted as /FACTORY
/dev/block/mmcblk0p4:UUID="57f8f4bc-abf4-655f-bf67-946fc0f9f25b" TYPE="ext4"
/dev/block/platform/omap/omap_hsmmc.1/by-name/efs /factory ext4 ro,relatime,barrier=1,data=ordered 0 0
20MB
/dev/block/mmcblk0p5 misc
/dev/block/platform/omap/omap_hsmmc.1/by-name/misc
Completely empty
128KB partition size
/dev/block/mmcblk0p6 Bootlogo
/dev/block/platform/omap/omap_hsmmc.1/by-name/bootlogo
Contains kobo arc picture
4MB partition size
/dev/block/mmcblk0p7 Logos
/dev/block/platform/omap/omap_hsmmc.1/by-name/logos
contains the battery charge logo
28MB partition size
/dev/block/mmcblk0p8 recovery
/dev/block/platform/omap/omap_hsmmc.1/by-name/recovery
data contains a GZ file, when decompressed we get a 8.5MB file of unknown type, exact same as in boot
5MB of data
16MB partition size
/dev/block/mmcblk0p9 boot
/dev/block/platform/omap/omap_hsmmc.1/by-name/boot
data contains a GZ file, when decompressed we get a 8.5MB file of unknown type, exact same as n recovery
4.5MB of data
8MB partition size
/dev/block/mmcblk0p10 CACHE
Mounted as /CACHE
/dev/block/mmcblk0p10: UUID="57f8f4bc-abf4-655f-bf67-946fc0f9f25b" TYPE="ext4"
/dev/block/platform/omap/omap_hsmmc.1/by-name/cache /cache ext4
rw,nosuid,nodev,noatime,errors=panic,barrier=1,nom blk_io_submit,data=ordered 0
0
768MB partition size
/dev/block/mmcblk0p11 SYSTEM
Mounted as /SYSTEM
/dev/block/mmcblk0p11: UUID="57f8f4bc-abf4-655f-bf67-946fc0f9f25b" TYPE="ext4"
/dev/block/platform/omap/omap_hsmmc.1/by-name/system /system ext4
rw,relatime,barrier=1,data=ordered 0 0
910MB partition size
/dev/block/mmcblk0p12 USERDATA
Mounted as /DATA
/dev/block/mmcblk0p12: UUID="57f8f4bc-abf4-655f-bf67-946fc0f9f25b" TYPE="ext4"
/dev/block/platform/omap/omap_hsmmc.1/by-name/userdata /data ext4
rw,nosuid,nodev,noatime,errors=panic,barrier=1,nom blk_io_submit,data=ordered 0
0
12GB partition size
Watching with interest. The root works. No frills CPU installed and working. There may be hope for this thing yet:good:
Moved to new thread and more appropriate forum - keep up the good work guys
im not sure that's going to work you know, ive had some permission errors with adb which suggests the root isn't full, terminal on the device works fine, but adb just has some problems, adb shell and the su seems to fix them.
http://www.gadgetsdna.com/android-terminal-adb-shell-command-list/1168/
http://www.addictivetips.com/android/make-nandroid-backups-on-android-without-booting-into-recovery/
im busy today but ive found these useful
i think Clockwork Recovery should be our focus at this point or if you have dumped your partitions(?) attempt to construct a rom for later use
or this should work too
Install any Custom Recovery with flash_image:
Just like the previous method, this method also requires following advanced steps and is not recommended if the first method is working for you. flash_image is a tool for Android devices that lets you rewrite your phone’s system partitions with partition image files and installing it to your device requires ADB. If you don’t already have ADB installed, check out our guide on installing ADB. Once you have ADB installed, flash the custom recovery image as follows:
WARNING: It is very important that the recovery image that you use in this method is compatible with your device. Else it will not work and flashing it could possibly brick your device.
Download flash_image and extract it from the zip file to a location on your computer. We extracted it to the main C drive (not in any folder) and will use that in the next steps.
Copy the recovery image for your phone to a convenient location on your computer, preferably with a short path. We will be placing it on the C Drive directly (not in any folder) and using that in the next steps.
Note: The recovery image should have .img extension. If it is in a zip file, extract the .img file from it.
Enable USB debugging mode on your device from Menu > Settings > Applications > Development.
Connect your device to your computer via USB.
Open a Command Prompt window on your computer and enter the following commands: adb push c:\flash_image /sdcard/adb push c:\recovery.img /sdcard/adb shellsumount -o remount, rw /systemcp /sdcard/flash_image /system/bincd /system/binchmod 777 flash_imageflash_image recovery /sdcard/recovery.imgThis will first transfer flash_image and recovery.img to your phone. Then it will copy flash_image to the /system/bin folder of your Android device and make it executable. Finally, it will flash the custom recovery image to your device using flash_image.
Note that we used c:\flash_image and c:\recovery.img in the first two lines as we had these files extracted at the root of our C drive. If you extracted the files elsewhere, use the appropriate paths and if your recovery image has a different name, use the appropriate name.
Reboot your device once the process is finished and you’re done. You may exit adb and the Command Prompt window on your computer by entering ‘exit’ thrice.
dazza9075 said:
im not sure that's going to work you know, ive had some permission errors with adb which suggests the root isn't full, terminal on the device works fine, but adb just has some problems, adb shell and the su seems to fix them.
http://www.gadgetsdna.com/android-terminal-adb-shell-command-list/1168/
http://www.addictivetips.com/android/make-nandroid-backups-on-android-without-booting-into-recovery/
im busy today but ive found these useful
i think Clockwork Recovery should be our focus at this point or if you have dumped your partitions(?) attempt to construct a rom for later use
or this should work too
Install any Custom Recovery with flash_image:
Just like the previous method, this method also requires following advanced steps and is not recommended if the first method is working for you. flash_image is a tool for Android devices that lets you rewrite your phone’s system partitions with partition image files and installing it to your device requires ADB. If you don’t already have ADB installed, check out our guide on installing ADB. Once you have ADB installed, flash the custom recovery image as follows:
WARNING: It is very important that the recovery image that you use in this method is compatible with your device. Else it will not work and flashing it could possibly brick your device.
Download flash_image and extract it from the zip file to a location on your computer. We extracted it to the main C drive (not in any folder) and will use that in the next steps.
Copy the recovery image for your phone to a convenient location on your computer, preferably with a short path. We will be placing it on the C Drive directly (not in any folder) and using that in the next steps.
Note: The recovery image should have .img extension. If it is in a zip file, extract the .img file from it.
Enable USB debugging mode on your device from Menu > Settings > Applications > Development.
Connect your device to your computer via USB.
Open a Command Prompt window on your computer and enter the following commands: adb push c:\flash_image /sdcard/adb push c:\recovery.img /sdcard/adb shellsumount -o remount, rw /systemcp /sdcard/flash_image /system/bincd /system/binchmod 777 flash_imageflash_image recovery /sdcard/recovery.imgThis will first transfer flash_image and recovery.img to your phone. Then it will copy flash_image to the /system/bin folder of your Android device and make it executable. Finally, it will flash the custom recovery image to your device using flash_image.
Note that we used c:\flash_image and c:\recovery.img in the first two lines as we had these files extracted at the root of our C drive. If you extracted the files elsewhere, use the appropriate paths and if your recovery image has a different name, use the appropriate name.
Reboot your device once the process is finished and you’re done. You may exit adb and the Command Prompt window on your computer by entering ‘exit’ thrice.
Click to expand...
Click to collapse
I've already tried that recovery method (I spent about two hours just googling), and it doesn't work with the Arc. The ADB won't let me push the image over.
As for Cyanogenmod, I tried something yesterday. A person on the Mobileread forums (apparently a Kobo employee) put out an update.zip file for the Kobo Arc. The file was quite old, and it's really just the 4.1.1 update that (I hope) we're all running. He said that as long as you put it on the root of the data partition, the Arc will flash it immediately. When I tried taking a Nexus 7's Cyanogenmod file and sticking it in the same place, the Arc started flashing it, but then just said there was an error with the update. So I personally think that you do require a properly signed ROM.
However, if you open up Kobo's update.zip using Winrar, a sidebar pops up that says "signed by SignApk". I don't know too much about this, but couldn't we use this "signapk" to sign our own ROMS and flash them?
Just a thought.
ThunderBird2678 said:
As for Cyanogenmod, I tried something yesterday. A person on the Mobileread forums (apparently a Kobo employee) put out an update.zip file for the Kobo Arc. The file was quite old, and it's really just the 4.1.1 update that (I hope) we're all running. He said that as long as you put it on the root of the data partition, the Arc will flash it immediately. When I tried taking a Nexus 7's Cyanogenmod file and sticking it in the same place, the Arc started flashing it, but then just said there was an error with the update. So I personally think that you do require a properly signed ROM.
However, if you open up Kobo's update.zip using Winrar, a sidebar pops up that says "signed by SignApk". I don't know too much about this, but couldn't we use this "signapk" to sign our own ROMS and flash them?
Just a thought.
Click to expand...
Click to collapse
I think there is a problem with the setup, I just flashed a CW recovery image and it worked, or didn't rather! but the concept did, transferred, flashed using adb, I had to replace it though as it was totally borked and kept restarting, apparently the touch based recovery methods can be like that, ill have some good time tomorrow night (UK time) if your about, and ill keep at it tonight if I get a chance!
copy recovery to adb location
adb push recovery.img /sdcard/
adb shell
su
cat /sdcard/recovery.img > /dev/block/platform/omap/omap_hsmmc.1/by-name/recovery
exit adb shell and type
adb reboot recovery
fixed it by holding power button and vol down to boot to fastboot recovery
then ran
fastboot flash recovery inputrecovery.img
inputrecovery being my original recovery file taken from partition 8!
ive updated the partition map on the post above with my progress, but it looks like we can flash to them my name so its probably less relevant now
oh ive ditched the drivers I was using and reinstalled the drivers from the official SDK, generic android adb for within android and android bootloader for fastboot
EDIT
Yaaas!! recovery replaced
ok, deleting or renaming /etc/install-recover.sh appears to have stopped custom recovery being changed back to stock after reboot, I used the recovery builder to make a build from partition 8, which it did without error, flashed using the above commands.
Still don't know what im doing though, but progress is progress
ill post a link to the custom recovery ive made soon, we need to make up some fstab file listing all the mounts etc, i tried one but it must be borked as recovery couldnt see anything
ok i have a working recovery http://jenkins.cyanogenmod.com/job/recovery/35325/artifact/
its not quite done, i need to mount the sdcard, its physical location is mounted, ie /data, but its virtual mount isn't /storage/sdcard
I have asked for some help so hopefully someone can help be on this, I think it needs to be symlinked
im going to need some help soon, so if your reading this with a kobo arc, I need you! im needing a hand folks! if your stuck getting this far let me know and we can PM to get it working
oh and recovery is also now persistant by deleting or renaming /etc/install-recover.sh"
Sorted folks!
I have made a stable and thus far, a working custom recovery.
its mounting everything and backing up / restoring works as it should, unless anyone can find any issues I consider this step in building a complete ROM completed,
you must have root, download arctic.apk and install on your tablet, you will need to enable unknown sources In dev options first
you must have android and java sdk also installed, you will need to add the google usb drivers in the android sdk, you will find them in the "extras"
Enable usb debug on the arc and install the generic google adb usb drivers
Delete or rename /etc/install-recover.sh this will make the custom recovery persistent
Copy the recovery.img to the SDCard, either by using drag and drop in windows ( to root of "internal storage") or by adb push, if you use adb push then remember to copy recovery.img to the same folder as adb
adb push recovery.img /sdcard/
The next job is to open up a command window and navigate to adb folder, type the following exactly, even better copy and paste them!
adb shell
su
cat /sdcard/recovery.img > /dev/block/platform/omap/omap_hsmmc.1/by-name/recovery
exit adb shell (ctrl+C) and type
adb reboot recovery
and bobs your uncle, one happy new recovery
Thanks for your hard work. Everything works quite well.
Sent from my Arc using Tapatalk 4
cancuck said:
Thanks for your hard work. Everything works quite well.
Sent from my Arc using Tapatalk 4
Click to expand...
Click to collapse
that's the easy bit, I have a feeling I need to make a couple of changes to the recovery.img but noting major, just a couple of other mounts I may have missed
I probably would like some help with the next bit however.
im just trying to build a development platform, I have a loathing for Linux as a desktop so will need to re educate myself without throwing my laptop out of the window, after that "challenge" the ROM should be easy
Well, I've just done it, and it works. Everything seems to be in order for the time being. I'm going to muck around with the new capabilities, and see what I can do.
<rant> I am annoyed at how many Windows users there are lurking here -- I mean, you can't even develop Android with Windows!!! Why is everything I find Windows oriented with no Linux option? </rant>
Here is the one click root zip with a (less verbose) Linux sh script. To quote the other thread,
Credit goes to the creator of the Zenfone 2 installer: @29y6145 Thread
You need ADB and fastboot installed first. Your distro has it, Google it.
Just unzip, and run:
Code:
chmod +x root.sh
./root.sh
And that's literally it. Thanks to the other people who found the files and wrote the commands
Download here: https://steelcowboy.me/zenfone_root.zip
hello..may explain further on how to do this method? is it terminal on the phone or on linux or on the windows (cmd)? and where's the zip file?
Not a newbie tutorial at all. You might want to appropriately title this or add instructions to make it newbie friendly.
cangcan said:
hello..may explain further on how to do this method? is it terminal on the phone or on linux or on the windows (cmd)? and where's the zip file?
Click to expand...
Click to collapse
It's a Linux sh script, so you run it in the Linux terminal. It's the same directions as the other tools, just for Linux
Jhdoubleoseven said:
<rant> I am annoyed at how many Windows users there are lurking here -- I mean, you can't even develop Android with Windows!!! Why is everything I find Windows oriented with no Linux option? </rant>
Here is the one click root zip with a (less verbose) Linux sh script. To quote the other thread,
Credit goes to the creator of the Zenfone 2 installer: @29y6145 Thread
You need ADB and fastboot installed first. Your distro has it, Google it.
Just unzip, and run:
Code:
chmod +x root.sh
./root.sh
And that's literally it. Thanks to the other people who found the files and wrote the commands
Download here: https://steelcowboy.me/zenfone_root.zip
Click to expand...
Click to collapse
I'm stuck in "waiting for devices" but at the start when i check my adb devices, my phone is there.
what's wrong ?
AceHa92 said:
I'm stuck in "waiting for devices" but at the start when i check my adb devices, my phone is there.
what's wrong ?
Click to expand...
Click to collapse
The phone takes a moment to reboot into fastboot mode, so the script has it wait for 30 seconds. Can you confirm that still nothing happens after 30 seconds? And the phone does boot into bootloader mode? If so, type
Code:
adb reboot bootloader
fastboot devices
into your terminal and see if it shows up. If it's not showing up you may have a problem with fastboot itself.
This seems to work (though the fastboot in Debian is too old, I needed to download a newer version) - but I end up with no Superuser app. What's wrong?
Worked perfectly for my memo pad 7 (176cx) Thank you so much!!
drbobb said:
This seems to work (though the fastboot in Debian is too old, I needed to download a newer version) - but I end up with no Superuser app. What's wrong?
Click to expand...
Click to collapse
Sorry for the late reply -- XDA didn't seem to notify me of a new post :/
Did you see all of the fastboot messages go by in both the terminal and the phone's screen? Did everything say "OKAY"? Did you try installing SuperSU from the Play Store to see if it rooted?
Jhdoubleoseven said:
Sorry for the late reply -- XDA didn't seem to notify me of a new post :/
Did you see all of the fastboot messages go by in both the terminal and the phone's screen? Did everything say "OKAY"? Did you try installing SuperSU from the Play Store to see if it rooted?
Click to expand...
Click to collapse
Yep, I think it was OKAY on all commands. I pulled in SuperSU from the store and all root functionality seems okay as well.
I don't understand much of what the script does, especially how
Code:
fastboot flash /system/bin/partlink supersu.tgz
is supposed to work - but then, I haven't looked too closely.
Awesome, really glad it worked out for you! And yeah, I'm not entirely sure -- usually gaining root is based on an exploit so I'd guess that it replaces system binaries with modified ones to allow root access, but haven't rooted many phones so not sure how it generally works. Especially
Code:
fastboot oem start_partitioning
Thanks for this. I tried other one clicks on my fedora 22 box and kept getting fastboot errors. This one worked flawlessly.
Interesting...
The approach is quite a bit different to the usual tethered TWRP suspects as the exploit tries to overwrite quite a few binaries. Naturally I had to try it on my ME572C and unfortunately it couldn't write a single one of those binaries.
therealprof said:
The approach is quite a bit different to the usual tethered TWRP suspects as the exploit tries to overwrite quite a few binaries. Naturally I had to try it on my ME572C and unfortunately it couldn't write a single one of those binaries.
Click to expand...
Click to collapse
That's not a Zenfone though my friend... this is only for Zenfone 2
Jhdoubleoseven said:
That's not a Zenfone though my friend... this is only for Zenfone 2
Click to expand...
Click to collapse
I know, but at some point I would hope that Asus gets an f'ing clue to develop things once and use that across multiple devices running similar hardware. It's already funny how my ME176C and ME572C run completely different Android implementations (one rootable, the other not) despite being somewhat similar.
It's probably a too obvious question, but as the tutorial is for newbies I feel allowed to do:
Do I need to have an unlocked bootloader to succeed in the rooting ? The reason for asking is that the script successfully restart the phone but then the fastboot commands don't work, I get stuck at "waiting for device".
Thanks.
Outdated security
Hey, your HTTPS certs are out of date. I added a temporary exception, then found the redirect failed. I think you server needs some updating...
Any chance of a mediafire or dropbox link?
Hello good peoples of Xda ,
I just purchased a Note 3 verizon I believe 900v on swappa It will arive in the next few day's and I want to get all my ducks in a row by that I mean aquire all the root and unlocking tools nessary for a best practices root and if nessary unlocking of my boot loader.
Goals for root are mostly to debloat the phone and hotspot mod's for no hassle teathering.
I may dip my toes into custom rom for this phone but mostly I am just looking for a clean lean experiance for my note 3. I have been pouring over the many many pages of the various rooting guids and I am just not sure witch method to use is the safest / most reliable .
thank you for your time and helpful suggestions.
This is what I have found so far.
ArabicToolApp : Root for lolipop
Odin3 v3.12.3 : flash tool is this latest ? best to use ?
Samsung usb drivers v1.5.45.0 : are these the proper drivers to install ?
You should start by figuring out which firmware release it has on it.
If it has PL1 (the newest security release, circa 2017/01/15), there will be no rooting for you... unless you manage to create a new exploit.
OB6 and OF1 - (one of) the yemen tool(s)**
NK1 - no root available ( and can't be rolled backwards w/ Odin, only NK1 or higher )
NJ6 - no root available? ( Try towelroot, or you can downgrade to NC4 using Odin )
MI9/MJ7/MJE/NC2(leak)/NC4 - Towelroot v3
For which bootloader unlock binary to use, see here.
Can't help you out with USB drivers, I don't remember what I used. afaik, they will either work 100% or not work at all, so you just need to get something working.
I've never used anything but Odin 3.0.9. Can't tell you if the version you mention is "better".
good luck
** i've never rooted OB6 or OF1, so can't give you any advice about which to use. Feel free to read the related threads. In my (casual) reading of those threads, it is nearly impossible to intuit out why some people have problems and others do not. Mostly because the reporting is not sufficiently detailed.
bftb0 said:
You should start by figuring out which firmware release it has on it.
Click to expand...
Click to collapse
Your right, after thinking about my post I realized there were 2 many variables that I need to know before I ask for help. So once I recieve the phone and if it's fully functional I will find out what firmware it has and what the cid it has and will post a follow up if I need help.
P.S thank you for the concise jist of what is and is not possible with the various firmware's.
Recieved my phone.
I got my note 3 and boy is it just a wonderful device. SM-900v running OF1 firmware, and My Cid is 15 so is all good.
procedurs completed.
I got root from useing the yemem tool.
and have tryed some debloating removed the NFL apk as a test with Tit.backup.
dissabled ota updates, I made a copy of the update.zip (that was downloaded with out me asking it too. I assume that this update.zip is the new PL4 firmware )and deleted it. renamed the fota.apk's with a .bak
not really sure if I should unlock the the bootloader I would love to have twerp.
Could anyone point me at a good debloating script ?
LOVE LOVE LOVE my note 3.
I also have a zero lemon battery/case combo on the way.
PL1 not PL4
See here. Might be dated - stuff tends to move around from release to release.
You should probably also freeze SDM.* and SysScope.* (in addition to LocalFOTA)**
There is a small permanent downside to unlocking - the blowing of the Knox Warranty Flag means that you will never be able to use Knox Secure containers, even if you did a full stock flash with Odin. Not sure how important this is to folks using the phone as a personal device (as opposed to a corporate device).
Operating with a rooted-stock device with a locked bootloader usually progresses through a customary arc - especially with new rooters, but also with experienced folks - where the user one day does some incremental mod that boot-loops the Android UI. At that point there is no means to reverse the small change. (You can't get in via "adb" as it's daemon isn't started yet, and even if it were, the fact that it is in secure mode means that you would have to have a stable UI in order to confirm the connection.) As there is no rooted secondary boot available (i.e., a custom recovery), there is no way to perform repairs, and a trip back to Odin is in store for the owner. Worse yet, a backup has never been made... so all customizations are all lost and must be re-created completely from scratch.
** this is a good idea if you unlock and install a custom recovery: (although TWRP may detect it and emasculate it automatically)
Code:
su
chmod 0000 /system/bin/install-recovery.sh
bftb0 said:
PL1 not PL4
Click to expand...
Click to collapse
Right PL1 ok.
Well I decided in for a penney in for a pound and have sucessfully unlocked my boot loader, had no issues.
my question now is how do I install twerp I have downloaded
twerp-3.0.2-0-hltevzw-4.4
and twerp 3.0.2-1-hlte.img.tar
I think I need to install the tar file.
but I don't know how. I have odin but not sure if that is the right program to use. I think I read where somone installed twerp with flashify or somthing like that.
What should I do ?
Truck'nfool said:
Right PL1 ok.
Well I decided in for a penney in for a pound and have sucessfully unlocked my boot loader, had no issues.
my question now is how do I install twerp I have downloaded
twerp-3.0.2-0-hltevzw-4.4
and twerp 3.0.2-1-hlte.img.tar
I think I need to install the tar file.
but I don't know how. I have odin but not sure if that is the right program to use. I think I read where somone installed twerp with flashify or somthing like that.
What should I do ?
Click to expand...
Click to collapse
man up and use a root prompt command line. It's a single command.
Code:
dd of=/dev/block/mmcblk0p15 if=/sdcard/twrp-3.0.2-0-hltevzw-4.4.img bs=2048
( assuming that you put the twrp .img file in the /sdcard folder. If it was in the download folder, then if=/sdcard/Download/twrp-3.0.2-0-hltevzw-4.4.img )
Note there are absolutely, positively no spaces anywhere in "mmcblk0p15". Critically important.
The above command writes a raw binary data (the .img file) to the 15th partition of the mmcblk0 device - the flash memory chip. You can do this with boot images (such as custom recoveries) or a few other binary images, but typically not with ext4 or other filesystems.
Note this command could be extremely dangerous if you made a mistake. If you were to write data someplace else it could be a permanent disaster. So cut-n-paste to be safest (without a new-line), and then double- and triple- check the command for typos before you hit the enter key.
FYI, you can see what the partition mapping is by doing a folder listing
Code:
ls -ld /dev/block/platform/*1/by-name/*
The partitioning scheme varies from android device to android device; but on the SM-N900V the recovery partition is the 15th partition. (On other devices it might be something different).
bftb0 said:
man up and use a root prompt command line. It's a single command.
dd of=/dev/block/mmcblk0p15 if=/sdcard/twrp-3.0.2-0-hltevzw-4.4.img bs=2048
Click to expand...
Click to collapse
are you talking about adb ?
So somthing like
adb shell
su
dd of=/dev/block/mmcblk0p15 if=/sdcard/twrp-3.0.2-0-hltevzw-4.4.img bs=2048
???
Truck'nfool said:
are you talking about adb ?
So somthing like
adb shell
su
dd of=/dev/block/mmcblk0p15 if=/sdcard/twrp-3.0.2-0-hltevzw-4.4.img bs=2048
???
Click to expand...
Click to collapse
That works.
Or a terminal emulator.
All you need is to put the file on your (internal, pseudo-) /sdcard, "su", and "dd".
For extra credit, make sure to compute a file checksum (e.g. "md5sum") every time you copy the original .img file to a new location and especially prior to flashing. That safeguards against a bad copy operation, crappy flash memory, etc.
Stock ROMs might not have a "md5sum" binary in /system/bin, but since you are rooted you could install a private busybox in someplace like /data/local/bin. I prefer to use a busybox which is SELinux-cognizant, e.g. v1.23.1 here as busybox_full_selinux_1.23.1.zip Note that I don't "install" this .zip so that stuff in /system/bin or /system/xbin get overwritten, but instead just keep it in a private area all on it's own.
Steps.
0) extract the "busybox" binary from the .zip file and get a copy to your SD card. Then
Code:
su
mkdir -p /data/local/bin
chmod 755 /data/local/bin
cp /sdcard/busybox /data/local/bin/
chmod 755 /data/local/bin/busybox
cd /data/local/bin
./busybox --install -s /data/local/bin
This allows it to be used as needed in a terminal/console shell.
e.g. using ls
1) Explicitly: /data/local/bin/ls -lZ *
2) Implicitly "as a last resort":
export PATH="${PATH}"':/data/local/bin'
ls -lZ *
3) Implicitly "as preferred":
export PATH='/data/local/bin:'"${PATH}"
ls -lZ *
I am now have root, unlocked bootloader and twrp Whoot!!
Well I now have twrp installed thank you vary much for all your help and direction I sincerly appreciate your assistance.
I installed termux and after updating the packages sucessfully used dd to install twrp.
1st thing I am going to do a full system backup.
No developer love for N900V not good