Related
OK I'm not a total n00b but I am a novice. I've been searching for an answer for this problem for a couple days now.
Device is a Nabi 2 that was rooted and had gapps installed on it using the Victoria tutorial on youtube. Everything was great until i tried to do the OTA update to 2.1. Obviously it wouldn't update because TWRP was installed so I downloaded Nabi Lab 2 to take it back to the stock ROM and bootloader. And now the problem starts...
After flashing the stock rom and installing the stock loader I rebooted. Now I'm stuck at the NABI loading screen with no animation. If I hold the Volume + key and power it will boot up to the screen with the options "boot normally, Fastboot Protect, Recovery Kernal, and Forced Recovery." However I am not able to navigate to any of the options or select anything. Also when the Nabi is connected to my PC Nabi Lab no longer sees it, nor does ADB (using "adb.exe devices" at the command prompt). It's also not detected by Device Manager. The only thing Device Manager sees is a MTP USB Device that it can not install a driver for.
So, PLEASE HELP! Before my daughter misses this stupid thing and I have to buy another.
dwelch77 said:
OK I'm not a total n00b but I am a novice. I've been searching for an answer for this problem for a couple days now.
Device is a Nabi 2 that was rooted and had gapps installed on it using the Victoria tutorial on youtube. Everything was great until i tried to do the OTA update to 2.1. Obviously it wouldn't update because TWRP was installed so I downloaded Nabi Lab 2 to take it back to the stock ROM and bootloader. And now the problem starts...
After flashing the stock rom and installing the stock loader I rebooted. Now I'm stuck at the NABI loading screen with no animation. If I hold the Volume + key and power it will boot up to the screen with the options "boot normally, Fastboot Protect, Recovery Kernal, and Forced Recovery." However I am not able to navigate to any of the options or select anything. Also when the Nabi is connected to my PC Nabi Lab no longer sees it, nor does ADB (using "adb.exe devices" at the command prompt). It's also not detected by Device Manager. The only thing Device Manager sees is a MTP USB Device that it can not install a driver for.
So, PLEASE HELP! Before my daughter misses this stupid thing and I have to buy another.
Click to expand...
Click to collapse
So you can't navigate the bootloader screen at all? If you click the vol- button it doesn't highlight the next menu item just nothing happens?
aicjofs said:
So you can't navigate the bootloader screen at all? If you click the vol- button it doesn't highlight the next menu item just nothing happens?
Click to expand...
Click to collapse
Exactly. I can not navigate the options at all. Volume - doesn't do anything, Volume + doesn't do anything.
OK scratch all of that. So while I was messing around with it this morning I accidentally dropped the tablet. After "impact calibration" the keys worked and I was able to get into TWRP. And Nabi Lab recognized it was plugged in. I was able to get it set all the back to factory with the factory boot recovery in place as well. As of right now update 2.1 is downloading and I'm keeping my fingers crossed that it will work.
The only thing I can think of is something on the board might have a broken solder connection, so as of right now I'm touching it as little as possible until the updates are done. I'll post back here when I have more information.
Nabi 2 Bricked ?
Hi,
I hope someone can help me with a Nabi 2 problem.
Basically I have 2 x Nabis. Rebuilt the first ok after a couple of days so that it now has Jelly Bean and Google Play (which is a big improvement). Then took it upon myself to start the 2nd one. I realised that something wasn't quite right and wiped in anticipation of rebuild again...what a mistake
So after installing the adb and fastboot drivers (pdanet) and TWRP 2.6.0 I can still get into TWRP BUT can no longer wipe "data", "cache", "system", "internal storage" etc as it says : "E:Unable to mount '/data' ....or system, or cache, addon, internal storage etc. Now i'm no expert on fastboot commands or terminal but can anyone please point me in the right direction as im completely clueless on this ?
I wouldn't know where to start
Thanks in advance
Dow
Dowmole said:
Hi,
I hope someone can help me with a Nabi 2 problem.
Basically I have 2 x Nabis. Rebuilt the first ok after a couple of days so that it now has Jelly Bean and Google Play (which is a big improvement). Then took it upon myself to start the 2nd one. I realised that something wasn't quite right and wiped in anticipation of rebuild again...what a mistake
So after installing the adb and fastboot drivers (pdanet) and TWRP 2.6.0 I can still get into TWRP BUT can no longer wipe "data", "cache", "system", "internal storage" etc as it says : "E:Unable to mount '/data' ....or system, or cache, addon, internal storage etc. Now i'm no expert on fastboot commands or terminal but can anyone please point me in the right direction as im completely clueless on this ?
I wouldn't know where to start
Thanks in advance
Dow
Click to expand...
Click to collapse
You are using wrong version(Jellybean vs ICS) of TWRP is my guess.
aicjofs said:
You are using wrong version(Jellybean vs ICS) of TWRP is my guess.
Click to expand...
Click to collapse
No matter what I do I cannot mount the internal storage (it shows 0MB under "Restore" and cannot mount the Micro SDcard either). All of the folders on the Nabi 2 are now empty and I would like to try to re-format and rebuild it. I have tried ICS and Jellybean TWRP but neither allow me to mount any folders (data, system,cache etc).
Is there anything I'm not doing or could try ?
Thanks
Dow
Dowmole said:
No matter what I do I cannot mount the internal storage (it shows 0MB under "Restore" and cannot mount the Micro SDcard either). All of the folders on the Nabi 2 are now empty and I would like to try to re-format and rebuild it. I have tried ICS and Jellybean TWRP but neither allow me to mount any folders (data, system,cache etc).
Is there anything I'm not doing or could try ?
Thanks
Dow
Click to expand...
Click to collapse
So what exactly did you do again? It was an original Nabi2 on ICS, and you "wiped" it. What exactly did you wipe? All the partitions not showing up is usually I sign of the wrong TWRP build but you said you tried both. Plus I have never seen where you can't mount the MicroSD
In the terminal app in TWRP(both versions) what does it say if you type
cat /proc/partitions
does it look like this:
major minor #blocks name
179 0 7766016 mmcblk0
179 1 8192 mmcblk0p1
179 2 8192 mmcblk0p2
179 3 823296 mmcblk0p3
179 4 481280 mmcblk0p4
179 5 2048 mmcblk0p5
179 6 32768 mmcblk0p6
179 7 1536000 mmcblk0p7
179 8 2048 mmcblk0p8
179 9 65536 mmcblk0p9
179 10 8192 mmcblk0p10
179 11 4485120 mmcblk0p11
179 32 2048 mmcblk0boot1
179 16 2048 mmcblk0boot0
179 48 31166976 mmcblk1
179 49 31162880 mmcblk1p1
or more like this
major minor #blocks name
179 0 7766016 mmcblk0
179 48 31166976 mmcblk1
179 49 31162880 mmcblk1p1
Thanks for your help on this aicjofs I really appreciate it
It shows :-
179 0 31166976 mmcblk0
179 1 1 mmckblk0p1
179 5 31164416 mmcblk0p5
The whole "short" story was....When I received the Nabi 2 just over a year ago I had to somehow get Google Play Store on it. As we know that wasn't possible until recently so I followed the guide by Victoria (I think from memory) on Youtube. This then did not allow me to do further Nabi updates. I managed to get this back to stock from your guide and then update bit by bit to the latest update (wit Jellybean). All was great until I realised that the wrong one of my children had been setup on it. I removed the user (from the parent portal on the Nabi website). This then stopped me using the external SD card (media errors stopping it)
So stupidly (in hindsight) I took it upon myself to wipe the Nabi from within Jellybean and re-boot, thinking that it would be a straightforward re-setup. But it wasn't. It seemed to have un-mounted everything. So now within TWRP I cannot mount data, system, cache, external sd card. and therefore cannot wipe those folders and start again (from TWRP that is). I have tried to mount those folders from terminal but am getting nowhere
Thanks
Dowmole
Ok I've now managed to mount all folders except external sd card.
I can push the system.ext4.win file to sdcard/twrp/backups/device name/oem/system.ext4.win ...but it does not show up in restore (can only see it in file manager). So therefore cannot restore.
Anyone have any ideas ?
Dowmole said:
Ok I've now managed to mount all folders except external sd card.
I can push the system.ext4.win file to sdcard/twrp/backups/device name/oem/system.ext4.win ...but it does not show up in restore (can only see it in file manager). So therefore cannot restore.
Anyone have any ideas ?
Click to expand...
Click to collapse
Hello Dowmole, I have the same problem as you because in my infinite wisdom I wiped and updated using the built in system as well.Would you mind telling me how you managed to mount your internal storage?Apparently now, it seems, our problems are inverted because I can ONLY mount my External SD.The tablet works fine but I can't reroot it or flash anything because TWRP is unable to mount /data etc...
also when I type cat /proc/partitions this is the result:
179 0 30892032 mmcblk0
179 1 30887936 mmcblk0p1
Is my internal sd corrupt or something should I format it?
Radmatazz said:
Hello Dowmole, I have the same problem as you because in my infinite wisdom I wiped and updated using the built in system as well.Would you mind telling me how you managed to mount your internal storage?Apparently now, it seems, our problems are inverted because I can ONLY mount my External SD.The tablet works fine but I can't reroot it or flash anything because TWRP is unable to mount /data etc...
also when I type cat /proc/partitions this is the result:
179 0 30892032 mmcblk0
179 1 30887936 mmcblk0p1
Is my internal sd corrupt or something should I format it?
Click to expand...
Click to collapse
I had a similar issue -- I think when I was installing the JB version of TWRP I also tried to change the screenlock image not realizing that the process had changed for JB. I had a complete mess with very similar if not identical issues as you.
What I did:
1. Make sure TWRP 2.6.3.0 for Jellybean is on the Nabi.
2. Download the stock 2.3.11 ROM from the Nabi wiki site and unzip it into a folder on your PC.
3. Next you need to copy the 4 recovery files from your PC to your SD card. I put the SD card into my PC and copied the files over putting them into a TWRP back up folder on the SD card. Now, in order for Jellybean TWRP to recognize the backup, I had to fool it into thinking I had a "good" existing Jellybean TWRP backup and rename the TWRP backup folders to something like this:
TWRP\BACKUPS\0f41000001000000\2014-01-24--09-54-07 JRO03C\
4. Put the SD card back into the Nabi and then boot into TWRP mode.
5. Do a restore from there.
It *should* install a clean fresh copy of Jellybean on the Nabi. It does take what seems like an eternity for it to get past the spinning circle with the NABI logo when it's loading for the first time so be patient.
Your solution was awesome!
2girlzdad said:
I had a similar issue -- I think when I was installing the JB version of TWRP I also tried to change the screenlock image not realizing that the process had changed for JB. I had a complete mess with very similar if not identical issues as you.
What I did:
1. Make sure TWRP 2.6.3.0 for Jellybean is on the Nabi.
2. Download the stock 2.3.11 ROM from the Nabi wiki site and unzip it into a folder on your PC.
3. Next you need to copy the 4 recovery files from your PC to your SD card. I put the SD card into my PC and copied the files over putting them into a TWRP back up folder on the SD card. Now, in order for Jellybean TWRP to recognize the backup, I had to fool it into thinking I had a "good" existing Jellybean TWRP backup and rename the TWRP backup folders to something like this:
TWRP\BACKUPS\0f41000001000000\2014-01-24--09-54-07 JRO03C\
4. Put the SD card back into the Nabi and then boot into TWRP mode.
5. Do a restore from there.
It *should* install a clean fresh copy of Jellybean on the Nabi. It does take what seems like an eternity for it to get past the spinning circle with the NABI logo when it's loading for the first time so be patient.
Click to expand...
Click to collapse
-----> My issue was EXACTLY the same, I used your solution and viola, it is fixed, it even auto asked me to install root before I rebooted! THANK YOU... as a rank amateur, I feel I should share the finer details of my solution to help anyone else out that also has this problem.
I did a couple things different from this, that I should share so that all will benefit.
I use NabiLabGUI. The TWRP that comes with it does NOT work with my build. I searched for the TWRP that comes with it,
Found at my 'C:\Users\Spam\AppData\Local\Apps\2.0\7J1BHCKA.8HM\5YTQ71XH.YAP\ then 2 sub directories,
nabi...exe_3432fd94fe885e67_0001.0002_none_141f851fecdb6e30 and
nabi..tion_3432fd94fe885e67_0001.0002_f75a67d47ecb93e2
since I have a nabi 2 NV7A, for my daughter, I opened the subdirectory '2' in each replacing the 2\recovery\new\recovery.img with the one from twrp-recovery-JBNV7AUS-263.zip (note you must rename it to 'recovery.img')
I then ran nabilabgui, simply selecting the recovery installer, to easily load the recovery image, booted into the now version 2.6.3 TWRP, and loaded the 'twrp-recovery-JBNV7AUS-263.zip'
No boot/softbrick
I am unable boot beyond the bootloader screen. I cannot gain access via Nabi Lab GUI with ADB but I can via Fastboot. So my issue is how do I fix my Nabi 2 via Fastboot? I need commands and where and what files to get back to stock.
Thank you,
Niles
Hi there I think I have softbricked my Nabi 2. I tried to update the software from ICS to JB using files from the XDA Nabi 2 Wiki but have come to a massive problem. I can't boot back into TWRP because all I get is an Android laying down with an ! on his chest. I can't re-install TWRP because my Windows 8 PC can no longer see the device!! I can get into the tablet options menu with fastboot, forced recover etc. I think the biggest problem is getting the PC to see the device.
If I try selecting different options in the tablet boot menu then Windows will see the device as Android ADB Device or MTP USB Device.
Can anyone help me get over this problem? I'm not used to using shell commands but fear I will have to install the Android environment to use ADB to get things working.
Please help if you can as this tablet belongs to a nephew of mine and he is missing his YouTube. I am close to tears trying to find the solution. I have read and re-read XDA posts in case I missed something.
Many Thanks In Advance.
Doozeman
Doozeman said:
Hi there I think I have softbricked my Nabi 2. I tried to update the software from ICS to JB using files from the XDA Nabi 2 Wiki but have come to a massive problem. I can't boot back into TWRP because all I get is an Android laying down with an ! on his chest. I can't re-install TWRP because my Windows 8 PC can no longer see the device!! I can get into the tablet options menu with fastboot, forced recover etc. I think the biggest problem is getting the PC to see the device.
If I try selecting different options in the tablet boot menu then Windows will see the device as Android ADB Device or MTP USB Device.
Can anyone help me get over this problem? I'm not used to using shell commands but fear I will have to install the Android environment to use ADB to get things working.
Please help if you can as this tablet belongs to a nephew of mine and he is missing his YouTube. I am close to tears trying to find the solution. I have read and re-read XDA posts in case I missed something.
Many Thanks In Advance.
Doozeman
Click to expand...
Click to collapse
Android lying down is stock recovery, need to put TWRP back on it.
Since you can get to the tablet menu you need to select fastboot protocol. It will not do anything unless 2 conditions are met. You need to have USB plugged in to your computer and the fastboot driver installed. The fastboot driver might be the hardest part, most of the time people use PDAnet installer. Once you have that you can then put TWRP back on it with
fastboot flash recovery recovery.img or with Nabilab GUI
Where you might run in to problems is where your upgrade failed, hard to tell if you now have the JB bootloader or the ICS bootloader. Try TWRP's for both versions until you figure it out.
aicjofs said:
Android lying down is stock recovery, need to put TWRP back on it.
Since you can get to the tablet menu you need to select fastboot protocol. It will not do anything unless 2 conditions are met. You need to have USB plugged in to your computer and the fastboot driver installed. The fastboot driver might be the hardest part, most of the time people use PDAnet installer. Once you have that you can then put TWRP back on it with
fastboot flash recovery recovery.img or with Nabilab GUI
Where you might run in to problems is where your upgrade failed, hard to tell if you now have the JB bootloader or the ICS bootloader. Try TWRP's for both versions until you figure it out.
Click to expand...
Click to collapse
Thanks very much for the reply. I did have PDANet installed and my computer couldn't see the tablet. I will try again soon later. I think my problem has arisen since i followed a procedure from this link http://forum.xda-developers.com/showpost.php?p=50431606&postcount=98 and I may have messed up flashing this file http://forum.xda-developers.com/showpost.php?p=50356162&postcount=91 too early!. Ultimately I wish to have this file http://forum.xda-developers.com/showpost.php?p=50341726&postcount=85 on the tablet and it being up and running with no problems.
First things first though I need to get the tablet seen by the computer.
Do I need to uninstall my Nexus 7 and Samsung Galaxy S III drivers first before installing PDANet? Once installed how do I get fastboot installed?
Many Thanks in Advance,
Doozeman
Okay I now have found how I can install TWRP via your command but I'm still unable to install an OS on the tablet. NabiLabs refuses to see the tablet and I am now stuck. Tell you what like this is a steep learning curve for me! Why can't this tablet be as easy as the Nexus 7 to flash or recover?
Have you any more suggestions as to how I can proceed? Is there another way I can push installation files? I have tried copying stock restore files (as supplied by Nabilabs) to a micro sd card using the following layout TWRP/BACKUPS/"My Device Number"/restore but no matter the version of TWRP installed there are no files shown to restore.
*Update* I have tried to install the latest TWRP via flashable zip but it won't install because of the missing folders as there is no OS installed. I get an error status 6. Unable to mount /data, /system, /cache etc.
I'm beginning to fear that I have killed this tablet
I'm tearing my hair out here!!
Many Thanks in Advance
Completely and totally stumped
This started yesterday. Never rooted this tablet, no custom roms, totally stock (it's my daughters); I decided to check for updates. All there was was a 'Google security update' or something like that. I was on JB already. So I installed the update and the tablet decided it had to restart and since then it had just gone into a bootloop (constant Nabi splash screen)... So I've follow instruction to get the TWRP recovery (2.6.3.0) on here via fastboot flash and I can boot into there just fine. I cannot mount anything on internal storage. I have 2127 & 2311 stock backups set up on an ext flash drive in the TWRP backup folder and can see it when I go to restore in TWRP, but they both fail because they 'cannot find partition size for boot'. No matter what I do I cannot mount anything from internal storage. I'm at the point where I think internal is corrupt. There's no OS. It shows Internal Storage (0MB) as well.
Anyone have any ideas at what I might be up against here or what I can do?
sandrewmorrison said:
This started yesterday. Never rooted this tablet, no custom roms, totally stock (it's my daughters); I decided to check for updates. All there was was a 'Google security update' or something like that. I was on JB already. So I installed the update and the tablet decided it had to restart and since then it had just gone into a bootloop (constant Nabi splash screen)... So I've follow instruction to get the TWRP recovery (2.6.3.0) on here via fastboot flash and I can boot into there just fine. I cannot mount anything on internal storage. I have 2127 & 2311 stock backups set up on an ext flash drive in the TWRP backup folder and can see it when I go to restore in TWRP, but they both fail because they 'cannot find partition size for boot'. No matter what I do I cannot mount anything from internal storage. I'm at the point where I think internal is corrupt. There's no OS. It shows Internal Storage (0MB) as well.
Anyone have any ideas at what I might be up against here or what I can do?
Click to expand...
Click to collapse
Usually a sign u flashed ICS TWRP instead of JB.
aicjofs said:
Usually a sign u flashed ICS TWRP instead of JB.
Click to expand...
Click to collapse
Can you tell me the version numbers of each version? I believe I have tried both. Both have told me I have no OS installed, cannot mount any internal anything, can't format it, and doesn't show any internal storage space. It comes up as 0mb.
Hi I've been reading through the forum here for about 2 years now and got a lot of helpful advice on rooting and flashing my Android devices but this is my first thread. Unfortunately I've messed up my USA Galaxy Player 5.0 and don't know what to do that I haven't already tried. Let me start at the beginning.
I rooted my player a while ago and everything was fine untill my micro-SD card wouldn't mount in other devices but sometimes it would in my player. So, I installed AParted on my Player and proceeded to format what I thought was the SD card. I found out when I rebooted my player hours later that it had wiped my Player rather than that SD card and my Player wouldn't boot but gave a bunch of errors.
I had flashed Samsung devices with odin 1.85 before and decided to try some of the rooted ROMs from this site. They all appeared to flash just fine in odin, however when the Player rebooted it stopped at the CWM recovery screen saying it could not mount the /cache. I went into mounts and storage and tried to format /cache and got this:
E:format_volume: make_extf4fs failed on /dev/block/mmcblk0p15.
I also tried installing CWM recovery zip files and they installed way too fast and then didn't work. It seems like my Player cannot write all of the needed files. Any suggestions? I dual boot WinXP and Ubuntu. In Ubuntu I installed Heimdall 1.4 and the frontend but am not real sure how to use it. I did get Heimdall started ok with sudo heimdall-frontend.
Marty
What rom did you flash? Also heimdall frontend 1.4 is just weird lol. I use 1.1 instead.
Sent from my YP-G1 using xda app-developers app
obscuresword said:
What rom did you flash? Also heimdall frontend 1.4 is just weird lol. I use 1.1 instead.
Sent from my YP-G1 using xda app-developers app
Click to expand...
Click to collapse
Well I tried a lot of ROMs that I'll list. The one I have a backup from a year ago (that's from my first Galaxy Player 5 that I hard bricked before I bought this 2nd one) uses Eryigit 3.5 USA ROM and also has CWM on it. That's what is on it now, though it only boots to CWM. These are the ROMs I tried that wouldn't boot:
Odin:
Eryigit 3.5 USA
Stock ROM with PIT UEKI8_MIN
CWM:
CM7.2.0-RC1
CM9-HWA-12.5.2012
Noisy Fox GB ROM ZKP9
Supermaster CM9
Chip 1.5-1
I honestly don't think it's a ROM problem since these have all worked for me on my previous Galaxy Player 5 USA model. I think AParted messed up the partitions when it formatted the device.
How do I fix the partitions? I thought that's what a PIT file did, but it seems to just get stuck on the PIT file in odin...how long should it take?
Marty
LinuxHippy said:
Well I tried a lot of ROMs that I'll list. The one I have a backup from a year ago (that's from my first Galaxy Player 5 that I hard bricked before I bought this 2nd one) uses Eryigit 3.5 USA ROM and also has CWM on it. That's what is on it now, though it only boots to CWM. These are the ROMs I tried that wouldn't boot:
Odin:
Eryigit 3.5 USA
Stock ROM with PIT UEKI8_MIN
CWM:
CM7.2.0-RC1
CM9-HWA-12.5.2012
Noisy Fox GB ROM ZKP9
Supermaster CM9
Chip 1.5-1
I honestly don't think it's a ROM problem since these have all worked for me on my previous Galaxy Player 5 USA model. I think AParted messed up the partitions when it formatted the device.
How do I fix the partitions? I thought that's what a PIT file did, but it seems to just get stuck on the PIT file in odin...how long should it take?
Marty
Click to expand...
Click to collapse
You need to check your partition table. flash Entrophy512's daily driver then in adb: fdisk -l /dev/block/mmcblk0
Compare output to image in this post http://forum.xda-developers.com/showpost.php?p=44626450&postcount=33
If it doesn't match exactly then read this entire thread: http://forum.xda-developers.com/showthread.php?t=2398120
EDIT: FYI - When you put a pit file in Odin, all it does is flash the PIT file to the PIT partition. If your partition table is jacked and the PIT Partition is missing...???
If you check "repartition" in Odin, then Odin reads the pit from the pit partition then reformats according to what the PIT says, but if your PIT Partition is missing...???
The galaxy player 5's PIT Partition is /dev/block/mmcblk0p6
Meticulus said:
You need to check your partition table. flash Entrophy512's daily driver then in adb: fdisk -l /dev/block/mmcblk0
Compare output to image in this post http://forum.xda-developers.com/showpost.php?p=44626450&postcount=33
If it doesn't match exactly then read this entire thread: http://forum.xda-developers.com/showthread.php?t=2398120
EDIT: FYI - When you put a pit file in Odin, all it does is flash the PIT file to the PIT partition. If your partition table is jacked and the PIT Partition is missing...???
If you check "repartition" in Odin, then Odin reads the pit from the pit partition then reformats according to what the PIT says, but if your PIT Partition is missing...???
The galaxy player 5's PIT Partition is /dev/block/mmcblk0p6
Click to expand...
Click to collapse
Good-then there is still hope...I thought I messed up a 2nd Galaxy Player. It boots to CWM now...can I flash Entropy´s kernel there or do I need to do that in odin?
Marty
LinuxHippy said:
Good-then there is still hope...I thought I messed up a 2nd Galaxy Player. It boots to CWM now...can I flash Entropy´s kernel there or do I need to do that in odin?
Marty
Click to expand...
Click to collapse
It doesn't matter how it gets flashed as long as it does...
Meticulus said:
It doesn't matter how it gets flashed as long as it does...
Click to expand...
Click to collapse
Well, I read over the threads u posted, got ADB working in Win XP, and then flashed my kernel so that it's using entropy512's kernel. All looked ok till is issued the fdisk command on the SGP and it couldn't find mmcblk0. What else would it call the root device? I issued a couple commands in the attached screenshot and it looks like I only have 376 MB rather than ~ 8 GB.
The screenshot file is attached to this post.
Marty
LinuxHippy said:
Well, I read over the threads u posted, got ADB working in Win XP, and then flashed my kernel so that it's using entropy512's kernel. All looked ok till is issued the fdisk command on the SGP and it couldn't find mmcblk0. What else would it call the root device? I issued a couple commands in the attached screenshot and it looks like I only have 376 MB rather than ~ 8 GB.
The screenshot file is attached to this post.
Marty
Click to expand...
Click to collapse
Its /dev/block/mmcblk0
Sent from my M470BSA using Tapatalk
That worked but the output didn't match yours at all. Besides there being no partitions (I was trying to format my SD card with a FAT32 filesystem) the device has 4 heads (yours had 1) and the units are cyclinder of 64 (you have 16). I attached another screenshot...I do still have 7944 MB, though!
So, with these differences should I proceed with repartitioning with fdisk??
Marty
I'm not root
LinuxHippy said:
That worked but the output didn't match yours at all. Besides there being no partitions (I was trying to format my SD card with a FAT32 filesystem) the device has 4 heads (yours had 1) and the units are cyclinder of 64 (you have 16). I attached another screenshot...I do still have 7944 MB, though!
So, with these differences should I proceed with repartitioning with fdisk??
Marty
Click to expand...
Click to collapse
I realized just now that I'm not root and when I try to change into root with su it cannot find that command because it doesn't have a /bin directory (in Ubuntu it's /bin/su). It may only display partitions to the root user and wouldn't let me create any without being root. Maybe it's running out of space and cannot create that directory? Could u put a link on here of the page for Entropy512's daily kernels? You had mentioned it, but the 1 I found is from 2012 and I'm not sure if it's daily.
Marty
I wrote my new partition table!
Well, I installed Entropy512's kernel from 01222012 and that gave me root. Then from ADB shell I was able to gain all the functions of fdisk. I still did not have any partitions. However, I could not follow your guide exactly because my Galaxy Player has 4 heads...this meant that each block was 32 bytes. So I had to use trial and error to try to get the Start and End blocks close to the number of blocks in each of your partitions. In fdisk I had to display the table after every new partition with P and if it wasn't the right number of blocks I would delete it with D and then try again keeping in mind that each block increased or decreased the size of the partition by 32 bytes.
I may be explaining this wrong and went about this the wrong way. I wrote the table and attached another screenshot. Before I wrote any ROMs to it, I wanted to make sure it looked good enough for ROMs to write to it.
Marty
Unpartitioned space
There is unpartitioned space at the end of this "drive".
Meticulus has 969728-969528=200
I have 242432-242373=59
This space is almost equal if u consider each head to use 50 and there are 4 heads...200. Each block takes 32 of these (bytes?).
I hope u can follow my reasoning since I don't know the units. If this space is unused, I'm wondering if 1 of these partitions could be increased by 32 bytes? If this space isn't used by a ROM, I could re-do this pretty easily to prevent my SGP from locking up again.
It looks like Samsung put out at least 2 USA geometries of their SGP5. Perhaps somebody else could post ADB outputs of fdisk -l /dev/blk/mmcblk0?
LinuxHippy said:
There is unpartitioned space at the end of this "drive".
Meticulus has 969728-969528=200
I have 242432-242373=59
This space is almost equal if u consider each head to use 50 and there are 4 heads...200. Each block takes 32 of these (bytes?).
I hope u can follow my reasoning since I don't know the units. If this space is unused, I'm wondering if 1 of these partitions could be increased by 32 bytes? If this space isn't used by a ROM, I could re-do this pretty easily to prevent my SGP from locking up again.
It looks like Samsung put out at least 2 USA geometries of their SGP5. Perhaps somebody else could post ADB outputs of fdisk -l /dev/blk/mmcblk0?
Click to expand...
Click to collapse
Please read the ENTIRE thread. Changing the heads is explained and you must change the head first. There is only one U.S.A "geometry".
Meticulus said:
Please read the ENTIRE thread. Changing the heads is explained and you must change the head first. There is only one U.S.A "geometry".
Click to expand...
Click to collapse
Oh, I missed something. I'll read the posted threads again (there are threads inside of threads here) later. It's good to know that Samsung only put out 1 version of their USA SGP5...I was gonna comb the web later for partition table screenshots and that woulda been a complete waste of time.
Can u post the EXACT posting that I should re-read?
Marty
LinuxHippy said:
Oh, I missed something. I'll read the posted threads again (there are threads inside of threads here) later. It's good to know that Samsung only put out 1 version of their USA SGP5...I was gonna comb the web later for partition table screenshots and that woulda been a complete waste of time.
Can u post the EXACT posting that I should re-read?
Marty
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=45458589&postcount=55
Have a better partition table!!
Meticulus said:
http://forum.xda-developers.com/showpost.php?p=45458589&postcount=55
Click to expand...
Click to collapse
OK, thanks for the last link...that was helpful! I hadn't read that & didn't know after 12 years of Linux use that there was an expert mode for fdisk...now I can fix my computer disk that I re-partitioned years ago and has 4 heads (that's working, though and like I've always been told, "if it aint broke, don't fix it!" I now re-did the partition table with 1 head and it ALMOST looks like your table. I attached a screenshot of your table and mine side by side so u can easily compare. What's on your table and missing from mine are 2 lines:
Omitting empty partition (18)
Partition 1 does not end on cylinder boundary
Are these important or am I ready to flash this puppy with the Low Level Russian ROM u suggested?
Marty
LinuxHippy said:
OK, thanks for the last link...that was helpful! I hadn't read that & didn't know after 12 years of Linux use that the was an expert mode for fdisk...now I can fix my computer disk that I re-partitioned years ago and has 4 heads (that's working, though and like I've always been told, "if it aint broke, don't fix it!" I now re-did the partition table with 1 head and it ALMOST looks like your table. I attached a screenshot of your table and mine side by side so u can easily compare. What's on your table and missing from mine are 2 lines:
Omitting empty partition (18)
Partition 1 does not end on cylinder boundary
Are these important or am I ready to flash this puppy with the Low Level Russian ROM u suggested?
Marty
Click to expand...
Click to collapse
Technically: fdisk in Entropy512's Daily Driver is the busybox version, which does not have "expert" mode but newer version of fdisk (not in busybox) do have an "expert" mode that you can select with the option "x" at the prompt. However the busybox fdisk does have the ability to change the heads which is in the "expert" mode in newer (non-busybox) versions of fdisk. But that isn't really relevant at this point. Just an FYI.
I don't know how relevant those 2 lines are...
All I can say is give it a go...:good:
All fixed
Well, I didn't have to flash another ROM after I had redone the partitions. Once I had shut down the SGP5 after doing the partitions, I left it on for a half hour or so and then shut it down. When I restarted the SGP5 it booted just fine into the last ROM I flashed. I think it's running Eryigit 3.5 but it may be another one. I'm gonna restore a backup in CWM that I made a year ago and that should be running Eryigit 3.5.
How can I find out which ROM it is running and any idea why there were 4 heads on the device? I bought it as a refurbished SGP5 so somebody else may have done it months ago or maybe the AParted app I was using to format an SD card did that.
Thanks for your help
Marty
LinuxHippy said:
Well, I didn't have to flash another ROM after I had redone the partitions. Once I had shut down the SGP5 after doing the partitions, I left it on for a half hour or so and then shut it down. When I restarted the SGP5 it booted just fine into the last ROM I flashed. I think it's running Eryigit 3.5 but it may be another one. I'm gonna restore a backup in CWM that I made a year ago and that should be running Eryigit 3.5.
How can I find out which ROM it is running and any idea why there were 4 heads on the device? I bought it as a refurbished SGP5 so somebody else may have done it months ago or maybe the AParted app I was using to format an SD card did that.
Thanks for your help
Marty
Click to expand...
Click to collapse
To find out what ROM your running, the best evidence is going to be in the "About Phone" area, or the build.prop. I think ( not really sure ) that there was a time that the "heads" property did represent the physical number of heads that the storage device had but with more modern forms of storage, it's just a number that part of an algorithm for organizing the space into units. I might be wrong there. It's just the impression that I get. Most likely it was a result of the way AParted partitions disks....
On a personal note, if you look @ the build.prop for Eryigit's rom, you'll probably see my name. "Meticulus". It's sort of an easter egg...:laugh:
Actually the backup I had wasn't working with google play so I wound up flashing with the LLF Russian ROM & then flashing a rooted stock gingerbread ROM and wiping data and caches. Then it was new and I had to login to google play. Now everything works.
Marty
Sent from my YP-G70 using xda app-developers app
Guys i have bricked my phone by restoring MK1 efs backup created with efs professional tool. Few days ago i upgraded it with android 4.4 version with ota. I restored all partitions with efs pro tool except user data and system. Now it's in qhsusb_dload mode. I tried i9205 debrick image from this forum and it's not working. I do not know how to make debrick image form stock rom or any other way. Can anyone help me to fix this?
Thanks
Finally unbricked it with DarkAngel's help. Many thanks to him.
For unbrick your phone please read all post's by DarkAngel.
ashikrobi said:
Guys i have bricked my phone by restoring MK1 efs backup created with efs professional tool. Few days ago i upgraded it with android 4.4 version with ota. I restored all partitions with efs pro tool except user data and system. Now it's in qhsusb_dload mode. I tried i9205 debrick image from this forum and it's not working. I do not know how to make debrick image form stock rom or any other way. Can anyone help me to fix this?
Thanks
Click to expand...
Click to collapse
Have you tried to Odin the Official Firmware available for the L600? It can be done via Kies as well.
L600VPUBNE4
I tried odin and kies
DarkAngel said:
Have you tried to Odin the Official Firmware available for the L600? It can be done via Kies as well.
L600VPUBNE4
Click to expand...
Click to collapse
Yes i tried but in qhsusb_dload mode odin cannot find the phone. It cannot be powered up bro so how can kies detect it? Do you know how to fix this issue? Please help.
ashikrobi said:
Yes i tried but in qhsusb_dload mode odin cannot find the phone. It cannot be powered up bro so how can kies detect it? Do you know how to fix this issue? Please help.
Click to expand...
Click to collapse
Which version of Odin are you using?
odin 3.09 and 3.04
DarkAngel said:
Which version of Odin are you using?
Click to expand...
Click to collapse
I tried with these versions. They do not detect the device. If you have a working phone, you can make a debrick image for me. Please install busybox and a terminal emulator. Then issue this command from the terminal and you will get the debrick image in your sd card.
su
busybox dd if=/dev/block/mmcblk0 of=/sdcard/debrick.img bs=1M count=128
Make sure you have SPH-L600 and android version 4.4 or the image will not work for me.
Please upload
Thanks
installed automatic upgrade stuck in boot loop
I have a Galaxy Mega SPH-L600 and i replaced the screen about a week ago and it was running fine opened it up 2 days ago and there was an update said needed to be done so hit ok and installed update it went to 100% and shut off and turned back on went to Samsung splash screen and shut off and turned back on did this for about a half hour so i tried to do the hard boot with power button,volume up and home button droid comes up and it says installing upgrade and goes back ito boot loop tried to hook up to laptop but can not get it to show up on my Windows 7 unit tried alot of stuff nothing works need some help from anyone that can point me in the right direction and thank you in advance
ashikrobi said:
I tried with these versions. They do not detect the device. If you have a working phone, you can make a debrick image for me. Please install busybox and a terminal emulator. Then issue this command from the terminal and you will get the debrick image in your sd card.
su
busybox dd if=/dev/block/mmcblk0 of=/sdcard/debrick.img bs=1M count=128
Make sure you have SPH-L600 and android version 4.4 or the image will not work for me.
Please upload
Thanks
Click to expand...
Click to collapse
The only problem I have with the debrick image is if the 128mb will include my EFS information. I have to mount it to an extra SDcard I have and check it's content before I give it out or post it up for grabs.
Thank you for the how too but I am familiar with making a debrick image using TE. I have one made for all my devices although I haven't bothered checking to see what was exactly on this one being it is at 128mb ( as my SGS3 needs only just about half of the requested to work ) so I can provide the needed files.
Just to make things clear not all images being from other carriers will work on other devices of the same model. They may be partitioned a different way than the L600. Also you PM'd me that you tried to recover your EFS info using the created backup from one of a MK1. I wouldn't have tried that. You already upgraded to 4.4 and have the newest Knox bootloader which will not allow you to downgrade the Bootloader at all.
Thanks for the reply
DarkAngel said:
The only problem I have with the debrick image is if the 128mb will include my EFS information. I have to mount it to an extra SDcard I have and check it's content before I give it out or post it up for grabs.
Thank you for the how too but I am familiar with making a debrick image using TE. I have one made for all my devices although I haven't bothered checking to see what was exactly on this one being it is at 128mb ( as my SGS3 needs only just about half of the requested to work ) so I can provide the needed files.
Just to make things clear not all images being from other carriers will work on other devices of the same model. They may be partitioned a different way than the L600. Also you PM'd me that you tried to recover your EFS info using the created backup from one of a MK1. I wouldn't have tried that. You already upgraded to 4.4 and have the newest Knox bootloader which will not allow you to downgrade the Bootloader at all.
Click to expand...
Click to collapse
Thanks DarkAngel for your reply. My sprint mega was reprogrammed by myself with dfs tool. I didn't provisioned it with any commercial way. I just changed it to use uim to get operator information and it was working. But after i changed the rom to slimkat i lost esn from efs. That's why i tried to restore efs backup after 4.4 ota update.
I knew you are an expert or an android developer so i requested help from you. Because you have some threads that maybe possible by a developer. I am in a horrible situation. I took my phone the other day to my local jtag repair center an they failed to repair it. They said there is no support for this phone still now. Brother please help me to fix my phone. Thanks.
ashikrobi said:
Thanks DarkAngel for your reply. My sprint mega was reprogrammed by myself with dfs tool. I didn't provisioned it with any commercial way. I just changed it to use uim to get operator information and it was working. But after i changed the rom to slimkat i lost esn from efs. That's why i tried to restore efs backup after 4.4 ota update.
I knew you are an expert or an android developer so i requested help from you. Because you have some threads that maybe possible by a developer. I am in a horrible situation. I took my phone the other day to my local jtag repair center an they failed to repair it. They said there is no support for this phone still now. Brother please help me to fix my phone. Thanks.
Click to expand...
Click to collapse
Well not an expert but I read a lot on here and do what I can when I can.
This is what I got from my Mega:
Code:
L600 Output
====================
Disk /dev/block/mmcblk0: 15.8GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
[U]
Number Start End Size File system Name Flags[/U]
[B] 1 4194kB 67.1MB 62.9MB modem
2 67.1MB 67.2MB 131kB sbl1
3 67.2MB 67.5MB 262kB sbl2
4 67.5MB 68.0MB 524kB sbl3
5 68.0MB 70.1MB 2097kB aboot
6 70.1MB 70.6MB 524kB rpm
7 70.6MB 71.2MB 524kB tz
8 71.2MB 84.3MB 13.1MB pad
9 84.3MB 92.7MB 8389kB param[/B]
[COLOR=Red][B]10 92.7MB 107MB 14.3MB ext4 efs[/B][/COLOR]
11 107MB 110MB 3146kB modemst1
12 110MB 113MB 3146kB modemst2
13 113MB 124MB 10.5MB boot
14 124MB 134MB 10.5MB recovery
15 134MB 145MB 10.5MB fota
16 145MB 152MB 7332kB backup
17 152MB 155MB 3146kB fsg
18 155MB 155MB 8192B ssd
19 155MB 164MB 8389kB ext4 persist
20 164MB 176MB 12.6MB ext4 persdata
21 176MB 2324MB 2147MB ext4 system
22 2324MB 3058MB 734MB ext4 cache
23 3058MB 3079MB 21.0MB ext4 carrier
24 3079MB 15.8GB 12.7GB ext4 userdata
pit file of my mega
DarkAngel said:
Well not an expert but I read a lot on here and do what I can when I can.
This is what I got from my Mega:
Code:
L600 Output
====================
Disk /dev/block/mmcblk0: 15.8GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
[U]
Number Start End Size File system Name Flags[/U]
[B] 1 4194kB 67.1MB 62.9MB modem
2 67.1MB 67.2MB 131kB sbl1
3 67.2MB 67.5MB 262kB sbl2
4 67.5MB 68.0MB 524kB sbl3
5 68.0MB 70.1MB 2097kB aboot
6 70.1MB 70.6MB 524kB rpm
7 70.6MB 71.2MB 524kB tz
8 71.2MB 84.3MB 13.1MB pad
9 84.3MB 92.7MB 8389kB param[/B]
[COLOR=Red][B]10 92.7MB 107MB 14.3MB ext4 efs[/B][/COLOR]
11 107MB 110MB 3146kB modemst1
12 110MB 113MB 3146kB modemst2
13 113MB 124MB 10.5MB boot
14 124MB 134MB 10.5MB recovery
15 134MB 145MB 10.5MB fota
16 145MB 152MB 7332kB backup
17 152MB 155MB 3146kB fsg
18 155MB 155MB 8192B ssd
19 155MB 164MB 8389kB ext4 persist
20 164MB 176MB 12.6MB ext4 persdata
21 176MB 2324MB 2147MB ext4 system
22 2324MB 3058MB 734MB ext4 cache
23 3058MB 3079MB 21.0MB ext4 carrier
24 3079MB 15.8GB 12.7GB ext4 userdata
Click to expand...
Click to collapse
Take a loot at my pit file previously created with efs professional tool. Same like yours. I hope your debrick image will work for my mega. Please upload when possible. Do not worry about efs partition. I have my efs backup. I will restore mine. I have a question, if my phone becomes useable after using your debrick image and i restore only efs partition from efs backup will it brick again?
Thanks.
SPH-L600 sprint mega bad ESN
so as not to make a new topic, I decided to write here
I recently bought SPH-L600 sprint mega with a bad ESN, he came to me activated on Sprint and Sprint have sim I played settings and activation dropped sprint
but I live in another country and I can not activate it!
help somehow activate it! I bought an unlock code network, but said that he needed seller activation sprint!
any help would be much appreciated!
ashikrobi said:
Take a loot at my pit file previously created with efs professional tool. Same like yours. I hope your debrick image will work for my mega. Please upload when possible. Do not worry about efs partition. I have my efs backup. I will restore mine. I have a question, if my phone becomes useable after using your debrick image and i restore only efs partition from efs backup will it brick again?
Thanks.
Click to expand...
Click to collapse
Yes, they should be the same thing as we both have L600's. I didn't have a chance to look it over but I will try and get it to you later on today.
All you need is for your Mega to be able to get to Download Mode. Then and only then you will have to Odin a copy of the Official Firmware L600VPUBNE4 for it not to stay bricked but you probably already know that. As far as becoming usable that would be up to you, being able to restore your EFS data. In theory it should not brick but you need to only restore the EFS portion of the data.
Here is all the info I gathered from using Terminal Emulator in case you need it for file locations:
EFS is located: /dev/block/mmcblkop10
As you can see msm_sdcc.1 is specific to our device ( I noticed that it was the same on my SGS3 but not my SGN2 on KitKat ) so one can locate the by-name file to get the list below.
The second picture shows GNU Parted being run in my Terminal Emulator. You would need the Parted Binary file located here at the end of the Original Post.
Just extract the parted binary manually and then copy and paste it to the /system/bin folder with any File Explorer with Root access. After you paste the binary you will need to set the permissions to the parted binary you pasted to rwxr-xr-x or (0755). You can do this to any device you have and run it either in Terminal Emulator and even via ADB on your computer. Really handy to have sometimes.
Once you get the debrick image, below are two guides that I saved in my subscriptions that may help you. You may have them already.
deBricker
gTan64
---------- Post added at 05:31 AM ---------- Previous post was at 05:29 AM ----------
Ura535 said:
so as not to make a new topic, I decided to write here
I recently bought SPH-L600 sprint mega with a bad ESN, he came to me activated on Sprint and Sprint have sim I played settings and activation dropped sprint
but I live in another country and I can not activate it!
help somehow activate it! I bought an unlock code network, but said that he needed seller activation sprint!
any help would be much appreciated!
Click to expand...
Click to collapse
Actually this is an entirely different topic from Debricking a phone. You have a phone with a bad ESN. With that I can not help. If the previous owner ( or seller in your case ) "maybe" did not pay his bill, then your phone is locked out until it is released from his/her account by Sprint. If there is a way around this, I may not know.
I had this happen to me once before with my wife's Sprint SGS4. It was a pain but eventually two days later the seller finally came through and the phone was released for activation.
You should start a separate thread to see if you can get the right help and not get your question lost in this thread. I am sorry I couldn't help you any further.
Sorry you misunderstood
DarkAngel said:
Yes, they should be the same thing as we both have L600's. I didn't have a chance to look it over but I will try and get it to you later on today.
All you need is for your Mega to be able to get to Download Mode. Then and only then you will have to Odin a copy of the Official Firmware L600VPUBNE4 for it not to stay bricked but you probably already know that. As far as becoming usable that would be up to you, being able to restore your EFS data. In theory it should not brick but you need to only restore the EFS portion of the data.
Here is all the info I gathered from using Terminal Emulator in case you need it for file locations:
EFS is located: /dev/block/mmcblkop10
As you can see msm_sdcc.1 is specific to our device ( I noticed that it was the same on my SGS3 but not my SGN2 on KitKat ) so one can locate the by-name file to get the list below.
The second picture shows GNU Parted being run in my Terminal Emulator. You would need the Parted Binary file located here at the end of the Original Post.
Just extract the parted binary manually and then copy and paste it to the /system/bin folder with any File Explorer with Root access. After you paste the binary you will need to set the permissions to the parted binary you pasted to rwxr-xr-x or (0755). You can do this to any device you have and run it either in Terminal Emulator and even via ADB on your computer. Really handy to have sometimes.
Once you get the debrick image, below are two guides that I saved in my subscriptions that may help you. You may have them already.
deBricker
gTan64
---------- Post added at 05:31 AM ---------- Previous post was at 05:29 AM ----------
Actually this is an entirely different topic from Debricking a phone and on yours, you have a bad ESN. With that I can not help. If the previous owner ( or seller in your case ) "maybe" did not pay his bill, then your phone is locked out until it is released from his/her account by Sprint. If there is a way around this, I may not know.
I had this happen to me once before with my wife's Sprint SGS4. It was a pain but eventually two days later the seller finally came through and the phone was released for activation.
You should start a separate thread to see if you can get the right help and not get your question lost in this thread. I am sorry I couldn't help you any further.
Click to expand...
Click to collapse
Dark Angel you misunderstood my message i don't have bad esn. I lost esn number or corrupt it with dfs cdma tool. Dfs shows my esn but status from efs shows cps_na error. I didn't bought this phone second hand. My cousin send it from USA and she bought it new.
Thanks and i am waiting for your reply.
Off Topic Post / Misunderstanding .....
ashikrobi said:
Dark Angel you misunderstood my message i don't have bad esn. I lost esn number or corrupt it with dfs cdma tool. Dfs shows my esn but status from efs shows cps_na error. I didn't bought this phone second hand. My cousin send it from USA and she bought it new.
Thanks and i am waiting for your reply.
Click to expand...
Click to collapse
Yes I know, please disregard the quote and answer from the previous person responding above my post, right after the pictures I posted ( you will see the quote ). It was an off topic post and the forum combined them for some reason in the response for you ( probably because they were so close in time frame when I posted ) ..... I tried separating them in different posts but it still combined them together.
That is why off topic posts should be posted in a new thread/topic to avoid confusion......
DarkAngel said:
Yes I know, please disregard the quote and answer from the previous person responding above my post, right after the pictures I posted ( you will see the quote ). It was an off topic post and the forum combined them for some reason in the response for you ( probably because they were so close in time frame when I posted ) ..... I tried separating them in different posts but it still combined them together.
That is why off topic posts should be posted in a new thread/topic to avoid confusion......
Click to expand...
Click to collapse
Wow!!! Dark Angel, you are the man i was looking for. You know linux like a pro. Linux is my favorite operating system. I didn't know parted was available for android also. How do you learn these things?
By the way sorry, i though your message about bad esn was for me.
Thanks
ashikrobi said:
Wow!!! Dark Angel, you are the man i was looking for. You know linux like a pro. Linux is my favorite operating system. I didn't know parted was available for android also. How do you learn these things?
By the way sorry, i though your message about bad esn was for me.
Thanks
Click to expand...
Click to collapse
Well not a Pro..... I still have much more to learn but Linux is my favorite OS to use for anything Android related. A lot I still do on Windows.
Debrick Image......
Okay try this image.......
I burnt this image several time over on a class 4, 8 gig card and it wrote the image on it perfect. I don't know if you will have to use a 16gig card for your Mega or not but try what you have 16 gig or less. Trial and error at this point.
You can probably add more to it if need be from the Official Firmware by dragging and dropping ( if I am not mistaken ) by just opening ( and not extracting ) the tar.md5 with WinRAR or 7zip. I can't remember if one was able to do this.......
L600 Debrick Image
Not working
DarkAngel said:
Okay try this image.......
I burnt this image several time over on a class 4, 8 gig card and it wrote the image on it perfect. I don't know if you will have to use a 16gig card for your Mega or not but try what you have 16 gig or less. Trial and error at this point.
You can probably add more to it if need be from the Official Firmware by dragging and dropping ( if I am not mistaken ) by just opening the tar.md5 with WinRAR or 7zip. I can't remember.
L600 Debrick Image
Click to expand...
Click to collapse
DarkAngel I wrote the img file to a 16gb sdcard and tried to boot my phone but it's not working. I waited 5 min and tried several times. I also used a usbjig to boot into download mode but failed.
Have a look these terminal output:
sudo dd if=/home/tails/Downloads/debrick.img of=/dev/sdc
174080+0 records in
174080+0 records out
89128960 bytes (89 MB) copied, 75.5075 s, 1.2 MB/s
[email protected]:~/Downloads$ sudo parted /dev/sdc print
Error: Invalid argument during seek for read on /dev/sdc
Retry/Ignore/Cancel? Ignore
Error: The backup GPT table is corrupt, but the primary appears OK, so that will be used.
OK/Cancel? ok
Backtrace has 8 calls on stack:
8: /lib/i386-linux-gnu/libparted.so.0(ped_assert+0x29) [0xb773ad19]
7: /lib/i386-linux-gnu/libparted.so.0(+0x4649c) [0xb777749c]
6: /lib/i386-linux-gnu/libparted.so.0(ped_disk_new+0x55) [0xb7742275]
5: parted() [0x804ea2b]
4: parted(non_interactive_mode+0x8c) [0x8055c4c]
3: parted(main+0x1970) [0x804d5b0]
2: /lib/i386-linux-gnu/libc.so.6(__libc_start_main+0xf3) [0xb753aa83]
1: parted() [0x804d6e2]
You found a bug in GNU Parted! Here's what you have to do:
Don't panic! The bug has most likely not affected any of your data.
Help us to fix this bug by doing the following:
Check whether the bug has already been fixed by checking
the last version of GNU Parted that you can find at:
http://ftp.gnu.org/gnu/parted/
Please check this version prior to bug reporting.
If this has not been fixed yet or if you don't know how to check,
please visit the GNU Parted website:
http://www.gnu.org/software/parted
for further information.
Your report should contain the version of this release (2.3)
along with the error message below, the output of
parted DEVICE unit co print unit s print
and the following history of commands you entered.
Also include any additional information about your setup you
consider important.
Assertion (last_usable <= disk->dev->length) at ../../../libparted/labels/gpt.c:994 in function _parse_header() failed.
By the way is there any other way to recover from this state? I found qpst finds my phone after installing qhsusb_dload driver. Please help me.
Thanks
You are using an installed version of Linux correct? Are you on 13.04? Well I know the GNU Parted is just the program from Linux but the image still wrote on the SD card.
After the image was written to the SDcard, were you able to see the image content inside? For me it showed about 60MB of actual space written from the 85mb image. After it wrote, I just wrote over it and wrote over it and wrote over it again. Funny thing is I could not see the image at first so I then removed the card from my computer and re-inserted it and was then able to see it. I even inserted it on a Windows 8 tablet I have from a co-worker and it read it fine.
I did this while just using the "Install CD" and trying Ubuntu ( don't have it re-installed yet on my Notebook yet ). I did it using 14.04 LTS though. Try updating your GNU Parted ( your at 2.3 ), if it hasn't already been done, to the most current and re-write the image again.
DarkAngel said:
You are using an installed version of Linux correct? Are you on 13.04? Well I know the GNU Parted is just the program from Linux but the image still wrote on the SD card.
After the image was written to the SDcard, were you able to see the image content inside? For me it showed about 60MB of actual space written from the 85mb image. After it wrote, I just wrote over it and wrote over it and wrote over it again. Funny thing is I could not see the image at first so I then removed the card from my computer and re-inserted it and was then able to see it. I even inserted it on a Windows 8 tablet I have from a co-worker and it read it fine.
I did this while just using the "Install CD" and trying Ubuntu ( don't have it re-installed yet on my Notebook yet ). I did it using 14.04 LTS though. Try updating your GNU Parted ( your at 2.3 ), if it hasn't already been done, to the most current and re-write the image again.
Click to expand...
Click to collapse
Yes i am using an installed version of ubuntu 14.04. I was also not able to view partitions after i wrote the image to sdcard. But after i reinsert the card it showed all partitions and maybe mounted modem partition contents. I could view partitions with windows 7 also.
But when i try to boot the phone with this sdcard nothing happened. I tried several times but failed. What can i do now? DarkAngel please tell me a way to unbrick my phone.
Thanks
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
Hey guys,
unfortunately i think i bricked my prime
Today i flashed crombi-kk rom which worked flawlessly fine. I came from HairyBean 2.31 so all i did was to up update my TWRP via fastboot and then flash the rom. As said, that worked fine. After my first boot of the rom i thought that i would like to test the "F2FS" option. For this i updated TWRP to v2.8 via the zip-file from this thread: http://forum.xda-developers.com/showthread.php?t=2772093 . This also worked and i've got my TWRP to the new version.
Now i wanted to format the /data partition to F2FS so i went to
Wipe>>Advanced Wipe>>Choose Data>>Repair or Change File System>>Change File System>>F2FS
At this time it told me that it can't UNmount the partition and therefore it couldn't change the file-system.
Dumb as i am i thought: "Okay, then why don't just unmount the partition" so i did this (Mount>>Disabled "Data") an then retried to format the data partition with f2fs. During this process i have to assume that something went wrong? It gave me some error which i fool can't remember.
From this point i couldn't access the /data partition anymore, i can't mount it nor can i boot into Android.
I still have access to TWRP and can get to fastboot access. I have no ADB Access in TWRP - it just can't recognize the prime. In Windows-Hardware Manager it just says: Transformer?! (i have universal naked driver installed)
Forget the last sentence - it seems that my USB-Cable is partly broken. Sometimes it recognizes the prime and sometimes not!
Is it gone forever or is there still hope to recover it?
Hopefully someone can help me, i'm really desperate
P.S.: D didn't want to make things worse, so i stopped messing around with it - would it help to reflash the ne0zone75_tf300t.blob file? Is this even possible if i already updated the TWRP to a newer version?
NiffStipples said:
I still have access to TWRP and can get to fastboot access.
Click to expand...
Click to collapse
As long as this is the fact, we don' t call it 'bricked'.
Try following one after another:
1. TWRP>>Wipe>>Advanced>>[check / data]>>repair file system, flash ROM again.
2. Fastboot:
Code:
fastboot -i 0x0b05 erase userdata
- then flash ROM again.
3. Last ressort: Flash stock ROM and start from scratch.
... hope you've pulled your nvflash files. Good luck!
... you might also want to flash another TWRP, though ne0zone75's normally works well. Try the official 2.8.3.0 (for tf300t because you are on Hairy Bean), works good with my prime.
Thanks a lot for your reply
I've tried the steps you provided:
1) While repairing the data partition it said again that it can't mount the data partition. (Picture of it in the attachment)
2) Reflasing the rom worked okay but as expected it couldn't boot (stuck in bootscreen) - in TWRP the /data partiton was again unmountable
3) erasing the userdata via fastboot gave me the following:
Code:
erasing 'userdata'...
FAILED (command write failed (Invalid argument))
finished. total time: 0.002s
At this time i didn't tried to reflash the rom because i don't think it would change anything?!
4) i only have the old nvflash files from ages ago when i started flashing with androwook - i fear they are the wrong ones? I don't have any clue what to do with these - are there good instructions to get the tab back to it's factory state?
Last but not least - do you have a link for the right TWRP you're talking about. I don't want to gave the wrong one a try
NiffStipples said:
Thanks a lot for your reply
I've tried the steps you provided:
1) While repairing the data partition it said again that it can't mount the data partition. (Picture of it in the attachment)
2) Reflasing the rom worked okay but as expected it couldn't boot (stuck in bootscreen) - in TWRP the /data partiton was again unmountable
3) erasing the userdata via fastboot gave me the following:
Code:
erasing 'userdata'...
FAILED (command write failed (Invalid argument))
finished. total time: 0.002s
At this time i didn't tried to reflash the rom because i don't think it would change anything?!
Click to expand...
Click to collapse
Sounds as if partition table is faulty.
1. You could try to redo the Hairy Bean procedure.
2. If you feel lucky, then you could try to format partition manually using
Code:
mkfs.ext4 /dev/block/mmcblk0p8
4) i only have the old nvflash files from ages ago when i started flashing with androwook - i fear they are the wrong ones?
Click to expand...
Click to collapse
nvflash files don't grow sour; you could try without changing to wheelie your blob.bin. If it works, you are safe and can continue with the other blobs.
I don't have any clue what to do with these - are there good instructions to get the tab back to it's factory state?
Click to expand...
Click to collapse
Best instruction you find here: http://forum.xda-developers.com/showthread.php?t=1894867
Last but not least - do you have a link for the right TWRP you're talking about. I don't want to gave the wrong one a try
Click to expand...
Click to collapse
I have actually the (official) one from http://www.techerrata.com/browse/twrp2/tf300t
Good Luck!
Okay, now i know why they always say that flashing is nothing for noobs
I'm a little bit confused - what (in your opinion) is the best shot i should give a try?
Formatting manually (from where? In TWRP or via adb? I'm on Windows)
Reflash everything with NVFLASH (is that possible without any hassle - the NVFLASH files are from ICS-times and i'm on JB/KK?!)
I know it's annoying to help someone who doesn't know what he's doing - hope you have time to get me through this flashing nightmare :/
NiffStipples said:
Okay, now i know why they always say that flashing is nothing for noobs
Click to expand...
Click to collapse
Everybody starts as a noob.
I'm a little bit confused - what (in your opinion) is the best shot i should give a try?
Formatting manually (from where? In TWRP or via adb? I'm on Windows)
Click to expand...
Click to collapse
I would first do that manually from TWRP>>Advanced>>Terminal Command>>Select Folder (root)>>type in: mkfs.ext4 /dev/block/mmcblk0p8
Reflash everything with NVFLASH (is that possible without any hassle - the NVFLASH files are from ICS-times and i'm on JB/KK?!)
Click to expand...
Click to collapse
Important is, that blob.bin works with
Code:
wheelie.exe -r --blob blob.bin
After that you should flash 'bricksafeTF201.img' and 'unlock-token-TF201'. Then you can flash any blobs of unblobbed ROMs you can find in the internet or flash stock ROM (JB). Then proceed to fastboot custom recovery and zipflash custom ROM.
I know it's annoying to help someone who doesn't know what he's doing - hope you have time to get me through this flashing nightmare :/
Click to expand...
Click to collapse
I went through any misstep you can think of with the three of 'em: TF201, TF300T, TF700T.
Mmmmh, the command
Code:
mkfs.ext4 /dev/block/mmcblk0p8
gives me back:
Code:
mkfs.ext4: not found
NiffStipples said:
Mmmmh, the command
Code:
mkfs.ext4 /dev/block/mmcblk0p8
gives me back:
Code:
mkfs.ext4: not found
Click to expand...
Click to collapse
Oops! My bad, try
Code:
make_ext4fs /dev/block/mmcblk0p8
.
.... for information's sake type
Code:
fdisk -l /dev/block/mmcblk0p8
You should get
Code:
Disk /dev/block/mmcblk0p8: 29.6 GB, 29618601984 bytes
4 heads, 16 sectors/track, 903888 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Hooray! :victory: Thanks a lot - everything is back where it belongs
Just for the learning effect - do you have any idea what did go wrong in my case and how would i correctly change the format of the data partition to f2fs? I think i've read a lot of times that this would improve rom speeds a lot?!
NiffStipples said:
Hooray! :victory: Thanks a lot - everything is back where it belongs
Just for the learning effect - do you have any idea what did go wrong in my case and how would i correctly change the format of the data partition to f2fs? I think i've read a lot of times that this would improve rom speeds a lot?!
Click to expand...
Click to collapse
Congrats!
If you would care to tell what you did last, one could make a guess, what went wrong.
... and yes, changing /data (only!) to f2fs makes a tremendous difference in speed. Normally TWRP complies the job without probs. What TWRP do you have now?
I prefer @ne0zone75's which I linked some posts before. They work on all my tabs.
I have installed v2.8.3.0 from the site you gave me above
Mh, as said in the first post i did the following steps to change the format
I tried Wipe>>Advanced Wipe>>Checked "Data">>Repair or Change File System>>Change File System>>Choose F2FS
Then the system gave me an error that it couldn't access the partition because it was mounted or couldn't be unmounted or something like this
So i went back to Mount>>unchecked "Data"
And then again to Advanced Wipe>>...>>Change File System>>F2FS
After that something went wrong because after that step i couldn't mount the data partition anymore?!
NiffStipples said:
I have installed v2.8.3.0 from the site you gave me above
Mh, as said in the first post i did the following steps to change the format
I tried Wipe>>Advanced Wipe>>Checked "Data">>Repair or Change File System>>Change File System>>Choose F2FS
Then the system gave me an error that it couldn't access the partition because it was mounted or couldn't be unmounted or something like this
So i went back to Mount>>unchecked "Data"
And then again to Advanced Wipe>>...>>Change File System>>F2FS
After that something went wrong because after that step i couldn't mount the data partition anymore?!
Click to expand...
Click to collapse
Yes, but what did you to fix it then?
Oh sorry, now i get it
I just used your command for repartitioning(?!?): make_ext4fs /dev/block/mmcblk0p8
I am still of two minds of f2fs on these tablets.. Just gone back to ext4 to compare... As was getting to sticky on the F2fs with redraws and lag..
Anyway good to hear a successful conclusion on the come back by the OP
NiffStipples said:
Oh sorry, now i get it
I just used your command for repartitioning(?!?): make_ext4fs /dev/block/mmcblk0p8
Click to expand...
Click to collapse
Good! Glad, it helped you. Now you could try the 'mkfs.f2fs' command also.
Already tried that - this time it worked without problems :highfive:
Thanks again for the great help!! F2FS brings the prime to a whole new level, now i just have to figure out how to change the dock layout language
NiffStipples said:
Already tried that - this time it worked without problems :highfive:
Thanks again for the great help!! F2FS brings the prime to a whole new level, now i just have to figure out how to change the dock layout language
Click to expand...
Click to collapse
That should be no problem. If you click in dock, there should be a keyboard icon in notification area, clicking it settings dialog will appear. Additional in settings>>language and input>>physical keyboard you can set keyboard layout of dock.
das chaos said:
Oops! My bad, try
Code:
make_ext4fs /dev/block/mmcblk0p8
.
.... for information's sake type
Code:
fdisk -l /dev/block/mmcblk0p8
You should get
Code:
Disk /dev/block/mmcblk0p8: 29.6 GB, 29618601984 bytes
4 heads, 16 sectors/track, 903888 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Click to expand...
Click to collapse
DC,
I wonder if this is why my f2fs where playing up for me?
using your commands I get the following..
Code:
[email protected]:/ $ su
[email protected]:/ # fdisk -l /dev/block/mmcblk0p8
Disk /dev/block/mmcblk0p8: 29.6 GB, 29618601984 bytes
4 heads, 16 sectors/track, 903888 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Disk /dev/block/mmcblk0p8 doesn't contain a valid partition table
[email protected]:/ #
Disk /dev/block/mmcblk0p8 doesn't contain a valid partition table
this is what I am looking at as a problem maybe?
is there a terminal command to see all the partitions and sizes?
I might have to take this thing back to scratch and start again as been flashing left right and center on it of late.
dgcruzing said:
DC,
I wonder if this is why my f2fs where playing up for me?
using your commands I get the following..
Code:
[email protected]:/ $ su
[email protected]:/ # fdisk -l /dev/block/mmcblk0p8
Disk /dev/block/mmcblk0p8: 29.6 GB, 29618601984 bytes
4 heads, 16 sectors/track, 903888 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Disk /dev/block/mmcblk0p8 doesn't contain a valid partition table
[email protected]:/ #
Disk /dev/block/mmcblk0p8 doesn't contain a valid partition table
this is what I am looking at as a problem maybe?
is there a terminal command to see all the partitions and sizes?
I might have to take this thing back to scratch and start again as been flashing left right and center on it of late.
Click to expand...
Click to collapse
No that's normal for f2fs, only fat systems have readable PT. What I was interested was geometry of fs and that is the same as mine. So everything is o.k. You have your tab up and running - that counts.
There is a free app Storage Partitions in the store, which can do no more than show information about partitions. Mainly an exploit of commands
Code:
cat /proc/mounts
and
Code:
cat /proc/partitions
das chaos said:
No that's normal for f2fs, only fat systems have readable PT. What I was interested was geometry of fs and that is the same as mine. So everything is o.k. You have your tab up and running - that counts.
There is a free app Storage Partitions in the store, which can do no more than show information about partitions. Mainly an exploit of commands
Code:
cat /proc/mounts
and
Code:
cat /proc/partitions
Click to expand...
Click to collapse
Used that one and another to have a look..
This is what I get, just for the hell of it..
As said for me.. F2Fs on this one doesn't play nice and the last few days I am back to Ext4..
Running it in and let it settled, putting it through its paces with plenty of tabs in chrome open and multitasking back and forwards in to Tapatalk and it runs normal with out lag and redraws..
I am using apex as a launcher and under F2Fs with kept in memory set..it was redrawing to the max and timing out from coming out of sleep..
Playing with other tweaks to see if can get it to a sweet spot.
Will let it settle for a few days and play then swop back and see which is better with the tweaks added