Related
Hi, I would like to ask a question about x1 phone, where is the boot loader file? Is in the Sector 0 of the built-in NAND flash? Coz I am worry that the gadget will not go into the boot loader mode if I read/write the entire NAND flash especially the sector 0 data.
Many thanks for people who answer out!
Anybody there who can help out about this issue?
Q:\PDA\cooking\itsutilsbin-20080602>pmemdump.exe 0xa8000000 524288 SPLdumped.nb
CopyProcessMemoryToFile(00000042, a8000000, 00080000, SPLdumped.nb)
i heard, that this is saving your bootloader.
Many thanks for ur reply okokur.
Lets assume that way is working for the saving data of bootloader, but can i restore the saved data of bootloader if the Sector 0 data is destroyed (it even can't go into first bootloader mode, there is no Active sync for it)?
Any idea for that?
robin.w2009 said:
Many thanks for ur reply okokur.
Lets assume that way is working for the saving data of bootloader, but can i restore the saved data of bootloader if the Sector 0 data is destroyed (it even can't go into first bootloader mode, there is no Active sync for it)?
Any idea for that?
Click to expand...
Click to collapse
If it wont go into bootloader then I think you're stuck, and it's a replacement device. This is another reason why we tend to use "hardSPL"..
however it might be best to ask in the general "questions and answers" thread or dev&hacking.
I did think mtty might help, but it needs to access bootloader from what I understand..
i know some of you have this problem and worries that something wrong happend during the process of unlocking your phone. well that's the same thing i was thinking about 3 days now and trying to figure it out how to fix this. i just a noobie here and new for all this android thingy but i guess im just lucky fixing it.
by reading again the thread of how to unlock. it mention there that your phone might have a sim lock. this might be the problem so i search some thread related to this and guess what a found the answer!
now here's how to fix it.
1. after unlocking your phone using msm7227_setool2. check if you have network signal so you won't do the step 2 of this thread.
2. now if there's no signal, open again your msm7227 folder (which is the unlock bootloader tool) and you will see there's another tool which is ms7227_semc.
3. put to debugging mode then connect your usb to your PC.
4. run the ms7227_semc and wait till it done.
5. reboot your phone and you already have network signal again.
i hope that this help you specially for those who are new to this kind of stuff..
it really work....thx a lot..my phone have the signal back again...
U mean that it supposed to have a weak signall,or no signal at all?
Sent from my Xperia X8 using XDA Premium App
you may try it too. but most of the time after unlocking have no signal at all because of the sim-Lock.
@mhieyato : if unlocking using msm7227_setool2 i put to debugging mode or NOT, if not to put debugging mode that tools can't running or stuck in " getting ROOT rights"...
Please explain step by step master...
mhieyato said:
i know some of you have this problem and worries that something wrong happend during the process of unlocking your phone. well that's the same thing i was thinking about 3 days now and trying to figure it out how to fix this. i just a noobie here and new for all this android thingy but i guess im just lucky fixing it.
by reading again the thread of how to unlock. it mention there that your phone might have a sim lock. this might be the problem so i search some thread related to this and guess what a found the answer!
now here's how to fix it.
1. after unlocking your phone using msm7227_setool2. check if you have network signal so you won't do the step 2 of this thread.
2. now if there's no signal, open again your msm7227 folder (which is the unlock bootloader tool) and you will see there's another tool which is ms7227_semc.
3. put to debugging mode then connect your usb to your PC.
4. run the ms7227_semc and wait till it done.
5. reboot your phone and you already have network signal again.
i hope that this help you specially for those who are new to this kind of stuff..
Click to expand...
Click to collapse
Hey, what if my phone still have no signal ? Could you show me the whole tutorial? I use the ms7227_semc but when its nearly done , the ms7227_semc suddenly shut down. Could you please help me? I want my x8 back :'(
why it doesn't work for me? when running msm phone reboots, and this:
process requires standard 2.x android firmware.
Press any key to continue . . .
Getting ROOT rights.
3487 KB/s (585731 bytes in 0.164s)
Failed to set prot mask (Inappropriate ioctl for device)
Waiting ...
Removing NAND MPU restrictions via SEMC backdoor. Permanent. Require ROOT rights
.
430 KB/s (3087 bytes in 0.007s)
success
Waiting ...
Getting ROOT rights.
Failed to set prot mask (Inappropriate ioctl for device)
Waiting ...
Writing patched semcboot. Two step process
First, we need get access to semcboot area
874 KB/s (8064 bytes in 0.009s)
insmod: can't insert '/data/local/tmp/mapper_2.6.29.ko': invalid module format
Second, we need to write semcboot
3643 KB/s (596916 bytes in 0.160s)
can't find userdate partition
Press any key to continue . . .
jjumphard said:
why it doesn't work for me? when running msm phone reboots, and this:
[...]
Failed to set prot mask (Inappropriate ioctl for device)
[...]
insmod: can't insert '/data/local/tmp/mapper_2.6.29.ko': invalid module format
[...]
Click to expand...
Click to collapse
As a wild guess I'd say you're not on Stock Kernel/ROM but some custom kernel/ROM.
Restore back to Stock Kernel/ROM.
EDIT: Oh wait, you're from the Unlocking Guide ... *should ID nicknames first*
Well, this can now be interesting to see if you can manage to unlock the boot loader again with nAa's Kernel flashed - as there's also no way to go back to Stock Kernel (through Flashtool, PCC, SEUS) while the boot loader is locked. :s
it works!
thanks a lot!
mhieyato said:
i know some of you have this problem and worries that something wrong happend during the process of unlocking your phone. well that's the same thing i was thinking about 3 days now and trying to figure it out how to fix this. i just a noobie here and new for all this android thingy but i guess im just lucky fixing it.
by reading again the thread of how to unlock. it mention there that your phone might have a sim lock. this might be the problem so i search some thread related to this and guess what a found the answer!
now here's how to fix it.
1. after unlocking your phone using msm7227_setool2. check if you have network signal so you won't do the step 2 of this thread.
2. now if there's no signal, open again your msm7227 folder (which is the unlock bootloader tool) and you will see there's another tool which is ms7227_semc.
3. put to debugging mode then connect your usb to your PC.
4. run the ms7227_semc and wait till it done.
5. reboot your phone and you already have network signal again.
i hope that this help you specially for those who are new to this kind of stuff..
Click to expand...
Click to collapse
hi, i have a question about this fix, i unlocked a Xperia X8 (E15a) with octopus suite and then ''no service'' this post work for me? thanks for your help.
yey it worked for me.. after 1 year of giving up on my xperia, i found this post then i thoght why not give it a shot.. then boom it worked.. thanks for the post ^_^
Wow!! Thanks you have saved my phone from "no service" this thingy
yeah it really works!
I was about to put my phone in my garbage, thanks
Hiya guys,
I'm new to the Sony side of things, I'm usually a HTC user but my mother has just got herself an X8 E15i and I am having a few problems with it and was hoping people could help?
firstly, I rooted, UNLOCKED BOOTLOADER, flashed a custom kernel (X8_v08a-cm7_Alfs_djnilse) & GingerZaraki-v05.
Then I had no signal at all, so I thought "ok, flash a newer baseband to attempt fix"
but alas, no joy.
I have then accidently relocked the bootloader :faceplant:
This has now caused her to have no signal... oops... arn't us teenagers great
and then I have read HERE that it is fixable, and I have followed the steps listed but I still can not get signal.
every time I run either script msm7227_semc.cmd OR msm7227_setool2.cmd they both get root, reboot, but still can not get signal.
EDIT: copy of cmd results...
"process requires standard 2.x android firmware.
Press any key to continue . . .
Getting ROOT rights.
adb server is out of date. killing...
* daemon started successfully *
415 KB/s (585731 bytes in 1.378s)
error: protocol fault (no status)
Waiting ...
Removing NAND MPU restrictions via SEMC backdoor. Permanent. Require ROOT rights.
52 KB/s (3087 bytes in 0.057s)
success
Waiting ...
Getting ROOT rights.
Waiting ...
Writing patched semcboot. Two step process
First, we need get access to semcboot area
18 KB/s (8064 bytes in 0.422s)
Second, we need to write semcboot
919 KB/s (596916 bytes in 0.634s)
successfully wrote 0003ff00
Press any key to continue . . ."
its obviously gettting root, but what does 'protocol fault: no status' mean?
and I know that the bootloader is locked because I have used "x8toolbox.final" which I found on here - I would give the maker of it the credit but can not remember who it was.
So at present my mother has a x8 e15i, running 2.1.1 but can't have signal at all??
EDIT1: please help or I think I am in trouble here...
EDIT2: Doesn't matter now guys, after soft-bricking and Hard-bricking (attempted bootloader unlock fail) the X8, I have resurrected it!
and I have successfully rooted (4th time tonight) and now I have flashed GingerDX, which is running great with the GingerDX O/C Kernel
GlennBrownie said:
EDIT2: Doesn't matter now guys, after soft-bricking and Hard-bricking (attempted bootloader unlock fail) the X8, I have resurrected it!
and I have successfully rooted (4th time tonight) and now I have flashed GingerDX, which is running great with the GingerDX O/C Kernel
Click to expand...
Click to collapse
And What you did to resurrect it? I am in the same situation and i can not Find any solution. I used omnius to unlock my simlock...
Sent from my iPhone using Tapatalk
well I have the same problem. after omnius unlock i unlocked the bootloader and no signal. HHHEEEEELLLLLPPPPPPPPPPPPP.
nice guide bro, it really works =D
hello everyone,
i have xperia x8 E15i
I unlocked my phone and after that the signal of the network is weak or inactive.
i think the problem is in a step while unlocking the phone.
i have an idea and i wish you can help fix it.
i didn't personnaly unlock the phone and i don't know the code unlock
tell me is this the same problem as you??
and thanks for sharing your technical experiences
Well for Omnius sim unlock problem you have the answer here: http://forum.xda-developers.com/showthread.php?t=1911915
Did not unlock bootloader but have 3 phones with same issues
In response to what you said, I have 3 Xperia X8's with the same issue but all were unrooted using superoneclick and then loaded gingerdx on them. They worked fine for about 2 months then on all 3 phones (friends) one by one they ended up accidentally putting their sim unlock pin code into the network unlock code thing that pops up on the gingerdx rom and all ended up with no signal at all.. I dont have seTool 2 pro only lite and i cant find any way to get the phone fixed. i live in southern Africa so limited resources etc.. PLEASE HELP
mhieyato said:
i know some of you have this problem and worries that something wrong happend during the process of unlocking your phone. well that's the same thing i was thinking about 3 days now and trying to figure it out how to fix this. i just a noobie here and new for all this android thingy but i guess im just lucky fixing it.
by reading again the thread of how to unlock. it mention there that your phone might have a sim lock. this might be the problem so i search some thread related to this and guess what a found the answer!
now here's how to fix it.
1. after unlocking your phone using msm7227_setool2. check if you have network signal so you won't do the step 2 of this thread.
2. now if there's no signal, open again your msm7227 folder (which is the unlock bootloader tool) and you will see there's another tool which is ms7227_semc.
3. put to debugging mode then connect your usb to your PC.
4. run the ms7227_semc and wait till it done.
5. reboot your phone and you already have network signal again.
i hope that this help you specially for those who are new to this kind of stuff..
Click to expand...
Click to collapse
hi somebody can help me
my galaxy ace had a baseband unknown but the problem is i dont have backup of my bml5 or stl5..
i need those file somebody can send me
If you change your bml5 = device bricked for life
Device bml5 is UNIQUE !
Galaxy_Ace_Love said:
If you change your bml5 = device bricked for life
Device bml5 is UNIQUE !
Click to expand...
Click to collapse
i dont care only i need for experiment sorry for my bad english
I've read old treaths saying that if you "Touch", even read the stl5 partition (like dd=...), will brick the device..., so, if it is possible to backup the partition containing the imei?, is there a proved method?, ive allready a bckup of bl5, for unlock my device, and i dont brick it, but is it in this partition the imei backup?
thx
Well I decided to sell this Atrix HD I just recently acquired and of course because I have no luck at all not even 5 mins after posting the ad on craigslist I ended up potentially bricking it, sadly. I've spent the better part of the past 2 hours scouring threads and posts hoping for a solution but so far I've had no luck so I'll take this last step and ask if anyone might have any advice or solutions. Here's the situation:
- Atrix HD, originally with JB 4.1.1 on it (pre-final AT&T update, mind you)
- rooted with motochopper then bootloader unlocked with motopocalypse, no issues over the past 10 days or so that I've owned this AHD at all)
- was running CM11 nightly without issues (installed with CWM 6.0.5.1, had flashed several ROMs over the past 10 days including CM12, the Mexican retail ROM, and then back to pure AT&T several times, actually
- about 2 hours before making this post I listed it on craigslist and then used Myth Tools to go back to stock (stock being MB886_att-user-4.1.1-9.8.0Q-97_MB886_FFW-20-27)
- no issues with the flashing process, booted up as expected, worked fine for a few mins then I connected to Wi-Fi and grabbed the final JB update released by AT&T, when it finished I clicked "Install now" to do the reboot and install it
- rebooted into the install and seemed to finish ok, didn't glitch or error out in any respect
- somewhere in the middle of the final reboot after the upgrade it crapped out and then went into the bootloader loop to AP Fastboot (S) mode
- got the following error (which is known to a few other members in the past based on postings I located):
Code:
(typical info at the top of the screen)
Device is LOCKED. Status Code: 0
Battery OK
Connect USB
Data Cable
downgraded security version
update gpt_main version failed
failed to hab check for gpt_backup:0x35
failed to load GPT
CID Read Failure
Invalid CID status 0x69
No SP partition found
Fastboot Reason: Invalid GPT
usb connected
As stated, this AHD was bootloader unlocked without any issues but for whatever is now showing as LOCKED. The thing that concerns me is that if I use fastboot devices it doesn't show the proper info as it used to (the typical TA00etcetcetc model number) - it's showing an 8 digit alphanumeric number I've never seen before so that's a big red flag right there.
I've attempted every process I can locate so far and had zero success at all - only one single fastboot command gives me an OKAY message and that's fastboot oem fb_mode_clear. Every other fastboot command offers up a FAILED (remote failure) error, all of them and I've tried pretty much all of them.
I cannot flash anything to the AHD it seems so I'm guessing that means it's 100% "bricked" in the sense that it's powering up, can be seen from the PC/laptop using fastboot devices, but that's it just not actually there at all for whatever reason.
I've attempted to use 2 different laptops, 1 desktop, multiple various USB ports, cables, you name it I'm pretty confident I've attempted to use it in some respect and still nada, zip, zilch, nothing has come from my efforts. If it's totally bricked then so be it, I'll live, but I keep holding out hope that something I missed will help but it's starting to look like this is beating a dead horse now.
I've attempted using RSD Lite to push the Mexican retail ROM to it (with the edited xml file), the AT&T retail ROM, etc - I can't locate any FXZ files at all so that might still be an option but I simply cannot find any of them if they exist.
So apparently for whatever reason the final JB update pooched this device (even in spite of it not doing it in the past week when I rolled back to stock at least 3 prior times in testing). I'm suspecting - but can't say for certain - that potentially the CWM 6.0.5.1 which I just installed like 2 days ago could be the culprit here; previously using 6.0.4.4 I had no issues whatsoever and that is the only variable that's changed in my flashing process that I can recall.
Anyway, that pretty much covers the situation - if anyone has any advice that might bring this AHD back to life I'm definitely interested in hearing it. I don't have JTAG hardware, don't have a factory cable (if one is required), don't have anyone in the area that does that I'm aware of, etc. Basically if I can't get it resolved on my own then it's a dead device I'll toss in a drawer till that miracle comes along...
Thanks for reading, regardless.
br0adband said:
Well I decided to sell this Atrix HD I just recently acquired and of course because I have no luck at all not even 5 mins after posting the ad on craigslist I ended up potentially bricking it, sadly. I've spent the better part of the past 2 hours scouring threads and posts hoping for a solution but so far I've had no luck so I'll take this last step and ask if anyone might have any advice or solutions. Here's the situation:
- Atrix HD, originally with JB 4.1.1 on it (pre-final AT&T update, mind you)
- rooted with motochopper then bootloader unlocked with motopocalypse, no issues over the past 10 days or so that I've owned this AHD at all)
- was running CM11 nightly without issues (installed with CWM 6.0.5.1, had flashed several ROMs over the past 10 days including CM12, the Mexican retail ROM, and then back to pure AT&T several times, actually
- about 2 hours before making this post I listed it on craigslist and then used Myth Tools to go back to stock (stock being MB886_att-user-4.1.1-9.8.0Q-97_MB886_FFW-20-27)
- no issues with the flashing process, booted up as expected, worked fine for a few mins then I connected to Wi-Fi and grabbed the final JB update released by AT&T, when it finished I clicked "Install now" to do the reboot and install it
- rebooted into the install and seemed to finish ok, didn't glitch or error out in any respect
- somewhere in the middle of the final reboot after the upgrade it crapped out and then went into the bootloader loop to AP Fastboot (S) mode
- got the following error (which is known to a few other members in the past based on postings I located):
Code:
(typical info at the top of the screen)
Device is LOCKED. Status Code: 0
Battery OK
Connect USB
Data Cable
downgraded security version
update gpt_main version failed
failed to hab check for gpt_backup:0x35
failed to load GPT
CID Read Failure
Invalid CID status 0x69
No SP partition found
Fastboot Reason: Invalid GPT
usb connected
As stated, this AHD was bootloader unlocked without any issues but for whatever is now showing as LOCKED. The thing that concerns me is that if I use fastboot devices it doesn't show the proper info as it used to (the typical TA00etcetcetc model number) - it's showing an 8 digit alphanumeric number I've never seen before so that's a big red flag right there.
I've attempted every process I can locate so far and had zero success at all - only one single fastboot command gives me an OKAY message and that's fastboot oem fb_mode_clear. Every other fastboot command offers up a FAILED (remote failure) error, all of them and I've tried pretty much all of them.
I cannot flash anything to the AHD it seems so I'm guessing that means it's 100% "bricked" in the sense that it's powering up, can be seen from the PC/laptop using fastboot devices, but that's it just not actually there at all for whatever reason.
I've attempted to use 2 different laptops, 1 desktop, multiple various USB ports, cables, you name it I'm pretty confident I've attempted to use it in some respect and still nada, zip, zilch, nothing has come from my efforts. If it's totally bricked then so be it, I'll live, but I keep holding out hope that something I missed will help but it's starting to look like this is beating a dead horse now.
I've attempted using RSD Lite to push the Mexican retail ROM to it (with the edited xml file), the AT&T retail ROM, etc - I can't locate any FXZ files at all so that might still be an option but I simply cannot find any of them if they exist.
So apparently for whatever reason the final JB update pooched this device (even in spite of it not doing it in the past week when I rolled back to stock at least 3 prior times in testing). I'm suspecting - but can't say for certain - that potentially the CWM 6.0.5.1 which I just installed like 2 days ago could be the culprit here; previously using 6.0.4.4 I had no issues whatsoever and that is the only variable that's changed in my flashing process that I can recall.
Anyway, that pretty much covers the situation - if anyone has any advice that might bring this AHD back to life I'm definitely interested in hearing it. I don't have JTAG hardware, don't have a factory cable (if one is required), don't have anyone in the area that does that I'm aware of, etc. Basically if I can't get it resolved on my own then it's a dead device I'll toss in a drawer till that miracle comes along...
Thanks for reading, regardless.
Click to expand...
Click to collapse
Did you edit the script when flashing the stock JB with Mythtools or RSD lite?
Sent from my ATRIX-RAZR HD using XDA Free mobile app
Yep, it even states that in my post:
I've attempted using RSD Lite to push the Mexican retail ROM to it (with the edited xml file), the AT&T retail ROM, etc - I can't locate any FXZ files at all so that might still be an option but I simply cannot find any of them if they exist.
Click to expand...
Click to collapse
Nothing will flash to the device which is the biggest issue of all; if I could flash the gpt_main0.bin file I'd be getting somewhere (since as I understand it that sets the partition layout for the partition img's that will follow in the flashing process).
As stated, the only thing that works in terms of a fastboot command is fb_mode_clear which gets an OKAY response (although fb_mode_set does too, actually). But no other fastboot commands are functional - I tried fastboot -w and get:
Code:
D:\motopocalypse\motopocalypse>fastboot -w
erasing 'userdata'...
Invalid partition name userdata
FAILED (remote failure)
finished. total time: 0.140s
so then I try:
Code:
D:\motopocalypse\motopocalypse>fastboot erase userdata
erasing 'userdata'...
Invalid partition name userdata
FAILED (remote failure)
finished. total time: 0.141s
and so on and so forth. No attempts to erase data nor write it in any manner are successful. RSD Lite basically is useless as well (pic attached below). Since I can't write any data to the device at all then as I've said, it's dead in the water unless a miracle comes along. Was looking at eBay in the hopes of finding a busted/broken AHD (damaged glass, etc) and swapping the mobo from that one back into my housing but they're a bit expensive for busted ones at the moment, guess I'll just keep hoping for that miracle.
I've never used a JTAG or factory cable on any devices I've ever owned but I have to wonder if such a contraption might get this back to a working state. Suppose I'll need to do some research into things - I tried to contact Motorola about it but of course since the AHD is so old now and I'm not the original owner, even though I registered the device in my name they won't honor the warranty without a proof of purchase (meaning the retail one years ago when it was new).
Out of over 100 smartphones and other devices I've owned over the decades this is the first time one's actually up and died on me and go figure: it died when doing an OTA update on a clean stock ROM installation.
How ironic...
Have you tried this http://forum.xda-developers.com/showthread.php?t=2259661
Sent from my LG-D850 using XDA Free mobile app
bmatney said:
Have you tried this http://forum.xda-developers.com/showthread.php?t=2259661
Sent from my LG-D850 using XDA Free mobile app
Click to expand...
Click to collapse
Yep, it's all the same basic process whether it's done scripted or manually, same result: as stated, nothing will flash to the AHD and kicks back the same error each time (partition errors). I have no idea what that damned OTA did but it totally wrecked the whole thing...
Even tried doing this under Linux - the issue isn't with fastboot or the builds, it's with the AHD itself because it's not writing anything I'm trying to flash to the device and I'm confident it's because the partition structure is pooched for whatever reason.
I'm still wondering about using a factory cable (will have to buy one off eBay I suppose) will make any difference at all, I just have no experience using them and if the phone isn't flashing/writing data to the device because the partitions are pooched, I can't imagine using a different albeit specific cable will make that much of a difference.
Bleh... I hate it when crap goes wrong, I really do.
Hi, this is my first post on XDA forums.
While unbricking my hard bricked Redmi 9 device, I am getting this error when running any mtkclient command.
Code:
struct.error: argument out of range
Searching for this error led me to this github issue where the owner mentioned that `That means that your gpt table likely is broken and needs to be reflashed.`. So the question is, how to reflash GPT partition?
Plz halp me