Code:
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
Error: Unable to satisfy all constraints on the partition.
Anyone seen this issue? I have tried unmounting to make sure nothing was mounted both in CWM and by force:
Code:
umount /data
umount /cache
Thanks for trying.
I thought I explained it for you in the PM. mmcblk0 is not a normal disk device at all (it's a NAND device, quite different), it does not have a "standard" partition table (in fact it does not have a partition table at all, the partitioning is done internally in the kernel), so parted doesn't know how to work with that.
ravilov said:
I thought I explained it for you in the PM. mmcblk0 is not a normal disk device at all (it's a NAND device, quite different), it does not have a "standard" partition table (in fact it does not have a partition table at all, the partitioning is done internally in the kernel), so parted doesn't know how to work with that.
Click to expand...
Click to collapse
My apologies, I logged in today and didnt see any response.
The concern I have is that others have ran the above command and did not have the response I got. Oh well.
My data partition is locked somehow in a read only state. Nothing I do causes it to wipe, I thought parted could help but it appears not.
ravilov said:
I thought I explained it for you in the PM. mmcblk0 is not a normal disk device at all (it's a NAND device, quite different), it does not have a "standard" partition table (in fact it does not have a partition table at all, the partitioning is done internally in the kernel), so parted doesn't know how to work with that.
Click to expand...
Click to collapse
Ah, thanks for that. Is there any way to access/read the partition table handled in the kernel? Not necessarily with parted, but through terminal some how?
The kernel dev team (namely Krystian) has been able to work something out regarding this but nothing has been published yet.
According to this thread
http://forum.xda-developers.com/showthread.php?t=1959445
Parted using the print or p command should bring back this
Code:
/ # 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) p
Disk /dev/block/mmcblk0: 31268536320B
Sector size (logical/physical): 512B/512B
Partition Table: gpt
-------------------------------------------------------------------------------
Number Start End Size FS-Type Name Flags
-------------------------------------------------------------------------------
1 4194304B 67108863B 62914560B modem
2 67108864B 67239935B 131072B sbl1
3 67239936B 67502079B 262144B sbl2
4 67502080B 68026367B 524288B sbl3
5 68026368B 70123519B 2097152B aboot
6 70123520B 70647807B 524288B rpm
7 70647808B 81133567B 10485760B boot
8 81133568B 81657855B 524288B tz
9 81657856B 82182143B 524288B pad
10 82182144B 92667903B 10485760B param
11 92667904B 106954751B 14286848B ext4 efs
12 106954752B 110100479B 3145728B modemst1
13 110100480B 113246207B 3145728B modemst2
14 113246208B 1686110207B 1572864000B ext4 system
15 1686110208B 30337400831B 28651290624B ext4 userdata
16 30337400832B 30345789439B 8388608B ext4 persist
17 30345789440B 31226593279B 880803840B ext4 cache
18 31226593280B 31237079039B 10485760B recovery
19 31237079040B 31247564799B 10485760B fota
20 31247564800B 31253856255B 6291456B backup
21 31253856256B 31257001983B 3145728B fsg
22 31257001984B 31257010175B 8192B ssd
23 31257010176B 31262253055B 5242880B grow
I am extremely interested in this as I need to find the boot partition for my device... But I am having the same issue as the OP, with the same response from parted
atmu5fear said:
According to this thread
http://forum.xda-developers.com/showthread.php?t=1959445
Parted using the print or p command should bring back this
Code:
/ # 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) p
Disk /dev/block/mmcblk0: 31268536320B
Sector size (logical/physical): 512B/512B
Partition Table: gpt
-------------------------------------------------------------------------------
Number Start End Size FS-Type Name Flags
-------------------------------------------------------------------------------
1 4194304B 67108863B 62914560B modem
2 67108864B 67239935B 131072B sbl1
3 67239936B 67502079B 262144B sbl2
4 67502080B 68026367B 524288B sbl3
5 68026368B 70123519B 2097152B aboot
6 70123520B 70647807B 524288B rpm
7 70647808B 81133567B 10485760B boot
8 81133568B 81657855B 524288B tz
9 81657856B 82182143B 524288B pad
10 82182144B 92667903B 10485760B param
11 92667904B 106954751B 14286848B ext4 efs
12 106954752B 110100479B 3145728B modemst1
13 110100480B 113246207B 3145728B modemst2
14 113246208B 1686110207B 1572864000B ext4 system
15 1686110208B 30337400831B 28651290624B ext4 userdata
16 30337400832B 30345789439B 8388608B ext4 persist
17 30345789440B 31226593279B 880803840B ext4 cache
18 31226593280B 31237079039B 10485760B recovery
19 31237079040B 31247564799B 10485760B fota
20 31247564800B 31253856255B 6291456B backup
21 31253856256B 31257001983B 3145728B fsg
22 31257001984B 31257010175B 8192B ssd
23 31257010176B 31262253055B 5242880B grow
I am extremely interested in this as I need to find the boot partition for my device... But I am having the same issue as the OP, with the same response from parted
Click to expand...
Click to collapse
You need to find the boot partition, but you can't look at the chart you provided and find the word boot?
palmbeach05 said:
You need to find the boot partition, but you can't look at the chart you provided and find the word boot?
Click to expand...
Click to collapse
Obviously... except that's not from my phone. That's an example as quoted from the thread I linked to, as to what SHOULD come back from the parted print command. My phone returns the exact same error message as the OP of this thread... So thanks for the condescending reply, but if you actually read my comment, well, it's pretty clear. Sorry to sound like an ass, but I've been looking into this for days, thanks, don't need critical comments from someone who doesn't actually read the post...
Sent from my SAMSUNG-SGH-T989 using xda app-developers app
First of all, if all you need is to find the boot partition, then you clearly do NOT have the same issue as the OP. Read his second post to find out why.
Second, why are you messing with parted anyway? What's wrong with this?
ravilov said:
First of all, if all you need is to find the boot partition, then you clearly do NOT have the same issue as the OP. Read his second post to find out why.
Second, why are you messing with parted anyway? What's wrong with this?
Click to expand...
Click to collapse
i agree with @ravilov. And why are you messing with parted to get the boot.img, when you can open a ROM package or a nandroid backup and retrieve said boot.img?
Sent from my MB860 using xda app-developers app
ravilov said:
First of all, if all you need is to find the boot partition, then you clearly do NOT have the same issue as the OP. Read his second post to find out why.
Second, why are you messing with parted anyway? What's wrong with this?
Click to expand...
Click to collapse
First of all, remind me of the title of this thread? If the OP is typing a command in parted and it's returning an error message, and I am also typing that same command and getting the same error message, that clearly we ARE having same issue. The second post is nothing more than his reason for using parted in the first place. So yes, his reason may be different than mine, but the issue is the same. Secondly, I ended up on this thread by searching the error message parted turned in Google. I do not have a Motorola Atrix, therefore your partition table that you spent so much time researching for the thread the link you provided is useless to me. That's what's wrong with it. After trying every command I could find to give me a partition table, with no success identifying the boot partition, I decided to try with parted. Which, by the way, returns a very clear table on my t989, just not my s730m which gives me the error message. So I guess your theory about mmcblk0 not having a partition table pretty much goes out the window. Thirdly, I don't recall saying I needed a boot.img, I said I needed to know the boot partition. Big difference, especially when one is writing a updater-script in which one needs to know the mmcblk0p_ to write the boot.img to. This info may be easy to find for a lot of phones including your Motorola, but not so much for phones that don't have a single flashable ROM out them, custom OR stock. There is one on the works by a member here, and myself for the s730m, but nothing currently available and thus needing to know the boot partition to write to, well, seems a bit important... I was able to find the info, which was more of a stumble across after using adb to pull the recovery.log from the device and viewing it on my laptop. Haven't pulled a recovery log for some time, totally forgot that all of the partition info is available on the first lines the log. I can honestly say that you two are the first people I've encountered on xda who have been rather ignorant, condescending, and critical instead of offering any sort of help or suggestions. Do I have your permission to continue my research and/or seek help and guidance when I get stuck or is that breaking some sort of unwritten rule? Not all of us are born knowing everything like the two of you obviously were, or at least think you were. Is that enough reason as to why I was "messing around with parted" and needed to know my boot partition (not needing to extract a boot.img), or would you like me to elaborate with every command I used, every Google search I performed, and every thread I read regards to the matter. Thanks again for pretending to know everything and criticize others who are simply out to learn and further their android knowledge though, that's great you guys...
Sent from my SAMSUNG-SGH-T989 using xda app-developers app
atmu5fear said:
I do not have a Motorola Atrix, therefore your partition table that you spent so much time researching for the thread the link you provided is useless to me.
Click to expand...
Click to collapse
This fact alone means your question doesn't even belong here. The forum is organized into specific subforums and boards for a very good reason. No reason to disrespect that just because you happened to have stumbled across this thread through some search on Google. If your question does not pertain specifically to Atrix 4G, then you need to ask it elsewhere.
ravilov said:
This fact alone means your question doesn't even belong here. The forum is organized into subforums and boards for a reason. If your question does not pertain to this specific device, then you need to ask it elsewhere.
Click to expand...
Click to collapse
Like I said I searched "parted unable to satisfy constraints" on Google, it brought me here. And since this error message has nothing to do with the Atrix itself, but with parted and any device that runs parted (potentially all android phones), I feel it's perfectly acceptable post here. The OP's question pertains to parted, not the specific device. Since there was already a topic with the question that I was looking for an answer to, why would I ask it elsewhere, further cluttering the forums with unnecessary threads?
Also the s730m does not have a device specific sub forum, I don't have much of and option but to search for the same issues with other devices.
Why do you feel the need to troll threads and criticize people with legitimate questions? These forums are here for people to ask questions and help each other out, not to troll and criticize. If you don't have any help to offer someone, why criticize the question?
Sent from my SAMSUNG-SGH-T989 using XDA Premium 4 mobile app
---------- Post added at 06:20 AM ---------- Previous post was at 06:04 AM ----------
For anyone else looking for their partition table and getting this error message.
In adb type:
adb pull /tmp/recovery.log
This will pull the log file from your device (Motorola, Samsung, Sony, etc, anything with a custom recovery) and will show you exactly what mmcblk0p_ for each partition is; boot, system, data, cache, etc.
Sent from my SAMSUNG-SGH-T989 using XDA Premium 4 mobile app
Like I said, however you managed to get here is irrelevant. This is a board for Atrix 4G ONLY, questions about other devices have no business here even if the topic doesn't seem device-specific. I'm sorry if your device doesn't have its own board but that doesn't give you any right to try and hijack someone else's thread with inquiries about a completely different situation (trust me, when it comes to things such as partition tables, just the fact you have an entirely different device makes a world of difference).
To reiterate - your question does not belong here. There is the general Android section, you could've tried there instead.
ravilov said:
Like I said, however you managed to get here is irrelevant. This is a board for Atrix 4G ONLY, questions about other devices have no business here even if the topic doesn't seem device-specific. I'm sorry if your device doesn't have its own board but that doesn't give you any right to try and hijack someone else's thread with inquiries about a completely different situation (trust me, when it comes to things such as partition tables, just the fact you have an entirely different device makes a world of difference).
To reiterate - your question does not belong here. There is the general Android section, you could've tried there instead.
Click to expand...
Click to collapse
Ya... anyway... To the OP or to anyone else who might end up here via Google, use the aforementioned adb command. If using Windows, type:
Code:
adb pull /tmp/recovery.log C:\Users\YourName\Desktop
I should mention you need to be in recovery when using this command. So reboot your device into recovery, then use the pull command to pull the recovery log.
This will pull the recovery log to your desktop, open it with notepad++ (you can use notepad but it's not at all organized) and the first dozen or so lines will tell you exactly what you need to know about your partition table. Hope it helps!
And no not really "like I said" in this case, being you didn't already say "how you got here is irrelevant". But regardless, sorry that you think you own the thread and the forum for the atrix and feel you have some sort of authority here over other people. (Trust me when it comes to things such as policing this forum and having authority, just the fact that you think you know everything doesn't actually mean that you do). I wasn't hijacking the thread, I was explaining that the parted command SHOULD bring back a partition table. In fact even the OP says it works for others, just not him.
To reiterate, I didn't ask a question, I made a statement, and then through my own research/tinkering, provided an answer to the OP's partition table identifying issue, and to anyone else who may view this thread with the same or similar issue, which is more than you can say about what you've contributed to this thread. So have a good one, enjoy trolling and criticizing others who are only trying to learn, and policing threads you don't have authority over, the rest of us will continue to offer whatever assistance we can, regardless of whether or not a few trolls feel it's in the appropriate sub forum or not. Good night
Sent from my SAMSUNG-SGH-T989 using XDA Premium 4 mobile app
atmu5fear said:
Ya... anyway... To the OP or to anyone else who might end up here via Google, use the aforementioned adb command. If using Windows, type:
Code:
adb pull /tmp/recovery.log C:\Users\YourName\Desktop
I should mention you need to be in recovery when using this command. So reboot your device into recovery, then use the pull command to pull the recovery log.
This will pull the recovery log to your desktop, open it with notepad++ (you can use notepad but it's not at all organized) and the first dozen or so lines will tell you exactly what you need to know about your partition table. Hope it helps!
And no not really "like I said" in this case, being you didn't already say "how you got here is irrelevant". But regardless, sorry that you think you own the thread and the forum for the atrix and feel you have some sort of authority here over other people. (Trust me when it comes to things such as policing this forum and having authority, just the fact that you think you know everything doesn't actually mean that you do). I wasn't hijacking the thread, I was explaining that the parted command SHOULD bring back a partition table. In fact even the OP says it works for others, just not him.
To reiterate, I didn't ask a question, I made a statement, and then through my own research/tinkering, provided an answer to the OP's partition table identifying issue, and to anyone else who may view this thread with the same or similar issue, which is more than you can say about what you've contributed to this thread. So have a good one, enjoy trolling and criticizing others who are only trying to learn, and policing threads you don't have authority over, the rest of us will continue to offer whatever assistance we can, regardless of whether or not a few trolls feel it's in the appropriate sub forum or not. Good night
Sent from my SAMSUNG-SGH-T989 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I have to say, @ravilov does have a point here, this is the section for the Atrix 4G, however, I am happy that you searched for the error, before opening a new thread
Now, if I understand you correctly, all you need is a partition table, right?
So run the following commands:
Code:
adb shell
ls -a | grep fstab
exit
adb pull /<result_of_the_ls_command> ~/<result_of_the_ls_command>
If you happen to have more issues about this, feel free to PM me, or open a thread in your device's section, but let's stop the discussions now
Thanks
Related
Alright, so the root filesystem image is in /mnt/system/androidmerged.squashfs.secure
So do a temp root, copy to /mnt/storage, and then a adb pull gets it over.
The squashfs itself is offset by 256 bytes, so:
losetup -o 256 /dev/loop0 ./androidmerged.squashfs.secure
At this point, the FS can be mounted or unsquashfs can be used to extract it.
So, what's the first 256 bytes? The secure implies some type of signature, but what kind, and what else is in all those bytes?
I'm not feeling brave enough to try just grabbing the first 256 bytes and appending a modified squashfs image to it on my device just yet, but if others try please report back. (On both if it works, and if not what it takes to recover the unit.)
how big is it? can you upload it somewhere? (or would this be illegal?)
damm.. i need my 101!
chulri said:
how big is it? can you upload it somewhere? (or would this be illegal?)
damm.. i need my 101!
Click to expand...
Click to collapse
75 MB - uploading now
Edit: And up: http://hotfile.com/dl/88050103/f99f306/androidmerged.squashfs.secure.html
thx!
how would you replace the root fs image on the device?
chulri said:
how would you replace the root fs image on the device?
Click to expand...
Click to collapse
Connect via ADB, do a temproot, put the file in /mnt/storage, then copy it into /mnt/system overwriting the existing file. /mnt/storage is an ext3 filesystem mounted read/write, however I simply do not know if it will be possible to recover the unit if there is some kind of signature verification and we fail due to a modified image.
Again, someone braver then I should make this attempt and let us know how it goes.
The source did not give all that many hints, but I need to dig through in some more detail.
zelch said:
Connect via ADB, do a temproot, put the file in /mnt/storage, then copy it into /mnt/system overwriting the existing file. /mnt/storage is an ext3 filesystem mounted read/write, however I simply do not know if it will be possible to recover the unit if there is some kind of signature verification and we fail due to a modified image.
Again, someone braver then I should make this attempt and let us know how it goes.
The source did not give all that many hints, but I need to dig through in some more detail.
Click to expand...
Click to collapse
If the unit will still boot to recovery could a full wipe and reinstall of the base AOS over USB get it back up and running?
krohnjw said:
If the unit will still boot to recovery could a full wipe and reinstall of the base AOS over USB get it back up and running?
Click to expand...
Click to collapse
Recovery shouldn't be part of the FS so at worst, you'd have to do a format/firmware install.
You can do a full system wipe/format from recovery. it's not in any damageable storage by us without flashing a new recovery image.
Interesting about the front 256 bytes. It must be a signature. Not sure what good rebuilding the squashfs will do as it'll still be read only but it's a start. We could at least update the system properly and install the appropriate apps. Maybe in make some of the system dirs symlinks to writable locations possibly.
Permroot, giving us a filesystem mounted RW and not no-suid.
Ideally, I'd like to have decent support for the internal storage being ext3 without nosuid, but first we need to be able to replace the root filesystem image.
Other notes..
Looking at the hexdumps, the 256 byte chunk does not contain the start of the md5, sha1, sha224, sha256, sha384, or sha512 checksums.
The most troubling option which comes to mind is that it is the right size for a RSA 2048 bit block, hopefully not.
Anyone have ideas on how to find the initramfs image that the bootloader is feeding the kernel?
For that matter, has anyone tried taking apart the OS update images?
zelch said:
For that matter, has anyone tried taking apart the OS update images?
Click to expand...
Click to collapse
I think the aos file or the responsible installer/updater should give us a lot of information about how this stuff can be updated.
chulri said:
I think the aos file or the responsible installer/updater should give us a lot of information about how this stuff can be updated.
Click to expand...
Click to collapse
Agreed.
It looks like usr/bin/abcbox in the root filesystem has something to do with the update process.
zelch said:
Agreed.
It looks like usr/bin/abcbox in the root filesystem has something to do with the update process.
Click to expand...
Click to collapse
And it definitely is!
On a rooted device:
Code:
/usr/bin # PATH=$PATH:/tmp
/usr/bin # ln -s /usr/bin/abcbox /tmp/cramfschecker
/usr/bin # cramfschecker
USAGE: cramfschecker FILENAME
/usr/bin # cramfschecker /mnt/system/androidmerged.squashfs.secure
cramfschecker : check against 2.0.54
cramfschecker verification OK
Anyone with some ARM disassembly skills feeling up to taking abcbox apart to see how it's doing the signature check?
And so I've been digging into this, and it turns out that this is really quite similar to how the Gen 7 Archos 5 IT is locked.
The signature there is a RSA + MD5 signature, which is really the worst case as that means a 2048 bit RSA key, so we're kinda screwed there.
http://strazzere.com/blog/?p=320 has a good description of the situation on the 5IT. Getting a flash_unlock binary should be fairly trivial, so perhaps we can tamper with the key store to add additional keys.
ah zelch, this is good stuff.
i'm gonna diff the archos gpl kernel, looking for changes at mtd stuff. maybe we can build a kernel module which enables r/w access to stage1
edit: or do we already have r/w access?
This stuff is all pretty interesting to read, but if I'm reading this correctly (and it is entirely possible I'm not) it looks kind of like this device is going to be a total pain in the ass to root, and it may take a considerable amount of time for us to get there.
Can someone who is more knowledgeable on this sort of thing verify that? Thanks for all your hard work guys. It's appreciated.
its definitly not going to be that easy as other android devices were but would it be so interesting if it wouldn't be so hard to root?
While that's true, it will make it a bigger triumph when it is finally rooted, the tinkerer in me is dying to mess with roms on this device and see what it can really do once it's cracked open. Keep up the great work guys, I'm following with baited breath.
Write to stage1 appears to exist, and indeed looking at /proc/mounts /mnt/rawfs is mounted rw. Looking at the kernel source, write support should Just Work.
So, looking through /mnt/rawfs avboot is clearly the boot loader which verifies stuff, but we lack source for it.
I have absolutely no knowledge of ARM asm, and screwing this up will absolutely brick your device, quite possibly beyond repair. (And I wouldn't bet on ArchOS being willing to replace it either, I sure wouldn't.)
So, anyone with the right background willing to step in here?
I'll keep digging, perhaps we can still find the answers.
Note: avboot has some strings which reference a development kernel, this bears some additional hunting.
I still haven't got my A101, but its finally on its way to my home.
can you please upload these files and give me kind of a tree of the folder structure?
Hi,
I just realised that I'm going to post this, hopefully to get some help getting the frame buffer issue working. I'm not giving up on it, but it just doesnt seem fair to sit on this any longer since it works, besides the GUI glitches.
As i said before, the S7 kernel does not support framebuffering, which makes the GUI in the recovery a bitt messy. When you move up / down in the menu, it switches between selecting an item on top and an item on the bottom (you'll see 4 menus in total, but the ones on each horizontal line is a mirror).
This means that it starts by using the lower one, and it uses the top one next, then it goes back to the lower one. Boot it up and you'll probably see what I mean. This shouldnt cause any problems with the recoverys operation anyhow.
If you want to enter adb in linux you will have to get a copy of usb_modeswitch and run the following line in order to get adb to recognize the device:
sudo usb_modeswitch -W -v 12d1 -p 1031 -V 12d1 -P 1035 -M "5553424370ab71890600000080010a1106000000000000000 0000000000000" -s 20
This will switch the huawei s7 usb device into adb mode.
Also i take no responsibilites of bricks or other problems caused by using this recovery. Its truly for learning usage only.
My credit list would be to long if I where to include all forums that I've visited to get more information about this device, but if you feel like you deserve credit, let me know and i'll add you, otherwise, thanks to all people posting information about android devices, i could never have done it without you.
Ofcourse i have to thank the creators of clockwork mod, and also the people who wrote the repack-image.pl and unpack-image.pl scripts
Thanks to my wife who put up with me sitting and messing around with this for almost a week, giving her not the attention that she deserved, and thanks to all users of the S7 tablet out there.
h***://rapidshare.com/files/438781673/recovery.img.zip (not allowed to post links yet)
The shortcut key for entering recovery is menu + send, if anyone wonders.
Hope you'll enjoy it as much as I did.
Works great. Ill research a bit to see if i can help
Sent from my Ideos S7 using XDA App
Sorry for qwestion, but... How can i put it into device? Via fastboot on cmd, or somehow other?
Sent from my Ideos S7 using XDA App
I hope we can get a 2.2 rom
sorry, but it working not fully...
its have errors to open nandroid-mobile.sh
and its cant format SDcart to partitions ext2 and ext3...
or maybe i doing something wrong
GvoZdik said:
sorry, but it working not fully...
its have errors to open nandroid-mobile.sh
and its cant format SDcart to partitions ext2 and ext3...
or maybe i doing something wrong
Click to expand...
Click to collapse
You're right, I noticed now that I the wrong ramdisk in the image that was released. I have several of them for which I use to debug the framebuffer stuff, and I forgot to use my own build.
I'll upload the correct one sometime this weekend.
Sorry.
Sent from my HTC Desire using Android Tablet Forum App
thanx, thats a great work anyway...
Sent from my S7 using XDA App
thanks perivarlura for your support!
perivarlura said:
You're right, I noticed now that I the wrong ramdisk in the image that was released. I have several of them for which I use to debug the framebuffer stuff, and I forgot to use my own build.
I'll upload the correct one sometime this weekend.
Sorry.
Sent from my HTC Desire using Android Tablet Forum App
Click to expand...
Click to collapse
The ui glitches even more now that the misc partition handled and the nandroid script is running. I guess i need to get this fixed before i release it, or it will just be a mess.
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
Ok here is the deal short and sweet . I have a nook tablet 8gb best i can tell it has NO partitions on the internal flash section.
I have used ADB to confirm this i used parted this way to check ... type in p or print and nothing shows.
step 1 adb
C:\ADB>adb devices
List of devices attached
0000000000000000 recovery <-----first error
but adb will connect thru adb shell
so i type in parted /dev/block/mmcblk0
~ # 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) <-----seems to be working now the print command
(parted) print
print
print
(parted)
nothing.
I followed another post on here that gave commands to re-partition but when i finish there never there.
I can also boot to CWM from a sd card ...... and have a CM7 system sdcard that does work fine
But would love to fix the nook tablet so its just back to factory state for my daughter. if i could get some help on makeing partitions stay put after i write them i think i could move on with this project.
Alternative If someone would point me in the right direction to permanently fix partitions so CM7 would install to the internal flash i could live with that.
Thanks for reading this far.
http://raywaldo.com/2012/06/how-to-un-brick-a-nook-tablet-8gb-or-16gb/
Sent from my CM 10 nook. Thanks devs.
Yes , i have tried this countless times different sd cards even bought a new 4 and 8 (4 speed) sdcard no luck even when it does boot from it the
red X show up and it reboots. So the best i can figure it has to have the factory partitions intact before this install will work. I even tried a clockwork mode recovery from another NT 8gb no luck o this either.
Im on week 2 of fighting with this thing i have learned alot but willing to learn more.
Thanks for the input
edit
i guess i should have posted that when a recovery sdcard does work it will run for about 3 seconds ten show a red ! in a book
Sounds like a bad emmc or other hardware in the nook. Try to warranty it, the worse they can do is say no. Don't lie to them but you may want to be selective about the customizing you have done.
Sent from my CM 10 nook. Thanks devs.
Well thats kinda the bad part it was used when i got it. And " I " done the damage. So i would not try and return it. But yes the emmc is blank dir under adb the only things i can find are in sbin folder and a few odd place like that.
I know this much if i ever fix this im writing a BIG tutorial on here cause i caint be the only one lol
Daddy.Mouse said:
Well thats kinda the bad part it was used when i got it. And " I " done the damage. So i would not try and return it. But yes the emmc is blank dir under adb the only things i can find are in sbin folder and a few odd place like that.
I know this much if i ever fix this im writing a BIG tutorial on here cause i caint be the only one lol
Click to expand...
Click to collapse
I don't think you necessarily broke it. Unfortunately components fail, sounds like possibly some bad blocks. If you can run it from SD pop CM 10 from iamafanof.WordPress.com on it and call it a day.
Sent from my CM 10 nook. Thanks devs.
Lol i would but im subborn i wanna fix it so maybe i can help others later I trying a AdamOutlerUbuntuTotalReFlash but it dont seem to boot at all Oh well back to the drawing board
Daddy.Mouse said:
Lol i would but im subborn i wanna fix it so maybe i can help others later I trying a AdamOutlerUbuntuTotalReFlash but it dont seem to boot at all Oh well back to the drawing board
Click to expand...
Click to collapse
Stubborn or not bad blocks means not fixing it unless you replace components. If it is indeed hardware related no matter what you try it isn't going to work.
Sent from my CM 10 nook. Thanks devs.
Daddy.Mouse said:
...
Alternative If someone would point me in the right direction to permanently fix partitions so CM7 would install to the internal flash i could live with that.
Thanks for reading this far.
Click to expand...
Click to collapse
The info in these two threads might be helpful:
http://forum.xda-developers.com/showthread.php?t=1515788
http://forum.xda-developers.com/showpost.php?p=23921174&postcount=15
Thanks for all the help At least ive got something new to try thanks again.
SlowCobra96 its not completly hopeless till its laying on the ground with my foot in it screen busted and in a thousand parts lol I will keep trying .
I think if i could re write the partitions and make the stay there would be some hope.
digixmax thanks for the links imma give it a try in a few i hadent seen them links before
Daddy.Mouse said:
Thanks for all the help At least ive got something new to try thanks again.
SlowCobra96 its not completly hopeless till its laying on the ground with my foot in it screen busted and in a thousand parts lol I will keep trying .
I think if i could re write the partitions and make the stay there would be some hope.
digixmax thanks for the links imma give it a try in a few i hadent seen them links before
Click to expand...
Click to collapse
The reason they aren't "staying" is probably the result of an impending failure. The corruption in the blocks gets pushed to the side during a format, at least for a short period, then the corrupted blocks start getting read/accessed causing data corruption and/or further block failure. Now without having it in front of me I can't guarantee this is the problem but I strongly believe it is based on the description.
Sent from my CM 10 nook. Thanks devs.
Slight update i now have the partitions back .... i think. Now when i turn it on with no sdcard in it finally boot loops the N logo.
It will show N then as soon as i see "read forever" it reboots .... Getting closer
Daddy.Mouse said:
Slight update i now have the partitions back .... i think. Now when i turn it on with no sdcard in it finally boot loops the N logo.
It will show N then as soon as i see "read forever" it reboots .... Getting closer
Click to expand...
Click to collapse
Update NOOK is now running with no problems !!!! I will write up a help file for how i came from no partitions to fulling working again .
Just want to say thanks to all the folks that pointed me here and there for different things to read and also all the help you guys and gals gave
Ohh Happy days !!!!
No ive not forgot about writing a tut just trying to reproduce my findings again before i write.
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