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"......
Related
Good day, everyone.
So, my problem is:
I can't boot my phone - its just freezing on Samsung logo and not booting further. I don't know why this happens - did not do anything special with the phone. I can boot into clockwork recover and download mode.
Diagnosis:
from adb:
~ # cat /cache/recovery/log
I:Checking for extendedcommand...
I:Skipping execution of extendedcommand, file not found...
W:failed to mount /dev/block/mmcblk0p12 (Invalid argument)
~ # fdisk -l /dev/block/mmcblk0
Disk /dev/block/mmcblk0: 15.7 GB, 15758000128 bytes
1 heads, 16 sectors/track, 1923584 cylinders
Units = cylinders of 16 * 512 = 8192 bytes
Device Boot Start End Blocks Id System
/dev/block/mmcblk0p1 1 1923584 15388671+ ee EFI GPT
Partition 1 does not end on cylinder boundary
What I tried:
1. format filesystems
format /sdcard fails with "error mounting /sdcard"
2. factory reset - didn't help
3. flash cyanogenmod and flash clockwork recovery once more - didn't help
So I assume that there is a problem with my partition table on internal sd due to logs and fdisk. Maybe I should try to repartition with heimdall? But I have no expereince with that. I need your advice.
Any help appreciated!
You are in the process of invalidating your warranty, flashing a pit alone will probably kill it dead.
If you don't have any warranty then try:
http://forum.xda-developers.com/showpost.php?p=30087735&postcount=6
But make sure you follow all the instructions.
Warranty is now void .
See the faqs and guides How to return to stock for warranty .
Then take it to a service centre .
jje
boomboomer said:
You are in the process of invalidating your warranty, flashing a pit alone will probably kill it dead.
If you don't have any warranty then try:
http://forum.xda-developers.com/showpost.php?p=30087735&postcount=6
But make sure you follow all the instructions.
Click to expand...
Click to collapse
I assume my warranty invalidated since I flashed cyanogen right after byuing this device About your link - what file I must download? I assume this is different baseband versions? Is there any difference in my case?
Baseband is modem .
Flash your firmware version .
JJEgan said:
Baseband is modem .
Flash your firmware version .
Click to expand...
Click to collapse
I don't know which firmware I have. I can't boot the phone and sadly right now I don't have any documents with me.
alsvartr1 said:
I don't know which firmware I have. I can't boot the phone and sadly right now I don't have any documents with me.
Click to expand...
Click to collapse
In that case flash a firmware for your country .
jje
alsvartr1 said:
I assume my warranty invalidated since I flashed cyanogen right after byuing this device About your link - what file I must download? I assume this is different baseband versions? Is there any difference in my case?
Click to expand...
Click to collapse
I think you just flash the latest version, which will hopefuly return your phone to factory condition.I think it's a multi country rescue file.
Guys i have bricked my phone by restoring MK1 efs backup created with efs professional tool. Few days ago i upgraded it with android 4.4 version with ota. I restored all partitions with efs pro tool except user data and system. Now it's in qhsusb_dload mode. I tried i9205 debrick image from this forum and it's not working. I do not know how to make debrick image form stock rom or any other way. Can anyone help me to fix this?
Thanks
Finally unbricked it with DarkAngel's help. Many thanks to him.
For unbrick your phone please read all post's by DarkAngel.
ashikrobi said:
Guys i have bricked my phone by restoring MK1 efs backup created with efs professional tool. Few days ago i upgraded it with android 4.4 version with ota. I restored all partitions with efs pro tool except user data and system. Now it's in qhsusb_dload mode. I tried i9205 debrick image from this forum and it's not working. I do not know how to make debrick image form stock rom or any other way. Can anyone help me to fix this?
Thanks
Click to expand...
Click to collapse
Have you tried to Odin the Official Firmware available for the L600? It can be done via Kies as well.
L600VPUBNE4
I tried odin and kies
DarkAngel said:
Have you tried to Odin the Official Firmware available for the L600? It can be done via Kies as well.
L600VPUBNE4
Click to expand...
Click to collapse
Yes i tried but in qhsusb_dload mode odin cannot find the phone. It cannot be powered up bro so how can kies detect it? Do you know how to fix this issue? Please help.
ashikrobi said:
Yes i tried but in qhsusb_dload mode odin cannot find the phone. It cannot be powered up bro so how can kies detect it? Do you know how to fix this issue? Please help.
Click to expand...
Click to collapse
Which version of Odin are you using?
odin 3.09 and 3.04
DarkAngel said:
Which version of Odin are you using?
Click to expand...
Click to collapse
I tried with these versions. They do not detect the device. If you have a working phone, you can make a debrick image for me. Please install busybox and a terminal emulator. Then issue this command from the terminal and you will get the debrick image in your sd card.
su
busybox dd if=/dev/block/mmcblk0 of=/sdcard/debrick.img bs=1M count=128
Make sure you have SPH-L600 and android version 4.4 or the image will not work for me.
Please upload
Thanks
installed automatic upgrade stuck in boot loop
I have a Galaxy Mega SPH-L600 and i replaced the screen about a week ago and it was running fine opened it up 2 days ago and there was an update said needed to be done so hit ok and installed update it went to 100% and shut off and turned back on went to Samsung splash screen and shut off and turned back on did this for about a half hour so i tried to do the hard boot with power button,volume up and home button droid comes up and it says installing upgrade and goes back ito boot loop tried to hook up to laptop but can not get it to show up on my Windows 7 unit tried alot of stuff nothing works need some help from anyone that can point me in the right direction and thank you in advance
ashikrobi said:
I tried with these versions. They do not detect the device. If you have a working phone, you can make a debrick image for me. Please install busybox and a terminal emulator. Then issue this command from the terminal and you will get the debrick image in your sd card.
su
busybox dd if=/dev/block/mmcblk0 of=/sdcard/debrick.img bs=1M count=128
Make sure you have SPH-L600 and android version 4.4 or the image will not work for me.
Please upload
Thanks
Click to expand...
Click to collapse
The only problem I have with the debrick image is if the 128mb will include my EFS information. I have to mount it to an extra SDcard I have and check it's content before I give it out or post it up for grabs.
Thank you for the how too but I am familiar with making a debrick image using TE. I have one made for all my devices although I haven't bothered checking to see what was exactly on this one being it is at 128mb ( as my SGS3 needs only just about half of the requested to work ) so I can provide the needed files.
Just to make things clear not all images being from other carriers will work on other devices of the same model. They may be partitioned a different way than the L600. Also you PM'd me that you tried to recover your EFS info using the created backup from one of a MK1. I wouldn't have tried that. You already upgraded to 4.4 and have the newest Knox bootloader which will not allow you to downgrade the Bootloader at all.
Thanks for the reply
DarkAngel said:
The only problem I have with the debrick image is if the 128mb will include my EFS information. I have to mount it to an extra SDcard I have and check it's content before I give it out or post it up for grabs.
Thank you for the how too but I am familiar with making a debrick image using TE. I have one made for all my devices although I haven't bothered checking to see what was exactly on this one being it is at 128mb ( as my SGS3 needs only just about half of the requested to work ) so I can provide the needed files.
Just to make things clear not all images being from other carriers will work on other devices of the same model. They may be partitioned a different way than the L600. Also you PM'd me that you tried to recover your EFS info using the created backup from one of a MK1. I wouldn't have tried that. You already upgraded to 4.4 and have the newest Knox bootloader which will not allow you to downgrade the Bootloader at all.
Click to expand...
Click to collapse
Thanks DarkAngel for your reply. My sprint mega was reprogrammed by myself with dfs tool. I didn't provisioned it with any commercial way. I just changed it to use uim to get operator information and it was working. But after i changed the rom to slimkat i lost esn from efs. That's why i tried to restore efs backup after 4.4 ota update.
I knew you are an expert or an android developer so i requested help from you. Because you have some threads that maybe possible by a developer. I am in a horrible situation. I took my phone the other day to my local jtag repair center an they failed to repair it. They said there is no support for this phone still now. Brother please help me to fix my phone. Thanks.
ashikrobi said:
Thanks DarkAngel for your reply. My sprint mega was reprogrammed by myself with dfs tool. I didn't provisioned it with any commercial way. I just changed it to use uim to get operator information and it was working. But after i changed the rom to slimkat i lost esn from efs. That's why i tried to restore efs backup after 4.4 ota update.
I knew you are an expert or an android developer so i requested help from you. Because you have some threads that maybe possible by a developer. I am in a horrible situation. I took my phone the other day to my local jtag repair center an they failed to repair it. They said there is no support for this phone still now. Brother please help me to fix my phone. Thanks.
Click to expand...
Click to collapse
Well not an expert but I read a lot on here and do what I can when I can.
This is what I got from my Mega:
Code:
L600 Output
====================
Disk /dev/block/mmcblk0: 15.8GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
[U]
Number Start End Size File system Name Flags[/U]
[B] 1 4194kB 67.1MB 62.9MB modem
2 67.1MB 67.2MB 131kB sbl1
3 67.2MB 67.5MB 262kB sbl2
4 67.5MB 68.0MB 524kB sbl3
5 68.0MB 70.1MB 2097kB aboot
6 70.1MB 70.6MB 524kB rpm
7 70.6MB 71.2MB 524kB tz
8 71.2MB 84.3MB 13.1MB pad
9 84.3MB 92.7MB 8389kB param[/B]
[COLOR=Red][B]10 92.7MB 107MB 14.3MB ext4 efs[/B][/COLOR]
11 107MB 110MB 3146kB modemst1
12 110MB 113MB 3146kB modemst2
13 113MB 124MB 10.5MB boot
14 124MB 134MB 10.5MB recovery
15 134MB 145MB 10.5MB fota
16 145MB 152MB 7332kB backup
17 152MB 155MB 3146kB fsg
18 155MB 155MB 8192B ssd
19 155MB 164MB 8389kB ext4 persist
20 164MB 176MB 12.6MB ext4 persdata
21 176MB 2324MB 2147MB ext4 system
22 2324MB 3058MB 734MB ext4 cache
23 3058MB 3079MB 21.0MB ext4 carrier
24 3079MB 15.8GB 12.7GB ext4 userdata
pit file of my mega
DarkAngel said:
Well not an expert but I read a lot on here and do what I can when I can.
This is what I got from my Mega:
Code:
L600 Output
====================
Disk /dev/block/mmcblk0: 15.8GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
[U]
Number Start End Size File system Name Flags[/U]
[B] 1 4194kB 67.1MB 62.9MB modem
2 67.1MB 67.2MB 131kB sbl1
3 67.2MB 67.5MB 262kB sbl2
4 67.5MB 68.0MB 524kB sbl3
5 68.0MB 70.1MB 2097kB aboot
6 70.1MB 70.6MB 524kB rpm
7 70.6MB 71.2MB 524kB tz
8 71.2MB 84.3MB 13.1MB pad
9 84.3MB 92.7MB 8389kB param[/B]
[COLOR=Red][B]10 92.7MB 107MB 14.3MB ext4 efs[/B][/COLOR]
11 107MB 110MB 3146kB modemst1
12 110MB 113MB 3146kB modemst2
13 113MB 124MB 10.5MB boot
14 124MB 134MB 10.5MB recovery
15 134MB 145MB 10.5MB fota
16 145MB 152MB 7332kB backup
17 152MB 155MB 3146kB fsg
18 155MB 155MB 8192B ssd
19 155MB 164MB 8389kB ext4 persist
20 164MB 176MB 12.6MB ext4 persdata
21 176MB 2324MB 2147MB ext4 system
22 2324MB 3058MB 734MB ext4 cache
23 3058MB 3079MB 21.0MB ext4 carrier
24 3079MB 15.8GB 12.7GB ext4 userdata
Click to expand...
Click to collapse
Take a loot at my pit file previously created with efs professional tool. Same like yours. I hope your debrick image will work for my mega. Please upload when possible. Do not worry about efs partition. I have my efs backup. I will restore mine. I have a question, if my phone becomes useable after using your debrick image and i restore only efs partition from efs backup will it brick again?
Thanks.
SPH-L600 sprint mega bad ESN
so as not to make a new topic, I decided to write here
I recently bought SPH-L600 sprint mega with a bad ESN, he came to me activated on Sprint and Sprint have sim I played settings and activation dropped sprint
but I live in another country and I can not activate it!
help somehow activate it! I bought an unlock code network, but said that he needed seller activation sprint!
any help would be much appreciated!
ashikrobi said:
Take a loot at my pit file previously created with efs professional tool. Same like yours. I hope your debrick image will work for my mega. Please upload when possible. Do not worry about efs partition. I have my efs backup. I will restore mine. I have a question, if my phone becomes useable after using your debrick image and i restore only efs partition from efs backup will it brick again?
Thanks.
Click to expand...
Click to collapse
Yes, they should be the same thing as we both have L600's. I didn't have a chance to look it over but I will try and get it to you later on today.
All you need is for your Mega to be able to get to Download Mode. Then and only then you will have to Odin a copy of the Official Firmware L600VPUBNE4 for it not to stay bricked but you probably already know that. As far as becoming usable that would be up to you, being able to restore your EFS data. In theory it should not brick but you need to only restore the EFS portion of the data.
Here is all the info I gathered from using Terminal Emulator in case you need it for file locations:
EFS is located: /dev/block/mmcblkop10
As you can see msm_sdcc.1 is specific to our device ( I noticed that it was the same on my SGS3 but not my SGN2 on KitKat ) so one can locate the by-name file to get the list below.
The second picture shows GNU Parted being run in my Terminal Emulator. You would need the Parted Binary file located here at the end of the Original Post.
Just extract the parted binary manually and then copy and paste it to the /system/bin folder with any File Explorer with Root access. After you paste the binary you will need to set the permissions to the parted binary you pasted to rwxr-xr-x or (0755). You can do this to any device you have and run it either in Terminal Emulator and even via ADB on your computer. Really handy to have sometimes.
Once you get the debrick image, below are two guides that I saved in my subscriptions that may help you. You may have them already.
deBricker
gTan64
---------- Post added at 05:31 AM ---------- Previous post was at 05:29 AM ----------
Ura535 said:
so as not to make a new topic, I decided to write here
I recently bought SPH-L600 sprint mega with a bad ESN, he came to me activated on Sprint and Sprint have sim I played settings and activation dropped sprint
but I live in another country and I can not activate it!
help somehow activate it! I bought an unlock code network, but said that he needed seller activation sprint!
any help would be much appreciated!
Click to expand...
Click to collapse
Actually this is an entirely different topic from Debricking a phone. You have a phone with a bad ESN. With that I can not help. If the previous owner ( or seller in your case ) "maybe" did not pay his bill, then your phone is locked out until it is released from his/her account by Sprint. If there is a way around this, I may not know.
I had this happen to me once before with my wife's Sprint SGS4. It was a pain but eventually two days later the seller finally came through and the phone was released for activation.
You should start a separate thread to see if you can get the right help and not get your question lost in this thread. I am sorry I couldn't help you any further.
Sorry you misunderstood
DarkAngel said:
Yes, they should be the same thing as we both have L600's. I didn't have a chance to look it over but I will try and get it to you later on today.
All you need is for your Mega to be able to get to Download Mode. Then and only then you will have to Odin a copy of the Official Firmware L600VPUBNE4 for it not to stay bricked but you probably already know that. As far as becoming usable that would be up to you, being able to restore your EFS data. In theory it should not brick but you need to only restore the EFS portion of the data.
Here is all the info I gathered from using Terminal Emulator in case you need it for file locations:
EFS is located: /dev/block/mmcblkop10
As you can see msm_sdcc.1 is specific to our device ( I noticed that it was the same on my SGS3 but not my SGN2 on KitKat ) so one can locate the by-name file to get the list below.
The second picture shows GNU Parted being run in my Terminal Emulator. You would need the Parted Binary file located here at the end of the Original Post.
Just extract the parted binary manually and then copy and paste it to the /system/bin folder with any File Explorer with Root access. After you paste the binary you will need to set the permissions to the parted binary you pasted to rwxr-xr-x or (0755). You can do this to any device you have and run it either in Terminal Emulator and even via ADB on your computer. Really handy to have sometimes.
Once you get the debrick image, below are two guides that I saved in my subscriptions that may help you. You may have them already.
deBricker
gTan64
---------- Post added at 05:31 AM ---------- Previous post was at 05:29 AM ----------
Actually this is an entirely different topic from Debricking a phone and on yours, you have a bad ESN. With that I can not help. If the previous owner ( or seller in your case ) "maybe" did not pay his bill, then your phone is locked out until it is released from his/her account by Sprint. If there is a way around this, I may not know.
I had this happen to me once before with my wife's Sprint SGS4. It was a pain but eventually two days later the seller finally came through and the phone was released for activation.
You should start a separate thread to see if you can get the right help and not get your question lost in this thread. I am sorry I couldn't help you any further.
Click to expand...
Click to collapse
Dark Angel you misunderstood my message i don't have bad esn. I lost esn number or corrupt it with dfs cdma tool. Dfs shows my esn but status from efs shows cps_na error. I didn't bought this phone second hand. My cousin send it from USA and she bought it new.
Thanks and i am waiting for your reply.
Off Topic Post / Misunderstanding .....
ashikrobi said:
Dark Angel you misunderstood my message i don't have bad esn. I lost esn number or corrupt it with dfs cdma tool. Dfs shows my esn but status from efs shows cps_na error. I didn't bought this phone second hand. My cousin send it from USA and she bought it new.
Thanks and i am waiting for your reply.
Click to expand...
Click to collapse
Yes I know, please disregard the quote and answer from the previous person responding above my post, right after the pictures I posted ( you will see the quote ). It was an off topic post and the forum combined them for some reason in the response for you ( probably because they were so close in time frame when I posted ) ..... I tried separating them in different posts but it still combined them together.
That is why off topic posts should be posted in a new thread/topic to avoid confusion......
DarkAngel said:
Yes I know, please disregard the quote and answer from the previous person responding above my post, right after the pictures I posted ( you will see the quote ). It was an off topic post and the forum combined them for some reason in the response for you ( probably because they were so close in time frame when I posted ) ..... I tried separating them in different posts but it still combined them together.
That is why off topic posts should be posted in a new thread/topic to avoid confusion......
Click to expand...
Click to collapse
Wow!!! Dark Angel, you are the man i was looking for. You know linux like a pro. Linux is my favorite operating system. I didn't know parted was available for android also. How do you learn these things?
By the way sorry, i though your message about bad esn was for me.
Thanks
ashikrobi said:
Wow!!! Dark Angel, you are the man i was looking for. You know linux like a pro. Linux is my favorite operating system. I didn't know parted was available for android also. How do you learn these things?
By the way sorry, i though your message about bad esn was for me.
Thanks
Click to expand...
Click to collapse
Well not a Pro..... I still have much more to learn but Linux is my favorite OS to use for anything Android related. A lot I still do on Windows.
Debrick Image......
Okay try this image.......
I burnt this image several time over on a class 4, 8 gig card and it wrote the image on it perfect. I don't know if you will have to use a 16gig card for your Mega or not but try what you have 16 gig or less. Trial and error at this point.
You can probably add more to it if need be from the Official Firmware by dragging and dropping ( if I am not mistaken ) by just opening ( and not extracting ) the tar.md5 with WinRAR or 7zip. I can't remember if one was able to do this.......
L600 Debrick Image
Not working
DarkAngel said:
Okay try this image.......
I burnt this image several time over on a class 4, 8 gig card and it wrote the image on it perfect. I don't know if you will have to use a 16gig card for your Mega or not but try what you have 16 gig or less. Trial and error at this point.
You can probably add more to it if need be from the Official Firmware by dragging and dropping ( if I am not mistaken ) by just opening the tar.md5 with WinRAR or 7zip. I can't remember.
L600 Debrick Image
Click to expand...
Click to collapse
DarkAngel I wrote the img file to a 16gb sdcard and tried to boot my phone but it's not working. I waited 5 min and tried several times. I also used a usbjig to boot into download mode but failed.
Have a look these terminal output:
sudo dd if=/home/tails/Downloads/debrick.img of=/dev/sdc
174080+0 records in
174080+0 records out
89128960 bytes (89 MB) copied, 75.5075 s, 1.2 MB/s
[email protected]:~/Downloads$ sudo parted /dev/sdc print
Error: Invalid argument during seek for read on /dev/sdc
Retry/Ignore/Cancel? Ignore
Error: The backup GPT table is corrupt, but the primary appears OK, so that will be used.
OK/Cancel? ok
Backtrace has 8 calls on stack:
8: /lib/i386-linux-gnu/libparted.so.0(ped_assert+0x29) [0xb773ad19]
7: /lib/i386-linux-gnu/libparted.so.0(+0x4649c) [0xb777749c]
6: /lib/i386-linux-gnu/libparted.so.0(ped_disk_new+0x55) [0xb7742275]
5: parted() [0x804ea2b]
4: parted(non_interactive_mode+0x8c) [0x8055c4c]
3: parted(main+0x1970) [0x804d5b0]
2: /lib/i386-linux-gnu/libc.so.6(__libc_start_main+0xf3) [0xb753aa83]
1: parted() [0x804d6e2]
You found a bug in GNU Parted! Here's what you have to do:
Don't panic! The bug has most likely not affected any of your data.
Help us to fix this bug by doing the following:
Check whether the bug has already been fixed by checking
the last version of GNU Parted that you can find at:
http://ftp.gnu.org/gnu/parted/
Please check this version prior to bug reporting.
If this has not been fixed yet or if you don't know how to check,
please visit the GNU Parted website:
http://www.gnu.org/software/parted
for further information.
Your report should contain the version of this release (2.3)
along with the error message below, the output of
parted DEVICE unit co print unit s print
and the following history of commands you entered.
Also include any additional information about your setup you
consider important.
Assertion (last_usable <= disk->dev->length) at ../../../libparted/labels/gpt.c:994 in function _parse_header() failed.
By the way is there any other way to recover from this state? I found qpst finds my phone after installing qhsusb_dload driver. Please help me.
Thanks
You are using an installed version of Linux correct? Are you on 13.04? Well I know the GNU Parted is just the program from Linux but the image still wrote on the SD card.
After the image was written to the SDcard, were you able to see the image content inside? For me it showed about 60MB of actual space written from the 85mb image. After it wrote, I just wrote over it and wrote over it and wrote over it again. Funny thing is I could not see the image at first so I then removed the card from my computer and re-inserted it and was then able to see it. I even inserted it on a Windows 8 tablet I have from a co-worker and it read it fine.
I did this while just using the "Install CD" and trying Ubuntu ( don't have it re-installed yet on my Notebook yet ). I did it using 14.04 LTS though. Try updating your GNU Parted ( your at 2.3 ), if it hasn't already been done, to the most current and re-write the image again.
DarkAngel said:
You are using an installed version of Linux correct? Are you on 13.04? Well I know the GNU Parted is just the program from Linux but the image still wrote on the SD card.
After the image was written to the SDcard, were you able to see the image content inside? For me it showed about 60MB of actual space written from the 85mb image. After it wrote, I just wrote over it and wrote over it and wrote over it again. Funny thing is I could not see the image at first so I then removed the card from my computer and re-inserted it and was then able to see it. I even inserted it on a Windows 8 tablet I have from a co-worker and it read it fine.
I did this while just using the "Install CD" and trying Ubuntu ( don't have it re-installed yet on my Notebook yet ). I did it using 14.04 LTS though. Try updating your GNU Parted ( your at 2.3 ), if it hasn't already been done, to the most current and re-write the image again.
Click to expand...
Click to collapse
Yes i am using an installed version of ubuntu 14.04. I was also not able to view partitions after i wrote the image to sdcard. But after i reinsert the card it showed all partitions and maybe mounted modem partition contents. I could view partitions with windows 7 also.
But when i try to boot the phone with this sdcard nothing happened. I tried several times but failed. What can i do now? DarkAngel please tell me a way to unbrick my phone.
Thanks
Hi all,
Thanks in advance for your help.
I've bricked--like totally bricked--my Nabi 2. On startup, it goes to the Nabi logo, flashes black for a moment and returns to the logo, and is unresponsive. I've tried starting up holding vol+, but nothing happens; no bootloader gets loaded.
How can I restore my device? I have installed nabilabs on my PC, but the Nabi device isn't recognized. I have installed both 32/64 bit drivers. I've also installed pdanet.
Thanks for your responses.
DB
dbbergen said:
Hi all,
Thanks in advance for your help.
I've bricked--like totally bricked--my Nabi 2. On startup, it goes to the Nabi logo, flashes black for a moment and returns to the logo, and is unresponsive. I've tried starting up holding vol+, but nothing happens; no bootloader gets loaded.
How can I restore my device? I have installed nabilabs on my PC, but the Nabi device isn't recognized. I have installed both 32/64 bit drivers. I've also installed pdanet.
Thanks for your responses.
DB
Click to expand...
Click to collapse
I have a similar situation. Major difference is that TWRP (v2.8.4.0) is installed and running, but there's no OS on it otherwise. I have tried various downloads (such as "246stock.zip", and TWRP says there was an error installing on ALL zip files I have tried. It can't be a bad download, since I have re-downloaded the files,. on different machines, and I get the same error each time. NabiLab and NabiLabGUI don't seem to work if there is not already a working OS on the tablet.
Seems like what I need is something like the microSD-based flash/install I used for my Nook Tablet (acclaim) to put CM11 on it. Is there, in fact, a way to outright flash a .IMG file of some sort onto this? Or have I already ruined this already worthless P.o.S.? At this point I'd be just as happy to run something like CyanogenMod on it, and forget the disaster that is the Nabi2 interface and bloatware (then hunt down some other utility for time and access controls).
Images tried, all of which gave me "Error flashing zip"
1937stock.zip
205stock.zip
2127stock.zip
246stock.zip
jelabarre59 said:
I have a similar situation. Major difference is that TWRP (v2.8.4.0) is installed and running, but there's no OS on it otherwise. I have tried various downloads (such as "246stock.zip", and TWRP says there was an error installing on ALL zip files I have tried. It can't be a bad download, since I have re-downloaded the files,. on different machines, and I get the same error each time. NabiLab and NabiLabGUI don't seem to work if there is not already a working OS on the tablet.
Seems like what I need is something like the microSD-based flash/install I used for my Nook Tablet (acclaim) to put CM11 on it. Is there, in fact, a way to outright flash a .IMG file of some sort onto this? Or have I already ruined this already worthless P.o.S.? At this point I'd be just as happy to run something like CyanogenMod on it, and forget the disaster that is the Nabi2 interface and bloatware (then hunt down some other utility for time and access controls).
Images tried, all of which gave me "Error flashing zip"
1937stock.zip
205stock.zip
2127stock.zip
246stock.zip
Click to expand...
Click to collapse
Those zips aren't flashable. You have to extract and restore them.
Do a back up of just the boot partition in TWRP. Just check "boot" and nothing else. Make sure you are backing up to external storage(MicroSD card)
Install 2.4.6 ROM and bootloader.
- Put SD card in computer. Navigate to the folder TWRP/BACKUPS/XXXX. XXX is a serial number unique to your Nabi.
- Make a new folder and call in whatever you want. So it should now look like TWRP/BACKUPS/XXX/yourfolder
- Unzip the 246stock.zip files you downloaded in to the "yourfolder" you created above. The files should look like ext4.system.win, emmc.boot.win, ext.addon.win, etc. This should set you up for the 2.4.6 ROM.
- Download this http://forum.xda-developers.com/showpost.php?p=50349692&postcount=89
- Copy it to the SDcard. This will be for the bootloader update.
- Put sdcard in Nabi
- Boot to TWRP
- Go to restore tab, and find the backup under the "yourfolder" you made and unzipped the files to.
- You should be able to select boot, system, and addon and skip the others.
- If everything restores then go to TWRP install tab, find the bootloader.zip you downloaded and install it.
- Reboot
Alternatively you can "restore" the new kitkat for Nabi. Just replace the instructions for 2.4.6 files above with these below.
3.0.13 stock zip
https://drive.google.com/file/d/0B08qqrSbn4djOFQ1a0cwQjVEV2M/view?usp=sharing
3.0.13 bootloader
https://drive.google.com/file/d/0B08qqrSbn4djcnVTYjI0dTJSQjA/view?usp=sharing
Not sure how bad your situation was but you may have to do a factory reset in TWRP as well. Try that if it doesn't boot after successfully doing the above.
aicjofs said:
Those zips aren't flashable. You have to extract and restore them.
Do a back up of just the boot partition in TWRP. Just check "boot" and nothing else. Make sure you are backing up to external storage(MicroSD card)
Install 2.4.6 ROM and bootloader.
- Put SD card in computer. Navigate to the folder TWRP/BACKUPS/XXXX. XXX is a serial number unique to your Nabi.
- Make a new folder and call in whatever you want. So it should now look like TWRP/BACKUPS/XXX/yourfolder
- Unzip the 246stock.zip files you downloaded in to the "yourfolder" you created above. The files should look like ext4.system.win, emmc.boot.win, ext.addon.win, etc. This should set you up for the 2.4.6 ROM.
- Download this http://forum.xda-developers.com/showpost.php?p=50349692&postcount=89
- Copy it to the SDcard. This will be for the bootloader update.
- Put sdcard in Nabi
- Boot to TWRP
- Go to restore tab, and find the backup under the "yourfolder" you made and unzipped the files to.
- You should be able to select boot, system, and addon and skip the others.
- If everything restores then go to TWRP install tab, find the bootloader.zip you downloaded and install it.
- Reboot
Alternatively you can "restore" the new kitkat for Nabi. Just replace the instructions for 2.4.6 files above with these below.
3.0.13 stock zip
https://drive.google.com/file/d/0B08qqrSbn4djOFQ1a0cwQjVEV2M/view?usp=sharing
3.0.13 bootloader
https://drive.google.com/file/d/0B08qqrSbn4djcnVTYjI0dTJSQjA/view?usp=sharing
Not sure how bad your situation was but you may have to do a factory reset in TWRP as well. Try that if it doesn't boot after successfully doing the above.
Click to expand...
Click to collapse
Just an update, I managed to get a warranty replacement, because it decided it didn't want to charge anymore. Got one of the newer units as a replacement, which has the much better power connector, and am running it as-is for the time being (their updated firmware isn't *as* bad, will have to see what happens with the Mattel ownership).
I am having the same type of issue. I currently have TWRP v2.3.3.0 (Nabi 1.9.3.7) installed, but it shows no OS installed. I attempted to restore to the 30.0.13 stock at got the following message:
E:Unable to wipe '/system'.
and got the Failed on the screen. I also attempted to use the wipe function on the system and got E: Unable to mount for /data, /data, /system, /cache, /data, /addon.
Any help would be greatly appreciated.
biglerad said:
I am having the same type of issue. I currently have TWRP v2.3.3.0 (Nabi 1.9.3.7) installed, but it shows no OS installed. I attempted to restore to the 30.0.13 stock at got the following message:
E:Unable to wipe '/system'.
and got the Failed on the screen. I also attempted to use the wipe function on the system and got E: Unable to mount for /data, /data, /system, /cache, /data, /addon.
Any help would be greatly appreciated.
Click to expand...
Click to collapse
You don't have the right TWRP version probably. That's the ICS version. Try the JB or KK version. http://forum.xda-developers.com/nabi-2/general/nabi-information-t3229119
OK, I had managed to repair the Nabi2s which was bricked before (the trick to "backup" the core files of the specific system, then extract files from 2_0_141107stock.zip), and restore. But for some reason it lost WiFi completely, so I figured I'd try re-flashing again. Now I have no TWRP, and cannot even make the device visible to boot to TWRP. Is it time to take out the sledgehammer, then send the pieces back to the founders at what used to be Fuhu?
I have gone round ans round on the site, tries to find which threads I had followed before, and I seriously think I NEVER want to buy another device where I can't wipe the HDD with a dd command, and boot an installer with a USB or DVD ever again.
jelabarre59 said:
OK, I had managed to repair the Nabi2s which was bricked before (the trick to "backup" the core files of the specific system, then extract files from 2_0_141107stock.zip), and restore. But for some reason it lost WiFi completely, so I figured I'd try re-flashing again. Now I have no TWRP, and cannot even make the device visible to boot to TWRP. Is it time to take out the sledgehammer, then send the pieces back to the founders at what used to be Fuhu?
I have gone round ans round on the site, tries to find which threads I had followed before, and I seriously think I NEVER want to buy another device where I can't wipe the HDD with a dd command, and boot an installer with a USB or DVD ever again.
Click to expand...
Click to collapse
If you can get to the bootloader screen you should be able to bring up fastboot and get TWRP back on tablet(or just boot to TWRP temporarily)
Did that tablet ever receive an update past KitKat?
No Wifi is usually one of two things.
1) Kernel(boot partition) doesn't match kernel modules(system partition). Fix: Restore both boot and system in TWRP.
2) The wifi conf is bad. Fix: Factory reset/wipe data partition Note: loses all personal data.
3) I suppose if there was an update past kitkat, maybe the bootloader or the misc partition got an update. Don't go down that route yet.
Here is the general flow for restoring things, should have everythin you need if you can get fastboot to come up:
https://forum.xda-developers.com/nabi-2/general/nabi-information-t3229119
My original(and only) notes on Nabi2s
https://forum.xda-developers.com/showpost.php?p=58603231&postcount=2504
https://forum.xda-developers.com/showpost.php?p=58623597&postcount=2507
aicjofs said:
If you can get to the bootloader screen you should be able to bring up fastboot and get TWRP back on tablet(or just boot to TWRP temporarily)
Click to expand...
Click to collapse
There's the problem. At this point the tablet only gets as far as the initial Nabi logo. Trying the "<Vol+><power>" option gives me the "Booting Android recovery..." followed shortl by the dead android. That's all the tablet will do.
Is there no way to make a microSD boot? That was what I would do with my Nook Tablet ("acclaim"). Seriously, whomever thought Android should be automatically locked out from the very people who bought/paid for/own the devices should be smacked by each and every Android user out there.
Thanks very much for the info. Took me 2 days to find this.
aicjofs said:
If you can get to the bootloader screen you should be able to bring up fastboot and get TWRP back on tablet(or just boot to TWRP temporarily)
Here is the general flow for restoring things, should have everythin you need if you can get fastboot to come up:
https://forum.xda-developers.com/nabi-2/general/nabi-information-t3229119
My original(and only) notes on Nabi2s
https://forum.xda-developers.com/showpost.php?p=58603231&postcount=2504
https://forum.xda-developers.com/showpost.php?p=58623597&postcount=2507
Click to expand...
Click to collapse
All these instructions presume I can get to a "recovery/bootloader" screen, which this tablet will NOT do. It gets the initial Nabi logo, and that's as far as it will ever go. You could leave it there for 5 hours and that's all it will do (happened to do that once letting it charge, and the Nabi likes to boot as soon as it gets power).
I would try your "nvflash", but it's a MSWin executable, and I'm running Linux.
I'm just wondering; if I had the appropriate image file, is there a way to do a raw dump/write to the USB port, forcing the data to a particular device? If I tail /var/log/syslog, then plug in the Nabi2s, I get these messages in the syslog (and nothing else from the tablet after that):
Code:
kernel: [ 5973.824134] usb 2-1: new high-speed USB device number 4 using ehci-pci
kernel: [ 5973.986609] ehci-pci 0000:00:1d.7: port 1 reset error -110
kernel: [ 5975.192071] usb 2-1: new high-speed USB device number 5 using ehci-pci
kernel: [ 5975.346686] ehci-pci 0000:00:1d.7: port 1 reset error -110
In theory there should be a raw device there somewhere (lsusb doesn't see it)
jelabarre59 said:
All these instructions presume I can get to a "recovery/bootloader" screen, which this tablet will NOT do. It gets the initial Nabi logo, and that's as far as it will ever go. You could leave it there for 5 hours and that's all it will do (happened to do that once letting it charge, and the Nabi likes to boot as soon as it gets power).
I would try your "nvflash", but it's a MSWin executable, and I'm running Linux.
I'm just wondering; if I had the appropriate image file, is there a way to do a raw dump/write to the USB port, forcing the data to a particular device? If I tail /var/log/syslog, then plug in the Nabi2s, I get these messages in the syslog (and nothing else from the tablet after that):
Code:
kernel: [ 5973.824134] usb 2-1: new high-speed USB device number 4 using ehci-pci
kernel: [ 5973.986609] ehci-pci 0000:00:1d.7: port 1 reset error -110
kernel: [ 5975.192071] usb 2-1: new high-speed USB device number 5 using ehci-pci
kernel: [ 5975.346686] ehci-pci 0000:00:1d.7: port 1 reset error -110
In theory there should be a raw device there somewhere (lsusb doesn't see it)
Click to expand...
Click to collapse
Keep in mind I had the Nabi 2S for all of a day, so what I am about to say only applies to the Nabi 2 not 2S. If you see no menu then there is a non functioning bootloader, or at least it doesn't load all the way. It won't front any USB port, and you won't see it with lusb. There is a way to manually start "forced recovery" though(or there was on the Nabi2) See this: https://forum.xda-developers.com/showpost.php?p=46694284&postcount=1701 If you can short the solder joints, I would assume the 2S has them too. That will start the 3pserver on the tegra itself, and bring up a USB interface. I don't think you need the APX driver for linux but you might check. There are plenty of linux nvflash binaries out there. Here is one that should work for tegra3 for sure: http://www.androidroot.mobi/pages/guides/tegra3-guide-nvflash-jellybean/ or search github and compile your own. That would allow what you want, however... I'm not sure where the bootloader partition is. In the notes I linked above I listed a cat /proc/partitions which I will markup below
179 0 15269888 mmcblk0
179 1 8192 mmcblk0p1 <---likely recovery partition but maybe boot
179 2 8192 mmcblk0p2 <---likely boot partition but maybe recovery
179 3 2048 mmcblk0p3 <---if like a Nabi 2 the EKS with crypto key
179 4 2048 mmcblk0p4 <---if like a Nabi 2 the linux backup partition table.
179 5 2097152 mmcblk0p5 <--- preload aka addon partition with all the Nabi apps and media
179 6 1572864 mmcblk0p6 <--- system partition
179 7 2097152 mmcblk0p7 <--- cache partition
179 8 2048 mmcblk0p8 <--- not sure
179 9 32768 mmcblk0p9 <---if like a Nabi 2 the USP or staging partition for placing blob files for flashing
179 10 2048 mmcblk0p10 <---Not sure
179 11 9435136 mmcblk0p11 <--- data partition
179 32 4096 mmcblk0boot1
179 16 4096 mmcblk0boot0
The problem here is the Nabi 2 had a 6MB partition that was clearly the bootloader. A 2MB that was the Nvidia/Tegra partition table(different structure then a linux PT), and a 4MB partition for the device parameters. Those are "nvidia partitions" and don't show up in the linux partition table. For the Nabi 2 the bootloader was nvidia partition 4
I would go about it like this:
Tear open the Nabi and see if it has the pins to force tegra to 3pserver
Get nvflash binary or compile one
Get the bootloader.bin from here(note the name is bootloader2S.bin and the commands below I have bootloader.bin so rename it: https://forum.xda-developers.com/showpost.php?p=58603231&postcount=2504
Force the tablet to 3pserver with the pins
Check to see if it's there with lusb
Use the commands(if you are a linux guy I assume you know you may need sudo, or ./nvflash, etc, etc)
nvflash --bl bootloader.bin --getpartitiontable partitiontable.txt
^^^examine the partitiontable.txt and see if it clarifies where the bootloader might be. They like to call it EBT in tegra. I would tell you how to flash the botloader but I just don't know where it is. The bootloader tries to load the boot.img from the boot partition, and has some sort of watchdog where if it doesn't load boot.img in such and such amount of time, it will try and load recovery.img. If that doesn't happen it just sits there staring at you. You could try and flash boot and recovery and maybe that brings you back to something more familiar. Examine the partition table text and find out which is boot and recovery. Boot is usually LNX, and recovery SOS.
If you are still in nvflash mode after all of this and havent shut down the tablet use commands below. If you have to restart you need have a first command of "nvflash --bl bootloader.bin <some command>" then all subsequent commands just need "nvflash --resume <some command>"
If it's exactly like a Nabi 2 then this would be the flow. So if your partitiontable.txt shows EBT as 4, SOS as 7, and LNX as 8
nvflash --resume --rawdeviceread 0 3072 nabibricksafe.img
nvflash --resume --read 4 04_EBT_raw.img
nvflash --resume --read 7 07_SOS_raw.img
nvflash --resume --read 8 08_LNX_raw.img
<optional>
nvflash --resume --download 4 bootloader.bin
nvflash --resume --download 7 twrp.img
nvflash --resume --download 8 twrp.img
nvflash --resume --go
^^^I have no idea about the 3072. That gets the first 3 "nvidia partitions" on a Nabi2 but that may not be long enough for a 2S, you can make it a larger read to be on the safe side(maybe 6000). You are basically reading the critical part of the tablet, backing up the current partition 4, 7, and 8, before reloading 7,8 with TWRP. Then tablet should restart. Remember if you have to restart the tablet the "resume" won't work, you will need to issue something with -bl bootloader.bin after a fresh boot as the first command of the session. You could add
nvflash --resume --download 4 bootloader.bin
in the above if the partition table confirms its the bootloader partition(EBT). In fact that may actually be the ONLY command you need to bring back the bootloader text, I'm just being cautious since it's not my tablet and taking a conservative approach.
That will put TWRP in both boot and recovery partitions so that hopefully you can boot TWRP somehow. If we can, then we can go back and fix things in TWRP. This may be all you need.
Side note: I never used nvflash on a 2S so who even knows if all this typing means anything, and maybe the emmc is just bad and none of this matters. I'm just try to give you all the major things I can think of to save you time. Good luck!
jelabarre59 said:
Just an update, I managed to get a warranty replacement, because it decided it didn't want to charge anymore. Got one of the newer units as a replacement, which has the much better power connector, and am running it as-is for the time being (their updated firmware isn't *as* bad, will have to see what happens with the Mattel ownership).
Click to expand...
Click to collapse
Thank you very much you saved my day
---------- Post added at 08:10 AM ---------- Previous post was at 08:08 AM ----------
aicjofs said:
Keep in mind I had the Nabi 2S for all of a day, so what I am about to say only applies to the Nabi 2 not 2S. If you see no menu then there is a non functioning bootloader, or at least it doesn't load all the way. It won't front any USB port, and you won't see it with lusb. There is a way to manually start "forced recovery" though(or there was on the Nabi2) See this: https://forum.xda-developers.com/showpost.php?p=46694284&postcount=1701 If you can short the solder joints, I would assume the 2S has them too. That will start the 3pserver on the tegra itself, and bring up a USB interface. I don't think you need the APX driver for linux but you might check. There are plenty of linux nvflash binaries out there. Here is one that should work for tegra3 for sure: http://www.androidroot.mobi/pages/guides/tegra3-guide-nvflash-jellybean/ or search github and compile your own. That would allow what you want, however... I'm not sure where the bootloader partition is. In the notes I linked above I listed a cat /proc/partitions which I will markup below
179 0 15269888 mmcblk0
179 1 8192 mmcblk0p1 <---likely recovery partition but maybe boot
179 2 8192 mmcblk0p2 <---likely boot partition but maybe recovery
179 3 2048 mmcblk0p3 <---if like a Nabi 2 the EKS with crypto key
179 4 2048 mmcblk0p4 <---if like a Nabi 2 the linux backup partition table.
179 5 2097152 mmcblk0p5 <--- preload aka addon partition with all the Nabi apps and media
179 6 1572864 mmcblk0p6 <--- system partition
179 7 2097152 mmcblk0p7 <--- cache partition
179 8 2048 mmcblk0p8 <--- not sure
179 9 32768 mmcblk0p9 <---if like a Nabi 2 the USP or staging partition for placing blob files for flashing
179 10 2048 mmcblk0p10 <---Not sure
179 11 9435136 mmcblk0p11 <--- data partition
179 32 4096 mmcblk0boot1
179 16 4096 mmcblk0boot0
The problem here is the Nabi 2 had a 6MB partition that was clearly the bootloader. A 2MB that was the Nvidia/Tegra partition table(different structure then a linux PT), and a 4MB partition for the device parameters. Those are "nvidia partitions" and don't show up in the linux partition table. For the Nabi 2 the bootloader was nvidia partition 4
I would go about it like this:
Tear open the Nabi and see if it has the pins to force tegra to 3pserver
Get nvflash binary or compile one
Get the bootloader.bin from here(note the name is bootloader2S.bin and the commands below I have bootloader.bin so rename it: https://forum.xda-developers.com/showpost.php?p=58603231&postcount=2504
Force the tablet to 3pserver with the pins
Check to see if it's there with lusb
Use the commands(if you are a linux guy I assume you know you may need sudo, or ./nvflash, etc, etc)
nvflash --bl bootloader.bin --getpartitiontable partitiontable.txt
^^^examine the partitiontable.txt and see if it clarifies where the bootloader might be. They like to call it EBT in tegra. I would tell you how to flash the botloader but I just don't know where it is. The bootloader tries to load the boot.img from the boot partition, and has some sort of watchdog where if it doesn't load boot.img in such and such amount of time, it will try and load recovery.img. If that doesn't happen it just sits there staring at you. You could try and flash boot and recovery and maybe that brings you back to something more familiar. Examine the partition table text and find out which is boot and recovery. Boot is usually LNX, and recovery SOS.
If you are still in nvflash mode after all of this and havent shut down the tablet use commands below. If you have to restart you need have a first command of "nvflash --bl bootloader.bin <some command>" then all subsequent commands just need "nvflash --resume <some command>"
If it's exactly like a Nabi 2 then this would be the flow. So if your partitiontable.txt shows EBT as 4, SOS as 7, and LNX as 8
nvflash --resume --rawdeviceread 0 3072 nabibricksafe.img
nvflash --resume --read 4 04_EBT_raw.img
nvflash --resume --read 7 07_SOS_raw.img
nvflash --resume --read 8 08_LNX_raw.img
<optional>
nvflash --resume --download 4 bootloader.bin
nvflash --resume --download 7 twrp.img
nvflash --resume --download 8 twrp.img
nvflash --resume --go
^^^I have no idea about the 3072. That gets the first 3 "nvidia partitions" on a Nabi2 but that may not be long enough for a 2S, you can make it a larger read to be on the safe side(maybe 6000). You are basically reading the critical part of the tablet, backing up the current partition 4, 7, and 8, before reloading 7,8 with TWRP. Then tablet should restart. Remember if you have to restart the tablet the "resume" won't work, you will need to issue something with -bl bootloader.bin after a fresh boot as the first command of the session. You could add
nvflash --resume --download 4 bootloader.bin
in the above if the partition table confirms its the bootloader partition(EBT). In fact that may actually be the ONLY command you need to bring back the bootloader text, I'm just being cautious since it's not my tablet and taking a conservative approach.
That will put TWRP in both boot and recovery partitions so that hopefully you can boot TWRP somehow. If we can, then we can go back and fix things in TWRP. This may be all you need.
Side note: I never used nvflash on a 2S so who even knows if all this typing means anything, and maybe the emmc is just bad and none of this matters. I'm just try to give you all the major things I can think of to save you time. Good luck!
Click to expand...
Click to collapse
Thank you guys keep up the good work
Hello i have a serious problem with nabi jr tab of my friend's , the model no. is SNBJR-MT5C , my friend was using busybox and adb , when he tried to add .bak file for fuhu in system/apps ,because he wanted to get rid of the password each time device starts, this resulted in a bootloop , because there was no twrp installed , as this device was running kitkat , he tried using a backup from here somewhere in xda but without scatter and files.md5 , so he manually make files.md5 and generated scatter from mtk droid tools from firmware.info , but when he tried flash from sp flash tool , it did not accept that scatter, because pre-loader and mbr has start address 0 , because scatter version was wrong, mtk droid tools generated MT6582_sctter.txt, but it was MT8127 SoC , MT6582 - v111, MT8127 - v112 , so he got v112 from somewhere , and then retried and it got DA(Download Agent) error , so he made a mistake and changed DA and it bricked it completely , now its black screen and it wont turn on , even wont go in fastboot/recovery mode by holding power button and volume + or - buttons , also not showing anything in pc device manager , its totally dead , does anyone had the same experience ? or can anyone guide me about anything? Thanks
aicjofs said:
Keep in mind I had the Nabi 2S for all of a day, so what I am about to say only applies to the Nabi 2 not 2S. If you see no menu then there is a non functioning bootloader, or at least it doesn't load all the way. It won't front any USB port, and you won't see it with lusb. There is a way to manually start "forced recovery" though(or there was on the Nabi2)
Click to expand...
Click to collapse
I managed to get all the pieces of my daughter's Nabi 2S in one place (well, except for the bumper, I had multiples so I must have one still available. But did find the right charger cable). Since she has a different tablet to use for now (I was given 4 XO tablets; one, maybe two actually work) I could send this to a developer who wants to dabble with the hardware. Mind you, it's bricked, so it powers up but can't get to recovery menus, etc. The Nabi 2S doesn't appear to have the solder joints to do a forced recovery, but there is something that looks like it might be a button to do the same thing.
It's April 2018, if there's a developer who wants to try out other experiments on a Nabi2s that's otherwise bricked, you can still contact me. The Nabi is sitting in a box in the closet, it's not doing anything, and my daughter is now using an OLPC OX tablet instead (hey, got 4 of them for free, 2 actually power up).
(yeah, want to re-flash that second one someday as well, just to get it to a clean, stripped-down base to start from).
Hello bro I have a different situation here I have a nabi 2 nv7a I installed twrp on it and deleted the previous ROM to install new one but unfortunately when I try to install any ROM it shows error e\ unable to mount storage then I figured that the solution for it is to change the type of internal storage but the twrp I installed doesn't have any option of changing the type I went to wipe internal storage there was only one option that swipes and when I wipes then it also shows e/unable to mount and there is no option of changing type and I'm unable to change my twrp because I have no is plssss someone help
Hey guys,
unfortunately i think i bricked my prime
Today i flashed crombi-kk rom which worked flawlessly fine. I came from HairyBean 2.31 so all i did was to up update my TWRP via fastboot and then flash the rom. As said, that worked fine. After my first boot of the rom i thought that i would like to test the "F2FS" option. For this i updated TWRP to v2.8 via the zip-file from this thread: http://forum.xda-developers.com/showthread.php?t=2772093 . This also worked and i've got my TWRP to the new version.
Now i wanted to format the /data partition to F2FS so i went to
Wipe>>Advanced Wipe>>Choose Data>>Repair or Change File System>>Change File System>>F2FS
At this time it told me that it can't UNmount the partition and therefore it couldn't change the file-system.
Dumb as i am i thought: "Okay, then why don't just unmount the partition" so i did this (Mount>>Disabled "Data") an then retried to format the data partition with f2fs. During this process i have to assume that something went wrong? It gave me some error which i fool can't remember.
From this point i couldn't access the /data partition anymore, i can't mount it nor can i boot into Android.
I still have access to TWRP and can get to fastboot access. I have no ADB Access in TWRP - it just can't recognize the prime. In Windows-Hardware Manager it just says: Transformer?! (i have universal naked driver installed)
Forget the last sentence - it seems that my USB-Cable is partly broken. Sometimes it recognizes the prime and sometimes not!
Is it gone forever or is there still hope to recover it?
Hopefully someone can help me, i'm really desperate
P.S.: D didn't want to make things worse, so i stopped messing around with it - would it help to reflash the ne0zone75_tf300t.blob file? Is this even possible if i already updated the TWRP to a newer version?
NiffStipples said:
I still have access to TWRP and can get to fastboot access.
Click to expand...
Click to collapse
As long as this is the fact, we don' t call it 'bricked'.
Try following one after another:
1. TWRP>>Wipe>>Advanced>>[check / data]>>repair file system, flash ROM again.
2. Fastboot:
Code:
fastboot -i 0x0b05 erase userdata
- then flash ROM again.
3. Last ressort: Flash stock ROM and start from scratch.
... hope you've pulled your nvflash files. Good luck!
... you might also want to flash another TWRP, though ne0zone75's normally works well. Try the official 2.8.3.0 (for tf300t because you are on Hairy Bean), works good with my prime.
Thanks a lot for your reply
I've tried the steps you provided:
1) While repairing the data partition it said again that it can't mount the data partition. (Picture of it in the attachment)
2) Reflasing the rom worked okay but as expected it couldn't boot (stuck in bootscreen) - in TWRP the /data partiton was again unmountable
3) erasing the userdata via fastboot gave me the following:
Code:
erasing 'userdata'...
FAILED (command write failed (Invalid argument))
finished. total time: 0.002s
At this time i didn't tried to reflash the rom because i don't think it would change anything?!
4) i only have the old nvflash files from ages ago when i started flashing with androwook - i fear they are the wrong ones? I don't have any clue what to do with these - are there good instructions to get the tab back to it's factory state?
Last but not least - do you have a link for the right TWRP you're talking about. I don't want to gave the wrong one a try
NiffStipples said:
Thanks a lot for your reply
I've tried the steps you provided:
1) While repairing the data partition it said again that it can't mount the data partition. (Picture of it in the attachment)
2) Reflasing the rom worked okay but as expected it couldn't boot (stuck in bootscreen) - in TWRP the /data partiton was again unmountable
3) erasing the userdata via fastboot gave me the following:
Code:
erasing 'userdata'...
FAILED (command write failed (Invalid argument))
finished. total time: 0.002s
At this time i didn't tried to reflash the rom because i don't think it would change anything?!
Click to expand...
Click to collapse
Sounds as if partition table is faulty.
1. You could try to redo the Hairy Bean procedure.
2. If you feel lucky, then you could try to format partition manually using
Code:
mkfs.ext4 /dev/block/mmcblk0p8
4) i only have the old nvflash files from ages ago when i started flashing with androwook - i fear they are the wrong ones?
Click to expand...
Click to collapse
nvflash files don't grow sour; you could try without changing to wheelie your blob.bin. If it works, you are safe and can continue with the other blobs.
I don't have any clue what to do with these - are there good instructions to get the tab back to it's factory state?
Click to expand...
Click to collapse
Best instruction you find here: http://forum.xda-developers.com/showthread.php?t=1894867
Last but not least - do you have a link for the right TWRP you're talking about. I don't want to gave the wrong one a try
Click to expand...
Click to collapse
I have actually the (official) one from http://www.techerrata.com/browse/twrp2/tf300t
Good Luck!
Okay, now i know why they always say that flashing is nothing for noobs
I'm a little bit confused - what (in your opinion) is the best shot i should give a try?
Formatting manually (from where? In TWRP or via adb? I'm on Windows)
Reflash everything with NVFLASH (is that possible without any hassle - the NVFLASH files are from ICS-times and i'm on JB/KK?!)
I know it's annoying to help someone who doesn't know what he's doing - hope you have time to get me through this flashing nightmare :/
NiffStipples said:
Okay, now i know why they always say that flashing is nothing for noobs
Click to expand...
Click to collapse
Everybody starts as a noob.
I'm a little bit confused - what (in your opinion) is the best shot i should give a try?
Formatting manually (from where? In TWRP or via adb? I'm on Windows)
Click to expand...
Click to collapse
I would first do that manually from TWRP>>Advanced>>Terminal Command>>Select Folder (root)>>type in: mkfs.ext4 /dev/block/mmcblk0p8
Reflash everything with NVFLASH (is that possible without any hassle - the NVFLASH files are from ICS-times and i'm on JB/KK?!)
Click to expand...
Click to collapse
Important is, that blob.bin works with
Code:
wheelie.exe -r --blob blob.bin
After that you should flash 'bricksafeTF201.img' and 'unlock-token-TF201'. Then you can flash any blobs of unblobbed ROMs you can find in the internet or flash stock ROM (JB). Then proceed to fastboot custom recovery and zipflash custom ROM.
I know it's annoying to help someone who doesn't know what he's doing - hope you have time to get me through this flashing nightmare :/
Click to expand...
Click to collapse
I went through any misstep you can think of with the three of 'em: TF201, TF300T, TF700T.
Mmmmh, the command
Code:
mkfs.ext4 /dev/block/mmcblk0p8
gives me back:
Code:
mkfs.ext4: not found
NiffStipples said:
Mmmmh, the command
Code:
mkfs.ext4 /dev/block/mmcblk0p8
gives me back:
Code:
mkfs.ext4: not found
Click to expand...
Click to collapse
Oops! My bad, try
Code:
make_ext4fs /dev/block/mmcblk0p8
.
.... for information's sake type
Code:
fdisk -l /dev/block/mmcblk0p8
You should get
Code:
Disk /dev/block/mmcblk0p8: 29.6 GB, 29618601984 bytes
4 heads, 16 sectors/track, 903888 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Hooray! :victory: Thanks a lot - everything is back where it belongs
Just for the learning effect - do you have any idea what did go wrong in my case and how would i correctly change the format of the data partition to f2fs? I think i've read a lot of times that this would improve rom speeds a lot?!
NiffStipples said:
Hooray! :victory: Thanks a lot - everything is back where it belongs
Just for the learning effect - do you have any idea what did go wrong in my case and how would i correctly change the format of the data partition to f2fs? I think i've read a lot of times that this would improve rom speeds a lot?!
Click to expand...
Click to collapse
Congrats!
If you would care to tell what you did last, one could make a guess, what went wrong.
... and yes, changing /data (only!) to f2fs makes a tremendous difference in speed. Normally TWRP complies the job without probs. What TWRP do you have now?
I prefer @ne0zone75's which I linked some posts before. They work on all my tabs.
I have installed v2.8.3.0 from the site you gave me above
Mh, as said in the first post i did the following steps to change the format
I tried Wipe>>Advanced Wipe>>Checked "Data">>Repair or Change File System>>Change File System>>Choose F2FS
Then the system gave me an error that it couldn't access the partition because it was mounted or couldn't be unmounted or something like this
So i went back to Mount>>unchecked "Data"
And then again to Advanced Wipe>>...>>Change File System>>F2FS
After that something went wrong because after that step i couldn't mount the data partition anymore?!
NiffStipples said:
I have installed v2.8.3.0 from the site you gave me above
Mh, as said in the first post i did the following steps to change the format
I tried Wipe>>Advanced Wipe>>Checked "Data">>Repair or Change File System>>Change File System>>Choose F2FS
Then the system gave me an error that it couldn't access the partition because it was mounted or couldn't be unmounted or something like this
So i went back to Mount>>unchecked "Data"
And then again to Advanced Wipe>>...>>Change File System>>F2FS
After that something went wrong because after that step i couldn't mount the data partition anymore?!
Click to expand...
Click to collapse
Yes, but what did you to fix it then?
Oh sorry, now i get it
I just used your command for repartitioning(?!?): make_ext4fs /dev/block/mmcblk0p8
I am still of two minds of f2fs on these tablets.. Just gone back to ext4 to compare... As was getting to sticky on the F2fs with redraws and lag..
Anyway good to hear a successful conclusion on the come back by the OP
NiffStipples said:
Oh sorry, now i get it
I just used your command for repartitioning(?!?): make_ext4fs /dev/block/mmcblk0p8
Click to expand...
Click to collapse
Good! Glad, it helped you. Now you could try the 'mkfs.f2fs' command also.
Already tried that - this time it worked without problems :highfive:
Thanks again for the great help!! F2FS brings the prime to a whole new level, now i just have to figure out how to change the dock layout language
NiffStipples said:
Already tried that - this time it worked without problems :highfive:
Thanks again for the great help!! F2FS brings the prime to a whole new level, now i just have to figure out how to change the dock layout language
Click to expand...
Click to collapse
That should be no problem. If you click in dock, there should be a keyboard icon in notification area, clicking it settings dialog will appear. Additional in settings>>language and input>>physical keyboard you can set keyboard layout of dock.
das chaos said:
Oops! My bad, try
Code:
make_ext4fs /dev/block/mmcblk0p8
.
.... for information's sake type
Code:
fdisk -l /dev/block/mmcblk0p8
You should get
Code:
Disk /dev/block/mmcblk0p8: 29.6 GB, 29618601984 bytes
4 heads, 16 sectors/track, 903888 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Click to expand...
Click to collapse
DC,
I wonder if this is why my f2fs where playing up for me?
using your commands I get the following..
Code:
[email protected]:/ $ su
[email protected]:/ # fdisk -l /dev/block/mmcblk0p8
Disk /dev/block/mmcblk0p8: 29.6 GB, 29618601984 bytes
4 heads, 16 sectors/track, 903888 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Disk /dev/block/mmcblk0p8 doesn't contain a valid partition table
[email protected]:/ #
Disk /dev/block/mmcblk0p8 doesn't contain a valid partition table
this is what I am looking at as a problem maybe?
is there a terminal command to see all the partitions and sizes?
I might have to take this thing back to scratch and start again as been flashing left right and center on it of late.
dgcruzing said:
DC,
I wonder if this is why my f2fs where playing up for me?
using your commands I get the following..
Code:
[email protected]:/ $ su
[email protected]:/ # fdisk -l /dev/block/mmcblk0p8
Disk /dev/block/mmcblk0p8: 29.6 GB, 29618601984 bytes
4 heads, 16 sectors/track, 903888 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Disk /dev/block/mmcblk0p8 doesn't contain a valid partition table
[email protected]:/ #
Disk /dev/block/mmcblk0p8 doesn't contain a valid partition table
this is what I am looking at as a problem maybe?
is there a terminal command to see all the partitions and sizes?
I might have to take this thing back to scratch and start again as been flashing left right and center on it of late.
Click to expand...
Click to collapse
No that's normal for f2fs, only fat systems have readable PT. What I was interested was geometry of fs and that is the same as mine. So everything is o.k. You have your tab up and running - that counts.
There is a free app Storage Partitions in the store, which can do no more than show information about partitions. Mainly an exploit of commands
Code:
cat /proc/mounts
and
Code:
cat /proc/partitions
das chaos said:
No that's normal for f2fs, only fat systems have readable PT. What I was interested was geometry of fs and that is the same as mine. So everything is o.k. You have your tab up and running - that counts.
There is a free app Storage Partitions in the store, which can do no more than show information about partitions. Mainly an exploit of commands
Code:
cat /proc/mounts
and
Code:
cat /proc/partitions
Click to expand...
Click to collapse
Used that one and another to have a look..
This is what I get, just for the hell of it..
As said for me.. F2Fs on this one doesn't play nice and the last few days I am back to Ext4..
Running it in and let it settled, putting it through its paces with plenty of tabs in chrome open and multitasking back and forwards in to Tapatalk and it runs normal with out lag and redraws..
I am using apex as a launcher and under F2Fs with kept in memory set..it was redrawing to the max and timing out from coming out of sleep..
Playing with other tweaks to see if can get it to a sweet spot.
Will let it settle for a few days and play then swop back and see which is better with the tweaks added
Phone is Elephone P7000, I can flash various stock roms and custom to it, doesn't boot into recovery unless I use CWM, which I can boot into and connect via adb.
Chip is MT6752, I've never flashed over bootloader or userdata, just the rest. Got it working a couple times, with different roms though would freeze after a while or a x has stopped working (I've had this phone since it was released and never updated the stock rom - I got the x has stopped working error before ever flashing anything and it got stuck in a boot loop after that), resetting stuck in boot loop, haven't got it working since then despite multiple flashing attempts. I have not tried firmware upgrade with SP Tool since that does the whole lot also haven't tried formatting.
Typically rebooting from CWM would help (just regular, not into fastboot), but to no avail anymore.
Memory Test on sptool passed everything except for nand flash which says it was not found.
in adb shell frompc via CWM recovery running.
fdisk -l /dev/block/mmcblk0
fdisk: can't open '/dev/blockmmcblk0': I/O error
obviously mmcblk1 (the external SD card) works just fine.
parted /dev/block/mmcblk0 print
Error: /dev/block/mmcblk0: unrecognised disk label
Again mmcblk1 will be fine.
It shows up using cat /proc/partitions
major minor #blocks name
179 0 15267840 mmcblk0
e2fsck /dev/block/mmcblk0
e2fsck: Attempt to read block from filesystem resulted in short read while trying to open /dev/block/mmcblk0
Could this be a zero-length partition?
C:\adb>adb shell
~ # mke2fs -n /dev/block/mmcblk0
mke2fs -n /dev/block/mmcblk0
mke2fs 1.41.14 (22-Dec-2010)
Filesystem label=
OS type: Linux
Block size=4096 (log=2)
Fragment size=4096 (log=2)
Stride=0 blocks, Stripe width=0 blocks
954720 inodes, 3816960 blocks
190848 blocks (5.00%) reserved for the super user
First data block=0
Maximum filesystem blocks=3909091328
117 block groups
32768 blocks per group, 32768 fragments per group
8160 inodes per group
Superblock backups stored on blocks:
32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208
~
Is there any chance of repairing this partition with a tool like you can on a PC?
Otherwise what should I do from here?
Athiril said:
Phone is Elephone P7000, I can flash various stock roms and custom to it, doesn't boot into recovery unless I use CWM, which I can boot into and connect via adb.
Chip is MT6752, I've never flashed over bootloader or userdata, just the rest. Got it working a couple times, with different roms though would freeze after a while or a x has stopped working (I've had this phone since it was released and never updated the stock rom - I got the x has stopped working error before ever flashing anything and it got stuck in a boot loop after that), resetting stuck in boot loop, haven't got it working since then despite multiple flashing attempts. I have not tried firmware upgrade with SP Tool since that does the whole lot also haven't tried formatting.
Typically rebooting from CWM would help (just regular, not into fastboot), but to no avail anymore.
Memory Test on sptool passed everything except for nand flash which says it was not found.
in adb shell frompc via CWM recovery running.
fdisk -l /dev/block/mmcblk0
fdisk: can't open '/dev/blockmmcblk0': I/O error
obviously mmcblk1 (the external SD card) works just fine.
parted /dev/block/mmcblk0 print
Error: /dev/block/mmcblk0: unrecognised disk label
Again mmcblk1 will be fine.kcuf
It shows up using cat /proc/partitions
major minor #blocks name
179 0 15267840 mmcblk0
Is there any chance of repairing this partition with a tool like you can on a PC?
Otherwise what should I do from here?
Click to expand...
Click to collapse
Ok bro heres how to repair your phone.You need a firmware image of your device and you need some way to flash it.Google
"your device" firmware then download and flash it.Everything will be repaired and your device will be in working order.
boyam99 said:
Ok bro heres how to repair your phone.You need a firmware image of your device and you need some way to flash it.Google
"your device" firmware then download and flash it.Everything will be repaired and your device will be in working order.
Click to expand...
Click to collapse
I'm not sure if you read what I've written, I've reflashed the phone repeatedly, apart from the preloader since that could be disastrous, and userdata partitions.
Anyone else reading: I want to try parted mklabel to give it a new label, but not sure what label to give it, and then try resuce under parted.
Athiril said:
I'm not sure if you read what I've written, I've reflashed the phone repeatedly, apart from the preloader since that could be disastrous, and userdata partitions.
Anyone else reading: I want to try parted mklabel to give it a new label, but not sure what label to give it, and then try resuce under parted.
Click to expand...
Click to collapse
hey am trying to help you dont say am not helping
---------- Post added at 08:39 AM ---------- Previous post was at 08:30 AM ----------
Athiril said:
I'm not sure if you read what I've written, I've reflashed the phone repeatedly, apart from the preloader since that could be disastrous, and userdata partitions.
Anyone else reading: I want to try parted mklabel to give it a new label, but not sure what label to give it, and then try resuce under parted.
Click to expand...
Click to collapse
do u have a backup of your device.If the stock rom isnt working its either a software problem or its the phone
---------- Post added at 08:39 AM ---------- Previous post was at 08:39 AM ----------
Athiril said:
I'm not sure if you read what I've written, I've reflashed the phone repeatedly, apart from the preloader since that could be disastrous, and userdata partitions.
Anyone else reading: I want to try parted mklabel to give it a new label, but not sure what label to give it, and then try resuce under parted.
Click to expand...
Click to collapse
do u have a backup of your device.If the stock rom isnt working its either a software problem or its the phone