Related
Please refer to this post before upgrading Your DHD
http://forum.xda-developers.com/showthread.php?t=879525
If You update to latest version You will NOT be able to boot custom HBOOT!!!
Here is guide how to downgrade Your DHD if You updated to latest version by mistake
http://forum.xda-developers.com/showthread.php?t=905003
This is complete guide for all HTC Desire HD owners who want's to root their devices and install custom recovery image.
FLASH THIS AT YOUR OWN RISK, I AM NOT RESPONSIBLE IF ANYTHING GOES WRONG
I have collected and summarize few guides on this forum in order to collect all informations on one place.
Check following threads for additional informations.
Please post all bug's and issues related to DHD scripts to sfjuocekr thread below.
http://forum.xda-developers.com/showthread.php?t=835746
http://forum.xda-developers.com/showthread.php?p=9183483
Summary:
1) Download Paul's Visionary+ tool (I have used version r12) (google removed this app from market) so You will have to download it from Paul's website.
This tools enables root and removes new HTC protection.
2) Install engineering version of HBOOT to get S-Off (HTC bootloader, something like BIOS for Your PC)
This step is optional and it's not required in order to flash custom ROM's on Your DHD but gives You more freedom with Your device.
3) Install custom recovery image (recovery is special program which is invoked from HBOOT
in order to flash ROM onto Your device.
Detailed description:
1) Download Paul's Visionary+ tool
1.1) Click here to download http://android.modaco.com/content/h...722/10-nov-r12-test-visionary-one-click-root/ or download it from here http://forum.xda-developers.com/attachment.php?attachmentid=447543&d=1290501865
1.2) Install Visionary+ on Your DHD
1.3) Run it, enable "Set system r/w after root
1.4) Click "Temproot Now!" - Wait until it's finished
1.5) Click Attempt Permroot Now!
1.6) DHD automatically reboot's
To test that everything went fine download from market application "terminal emulator"
run it, type su
If You get after that sign # it mean's that everything went fine.
Time for next step!
2) Install engineering version of HBOOT to get S-Off
2.1) Download sfjuocekr DHD script for flashing HBOOT from here
http://forum.xda-developers.com/showthread.php?t=835746
2.2) Unzip it and copy it to Your SDCard (It's important that You have on Your SDCard root directory with name DHD and all files inside this directory. Rename DHD-smart folder on Your SDCARD to DHD.
2.3) Run Terminal Emulator
2.4) Type su
2.5) Type "sh /sdcard/DHD/check
(Please be aware that You have to type "sh" in front of command)
2.6) If everything went OK type
sh /sdcard/DHD/backup
2.7) If this also went OK proceed with
sh /sdcard/DHD/hboot
This command will install engineering hboot which have S-Off turned off.
3) Install custom recovery image
3.1) Since ROM manager now officially support's Desire HD, we will use it to download and install custom clockwork image.
3.2) Run android market app on Your DHD and download and install ROM Manager app from market.
3.3) Download and install ROM manager.
3.4) Run ROM manager and select first option (Flash ClockWorkMod Recovery).
3.5) Wait until ROM Manager say's that installation went successfully (Current version of ClockWorkMod is 2.5.1.3)
3.6) After installation tap in Rom manager option Reboot into Recovery to test that everything went well.
3.7) DHD should reboot in clockwork recovery manager.
Enjoy.
This afternoon I've done what you describe in your guide and can say that everything works fine on my DHD !
Another Desire HD free from chains
Alright this probably sounds disgustingly noob but my phone isn't going into bootloader mode x_x. I've rooted the phone and followed the S-OFF procedure and no luck... Any ideas?
EDIT: Don't worry issue resolved. I had to end up using adb shell reboot bootloader. It's still a bit weird though, as to why I can't do this without adb...
Did You manage to install clockwork successfully?
zexbig said:
This is complete guide for all HTC Desire HD owners who want's to root their devices and install custom recovery image.
(I hade run into the strange problem for which I'm not sure is it problem with my PC or DHD, each time when I connected my DHD via USB cable my SDCard was automatically mounted as Disk Drive instead of just being in "Charge only" mode. I resolved this by removing back cover and ejecting SDCard and inserting it again while phone was operational, which is very unsafe thing to do!).
Enjoy.
Click to expand...
Click to collapse
known issue : can't remember the app, double-twist I think, it auto mounts SD card. Do you have that? Deselect or uninstall.
Yup looks like it. It's saying ClockworkMod Recovery v2.5.1.2. The only issue is, I can't select any of the options lol
EDIT: don't worry also solved that
Just another question though, using NANDROID am I able to backup my current ROM? I'm with Vodafone australia and I want to be able to restore this ROM (for warranty purposes).
crypticc said:
known issue : can't remember the app, double-twist I think, it auto mounts SD card. Do you have that? Deselect or uninstall.
Click to expand...
Click to collapse
Hmm probably something which come with original HTC ROM, I didn't install anything similar to that. But will double check..
Sylpher said:
Yup looks like it. It's saying ClockworkMod Recovery v2.5.1.2. The only issue is, I can't select any of the options lol
EDIT: don't worry also solved that
Just another question though, using NANDROID am I able to backup my current ROM? I'm with Vodafone australia and I want to be able to restore this ROM (for warranty purposes).
Click to expand...
Click to collapse
Backing up current ROM and restoring is primary function of nanodroid
zexbig said:
Backing up current ROM and restoring is primary function of nanodroid
Click to expand...
Click to collapse
Haha just making sure . I didn't want to lose my current ROM because Vodafone doesn't honour warranties on phones that have been modified in this manner.
Also I forgot altogether to say thanks lol! Thanks for the simple and straightforward guide
Hi, Does anyone have 10/Nov r12 test: VISIONary + one click root and can send it to me? I can't seem to be able to download it anywhere! Pages are down
clockwork installed can't select
HUGE thanks for writing these instructions. They worked perfectly.
rolphez said:
Hi, Does anyone have 10/Nov r12 test: VISIONary + one click root and can send it to me? I can't seem to be able to download it anywhere! Pages are down
Click to expand...
Click to collapse
Here you have the VISIONary r13, I've rootet successfully with this version.
just followed the guide and im backing up my phone now. Thanks very much.
help
3.5) Download test clockwork image from
and put it in C:\android-sdk-windows\tools\ directory.
3.6) Reboot Your phone into bootloader (Turn off phone, and press VOLUME DOWN and HOLD IT, and it the same time PRESS POWER and hold it until You get bootloader screen.
Then scroll with Volume down button on to fastboot and press power, connect USB cable and wait until android fastboot interface is installed.
3.7) Run cmd and cd to C:\android-sdk-windows\tools\
3.8) type
fastboot flash recovery clockwork.img
3.9) If everything went OK You will get following message:
C:\android-sdk-windows\tools>fastboot.exe flash recovery clockwork.img
sending 'recovery' (4914 KB)... OKAY
writing 'recovery'... OKAY
3.10)This means that You are almost finished. Type
C:\android-sdk-windows\tools\fastboot.exe reboot-bootloader
to reboot Your phone in bootloader mode.
When You are back in bootloader mode select recovery and phone will reboot in Clockwork recovery mode, since DHD does not have optical trackball just scroll 3 times trough menu (just press volume down button until You get message "back menu button enabled".
Enjoy.[/QUOTE]
hi
thanks for the guide.
done all the steps upto 2 everything good
cant get the step 3 , can you explain more deeply.
downloaded all the files , kept on my pc . do i need to move andriod -sk folder to sd and then rebot my phone . as you said to boot in bootloader but wen i press and hold power and volume down nothing happens
need help plz
another question how can i keep my original rom backed up , with which app?
I also cant get into the bootloader by pressing volume down when powering on. Also tried through shell (I think?, is the commands 'su' and then 'reboot bootloader'?) and got a 'not permitted'.
solved
I had to end up using adb shell reboot bootloader
its backing up my phone now
than everybody
where the backup will be saved , name of the files , so i can save them . and i f anything go wrong how to restore the original files?
help
after doing step one can i remove Visionary+ from phone?
any pros of keeping it?
You can remove visionary, only cons is that visionary have unroot option if You want to revert back this maybe usefull.
Sent from my Desire HD using Tapatalk
OP
please help me out here:
i always get this from cmd:fastboot not recognized as an internal or external command and nothing happens! any ideas please.
thank you
Many people seem to be having a lot of trouble flashing recoveries for their Ideos so I figured I would write this thread because I haven't found any other guides for flashing U8150 recoveries.
Method 1
1. Install Terminal Emulator from the market.
2. Install Root Explorer from the market.
3. Download the recovery of your choice and copy the recovery.img to your sd card. (if its not named recovery.img rename it)
4. With Root Explorer, navigate to where the recovery is and copy it to /system/bin/ (remember to select mount as R/W first in order for it to copy.)
5. Open Terminal Emulator and enter the command "su" (without the quotes)
6. After that enter the command "flash_image recovery /system/bin/recovery.img" (again without the quotes)
7. That's it, the recovery has been flashed. Reboot in recovery to confirm.
8. Once you've confirmed the recovery flashed properly remember to delete the recovery.img from /system/bin/ (using root explorer, and mount as R/W)
Method 2
I find this method much easier because you don't have to go through the trouble of installing drivers. Also you don't need to connect your device to your PC. Your device needs to be rooted though. If your device isn't rooted simply download z4root from the market and root it.
1. Download and install ROM Manager from the market.
(If you simply want to flash the latest working ClockworkMod Recovery and not an older version or UltraJack skip to step 6.)
2. Navigate to the folder /clockworkmod/download/mirror.sea.tdrevolution.net/cm/recoveries/ (create the folders if they are not already there)
3. Delete any files in that folder.
4. Download the recovery you want to use from the recovery links below. Unzip the file. Rename the "recovery.img" file to "recovery-clockwork-3.0.2.4-ideos.img". (See note below)
5. Copy the renamed "recovery-clockwork-3.0.2.4-ideos.img" into the recoveries folder (/clockworkmod/download/mirror.sea.tdrevolution.net/cm/recoveries/)
6. Open ROM Manager and select Flash ClockworkMod Recovery. It will bring up a list of devices, just scroll down until you find Huawei U8150 Ideos and select it.
7. ROM Manager will flash the recovery image for you and you're done.
Now you have a working recovery. To test select Reboot into Recovery from ROM Manager.
Since you are renaming the recoveries remember to keep track of which recovery is currently in the recoveries folder.
Note: recovery-clockwork-3.0.2.4-ideos.img is the name of the latest ClockworkMod Recovery in rom manager at this time (28/04/2011). If it is updated and I haven't updated the thread, change the name of the recovery to the latest version.(i.e if the latest recovery is ClockworkMod 3.0.2.5, rename the img to recovery-clockwork-3.0.2.5-ideos.img instead of recovery-clockwork-3.0.2.4-ideos.img)
Method 3
Installing Drivers
Windows 7:
Download and install PDANet. That should install the drivers for you.
Alternatively, you could download the drivers and install them manually. First download the drivers for your OS from here.
Drivers Windows 32-Bit Mediafire Multiupload
Drivers Windows 64-Bit Mediafire Multiupload
Connect your device(you don't need to turn on USB storage) then open device manager. Right click on your device and select properties, select the hardware tab and then select properties. Select the drivers tab, then select Reinstall/Update Driver. Choose the option (Browse my computer for driver software) and select the drivers you just downloaded. (Extract the zip file first)
MacOS
Download and install PDANet. That should install the drivers for you.
Linux
Follow this guide by bloodychaos to get ADB working.
Flashing Recovery
1. Once you have the drivers installed download the recovery of your choice from the links below.
2. Extract the zip file and open the folder.
3. Turn off your phone.
4. Connect your phone to your PC.
5. Reboot your phone in bootloader mode. (Turn it on while holding the Volume Down button and the End(Red) Key.)
6. Run the install-recovery file/script for your OS found in the extracted recovery folder.
7. Once it flashes your phone should reboot.
N/B If you have trouble with the drivers or any other problems try Method 1.
Now you have a working recovery. To test turn off your phone, then turn it on while holding the Volume Up Key and the Green(Call) Key.
Recovery Links
ClockworkMod 3.0.2.4 (by marcnvidic)
Download Mediafire Multiupload XDA Thread
UltraJack 6.2.2 (by Ultrakiller)
Download Mediafire Multiupload XDA Thread
ClockworkMod 3.0.1.(by udK)
Download Mediafire Multiupload
Credits
marcnvidic, Ultrakiller, udK for making the recoveries. bloodychaos for the Linux ADB guide. Koush for ROM Manager. f1ng3r for pointing out the terminal emulator method.
All other Ideos devs who've helped me along the way because I picked up a lot of this info from random threads.
Reserved for future use.
Thnx, very informative
No Huawei U8150 Ideos on the list of ClockWorkMod
wachw said:
6. Open ROM Manager and select Flash ClockworkMod Recovery. It will bring up a list of devices, just scroll down until you find Huawei U8150 Ideos and select it....
Click to expand...
Click to collapse
I've just downloaded Rom Manager Premium c4.2.0.2 (latest) from the market and i can't find the Huawei U8150 Ideos on the list of ClockWorkMod
Am i missing something? I copied the image file to the directory specified.
cheers,
Simon
sayo9394 said:
I've just downloaded Rom Manager Premium c4.2.0.2 (latest) from the market and i can't find the Huawei U8150 Ideos on the list of ClockWorkMod
Am i missing something? I copied the image file to the directory specified.
cheers,
Simon
Click to expand...
Click to collapse
For some reason the ideos does not appear on the list, I have no idea why, you might have to try one of the other methods to flash a recovery.
wachw said:
For some reason the ideos does not appear on the list, I have no idea why, you might have to try one of the other methods to flash a recovery.
Click to expand...
Click to collapse
Thanx for the quick reply, i ended up using method 3.
Just one thing about method 3, the batch file doesn't exist in the ClockworkMod 3.0.2.4 (by marcnvidic) link as it's only an .img file. So i simply downloaded the ClockworkMod 3.0.1.(by udK) zip file, and replaced the image with the newer 3.0.2.4 after unzipping it.
Thank you for the guide, i've successfully flashed clockworkmod, and backed up the phone. now all i have to do is choose a ROM.
which ROM do u suggest???
cheers,
Simon
sayo9394 said:
Thanx for the quick reply, i ended up using method 3.
Just one thing about method 3, the batch file doesn't exist in the ClockworkMod 3.0.2.4 (by marcnvidic) link as it's only an .img file. So i simply downloaded the ClockworkMod 3.0.1.(by udK) zip file, and replaced the image with the newer 3.0.2.4 after unzipping it.
Thank you for the guide, i've successfully flashed clockworkmod, and backed up the phone. now all i have to do is choose a ROM.
which ROM do u suggest???
cheers,
Simon
Click to expand...
Click to collapse
That was the official link from marcnvidic, the multipuload & mediafire mirrors should have the batch files. Anyway, for the rom I would suggest FUSIONideos or Dronix 0.4, there's a poll somewhere on this forum and those are the most popular, Gingerman V4 is also pretty good but I wouldn't suggest it as your first rom because its still relatively new and is still being improved so it isn't perfect as a daily use rom yet. I switch btw fusion & gingerman, but I can tell you fusion is pretty stable. One thing to note however, if you are not using gingerman or another cyanogenmod port, I would suggest using clockworkmod by udK as your recovery, cwm 3.0.2.4 has some issues making backups of other roms.
Mate, I'm loving this
So far i've flashed CM6.1 port, Fusion, and Dronix 0.4! hehe i'm addicted now! Right now i'm back to CM6.1, but will try Gingerman V4 soon
Thanx for your help mate, you're a champion.
EDIT: thought i'd explain why i'm on CM6.1. Reason being is that I even though i think Fusion is the better one so far, I can't seem to have a solid 3G connection.
I'm from Sydney Australia, and with Optus. The APN seems to be correct and all, but the phone keeps switching from 3G to H.
tq for this information...i have done it
thanks !!!!!
I'm having a bit of trouble.
I was trying method 2 and clicked the wrong phone model. I went to change it but found that "Huawei IDEOS U8150" is not listed. Now I cannot access my recovery menu, and cannot install clockwork recovery. How would I fix this? I've been searching for hours and only found ways to remove it via the recovery menu.
Everything is functioning fine so it's not a big problem, I just can't get to the recovery menu/boot loader.
Also, I attempted method 1 because it doesn't involve the use of the recovery menu. It says, "flash_image: not found" when I type the command.
Nevermind, put about another hour into searching. Thank you so much for this guide it helped me alot.
I installed ROM Manager and pressed "Flash ClockworkMod Recovery".
It downloaded some files and flashed the Mod.
(I have my u8150 rooted using SuperOneClick)
Now it shows that my ClockworkMod Recovery version is 3.0.2.4
BUT the problem is that:
1>If I press reboot into recovery, the phone reboots and I end up staring at the IDEOS logo for ... like ever.
2>I pressed Backup Current ROM and after giving it a name (Stock ROM), I pressed OK and again the same result.
3> I found on the internet that to go into the recovery mode I need to press the SEND (green button) and the Volume UP together and then press Power.
I did it, even held the three buttons in the next try... but sadly every time the phone got stuck and I ended up looking at the IDEOS logo.
and the only way to get the phone working again was to take out the battery and press Power. (the phone itself is running fine)
PLz kindly help me out on this.. am I missing something??
Thnx
That means the recovery didn't flash correctly. Are u sure u selected the right phone from the rom manager list. Try flash recovery again. But first u need to delete everything in the clockworkmod/download directory on the sd card. Or if you know how to, just delete the recovery image in that folder.
yes I selected the corret phone i.e. Huawei u8150 Ideos
i deleted everything in the clockworkmod/download directory on the sd card
re-flashed..
still the same problem
btw.. during flashing, twice I got a pop-up asking me to either "force close" or "wait" and I pressed "wait" both times.
P.S. I just noticed after removing the battery that it says the model of my phone is U8150-D. I wonder what the "D" stands for?
It shuld not be force closing. Maybe rom manager has a problem. Try reinstalling it. If that doesn't work I suggest trying one of the other methods to flash the recovery.
ok so ive just tried Method 1 and followed every step... and the funny thing is that when I enter the following command in terminal emulator:
flash_image recovery /system/bin/recovery.img
.. it says
flash_image: not found
lol
now im downloading ultrajack
Update:
Ive tried Method 3:
and for 10 minutes now.. my command prompt is still showing this message:
< waiting for device >
:-(
For method 3 try running the bat file first then when it shows you the waiting for device message turn on the phone in bootloader mode.
just did as you said, i turned off the phone.. ran the bat file, when it said waiting for device I plugged in the phone (battery charging started), then I pressed power while holding Red and Volume Down...
the result is the same..
(the same was the result when running ultrajack)
>im just wondering... do I need to install any kernel or something before doing this??
>also I noticed that the CWM's recovery.img that I got from this forum is 3.94MB, while the one I downloaded through the Rom Manager was 3.71MB (on both tries).
P.S. how do I completely remove CWM and its files? so i can start the process fresh. I read at some forum that there is some file related to this called update.zip... whats that?
(Sorry for being a bother and thnx for your help)
UPDATE !!!
Its done... its finally done. Yattaaaaa!!!
ok so here is is what I did....
>I deleted everything in the clockworkmod folder like you once mentioned before.
>You said that while flashing I shouldn't be getting a pop-up that asks me to either force close or wait.
>So I had a hunch that the popup that appeared during the flashing might have been caused due to the screen timeout set at 30 sec (i mean a clash of two processes)
>So, i set the screen timeout to 30 minutes (hehe) and pressed Flash ClockworkMod Recovery from the Rom Manager.
>It flashed without any pop-ups and it successfully booted into recovery mode (and the first thing I did was to backup my phone)
Once again thnx for your support wachw.
... and if you don't mind can you help me with one more thing (if it's convenient for you)... plz guide me how to install multitouch for my phone provided here (coz nobody at that thread has been generous enough to guide me ;_; )
http://forum.xda-developers.com/showthread.php?t=1014183
[i have downloaded the multitouch patch and the complied kernel, plz guide me on what to do next. thnx ]
Sorry about the delay, been busy, but, if you send me the link to your provider's rom I can make a multitouch version for you. Why don't you want to install a custom rom?
here is the link to my provider's rom:
http://webftp.myppc.it/index.php?dir=Ideos/ROM/
direct link
http://webftp.myppc.it/index.php?dir=Ideos/ROM/&file=U8150 V100R001C230B828SP02(Pakistan Ufone ).rar
custom rom, hmm.. well ive heard about them but for now i want to see how much can the stock rom be modified xD
btw is it really possible to edit the rom and remove the simlock
someone here says so:
http://forum.xda-developers.com/showthread.php?t=850110&page=5
Acer Liquid E1 All in One thread; Rooting, Recovery and Kernel, Roms and Unbricking
Disclaimer
We are Not responsible if you brick your device or lose your data. Rooting is done at own risk and we are not the ones to blame for messing up your phone. When you rooted this phone, you lost your warranty. Vache and Paugustin provided a way to restore your device to stock in case you mess up, and I've made a tutorial on that which you can find at the beginning of this thread.
If you have any question, feel free to reply, or leave a PM. I am always open for suggestions!
Of course, if you get stuck somewhere in the process, tell us! but don't forget to tell us exactly what you did, what the screen shows, and what files you used.
Here is a simple overview of the thread for you so you can quick acces all posts:
Rooting
http://forum.xda-developers.com/showpost.php?p=39293790&postcount=2
Click to expand...
Click to collapse
Reverting back to stock rom/ unbrick your device
http://forum.xda-developers.com/showpost.php?p=39293936&postcount=3
Click to expand...
Click to collapse
Custom rom section
http://forum.xda-developers.com/showthread.php?t=2226375
Click to expand...
Click to collapse
The user iulian1421 has been kind enough to provice me with a zipped Nandroid backup. This means that we now have acces to both dual-sim, and single-sim firmwares. If you want to give it a try, flash the CWM recovery, unzip this file and place it in SD card. apply the backup through CWM restore option.
mega.co.nz/#!V0YDXTKA!I2H1biA_NzBzFUbORHv020gzpQpcZzl5XcroeTQ Dpbg
Click to expand...
Click to collapse
People who contributed in this project, and helped me out big time :highfive:
Brick3d
Vache
Paugustin
iulian1421
Master Shifu Yuweng
Pratikmore
Socr4te @ Needrom
Rooting
Rooting
So, you want to root the phone? Alright let's get you started!
1. Download this file. This is a .zip I made which contains all the files you need to root the phone. It might be confusing at first, but you'll be doing this with your eyes closed after 2 times.
http://www.mediafire.com/download.php?fxqckmx2jx6b573
2. Extract the files into a folder you like (mine is Desktop/ROOT, so that i cant forget where it is)
3. Shut down your phone, pull out the battery. next, plug it into your pc with the battery still out. open device manager, and youll see
* unknown device
*mtk 57*** preloader with (!) triangle.
4. Manually install the drivers for that device which you can find in the folder you extracted. Be sure to install the drivers provided for your OS!!!
5. After installing, put the battery back in your phone and unplug it for now.
The actual rooting process
1. Open the folder > Flash tool > run Flash_Tool.exe
2. Click scatter-loading, and select the MT6577_emmc_aa66_Acer_AV051_V360_1.003.00_WW_GEN1.txt file. (you can find that in the scatter folder)
3. From the list, check the mark at Recovery. (All other marks should be UNCHECKED)
4. Double click recovery, and select recoE1-superuser.img from the Images folder.
5. Click download, and confirm the popup with yes.
6. With the power of the phone still off, connect it to usb
7. Next you will see the progress bar turn red, then yellow, and if it's finished correctly you will see a green popup ring appear in the flash tool.
8. remove the usb cable from the phone, and boot into recovery mode (volume + and power buttons)
9. Go to the recovery, and you will be presented an android triangle! dont worry, just press volume + once.
11. Now highlight the reboot system now, and you're all done
12. Give a thanks, and subscribe to this thread. If i get the permissions from them I will update this thread with the new creations of Vache, and Paugustin, as well as my own.
#Update 2#
Vache has released a CWM (v 6.0.2.8) onto his website. Flash this one like you would when flashing any boot img (see tutorial for that)
http://www.vache-android.com/Smartphones/Liquid%20E1/recovery/CWM-6.0.2.8_Acer-E1.img
Release TWRP recovery, the swipe to action is still not working, waiting for a fix!
http://www.vache-android.com/Smartphones/Liquid%20E1/recovery/TWRP-2.3.2.3_Acer-E1.img
Give this guy a big thanks for the awesome work he is doing!!!
Revert back to stock rom/ Unbrick device
Unbricking the phone or revert back to stock rom
This guide is written with the intention of being as noob friendly as possible. I know some things around here are a bit hard to understand, so I wrote it like this just so that everyone could understand.
First of all, you want to download and install the drivers from the acer site:
http://www.acer.nl/ac/nl/NL/content/drivers
* you might need to look up your phone model again here, which is V360 (you can type that into the model name bar and it will redirect you to the correct
page).
Once downloaded you want to download these 2 files:
Here is the ROM : https://truck.it/p/NSKm45nxjh
Here is ADB+ Fastboot: http://d-h.st/592
Once you've got both files downloaded (main rom is 600mb), unzip the rom first. You will get 2 folders:
* Database_Acer_AV051_V360_1.003.00_WW_GEN1
* Images
The Images folder is what we need most. You want to extract all contents from the ADB/fastboot zip file into the Images folder.
After you've done that (and assuming the drivers you installed are working correctly, a reboot of your pc might be required for that), shut down the phone.
Plug your phone into your pc with a USB cable (pretty obvious right?)
Hold the Volume + and Power buttons until it vibrates and shows you a nice little recovery menu. From here you need to pick the 'Fastboot'.
(Volume + is scrolling through menus, and volume down is selecting!!!)
After you've done that, you are shown the acer logo, with a small line of text underneath it which you can't completely read. Don't worry, its normal and if
the drivers are installed correctly it'll work anyways.
Now that you have set everything up you're ready to flash everything back to stock!
Once inside the folder containing the img files and adb/fastboot and their .dll files, you need to open a cmd in that window:
shift+ right mouse button > open command window here.
in the cmd screen now type this:
* fastboot flash boot boot.img - wait until it's finished. you will get an error or completed message in
the cmd screen.
* fastboot flash recovery recovery.img - should be done in a few seconds.
* fastboot flash system system.img - this will take long, because as you can see its over 600mb, don't give
up, first time it took me about 3 minutes to finish.
After flashing the system.img is done, wait for 10 seconds, then pull out the usb cable. Remove the battery from the phone, reinstert it, and boot it as usual. This should have flahsed your phone back to the stock JB Acer provided, including all apps and bugs that came with it.
great
i have rooted Acer Liquid E1, great, i waiting for next users happy we need big community for this big phone THX
Re: [GUIDE] Acer Liquid E1 All-In-One Guide
It's growing and I'm sure we'll see some nice stuff for this phone
Envoyé depuis mon V360 avec Tapatalk
atm I'm playing around with build.prop tweaks until Vache brings us init.d support and a flashable zip file for roms, I cannot make one. I also have succesfully installed Bravia Engine from sony, looks great!
Hi I did exactly as instructed and got all steps done right but I am not rooted.. Any idea why Thanks
Just tell us what happened. If you're not rooted it means something did not work and that is probably because you missed something. Check all the steps and try again. If you have an error message tell us what and when.
rizanx said:
Hi I did exactly as instructed and got all steps done right but I am not rooted.. Any idea why Thanks
Click to expand...
Click to collapse
Hmm, can you check up on the drivers? what does it show when you plug in the phone while the power is off?
I have no idea wether you're new to rooting etc or not, but have you checked these 2?
ADB Debugging on: settings > options for developers> turn on adb debugging
unknown source on: settings > security > turn on unknown sources
I believe those 2 settings are your problem
Brick3d said:
Hmm, can you check up on the drivers? what does it show when you plug in the phone while the power is off?
I have no idea wether you're new to rooting etc or not, but have you checked these 2?
ADB Debugging on: settings > options for developers> turn on adb debugging
unknown source on: settings > security > turn on unknown sources
I believe those 2 settings are your problem
Click to expand...
Click to collapse
Thanks for the reply man. I figured it out. I had to go to recovery and then reboot from there. One I did that I am rooted. Now hopefully some custom rom will appear.
hehe good to know! I was wondering if I had maybe forgotten something in the tutorial.. if you're a benchmark believer, im making a rom as of now, got the antutu scores up from +-2400 to -+2800.
Edit: I've gotten it up to 3k, quite proud of that!
I still can't make a real flashable rom because there is no fully functional CWM for this device yet.
I want to make a camera mod atm, but there is no media_profiles.xml present...anyone knows where its at or what the right file is?
Hi all
I have made cwm recovery 6.0.2.8 for this device on italian forum ----> Here
I think not bugs (i hope)
BackUp OK
Restore OK
Wipe OK
Mount USB Windows OK
Mount USB Linux OK
If you find bug i'm here for try to fix.
Bye all.
I tested erlucky CWM with Vache and it works well !
erlucky said:
Hi all
I have made cwm recovery 6.0.2.8 for this device on italian forum ----> Here
I think not bugs (i hope)
BackUp OK
Restore OK
Wipe OK
Mount USB Windows OK
Mount USB Linux OK
If you find bug i'm here for try to fix.
Bye all.
Click to expand...
Click to collapse
can you upload it on here in attachement please? I cant download it I think...
It's on Vache ftp : http://vache-android.com/Smartphones/Liquid E1/recovery/CWM-6.0.2.8_Acer-E1.img
To flash you just have to use the exact same method used for rooting. Just use this .img instead of the rooting recovery.img
Re: [GUIDE] Acer Liquid E1 All-In-One Guide
Ah yes ive downloaded that one alteady. I cant flash any images every time i get an error or it says completed but nothing is changed in system...
Sent from my V360 using xda app-developers app
It happened to me once, the flashing went ok but the recovery would not start at all. I flashed from another computer and it went OK.
Re: [GUIDE] Acer Liquid E1 All-In-One Guide
No its working properly, everything is fine except for that...
Sent from my V360 using xda app-developers app
Brick3d said:
No its working properly, everything is fine except for that...
Sent from my V360 using xda app-developers app
Click to expand...
Click to collapse
My Recovery is another cwm 6.0.2.8, i have porting from bruno martins basis for MTK 65xx emmc/mtd.....
I have added usb Mount file into ramdisk.
I'm Lucky76 in other forum (italian and Modaco)
With the help of the ever awesome Team Win, and specifically a developer named Dees Troy we now have a working recovery for the I9505G.
[Update 8/22/2013]: Thanks to ClockworkMod developer gweedo767, the official CWM Recovery for I9505/jfltexx/International GS4 is now fully compatible with I9505G/jgedlte/GS4 GPe. Download either the regular or Touch version here (scroll down to "Samsung Galaxy S4 (i9505)"). Also, official CM 10.x and CM 11 nightlies for I9505/jfltexx are now fully compatible with I9505G/jgedlte, without any modifications.
Here is the guide to get both the recovery and CM 10.x/11 onto the GS4 GPe GT-I9505G:
Assuming you are on a Windows machine.
First we need to install the USB drivers:
Download and install Android SDK tools from here.
Run "SDK Manager.exe" from wherever you installed Android SDK in previous step.
Under "Tools" section select "Android SDK Tools" and "Android SDK Platform-tools". Under "Extras" section select "Google USB Driver."
Click the "Install" button and wait for installation to complete.
Exit the SDK Manager program.
Now unlock the bootloader (according to some people this step may not be necessary):
Boot up device normally, skip setup or do minimal setup - NOTE: you will wipe your phone during this process, so don't go nuts yet on config/installing apps.
Go to Settings --> About Phone
Tap Build Number 7 times, go back to Main Settings Menu and under now shown Developer Options enable USB debugging.
Plug into PC and ensure the phone is recognized.
On the phone accept the footprint signature popup - if it DOESN'T appear unplug/replug USB cable.
Under Command Prompt or Terminal on PC type in "adb devices" and press Enter. Ensure it shows the device and doesn't show "Offline" - if it does repeat steps 4-5.
Under Command Prompt or Terminal type in:
Code:
adb reboot bootloader
and press Enter.
Once in bootloader, on your PC Command Prompt type in:
Code:
fastboot oem unlock
and press Enter. Note that in Linux you will need to run fastboot with elevated privileges, i.e.
Code:
sudo fastboot oem unlock
.
Accept unlock using Volume key, and confirm with Power button - device will reboot possibly a few times, once rebooted and in device you can sign into accounts - REPEAT step 2-3 to re-enable USB debugging.
Now we can get down to flashing a custom recovery:
Un-install all existing Samsung drivers from your PC. This includes Kies program. I can't stress enough how important this step is for avoiding issues with flashing images via Heimdall or Odin.
Download the latest version of Heimdall from here and extract the ZIP to a folder on your hard drive (e.g. C:\Heimdall\ )
Download and install Microsoft Visual C++ 2012 redistributables package from here. These are required to have Heimdall work properly.
Download either the latest TWRP recovery from here, or latest official ClockworkMod Recovery for I9505 here and place the .IMG file into the Heimdall folder.
Shut down your phone, disconnect it from USB, and turn it on by holding Home + Volume Down + Power buttons together. This will start the phone in the Download mode. *NOTE: It is very important to get into the Download mode from a switched off phone. If you are coming from a different custom ROM, do not simply reboot into download mode (via advanced reboot option, or via "adb reboot bootloader" command) as that will cause issues with Heimdall and Odin.
Connect the phone to your computer via USB.
Run zadig.exe included in the "Drivers" sub-directory of Heimdall installation. From the menu chose Options -> List All Devices. From the USB Device list chose "Samsung USB Composite Device", or "MSMnnnn" - basically the S4. Press "Install Driver", click "Yes" to the prompt and if you receive a message about being unable to verify the publisher of the driver click "Install this driver software anyway". Your phone should now be recognized by Heimdall.
Open Windows Command Prompt and navigate to the directory where you extracted Heimdall. Now type in the following command:
Code:
heimdall flash --RECOVERY file-name-of-recovery-image-here.img --no-reboot
and press Enter. This will flash the recovery. Disconnect the USB cable, and hold the Power button until the phone vibrates. Now hold Home + Volume Up + Power to boot into the recovery.
Now we can flash the i9505's CM nightly:
Once in Recovery mode, connect your phone to USB. You may need to once again install the USB drivers. Just point it to \extras\google\usb_driver\ folder and select "Samsung USB Composite Device".
Perform a backup if you wish (highly recommended!)
Back on the computer, download the CM nightly build (10.x or 11) for the i9505/jflte from here.
Download the latest GApps package appropriate for the CM version you downloaded in previous step from here. (CM 11 compatible gapps, especially those working with new ART VM are currently in flux, but someone put together images of most used ones here).
Back on the phone in Recovery mode perform a full wipe (system, data, cache, and dalvik-cache.)
Flash the files in the following order: 1) CM nightly 2) GApps zip 3) Any other ZIPs you usually flash.
Reboot.
At this point your phone should be booting CyanogenMod. Should something go wrong, follow instructions in donovanbrock's thread to flash back to the stock GE firmware.
Older CM 10.1 ROMs for jfltexx used an outdated syntax for MOUNT command that required an edit to the updater-script, as described here. However, latest CM 10.x and all CM 11 nightlies converted to using a new mount syntax that does not need any modifications.
Working:
Root (superuser) without having to flash or install other packages.
Wi-Fi
Cell data (with LTE)
GPS
Bluetooth
NFC
Vibration
A/C and USB charging
Voice calls
Notification lights
All sensors
Both cameras
Physical and capacitive buttons
Google Apps (Gmail, Play Store, etc.)
Wi-Fi Tethering.
Not Working:
IR Blaster - CM doesn't have official support for it yet. Only apps that access IR modules via root methods will work (e.g. IR Universal Remote.) The functionality has changed from Android 4.3 to 4.4, so it will take some time for CM team to get it working properly. It should make it into CM eventually.
Sometimes when you simply reboot the phone, it gets stuck on the Google logo and doesn't proceed to boot into CM. This seems to be a known issue for the GS4 models and CM, which might have been introduced with SELinux commits. Experts think this is due to a race condition during initial boot-up phases, and are working on a fix. For now the work-around is manually ejecting the SD Card, and immediately putting it back in.
Untested:
Wireless display.
HDMI-out
Thanks and acknowledgements:
Team Win for TWRP recovery, especially Dees_Troy for making it work on I9505G.
CloclworkMod team for the CWM recovery, especially gweedo767 for getting it to work on I9505G.
CM Team for the ROM.
@donovanbrock for the flashing back to stock guide.
@NPS_CA for the bootloader unlock instructions.
Google for Android, and JBQ for AOSP.
WinZip
I claim no credit or ownership of any of the above. The pieces were already out there, I just put them together.
All the linked files are here.
Android SDK tools
Project page: http://developer.android.com/sdk/index.html
Direct download (Windows): installer_r23-windows.exe
Heimdall 1.40
Project page: http://www.glassechidna.com.au/products/heimdall/
Direct download (Windows): heimdall-suite-1.4.0-win32.zip
Support files: Microsoft Visual C++ 2012 redistributables.
Official TWRP recovery for I9505G/jgedlte
Project page: http://teamw.in/project/twrp2/192
Direct download: jgedlte.img
Official CWM recovery for I9505/jfltexx (fully compatible with I9505G/jgedlte)
Project page: http://www.clockworkmod.com/rommanager
Direct download Regular version: recovery-clockwork-6.0.4.7-jfltexx.img
Direct download Touch version: recovery-clockwork-touch-6.0.4.7-jfltexx.img
CM 10.x or 11 for the i9505 (jflte)
Download page: jflte nightlies
Latest GApps package for 4.2.x or 4.3.x (CM 10.x)
Project page: http://goo.im/gapps
Direct download for 4.2.x/CM 10.1: gapps-jb-20130812-signed.zip
Direct download for 4.3/CM 10.2: gapps-jb-20130813-signed.zip
Latest GApps images for 4.4.x (CM 11)
XDA-developers link: http://forum.xda-developers.com/showthread.php?t=2012857
Bonus: 4.3 Camera with Gallery that preserves Picasa Albums sync
Downloads: jb-43-camera-gallery-picasa.zip and jb-43-camera-gallery-picasa_lib.zip
Instructions: Flash both these files in Recovery AFTER flashing the ROM and GApps packages.
Excellent tutorial, thank you. Really happy to see some progress on custom ROMs for the 9505G. Hopefully we will have some custom kernels soon too!
Been waiting on the final version of TWRP. Just flashed. Good work guys!!! :good:
donovanbrock said:
Been waiting on the final version of TWRP. Just flashed. Good work guys!!! :good:
Click to expand...
Click to collapse
Well, it's not final until it shows up on http://teamw.in/project/twrp2 but it's close enough.
I keep getting error:
Code:
Installing '/sdcard/cm-10.1-20130719-NIGHTLY-jfltexx.zip'...
Checking for MD5 file...
I:Cannot find file /sdcard/cm-10.1-20130719-NIGHTLY-jfltexx.zip.md5
Skipping MD5 check: no MD5 file found.
line 1 col 93: syntax error, unexpected BAD, expecting IF or STRING or '!' or '('
1 parse errors
E:Error executing updater binary in zip '/sdcard/cm-10.1-20130719-NIGHTLY-jfltexx.zip'
Error flashing zip '/sdcard/cm-10.1-20130719-NIGHTLY-jfltexx.zip'
Any work need to be done to /META-INF/com/google/android/update-binary
?
Has anybody done a successful restore and backup using TWRP? Also silly questions but will the touchwiz roms work on this phone? I was going to do a backup and attempt flashing different ROMs for 9505 or should I hold off?
Thanks all and very nice work
donovanbrock said:
I keep getting error:
Code:
Installing '/sdcard/cm-10.1-20130719-NIGHTLY-jfltexx.zip'...
Checking for MD5 file...
I:Cannot find file /sdcard/cm-10.1-20130719-NIGHTLY-jfltexx.zip.md5
Skipping MD5 check: no MD5 file found.
line 1 col 93: syntax error, unexpected BAD, expecting IF or STRING or '!' or '('
1 parse errors
E:Error executing updater binary in zip '/sdcard/cm-10.1-20130719-NIGHTLY-jfltexx.zip'
Error flashing zip '/sdcard/cm-10.1-20130719-NIGHTLY-jfltexx.zip'
Any work need to be done to /META-INF/com/google/android/update-binary
?
Click to expand...
Click to collapse
Could be pastebin messed up the formatting of the updater-script. I'll upload from my original source in a minute.
Edit: Done. Try the file attached in this post, and if it works I'll replace in OP.
Chahk said:
Could be pastebin messed up the formatting of the updater-script. I'll upload from my original source in a minute.
Edit: Done. Try the file attached in this post, and if it works I'll replace in OP.
Click to expand...
Click to collapse
Yah buddy.. update your OP. The new files worked flawlessly. :highfive:
Worked for me as well. Very happy to see CM on our GE S4's.
I would like to add this, though: I've performed every step successfully without ever performing a "fastboot oem unlock". In other words, I'm currently running TWRP + CM10.1 without unlocking my bootloader. May be worth noting. Either way, good work everyone.
Thanks for this! Subscribed.
Gave this a try and can't get it working at all and now my phone just keeps booting into recovery.
When I trying wiping it takes forver (which I assume is it timing out) then I get:
E: Failed to Wipe dalvik
E: Unable to mount '/preload
Then the recovery ends with Failed
When I try flashing I just get error flashing:
Unable to mount /preload
Then just says failed.
Anyone have any thoughts? I tried re flashing the recovery... No luck.. Should also mention the recovery is prompting me for a password when I first get into it (which I never set) and I'm just hitting cancel...
Not for nothing guys, But why would anyone buy the GE Galaxy S4 when you can just buy the i9505 or the T Mobile variant which is literally what the GE is with a different bootloader. Its also $100 cheaper than the GE. with the GE you are **** out of luck with running touchwiz roms for now and you have to struggle to get CM 10.1 working when its already here and flawless on other variants..
drdingo21 said:
Gave this a try and can't get it working at all and now my phone just keeps booting into recovery.
When I trying wiping it takes forver (which I assume is it timing out) then I get:
E: Failed to Wipe dalvik
E: Unable to mount '/preload
Then the recovery ends with Failed
When I try flashing I just get error flashing:
Unable to mount /preload
Then just says failed.
Anyone have any thoughts? I tried re flashing the recovery... No luck.. Should also mention the recovery is prompting me for a password when I first get into it (which I never set) and I'm just hitting cancel...
Click to expand...
Click to collapse
Are you using the recovery I linked to?
Also, when modifying the ROM zip, make sure you are not editing the updater-script or build.prop files in an editor that will mangle line endings like Notepad. Try an advanced editor like Notepad++ instead.
Chahk said:
Are you using the recovery I linked to?
Also, when modifying the ROM zip, make sure you are not editing the updater-script or build.prop files in an editor that will mangle line endings like Notepad. Try an advanced editor like Notepad++ instead.
Click to expand...
Click to collapse
Yep! Everything from your op. are you not getting a password prompt?
I also didn't edit the files. I just dropped them into the Zip
drdingo21 said:
Yep! Everything from your op. are you not getting a password prompt?
I also didn't edit the files. I just dropped them into the Zip
Click to expand...
Click to collapse
No, no password prompts here. Can you try re-flashing the recovery via download mode again?
I heard the LTE bands are different for the phone because of the locked radio and modem. Only the GE edition can operate on both US carriers.
Sent from my GT-I9505G using xda premium
Chahk said:
No, no password prompts here. Can you try re-flashing the recovery via download mode again?
Click to expand...
Click to collapse
Alright. New computer with windows JUST installed.
When I flash the recovery and reboot it doesn't boot into recovery right away. It sits on the Teamwin splash (which it did before) but a reboot gets me into recovery. I still get the password prompt. I re downloaded everything in the OP. Is there somewhere else I should try grabbing the recovery?
---------- Post added at 09:46 PM ---------- Previous post was at 09:16 PM ----------
So I fixed my problems.
I've had my phone since they day they were shipped. I just tried the how to above with out any kind of wipe before hand.
I reflashed the stock recovery then did a full wipe and then wiped the cache again to be sure. Reflashed the attached recovery and all is well! I assume there was something making twrp think there was a password.
thanks for the tutorial!
Can your tweaked installer be used in the same way to make other 9505 ROMs and kernels work on the 9505G?
i had to change zadigto libusb0 (v1.2.5.0) from the default WinUSB (v6.1.7600.16385)
then everyting worked
i know have twrp on my i9505G.
btw if you boot the file using fastboot the touchscreen dose not work but once you flash it it works.
SPECIAL KNO'DIS: This Guide has been changed to refelct proper installation for both types of Maven Pro tablets, be Sure to follow the appropriate guide.
For the purpose of this guide, I'll assume you already have working ADB and Fastboot on your PC, if not, you'll need to set that up first. This guide doesn't cover installation of ether of those. If you're looking for the guide to the Viking Pro (RCT6303W87DK), go here.
KNO'DIS: I, OR ANYONE ELSE AT XDA, WILL NOT BE HELD RESPONSIBLE FOR "BRICKING" YOUR TABLET!! IF YOU MANAGE TO MAKE A BRICK, DUE TO YOUR "FUN-DA-MENTAL" INABILITY TO READ, GO BUILD A BBQ PIT WITH IT!! (Or ask for help, there's a lot of friendly people around here)
So, without further ado, lets get started. First, you'll need to know which version of firmware your device is running, this can be found in 2 different ways. From a running device go to: Settings/About tablet and look at the Build number. Or you can boot into stock recovery and the firmware version will be at the top left of the screen.
You should see something like the following, and note the 2nd number after the 2nd "V":
Code:
RCT6213W87DK-ANDROID5.0-V37-V1.9.30 <-- This is x.9.x version of firmware
or
RCT6213W87DK-ANDROID5.0-V68-V1.12.30-B <-- This is x.12.x version of firmware
Now that you know which firmware you have, follow the approriate guide below. I've broken this post into 2 different sections, as each tablet is just a little bit different.
About the Bootloader
This applies to both versions of firmware and tablet users. Turns out, the booloader doesn't have to be unlocked in order to install a custom recovery or root the device. So there's really no reason to unlock it, and I have removed that portion of this guide.
Installing MTK Preloader Signed Drivers
Drivers located Here
x.9.x Versions
Steps (Windows 8/8.1/10): For step 2 you will have less than five seconds. Preloader mode is only active for a few seconds. So read first!
1- Extract the drivers to the Desktop and open the Device Manager ("right click" on the Start button, select "Device Manager")
2- Plug your tablet in as such: turn off the tablet. Plug in the micro USB on the tablet, the other to the USB port on the PC, now very quickly in the device manager locate the new device and right click on it. For me, it showed up under "Other devices" and read MT65XX.
3- Select "update driver software" then select "browse my computer for driver software" (make sure "Include subfolders" is selected.
4- Click "Browse..." and navigate to where you extracted the driver zip. You "should" be at the following path: Desktop/MTK Preloader Signed Drivers
5- Click on "OK" then "Next". The driver should install at this point. Once that is done, unplug the usb cable from the pc (I find it easier to just keep the micro in the tablet).
x.12.x Versions (Requires Full size Male-to-Male USB Cable)
Steps (Windows 8/8.1/10): For step 2 you will have less than five seconds. Preloader mode is only active for a few seconds. So read first!
1- Extract the drivers to the Desktop and open the Device Manager ("right click" on the Start button, select "Device Manager")
2- Plug your tablet in as such: turn off the tablet. Plug in the full size USB cable to both the tablet and the PC.
3- Plug the micro USB into the tablet, the other to another USB port on the PC, now very quickly in the device manager locate the new device and right click on it. For me, it showed up under "Other devices" and read MT65XX.
4- Select "update driver software" then select "browse my computer for driver software" (make sure "Include subfolders" is selected.
5- Click "Browse..." and navigate to where you extracted the driver zip. You "should" be at the following path: Desktop/MTK Preloader Signed Drivers
6- Click on "OK" then "Next". The driver should install at this point. Once that is done, unplug both USB cables from the PC (I find it easier to just keep them in the tablet).
Installing TWRP
Firmware/TWRP Downloads
Maven x.9.x (Currently Contains: V37-1.9.30 and TWRP)
Maven x.12.x (Currently Contains: V63-V1.12.0-20150802 and V66-1.12.20-B-20150831 Firmware and TWRP)
Special Thanks to: @ShadowCX11 for testing for me.
Be sure you are using the appropriate TWRP for your version of firmware, and do the following:
1- Extract the firmware and the SP Flash Tool to your desktop.
2- Start the SP Flash Tool, and where it says "scatter file loading" click and navigate to the folder where you have the firmware and load the scatter file (depending on device, it could be in the "Images" folder).
3- Once that is done, uncheck everything, and select "recovery" only, from the list, navigate to the TWRP image file and click "Open", then click on the download button.
4- Plug the USB cable(s)* back into your PC. At this point the flash tool will load the recovery to the tablet. DO NOT UNPLUG ANYTHING UNTIL THE FLASH TOOL SHOWS YOU A GREEN CHECK MARK TO INDICATE THAT IT IS DONE, OR YOUR TABLET COULD BE HARD BRICKED AND IRREPARABLE.
5- After you get your check mark, unplug and boot into recovery, hold the Volume + and Power button. When splash screen comes up (the 2 dogs) release the power button.
6- Welcome to TWRP
*Remember, x.12.x requires 2 USB cables to work
ROOT
You can get root by flashing the latest SuperSu zip file located here, be sure to download the flashable zip.
Otherwise, for root, you can use the KingRoot app located here, (get the apk, or "Download for Android") and if you don't want a Chinesse Super User app, you can replace it with the ChainFire SuperSu by going here.
NOTE: This method of replacing KingRoot with SuperSu no longer works properly, and results in a bricked device.
Device Tree
GitHub
CREDITS
@vampirefo (for the CWM Recovery and teaching me about TWRP, there would be no recoveries if it wasn't for him!)
@Bogram (for the lk.bin patch trick)
@smartmanvartan (for the flashing guide)
Reserved
Reserved #2
Hello! I've had my Maven Pro for a couple months now and I still haven't rooted it like I have with the rest of my devices. I'd love to do it too, but reviewing your instructions, I found that my version number is way different. V66-V1.12.20-B. will that version patch tool still work for it? is there an update that it's refusing to download? Thanks!
Edit: on top of this, i can't get it to even connect (step 2) with any of my microUSB cables. (they work with my other devices)
equinox13 said:
Hello! I've had my Maven Pro for a couple months now and I still haven't rooted it like I have with the rest of my devices. I'd love to do it too, but reviewing your instructions, I found that my version number is way different. V66-V1.12.20-B. will that version patch tool still work for it? is there an update that it's refusing to download? Thanks!
Edit: on top of this, i can't get it to even connect (step 2) with any of my microUSB cables. (they work with my other devices)
Click to expand...
Click to collapse
Ooh, a v12, sorry friend, lol. Make sure the tablet is off, and be ready with "Device Manager" open, the preloader only shows up for a bit, then it disappears. The patch tool should still work for you, but the TWRP recovery may not. If it doesn't, the CWM recovery will after I modify it, because it's non-touch.
If neither recovery works for you, you can give me a copy of your "boot.img" file, and I can convert TWRP or CWM to work on your tablet. Also, I've changed the guide up top to include other root methods.
If you have any trouble, by all mean, post, and I'll try to help you through it
Regards,
Nepo
EDIT:
A friend found some V12 firmware, and I'll be uploading it soon. I can get a boot.img file from it to make a recovery.
My maven pro is stuck in a bootloop after I rooted now I don't know what to do. I can't even shut it down
GartimusPrime said:
My maven pro is stuck in a bootloop after I rooted now I don't know what to do. I can't even shut it down
Click to expand...
Click to collapse
You can reflash firmware while it is in a bootloop, I've done this many times. If you have everything set up, drivers, SP Flash Tool, firmware, etc..
Do the following:
1) Startup the Flash Tool and Load your firmware, as described in the OP (be sure to "uncheck" the Preloader)
2) Plug in your micro USB cable to both the PC and the tablet
3) Press and hold the "Reset" button located on the back
4) Click the Download button, then let go of the reset button, it should start flashing the firmware.
If it doesn't the first time, retry steps 3 and 4. I've had it fail the first time before, but work on the second.
Good Luck and let me know how it goes. Also, if the battery is completely drained by the time you read this, just flash firmware normally (again, uncheck the preloader). The tablet has to be powered off to flash it anyway.
Regards
Nepo
So after reflashing my tablet (a Canadian V12 that had V68, and flashed to V66 trying to unlock the boot loader and install CWM), USB doesn't work. The port doesn't output any voltage, and neither does the keyboard connector. The tablet acts like nothing is there, as does the PS3 controller I tried. Also, before, Firmware Update would say there's no updated firmware. Now, it doesn't seem to do anything. I flashed every partition except preloader, MBR and ebr, and the sec partitions. Do I have to reflash again, or is there something else I can do?
On a completely different note, I tried flashing a patched lk.bin, and it failed with an error I don't remember (I had temporary access to a PC).
One more thing that was quite interesting to me. It seems if you reboot into recovery or bootloader from Android (APM+ or root), you're then able to access the recovery with Power + Vol. Up. Is this known, or was it a fluke?
ShadowCX11 said:
So after reflashing my tablet (a Canadian V12 that had V68, and flashed to V66 trying to unlock the boot loader and install CWM), USB doesn't work. The port doesn't output any voltage, and neither does the keyboard connector. The tablet acts like nothing is there, as does the PS3 controller I tried. Also, before, Firmware Update would say there's no updated firmware. Now, it doesn't seem to do anything. I flashed every partition except preloader, MBR and ebr, and the sec partitions. Do I have to reflash again, or is there something else I can do?
On a completely different note, I tried flashing a patched lk.bin, and it failed with an error I don't remember (I had temporary access to a PC).
One more thing that was quite interesting to me. It seems if you reboot into recovery or bootloader from Android (APM+ or root), you're then able to access the recovery with Power + Vol. Up. Is this known, or was it a fluke?
Click to expand...
Click to collapse
No USB is a new one on me, I wish I had a x.12 version of this tablet to test on (mine's x.9) I'd try a re-flash, this time, do everything but the preloader, the reason for not flashing a preloader is because it sometimes semi-bricks one of these tablets.
Interesting note, there was a guy on the Viking thread (RCT6303W87DK) that flashed CWM without unlocking his bootloader, and everything is working fine for him...
Regards,
Nepo
PS, Power + Vol Up is the standard way to enter recovery on this device (I have the Xposed APM+ apk installed too)
NepoRood said:
No USB is a new one on me, I wish I had a x.12 version of this tablet to test on (mine's x.9) I'd try a re-flash, this time, do everything but the preloader, the reason for not flashing a preloader is because it sometimes semi-bricks one of these tablets.
Interesting note, there was a guy on the Viking thread (RCT6303W87DK) that flashed CWM without unlocking his bootloader, and everything is working fine for him...
Regards,
Nepo
PS, Power + Vol Up is the standard way to enter recovery on this device (I have the Xposed APM+ apk installed too)
Click to expand...
Click to collapse
So just a quick question: Is the device /dev/recovery for sure recovery? I want to see if I can just use dd to flash recovery.
ShadowCX11 said:
So just a quick question: Is the device /dev/recovery for sure recovery? I want to see if I can just use dd to flash recovery.
Click to expand...
Click to collapse
Yes, to pull a copy from a running tablet you use dd, and the path is: /dev/recovery
So, I'd do it this way, using adb:
Code:
adb push NAME_OF_RECOVERY.img /data/local/tmp
# Wait for it, then type:
adb shell
#Followed by:
dd if=/data/local/tmp/NAME_OF_RECOVERY.img of=/dev/recovery
#After it finishes:
reboot recovery
Okay, I got CWM installed! Now to see if I can find a way to build TWRP...
ShadowCX11 said:
Okay, I got CWM installed! Now to see if I can find a way to build TWRP...
Click to expand...
Click to collapse
Great! Is the CWM in portrait or landscape? You can always try to port the one I built for the x.9's, just unpack stock recovery, unpack TWRP, swap out the prebuilt kernel and repack.
NepoRood said:
Great! Is the CWM in portrait or landscape? You can always try to port the one I built for the x.9's, just unpack stock recovery, unpack TWRP, swap out the prebuilt kernel and repack.
Click to expand...
Click to collapse
It's in landscape, and works quite well! I just like the touch interface a bit more. I'll try the kernel replacement.
ShadowCX11 said:
It's in landscape, and works quite well! I just like the touch interface a bit more. I'll try the kernel replacement.
Click to expand...
Click to collapse
I prefer TWRP as well, that's why I built it
The only reason I don't have one posted for x.12 users is I can't test it. If you get it to work properly, let me know and I'll add it to the OP so others can benefit. :good:
If not, I can do some builds for you to test, if you don't mind. I have the x.12 kernel in my repo
NepoRood said:
I prefer TWRP as well, that's why I built it
The only reason I don't have one posted for x.12 users is I can't test it. If you get it to work properly, let me know and I'll add it to the OP so others can benefit. :good:
If not, I can do some builds for you to test, if you don't mind. I have the x.12 kernel in my repo
Click to expand...
Click to collapse
Yeah, I can't figure out how to extract the kernel, because I don't usually have access to a PC. However, I'll take some testing builds if you can make them.
Also, back to the USB issue, a reflash of everything except preloader didn't fix it. However, checking the firmware update now tells me that this is the latest version (which is definitely wrong, since I had v68). It must be an incompatibility between the USA and Canadian variants. If you find a Canadian firm dump, can you send me a link?
---
Hmm, okay.
So I just took a look at the model number on my box, and it's RCT5213W87DKF. That extra letter is what changes this a bit. I'll try seeing what I can dig up in terms of OTA updates, and I'll keep posting about what I find.
---
Okay, so after a few packet captures, I found the tablet makes a GET request to http://tablet12.gyrodock.com:2300/OtaUpdater/android?device=RCT6213W87DK with the User-Agent rk29sdk/4.0, but the server returns a 404 page. When I do this in the browser, however, I get something quite peculiar happen, which interests me. Most of the other places on the site return a Tomcat 404 that has the path in the parenthesis. However, for the OTA URL, it just has empty parenthesis. POST requests to that URL return a 200 OK with no return data, which is also interesting. I'll keep hunting around.
Some people might not have a PC to run flash_tool on, so here's how you can flash recovery/uboot/mbr/ebr2/logo/sec_ro from within Android
I'll use recovery as an example. I'm using a V12 tablet, so steps might be different if you have a V9. I tried to make this guide as revision-agnostic as possible, so correct me if I mess something up.
Root your device. The method I use is KingRoot, because it doesn't require any weird things. You can uninstall KingRoot and flash SuperSU later.
Download a recovery image. Make sure if you have a V12 tablet, you download a recovery image for V12, and a V9 recovery for a V9 tablet, or you'll brick your recovery. I personally prefer TWRP, because it has more features and a nicer UI, but CWM works too.
Get shell access. You can use a terminal emulator.
Type in su, and give the terminal superuser access on your device.
Type in dd if=/sdcard/Download/mavenVY_XXX.img of=/dev/recovery, where Y is 9 or 12, and XXX is CWM or twrp3.0.2. This will flash the recovery image.
Finally, type in reboot recovery. This should reboot into your custom recovery! It might also enable Power + Vol Up access to recovery, however, this hasn't been confirmed.
All the other partitions are similar, just replace the references to recovery images with the respective file names for the raw partition, and /dev/recovery with /dev/[PARTITION]. You can NOT flash the android or usrdata partition while in Android or you'll most likely soft-brick your tablet, however, you can boot into TWRP and go to the terminal and do the flash. You must copy your disk images to /tmp when doing so however, or you'll probably lose the disk image during the flash, effectively causing a brick.
Hope this helps people out!
ShadowCX11 said:
I've found out that it seems the v12 tablets strictly enforce the checksums of partition images, so flashing a custom recovery or uboot does not work with flashtool.
Click to expand...
Click to collapse
Nice addition, but all you have to do is disable it in the Checksum.ini file (change the 1 to 0):
Code:
[IsEnableChecksum]
CHECKSUM_SWITCH=0
I did that for the v9 versions, but only uploaded the v12 firmware...
NepoRood said:
Nice addition, but all you have to do is disable it in the Checksum.ini file (change the 1 to 0):
Code:
[IsEnableChecksum]
CHECKSUM_SWITCH=0
I did that for the v9 versions, but only uploaded the v12 firmware...
Click to expand...
Click to collapse
Oh... makes sense...
ShadowCX11 said:
Oh... makes sense...
Click to expand...
Click to collapse
I'm glad you posted that info, it'll be super handy for folks that may not have access to a PC, or would rather use their device instead of a PC :good: