Related
Okay, have had my Gtab since late November, initially rooted it and installed Google services (market and gmail), later flashed to TnT-lite 2.2 then 3.1.4. Flashed over to Vegan b5.1 recently everything was great......
Then I mistakenly "updated" ClockworkMod Recovery and it's been a crash and burn ever since.
Got the Magic Mis-Match or whatever and tried to correct that has now made my Gtab a non-functional paperweight.
I can NVFlash the stock image (or even the NVFlash of TnT-lite 1.02) and the tablet will boot after the flash and function. Power it off (or do something that requires a reboot) and the tablet will no longer function. No power on (that I can tell), can't boot to recovery......and if I plug the tablet in to the PC I can NVFlash it and it boots. It's like it's stuck in APX mode now. I just have to plug it in to the PC, no Power + Volume- combo.....just plug the USB in and run NVFlash. It boots (to whatever I flashed) and will run until I power it off or try to reboot.
I've pulled it open and pressed the reset button, I've drained the battery until the OS shut the tablet down and then waited about 24 hours until trying anything again....neither of those changed anything...
Is there anything else I can try besides throwing it against a brick wall?
I'd really like something to completely wipe/format/repartition the tablet completely back to factory and start over......
Getting APX mode to function is not a problem......so I can NVFlash it but what I've tried so far has not worked (it doesn't delete the data partition, etc..as I reflash and it's right where it was before I turned it off).
Windows or Ubuntu methods are fine....I'd just like to get this tablet functional again.
Your tablet is bricked
I`m sorry to be the bearer of bad news, but im afraid your tablet has been bricked, meaning that irreversible damage has been done to your device after tampering with it. Any wrong steps and your device becomes a paperweight. You have now choice but to get a new tablet or phone. You cant send that in for repair as flashing a custom rom would have voided your warranty, sorrry
With APX mode still accessible I do not believe the tablet is "bricked" at this point.
Something is preventing it from "booting" normally though it can boot after an nvflash.
you are using nvflash to install a temporary firmware onto your device. however, the original firmware on you device has been damaged beyond repair and the only solution is to use a hardware debug board and hook it up to somewhere in the motherboard of your tab and do stuff even i dont know how to.
that is the meaning of bricked!!!
tcrews said:
With APX mode still accessible I do not believe the tablet is "bricked" at this point.
Something is preventing it from "booting" normally though it can boot after an nvflash.
Click to expand...
Click to collapse
Hi,
Did you look through this thread:
http://forum.xda-developers.com/showthread.x?t=865058&highlight=stuck+apx&page=2
Sorry to hear about your plight ...
One of the suggestions there was, after you NVflashed to stock, to install Z4root and then root it. There was another post about holding both volume + and - while powering on.
I kind of agree that if you can NVflash, you should be able to unbrick-ify it. If none of those things work, maybe roebeet or rothnic can help?
Sorry if this is not too helpful...
Jim
P.S. Question: Are you sure/do you know if you might have one of those few "320" units, the ones with the 1GB RAM instead of the 512MB RAM? I seem to recall that roebeet said that those are partitioned differently, and that the stock NVflash wouldn't work with them, so maybe that might explain why? Just a thought...
IT IS NOT BRICKED. You need to go to the development forum and read about nvflashing all partitions back to stock. As long as you can get into apx mode you haven't bricked it. Most likely your partitions are screwed up. Yoour recovery partition seems to be wiped and possibly your boot partition too. Your tab doesnt know what to do when you turn it on so it goee to apx. There is a thread in devekopment that shows you how to go back to stock with all partition
HERE IS THE LINK
http://forum.xda-developers.com/showthread.php?t=861950
siidheesh said:
I`m sorry to be the bearer of bad news, but im afraid your tablet has been bricked, meaning that irreversible damage has been done to your device after tampering with it. Any wrong steps and your device becomes a paperweight. You have now choice but to get a new tablet or phone. You cant send that in for repair as flashing a custom rom would have voided your warranty, sorrry
Click to expand...
Click to collapse
WRONG!
rayden25 said:
WRONG!
Click to expand...
Click to collapse
With what little I know (still learning) about the Gtab, I agree with what rayden and some others have said. The Gtab is probably one of the few (maybe the only one) tablets that have the tools to be "almost" unbrickable.
Just about the only thing that is not there is a JTAG port (and there's probably one there that hasn't been unearthed).
Hopefully we aren't all wrong about that ...
JMHO...
Jim
You really dont need a jtag because of the apx mode. Apx is almost like jtag in a sense, it gives you direct access to flash what you need to. Thats why his tab will boot the one time but something else is borked up. The more i think about it the more i feel he has a messed up recovery partition or boot partition. He was playing with clockwork when this all started which gets flashed to recovery. If he flashes a stock recovery partition he should be good.
Oh make sure to take any update.zip off sdcard so when you do get recovery back it doesnt flash something else.
Yea that sux dude. I be worried when I'm flashing roms of this happening. Sum ppl flash just anything just to do it.
Sorry about ur device..
Sent from my HTC Vision using XDA App
Tcrews,
BTW, there's also an IRC channel where some folks hang out:
http://forum.xda-developers.com/showthread.php?t=888465
If someone's there they might help.
Jim
jimcpl said:
Hi,
Did you look through this thread:
http://forum.xda-developers.com/showthread.x?t=865058&highlight=stuck+apx&page=2
Click to expand...
Click to collapse
Yep, that got me flashed back to a stock image and even to a TnT-lite 1.02 image. Still not able to boot without flashing first.
jimcpl said:
Hi,
One of the suggestions there was, after you NVflashed to stock, to install Z4root and then root it. There was another post about holding both volume + and - while powering on.
Click to expand...
Click to collapse
Tried that as well. At end of root it asks to reboot, and then I'm back to having to use NVflash to bring it back up.
jimcpl said:
Hi,
P.S. Question: Are you sure/do you know if you might have one of those few "320" units, the ones with the 1GB RAM instead of the 512MB RAM? I seem to recall that roebeet said that those are partitioned differently, and that the stock NVflash wouldn't work with them, so maybe that might explain why? Just a thought...
Click to expand...
Click to collapse
I just checked the back, model is UPC300-2 2.
I'll keep playing. Someone posted in another thread here that they had the same issue (having to use nvflash to boot) but then posted they fixed it (but without what they did other than using ADB). I've PM'd them to see exactly what they did so I'm hoping they respond.
tcrews said:
Yep, that got me flashed back to a stock image and even to a TnT-lite 1.02 image. Still not able to boot without flashing first.
Tried that as well. At end of root it asks to reboot, and then I'm back to having to use NVflash to bring it back up.
I just checked the back, model is UPC300-2 2.
I'll keep playing. Someone posted in another thread here that they had the same issue (having to use nvflash to boot) but then posted they fixed it (but without what they did other than using ADB). I've PM'd them to see exactly what they did so I'm hoping they respond.
Click to expand...
Click to collapse
Sorry to hear all that ... Can you post back as you progress, as it might be helpful to others here. Also, have you tried the IRC channel, to see if there's anyone there that might be able to help?
Jim
Dude, TNT Lite does not have a recovery partition in it. That's why it's not "sticking". You need to update with something with the recovery partition in it. None of the custom roms flash the recovery partition. You need to use one of the stock roms direct from viewsonic or nvflash from the link I posted. Trust me. It will work.
rayden25 said:
Dude, TNT Lite does not have a recovery partition in it. That's why it's not "sticking". You need to update with something with the recovery partition in it. None of the custom roms flash the recovery partition. You need to use one of the stock roms direct from viewsonic or nvflash from the link I posted. Trust me. It will work.
Click to expand...
Click to collapse
I've done all that...I thought I had mentioned it in the first post...
Basically I can NVFlash anything, but power off or attempt a reboot and nothing...until I nvflash again.
I started with the stock images...then NVFlash of TnT-lite 1.02 (which includes Clockworkmod), then threw in the system.img from the latest TnT.....nothing "sticks".
I'll flash the stock TnT and get an update notification that 1.1-3389 is available....download that....and when it reboots to install.....nothing. Have to flash again something to get it to boot. Also if I don't download the update and just power off or install something that forces a reboot....nothing.
It's very close to being used for target practice now....
(it's downloading 1.1-3389 again since I just did another nvflash
(below is what I get every time I nvflash)
[email protected]:~/NVFlash/tegra_froyo_20101105$ ./nvflash_gtablet.sh
Flashing G Tablet with base images...
[sudo] password for snkbitten:
Nvflash started
rcm version 0X20001
System Information:
chip name: t20
chip id: 0x20 major: 1 minor: 3
chip sku: 0x8
chip uid: 0x17144042441fe1d7
macrovision: disabled
hdcp: enabled
sbk burned: false
dk burned: false
boot device: nand
operating mode: 3
device config strap: 0
device config fuse: 0
sdram config strap: 0
sending file: gtablet.bct
- 4080/4080 bytes sent
gtablet.bct sent successfully
downloading bootloader -- load address: 0x108000 entry point: 0x108000
sending file: bootloader.bin
| 928945/928945 bytes sent
bootloader.bin sent successfully
waiting for bootloader to initialize
bootloader downloaded successfully
setting device: 1 0
creating partition: BCT
creating partition: PT
creating partition: EBT
creating partition: MBT
creating partition: BLO
creating partition: MSC
creating partition: OGO
creating partition: SOS
creating partition: LNX
creating partition: APP
creating partition: CAC
Formatting partition 2 BCT please wait.. done!
Formatting partition 3 PT please wait.. done!
Formatting partition 4 EBT please wait.. done!
Formatting partition 5 MBT please wait.. done!
Formatting partition 6 BLO please wait.. done!
Formatting partition 7 MSC please wait.. done!
Formatting partition 8 OGO please wait.. done!
Formatting partition 9 SOS please wait.. done!
Formatting partition 10 LNX please wait.. done!
Formatting partition 11 APP please wait.. done!
Formatting partition 12 CAC please wait.. done!
done!
sending file: part4.img
/ 2097152/2097152 bytes sent
part4.img sent successfully
sending file: part5.img
\ 131072/131072 bytes sent
part5.img sent successfully
sending file: part6.img
/ 4194304/4194304 bytes sent
part6.img sent successfully
sending file: part7.img
/ 16777216/16777216 bytes sent
part7.img sent successfully
sending file: part8.img
/ 33554432/33554432 bytes sent
part8.img sent successfully
sending file: part9.img
/ 16777216/16777216 bytes sent
part9.img sent successfully
sending file: part10.img
/ 16777216/16777216 bytes sent
part10.img sent successfully
sending file: system.img
\ 117292032/117292032 bytes sent
system.img sent successfully
Done!
Click to expand...
Click to collapse
and as an "just now" update...accepting the install of 1.1-3389 shuts down and leaves it down and unable to boot until I nvflash.
I just noticed above (and while doing it a few times just now) it formats 2 and 3 but doesn't send the images...it starts with sending file: part4.img
Anyone know what partitions BCT and PT are?
the gtablet.cfg file has them with part2.img and part3.img which are in the same folder with the other images..
[partition]
name=BCT
id=2
type=boot_config_table
allocation_policy=sequential
filesystem_type=basic
size=3145728
file_system_attribute=0
partition_attribute=0
allocation_attribute=8
percent_reserved=0
filename=part2.img
[partition]
name=PT
id=3
type=partition_table
allocation_policy=sequential
filesystem_type=basic
size=131072
file_system_attribute=0
partition_attribute=0
allocation_attribute=8
percent_reserved=0
filename=part3.img
tcrews said:
I just noticed above (and while doing it a few times just now) it formats 2 and 3 but doesn't send the images...it starts with sending file: part4.img
Anyone know what partitions BCT and PT are?
the gtablet.cfg file has them with part2.img and part3.img which are in the same folder with the other images..
[partition]
name=BCT
id=2
type=boot_config_table
allocation_policy=sequential
filesystem_type=basic
size=3145728
file_system_attribute=0
partition_attribute=0
allocation_attribute=8
percent_reserved=0
filename=part2.img
[partition]
name=PT
id=3
type=partition_table
allocation_policy=sequential
filesystem_type=basic
size=131072
file_system_attribute=0
partition_attribute=0
allocation_attribute=8
percent_reserved=0
filename=part3.img
Click to expand...
Click to collapse
I think that this has a partition layout info:
http://tosh-ac100.wetpaint.com/page/Partition+Layout
BCT = boot configuratin table
PT = partition table
Jim
I'm sorry, I didn't understand that you did a full NVFLASH restore, but something obviously still isn't right. I am 100% confident the device is not bricked. It just needs to have a full restore and it should be good.
Where did you get the recovery files from? How are you running them? Windows or
Linux?
I am commited to getting this thing to work again. It's a challenge that has me thinking like crazy!
rayden25 said:
I'm sorry, I didn't understand that you did a full NVFLASH restore, but something obviously still isn't right. I am 100% confident the device is not bricked. It just needs to have a full restore and it should be good.
Where did you get the recovery files from? How are you running them? Windows or
Linux?
I am commited to getting this thing to work again. It's a challenge that has me thinking like crazy!
Click to expand...
Click to collapse
Oh...it's already drove me crazy!
I got them from the same thread you had linked.
I've done it on both Windows 7 (64 bit and 32bit) and Ubuntu 64bit 10.04.
It's frustrating in that it boots after the flash, everything works but I can't power it off or reboot it.
Once it shuts down....it's down. Screen doesn't flash from pressing power....no recovery to boot in to (stock or otherwise)....just plug it in and either nothing (then press volume - and power and watch for USB activity as the screen doesn't flash or anything) and then I can nvflash to it.
Once I nvflash and boot...I can adb access it, use wifi, etc....but that's it.
As I have followed some instructions to run fastboot command in my pc , however my pc showed " CANNOT RECOGNISED IT IS EXTERNAL OR INTERNAL COMMAND " What's wrong ?
Pls. help me !
nicolas russell said:
As I have followed some instructions to run fastboot command in my pc , however my pc showed " CANNOT RECOGNISED IT IS EXTERNAL OR INTERNAL COMMAND " What's wrong ?
Pls. help me !
Click to expand...
Click to collapse
1) you need to read some more
2) you probably open the command prompt from the wrong folder
3) you haven't set your environment paths
If you don't know what 2 and 3 mean then that proves you haven't done enough of number 1
Thank you !
Dear cdzo72
Thanks for your advices that I can flash any custom recovery to my Dell Streak 5 , but new question come : Whethet not all recoveries applicable to Dell Streak 5 or some technical problems which I cannot still tackle ?
nicolas russell said:
Dear cdzo72
Thanks for your advices that I can flash any custom recovery to my Dell Streak 5 , but new question come : Whethet not all recoveries applicable to Dell Streak 5 or some technical problems which I cannot still tackle ?
Click to expand...
Click to collapse
First of all what are you trying to get accomplish?
By flashing StreakMod you are then able to flash zip files (custom ROM's, themes, etc...)
Stock recoveries are for flashing stock ROM update packages. The recovery has to match the ROM or at least the region.
Now let me say this again as politely as possible.... The fact that you asked what you did proves 1 of two things.... You haven't read OR you don't understand what you're reading. In either case I strongly suggest you get a grasp of what you are doing BEFORE you end up with a device you can't repair
Sent from my cm_tenderloin using Tapatalk 2
Please use the Q&A Forum for questions &
Read the Forum Rules Ref Posting
Moving to Q&A
Hey.
Since i installed Cyanogen mod 7, I've been in big problems.
So I tried to NVFlash (forum.xda-developers.c o m/showthread.php?t=1044326&page=1) NOTE! Remove spaces between com
But after having entered the command into command prompt, it gives me this error:
downloading bootloader -- load address: 0x108000 entry point: 0x108000
sending file: fastboot.bin
/ 1024992/1024992 bytes sent
fastboot.bin sent successfully
waiting for bootloader to initialize
bootloader downloaded successfully
failed executing command 14 NvError 0x120000
command failure: partition download failed
What do i do? Other people have the same problem. See page 28 int he thread (Link above)
I couldn't post in the thread itself, as i am a new user.
Thanks for all help!
search at the forum
budak_getah said:
search at the forum
Click to expand...
Click to collapse
Tried that, didn't help too much.
Com on guys! (And girls) Urgent! need help here! :/
Please use the Q&A Forum for questions &
Read the Forum Rules Ref Posting
Thanks ✟
Moving to Q&A
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.
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.