Related
I finally did what Archos support said couldn’t be done. I was able to downgrade my firmware from the extremely buggy (and non-rootable) 2.0.71 firmware, to the 2.0.54 rootable firmware.
Warning: This process involves downloading and installing the Archos SDE firmware. This WILL void your warranty. Proceed at your own risk!
This process was done using a Windows 7 machine (and the Archos tablet, of course).
Phase 1 – Removing the 2.0.71 firmware and replacing it with the Angstrom OS
1. If you do not have your Archos plugged into the AC Adapter, plug it in now.
2. Download the SDE Developer Edition firmware here:
http://www.archos.com/support/download/firm_dev/firmware_archos_android_gen8.aos
3. Power off your Archos (if powered on). Then boot your Archos in Recovery mode by holding the Volume – button and pressing the power button. Release the power button, but keep the Volume – button held down. It will boot into recovery mode.
Recovery Mode navigation works as follows:
Volume + moves up
Volume – moves down
Pressing Power is Enter
4. Press Volume – to Format System and Press Power.
5. Press Volume – to Reformat Device and Press Power.
Warning: Make sure you have backed up any critical data on your Archos tablet prior to proceeding any further. If you have not backed up your data, select No and press Power, and No on the previous menu. At that point it will reboot the device and you can back up your data.
6. Press Volume – to I understand and press Power. It will then reformat the partitions.
7. When the USB Connection menu appears, plug in the Micro USB cable into your computer and into the Archos tablet. Windows (or your mac, I suppose) will recognize the tablet as a drive letter in My Computer - Mine was A101IT (I). Copy the SDE firmware file firmware_archos_android_gen8.aos to the tablet (e.g. drive I: on my computer). Copy to the root directory ( /) folder on the tablet.
8. Once the copy is done, press Power on the Archos Tablet (and remove the Micro USB Cable)
9. It will install the SDE firmware, then reboot.
10. It will boot into the AngStrom OS. At first this OS looks intimidating, but it is quite harmless.
11. It will come up with a new user details screen. Type in a user name, a password, and confirm the password. Then press OK. It will then log in and take you to the desktop.
12. Press the ^ key in the lower left hand side of the screen, and press Turn off. You may have to press a few times to get it to respond as the touch responsiveness was NOT very good for me.
13. Press Yes to log off. It will then power down
Phase 2 – Installing the 2.0.54 firmware onto your tablet.
1. If you do not have your Archos plugged into the AC Adapter, plug it in now.
2. On your pc, download the Archos 2.0.54 firmware from here:
http://www.arctablet.com/assets/archos-firmware/gen8_2.0.54-firmware_archos_android_gen8.aos
3. Rename the file firmware_archos_android_gen8.aos. (If you downloaded the file in the same place you downloaded the SDE firmware file, just overwrite it.)
4. Then boot your Archos in Recovery mode by holding the Volume – button and pressing the power button. Release the power button, but keep the Volume – button held down. It will boot into recovery mode.
Recovery Mode navigation works as follows:
Volume + moves up
Volume – moves down
Pressing Power is Enter
5. Press Volume – to Format System and Press Power.
6. Press Volume – to Reformat Device and Press Power.
7. Press Volume – to I understand and press Power. It will then reformat the partitions.
8. When the USB Connection menu appears, plug in the Micro USB cable into your computer and into the Archos tablet. Windows (or your mac, I suppose) will recognize the tablet as a drive letter in My Computer - Mine was A101IT (I). Copy the 2.0.54 firmware file firmware_archos_android_gen8.aos to the tablet (e.g. drive I: on my computer). Copy to the root directory ( /) folder on the tablet.
9. Once the copy is done, press Power on the Archos Tablet (and remove the Micro USB Cable)
10. It will install the 2.0.54 firmware, then reboot.
11. Congratulations, you now have the 2.0.54 firmware installed.
Enjoy,
Jason Andreas
I can confirm this guide is correct. Downgrade working. Only for 2.0.54 . Downgrade to 1.0.84 has failure message .
2.0.54 with z4root and setCPU 1000 gives faster A70IT than 2.0.71 fw Overdrive mode. And less screen decalibration issues.
EDIT : Original guide was posted in androidtablets.net forum
For some unknown reason my 101it can't see my home network after downgrading! It's able to see my neighbours wep encrypted network but not mine which is wpa encrypted? Anybody else having this problem and any solution would be appreciated.
Need some help guys;
Step 10 of the phase 2 :
I have copy/paste the .aos file in the root directory but I have this message : "Update failed: (1)"
Sry for bad English, I'm french..
PS : This is not the first time I do that kind of skill =X
1. It only sees WEP encrypted networks. (2.0.54 problem) , change your to WEP and everything is ok.
2. Are you sure you copied 2.0.54 aos file and not the 1.0.84 ??? Download again and copy it again. and carefull to lace it in root (not in folder by accident)
thanks for the quick reply.bit ****e that it only see's wep networks though . anybody know of a workaround to get wpa recognised?
lagoskon said:
1. It only sees WEP encrypted networks. (2.0.54 problem) , change your to WEP and everything is ok.
2. Are you sure you copied 2.0.54 aos file and not the 1.0.84 ??? Download again and copy it again. and carefull to lace it in root (not in folder by accident)
Click to expand...
Click to collapse
2.0.54 and WPA2 PSK running fine here.
iznogooood said:
2.0.54 and WPA2 PSK running fine here.
Click to expand...
Click to collapse
Confirmed ...
I tried WPA/WPA2 combined in my router . I turned to WPA2 PSK and it connects fine. Thanks
I am able to get connected via WPA2 with my A101 without any problems.
@apr24991, thanks a lot for this guide! I did not downgrade to 2.0.54, but i've used your guide to permanently boot to urokdroid's kernel. I'm now able to boot urokdroid's 2.0.71 without going through the recovery menu. Now I don't need to press volume - while powering up or rebooting to up bring up the modified kernel/initramfs. It now always boot to urokdroid's kernel which is what i want.
@constant7010 : Bravo ! And ... how did you do so ?
I'm quite interested but how did you converte the urku files to .aos file ?
if i could have urku native on my a101 it should be e great thing !
I'll try to retrace the steps I did, and put more detailed/clear instructions if i have a chance, but basically here's what i did:
1) follow uruk's instructions on installing to sd card. create 2 ext4 partitions 1 for root 1 for data.
2) create additional 2 ext4 partitions on the SD.
3) boot into uruk's kernel.
4) use adb to mount the 2 partitions (/tmp/rawfs, /tmp/system), and copy the contents of /mnt/rawfs to 3rd partition and the contents of /mnt/system to 4th partition (cp -a /mnt/rawfs/* /tmp/rawfs/, cp -a /mnt/system/* /tmp/system/)
5) extract and modify initramfs.cpio.gz. i edited etc/moutpoints change the devices for rawfs, system and data to the devices of sd partitions (e.g. mmcblk0p1 to mmcblk2p3, etc). change mount type to ext4 with noatime option.
6) repackage initramfs.cpio.gz.
7) follow the phase 1 downgrade instructions here. this will natively boot the developer edition.
8) go to recovery menu, developer menu, then go to flash kernel/initramfs. flash uruk's kernel and the modified initramfs.cpio.gz.
after this everytime you boot or power on it will always boot to sd card.
USB host gone
Hi, anybody having problems with the USB host after downgrading?
I can´t connect anything anymore, no mouse or memory stick.
@constant7010 : tx for you guideline.
So i assume that IF i want to boot with the original system i just have to boot in recovery mode and select Android Boot ?
I asked just to know if i keep the choice to boot a proper systeme if something goes wrong with the sd card
@foxtrotter,
I'm not sure about but this is what I have observed. After you apply Phase 1 of the instructions in post#1, you actually lose your android firmware, and will be replaced by developer mode firmware (Angstorm). So everytime you boot it always boot in developer mode. In fact after this, you will no longer see Android as one of the boot options in recovery mode. However you can always reapply the Android firmware in the recovery menu to bring back the original OS.
Actually on my first try after doing phase 1, i thought applying urok's kernel and initramfs.cpio is enough. But my system just kept on rebooting. Since Android was no longer accessible in recovery menu, I had to reapply the Android firmware, which is phase 2 on post#1, but using 2.0.71 firmware. And then I traced the Android boot process, and it looks it's accessing the contents /mnt/rawfs and /mnt/system which were missing after you apply phase 1. So I tried copying the contents of /mnt/rawfs and /mnt/system to 2 new partitions in my SD, and modify initramfs to use these partitions. And after applying phase 1 again, and putting urok's kernel and my modified initramfs, it now successfully boots to SD.
flo44 said:
Need some help guys;
Step 10 of the phase 2 :
I have copy/paste the .aos file in the root directory but I have this message : "Update failed: (1)"
Sry for bad English, I'm french..
PS : This is not the first time I do that kind of skill =X
Click to expand...
Click to collapse
@flo44,
Make sure that you renamed the Gen8_2.0.54-firmware_archos_android_gen8.aos file to just firmware_archos_android_gen8.aos. Then copy the renamed file to your Archos. Make sure the file is placed in the root folder (/) of the device.
Look at step 3 under Phase 2.
If you just copy the file over without renaming it, you will get the (1) error.
You can always power the unit off and boot back into recovery and start Phase 2 over.
k1nk33 said:
For some unknown reason my 101it can't see my home network after downgrading! It's able to see my neighbours wep encrypted network but not mine which is wpa encrypted? Anybody else having this problem and any solution would be appreciated.
Click to expand...
Click to collapse
k1nk33,
I was playing around yesterday trying to get different 1.x firmwares to work with no avail. So then I decied to go back to the 2.0.54 firmware. When I did, I noticed that my wifi was not working. So I upgraded to the 2.0.74 firmware, then went through the whole downgrade process again. That fixed my problem.
@constant7010 : ok so i can see you rule to manage the Archos SDE boot.
I'm not so confident so i will keep my backup solution with multi boot.
But plz don't hesitate to keep us aware of the stability of your new configuration with those added partitions !
can i downgrade from 2.1.4 (froyo2.2.1) to 2.0.54 following this tutorial?
thanks in advance!
regards.
Write Protected
Hi there,
i tried that tutorial, but i cant copy any files on the root file system of the pad. It says "Device is write protected."
What did i do wrong?
Regards
Serpens
I figured Id start another thread so no one has to search and read thru all other threads for help like I had to.
I had to write this because i thought other guides were incomplete, and frankly they didnt work.
I will try to update and make things easier to read and use spellchecker when time permits.
and add in-between steps that i left out because i have no dam time. Thats why i call it expert guide-you need some knowledge of doing this.
This is just to help out someone who has had a hard time with other guides
It is not a step by step
Knowledge of cygwin and adb is expected.
Learn it, and how to setup, using google and xda like the rest of us.
I TAKE NO RESPONSIBILITY OF BRICKING YOUR PHONE ANY MORE THAN IT IS.
Here is were I made the mistake:
http://forum.xda-developers.com/showthread.php?t=1745865
These are the 2 files
1.Galaxy-S-fre3-2.51.zip
2.Galaxy-S-fre3-MD4FirmwareModemAIO.zip
First of all I ALWAYS CHECK MDMSUMS
The second zip was flashed first, and wamo no andro
Heres my specs.
Android Ver:
4.3
Baseband Ver:
L710VPUCMK3
Build:
JSS15JL710VPUCMK3
Hardware Ver:
L710.14
Im guessing it bricked my phone because I flashed the Galaxy-S-fre3-MD4FirmwareModemAIO.zip before the actual rom itself "Galaxy-S-fre3-2.51.zip"
Obviosly I should have done it the other way around, well im only hu............ngry. haha, so im a knuklehead.
I refuse to go to that particular site to read the first post and see if there is some sort of DONT FLASH OUT OF ORDER OR RISK LOOSING A LIMB, warning posted.
I thought i lost my device (this is still a bad-ass phone, almost too nice to be in a roofers pouch and getten toren up. But it takes really nice pictures of my custom work, and takes em fast so i can get back to work.
I lost 12 hours for stupid mistake, (im sure someone will say thats the business, of course thats why we do it.)
Not to mention the last device i bricked was my first (Hero) and thought was my last.
When you play the Rom Game you may get Ram'd
I will post this to that fre3 site, however unless the OP makes note of this others will be in the same mess.
The only life left in the device, was red light, when battery removed (when battery was placed in during charge, red light went out in 5 to 10 sec.)
When battery was in unit, no lights at all.
I noticed when usb cable attached to ubuntu, oh **** i forgot what and how i saw it but it was some kind of Qualcomm Device _DLMODE or somthing.
I will edit this post when i find it again, but anyway that led to nothing.
My first attempts were made following this guide: http://forum.xda-developers.com/showthread.php?t=2369125
I couldnt figure out by reading the threads if how I was to format the fat32 partition default 8 or 4 or 1Mg
I couldnt understand why we would have to try to write the image over and over...Why it wouldnt write it right the first time.
I had a hard time trying to write the image file ..debrick_sph_l710.img to sdcard using my v-box..
(Virtual-Box under windows 8 with Ubuntu 13.10 installed ....Android-Kernel-Build ready ).
After trying all the different ways and different images, I said screw it i give up.
.........Till after dinner
wife made a roasted chicken not gonna be late.
Finally I made my own image from my wifes phone, because we bought them at the same time.
One problem hers isnt rooted and she wasnt about to let me touch it.............
Solution: I bought her a galaxy4 for 49.00 /w upgrade, now i have 2 galaxy 3's. But only one works.:/
That was a pain rooting because she always excepts the firmware upgrades when they come over air.
Couldnt get the "seLinux seAndroid" thing so i just went back to 4.1 for now so that i could adb.
Heres What Did It...
http://forum.xda-developers.com/showthread.php?t=2345860
HERES HOW I DID IT
To extract a de-brick image from your phone (an UnBricked Phone) do in an adb shell:
If you know the partition use:
dd if=/dev/block/mmcblk0 of=/sdcard/HomefixSprint_S3_L710.img bs=1048576 count=70
If not use:
dd if=/dev/block/platform/msm_sdcc.1/by-name/modem of=/sdcard/HomefixSprint_S3_L710.img bs=1048576 count=70
MY TERMINAL SHOWS:
C:\Users\dad>adb shell
[email protected]:/ # busybox dd if=/dev/block/mmcblk0 of=/sdcard/HomefixSprint_S3_L710.img bs=1048576 count=70
0 of=/sdcard/HomefixSprint_S3_L710.img bs=1048576 count=70 <
70+0 records in
70+0 records out
73400320 bytes (70.0MB) copied, 4.578239 seconds, 15.3MB/s
Take that image, copy it to your cygwin directory and write it to an unformatted 16mb sdcard using cygwin:
TO GET THE SDCARD READY:
get EaseUS Partition Master Free Edition-Free For Home Users
and find the sdcard, its about 14.82GB, if u have more than 1 your on your own.
Select that one, and delete all partitions.
Then, New partition, select fat32, and then finish by applying the operations.
DO NOT FORMAT
IN CYGWIN:
Get sdcard info:
cat /proc/partitions
MY TERMINAL SHOWS:
[email protected] ~
$ cat /proc/partitions
major minor #blocks name
8 0 976762584 sda
8 1 976759808 sda1
8 16 117220824 sdb
8 17 358400 sdb1
8 18 116859904 sdb2
8 32 976762584 sdc
8 33 976759808 sdc1
8 48 244198584 sdd
8 49 244196001 sdd1
8 64 976762584 sde
8 65 976657408 sde1
8 80 976762584 sdf
8 81 976760001 sdf1
8 96 976762584 sdg
8 97 976760001 sdg1
8 112 976075776 sdh
8 113 976074752 sdh1
8 128 15558144 sdi
8 129 15558110 sdi1
[email protected] ~
$ ls
debrick_sph_l710.img HomefixSprint_S3_L710.img kitchen
[email protected] ~
$ dd if=HomefixSprint_s3_L710.img of=/dev/sdi
143360+0 records in
143360+0 records out
73400320 bytes (73 MB) copied, 338.771 s, 217 kB/s
I DID WHAT I WAS SUPPOSED TO DO:
Put battery in
Connect usb cable
Insert sdcard
Vol-up/Home and Power
I felt the vibration no more than a second after pressing power (along with vol_dwn and home key pressed and held)
As you can imagine, my adrenilin was pumpped to the point of feeling like i smoked a pack of camel ciggirettes, AGAIN, as i try to boot the phone.
I knew i was out of the woods after I saw the samsung logo.
It Skipped past download.
I was able to boot right into my desktop, however there were no signal bars.
and the Baseband ver: was unknown.
I powered down the phone (man that was hard to do) but i did.
Tried to get into download mode but failed at first, recovery failed also.
Finally got to download then i was good.
NOTES:
After I revived the phone I had nothing too loose because now I had 2 S3's, so I played a bit.
Its fun to brick your phone on purpose haha
I fed this PIECE OF S#!+ Galaxy-S-fre3-MD4FirmwareModemAIO.zip to my phone the first time and i lost 12 hrs plus the time write this.
:The debrick_sph_l710.img or the Debrick_Sprint_S3_L710_4.3.img did not work for me
:I did not need the class 10, class 4 worked too
:did not need cable attached
:did not Matter wich order i put battery, sdcard, usb-cord to boot
:did not format card
nly took 1 try to write working image each time ( didnt take several attemts) I wrote and tested 3 different images.
:Upon booting It seems to be the same each time ,couple three four sec (out of a few times playing it may have taken 10sec to boot on one occasion).
:I think the issues with ubuntu was,the sdcard was not ejecting properly and corrupting the image.
:If you have a sucssesful write to sdcard, it may not show up in file explorer until you pull out card reader and re-insert it... then it will show up in file explorer as a folder called "image" with bunch of files or somthing in it, then you know it wrote ok.
:for some reason after i haha... BRICKED MY SG3 ON PURPOSE....Oh my GOD....Im SHOT, booted to my homemade image, i was able to boot into recovery as well as Download.
:Not for nothen I tried to:
dd if=/sdcard/recovery.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery
dd if=/sdcard/boot.img of=/dev/block/platform/msm_sdcc.1/by-name/boot
dd if=/sdcard/modem.img of=/dev/block/platform/msm_sdcc.1/by-name/modem
(Remember i was able to boot to system, so adb worked)
Did not work, however it may have worked if i used the syntax...mmcblk0 and such.
Questions:
Why is my debrick.img smaller than others on this site
Why my image works for my device and no others will work
Are all phones with these snapdragon cpu's have the ability to "sdcard boot"
Why do we spend endless hours with our phones and forget we have a family.
MY FILE:................ http://rooferdave.com/Downloads/sprintsg3.html
This is in the wrong forum. This is a Sprint Note 3 forum, and your guide appears to be for the S3.
Sent from my SM-N900P using Xparent BlueTapatalk 2
Homefix said:
I figured Id start another thread so no one has to search and read thru all other threads for help like I had to.
I had to write this because i thought other guides were incomplete, and frankly they didnt work.
I will try to update and make things easier to read and use spellchecker when time permits.
and add in-between steps that i left out because i have no dam time. Thats why i call it expert guide-you need some knowledge of doing this.
This is just to help out someone who has had a hard time with other guides
It is not a step by step
Knowledge of cygwin and adb is expected.
Learn it, and how to setup, using google and xda like the rest of us.
I TAKE NO RESPONSIBILITY OF BRICKING YOUR PHONE ANY MORE THAN IT IS.
Here is were I made the mistake:
http://forum.xda-developers.com/showthread.php?t=1745865
These are the 2 files
1.Galaxy-S-fre3-2.51.zip
2.Galaxy-S-fre3-MD4FirmwareModemAIO.zip
First of all I ALWAYS CHECK MDMSUMS
The second zip was flashed first, and wamo no andro
Heres my specs.
Android Ver:
4.3
Baseband Ver:
L710VPUCMK3
Build:
JSS15JL710VPUCMK3
Hardware Ver:
L710.14
Im guessing it bricked my phone because I flashed the Galaxy-S-fre3-MD4FirmwareModemAIO.zip before the actual rom itself "Galaxy-S-fre3-2.51.zip"
Obviosly I should have done it the other way around, well im only hu............ngry. haha, so im a knuklehead.
I refuse to go to that particular site to read the first post and see if there is some sort of DONT FLASH OUT OF ORDER OR RISK LOOSING A LIMB, warning posted.
I thought i lost my device (this is still a bad-ass phone, almost too nice to be in a roofers pouch and getten toren up. But it takes really nice pictures of my custom work, and takes em fast so i can get back to work.
I lost 12 hours for stupid mistake, (im sure someone will say thats the business, of course thats why we do it.)
Not to mention the last device i bricked was my first (Hero) and thought was my last.
When you play the Rom Game you may get Ram'd
I will post this to that fre3 site, however unless the OP makes note of this others will be in the same mess.
The only life left in the device, was red light, when battery removed (when battery was placed in during charge, red light went out in 5 to 10 sec.)
When battery was in unit, no lights at all.
I noticed when usb cable attached to ubuntu, oh **** i forgot what and how i saw it but it was some kind of Qualcomm Device _DLMODE or somthing.
I will edit this post when i find it again, but anyway that led to nothing.
My first attempts were made following this guide: http://forum.xda-developers.com/showthread.php?t=2369125
I couldnt figure out by reading the threads if how I was to format the fat32 partition default 8 or 4 or 1Mg
I couldnt understand why we would have to try to write the image over and over...Why it wouldnt write it right the first time.
I had a hard time trying to write the image file ..debrick_sph_l710.img to sdcard using my v-box..
(Virtual-Box under windows 8 with Ubuntu 13.10 installed ....Android-Kernel-Build ready ).
After trying all the different ways and different images, I said screw it i give up.
.........Till after dinner
wife made a roasted chicken not gonna be late.
Finally I made my own image from my wifes phone, because we bought them at the same time.
One problem hers isnt rooted and she wasnt about to let me touch it.............
Solution: I bought her a galaxy4 for 49.00 /w upgrade, now i have 2 galaxy 3's. But only one works.:/
That was a pain rooting because she always excepts the firmware upgrades when they come over air.
Couldnt get the "seLinux seAndroid" thing so i just went back to 4.1 for now so that i could adb.
Heres What Did It...
http://forum.xda-developers.com/showthread.php?t=2345860
HERES HOW I DID IT
To extract a de-brick image from your phone (an UnBricked Phone) do in an adb shell:
If you know the partition use:
dd if=/dev/block/mmcblk0 of=/sdcard/HomefixSprint_S3_L710.img bs=1048576 count=70
If not use:
dd if=/dev/block/platform/msm_sdcc.1/by-name/modem of=/sdcard/HomefixSprint_S3_L710.img bs=1048576 count=70
MY TERMINAL SHOWS:
C:\Users\dad>adb shell
[email protected]:/ # busybox dd if=/dev/block/mmcblk0 of=/sdcard/HomefixSprint_S3_L710.img bs=1048576 count=70
0 of=/sdcard/HomefixSprint_S3_L710.img bs=1048576 count=70 <
70+0 records in
70+0 records out
73400320 bytes (70.0MB) copied, 4.578239 seconds, 15.3MB/s
Take that image, copy it to your cygwin directory and write it to an unformatted 16mb sdcard using cygwin:
TO GET THE SDCARD READY:
get EaseUS Partition Master Free Edition-Free For Home Users
and find the sdcard, its about 14.82GB, if u have more than 1 your on your own.
Select that one, and delete all partitions.
Then, New partition, select fat32, and then finish by applying the operations.
DO NOT FORMAT
IN CYGWIN:
Get sdcard info:
cat /proc/partitions
MY TERMINAL SHOWS:
[email protected] ~
$ cat /proc/partitions
major minor #blocks name
8 0 976762584 sda
8 1 976759808 sda1
8 16 117220824 sdb
8 17 358400 sdb1
8 18 116859904 sdb2
8 32 976762584 sdc
8 33 976759808 sdc1
8 48 244198584 sdd
8 49 244196001 sdd1
8 64 976762584 sde
8 65 976657408 sde1
8 80 976762584 sdf
8 81 976760001 sdf1
8 96 976762584 sdg
8 97 976760001 sdg1
8 112 976075776 sdh
8 113 976074752 sdh1
8 128 15558144 sdi
8 129 15558110 sdi1
[email protected] ~
$ ls
debrick_sph_l710.img HomefixSprint_S3_L710.img kitchen
[email protected] ~
$ dd if=HomefixSprint_s3_L710.img of=/dev/sdi
143360+0 records in
143360+0 records out
73400320 bytes (73 MB) copied, 338.771 s, 217 kB/s
I DID WHAT I WAS SUPPOSED TO DO:
Put battery in
Connect usb cable
Insert sdcard
Vol-up/Home and Power
I felt the vibration no more than a second after pressing power (along with vol_dwn and home key pressed and held)
As you can imagine, my adrenilin was pumpped to the point of feeling like i smoked a pack of camel ciggirettes, AGAIN, as i try to boot the phone.
I knew i was out of the woods after I saw the samsung logo.
It Skipped past download.
I was able to boot right into my desktop, however there were no signal bars.
and the Baseband ver: was unknown.
I powered down the phone (man that was hard to do) but i did.
Tried to get into download mode but failed at first, recovery failed also.
Finally got to download then i was good.
NOTES:
After I revived the phone I had nothing too loose because now I had 2 S3's, so I played a bit.
Its fun to brick your phone on purpose haha
I fed this PIECE OF S#!+ Galaxy-S-fre3-MD4FirmwareModemAIO.zip to my phone the first time and i lost 12 hrs plus the time write this.
:The debrick_sph_l710.img or the Debrick_Sprint_S3_L710_4.3.img did not work for me
:I did not need the class 10, class 4 worked too
:did not need cable attached
:did not Matter wich order i put battery, sdcard, usb-cord to boot
:did not format card
nly took 1 try to write working image each time ( didnt take several attemts) I wrote and tested 3 different images.
:Upon booting It seems to be the same each time ,couple three four sec (out of a few times playing it may have taken 10sec to boot on one occasion).
:I think the issues with ubuntu was,the sdcard was not ejecting properly and corrupting the image.
:If you have a sucssesful write to sdcard, it may not show up in file explorer until you pull out card reader and re-insert it... then it will show up in file explorer as a folder called "image" with bunch of files or somthing in it, then you know it wrote ok.
:for some reason after i haha... BRICKED MY SG3 ON PURPOSE....Oh my GOD....Im SHOT, booted to my homemade image, i was able to boot into recovery as well as Download.
:Not for nothen I tried to:
dd if=/sdcard/recovery.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery
dd if=/sdcard/boot.img of=/dev/block/platform/msm_sdcc.1/by-name/boot
dd if=/sdcard/modem.img of=/dev/block/platform/msm_sdcc.1/by-name/modem
(Remember i was able to boot to system, so adb worked)
Did not work, however it may have worked if i used the syntax...mmcblk0 and such.
Questions:
Why is my debrick.img smaller than others on this site
Why my image works for my device and no others will work
Are all phones with these snapdragon cpu's have the ability to "sdcard boot"
Why do we spend endless hours with our phones and forget we have a family.
MY FILE:................ http://rooferdave.com/Downloads/sprintsg3.html
Click to expand...
Click to collapse
Lol hell of lot of a posting to be in a wrong forum.
Sent from my SM-N900P using Tapatalk
JonSCSL said:
Lol hell of lot of a posting to be in a wrong forum.
Sent from my SM-N900P using Tapatalk
Click to expand...
Click to collapse
Nice quoting the whole thing before it gets Stryked.
I've wanted to quote an entire OP for a long time, just never had the stones. This was a pretty risk free shot, and ya took it.
Pitch-perfect delivery my man, @JonSCSL.
I bet I dime®
Triband Cubed®
Fix-it-at-Home Likes Listing Lots of Devices Experts Guide in the Wrong Device Forum®
Lol®
Sent from my SM-N900P using Xparent BlueTapatalk 2
I'll give him a THANKS for that long A$$ write up! haha..
ImEVO said:
I'll give him a THANKS for that long A$$ write up! haha..
Click to expand...
Click to collapse
I did the same. This was just superb all around. From the thread title, opening premise of the thread/raison d'etre, the avatar, moniker, all the way down to the signature line, quite an enjoyable post from top to bottom.
It had a lot of different colors in the text, too, an attention to detail that I very much appreciated.
Sent from my SM-N900P using Xparent BlueTapatalk 2
micmars said:
I did the same. This was just superb all around. From the thread title, opening premise of the thread/raison d'etre, the avatar, moniker, all the way down to the signature line, quite an enjoyable post from top to bottom.
It had a lot of different colors in the text, too, an attention to detail that I very much appreciated.
Sent from my SM-N900P using Xparent BlueTapatalk 2
Click to expand...
Click to collapse
LMFAO..
Hi all,
Thanks in advance for your help.
I've bricked--like totally bricked--my Nabi 2. On startup, it goes to the Nabi logo, flashes black for a moment and returns to the logo, and is unresponsive. I've tried starting up holding vol+, but nothing happens; no bootloader gets loaded.
How can I restore my device? I have installed nabilabs on my PC, but the Nabi device isn't recognized. I have installed both 32/64 bit drivers. I've also installed pdanet.
Thanks for your responses.
DB
dbbergen said:
Hi all,
Thanks in advance for your help.
I've bricked--like totally bricked--my Nabi 2. On startup, it goes to the Nabi logo, flashes black for a moment and returns to the logo, and is unresponsive. I've tried starting up holding vol+, but nothing happens; no bootloader gets loaded.
How can I restore my device? I have installed nabilabs on my PC, but the Nabi device isn't recognized. I have installed both 32/64 bit drivers. I've also installed pdanet.
Thanks for your responses.
DB
Click to expand...
Click to collapse
I have a similar situation. Major difference is that TWRP (v2.8.4.0) is installed and running, but there's no OS on it otherwise. I have tried various downloads (such as "246stock.zip", and TWRP says there was an error installing on ALL zip files I have tried. It can't be a bad download, since I have re-downloaded the files,. on different machines, and I get the same error each time. NabiLab and NabiLabGUI don't seem to work if there is not already a working OS on the tablet.
Seems like what I need is something like the microSD-based flash/install I used for my Nook Tablet (acclaim) to put CM11 on it. Is there, in fact, a way to outright flash a .IMG file of some sort onto this? Or have I already ruined this already worthless P.o.S.? At this point I'd be just as happy to run something like CyanogenMod on it, and forget the disaster that is the Nabi2 interface and bloatware (then hunt down some other utility for time and access controls).
Images tried, all of which gave me "Error flashing zip"
1937stock.zip
205stock.zip
2127stock.zip
246stock.zip
jelabarre59 said:
I have a similar situation. Major difference is that TWRP (v2.8.4.0) is installed and running, but there's no OS on it otherwise. I have tried various downloads (such as "246stock.zip", and TWRP says there was an error installing on ALL zip files I have tried. It can't be a bad download, since I have re-downloaded the files,. on different machines, and I get the same error each time. NabiLab and NabiLabGUI don't seem to work if there is not already a working OS on the tablet.
Seems like what I need is something like the microSD-based flash/install I used for my Nook Tablet (acclaim) to put CM11 on it. Is there, in fact, a way to outright flash a .IMG file of some sort onto this? Or have I already ruined this already worthless P.o.S.? At this point I'd be just as happy to run something like CyanogenMod on it, and forget the disaster that is the Nabi2 interface and bloatware (then hunt down some other utility for time and access controls).
Images tried, all of which gave me "Error flashing zip"
1937stock.zip
205stock.zip
2127stock.zip
246stock.zip
Click to expand...
Click to collapse
Those zips aren't flashable. You have to extract and restore them.
Do a back up of just the boot partition in TWRP. Just check "boot" and nothing else. Make sure you are backing up to external storage(MicroSD card)
Install 2.4.6 ROM and bootloader.
- Put SD card in computer. Navigate to the folder TWRP/BACKUPS/XXXX. XXX is a serial number unique to your Nabi.
- Make a new folder and call in whatever you want. So it should now look like TWRP/BACKUPS/XXX/yourfolder
- Unzip the 246stock.zip files you downloaded in to the "yourfolder" you created above. The files should look like ext4.system.win, emmc.boot.win, ext.addon.win, etc. This should set you up for the 2.4.6 ROM.
- Download this http://forum.xda-developers.com/showpost.php?p=50349692&postcount=89
- Copy it to the SDcard. This will be for the bootloader update.
- Put sdcard in Nabi
- Boot to TWRP
- Go to restore tab, and find the backup under the "yourfolder" you made and unzipped the files to.
- You should be able to select boot, system, and addon and skip the others.
- If everything restores then go to TWRP install tab, find the bootloader.zip you downloaded and install it.
- Reboot
Alternatively you can "restore" the new kitkat for Nabi. Just replace the instructions for 2.4.6 files above with these below.
3.0.13 stock zip
https://drive.google.com/file/d/0B08qqrSbn4djOFQ1a0cwQjVEV2M/view?usp=sharing
3.0.13 bootloader
https://drive.google.com/file/d/0B08qqrSbn4djcnVTYjI0dTJSQjA/view?usp=sharing
Not sure how bad your situation was but you may have to do a factory reset in TWRP as well. Try that if it doesn't boot after successfully doing the above.
aicjofs said:
Those zips aren't flashable. You have to extract and restore them.
Do a back up of just the boot partition in TWRP. Just check "boot" and nothing else. Make sure you are backing up to external storage(MicroSD card)
Install 2.4.6 ROM and bootloader.
- Put SD card in computer. Navigate to the folder TWRP/BACKUPS/XXXX. XXX is a serial number unique to your Nabi.
- Make a new folder and call in whatever you want. So it should now look like TWRP/BACKUPS/XXX/yourfolder
- Unzip the 246stock.zip files you downloaded in to the "yourfolder" you created above. The files should look like ext4.system.win, emmc.boot.win, ext.addon.win, etc. This should set you up for the 2.4.6 ROM.
- Download this http://forum.xda-developers.com/showpost.php?p=50349692&postcount=89
- Copy it to the SDcard. This will be for the bootloader update.
- Put sdcard in Nabi
- Boot to TWRP
- Go to restore tab, and find the backup under the "yourfolder" you made and unzipped the files to.
- You should be able to select boot, system, and addon and skip the others.
- If everything restores then go to TWRP install tab, find the bootloader.zip you downloaded and install it.
- Reboot
Alternatively you can "restore" the new kitkat for Nabi. Just replace the instructions for 2.4.6 files above with these below.
3.0.13 stock zip
https://drive.google.com/file/d/0B08qqrSbn4djOFQ1a0cwQjVEV2M/view?usp=sharing
3.0.13 bootloader
https://drive.google.com/file/d/0B08qqrSbn4djcnVTYjI0dTJSQjA/view?usp=sharing
Not sure how bad your situation was but you may have to do a factory reset in TWRP as well. Try that if it doesn't boot after successfully doing the above.
Click to expand...
Click to collapse
Just an update, I managed to get a warranty replacement, because it decided it didn't want to charge anymore. Got one of the newer units as a replacement, which has the much better power connector, and am running it as-is for the time being (their updated firmware isn't *as* bad, will have to see what happens with the Mattel ownership).
I am having the same type of issue. I currently have TWRP v2.3.3.0 (Nabi 1.9.3.7) installed, but it shows no OS installed. I attempted to restore to the 30.0.13 stock at got the following message:
E:Unable to wipe '/system'.
and got the Failed on the screen. I also attempted to use the wipe function on the system and got E: Unable to mount for /data, /data, /system, /cache, /data, /addon.
Any help would be greatly appreciated.
biglerad said:
I am having the same type of issue. I currently have TWRP v2.3.3.0 (Nabi 1.9.3.7) installed, but it shows no OS installed. I attempted to restore to the 30.0.13 stock at got the following message:
E:Unable to wipe '/system'.
and got the Failed on the screen. I also attempted to use the wipe function on the system and got E: Unable to mount for /data, /data, /system, /cache, /data, /addon.
Any help would be greatly appreciated.
Click to expand...
Click to collapse
You don't have the right TWRP version probably. That's the ICS version. Try the JB or KK version. http://forum.xda-developers.com/nabi-2/general/nabi-information-t3229119
OK, I had managed to repair the Nabi2s which was bricked before (the trick to "backup" the core files of the specific system, then extract files from 2_0_141107stock.zip), and restore. But for some reason it lost WiFi completely, so I figured I'd try re-flashing again. Now I have no TWRP, and cannot even make the device visible to boot to TWRP. Is it time to take out the sledgehammer, then send the pieces back to the founders at what used to be Fuhu?
I have gone round ans round on the site, tries to find which threads I had followed before, and I seriously think I NEVER want to buy another device where I can't wipe the HDD with a dd command, and boot an installer with a USB or DVD ever again.
jelabarre59 said:
OK, I had managed to repair the Nabi2s which was bricked before (the trick to "backup" the core files of the specific system, then extract files from 2_0_141107stock.zip), and restore. But for some reason it lost WiFi completely, so I figured I'd try re-flashing again. Now I have no TWRP, and cannot even make the device visible to boot to TWRP. Is it time to take out the sledgehammer, then send the pieces back to the founders at what used to be Fuhu?
I have gone round ans round on the site, tries to find which threads I had followed before, and I seriously think I NEVER want to buy another device where I can't wipe the HDD with a dd command, and boot an installer with a USB or DVD ever again.
Click to expand...
Click to collapse
If you can get to the bootloader screen you should be able to bring up fastboot and get TWRP back on tablet(or just boot to TWRP temporarily)
Did that tablet ever receive an update past KitKat?
No Wifi is usually one of two things.
1) Kernel(boot partition) doesn't match kernel modules(system partition). Fix: Restore both boot and system in TWRP.
2) The wifi conf is bad. Fix: Factory reset/wipe data partition Note: loses all personal data.
3) I suppose if there was an update past kitkat, maybe the bootloader or the misc partition got an update. Don't go down that route yet.
Here is the general flow for restoring things, should have everythin you need if you can get fastboot to come up:
https://forum.xda-developers.com/nabi-2/general/nabi-information-t3229119
My original(and only) notes on Nabi2s
https://forum.xda-developers.com/showpost.php?p=58603231&postcount=2504
https://forum.xda-developers.com/showpost.php?p=58623597&postcount=2507
aicjofs said:
If you can get to the bootloader screen you should be able to bring up fastboot and get TWRP back on tablet(or just boot to TWRP temporarily)
Click to expand...
Click to collapse
There's the problem. At this point the tablet only gets as far as the initial Nabi logo. Trying the "<Vol+><power>" option gives me the "Booting Android recovery..." followed shortl by the dead android. That's all the tablet will do.
Is there no way to make a microSD boot? That was what I would do with my Nook Tablet ("acclaim"). Seriously, whomever thought Android should be automatically locked out from the very people who bought/paid for/own the devices should be smacked by each and every Android user out there.
Thanks very much for the info. Took me 2 days to find this.
aicjofs said:
If you can get to the bootloader screen you should be able to bring up fastboot and get TWRP back on tablet(or just boot to TWRP temporarily)
Here is the general flow for restoring things, should have everythin you need if you can get fastboot to come up:
https://forum.xda-developers.com/nabi-2/general/nabi-information-t3229119
My original(and only) notes on Nabi2s
https://forum.xda-developers.com/showpost.php?p=58603231&postcount=2504
https://forum.xda-developers.com/showpost.php?p=58623597&postcount=2507
Click to expand...
Click to collapse
All these instructions presume I can get to a "recovery/bootloader" screen, which this tablet will NOT do. It gets the initial Nabi logo, and that's as far as it will ever go. You could leave it there for 5 hours and that's all it will do (happened to do that once letting it charge, and the Nabi likes to boot as soon as it gets power).
I would try your "nvflash", but it's a MSWin executable, and I'm running Linux.
I'm just wondering; if I had the appropriate image file, is there a way to do a raw dump/write to the USB port, forcing the data to a particular device? If I tail /var/log/syslog, then plug in the Nabi2s, I get these messages in the syslog (and nothing else from the tablet after that):
Code:
kernel: [ 5973.824134] usb 2-1: new high-speed USB device number 4 using ehci-pci
kernel: [ 5973.986609] ehci-pci 0000:00:1d.7: port 1 reset error -110
kernel: [ 5975.192071] usb 2-1: new high-speed USB device number 5 using ehci-pci
kernel: [ 5975.346686] ehci-pci 0000:00:1d.7: port 1 reset error -110
In theory there should be a raw device there somewhere (lsusb doesn't see it)
jelabarre59 said:
All these instructions presume I can get to a "recovery/bootloader" screen, which this tablet will NOT do. It gets the initial Nabi logo, and that's as far as it will ever go. You could leave it there for 5 hours and that's all it will do (happened to do that once letting it charge, and the Nabi likes to boot as soon as it gets power).
I would try your "nvflash", but it's a MSWin executable, and I'm running Linux.
I'm just wondering; if I had the appropriate image file, is there a way to do a raw dump/write to the USB port, forcing the data to a particular device? If I tail /var/log/syslog, then plug in the Nabi2s, I get these messages in the syslog (and nothing else from the tablet after that):
Code:
kernel: [ 5973.824134] usb 2-1: new high-speed USB device number 4 using ehci-pci
kernel: [ 5973.986609] ehci-pci 0000:00:1d.7: port 1 reset error -110
kernel: [ 5975.192071] usb 2-1: new high-speed USB device number 5 using ehci-pci
kernel: [ 5975.346686] ehci-pci 0000:00:1d.7: port 1 reset error -110
In theory there should be a raw device there somewhere (lsusb doesn't see it)
Click to expand...
Click to collapse
Keep in mind I had the Nabi 2S for all of a day, so what I am about to say only applies to the Nabi 2 not 2S. If you see no menu then there is a non functioning bootloader, or at least it doesn't load all the way. It won't front any USB port, and you won't see it with lusb. There is a way to manually start "forced recovery" though(or there was on the Nabi2) See this: https://forum.xda-developers.com/showpost.php?p=46694284&postcount=1701 If you can short the solder joints, I would assume the 2S has them too. That will start the 3pserver on the tegra itself, and bring up a USB interface. I don't think you need the APX driver for linux but you might check. There are plenty of linux nvflash binaries out there. Here is one that should work for tegra3 for sure: http://www.androidroot.mobi/pages/guides/tegra3-guide-nvflash-jellybean/ or search github and compile your own. That would allow what you want, however... I'm not sure where the bootloader partition is. In the notes I linked above I listed a cat /proc/partitions which I will markup below
179 0 15269888 mmcblk0
179 1 8192 mmcblk0p1 <---likely recovery partition but maybe boot
179 2 8192 mmcblk0p2 <---likely boot partition but maybe recovery
179 3 2048 mmcblk0p3 <---if like a Nabi 2 the EKS with crypto key
179 4 2048 mmcblk0p4 <---if like a Nabi 2 the linux backup partition table.
179 5 2097152 mmcblk0p5 <--- preload aka addon partition with all the Nabi apps and media
179 6 1572864 mmcblk0p6 <--- system partition
179 7 2097152 mmcblk0p7 <--- cache partition
179 8 2048 mmcblk0p8 <--- not sure
179 9 32768 mmcblk0p9 <---if like a Nabi 2 the USP or staging partition for placing blob files for flashing
179 10 2048 mmcblk0p10 <---Not sure
179 11 9435136 mmcblk0p11 <--- data partition
179 32 4096 mmcblk0boot1
179 16 4096 mmcblk0boot0
The problem here is the Nabi 2 had a 6MB partition that was clearly the bootloader. A 2MB that was the Nvidia/Tegra partition table(different structure then a linux PT), and a 4MB partition for the device parameters. Those are "nvidia partitions" and don't show up in the linux partition table. For the Nabi 2 the bootloader was nvidia partition 4
I would go about it like this:
Tear open the Nabi and see if it has the pins to force tegra to 3pserver
Get nvflash binary or compile one
Get the bootloader.bin from here(note the name is bootloader2S.bin and the commands below I have bootloader.bin so rename it: https://forum.xda-developers.com/showpost.php?p=58603231&postcount=2504
Force the tablet to 3pserver with the pins
Check to see if it's there with lusb
Use the commands(if you are a linux guy I assume you know you may need sudo, or ./nvflash, etc, etc)
nvflash --bl bootloader.bin --getpartitiontable partitiontable.txt
^^^examine the partitiontable.txt and see if it clarifies where the bootloader might be. They like to call it EBT in tegra. I would tell you how to flash the botloader but I just don't know where it is. The bootloader tries to load the boot.img from the boot partition, and has some sort of watchdog where if it doesn't load boot.img in such and such amount of time, it will try and load recovery.img. If that doesn't happen it just sits there staring at you. You could try and flash boot and recovery and maybe that brings you back to something more familiar. Examine the partition table text and find out which is boot and recovery. Boot is usually LNX, and recovery SOS.
If you are still in nvflash mode after all of this and havent shut down the tablet use commands below. If you have to restart you need have a first command of "nvflash --bl bootloader.bin <some command>" then all subsequent commands just need "nvflash --resume <some command>"
If it's exactly like a Nabi 2 then this would be the flow. So if your partitiontable.txt shows EBT as 4, SOS as 7, and LNX as 8
nvflash --resume --rawdeviceread 0 3072 nabibricksafe.img
nvflash --resume --read 4 04_EBT_raw.img
nvflash --resume --read 7 07_SOS_raw.img
nvflash --resume --read 8 08_LNX_raw.img
<optional>
nvflash --resume --download 4 bootloader.bin
nvflash --resume --download 7 twrp.img
nvflash --resume --download 8 twrp.img
nvflash --resume --go
^^^I have no idea about the 3072. That gets the first 3 "nvidia partitions" on a Nabi2 but that may not be long enough for a 2S, you can make it a larger read to be on the safe side(maybe 6000). You are basically reading the critical part of the tablet, backing up the current partition 4, 7, and 8, before reloading 7,8 with TWRP. Then tablet should restart. Remember if you have to restart the tablet the "resume" won't work, you will need to issue something with -bl bootloader.bin after a fresh boot as the first command of the session. You could add
nvflash --resume --download 4 bootloader.bin
in the above if the partition table confirms its the bootloader partition(EBT). In fact that may actually be the ONLY command you need to bring back the bootloader text, I'm just being cautious since it's not my tablet and taking a conservative approach.
That will put TWRP in both boot and recovery partitions so that hopefully you can boot TWRP somehow. If we can, then we can go back and fix things in TWRP. This may be all you need.
Side note: I never used nvflash on a 2S so who even knows if all this typing means anything, and maybe the emmc is just bad and none of this matters. I'm just try to give you all the major things I can think of to save you time. Good luck!
jelabarre59 said:
Just an update, I managed to get a warranty replacement, because it decided it didn't want to charge anymore. Got one of the newer units as a replacement, which has the much better power connector, and am running it as-is for the time being (their updated firmware isn't *as* bad, will have to see what happens with the Mattel ownership).
Click to expand...
Click to collapse
Thank you very much you saved my day
---------- Post added at 08:10 AM ---------- Previous post was at 08:08 AM ----------
aicjofs said:
Keep in mind I had the Nabi 2S for all of a day, so what I am about to say only applies to the Nabi 2 not 2S. If you see no menu then there is a non functioning bootloader, or at least it doesn't load all the way. It won't front any USB port, and you won't see it with lusb. There is a way to manually start "forced recovery" though(or there was on the Nabi2) See this: https://forum.xda-developers.com/showpost.php?p=46694284&postcount=1701 If you can short the solder joints, I would assume the 2S has them too. That will start the 3pserver on the tegra itself, and bring up a USB interface. I don't think you need the APX driver for linux but you might check. There are plenty of linux nvflash binaries out there. Here is one that should work for tegra3 for sure: http://www.androidroot.mobi/pages/guides/tegra3-guide-nvflash-jellybean/ or search github and compile your own. That would allow what you want, however... I'm not sure where the bootloader partition is. In the notes I linked above I listed a cat /proc/partitions which I will markup below
179 0 15269888 mmcblk0
179 1 8192 mmcblk0p1 <---likely recovery partition but maybe boot
179 2 8192 mmcblk0p2 <---likely boot partition but maybe recovery
179 3 2048 mmcblk0p3 <---if like a Nabi 2 the EKS with crypto key
179 4 2048 mmcblk0p4 <---if like a Nabi 2 the linux backup partition table.
179 5 2097152 mmcblk0p5 <--- preload aka addon partition with all the Nabi apps and media
179 6 1572864 mmcblk0p6 <--- system partition
179 7 2097152 mmcblk0p7 <--- cache partition
179 8 2048 mmcblk0p8 <--- not sure
179 9 32768 mmcblk0p9 <---if like a Nabi 2 the USP or staging partition for placing blob files for flashing
179 10 2048 mmcblk0p10 <---Not sure
179 11 9435136 mmcblk0p11 <--- data partition
179 32 4096 mmcblk0boot1
179 16 4096 mmcblk0boot0
The problem here is the Nabi 2 had a 6MB partition that was clearly the bootloader. A 2MB that was the Nvidia/Tegra partition table(different structure then a linux PT), and a 4MB partition for the device parameters. Those are "nvidia partitions" and don't show up in the linux partition table. For the Nabi 2 the bootloader was nvidia partition 4
I would go about it like this:
Tear open the Nabi and see if it has the pins to force tegra to 3pserver
Get nvflash binary or compile one
Get the bootloader.bin from here(note the name is bootloader2S.bin and the commands below I have bootloader.bin so rename it: https://forum.xda-developers.com/showpost.php?p=58603231&postcount=2504
Force the tablet to 3pserver with the pins
Check to see if it's there with lusb
Use the commands(if you are a linux guy I assume you know you may need sudo, or ./nvflash, etc, etc)
nvflash --bl bootloader.bin --getpartitiontable partitiontable.txt
^^^examine the partitiontable.txt and see if it clarifies where the bootloader might be. They like to call it EBT in tegra. I would tell you how to flash the botloader but I just don't know where it is. The bootloader tries to load the boot.img from the boot partition, and has some sort of watchdog where if it doesn't load boot.img in such and such amount of time, it will try and load recovery.img. If that doesn't happen it just sits there staring at you. You could try and flash boot and recovery and maybe that brings you back to something more familiar. Examine the partition table text and find out which is boot and recovery. Boot is usually LNX, and recovery SOS.
If you are still in nvflash mode after all of this and havent shut down the tablet use commands below. If you have to restart you need have a first command of "nvflash --bl bootloader.bin <some command>" then all subsequent commands just need "nvflash --resume <some command>"
If it's exactly like a Nabi 2 then this would be the flow. So if your partitiontable.txt shows EBT as 4, SOS as 7, and LNX as 8
nvflash --resume --rawdeviceread 0 3072 nabibricksafe.img
nvflash --resume --read 4 04_EBT_raw.img
nvflash --resume --read 7 07_SOS_raw.img
nvflash --resume --read 8 08_LNX_raw.img
<optional>
nvflash --resume --download 4 bootloader.bin
nvflash --resume --download 7 twrp.img
nvflash --resume --download 8 twrp.img
nvflash --resume --go
^^^I have no idea about the 3072. That gets the first 3 "nvidia partitions" on a Nabi2 but that may not be long enough for a 2S, you can make it a larger read to be on the safe side(maybe 6000). You are basically reading the critical part of the tablet, backing up the current partition 4, 7, and 8, before reloading 7,8 with TWRP. Then tablet should restart. Remember if you have to restart the tablet the "resume" won't work, you will need to issue something with -bl bootloader.bin after a fresh boot as the first command of the session. You could add
nvflash --resume --download 4 bootloader.bin
in the above if the partition table confirms its the bootloader partition(EBT). In fact that may actually be the ONLY command you need to bring back the bootloader text, I'm just being cautious since it's not my tablet and taking a conservative approach.
That will put TWRP in both boot and recovery partitions so that hopefully you can boot TWRP somehow. If we can, then we can go back and fix things in TWRP. This may be all you need.
Side note: I never used nvflash on a 2S so who even knows if all this typing means anything, and maybe the emmc is just bad and none of this matters. I'm just try to give you all the major things I can think of to save you time. Good luck!
Click to expand...
Click to collapse
Thank you guys keep up the good work
Hello i have a serious problem with nabi jr tab of my friend's , the model no. is SNBJR-MT5C , my friend was using busybox and adb , when he tried to add .bak file for fuhu in system/apps ,because he wanted to get rid of the password each time device starts, this resulted in a bootloop , because there was no twrp installed , as this device was running kitkat , he tried using a backup from here somewhere in xda but without scatter and files.md5 , so he manually make files.md5 and generated scatter from mtk droid tools from firmware.info , but when he tried flash from sp flash tool , it did not accept that scatter, because pre-loader and mbr has start address 0 , because scatter version was wrong, mtk droid tools generated MT6582_sctter.txt, but it was MT8127 SoC , MT6582 - v111, MT8127 - v112 , so he got v112 from somewhere , and then retried and it got DA(Download Agent) error , so he made a mistake and changed DA and it bricked it completely , now its black screen and it wont turn on , even wont go in fastboot/recovery mode by holding power button and volume + or - buttons , also not showing anything in pc device manager , its totally dead , does anyone had the same experience ? or can anyone guide me about anything? Thanks
aicjofs said:
Keep in mind I had the Nabi 2S for all of a day, so what I am about to say only applies to the Nabi 2 not 2S. If you see no menu then there is a non functioning bootloader, or at least it doesn't load all the way. It won't front any USB port, and you won't see it with lusb. There is a way to manually start "forced recovery" though(or there was on the Nabi2)
Click to expand...
Click to collapse
I managed to get all the pieces of my daughter's Nabi 2S in one place (well, except for the bumper, I had multiples so I must have one still available. But did find the right charger cable). Since she has a different tablet to use for now (I was given 4 XO tablets; one, maybe two actually work) I could send this to a developer who wants to dabble with the hardware. Mind you, it's bricked, so it powers up but can't get to recovery menus, etc. The Nabi 2S doesn't appear to have the solder joints to do a forced recovery, but there is something that looks like it might be a button to do the same thing.
It's April 2018, if there's a developer who wants to try out other experiments on a Nabi2s that's otherwise bricked, you can still contact me. The Nabi is sitting in a box in the closet, it's not doing anything, and my daughter is now using an OLPC OX tablet instead (hey, got 4 of them for free, 2 actually power up).
(yeah, want to re-flash that second one someday as well, just to get it to a clean, stripped-down base to start from).
Hello bro I have a different situation here I have a nabi 2 nv7a I installed twrp on it and deleted the previous ROM to install new one but unfortunately when I try to install any ROM it shows error e\ unable to mount storage then I figured that the solution for it is to change the type of internal storage but the twrp I installed doesn't have any option of changing the type I went to wipe internal storage there was only one option that swipes and when I wipes then it also shows e/unable to mount and there is no option of changing type and I'm unable to change my twrp because I have no is plssss someone help
[GUIDE/TUTORIAL] Asus Transformer Prime to Android 7.1/LineageOS 14.1
[GUIDE/TUTORIAL/HOWTO] Asus Transformer Prime/TF201 stock to Android 7.1 Nougat/LineageOS 14.1
This detailed step-by-step guide helps you transform your Asus Transformer Prime with Android 4.1.1 to a powerful one with Android 7.1 (Nougat).
### I'll make a few comments like this, read these or you may miss something.
### The Asus Transformer Prime codename is TF201.
Try to prefer USB2 connections, but USB3 works fine too.
CHANGELOG
v11. Improvemed unlock section
v10. Updated links
v9. ROM v39 and removed obsolete info
v8. ROM v35 and enhenced link for OpenGapps
v7. Refresh pack for ROM v32 and TWRP recovery 3.2.3-0
v6. Google Play certification
v5. Updated djibe pack for easier install (kang recovery 3.1.0-1, SuperSU, drivers if fails at Step 6) + switched to v26 of Katkiss
v4. TWRP Kang recovery 3.1.0-1
v3. Tweaks and walkthrough
v2. Android 7, many hints added for more accurate tutorial
v1. Initial release
BEFORE STARTING
Make sure you have the latest official updates for your tab :
In Android, go to Settings -> About tablet -> System Update
### Make sure you read all comments starting by ###
To make sure your tab is the correct model, go to Settings -> About tablet.
The details below are listed :
• Android 4.1.1 (JellyBean; Nvidia logo bottom right on boot)
bootloader V 10.4.2.18
### To verify bootloader version, shut down tab. Then hold Power + Volume- for 3 seconds and release.
### You are in bootloader : on top left corner is written Android (...) epad-10.4.2.18.
### To quit bootloader, press Volume- to go over the Android icon, then Volume+ to confirm.
### If not V 10.4.2.18, check official updates for your tab before starting this tutorial
### or check more info on Asus support web page and download the version identical to the Firmware Description written top left corner of the bootloader
### Asus support is here : https://www.asus.com/Tablets/Eee_Pad_Transformer_Prime_TF201/HelpDesk_BIOS/
• GPS 7.9.13
• Wi-Fi 7.1.0.24
• BT 10.33
• Camera FT201-0x9900
• Ecran MXT-2.0 build-170
• Kernel 3.1.10.00002-9599d0cf [email protected]
o #1 SMP PREEMPT Thui Nov 22:12:01 CST 2012
• Build nr JR003C.WW_epad-10.4.2.18-20121122
Still in Settings -> About tablet, tap 7 times on build number to unlock Developer menu.
0) BACKUP YOUR DATA
Backup SMS, photos, contacts before going any further (ex: use the backupyourmobile app).
Check that backup is located on microSD card.
Then copy the backup on your PC.
1) DOWNLOAD
djibe Transformer Prime pack v2: http://bit.ly/djibeTransformerPrimev2
(contains Windows Universal Naked drivers + android_winusb if step 6 is difficult + Asus UnLock_Device_App_V6.apk + fastboot.exe + adb.exe + nvflash.exe + HairyBean Bootloader and various recoveries necessary + SuperSU 2.82).
Unzip the file on Windows desktop.
+ ROM KatKiss Nougat v39 Android 7.1
XDA Thread: https://forum.xda-developers.com/transformer-tf700/development/rom-t3457417
Download here: https://downloads.timduru.org/android/tf201/K.A.T/KatKiss/7.x/dev/ or https://www.androidfilehost.com/?fid=14943124697586357425
+ OpenGapps ARM 7.1 ARM Pico (NO OTHER DISTRIB THAT ARM PICO please): https://opengapps.org/?arch=arm&api=7.1&variant=pico
You must have a microSD card (FAT32 format), copy the zip files from Katkiss ROM, OpenGapps and SuperSU.
Then insert it in the tab.
2) INSTALL WINDOWS DRIVERS FOR ASUS TRANSFORMER PRIME TF201
- Windows 8/10 :
On keyboard, type combo : "Windows key + R"
In the command prompt, type :
Code:
shutdown -o -r -t 0
It opens Windows Recovery menu:
Go to Troubleshoot -> Advanced Options -> Startup settings -> Restart.
At reboot, hit 7 (Disable driver control) and follow instructions for Windows Vista/7.
Once driver installation is completed, reboot PC as usual.
- Windows Vista/Windows 7 :
Go to folder /Universal Naked Drivers 0.72 you unziped earlier (on Windows desktop).
Select file android_apxusb.inf, then right click -> Install.
Force driver installation and wait until a success message prompts.
Repeat operation with android_winusb.inf .
Then plug tablet to PC (USB2 port) to end driver installation.
### If it fails to install you may try using Windows device manager :
### In Windows Device Manager menu -> Right-click on Asus Android Device -> Update Driver Software -> Let me pick -> Have disk -> Browse to the .inf file and install BOTH .inf files.
### See this post if still doesn't work : https://forum.xda-developers.com/showpost.php?p=75240547&postcount=166
- For Linux, I have no experience. Every tools should be here : https://github.com/AndroidRoot/androidroot.github.io/tree/master/download
- Copy the UnLock_Device_App in tablet's internal memory
Tab should normaly be seen in Windows explorer as TF201.
Check MTP file transfer protocol is active on the tab.
Copy the UnLock_Device_App_V6.apk in the root folder of the tab.
3) UNLOCK BOOTLOADER OF ASUS TF201
Tablet must be fully charged to 100 %.
In Android, go to Settings -> Security -> Check Unknown Sources.
Then Settings -> Developer options -> Enable USB debugging.
Launch the preinstalled app File Manager to install UnLock_Device_App_V6.apk.
### If it fails to install, delete your Google Account. Go to Settings -> Accounts. Delete the Google Account.
Launch the UnlockApp.
Accept User agreements. Your warranty is now void.
Accept and click to unlock the tab,
let the tab restart and work.
After reboot , "This device is unlocked" is written on top left screen.
### It probably won't work that simple.
### The solution is here, but I didn't have to test it: https://forum.xda-developers.com/t/howto-unlock-tf700t-in-2020.4157143/post-85255809
4) PREVENT BRICK : NVFlash
This step is optionnal but highly higly highly recommended, your tab will never be bricked after it !!!
1ST PART --------------------
Tab shut down, press Power + Volume- for 3 seconds and release, you are in the bootloader.
Use Volume- to move cursor over the USB logo, confirm with Volume+, you are in the fastboot mode.
Connect Transformer Prime to PC.
Select the "Files" folder you you unziped earlier.
Do Shift + right click on folder -> Open a Command Line.
Type:
Code:
fastboot -i 0x0b05 flash recovery flatline_tf201.img
and confirm with Enter.
### If you get error "fastboot : The term 'fastboot' is not recognized as the name of a cmdlet, function, script file, or operable program",
### type the command starting with a dot :
Code:
.\fastboot -i 0x0b05 flash recovery flatline_tf201.img
A blue bar appears on the tablet indicating flash success.
Wait until command line reports the flashing success.
then type :
Code:
fastboot reboot-bootloader
and confirm with Enter.
This time in Bootloader, use Volume- to select RCK (recovery) and confirm with Volume+.
You are in the flatline recovery.
Use Volume- to go to Advances, confirm with Power.
then wheelie, confirm (Power button),
then i accept the above statement (Power button),
then Step 1: flash AndroidRoot BL, tab powers down.
Start tab with Power only,
let the blue bar fill completly and start Android normally.
Once in Android, shut it down.
Start tab in bootloader Mode again (still Power + Volume- ;-) ), go to recovery again (RCK).
Connect tab to PC.
In recovery, return to Advanced -> wheelie then select Step 2: generate wheelie blobs.
It generates the backup files !!!
Open another Windows command prompt for fastboot mode and type :
Code:
adb pull /data/media/AndroidRoot
.
Backup files are stored in your "Files" folder. Make another backup of these files in a safe place.
(7 files are saved : recovery.bct, create.bct, bootloader.ebt, blob.log, blob.bin, pt_restore.log and pt_patch.log)
### If
Code:
adb pull /data/media/AndroidRoot
doesn't work : start Android normally, connect to PC as multimedia storage and
### navigate to My Computer -> Transformer Prime TF201 -> Internal Memory -> Android Root and copy the files in here.
Shut down tab.
2ND PART, NvFlash ----------------
Copy these 7 files in the folder "files/nvflash" (Another copy, in addition to the backup you made).
Connect tab to PC.
Start tab in Nvidia APX Mode : Hold Power + Volume+ for 3 seconds.
Anything happens, it's normal, screen stays black.
The tab is visible as an external drive and is called APX.
Open another Windows command prompt on the nvflash folder.
Type :
Code:
wheelie --blob blob.bin
and confirm with Enter.
If successful : the tab launches in bootloader mode and the Command prompt writes a few lines.
Type in command :
Code:
nvflash --resume --rawdeviceread 0 2944 bricksafe.img
then :
Code:
nvflash --resume --read 14 factory-config.img
then :
Code:
nvflash --resume --read 7 unlock-token.img
You have to backup 3 new files : bricksafe.img, factory-config.img and unlock-token.img.
Copy these files in a safe storage with your blobs for future repair if needed.
### If you need to restore those backups one day, follow the tutorial of craigacgomez : https://forum.xda-developers.com/showthread.php?t=1927818
### If you have error "not enough space for GApps (error 70), follow this tutorial https://forum.xda-developers.com/showpost.php?p=73403429&postcount=137
5) RECOVERY
(Only applies to stock bootloader V 10.4.2.18).
Charge tab to 100% before continuing.
Start it in bootloader mode (Power + Volume-).
Connect it to PC.
Set the icon over the USB selection.
Confirm with Volume+; you are again in fastboot mode.
Open a command prompt on the /files folder.
Type :
Code:
fastboot devices
.
if the serial number is written, tab is well connected.
### Or check driver installation if not.
then type :
Code:
fastboot -i 0x0b05 flash recovery twrp_tf201t.blob
and wait for the "finished" success message,
then type :
Code:
fastboot -i 0x0b05 reboot-bootloader
,
and confirm with Volume+ to get into RCK (recovery, again), it is now TWRP 2.6.3.0.
6) BOOTLOADER
Once in TWRP recovery, type in command prompt :
Code:
adb devices
-> terminal returns : 012345678ABCDEF recovery.
Type :
Code:
adb push HairyBean_Bootloader_TWRP2.5.zip /sdcard
Now on the tab, still in TWRP recovery, go to Install then click on HairyBean_Bootloader_TWRP2.5.zip
(file is in Internal memory, in folder /sdcard).
Swype to the right to confirm flashing, wait until Successful message appears.
Now click Reboot System and Do Not Install when SuperSU is proposed.
Let the tab reboot with another blue bar. Let it work.
The tab reboots and launches the HairyBean TWRP recovery (androwook).
In Windows command prompt, type :
Code:
adb reboot-bootloader
,
tab reboots in bootloader mode and the USB icon is gone, it's perfect.
### If Windows doesn't recognize your tab, or recognizes it as VID_0B05&PID_4C83, try the fix from XTCrefugee included in my pack : folder \Drivers android_winusb if hairybeen TWRP not recognized
### Install this .inf driver file as you did earlier
###
### YOUR BOOTLOADER IS NOW IN 10.6.1.27.1 VERSION
###
In command prompt, type :
Code:
fastboot -i 0x0b05 flash recovery twrp-3.2.3-0_KANG-tf201t.img
Wait till blue bar completes.
When finished message appears in terminal,
type :
Code:
fastboot -i 0x0b05 reboot-bootloader
, tab reboots.
Now enter in new recovery with Volume+ : recovery is now TWRP Kang 3.2.3-0 Recovery
### Your tablet will be seen by Windows as a TF201T now !
7) SET FILESYSTEM TO F2FS
F2FS is the fastest filesystem for read and write partitions on flash memories. Compared to EXT4, gain is from 15 to 280 %.
No need to format the /System partition because it is Read only and Ext4 is still faster.
Go to Wipe -> Advanced Wipe, select only the Data partition,
then tap on Repair or Change File System -> Change File System and tap on F2FS.
Swype to force partition system as F2FS. Wait till done prompts. Then go back to Advanced Wipe.
### If TWRP sends you this log in red : E:Failed to get default contexts and file node for storage files,
### Reboot to TWRP recovery again before going any further.
Repeat the operation of F2FS conversion for the Cache partition.
8) INSTALL ANDROID NOUGAT 7.1
Still on TWRP Advanced Wipe menu,
select Dalvik Cache, System, Cache, Data AND Internal Storage and Swype to force cleanup. Wait till completion.
Back to Home screen, tap Install, then Storage: Internal Storage and change it to microSD card -> OK.
Select KatKiss* .zip, and Add More Zips,
select SuperSU.zip, and Add More Zips,
then open_gapps-arm-7.1-pico*.zip and Swype to force install. Be patient.
### Make sure once again you have the Pico Gapps version or system will hang.
### If TWRP crashes to its Home screen, you microSD might be in cause. Find another one, and then try to install Zips 1 by 1.
### If error installing Gapps, see this thread : https://forum.xda-developers.com/android/help/fix-error-70-install-gapps-t3311779
When done prompts, tap on Wipe Cache/Dalvik and swype to confirm, wait.
Go back to Home when done.
Then Reboot -> System.
Let the tab start during at least 15 minutes.
9) START ANDROID N 7.1
### During first setup, manually toggle Wifi ON using the Wifi icon on the bottom right corner. If you don't, the setup app will crash.
### It can crash a few times before turning on, keep activating it.
Configure Android as you like.
In Settings -> Mediascanner filters, uncheck Scan.
In Settings -> About, tap 7 times on build number, it unlocks the Options for developers in Settings.
Enter this new menu.
In the Hardware acceleration, try both GPU rendering active and disabled.
I can't figure which one works best. Share with us.
Good to know about this ROM:
Bluetooth requires to be turned on twice before it turns on.
A few things including the navbar buttons can be tweaked in Settings => System UI Tuner.
AND more on XDA Katkiss thread (See DOWNLOAD CHAPTER ABOVE)
10) ROOT
Open app SuperSU to see more details about the Root access.
After ROM first launch, go to Settings -> About tablet.
Tap 7 times on build number, it will unlock the Developer menu.
In the developer menu -> Try to turn ON and OFF the Force GPU option and tell me what is the faster one.
(I think I prefer when GPU forcing is disabled).
11) PERFORMANCES AND OVERCLOCK
Source of benchmarks: http://androidmodguide.blogspot.fr/p/blog-page.html
Install Kernel Adiutor app from Google Play Store.
Launch app and go to Settings -> Kernel -> CPU :
Check Apply on boot and change CPU Maximum Frequency to 1600 or 1700 Mhz, set Governor to Interactive
Now Kernel -> I/O Scheduler :
Check Apply on boot and set Scheduler to Zen, then Readahead to 1024 Ko (or 2048. Try yourself)
Now Kernel -> Various :
Check Apply on boot and set TCP congestion to Cubic (or Westwood)
12) VARIOUS FIXES
### Your tablet doesn't see the Wifi ? (that is on Channel 13 by example).
Try this first : in the Wifi screen (where you see all visible networks), tap on the three-dots icon to open the menu -> Advanced wifi parameters.
Tap on the Wifi region code item to select the region : chose the corresponding region.
Now verify your Wifi network is visible.
If not, try this :
Open Kernel adiutor, Menu -> Build.prop editor.
In key search field, type wifi.
Click ro.wifi.channels -> Edit -> in the value field, set 13. Confirm with OK.
At the same time, you can set wifi.supplicant_scan_interval=180 to 180 (seconds) to reduce number of scans and reduce battery usage.
Restart tab, your wifi network should be visible again.
### Your keyboard isn't in the correct language
Go to Android Settings menu -> Languages & inputs -> Physical keyboard -> Android keyboard
Enjoy your new tab ;-)
djibe
Thanks : @timduru, matthill.eu, Kang for updated TWRP, TWRP team, Android Root Team, Lineage OS team, TacoNikky, Saber
Thanks for the step-by-step. I've worked my way to nougat and the path there is kind of forgotten after a while. Different bootloader, different file systems, sort of lose track of things.
Sent from my XT1575 using Tapatalk
HorthLithperer said:
Thanks for the step-by-step. I've worked my way to nougat and the path there is kind of forgotten after a while. Different bootloader, different file systems, sort of lose track of things.
Sent from my XT1575 using Tapatalk
Click to expand...
Click to collapse
Thanks for your support. It was a tough job to explain step by step.
Took me 3 days to discover all the details.
thanks
really great work.
i want to add a comment : When trying to unlock bootloader, it kept on asking pw for google account (and double authentification disabled). I deleted google account from prime and it went through.
yo29570 said:
really great work.
i want to add a comment : When trying to unlock bootloader, it kept on asking pw for google account (and double authentification disabled). I deleted google account from prime and it went through.
Click to expand...
Click to collapse
Thx for feedback.
I had the same problem and used the tab factory reset.
I've updated tutorial and told to delete the Google Account.
I just wanted to thank you for making these instructions. Ive never delt with any android device with this many steps. Compared to a nexus 6p this is nuts. Ive messed around with Motorola and Samsung phones but this tablet is a whole other league. You made it very simple to turn my daughters slow old tablet into a relevant one. I still cant believe there was that much to it. Its only 10 steps...lol
Woodrow256 said:
I just wanted to thank you for making these instructions. Ive never delt with any android device with this many steps. Compared to a nexus 6p this is nuts. Ive messed around with Motorola and Samsung phones but this tablet is a whole other league. You made it very simple to turn my daughters slow old tablet into a relevant one. I still cant believe there was that much to it. Its only 10 steps...lol
Click to expand...
Click to collapse
Glad you liked it and tab is healthy again !
I've made tuts for Xperia Tablet Z and Samsung devices too if you are interested
Problem with step 8 - INSTALL Android 6 ROM
Hello djibe89,
First of all, I would like to thank you very much for this well documented step-by-step guide for upgrading the TF201! It was no problem for me, a novice in this, to follow.
However i do have encountered a problem with booting after the installation of step 8. And i hope you are able to help me with this. When i try to boot the device after Successful installing KatKiss-6.0_TF201_029.zip, open_gapps-arm-6.0-pico-20160320.zip, and Beta-superSU-v2.52.zip, the device seems to be in a boot-loop. The OS never starts up.
I also tried the older KatKiss-6.0_TF201_028.zip with the two other zip files, but the result is the same.
Until step 8, all installations went without major problems. (i made a document from your instructions and documented every step i did, (including serial number received from fastboot etc). So my TF201 is now Unlocked and the bootloader TWRP is at version 2.8.3.0.
There is only one thing i received at step 7, wich i think i should mention. When i do Wipe -> Format Data, i receive the following message when it's Done:
Updating partition details ...
... done
Full SELinux Support is present.
(in red) E: Failed to get default contexts and file node for storage files.
MTP Enabled
Formatting Data using make_extfs function
You may need to reboot recovery to be able to use /data again.
Updating partition details ...
... done
I did not pay attention to this message, because there was also the Successful message.
But perhaps it does have something to do with my problem of not being able to boot into KatKiss.
Hope you are able to help me with this.
(Maybe i will try to install Nougat for the TF201, since the recovery with TWRP is OK.)
Kind regards, Bert
deltabert said:
Hello djibe89,
First of all, I would like to thank you very much for this well documented step-by-step guide for upgrading the TF201! It was no problem for me, a novice in this, to follow.
However i do have encountered a problem with booting after the installation of step 8. And i hope you are able to help me with this. When i try to boot the device after Successful installing KatKiss-6.0_TF201_029.zip, open_gapps-arm-6.0-pico-20160320.zip, and Beta-superSU-v2.52.zip, the device seems to be in a boot-loop. The OS never starts up.
I also tried the older KatKiss-6.0_TF201_028.zip with the two other zip files, but the result is the same.
Until step 8, all installations went without major problems. (i made a document from your instructions and documented every step i did, (including serial number received from fastboot etc). So my TF201 is now Unlocked and the bootloader TWRP is at version 2.8.3.0.
There is only one thing i received at step 7, wich i think i should mention. When i do Wipe -> Format Data, i receive the following message when it's Done:
Updating partition details ...
... done
Full SELinux Support is present.
(in red) E: Failed to get default contexts and file node for storage files.
MTP Enabled
Formatting Data using make_extfs function
You may need to reboot recovery to be able to use /data again.
Updating partition details ...
... done
I did not pay attention to this message, because there was also the Successful message.
But perhaps it does have something to do with my problem of not being able to boot into KatKiss.
Hope you are able to help me with this.
(Maybe i will try to install Nougat for the TF201, since the recovery with TWRP is OK.)
Kind regards, Bert
Click to expand...
Click to collapse
Hi, I'm glad you liked it.
Seems like you chose wrong Filesystem format " Formatting Data using make_extfs function".
We need a F2FS partition.
Go back to your TWRP 2.8 recovery,
wipe all partitions,
chose /data partition and change filesystem to F2FS.
Make sure /Cache partition is F2FS too.
Then you can Install the zips.
Keep in touch.
Merry christmas from France
djibe89 said:
Hi, I'm glad you liked it.
Seems like you chose wrong Filesystem format " Formatting Data using make_extfs function".
We need a F2FS partition.
Go back to your TWRP 2.8 recovery,
wipe all partitions,
chose /data partition and change filesystem to F2FS.
Make sure /Cache partition is F2FS too.
Then you can Install the zips.
Keep in touch.
Merry christmas from France
Click to expand...
Click to collapse
Hello djibe89,
Thank you for answering my question.
But before receiving your answer I was already trying to do the steps again (from step 4), which was (looking back) obviously a bad idea. I am afraid I made a mess of it right now. First of all i should have read the error msg carefully to see the file system type. I was aware that this KatKiss is using f2fs?
I already send you a pm describing what i had done, and that i had to stop experimenting until after Christmas
Today (27 dec.) i tried an other attempt to revive my tab, and started by: 2ND PART, NvFlash---
Got the tab in APX mode again (Windows Device Manager shows Asus T. P. APX..)
So i went on with 5 - RECOVERY
I do get the fastboot screen; with the menu's RCK - Android - USB - Wipe Date, and went to USB.
Giving the command fastboot devices gives the serial number, so its connected.
Then i gave fastboot -i 0x0b05 flash recovery twrp_tf201t.blob which gave sending 'recovery' <7934 KB>...
OKAY [2.213s]
writing 'recovery'...
OKAY [ 3.534s]
finished. total time: 5.747sthen a reboot bootloader with: fastboot -i 0x0b05 reboot-bootloader
After this i had the TWEAMWIN screen again.
with adb devices i get the 012345678ABCDEF recovery message. So, adb can connect.
But re-installing HairyBean_Bootloader with adb push HairyBean_Bootloader_TWRP2.5.zip /sdcardgives an error on the tab.
Then i realized that i have just re-installed TWRP 2.6, which is intended for JB bootloader! So i booted the tab to fastboot and installed the TWRP 2.8 with:
fastboot -i 0x0b05 flash recovery twrp.blob That went OK.
Now i tried to install KatKitt6 again, now with all partitions formatted as f2fs.
But i stil don't get Katkitt6 booting. It keeps rebooting.
===============================================================
Today, 28 dec. i did an other attempt and made photo's from the screen of the tab.
From within TRWP 2.8.3.0, I started at Step 7 – SET FILESYSTEM TO F2FS
Wipe :: Format Data, uses ext4 filesystem (as described in the tutorial) and takes indeed a long time.
Next Wipe :: Advanced Wipe ONLY the data folder, and set to F2FS
Also with the Cache partition also set to F2FS
Step 8 – Install Android 6 ROM. From TWRP Wipe :: Advanced Wipe. Select Dalvik Cache, System, Cache and Internal Storage. Swipe to cleanup. NO mention of changing the filesystem to F2FS so I left these as they are!
Installation of the tree .ZIP files, see pictures below:
Unfortunately, i am only able to put links to photo's when i have at least posted 10 posts. Since i am new here i try an other way of linking to the photos:
Step 7 and 8 - Photo 1 https: // deltabert.stackstorage.com/s/gszDWyVd9sqHiQs
Step 7 and 8 - photo 2 https: // deltabert.stackstorage.com/s/Ju0tmwMIUjJXHg4
Step 7 and 8 - photo 3 https: // deltabert.stackstorage.com/s/o0tTQ3tPBHF85Wu
Step 7 and 8 - photo 4 https: // deltabert.stackstorage.com/s/Cls41PHHcCa0TKr
And when I press Reboot, after Wiping Dalvik Cache, the tab keeps rebooting! This time I see no error messages.
And believe me, I left it booting for hours…
Any idea as what I could do next?
deltabert said:
Hello djibe89,
Thank you for answering my question.
But before receiving your answer I was already trying to do the steps again (from step 4), which was (looking back) obviously a bad idea. I am afraid I made a mess of it right now. First of all i should have read the error msg carefully to see the file system type. I was aware that this KatKiss is using f2fs?
I already send you a pm describing what i had done, and that i had to stop experimenting until after Christmas
Today i tried an other attempt to revive my tab, and started by: 2ND PART, NvFlash---
But unfortunately i am not able to get the tab in APX mode again.
Then i skipped this en went on with 5 - RECOVERY
I do get the fastboot screen; with the menu's RCK - Android - USB - Wipe Date, and went to USB.
Giving the command fastboot devices gives the serial number, so its connected.
Then i gave fastboot -i 0x0b05 flash recovery twrp_tf201t.blob which gave sending 'recovery' <7934 KB>...
OKAY [2.213s]
writing 'recovery'...
OKAY [ 3.534s]
finished. total time: 5.747sthen a reboot bootloader with: fastboot -i 0x0b05 reboot-bootloader
After this i had the TWEAMWIN screen again.
with adb devices i get the 012345678ABCDEF recovery message. So, adb can connect.
But re-installing HairyBean_Bootloader with adb push HairyBean_Bootloader_TWRP2.5.zip /sdcardgives an error on the tab.
Then i realized that i have just re-installed TWRP 2.6, which is intended for JB bootloader! So i booted the tab to fastboot and installed the TWRP 2.8 with:
fastboot -i 0x0b05 flash recovery twrp.blob That went OK.
Now i tried to install KatKitt6 again, now with all partitions formatted as f2fs.
But i stil don't get Katkitt6 booting. It keeps rebooting.
Besides this, I am still worried that NvFlash might be no longer on the tab...
And i don't get the FlatLine booting with volume-up and power anymore...
===============================================================
Today, 28 dec. i did an other attempt and made photo's from the screen of the tab.
From within TRWP 2.8.3.0, I started at Step 7 – SET FILESYSTEM TO F2FS
Wipe :: Format Data, uses ext4 filesystem (as described in the tutorial) and takes indeed a long time.
Next Wipe :: Advanced Wipe ONLY the data folder, and set to F2FS
Also with the Cache partition also set to F2FS
Step 8 – Install Android 6 ROM. From TWRP Wipe :: Advanced Wipe. Select Dalvik Cache, System, Cache and Internal Storage. Swipe to cleanup. NO mention of changing the filesystem to F2FS so I left these as they are!
Installation of the tree .ZIP files, see pictures below:
Unfortunately, i am only able to put links to photo's when i have at least posted 10 posts. Since i am new here i try an other way of linking to the photos:
Step 7 and 8 - Photo 1 https: // deltabert.stackstorage.com/s/gszDWyVd9sqHiQs
Step 7 and 8 - photo 2 https: // deltabert.stackstorage.com/s/Ju0tmwMIUjJXHg4
Step 7 and 8 - photo 3 https: // deltabert.stackstorage.com/s/o0tTQ3tPBHF85Wu
Step 7 and 8 - photo 4 https: // deltabert.stackstorage.com/s/Cls41PHHcCa0TKr
And when I press Reboot, after Wiping Dalvik Cache, the tab keeps rebooting! This time I see no error messages.
And believe me, I left it booting for hours…
Any idea as what I could do next?
Click to expand...
Click to collapse
did you ever get through this part?
im on the same boat.....finished everything successfully but once i install the ROM it keeps rebooting and stays on the TWRP until i reboot again
ALDO_MAC12 said:
did you ever get through this part?
im on the same boat.....finished everything successfully but once i install the ROM it keeps rebooting and stays on the TWRP until i reboot again
Click to expand...
Click to collapse
Hi ALDO-MAC12,
Unfortunately, i have not yet got my TF201 working. I'l wait now until djibe89 has time to react.
(When i opened his zip file i noticed he has also a France language description, and he is at the moment in France, So i guess he is a French-Canadian, on vacation in France.)
I did study the original posts from timduru and TacoNikky, but i can find no differences with the description of djibe89. Noticed there is also a Android 7 rom from timduru. But i think i should first get to manage the hole process.
For me all this is new. My tab became so horribly slow that i only sparsely used it anymore. So that's why i would like to give it a try.
BTW, i do get the tab in APX mode; with volume up and power, i get a black screen but in Windows Device Manager there shows up the Asus Transformer Prime APX ... driver.
If you're running Windows 10, you need to delete all your other android drivers, then disable the signature checking on your driver installation and install the Naked Universal driver.
Super SU wants update
Works for me on windows 10. Make sure tablet is plugged in directly and not into keyboard also. Although Super SU is now reporting an update in necessary. Is it recommended in update Super SU after installation? Btw thanks for bringing new life to my tablet!
Have you tried not to change /cache partition to f2s2. The original KatshMallow thread says:
This ROM is for TF201 and F2FS only
Convert just /data partition to F2FS
Click to expand...
Click to collapse
...
Hello all,
Thank you for thinking with me, I appreciate this very much! I will react to the suggestions given.
@lazuhrus, I think the Universal Naked Drivers 0.72 are correctly installed on my Win-10 PC. I followed the procedure for Win-10 to disable driver control. To confirm this: I am able to use fastboot from Win-10; fastboot devices gives me the serial number of the tf201.
Also the command adb devices gives me: 012345678ABCDEF recovery.
Further, when I bring the tf201 (with volume UP and power) in APX mode, I get a dark screen on the tab, but in Windows Device Manager there shows up the Android device: Asus Transformer Prime APX Interface.
So for me this seems OK. This lets me conclude that the Universal Naked Drivers 0.72 are correctly installed and working. Or am I overlooking something here?
Btw, I do this on the bare tablet, without the keyboard dock.
With volume DOWN and power, I get the tab in TWRP version 2.8.3.0.
And installing KatKiss seems to go well (see the screenshots I posted in #10 from the TWRP format and install process).
@ shaDNfro, I did change the /cache partition to f2fs, as the screenshots are showing too.
However, there is one strange thing. After the last install (post #10) when I am in TWRP and connect the tab to my PC (win10) I see in the File Explorer an entry for an ASUS Transformer Pad TF300T; while mine is an TF201!!
Picture File Explorer: https: // deltabert.stackstorage.com/s/Nj1C01jTyZ5MoWB
And in the Device Manager I see also references to the wrong tab type!
(But you can see the Asus Android Composite ADB Interface.
Picture Win10 Device Manager: https: // deltabert.stackstorage.com/s/zK2LIoAthr4jKJ7
(added spaces around // because i am as novice not (yet) able to post links)
Hopefully anyone can help me with this...
Hi guys,
I am French from France indeed
- Maybe try to reformat the /cache partition in EXT4 (instead of F2FS).
Then wipe all partitions and install all zips again.
- It is normal that your tab is seen as TF300 as the TWRP 2.8.3.0 is originaly openrecovery-twrp-2.8.3.0-tf300t.blob.
I no longer have my tab so it's tricky to help you. I'll try anyway
djibe89 said:
Hi guys,
I am French from France indeed
- Maybe try to reformat the /cache partition in EXT4 (instead of F2FS).
Then wipe all partitions and install all zips again.
- It is normal that your tab is seen as TF300 as the TWRP 2.8.3.0 is originaly openrecovery-twrp-2.8.3.0-tf300t.blob.
I no longer have my tab so it's tricky to help you. I'll try anyway
Click to expand...
Click to collapse
Thank you djibe89,
I really hope you can help me with this, I become a little desperate...
I wonder if there is something wrong with the bootloader (HairyBean_Bootloader_TWRP2.5.zip). When I boot the tab with vol-down and power I get the following bootloader info: Android cardhu-user bootloader <1.00 e> released by “WW_epad-10.4.2.15-20120917†A03
Do you know if this is correct?
OK, I put the tab in TWRP 2.8.3.0 mode.
Formatted the /Cache partition using make_ext4fs
Then I wiped Dalvik Cache, followed by /System, which formats to ext4fs.
Then format /Data, first with make_ext4fs, and when finished, I change the filesystem of /Data to f2fs. Wiped all other partitions, except Micro SDcard (not sure if this is the internal or external SDcard)
Then I installed the three .zip files. KatKiss-6.0_TF201_029.zip, open_gapps-arm-6.0-pico-20160320.zip and BETA-SuperSU-v2.52.zip.
I also put the MD5 checksum file of KatKiss-6.0_TF201_029.zip on the sdcard and the install procedure checks the .zip successful.
When install is done: Successful, I wiped Dalvik Cache and rebooted the tab.
But then I have the same reboot problem: First i see a blue bar for one second, then the tab boots with the ASUS splash screen at medium intensity, then switches for a moment to high intensity and back to medium intensity, and after a few seconds it reboots and it starts over again.
When I leave the tab booting for two hours, I can feel it is doing something; the backside is becoming slightly warm; processor: ~ 45°C.
The bootloader is part of HairyBeen isn't it? Could I re-install the correct HairyBean_Bootloader_TWRP2.5.zip again, by putting it on the external sdcard and selecting it from TWRP 2.8.3.0?
fastboot, adb and Nvidia APX Mode are still functioning, so there must be a solution...
Hopefully you have a good suggestion?
Kind regards, Bert
Yo Bert,
you must be in distress.
Maybe it's time to look for a NVIDIA APX restoration.
I hope you still have your backup files.
I don't know anything about it,
so read all Google carefully to proceed.
That's why I motivated you to backup APX in my tutorial, since we never what can happen with Android hardware.
Keep in touch
djibe89 said:
Yo Bert,
you must be in distress.
Maybe it's time to look for a NVIDIA APX restoration.
I hope you still have your backup files.
I don't know anything about it,
so read all Google carefully to proceed.
That's why I motivated you to backup APX in my tutorial, since we never what can happen with Android hardware.
Keep in touch
Click to expand...
Click to collapse
Hi djibe89,
I will look into the restoration option. I do have the APX backup files.
Will be continued....
Hey All
I'm new to Android but not linux.
Bought cheap Allwinner type 5.1.1 tablet - 10.6" Fusion5 108 Octa Core Android Tablet PC
rooted it using KingRoot, messed around with Supersume to remove KingRoot and now device won't boot properly. Using adb I can see dmesg is complaining about debuggered which is actually now a zero byte file. su won't work now and I don't have the rights to fix it.
Before I did any of this the first thing I did as root was backup the mmc partitions to a USB stick.
The bootloader and recovery areas have not been changed.
Can I use my system partition backup to create a update.zip for use in recovery mode?
Or maybe in fastboot though I'm currently having problems getting fastboot to see my tablet whether I use linux or windows so recovery mode fix prefered..
lol
Looks like the solution is to post here, and then find a partial answer 5 minutes later.
fastboot command on linux didn't work (despite adb working, udev configured etc)
Then tried with manufacturer id
fastboot -i 0x1f3a
then works
Then did
fastboot -i 0x1f3a erase system
fastboot -i 0x1f3a flash system /home/user/android/13-11-16/system
It complained that about magic so I suspect this DIDN'T work. although data was sent.
fastboot -i 0x1f3a reboot
and device came up in a graphical environment asking for wireless password. Judging by network trace on my router I think it might be trying to download a factory image over the Internet. Will see.
Bit confused as my system parition backup is like 900Mb but when I did flash system I think it said device reported size was 32MB approx. More to learn
OK
The 32Mb was referring to buffer size, so can confirm system flash did work.
Device was booting, getting to graphical environment, and then trying to connect some web servers - not sure why really but seem to have got past that point.
Now can't install apps - get stuff like
W/art ( 9462): Unable to open /data/dalvik-cache/. to delete it's contents: Permission denied
W/art ( 9462): Unable to open /data/dalvik-cache/arm to delete it's contents: Permission denied
W/art ( 9462): Could not create image space with image file '/system/framework/boot.art'. Attempting to fall back to imageless running. Error was: Unable to relocate image '/system/framework/boot.art' from '/system/framework/arm/boot.art' to '/data/dalvik-cache/arm/[email protected]@boot.art': Only the zygote can create the global boot image.
Think /data is corrupt so will flash my backup of that.
I'm more thinking outloud at this point rather than expecting people to do it for me But I'll post anyway if that's ok if only for my own reference - though any insights by all means.
Can't flash data backup.
Ended up with 13Gb file from mmc copy when system was working so after img2img didn't seem to be working used ext2simg on it as it was a ext image.
Created a more reasonable sparse 887335016 file.
fastboot wouldn't flash it though complaining that data partition was unknown. Searching seems to suggest that sometimes the bootloader doesn't know about all partitions (though it does about system which was flashed ok).
Tried playing with other recovery environments. Not willing to flash anything at this point so trying flashboot boot <img>. No luck so far - device just stays on bootloader splash screen. Probably not great that this device is a Allwinner A38 to which there doesn't seem to be huge support at the moment.
Even tried flashboot boot <recovery partition dump> file I made and that doesn't work.
Trimmed the first 0x800 so image starts with kernel code without joy.
A binwalk of the initrd image inside the dump shows a init.recovery.sun8i.rc file, and a default.prop with
ro.secure=1
ro.allow.mock.location=0
ro.debuggable=0
in init
# Always start adbd on userdebug and eng builds
on property:ro.debuggable=1
write /sys/class/android_usb/android0/enable 1
start adbd
So assuming default.prop is used (I'm still learning) then that's why I can't adb when in recovery mode. Seems stupid to design it that way.
I'm thinking if I can restore data partition it will fix the can't install apps problem, though perhaps the /system part is fundamentally busted. If I can reinstall KingRoot and root again I assume the device will be usable as it would effectively undo my supersume attempt to remove it.
Env partition dump I made used by the bootloader there is
Code:
boot_normal=sunxi_flash read 40007800 boot;boota 40007800 boot
boot_recovery=sunxi_flash read 40007800 recovery;boota 40007800 recovery
Usage:
sunxi_flash read command parmeters :
parmeters 0 : addr to load(hex only)
parmeters 1 : the name of the part to be load
[parmeters 2] : the number of bytes to be load(hex only)
if [parmeters 2] not exist, the number of bytes to be load is the size of the part indecated on partemeter 1
Click to expand...
Click to collapse
So maybe I need to specify the correct memory location when I'm fastboot boot'ing
There's no image type header specifing load address at the start of the recovery part dump I made.
Didn't manage to boot the recovery image - don't know why but a challenge for another day. Would probably be easier with UART access or similar to see what is actually happening.
In the end I mounted my /system backup on my linux server, cleaned it of KingRoot crap, and flashed it. Now everything is fine! Except no root access and the script I added to give me it comes us as unlabeled in selinux and isn't accessible.
The learning journey continues
og0 said:
Didn't manage to boot the recovery image - don't know why but a challenge for another day. Would probably be easier with UART access or similar to see what is actually happening.
In the end I mounted my /system backup on my linux server, cleaned it of KingRoot crap, and flashed it. Now everything is fine! Except no root access and the script I added to give me it comes us as unlabeled in selinux and isn't accessible.
The learning journey continues
Click to expand...
Click to collapse
I know this is a 2 year old thread... but does the OP still have that firmware that fixed the tab??
I have a Fusion5_108 with the A83T allwinner processor, stuck in a boot loop, wont get past the 'no command' screen when trying to recover,
think my only option is to make an sd card with a working firmware on it, and load it onto the devise like that, but i cant find a firmware or anything for this tablet