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 All,
I have purchased a leagoo lead 1 http://www.leagoo.cc/c51181.html (slick design and under 150$) but now I'm trying to get it rooted.
I've tries Kingo root, V Root, Shuame, Towel root, Framaroot and none of it is working.
The phone operates on 4.4.2 with an MTK 6582 processor..
When holding Vol up + power I get a fastboot option though.
Would extracting boot.img and rework it mean something? or has anyone usefull tips?
Thnks in advance.
Check this topic: http://forum.xda-developers.com/showthread.php?t=2783157
Could you throw in some review, particularly WiFi and GSM signal strength, GPS strength, battery? Thanks!
boyanpa said:
Check this topic: http://forum.xda-developers.com/showthread.php?t=2783157
Could you throw in some review, particularly WiFi and GSM signal strength, GPS strength, battery? Thanks!
Click to expand...
Click to collapse
First of all .. I managed to root it.
Needed: Kingosoft Sony bootloader unlocker, Kingosoft one click root, (www.kingoapp.com) Mobile uncle tools
Start sony bootloader unlocker and run it with your phone connected.
It will restart your phone to fastboot and then it remains idle.
Keep your phone plugged in, switch it off and boot manually into the fastboot (power + vol up)
From here the unlocker will proceed unlocking.
Step 1 done.
Now open kingosoft root connect the phone and let it do its thing.
At restart of the phone kingosoft will show on screen a message like "checking root status"
Launch mtk uncle and enter engineer mode.
Go to log and debugging tab ans select user2root
Select Root.
Now kingosoft will tell you that root is succesfull and restarts the phone.
That's that. Phone is rooted. For recovery see the posts 22 and 24 from Vampirefo who did the real hard work in creating 2 flavours of recovery. [emoji106][emoji106]
Non linux users can also flash the img through MTK uncle from sdcard if that doesn't work. See post 40 for flashing recovery via SP tools
The phone runs smooth on what seems to be Yun Os aka Aliyun. Gapps and all android functionalities are working well. At first it seemed that the WIFI reception was poor but with an OTA update seems this has been fixed.
Only trouble I have is getting a GPS fix. It does see 11-13 sattelites but I'm unable to get a proper fix on it. Also the EPO function is not acessible from 4.4.2 . so now with root I'm trying to inject the GPS.CONF file into system/etc and see if it gets a fix or not.
For the time I've been playing around with it... it seems a pretty decent phone with a good response for a reasonable price.
de vetnek said:
First of all ..Looks like I (accidentaly) managed to root it.
Needed: Kingosoft Sony bootloader unlocker, Kingo soft one click root, Mobile uncle tools
I Downloaded from kingosoft the sony bootloader unlocker.
It puts the phone in fastboot mode and then it hangs. I unplugged my phone, switch it off (keep the unlocker running) and manually booted into fastboot (vol up+power) the bootloader unlocker then proceeded untill finished.
Next I installed this root tool and started it while the phone was still in the fastboot mode. after a couple of restarts it says checking for Root, then I decided to start MTK uncle tools and scroll to "log and debugging" and select User2Root. then clicked Root and all of a sudden the phone was sucessfully rooted.. Smiling Smiling I don't know what exactly sparked the root access but It's rooted and works!
If anyone can reproduce this in a correct order. please feel free to share.
The phone runs smooth on what seems to be Yun Os aka Aliyun. Gapps and all android functionalities are working well. At first it seemed that the WIFI reception was poor but with an OTA update seems this has been fixed.
Only trouble I have is getting a GPS fix. It does see 11-13 sattelites but I'm unable to get a proper fix on it. Also the EPO function is not acessible from 4.4.2 . so now with root I'm trying to inject the GPS.CONF file into system/etc and see if it gets a fix or not.
For the time I've been playing around with it... it seems a pretty decent phone with a good response for a reasonable price.
Click to expand...
Click to collapse
You state you next installed this root tool, what is this root tool? a link to tool would be nice.
vampirefo said:
You state you next installed this root tool, what is this root tool? a link to tool would be nice.
Click to expand...
Click to collapse
http://www.kingoapp.com/ :angel:
Also found the solution for the GPS.
In Engineer mode, Switch AGPS from User plane to Control plane.
de vetnek said:
http://www.kingoapp.com/ :angel:
Also found the solution for the GPS.
In Engineer mode, Switch AGPS from User plane to Control plane.
Click to expand...
Click to collapse
Thanks, GPS was working great on my phone out of box.
vampirefo said:
Thanks, GPS was working great on my phone out of box.
Click to expand...
Click to collapse
Mine wasn't but probably due to a factory reset from recovery? OR it wasn't fit yet to see the dutch sky
Managed to root the thing?
Yes mine is rooted also, Similar to the way you rooted yours.
I used Linux and wine to run the bootloader tool from there, I had to use another tool to get temp root, then I pushed su and set permissions.
The bootloader tool you used works via wine but the root tool doesn't.
Sent from my Leagoo Lead1 via taptak.
So we can carefully state that the (accidental) rooting method works.
Btw. I figured out that /system is ro and not rw
Also with adbd insecure it remains ro. Means it has to be scripted to rw at every boot or.... Can try to run framaroot exploit.
System is supposed to be ro this is normal, to get rw add busybox and then remount rw.
Also you can edit the boot.img and make a insecure boot.img and flash, I have done this myself, this enables adb remount, you can add a script to /system/xbin, to force rw or ro.
I wouldn't want rw all this time, as this can cause instability use ro until you need rw, es filemanger with root also allows you to mount system rw as needed.
Added some pics of phone showing it's rooted.
http://postimg.org/gallery/6ol04a9i/
Sent from my Leagoo Lead1 via taptak.
Check
Noticed that the 1GB Rom quickly runs full if you are not keen on the installation location of apps.
Facebook though can't be moved to SD card.
libvc1dec.sa.ca7.so has text relocations . This is wasting memory and is a security risk. please fix
I have been able to hack through recovery, I now have root in recovery mode, so can do backups and restore, dual boot and should be able to increase the size of data partition.
Code:
[email protected]:~/Desktop$ adb devices
List of devices attached
0123456789ABCDEF recovery
[email protected]:~/Desktop$ adb shell
/system/bin/sh: /system/etc/mkshrc[9]: getprop: not found
/system/bin/sh: /system/etc/mkshrc[10]: id: not found
@android:/ #
vampirefo said:
I have been able to hack through recovery, I now have root in recovery mode, so can do backups and restore, dual boot and should be able to increase the size of data partition.
Code:
[email protected]:~/Desktop$ adb devices
List of devices attached
0123456789ABCDEF recovery
[email protected]:~/Desktop$ adb shell
/system/bin/sh: /system/etc/mkshrc[9]: getprop: not found
/system/bin/sh: /system/etc/mkshrc[10]: id: not found
@android:/ #
Click to expand...
Click to collapse
Below shows data is now 4GB, as I am running data from sdcard, I can of course make data any size I want, only limited by size of sdcard, I think this phone supports 64GB, so data could be 64GB.
Code:
[email protected]:/ # busybox df -h
Filesystem Size Used Available Use% Mounted on
tmpfs 481.6M 128.0K 481.4M 0% /dev
none 481.6M 12.0K 481.5M 0% /sys/fs/cgroup
tmpfs 481.6M 0 481.6M 0% /mnt/secure
tmpfs 481.6M 0 481.6M 0% /mnt/asec
tmpfs 481.6M 0 481.6M 0% /mnt/obb
/[email protected] 885.8M 819.2M 66.6M 92% /system
/dev/block/mmcblk1p3 4.0G 999.8M 2.8G 26% /data
/[email protected] 123.0M 4.1M 119.0M 3% /cache
/[email protected]_f 8.8M 4.1M 4.8M 46% /protect_f
/[email protected]_s 8.8M 4.1M 4.8M 46% /protect_s
/dev/block/loop0 1.5M 1.5M 0 100% /mnt/cd-rom
I use Vocano support MTK chipset root but not done, VOcano have support new version, you can test, good luck
tunglethanh90 said:
I use Vocano support MTK chipset root but not done, VOcano have support new version, you can test, good luck
Click to expand...
Click to collapse
No ideal what you are saying, Have you rooted your leagoo lead1? if so by what? what is VOcano? Post more details, you say you root but not done, what does that mean?
Hacking through the recovery is a bit out of my league.
Is there a tut how to do this on a windows machine?
Another way I could think of is to create an ext2 partition (with an external program) on the SD card and use link2SD to utilize that as internal memory.
But I'm open for smarter ways of doing so.
de vetnek said:
Hacking through the recovery is a bit out of my league.
Is there a tut how to do this on a windows machine?
Another way I could think of is to create an ext2 partition (with an external program) on the SD card and use link2SD to utilize that as internal memory.
But I'm open for smarter ways of doing so.
Click to expand...
Click to collapse
There isn't a tut for Linux, so I doubt there is one for Windows, hacking comes from one's mind, lol. If link2SD works for you that would be just fine.
My method requires pulling stock recovery from phone unpacking recovery, adding adb support adding busybox support repacking stock recovery then flash to phone.
From the repacked recovery, full access to phone is possible, dual booting, running from phone from sdcard, creating and restoring backups.
vampirefo said:
There isn't a tut for Linux, so I doubt there is one for Windows, hacking comes from one's mind, lol. If link2SD works for you that would be just fine.
My method requires pulling stock recovery from phone unpacking recovery, adding adb support adding busybox support repacking stock recovery then flash to phone.
From the repacked recovery, full access to phone is possible, dual booting, running from phone from sdcard, creating and restoring backups.
Click to expand...
Click to collapse
Things just got worse hehe.. Did the whole link2sd thing and linked a couple of apps and voila. playstore, facebook, whatsapp gone.. and nowhere to be found back........... doubting whether a factory reset would fix the thing? So in short.... nope.. link2SD does not work.
wouldn't posting the repacked recovery and flashing it to another phone be possible?
Yes the recovery can be flashed on another rooted tablet, but there is more to getting data on sdcard that just flashing a recovery.
I just now modified cwm recovery to work on leagoo lead1, cwm recovery is bigger than my packed stock recovery, but I am able to squeeze in it, lol.
In Utopia..... This would be a good solution for the Leagoo too
http://forum.xda-developers.com/showthread.php?t=2020677
Don't know exactly how they fixed it.. but..... there you also went from 1 to 2.5 GB internal...
[Q] stock unrooted at&t sgh-i777 stuck in boot loop. can I pull contacts, sms, memos
Hello folks,
I have a stock, unrooted AT&T SGH-i777 which is stuck in a 'boot loop' - on power on, I see 'Samsung Galaxy SII' blink infinitely.
The good news is that I can go into download mode as well as recovery mode. I can also connect via adb from my win7 machine.
I was able to pull camera files (pics/vids) from /sdcard/DCIM and whatsapp data (/sdcard/WhatsApp/) using adb pull.
I want to backup (or pull) my contact and sms data (it wasn't synced on phone) as well. However I'm not able to. Do I need to root the phone to use adb for this? If so, how do I root the phone?
Alternatively is there is another way to restore the phone to working condition without losing my contacts and sms data?
I tried rooting it using the 'Easy Rooting Toolkit' v2.0 by DooMLoRD modified by Max Lee @ GalaxyS2Root.com but the runme.bat starts adb and then hangs there indefinitely.
Any help would be appreciated.
Thank you,
Hammad.
...Whether this works on an Unrooted device, I am not sure, but the goal is to install custom firmware onto a stock device without formatting the data partition (where your sms/contacts/other data are kept)...
Use desktop ODIN to flash a custom kernel/recovery
perform a nandroid backup (via custom kernel/recovery)**
install Samsung-based firmware (cooked or shostock) via custom recovery***
**creates a snapshot of the nand memory module, where everything is stored. Once a working setup is established, Titanium backup (among other tools) can extract contacts, wifi settings, sms & mms messages, etc from this nandroid backup even if you have to conduct a factory reset, in the process of restoring the device.
***this "dirty flash" approach which will hopefully allow you to boot into the device, and backup what you need.
This process has been used recently in a similar scenario, and is fully detailed in another thread:
http://forum.xda-developers.com/galaxy-s2-att/help/phone-wont-boot-to-restore-deleted-file-t2827622
-Cyril
hsophie said:
Hello folks,
I have a stock, unrooted AT&T SGH-i777 which is stuck in a 'boot loop' - on power on, I see 'Samsung Galaxy SII' blink infinitely.
The good news is that I can go into download mode as well as recovery mode. I can also connect via adb from my win7 machine.
I was able to pull camera files (pics/vids) from /sdcard/DCIM and whatsapp data (/sdcard/WhatsApp/) using adb pull.
I want to backup (or pull) my contact and sms data (it wasn't synced on phone) as well. However I'm not able to. Do I need to root the phone to use adb for this? If so, how do I root the phone?
Alternatively is there is another way to restore the phone to working condition without losing my contacts and sms data?
I tried rooting it using the 'Easy Rooting Toolkit' v2.0 by DooMLoRD modified by Max Lee @ GalaxyS2Root.com but the runme.bat starts adb and then hangs there indefinitely.
Any help would be appreciated.
Thank you,
Hammad.
Click to expand...
Click to collapse
Thank you Cyril279 for your response. I had a few questions/clarifications since I'm a complete newbie when it comes to flashing/ROMs/rooting/android:
My Android version is Gingerbread 2.3.x. I never upgraded it since I bought it in mid Feb 2012.
cyril279 said:
...Whether this works on an Unrooted device, I am not sure, but the goal is to install custom firmware onto a stock device without formatting the data partition (where your sms/contacts/other data are kept)...
Click to expand...
Click to collapse
I'm new to this stuff so I want to make sure that I state things correctly. By unrooted, I mean my device has never ever been rooted. It is stock in all ways from AT&T. Does that change anything?
cyril279 said:
Use desktop ODIN to flash a custom kernel/recovery
perform a nandroid backup (via custom kernel/recovery)**
install Samsung-based firmware (cooked or shostock) via custom recovery***
**creates a snapshot of the nand memory module, where everything is stored. Once a working setup is established, Titanium backup (among other tools) can extract contacts, wifi settings, sms & mms messages, etc from this nandroid backup even if you have to conduct a factory reset, in the process of restoring the device.
***this "dirty flash" approach which will hopefully allow you to boot into the device, and backup what you need.
This process has been used recently in a similar scenario, and is fully detailed in another thread:
http://forum.xda-developers.com/galaxy-s2-att/help/phone-wont-boot-to-restore-deleted-file-t2827622
-Cyril
Click to expand...
Click to collapse
I read through the thread that you linked to. I want to make sure I understand what I need to do is in:
A. message #5: get ODIN and siyah kernels.
Questions: The Siyah website says that the kernel is for i9100 on JB. Should I still use that one even though my phone is the SGH-I777 and on Gingerbread? Will this upgrade the kernel to JellyBean?
B. message #7: do steps 1,2,3,6,7; (skip 4,5).
Question: Step 6 states '...rooted android'. My phone is not rooted. Will it get rooted as part of A?
Thank you for your patience with me.
Hammad.
Hey guys I'm looking for help with the same issue.. If I had twrp or cwm I'd be good but this phone is my daughters and has not been brought over to the dark side..
This is the problem. Yesterday she came to me and her phone was bootlooping the samsung logo. So I've tried to pull the battery, master reset and call att with no luck. :thumbdown:
I'm wondering since I'm in bootloop and no custom recovery can I maybe flash a custom rom or stock rom to this with the same method..
Thanks Any advice is well appreciated...
I need to get this fixed ASAP. My daughter is two young to be home alone with no phone.....
Sent from my SM-G900A using Xparent BlueTapatalk 2
In this case, we are only using the recovery portion of the kernel, so it doesn't matter that it's for an i9100. There are other .tar versions that are designed specifically for the i777, I just didn't search for them.
I haven't tried this procedure on a never-rooted device, but I expect that it works. Perhaps one of our peers will chime in if they know better, otherwise if you're willing to wait a couple days, I will try the complete procedure out on my own i777, starting from gingerbread.
As long as you can get into download mode, and you DO NOT perform a factory reset, then the prognosis for data recovery is good.
In the meantime, in may be helpful to familiarize yourself with the use of desktop odin.
-Cyril
hsophie said:
Thank you Cyril279 for your response. I had a few questions/clarifications since I'm a complete newbie when it comes to flashing/ROMs/rooting/android:
My Android version is Gingerbread 2.3.x. I never upgraded it since I bought it in mid Feb 2012.
I'm new to this stuff so I want to make sure that I state things correctly. By unrooted, I mean my device has never ever been rooted. It is stock in all ways from AT&T. Does that change anything?
I read through the thread that you linked to. I want to make sure I understand what I need to do is in:
A. message #5: get ODIN and siyah kernels.
Questions: The Siyah website says that the kernel is for i9100 on JB. Should I still use that one even though my phone is the SGH-I777 and on Gingerbread? Will this upgrade the kernel to JellyBean?
B. message #7: do steps 1,2,3,6,7; (skip 4,5).
Question: Step 6 states '...rooted android'. My phone is not rooted. Will it get rooted as part of A?
Thank you for your patience with me.
Hammad.
Click to expand...
Click to collapse
---------- Post added at 04:51 PM ---------- Previous post was at 04:47 PM ----------
"master reset"? = factory reset?
If so, then you're not worried about the recovery of any data, and the easiest path is to use desktop Odin to flash the stock i777UCMD8 firmware onto your I777. That firmware can be found here:
http://forum.xda-developers.com/showpost.php?p=20229527&postcount=46
JEZZEJAMEZ said:
Hey guys I'm looking for help with the same issue.. If I had twrp or cwm I'd be good but this phone is my daughters and has not been brought over to the dark side..
This is the problem. Yesterday she came to me and her phone was bootlooping the samsung logo. So I've tried to pull the battery, master reset and call att with no luck. :thumbdown:
I'm wondering since I'm in bootloop and no custom recovery can I maybe flash a custom rom or stock rom to this with the same method..
Thanks Any advice is well appreciated...
I need to get this fixed ASAP. My daughter is two young to be home alone with no phone.....
Sent from my SM-G900A using Xparent BlueTapatalk 2
Click to expand...
Click to collapse
cyril279 said:
In this case, we are only using the recovery portion of the kernel, so it doesn't matter that it's for an i9100. There are other .tar versions that are designed specifically for the i777, I just didn't search for them.
I haven't tried this procedure on a never-rooted device, but I expect that it works. Perhaps one of our peers will chime in if they know better, otherwise if you're willing to wait a couple days, I will try the complete procedure out on my own i777, starting from gingerbread.
As long as you can get into download mode, and you DO NOT perform a factory reset, then the prognosis for data recovery is good.
In the meantime, in may be helpful to familiarize yourself with the use of desktop odin.
-Cyril
Click to expand...
Click to collapse
Thank you once again Cyril279. I'll familiarize myself with ODIN. I'm not in a hurry since I have a replacement phone. I just want to make sure I can get my data and restore my device. Where can I find kernel for i777?
Hammad.
Thanks, my wife is all over my azz. School is about to start, with our busy schedules she's(daughter) home alone alot. As many others we don't have a land phone.. ...
Sent from my SM-G900A using Xparent BlueTapatalk 2
hsophie said:
Where can I find kernel for i777?
Click to expand...
Click to collapse
Siyah for 2.3.x. There is a tar version.
hsophie said:
Thank you Cyril279 for your response. I had a few questions/clarifications since I'm a complete newbie when it comes to flashing/ROMs/rooting/android:
My Android version is Gingerbread 2.3.x. I never upgraded it since I bought it in mid Feb 2012.
I'm new to this stuff so I want to make sure that I state things correctly. By unrooted, I mean my device has never ever been rooted. It is stock in all ways from AT&T. Does that change anything?
Click to expand...
Click to collapse
No, that does not change anything for this excersize.
hsophie said:
I read through the thread that you linked to. I want to make sure I understand what I need to do is in:
A. message #5: get ODIN and siyah kernels.
Questions: The Siyah website says that the kernel is for i9100 on JB. Should I still use that one even though my phone is the SGH-I777 and on Gingerbread? Will this upgrade the kernel to JellyBean?
Click to expand...
Click to collapse
The initial kernel flash (step 1) is only for the custom recovery. It will be overwritten by a more appropriate kernel later, when we flash the firmware.
Regarding kernel choice, there are usually two major considerations: what device, and what firmware version is it designed for. An i9100 kernel will boot an i777 into recovery without issue. Since this process won't be using the initial kernel to boot into android, we are not limited to specific versions of i9100 or i777 kernels. We only need to find a .tar version for use with desktop Odin.
--that said--
If you do use an i777 version that is designed for android 2.3.x (thanks @creepyncrawly), then you have the option of booting into Android once the kernel is flashed.
hsophie said:
B. message #7: do steps 1,2,3,6,7; (skip 4,5).
Question: Step 6 states '...rooted android'. My phone is not rooted. Will it get rooted as part of A?
[...]
Click to expand...
Click to collapse
Desktop Odin uses root-level access to install firmware (whether stock or custom), so establishing root-access prior, or as a separate step is not necessary when using this method to install custom firmware.
Our process will be different than that shown in message #7, since we are not trying to manually repair the system. We will be attempting the dirty-flash method which involves the first few steps of message #7, and more from message #11.
Process:
0.5) Save custom Samsung-based firmware (cooked v2.2 or shostock3) onto internal memory or sdcard
1) Use desktop Odin to flash Siyah kernel
^^ Installs a kernel/recovery that will allow you to perform a nandroid backup, and flash firmware.
^^This WILL change the initial boot screen (can be corrected later, but does not affect the function of the firmware), and will notch the flash counter (simply doesn't matter).
2) Boot to recovery
3) Create nandroid backup
^^ If things go sideways, you have a snapshot of where you are. If you have to start from scratch, there are apps that can restore Apps, settings, and more, from a backup.
4) Install custom Samsung-based Firmware
^^ Restores the original file-system, without overwriting the /data partition.
5) Attempt boot into android
-Success?
Thank you for your detailed response Cyril279.
For confirmation, I will:
0. use the shostock3 v2.3a firmware from here. I'm assuming that getting it onto the device will require connecting via adb, use adb shell to mkdir and then push the unzipped contents to a directory such as /sdcard/shostock3v23a/
1a. install Desktop ODIN 1.85 or 3.07.
b. use Odin to flash the Siyah-v2.6.14-att.tar mentioned by creepyncrawly [have to read how to do this]
2. boot to recovery
3. create nandroid backup.
Q: Is there a way to exclude the DCIM folder during backup or delete all my pics from the camera before backup since I already have backed all content from /sdcard/DCIM (camera). It was 5.5gb? I'm also assuming that the backup will be created on the phone itself so it has to have enough space on it to hold the backup.
4. Install shostock3 v2.3a [have to read how to do this]
5. hopefully boot successfully into my phone.
cyril279 said:
Process:
0.5) Save custom Samsung-based firmware (cooked v2.2 or shostock3) onto internal memory or sdcard
1) Use desktop Odin to flash Siyah kernel
^^ Installs a kernel/recovery that will allow you to perform a nandroid backup, and flash firmware.
^^This WILL change the initial boot screen (can be corrected later, but does not affect the function of the firmware), and will notch the flash counter (simply doesn't matter).
2) Boot to recovery
3) Create nandroid backup
^^ If things go sideways, you have a snapshot of where you are. If you have to start from scratch, there are apps that can restore Apps, settings, and more, from a backup.
4) Install custom Samsung-based Firmware
^^ Restores the original file-system, without overwriting the /data partition.
5) Attempt boot into android
-Success?
Click to expand...
Click to collapse
Close, you're close.
Regarding getting the firmware onto the device, the easiest method is to save the files on a micro sd card via PC (formatted as fat32), then insert the card into the device. Otherwise yes, adb push will get it there as well.
0 Use the shostock from the first post of that thread (420mb). The "version 2.3a" that you mention is just a kernel.
1a. install Desktop ODIN 1.85 or 3.07
1b Use Odin to flash the siyah.tar mentioned by creepyncrawly.
desktop Odin use: http://forum.xda-developers.com/showpost.php?p=53669365&postcount=360
2. boot to recovery
3. create nandroid backup.
Don't worry about DCIM, the nandroid does not backup the internal memory partition (aka internal sd card) where your photos are stored.
A factory reset also does not touch this partition. <-- BUT DO NOT FACTORY RESET
You are correct that the backup is stored on the device, so it IS important that there is enough space for the backup.
4. Install shostock3 v4.0 [have to read how to do this]
^^It's fairly straight forward while in recovery. If not, we're here to help.
5. hopefully boot successfully into my phone.
hsophie said:
Thank you for your detailed response Cyril279.
For confirmation, I will:
0. use the shostock3 v2.3a firmware from here. I'm assuming that getting it onto the device will require connecting via adb, use adb shell to mkdir and then push the unzipped contents to a directory such as /sdcard/shostock3v23a/
1a. install Desktop ODIN 1.85 or 3.07.
b. use Odin to flash the Siyah-v2.6.14-att.tar mentioned by creepyncrawly [have to read how to do this]
2. boot to recovery
3. create nandroid backup.
Q: Is there a way to exclude the DCIM folder during backup or delete all my pics from the camera before backup since I already have backed all content from /sdcard/DCIM (camera). It was 5.5gb? I'm also assuming that the backup will be created on the phone itself so it has to have enough space on it to hold the backup.
4. Install shostock3 v2.3a [have to read how to do this]
5. hopefully boot successfully into my phone.
Click to expand...
Click to collapse
Thank you Cyril279 once again.
I started the process last night... have some more questions. Please see below:
cyril279 said:
Close, you're close.
Regarding getting the firmware onto the device, the easiest method is to save the files on a micro sd card via PC (formatted as fat32), then insert the card into the device. Otherwise yes, adb push will get it there as well.
0 Use the shostock from the first post of that thread (420mb). The "version 2.3a" that you mention is just a kernel.
Click to expand...
Click to collapse
For step 0:
I downloaded the full shostock rom as specified. Since I don't have a microSD card available I'm going to copy shostock to the internal sdcard (/sdcard) using adb push.
Do I need to copy the unzipped contents of shostock or just put the single zip file there?
cyril279 said:
1a. install Desktop ODIN 1.85 or 3.07
1b Use Odin to flash the siyah.tar mentioned by creepyncrawly.
desktop Odin use: http://forum.xda-developers.com/showpost.php?p=53669365&postcount=360
2. boot to recovery
3. create nandroid backup.
Don't worry about DCIM, the nandroid does not backup the internal memory partition (aka internal sd card) where your photos are stored.
A factory reset also does not touch this partition. <-- BUT DO NOT FACTORY RESET
You are correct that the backup is stored on the device, so it IS important that there is enough space for the backup.
Click to expand...
Click to collapse
I wanted to make sure I have enough space for step 3 so I connected via adb and checked disk space using df. I get this:
Code:
D:\Program Files (x86)\Android\android-sdk\platform-tools>adb shell df
Filesystem Size Used Free Blksize
/dev 418M 76K 418M 4096
/tmp 418M 56K 418M 4096
/system 503M 472M 31M 4096
/mnt/.lfs: Function not implemented
/cache 246M 4M 241M 4096
/sdcard 11G 8G 3G 32768
Questions:
1. Which filesystem will get backed up from above using nandroid?
2. Do I have enough space given the information above?
3. I wasn't able to figure out whether you can specify where to save your nandroid backup from my research. Does it allow you specify a backup location? [I would want to put it under the /sdcard partition since its got the most space].
cyril279 said:
4. Install shostock3 v4.0 [have to read how to do this]
^^It's fairly straight forward while in recovery. If not, we're here to help.
5. hopefully boot successfully into my phone.
Click to expand...
Click to collapse
Thanks for the encouragement, I'll probably try the process tonight. Will post update once done unless I have other questions.
Hammad.
hsophie said:
[...]
For step 0:
I downloaded the full shostock rom as specified. Since I don't have a microSD card available I'm going to copy shostock to the internal sdcard (/sdcard) using adb push.
Do I need to copy the unzipped contents of shostock or just put the single zip file there?
Click to expand...
Click to collapse
Copy the entire zip file onto the device.
hsophie said:
I wanted to make sure I have enough space for step 3 so I connected via adb and checked disk space using df. I get this:
Code:
D:\Program Files (x86)\Android\android-sdk\platform-tools>adb shell df
Filesystem Size Used Free Blksize
/dev 418M 76K 418M 4096
/tmp 418M 56K 418M 4096
/system 503M 472M 31M 4096
/mnt/.lfs: Function not implemented
/cache 246M 4M 241M 4096
/sdcard 11G 8G 3G 32768
Questions:
1. Which filesystem will get backed up from above using nandroid?
2. Do I have enough space given the information above?
3. I wasn't able to figure out whether you can specify where to save your nandroid backup from my research. Does it allow you specify a backup location? [I would want to put it under the /sdcard partition since its got the most space].
Click to expand...
Click to collapse
1. A nandroid backup will typically backup /system, /data, and /boot(/kernel) partitions (Your partition report is missing a few items). -stock i777 partition table-
2. 3GB is enough for a nandroid
3.Typically, from the first screen of ClockworkMod recovery you would select {backup & restore}, and the submenu will provide options to {backup to internal sdcard} or {backup to external sdcard} (among others)
hsophie said:
Thanks for the encouragement, I'll probably try the process tonight. Will post update once done unless I have other questions.
Hammad.
Click to expand...
Click to collapse
:fingers-crossed:
---------- Post added at 04:13 PM ---------- Previous post was at 03:32 PM ----------
I have never used that shell df command, and I'm not yet sure about all of what it returns, but I certainly got different results when booted into android, than when I was booted into recovery. Were you booted into the stock 3e recovery when you performed the shell df command?
Code:
List of devices attached
001952750d598e recovery
C:\Android\sdk\platform-tools>adb shell df
Filesystem 1K-blocks Used Available Use% Mounted on
tmpfs 404636 136 404500 0% /dev
tmpfs 404636 12 404624 0% /tmp
/dev/block/mmcblk0p7 251968 4276 247692 2% /cache
/dev/block/mmcblk0p11
11901568 6185360 5716208 52% /emmc
/dev/block/mmcblk0p11
11901568 6185360 5716208 52% /and-sec
Code:
List of devices attached
001952750d598e device
C:\Android\sdk\platform-tools>adb shell df
Filesystem Size Used Free Blksize
/dev 395.2M 136.0K 395.0M 4096
/sys/fs/cgroup 395.2M 12.0K 395.1M 4096
/mnt/asec 395.2M 0.0K 395.2M 4096
/mnt/obb 395.2M 0.0K 395.2M 4096
/mnt/fuse 395.2M 0.0K 395.2M 4096
/system 503.9M 320.2M 183.8M 4096
/cache 246.1M 4.2M 241.9M 4096
/efs 19.7M 9.2M 10.5M 4096
/data 2.0G 1.0G 941.5M 4096
/preload 503.9M 293.6M 210.3M 4096
/mnt/media_rw/sdcard0: Permission denied
/mnt/secure/asec: Permission denied
/storage/sdcard0 11.4G 5.9G 5.5G 8192
cyril279 said:
1. A nandroid backup will typically backup /system, /data, and /boot(/kernel) partitions (Your partition report is missing a few items).
I have never used that shell df command, and I'm not yet sure about all of what it returns, but I certainly got different results when booted into android, than when I was booted into recovery. Were you booted into the stock 3e recovery when you performed the shell df command?
Click to expand...
Click to collapse
Yes, I was in the stock 3e recovery when I connected via adb and ran the command. Since I'm not root perhaps its not showing me the /data partition. I can cd into /data but ls doesn't show anything.
I'll send you an update tonight. Thanks for all of your help so far! I really appreciate it.
OK, here is what I did:
1. I wasn't able to copy/push shostock to my phone via adb. I kept getting "failed to copy ? to ?: Read-only file system."
I tried remounting, but it also failed, probably because I don't have root access.
So I've deferred this step to later.
2. I ran ODIN 1.85 desktop, put the phone in ODIN mode and flashed the siyah kernel. ODIN ran successfully and my phone rebooted successfully!
The boot screen shows a yellow triangle and I9100 on it though.
At this point I have access to my phone again. I was able to copy whatsapp history using the guide on their website.
I decided that I'll just sync contacts to google, but lo and behold, I just discovered that wifi isn't working. When I turn it on, it turns off after a few seconds. It doesn't bring up any wifi networks on scan.
Is there a way to make the wifi work again?
Thanks
Hammad.
Update:
1. I copied the shostock ROM through USB/windows
2. I created a nandroid backup from CWMR Touch Recovery onto internal sdcard. I got the following messages on backup:
Code:
SD Card space free: 8645MB
Backing up boot image...
Backing up system...
Backing up data...
[I]No /sdcard/.android_secure found. Skipping backup of applications on external storage.[/I]
Backing up cache...
[I]No sd-ext found. Skipping backup of sd-ext.[/I]
Generating md5 sum...
Backup complete!
Are the two messages in italics a problem?
Update #2:
I decided to install shostock. Installation went smoothly. My wi-fi issue was also resolved with the upgrade and I have Android 4.1.2 on my phone.
Thank you Cyril279 for all of your help on this. I couldn't have done it without your guidance!
hsophie said:
[...]
1. I wasn't able to copy/push shostock to my phone via adb. I kept getting "failed to copy ? to ?: Read-only file system."
I tried remounting, but it also failed, probably because I don't have root access.
So I've deferred this step to later.
Click to expand...
Click to collapse
When I tried the process, as soon as I rebooted to the siyah kernel, I was able to ADB push to the device, but I don't know what command you issued, or what path you chose.
Code:
adb push c:\path\to\file.zip /storage/sdcard0/
Code:
adb push c:\path\to\file.zip /sdcard/
Ultimately this didn't matter since you were able to boot into android, and the file could be copied via USB.
hsophie said:
2. I ran ODIN 1.85 desktop, put the phone in ODIN mode and flashed the siyah kernel. ODIN ran successfully and my phone rebooted successfully!
Click to expand...
Click to collapse
Darn right it did!
Thanks again @creepyncrawly, using this specific kernel made this portion of the process possible.
hsophie said:
The boot screen shows a yellow triangle and I9100 on it though.
Click to expand...
Click to collapse
The method of recovery that we used tripped the device's custom-flash monitor (voids service under warranty). It doesn't affect the functionality of the firmware at all, but if you prefer to have the correct initial boot animation, then you'll need to follow an additional procedure.
http://forum.xda-developers.com/gal...to-restore-deleted-file-t2827622/post54521059
hsophie said:
At this point I have access to my phone again. I was able to copy whatsapp history using the guide on their website.
I decided that I'll just sync contacts to google, but lo and behold, I just discovered that wifi isn't working. When I turn it on, it turns off after a few seconds. It doesn't bring up any wifi networks on scan.
Is there a way to make the wifi work again?
Thanks
Hammad.
Update:
1. I copied the shostock ROM through USB/windows
2. I created a nandroid backup from CWMR Touch Recovery onto internal sdcard. I got the following messages on backup:
Code:
SD Card space free: 8645MB
Backing up boot image...
Backing up system...
Backing up data...
[I]No /sdcard/.android_secure found. Skipping backup of applications on external storage.[/I]
Backing up cache...
[I]No sd-ext found. Skipping backup of sd-ext.[/I]
Generating md5 sum...
Backup complete!
Are the two messages in italics a problem?
Click to expand...
Click to collapse
No they are not a problem at all. Both of those messages are the result of the fact that you simply didn't have an external sd card installed, so it's informing you that it skipped the backup of the cache files there-on. /boot, /system and /data are what really matter.
hsophie said:
Update #2:
I decided to install shostock. Installation went smoothly. My wi-fi issue was also resolved with the upgrade and I have Android 4.1.2 on my phone.
Thank you Cyril279 for all of your help on this. I couldn't have done it without your guidance!
Click to expand...
Click to collapse
Our pleasure, although the process wasn't quite as expected, I'm certainly glad to hear that it worked out.
As mentioned earlier, if the i9100 bootscreen bothers you, then there's another (easier) adventure with your name all over it!
Happy flashing
-Cyril
cyril279 said:
When I tried the process, as soon as I rebooted to the siyah kernel, I was able to ADB push to the device, but I don't know what command you issued, or what path you chose.
Code:
adb push c:\path\to\file.zip /storage/sdcard0/
Code:
adb push c:\path\to\file.zip /sdcard/
Ultimately this didn't matter since you were able to boot into android, and the file could be copied via USB.
-Cyril
Click to expand...
Click to collapse
Just to clarify, I tried adb pushing it before flashing the siyah kernel. The phone wasn't rooted so thats why it didn't work.
My next challenge is to figure out how to copy my calendar to google calendar and then sync it so that it copies to my replacement phone (HTC One M8). I was using the samsung calendar, without it being linked to my google account.
Whatsapp data transfer was a cinch. Just copy the folder to the same location on new phone and install whatsapp and you're done.
I transferred memos from the S2 to M8 but I think the memo files are samsung proprietary format. I'll need to figure out how to transfer that info.
The other issue would be transferring my sms as well.
Any recommendations on tools for this would be appreciated.
Thanks.
Hammad.
hsophie said:
Just to clarify, I tried adb pushing it before flashing the siyah kernel. The phone wasn't rooted so thats why it didn't work.
Click to expand...
Click to collapse
Got it, makes sense.
hsophie said:
My next challenge is to figure out how to copy my calendar to google calendar and then sync it so that it copies to my replacement phone (HTC One M8). I was using the samsung calendar, without it being linked to my google account.
Whatsapp data transfer was a cinch. Just copy the folder to the same location on new phone and install whatsapp and you're done.
I transferred memos from the S2 to M8 but I think the memo files are samsung proprietary format. I'll need to figure out how to transfer that info.
The other issue would be transferring my sms as well.
Any recommendations on tools for this would be appreciated.
Thanks.
Hammad.
Click to expand...
Click to collapse
I can't recommend titanium backup highly enough for backup and restoration of apps and their data -including contacts, calendar content, wifi connections, sms/mms, etc. It might not be able to get the memo data to a different program, but remember, all of this info is captured in your nandroid backup as well, and titanium backup can extract it directly from the nandroid into the new firmware.
-Cyril
cyril279 said:
I can't recommend titanium backup highly enough for backup and restoration of apps and their data -including contacts, calendar content, wifi connections, sms/mms, etc. It might not be able to get the memo data to a different program, but remember, all of this info is captured in your nandroid backup as well, and titanium backup can extract it directly from the nandroid into the new firmware.
-Cyril
Click to expand...
Click to collapse
I could have sworn that I've read on here multiple times that restoring data to apps, even with TIB, results in problematic operations. If I jumped ROMs but had backed up my apps and data with TIB, if I restore the data ONLY in the new ROM, that should be no problem?
Q&A for [TOOL][NABI2] NabiLab - Root, Play, Recovery
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [TOOL][NABI2] NabiLab - Root, Play, Recovery. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
State of Nabi 2 Root as of 12/14?
So I have admittedly been out of the loop on the state of rooting my two Nabi 2s since after I restored them to stock and all back last year when they released the update that included the Gapps. So I've been running stock since then and am on the latest firmware (2.4.6 I believe). All is mostly fine, but I would really like to get the external SD cards to be writable again, and from what I can tell, I need root again to do that.
So...as of today...what is the state (and best procedure) of rooting the Nabi 2 on the latest OTA update? Is Nabi Lab still the best tool? From what I've pieced together from scattered threads, it's looking like possibly use Nabi Lab to install TWRP, and then use that to install the SuperSU (http://forum.xda-developers.com/showthread.php?t=1538053). However, I could likely be wrong...hence why I'm asking.
Eyebolt said:
So I have admittedly been out of the loop on the state of rooting my two Nabi 2s since after I restored them to stock and all back last year when they released the update that included the Gapps. So I've been running stock since then and am on the latest firmware (2.4.6 I believe). All is mostly fine, but I would really like to get the external SD cards to be writable again, and from what I can tell, I need root again to do that.
So...as of today...what is the state (and best procedure) of rooting the Nabi 2 on the latest OTA update? Is Nabi Lab still the best tool? From what I've pieced together from scattered threads, it's looking like possibly use Nabi Lab to install TWRP, and then use that to install the SuperSU (http://forum.xda-developers.com/showthread.php?t=1538053). However, I could likely be wrong...hence why I'm asking.
Click to expand...
Click to collapse
Nabilab will still work as long as you use a version with a Jellybean TWRP(since you are on 2.4.6).
katinatez repackaged it for jellybean here:
http://forum.xda-developers.com/showpost.php?p=48987089&postcount=2088
I've searched high and low and can't find anything. I have nabi2S running KitKat. Every rooting guide I've found is for JB. Is there any way to root the 2S?
Sent from my Nexus 5 using XDA Free mobile app
jaxbierley said:
I've searched high and low and can't find anything. I have nabi2S running KitKat. Every rooting guide I've found is for JB. Is there any way to root the 2S?
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
For the sake of anyone else looking for this information we are discussing it at the main Nabi thread starting at post #2477
http://forum.xda-developers.com/showthread.php?t=1905674&page=248
Stock Restore
Hi
I have downloaded NabiLab, as I am having wifi issues on my updated Nabi2. I unzipped, ran the .bat and chose option 3 (with my nab connected via USB). Nothing happened, no errors etc, the screen flashed up and shut down. Do I need to do something with the Nabi (recovery mode etc), do I need to install anything from NabiLab before trying this? Any help would be appreciated
Firepants said:
Hi
I have downloaded NabiLab, as I am having wifi issues on my updated Nabi2. I unzipped, ran the .bat and chose option 3 (with my nab connected via USB). Nothing happened, no errors etc, the screen flashed up and shut down. Do I need to do something with the Nabi (recovery mode etc), do I need to install anything from NabiLab before trying this? Any help would be appreciated
Click to expand...
Click to collapse
What version of software? Use Nabilab2015 http://forum.xda-developers.com/showpost.php?p=59073456&postcount=2544
It has more diagnostic info. Just be in Android or TWRP with ADb enabled. It also can see if drivers are loaded.
Hacking Nabi2 to Allow Data2SD
I managed today to hack my kids Nabi2 to enable Data2SD. I was to frustrated by the limited space in the tab. My kids were complaining about not being able to add more games. Thus, I decided to take the risk of modifying the mount points of the tab to allow the data partition to point to a partition in a large sdcard, instead of the limited 4.5 GB space in the internal storage.
Warning: I am not responsible of any damage as a result of following the next steps. Always make backups
Note: I have the last update (KitKat) installed in the Nabi2
1- Dump the boot image from an adb shell:
Code:
su
cat /dev/block/platform/sdhci-tegra.3/by-name/LNX > /sdcard/boot.img
2- Open this url http://android-dls.com/wiki/index.php?title=HOWTO:_Unpack,_Edit,_and_Re-Pack_Boot_Images
to see the instructions of how to unpack and repack the boot image. Note that, the splitimage script mentioned in the page can be found at https://gist.github.com/jberkel/1087743
Warning: do not do anything in the tutorial, just wait
3- Format an sdcard as one partition of ext4 type
4- Insert the sdcard in the nabi2
5- Use the tutorial in step 2 to extract the ramdisk contents from the boot image and then Modify the file "fstab.mt799" in the ramdisk folder by replacing the line
Code:
/dev/block/platform/sdhci-tegra.3/by-name/UDA /data ext4 noatime,nosuid,nodev,journal_async_commit,data=writeback,nodelalloc,errors=panic wait,check,encryptable=/dev/block/platform/sdhci-tegra.3/by-name/MDA
with
Code:
/dev/block/platform/sdhci-tegra.0/by-num/p1 /data ext4 noatime,nosuid,nodev,journal_async_commit,data=writeback,nodelalloc,errors=panic wait,check,encryptable=/dev/block/platform/sdhci-tegra.3/by-name/MDA
which switches the data partition mount point to be on the sdcard
and the line
Code:
/devices/platform/sdhci-tegra.0/mmc_host/mmc2 auto vfat defaults voldmanaged=sdcard1:auto
with
Code:
/devices/platform/sdhci-tegra.3/mmc_host/mmc0 auto vfat defaults voldmanaged=sdcard1:12
which mount your old data partition into the directory of the external sdcard
6- Repack the boot image as mentioned in the url in step 2
7- Copy the new boot image to the nabi2 sdcard
8- Once you copied the new boot image (e.g. new_boot.img), replace the current boot image with the new one using adb shell:
Code:
su
cat /sdcard/new_boot.img > /dev/block/platform/sdhci-tegra.3/by-name/LNX
9- Now the kernel is replaced and once you rebooted your external sdcard would be in use, but note that your device is now having an empty data partition on the external sdcard, so you have to setup everything from the beginning. Note also that your previous data partition is now mounted as an sdcard, however, you have to format it from ext4 to fat32 to work as an sdcard (you can do the format from setings->storage->sdcard format)
ashahin1 said:
I managed today to hack my kids Nabi2 to enable Data2SD. I was to frustrated by the limited space in the tab. My kids were complaining about not being able to add more games. Thus, I decided to take the risk of modifying the mount points of the tab to allow the data partition to point to a partition in a large sdcard, instead of the limited 4.5 GB space in the internal storage.
Warning: I am not responsible of any damage as a result of following the next steps. Always make backups
Note: I have the last update (KitKat) installed in the Nabi2
1- Dump the boot image from an adb shell:
Code:
su
cat /dev/block/platform/sdhci-tegra.3/by-name/LNX > /sdcard/boot.img
2- Open this url http://android-dls.com/wiki/index.php?title=HOWTO:_Unpack,_Edit,_and_Re-Pack_Boot_Images
to see the instructions of how to unpack and repack the boot image. Note that, the splitimage script mentioned in the page can be found at https://gist.github.com/jberkel/1087743
Warning: do not do anything in the tutorial, just wait
3- Format an sdcard as one partition of ext4 type
4- Insert the sdcard in the nabi2
5- Use the tutorial in step 2 to extract the ramdisk contents from the boot image and then Modify the file "fstab.mt799" in the ramdisk folder by replacing the line
Code:
/dev/block/platform/sdhci-tegra.3/by-name/UDA /data ext4 noatime,nosuid,nodev,journal_async_commit,data=writeback,nodelalloc,errors=panic wait,check,encryptable=/dev/block/platform/sdhci-tegra.3/by-name/MDA
with
Code:
/dev/block/platform/sdhci-tegra.0/by-num/p1 /data ext4 noatime,nosuid,nodev,journal_async_commit,data=writeback,nodelalloc,errors=panic wait,check,encryptable=/dev/block/platform/sdhci-tegra.3/by-name/MDA
which switches the data partition mount point to be on the sdcard
and the line
Code:
/devices/platform/sdhci-tegra.0/mmc_host/mmc2 auto vfat defaults voldmanaged=sdcard1:auto
with
Code:
/devices/platform/sdhci-tegra.3/mmc_host/mmc0 auto vfat defaults voldmanaged=sdcard1:12
which mount your old data partition into the directory of the external sdcard
6- Repack the boot image as mentioned in the url in step 2
7- Copy the new boot image to the nabi2 sdcard
8- Once you copied the new boot image (e.g. new_boot.img), replace the current boot image with the new one using adb shell:
Code:
su
cat /sdcard/new_boot.img > /dev/block/platform/sdhci-tegra.3/by-name/LNX
9- Now the kernel is replaced and once you rebooted your external sdcard would be in use, but note that your device is now having an empty data partition on the external sdcard, so you have to setup everything from the beginning. Note also that your previous data partition is now mounted as an sdcard, however, you have to format it from ext4 to fat32 to work as an sdcard (you can do the format from setings->storage->sdcard format)
Click to expand...
Click to collapse
If you are not sure which line to change, I have the fstab.mt799 file attached with this post. You can simply replace your file with this one.
ashahin1 said:
I managed today to hack my kids Nabi2 to enable Data2SD. I was to frustrated by the limited space in the tab. My kids were complaining about not being able to add more games. Thus, I decided to take the risk of modifying the mount points of the tab to allow the data partition to point to a partition in a large sdcard, instead of the limited 4.5 GB space in the internal storage.
Warning: I am not responsible of any damage as a result of following the next steps. Always make backups
Note: I have the last update (KitKat) installed in the Nabi2
1- Dump the boot image from an adb shell:
Code:
su
cat /dev/block/platform/sdhci-tegra.3/by-name/LNX > /sdcard/boot.img
2- Open this url http://android-dls.com/wiki/index.php?title=HOWTO:_Unpack,_Edit,_and_Re-Pack_Boot_Images
to see the instructions of how to unpack and repack the boot image. Note that, the splitimage script mentioned in the page can be found at https://gist.github.com/jberkel/1087743
Warning: do not do anything in the tutorial, just wait
3- Format an sdcard as one partition of ext4 type
4- Insert the sdcard in the nabi2
5- Use the tutorial in step 2 to extract the ramdisk contents from the boot image and then Modify the file "fstab.mt799" in the ramdisk folder by replacing the line
Code:
/dev/block/platform/sdhci-tegra.3/by-name/UDA /data ext4 noatime,nosuid,nodev,journal_async_commit,data=writeback,nodelalloc,errors=panic wait,check,encryptable=/dev/block/platform/sdhci-tegra.3/by-name/MDA
with
Code:
/dev/block/platform/sdhci-tegra.0/by-num/p1 /data ext4 noatime,nosuid,nodev,journal_async_commit,data=writeback,nodelalloc,errors=panic wait,check,encryptable=/dev/block/platform/sdhci-tegra.3/by-name/MDA
which switches the data partition mount point to be on the sdcard
and the line
Code:
/devices/platform/sdhci-tegra.0/mmc_host/mmc2 auto vfat defaults voldmanaged=sdcard1:auto
with
Code:
/devices/platform/sdhci-tegra.3/mmc_host/mmc0 auto vfat defaults voldmanaged=sdcard1:12
which mount your old data partition into the directory of the external sdcard
6- Repack the boot image as mentioned in the url in step 2
7- Copy the new boot image to the nabi2 sdcard
8- Once you copied the new boot image (e.g. new_boot.img), replace the current boot image with the new one using adb shell:
Code:
su
cat /sdcard/new_boot.img > /dev/block/platform/sdhci-tegra.3/by-name/LNX
9- Now the kernel is replaced and once you rebooted your external sdcard would be in use, but note that your device is now having an empty data partition on the external sdcard, so you have to setup everything from the beginning. Note also that your previous data partition is now mounted as an sdcard, however, you have to format it from ext4 to fat32 to work as an sdcard (you can do the format from setings->storage->sdcard format)
Click to expand...
Click to collapse
If you don't have the time to do all these steps, I have the modified boot file attached here.
Yo can either follow steps 7 and 8 above to write it, or use the fastboot command as follows:
Code:
fastboot flash boot new_boot.img
Nabi2 not found
Hi, I purchased a reconditioned Nabi, which was reset back to stock. The wifi worked fine, until I updated it through the tablet. I am now on version 2.0 with no wifi. I have tried various options through NabiLab , however my Nabi is not recognised as being connected (although windows picks it up). Please help!
Swipe to restore
I am trying to return my nabi to stock, i can get to the screen that asks you to 'swipe to restore' but the screen is not responding. I dont have issues with the touchscreen normally
Aytul said:
I am trying to return my nabi to stock, i can get to the screen that asks you to 'swipe to restore' but the screen is not responding. I dont have issues with the touchscreen normally
Click to expand...
Click to collapse
That's weird...if you keep messing with it you may find a spot a little left, right, higher, or lower where you can grab the button to swipe....or you try to re-flash TWRP or maybe there's a new version of TWRP for your particular nabi software version.
did you ever get nabilab to see it? did you check the device manager to see if it was totally recognized? Are developer options enabled?
n3wt said:
That's weird...if you keep messing with it you may find a spot a little left, right, higher, or lower where you can grab the button to swipe....or you try to re-flash TWRP or maybe there's a new version of TWRP for your particular nabi software version.
did you ever get nabilab to see it? did you check the device manager to see if it was totally recognized? Are developer options enabled?
Click to expand...
Click to collapse
The Nabi is showing as a device, it's responds as it should up to the point of TWRP. I had to repeatedly press buttons to get to the restore swipe and have tried many times, unsuccessfully. Where do I enable developer options?
I am on version 2 (Nabi) and using the most up-to-date version of NabiLab. I am trying to restore to stock so that the software version goes back, as the update has stopped my wifi working. Even a factory reset doesn't take the Nabi software back further than v2.0
Aytul said:
The Nabi is showing as a device, it's responds as it should up to the point of TWRP. I had to repeatedly press buttons to get to the restore swipe and have tried many times, unsuccessfully. Where do I enable developer options?
I am on version 2 (Nabi) and using the most up-to-date version of NabiLab. I am trying to restore to stock so that the software version goes back, as the update has stopped my wifi working. Even a factory reset doesn't take the Nabi software back further than v2.0
Click to expand...
Click to collapse
For developer options you go to settings, scroll all the way down, if you don't see "Developer options" there, press About tablet, then repeatedly tap build number until it pops up and says "You are now a developer!", then go back and now you should see the Developer options menu item, press it and then make sure it's on at the top and that the USB Debugging option is checked.....then try nabilab again.
n3wt said:
For developer options you go to settings, scroll all the way down, if you don't see "Developer options" there, press About tablet, then repeatedly tap build number until it pops up and says "You are now a developer!", then go back and now you should see the Developer options menu item, press it and then make sure it's on at the top and that the USB Debugging option is checked.....then try nabilab again.
Click to expand...
Click to collapse
Yes this is enabled, as without it I am unable to run nabilab etc. The problem is TWRP & the version of software I am running on the tablet?
Aytul said:
Yes this is enabled, as without it I am unable to run nabilab etc. The problem is TWRP & the version of software I am running on the tablet?
Click to expand...
Click to collapse
Well, the touch issues are probably due to a bad build of TWRP but not necessarily the wrong one. The problem with nabilab not being able to see the tablet I think has to be drivers. Have you checked device manager to make sure there are no unrecognized things? 'cause the tablet show up as two separate things in there and it sounds like the USB storage part is working but not the adb and/or fastboot part(s).
n3wt said:
Well, the touch issues are probably due to a bad build of TWRP but not necessarily the wrong one. The problem with nabilab not being able to see the tablet I think has to be drivers. Have you checked device manager to make sure there are no unrecognized things? 'cause the tablet show up as two separate things in there and it sounds like the USB storage part is working but not the adb and/or fastboot part(s).
Click to expand...
Click to collapse
I've managed to sort the drivers by installing PDANet, then managed to sort TWRP by installing an older version. I've now updated to 2.1 on the Nabi but no luck with the wifi issue..i'm guessing it's really broken and it happening whilst updating may have been a coincidence?!
Aytul said:
I've managed to sort the drivers by installing PDANet, then managed to sort TWRP by installing an older version. I've now updated to 2.1 on the Nabi but no luck with the wifi issue..i'm guessing it's really broken and it happening whilst updating may have been a coincidence?!
Click to expand...
Click to collapse
It might just be broken but that's a heck of a coincidence... Do you have a backup from before the wifi issue started? If so, I'd try to thoroughly wipe everything but your external sd card and then restoring your backup and see if that helps.
n3wt said:
It might just be broken but that's a heck of a coincidence... Do you have a backup from before the wifi issue started? If so, I'd try to thoroughly wipe everything but your external sd card and then restoring your backup and see if that helps.
Click to expand...
Click to collapse
Hi, I bought it as a reconditioned did unit. Turned it on, updates it (wifi worked) and then had this problem, so no backup to go back to unfortunately
Hello all. hdx 7 was running the original version of safestrap and gapps on the very first firmware. accidently wiped internal and now can only boot to safestrap no abd so bricked or not and by the way i already read like damm near all the threrads i could find so dont accuse me of being a lazy no good non reasearching az mf thanx
jamesh1979 said:
Hello all. hdx 7 was running the original version of safestrap and gapps on the very first firmware. accidently wiped internal and now can only boot to safestrap no abd so bricked or not and by the way i already read like damm near all the threrads i could find so dont accuse me of being a lazy no good non reasearching az mf thanx
Click to expand...
Click to collapse
Ok, if I understand you correctly, you wiped internal storage of your sdcard, so no backups to restore for safestrap.
But when wiping happened, you were on activated extra rom slot? So now safestrap cant boot there, because with internal storage you deleted image files for rom slots...
If you can boot into safestrap, can you switch to stock rom? And boot into it? If yes, and Fireos start normally, then nothing is lost, reinstall safestrap, you should have adb access, and do whatever you want to do next...
Did you disabled OTA updates on stock rom? If not, turn off wifi as fast as you can, when you boot into Fireos, so it cant update to nonrootable FW.
thats whats wierd i was on rom slot one but it wiped even my stock img as far as i can tell because it wont let me switch to it , and yes disabled ota with toolkit like a year ago and all was fine?
jamesh1979 said:
thats whats wierd i was on rom slot one but it wiped even my stock img as far as i can tell because it wont let me switch to it , and yes disabled ota with toolkit like a year ago and all was fine?
Click to expand...
Click to collapse
Well, I installed safestrap on my working kindle, so I can check what else was deleted in the wiping, unfortunately there was a little config file where safestrap stored which slot was last active. This file no longer exist, so safestrap dont know from what to switch where.
The only thing we can try (AFAIK) requires working adb connection and it must be working from safestrap, so you can use adb sideload feature - so enter safestrap and connect kindle to your pc or laptop. Then start cmd window or terminal if you using linux, and try:
adb devices
it should return:
list of devices attached
xxxxxxxxx recovery
if you can achieve this, we can try with sideloading, if not I am sorry, dont know what else to do - actually there is one thing you can try - with working adb access you can recreate directory structure needed for safestrap config file and push it there (I will attach it later), then restart and see if it boot to stock rom
edit:
I was able connect through adb from windows to running safestrap, so it is possible (at least kindle is recognized in "adb devices")
ok guys i got the pc to see the kindle in recovery via adb!!! so what now push a rom to internal storage and flash it and then reinstall safestrap to get stock slot available or what????
jamesh1979 said:
ok guys i got the pc to see the kindle in recovery via adb!!! so what now push a rom to internal storage and flash it and then reinstall safestrap to get stock slot available or what????
Click to expand...
Click to collapse
Great!
Now download this 13.3.1.0 (Kindle HDX 7") update - pure amazon FireOS so OTA updates enabled - do not connect to wifi/register your kindle if you want root and use of custom recovery after flashing this
A. Now, since I am not expert for adb installing pushing repairing etc., read this thread [HOWTO] Unbrick your device, especially this post (shows similar symptoms as your current problem)
B. If that for whatever reason wont work, you can try sideload update-kindle-13.3.1.0_user_310079820.bin (rename .bin to .zip before sideloading) through safestrap recovery, but because Safestrap is "only" TWRP based, I cant guarantee that this will work either (it should, but this is one way ticket, your working safestrap recovery will be destroyed in the process of update):
0. connect kindle to pc/laptop
1. enter Safestrap, tap Advanced -> ADB Sideload -> Swipe slider to start Sideload
2. on pc/laptop open cmd/terminal, type adb devices, you should see:
List of devices attached
XXXXXXXXXXXXXXXX sideload
3. type adb sideload update-kindle-13.3.1.0_user_310079820.zip
4. You will see a progress bar in the command prompt indicating that the Zip file is being copied to the device. Once the file is transferred, the Zip is automatically installed on your device.
C. You can consider also recreating deleted folder containing slot config file for Safestrap (active_slot file attached below (file is in archive, you need extract it)) through adb shell:
0. connect kindle to pc/laptop
1. enter Safestrap
2. on pc/laptop open cmd/terminal, type adb devices, you should see:
List of devices attached
XXXXXXXXXXXXXXXX recovery
3. type adb shell
4. type mkdir -p data/media/safestrap/rom-slot1
5. type exit
6. type adb push active_slot data/media/safestrap
7. reboot/reboot into recovery and see if you can switch/boot to stock rom (which is still there, otherwise safestrap will not be accessible)
C variant is a really long-shot, but relatively harmless (or maybe not who knows, I am not expert)
OK fingers crossed, I hope something will work, but things can go wrong, unfortunatelly from my side all above is just a theory, adb commands should works, I tested them all (except sideload), works on my side...
Thanx a lot guys I got I t back in action thanx for all the help
jamesh1979 said:
Thanx a lot guys I got I t back in action thanx for all the help
Click to expand...
Click to collapse
Care to share which method you use to recover your kindle?
anyone here? lol