I have root dell venue 2.3.3
download system.img
406
115.com/file/dn3dfplj
venue233.rar
408
115.com/file/aqoa9e6q#
system233菜单汉化.rar
408 add china language
1:install updata.pkg for 2.3.3
2:use fastboot mode flash system.img
reboot your phone
OK ,your phone root Successfully
Add RootExplorer.apk Superuser.apk
Really?
Sent from my Dell Venue using XDA App
Oh! That really seems.
Someone in the forum, attending is a screenshot taken by direct experiment.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
@liu: you rock! Could you please tell us how did you do that? Btw, could you please consider hosting your result in another place? I tried many times today, but still cannot get what you shown there!
I figured out which link/area of the Chinese page to click (tried them all) and was able to download the venue 2.3.3 .img file.
Here's a link to the file I uploaded: http://www.mediafire.com/?hbag5amdukmxl2h
---------- Post added at 09:35 PM ---------- Previous post was at 08:52 PM ----------
hwon123 said:
Someone in the forum, attending is a screenshot taken by direct experiment.
View attachment 788887
View attachment 788888
View attachment 788889
Click to expand...
Click to collapse
@hwon,
Did you actually try that and these are your attached files? I'm not sure what you meant but I understand English is not your native language so it is not a problem at all Just trying to clarify.
root way
1: unpack updata.pkg
2: unpack root.img
3: root kernel
4: repack root.img
5: flash root.img
5: reboot phone
ok ,ROOT Successful
@liuhui: it's cool! I tried to use your system.img and it works. Could you please tell me the detail (e.g. use which tool to unpack .pkg file, then perform which modification. I think your details will be good for all of us here). Thank you!
Luihui, congrats!
Sent from my Dell Streak using XDA App
Will this really work? Sorry newbie here.
streak4m3 said:
I figured out which link/area of the Chinese page to click (tried them all) and was able to download the venue 2.3.3 .img file.
Here's a link to the file I uploaded: http://www.mediafire.com/?hbag5amdukmxl2h
---------- Post added at 09:35 PM ---------- Previous post was at 08:52 PM ----------
@hwon,
Did you actually try that and these are your attached files? I'm not sure what you meant but I understand English is not your native language so it is not a problem at all Just trying to clarify.
Click to expand...
Click to collapse
1st picture means 'Change system Font'
2nd picture means 'Created superuser'
3rd picture means 'Rootexplorer 'Mount R / O' button is activated.'
The above three preconditions 'root' should be.
works great!
we should make this thread a sticky!
it's in chinese?
r0b1n84 said:
it's in chinese?
Click to expand...
Click to collapse
I uploaded the file for English speakers here: http://www.mediafire.com/?hbag5amdukmxl2h
ok, after some experimenting I found the following. You only need to flash recovery.img fron Update 319 then boo into recovery, upgrade update.pkg (406 on sd card), on reboot boot into flash mode and flash system.img(venue233.img) make sure to rename the 233 image file to system.img or write fail error will occur when flashing. cheers!
ckicky:
319 recovery.img
Steps for newbies
Hi Omnichron, would you mind specify the steps involved for newbies:
(1) Flash recovery.img from Update 319, how? via PC with what software? or just on SD card?
(2) Reboot into recovery mode, how to do that?
(3) Upgrade update.pkg (406 on sd card), with my HK rom, it declines to process update.pkg because of language conflict with Korean :-(
(4) Reboot into flash mode and flash system.img (venue233.img), I suppose this is the same as (1) but how?
Thanks very much!
R
You can't use the phone since it can only load update.pkg when in recovery mode.
You need to use a tool called fastboot to load the other files (recovery.img).
Than turn off phone, than turn on phone but turn on mute and hold the vol down button and you'll be in a special boot menu where you can load upgrade.pkg
The last step you are correct, same method as first, use fastboot to load the file onto the phone.
I'm trying to duplicate Omnichron's steps, but my PC doesn't detect the phone with fastboot, only ADB detects the phone. I can't find any drivers for fastboot for Dell Venue that actually works...
royoni said:
Hi Omnichron, would you mind specify the steps involved for newbies:
(1) Flash recovery.img from Update 319, how? via PC with what software? or just on SD card?
(2) Reboot into recovery mode, how to do that?
(3) Upgrade update.pkg (406 on sd card), with my HK rom, it declines to process update.pkg because of language conflict with Korean :-(
(4) Reboot into flash mode and flash system.img (venue233.img), I suppose this is the same as (1) but how?
Thanks very much!
R
Click to expand...
Click to collapse
i'm still confuse about how to update, please give step by step, and what software we need to do that. really thanx for the hep
r0b1n84 said:
i'm still confuse about how to update, please give step by step, and what software we need to do that. really thanx for the hep
Click to expand...
Click to collapse
This will help you, check it out: http://forum.xda-developers.com/showthread.php?t=1219566
---------- Post added at 12:39 PM ---------- Previous post was at 12:37 PM ----------
webdoctors said:
I'm trying to duplicate Omnichron's steps, but my PC doesn't detect the phone with fastboot, only ADB detects the phone. I can't find any drivers for fastboot for Dell Venue that actually works...
Click to expand...
Click to collapse
This will help you, it works for me: ftp://ftp.dell.com/handheld/R291096.exe
How to get into fastboot?
Hi all,
I found this picture online but not sure if this is the fastboot menu? How can I get there and what is the next step? Which option is the fastboot?
[05] SD download confirms to brick the phone
Thanks!
I think there are two menus. The one with the picture above and another one that you need to use to flash the recovery and system images. Here are steps:
1. Turn the "Mute" switch to "On" (you will see red).
2. Turn off the phone.
3. Turn it back on and at the same time hold the "Volume down" button. You will see a single line saying something about fastboot mode.
4. Now, connect your Venue to your PC via USB cable. On the Venue screen it will say something like " fastboot connected".
5. At that point you can start flashing.
~~~~~~~~~~~~~~~~~~~~~~~~
6. After you flashed the recovery and rebooted your phone (via fastboot command), you need to disconnect the USB cable from your PC.
7. As soon as you see the Dell logo you need to press and hold both volume buttons (Up and Down). This will take you to a new screen prompt which gives you three lines: one for factory reset, another for sd card update and I cant remember the third one (maybe calibration).
8. Choose the "sd card update" by pressing the camera button and you will see a new screen prompt with blue letters.
9. At this point you need to press the camera button again and the update will start (it will take some time).
10. Once the update is installed your phone will reboot and you need make sure your "mute" button is still on (you will see red) and press and hold the "volume down" button as soon as you see the Dell logo. You will see the familiar single line that says something about fastboot USB mode.
11. Now connect your phone via USB cable back to the PC and it will change the status on the Venue to "fastboot connected".
12. Now you can flash the system image. After the flashing is done, you would need to enter a fastboot reboot command and the phone will reboot and factory reset on it's own.
And that should be it.
If you need help flashing, let me know and I will type up the steps too.
P.S. The option that royoni illustrated via the image in his post WILL BRICK your phone. He warns you and I will too. I have done it and had to send it back to Dell.
Hope this helps
Related
Attention, Do On Your Own Risk
I am not responsible if there is any damage to your device
And read this carefully
ONLY FOR LG L7 II P713
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Let's get started it
First, check your software, go to settings> about phone> software information
If you are already using firmware p71310e-ESA-XX
You can directly use the apk below to rooting process
download apk from here
- install apk
- open it, and select the Superuser or SuperSU(Recomended use this)
- Click Gandalf
- Reboot
You have succesfully rooted your device
For non p7130e-ESA-XX user
Follow these instruction
>First, Download all these
1. USB Driver
2. KDZ FW Updater
3. Download Firmware LG L7 with Root support from here
4. Choose THA/THAILAND V10E LGP713
5. Download apk from here
Second, install
1. Usb Driver
2. Extract the KDZ FW Updater, find msxml.msi and instali it
3. Connect the device computer, do not forget to check the USB debugging on, once there select the connection notification, select Software LG
4. Open KDZ update
Choose Type =3GQCT
Phone Mode =DIAG
5.Browse File KDZ that you've download, then click ''Launch Software Update"
6. Find some food until the process is done,
cause It's take a long time, between 15-20 minutes, i'm not kidding
7. Install apk
8. Open it, and select the Superuser or SuperSU(Recomended use this)
9. Click/Choose Gandalf
10. Reboot your device
Finally, You have succesfully rooted your device
Special thanks
@alephzain
for this awesome application
Of course, all of these operations need the right Root User
1. Download and unpack this archive boothack+recovery
2. Install the program Gscript.apk on your phone
3. File boothack-cwm.sh put the path /storage/sdcard0/gscript /
4. APPSSBL.bin and recovery.img files put the path /storage/external_SD/
5. Run a previously installed Gscript
6. Press the softkey menu -> Add Script -> Load File -> boothack-cwm.sh -> save (it is added to the list)
7. Click on the saved script boothack-cwm
8. You're done! (the phone will restart in recovery mode)
Known issues at the moment:
1. The problem with the display. Displayed upside down and while navigating jumps in width. At this point in the stage of searching for a solution. Nevertheless, all necessary functions are performed
Solution for bootloop problem while using CWM
solution is: pull out the battery > plug in to USB or charger if you don't have pc > just let it blinks with LG logo > now put your battery in, you will see the battery icon charged > plug out the cable > then turn it on like usual.... wallaa... you got your phone back to home...
after this, please use kdz flasher to remove cwm recovery ( do not wipe data if you won't )
that's all... cheers
credit goes to
thanks @yayakuya for the solution
Reserved
I want to ask something. Will framaroot 1.7.0 work on 10D ? If not, why not using motochoper instead ?
Sent from my LG-P713 using xda app-developers app
thank ,i was rooted for my p713 .
but i can't install recovery .
karkand said:
I want to ask something. Will framaroot 1.7.0 work on 10D ? If not, why not using motochoper instead ?
Sent from my LG-P713 using xda app-developers app
Click to expand...
Click to collapse
nope, 10d didn't working with all framaroot version, you must change you fw
vananuan said:
thank ,i was rooted for my p713 .
but i can't install recovery .
Click to expand...
Click to collapse
open this thread to install cwm
http://forum.xda-developers.com/showthread.php?t=2277972&page=2
follow the instructions
please note this
the recovery doesn't stable yet, don't blame anyone if there's something wrong later
vananuan said:
thank ,i was rooted for my p713 .
but i can't install recovery .
Click to expand...
Click to collapse
Thx. Now my phone root
Sent from my LG-P713 using xda app-developers app
damn... my p713 was v10a
i hate to play with flasher...
but nvm, thanks for those bro,
can't do oplosan shake before breaking the system
yayakuya said:
damn... my p713 was v10a
i hate to play with flasher...
but nvm, thanks for those bro,
can't do oplosan shake before breaking the system
Click to expand...
Click to collapse
you're welcome brother
just shaking the oplosan dance at the same time while you breaking the system
happy dancing and happy flashing
nasheich said:
you're welcome brother
just shaking the oplosan dance at the same time while you breaking the system
happy dancing and happy flashing
Click to expand...
Click to collapse
oi bro...
why after I pull my sdcard out, my phone just going to bootloop...
I still can go to cwm, but why that's only for few seconds then it just reboot it self???
I can't do restore the backup coz it will be rebooted while in the middle of process...
the worst thing, I can't use kdz flasher coz adb can not read my phone while in bootlooping (actually it's readable, but the bootloop is not stucked... it's round over n over again)
so adb just read for a while coz phone turned off n then restarted again...
did you know which buttons combo for bring it to emergency mode?
thanks
yayakuya said:
oi bro...
why after I pull my sdcard out, my phone just going to bootloop...
I still can go to cwm, but why that's only for few seconds then it just reboot it self???
I can't do restore the backup coz it will be rebooted while in the middle of process...
the worst thing, I can't use kdz flasher coz adb can not read my phone while in bootlooping (actually it's readable, but the bootloop is not stucked... it's round over n over again)
so adb just read for a while coz phone turned off n then restarted again...
did you know which buttons combo for bring it to emergency mode?
thanks
Click to expand...
Click to collapse
1. don't use cwm for now, isn't stable yet
2. like Samsung's device, use combination of home+volume down+power to go emergency mode
3. if the number 2 doesn't work, pull out the battery, connect your device to PC(don't use the battery) and go to emergency mode by holding home+volume down+power as fast as you can
4. now flash the stock rom using kdz updater again(make sure you downloaded that)
sorry for late reply, I'm busy dancing oplosan
nasheich said:
1. don't use cwm for now, isn't stable yet
2. like Samsung's device, use combination of home+volume down+power to go emergency mode
3. if the number 2 doesn't work, pull out the battery, connect your device to PC(don't use the battery) and go to emergency mode by holding home+volume down+power as fast as you can
4. now flash the stock rom using kdz updater again(make sure you downloaded that)
sorry for late reply, I'm busy dancing oplosan
Click to expand...
Click to collapse
thanks mate..
ok, now i'll try it then report to you soon...
___edit__
kdz won't read the emergency mode!
I was trying those three modes in kdz, but phone can't read it.... :$
yayakuya said:
thanks mate..
ok, now i'll try it then report to you soon...
Click to expand...
Click to collapse
you're welcome
yayakuya said:
thanks mate..
ok, now i'll try it then report to you soon...
___edit__
kdz won't read the emergency mode!
I was trying those three modes in kdz, but phone can't read it.... :$
Click to expand...
Click to collapse
make sure you have install the driver first
use driver from the op
nasheich said:
you're welcome
Click to expand...
Click to collapse
how to read the phone in emergency mode?
the LG United driver only read adb....
any suggestion?
yayakuya said:
how to read the phone in emergency mode?
the LG United driver only read adb....
any suggestion?
Click to expand...
Click to collapse
like in the op, just change the "Phone Mode" to "Emergency Mode" at the KDZ Updater
Second, install
1. Usb Driver
2. Extract the KDZ FW Updater, find msxml.msi and
instali it
3. Connect the device computer,
4. Open KDZ update
Choose Type =3GQCT
Phone Mode =DIAG > change to emergency mode
5.Browse File KDZ that you've download, then click
''Launch Software Update"
6. Find some food until the process is done,
nasheich said:
like in the op, just change the "Phone Mode" to "Emergency Mode" at the KDZ Updater
Second, install
1. Usb Driver
2. Extract the KDZ FW Updater, find msxml.msi and
instali it
3. Connect the device computer,
4. Open KDZ update
Choose Type =3GQCT
Phone Mode =DIAG > change to emergency mode
5.Browse File KDZ that you've download, then click
''Launch Software Update"
6. Find some food until the process is done,
Click to expand...
Click to collapse
like I was mentioned above, I did try those three mode "emergency n cs_emergency mode" but still phone not found...
but nevermind, I've got new solution for it by my self....
if you guys having problem after installing cwm n do normal reboot, it will never bring you to the home screen... it's just bootloop...
solution is: pull out the battery > plug in to USB or charger if you don't have pc > just let it blinks with LG logo > now put your battery in, you will see the battery icon charged > plug out the cable > then turn it on like usual.... wallaa... you got your phone back to home...
after this, please use kdz flasher to remove cwm recovery ( do not wipe data if you won't )
that's all... cheers
I'm not using LG L7 anymore, i was changing about 2 months ago
btw, I'll put it at first page if you don't mind
OK so I followed thread:
http://forum.xda-developers.com/dell-venue/development/guide-how-to-root-android-4-4-4-dell-t2918427
Now I get
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
and
http://imgur.com/oCR0VqC,r9FmCXd#0
and
http://imgur.com/r9FmCXd
SO I figured there was a recovery option from http://opensource.dell.com/releases/Venue_8_3840_Merrifield/developer-edition/Doc/OSS_A150&A195.pdf
When I download YTD802A519500-2014-07-16-16.tgz CRC error upon unpacking. Downloaded twice on Windows and Linux machines. Doesn't matter cause xFSTK-Downloader doesn't see it. I have iSocUSB 1.0.4 drivers installed.
This thread didn't seem to apply: http://forum.xda-developers.com/showthread.php?t=1416537 since I don't have a custom recovery.
And all the links are dead in this thread which I think would have worked : http://forum.xda-developers.com/showthread.php?t=1219566
Oh and I can still get into recovery mode.
Fastboot is seen Windows
Any ideas? Any help?
Thanks in advance.
P_Link said:
OK so I followed thread:
http://forum.xda-developers.com/dell-venue/development/guide-how-to-root-android-4-4-4-dell-t2918427
Now I get
and
http://imgur.com/oCR0VqC,r9FmCXd#0
and
http://imgur.com/r9FmCXd
SO I figured there was a recovery option from http://opensource.dell.com/releases/Venue_8_3840_Merrifield/developer-edition/Doc/OSS_A150&A195.pdf
When I download YTD802A519500-2014-07-16-16.tgz CRC error upon unpacking. Downloaded twice on Windows and Linux machines. Doesn't matter cause xFSTK-Downloader doesn't see it. I have iSocUSB 1.0.4 drivers installed.
This thread didn't seem to apply: http://forum.xda-developers.com/showthread.php?t=1416537 since I don't have a custom recovery.
And all the links are dead in this thread which I think would have worked : http://forum.xda-developers.com/showthread.php?t=1219566
Oh and I can still get into recovery mode.
Fastboot is seen Windows
Any ideas? Any help?
Thanks in advance.
Click to expand...
Click to collapse
You may need to post your help questions in this thread, http://forum.xda-developers.com/dell-venue/development/guide-how-to-root-android-4-4-4-dell-t2918427
Most likely just downloading and flashing the stock boot.img should allow the tablet to boot.
vampirefo said:
You may need to post your help questions in this thread, http://forum.xda-developers.com/dell-venue/development/guide-how-to-root-android-4-4-4-dell-t2918427
Most likely just downloading and flashing the stock boot.img should allow the tablet to boot.
Click to expand...
Click to collapse
I can't post in the section due to low post count. Sucks being a lurker sometimes.
Also if you know where to find stock 3840 images please link.
P_Link said:
Also if you know where to find stock 3840 images please link.
Click to expand...
Click to collapse
Same post you got the boot.img from, hharte has uploaded stock system, boot.img and recovery.img
vampirefo said:
You may need to post your help questions in this thread, http://forum.xda-developers.com/dell-venue/development/guide-how-to-root-android-4-4-4-dell-t2918427
Most likely just downloading and flashing the stock boot.img should allow the tablet to boot.
Click to expand...
Click to collapse
vampirefo said:
Same post you got the boot.img from, hharte has uploaded stock system, boot.img and recovery.img
Click to expand...
Click to collapse
Holy crap I was searching and looking everywhere else I didn't even see that. Thank you. I should be able to flash this.
vampirefo said:
Same post you got the boot.img from, hharte has uploaded stock system, boot.img and recovery.img
Click to expand...
Click to collapse
Did not work, Fastboot crashes. I tried other system images and I just get a failed error after about 30 seconds, I've tried img and .gz formats as I believe it's suspose to be .gz since it's Intel
P_Link said:
Did not work, Fastboot crashes. I tried other system images and I just get a failed error after about 30 seconds, I've tried img and .gz formats as I believe it's suspose to be .gz since it's Intel
Click to expand...
Click to collapse
Why would you flash system? you should have only flashed stock boot.img
Most likely now you need to read complete thread and follow the unbricking procedures.
Get enough posts, and post in other thread..
vampirefo said:
Same post you got the boot.img from, hharte has uploaded stock system, boot.img and recovery.img
Click to expand...
Click to collapse
vampirefo said:
Why would you flash system? you should have only flashed stock boot.img
Most likely now you need to read complete thread and follow the unbricking procedures.
Get enough posts, and post in other thread..
Click to expand...
Click to collapse
Thought is was supposed to be system? Also the unbricking guide from Dell pdf has corrupted files. But I will try and do boot and see what happens.
Edit: no change. Flashed boot.img and then did a factory restore. Now it's boots to a black screen, like it's looking for an OS. I guess I really screwed it with the flashing the system.img.gz.
Thanks for the help
P_Link said:
Thought is was supposed to be system? Also the unbricking guide from Dell pdf has corrupted files. But I will try and do boot and see what happens.
Edit: no change. Flashed boot.img and then did a factory restore. Now it's boots to a black screen, like it's looking for an OS. I guess I really screwed it with the flashing the system.img.gz.
Thanks for the help
Click to expand...
Click to collapse
You need to download this .tgz from Dell to unbrick A150:
YTP802A115030-2014-06-23-30.tgz 28-Aug-2014 12:35 755M
http://opensource.dell.com/releases/Venue_8_3840_Merrifield/developer-edition/A150/Unbrick/
When you untar it (tar xfvz YTP802A115030-2014-06-23-30.tgz) you will get a bunch of files:
Code:
images-YTP802A115030/
images-YTP802A115030/oemlogo_8.bin
images-YTP802A115030/P802_flash_device_wifi_only.bat
images-YTP802A115030/oemlogo_7.bin
images-YTP802A115030/recovery.img
images-YTP802A115030/system.img
images-YTP802A115030/boot.img
images-YTP802A115030/dnx_fwr_0005_10CD_PRQ.bin
images-YTP802A115030/droidboot.img
images-YTP802A115030/partition.tbl
images-YTP802A115030/droidboot.img.POS.bin
images-YTP802A115030/dnx_osr_0005_10CD_PRQ.bin
images-YTP802A115030/for_product_ifwi_PRQ.bin
images-YTP802A115030/ifwi_0005_10CD_PRQ.bin
There are some other unbrick files (for A195 I think) that are broken. I emailed Dell about it, but got no reply so far. Just start completely over, following the Unbrick guide. I've done it many times on my Venue 8 3840, and it works fine.
In order for the rooted boot.img to work, you need to end up with your tablet having the IWFI, DNX, and droidboot from the Linux kernel package that Dell provided. You also need the 4.4.4 system.img, which can be obtained by following the unbrick process, and then letting the tablet OTA to 4.4.4. If the unlocked IFWI, DNX, or droidboot are not flashed, then the tablet will not run fastboot, and you'll either get a black screen with a USB symbol on it, or it will boot into recovery.
hharte said:
You need to download this .tgz from Dell to unbrick A150:
YTP802A115030-2014-06-23-30.tgz 28-Aug-2014 12:35 755M
http://opensource.dell.com/releases/Venue_8_3840_Merrifield/developer-edition/A150/Unbrick/
When you untar it (tar xfvz YTP802A115030-2014-06-23-30.tgz) you will get a bunch of files:
Code:
images-YTP802A115030/
images-YTP802A115030/oemlogo_8.bin
images-YTP802A115030/P802_flash_device_wifi_only.bat
images-YTP802A115030/oemlogo_7.bin
images-YTP802A115030/recovery.img
images-YTP802A115030/system.img
images-YTP802A115030/boot.img
images-YTP802A115030/dnx_fwr_0005_10CD_PRQ.bin
images-YTP802A115030/droidboot.img
images-YTP802A115030/partition.tbl
images-YTP802A115030/droidboot.img.POS.bin
images-YTP802A115030/dnx_osr_0005_10CD_PRQ.bin
images-YTP802A115030/for_product_ifwi_PRQ.bin
images-YTP802A115030/ifwi_0005_10CD_PRQ.bin
There are some other unbrick files (for A195 I think) that are broken. I emailed Dell about it, but got no reply so far. Just start completely over, following the Unbrick guide. I've done it many times on my Venue 8 3840, and it works fine.
In order for the rooted boot.img to work, you need to end up with your tablet having the IWFI, DNX, and droidboot from the Linux kernel package that Dell provided. You also need the 4.4.4 system.img, which can be obtained by following the unbrick process, and then letting the tablet OTA to 4.4.4. If the unlocked IFWI, DNX, or droidboot are not flashed, then the tablet will not run fastboot, and you'll either get a black screen with a USB symbol on it, or it will boot into recovery.
Click to expand...
Click to collapse
OK so I am using file YTP802A115030-2014-06-23-30.tgz that you suggested and it's content with xFSTK Downloader 1.5.1 and using iSocUSB Drivers 1.0.4. Following the Dell guide for bricking . I get to page 3 of http://opensource.dell.com/releases/Venue_8_3840_Merrifield/developer-edition/Doc/OSS_A150&A195.pdf
I get the following error XFSTK-LOG-Windriver Error: 0x20000015. Timeout expirded.
The tab is seen as a target
Thank you
OS 8.1
P_Link said:
OK so I am using file YTP802A115030-2014-06-23-30.tgz that you suggested and it's content with xFSTK Downloader 1.5.1 and using iSocUSB Drivers 1.0.4. Following the Dell guide for bricking . I get to page 3 of http://opensource.dell.com/releases/Venue_8_3840_Merrifield/developer-edition/Doc/OSS_A150&A195.pdf
I get the following error XFSTK-LOG-Windriver Error: 0x20000015. Timeout expirded.
The tab is seen as a target
Thank you
OS 8.1
Click to expand...
Click to collapse
I've seen that many times as well. One of the most frustrating parts for me working with this tablet was that error! The following seemed to work for me, but I figured it out towards the end of my adventure with this device, so I didn't get to try it repeatedly to see if the behavior is consistent:
Note on XFSTK: if you have trouble getting XFSTK to download properly, try:
Turn off the device (hold power button for 10 seconds.)
Press the Start Download button in XFSTK.
With USB cable connected, turn tablet on with Power + Volume Up.
I'm also using Windows 8.1 64-bit (on a Surface Pro 3.) I've tried both the built-in USB port and also each of the ports (USB 2.0 and USB 3.0) on the Surface docking station. The port doesn't seem to matter, nor do the cables. What definitely doesn't help is rebooting your PC, reinstalling the drivers/xFSTK, etc. I tried those things too. The Power+Vol UP was what I tried last time I went through the Unbrick, and it worked, but perhaps it was a coincidence. Please report back if you find that it works for you.
For what it's worth, I tried flashing the boot image on mine again using the one downloaded from the other post, and it worked fine.
Code:
H:\rooted_4.4.4_images>md5sum Dell_Venue_8_3840_rooted_4.4.4_boot.img
2bfefbaa81e78e90d78a5869987ee82f *Dell_Venue_8_3840_rooted_4.4.4_boot.img
H:\rooted_4.4.4_images>fastboot flash boot Dell_Venue_8_3840_rooted_4.4.4_boot.img
target reported max download size of 577456810 bytes
sending 'boot' (9604 KB)...
OKAY [ 1.271s]
writing 'boot'...
OKAY [ 1.447s]
finished. total time: 2.718s
H:\rooted_4.4.4_images>fastboot reboot
rebooting...
finished. total time: 0.516s
H:\rooted_4.4.4_images>adb devices
List of devices attached
Medfield317A5CF8 device
H:\rooted_4.4.4_images>adb shell
[email protected]:/ #
hharte said:
You need to download this .tgz from Dell to unbrick A150:
YTP802A115030-2014-06-23-30.tgz 28-Aug-2014 12:35 755M
http://opensource.dell.com/releases/Venue_8_3840_Merrifield/developer-edition/A150/Unbrick/
When you untar it (tar xfvz YTP802A115030-2014-06-23-30.tgz) you will get a bunch of files:
Code:
images-YTP802A115030/
images-YTP802A115030/oemlogo_8.bin
images-YTP802A115030/P802_flash_device_wifi_only.bat
images-YTP802A115030/oemlogo_7.bin
images-YTP802A115030/recovery.img
images-YTP802A115030/system.img
images-YTP802A115030/boot.img
images-YTP802A115030/dnx_fwr_0005_10CD_PRQ.bin
images-YTP802A115030/droidboot.img
images-YTP802A115030/partition.tbl
images-YTP802A115030/droidboot.img.POS.bin
images-YTP802A115030/dnx_osr_0005_10CD_PRQ.bin
images-YTP802A115030/for_product_ifwi_PRQ.bin
images-YTP802A115030/ifwi_0005_10CD_PRQ.bin
There are some other unbrick files (for A195 I think) that are broken. I emailed Dell about it, but got no reply so far. Just start completely over, following the Unbrick guide. I've done it many times on my Venue 8 3840, and it works fine.
In order for the rooted boot.img to work, you need to end up with your tablet having the IWFI, DNX, and droidboot from the Linux kernel package that Dell provided. You also need the 4.4.4 system.img, which can be obtained by following the unbrick process, and then letting the tablet OTA to 4.4.4. If the unlocked IFWI, DNX, or droidboot are not flashed, then the tablet will not run fastboot, and you'll either get a black screen with a USB symbol on it, or it will boot into recovery.
Click to expand...
Click to collapse
hharte said:
I've seen that many times as well. One of the most frustrating parts for me working with this tablet was that error! The following seemed to work for me, but I figured it out towards the end of my adventure with this device, so I didn't get to try it repeatedly to see if the behavior is consistent:
Note on XFSTK: if you have trouble getting XFSTK to download properly, try:
Turn off the device (hold power button for 10 seconds.)
Press the Start Download button in XFSTK.
With USB cable connected, turn tablet on with Power + Volume Up.
I'm also using Windows 8.1 64-bit (on a Surface Pro 3.) I've tried both the built-in USB port and also each of the ports (USB 2.0 and USB 3.0) on the Surface docking station. The port doesn't seem to matter, nor do the cables. What definitely doesn't help is rebooting your PC, reinstalling the drivers/xFSTK, etc. I tried those things too. The Power+Vol UP was what I tried last time I went through the Unbrick, and it worked, but perhaps it was a coincidence. Please report back if you find that it works for you.
For what it's worth, I tried flashing the boot image on mine again using the one downloaded from the other post, and it worked fine.
Code:
H:\rooted_4.4.4_images>md5sum Dell_Venue_8_3840_rooted_4.4.4_boot.img
2bfefbaa81e78e90d78a5869987ee82f *Dell_Venue_8_3840_rooted_4.4.4_boot.img
H:\rooted_4.4.4_images>fastboot flash boot Dell_Venue_8_3840_rooted_4.4.4_boot.img
target reported max download size of 577456810 bytes
sending 'boot' (9604 KB)...
OKAY [ 1.271s]
writing 'boot'...
OKAY [ 1.447s]
finished. total time: 2.718s
H:\rooted_4.4.4_images>fastboot reboot
rebooting...
finished. total time: 0.516s
H:\rooted_4.4.4_images>adb devices
List of devices attached
Medfield317A5CF8 device
H:\rooted_4.4.4_images>adb shell
[email protected]:/ #
Click to expand...
Click to collapse
Ok making some headway. The Power+Volume up was able to FW and OS Complete it says... However I can not boot. I can enter Droidboot but there is no Fastboot running, even tho it says it is. ADB device is seen.
I have no idea.
Thank you for your time.
P_Link said:
Ok making some headway. The Power+Volume up was able to FW and OS Complete it says... However I can not boot. I can enter Droidboot but there is no Fastboot running, even tho it says it is. ADB device is seen.
I have no idea.
Thank you for your time.
Click to expand...
Click to collapse
I'm pretty sure what's going on is that the driver loaded on the Fastboot device is the ADB driver. To fix this, when the tablet is in Droidboot:
1. open Device Manager (from Windows command prompt, type devmgmt.msc)
2. Find the device (it probably is under Android Devices.)
3. RIght click on the device, choose "Update Driver" and then "Browse My Computer..." and then "Let me pick from a list of device drivers on my computer."
4. You might have to unclick "Show Compatible Hardware"
5. In the Manufacturer section, pick Google or Intel.
6. Under Model, pick "Android Bootloader Interface."
7. Click Next, and then Ok to Ignore scary warnings.
After you get Fastboot running (fastboot devices should show some output) then you can proceed with the rest of the unbricking process, which is basically running a batch file that re-partitions the device, and then writes each of the partition images one by one. After the reboot you will be back to 4.4.2 stock, and you need to let the OTA happen. There should be one large (~200MB+) OTA.
Then you can continue with rooting...
hharte said:
I'm pretty sure what's going on is that the driver loaded on the Fastboot device is the ADB driver. To fix this, when the tablet is in Droidboot:
1. open Device Manager (from Windows command prompt, type devmgmt.msc)
2. Find the device (it probably is under Android Devices.)
3. RIght click on the device, choose "Update Driver" and then "Browse My Computer..." and then "Let me pick from a list of device drivers on my computer."
4. You might have to unclick "Show Compatible Hardware"
5. In the Manufacturer section, pick Google or Intel.
6. Under Model, pick "Android Bootloader Interface."
7. Click Next, and then Ok to Ignore scary warnings.
After you get Fastboot running (fastboot devices should show some output) then you can proceed with the rest of the unbricking process, which is basically running a batch file that re-partitions the device, and then writes each of the partition images one by one. After the reboot you will be back to 4.4.2 stock, and you need to let the OTA happen. There should be one large (~200MB+) OTA.
Then you can continue with rooting...
Click to expand...
Click to collapse
Thanks for all the info. I got the driver loaded with no issues. SO I was able to access Fastboot. Used the files from Dell FTP no go. Just got Intel logo? Any how I read on another post that he had to cobble to together file from the user social-design-concepts post and the files from Dell. That didn't work either but it did bring back the Dell splash screen.
I really hope the development goes further with this tablet. I returned it to Dell got a new one on the way. Thanks again for your help, sorry I couldn't follow directions.
Can someone help me with these -
1)
Where do I download 'droidboot.img'
(for these steps
Go to the directory contains “boot.img” and run these commands
\> fastboot flash boot boot.img
\> fastboot flash fastboot droidboot.img )
2) I have put my Venue 3840 in fastboot mode, and plugged in usb and run fastboot on command prompt. But on fastboot devices command it does not show my dell venue. I have installed all the drivers in the steps 1-4 on the dell reference pdf.
Neole
---------- Post added at 03:31 PM ---------- Previous post was at 03:16 PM ----------
Ok I got the dell venue to show as 'Medfield32715DD2' on fastboot devices command after doing this (thanks to who posted this!) -
1. open Device Manager (from Windows command prompt, type devmgmt.msc)
2. Find the device (it probably is under Android Devices.)
3. RIght click on the device, choose "Update Driver" and then "Browse My Computer..." and then "Let me pick from a list of device drivers on my computer."
4. You might have to unclick "Show Compatible Hardware"
5. In the Manufacturer section, pick Google or Intel.
6. Under Model, pick "Android Bootloader Interface."
7. Click Next, and then Ok to Ignore scary warnings.
Still haven't found droidboot.img - where do I download this?
I managed to find it here -
opensource.dell.com/releases/Venue_8_3840_Merrifield/developer-edition/
Now starting the root process.
Neole
Neole said:
Can someone help me with these -
1)
Still haven't found droidboot.img - where do I download this?
Click to expand...
Click to collapse
---------- Post added at 05:36 PM ---------- Previous post was at 04:50 PM ----------
Oh no! Now I've got the dead android same as posted by OP -
imgur.com/oCR0VqC,r9FmCXd#0
What's the solution??
btw I get a strange USB symbol when I boot in recovery mode (volume down + power button). When I boot normally I get the dead android with red triangle exclamation mark.
Here is the USB icon I see in recovery mode, there is nothing else and fastboot doesnt recognize the Dell Venue -
s29.postimg.org/t789qze07/Dell_Venue3840_Bricked.jpg
(Sorry for weird crop on the pic)
Please advise!!
Neole
I am doing the unbricking on the usb logo. Tablet is getting detected on xFSTK downloader and on Downloading I keep getting the same error as OP -
XFSTK-LOG-Windriver Error: 0x20000015. Timeout expired.
Will try again to see if it resolves later.
---------- Post added at 10:37 PM ---------- Previous post was at 09:58 PM ----------
Hurrah - I got it unbricked again! hharte's method worked -
Turn off the device (hold power button for 10 seconds.)
Press the Start Download button in XFSTK.
With USB cable connected, turn tablet on with Power + Volume Up.
Now to figure out why I couldn't root it in the first place? I'm sure I followed all the instructions correctly.
Neole said:
I am doing the unbricking on the usb logo. Tablet is getting detected on xFSTK downloader and on Downloading I keep getting the same error as OP -
XFSTK-LOG-Windriver Error: 0x20000015. Timeout expired.
Will try again to see if it resolves later.
---------- Post added at 10:37 PM ---------- Previous post was at 09:58 PM ----------
Hurrah - I got it unbricked again! hharte's method worked -
Turn off the device (hold power button for 10 seconds.)
Press the Start Download button in XFSTK.
With USB cable connected, turn tablet on with Power + Volume Up.
Now to figure out why I couldn't root it in the first place? I'm sure I followed all the instructions correctly.
Click to expand...
Click to collapse
Have you tried sdc's lastest method to root with recovery? he changed activation point.
vampirefo - "Have you tried sdc's lastest method to root with recovery? he changed activation point."
No I haven't tried that.. is it for Venue 3840? I couldn't find any more rooting threads for Venue 3840, could you point me to the thread with the instructions?
Thanks!
Neole
Hi,
I search the recovery.img of Oukitel K10.
I have make OEM Unlock, and I can get fastboot.
I have find many fake websites to hot to do this, but realy don't trust (last time I have brick my K10000 Pro).
The better way is now to "fastboot boot test.img" and see if my phone boot before flash anything.
But I dont find a recvery.img who boot my phone
I have the "fake" ROM (I search inside, and it's seem match as mine)
The other problem is SP flash tools don't want to get me my NVRAM ...
Anyone have root is K10 ? (I have a brick until my device is not root, I don't use it in stock ROM !)
So I finaly test the "normal" way, whit the SP Flash tool method, and it's works.
I don't know why, when I fastboot the image, the phone won't boot, but whith flashtools, it's works.
I have now My Oukitel K10 rooted, and cleaned
So, what did you use to root it?
Yea can u tell us how you did it atep by step. My flashlight its not working andi cant hear a thing on Bluetooth... Need to root this.. or someone else knows how to fix it?
I actually found a step-by-step guide here:
https://www.getdroidtips.com/twrp-recovery-oukitel-k10/
But, i got stuck at downloading the image over my phone,.... i never get green light after flashing....
The phone functions normal, after... because nothing flashed i guess...
And that guide is incomplete, you need to first disable digitally signed drivers check, otherwise the preloader won't work at all...
Did anyone else try it?
What do you guys get?
Mind to share your knowledge? How you obtain your Oukitel K10 rooted cleaned?
I've got this phone today. Here is my quick root procedure.
1. Prepare a magnifiying glass for reading messages on your phone.
2. Download SuperSU (ZIP) and TWRP for oukitel k10.
This one works for me (OKITEL_K10_V121_20180112).
3. Reboot to bootloader.
VOL-DOWN+POWER
4. Unlock bootloader. It will destroy /data now.
fastboot oem unlock
# VOL-UP confirm
5. Reboot to system, then reboot to bootloader again.
6. Flash recovery
fastboot flash recovery recovery.img
7. Reboot to recovery
# Hold VOL-UP
fastboot reboot
8. Format /data again
because no one knows password
9. Install SuoperSU.zip
Advanced - sideload -swipe # <-- on phone
adb sideload SuperSU-v2.82-201705271822.zip # <-- on computer
10. Reboot to system, setup and install SuperSU from market.
Now you should have root.
sergey1369 said:
I've got this phone today. Here is my quick root procedure.
1. Prepare a magnifiying glass for reading messages on your phone.
2. Download SuperSU (ZIP) and TWRP for oukitel k10.
This one works for me (OKITEL_K10_V121_20180112).
3. Reboot to bootloader.
VOL-DOWN+POWER
4. Unlock bootloader. It will destroy /data now.
fastboot oem unlock
# VOL-UP confirm
5. Reboot to system, then reboot to bootloader again.
6. Flash recovery
fastboot flash recovery recovery.img
7. Reboot to recovery
# Hold VOL-UP
fastboot reboot
8. Format /data again
because no one knows password
9. Install SuoperSU.zip
Advanced - sideload -swipe # <-- on phone
adb sideload SuperSU-v2.82-201705271822.zip # <-- on computer
10. Reboot to system, setup and install SuperSU from market.
Now you should have root.
Click to expand...
Click to collapse
I am not able to get to bootloader how to do that? voldown and power button does nothing but restarting phone everytime.
Hello. Turn off your phone first. Then hold button and turn it on. Be carefull - font is too small in menus.
sergey1369 said:
Hello. Turn off your phone first. Then hold button and turn it on. Be carefull - font is too small in menus.
Click to expand...
Click to collapse
I did turn off the phone then pressed power button and volume down button at a time then kept pressing it till logo came. as soon as I release them .. Phone just get started, instead of going to bootloader
Can anyone share recovery img file? I cant find anywhere.
Hi, you need Vol-up+Power.
It takes about 11 seconds on my phone.
Choose Fastboot mode with Vol-up and
confirm selection with Vol-down.
sergey1369 said:
Hi, you need Vol-up+Power.
It takes about 11 seconds on my phone.
Choose Fastboot mode with Vol-up and
confirm selection with Vol-down.
Click to expand...
Click to collapse
Thanks a lot for reply .. yes it gives me recovery propmpt
Have you got K10 Recovery? Cant find anywhere. The one link given here. Takes me to other website which need to paid membership and I tried to pay but Cant pay via paypal and developer inbox is full so cant contact him too.
Oh, that's weird, it was free. Here is a copy
Anyone know how install cleaned rom?
I keep getting bootloops as soon as I try to flash Magisk. I have no trouble flashing and starting up TWRP, but after flashing I can´t reboot to system. I also get the warning from my Pc when I connect my phone that it doesn´t recognize it. It reboots fine if I don´t flash anything. Any help? I also tried the steps on page 1 (Bootloader is successfully unlocked).
SuperSu works, but fails Safety Net, that´s why I want Magisk.
k10 ROOT
Hello Friend,
I have a K10 but I have not been able to do the ROOT, can you help me ??
What is the procedure?
FukTheRegister said:
So I finaly test the "normal" way, whit the SP Flash tool method, and it's works.
I don't know why, when I fastboot the image, the phone won't boot, but whith flashtools, it's works.
I have now My Oukitel K10 rooted, and cleaned
Click to expand...
Click to collapse
Hey there and sorry for the late response. What steps did you do so far? Is your bootloader unlocked already? Or are you at the start and this is your first try? If it is your first try, here is a step by step guide on what to do and what you will need.
What you need:
1. The SP Flash Tool and its drivers. You can find them on the Oukitel website or in the internet. Search for SP Flash Tool and download the latest. For the drivers it´s best to get them from Oukitel. Lower right side of their website and then click Latest software Rom and choose the K10.
2. The adb and fastboot drivers. Search them on the internet.
3. Your Smartphone.
4. A computer and the data cable.
5. The SuperSU 2.82 S3 files from chainfire. Again, search them on the internet.
6. The TWRP Image from this thread.
If you have everything, you do the following:
1. If you have used your phone already, safe everything you want to keep on your computer! You will have to erase your data at least once in the process!
2. Turn your phone on and go to settings.
3. Then tap on About your phone and scroll all the way down to see its build number.
4. Tap on that 7 times in a row to get the message: Congratulations you are now a developer. Go back to the settings to see a new option, the developer options.
5. Go to the developer options and tap on allow oem unlock and also tap on enable debugging options.
6. Leave the settings and connect your phone to your computer. Push the SuperSU file to your sd card (Magisk unfortunately does not seem to work and results in a bootloop at least for me).
7. On your computer, go to the folder where you saved the adb.exe and fastboot.exe. Hold shift and open a power shell or command window in there (don´t actually know the steps for a Mac or Linux computer, sry).
8. Now type adb devices and confirm the access on your phone. If your phone doesn´t show up or there is no confirmation message on your phone, type adb kill-server and then adb devices.
9. Once your phone is confirmed, you type adb reboot-bootloader.
10. Now type fastboot oem unlock and press the volume up button on your phone to confirm the bootloader unlock.
11. Your phone will now erase your data (internal storage only, your sd card will not be touched, but may need to be set up and formatted again if it was used to extend the internal storage).
12. On your computer, type fastboot reboot and set up your phone again (just the basics, because you will have to erase it again). Don´t forget to turn on the debugging mode again.
13. Open up the SP Flash Tool on your computer and choose the scatter file from the twrp image (custom recovery). Only recovery should be ticked. Hit the download all button, connect your phone to computer and turn off the phone. Now wait till there is a green hook on your computer. This means, the download has been successfull.
14. Get to recovery mode on your phone by holding the volume up and power button at the same time and choose the first option, then hit the volume down button to enter recovery mode.
15. From here, go to the settings in the upper right corner and choose your language (ignore the message of the password and hit back).
16. Now go to Wipe and format your data.
17. Hit the restart button and press Recovery. Allow it to modify the system and pull the slider.
18. Now go to Install, choose your sd card and press SuperSU. Let it run through the process. Then restart and press system. First time the boot may take a while, so be patient.
19. Set up the phone and enjoy your root.
Magisk 17.1
Magisk 17.1 install AS IS, no warranty, no testing (yet).
!!! You can lose your data or brick your phone !!!
0. Don't try default install or upgrade via MagiskManager - you'll get bootloop.
1. You can try this boot-magisk.img (AIK repacked with force encryption and dm-verity enabled).
It works for me, but I did factory reset before trying.
- boot.img comes from OUKITEL_K10_V12_20180112.rar (I'm not sure about file's source)
fastboot flash boot boot-magisk.img
2. If your phone freeze on Oukitel logo, don't touch it. Wait.
If you stop phone here, you'll lose your data.
There is no way back - it starts data encryption.
3. If it fails, try flashing stock boot back and factory reset your phone.
fastboot flash boot boot.img
That modified boot.img did the trick. What did you modify to make it work?
The forced encryption, however, is annoying. Is there a possibility to undo that?
help ... Oukitel K10
I flash firmware Oukitel K10 by SP_MDT_v3.1828 (Format and Download All). now : looked picture(red font). Phone call ok. please help me. I from Vietnam. Thankyou!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Hi there!
I ported this TWRP recovery from Mi pad 3 and it works perfectly! It was tested on official firmware TOS-V2.01-A921 (Phoenix OS), I don't know will it work on older firmwares or not (try at your own risk). All user data and storage will be fully erased!
Step 1
First of all you need to unlock bootloader. It's required ADB to be installed on your PC, because it will be done via fastboot.
Follow this steps:
-connect the tablet to pc, (first you have to enable OEM unlocking and USB debugging in Developer options)
- reboot the tablet in fastboot mode, hold buttons “power+Vol +” at startup, choose fastboot mode with Vol+ button, valid with Vol-
- open a command prompt in adb folder, then “fastboot devices”, then “fastboot oem unlock”, it should say “OKAY, finished”
Now it's done.
Step 2
Download this archive and unpack it (contains everything you need) - https://mega.nz/#!C1w0GaAI!Zw1QXuAgBLNOjymsWanQPuoKr8N6IhPAhuZy1yjlv-k
- Install MTK drivers
- Click on Flash_tool.exe
- Select "scatter-Loading" and search MT8173_Android_scatter.txt
- Press "recovery" and add path (choose) recovery file - TWRP 3.2.3
- Select "Download Only"
- Turn off your tablet and wait some seconds
- Press “Download” button in FlashTool programm to start
- Connect your tablet into the computer via USB data cable holding volume + button (do not press power button!).
- The process will start and a red progress bar will appear after color purple, yellow. Finally, green circles should display.
That's all. Now you should flash TWRP: hold buttons “power+Vol +” at startup, choose recovery mode with Vol+ button, valid with Vol- (alike in step 1)
If you face Error message like this:
BROM ERROR : S_DL_GET_DRAM_SETTING_FAIL (5054)
Obtain DRAM Failed!
Please check your load matches to your target which is to be downloaded.
Do this steps: choose scatter load -> load TWRP file ->[/B ]Push download button -> plug in the usb cable without pushing volume up
Step 3
Now it is required to format internal storage to be displayed properly (you will see 0 mb storage size). Just go to wipe section and choose "wipe data" option (write "yes" on keybord and accept).
After this reboot recovery ( go to reboot section -> reboot recovery)
Step 4
Connect tablet to PC and copy Magisk package to internal storage (Magisk should be flashable via TWRP in .zip format and can be found in appropriative thread). I've succesfully installed Magisk v17.1.
Afterwards, go to install section -> install package and reboot device (no wipes after installation are required). If it will ask for installing TWRP app , just cancel that.
All above-described actions should be fully completed, sure nothing is missed ! Because in this case your tablet will not boot!
So, that's all ! Let me know if you face any issues. Enjoy
Custom ROMs for TWRP can be found here:
Modified stock ROM - https://forum.xda-developers.com/android/help/firmware-modified-stock-rom-v2-01-t3894124
ASUS ZenUI ROM - https://forum.xda-developers.com/android/help/firmware-asus-zenui-rom-teclast-t8-t3898591
MIUI 10 ROM (stable!) - https://forum.xda-developers.com/android/help/firmware-miui-10-rom-teclast-t8-beta-t3910219
Pixel Experience ROM - https://forum.xda-developers.com/android/help/firmware-pixel-experience-rom-teclast-t8-t3919512
>> P.S. In the nearest future I will release some custom ROM'S for our device, at least Stock ROM for flashing via TWRP with ROOT added.
This will be amazing - THANK YOU!
Thank you for your tuto.
I want to put your asus rom in my teclast T8.
On my computer flash tool don't seems to work. I have a screen sp flash tool is loading and then, nothing.
I am on Win10 and try all compatibility mods and admin mod..
Any idea ?
naonilio said:
Thank you for your tuto.
I want to put your asus rom in my teclast T8.
On my computer flash tool don't seems to work. I have a screen sp flash tool is loading and then, nothing.
I am on Win10 and try all compatibility mods and admin mod..
Any idea ?
Click to expand...
Click to collapse
Try to install drivers for win 10 from: https://forum.xda-developers.com/showthread.php?t=1982587. For me it works perfectly on win 7,8. But it is recommended to use version of SP flashtool I attached here for our device.
Sword900 said:
Try to install drivers for win 10 from: https://forum.xda-developers.com/showthread.php?t=1982587. For me it works perfectly on win 7,8. But it is recommended to use version of SP flashtool I attached here for our device.
Click to expand...
Click to collapse
Looks that this issue is caused by very unfortunate folder naming in zip archive. Remove "," from folder names and you should be fine . Just remember to do that also for folder T8 TWRP RECOVERY - otherwise you will face "scatter file invalid" error later.
hello sword900,
i have downloaded your mtkflash tool but i have always an issue with the download of your recovery to the tablet.
every time, i have an flash error 4051 dram or so.
i have many tried this with different mtk drivers and disabling windows driver signature but it wont work.
after that i have installed the last official firmware V2.01-A921.
the installation was successful and that approved that my setup is ok.
i think there is a mistake between the recovery file and the scatter information.
have you any idea, what i can do to solve this problem?
thanks in advance
dreas
ok, i have found the solution. with an other flash tool and scatter file it works.
now i have tried the asus and stock rom.
it seems to be that the asus rom has gps funktionality. nice!
dreas74 said:
ok, i have found the solution. with an other flash tool and scatter file it works.
now i have tried the asus and stock rom.
it seems to be that the asus rom has gps funktionality. nice!
Click to expand...
Click to collapse
Yeah, this recovery works only on last firmware TOS v2.01. As I know, our device is not supplied with GPS module, so it won't work. Anyway let me know about your experience after testing my ROMs
dreas74 said:
ok, i have found the solution. with an other flash tool and scatter file it works.
now i have tried the asus and stock rom.
it seems to be that the asus rom has gps funktionality. nice!
Click to expand...
Click to collapse
I also solve mi matter with an other flash tool and scatter file !
I am on the asus ROM for the moment and that's working like a charm, thank you for your work.
---------- Post added at 11:04 PM ---------- Previous post was at 11:02 PM ----------
alex.niemnozka said:
Looks that this issue is caused by very unfortunate folder naming in zip archive. Remove "," from folder names and you should be fine . Just remember to do that also for folder T8 TWRP RECOVERY - otherwise you will face "scatter file invalid" error later.
Click to expand...
Click to collapse
I can confirm, I lost probably many thousands of my hairs with that problem !
Tried somebody this solution on 1.10? Will it work, or i have to update to TOS-V2.01-A921?
Teclastt8 said:
Tried somebody this solution on 1.10? Will it work, or i have to update to TOS-V2.01-A921?
Click to expand...
Click to collapse
You can try this but I don't think stock firmware will boot after this. So, you can install twrp and flash custom ROM. Anyway all your data will be lost...
Sword900 said:
You can try this but I don't think stock firmware will boot after this. So, you can install twrp and flash custom ROM. Anyway all your data will be lost...
Click to expand...
Click to collapse
:good: Thank you! I don't want to use the original, I want to use your asus rom, just asked it because i want to know that the 2.01 is necessary or not.
Excuse my bad English!
Another question... if i want back the original 1.10, i only need install it via SP flash tool?
Teclastt8 said:
:good: Thank you! I don't want to use the original, I want to use your asus rom, just asked it because i want to know that the 2.01 is necessary or not.
Excuse my bad English!
Another question... if i want back the original 1.10, i only need install it via SP flash tool?
Click to expand...
Click to collapse
Yeah, you should do firmware upgrade via SP flash tool in this case.
Hi, i have tried to install TWRP for a couple days now on my Teclast T8. Tried several different drivers, scatter-files and Smart Phone Flash Tool. Any hints that i have missed?
Error message with included Smart Phone Flash Tool, scatter and TWRP.
BROM ERROR : S_DL_GET_DRAM_SETTING_FAIL (5054)
Obtain DRAM Failed!
Please check your load matches to your target which is to be downloaded.
Windows 10 10.0.17763
Build Number in Android: TOS V2.01_20180612
MediaTek USB Port (COM3) Driver 3.0.1504.0
pB2NP said:
Hi, i have tried to install TWRP for a couple days now on my Teclast T8. Tried several different drivers, scatter-files and Smart Phone Flash Tool. Any hints that i have missed?
Error message with included Smart Phone Flash Tool, scatter and TWRP.
BROM ERROR : S_DL_GET_DRAM_SETTING_FAIL (5054)
Obtain DRAM Failed!
Please check your load matches to your target which is to be downloaded.
Windows 10 10.0.17763
Build Number in Android: TOS V2.01_20180612
MediaTek USB Port (COM3) Driver 3.0.1504.0
Click to expand...
Click to collapse
Just read some previous posts, it should help. Remove all commas,spaces etc in all folders' names. If not - try to use another scatter file and version of SP flashtool.
Sword900 said:
Just read some previous posts, it should help. Remove all commas,spaces etc in all folders' names. If not - try to use another scatter file and version of SP flashtool.
Click to expand...
Click to collapse
Thanks for replying!
As you can see in this picture i have replaced the spaces in folder and file names.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Could you please refer to other scatter files that may work? I have tried with SP flashtool v 5.1824 aswell, but it's the same error there.
If I remember correctly, I did it that way:
scatter load->Twrp load->Push download button->without push volume up, plug in the usb cable
Try this, if nothing else can help.
Teclastt8 said:
If I remember correctly, I did it that way:
scatter load->Twrp load->Push download button->without push volume up, plug in the usb cable
Try this, if nothing else can help.
Click to expand...
Click to collapse
Yeeez... That worked. Thanks a lot.
@Sword900, could you add this in the description for other frustrated people like me?
I have two new T8, when i try to start new instalation latest version of facebook, messenger, instagram apps, apps can not start. App closed, send report or restart it. Not working. Tried with 1.10 and 2.10 firmware but result is the same. Others apps or games are ok. Any idea to fix it? Thank you.
Error
Deleted.
Hello all, I've been trying to install /e/ os GSI on my Redmi Note 11S. I already unlocked the bootloader.
Whenever i tried flashing system.img, (with boot.img patched manually via fastboot, not via a custom recovery), the phone would only boot fastboot. So I tried installing this custom recovery, and patch boot.img from there, but that still wouldn't work (though the recovery at least worked). So I tried installing the stock ROM, and try something else.
I went with latest fastboot EEA image and ran flash_all.sh (worked last time I tried), but this time I got an error (something about partition preloader not found). So I restarted the phone after which it got stuck in this bootloop. Can't boot into fastboot, nor recovery. Instead, the phone keeps flashing the mi logo on and off every 5 seconds. fastboot on my Linux install can't detect the phone. My Windows 10 install can't find it either, though it plays the "device connected" sound followed by the "device disconnected" sound shortly after. I can't turn the phone off either. Windows 10 USB drivers worked, or at least when I was unlocking the bootloader, so I don't think the issue is there. Any idea how to fix this?
Thank you in advance
Edit: Typos. Also I noticed that it only plays the "device connected" and "disconnected" sounds on Windows 10 only when i hold down the power and vol- buttons.
UPDATE: This tool can at least detect the phone, though I do get this error afterwards:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
UPDATE: Managed to get FASTBOOT back, thanks to this kind stranger (system is still unbootable).
UPDATE: IT'S ALIVE! Did a quick install_all.sh on the stock ROM, and it's working again! Thank you all for helping me resolve this problem
no idea
Normally you use flashall.bat and not .sh, try using flashall.bat and hopefully you'll get out of the bootloop.
Try following my "how to fix bootloop" guide again, atleast till step 4 when you get the fastboot mode back up again.
warhead1721972 said:
Normally you use flashall.bat and not .sh, try using flashall.bat and hopefully you'll get out of the bootloop.
Try following my "how to fix bootloop" guide again, atleast till step 4 when you get the fastboot mode back up again.
Click to expand...
Click to collapse
Could you send a link to the guide please? The only guide I could find on your profile is the one with the rooting, which is among the first guides I tried and it was the one to get me into this situation. Note that in your guide, it appears that you can at least get to the FASTBOOT screen, which I can't. My phone just stays on the logo for 5 seconds before rebooting, and no matter which buttons I press or hold, I can't get it to go to the FASTBOOT screen.
Also, what's the difference between flash_all.bat, and flash_all.sh, aside of one being for Linux and the other for Windows?
UPDATE: This tool can at least detect the phone, though I do get this error afterwards:
kritomas said:
Could you send a link to the guide please? The only guide I could find on your profile is the one with the rooting, which is among the first guides I tried and it was the one to get me into this situation. Note that in your guide, it appears that you can at least get to the FASTBOOT screen, which I can't. My phone just stays on the logo for 5 seconds before rebooting, and no matter which buttons I press or hold, I can't get it to go to the FASTBOOT screen.
Also, what's the difference between flash_all.bat, and flash_all.sh, aside of one being for Linux and the other for Windows?
Click to expand...
Click to collapse
Press and hold all the 3 buttons, vol +, vol - and power button at the same time, till you see the phone switched off for a few seconds.
Then press the power and vol - button to get to the fastboot mode.
About the flashall.bat, I completely forgot that you were using Linux my bad.
Also sometimes some drivers don't work well in Linux try using windows.
Did you follow the guide which was at the end of this?
warhead1721972 said:
Press and hold all the 3 buttons, vol +, vol - and power button at the same time, till you see the phone switched off for a few seconds.
Then press the power and vol - button to get to the fastboot mode.
About the flashall.bat, I completely forgot that you were using Linux my bad.
Also sometimes some drivers don't work well in Linux try using windows.
Did you follow the guide which was at the end of this?
Click to expand...
Click to collapse
Yes, that's the one, and it won't go into fastboot.
Isn't /e/ Murena GSI just android 10? I am pretty sure it won't work. I had the same problem, but I fixed it by installing stock ROM..
And that /e/ GSI is not actively developed and not even in beta stage (not usable at most cases)
Don't use SP Flash tool for full flash this phone seriously, Sp flash tool will make your phone stuck in recovery miui and show Nvdata Corrupted even you choose download only mode.
for now try to use mtkclient to flash boot.img only to both side A&B.
move your boot.img to mtk client folder
open cmd on that folder
type this command:
Code:
python mtk w boot_a,boot_b boot.img,boot.img
and try turn on your phone.
if still can't boot try to flash one by one img from your firmware
I has your same problem. Just hold the vol- for more than your usually Need and should boot into fastboot and than you flash with flashall.bat
I've sucessfully restore my phone and work as normal.
soutaminori said:
Don't use SP Flash tool for full flash this phone seriously, Sp flash tool will make your phone stuck in recovery miui and show Nvdata Corrupted even you choose download only mode.
for now try to use mtkclient to flash boot.img only to both side A&B.
move your boot.img to mtk client folder
open cmd on that folder
type this command:
Code:
python mtk w boot_a,boot_b boot.img,boot.img
and try turn on your phone.
if still can't boot try to flash one by one img from your firmware
Click to expand...
Click to collapse
Thank you so much, it worked!!!
I think. It's now at least on the FASTBOOT screen, which is progress. And the MIUI recovery is now back as well. While the system is still unbootable, I think I can take it from here. Thank you
Hypeka said:
I has your same problem. Just hold the vol- for more than your usually Need and should boot into fastboot and than you flash with flashall.bat
I've sucessfully restore my phone and work as normal.
Click to expand...
Click to collapse
That's the first thing I tried, and no luck. But I fixed it now (I think).
Very welcome, Glad to hear that
Note for everyone:
Backup this partition it's very important.
nvcfg.img, nvdata.img, nvram.img, persist.img, proinfo.img, protect1.img, protect2.img, md1img.img
Thats all partition about imei, security and network configuration for ur device. CMIW.
mtkclient also can do that,
and it's the clue:
Code:
python mtk r nvcfg,nvdata,nvram,persist,proinfo,protect1,protect2,md1img nvcfg.img,nvdata.img,nvram.img,persist.img,proinfo.img,protect1.img,protect2.img,md1img.img
Check ur mtk client folder, now you got the back up.
u can also use this Partitions Backup & Restore this tool don,t need PC for backup and restore, but i'm not really sure can be work perfectly. i just try for boot partition and its worked.
cheeerrss
Hi. Could you help me to unbrick my Note 11S 4g? I faced with bootloop after trying rooting phone by twrp. And now i can`t enter to fastboot.
When i try to - python mtk w boot_a,boot_b boot.img,boot.img
Or when I try to disable auth brom i have another one issue.
alzhuks said:
Hi. Could you help me to unbrick my Note 11S 4g? I faced with bootloop after trying rooting phone by twrp. And now i can`t enter to fastboot.
When i try to - python mtk w boot_a,boot_b boot.img,boot.img
Or when I try to disable auth brom i have another one issue.
Click to expand...
Click to collapse
i can't see mtk client log. but maybe driver problem or try to unlock BL again with THIS TOOL
alzhuks said:
Hi. Could you help me to unbrick my Note 11S 4g? I faced with bootloop after trying rooting phone by twrp. And now i can`t enter to fastboot.
When i try to - python mtk w boot_a,boot_b boot.img,boot.img
Or when I try to disable auth brom i have another one issue.
Click to expand...
Click to collapse
I myself did it with the terminal and on Linux. I didn't use the GUI, so I can't help with that. Could you send a higher res picture of the terminal please? We can't really see anything.
If you're doing this on Windows, then my guess is a driver issue (I did have to install a special driver for Windows to work with Fastboot, could be that mtk needs it too).
Hi All,
I unbricked my phone by using fresh release of mtkclient (https://github.com/bkerler/mtkclient).