hello everybody.
first of all i will present myself.
i'm from France and this is the first time i have a smartphone.
my phone is :
Téléphone : Acer Liquid express E320 -orange
Android : 2.3.4
ROM : acer E320 1.013.00 EMAEA ORGFR
Bande de base : C6-1.013.00
Kernel : 2.6.35.7
after several check in different forums, i didn't find the solution in order to root my phone.
i have tried Doomlord V4 and V3 and it don't work.
i want to root my phone in order to delete some ORANGE application that i would never use.
then it can give some free space on the phone memory (that is very smal = 150Mo).
on a french forum, we are 3 people with exactly the same problem.
so if you help me, you help 3 people....!!
we have tried with all software available on the net but nothing as work.
please find in the link below, the screen shot of my last try with doomlord V4.
https://docs.google.com/open?id=0B9iSIWzMh8dueThpRnJBbGdYTlU
if you need more information or if you have some other things to test, do not hesitate to ask.
.
Thread moved to Q&A due to it being a question. Would advise you to read forum rules and post in correct section.
Failure to comply with forum rules will result in an infraction and/or ban depending on severity of rule break.
chapoune42 said:
hello everybody.
first of all i will present myself.
i'm from France and this is the first time i have a smartphone.
my phone is :
Téléphone : Acer Liquid express E320 -orange
Android : 2.3.4
ROM : acer E320 1.013.00 EMAEA ORGFR
Bande de base : C6-1.013.00
Kernel : 2.6.35.7
after several check in different forums, i didn't find the solution in order to root my phone.
i have tried Doomlord V4 and V3 and it don't work.
i want to root my phone in order to delete some ORANGE application that i would never use.
then it can give some free space on the phone memory (that is very smal = 150Mo).
on a french forum, we are 3 people with exactly the same problem.
so if you help me, you help 3 people....!!
we have tried with all software available on the net but nothing as work.
please find in the link below, the screen shot of my last try with doomlord V4.
https://docs.google.com/open?id=0B9iSIWzMh8dueThpRnJBbGdYTlU
if you need more information or if you have some other things to test, do not hesitate to ask.
Click to expand...
Click to collapse
Salut, t'as essayé avec le OneClickRoot ? USB DebugMod ON ?
Essaye ici... http://www.androidust.com/how-to-root-acer-liquid-express-e320-with-one-click-root/
Sinon essaye avec ça... je sais pas si ça fonctionne par contre... http://www.actualitemobile.com/foru...5df3c2a0662ba09e5bc74a7a1&/topic,19874.0.html
A+
@prg626
oui j'ai essayé avec ces 2 méthodes et aucune ne marche.
merci quand même
Hope someone could help me (and the 2 other french user i know with the same trouble)
thanks
Try This...
I don't have that device nor seen it but in my shop experience, you can modify the rooting programs by extracting the SU and SUPERUSER files from other SuperOneClick programs and pasting those files into that one you posted here and try that. If that does'nt work, then try to get that device in a custom recovery and find a root.zip flashable file and paste the SU and SUPERUSER files into it. Then flash the Root.zip file from the root of your sd card. I got that to work on alot of IMPOSSIBLE devices Sometimes devices are "read only error" so your only alternative is to flash from recovery.
thanks but it seems a litle bit complicated for me...
nonody has another easyest solution for me ?
probably someone has already reach the goal of root this phone... so if he can give us the way to do it, he will be great.
It would seem all rooting exploits are or have been blocked, the only way I have found to root the E320 is the Xakep ROM Flash from acer-club.ru although the rom flash is for 1.008.00 and not 1.013.00 (I did read that 1.008.00 could gain root access using DoomLords tool but not sure of version but depending on your phones production date may now be blocked) I have flashed Xakep ROM 1.008.00 after 1.013.00 now cannot update or reflash as the Radio/AMSS side of ROM is still 1.013.00 ... just to make you aware.... would advise to read as much as possible from Xakep's postings
Rooted Xakep E320/C6 EUU Hacked Update
thanks for this info.
probably i have found a solution :
replace the original ROM Orange (impossible to root) by another ROM Acer already rooted...
does someone can confirm me that it will be possible ?
i want to replace : OS_Acer_1.013.00.EMEA.ORGFR_A23G_A
by this one : acer_E320_1.008.00_EMEA_GEN1:
That is what I'm on now although it has given me the problem that neither the Xakep 1.008.00 or the Orange 1.013.00 EUU'S will reflash the phone.
I must admit I have not tried to solve this problem yet as phone is working 100% other than unable to reflash.
One thing it will not update is the RADIO part of the phone, this will remain as 1.013.00 and this is probably the reason for being unable to reflash.
Rooted Xakep E320/C6 EUU Hacked Update
Since it was stated in another post (possibly on another site just can't remember ) that prior to an OTA update root access was gained using DoomLords exploit, finally a ROM has surfaced *** :highfive: *** that may be of use - Link at the bottom of the page for the ROM
Yes I have it on my phone now and seems A-OK BUT..... and this is a big BUT!!!!......
Please..............(the dreaded disclaimering bit)
DO NOT ATTEMPT TO FLASH THIS IF YOU ARE NOT 100% SURE YOU CAN RECOVER FROM ANY PROBLEMS WITH FLASHING THE ROM
AS YOU WILL HAVE TO EDIT FILES TO 'DOWNGRADE' YOUR PHONES SYSTEM.
If you are confident in editing and flashing then by all means do so BUT I am not held accountable for errors or unusable software/hardware, what may have worked for me may NOT work for you.....
(Basically if you're not sure don't do it - I was only 80% sure trying it but I take risks and fully accept the consequences if I brick my phone)
What you will need to do is the following:
Firstly you will need the Temp files of both the ROM you are using and 1.005.00 ROM.
Current Rom...
No Need To Connect Your Phone For This.
Run the update program.
Search for (depending on your ROM) a folder in
C:\Documents and Settings\*Current_User*\Application Data\
the folder named ACER_EUU_Download_Tools (Stock Update)
Click to expand...
Click to collapse
or for
C:\Documents and Settings\*Current_User*\Local Settings\Temp\
a folder named 7ZipSfx.000 (Xakep ROM's as I have come across no others yet and the .000 can increment .001 .013)
Click to expand...
Click to collapse
Copy that folder to another location then cancel the update (you will notice if you check all but a few files are deleted - this happens even if the update succeds or fails to flash your phone)
Now do the same for the 1.005.00 update and copy the folder to another location.
From the 1.005.00 copied update folder copy the following files:
AMSS_C6.Orange.1.005.00_4G_2Die.hex
Android_C6.Orange.1.005.00_User_Signed.hex
flex-Orange_FR_C6.Orange.1.005.00_User_Signed.hex
Click to expand...
Click to collapse
Paste into the copied Current ROM folder.
Rename the corresponding files - examples:
AMSS
Orange = AMSS_C6.Orange.1.014.00_4G_2Die.hex
Xakep =C6_Image_4G_2Die_MODEM.hex
Android System
Orange = Android_C6.Orange.1.014.00_User_Signed.hex
Xakep = C6_Android_WB_1.008.00_release_key.hex
FLEX
Orange = flex-EMEA_GEN1_signed.hex
Xakep = flex_Orange_UK_C6.Orange.1.014.00_User_Signed.hex
rename and add .bak to the files (we want to preserve the filenames)
Click to expand...
Click to collapse
Now rename the copied 1.005.00 files to the corresponding files renamed .bak (to suit your ROM's files)
Make a backup copy of your now edited folder incase of any failure
(the EUU deletes files on success AND failure - we don't want to have to go through this again)
You can now delete/remove any files you no longer require (1.005.00 copied folder - .bak files)
You can now run the file EUU.exe from the edited folder and update the phone.
SKU - The French/Russian ROM's use different SKU than the UK ROM, the above method is the only one i've been able to
revert my phone back to a UK ROM - FR and RU ROMS can flash over each other and UK...UK is unable to flash over FR/RU ROM.
Click to expand...
Click to collapse
Any DEV interested in modding and maybe making Root Access persistant (think this is the only ROM prior to 1.008.00 update that is rootable) --==>>HERE<<==-- is the link for ACER 1.005.00 ORGFR ROM I found.
Have Fun.
*** Tested and rooted with DooMLoRD V4 ROOT ***
Code:
--- STARTING ---
--- WAITING FOR DEVICE
* deamon not running. starting it now *
*daemon started successfully *
---creating temporary directory
mkdir failed for tmp, File exists
--- cleaning
--- pushing zergrush
720 KB/s (23060 bytes in 0.031s)
--- correcting permissions
--- executing zergrush
[**] Zerg rush - Android 2.2/2.3 local root
[**] (C) 2011 Revolutionary. All rights reserved.
[**] Parts of code from Gingerbreak, (C) 2010-2011 The Android Exploit Crew.
[+] Found a GingerBread ! 0x00000118
[*] Scooting ...
[*] Sending 149 zerglings ...
[+] Zerglings found a way to enter ! 0x10
[+] Overseer found a path ! 0x00015180
[*] Sending 149 zerglings ...
[+] Zerglings caused crash (good news): 0x40121cf4 0x0064
[*] Researching Metabolic Boost ...
[+] Speedlings on the go ! 0xafd24fcf 0xafd39027
[*] Popping 8 more zerglings
[*] Sending 157 zerglings ...
[+] Rush did it ! It's a GG, man !
[+] Killing ADB and restarting as root...enjoy!
--- WAITING FOR DEVICE TO RECONNECT
if it gets sstuck over here for a long time then try:
disconnect usb cable and reconnect it
toggle "USB DEBUGGING" (first disable it then enable it)
--- DEVICE FOUND
---pushing busybox
1049 KB/s (1075144 bytes in 1.000s)
--- correcting permissions
--- remounting /system
--- checking free space on /system
27 KB/s (439 bytes in 0.015s)
df: /data/DxDrm/fuse: Permission denied
--- Free space on /system : 5356 bytes
--- Not enough free space on /system!!!
--- making free space by removing Google Maps
--- copying busybox to /system/xbin/
2099+1 records in
2099+1 records out
1075144 bytes transfered in 0.452 secs (2378637 bytes/sec)
--- correcting ownership
--- correcting permissions
--- installing busybox
--- pushing SU binary
347 KB/s (22228 bytes in 0.062s)
--- correcting ownership
--- correcting permissions
--- correcting symlinks
--- pushing Superuser app
2135 KB/s (785801 bytes in 0.359s)
--- cleaning
--- rebooting
ALL DONE!!!
Press any key to continue . . .
:cyclops: . . . . . and here is an OTA .zip I grabbed - Official OTA contains .mbn & .img files so here's some info .txt
Has anyone else tried this yet?
I have tried it but I had firmware from acer-club.ru and I have bricked my phone, so as this post says be careful.
If anyone know how to get past 'aFlex download fail!!!' and the USB is not recognized by PC then let me know.
For those that come across this I finally got it working. I am not sure what did it but this is what happened.
Phone was left with battery disconnected most of the day.
I formatted a 4GB mini SD card and copied the folder from OTA.ZIP file on the bottom of Antagonist42 post.
Inserted this mini SD refitted the battery and whilst holding volume up and volume down press and held the power button.
Not sure if I released one of the volume keys but modem download came up without the dreaded 'aFlex download fail!!!' message.
Connected to laptop flashed with standard 1.013.00 firmware from Acer UK website.
Phone then booted and did OTA update to 1.014.00 and all looks OK. (sorry Antagonist42 was not quick enough to the OTA files)
I don't know what helped here but I thought I would let you all know what I did.
My warranty is still sending out a replacement phone tomorrow even though I got it going so I will try Antagonist42's root fix when I have the new one as this one needs to go back with the stock ROM.
Finally have phone working ( to a degree ) and moved house ( unable to play with phone and OTA ).
aSYSTEM/aFLEX/etc download fails
Initially rerun the update program and/or download the updater again, ensure you're not getting decompression/write errors on your PC as this will give you the same errors.
If after doing the above the error remains then it could actually be hardware failure ( still trying to iron my own NAND/partition error out )
As for running OTA over an error the OTA is not written to memory in the same way as the PC updater as with prior post my guess is corrupt file and not an actual 'brick' as running a fresh updater (the same as the rom that was installed and not a different rom) would probably have corrected the fault.
I'll soon post what other small but interesting things you can do with a stock updater that does not require hacking or vast programming knowledge
Sent from my Poorly Acer E320
Does anyone got the file EUUs_E320_1.005.00_EMEA_ORGFR.zip? The link to dropbox is dead/blacklisted
Need this file urgently, i would really appreaciate it....
Thanks
Orange French EUU 1.005.00
here's a link for EUU EMEA ORGFR if you're in UK you may not get some apps that appear on Google Play as it uses a different SKU (says which country it can be used in)
https://anonfiles.com/file/b197e1af76f99f9628ce0576c9f2d0b3
Related
Hello.
Well, sorry for bothering you... but I really don't know what to do. I am too lost so the things I wrote here may not have sense
There is a recap at the end of this post, so I won't annoy you more than necessary.
Before explaining anything, I will show you my mobile specifications.
- Model: Sony Xperia Go ST27i
- Android version: Ice Cream Sandwich 4.0.4
- Kernel: 6.1.1.B.1.54
- Root?: No
- Unblocked Bootload: No
Click to expand...
Click to collapse
My mobile phone was in the 6.1.B.0.599 kernel. Thanks to the user Bin4ry and his application Root and Restore, I could root it and gain superuser privileges, so I could uninstall annoying apps and customize my phone as I wanted with a custom launcher, etc.
Suddenly, every time I reseted the phone, it began to happen a strange thing. I will explain it detailedly.
- I turn on the phone.
- The screen brights with the SONY logo.
- The XPERIA logo appears.
- The phone vibrates shortly and the screen stops brighting.
- The XPERIA logo keeps until an undetermined moment.
- After X time (minutes, hours), Android asks me for the PIN number and starts working normally.
I was tired of this, but I didn't know what to do or why do this happen.
Today I connected the phone to the PC and Sony Companion asked me to update to 6.1.1.B.1.54. I hoped that would help with the problem. What I didn't know is that when I update the kernel, I must root the phone again.
That's because I tried to root the phone again, but the application Root and Restore couldn't do it. I mean, the application did the work, the phone reseted and the problem I had with the Xperia initialization solved, but the mobile kept unrooted.
This is the Root and Restore log:
Code:
======================================================================
= This script will root your Android phone with adb restore function =
= Script by Bin4ry (thanks to Goroh_kun and tkymgr for the idea) =
= Idea for Tablet S from Fi01_IS01 =
= (18.12.2012) v17 =
======================================================================
Device type:
1) Normal
2) Special (for example: Sony Tablet S, Medion Lifetab)
x) Unroot
Make a choice: 1
Checking if i should run in Normal Mode or special Sony Mode
Please connect your device with USB-Debugging enabled now
Waiting for device to shop up, if nothing happens please check if Windows ADB-dr
ivers are installed correctly!
1656 KB/s (210390 bytes in 0.124s)
remote object '/system/bin/ric' does not exist
.
Found Sony Backup-Restore.apk
LT26,LT22 etc. mode enabled!
.
Pushing busybox....
3010 KB/s (1085140 bytes in 0.352s)
Pushing su binary ....
2897 KB/s (91980 bytes in 0.031s)
Pushing Superuser app
3908 KB/s (996704 bytes in 0.249s)
Making busybox runable ...
.
Pushing fake Backup
2999 KB/s (73728 bytes in 0.024s)
Extracting fakebackup on device ...
Watch now your device. Select the backup named RootMe and restore it!
Starting: Intent { act=android.intent.action.MAIN cat=[android.intent.category.L
AUNCHER] cmp=com.sonyericsson.vendor.backuprestore/.ui.BackupActivity }
If all is successful i will tell you, if not this shell will run forever.
Running ......
Good, it worked! Now we are rebooting soon, please be patient!
Waiting for device to come up again....
Going to copy files to it's place
[B]mount: permission denied (are you root?)[/B]
You can close all open command-prompts now!
After reboot all is done! Have fun!
Bin4ry
After I investigated a little in this forum, I learnt that I precisely updated to an unrooteable kernel...
I kept investigating and I found out that the solution was downgrading to the kernel I was, then rooting and finally upgrading again, but to downgrade and upgrade I needed to "flash".
I'm not English, I'm noob in Android world and I'm retard, so I couldn't understand how to flash. I installed FlashTools, but I need to download the kernel and I don't know how to find the correct one for my phone. I don't know if FlashTools needs me to unblock Bootload either, but if I need it, I've already got the code from Sony, though maybe there are other unofficial methods...
Sorry for this huge Bible. I will summarize:
I upgraded from .599 to .54 and I can't root. How can I downgrade the kernel?
I'm sorry again for bothering you and for being so retard in this, but could you help me, please? I would like so much to become root again... You can laugh at me :silly: If I wrote something wrong, please, correct me because I'm not English and I could not realize.
Thank you so much :victory:
crystaldolly said:
Hello.
Well, sorry for bothering you... but I really don't know what to do. I am too lost so the things I wrote here may not have sense
There is a recap at the end of this post, so I won't annoy you more than necessary.
Before explaining anything, I will show you my mobile specifications.
My mobile phone was in the 6.1.B.0.599 kernel. Thanks to the user Bin4ry and his application Root and Restore, I could root it and gain superuser privileges, so I could uninstall annoying apps and customize my phone as I wanted with a custom launcher, etc.
Suddenly, every time I reseted the phone, it began to happen a strange thing. I will explain it detailedly.
- I turn on the phone.
- The screen brights with the SONY logo.
- The XPERIA logo appears.
- The phone vibrates shortly and the screen stops brighting.
- The XPERIA logo keeps until an undetermined moment.
- After X time (minutes, hours), Android asks me for the PIN number and starts working normally.
I was tired of this, but I didn't know what to do or why do this happen.
Today I connected the phone to the PC and Sony Companion asked me to update to 6.1.1.B.1.54. I hoped that would help with the problem. What I didn't know is that when I update the kernel, I must root the phone again.
That's because I tried to root the phone again, but the application Root and Restore couldn't do it. I mean, the application did the work, the phone reseted and the problem I had with the Xperia initialization solved, but the mobile kept unrooted.
This is the Root and Restore log:
Code:
======================================================================
= This script will root your Android phone with adb restore function =
= Script by Bin4ry (thanks to Goroh_kun and tkymgr for the idea) =
= Idea for Tablet S from Fi01_IS01 =
= (18.12.2012) v17 =
======================================================================
Device type:
1) Normal
2) Special (for example: Sony Tablet S, Medion Lifetab)
x) Unroot
Make a choice: 1
Checking if i should run in Normal Mode or special Sony Mode
Please connect your device with USB-Debugging enabled now
Waiting for device to shop up, if nothing happens please check if Windows ADB-dr
ivers are installed correctly!
1656 KB/s (210390 bytes in 0.124s)
remote object '/system/bin/ric' does not exist
.
Found Sony Backup-Restore.apk
LT26,LT22 etc. mode enabled!
.
Pushing busybox....
3010 KB/s (1085140 bytes in 0.352s)
Pushing su binary ....
2897 KB/s (91980 bytes in 0.031s)
Pushing Superuser app
3908 KB/s (996704 bytes in 0.249s)
Making busybox runable ...
.
Pushing fake Backup
2999 KB/s (73728 bytes in 0.024s)
Extracting fakebackup on device ...
Watch now your device. Select the backup named RootMe and restore it!
Starting: Intent { act=android.intent.action.MAIN cat=[android.intent.category.L
AUNCHER] cmp=com.sonyericsson.vendor.backuprestore/.ui.BackupActivity }
If all is successful i will tell you, if not this shell will run forever.
Running ......
Good, it worked! Now we are rebooting soon, please be patient!
Waiting for device to come up again....
Going to copy files to it's place
[B]mount: permission denied (are you root?)[/B]
You can close all open command-prompts now!
After reboot all is done! Have fun!
Bin4ry
After I investigated a little in this forum, I learnt that I precisely updated to an unrooteable kernel...
I kept investigating and I found out that the solution was downgrading to the kernel I was, then rooting and finally upgrading again, but to downgrade and upgrade I needed to "flash".
I'm not English, I'm noob in Android world and I'm retard, so I couldn't understand how to flash. I installed FlashTools, but I need to download the kernel and I don't know how to find the correct one for my phone. I don't know if FlashTools needs me to unblock Bootload either, but if I need it, I've already got the code from Sony, though maybe there are other unofficial methods...
Sorry for this huge Bible. I will summarize:
I upgraded from .599 to .54 and I can't root. How can I downgrade the kernel?
I'm sorry again for bothering you and for being so retard in this, but could you help me, please? I would like so much to become root again... You can laugh at me :silly: If I wrote something wrong, please, correct me because I'm not English and I could not realize.
Thank you so much :victory:
Click to expand...
Click to collapse
Download Flashtool by Bin4ary and Androxyde. Install it. Then You should find the 'rootable ftf' file of your firmware in your Xperia Go forum. Download it. and then put it in the folder where you installed Flashtool. Ex. If you installed it in C Drive, go to C> Program Files> Flashtool> Firmwares and paste the 'ftf' file. Then open Flashtool and click on 'Flash' icon. Select flashmode. Select firmware (Careful). Select Ok and follow instructions on screen. After it is done flashing, disconnect the phone and turn it on. It WILL NOT turn ON on its own. Before flashing, make sure USB debugging is on, unknown sources is checked & you are in MSC mode not in MTP mode.
Flashing this ftf will solve ALL of your problems and will unroot your device.
Once the phone turns on, go to your forum section and search on topics how to root. Once rooted, you can remove any unwanted bloat from your system. I prefer using NoBloat free from market. It's cool and safe app that backups all the apps you delete so you can replace them.
Hit thanks if ^^^it^^^ helped you.
kadukarashutosh7 said:
C Drive, go to C> Program Files> Flashtool> Firmwares and paste the 'ftf' file.
Click to expand...
Click to collapse
its not in program files, just c>flashtool>firmwares
try going here
go .54
or here
or here
for flashtool download
for use search the forums
hit thanks.
Ooooooooh, THANK-YOU-SO-MUUUUUUCH! You're awesome. I don't know how to thank you. I'm root again and I've solved all my problems! Really, thank you. :laugh:
:highfive:
crystaldolly said:
Ooooooooh, THANK-YOU-SO-MUUUUUUCH! You're awesome. I don't know how to thank you. I'm root again and I've solved all my problems! Really, thank you. :laugh:
:highfive:
Click to expand...
Click to collapse
Your welcome. And thanks for your comment. someone from xda helped me to root. So I should do my part for the community
Oh and next time you make a thread, don't include all the bio-history from ten years before, okay.
Sent from my Xperia Mini Pro
---------- Post added at 09:21 PM ---------- Previous post was at 09:17 PM ----------
Oh and change the title to solved, edit it, go advanced and insert solved in place of Q
Sent from my Xperia Mini Pro
Ok, so first, I decided to root my TF700,
I went to the All-In-ONE guide, when my tf700 was on JB 4.1.1, The debugfs allways felt,
Waiting for device to be detected...
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
Found system partition at: /dev/block/mmcblk0p1
Step 1 - Pushing files...
926 KB/s (1862336 bytes in 1.961s)
895 KB/s (380532 bytes in 0.415s)
10 KB/s (142 bytes in 0.012s)
Rebooting...
Once your devices has finished restarting,
Press any key to continue . . .
----
this is what he supposed to show but when i did it at the bold column he typed, cant find system............. (it was really fast and then it get out from the method so i couldn't read it, i saw only CANT FIND .... )
I Downgrade my tf700 to ICS 4.0.3 ( 9.4.5.30 )
and its still happening, some body can help me plz? i really want this root..
P.s i allready unlocked the bootloader,
thx for helping !
JusTeN_ said:
Ok, so first, I decided to root my TF700,
I went to the All-In-ONE guide, when my tf700 was on JB 4.1.1, The debugfs allways felt,
Waiting for device to be detected...
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
Found system partition at: /dev/block/mmcblk0p1
Step 1 - Pushing files...
926 KB/s (1862336 bytes in 1.961s)
895 KB/s (380532 bytes in 0.415s)
10 KB/s (142 bytes in 0.012s)
Rebooting...
Once your devices has finished restarting,
Press any key to continue . . .
----
this is what he supposed to show but when i did it at the bold column he typed, cant find system............. (it was really fast and then it get out from the method so i couldn't read it, i saw only CANT FIND .... )
I Downgrade my tf700 to ICS 4.0.3 ( 9.4.5.30 )
and its still happening, some body can help me plz? i really want this root..
P.s i allready unlocked the bootloader,
thx for helping !
Click to expand...
Click to collapse
You don't need to downgrade to root anymore there is a new tool called motochopper can be used to root even you're on JB. OK, since you're UNLOCKED, no need to root. Here is what you should do:
1. Go here to download the tool that you're going to use to flash custom recovery (TWRP): http://forum.xda-developers.com/showthread.php?t=2094746
2. Use the tool to flash TWRP to your device.
3. Boot into recovery (which is TWRP) and flash stock PRE ROOTED rom here.http://forum.xda-developers.com/showthread.php?t=2223918
a) first flash the new 4.2 bootloader zip
b) flash the rom.
Jus Ten is all sorted I guided him through updating to 4.2.1 and rooting earlier.
The Acer Iconia Toolkit is supporting following devices at the moment:
B1-A71
B1-710
B1-A710
B1-711
B1-720
A1-810
A1-811
A3-A10
Liquid S1
Only use these methods if you are sure the device cannot be rooted using a custom recovery from the following thread:
http://forum.xda-developers.com/andr...ax-b1-t2875894
Intel based devices will not be supported ever by this toolkit! Only Mediatek chips are supported!
At the moment the following features are available:
Root from scratch (Unix only / recommended)
Root with prerooted Image (see Download links at the bottom)
Unroot
Swap External <-> Internal SD
Odex ROM
Pull system.img.gz off your device
Download Acer Iconia Toolkit Latest Version
Older Versions:
v0.9.0
v0.8.5
v0.8.4
v0.8.3
v0.8.2
Thank you goes to:
FireDiamond, bullbrand, pawitp, alba81, sodaFR, MatrixDJ96, ak6, min-dfreak, Gilly10, agentdeep, nick_1964, sampod
and the testers
Acer Iconia B1-A71:
Unlock Bootloader
CWM update, that removes bloat
thx to FireDiamond
Apply the "Invalid Partition Error" fix before rooting!!!
To avoid unfixable bootloop, first apply this patch from Acer.
Install the APK, start it, click on FixG1PMT (no feedback) and uninstall afterwards. Good luck!
If you're rooting with prerooted system.img.gz here are the Downloads. Pick the one, fitting to the firmware installed on your tablet, otherwise you will get into bootloop!
RV03RC05:
Acer Firmware Update [mirror] [mirror + md5]
RV04RC04:
[system.img.gz] [mirror]
RV05RC05:
Acer Firmware Update [mirror1] [mirror2] [mirror3] [mirror4 + md5] [mirror5 + md5]
[system.img.gz]
RV02RC12:
system.img.gz
Acer Iconia B1-710 / B1-A710:
Unlock Bootloader (thx to FireDiamond and abstrkt1337)
RV04RC01:
system.img.gz [mirror1] [mirror2]
Stock system Images for B1-710 RV04RC01
Hamza91: stock, rooted
RV04RC01_PA_CA:
Stock and Rooted system image
Acer Iconia B1-711:
RV01RC04_WW_GEN1:
system.img.gz
Acer Iconia B1-720:
RV03RC01_WW_GEN1:
system.img.gz (thx to Hayastan)
RV07RC01_WW_GEN1:
system.img.gz (thx to Hayastan)
Acer Iconia A1-810:
Acer Firmwares
Modified XPosed Installer
RV03RC08:
system.img.gz
RV18RC07_WW_GEN1:
update.zip (about 4MB)
system.img.gz with /system RW workaround (MD5 = 214db984aee42ef0c05d1cfa43d193c1) (needs extra config and SuperSU instead of Superuser) [torrent] (see this post also)
RV21RC02_WW_GEN1:
update.zip
system.img.gz with /system RW workaround (needs extra config and SuperSU instead of Superuser) (see this post also)
RV21RC03_TWN:
system.img.gz with /system RW workaround (needs extra config and SuperSU instead of Superuser) (see this post also)
RV27RC02_PA_CA:
stock system.img.gz (rename to system.img.gz first!)
system.img.gz (rename to system.img.gz first!)
RV27RC03_WW_GEN1:
system.img.gz
stock system.img.gz
update.zip
RV18RC10_PA_CA:
system.img.gz with /system RW workaround (needs extra config and SuperSU instead of Superuser) (see this post also)
RV26RC06_PA_CUS1:
system.img.gz
Stock Images: (Workaround to unroot: Put the system.img.gz of your version into system_image and choose root option in toolkit)
RV03RC08:
system.img.gz
RV18RC07:
system.img.gz ( MD5=550ECDB192F5668264B11B1070F4B932 )
How to root from scratch
Acer Iconia A1-811:
RV01RC11_WW_GEN1:
Acer Firmware Update
RV02RC20:
system.img.gz rooted and stock (including xposed) (thx to konsolen!!)
RV02RC22_TWN_GEN1:
system.img.gz with /system RW workaround (needs extra config and SuperSU instead of Superuser) (see this post also)
Unbrick:
Stock Firmware RV01RC11 (copy on SD and flash from recovery)
Acer Iconia A3-A10:
A3-A10_RV05RC01_PA_CA:
stock system image
Your device not listed above?
Help us getting your device to work with the toolkit.
See this post how you can help.
Common
B1-A71 / B1-710 / B1-A710: Install this after rooting: Superuser App on Google Play Store
A1-810 / A1-811 / B1-711: Install this after rooting: SuperSU App on Google Play Store
Verify your root: Root Checker on Play Store
FAQ
Q: I'm stuck inside a bootloop after rooting!!!11
A1: The system.img.gz you applied, wasn't suiting to the firmware version installed on your tablet. Download latest Acer firmware update ( !!! if available !!!), copy it on a micro sd card, plug it into your Iconia, go to recovery by holding Volume up and Power button while device is turned off. Then choose apply update from sd card.
A2: If you cannot apply any Acer firmware, because you always get a partition error while installing, you should do a reboot after you get the error. A user reported that this made her/his device boot into Android again, showing the new version in settings -> info. Good luck
A3: If your device is really bricked you could try bring it back to life. Here you find help: link1, link2, link3, link4 (many thanks to Gilly10, drmad and Hamza91)
A4 (B1-A71, B1-710, B1-711 only): Unbrick
A5: If the A1 - A4 didn't help. Send back the device to Acer. Tell them you tried to apply an update from sd card and ended up in this bootloop. Sending device back to Acer over UPS is free. Good luck!
Q: Successfully rooted, but still no root after rebooting!
A: Have you installed Superuser App from Google Play Store?
(B1-A71 only)Q: Cannot update, always getting ERROR: - Invalid partition setting; 17: fat 238e8000:888e8000; Instalation aborted.
A: Download "Invalid Partition Error" Patch.
(B1-A71 only)Q: I applied update from RV05RC05 to RV05RC06 but still it shows RV05RC05.
A: There is no RV05RC06. It is the RV05RC05. It got on Acers Download section with a RV05RC06 named zip file. But the content is 100% equal to RV05RC05.
Q: Toolkit fails or crashes for any reason and I don't know what to do.
A: Run it again with parameter -d, e.g.: toolkit.exe -d and post the entire output here.
Q: Root from scratch on Linux doesn't work because of Error message: 'No such file or directory bin/posix/64/adb'
A: sudo apt-get install ia32-libs libstdc++6 libgcc1 zlib1g libncurses5 libsdl1.2debian
Q: Can i flash a custom recovery?
A: No, because bootloader is locked. You would brick your tablet.
Q: Are there Custom ROMs?
A: No, see answer above.
Q: Is my data wiped during root?
A: No.
Q: Do i lose root after factory reset or wipe date?
A: No.
Q: I get an error in Engineer mode entering telnet command.
A: If Swiftkey is installed / enabled try settings Google AOSP Keyboard as default.
Q: How can I start telnet server manually?
A: Try this.
What you can do with root:
Apply Supercharger V6 by zeppelinrox and significally speed up your tablet! [My small How-To]
Install Adaway, an ad-blocker for webbrowsers and apps containing ads.
Install ROM Toolbox and customize boot screen and other funny things.
Install Titanium Backup to Backup, Freeze, Uninstall any App and more.
Install Datasync to sync app data like save states between rooted devices.
What you can NOT do with root on these devices:
Change DPI
Flash Custom Recoveries
Flash Custom ROMs
Sources and Changelos @ github (thanks to nikagl)
Changelog:
v0.9.4
======
- Updated SuperSU to 2.46
- Removed Xposed APK
- Added Liquid S1 support!
v0.9.3
======
- Fix Xposed removal
- Wait longer for MTKLogger to press settings
- Add 811 and KK 810 and 811 to root from system.img
v0.9.2
======
- Removed Xposed till it works
- Add global for allatonce
v0.9.1
======
Added option to enable write access to external sdcard
Added comment for Xposed not working
Removed su delete command in invalid section
v0.9.0
======
- A1-811: Kitkat Support
- A1-xxx: Added proper su-binary
- Added timestamps
- Added descision for Superuser/Supersu
- Added selection for Xposed **not working yet**
- Added option to enable write access to external sdcard
- Added selection to continue automatically (also import the system instead of waiting for enter)
- Removed invalid quote and double exit command
- Added forward delete of characters to make sure Run command is empty
- Added some additional messages during the root process
v0.8.5
======
- A1-810: Fixed target directory for system image (no permissions for /cache directory since Kitkat)
- A1-810: Fixed root from scratch for Kitkat versions (thanks to Just_Another_N00b)
v0.8.4
======
- A1-810: Fixed root for Android Kitkat >= 4.4.2
- A1-810: Fixed abd devices id, changed sind Kitkat update
v0.8.3
======
- Fixed pulling system.img.gz from Windows
v0.8.2
======
- New: Supporting B1-720
v0.8.1
======
- A1-81x: Fixed missing read/write permissions for /system partition (thanks
to twu2!)
- All other devices: fixed missing path to su binary (thanks to arzakon.nn)
v0.8.0
======
- New: Pull system.img.gz from your tablet
- New: Supporting A3-A10
v0.7.8
======
- fixed Swap Internal to External for A1 and B1-710
v0.7.7
======
- Supporting Swap Internal to External for A1 and B1-710
- fixed bug in root from scratch: checking for /bin/su although it's not there
Full Changelog inside the Download.
Error "Permision denied"
entonjackson said:
Changelog:
v0.2.1
======
- Windows: Providing an .exe, so Python is no more needed for Windows users. But you could still use the Python script.
- Unix: Python3 compatibility fixes
v0.2.0
======
- supporting windows 64 and 32 bit (only for rooting with prerooted system.img.gz)
- Linux: added option to choose between 'Root from scratch' and 'Root from prerooted image'
- supporting all versions between python 2.7.4 and 3.3
v0.1.1
======
- supporting linux 64 AND 32bit
- instructions at the beginning
- make compatible to python 3.3
v0.1.0
======
- initial release, only supporting linux 64bit
Click to expand...
Click to collapse
Hi Thanks for your effor and sharing with us.
I got error "failed to copy system._image\system.image.gz to cache/system.image.gz , permission denied
can you give me solution.
thanks very much
cakadut said:
Hi Thanks for your effor and sharing with us.
I got error "failed to copy system._image\system.image.gz to cache/system.image.gz , permission denied
can you give me solution.
thanks very much
Click to expand...
Click to collapse
Windows or Linux?
edit: Ok i found the issue, I just fixed it and going to upload a new version this evening.
New version v0.2.2 is up.
entonjackson said:
New version v0.2.2 is up.
Click to expand...
Click to collapse
I thanks for your work.
I have one problem
failed to copy 'system_image\system.img.gz' to '/cache/system.img.gz': Permissio
n denied
Traceback (most recent call last):
File "easy_root_iconia_b1.py", line 724, in <module>
else:
File "easy_root_iconia_b1.py", line 26, in main
win_main(python3)
File "easy_root_iconia_b1.py", line 642, in win_main
out = p.stdout.readline()
File "subprocess.pyc", line 575, in check_output
subprocess.CalledProcessError: Command ' bin\windows\32\adb.exe push system_imag
e\system.img.gz /cache' returned non-zero exit status 1
Thanks for your futur help
sorry for my english
V0.2.2 still Error
entonjackson said:
New version v0.2.2 is up.
Click to expand...
Click to collapse
Dear Eaton,
after dowbload and run v0.2.2 , still found same problem.
No Progress bar during copy image.
and system shown
failed to copy 'system_image\system.img.gz' to '/cache/system.img.gz': Permissio
n denied
Traceback (most recent call last):
File "easy_root_iconia_b1.py", line 724, in <module>
else:
File "easy_root_iconia_b1.py", line 26, in main
win_main(python3)
File "easy_root_iconia_b1.py", line 642, in win_main
out = p.stdout.readline()
File "subprocess.pyc", line 575, in check_output
subprocess.CalledProcessError: Command ' bin\windows\32\adb.exe push system_imag
e\system.img.gz /cache' returned non-zero exit status 1
Note I am using windows 7.- 64 Bit
Regards,
I uploaded a new version where I added some commands that hopefully resolve the permissions issues.
The problem is, that I can't reproduce it.
Are you rooting the Iconia the first time? or did you already have root before?
Regarding the progress bar. It only appears when writing the system.img.gz
I have Windows 7 64 bit, btw.
entonjackson said:
I uploaded a new version where I added some commands that hopefully resolve the permissions issues.
The problem is, that I can't reproduce it.
Are you rooting the Iconia the first time? or did you already have root before?
Regarding the progress bar. It only appears when writing the system.img.gz
I have Windows 7 64 bit, btw.
Click to expand...
Click to collapse
Dear Enton,
Yes this is the first time B1 will rooting,
I will try again, and report to you,
Regards
cakadut said:
Dear Enton,
Yes this is the first time B1 will rooting,
I will try again, and report to you,
Regards
Click to expand...
Click to collapse
Dear Enton,
The Messages still same, I Attached the Error Pic.
Note :
Iconia B1-A71
ROM 16 GB
RAM 512 MB
Android Version : 4.1.2
Kernel Version : 3.4.0
Image Version : Acer_AV051_B1-A71_RV05RC05_WW_GEN1
Build Number : Acer_AV051_B1-A71_1.258.00_WW_GEN1
Regards,
cakadut said:
Dear Enton,
The Messages still same, I Attached the Error Pic.
Note :
Iconia B1-A71
ROM 16 GB
RAM 512 MB
Android Version : 4.1.2
Kernel Version : 3.4.0
Image Version : Acer_AV051_B1-A71_RV05RC05_WW_GEN1
Build Number : Acer_AV051_B1-A71_1.258.00_WW_GEN1
Regards,
Click to expand...
Click to collapse
I will try to fix it asap. The problem is, that I cannot reproduce it.
I assume that the chmod 777 /cache command that I do, before the adb push command fails with "Operation not permitted."
But this I still don't know how to fix. If someone knows, tell me!
error in v.0.2.3
Dear entonjackson,
thanks for your work and for the time you spend on it.
Unfortunately, I too have problems with the tool for Windows since version 0.2.0 and also with the latest version (0.2.3).
The error messages that I receive are identical (with the same line numbers) to those receiving cakadut in his last post.
I am trying to root Iconia for the first time.
I tried with Windows 7-32bit and Windows 7 64-bit.
My configuration:
Iconia B1-A71 8GB ROM, 512Mb ram
Android 4.1.2
kernel 3.4.0
Image version: Acer_AV051_B1-A71_RV04RC04_WW_GEN1
Build Number: Acer_AV051_B1-A71_1.174.00_WW_GE
I hope you can find the solution.
Thank you for sharing your work with us.
Just uploaded a new version. Could you please try again?
It's hard to fix for me, because I don't have the problem, so all I can do is try. Thanks for the patience!
****, I think i found the bug. Don't try 0.2.4 it won't work also.
foxterrier said:
Dear entonjackson,
thanks for your work and for the time you spend on it.
Unfortunately, I too have problems with the tool for Windows since version 0.2.0 and also with the latest version (0.2.3).
The error messages that I receive are identical (with the same line numbers) to those receiving cakadut in his last post.
I am trying to root Iconia for the first time.
I tried with Windows 7-32bit and Windows 7 64-bit.
My configuration:
Iconia B1-A71 8GB ROM, 512Mb ram
Android 4.1.2
kernel 3.4.0
Image version: Acer_AV051_B1-A71_RV04RC04_WW_GEN1
Build Number: Acer_AV051_B1-A71_1.174.00_WW_GE
I hope you can find the solution.
Thank you for sharing your work with us.
Click to expand...
Click to collapse
Ok, people. With pawitp's help I hopefully fixed the permissions bug.
The problem was, that i was trying to chmod the /cache directory directly from adb shell, which isn't possible. I forgot, that this needs to be done from telnet. So in 0.2.6 I'm setting permission with telnet. This should fix it!
Please report!
Good luck :fingers-crossed:
Dear ethon
hi ethon can u do tutorial video cause i can't found the directory for the "step 6 : go to go to connectivity -> CDS Inforamtion ->Network Utility " and Thnk You :good:
diskenz said:
hi ethon can u do tutorial video cause i can't found the directory for the "step 6 : go to go to connectivity -> CDS Inforamtion ->Network Utility " and Thnk You :good:
Click to expand...
Click to collapse
I will try to do a video tutorial, but it's very easy to do.
Download and install Ex Dialer & Contacts.
Launch the app.
Dial *#*#ENGMODE#*#*.
Swipe from right to left (to Connectivity). Then choose CDS Information and Network Utility.
There you paste this command: /data/local/tmp/busybox telnetd -l /system/bin/sh -p 1234
stell no thing happen maybe i must upgrade to pro version ???
diskenz said:
stell no thing happen maybe i must upgrade to pro version ???
Click to expand...
Click to collapse
No.
Try to dial *#*#3646633#*#*
Else I don't know... this should work in any case...
entonjackson said:
Ok, people. With pawitp's help I hopefully fixed the permissions bug.
The problem was, that i was trying to chmod the /cache directory directly from adb shell, which isn't possible. I forgot, that this needs to be done from telnet. So in 0.2.6 I'm setting permission with telnet. This should fix it!
Please report!
Good luck :fingers-crossed:
Click to expand...
Click to collapse
Thanks entonjackson,
unfortunately with version 0.2.6 I can not get the ADB connection with the tablet. The message it gives me is:
"Trying to Establish ADB Connection (If this hangs, ADB Connection failed. CMD Shell Close and open a new one) ..."
and remains so without making the connection.
If I run the command 'adb devices' in another command line session, the device is seen correctly (0123456789ABCDEF device),
but when I run the new version (0.2.6) of the tool, the message is what I wrote above.
Thank you for your patience.
Hello Guys I made a new program that roots your android phone Root With One Click it's named RootBox Changed To RootX
It's Easy To Use
1-Enable Usb Debugging On Your Phone
2-UnZip The File You Have Downloaded Them
3-Run [X.bat]
4-Hit Enter After You Read The Text
5-When It's Done Hit Enter
This Tool Is Supported By Windows Only
I Will Make It Supported By Linux Soon On Next Update
WARNING:This will void the warranty on your device. I am
not responsible for any damage to your phone
Changelog:
Updated Su Binary And SuperSU APP
Added Lollipop Files
Rebuilted Whole Thing From Scratch Also Written The X.Bat From Scratch
V2.45:
V1:First Relese
Download:
All In One Version Still Beta
Down In Attachments
Please Report Any Bugs
:laugh:
Credits:
Mohammad Nagib
Laith al Shishani
Enjoy
laith al shishani said:
Hello Guys I made a new program that roots your android phone Root With One Click it's named RootBox
It's Easy To Use
1-Enable Usb Debugging On Your Phone
2-UnZip The File You Have Downloaded Them
3-Run [RunRootBox.bat]
4-Hit Enter After You Read The Text
5-When It's Done Hit Enter
Enjoy
This Tool Is Supported By Windows Only
I Will Make It Supported By Linux Soon
WARNING:This will void the warranty on your device. I am
not responsible for any damage to your phone
Download:
GB Still Beta in Test:http://d-h.st/nUN
ICS JB KK Still in Test:http://d-h.st/3wO
Please Report Any Bugs
:laugh:
Click to expand...
Click to collapse
salam bro
i've tried it on a huawei G535-L11 (branded as Kestrel from EE) no luck, starting daemon successfully then just nothing, i hope you can make it work, as so far i've found nothing that can root this phone running on :jelly bean 4.3 . Emotion UI 2.0 Lite .Build number: V100R001C440B114
Kernel version: 3.4.0-g251524c
[email protected]#1
i hope this info helps in finding a way to root this device.
thanks
rophaq said:
salam bro
i've tried it on a huawei G535-L11 (branded as Kestrel from EE) no luck, starting daemon successfully then just nothing, i hope you can make it work, as so far i've found nothing that can root this phone running on :jelly bean 4.3 . Emotion UI 2.0 Lite .Build number: V100R001C440B114
Kernel version: 3.4.0-g251524c
[email protected]#1
i hope this info helps in finding a way to root this device.
thanks
Click to expand...
Click to collapse
Salam
Did you installed Huawei drivers if not install them ((google it))
Also unlock your bootloader ((again just google it))
I hope this will work
laith al shishani said:
Salam
Did you installed Huawei drivers if not install them ((google it))
Also unlock your bootloader ((again just google it))
I hope this will work
Click to expand...
Click to collapse
salam.
bootloader unlocked and drivers installed thats how i unlocked the bootloader, i've tried saferoot from samsung forum, it came as the kernel is patched !!.
i don't know any other way of rooting , few people here are having the same problem, i was wondering if you know how to root this tough phone.
salam bro
got it to work, this is what i got , i'll wait for a fix
[*] Press enter to root your phone...
Press any key to continue . . .
[*]
[*] Waiting for device...
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
[*] Device found.
[*] Pushing exploit...
2238 KB/s (1283460 bytes in 0.560s)
[*] Pushing root tools...
1298 KB/s (113036 bytes in 0.085s)
1925 KB/s (493036 bytes in 0.250s)
2542 KB/s (2278361 bytes in 0.875s)
open: Permission denied
pkg: /data/local/tmp/SuperSu.apk
Success
[*] Rooting phone...
[+] This may take a few minutes.
[-] Failure.
[*] Cleaning up...
[*] This Tool Will Be Updated When New Binaries Relesed
[*] Finish. Press enter to reboot and exit.
Press any key to continue . . .
rophaq said:
salam bro
got it to work, this is what i got , i'll wait for a fix
[*] Press enter to root your phone...
Press any key to continue . . .
[*]
[*] Waiting for device...
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
[*] Device found.
[*] Pushing exploit...
2238 KB/s (1283460 bytes in 0.560s)
[*] Pushing root tools...
1298 KB/s (113036 bytes in 0.085s)
1925 KB/s (493036 bytes in 0.250s)
2542 KB/s (2278361 bytes in 0.875s)
open: Permission denied
pkg: /data/local/tmp/SuperSu.apk
Success
[*] Rooting phone...
[+] This may take a few minutes.
[-] Failure.
[*] Cleaning up...
[*] This Tool Will Be Updated When New Binaries Relesed
[*] Finish. Press enter to reboot and exit.
Press any key to continue . . .
Click to expand...
Click to collapse
In This Case Try GB Version If Its not worked
open: Permission denied This Line Means Your Phone Has Other Security Thing Try Serching
I Rooted HTC Desire s (Boot loader Unlocked) and Galaxy S2 On Jelly Bean And Kitkat
You Are Out Of Luck :crying:
laith al shishani said:
In This Case Try GB Version If Its not worked
open: Permission denied This Line Means Your Phone Has Other Security Thing Try Serching
I Rooted HTC Desire s (Boot loader Unlocked) and Galaxy S2 On Jelly Bean And Kitkat
You Are Out Of Luck :crying:
Click to expand...
Click to collapse
tried out the GB version, same thing ,no luck
when i tried the softroot, it came out that the kernel is patched ??
Here wo go for another level...
First Soho Fireos 4 based customized rom
Instruction:
you need to unlock your bootloader first
install TWRP (i dont recommend twrp 3.x)
download:
twrp backup (new version):
2017-06-06--09-43-38_KTU84M_test-keys.part1.rar
This file has been shared with you on pixeldrain
pixeldrain.com
2017-06-06--09-43-38_KTU84M_test-keys.part2.rar
This file has been shared with you on pixeldrain
pixeldrain.com
now have fun
i hope you know how to install a twrp backup
extract the rar on your /sdcard goto twrp and restore backup for system
XDA:DevDB Information
pX-Fire Rom 4.5.5.2, ROM for the Amazon 7" Kindle Fire HD
Contributors
pxrave, spudowiar, ggow, hashcode
ROM OS Version: 4.4.x KitKat
ROM Kernel: Linux 3.4.x
ROM Firmware Required: 4.5.5.x
Based On: FireOS
Version Information
Status: No Longer Updated
Current Stable Version: 4.5.5.x
Stable Release Date: 2017-06-10
Created 2016-12-25
Last Updated 2017-06-10
reserved
reserved too
thanks for the rom, i ve already flashed it onto my soho.
is there a list with all the features of the rom? what did you remove and could you remove the amazon-ads too?
rom seems bugless so far and i ve installed xposed from solarwarez without a problem.
Many thanks for putting this ROM together - it breathes new life into my soho Kindle.
I've just finished installing/booting, ROM is working great. Any tweaking for power/speed would be awesome.
Cheers !
kindle hd 7 3rd generation
will this work with the above kindle. I've already rooted and rom'd my hdx 8.9, so am familiar with the language..its running 4.5.5.2 as well.
I also purchased a fastboot cable.
thanks
How do I root my soho..ive looked through so much today that my mind is spinning... I have a fastboot cable.. ive looked at various threads, but still not sure where to start. I would really appreciate some help, ive read through a document that goes through stages, but i seem to falter at the first hurdle. Anyway, I am not going to give up, just some bullet points as to what to do in what order would be great ...... thank you in anticipation...
wheres the link to the rom?
Smokeybear1987 said:
wheres the link to the rom?
Click to expand...
Click to collapse
I too would like to try this ROM. Does anyone have a link to it?
It is listed but not hyperlinked - First Soho Fireos 4 based customized rom
Thanks!
So I wiped the system partition prior to flashing, and now missing basic system elements for boot. Apparently this is a mod and not a ROM. So what's custom? I don't see anything different. What's "unlocked" exactly that wasn't already?
hey guys i have a twrp system backup for you for the latest update but i recommend the new Android 7.1.X based rom for our device
one last update: for amazon fire os will be uploaded this week
this project is discontinued
check the new rom here
How to root a Kindle Fire 7 (2013) soho
Hello everybody! I am new to xda so I hope I'm in the right place. I have tried to start a new thread about this but I coudl not so I am posting this here hoping to find an answer. Rooting a KF (2013) has proved to be quite challenging for me, also because I am dumb . Anyway I have tried to install the 'Permanent Root with Superuser' via Kindle Fire Utility 0.9.8 but I am not able to. I know that I am missing something but I am too dumb to understand what. I need the help of experts. So, I have run Kindle Fire Utility 0.9.8 and I got this:
HTML:
*****************************************************************
* Kindle Fire Utility 0.9.8 *
*****************************************************************
* This is now being maintained by awidawad *
*****************************************************************
* Credit goes to Vashypooh for original work *
*****************************************************************
1 Bootmode Menu
2 Install Permanent Root with Superuser
3 Install Latest TWRP Recovery
4 Install Latest FireFireFire
5 Extras (Requires Root)
0 Recheck Device Status
ADB Status: Online
Boot Status: Unknown
Please make a selection or hit ENTER to exit:
I have connected my KF Soho to the laptop through the factory cable and I have selected 1, and I got this:
HTML:
*****************************************************************
* Kindle Fire Utility 0.9.8 *
*****************************************************************
* This is now being maintained by awidawad *
*****************************************************************
* Credit goes to Vashypooh for original work *
*****************************************************************
1 Normal (4000)
2 Fastboot (4002)
3 Recovery (5001)
0 Recheck ADB/Fastboot Mode
ADB Status: Online
Boot Status: Unknown
Please make a selection or hit ENTER to return:
Then I have selected 1 and I got this:
HTML:
***********************************************
* Activating Normal (4000) *
***********************************************
The system cannot find the drive specified.
failed to copy 'files\nbmode' to '/data/local/nbmode': Permission denied
Unable to open /data/local/nbmode: No such file or directory
/system/bin/sh: /data/local/nbmode: not found
The kindle has been told to reboot in Normal Mode.
Press any key to continue . . .
If I select fastboot instead, I get this:
HTML:
***********************************************
* Activating Fastboot (4002) *
***********************************************
failed to copy 'files\fbmode' to '/data/local/fbmode': Permission denied
Unable to open /data/local/fbmode: No such file or directory
/system/bin/sh: /data/local/fbmode: not found
The kindle has been told to reboot in Fastboot Mode.
Press any key to continue . . .
In both cases my tablet reboots but checking with 'Root Analyzer' I can see that it is not rooted.
I have also tried rooting with Root_with_Restore_by_Bin4ry_v30 choosing the 1st option but I get this:
HTML:
======================================================================
= This script will root your Android phone with adb restore function =
= Script by Bin4ry (thanks to Goroh_kun and tkymgr for the idea) =
= Idea for Tablet S from Fi01_IS01 =
= (01.05.2013) v30 =
======================================================================
Device type:
1) Normal
2) Special (for example: Sony Tablet S, Medion Lifetab)
3) New Xperia Root by Goroh_kun (Xperia Z, Xperia V [JellyBean] ...)
G) Google Glass Mode (thx Saurik for the ab file)
x) Unroot
Make a choice: 1
Checking if i should run in Normal Mode or special Sony Mode
Please connect your device with USB-Debugging enabled now
Waiting for device to shop up, if nothing happens please check if Windows ADB-drivers are installed correctly!
adb server is out of date. killing...
* daemon started successfully *
remote object '/system/app/Backup-Restore.apk' does not exist
remote object '/system/bin/ric' does not exist
.
.
Above file not found warning ARE NOT ERRORS, it is intended to be this way!
Normal Mode enabled!
.
Pushing busybox....
5282 KB/s (1165484 bytes in 0.215s)
Pushing su binary ....
6985 KB/s (380532 bytes in 0.053s)
Pushing Superuser app
5148 KB/s (1500495 bytes in 0.284s)
Making busybox runable ...
.
Now unlock your device and confirm the restore operation.
Please look at your device and click RESTORE!
If all is successful i will tell you, if not this shell will run forever.
Running ...
At this point, my kindle fire displays a screen where I have to choose between 'Do not restore' and 'Restore my data' and I chose 'Restore my data' but my tablet does not reboot at all and the runme.bat file keeps running forever. I have also tried not to press anything at all on the 'Do not restore/Restore my data' screen and I get this:
HTML:
Successful, going to reboot your device in 10 seconds!
Waiting for device to show up again....
Going to copy files to it's place
mount: permission denied (are you root?)
You can close all open command-prompts now!
After reboot all is done! Have fun!
Bin4ry
Press any key to continue . . .
My tablet actually reboots but checking with Root Analyzer I still see the message 'No, your device is not rooted'. What should I do? :'( Ask me all the questions you need and I'll do my best to answer them. Also, please keep in mind that I am not technical therefore explain me things as you would explain them to a quite smart baby Thanks for your help!
Also, I'll write here more details about my device if it is of any help for you guys:
Device model: Kindle Fire HD (3rd generation)
Year: 2013
Bootloader: Uknown
Board: soho
Device: soho
Model: KFSOWI
OS: Fire OS 4.5.5.3
Try kingroot app
Already tried but it could not root
ssurell said:
Try kingroot app
Click to expand...
Click to collapse
Thanks for your answer. I have tried Kingroot and iRoot but they could not root my tablet. I have tried downloading root_script.zip from the following link: https://forum.xda-developers.com/showpost.php?p=47881661&postcount=1
and I get this
HTML:
======================================================================
======================================================================
Welcome to Kindle Root Utility
Special Thanks to:
Moronig
jcase
fi01
======================================================================
======================================================================
WARNING THIS WORKS ONLY WITH KINDLE HD 7" 2013!
======================================================================
======================================================================
Please connect Device with enabled USB-Debugging to your Computer!
Device connected. Pushing files...
5105 KB/s (104564 bytes in 0.020s)
46 KB/s (188 bytes in 0.003s)
4394 KB/s (89968 bytes in 0.019s)
Changing permissions...
Executing Exploit (could take some minutes, be patient!)
Hit ENTER to continue
Press any key to continue . . .
Device detected: ()
Try to find address in memory...
Attempt msm_cameraconfig exploit...
Detected kernel physical address at 0x80008000 form iomem
Attempt fb_mem exploit...
Detected kernel physical address at 0x80008000 form iomem
Failed to open /dev/graphics/fb0 due to Permission denied
You need to manage to get remap_pfn_range addresses.
Failed to get prepare_kernel_cred addresses.
Failed to get commit_creds addresses.
Failed to get ptmx_fops addresses.
() is not supported.
Failed to setup variables.
Press any key to continue . . .
When I press any key to continue the runme.bat closes down but my does not reboot rooted. I am going to throw it out of the window hahaha
hello guys i updated the links. have fun or create mirrors. thanks