Related
I believe I narrowed down my problem to needing to format the different mmcblk’s so I can get one of the different recoveries to restore the image. As to what I have tried and have not keep reading.
So one day decided to try cm7 via SD Card, and it looked impressive. However It said something about issues with the sd card. I had no Idea what it would do to the nook ( I should've read the the instructions more thoroughly)
So I reboot only to find the nook looping back to cwm recovery (it was rooted).
After some searching I try the Ubuntu restore. It got stuck at the MLO part, I decided maybe it takes a while and i guess it Zeroed out mmcblk5 (I guess i'm not sure of anything at this point). The only issue later I find is that Ubuntu doesn't do any formatting, it just blanks out the partition and reloads it. After that failed attempt CWM just freezes at the cardboard box
I gave this a try
http://forum.xda-developers.com/showthread.php?t=1663836
but it spends a while with 1 red x and then reboots into locked recovery.
Giving it another try, I start apply the method described in:
http://forum.xda-developers.com/showthread.php?t=1605664
but “scripts” zip file gives a 404 error at Drop box.... the other files worked like a charm. It did get me pretty close and gave me this state (3 drives formatted in ext, I just need the others to format and restore). Thanks meghd00t!
List of devices attached
0000000000000000 recovery
~ # parted /dev/block/mmcblk0
parted /dev/block/mmcblk0
GNU Parted 1.8.8.1.179-aef3
Using /dev/block/mmcblk0
Welcome to GNU Parted! Type 'help' to view a list of commands.
(parted) print
print
print
Model: MMC MAG4FB (sd/mmc)
Disk /dev/block/mmcblk0: 15.6GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Number Start End Size File system Name Flags
1 131kB 262kB 131kB xloader
2 262kB 524kB 262kB bootloader
3 524kB 16.3MB 15.7MB recovery
4 16.3MB 33.6MB 17.3MB boot
5 33.6MB 83.9MB 50.3MB rom
6 83.9MB 134MB 50.3MB bootdata
7 134MB 522MB 388MB factory
8 522MB 1164MB 642MB ext4 system
9 1164MB 1611MB 447MB ext4 cache
10 1611MB 14.5GB 12.9GB media
11 14.5GB 15.6GB 1139MB ext4 userdata
So now I am trying
http://forum.xda-developers.com/showthread.php?t=1545766
See post#2. However I am no linux guru and I am stuck at the step that says
Copy device and vendor folder from Nook-Tablet to ~/android/system/
I followed the instructions on
http://forum.xda-developers.com/showthread.php?t=1570022
To setup ubuntu on the vm box. I can connect to the nook via adb on windows 7 but it refuses to work from Ubuntu, it just wont show (I added the adb_usb.ini and launched adb via sudo). I tried to pull from windows but it doesn't look right and think it would be best if I pull it from Ubuntu.
P.S.
Oh also, since I reason that my partitions are pretty much gone I tried to pull it from the cm7 sd image. unless someone knows how for me to mount the mmcblk’s and extract the needed files from there.
Fixed Somewhat ...
Well I found the missing files to get this method to work.
http://forum.xda-developers.com/showthread.php?t=1605664
Then I applied the Ubuntu recovery.
http://forum.xda-developers.com/showthread.php?t=1470910
However the nook just boots then it says: Please restart your device and try again, and powers down...
For some reason I cant get the acclaim_update.zip to work. Can anyone please help or send me in a new direction?
Please restart...
Riddler9884 said:
Well I found the missing files to get this method to work.
http://forum.xda-developers.com/showthread.php?t=1605664
Then I applied the Ubuntu recovery.
http://forum.xda-developers.com/showthread.php?t=1470910
However the nook just boots then it says: Please restart your device and try again, and powers down...
For some reason I cant get the acclaim_update.zip to work. Can anyone please help or send me in a new direction?
Click to expand...
Click to collapse
That is the notice that the Nook is trying to load Recovery but there is not a recovery.img
I note in the op that you tried Megd00t's repart. It is absolutely solid in my opinion. I even intentionally bricked my nt8 to film the video that shows how to make it work.
If you try it again, you should be able to use an SDCard version of Clockworkmod to flash any *.zip to the device. See my series of videos here: http://www.youtube.com/playlist?list=PL676779C4F7BE8FEB&feature=mh_lolz
PM me if you have questions. I have not yet finished the accompanying articles describing the processes.
I am stumped
I performed this again
http://forum.xda-developers.com/show....php?t=1605664
with the added lines from the DD recovery
for blocks 7, 8 and 9
No go - It boot loops the stock recovery
Then I applied the Ubuntu recovery.
http://forum.xda-developers.com/show....php?t=1470910
Same result - It boot loops the stock recovery
by what I read both of these are supposed usually do the trick but it still doesn't do it. I followed the advice that cwm should be able to apply any zip
but the stock bn update zip doesnt work
acclaim update fails
heck the ribbon rom fails
it gave a status one. What am I overlooking?
Would there be a way to make a disk image of the entire nook with all the sub partitions defined?
It would have blocks 1-9 with their stock info and the rest of the partitions zeroed out. So they loaded with info when you boot to recovery?
Stock cannot be flashed without mod
Riddler9884 said:
I followed the advice that cwm should be able to apply any zip
but the stock bn update zip doesnt work
acclaim update fails
heck the ribbon rom fails
it gave a status one. What am I overlooking?
Click to expand...
Click to collapse
My error. (Sorry) The B&N update file (the BN acclaim update is the same) cannot be flashed without modification. Meghd00t posted a "howto" I believe but I don't have a link right now.
However, you SHOULD be able to flash the Ribbon Root and other custom ROMs using CWM. I don't know where you should go now...
---------- Post added at 06:02 PM ---------- Previous post was at 06:00 PM ----------
Riddler9884 said:
Would there be a way to make a disk image of the entire nook with all the sub partitions defined?
It would have blocks 1-9 with their stock info and the rest of the partitions zeroed out. So they loaded with info when you boot to recovery?
Click to expand...
Click to collapse
I believe that is Albert Wertz's process. You might want to check it out. His file is a CWM "Backup" image that you should be able to "Restore" (with CWM). Might be worth a try...
Well I am not sure but I believe what fixed it was:
repartitioning the Nook using: http://forum.xda-developers.com/showthread.php?t=1605664
Then Using: SD_R3NT16or8gbV4_7
http://forum.xda-developers.com/showthread.php?t=1528625
I flashed flash-restore-stock.zip from:
http://forum.xda-developers.com/showthread.php?t=1545766
followed up by using the restore feature in SD_R3NT16or8gbV4_7
to complete the missing info
I almost got my nook back. Now I just need to work out how to get my sn back.
Riddler9884 said:
Well I am not sure but I believe what fixed it was:
repartitioning the Nook using: http://forum.xda-developers.com/showthread.php?t=1605664
Then Using: SD_R3NT16or8gbV4_7
http://forum.xda-developers.com/showthread.php?t=1528625
I flashed flash-restore-stock.zip from:
http://forum.xda-developers.com/showthread.php?t=1545766
followed up by using the restore feature in SD_R3NT16or8gbV4_7
to complete the missing info
I almost got my nook back. Now I just need to work out how to get my sn back.
Click to expand...
Click to collapse
Hey sounds like you are almost there.
The sn is under the SDCard door. I saw a post somewhere on XDA about a process for manually putting it back in the device memory. Search here and Google.
Sent from my NookTablet using XDA
I tried
http://forum.xda-developers.com/showthread.php?t=1610069
I guess it works depending on how much you have cleared from the nooks internal memory in the process of restoring the nook.
I kind of put this together based on what I saw here
http://nookdevs.com/NookColor_Fix_Boot_Loops
Look at the section that says
echo -n -e "\x08\x00\x00\x00" > /mnt/devconf/BootCnt
i did a little research
Their method didn't work form me, but it gave me insight. I worked out the chmod by what was said here
http://forum.xda-developers.com/showthread.php?t=1586281
~ # echo -n -e "20201700########" > /rom/devconf/SerialNumber
~ # echo -n -e "20201700########" > /rom/devconf/DeviceID
~ #echo -n -e "5867########" > /rom/devconf/MACAddress
~ # cd /rom/devconf
/rom/devconf # chmod 440 MACAddress
/rom/devconf # chmod 440 DeviceID
/rom/devconf # chmod 440 SerialNumber
Update - It Couldn't Register but I did find this out by chance:
When I originally got my tablet and rooted the google play store saw this under My Devices:
(From a pc, Log in, all the way at the bottom, My Devices tab)
Maker-> Barnes&Noble
Model-> BNTV250
I went back in recently after restoring and got this:
Maker-> Bn
Model-> Nook Tablet
Maybe one of the restores was messing with changing the name for Compatibility? I used so many things I cant tell where the above came from.
repart.img
Riddler9884 said:
Maybe one of the restores was messing with changing the name for Compatibility? I used so many things I cant tell where the above came from.
Click to expand...
Click to collapse
What is the ID that is displayed when you connect with ADB? In all of my (3 months) trial of being "bricked", I did not stop getting my serial number as the id when I connected with adb. But, nothing else on the internal memory worked. The only way I could use the Nook was with an external SD-based ROM (I used CM7a).
What I suggest is (repeat this after each different attempt to fix your issues): Try Meghd00t's repart.img again. Let it clear everything and restore back to stock. You might be pleasantly surprised! I sure was.
Here is a link to my step-by-step guide. http://raywaldo.com/2012/06/how-to-un-brick-a-nook-tablet-8gb-or-16gb/
Nope no more, re-imaging the nook for this test. My wife will kill me if I keep ignoring her to tinker with the nook, Especially since it was for her to read her novels.
After loading albertwertz image and having access to android market and the amazon store has her happy.
Registering the B&N would just be a plus.... I need a tablet I will just get a Samsung 7 inch tablet.
Restore serial number on Nook
Riddler9884 said:
Nope no more, re-imaging the nook for this test. My wife will kill me if I keep ignoring her to tinker with the nook, Especially since it was for her to read her novels.
After loading albertwertz image and having access to android market and the amazon store has her happy.
Registering the B&N would just be a plus.... I need a tablet I will just get a Samsung 7 inch tablet.
Click to expand...
Click to collapse
I found this on one of Succulent's posts:
- To get your serial number back, you need to perform factory restore (8 failed boot method)
- The one that prompt,
Clearing data…
A reset is being performed.
This may take a few minutes
Click to expand...
Click to collapse
Here is a link to the thread: http://forum.xda-developers.com/showthread.php?t=1545766
TLDR: Phone was bricked revived it now stuck with generic IMEI
Ok so basically my GS3 got bricked dont know exactly why but in recovery it said e: failed to mount /efs (Invalid argument) i was able however to revive it with this thread post #4 ( http://forum.xda-developers.com/showthread.php?t=2204960 ) but now my IMEI is "generic" 004999010640000 and now i cant connect to the network. Im on a mac and the only tutorials ive seen are for windows. my question is is there anyway to change it from the phone itself or on a mac? Sorry if this has been asked before but if anyone can point me in the right direction that would be great.
PS i know changing your IMEI is HIGHLY illegal but i just want to change it back to the original one on the back of the phone.
You're #2 today and #1073453 in total, asking for help with 00499... issue! Not nice...
Use the flipping search bar! :/
Im on a mac...
oh im sorry but if you read the whole thing IM ON A MAC so anyway to fix this would be great...
djembey said:
You're #2 today and #1073453 in total, asking for help with 00499... issue! Not nice...
Use the flipping search bar! :/
Click to expand...
Click to collapse
Restore your backed up EFS folder through whatever method you used .
No backup then a Samsung service centre .
jje
Ok so i have a backup but its the coorrupted one... anyway to open up the .img and copy the files manually on a mac? sidenote when i restore the corrupted one im in a boot loop
JJEgan said:
Restore your backed up EFS folder through whatever method you used .
No backup then a Samsung service centre .
jje
Click to expand...
Click to collapse
Sorry not a clue don't even know how to switch a Mac on .
jje
If your EFS dump is a full partition dump (it being .img suggests that), you can simply write it back in recovery with:
Code:
umount /efs
dd if=/sdcard/yourefs.iso of=/dev/block/mmcblk0p3
reboot
If that fails or throws errors, repeat the steps in the tutorial you linked to re-create an empty EFS partition.
By the way /efs is an EXT4 partition so neither Windows nor Mac (or any other BSD-derivate) are natively capable of reading it, only Linux computers (read: Ubuntu, ...) or specialized tools that simulate filesystem drivers are able to do so.
so i tried that and wasnt able to boot past the i9300 screen. any other suggestions?
d4fseeker said:
If your EFS dump is a full partition dump (it being .img suggests that), you can simply write it back in recovery with:
Code:
umount /efs
dd if=/sdcard/yourefs.iso of=/dev/block/mmcblk0p3
reboot
If that fails or throws errors, repeat the steps in the tutorial you linked to re-create an empty EFS partition.
By the way /efs is an EXT4 partition so neither Windows nor Mac (or any other BSD-derivate) are natively capable of reading it, only Linux computers (read: Ubuntu, ...) or specialized tools that simulate filesystem drivers are able to do so.
Click to expand...
Click to collapse
ugh
Ok so i havent updated this in awhile but here it goes...
First i installed ubuntu on my mac and converted my corrupted EFS partition to .iso and opened it in linux. Anyway no files in there.
Second the samsung service center here in alaska is only for TVs...
Third ill call samsung on monday but dunno what i can do besides save up for another phone or a octopus box or what you call it.
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
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