Related
[GUIDE-IMPORTANT!] "rescue-backdoor" - regarding bootloop, do it before change in sys
UPDATE: THIS IS OBSOLETE.
USE S.onyTablet.S [ALLinONE] tool
Below guide/tool use as 'description'
-------------------------------------------------------------------------
Hi guys,
We've got now ROOT. We can do a lot of things, which we couldn't do before.
But before you begin to make changes in system files, first you need to know few things.
Few users experienced "bootloop". Its brick state. There is no access to shell, no adb.
Damaged device.
How to avoid that?
Yes, there is a solution. We need to get proper update zip for our device.
We also need to fool device, that it is a newer file, than the firmware in device.
How to, step by step:
Of course, ROOT is required.
To get proper ota-update-zip for your device you have to edit /build.prop:
- easiest way is via "Root Explorer", or directly via "build.prop Editor" (in market, free),
- do not use "File Manager HD" or other filemanager, which doesn't support root operations (thx kryddan),
- always make backup of files, which you are modifying,
- change value of "ro.sony.build.incremental" to lower one to fake firmware version,
- for example on my device newest firmware has: "ro.sony.build.incremental=111201022" - decrease that value,
in my case to 111201021.
Reboot device.
OTA update notification will appear - click on "Download" button.
Wait until download finishes, but don't click "Update"!!!
I repeat - DON'T CLICK UPDATE! It will reflash firmware,
and you will have to make everything from the beginning (inc. root).
Update zip is located in /cache/ota/signed-nbx03_.......zip - make a copy to safe place - external sd and/or in pc.
Leave build.prop modified. IMPORTANT. Don't revert back changes.
To enter RECOVERY-MODE - power off device,
hold vol-down + power button.
When you want to flash your device, Sony Tablet is checking few things:
is update zip proper one - signed one,
is the update zip - for your region - SKU value,
is the update zip is newer one than firmware in device - equal and higher will not update,
only lower - thats what we're faking.
If you will revert back build.prop = update will fail,
if you will try to update with other region update zip = update fail.
So if we stay with modified build.prop = we can just enter recovery,
and update from external sd card, to our downloaded update zip
Remember, that after reflash in recovery, your build.prop will be updated back
to higher value, then to be safe you need to reapply modification!
I have tested that "rescue-backdoor" on my own device,
deleted some system framework file - of course bootloop, without adb access.
Flashed through recovery - voila, device fixed
Of course, everything what you do with your device, you are doing at your own
risk. I'm sure that in 99% cases with "rescue-backdoor" you will fix your device,
always could be that other 0,01% case.
One condition for sure = build.prop file has to be correct.
[OPTIONAL]
You can disable ota update notification - which appears on every reboot.
To do this use "Titanium Backup" app, look for "System Update" app on list,
and use "Freeze" option
Any questions, suggestions - just ask
PS. I'm thining about writing auto-script for that...
br
condi
great guide, thank you
I think an automated-script would be much appreciated
condi said:
Hi guys,
We've got now ROOT. We can do a lot of things, which we couldn't do before.
But before you begin to make changes in system files, first you need to know few things.
Few users experienced "bootloop". Its brick state. There is no access to shell, no adb.
Damaged device.
How to avoid that?
Yes, there is a solution. We need to get proper update zip for our device.
We also need to fool device, that it is a newer file, than the firmware in device.
How to, step by step:
Of course, ROOT is required.
To get proper ota-update-zip for your device you have to edit /build.prop:
- easiest way is via "Root Explorer", or directly via "build.prop Editor" (in market, free),
- always make backup of files, which you are modifying,
- change value of "ro.sony.build.incremental" to lower one to fake firmware version,
- for example on my device newest firmware has: "ro.sony.build.incremental=111201022" - decrease that value,
in my case to 111201021.
Reboot device.
OTA update notification will appear - click on "Download" button.
Wait until download finishes, but don't click "Update"!!!
I repeat - DON'T CLICK UPDATE! It will reflash firmware,
and you will have to make everything from the beginning (inc. root).
Update zip is located in /cache/ota/signed-nbx03_.......zip - make a copy to safe place - external sd and/or in pc.
Leave build.prop modified. IMPORTANT. Don't revert back changes.
When you want to flash your device, Sony Tablet is checking few things:
is update zip proper one - signed one,
is the update zip - for your region - SKU value,
is the update zip is newer one than firmware in device - equal and higher will not update,
only lower - thats what we're faking.
If you will revert back build.prop = update will fail,
if you will try to update with other region update zip = update fail.
So if we stay with modified build.prop = we can just enter recovery,
and update from external sd card, to our downloaded update zip
I have tested that "rescue-backdoor" on my own device,
deleted some system framework file - of course bootloop, without adb access.
Flashed through recovery - voila, device fixed
Of course, everything what you do with your device, you are doing at your own
risk. I'm sure that in 99% cases with "rescue-backdoor" you will fix your device,
always could be that other 0,01% case.
One condition for sure = build.prop file has to be correct.
[OPTIONAL]
You can disable ota update notification - which appears on every reboot.
To do this use "Titanium Backup" app, look for "System Update" app on list,
and use "Freeze" option
Any questions, suggestions - just ask
PS. I'm thining about writing auto-script for that...
br
condi
Click to expand...
Click to collapse
Thanks Condi! Download worked great but under my cache there is nothing. Could the file be located elsewhere?
It should be under '/cache/ota' ... nowhere else ..
Judah001 said:
Thanks Condi! Download worked great but under my cache there is nothing. Could the file be located elsewhere?
Click to expand...
Click to collapse
Be sure that ota has been download, check again /cache/ota.
If still no zip, then run 'adb shell' then:
Code:
su
find -name *signed*
or
Code:
find -name *.zip
If your ota update will be in different location, then please post it.
br
condi
condi said:
Be sure that ota has been download, check again /cache/ota.
If still no zip, then run 'adb shell' then:
Code:
su
find -name *signed*
or
Code:
find -name *.zip
If your ota update will be in different location, then please post it.
br
condi
Click to expand...
Click to collapse
ok I will try once I am home through adb. So far there is nothing under my cache folder. I am using file manager HD but it should pick up a zip file.
Thank you condi... The instructions worked perfectly!!
Judah001 said:
ok I will try once I am home through adb. So far there is nothing under my cache folder. I am using file manager HD but it should pick up a zip file.
Click to expand...
Click to collapse
Just a little tip. I'd suggest you use Root Explorer instead of File Manager HD.
You see, File Manager HD does not show the files in /cache. (mine didn't)
I tried File Manager HD on my tablet and found nothing inside /cache
But with Root Explorer I found three different directories. There among OTA.
kryddan said:
Just a little tip. I'd suggest you use Root Explorer instead of File Manager HD.
You see, File Manager HD does not show the files in /cache. (mine didn't)
I tried File Manager HD on my tablet and found nothing inside /cache
But with Root Explorer I found three different directories. There among OTA.
Click to expand...
Click to collapse
That did the trick. I used the root browser in rom tool box and copied the zip to my sd card. Thank you for the help guys.
Good advice kyddan ... same on my tab with file manager HD.
I work normally with Root Explorer or File Expert.
Both show the folders and files in /cache .. File Manager HD do not.
my ro.sony.build.incremental is 111201038
Do I have to decrease it by 1 to 111201037 ?
EDIT: nevermind. I did so. Worked.
sebarkh said:
my ro.sony.build.incremental is 111201038
Do I have to decrease it by 1 to 111201037 ?
Click to expand...
Click to collapse
Yep, exacty. And then you will get newest ota zip of 111201038 pozdro
hahahahah I just had brick... I'm working on auto-install script for "rescue-backdoor", and accidentally I've pushed empty 0bytes build.prop - after reboot - sony logo, then black screen.... and guess what...
recovery reads incremental value (which doesnt exists..) as "0" zero
so i've got lower value, and reflash done.
after reboot my tab started correctly, but.. after reboot again brick - black screen.
fortunatelly - after few min with black screen i've got adb access.
but for first - i can't get root access.. 'su' not works.
but... '/system/xbin/su' works root lets check - build.prop still empty,
remounted system as rw, pushed correct build.prop - ahhh again working !!
that was good experience hahah.
-------------edit:
i've got auto-install tool ready... need to make one more full test with my device and will publish it.
full automatic !!!!!
This is driving me crazy. why everyone is getting update message when changing the incremental value while my dumass tablet keeps saying that my system is up to date
ase3000 said:
This is driving me crazy. why everyone is getting update message when changing the incremental value while my dumass tablet keeps saying that my system is up to date
Click to expand...
Click to collapse
Just wait for automatic-tool. Its ready, but need to make final tests.
condi said:
So if we stay with modified build.prop = we can just enter recovery,
and update from external sd card, to our downloaded update zip
Click to expand...
Click to collapse
In which way we can enter to recovery??
riccardo91 said:
In which way we can enter to recovery??
Click to expand...
Click to collapse
power off, hold vol-down + power.
All done! It works well! Thanks! Avoiding bootloop it's even a good thing!
riccardo91 said:
All done! It works well! Thanks! Avoiding bootloop it's even a good thing!
Click to expand...
Click to collapse
Great Just remember one thing - after reflash in recovery, your build.prop will be updated to higher value - then to be safe you need to reapply modification!
--- my 100th post !
condi said:
Great Just remember one thing - after reflash in recovery, your build.prop will be updated to higher value - then to be safe you need to reapply modification!
--- my 100th post !
Click to expand...
Click to collapse
I bricked my XTS playuing with build.prop. Shame I didn't see this post before. For future - how can I edit build.prop in a safe way? I changed file permission then I forgot to restore default. After restart brick. Do I need to change permission to edit build.prop then do i NEED to restore proper permission back? I'm still confused with it
For all you Shotputterz heres the factory image we've been waiting for
assuming you have debug mode enabled, ADB and fastboot working properly
EDIT 1: REUP'D CWM mod
EDIT 2: reordered process to make more sense
Method:
1. Download the Beta CWM mod from rootzwikis credit to birdman EDIT:REUP'ED http://d-h.st/Fdp
2. Using fastboot, DO NOT FLASH Clockwork mod just use the syntax
"fastboot boot 'File path of clockwork mod image'
Note* this will boot directly into the recovery without permanently writing to the recovery and boot partition on the eMMC on the Nexus Qs board
3. Download the posted CWM factory backup posted
4. make the directory on the device and adb push the backup folder (unzipped) to /sdcard/clockworkmod/backup while in CWM recovery
*The device should show up in "adb devices" while in the CWM recovery*
5. *TEXT WILL BE REALLY SMALL! Now navigate with the Scroll wheel to backups and restore and tap the mute button to select.
*IF SOMETHING IS SELECTED IN ERROR THERE IS NO BACK BUTTON JUST REBOOT AND REDO FASTBOOT BOOT*
6. Now select restore and select the image folder
7.blah blah CWM Freaking MAGIC
8. Your Q is back to factory state
If someone wants to PM me or show me how to package this in a nicer CWM zip to install with a script let me know
http://d-h.st/yeo
*Note* I am NOT responsible if you brick your already bricked Nexus Q*
You sir get a beer, since my 2nd (dev) Q won't arrive until later this week, and mine was a shot put until this post.
If you happen to be in NYC before I move to SF, you get three beers.
Hoppy ones.
I am moving to SF
Did the reflash go smoothly?
fiveipads said:
I am moving to SF
Did the reflash go smoothly?
Click to expand...
Click to collapse
No unfortunately it didn't--I blew away all partitions other than bootloader so I can't, to my knowledge at least, push the zip since I can't adb.
I've got factory recovery, boot, system imgs but the system img won't push out because of fastboot's apparent inability to handle files that large (1GB exactly I believe).
...I guess I have to patiently await my second Q but the point of having two was to *use* one and have one for dev... rather than have one as a heavy reminder of my overzealous endeavors...
Hopefully I can give it more time while on this SF trip...
Boot into the cwm bootloader with fastboot without flashing. Adb will be enabled and you can push files the files while your in adb recovery. Try that and flash it.
Sent from my SPH-D710 using xda app-developers app
Does our Q's have internal memory.. if not wouldn't it be possible to run back up of off otg memory stick if recovery would support it
Sent from my Galaxy Nexus using xda premium
fiveipads said:
Boot into the cwm bootloader with fastboot without flashing. Adb will be enabled and you can push files the files while your in adb recovery. Try that and flash it.
Sent from my SPH-D710 using xda app-developers app
Click to expand...
Click to collapse
The problem I'm having is that ADB is not responding from CWM... at least not on a Windows machine. The drivers are fine as ADB was working in normal mode before my issue sprung up.
EDIT: As suspected Virtual Ubuntu on a Win host didn't see the device, Physical Ubuntu had no issue. NQ reloaded.
fiveipads said:
Boot into the cwm bootloader with fastboot without flashing. Adb will be enabled and you can push files the files while your in adb recovery. Try that and flash it.
Sent from my SPH-D710 using xda app-developers app
Click to expand...
Click to collapse
Can we do this by say pushing the file to the download folder and then installing from zip?
And i know slightly off topic but once we've installed some apks for example, what's currently the best interface to use to navigate through the apps and use them?
How do I make a directory on Nexus Q
fiveipads said:
For all you Shotputterz heres the factory image we've been waiting for
assuming you have debug mode enabled, ADB and fastboot working properly
Method:
1. Download the posted CWM factory backup posted
2. make the directory on the device and adb push the backup folder (unzipped) to /sdcard/clockworkmod/backup
http://d-h.st/yeo
Click to expand...
Click to collapse
In step 2 you say make a directory for the file that is posted below. How do I create a directory on the Nexus Q? Currently my Q is stuck in a bootloop after trying to launch CWM from a Galaxy Nexus. If you could post command codes that would be awesome!
I figured it out. You can just follow step #4 and in CWM you can push the CWM Factory img to the /sdcard/Download/ folder and use CWM to unzip and launch.
Could someone please provide me the beta cwm image for Nexus Q? The links are all circular and point to
http://goo.im/devs/birdman/CWM-steelhead-beta.img
Which is dead...
discoltk said:
Could someone please provide me the beta cwm image for Nexus Q? The links are all circular and point to
http://goo.im/devs/birdman/CWM-steelhead-beta.img
Which is dead...
Click to expand...
Click to collapse
I've been trying to get ahold of this image too! Anyone?? anyone?? Bueller???
WildSatchmo said:
I've been trying to get ahold of this image too! Anyone?? anyone?? Bueller???
Click to expand...
Click to collapse
Me as well...not sure why I got this damn thing...lol
The edit didn't prompt an email to me even though I'm following the thread, so those of you looking for the clockworkmod beta image please take note that OP was kind enough to provide a working link to the image.
Thanks fiveipads!
Can someone post full backup please?
caioketo said:
Can someone post full backup please?
Click to expand...
Click to collapse
The link at the bottom still works for me...
http://d-h.st/yeo
..
ok this is really bothering me, i've restored with this factory image several times, and I have to do it again right now and I cannot seem to push this file folder to /sdcard/clockworkmod/backup
what am i doing wrong..
it should be:
adb push NexusQFactoryImage /sdcard/clockworkmod/backup/ (assuming the file is in same folder as adb which it is)
that's it right.... the extracted folder contents in a folder.. not the zip.. so i dont understand why this is not working. Everytime I go to CWM and try to restore it tells me nothing to restore...
what really bothers me is that i've done this a hundred times, and never had this problem..
UKROB86 said:
ok this is really bothering me, i've restored with this factory image several times, and I have to do it again right now and I cannot seem to push this file folder to /sdcard/clockworkmod/backup
what am i doing wrong..
it should be:
adb push NexusQFactoryImage /sdcard/clockworkmod/backup/ (assuming the file is in same folder as adb which it is)
that's it right.... the extracted folder contents in a folder.. not the zip.. so i dont understand why this is not working. Everytime I go to CWM and try to restore it tells me nothing to restore...
what really bothers me is that i've done this a hundred times, and never had this problem..
Click to expand...
Click to collapse
BUMP.. stuck in CWM unable to get a restorable file.. no idea why...
Download OneClickRestore (it's the factory image straight from Google with the needed fastboot files included)
Extract zip to OneClickRestore
Unplug Nexus Q
Plug in Nexus Q and place hand on it til the leds turn red then remove hand
Launch "flash-all.bat" from the OneClickRestore folder
You may need to do a full reset, it's hit or miss
Another option is push & flash (Nexus Q)uantum Singularity Project RTS ROM from CWM and again may need to hard reset.
RTS is
Based on stock 4.0.4 build IAN67K
Deodexed
Zip aligned
init.d Support
bash support
Busybox updated
Prerooted
Superuser
Updated Keymap (Home=Home, End=Back, Delete=Menu, Insert=Visualizer)
Lokifish Marz said:
Download OneClickRestore (it's the factory image straight from Google with the needed fastboot files included)
Extract zip to OneClickRestore
Unplug Nexus Q
Plug in Nexus Q and place hand on it til the leds turn red then remove hand
Launch "flash-all.bat" from the OneClickRestore folder
You may need to do a full reset, it's hit or miss
Another option is push & flash (Nexus Q)uantum Singularity Project RTS ROM from CWM and again may need to hard reset.
RTS is
Based on stock 4.0.4 build IAN67K
Deodexed
Zip aligned
init.d Support
bash support
Busybox updated
Prerooted
Superuser
Updated Keymap (Home=Home, End=Back, Delete=Menu, Insert=Visualizer)
Click to expand...
Click to collapse
The problem with putting Quantum singularity project on is that I can't turn on ADB debug, because i use a bluetooth mouse and keyboard, don't have an OTG mouse/keyboard, so somehow I need to be able to connect with adb to setup a bluetooth connected mouse/keyboard
I was thinking to install stock image, and then without wiping install Quantum SIngularity Project over top to preserve the settings for usb debug, on.
what's confusing to me is that i've restored the stock image many times before, and never had a problem.. that's why im wondering what the problem is.. if im typing something wrong.
I used the OneClickRestore as you said, and im just booting it up now
EDIT: didn't get past boot logo, i'll try again
So just to confirm this OneClickRestore is loading the stock nexus Q img right? I've never used it before I usually manually do it
EDIT: still stuck at the nexus q logo before home screen
do you see any error in my commands of trying to push the stock img folder (original post) to "/sdcard/clockworkmod/backup" ? I've done it many times before never had a problem
Hello,
I installed last week this version of android on my G9, all was fine until today when my tablet ran out of battery, I plugged it and start it again as I always do in that case. Except that today android didn't start and I got the multiboot screen which you can see in attached files. I tried both options but my tablet always restart on that screen.
When my tablet is plugged into my computer it is not recognized so I can't put a new ROM of android and make a new installation, I tried to use ADB to debug it but there are no device detected ...
Does someone have a solution to my problem ?
Thanks in advance for your answers.
Olorin59.
PS: sorry if there are language mistakes in what I wrote but i'm French so English is not my birth language.
You have 2 options right now. You can either just install stock ROM, or if you have Linux in you computer you can use sde to mount data partition to your PC and moving the ROM again in there.
Installing stock ROM is easier and faster, so I recommend doing that. You remember how it goes? Download latest firmware from achos' site an use firmware update option located in sde.
Sent from my GT-I9100 using xda app-developers app
I think I already tried that : download the aos file from the official site of archos, go in recovery mode, chose upgrade firmware and copy the aos file to the drive which appears on my computer then chose ok ???
If it is that I tried and I got an error message "update failled : 221".
So if it is that could you explain me more how to do it with linux, i'm not sure I understood everything.
olorin59 said:
I think I already tried that : download the aos file from the official site of archos, go in recovery mode, chose upgrade firmware and copy the aos file to the drive which appears on my computer then chose ok ???
If it is that I tried and I got an error message "update failled : 221".
So if it is that could you explain me more how to do it with linux, i'm not sure I understood everything.
Click to expand...
Click to collapse
Okay.
That 221 sounds weird.
After booting in to Linux (livecd is sufficient, I recommend Ubuntu or variant of it), open the sde in archos and navigate to data mount option. I can't remember what it is called, but should be something like mount data partition. Then plug your tablet to PC running Linux, and the PC should find the tablet.
You should now be able to browse data on /data partition of the tablet, but writing there requires you to use superuser.
Check the path to data partition. If I remember correctly, it will be something like /media/(device name)/ but I'm not sure.
Navigate to archos.etx4.update file and use this command to move it:
sudo mv archos.ext4.update path-to-data/media/archos.ext4
If /media/path-to-data/media won't work, try using /media/path-to-data/local
Sent from my GT-I9100 using xda app-developers app
I don't have mount data partition but I do have "export data partition" and "export hard disk (H models only)" in the developer edition menu, is it what you are talking about ?
olorin59 said:
I don't have mount data partition but I do have "export data partition" and "export hard disk (H models only)" in the developer edition menu, is it what you are talking about ?
Click to expand...
Click to collapse
Yeah, that is the one: export data partition
Sent from my GT-I9100 using xda app-developers app
When I plugged my tablet, ubuntu told that I do not have the authorisation to see the content of the drive ...
Can't I do the same with windows ?
olorin59 said:
When I plugged my tablet, ubuntu told that I do not have the authorisation to see the content of the drive ...
Can't I do the same with windows ?
Click to expand...
Click to collapse
HMM.. That sounds weird, as I do not have that problem. Can you try other Linux? I think backtrack allows you to login as root, so you are able to do anything...
The filesystem of data partition is ext4 I guess... Or ext3. Windows can not read ext filesystem, so you can't use windows.
Sent from my GT-I9100 using xda app-developers app
Ok I'll try an other version of linux, backtrack is downloading as i'm writing this. I'll get back to you soon.
Hi julle131, I'm currently using backtrack which as you told allows me without problems to access the data on the tablet.
I'm a little bit lost about what's next to do.
The tablet appears as a drive called "data" in which there a is folder called media as you said, inside it there are a lot of folders for various apps I had installed. If I understood correctly the goal is to find the archos.ext4 file but I can't find it ...
Can I download the archos.ext4 file and put it again on the memory of my tablet to re-install it ?
olorin59 said:
Can I download the archos.ext4 file and put it again on the memory of my tablet to re-install it ?
Click to expand...
Click to collapse
Yes you can.
Hopefylly after downloading archos.ext4, your tablet will hopefully work normally again :thumbup:
Sent from my GT-I9100 using xda app-developers app
So, I copied archos.ext4 to in the media folder of the tablet then in recovery mode, I flashed kernel and initramfs but after that my tablet don't reboot, it don't have the multi boot menu or anything and when I press the start button nothing happens I can only access the recovery menu. Do you have any idea ?
olorin59 said:
So, I copied archos.ext4 to in the media folder of the tablet then in recovery mode, I flashed kernel and initramfs but after that my tablet don't reboot, it don't have the multi boot menu or anything and when I press the start button nothing happens I can only access the recovery menu. Do you have any idea ?
Click to expand...
Click to collapse
The initramfs you flashed probably does not have multiboot menu. Keep the zImage from the rom you downloaded and get initramfs from this link:
http://forum.xda-developers.com/showthread.php?t=1578438
when you download the zip, only extract the initramfs.
Then install zImage from the original rom and initramfs from the multiboot menu thread. That should bring the multiboot menu back, and hopefully you can see the new archos.ext4 in there.
I just tried : Kernel (zImage) not found !
olorin59 said:
I just tried : Kernel (zImage) not found !
Click to expand...
Click to collapse
What i meant was to take the zImage from the rom you downloaded and initramfs from my link, and install them both.
Make a new folder to the desktop, and extract initramfs from the link i gave you in earlier post.
Now you have a new folder with initramfs inside it. Then put the zImage from the rom you downloaded to the folder.
Now you should have a folder which has initramfs AND zImage, right? Then just install them to the tablet. This way you get the multiboot and the new kernel.
It's what I did.
I chose flash kernel and Initramfs in the recovery menu and I paste inside the ramdisk the initramfs from your link and the zImage from my ROM.
I tried both version of the initramfs from the link you gave me.
Any idea, please ?
I'm still stuck on the multi boot menu ...
Can someone help me please ?
After 3 days tried to find out how to recovered or fix bootloop/brick ME170C, here is the way which was succeed for me.
1. Download latest firmware from ASUS website
the best way using complete firmware (containing stock rom) like this version UL-K017-WW-11.2.3.18.2-user, if succeed then later on you can continue with OTA system update
2. Rename the firmware file to K017_sdupdate.zip and put on SD card then Insert the SD card into a tablet. (Use good one SD card, Sandisk perfect I don't know others)
3. Download flashtools and USB driver at the bottom of this thread
4. Enter the DROIDBOOT, for this purpose on the tablet off push and hold button volume + and power then connect USB cable to tablet and PC.
5. Open your firmware archive and copy or drag & drop the boot.img, fastboot.img, splashscreen.img into Flashtools folder ( in computer )
6. go to flashtools folder and then push button shift and right click together and choose “Open command windows here”, to start open CMD on the right folder (in computer)
7. Test your device by typing fastboot devices on that cmd (in computer)
8. Enter the queue codes on CMD; (in computer)
fastboot erase cache
fastboot erase userdata
fastboot erase system
fastboot flash boot boot.img
fastboot flash fastboot fastboot.img
fastboot flash splashscreen splashscreen.img
fastboot reboot-bootloader
8. Disconnect the USB cable and select the SD update or Recovery.
9. Take your coffee and sit, walaaaaaaa I see you are smiling
I am curious , is it work for others ASUS tablet? do with your own risk, but btw with this step I did wake up a hard brick devices.
Tag [ Asus memopad fonepad zenfone ME170 brick, bootloop, stuck on asus logo, boot problem, solved brick, guide how to]
So awesome you figured this out! Glad it worked out for you and I'll be saving this in case I find myself in the same boat. Thank you for this!!
Sent from my Nexus 6
K01A, aka ASUS MeMO Pad ME170CX
Prod date 2014-10 IIRC.
I appreciate you taking time to create this thread, have been unable to flash stock firmware to the ME170CX using just the ME170CX itself. ASUS website just mentions a SOP method and when I insert SD that has had the firmware files which have been extracted (1) time to the SD card, the prompt that is supposed to "pop-up" on the taskbar as mentioned in the PDF's I found online about the SOP method does NOT occur.
(I have 2 ME170CX's about 30-days old running 4.4.2, firmware Version WW_V11.2.3.27 in which one of them all the sudden the camera app crashes 100% of the time, then gives a "No camera is found" error message.
Beyond a hardware issue no-one knows what causes this beyond (1) poster that mentioned he thought problem first occurred after hitting the "Home" button right after hitting the cam icon and the thought is the app gets confused by this and the app/firmware for the camera gets corrupted.
Reset via OS itself. Wiping data and choosing "Recovery" in DROIDBOOT with "FASTBOOT" text at bottom of screen didn't make any difference. Camera is dead, dead, dead.
Figured I'd re-flash with same Version WW_V11.2.3.27, if that doesn't work try Version WW_V11.2.3.28 before RMA'ing it back to ASUS so I appreciate you listing the steps, and also attaching the needed files.)
***************
Question about Step 2, Please clarify:
2. Extract (archive in archive) and throws to the SD card. Rename the file to K017_sdupdate.zip and Insert the flash drive into a tablet. (Use good one SD card)
Click to expand...
Click to collapse
To clarify you are saying to extract the firmware from the "zip" package of zip that matches the firmware specific to the device from ASUS, which itself contains a zip file named IFWI.ZIP (1 ), one time, then rename the file named IFWI.ZIP (which contains 4 Bin files) to K017_sdupdate.zip.
Upon extraction process completing and renaming the zip you then copy the contents over to a known good MiroSD of at least 2GB which is formatted FAT32 to the ROOT of the drive.
IE: You do not extract the zip within the archive, you're just renaming IFWI.ZIP to K017_sdupdate.zip?
OR are you saying to extract the BINS also?
If so do these go in the ROOT of the SD card?
Another question, is there a reason for renaming IFWI.zip to K017_sdupdate.zip?
.
WeAreNotAlone said:
K01A, aka ASUS MeMO Pad ME170CX
Prod date 2014-10 IIRC.
I appreciate you taking time to create this thread, have been unable to flash stock firmware to the ME170CX using just the ME170CX itself. ASUS website just mentions a SOP method and when I insert SD that has had the firmware files which have been extracted (1) time to the SD card, the prompt that is supposed to "pop-up" on the taskbar as mentioned in the PDF's I found online about the SOP method does NOT occur.
(I have 2 ME170CX's about 30-days old running 4.4.2, firmware Version WW_V11.2.3.27 in which one of them all the sudden the camera app crashes 100% of the time, then gives a "No camera is found" error message.
Beyond a hardware issue no-one knows what causes this beyond (1) poster that mentioned he thought problem first occurred after hitting the "Home" button right after hitting the cam icon and the thought is the app gets confused by this and the app/firmware for the camera gets corrupted.
Reset via OS itself. Wiping data and choosing "Recovery" in DROIDBOOT with "FASTBOOT" text at bottom of screen didn't make any difference. Camera is dead, dead, dead.
Figured I'd re-flash with same Version WW_V11.2.3.27, if that doesn't work try Version WW_V11.2.3.28 before RMA'ing it back to ASUS so I appreciate you listing the steps, and also attaching the needed files.)
***************
Question about Step 2, Please clarify:
To clarify you are saying to extract the firmware from the "zip" package of zip that matches the firmware specific to the device from ASUS, which itself contains a zip file named IFWI.ZIP (1 ), one time, then rename the file named IFWI.ZIP (which contains 4 Bin files) to K017_sdupdate.zip.
Upon extraction process completing and renaming the zip you then copy the contents over to a known good MiroSD of at least 2GB which is formatted FAT32 to the ROOT of the drive.
IE: You do not extract the zip within the archive, you're just renaming IFWI.ZIP to K017_sdupdate.zip?
OR are you saying to extract the BINS also?
If so do these go in the ROOT of the SD card?
Another question, is there a reason for renaming IFWI.zip to K017_sdupdate.zip?
.
Click to expand...
Click to collapse
some firmware when you download it from asus site ZIP compresed twice, you can rename it directly from WW_V11.2.3.28.zip to K017_sdupdate.zip, if your device is K01A try to renaming firmware to K01A_sdupdate.zip and then put in SD card (do not created any folder in SD card ). the key to success is the SD card compatibility with ASUS DROIDBOOT, I was using Sandisk SD card. I did format fat32 the SD card and insert in another android devices first and then put the renamed firmware file there.
inside firmware file there is boot.img, fastboot.img and splashscreen.img you need to extract it in flashtool/fasboot folder and then flashing it your tablet. this trick to make firmware recognize correct devices to be update.
try again.
sevensvr said:
some firmware when you download it from asus site ZIP compresed twice, you can rename it directly from WW_V11.2.3.28.zip to K017_sdupdate.zip, if your device is K01A try to renaming firmware to K01A_sdupdate.zip and then put in SD card (do not created any folder in SD card ). the key to success is the SD card compatibility with ASUS DROIDBOOT, I was using Sandisk SD card. I did format fat32 the SD card and insert in another android devices first and then put the renamed firmware file there.
inside firmware file there is boot.img, fastboot.img and splashscreen.img you need to extract it in flashtool/fasboot folder and then flashing it your tablet. this trick to make firmware recognize correct devices to be update.
try again.
Click to expand...
Click to collapse
RE: boot.img, fastboot.img and splashscreen.img you need to extract it in flashtool/fasboot folder ???????
Having some progress, renaming ifwi.zip which contains (4) bin files when Recovery was selected caused the robot with the Updating System Settings to appear, but a couple of seconds later it said ERROR with the robot laying on it's back, then it exits. Device reboots as normal.
To clarify:
WW_V11.2.3.28.zip download from ASUS was extracted with a Windows computer,
WW_V11.2.3.28.zip extracting /creating following folders, files, then the contents were copied to the ROOT of a MicroSD card formated Fat32
1: boot.img, fastboot.img and splashscreen.img (TO ROOT)
2: ifwi.zip to ROOT. (contains (4) bin files, is this supposed to be extracted to I assume folder by same name off root? OR does this ZIP file just get renamed?)
3: System folder
4: Recovery folder
5: META-INF folder
I do not see a flashtool/fasboot folder. (Fastboot, right?)
Q: Is boot.img, fastboot.img and splashscreen.img supposed to be in a folder named "Flashtool" OR are they supposed to be in folder named "Fastboot" with a pathway of Root (Drive) D:/Flashtool/fastboot ?
.
(NOTE ALL OF THIS IS BEING DONE ON THE DEVICE ITSELF, with contents on SD card.)
Still getting the ERROR! message wit the Adroid robot that is laying on his back.
The zip file that extracts from the main zip WW_V11.2.3.28.zip is named:
ifwi.zip...
I have left a copy of it in the ROOT, plus copied it and renamed it to
K01A_sdupdate.zip
K017_sdupdate.zip
LEAVING COPIES OF ALL IN THE ROOT OF THE SDCARD.
Q: If more than (1) zip is present does this confuse fastboot? OR does fastboot automatically look for zip zip which matches model ID of device? (K01A)
I have left copies of boot.img, fastboot.img and splashscreen.img in the ROOT of the drive.
AND
Created: (ROOT) flashtools/fastboot with *img files in it.
Created: (ROOT) fastboot with *img files in it.
Copied the *img files to under "Flashtools" folder in flashtools/fastboot.
Figuring all the bases would be covered. (EG: *img Files in ROOT, files in Flashtools, Flashtools/fastboot, and a folder named fastboot as well.
Q: I've noticed on the SD card files appearing that previously were not there, when the flash aborts is there some kind of file or files you need to delete, or is it ok to leave the newly generated files there?
---------- Post added at 03:43 AM ---------- Previous post was at 03:37 AM ----------
Deleted:
ifwi.zip.
K017_sdupdate.zip
Tried:
K01A_sdupdate.zip
Still getting robot on it's back with ERROR!
who said you need to renaming ifwi.zip, What you need is read all instruction carefully,
do not put more than 1 zip file in SD card only firmware file which is already renamed to K017_sdupdate.zip, and use good brand SD card.
I successfully complete all step after "Installing system update" nothing change again stuck on asus logo.
commando987 said:
I successfully complete all step after "Installing system update" nothing change again stuck on asus logo.
Click to expand...
Click to collapse
when installing update, the robot end with error or not?, the installing bar moved till finish ? the installing process will take 3 to 5 minutes.
if you did all above and still got stuck on asus logo, try to change the firmware with this version UL-K017-WW-11.2.3.18.2-user, if succeed then you can continue with OTA system update
My Asus MemoPad ME170C has risen again!
sevensvr said:
After 3 days tried to find out how to recovered or fix bootloop/brick ME170C, here is the way which was succeed for me.
1. Download latest firmware from ASUS website
2. Rename the firmware file to K017_sdupdate.zip and put on SD card then Insert the SD card into a tablet. (Use good one SD card, Sandisk perfect I don't know others)
3. Download flashtools and USB driver at the bottom of this thread
4. Enter the DROIDBOOT, for this purpose on the tablet off push and hold button volume + and power then connect USB cable to tablet and PC.
5. Open your firmware archive and copy or drag & drop the boot.img, fastboot.img, splashscreen.img into Flashtools folder ( in computer )
6. go to flashtools folder and then push button shift and right click together and choose “Open command windows here”, to start open CMD on the right folder (in computer)
7. Test your device by typing fastboot devices on that cmd (in computer)
8. Enter the queue codes on CMD; (in computer)
fastboot erase cache
fastboot erase userdata
fastboot erase system
fastboot flash boot boot.img
fastboot flash fastboot fastboot.img
fastboot flash splashscreen splashscreen.img
fastboot reboot-bootloader
8. Disconnect the USB cable and select the SD update or Recovery.
9. Take your coffee and sit, walaaaaaaa I see you are smiling
I am curious , is it work for others ASUS tablet? do with your own risk, but btw with this step I did wake up a hard brick devices.
Tag [ Asus memopad fonepad zenfone ME170 brick, bootloop, stuck on asus logo, boot problem, solved brick, guide how to]
Click to expand...
Click to collapse
I bought my memopad 170c just a couple of days ago and because of excitement i flash the wrong firmware and it went dead i tried the recovery method but nothing happens i'm beginning to get nervous as this tablet is a gift for my daughter but thankfully i found this site especially to your instruction did every step with my finger crossed and like what you said sit back and walaaaaa! my tablet err my daughter's tablet has risen again. thank you for sharing your knowledge.
sevensvr said:
when installing update, the robot end with error or not?, the installing bar moved till finish ? the installing process will take 3 to 5 minutes.
if you did all above and still got stuck on asus logo, try to change the firmware with this version UL-K017-WW-11.2.3.18.2-user, if succeed then you can continue with OTA system update
Click to expand...
Click to collapse
Installing bar not complete at the end but not give error and restart. After restart stuck on asus logo. Now i download version UL-K017-WW-11.2.3.18.2 and check it.
mapagmatyag said:
I bought my memopad 170c just a couple of days ago and because of excitement i flash the wrong firmware and it went dead i tried the recovery method but nothing happens i'm beginning to get nervous as this tablet is a gift for my daughter but thankfully i found this site especially to your instruction did every step with my finger crossed and like what you said sit back and walaaaaa! my tablet err my daughter's tablet has risen again. thank you for sharing your knowledge.
Click to expand...
Click to collapse
you welcome friend
commando987 said:
Installing bar not complete at the end but not give error and restart it. After restart stuck on asus logo. Now i download version UL-K017-WW-11.2.3.18.2 and check it.
Click to expand...
Click to collapse
it seems the tablet didn't read your SD card, to assure SD card problem when the robot appear while system update press buttom vol + and - rapidly to show installing status.
if the tablet didn't read ur SD card try to use another SD card
BIG Thanks
I've been stuck with the bricked 2 day old tablet for at least 3 months. Today I did the procedure you described and it worked. I had to install version V11.2.3.18.2 and then, once unbricked, apply latest version update.
Again, thanks a lot!.. Best regards.
mnabarro said:
I've been stuck with the bricked 2 day old tablet for at least 3 months. Today I did the procedure you described and it worked. I had to install version V11.2.3.18.2 and then, once unbricked, apply latest version update.
Again, thanks a lot!.. Best regards.
Click to expand...
Click to collapse
happy to heard it
Hi, am trying to fix my ME170CX because an original root attempt that failed and am getting a demo error message that won't go away.
I tried following all your instructions to fix this but it gets stuck "waiting for device" once I begin entering the commands.
I have tried multiple sd cards (including a sandisk) and both the V11.2.3.27 & V11.2.3.28 firmware versions to no avail.
I also tried naming the zip file K017 & K01A.
I am also wondering why we need to download the USB driver file? I don't see anywhere in your instructions on what to do with this.
Any help would be greatly appreciated.
Mike
mashton70 said:
Hi, am trying to fix my ME170CX because an original root attempt that failed and am getting a demo error message that won't go away.
I tried following all your instructions to fix this but it gets stuck "waiting for device" once I begin entering the commands.
I have tried multiple sd cards (including a sandisk) and both the V11.2.3.27 & V11.2.3.28 firmware versions to no avail.
I also tried naming the zip file K017 & K01A.
I am also wondering why we need to download the USB driver file? I don't see anywhere in your instructions on what to do with this.
Any help would be greatly appreciated.
Mike
Click to expand...
Click to collapse
Youll want to get your answer from him but i think i may be able to help. You need to install usb drivers so you can access abd and give commands to your tablet. Which i think is why it just says waiting for device... I could be wrong though....
Sent from my Nexus 6
anthonyg45157 said:
Youll want to get your answer from him but i think i may be able to help. You need to install usb drivers so you can access abd and give commands to your tablet. Which i think is why it just says waiting for device... I could be wrong though....
Sent from my Nexus 6
Click to expand...
Click to collapse
OK, I finally got the usb drivers working on my computer and made it through all commands which is much further than I was getting before.
I got to step 8 "Disconnect the USB cable and select the SD update or Recovery" and selected "Recovery" in DROIDBOOT (I don't have an "SD update" option there) and after like 1 second of "installing system updates" I get the android falling over guy error and then it hangs on the asus splash screen for ever.
download ME70CX for ME170CX
anthonyg45157 said:
Youll want to get your answer from him but i think i may be able to help. You need to install usb drivers so you can access abd and give commands to your tablet. Which i think is why it just says waiting for device... I could be wrong though....
Sent from my Nexus 6
Click to expand...
Click to collapse
have you been able to restore it ?
Can NOT use download of ME170C
Use download of ME70CX. Just did it, and tablet back to "almost" normal.
I have wifi button issue now. Button is stuck.
bye
ydobon.999 said:
have you been able to restore it ?
Can NOT use download of ME170C
Use download of ME70CX. Just did it, and tablet back to "almost" normal.
I have wifi button issue now. Button is stuck.
bye
Click to expand...
Click to collapse
That did it!
I used the firmware ME70CX and renamed the file "K01A_sdupdate.zip" and followed all of the other steps as per the original instructions and got my ME170CX working again but for one problem. . . I was still getting the "demo has stopped" error! So I proceeded to attempt root again, this time with RootZenFone-1.4.6r and and now it's working perfectly and rooted as well!
Many thanks to all!!
Hi Guys,
I'm hoping someone can help me here with unbricking my daughters Nabi 2 tablet.
The long story short is that I've tried to update to the latest OTA with TWRP 2.3.3.0 (Nabi 1.9.37) and gapps installed in the past (in order to have google play services).
After downloading the OTA and successfull file verification it booted into TWRP mode and this is when things went wrong...
As I wasn't sure about how to even leave the TWRP mode I have hit few things by accident (I think one of them asked me if I want to wipe my ROM and I said YES + when I was after that trying to reboot the tablet it gave me a warning saying something like "you have no OS installed - are you sure to reboot?).
Now, of course due to my stupid actions it doesn't work - stuck on Nabi boot logo and when I try to pres Volume+ and Power together it gives me the screen with 4 options to choose from (Boot Normally, Fastboot Protocol, Recovery Kernel, Forced Recovery) but I still can't select/move the highlighted item. All what I'm able to do now is to power it off by holding the power button pressed for couple seconds.
Based on your experience here - is there anything that can be done or is it a "real brick" and we need to buy something new for her?
Thank you for any suggestions.
Hi,
I managed to boot into TWRP somehow...
Could someone please direct me how I can re-flash it with a Nabi 2 UK OS (and where I can source the file from if possible at all)?
Cheers,
T1000
termostat1000 said:
Hi,
I managed to boot into TWRP somehow...
Could someone please direct me how I can re-flash it with a Nabi 2 UK OS (and where I can source the file from if possible at all)?
Cheers,
T1000
Click to expand...
Click to collapse
Try sections 9 and 10. http://forum.xda-developers.com/nabi-2/general/nabi-information-t3229119
Hi,
Using NabiLab I managed to load stock 1.9.37 through TWRP.
At the moment tablet will start, let me through the initial setup wizard and go into normal mode from when it was new (no Google services available).
When I try to install gapps (TWRP mode) using NabiLab it goes into endless boot loop showing just a splash screen of the screen lock and reloads again.
I tried also bringing it more to factory condition but it is not recognised in NabiLab when android is fully booted (even though PC can see it). I tried different drivers but without too much luck. When in TWRP mode it comes up as Alcatel ADB Device and when adroid is booted it comes up as a storage device rather than ADB.
I feel I'm pretty close but I need just a hint how to solve it finally without bricking it for real...
Cheers
T
termostat1000 said:
Hi,
Using NabiLab I managed to load stock 1.9.37 through TWRP.
At the moment tablet will start, let me through the initial setup wizard and go into normal mode from when it was new (no Google services available).
When I try to install gapps (TWRP mode) using NabiLab it goes into endless boot loop showing just a splash screen of the screen lock and reloads again.
I tried also bringing it more to factory condition but it is not recognised in NabiLab when android is fully booted (even though PC can see it). I tried different drivers but without too much luck. When in TWRP mode it comes up as Alcatel ADB Device and when adroid is booted it comes up as a storage device rather than ADB.
I feel I'm pretty close but I need just a hint how to solve it finally without bricking it for real...
Cheers
T
Click to expand...
Click to collapse
Pretty hard to brick a Nabi2.
Why did you choose 1.9.37? Isn't the latest 2.3.2 and already has Gapps?
When in Android do you have ADB turned on in Developer options?
Is this the procedure you used?
a) Download the ROM for your device in section 10
b) Boot to TWRP (see above for instructions)
c) Do a backup of just the boot partition in TWRP.
- Click Restore tab
- Just check "boot" and nothing else.
- Swipe to Backup
d) Eject the external SD from the tablet and place in the computer
- Note: You should unmount the card from the mount tab in TWRP before ejecting it. (Uncheck the box next to external SD)
e) Connect the SD card to you computer
f) On the SD card navigate to the folder TWRP/BACKUPS/XXXX. XXX is a serial number unique to your Nabi.
g) Make a new folder and call in whatever you want. So it should now look like TWRP/BACKUPS/XXX/yourfolder
h) Unzip the ROM file you downloaded in to the "yourfolder" you created above. The files should look like ext4.system.win, emmc.boot.win, ext.addon.win, etc. Inside the the "yourfolder" directory.
i) Download the bootloader zip for your device from section 10
j) Copy it to the external SD in a location you will remember. This will be for the bootloader update.
k) Eject the SD card from your computer (safely eject it)
l) Install SD card in Nabi
- After inserted in tablet go to TWRP mount tab and check the box to mount the SD card
m) Go to restore tab, and find the backup under the "yourfolder" you made and unzipped the files to.
n) You should be able to select boot, system, and addon and skip the others.
o) If everything restores then go to TWRP install tab, find the bootloader.zip you downloaded and install it.
p) Reboot
Code:
[U][B]Nabi2 Original United Kingdom (NABI-NV7A-UK)[/B][/U]
Version 2.3.2[URL="https://www.androidfilehost.com/?fid=24269982087011751"] Download[/URL]
ROM Mirror[URL="http://www.nabtabhacks.com/downloads/232UKstock.zip"] Download[/URL]
Bootloader [URL="https://www.androidfilehost.com/?fid=24269982087013995"] Download[/URL]
aicjofs said:
Pretty hard to brick a Nabi2.
Why did you choose 1.9.37? Isn't the latest 2.3.2 and already has Gapps?
When in Android do you have ADB turned on in Developer options?
Is this the procedure you used?
a) Download the ROM for your device in section 10
b) Boot to TWRP (see above for instructions)
c) Do a backup of just the boot partition in TWRP.
- Click Restore tab
- Just check "boot" and nothing else.
- Swipe to Backup
d) Eject the external SD from the tablet and place in the computer
- Note: You should unmount the card from the mount tab in TWRP before ejecting it. (Uncheck the box next to external SD)
e) Connect the SD card to you computer
f) On the SD card navigate to the folder TWRP/BACKUPS/XXXX. XXX is a serial number unique to your Nabi.
g) Make a new folder and call in whatever you want. So it should now look like TWRP/BACKUPS/XXX/yourfolder
h) Unzip the ROM file you downloaded in to the "yourfolder" you created above. The files should look like ext4.system.win, emmc.boot.win, ext.addon.win, etc. Inside the the "yourfolder" directory.
i) Download the bootloader zip for your device from section 10
j) Copy it to the external SD in a location you will remember. This will be for the bootloader update.
k) Eject the SD card from your computer (safely eject it)
l) Install SD card in Nabi
- After inserted in tablet go to TWRP mount tab and check the box to mount the SD card
m) Go to restore tab, and find the backup under the "yourfolder" you made and unzipped the files to.
n) You should be able to select boot, system, and addon and skip the others.
o) If everything restores then go to TWRP install tab, find the bootloader.zip you downloaded and install it.
p) Reboot
Code:
[U][B]Nabi2 Original United Kingdom (NABI-NV7A-UK)[/B][/U]
Version 2.3.2[URL="https://www.androidfilehost.com/?fid=24269982087011751"] Download[/URL]
ROM Mirror[URL="http://www.nabtabhacks.com/downloads/232UKstock.zip"] Download[/URL]
Bootloader [URL="https://www.androidfilehost.com/?fid=24269982087013995"] Download[/URL]
Click to expand...
Click to collapse
Hi aicjofs,
I followed the steps above except step c which I haven't done.
So it looked good with the NabiLab built in 1.9.37 and it seemed to load fine with my TWRP 2.3.3.0 but it was hgoing into this endless boot loop after trying to install gapps. BTW I went for 1.9.37 as it came with NabiLab and turned right.
After your reply I've donwloaded the 232UK stock rom and bootloader. Copied both onto SD card - at that stage it would let me do a restore directly from the SD card so I've copied the 232UK rom into internal memory. Restore process went OK and at the end I've installed its dedicated bootloader...
Right now the situation is that I can only boot into TWRP but restore doesn't show any available roms (both internal or external memory) even though there is backup folder on the SD card.
What worries me the most is when I go to advanced / file manager / sdcard (internal memory) in TWRP mode it doesn't show any files or folders there. When I try to dipslpay tablet information in NabiLab it shows the external SD card properties properly (capacity/free space) but on the internal memory it says "Size df:KB Free can'tKB used find".
Does it mean it has wiped all the internal memory down to zero? Would this be the reason for recovery no being able to identify the roms on external SD card too?
Looking at the log in TWRP mode it is filled with entries like
E:Unable to mount '/data'
E:Unable to mount '/cache'
E:Can't open /cache/recovery/last_install
E:Can't open (No such file or directory)
What a pain is this thing, honestly...
termostat1000 said:
Hi aicjofs,
I followed the steps above except step c which I haven't done.
So it looked good with the NabiLab built in 1.9.37 and it seemed to load fine with my TWRP 2.3.3.0 but it was hgoing into this endless boot loop after trying to install gapps. BTW I went for 1.9.37 as it came with NabiLab and turned right.
After your reply I've donwloaded the 232UK stock rom and bootloader. Copied both onto SD card - at that stage it would let me do a restore directly from the SD card so I've copied the 232UK rom into internal memory. Restore process went OK and at the end I've installed its dedicated bootloader...
Right now the situation is that I can only boot into TWRP but restore doesn't show any available roms (both internal or external memory) even though there is backup folder on the SD card.
What worries me the most is when I go to advanced / file manager / sdcard (internal memory) in TWRP mode it doesn't show any files or folders there. When I try to dipslpay tablet information in NabiLab it shows the external SD card properties properly (capacity/free space) but on the internal memory it says "Size df:KB Free can'tKB used find".
Does it mean it has wiped all the internal memory down to zero? Would this be the reason for recovery no being able to identify the roms on external SD card too?
Looking at the log in TWRP mode it is filled with entries like
E:Unable to mount '/data'
E:Unable to mount '/cache'
E:Can't open /cache/recovery/last_install
E:Can't open (No such file or directory)
What a pain is this thing, honestly...
Click to expand...
Click to collapse
My fault. I forgot to tell you once you update the bootloader you need to use TWRP for Jellybean, you are still using TWRP for Ice Cream Sandwich .
Code:
[B][U]Nabi2 Original (NABI-NV7A)[/U][/B]
Ice Cream Sandwich TWRP 2.6.3[URL="http://forum.xda-developers.com/attachment.php?attachmentid=2586828&d=1392743412"] Download[/URL]
Jellybean TWRP 2.8.5[URL="http://forum.xda-developers.com/attachment.php?attachmentid=3211498&d=1426404068"] Download[/URL]
KitKat TWRP 2.8.7[URL="http://forum.xda-developers.com/attachment.php?attachmentid=3473994&d=1442276115"] Download[/URL]
Discussion Thread [URL="http://forum.xda-developers.com/showthread.php?t=2074501"]Link[/URL]
At that point you can try to restore the 2.3.2 ROM again. Or try the 2.2 ROM http://forum.xda-developers.com/showpost.php?p=50341726&postcount=85
aicjofs said:
My fault. I forgot to tell you once you update the bootloader you need to use TWRP for Jellybean, you are still using TWRP for Ice Cream Sandwich .
Code:
[B][U]Nabi2 Original (NABI-NV7A)[/U][/B]
Ice Cream Sandwich TWRP 2.6.3[URL="http://forum.xda-developers.com/attachment.php?attachmentid=2586828&d=1392743412"] Download[/URL]
Jellybean TWRP 2.8.5[URL="http://forum.xda-developers.com/attachment.php?attachmentid=3211498&d=1426404068"] Download[/URL]
KitKat TWRP 2.8.7[URL="http://forum.xda-developers.com/attachment.php?attachmentid=3473994&d=1442276115"] Download[/URL]
Discussion Thread [URL="http://forum.xda-developers.com/showthread.php?t=2074501"]Link[/URL]
At that point you can try to restore the 2.3.2 ROM again. Or try the 2.2 ROM http://forum.xda-developers.com/showpost.php?p=50341726&postcount=85
Click to expand...
Click to collapse
Forgive me please but I'm not entirely sure how to load this TWRP 2.8.5 for JellyBean on it with TWRP 2.3.3.0 in place..
Cheers
termostat1000 said:
Forgive me please but I'm not entirely sure how to load this TWRP 2.8.5 for JellyBean on it with TWRP 2.3.3.0 in place..
Cheers
Click to expand...
Click to collapse
You will need to use fastboot to load it. If you have a nabilab folder it already has fastboot available. So using the procedure below you couldn't download the ZIP file I linked in post above. Extract the from the zip the recovery.img or twrp-recovery.img and put it in the nabilab folder. (Im puling the procedure from http://forum.xda-developers.com/nabi-2/general/nabi-information-t3229119 )
1) To load TWRP we will be in the fastboot operational mode(see section 3)
Device powered off:
-Depending on device press and hold the power and vol - keys OR power and vol + key. Some will boot straight to recovery, and others will come to the "bootloader" screen. We want the bootloader.
-To enter fastboot use vol+ and vol- to highlight and select fastboot protocol. (Device will need to be plugged in to computer and fastboot driver installed before the screen will change)
Device powered on:
-Use ADB and execute from the command line:
Code:
adb reboot-bootloader
2) USB plugged in and Fastboot/Bootoader Driver loaded(see section 4) verify with windows device manager if needed.
3) Download the TWRP zip file for your device from TWRP list below(see section 8)
4) Extract the file to the location your are running your command prompt(see section 6)
-The file will be called twrp-recovery.img or recovery.img
5) Depending on the name of the file in step 4, load TWRP by typing at the command prompt:
Code:
fastboot flash recovery recovery.img
or
Code:
fastboot flash recovery twrp-recovery.img
aicjofs said:
You will need to use fastboot to load it. If you have a nabilab folder it already has fastboot available. So using the procedure below you couldn't download the ZIP file I linked in post above. Extract the from the zip the recovery.img or twrp-recovery.img and put it in the nabilab folder. (Im puling the procedure from http://forum.xda-developers.com/nabi-2/general/nabi-information-t3229119 )
1) To load TWRP we will be in the fastboot operational mode(see section 3)
Device powered off:
-Depending on device press and hold the power and vol - keys OR power and vol + key. Some will boot straight to recovery, and others will come to the "bootloader" screen. We want the bootloader.
-To enter fastboot use vol+ and vol- to highlight and select fastboot protocol. (Device will need to be plugged in to computer and fastboot driver installed before the screen will change)
Device powered on:
-Use ADB and execute from the command line:
Code:
adb reboot-bootloader
2) USB plugged in and Fastboot/Bootoader Driver loaded(see section 4) verify with windows device manager if needed.
3) Download the TWRP zip file for your device from TWRP list below(see section 8)
4) Extract the file to the location your are running your command prompt(see section 6)
-The file will be called twrp-recovery.img or recovery.img
5) Depending on the name of the file in step 4, load TWRP by typing at the command prompt:
Code:
fastboot flash recovery recovery.img
or
Code:
fastboot flash recovery twrp-recovery.img
Click to expand...
Click to collapse
Hi,
Thank you very much for your help but it clearly looks that this is way beyond my knowledge on how to use all of these fastboot, command, adb and so on...
I regret I ever touched the thing at all.
So there is absolutely no easy way - command line is a must from where I am right now?
termostat1000 said:
Hi,
Thank you very much for your help but it clearly looks that this is way beyond my knowledge on how to use all of these fastboot, command, adb and so on...
I regret I ever touched the thing at all.
So there is absolutely no easy way - command line is a must from where I am right now?
Click to expand...
Click to collapse
Its not a must but easiest to try and walk you through. Which version of Nabilab are you using? You could move some files around and still use Nabilab. Up to you which way to go forward. I'll try and help.
aicjofs said:
Its not a must but easiest to try and walk you through. Which version of Nabilab are you using? You could move some files around and still use Nabilab. Up to you which way to go forward. I'll try and help.
Click to expand...
Click to collapse
Hi,
I'm not so much afraid of copy/paste for cmd... the biggest fear is that I don't know anything about ADB, fasboot etc. So when your instruction in previous post says use ADB and I purely don't know what it means.
I think if the option is there I'd like to ask if you could help with restoring it with Nabilab.
Thanks a million for your help!
T
termostat1000 said:
Hi,
I'm not so much afraid of copy/paste for cmd... the biggest fear is that I don't know anything about ADB, fasboot etc. So when your instruction in previous post says use ADB and I purely don't know what it means.
I think if the option is there I'd like to ask if you could help with restoring it with Nabilab.
Thanks a million for your help!
T
Click to expand...
Click to collapse
Which version of Nabilab are you using? Is it the commandline version. Black window, where you have to use keyboard to make selections?
aicjofs said:
Which version of Nabilab are you using? Is it the commandline version. Black window, where you have to use keyboard to make selections?
Click to expand...
Click to collapse
Hi,
I'm using Nabilab ver 2 - black windows with keyboard made selections.
termostat1000 said:
Hi,
I'm using Nabilab ver 2 - black windows with keyboard made selections.
Click to expand...
Click to collapse
Find the Nabilab folder on your computer. Open the "recovery" folder. Then open the "stock" folder. Inside it there is recovery.img file. Rename it to recoverystock.img.
You downloaded the twrp-recovery-JBNV7AUS.zip from a few posts back. Extract the twrp-recovery.img file and put it in the stock folder. Now rename the twrp-recovery.img file to recovery.img.
Now boot the tablet to TWRP recovery(the one that isn't working) and run Nabilab. Select 4 Install recoveries. Then 4 instal stock recovery. Then reboot in to recovery and see if you have the 2.8.5 recovery
aicjofs said:
Find the Nabilab folder on your computer. Open the "recovery" folder. Then open the "stock" folder. Inside it there is recovery.img file. Rename it to recoverystock.img.
You downloaded the twrp-recovery-JBNV7AUS.zip from a few posts back. Extract the twrp-recovery.img file and put it in the stock folder. Now rename the twrp-recovery.img file to recovery.img.
Now boot the tablet to TWRP recovery(the one that isn't working) and run Nabilab. Select 4 Install recoveries. Then 4 instal stock recovery. Then reboot in to recovery and see if you have the 2.8.5 recovery
Click to expand...
Click to collapse
Great!
Your trick worked fine and now I can see TWRP 2.8.5.0 and I have problems with drivers - keeps failing to recognize the tablet.
I'll work on the driver issue or is there something I should know about it with TWRP 2.8.5.0 lodaed?
What is my next step from here as Android is still stuck on Nabi logo (no motion) and I'm afraid to do anything in case I create even bigger mess than I already have
I also noticed when I try to shut it down from inside TWRP it asks me a question if I want to root the tablet (Install super SU) - is it something I should do and at what stage?
Thanks!
T
termostat1000 said:
Great!
Your trick worked fine and now I can see TWRP 2.8.5.0 and I have problems with drivers - keeps failing to recognize the tablet.
I'll work on the driver issue or is there something I should know about it with TWRP 2.8.5.0 lodaed?
What is my next step from here as Android is still stuck on Nabi logo (no motion) and I'm afraid to do anything in case I create even bigger mess than I already have
I also noticed when I try to shut it down from inside TWRP it asks me a question if I want to root the tablet (Install super SU) - is it something I should do and at what stage?
Thanks!
T
Click to expand...
Click to collapse
If you can see the files again now with the correct TWRP. You can try to restore the 2.3.2 ROM again. Or maybe try the procedure from post #5 with the 2.2 ROM I linked to in post #7. You don't have to do the bootloader install anymore so skip that step. Installing root doesn't matter, you can choose to install or not.
aicjofs said:
If you can see the files again now with the correct TWRP. You can try to restore the 2.3.2 ROM again. Or maybe try the procedure from post #5 with the 2.2 ROM I linked to in post #7. You don't have to do the bootloader install anymore so skip that step. Installing root doesn't matter, you can choose to install or not.
Click to expand...
Click to collapse
You're a STAR!
All happy working as new with 232UK ROM and bootloader loaded with your instructions.
I'd never get this sorted without your specialized help.
If I only could I'd send you something just to say Thank You...
T - Happy Dad of Amelia
termostat1000 said:
You're a STAR!
All happy working as new with 232UK ROM and bootloader loaded with your instructions.
I'd never get this sorted without your specialized help.
If I only could I'd send you something just to say Thank You...
T - Happy Dad of Amelia
Click to expand...
Click to collapse
Your thanks is enough Glad we got it sorted and a happy kid!