I sincerely apologize if an answer to this issue has been posted as I could not find it.
Running stock ICS, rooted & bmm is installed.
Phone had been acting a bit odd, and just recently numerous apps force close at odd and beyond annoying times, like while in car dock with Navigator running, and everything from rule suggestions to google play to acore force close. Kind of distracting to have it appear over the map, and this is if it isn't Map/navigator that crashes. I also noticed that multiple settings seemed to revert back to what they use to be after a reboot. Example: enable audio and then power off phone. Upon turning it back on, it is once again in silent mode. In Titanium backup, I noticed that the system rom now showed 500 used, 0 free. I used a root browser and removed some audio files from the system rom. After doing so, I managed to free about 4 mb according to titanium. Restarted phone and it shows 0 free again, as well as the files I thought I had deleted, were back.
Decided it was worth the hassle to restore the phone. Did factory reset, and was a bit surprised when the phone showed the bmm bootloader. But I thought, maybe it could survive a reset. I was more surprised when it loaded ics and nothing had changed, however.
Same result with FXZ. RSDlite went through all 19 steps, and proceeded to reboot phone. I have to admit I raised an eyebrow when I was then faced once again with bmm and shortly thereafter an unchanged ics.
I thought about removing BMM but am unwilling to do so since an fxz has already failed without warning.
Any ideas would be appreciated, because at this time I do not have the answers.
lunatic987 said:
I sincerely apologize if an answer to this issue has been posted as I could not find it.
Running stock ICS, rooted & bmm is installed.
Phone had been acting a bit odd, and just recently numerous apps force close at odd and beyond annoying times, like while in car dock with Navigator running, and everything from rule suggestions to google play to acore force close. Kind of distracting to have it appear over the map, and this is if it isn't Map/navigator that crashes. I also noticed that multiple settings seemed to revert back to what they use to be after a reboot. Example: enable audio and then power off phone. Upon turning it back on, it is once again in silent mode. In Titanium backup, I noticed that the system rom now showed 500 used, 0 free. I used a root browser and removed some audio files from the system rom. After doing so, I managed to free about 4 mb according to titanium. Restarted phone and it shows 0 free again, as well as the files I thought I had deleted, were back.
Decided it was worth the hassle to restore the phone. Did factory reset, and was a bit surprised when the phone showed the bmm bootloader. But I thought, maybe it could survive a reset. I was more surprised when it loaded ics and nothing had changed, however.
Same result with FXZ. RSDlite went through all 19 steps, and proceeded to reboot phone. I have to admit I raised an eyebrow when I was then faced once again with bmm and shortly thereafter an unchanged ics.
I thought about removing BMM but am unwilling to do so since an fxz has already failed without warning.
Any ideas would be appreciated, because at this time I do not have the answers.
Click to expand...
Click to collapse
Is there ANY chance that your phone could be stuck in what we like to call "safe mode"? if it is it may have the write bit on the storage set to read-only, or possibly you have a bad USB cable, or something else is wrong with the storage in the phone.
Try another computer, if you can try one with XP, and not windows 7 or 8, just to see if it is any different, we have seen some very odd things from RSDlite, in the past. This may be more for a troubleshooting thing than anything else at this point.
Also try another USB port on your computer, and possibly another cable as well. Also try a factory reset, and make sure you uninstall BMM, I know you said you do not want to, but there could be a bad install of it, locking up your system partition, or something else you installed.
Now all of this being said the bad BMM/app install is the least of your issues at this point, and the fact that you can not get the FXZ to write to the partitions, is a concern.
Have you tried any of the restore scripts? You can go and grab one of them, and just add the files for the correct fxz to it, and run it from a windows command line, that has worked for others in the past, and there are a few iterations of them in the dev section, and I have another one that I can send you a link to download if you like, you will just have to grab the correct fxz and put it in the correct place with the script, and that might work.
Here is my all in one script:
http://www.androidfilehost.com/?fid=9390288116658471426
Run it, and choose to do the fxz, and you will put ALL the fxz files in the fxz directory in the root of this script, and run it from the command line this just might work for you.
Both the factory reset and the attempt at fxz showed the droid on it's back with the red exclamation before reverting back to normal behavior. Of course I expected to see the exclamation.
I'm reluctant to remove bmm because the last time I did that, I was left with no alternative but fxz afterwards. So without that functioning, even a barely working phone is better than no phone at all, that is, IF it would even remove bmm, and at this point, I'm doubting it.
It is the same rsd, windows install, etc. as previous times., USB Port and cable was probably different, though, although that shouldn't really matter?
As far as I know, it shouldn't be stuck in a 'safe mode' There is nothing to identify to me as such, and I have not knowingly done so. A write bit being set to read only is exactly how it is acting, though. Except that android doesn't even seem to realize it.
I do now see that a year ago someone had a similar with no resolution indicated, as well as back in Jan.
I'll try in the morning with some of those suggestions to try and troubleshoot/get it back to working. Barring that, I'll see if I can put a rom on system 3 or something. Primarily out of curiosity. If even that fails, I might consider putting the poor phone out of it's misery.... violently. Shame, too, since it is (was) able to boot kexec
lunatic987 said:
Both the factory reset and the attempt at fxz showed the droid on it's back with the red exclamation before reverting back to normal behavior. Of course I expected to see the exclamation.
I'm reluctant to remove bmm because the last time I did that, I was left with no alternative but fxz afterwards. So without that functioning, even a barely working phone is better than no phone at all, that is, IF it would even remove bmm, and at this point, I'm doubting it.
It is the same rsd, windows install, etc. as previous times., USB Port and cable was probably different, though, although that shouldn't really matter?
As far as I know, it shouldn't be stuck in a 'safe mode' There is nothing to identify to me as such, and I have not knowingly done so. A write bit being set to read only is exactly how it is acting, though. Except that android doesn't even seem to realize it.
I do now see that a year ago someone had a similar with no resolution indicated, as well as back in Jan.
I'll try in the morning with some of those suggestions to try and troubleshoot/get it back to working. Barring that, I'll see if I can put a rom on system 3 or something. Primarily out of curiosity. If even that fails, I might consider putting the poor phone out of it's misery.... violently. Shame, too, since it is (was) able to boot kexec
Click to expand...
Click to collapse
Try my script, instead of RSD... It will write directly to the partitions using commands that RSD won't... People that have had the same issue as you have had success with my script (I posted it above in my last reply).
You just put the phone in fastboot load ONLY the files from the fxz (not the directory it comes in), into the fxz directory of my script and run it from the command line. If that does not flash you have a serious issue.
Jim
jimbridgman said:
Try my script, instead of RSD... It will write directly to the partitions using commands that RSD won't... People that have had the same issue as you have had success with my script (I posted it above in my last reply).
You just put the phone in fastboot load ONLY the files from the fxz (not the directory it comes in), into the fxz directory of my script and run it from the command line. If that does not flash you have a serious issue.
Jim
Click to expand...
Click to collapse
That link was to the edison jb. But I did find the all in one script for atrix 2 that you had uploaded yesterday.
I had to manually pull out the restore portion as choice doesn't work. Below is the output.
Erasing Boot
sending 'mbm' (256 KB)... OKAY [ 0.023s]
writing 'mbm'... OKAY [ 0.469s]
Rebooting into bootloader
rebooting into bootloader... OKAY [ 0.283s]
Flashing mbmloader.bin
sending 'mbmloader' (41 KB)... FAILED (command write failed (No such file or
directory))
Flashing mbm.bin
sending 'mbm' (256 KB)... FAILED (command write failed (No such file or
directory))
Rebooting into bootloader
< waiting for device >
rebooting into bootloader... OKAY [ 0.006s]
Flashing cdt.bin
sending 'cdt.bin' (16 KB)... FAILED (command write failed (No such file or
directory))
Erasing userdata
erasing 'userdata'... FAILED (command write failed (No such file or
directory))
Erasing cache
< waiting for device >
erasing 'cache'... OKAY [ 0.012s]
Flashing lbl
sending 'lbl' (16 KB)... OKAY [ 0.007s]
writing 'lbl'... OKAY [ 0.498s]
Flashing logo.bin
sending 'logo.bin' (854 KB)... OKAY [ 0.336s]
writing 'logo.bin'... OKAY [ 0.254s]
Flashing ebr
sending 'ebr' (16 KB)... OKAY [ 0.284s]
writing 'ebr'... OKAY [ 0.497s]
Flashing mbr
sending 'mbr' (16 KB)... OKAY [ 0.283s]
writing 'mbr'... OKAY [ 0.467s]
flashing device_tree.bin
sending 'devtree' (512 KB)... OKAY [ 0.315s]
writing 'devtree'... OKAY [ 0.512s]
Flashing System
sending 'system' (262144 KB)... OKAY [ 16.417s]
writing 'system'... OKAY [ 6.099s]
sending 'system' (229120 KB)... OKAY [ 14.341s]
writing 'system'... OKAY [ 5.329s]
Flashing Radio
sending 'radio' (13780 KB)... OKAY [ 0.868s]
writing 'radio'... OKAY [ 0.551s]
Flashing cdrom
sending 'cdrom' (12032 KB)... OKAY [ 1.024s]
writing 'cdrom'... OKAY [ 0.864s]
Flashing preinstall
sending 'preinstall' (262144 KB)... OKAY [ 16.480s]
writing 'preinstall'... OKAY [ 6.050s]
sending 'preinstall' (20480 KB)... OKAY [ 1.290s]
writing 'preinstall'... OKAY [ 0.495s]
Flashing Boot image
sending 'boot' (8192 KB)... OKAY [ 0.521s]
writing 'boot'... OKAY [ 0.707s]
After this, like the other attempts, I am thrown into Android system recovery. Rebooting just sends back into my main system (same with waiting a while). I attempted to apply update from external storage, loading the InlineFlashing_Edison_67.21.125_CFC_P3_APBP.xml.zip, and received message: E: signature verification failed
I verified the MD5 and it was indeed correct, so I assumed there shouldn't be any corruption of the zip. This is, of course, the exact same file I used to put ics on it.
I tried 2 other sdcards in a 'why not' idea.
Looking under cache on there showed only the recovery and lost and found folders. I then chose wipe cache out of curiosity, looked again, lost and found, and recovery were both still under cache. I went back to the main options, then accidentally selected update from cache again, saw the 2 folders on there, and suddenly the droid appeared standing with the geometric sphere rotating. I am confused and I do not trust it, but know of nothing else to do, except sit here, watch it spinning, appearing to do nothing else.
edit: eventually pulled battery, booted back into main system...
lunatic987 said:
That link was to the edison jb. But I did find the all in one script for atrix 2 that you had uploaded yesterday.
I had to manually pull out the restore portion as choice doesn't work. Below is the output.
Erasing Boot
sending 'mbm' (256 KB)... OKAY [ 0.023s]
writing 'mbm'... OKAY [ 0.469s]
Rebooting into bootloader
rebooting into bootloader... OKAY [ 0.283s]
Flashing mbmloader.bin
sending 'mbmloader' (41 KB)... FAILED (command write failed (No such file or
directory))
Flashing mbm.bin
sending 'mbm' (256 KB)... FAILED (command write failed (No such file or
directory))
Rebooting into bootloader
< waiting for device >
rebooting into bootloader... OKAY [ 0.006s]
Flashing cdt.bin
sending 'cdt.bin' (16 KB)... FAILED (command write failed (No such file or
directory))
Erasing userdata
erasing 'userdata'... FAILED (command write failed (No such file or
directory))
Erasing cache
< waiting for device >
erasing 'cache'... OKAY [ 0.012s]
Flashing lbl
sending 'lbl' (16 KB)... OKAY [ 0.007s]
writing 'lbl'... OKAY [ 0.498s]
Flashing logo.bin
sending 'logo.bin' (854 KB)... OKAY [ 0.336s]
writing 'logo.bin'... OKAY [ 0.254s]
Flashing ebr
sending 'ebr' (16 KB)... OKAY [ 0.284s]
writing 'ebr'... OKAY [ 0.497s]
Flashing mbr
sending 'mbr' (16 KB)... OKAY [ 0.283s]
writing 'mbr'... OKAY [ 0.467s]
flashing device_tree.bin
sending 'devtree' (512 KB)... OKAY [ 0.315s]
writing 'devtree'... OKAY [ 0.512s]
Flashing System
sending 'system' (262144 KB)... OKAY [ 16.417s]
writing 'system'... OKAY [ 6.099s]
sending 'system' (229120 KB)... OKAY [ 14.341s]
writing 'system'... OKAY [ 5.329s]
Flashing Radio
sending 'radio' (13780 KB)... OKAY [ 0.868s]
writing 'radio'... OKAY [ 0.551s]
Flashing cdrom
sending 'cdrom' (12032 KB)... OKAY [ 1.024s]
writing 'cdrom'... OKAY [ 0.864s]
Flashing preinstall
sending 'preinstall' (262144 KB)... OKAY [ 16.480s]
writing 'preinstall'... OKAY [ 6.050s]
sending 'preinstall' (20480 KB)... OKAY [ 1.290s]
writing 'preinstall'... OKAY [ 0.495s]
Flashing Boot image
sending 'boot' (8192 KB)... OKAY [ 0.521s]
writing 'boot'... OKAY [ 0.707s]
After this, like the other attempts, I am thrown into Android system recovery. Rebooting just sends back into my main system (same with waiting a while). I attempted to apply update from external storage, loading the InlineFlashing_Edison_67.21.125_CFC_P3_APBP.xml.zip, and received message: E: signature verification failed
I verified the MD5 and it was indeed correct, so I assumed there shouldn't be any corruption of the zip. This is, of course, the exact same file I used to put ics on it.
I tried 2 other sdcards in a 'why not' idea.
Looking under cache on there showed only the recovery and lost and found folders. I then chose wipe cache out of curiosity, looked again, lost and found, and recovery were both still under cache. I went back to the main options, then accidentally selected update from cache again, saw the 2 folders on there, and suddenly the droid appeared standing with the geometric sphere rotating. I am confused and I do not trust it, but know of nothing else to do, except sit here, watch it spinning, appearing to do nothing else.
edit: eventually pulled battery, booted back into main system...
Click to expand...
Click to collapse
Ok, so first off the xml.zip will not load from BMM or system recovery, it was not meant to be used like that... and it is only meant to be used with RSD, and why the check fails when doing it from those other methods.
Yes I know the script was never really ever finished for windows, it was originally meant as a way for linux users to flash the fxz, and then a few windows users made the request I never really got time to fully finish it.
Are you sure you have the right FXZ for your phone? The errors that you have from my script are that it can not flash the bootloader pre-install files and the cdt.bin, that tells me you may have the wrong fxz, possibly. Otherwise you are missing those files, or worse that that since you flashed the JB image, you may have to modify my script, so that it does not flash the mbm files, and then edit the xml file to use the cdt.bin from the JB image... This has been a know deal around here since ICS came out.
At this point you can try poking around with my script, since I do not have windows, I can't really test it, but you can see if there is a way you can get it to see those files it is complaining about, you may have to hardcode their location into the script to make it do it... but be careful, since you loaded JB on there.
Jim
jimbridgman said:
Ok, so first off the xml.zip will not load from BMM or system recovery, it was not meant to be used like that... and it is only meant to be used with RSD, and why the check fails when doing it from those other methods.
Yes I know the script was never really ever finished for windows, it was originally meant as a way for linux users to flash the fxz, and then a few windows users made the request I never really got time to fully finish it.
Are you sure you have the right FXZ for your phone? The errors that you have from my script are that it can not flash the bootloader pre-install files and the cdt.bin, that tells me you may have the wrong fxz, possibly. Otherwise you are missing those files, or worse that that since you flashed the JB image, you may have to modify my script, so that it does not flash the mbm files, and then edit the xml file to use the cdt.bin from the JB image... This has been a know deal around here since ICS came out.
At this point you can try poking around with my script, since I do not have windows, I can't really test it, but you can see if there is a way you can get it to see those files it is complaining about, you may have to hardcode their location into the script to make it do it... but be careful, since you loaded JB on there.
Jim
Click to expand...
Click to collapse
I did not download a jb anything. Only the scripts. The fxz I'm attempting to use is the att stock ics that I have used via rsd previously (phone is indeed ATT MB865. Rather than keep modifying the script, I got the one modified by alteredlikeness, and it did everything without failure, yet still nothing actually changes. BMM is itself unable to create partitions for new systems, or any other changes, same as everything else.
The other things I mentioned I tried as a why not.
So where things are: I have used RSDlite as well as a script, both indicate without failure, and yet nothing changes at all. I can delete any file in a root browser and upon restart the file is still there. I can remove apps and they also remain upon restart.
lunatic987 said:
I did not download a jb anything. Only the scripts. The fxz I'm attempting to use is the att stock ics that I have used via rsd previously (phone is indeed ATT MB865. Rather than keep modifying the script, I got the one modified by alteredlikeness, and it did everything without failure, yet still nothing actually changes. BMM is itself unable to create partitions for new systems, or any other changes, same as everything else.
The other things I mentioned I tried as a why not.
So where things are: I have used RSDlite as well as a script, both indicate without failure, and yet nothing changes at all. I can delete any file in a root browser and upon restart the file is still there. I can remove apps and they also remain upon restart.
Click to expand...
Click to collapse
I think you have a hardware issue, maybe the phones internal storage has an issue.
BTW the script that alteredlikness posted is mine, with the "official" ICS FXZ. I would have linked you to that one, but I thought you had an international phone, and needed to use another FXZ, sorry about that, that would have been way easier.
If you still have a warranty I would try and use it, if not, you may try and buy an atrix2 off ebay with a broken screen and use your screen and digitizer with the board from the phone with the broken screen that you buy, they are much cheaper this way... There is a post in the General section on how to do this.
You may also have to uninstall BMM, it could be the one locking up your partition table, I know you really do not want to, but that is worth a try, if you can then restore the FXZ.
jimbridgman said:
I think you have a hardware issue, maybe the phones internal storage has an issue.
BTW the script that alteredlikness posted is mine, with the "official" ICS FXZ. I would have linked you to that one, but I thought you had an international phone, and needed to use another FXZ, sorry about that, that would have been way easier.
If you still have a warranty I would try and use it, if not, you may try and buy an atrix2 off ebay with a broken screen and use your screen and digitizer with the board from the phone with the broken screen that you buy, they are much cheaper this way... There is a post in the General section on how to do this.
You may also have to uninstall BMM, it could be the one locking up your partition table, I know you really do not want to, but that is worth a try, if you can then restore the FXZ.
Click to expand...
Click to collapse
Even the attempt at removing BMM did not actually succeed. And at this point I'm betting I could fxz things that would normally brick ics and it will have no effect.
I was hoping there might be some hidden little trick I could pull off to shock it into working properly for now, although I wouldn't be able to trust it. So conclusion is internal storage is now effectively Read Only Memory instead of behaving as flash. Since threatening it's life hasn't worked, I guess I'm now going to be threatening to rip out it's soul and replace it with a less stubborn soul. I'll have to keep an eye on damaged phones on ebay then, to try and repair it.
Phone was slightly used when I got it, a couple months out from release, so yeah no warranty. Ugh because I took care of the phone... ungrateful thing.
Thanks for help, just sucks it did not work.
xml script file for Stock Jelly Bean leak 1 for Non AT&T model
jimbridgman said:
Ok, so first off the xml.zip will not load from BMM or system recovery, it was not meant to be used like that... and it is only meant to be used with RSD, and why the check fails when doing it from those other methods.
Yes I know the script was never really ever finished for windows, it was originally meant as a way for linux users to flash the fxz, and then a few windows users made the request I never really got time to fully finish it.
Are you sure you have the right FXZ for your phone? The errors that you have from my script are that it can not flash the bootloader pre-install files and the cdt.bin, that tells me you may have the wrong fxz, possibly. Otherwise you are missing those files, or worse that that since you flashed the JB image, you may have to modify my script, so that it does not flash the mbm files, and then edit the xml file to use the cdt.bin from the JB image... This has been a know deal around here since ICS came out.
At this point you can try poking around with my script, since I do not have windows, I can't really test it, but you can see if there is a way you can get it to see those files it is complaining about, you may have to hardcode their location into the script to make it do it... but be careful, since you loaded JB on there.
Jim
Click to expand...
Click to collapse
Hello Jim,
Long time and I hope you read this. Maybe I may not be able to word this correctly but the xml file script method which you made for ICS & which Altered too mapped the same, I was hoping if You,Altered or any of the developers could post the same but for stock official Jellybean leak 1 seeing how many A2 users have hopped on to the Jelly bean platform (of course these are the non AT&T model users). I ask this as yet we see many people stating their fxz has failed via RSD and could be extremely helpful for many of us & also until the time we wait for a stable SafeStrap by Hashcode which he is apparently working on for the Edison which will have regular updates as BMM 0.3.4 support has been discontinued & it has many quirks. Thanks!
Related
Hello everyone. I royally screwed up my Kyocera Zio. Long story short I have a phone with all of the system partitions that were erased using FastBoot (Don't Ask lol) If someone can upload a full stock 1.6 Cricket ROM would I be able to flash the .img files into the corresponding partitions using FastBoot? My phone is partitioned as follows
'fota_amss'
'boot'
'system'
'flex'
'recovery'
'userdata'
'fota_boot"
'cache'
'misc'
Please Please someone help
http://www.megaupload.com/?d=7GXDFKOG maybe this could help it looks to be a dump file and not really a rom but maybe just maybe you can do something with it. lol well cricket and sanyo says they are going to be updating the phone by a link this is looking good they both say jan or feb they seem to be on the same page.
im also looking to see if i have anyfriends that work for cricket maybe i can get my hands on a reflash rom
I'm trying to follow the instructions for getting TWRP recovery: http://forum.xda-developers.com/showthread.php?t=1239821 I'm running into a problem, but since I'm a noob, I can't post on that thread. Can someone point me to where I should post this question?
Here is my problem. I've gone through all the instructions listed on the post (unloved my Evo3d via the HBoot method) and things work fine till this point:
It will ouput something like this,
Code:
sending 'recovery' <5068 KB>... OKAY
writing 'recovery'... OKAY
finished. total time: 11.355s
Now you have twrp recovery, so you can navigate to it. On ur phone, use the power button to pick bootloader, then scroll down to recovery and pick that. You will then be booted into recovery.
Here you can pick "install zip" and then pick the "su-2.3.6.3.zip"
Click to expand...
Click to collapse
I believe I'm in the twrp recovery, but when I select "bootloader" with the power button, I don't get the chance to scroll down to "recovery", because it starts doing something right after I select "bootloader" At the end it gives me this message: "Main Version is older! Update Fail! Press <Power> to reboot".
Any help is appreciated. If I'm posting in the wrong place, I'm sorry. I'm not sure where to put this question...
Yes you have...
Thread moved to Q&A due to it being a question. Would advise you to read forum rules and post in correct section.
Failure to comply with forum rules will result in an infraction and/or ban depending on severity of rule break.
Sorry about that! I'll read over the rules and make sure I post in the right place
I figured this out. I needed to delete the PG86IMG.zip file out of the root of my SD card, after doing that, all worked as expected.
Hi,
http://forum.xda-developers.com/showthread.php?t=1865582
I earlier posted this thread, but at that time I was not sure of so many things and what exactly was wrong with my phone.
But now after trying for about a week or so I have got most of the things figured out
So here it goes....
I was not able to install the OTA 2.3.6 update by any means possible.(I was on 2.3.5 all the time and I am still on 2.3.5 only)
So, I tried to unlock my phone using the 2.3.6 one click method(I am not sure why I thought it will help with installing the update)....I dont exactly remember it worked or not.
I was still not able to install the update. So, I thought lets get to stock and then try it again.
So, I followed this post to get back to stock 2.3.5
http://forum.xda-developers.com/showthread.php?t=1396650
I tried to create the back up first using this guide
http://forum.xda-developers.com/showthread.php?t=1511616
I installed ATRIX2 BOOTSTRAP but I rebooted it never rebooted in Clockworkmod Recovery mode.
So , I was not able to create any backup.
But, when I tried to use the RSD lite to install the 2.3.5 firmware back to the phone it failed with this error
Failed flashing process: Failed flashing process 3/20 flash mbmloader "mbmloader.bin" -> Phone returned FAIL ;phone connected"
After this I was rebooting all the time in AP fast boot mode only and had to select normal reboot to use my phone....but everything kept on crashing after this...many processes were force closing....but I was still able to make calls and playing music.
Then I came across the http://forum.xda-developers.com/showthread.php?t=1539167 return to stock script... it was able to write everything except this < waiting for device >
sending 'mbmloader' (39 KB)... OKAY [ 0.005s]
writing 'mbmloader'... INFOCommand restricted
FAILED (remote: ) (you can see the complete output in my previous post link above)
The script fixed the always booting in fastboot mode. But still rest of the things were the same all processes force closing
But, it was so irritating I had to restart my phone every few hours because some critical android process was force closed. sometimes the contacts were not loaded etc.....
So, I posted the previous thread on this forum asking help, but since I was not very precise about the problem I think people were not able to help me.
So, what actually I have figured out is my complete phone memory is in read only mode...I don't know which of the above things would have did this. Well, if you ask me how I know this... I used the es file explorer to go into the system dir deleted some files rebooted and they were back there. I tried the adb shell and tried to set the permission but it failed saying the file system is read only.
Also, when I try the root.bat file its saying this...
2100 KB/s (501292 bytes in 0.233s)
[*] Motofail: Universal Motorola Android Root Exploit
[*] Copyright (c) 2012 Dan Rosenberg (@djrbliss)
[*] Exploit complete.
[*] Done. Rebooting device...
[*] Done. Pushing su and Superuser to device...
failed to copy 'su' to '/system/xbin/su': Read-only file system
Unable to chmod /system/xbin/su: Read-only file system
link failed File exists
failed to copy 'Superuser.apk' to '/system/app/Superuser.apk': Read-only file sy
stem
[*] Done. Cleaning up exploit...
/data/local/motofail: not found
rm failed for /data/local/motofail, No such file or directory
and when I try the unroot file it says that it is not able to find Superuser.apk and it finds xbin/su but it cannot remove it saying file system is readonly
Please help me get out of this problem...I have looked around the internet but I have not found any solution.
Also, here is the system info of my phone
System Version: 55.11.16.MB865.ATT.en.US
Android Version:2.3.5
Kernel Version: 2011-09-21 09:42 off.Bld LUD_EDISON_RLD7_PATCH_27_110921_0913
Build number:5.5.1-175 EDEFW1-16
All I want is to somehow get the file system out of the read only mode so that I get unroot the phone and get it repaired form the motorola people only....I cannot give them this rooted phone since they ill just return it saying the warranty is void since its rooted.
OR it would be much much better if someone can figure out what the problem is and I can just get back to stock....
Thanks in advance guys....I hope someone will be able to figure out what I did wrong.
Ok I can go into why your phone did everything that it did, but that would take too long. if you'd really like know I can respond later when I'm not on my phone.
Fxz back will fix all these problems.
So, some questions then. So you have the proper Motorola drivers installed? What version of rsd lite are you using?
If you're having issues with rsd, we can adjust Jim's script to work with the regular fxz.
Sent from my SAMSUNG-SGH-I727 using xda premium
Fall of Enosis said:
Ok I can go into why your phone did everything that it did, but that would take too long. if you'd really like know I can respond later when I'm not on my phone.
Fxz back will fix all these problems.
So, some questions then. So you have the proper Motorola drivers installed? What version of rsd lite are you using?
If you're having issues with rsd, we can adjust Jim's script to work with the regular fxz.
Sent from my SAMSUNG-SGH-I727 using xda premium
Click to expand...
Click to collapse
Hi, I would love to hear from you what the problem was, whenever you can tell me
I am using RSD Lite v5.6
I suppose I have the right Motorola drivers installed...not sure how to check it..but I am able to connect my phone use adb to it and all...
I am not sure if it was RSD lite or it was me that caused it....
Also I was trying to do this on Aug 29.... and whenever I reboot my phone my last call history gives me the call I placed on Aug 29 4:27 pm....
black_panther10 said:
I installed ATRIX2 BOOTSTRAP but I rebooted it never rebooted in Clockworkmod Recovery mode.
So , I was not able to create any backup.
Click to expand...
Click to collapse
I am assuming this is most likely due to the fact that your did not hit the "top" button to install the recovery, so it wouldn't boot into it.
black_panther10 said:
But, when I tried to use the RSD lite to install the 2.3.5 firmware back to the phone it failed with this error
Failed flashing process: Failed flashing process 3/20 flash mbmloader "mbmloader.bin" -> Phone returned FAIL ;phone connected"
After this I was rebooting all the time in AP fast boot mode only and had to select normal reboot to use my phone....but everything kept on crashing after this...many processes were force closing....but I was still able to make calls and playing music.
Click to expand...
Click to collapse
I am also assuming in Fastboot it said "Flash failure" in the corner? This is because, for whatever reason, some part of the FXZ didn't flash properly. Now on boot up the phone does system checks and if those checks don't pass it will automatically throw you into fastboot. Hence the "flash failure". Whatever part of the FXZ that failed is what was failing the system checks.
black_panther10 said:
Also, when I try the root.bat file its saying this...
2100 KB/s (501292 bytes in 0.233s)
[*] Motofail: Universal Motorola Android Root Exploit
[*] Copyright (c) 2012 Dan Rosenberg (@djrbliss)
[*] Exploit complete.
[*] Done. Rebooting device...
[*] Done. Pushing su and Superuser to device...
failed to copy 'su' to '/system/xbin/su': Read-only file system
Unable to chmod /system/xbin/su: Read-only file system
link failed File exists
failed to copy 'Superuser.apk' to '/system/app/Superuser.apk': Read-only file sy
stem
[*] Done. Cleaning up exploit...
/data/local/motofail: not found
rm failed for /data/local/motofail, No such file or directory
Click to expand...
Click to collapse
The generic "Motofail" exploit does NOT work on the A2. See the NOOB thread with the proper way to ROOT 2.3.5, or 2.3.6 (as both are different.)
black_panther10 said:
and when I try the unroot file it says that it is not able to find Superuser.apk and it finds xbin/su but it cannot remove it saying file system is readonly
Click to expand...
Click to collapse
I'm assuming this is because you never properly rooted. Can't remove something that isn't there.
NOW. DEEP BREATH FALL....
You can do this one of two ways. I think the FXZ you have is borked somehow. DL the 2.3.5 FXZ from THIS thread. MAKE SURE THE MD5 MATCHES. If you don't know how to check MD5's then download hashtab and check it that way. Find PRicherdson's thread on it HERE. Make sure to thank the man.
Then check and make sure the proper Moto drivers are installed. Fine those HERE.
Next make sure your USB cable is plugged into the BACK of your PC. Hop into fastboot and make sure it says "Battery ok, Ok to program"
Then make sure the FXZ file is located on the ROOT of the C drive. It's easier if it's just dropped onto the C: drive. Also, feel free to Unzip it, as RSD lite will still recognize it and flash faster.
Then run it. Let me know how it goes. If it fails, we can modify Jim's script and go that route.
Good luck! :victory:
Thanks for your reply.....
I tried to flash it using the fsz and it failed at 3/20 failed to load mbmloader.bin.....also I hecked the md5 and it was correct......
Also, I did pressed the top button in the Atrix2 bootstrap...I pressed the top button it immediately rebooted but it rebooted normally......
Right now its booting in AP Fast Boot mode and I have to select normal mode each time.....
How should we proceed
Waiting for your reply....
The bootloader isn't flashing properly, causing some rift is his space-time continuum?
Sent from my fingers to your peepers
Apex_Strider said:
The bootloader isn't flashing properly, causing some rift is his space-time continuum?
Sent from my fingers to your peepers
Click to expand...
Click to collapse
Man, you have any other suggestions to solve this problem....
Hey, I have a question since its failing on the mbmloader can't I just remove that entry form the xml file in the image and then try it with rsd lite most probably it will skip the mbmloader.bin and continue. What I just noticed is that the script is that the script method does not write grfs.img and system.img
So, may be this is why even after trying the script method my phone was still in the same state as it was.......??
Is the mbmloader.bin critical?? if it is not changed.... I have tried the 2.3.6 upgrade but it always failed so I suppose it is never changed???
Also in this link the same solution is mentioned
http://mobility.forumsee.com/a/m/s/...-from-after-any-type-bootloop-fxz-errors.html
Please reply....
Bounce...
Please reply guys I really need all your help....
The mbmloader.bin has to flash in the fxz, you cannot omit this from the .xml as this is the bootloader itself. Doing so you will likely fail at another process and/or your phone will not boot. Try and re-download the proper fxz for your phone, make sure your USB cable is good, and you're using the latest version of RSD Lite, USB to back of PC, latest Motorola drivers installed on your PC, and maybe restart your PC after checking all this before you attempt again...
Sent from my fingers to your peepers
Apex_Strider said:
The mbmloader.bin has to flash in the fxz, you cannot omit this from the .xml as this is the bootloader itself. Doing so you will likely fail at another process and/or your phone will not boot. Try and re-download the proper fxz for your phone, make sure your USB cable is good, and you're using the latest version of RSD Lite, USB to back of PC, latest Motorola drivers installed on your PC, and maybe restart your PC after checking all this before you attempt again...
Sent from my fingers to your peepers
Click to expand...
Click to collapse
I am doing all these things and the MD5 is right, the fsz version is exactly the same as on my settings...but after I reimage my phone...after reimaging everything,,,,when the phone restarts nothing changes I mean the phone remains completely the same was on Aug 29.......After reimaging it should be like a brand new phone asking for my gmail accounts and all those things instead after restart its like I did nothing to it....nothing is actually written to the memory???
Can you please think of any possible reason that this might be happening...??
It started from Aug 29 when I was trying to fsz back to 2.3.5,,,,I was already on 2.3.5 but still I was trying it and I did something wrong that caused this...??
Eagerly waiting for your reply......
BUMP!!!!!......
http://forum.xda-developers.com/showthread.php?t=1901172
Found this on the forum....but when I try to remove the CWM Recovery it says the file system is read only even when I am trying to do it in root terminal.
Please help guys...I am stuck badly......Now I know what caused the problem but how to fix it??
Thanks in advance...
black_panther10 said:
BUMP!!!!!......
http://forum.xda-developers.com/showthread.php?t=1901172
Found this on the forum....but when I try to remove the CWM Recovery it says the file system is read only even when I am trying to do it in root terminal.
Please help guys...I am stuck badly......Now I know what caused the problem but how to fix it??
Thanks in advance...
Click to expand...
Click to collapse
Try using Root Explorer, clicking the "R/O" button at the top right when you locate the files you want to delete, which will change it to "R/W", and you should be able to delete...
Sent from my rooted Mayan Calendar
Do you have USB debuging mode clicked on, on your phone?
You can download the latest drivers directly from Motorola's website.
You may have to run the restore fxz a couple of times to get it to go without errors.
I have a Motorola Droid RAZR HD XT926 (CDMA for Verizon Wireless). I was running root stock ROM on it, and have run into the following problems:
Phone boot is stuck at Motorola logo.
Attempting to go into recovery (ClockworkMod) gives errors that it can't mount any directory (cache, system, etc).
Attempting to RSDLite back to stock fails (on step 1 out of 6 - boot.img - phone returned FAIL).
Attempts to use Droid RAZR HD Toolkit v1.21 and flashing system.img fails (unable to format remote storage).
Anything else worth trying? Or is this hard-bricked, and going on eBay for parts?
Thank you.
How long should it take for RSD to load the 27 files?
I was trying to FXZ back to stock JB but the boot.img file 10MB too about an hour, so I looked at the next file and it was system.... something and it was over 300 MB anyway quick math it would be days to complete so I stopped it and UT oh got the phone back to booting but then it bricked but that's another story.... How long should it take RSD to load the FXZ files?
Thanks,
daredream777 said:
I was trying to FXZ back to stock JB but the boot.img file 10MB too about an hour, so I looked at the next file and it was system.... something and it was over 300 MB anyway quick math it would be days to complete so I stopped it and UT oh got the phone back to booting but then it bricked but that's another story.... How long should it take RSD to load the FXZ files?
Thanks,
Click to expand...
Click to collapse
i dont think i have had it take much more than 5 minutes, defiantly no more than 10, but i have heard reports of as long as 15.
daredream777 said:
I was trying to FXZ back to stock JB but the boot.img file 10MB too about an hour, so I looked at the next file and it was system.... something and it was over 300 MB anyway quick math it would be days to complete so I stopped it and UT oh got the phone back to booting but then it bricked but that's another story.... How long should it take RSD to load the FXZ files?
Thanks,
Click to expand...
Click to collapse
Have you try flashing it through fastboot? something like
Code:
fastboot flash boot boot.img
but probably you will need to use mfastboot due to the img size
Code:
mfastboot flash boot boot.img
pbosio said:
Have you try flashing it through fastboot? something like
Code:
fastboot flash boot boot.img
but probably you will need to use mfastboot due to the img size
Code:
mfastboot flash boot boot.img
Click to expand...
Click to collapse
fastboot will flash it all day long. you generally only need mfastboot for re-writing partitions. but it will flash the img also, as you suggest.
fastboot
bweN diorD said:
fastboot will flash it all day long. you generally only need mfastboot for re-writing partitions. but it will flash the img also, as you suggest.
Click to expand...
Click to collapse
So you are saying fastboot will take a loooong time to load? I need to get back to factory fresh.... What is the best way to do that without taking 3 days?
I have a Razr Maxx HD on JB and have run djbliss recovery but the phone is still rooted afterward. The phone wants to upgrade to KItKat but I have not allowed that since I have heard about some problems for the XT926.... What do you say? If I could just let it upgrade that may be the easiest path but I just want the thing working again.
On those code lines do I just type that in to a command prompt? Somewhat of a noob so can you give me specifics?
Thanks.
ps. Amazingly my phone was bricked. Black, nothing not fastboot no usb port showing up.... I plugged in to wall charger and after about 24 hours I noticed the green light was on ... I pressed the power button, the battery icon showed 3%. A couple minutes later (after I had pressed the power button) it was 12%. Can you explain that? I guess just enough juice trickles in to eventually get a little charge in .... slow enough to maybe make some people go and get a new phone!
---------- Post added at 12:04 PM ---------- Previous post was at 11:39 AM ----------
Ok so I looked at djrbliss batch file and see he is using "fastboot" so yes I have tried that. and it runs through it but the phone is still rooted. Did something go wrong?
Also, VRZ_XT926_9.8.1Q-94-1_CFC.xml appears to be a newer file then he uses but one difference I noticed. "system.img" .... in this file it is "system.img.ext4" Can you explain that?
Thanks.
daredream777 said:
So you are saying fastboot will take a loooong time to load? I need to get back to factory fresh.... What is the best way to do that without taking 3 days?
I have a Razr Maxx HD on JB and have run djbliss recovery but the phone is still rooted afterward. The phone wants to upgrade to KItKat but I have not allowed that since I have heard about some problems for the XT926.... What do you say? If I could just let it upgrade that may be the easiest path but I just want the thing working again.
On those code lines do I just type that in to a command prompt? Somewhat of a noob so can you give me specifics?
Thanks.
ps. Amazingly my phone was bricked. Black, nothing not fastboot no usb port showing up.... I plugged in to wall charger and after about 24 hours I noticed the green light was on ... I pressed the power button, the battery icon showed 3%. A couple minutes later (after I had pressed the power button) it was 12%. Can you explain that? I guess just enough juice trickles in to eventually get a little charge in .... slow enough to maybe make some people go and get a new phone!
---------- Post added at 12:04 PM ---------- Previous post was at 11:39 AM ----------
Ok so I looked at djrbliss batch file and see he is using "fastboot" so yes I have tried that. and it runs through it but the phone is still rooted. Did something go wrong?
Also, VRZ_XT926_9.8.1Q-94-1_CFC.xml appears to be a newer file then he uses but one difference I noticed. "system.img" .... in this file it is "system.img.ext4" Can you explain that?
Thanks.
Click to expand...
Click to collapse
i did not intend to imply the process took a day to flash, "all day long" is merely 'slang' implying it could do it at any time.
the flash could take any where from a few minutes to as long as 15, however 5min or so is most common.
razr utility from the dev forum will restore your phone to factory. make sure you get the correct version, or a newer one is fine too.
not sure what you mean by "have run djbliss recovery", i wasnt aware he made recoveries. can you provide a link so i can see what your talking about.
if you upgrade to the FIRST kk build, you can unlock the bootloader, then if you dont like kk, you can flash back to jb.
yes you can just enter those into a command prompt, but your phone has to be in fastboot, and you have to have adb and fastboot installed on your pc or it wont work.
i can only assume your battery charging issues are a result of running it completely dead. thats not a good idea, and wont always charge back up no matter how long its plugged in. i would consider yourself lucky on that and try not to do it again.
i cant comment on this "Ok so I looked at djrbliss batch file...." until i see what you are talking about.
i dont know the reason for the "ext" extension. either the partition format changed, or some other reason i cant explain.
as long as you flash all the files in any build, there should be no issues.
Back to fresh & JB vs KK
bweN diorD said:
i did not intend to imply the process took a day to flash, "all day long" is merely 'slang' implying it could do it at any time.
the flash could take any where from a few minutes to as long as 15, however 5min or so is most common.
razr utility from the dev forum will restore your phone to factory. make sure you get the correct version, or a newer one is fine too.
not sure what you mean by "have run djbliss recovery", i wasnt aware he made recoveries. can you provide a link so i can see what your talking about.
if you upgrade to the FIRST kk build, you can unlock the bootloader, then if you dont like kk, you can flash back to jb.
yes you can just enter those into a command prompt, but your phone has to be in fastboot, and you have to have adb and fastboot installed on your pc or it wont work.
i can only assume your battery charging issues are a result of running it completely dead. thats not a good idea, and wont always charge back up no matter how long its plugged in. i would consider yourself lucky on that and try not to do it again.
i cant comment on this "Ok so I looked at djrbliss batch file...." until i see what you are talking about.
i dont know the reason for the "ext" extension. either the partition format changed, or some other reason i cant explain.
as long as you flash all the files in any build, there should be no issues.
Click to expand...
Click to collapse
Thanks for your info! I didn't realize the battery was drained! You are right I was very lucky. I ordered a usb programming adapter from Black Hat.
Yes all of those (adb & fastboot) seem to be present from the Droid Razr Utility 1.21. Which is where djrbliss batch file came from (windowsutility.bat) .... Here is the link from where I got it. http://forum.xda-developers.com/showthread.php?t=2307439
Also, here is the link to the (looks like) newer JB XML http://sbf.droid-developers.org/phone.php?device=5 vs the one that was in the Utility 1.21. This has the "system.img.ext4"
Additionally I have a mac but I don't seem to get good results when I try to use the mac.... failure messages. Does that have anything to do with the usb setting in the phone of MTP or Camera? (debugging is on)
All of this is because my phone doesn't receive text messages on pageplus since trying to unflash and upgrading to 4G. Everything else worked fine calls, data and can send text and I just wanted to try and get back to a totally fresh install to see if that made a difference.
Could the long write time in RSD Lite be due to using a virtual Windows 7 on fusion?
So what is your opinion on Kit Kat? Is it worth the upgrade? Is there anything really gained? I am content with JB but if there are some cool user features or something .... my battery lasts 2 days under JB so that really isn't an issue but hey if KK makes it go even longer that would be a +.
Thanks again.
daredream777 said:
Thanks for your info! I didn't realize the battery was drained! You are right I was very lucky. I ordered a usb programming adapter from Black Hat.
Yes all of those (adb & fastboot) seem to be present from the Droid Razr Utility 1.21. Which is where djrbliss batch file came from (windowsutility.bat) .... Here is the link from where I got it. http://forum.xda-developers.com/showthread.php?t=2307439
Also, here is the link to the (looks like) newer JB XML http://sbf.droid-developers.org/phone.php?device=5 vs the one that was in the Utility 1.21. This has the "system.img.ext4"
Additionally I have a mac but I don't seem to get good results when I try to use the mac.... failure messages. Does that have anything to do with the usb setting in the phone of MTP or Camera? (debugging is on)
All of this is because my phone doesn't receive text messages on pageplus since trying to unflash and upgrading to 4G. Everything else worked fine calls, data and can send text and I just wanted to try and get back to a totally fresh install to see if that made a difference.
Could the long write time in RSD Lite be due to using a virtual Windows 7 on fusion?
So what is your opinion on Kit Kat? Is it worth the upgrade? Is there anything really gained? I am content with JB but if there are some cool user features or something .... my battery lasts 2 days under JB so that really isn't an issue but hey if KK makes it go even longer that would be a +.
Thanks again.
Click to expand...
Click to collapse
thats Matt's utility, not Dan's, the same one i maintain here since Matt stopped.
unfortunately, i havent been updating the mac and osx files, so i doubt you can use it directly on a mac. maybe with a virtual setup, but im no expert on that.
if you are happy with your setup, i would just try to re-flash that if need be. mainly the system, if nothing else, then factory reset, or -w command in fastboot.
everyone's option off kk will be different, i dont think its worth leaving something that you like for though.
if you can use a windows machine for 15min or so, you can use this guide to flash kk, root, unlock the bootloader, then flash back to jb if you dont like it. if you update past the first kk to the current one before unlocking, you will not be able to go back to jb, ever. just a fyi.
RSD vs Fastboot
bweN diorD said:
thats Matt's utility, not Dan's, the same one i maintain here since Matt stopped.
unfortunately, i havent been updating the mac and osx files, so i doubt you can use it directly on a mac. maybe with a virtual setup, but im no expert on that.
if you are happy with your setup, i would just try to re-flash that if need be. mainly the system, if nothing else, then factory reset, or -w command in fastboot.
everyone's option off kk will be different, i dont think its worth leaving something that you like for though.
if you can use a windows machine for 15min or so, you can use this guide to flash kk, root, unlock the bootloader, then flash back to jb if you dont like it. if you update past the first kk to the current one before unlocking, you will not be able to go back to jb, ever. just a fyi.
Click to expand...
Click to collapse
Thanks for the info.
So what is the difference between doing a flash with RSD and using the Utility(or fastboot)? Is one more complete? When I used the utility I was still rooted, so in my mind that is not factory fresh and I had killed the sound on boot up and that is still silent.
What does the -w do?
Is RSD flasher just a fancy automated way of doing an RSD flash?
Did you figure out what the ".ext4" was on the end of the system.img.ext4? VRZ_XT926_9.8.1Q-94-1_CFC.xml
I'm starting to get my head around some of this but wow there is a lot to it!
Thanks for your help.
daredream777 said:
Thanks for the info.
So what is the difference between doing a flash with RSD and using the Utility(or fastboot)? Is one more complete? When I used the utility I was still rooted, so in my mind that is not factory fresh and I had killed the sound on boot up and that is still silent.
What does the -w do?
Is RSD flasher just a fancy automated way of doing an RSD flash?
Did you figure out what the ".ext4" was on the end of the system.img.ext4? VRZ_XT926_9.8.1Q-94-1_CFC.xml
I'm starting to get my head around some of this but wow there is a lot to it!
Thanks for your help.
Click to expand...
Click to collapse
fastboot can do a bit more than rsd and you can flash one file or many rather easily.
most of the utilites only contain key files needed to upgrade or re-flash, regardless if they were changed. i only made 2 builds with a complete flash, v-1.4 and v-1.41.
about root, im pretty sure i have never had that happen, and i have flashed quite a bit. maybe i just never noticed. i believe the system would need to be formatted to completely clean it, but i dont know if its done by default or not. did the system flash properly in the utility? all pass no fail?
if you used the wrong version, some things would fail if your bootloader is locked.
-w is basically a factory reset.
i didnt look into the ext extension.
Utility run failure
bweN diorD said:
fastboot can do a bit more than rsd and you can flash one file or many rather easily.
most of the utilites only contain key files needed to upgrade or re-flash, regardless if they were changed. i only made 2 builds with a complete flash, v-1.4 and v-1.41.
about root, im pretty sure i have never had that happen, and i have flashed quite a bit. maybe i just never noticed. i believe the system would need to be formatted to completely clean it, but i dont know if its done by default or not. did the system flash properly in the utility? all pass no fail?
if you used the wrong version, some things would fail if your bootloader is locked.
-w is basically a factory reset.
i didnt look into the ext extension.
Click to expand...
Click to collapse
Just reran the utility and it did not run clean
Here is the results of the utility run
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I inserted the image but it is not showing up. Basically it said it:
load_file: could not allocate 870148648 bytes
error: cannot load 'system.img'
sending 'boot' (10240 KB) ....
OKAY [ 0.781s]
writing 'boot' ...
Preflash validation failed
FAILED (remote failure)
everything after this point ran fine.
Another note this article http://www.andromods.com/tips-trick...-unroot-unbrick-droid-razr-maxx-hd-xt926.html says to remove the 'getvar' from the xml file and it will be factory fresh. What does that do? Any opinion?
Thanks.
ps running RSD and it appears to hang at system .... has run for 20 minutes so far. This is where I pulled the plug when 'boot' took an hour on my virtual windows 7. This time boot took less than a second on a real windows 7 machine. I just saw it flash up and it was done.
daredream777 said:
Just reran the utility and it did not run clean
Here is the results of the utility run
I inserted the image but it is not showing up. Basically it said it:
load_file: could not allocate 870148648 bytes
error: cannot load 'system.img'
sending 'boot' (10240 KB) ....
OKAY [ 0.781s]
writing 'boot' ...
Preflash validation failed
FAILED (remote failure)
everything after this point ran fine.
Another note this article http://www.andromods.com/tips-trick...-unroot-unbrick-droid-razr-maxx-hd-xt926.html says to remove the 'getvar' from the xml file and it will be factory fresh. What does that do? Any opinion?
Thanks.
ps running RSD and it appears to hang at system .... has run for 20 minutes so far. This is where I pulled the plug when 'boot' took an hour on my virtual windows 7. This time boot took less than a second on a real windows 7 machine. I just saw it flash up and it was done.
Click to expand...
Click to collapse
its acting like you are using too old version of the script or something else unexpected is happening. not everything is failing, thats good. usually means its fixable.
if you are trying to flash jb, use this. it should either fix the problem, or the output failures will let me know what to try next.
if you were trying to flash kk then use this.
dont try the kk version if you havent tried to flash kk yet! it should work, i just dont want to further complicate this if it doesnt.
the getvar line is removed from the utilities and you should edit it out of the xml file if flashing with rsd.
the problem with rsd right now is it cant re-partition the phone unless you are upgrading. im trying to re-partition it for you as is, which mfastboot can do. mfastboot is what the utilities above use, and the partition files, which are not included in the general versions of the script.
post your results and well go from there.
SOLVED! I ran House of Moto utils
bweN diorD said:
its acting like you are using too old version of the script or something else unexpected is happening. not everything is failing, thats good. usually means its fixable.
if you are trying to flash jb, use this. it should either fix the problem, or the output failures will let me know what to try next.
if you were trying to flash kk then use this.
dont try the kk version if you havent tried to flash kk yet! it should work, i just dont want to further complicate this if it doesnt.
the getvar line is removed from the utilities and you should edit it out of the xml file if flashing with rsd.
the problem with rsd right now is it cant re-partition the phone unless you are upgrading. im trying to re-partition it for you as is, which mfastboot can do. mfastboot is what the utilities above use, and the partition files, which are not included in the general versions of the script.
post your results and well go from there.
Click to expand...
Click to collapse
Got it! Finally! Ran House of Moto script gen on it and it loaded back to factory fresh without a hitch. Thanks. So much info out there it takes a while to find the right path.
I'm sure there are other posts like this will be. I know - I've read probably all of them. But I am still stuck.
MHA-L29C636 phone. I rooted last night and when I was setting my apps back up, I noticed Snapchat wasn't working. A quick search told me to install XPosted Framework. I downloaded and installed it, and shortly after that, if not immediately, my phone shut off and wouldn't start.
I was at work, so I panicked. Thankfully, the eRecovery thing booted up and told me I could reinstall over WiFi. GREAT! Nope. It was not able to connect to the server. I tried a few times, reset. A few more, reset. Different network, reset.... Nothing was working. So, I did a data wipe and selected Dalvik Cache, Data, Internal Storage, Cache, System partition, and then did a factory reset. I figured that could clear out the XPosted install and I would start fresh. No, that also did not work...
So, I've searched for 6 hours since I've gotten home from work, tried countless methods and downloaded almost 20GB of images, custom ROMS, firmware files, etc. And LITERALLY almost 20GB. I keep running into issue after issue preventing me from getting anything to work.
I've installed ADB/Fastboot. That wasn't working, so I installed the full Android Studio and SDK Toolkit. Didn't get anywhere with Fastboot.
I've tried flashing custom ROM's to get SOMETHING back on my phone. Nothing will install.
I've tried doing a forced update with the POWER + VOL UP + VOL DOWN. Did not work. Gives an error of unable to update.
Then I came across HWOTA. The write ups were confusing as hell to me... but finally I understood one. Copied the 3 files to the SD card to load into the phone and went to run update.bat from the HWOTA extracted folder..... Except the batch file instantly closes and I don't get to see the screen with the numbers that EVERYONE else gets to see apparently.
HiSuite doesn't even see the phone.
I'm completely lost. I need some help. Badly.
@mankindtw I've seen hundreds of your posts. You seem pretty in the know with the Mate 9
http://www.carbontesla.com/2017/05/tutorial-rebrand-convert-huawei-mate-9-to-any-region/
https://forum.xda-developers.com/mate-9/how-to/guide-how-to-unbrick-mate-9-access-t3720953
https://forum.xda-developers.com/mate-9/how-to/guide-mate-9-flash-update-package-t3593108
I was following these guides for the HWOTA procedure, and as I said, the update.bat will not execute. "...is not recognized as an internal or external command,
operable program or batch file." is the message that is created.
https://www.getdroidtips.com/huawei-mate-9-b321-oreo-firmware/
I downloaded my firmware files from here, as well as the page here on XDA.
https://forum.xda-developers.com/mate-9/how-to/guide-mate-9-flash-update-package-t3593108/page26
Then I came across this man showing me what I can't see with update.bat. >.>
Hopefully someone can help quickly. I'm tired of messing with this phone and I'm needing it for this weekend.
What Android's version did you have? Nougat or Oreo?
If Nougat there is quick method to unbrick.
https://forum.xda-developers.com/mate-9/how-to/guide-rebrand-chinese-al00-mate9-to-t3554656
Just do option 4 - download special service ROM for your region C636 and apply it via dload.
If your phone will boot and has no system update, then do options with installing TWRP and additional package. System update will appear and you will have ability to get new ROM.
P.s. I don't know does this method work in case with Oreo's "brick". It did not tested.
5[Strogino] said:
What Android's version did you have? Nougat or Oreo?
If Nougat there is quick method to unbrick.
https://forum.xda-developers.com/mate-9/how-to/guide-rebrand-chinese-al00-mate9-to-t3554656
Just do option 4 - download special service ROM for your region C636 and apply it via dload.
If your phone will boot and has no system update, then do options with installing TWRP and additional package. System update will appear and you will have ability to get new ROM.
P.s. I don't know does this method work in case with Oreo's "brick". It did not tested.
Click to expand...
Click to collapse
Unfortunately, it just updated to O last week. I'm wondering if that's why the eRecovery does not work as it should.
I don't know enough about the file structure of Huawei to be able to know how to reload everything back into place, brand new. I'm familiar with Samsung and Odin, but I'm trying to find out the steps for getting everything squared away.
I also realized that I'm not 100% certain that this had the C636 FW. It's a dual SIM and I believe I bought the International version instead of the US version. Would it be best to rebrand to a specific region so I at least know what it's set up for?
What is the correct process for re-flashing the file structure and files? I'd imagine what I need to do is a full format, and then reload everything from the ground up. I just don't know the correct order. Re-brand, flash new UPDATE.APP and the 3 zip files? Would I force flash the UPDATE.APP and then flash zip through TWRP?
I've thought about cutting my losses and trying out this FunkyHuawei thing, that's just a good bit of money I was not prepared to be spending, and especially for no guaranteed result. I was not looking to mod this phone at all, just root access for some monitoring apps.
I may see what an authorized service center will charge to fix it. I'd hate to keep tinkering with it and get it hard bricked.
Why don't you try FunkyHuawei? You have to buy credits though... https://funkyhuawei.club/
gioarvdv said:
Why don't you try FunkyHuawei? You have to buy credits though... https://funkyhuawei.club/
Click to expand...
Click to collapse
I had said above that it was a lot of money to invest in something not guaranteed to work. At least if I brought it to a shop, I wouldn't pay unless it were fixed.
300zxmatt said:
I had said above that it was a lot of money to invest in something not guaranteed to work. At least if I brought it to a shop, I wouldn't pay unless it were fixed.
Click to expand...
Click to collapse
I think the reason your .bat file doesn't work is where you have it placed. I had the howta folder on my desktop and it wouldn't work not matter what I did. I moved it to the root of the c:// drive and then it worked. Perhaps you should try that.
Mmm... I have to just saying: stop killing phone!
Why you are thinking that format system will help? It will kill your system partition and you will get no ability to run into normal mode anymore. Without system partition phone will not run.
Why are you thinking that rebranding will help you? You have troubles with current region. You will feed the mess while rebranding cause it will get additional troubles with metadata mismatch.
Your current goal is to get phone when it is running normal. To do that, you can apply service ROM. Service ROM is special one, it is only ROM that can be flashed via dload. Other ROMs can not be flashed this way.
5[Strogino] said:
Mmm... I have to just saying: stop killing phone!
Why you are thinking that format system will help? It will kill your system partition and you will get no ability to run into normal mode anymore. Without system partition phone will not run.
Why are you thinking that rebranding will help you? You have troubles with current region. You will feed the mess while rebranding cause it will get additional troubles with metadata mismatch.
Your current goal is to get phone when it is running normal. To do that, you can apply service ROM. Service ROM is special one, it is only ROM that can be flashed via dload. Other ROMs can not be flashed this way.
Click to expand...
Click to collapse
Alright, I downloaded that offline firmware dload zip, extracted it on my SD card all alone, and tried installing. It gave a "Software Install Failed" message just like the other times.
https://forum.xda-developers.com/showthread.php?t=2277112
Following this to get a better understanding of Fastboot and how to use it.
I tried 'fastboot erase system -w' and it returned with
"wiping userdata...
Erase successful, but not automatically formatting.
Can't determine partition type.
FAILED (remote: Command not allowed)
erasing 'system'...
OKAY [ 46.028s]
erasing 'userdata'...
(bootloader) success to erase cryypt info in oeminfo
OKAY [ 0.358s]
finished. total time: 46.388s"
That first bit about being unable to determine the partition type worries me a little bit. That is why I was talking about re-wiping everything and starting from scratch @5[Strogino]
Wow. I booted into TWRP and went to do the factory reset through there and it threw an error for every operation. I have a feeling that trying more things is doing more harm than good.
Edit: found out how to fix that. I went to Wipe>Advanced Wipe>Selected 'System'>'Repair or Change'> and opted for EXT4 because apparently that is the most common.
300zxmatt said:
Wow. I booted into TWRP and went to do the factory reset through there and it threw an error for every operation. I have a feeling that trying more things is doing more harm than good.
Edit: found out how to fix that. I went to Wipe>Advanced Wipe>Selected 'System'>'Repair or Change'> and opted for EXT4 because apparently that is the most common.
Click to expand...
Click to collapse
Dude you're really just making **** worse by throwing the everything and the kitchen sink at it. Inbox me or something so we can have a conversation as to your options
I agree...
shae23 said:
I think the reason your .bat file doesn't work is where you have it placed. I had the howta folder on my desktop and it wouldn't work not matter what I did. I moved it to the root of the c:// drive and then it worked. Perhaps you should try that.
Click to expand...
Click to collapse
the reason why the Batch file instantly closes is due to where you have saved it. Move it to C:\ and you should be good to go. HWOTA is by far the best method to recover your phone (in my opinion)....and even better....it's free!
rbt001 said:
the reason why the Batch file instantly closes is due to where you have saved it. Move it to C:\ and you should be good to go. HWOTA is by far the best method to recover your phone (in my opinion)....and even better....it's free!
Click to expand...
Click to collapse
Well! That got me somewhere! I never saw anywhere that I found to place it in the root directory of the drive. I guess since ADB is located there, it kind of makes sense?
Now, new issue. This is what I'm getting off the bat.
****************************************
* *
* This script is made by XDA mankindtw *
* *
****************************************
Use Vol-Dn + USB Cable to boot into fastboot mode.
Press ENTER key to continue...
Replace recovery to TWRP, please wait...
target reported max download size of 471859200 bytes
sending 'recovery' (20702 KB)...
OKAY [ 0.665s]
writing 'recovery'...
FAILED (remote: partition length get error)
finished. total time: 0.678s
Disconnect usb cable and turn off phone, use Vol-Up and Power key to enter TWRP recovery.
Press ENTER key to continue...
Click to expand...
Click to collapse
And after this failure, it will not do anything when I attempt to follow the prompt to boot and reconnect USB inside TWRP.
Any ideas from this point? Happy to have SOME amount of progress, and glad to be learning the correct procedure!
300zxmatt said:
Well! That got me somewhere! I never saw anywhere that I found to place it in the root directory of the drive. I guess since ADB is located there, it kind of makes sense?
Now, new issue. This is what I'm getting off the bat.
And after this failure, it will not do anything when I attempt to follow the prompt to boot and reconnect USB inside TWRP.
Any ideas from this point? Happy to have SOME amount of progress, and glad to be learning the correct procedure!
Click to expand...
Click to collapse
That's easy enough, do you have Twrp installed, if not, what was your last Android version, nougat or Oreo?
shae23 said:
That's easy enough, do you have Twrp installed, if not, what was your last Android version, nougat or Oreo?
Click to expand...
Click to collapse
Yes, I have TWRP installed prior to all of this. Most recent version was Oreo. I used the "twrp_android_o_mate9_a1" file to flash TWRP.
Under C:\HWOTA\recovery\MHA, I have 3 recovery versions. I'm assuming the script flashes "MHA_twrp-3.0.3-1-hi3660" judging my the returned file size and the file size in Windows for that file. I wonder if flashing it manually would fix the issue.
Here is the solution (forwad)
This is TWRP to Mate 9/Android O, brought to you by FunkyHuawei. This will also work for the Mate 10, Mate 10 Pro, Mate 10 Porsche and other EMUI 8 devices.
It´s just a preliminary build so I can´t promise anything/everything will work! Keep that in mind. I´m not responsible if you brick your device.
DOWNLOAD LINK:
https://drive.google.com/file/d/0B45...Eh2aDFLM3JlYkU
It works on the Android O build here:
https://www.reddit.com/r/FunkyHuawei...id_o_beta_for/
and the official European beta.
To install:
First, have Android O running. Unlock the bootloader. Download the twrp image.
Then, run in fastboot mode:
fastboot flash recovery_ramdisk twrp_android_o_mate9_a1.img
Then, reboot holding volume up, and you´ve got TWRP!
Note: With the Android O update, it is no longer possible to flash the recovery2 partition. Furthermore, the names of the partitions have changed. Please keep that in mind, and don´t mess around too much with TWRP, to be sure you don´t brick your system!
Click to expand...
Click to collapse
I tried flashing the TWRP included in HWOTA and it err'd the same way. I'm assuming that like when I first installed TWRP and it didn't take the regular release, the version included and scripted with HWOTA is not compatible with O?
@mankindtw do you know anything about what my issue is with the script? TIA!
Here is the solution (forwad)
This is TWRP to Mate 9/Android O, brought to you by FunkyHuawei. This will also work for the Mate 10, Mate 10 Pro, Mate 10 Porsche and other EMUI 8 devices.
It´s just a preliminary build so I can´t promise anything/everything will work! Keep that in mind. I´m not responsible if you brick your device.
DOWNLOAD LINK:
https://drive.google.com/file/d/0B45...Eh2aDFLM3JlYkU
It works on the Android O build here:
https://www.reddit.com/r/FunkyHuawei...id_o_beta_for/
and the official European beta.
To install:
First, have Android O running. Unlock the bootloader. Download the twrp image.
Then, run in fastboot mode:
fastboot flash recovery_ramdisk twrp_android_o_mate9_a1.img
Then, reboot holding volume up, and you´ve got TWRP!
Note: With the Android O update, it is no longer possible to flash the recovery2 partition. Furthermore, the names of the partitions have changed. Please keep that in mind, and don´t mess around too much with TWRP, to be sure you don´t brick your system!
Click to expand...
Click to collapse
I tried flashing the TWRP included in HWOTA and it err'd the same way. I'm assuming that like when I first installed TWRP and it didn't take the regular release, the version included and scripted with HWOTA is not compatible with O?
@mankindtw do you know anything about what my issue is with the script? TIA!
C:\Users\Matt\Downloads>fastboot flash recovery_ramdisk twrp_android_o_mate9_a1.img
target reported max download size of 471859200 bytes
sending 'recovery_ramdisk' (26982 KB)...
OKAY [ 1.045s]
writing 'recovery_ramdisk'...
OKAY [ 0.267s]
finished. total time: 1.314s
Click to expand...
Click to collapse
Flashing the O version above works fine.