My apologies if I've missed instructions somewhere. I've got a brand new 3840, but all the instructions I can find for rooting are for the 3830. Does anyone know how to root the 3840? I can provide files/etc from the device if needed.
khuey said:
My apologies if I've missed instructions somewhere. I've got a brand new 3840, but all the instructions I can find for rooting are for the 3830. Does anyone know how to root the 3840? I can provide files/etc from the device if needed.
Click to expand...
Click to collapse
perhaps you can pm @social-design-concepts
I working on resolving the issues with unpacking and packing of the boot.img and recovery.img once i finish that it shouldn't be an issue making a cwm for this 3840 and the 3740 series . . .
social-design-concepts said:
I working on resolving the issues with unpacking and packing of the boot.img and recovery.img once i finish that it shouldn't be an issue making a cwm for this 3840 and the 3740 series . . .
Click to expand...
Click to collapse
Thanks social-design-concepts, that's really cool. I can't wait to root mine and remove the dell cast, Maxx Audio stuff off it. And to install Xposed for customization.
BTW, is there a general walk through (/approach) about how to go about finding a root for a device? I see most of the popular devices have root procedure that can be followed for rooting. It would be nice if I can poke around myself and try to come up with a rooting method if not too tricky. (I know the very first step would be install drivers and get into fastboot, right? but what to do next...) Beats simply following others' path, and could be beneficial for others too.
Thanks
social-design-concepts said:
I working on resolving the issues with unpacking and packing of the boot.img and recovery.img once i finish that it shouldn't be an issue making a cwm for this 3840 and the 3740 series . . .
Click to expand...
Click to collapse
Cant wait till you get that done I have been looking everywhere on how to root this device and no resolution. Thanks.
a couple testers needed to test a new root method , sorry it took so long but i do believe i have it figured out :
[TOOL KIT] myKIT_BATCHV1.1.x :
Follow the instructions for setting up myKIT_BATCHV1.1.x use this root downloadable in that same post .
SDC_INTEL_ROOTKIT.7z
Let me know if it works . . .
I apologize for confusing so I'm using a machine translation.
at Dell Venue 8 3840 LTE
I've tried the SDC_INTEL2_ROOTKIT.7z and [TOOL KIT] myKIT_BATCHV1.1.x.
It was failed.
It will fail to write to "/sbin/adbd".
>FAILED (remote: flash_cmds error!
>)
I used "Rooting and bootloader unlocking process using OTA package" and "Unbricking Process" in opensource.dell.com previously.
Do you have any advice?
Santin said:
I apologize for confusing so I'm using a machine translation.
at Dell Venue 8 3840 LTE
I've tried the SDC_INTEL2_ROOTKIT.7z and [TOOL KIT] myKIT_BATCHV1.1.x.
It was failed.
It will fail to write to "/sbin/adbd".
>FAILED (remote: flash_cmds error!
>)
I used "Rooting and bootloader unlocking process using OTA package" and "Unbricking Process" in opensource.dell.com previously.
Do you have any advice?
Click to expand...
Click to collapse
Not at this time I'll investigate though thanks for the info. Can you post a pic of the device screen at that point?
Sent from my XT907 using XDA Free mobile app
Hi social-design-concepts
I was so confused, I do the following in order to organize.
1. I did again Unbricking Process.
2. I made a setting up a terminal minimal and OS updates(for kitkat 4.4.4).
3. And I setup ADB driver. (path is E:\myKIT_BATCHv1.1.x\mykits\driverKIT\ADB\usb_driver\android_winusb.inf)
http://forum.xda-developers.com/attachment.php?attachmentid=2963891&stc=1&d=1412770552
4. run run-me.bat.
http://forum.xda-developers.com/attachment.php?attachmentid=2963902&stc=1&d=1412771006
5. rootkit issues an error as follows.
http://forum.xda-developers.com/attachment.php?attachmentid=2963904&stc=1&d=1412771253
Whether there will be information necessary something else?
Here's where mine failed
It failed at the very first step of flashing ADBD (screen capture attached):
writing '/sbin/adbd'...
FAILED (remote: flash cmds error!)
4ge6 said:
It failed at the very first step of flashing ADBD (screen capture attached):
writing '/sbin/adbd'...
FAILED (remote: flash cmds error!)
Click to expand...
Click to collapse
As i said it was a trial it looks as if the fixed it in 4.4.4, when I get home I'll remove it from the list. I need to try to get the 4.4.2 on dells open source site booting on my fake hardware and try to capture the 4.4.4 ota sorry.
Sent from my XT907 using XDA Free mobile app
---------- Post added at 03:00 PM ---------- Previous post was at 02:56 PM ----------
Santin said:
I apologize for confusing so I'm using a machine translation.
at Dell Venue 8 3840 LTE
I've tried the SDC_INTEL2_ROOTKIT.7z and [TOOL KIT] myKIT_BATCHV1.1.x.
It was failed.
It will fail to write to "/sbin/adbd".
>FAILED (remote: flash_cmds error!
>)
I used "Rooting and bootloader unlocking process using OTA package" and "Unbricking Process" in opensource.dell.com previously.
Do you have any advice?
Click to expand...
Click to collapse
Maybe you would wanna roll back to the 4.4.2 and try to root and capture the ota should be able to make a prerooted system.img for 4.4.4
Sent from my XT907 using XDA Free mobile app
social-design-concepts said:
Maybe you would wanna roll back to the 4.4.2 and try to root and capture the ota should be able to make a prerooted system.img for 4.4.4
Sent from my XT907 using XDA Free mobile app
Click to expand...
Click to collapse
Downgrade to 4.4.2 before root might be a viable route.
But how can I downgrade to 4.4.2?
(Would only downgrading the boot partition be OK? No need to downgrade the system partition right?)
(will be looking, and report back if I can figure it out)
Although I tried various ...
I write below the work that I've tried.
*Working with non-TOOL KIT depends on the opensource.dell.com.
1. I gave a Unbricking Process again. (roll back to the 4.4.2)
Fastboot mode is not valid in this state.
Also in process of restarting at TOOL KIT, it does not take into fastboot mode even Reboot the tablet and press power + volumn down button.
2. I have enabled the fastboot mode of opensource.dell.com the "Enable fastboot mode" process in 4.4.2 above.
Therefore, I tried to start the run-me.bat,
> writing '/sbin/adbd' ...
> FAILED (remote: flash cmds error!)
Error display came out with.
3. I gave a Unbricking Process again. (roll back to the 4.4.2)
Apply OTA update for first time. (update 4.4.4)
(Fastboot mode is enabled this update later)
I tried to start the run-me.bat,
> writing '/sbin/adbd' ...
> FAILED (remote: flash cmds error!)
Error display again.
4. Apply OTA update for the second time. (update 4.4.4)
Run run-me.bat. The same error is displayed, rooting failed.
It is regrettable, but I tried writing to '/sbin/adbd' has become an error.
to social-design-concepts
And I tried to donate to you, but could not pay for you from my PayPal account(in Japan). I'm sorry.
Santin said:
I write below the work that I've tried.
*Working with non-TOOL KIT depends on the opensource.dell.com.
1. I gave a Unbricking Process again. (roll back to the 4.4.2)
Fastboot mode is not valid in this state.
Also in process of restarting at TOOL KIT, it does not take into fastboot mode even Reboot the tablet and press power + volumn down button.
2. I have enabled the fastboot mode of opensource.dell.com the "Enable fastboot mode" process in 4.4.2 above.
Therefore, I tried to start the run-me.bat,
> writing '/sbin/adbd' ...
> FAILED (remote: flash cmds error!)
Error display came out with.
3. I gave a Unbricking Process again. (roll back to the 4.4.2)
Apply OTA update for first time. (update 4.4.4)
(Fastboot mode is enabled this update later)
I tried to start the run-me.bat,
> writing '/sbin/adbd' ...
> FAILED (remote: flash cmds error!)
Error display again.
4. Apply OTA update for the second time. (update 4.4.4)
Run run-me.bat. The same error is displayed, rooting failed.
It is regrettable, but I tried writing to '/sbin/adbd' has become an error.
to social-design-concepts
And I tried to donate to you, but could not pay for you from my PayPal account(in Japan). I'm sorry.
Click to expand...
Click to collapse
Could you upload the ota some where?
Sent from my XT907 using XDA Free mobile app
social-design-concepts said:
Could you upload the ota some where?
Sent from my XT907 using XDA Free mobile app
Click to expand...
Click to collapse
I Uploaded to google drive the OTA package, I sent a PM who wrote the url.
Santin said:
I Uploaded to google drive the OTA package, I sent a PM who wrote the url.
Click to expand...
Click to collapse
I finally received my new Dell 3840 today and was able to capture some details about the OTA update using Wireshark.
http://mobileupdate.dell.com/?version=YTP802A119530 will bring you to a webpage where you can download the OTA package: YTP802A125330-i-YTP802A119530-2014-08-23-38.pkg
Alternatively, you can just download this:
http://mobileupdate.dell.com/Packag...P802A125330-i-YTP802A119530-2014-08-23-38.pkg
The .pkg file is just a regular update.zip. If you rename it to YTP802A125330-i-YTP802A119530-2014-08-23-38.pkg.zip, you can unzip it.
It looks like the Android updater also pulls down a couple other files from Google:
http://www.gstatic.com/android/config_update/07172013-sms-metadata.txt
http://www.gstatic.com/android/config_update/07172013-sms-blacklist.txt
-Howard
Is there a 4.4.4 image, available for download, would like to see if it can be modified to run on 3830.
sent from my kingSing T1 via taptalk
vampirefo said:
Is there a 4.4.4 image, available for download, would like to see if it can be modified to run on 3830.
sent from my kingSing T1 via taptalk
Click to expand...
Click to collapse
There still no root for them yet, so I don't think you'll find one.
Sent from my XT907 using XDA Free mobile app
And another OTA update after 4.4.4:
http://mobileupdate.dell.com/?version=YTP802A125330
hharte said:
And another OTA update after 4.4.4:
Click to expand...
Click to collapse
How to install it properly?
Thanks.
Related
Hi,
Does anyone know how to fix the problem in the attached pictures?
Thanks,
Seems to be an issue with your bootloader, try flashing a new one through fastboot
fastboot flash hboot hboot.img
Sent from my Nexus 4 using xda premium
i got same problem, Does anyone know how to fix it?
Fastboot flash a Google stock image for it. Worked for me..... twice
Sent from carbon note 2 on XDA premium app
Booting Failed
Im having the same problem, Can someone help me? I am a bit of a noob. i did download nexus root tool kit. But now i cant even get it to be seen on the computer. all i can hit is restart bootloader or power off. Everything else leads to booting failed.please help need tablet for school.
Help!!!
Okay. i messed up somewhere when trying to flash back to factory rom and completely restore my Nexus 7(I had rooted it and flashed to a custom rom perfectly fine, just wanted to go back to factory just because). Because now whenever i turn on my nexus it says booting failed. Can someone use team viewer or something with me to help me get this fixed. i really need my Nexus for school...
If you need teamviewer I'll be at a PC soon but you should be able to do all this yourself quite easily
Which model do you have 2012? 2013? WiFi? Gsm?
Do you have adb and fastboot set up on PC?
Windows? Linux?
Bootloader locked or unlocked right now?
Boot to bootloader and write down everything on screen here
Let me know and I'll get you the proper software
Sent from my Nexus 7 using XDA Premium 4 mobile app
Thanks for replying
demkantor said:
If you need teamviewer I'll be at a PC soon but you should be able to do all this yourself quite easily
Which model do you have 2012? 2013? WiFi? Gsm?
Do you have adb and fastboot set up on PC?
Windows? Linux?
Bootloader locked or unlocked right now?
Boot to bootloader and write down everything on screen here
Let me know and I'll get you the proper software
Sent from my Nexus 7 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I have the 2012 wifi version of the Nexus 7. i have ADB set up on my computer but i'm not sure about fastboot... Bootloader is unlocked. just booted to bootloader, it says google in the middle, a little unlocked lock at the bottom, and with the volume up and down i can choose start, restart bootloader, recovery mode, and power off. When i press start, nothing happens, the screen flashes though for half a second.... Sometimes it will say boot failed at the top left.
Thanks in advanced. i would extremely prefer to do this in team viewer because i'm good with electronics most of the time, but when it comes to this stuff i have no clue what to do. i have watched countless videos with no success.
You'll need to download factory image here
https://developers.google.com/android/nexus/images
Unzip it
Run flash all.bat from fastboot
http://forum.xda-developers.com/showthread.php?t=2277112
I won't be near a PC for about 7-8 hours. If your stuck let me know around then and I can help
Sent from my Nexus 4 using XDA Premium 4 mobile app
THanks!
demkantor said:
You'll need to download factory image here
https://developers.google.com/android/nexus/images
Unzip it
Run flash all.bat from fastboot
http://forum.xda-developers.com/showthread.php?t=2277112
I won't be near a PC for about 7-8 hours. If your stuck let me know around then and I can help
Sent from my Nexus 4 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Ok so i did the flash all thing and it worked!!! Now do i follow the custom recovery steps? because still when i press start it says booting failed
Edit: i went ahead and did the recovery thing from the one i downloaded from the site you told me to go to. and i still get booting failed
Try this
fastboot erase system -w
fastboot erase boot
fastboot erase recovery
Now double check you downloaded the correct factory image probably a good idea to check md5sum as well
Then run flashall.bat again
Let me know if that works
Sent from my Nexus 4 using XDA Premium 4 mobile app
errors
demkantor said:
Try this
fastboot erase system -w
fastboot erase boot
fastboot erase recovery
Now double check you downloaded the correct factory image probably a good idea to check md5sum as well
Then run flashall.bat again
Let me know if that works
Sent from my Nexus 4 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
when typing in the first command it gave me all okays until erasing 'cache'...
Failed <command write failed <No such device or address>>
After that i thought "hmm maybe thats supposed to happen?" so i went ahead to the erase boot command, again
erasing 'boot'...
Failed <command write failed <unknown error>>
Please help. im soooo confused im about to explode... haha
Thanks
EDIT: i realize whenever i run the flash all file, it says
sending bootloader
Failed <command write failed <Invalid argument>>
and then bootloader reboots fine...
then
checking version-bootloader...
Failed
Device version-bootloader is '4.18' .
Update requires '4.23' .
Is this why its not working?? if so how do i update my bootloader?
Can you either attach a pic or write down everything from bootloader screen line by line
Sent from my Nexus 4 using XDA Premium 4 mobile app
Pics
demkantor said:
can you either attach a pic or write down everything from bootloader screen line by line
sent from my nexus 4 using xda premium 4 mobile app
Click to expand...
Click to collapse
View attachment 2551680
View attachment 2551681
First Picture is the flashall file
Second picture is when i type the fastboot erase system -w command
xlilCHeesEitxX3 said:
View attachment 2551680
View attachment 2551681
First Picture is the flashall file
Second picture is when i type the fastboot erase system -w command
Click to expand...
Click to collapse
If you meant the bootloader screen of my nexus im sorry!!
okay so it has the volume rocker buttons and stuff at the top right as usual.
now in order from top to bottom
Fastboot mode (red letters)
Product Name - grouper
Variant - grouper
HW Version - ER3
Bootloader Version - 4.18
Baseband version - N/A
Serial Number - 015d24a42b23ea09
Signing - not defined yet
Lock State - Unlocked (red letters)
hope this is what you were looking for
well I'm at a PC if you want to use team view, if you don't get this until later what I would do is flash everything separate
fastboot flash bootloader bootloader-grouper-4.23.img
(or whatever it is labled)
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot flash data userdata.img
fastboot flash boot boot.img
if this doesn't work than put up the screenshots of cmd again
Team Viewer
demkantor said:
well I'm at a PC if you want to use team view, if you don't get this until later what I would do is flash everything separate
fastboot flash bootloader bootloader-grouper-4.23.img
(or whatever it is labled)
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot flash data userdata.img
fastboot flash boot boot.img
if this doesn't work than put up the screenshots of cmd again
Click to expand...
Click to collapse
I really hope you are still able to use Team Viewer at the time. I tried flashing everything separately but still a no go ....
Thanks so much for all the help so far.. i really appreciate it.
Screenshots
xlilCHeesEitxX3 said:
I really hope you are still able to use Team Viewer at the time. I tried flashing everything separately but still a no go ....
Thanks so much for all the help so far.. i really appreciate it.
Click to expand...
Click to collapse
View attachment 2552860
View attachment 2552861
1st image is when i flash the system
2nd is when i flash the bootloader
Yeah this is not looking too good, I've seen a few times that people have gotten there nexi working when the failed boot pops up but when all these flashes fail it becomes unlikely. Is warranty up? If it is we can try when I get to a PC again but that may not be for a while.
Sent from my Nexus 4 using XDA Premium 4 mobile app
demkantor said:
Yeah this is not looking too good, I've seen a few times that people have gotten there nexi working when the failed boot pops up but when all these flashes fail it becomes unlikely. Is warranty up? If it is we can try when I get to a PC again but that may not be for a while.
Sent from my Nexus 4 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I think my warranty is up... but alright. maybe im doing something wrong? who knows hopefully we can get it fixed
---------- Post added at 10:54 AM ---------- Previous post was at 10:26 AM ----------
xlilCHeesEitxX3 said:
I think my warranty is up... but alright. maybe im doing something wrong? who knows hopefully we can get it fixed
Click to expand...
Click to collapse
i finnaly got the bootloader to flash. so now everything works except when i try to flash the system... it says
erasing 'system'...
OKAY ( 0.095s)
Sending 'system' <471804 KB>...
FAILED <unknown status code>
finished. total time: 61.355s
hopefully you know of a fix
Q&A for [ROM][STOCK][JB 4.2.2] ASUS MeMO Pad 8 (ME180A-WW-3.1.0.42)
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [ROM][STOCK][JB 4.2.2] ASUS MeMO Pad 8 (ME180A-WW-3.1.0.42). If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
My asus memo pad 8 not booting and not reach to check usb debuging...
When conecct usb fastboot mode device not found in win 8.1
Help me please
Sorry my bad english
hhzznn said:
My asus memo pad 8 not booting and not reach to check usb debuging...
When conecct usb fastboot mode device not found in win 8.1
Help me please
Sorry my bad english
Click to expand...
Click to collapse
Hello there,
If not using the "adbsetup" drivers or the ones off the ASUS website (sorry, couldn't find the ASUS drivers when I looked ), use one of the above. If using one and still not connecting, try the other option.
Also, check your USB ports to make sure you are not connecting via a USB 3.x standard. Android (or at least some Android devices) don't like those.
If all else fails, you may need a Linux build
Hope this provides a head start.
Sent from my LG-D520 using XDA Free mobile app
help me please
hello
my asus memo pad 8 not booting becuse im delete odex file in system/app after rooting..now device not booting any way!wipe data and wipe cash dont answer and not booting yet!!
in fast boot mode unlock oem not answering...
please help me ...
email :[email protected]
hhzznn said:
hello
my asus memo pad 8 not booting becuse im delete odex file in system/app after rooting..now device not booting any way!wipe data and wipe cash dont answer and not booting yet!!
in fast boot mode unlock oem not answering...
please help me ...
email :[email protected]
Click to expand...
Click to collapse
Looks you got a little further... :good:
From what I remember when I followed the guide, there was no feedback (nothing on the screen, and tablet remains black) on when you issue the unlock commands - which by the way, are:
Code:
fastboot oem unlock61646
fastboot oem unlockD696E
Then, reboot the bootloader and install CWM (first line may be substituted with rebooting into fastboot by hand):
Code:
fastboot reboot-bootloader
fastboot flash recovery recovery_cwm.img
fastboot flash misc misc_reboot-recovery.img
fastboot reboot
You shouldn't get a write-protect error this time around. Hope this helps.
By the way, your SKU is WW version, right? If not, my ROM may not help you (without going the long way around of instead of flashing the ROM, copying the odex files back into /system/app using CWM's ADB push command). Just a warning. If you are not WW, and insist on flashing anyway, I would highly recommend a nandroid backup (and probably copied) to MicroSD to protect your original (broken) ROM.
help me
my pad is sku = ww
in the fastboot mode i type fastboot oem unlock61646 and i get asnwer okey and finish but when type fastboot oem unlockD696E i get answer oem admunlock not request
help me please
hhzznn said:
my pad is sku = ww
in the fastboot mode i type fastboot oem unlock61646 and i get asnwer okey and finish but when type fastboot oem unlockD696E i get answer oem admunlock not request
help me please
Click to expand...
Click to collapse
The latter may have been for the 10" model - cannot remember. Try rebooting into fastboot now and see if CWM install takes.
Sent from my LG-D520 using XDA Free mobile app
joel.maxuel said:
The latter may have been for the 10" model - cannot remember. Try rebooting into fastboot now and see if CWM install takes.
Sent from my LG-D520 using XDA Free mobile app
Click to expand...
Click to collapse
the code:fastboot unlock oem61646 worked but fastboot oemD696E not working
in stock recovery i cant install rom.zip
and in fastboot when install recovery cwm answer bootloader lock
any offer for me?
---------- Post added at 09:14 AM ---------- Previous post was at 09:07 AM ----------
**you may need a Linux build **
i have a linux base ,, may you help me??
hhzznn said:
**you may need a Linux build **
i have a linux base ,, may you help me??
Click to expand...
Click to collapse
May not be as important now (if you got fastboot working in windows), but what distro do you have? I am familiar with Debian, Ubuntu, and their derivates.
Sent from my LG-D520 using XDA Free mobile app
joel.maxuel said:
May not be as important now (if you got fastboot working in windows), but what distro do you have? I am familiar with Debian, Ubuntu, and their derivates.
Sent from my LG-D520 using XDA Free mobile app
Click to expand...
Click to collapse
i have ubuntu....what should i do?
hhzznn said:
i have ubuntu....what should i do?
Click to expand...
Click to collapse
In a terminal...
apt-get install android-tools-fastboot
...would be a good start. You may need to register the device vendor in your configuration, which I can research later if...
fastboot devices
...lists nothing. Hope this helps.
Sent from my LG-D520 using XDA Free mobile app
Hi...I was having issues with my ME180A (WW variant) where the OTA update would never take (I had the tablet rooted) so when I finally found this thread and the associated stock ROM install instructions I thought I would give it a go to see if I could clean up the mess that I must have made rooting and de-bloating my tablet. I got adb and fastboot install on my win 8.1 machine with no problems, got CWM (from your link) installed on my tablet with no issues but when I tried to flash your original rom onto my tablet it would get partially through the install and then I would get
set_metadata_recursive; some changes failed
error in /data/media/0/K00L_Back_To_Stock_Untouched_Orig.zip
status 7
and the install would fail. I think this has somehow screwed up my bootloader because now my tablet constantly reboots into CWM no matter what I do. When the tablet is connected to my Windows machine, the drivers don't get loaded so ADB and fastboot just sit at "waiting for device" after I try some of the different commands. I'm familiar with flashing ROMs onto my phones and have never had an issue but I have had a lot of difficulties with this tablet. Do you have any advice to solve the bootloader and ROM flashing issues?
Thanks in advance for any assistance that can be provided.
Syncline said:
Hi...I was having issues with my ME180A (WW variant) where the OTA update would never take (I had the tablet rooted) so when I finally found this thread and the associated stock ROM install instructions I thought I would give it a go to see if I could clean up the mess that I must have made rooting and de-bloating my tablet. I got adb and fastboot install on my win 8.1 machine with no problems, got CWM (from your link) installed on my tablet with no issues but when I tried to flash your original rom onto my tablet it would get partially through the install and then I would get
set_metadata_recursive; some changes failed
error in /data/media/0/K00L_Back_To_Stock_Untouched_Orig.zip
status 7
and the install would fail. I think this has somehow screwed up my bootloader because now my tablet constantly reboots into CWM no matter what I do. When the tablet is connected to my Windows machine, the drivers don't get loaded so ADB and fastboot just sit at "waiting for device" after I try some of the different commands. I'm familiar with flashing ROMs onto my phones and have never had an issue but I have had a lot of difficulties with this tablet. Do you have any advice to solve the bootloader and ROM flashing issues?
Thanks in advance for any assistance that can be provided.
Click to expand...
Click to collapse
Hmmmm, I guess this is why I made two files, but the other may have similar problems because of this issue.
I will see if I can change the updater program. In the meantime, pop the other back-to-stock file onto MicroSD, reload CWM, and try that one. Report back to me in any case.
UPDATE:
If the above fails, try this one as well.
joel.maxuel said:
Hmmmm, I guess this is why I made two files, but the other may have similar problems because of this issue.
I will see if I can change the updater program. In the meantime, pop the other back-to-stock file onto MicroSD, reload CWM, and try that one. Report back to me in any case.
UPDATE:
If the above fails, try this one as well.
Click to expand...
Click to collapse
Joel,
I tried to flash the other back-to-stock file as you recommended however the end result was the same.
set_metadata_recursive: some changes failed
E:Error in /external_sd/K00L_Back_To_Stock_Re-Perm-Linked.zip
(Status 7)
Installation aborted.
Are there any other things that you can think of that I can try to get this issue fixed? And thanks for all your assistance, it is appreciated.
Syncline said:
Joel,
I tried to flash the other back-to-stock file as you recommended however the end result was the same.
set_metadata_recursive: some changes failed
E:Error in /external_sd/K00L_Back_To_Stock_Re-Perm-Linked.zip
(Status 7)
Installation aborted.
Are there any other things that you can think of that I can try to get this issue fixed? And thanks for all your assistance, it is appreciated.
Click to expand...
Click to collapse
So the third file I created (in my post update) replaces the updater-binary that would be causing issues with that particular CWM.
Third times the charm... :fingers-crossed:
joel.maxuel said:
So the third file I created (in my post update) replaces the updater-binary that would be causing issues with that particular CWM.
Third times the charm... :fingers-crossed:
Click to expand...
Click to collapse
Things worked great that time with the flash working and the tablet rebooting properly however now it is asking for a password to decrypt storage and this is the first time I've ever seen this. Any thoughts?
Syncline said:
Things worked great that time with the flash working and the tablet rebooting properly however now it is asking for a password to decrypt storage and this is the first time I've ever seen this. Any thoughts?
Click to expand...
Click to collapse
Were you encrypted before?
Could do is a nandroid of the data partition and then factory reset. You will have to set your apps up by hand again, but it is better than that message.
Sent from my MeMO Pad 8"
joel.maxuel said:
Were you encrypted before?
Could do is a nandroid of the data partition and then factory reset. You will have to set your apps up by hand again, but it is better than that message.
Sent from my MeMO Pad 8"
Click to expand...
Click to collapse
No I wasn't encrypted before but from what I read it seems to involve a failure to mount the DATA partition correctly, and the Android OS erroneously assumes it's encrypted. I'm not overly concerned about setting up apps by hand, I do have a titanium backup of my apps and data. As I'm still at work, I can't do too much playing around on my tablet. I don't have access to my personal computer that has all my tools like adb, fastboot, etc. until the work day is done. I've said it a couple of times, but I truly appreciate the assistance that you've provided.
UPDATE: After booting back into CWM, doing a factory reset and a format of the /data partition seems to have done the trick. I'm back into my tablet and currently updating all the pre-installed apps that require it. One more quick question Joel, you mention that the ROM is rooted and I do have SuperSU installed, however when I run the app it tells me there is no SU binary installed and SuperSU cannot install it, can I just install the latest version of a flashable SuperSU zip with CWM to fix this?
Syncline said:
UPDATE: After booting back into CWM, doing a factory reset and a format of the /data partition seems to have done the trick. I'm back into my tablet and currently updating all the pre-installed apps that require it. One more quick question Joel, you mention that the ROM is rooted and I do have SuperSU installed, however when I run the app it tells me there is no SU binary installed and SuperSU cannot install it, can I just install the latest version of a flashable SuperSU zip with CWM to fix this?
Click to expand...
Click to collapse
That's an interesting side effect...never had that happen before.
You can try it, and let me know. Hopefully your CWM is still kicking around, or else you will have to reinstall via fastboot. Or alternatively, just re-root normally (like with Kingo).
By the way, before you do that, does /system/xbin/su exist? Or what you could answer, is you could download Voodoo OTA RootKeeper and report back which values are not checked off. I think SuperSU update.zip places the su binary, nothing else. But we shall see.
Sorry Joel, I didn't see your reply before I flashed the SuperSU zip but it did work, my tablet is rooted again.
Hi,
I tried to install the new 5.1.1 Android version, but I have a issue :
1°) my Device States is locked
2°) my Device doesn't not start I have the animation + Android is uprading your app + Starting your app in loop, but no access to the devs mod and activate oem install in the devs option.
My Question is :
How can i fix this ^^ ?
Ncisboys said:
Hi,
I tried to install the new 5.1.1 Android version, but I have a issue :
1°) my Device States is locked
2°) my Device doesn't not start I have the animation + Android is uprading your app + Starting your app in loop, but no access to the devs mod and activate oem install in the devs option.
My Question is :
How can i fix this ^^ ?
Click to expand...
Click to collapse
Sent from my Nexus 9 using XDA Free mobile app
---------- Post added at 07:19 PM ---------- Previous post was at 07:18 PM ----------
Ncisboys said:
Hi,
I tried to install the new 5.1.1 Android version, but I have a issue :
1°) my Device States is locked
2°) my Device doesn't not start I have the animation + Android is uprading your app + Starting your app in loop, but no access to the devs mod and activate oem install in the devs option.
My Question is :
How can i fix this ^^ ?
Click to expand...
Click to collapse
How did you try to install the update? By OTA or other means? Can you boot into recovery?
Sent from my Nexus 9 using XDA Free mobile app
---------- Post added at 07:20 PM ---------- Previous post was at 07:19 PM ----------
Ncisboys said:
Hi,
I tried to install the new 5.1.1 Android version, but I have a issue :
1°) my Device States is locked
2°) my Device doesn't not start I have the animation + Android is uprading your app + Starting your app in loop, but no access to the devs mod and activate oem install in the devs option.
My Question is :
How can i fix this ^^ ?
Click to expand...
Click to collapse
How did you try to install the update? By OTA or other means? Can you boot into recovery?
Sent from my Nexus 9 using XDA Free mobile app
I try by the factory file with the script
Some others informations. I try the recovery mod a the command adb sideload 5.1.1 version OTA file. I have an issue during the sending (expected a previous version). I don't remember the exact message but it failed
Ncisboys said:
Some others informations. I try the recovery mod a the command adb sideload 5.1.1 version OTA file. I have an issue during the sending (expected a previous version). I don't remember the exact message but it failed
Click to expand...
Click to collapse
We can't help you without the error message. Try it again and write it down.
Package*expects*build fingerprint of google/volantis/flounder: + Version Number
Ncisboys said:
Package*expects*build fingerprint of google/volantis/flounder: + Version Number
Click to expand...
Click to collapse
The OTA will only work if you are currently on 5.0.2. What version is currently on your N9?
5.0.2. But something strange. On the bootloader I can see Os n/a ... It is normal?
Maybe can you explain how can I unlock oem without having access to the development option. If I can unlock it maybe I can flash factory image again
Simple answer.. You can't.
Ncisboys said:
Maybe can you explain how can I unlock oem without having access to the development option. If I can unlock it maybe I can flash factory image again
Click to expand...
Click to collapse
"Enable OEM Unlock" is an option within Developer Options that needs to be enabled in order to unlock the bootloader.
IMHO the 1st three things everyone who owns this device should do immediately is :
1.) Enable Developer Options ("how to's" are all over the place on the net and easily found.)
2.) Put a check box in "Enable OEM Unlock" in Developer Options
3.) Put a check box in "Enable USB debugging" in Developer Options.
So I can't use my nexus 9 anymore?
Assuming you grabbed the factory image from the google developer site you should have seen following the instructions on that page...
To flash a system image:
1.) Download the appropriate system image for your device below, then unzip it to a safe directory.
2.) Connect your device to your computer over USB.
3.) Start the device in fastboot mode with one of the following methods:
Using the adb tool: With the device powered on, execute:
adb reboot bootloader
4.) If necessary, unlock the device's bootloader by running:
fastboot oem unlock
STEP 4 is critical ...
What isn't mentioned here is that on the Nexus 9, in order for this command to be successfully executed, "Enable OEM Unlock" must 1st be checked off under Developer Options in the OS.
So you are now in a chicken and egg situation,,, You need to flash the factory image to get your device back up and running but unfortunately you need to have a device up and running to enable oem unlock in the 1st place.
You will likely have to RMA your device.
Ncisboys said:
So I can't use my nexus 9 anymore?
Click to expand...
Click to collapse
What is RMA?
Google it please.
Ncisboys said:
What is RMA?
Click to expand...
Click to collapse
I saw it after asking. I thought I was a manipulation...
Ncisboys said:
I saw it after asking. I thought I was a manipulation...
Click to expand...
Click to collapse
Ha, very funny. (although I'm sure it's not to you).
Yup, you'll have to return the device for service and/or replacement.
Thank you for the help.
I am trying to ultimately root this device and it is not working.
I tried to install an older build system and I'm getting the following error.
"downgraded security version update gpt_main version failed. preflash validation failed for GPT"
What does this mean? I'm new to this and could use some help.
Which file did you use to downgrade it?
I started getting the validation failure when I got to flashing system.IMG. I was using the 4.4.4 SU6-7 files.
Use the 6-7 files from crashxxl thread to downgrade using rsdlite. Then do all the stuff to root the device. If it doesn't work in rsdlite try doing it manually from your computer using fastboot. Open the XML and manually type in the commands in fastboot. You can find tutorials on how to do it exactly. Make sure when u do it manually you do mfastboot system system.img when u flash the system file.
CustomStuff said:
Use the 6-7 files from crashxxl thread to downgrade using rsdlite. Then do all the stuff to root the device. If it doesn't work in rsdlite try doing it manually from your computer using fastboot. Open the XML and manually type in the commands in fastboot. You can find tutorials on how to do it exactly. Make sure when u do it manually you do mfastboot system system.img when u flash the system file.
Click to expand...
Click to collapse
As a newbie to this process how do you "manually" do this? You mention there are tutorials on how to do it. If you could be so kind can you point me directly to where the tutorial is.
Thanks in Advance.
Same Issue
Rocketmaker10000 said:
As a newbie to this process how do you "manually" do this? You mention there are tutorials on how to do it. If you could be so kind can you point me directly to where the tutorial is.
Thanks in Advance.
Click to expand...
Click to collapse
I am having the same issue and do not know how to do it manually. I need someone that understands that I am a newbie and point me in the right direction I dont want anyone to do the work for me. Thanx
Any news about to root the iRulu V3?
Boris The Spider said:
Any news about to root the iRulu V3?
Click to expand...
Click to collapse
I can't find any information on how to root this device at all...
I did notice in the developer options there is a "allow bootloader to be unlocked" option. Is there anything we can do with that?
volcomyae23 said:
I can't find any information on how to root this device at all...
I did notice in the developer options there is a "allow bootloader to be unlocked" option. Is there anything we can do with that?
Click to expand...
Click to collapse
i am also interested in rooting this phone, i have the firmware if anyone can make a custom recovery in order to root it.
i have tried every rooting tool without success.
I'm also looking for a root method for the v3.
It's an inexpensive, neat, non bloatware phone which is really underrated and unappreciated by the rooting community. I also have the firmware and I'm willing to donate the cost of the phone to whomever can post a successful root method?
I have heard that framaroot 1.9.1 would root this phone.
I found this solution in China web site.
Sent from my Nexus 5 using xda premium
Please,somebody can give me the firmware link?
Thx
I'm not sure which serial number it is...
N.Ákos said:
Please,somebody can give me the firmware link?
Thx
Click to expand...
Click to collapse
Right from irulu.
https://www.irulu.com/download/lists.html
Can anyone help verify the serial for the V3 2gb/16gb?
I can't find the firmware on Irulu's website
Hi
I believe that this is firmware:x1067wf1601073e.
Confirm if this is correct.
When searching for this use PC or desktop mode.
Sent from my Nexus 5 using xda premium
This is the link i got from seller, i flashed and everything ok.
https : // yunpan . cn / crdNUgR8G5uWj
(remove spaces).
key 857b
model 2g/16g
marsian0 said:
This is the link i got from seller, i flashed and everything ok.
https : // yunpan . cn / crdNUgR8G5uWj
(remove spaces).
key 857b
model 2g/16g
Click to expand...
Click to collapse
how did you flash it (using what)?
In the zip are the instructions, and the tools required (qpst or some). My device no longer works, cause i flashed by mistake another firmware from another device, it boots but the touch is totally messed up.
Sent from my Nexus 6 using Tapatalk
I downloaded the above V3 high configuration and all the tools and instructions are there in the zip file. Here is the problem though with rooting the device. The device needs to have the bootloader unlocked prior to rooting and if you check your device you'll find that the bootloader is locked on it. I've tried all the oem unlock options and none of it works because it appears that irulu has the fastboot commands turn off for the most part on our device. What we need to do now is to figure out how to edit the bootloader files, ie aboot.c specifically, to allow for bootloader unlocking, then after we do that and flash that bootloader to the device we'll be able to install a custom recovery and root it probably pretty easily. Anyways, if anyone that knows a little bit more about how to edit those files and stuff would like to get involved in this I can confirm that the above link to the V3 firmware is legit and contains the correct files and firmware.
Actually I take that back. I was able to unlock the bootloader with the command 'fastboot oem forceunlock' followed by fastboot oem unlock-go just to be sure and then I checked with fastboot oem device-info and it then stated that the bootloader was indeed unlocked. So that's good news, now we just need to figure out a way to root and install a custom recovery.
I'm pretty satisfied with the V3 2GB phone the way it is coming out of the box.
The only reason I wish to root the device is to get rid of that stupid and annoying bootup music file .
The file on the irulu site is for the 1GB V3 version phone.
I can see that that the link supplied in the past post is for the V3 2GB US LTE device ?
Is that correct?
Thank You
Going to take 2 days to download the V3 High Configuration firmware.
Anyone have a better link so far irulu has not assisted.
Thanks.
http://forum.xda-developers.com/showthread.php?p=32965365
How to compile twrp.
Sent from my Nexus 6 using xda premium
Ended up downloading the 1.6GB file using my cell phone using T-mobile.
Centurylink fiber has some kind of blocks against Chinese file sharing .
Finally!
Okay I finally managed to root this god damn phone lol I had to port a twrp recovery.img and after trial and error more times then I can count I finally managed to flash a working twrp recovery on it and then from there flashed the latest SuperSU flashable zip via twrp and now it's rooted and good to go. When I get a chance a little later I'll post the twrp that I made if anyone wants to try out out.
BigDizawg2015 said:
Okay I finally managed to root this god damn phone lol I had to port a twrp recovery.img and after trial and error more times then I can count I finally managed to flash a working twrp recovery on it and then from there flashed the latest SuperSU flashable zip via twrp and now it's rooted and good to go. When I get a chance a little later I'll post the twrp that I made if anyone wants to try out out.
Click to expand...
Click to collapse
Thank You for sharing your skills.