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,
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
I understand that there is a seperate thread for the LG G Vista, but I was hoping that it was okay to post this. I noticed that there is not any guide on how to install CWM on the D-631 so here is a guide on how to do just that.
First of all..... you will need to enable USB Debugging.
To do this
\go to 'Settings' then 'About Phone' then 'Software Information' then click 'Build number' 7 times or so until it says 'You are now a developer!'
go back to 'Settings' and scroll down to the new box Developer Options
turn it on, and enable USB Debugging. ( I also check stay awake)
I rooted my phone with iRoot, and it installed Kinguser as my super user apk. Whether or not it is the best, I don't know. It just is the only one I could get working.
1. Install The LG Unified drivers from here ( I used LG USB Drivers 3.11)
http://www.mylgphones.com/lg-android-usb-device-drivers
2. Install ADB & fastboot (follow the xda thread here)
http://forum.xda-developers.com/showthread.php?t=2588979
3. now you have to use tese adb commands to zero out the laf partition on your D-631
adb shell
su
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/laf
(I also ran this command to zero out the actual block partition)
dd if=/dev/zero of=/dev/block/mmcblk0p15
after I eliminated the LG Download so that fastboot takes priority (just as the G3) I could now boot into fastboot.
*Source from here* http://www.theandroidsoul.com/lg-g3-fastboot-mode-61660/
4. boot to fastboot. To do this.. Power down your phone. Hold vol+ and plug your phone into your pc.
It will still say DOWNLOAD MODE at the top, but it should now say 'fastboot processing commands'
5. unlock bootloader with this fastboot command
fastboot oem unlock
*this did not delete anything off my phone*
6. download and flash CWM recovery
Here is the recovery file
https://drive.google.com/file/d/0B-GvkM12QEbMbWxSV2RHcWRMOWs/view?usp=sharing
also on my main google drive
https://drive.google.com/folderview?id=0B-GvkM12QEbMeFFxRThfMlRvMWc&usp=sharing
fastboot flash recovery xxxxxxxxx
"xxxxxxx" is your directory of the recovery.img
bam all done.........
but this is what sucks..... fastboot reboot commands dont work. and idk how to fix that, but. I need help with the rest, PLEASE. and also some tweaks on the recovery file will need to be done. I just made it possible for us
so to reboot you must pull your battery.
I still dont know the hard key combo to enter into recovery so I had to install Xposed Framework from here
http://repo.xposed.info/module/de.robv.android.xposed.installer
then from googlen play I downloaded these
Xposed Additions
G3 Tweakbox <------------= This can enable the option for REboot REcovery
Busybox
SD Maid
(I used SDMaid to uninstall Carrier IQ tracking software, but I had to toggle the carrier IQ autostart component that starts with Android System)
So yeah, long nights, long days, but no bricks and now here it is
+XDA (as posted on your thread) and I am not responsible for any damage that may be caused.
=Do not steal this, give credit where it is due, link it here to this thread please.
Sorry I did not see the area for the guides and I apologize about that.
Also I forgot to thank everyone who gave their time on the LG G3 fast-boot project, as without your information I would not have been able to do this.
Also thanks to Google translate lol.... I couldnt have read Korean
great work friend
I delete some system files and now I cannot install anything from Google Play
I follow you method and I have CWM installed on my device can you help me to say how flash recovery to IMG FILES from you google drive all files are IMG not .tar ...
What files did you delete? I may be able to pull them with titabium backup and send you them all in a .zip file or something like that.
I used the fastboot commands to flash partitions.
fastboot flash xxxx <dir>
Where dir is the directory of said file to be flashed.
However installing apk's and what not i am not sure on how to do that.
Ill create some files in the .tar format as well. Im attempting to compile an un-official .bin, ,.tot, .dz or .kdz file for the d631. I have dzcreate and what nots. Its just that i drove away with my phone on the bumper and have to wait for my new screen from amazon.
djacks222 said:
What files did you delete? I may be able to pull them with titabium backup and send you them all in a .zip file or something like that.
I used the fastboot commands to flash partitions.
fastboot flash xxxx <dir>
Where dir is the directory of said file to be flashed.
However installing apk's and what not i am not sure on how to do that.
Ill create some files in the .tar format as well. Im attempting to compile an un-official .bin, ,.tot, .dz or .kdz file for the d631. I have dzcreate and what nots. Its just that i drove away with my phone on the bumper and have to wait for my new screen from amazon.
Click to expand...
Click to collapse
when I flashing the file system.img ( 2 GB size) obtain a error from fastboot for the size of system.img over 512 mb my partition system i
/system 1.97G 1.71G 260.18M 4096
/data 3.96G 1011.82M 2.97G 4096
/persist 31.46M 4.03M 27.43M 4096
/cache 884.61M 14.61M 870.00M 4096
/persist-lg 7.83M 4.33M 3.50M 4096
/sns 7.83M 4.03M 3.80M 4096
/firmware 63.95M 56.39M 7.56M 16384
/mpt 31.46M 13.36M 18.10M 4096
/mnt/shell/emulated 3.96G 1011.82M 2.97G 4096
/storage/emulated/legacy 3.96G 1011.82M 2.97G 4096
/storage/emulated 677.76M 0.00K 677.76M 4096
/mnt/media_rw/external_SD 3.72G 395.72M 3.33G 32768
/mnt/secure/asec 3.72G 395.72M 3.33G 32768
/storage/external_SD 3.72G 395.72M 3.33G 32768
/storage/emulated/0 3.96G 1011.82M 2.97G 4096
/storage/emulated/0/Android/obb 3.96G 1011.82M 2.97G 4096
/storage/emulated/legacy 3.96G 1011.82M 2.97G 4096
/storage/emulated/legacy/Android/obb 3.96G 1011.82M 2.97G
4096
Thank you! I just pulled your recovery image for the D631 and used flashify to flash it. Now custom CWM recovery is working fully!! Thank you for your work. I am looking into porting a rom to our device so that all of us G Vista owners have some options! Now that we have root and custom recovery we are almost there!
Sent from my LG-D631 using XDA Free mobile app
Man dude that would be awesome. I will even help in aid of development. I dont know exactly what to do but im sure that i could figure something out with all the guides here on xda.
I am in need of other devs to help out...but it looks like none are able..so i dunno where to go from here. Looks like we are stuck.
Sent from my LG-D631 using XDA Free mobile app
Msm8226 is the board for the d631. It is also the board for the v410 lte tablet. Is there any compatibility between the two
Sent from my LG-V410 using Tapatalk
Once rooted with one click, you can install the quick boot app from the Play store and use it to reboot into recovery.
oranget said:
Thank you! I just pulled your recovery image for the D631 and used flashify to flash it. Now custom CWM recovery is working fully!! Thank you for your work. I am looking into porting a rom to our device so that all of us G Vista owners have some options! Now that we have root and custom recovery we are almost there!
Sent from my LG-D631 using XDA Free mobile app
Click to expand...
Click to collapse
what is this is it hope
it's not a brick it's a wonderful egg i'm going to hatch into a beautiful budget-friendly princess
Issues step 6
djacks222 said:
I understand that there is a seperate thread for the LG G Vista, but I was hoping that it was okay to post this. I noticed that there is not any guide on how to install CWM on the D-631 so here is a guide on how to do just that.
First of all..... you will need to enable USB Debugging.
To do this
\go to 'Settings' then 'About Phone' then 'Software Information' then click 'Build number' 7 times or so until it says 'You are now a developer!'
go back to 'Settings' and scroll down to the new box Developer Options
turn it on, and enable USB Debugging. ( I also check stay awake)
I rooted my phone with iRoot, and it installed Kinguser as my super user apk. Whether or not it is the best, I don't know. It just is the only one I could get working.
1. Install The LG Unified drivers from here ( I used LG USB Drivers 3.11)
http://www.mylgphones.com/lg-android-usb-device-drivers
2. Install ADB & fastboot (follow the xda thread here)
http://forum.xda-developers.com/showthread.php?t=2588979
3. now you have to use tese adb commands to zero out the laf partition on your D-631
adb shell
su
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/laf
(I also ran this command to zero out the actual block partition)
dd if=/dev/zero of=/dev/block/mmcblk0p15
after I eliminated the LG Download so that fastboot takes priority (just as the G3) I could now boot into fastboot.
*Source from here* http://www.theandroidsoul.com/lg-g3-fastboot-mode-61660/
4. boot to fastboot. To do this.. Power down your phone. Hold vol+ and plug your phone into your pc.
It will still say DOWNLOAD MODE at the top, but it should now say 'fastboot processing commands'
5. unlock bootloader with this fastboot command
fastboot oem unlock
*this did not delete anything off my phone*
6. download and flash CWM recovery
Here is the recovery file
https://drive.google.com/file/d/0B-GvkM12QEbMbWxSV2RHcWRMOWs/view?usp=sharing
also on my main google drive
https://drive.google.com/folderview?id=0B-GvkM12QEbMeFFxRThfMlRvMWc&usp=sharing
fastboot flash recovery xxxxxxxxx
"xxxxxxx" is your directory of the recovery.img
bam all done.........
but this is what sucks..... fastboot reboot commands dont work. and idk how to fix that, but. I need help with the rest, PLEASE. and also some tweaks on the recovery file will need to be done. I just made it possible for us
so to reboot you must pull your battery.
I still dont know the hard key combo to enter into recovery so I had to install Xposed Framework from here
http://repo.xposed.info/module/de.robv.android.xposed.installer
then from googlen play I downloaded these
Xposed Additions
G3 Tweakbox <------------= This can enable the option for REboot REcovery
Busybox
SD Maid
(I used SDMaid to uninstall Carrier IQ tracking software, but I had to toggle the carrier IQ autostart component that starts with Android System)
So yeah, long nights, long days, but no bricks and now here it is
+XDA (as posted on your thread) and I am not responsible for any damage that may be caused.
=Do not steal this, give credit where it is due, link it here to this thread please.
Click to expand...
Click to collapse
Wonderful work btw. Needed this thread. I only had one problem!!1
I made int all the way down to Step 6 and got hung up. I have renamed the the file to "recovery.img" and I entered "fastboot flash recovery c:\users\jason\desktop\recovery.img" (file location\file) and Command window says,
target reported max download size of 536670912 bytes
sending 'recovery' (10465 KB)......
okay [ 0.406s]
writing 'recovery'....
FAILED (remote unknown command)
Finished. total time: 0.422s
No CWM recovery... where have i gone wrong?
Thanks in advance.
Drake865 said:
Wonderful work btw. Needed this thread. I only had one problem!!1
I made int all the way down to Step 6 and got hung up. I have renamed the the file to "recovery.img" and I entered "fastboot flash recovery c:\users\jason\desktop\recovery.img" (file location\file) and Command window says,
target reported max download size of 536670912 bytes
sending 'recovery' (10465 KB)......
okay [ 0.406s]
writing 'recovery'....
FAILED (remote unknown command)
Finished. total time: 0.422s
No CWM recovery... where have i gone wrong?
Thanks in advance.
Click to expand...
Click to collapse
If you are rooted, you could try using flashify. It worked for me. It'll load cwm first and reboot, but after the second try you should be up and running.
Questions???Anything on the update for this device thanks
System Dump
I currently have a full system dump of the lg g vista d631 on android version 4.4.2 for the purpose of roms. The one issue I have is I'm not able to get a hold of 2 files, "WCNSS_qcom_cfg.ini" and "WCNSS_qcom_wlan_nv.bin". They are located in the directory etc/firmware/wlan/prima. They are important for wifi connectivity and I don't want to build a rom without them. Can anyone retrieve them?
Edit: I've gotten everything now. I'll work on building a rom for testing.
How would I go about retrieving those two files
---------- Post added at 06:44 PM ---------- Previous post was at 06:39 PM ----------
I have the 2 files that you need but I need a email address to send it to you
Any kdz file or anything how to update to 5.0
at&t d631 rom
Isaiah.E.Scott said:
I currently have a full system dump of the lg g vista d631 on android version 4.4.2 for the purpose of roms. The one issue I have is I'm not able to get a hold of 2 files, "WCNSS_qcom_cfg.ini" and "WCNSS_qcom_wlan_nv.bin". They are located in the directory etc/firmware/wlan/prima. They are important for wifi connectivity and I don't want to build a rom without them. Can anyone retrieve them?
Edit: I've gotten everything now. I'll work on building a rom for testing.
Click to expand...
Click to collapse
Where you able to get a rom put together? I have the d631 5.0.2 rooted and removed the wrong contacts apk and now can't save any contacts. Do you have a way to retrieve the apks from this version?
piptravels said:
Where you able to get a rom put together? I have the d631 5.0.2 rooted and removed the wrong contacts apk and now can't save any contacts. Do you have a way to retrieve the apks from this version?
Click to expand...
Click to collapse
Can't you upload the update zip
Rican39 said:
Can't you upload the update zip
Click to expand...
Click to collapse
Where is the update zip? I have seen a lot of stuff about kdz and tot files but I don't see anything identifying if they're for the AT&T version of the LG G Vista or the Verizon version.
Hi!
I installed CM 12.1 recently and found that the cyanogen recovery doesnt offer any backup option. Since I need this, I went back to my backup (CM 11).
I am a little confused about how I should proceed to use CM 12.1 AND have the backup option in recovery:
Can I just flash CWM (from the clockworkmod website) or TWRP recovery after installing CM 12.1? I read that this replaces the kernel of the i9100 aswell, will this result in any issues?
And can I flash it by using the cyanogen recovery (download the zip and install in recovery)?
And will CM 12.1 replace the recovery immediately, even if I unchecked "Update Cyanogen recovery" in the developer options? (I think I tried to install CWM before but it got replaced nevertheless...)
I hope that this question hasn't been asked already, I found so many topics which couldn't really help me...
Thank you!!
GridLockFour said:
Hi!
I installed CM 12.1 recently and found that the cyanogen recovery doesnt offer any backup option. Since I need this, I went back to my backup (CM 11).
I am a little confused about how I should proceed to use CM 12.1 AND have the backup option in recovery:
Can I just flash CWM (from the clockworkmod website) or TWRP recovery after installing CM 12.1? I read that this replaces the kernel of the i9100 aswell, will this result in any issues?
And can I flash it by using the cyanogen recovery (download the zip and install in recovery)?
And will CM 12.1 replace the recovery immediately, even if I unchecked "Update Cyanogen recovery" in the developer options? (I think I tried to install CWM before but it got replaced nevertheless...)
I hope that this question hasn't been asked already, I found so many topics which couldn't really help me...
Thank you!!
Click to expand...
Click to collapse
CM recovery is almost like a stock recovery! you cant flash anything unless is signed!
First you cant flash random recovery! "A kernel is a recovery and a recovery is a kernel." it must be build and compatible with phone and ROM that you using!
After you flash your rom, recovery will get replaced by roms buildin recovery/kernel! SG2 doesn't have a separate partition for recovery.
Here is KK kernel and LP kernel by @gsstudios
ultravy said:
CM recovery is almost like a stock recovery! you cant flash anything unless is signed!
First you cant flash random recovery! "A kernel is a recovery and a recovery is a kernel." it must be build and compatible with phone and ROM that you using!
After you flash your rom, recovery will get replaced by roms buildin recovery/kernel! SG2 doesn't have a separate partition for recovery.
Here is KK kernel and LP kernel by @gsstudios
Click to expand...
Click to collapse
Thank you! I now use the dorimanX Kernel (+Trim) and finally have a proper recovery AND cm 12.1
It's a bit slower (Cm 12.1) than Cm 11, but I guess that's a different problem.
Thanks again!
GridLockFour said:
Thank you! I now use the dorimanX Kernel (+Trim) and finally have a proper recovery AND cm 12.1
It's a bit slower (Cm 12.1) than Cm 11, but I guess that's a different problem.
Thanks again!
Click to expand...
Click to collapse
Be sure to check for brickbug before do trim on partitions! but i trimmed anyway on a temporary trim kernel! And this is my result! do a test before and compare them after you do a trim!
GT-I9100 appears to have a separate recovery partition
ultravy said:
CM recovery is almost like a stock recovery! you cant flash anything unless is signed!
First you cant flash random recovery! "A kernel is a recovery and a recovery is a kernel." it must be build and compatible with phone and ROM that you using!
After you flash your rom, recovery will get replaced by roms buildin recovery/kernel! SG2 doesn't have a separate partition for recovery.
Here is KK kernel and LP kernel by @gsstudios
Click to expand...
Click to collapse
By SG2, I assume you meant GS2. I have an GT-I9100.
I've read several times in various places that GS2s do not have a separate recovery partition. Though I'm quite new to android in general, it seems that my GS2 does.
Here is a bit of my PIT (heimdall print-pit --verbose) output:
...
--- Entry #6 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 6
Attributes: 0 (Read-Only)
Update Attributes: 0
Partition Block Size/Offset: 73728
Partition Block Count: 16384
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: KERNEL
Flash Filename: zImage
FOTA Filename:
--- Entry #7 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 7
Attributes: 0 (Read-Only)
Update Attributes: 0
Partition Block Size/Offset: 90112
Partition Block Count: 16384
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: RECOVERY
Flash Filename:
FOTA Filename:
...
Here are the details of all the partitions listed in the verbose PIT output (sorry about the formatting):
Partition offset blocks hi-end size (MiB)
GANG 0 0 0.00
BOOT 0 8192 8192 4.00
EFS 8192 40960 49152 20.00
SBL1 49152 2560 51712 1.25
SBL2 53248 2560 55808 1.25
PARAM 57344 16384 73728 8.00
KERNEL 73728 16384 90112 8.00
RECOVERY 90112 16384 106496 8.00
CACHE 106496 204800 311296 100.00
MODEM 311296 32768 344064 16.00
FACTORYFS 344064 1048576 1392640 512.00
DATAFS 1392640 4194304 5586944 2.00
UMS 5586944 24133632 29720576 11.00
HIDDEN 29720576 1048576 30769152 512.00
blank 0 0 0 0.00
15022.50 Total
As you can see, there are no overlaps. In fact, the SBL1 and SBL2 have unused space after them - if they were 4096 blocks (2 MiB) instead of 2560 (1.25 MiB), then all the space would be allocated in contiguous, non-overlapping chunks.
Q1: is my reading correct, that is, my GS2 does have a separate recovery partition? (As there are several GS2 models, my question relates to the I9100.)
Second point. It seems that when I flash a CWM recovery, it really is being written to (what I believe to be) the recovery partition.
On my Linux desktop:
$ ls -l zImage
-rwxr-xr-x. 1 me me 6190876 Mar 16 2013 zImage*
$ sha1sum zImage
ee4464781de5396b769eab9325ae43a84e942ef9 zImage
$ adb shell
Now On my GS2:
[email protected]:/ $ su
Note: I used a block size of 4 because 4 x 1547719 = 6190876.
[email protected]:/ # dd if=/dev/block/mmcblk0p6 bs=4 count=1547719 | sha1sum
ee4464781de5396b769eab9325ae43a84e942ef9 -
1547719+0 records in
1547719+0 records out
6190876 bytes transferred in 26.631 secs (232468 bytes/sec)
As you can see, the sums agree. So, assuming /dev/block/mmcblk0p6 is pointing to the (presumed to exist) recovery partition, the zImage contents is definitely there.
So, it seems to me that RECOVERY is a separate chunk of the storage partition, and that I have successfully written an image to that partition. Booting CM 12.1 does not overwrite this. CM appears to ignore it.
Q2: If that is correct, why does booting into recovery still boot the "Cyanogen Recovery" - and, is there any way to get it to boot off the zImage?
Q3: Can anyone please post some useful links into how this all works? I've spent quite a while looking, but I have yet to find anywhere that clearly (and accurately!) documents how this all works.
Tx
jimstaffer said:
By SG2, I assume you meant GS2. I have an GT-I9100.
So, it seems to me that RECOVERY is a separate chunk of the storage partition, and that I have successfully written an image to that partition. Booting CM 12.1 does not overwrite this. CM appears to ignore it.
Q2: If that is correct, why does booting into recovery still boot the "Cyanogen Recovery" - and, is there any way to get it to boot off the zImage?
Q3: Can anyone please post some useful links into how this all works? I've spent quite a while looking, but I have yet to find anywhere that clearly (and accurately!) documents how this all works.
Tx
Click to expand...
Click to collapse
Yes i meant gt i9100! Indeed partition blocks shows recovery and kernel, but i think there is some link between them, otherwise experienced devs should figure this out by now! You should ask a dev for detailed information!
help me out...
am stuck with 12.1 ... i want to downgrade but am unable to find suitable help, way & firmware...even phn's internal memory is not allowing to modify it,,,as says its read only memory... its nealy full but i cant remove anything ...
garry4rm.asr said:
am stuck with 12.1 ... i want to downgrade but am unable to find suitable help, way & firmware...even phn's internal memory is not allowing to modify it,,,as says its read only memory... its nealy full but i cant remove anything ...
Click to expand...
Click to collapse
put your phone on download mode and install a kernel using ODIN. Here are some of the pre-made kernel .tar files for ODIN: http://forum.xda-developers.com/galaxy-s2/development-derivatives/convert-kernel-zip-to-tar-t2994381 Flash one of these under PDA and enter you phone in recovery mode again. Try installing a zip or see if you can access internal storage. If problems still occurs, try mounting you internal sd card in CWM under the mounts and storage menu.
If all still doesn't work, then you should consider flashing back to stock.
gsstudios.
gsstudios said:
put your phone on download mode and install a kernel using ODIN. Here are some of the pre-made kernel .tar files for ODIN: http://forum.xda-developers.com/galaxy-s2/development-derivatives/convert-kernel-zip-to-tar-t2994381 Flash one of these under PDA and enter you phone in recovery mode again. Try installing a zip or see if you can access internal storage. If problems still occurs, try mounting you internal sd card in CWM under the mounts and storage menu.
If all still doesn't work, then you should consider flashing back to stock.
gsstudios.
Click to expand...
Click to collapse
every link open with a new confusion and a new link.... my mind like its in a grinder and cant see which way its rotating....pheeeeewwww....
plz provide link with compatible kernal of i9100 12.1 CyanogenMod, lollypop.....
found a way to delete but with small time window
today when i made my mind to accept that its over with s2...but again when phn is on the way of booting and installing apps.... a 5-10 seconds time window is there to le me delete some media...but as soon as phn is fully booted..again same nonsense starts to appear " some files cannot be deleted or this is read only memory"......
This is a question thread for people who have Clone Phones by HDC, Goophone, Tengda, iHD, and other manufacturers' phones that are based upon an existing phone by a major manufacturer.
The design of this thread is equal to this
Make sure to read the Forum Rules before posting
Anyone can answer.
All questions are welcome!
Hardware: MT6572 (MTK6595 IS FAKE) MODEL :S960c
Hi Xda,
I have a fake Lenovo S960c (didn't knew before i purchased it) , after i rooted it with kingo user, because there was a malware which was located only by rooting . the malware was removed , but after few months the same type of malware came again but this time there was two or three malware which was causing my battery to drain and i couldn't charge my phone battery to 100% . My Antivirus Showed my Mediatek file had a malware , i didnt know so i uninstalled that file after my phone restarted it is caught in bootloop and won't go beyond the lenovo logo.
Please advise how can i solve this problem as i have been scammed when i bought this phone from Aliexpress,
thinking this was a real MTK6595 MODEL original Lenovo phone. I have written below my phone's real spec which
i got using Mtk droid tools for your reference. please advise how can i fix my phone again.
Hardware: Mtk6572 (Mtk6595 is fake)
Model: S960c
Build Number : S5_JB3_3G_EMMC_QHD_32_4_XLD_Z12_LENO
Build Date : 20150417-064045
Andriod v: 4.4.3
Baseband: ____
Kernel v: 3.4.5([email protected])(gcc version 4.6x-google 20120106 (prerelease)(GCC)#1 SMP Fri Apr 17
18:02:31 CST 2015
sufyan nuhammad said:
Hi Xda,
I have a fake Lenovo S960c (didn't knew before i purchased it) , after i rooted it with kingo user, because there was a malware which was located only by rooting . the malware was removed , but after few months the same type of malware came again but this time there was two or three malware which was causing my battery to drain and i couldn't charge my phone battery to 100% . My Antivirus Showed my Mediatek file had a malware , i didnt know so i uninstalled that file after my phone restarted it is caught in bootloop and won't go beyond the lenovo logo.
Please advise how can i solve this problem as i have been scammed when i bought this phone from Aliexpress,
thinking this was a real MTK6595 MODEL original Lenovo phone. I have written below my phone's real spec which
i got using Mtk droid tools for your reference. please advise how can i fix my phone again.
Hardware: Mtk6572 (Mtk6595 is fake)
Model: S960c
Build Number : S5_JB3_3G_EMMC_QHD_32_4_XLD_Z12_LENO
Build Date : 20150417-064045
Andriod v: 4.4.3
Baseband: ____
Kernel v: 3.4.5([email protected])(gcc version 4.6x-google 20120106 (prerelease)(GCC)#1 SMP Fri Apr 17
18:02:31 CST 2015
Click to expand...
Click to collapse
Most likely, the malware was caused by a required system app. Maybe the dialer, MMS, or search app? Whenever the app sweeps your phone to check and sees there is no malware app, it connects to a server and, unbeknownst to you, installs it as a system app.
Do you know the actual manufacturer? In antutu it would show Zen, Alps, Wen, Next, or another OEM name. If so, that helps a lot in recovering your OEM mtk phone.
Your phone is recognized by mtk droid tools right? If so, you should be able to go into recovery as well. Even make cwm which should help
Sent from my SGH-M919 using XDA Free mobile app
Hardware: MT6572 (MTK6595 IS FAKE) MODEL :S960c
Qiangong2 said:
Most likely, the malware was caused by a required system app. Maybe the dialer, MMS, or search app? Whenever the app sweeps your phone to check and sees there is no malware app, it connects to a server and, unbeknownst to you, installs it as a system app.
Do you know the actual manufacturer? In antutu it would show Zen, Alps, Wen, Next, or another OEM name. If so, that helps a lot in recovering your OEM mtk phone.
Your phone is recognized by mtk droid tools right? If so, you should be able to go into recovery as well. Even make cwm which should help
Sent from my SGH-M919 using XDA Free mobile app
Click to expand...
Click to collapse
First of all thanks for your kind Reply , really appreciated , when its comes to android, I am a toddler , not much experience in installing or flashing roms or making recoveries either. Please guide me step by step way , like a child
how to fix my phone again , as my hard earned money will go down the drain. if try to flash or do something else,
already i made it stuck on boot loop.
:good::good:
Regards
Sufyan
sufyan nuhammad said:
First of all thanks for your kind Reply , really appreciated , when its comes to android, I am a toddler , not much experience in installing or flashing roms or making recoveries either. Please guide me step by step way , like a child
how to fix my phone again , as my hard earned money will go down the drain. if try to flash or do something else,
already i made it stuck on boot loop.
:good::good:
Regards
Sufyan
Click to expand...
Click to collapse
No problem, I'm happy to help.
1. Is your phone still recognized when you plug it in to mtk droid tools?
2. Do you know what the actual manufacturer of your phone? If so, what?
3. What was the name of the file you deleted? (not needed, but it might help)
Qiangong2
Hardware: MT6572 (MTK6595 IS FAKE) MODEL :S960c
Qiangong2 said:
No problem, I'm happy to help.
1. Is your phone still recognized when you plug it in to mtk droid tools?
2. Do you know what the actual manufacturer of your phone? If so, what?
3. What was the name of the file you deleted? (not needed, but it might help)
Qiangong2
Click to expand...
Click to collapse
Yes , its does when i connect it to the droid tools it says in the message window,
Attention fake hardware in kernel or firmware doesn't correspond to phone
Attention File/system/Recovery-from-boot-p which restore factory recovery in case of phone
switching on in a normal mode is found.
also in left side menu the beside yellow light there is a message which says ,
S960c system/bin/su is found! Via root button it is possible to get root shell.
then when i press root button this message appears ,
to try to receive root shell through already established su .
I press yes to the button, after a while this error pop's up ,
Loss of communication with the device! the program will be closed.
I press OK then the software window is gone.
I am sorry, really don't know the actual manufacturer of the phone , i even did an tutu test but really , i only remember is the fake specs that mesmerized me a lot nothing else ,
The Files I deleted where Mediatek file , i bingo as the Anti Virus showed serious Malware in them.
sufyan nuhammad said:
Yes , its does when i connect it to the droid tools it says in the message window,
Attention fake hardware in kernel or firmware doesn't correspond to phone
Attention File/system/Recovery-from-boot-p which restore factory recovery in case of phone
switching on in a normal mode is found.
Click to expand...
Click to collapse
The first "Attention" shouldn't matter, it's just reading the build.prop which claims that it is an MT6595 instead of an MT6572. The second "Attention" is more interesting. I've actually never seen that one before, but it seems like there was some error in the ROM, and (when there is) it defaults to booting to factory/stock recovery.
also in left side menu the beside yellow light there is a message which says ,
S960c system/bin/su is found! Via root button it is possible to get root shell.
then when i press root button this message appears ,
to try to receive root shell through already established su .
I press yes to the button, after a while this error pop's up ,
Loss of communication with the device! the program will be closed.
I press OK then the software window is gone.
Click to expand...
Click to collapse
You may already have root, or it may not be there anymore. Try opening adb (from the adb button) and type:
Code:
adb devices
If your phone is recognized, type:
Code:
adb shell
Then (if it works) type:
Code:
su
if you see a # sign right next to where you type, then you have root.
I am sorry, really don't know the actual manufacturer of the phone , i even did an tutu test but really , i only remember is the fake specs that mesmerized me a lot nothing else ,
Click to expand...
Click to collapse
That's okay, it will just be harder to find information about your device firmware, not impossible though.
The Files I deleted where Mediatek file , i bingo as the Anti Virus showed serious Malware in them.
Click to expand...
Click to collapse
That should be fine... Mediatek files can be required or useless. Most of the time they only activate if you enter factory test mode. Since they had malware in them, they shouldn't be needed.
Qiangong2 said:
The first "Attention" shouldn't matter, it's just reading the build.prop which claims that it is an MT6595 instead of an MT6572. The second "Attention" is more interesting. I've actually never seen that one before, but it seems like there was some error in the ROM, and (when there is) it defaults to booting to factory/stock recovery.
You may already have root, or it may not be there anymore. Try opening adb (from the adb button) and type:
Code:
adb devices
If your phone is recognized, type:
Code:
adb shell
Then (if it works) type:
Code:
su
if you see a # sign right next to where you type, then you have root.
That's okay, it will just be harder to find information about your device firmware, not impossible though.
That should be fine... Mediatek files can be required or useless. Most of the time they only activate if you enter factory test mode. Since they had malware in them, they shouldn't be needed.
Click to expand...
Click to collapse
Sorry i forgot to tell you that when my phone was in OK condition , i did root it with kingo root , so do you think , it
is still rooted while caught in boot loop. sorry for not telling you the complete details. So should i follow the above mentioned details , also where would i find the adb button , is it when i connect the phone through droid tools it will appear there or you are talking about phone recovery menu.
---------- Post added at 11:29 AM ---------- Previous post was at 11:22 AM ----------
sufyan nuhammad said:
Sorry i forgot to tell you that when my phone was in OK condition , i did root it with kingo root , so do you think , it
is still rooted while caught in boot loop. sorry for not telling you the complete details. So should i follow the above mentioned details , also where would i find the adb button , is it when i connect the phone through droid tools it will appear there or you are talking about phone recovery menu.
Click to expand...
Click to collapse
i tried all your commands mentioned above while pressing Adb Terminal Buttton, in the end the command line showed # as you have mentioned , now what should i do please advise. once again thanks for your efforts brother.
sufyan nuhammad said:
Sorry i forgot to tell you that when my phone was in OK condition , i did root it with kingo root , so do you think , it
is still rooted while caught in boot loop. sorry for not telling you the complete details. So should i follow the above mentioned details , also where would i find the adb button , is it when i connect the phone through droid tools it will appear there or you are talking about phone recovery menu.
---------- Post added at 11:29 AM ---------- Previous post was at 11:22 AM ----------
i tried all your commands mentioned above while pressing Adb Terminal Buttton, in the end the command line showed # as you have mentioned , now what should i do please advise. once again thanks for your efforts brother.
Click to expand...
Click to collapse
You have root so you are stuck in bootloop. The bootloop seems to be caused by mediatek file now...
Have you removed any other files? Also, where was the file placed that you removed?
Qiangong2 said:
You have root so you are stuck in bootloop. The bootloop seems to be caused by mediatek file now...
Have you removed any other files? Also, where was the file placed that you removed?
Click to expand...
Click to collapse
As i mentioned before i only removed the file from settings, then click app, then all files , from there i uninstalled mediatek file and iBingo file nothing else. . Please advise what to do now.
sufyan nuhammad said:
As i mentioned before i only removed the file from settings, then click app, then all files , from there i uninstalled mediatek file and iBingo file nothing else. . Please advise what to do now.
Click to expand...
Click to collapse
The mediatek file is the problem then. We need to figure out what exactly the file is and also whether it is a customised file or a generic. If it is generic, then we can just copy it from another MT6572 phone with the same screen aspect ratio. If it is customised, then we need to somehow recover the file, or just get a copy of the stock firmware from the manufacturer.
On a side note: have you tried pulling a copy of your stock ROM out using adb? It may be able to shine some light onto what exactly the file affected. If you can't, that's fine. We'll just move on
Qiangong2 said:
The mediatek file is the problem then. We need to figure out what exactly the file is and also whether it is a customised file or a generic. If it is generic, then we can just copy it from another MT6572 phone with the same screen aspect ratio. If it is customised, then we need to somehow recover the file, or just get a copy of the stock firmware from the manufacturer.
On a side note: have you tried pulling a copy of your stock ROM out using adb? It may be able to shine some light onto what exactly the file affected. If you can't, that's fine. We'll just move on
Click to expand...
Click to collapse
Sorry, Brother i don't really know if the file is generic or Customised one, i only remember when i uninstalled mediatek and i bingo , the first error which came up was some google gaaps type error , it asked me to repair it i clicked OK , then my phone restarted and when into boot loop. I wish i new how to do adb backup and copy my stock ROM , as i said earlier not a pro , not even a rookie , just a dumb toddler who doesn't know much about android apps and system mechanics . sorry to put you in a mess brother. thanks for your cooperation
sufyan nuhammad said:
Sorry, Brother i don't really know if the file is generic or Customised one, i only remember when i uninstalled mediatek and i bingo , the first error which came up was some google gaaps type error , it asked me to repair it i clicked OK , then my phone restarted and when into boot loop. I wish i new how to do adb backup and copy my stock ROM , as i said earlier not a pro , not even a rookie , just a dumb toddler who doesn't know much about android apps and system mechanics . sorry to put you in a mess brother. thanks for your cooperation
Click to expand...
Click to collapse
Okay, go into adb from mtk droid tools, and type:
Code:
adb shell
Then (once it connects) type:
Code:
su
Now you have root. Next type this:
Code:
cat /proc/partitions
To find out which partition contains your system.img, your boot.img, and your data.img.
If none of the partitions say system or boot. Then make a copy of the partition list and upload it. We'll go from there.
Qiangong2 said:
Okay, go into adb from mtk droid tools, and type:
Code:
adb shell
Then (once it connects) type:
Code:
su
Now you have root. Next type this:
Code:
cat /proc/partitions
To find out which partition contains your system.img, your boot.img, and your data.img.
If none of the partitions say system or boot. Then make a copy of the partition list and upload it. We'll go from there.
Click to expand...
Click to collapse
i followed the instructions and type the command adb shell , from there , the com and line became like this
[email protected]:/$ when i typed su beside this this error came {-} connection to ui timed out , i still went with the last command and when i wrote cat /proc/partitions , this is whats happened afterwards,
major minor #blocks name
7 0 1254 loop0
179 0 3795968 mmcblk0
179 1 1 mmcblk0p1
179 2 10240 mmcblk0p2
179 3 10240 mmcblk0p3
179 4 665600 mmcblk0p4
179 5 385024 mmcblk0p5
179 6 1355776 mmcblk0p6
179 7 1332992 mmcblk0p7
179 64 4096 mmcblk0boot1
179 32 4096 mmcblk0boot0
179 96 3933184 mmcblk1
179 97 3929088 mmcblk1p1
[email protected]:/ $ mmc
Did i do something wrong or is this what you are looking for , please advise me .
sufyan nuhammad said:
i followed the instructions and type the command adb shell , from there , the com and line became like this
[email protected]:/$ when i typed su beside this this error came {-} connection to ui timed out , i still went with the last command and when i wrote cat /proc/partitions , this is whats happened afterwards,
major minor #blocks name
7 0 1254 loop0
179 0 3795968 mmcblk0
179 1 1 mmcblk0p1
179 2 10240 mmcblk0p2
179 3 10240 mmcblk0p3
179 4 665600 mmcblk0p4
179 5 385024 mmcblk0p5
179 6 1355776 mmcblk0p6
179 7 1332992 mmcblk0p7
179 64 4096 mmcblk0boot1
179 32 4096 mmcblk0boot0
179 96 3933184 mmcblk1
179 97 3929088 mmcblk1p1
[email protected]:/ $ mmc
Did i do something wrong or is this what you are looking for , please advise me .
Click to expand...
Click to collapse
This is what we're looking for. mmcblk0 is the entire device. it seems like mmcblk0p4 is the system.img as it is the largest partition within device mmcblk0.
use this:
Code:
cat dev/block/mmcblk0p4 /sdcard/system.img
Which should save your system partition as a .img file on your sdcard which, once transferred to your computer, you can open with the applications ext2read and ext2explore (both on sourceforge)
Repeat previous code, replacing mmcblk0p4 with: mmcblk0p6, mmcblk0p7, and mmcblk0p5. those should bring out your boot.img and your recovery.img at least. use the perl scripts I've attached to unpack those. the instructions are in the readme file.
You are gonna be hard pressed to learn android on a knock off device. No real developer will even touch it.
Qiangong2 said:
This is what we're looking for. mmcblk0 is the entire device. it seems like mmcblk0p4 is the system.img as it is the largest partition within device mmcblk0.
use this:
Code:
cat dev/block/mmcblk0p4 /sdcard/system.img
Which should save your system partition as a .img file on your sdcard which, once transferred to your computer, you can open with the applications ext2read and ext2explore (both on sourceforge)
Repeat previous code, replacing mmcblk0p4 with: mmcblk0p6, mmcblk0p7, and mmcblk0p5. those should bring out your boot.img and your recovery.img at least. use the perl scripts I've attached to unpack those. the instructions are in the readme file.
Click to expand...
Click to collapse
i started in adb, then command line by typing cat dev/block/mmcblk0p4 /sdcard/system.img but it said
'cat' is not a recognized as an internal or external command, operable program or batch file.
then i retyped adb shell , then su then i typed this cat dev/block/mmcblk0p4 /sdcard/system.img
this error show up
/system/bin/sh: cat: dev/block/mmcblk0p4 / permission denied
/system/bin/sh: cat: /sdcard/system.img / no such file or directory
1 :[email protected]:/ $
now what should i do , please advise.
sufyan nuhammad said:
i started in adb, then command line by typing cat dev/block/mmcblk0p4 /sdcard/system.img but it said
'cat' is not a recognized as an internal or external command, operable program or batch file.
then i retyped adb shell , then su then i typed this cat dev/block/mmcblk0p4 /sdcard/system.img
this error show up
/system/bin/sh: cat: dev/block/mmcblk0p4 / permission denied
/system/bin/sh: cat: /sdcard/system.img / no such file or directory
1 :[email protected]:/ $
now what should i do , please advise.
Click to expand...
Click to collapse
You could always just do a backup in mtk droid tools.
To do this,
1) connect your phone to the computer
2) open mtk droid tools
3) when the information shows up, click root button to get root shell (if you don't already have root shell). Then, click the root, backup, and recovery tab.
4) click backup. It is now starting to backup your phone. It doesn't matter if you pack it or not at the end.
All of the files should be in the mtk droid tools backup folder.
Qiangong2 said:
You could always just do a backup in mtk droid tools.
To do this,
1) connect your phone to the computer
2) open mtk droid tools
3) when the information shows up, click root button to get root shell (if you don't already have root shell). Then, click the root, backup, and recovery tab.
4) click backup. It is now starting to backup your phone. It doesn't matter if you pack it or not at the end.
All of the files should be in the mtk droid tools backup folder.
Click to expand...
Click to collapse
when i click root in droidtools . this message then this message shows up
to try to receive root shel through already established su? i clicked yes , after a while in the left side message screen it shows : error su inaccessible . i retried again this time i click no , but this time in the message screen there was a different message :
Through CWM it is possible to get root on this phone! Look URLs :
http://forum.china-iphone.ru/viewtopic.php?p=502084#p502084
please tell what to do .
---------- Post added at 05:50 PM ---------- Previous post was at 05:49 PM ----------
sufyan nuhammad said:
when i click root in droidtools . this message then this message shows up
to try to receive root shel through already established su? i clicked yes , after a while in the left side message screen it shows : error su inaccessible . i retried again this time i click no , but this time in the message screen there was a different message :
Through CWM it is possible to get root on this phone! Look URLs :
http://forum.china-iphone.ru/viewtopic.php?p=502084#p502084
http://forum.xda-developers.com/showpost.php?p=38337401&postcount=5
please tell what to do .
Click to expand...
Click to collapse
also this message was included
http://forum.xda-developers.com/showpost.php?p=38337401&postcount=5
sufyan nuhammad said:
when i click root in droidtools . this message then this message shows up
to try to receive root shel through already established su? i clicked yes , after a while in the left side message screen it shows : error su inaccessible . i retried again this time i click no , but this time in the message screen there was a different message :
Through CWM it is possible to get root on this phone! Look URLs :
http://forum.china-iphone.ru/viewtopic.php?p=502084#p502084
please tell what to do .
---------- Post added at 05:50 PM ---------- Previous post was at 05:49 PM ----------
also this message was included
http://forum.xda-developers.com/showpost.php?p=38337401&postcount=5
Click to expand...
Click to collapse
please help me if you are not busy, waiting for your reply.