Related
I have a T-Mobile UK DHD that I'd fully rooted, Eng-Off, Radio S-Off & SuperCID
I was running a LeeDroid ROM but yesterday it began frequently locking up so I tried to do a wipe and reinstall the ROM but at the end of the ROM installation after "Writing boot.img" it said:
assert failed: write_raw_image ("/tmp/boot.img","boot")
E:Error in /sdcard/LeeDrOiD_HD_V2.0.0.zip
(Status 7)
Installation aborted.
I also kept getting the messages E:Can't mount CACHE:recovery/log & E:Can't open CACHE:recovery/log
I then tried to install the stock 1.32 RUU but that stuck at the Updating User Data stage at 40%.
I'm now stuck with the bootloader options and simply have a white screen with the below and warning triangles bottom left & right.
ACE PVT SHIP S-OFF
HBOOT-0.85.0007
MICROP-0438
RADIO-26.04.02.17_M2
eMMC-BOOT
Oct 11 2010, 12:47:02
RUU (This is highlighted yellow)
I have tried ADB but the device isn't shown as attached. However, Fastboot shows it attached but I've had no success pushing the ROM this way either. Below is copy of the cmd window:
C:\AndroidSDK\tools>fastboot boot PD98IMG.zip
creating boot image...
creating boot image - 301006848 bytes
downloading 'boot.img'...
OKAY [ 47.302s]
booting...
FAILED (remote: not allowed)
finished. total time: 47.302s
Can anyone offer any assistance as I've run out of ideas and fear I've bricked it.
you cant just flash rom via ADB. you need recovery. Do you have clockwork mod recovery?
The message you get about being unable to write boot suggests you are no longer S-off, whilst bootloader suggests you have s-off, l would start from scratch and s-off again and then try reinstalling the rom
20mark said:
you cant just flash rom via ADB. you need recovery. Do you have clockwork mod recovery?
Click to expand...
Click to collapse
I used to but it's been wiped as part of the the failed RUU installation. Power On/Vol Down now does nothing
ghostofcain said:
The message you get about being unable to write boot suggests you are no longer S-off, whilst bootloader suggests you have s-off, l would start from scratch and s-off again and then try reinstalling the rom
Click to expand...
Click to collapse
Do you mean Eng or Radio off? Can I do that with no bootloader options or recovery?
How would you suggest installing the ROM and which one?
Thanks for any advice.
I've just tried jkolo's easy S-Off tool but I get an error message pop-up "Module or hboot fail. Aborting."
So what happenes when you choose the recovery option?
Oh and btw don't worry too much about the void warranty, I've read of a few people who've had to send phones back to HTC without being able to revert to stock first and they've been successful - obviously this is a last resort.
EmprtArea said:
So what happenes when you choose the recovery option?
Click to expand...
Click to collapse
I don't have a recovery option on the Phone.
So can you use fastboot to do this successfully?
fastboot erase recovery
fastboot flash recovery clockwork-recovery.img
If you need the image it here: http://mirror1.kanged.net/recoveries/recovery-clockwork-3.0.0.6-ace.img
EmprtArea said:
So can you use fastboot to do this successfully?
fastboot erase recovery
fastboot flash recovery clockwork-recovery.img
Click to expand...
Click to collapse
I haven't tried that yet but fear the 1st line may wipe my only way of communicating if the 2nd part doesn't work
well you say you haven't got the recovery option anyway, so you could leave that line out I only put it because that's what I'd do.
HOWEVER: I'm no expert.
Question after Re-reading your post: Are you worried you'll delete fastboot? I'm sure that's not what I'm suggesting. But as it's your £500 device wait for someone else to confirm.
EmprtArea said:
So can you use fastboot to do this successfully?
fastboot erase recovery
fastboot flash recovery clockwork-recovery.img
If you need the image it here: http://mirror1.kanged.net/recoveries/recovery-clockwork-3.0.0.6-ace.img
Click to expand...
Click to collapse
No luck
Code:
C:\AndroidSDK\tools>fastboot flash recovery recovery-clockwork-3.0.0.6-ace.img
sending 'recovery' (3334 KB)...
OKAY [ 0.560s]
writing 'recovery'...
FAILED (remote: not allowed)
finished. total time: 0.562s
Everytine you try writing it fails what else can you do?
Sent from my Desire HD using XDA App
I'd jump to thinking you're not ENG S-Off anymore (got to say probably the failed 1.32 flash that did it. And you can't use that tool so look for an alternative description of how to get there.
If you can't use ADB I don't know how to get there.
If somehow ADB does start working then the CyanogenMod wiki might be useful.
http://wiki.cyanogenmod.com/index.php?title=HTC_Desire_HD:_Full_Root_Guide
If you lost s-off while flashing the 1.32 rom then I also suspect you lost root.
Sent from my Desire HD using XDA App
I've got backups of:
hboot_original.bin & part7backup-1294609557.bin
Are they of any help?
I can't see any way to gain Eng-Off without root so I'm at a loss.
The frustrating thing is I don't know what happened in the 1st place that froze my phone and kicked all this off. I'm guessing I have a hardware fault of some sort
Would T-Mobile exchange or repair under warranty, despite the mods I'd made?
Aamir.Badat said:
If you lost s-off while flashing the 1.32 rom then I also suspect you lost root.
Sent from my Desire HD using XDA App
Click to expand...
Click to collapse
I'm starting to regret trying that as a solution now
I remembered something similar being posted on these forums a few months ago, so I had a search and found this thread:
http://forum.xda-developers.com/showthread.php?p=9139950
I'm not an expert on these things, so I don't know if this would work for you. I would suggest waiting for someone with a bit more experience than me to join the discussion, as I don't know how similar your circumstances are to the ones in that thread. Do you get any error messages on your PC when you run the RUU? I take it that it finds your phone, whereas in the thread above the RUU wasn't seeing the phone.
However I thought reading that might give you some hope. Worth reading the thread all the way through.
I think what disabled most of your options was flashing a stock ruu. It overwrites hboot and the recovery.
Edit: since the ruus fail installing, maybe someting is off with your device, NAND error or someting.
this sort of thing doesnt happen if you are flashing custom roms though right? its making me nervous now!
preacher65 said:
I remembered something similar being posted on these forums a few months ago, so I had a search and found this thread:
http://forum.xda-developers.com/showthread.php?p=9139950
I'm not an expert on these things, so I don't know if this would work for you. I would suggest waiting for someone with a bit more experience than me to join the discussion, as I don't know how similar your circumstances are to the ones in that thread. Do you get any error messages on your PC when you run the RUU? I take it that it finds your phone, whereas in the thread above the RUU wasn't seeing the phone.
However I thought reading that might give you some hope. Worth reading the thread all the way through.
Click to expand...
Click to collapse
Thanks for the tip. I'll have a read and may give that a go.
KamikaZeeFu said:
I think what disabled most of your options was flashing a stock ruu. It overwrites hboot and the recovery.
Edit: since the ruus fail installing, maybe someting is off with your device, NAND error or someting.
Click to expand...
Click to collapse
I don't get errors, the RUU just freezes and I have to pull the plug.
danrobz said:
this sort of thing doesnt happen if you are flashing custom roms though right? its making me nervous now!
Click to expand...
Click to collapse
The errors started when I was on a Custom ROM but my suspicion is that it's a hardware fault to blame. If I can't fix this then whilst the custom ROM probably didn't cause the damage, the general unlocking etc may have voided my warranty.
I hate to do this but I this is my last resort to getting my phone back working. I currently can not get pass splash screen. Phone was already rooted running cm7 and I wanted to go back to one of my old nandroid so I flashed CW 2.5.1.2. It was working fine but was running slow so I did a data format and wipe cache and ever since then it will not boot up. I am getting a E:Cant' mount CACHE:recovery/command and log message when recovery loads up.
I can get into fastboot and recovery fine but I cant seem to flash any of my nandroids anymore. I have about 5 of them and none work. I can't flash any roms either. It seems as if my root may be gone because when Im in adb shell and run su it does not give me root and I cannot mount any systems in recovery. I tried everything from trying to flash to stock through hboot and even flashing new recovery in fastboot but that did not work since I do not have ENG HBOOT. Tried rerooting and unrooting it again but I always have to go into that /data/local but I am never able to gain access. I do still have S-OFF but that seems to be about it. Oh yeah and I cant even do a wipe data/factory reset. Says E:format_root device: can't find mmc partition.
So if someone knows anything else I could try to get this resolve that would be cool.
Ok lets start don't panic all is not lost yet you can still have root with S-OFF and have access fastboot and recovery. I am not sure why you reverted back to older CWMR2.5.1.2 as if you had CWMR3.0.0.6 you could have done it without fastboot but makes no diff now.
First go try "fastboot erase system -w" and then boot in to recovery and do full factory wipe and then flash as you normally would do.
BlackSHELF said:
Ok lets start don't panic all is not lost yet you can still have root with S-OFF and have access fastboot and recovery. I am not sure why you reverted back to older CWMR2.5.1.2 as if you had CWMR3.0.0.6 you could have done it without fastboot but makes no diff now.
First go try "fastboot erase system -w" and then boot in to recovery and do full factory wipe and then flash as you normally would do.
Click to expand...
Click to collapse
I reverted back to that one thinking that it would enable me to flash a none cm7 rom.
Here is what I got. From my understanding I am getting this because I do not have ENG HBOOT but please correct me if Im wrong
C:\android-sdk-windows\tools>fastboot erase system -w
erasing 'system'...
FAILED (remote: not allowed)
finished. total time: 0.020s
Hmmm I just reread your OP and you saying you somehow lost root trying to unroot and reroot, so I am not sure about the current status.
NOMRAL CASE:
http://forum.xda-developers.com/attachment.php?attachmentid=516463&d=1297577207
^ download that and unzip it and get the recovery.img for 3.0.0.6 and try "fastboot flash recovery recovery.img" as that would do if not try the below.
EXTREME CASE:
http://www.filefactory.com/file/caa....140e_26.03.02.26_M_release_155771_signed.zip
File: PD15IMG_Glacier_TMOUS_1.17.531.2_Radio_12.28b.60.1 40e_26.03.02.26_M_release_155771_signed.zip
MD5: 49D07F0EE7DE1765A6A84CB12FA53110
Size: 312 MB
^ go download the file and then rename it from "PD15IMG_Glacier_TMOUS_1.17.531.2_Radio_12.28b.60. 140e_26.03.02.26_M_release_155771_signed.zip" to "PD15IMG.zip" (make sure its not PD15IMG.zip.zip) and put it in root of your SDCard. Go in to bootloader and follow the instructions. This will get you to stock rom/radio from there you can redo all your stuff.
BlackSHELF said:
Hmmm I just reread your OP and you saying you somehow lost root trying to unroot and reroot, so I am not sure about the current status.
NOMRAL CASE:
http://forum.xda-developers.com/attachment.php?attachmentid=516463&d=1297577207
^ download that and unzip it and get the recovery.img for 3.0.0.6 and try "fastboot flash recovery recovery.img" as that would do if not try the below.
EXTREME CASE:
http://www.filefactory.com/file/caa....140e_26.03.02.26_M_release_155771_signed.zip
File: PD15IMG_Glacier_TMOUS_1.17.531.2_Radio_12.28b.60.1 40e_26.03.02.26_M_release_155771_signed.zip
MD5: 49D07F0EE7DE1765A6A84CB12FA53110
Size: 312 MB
^ go download the file and then rename it from "PD15IMG_Glacier_TMOUS_1.17.531.2_Radio_12.28b.60. 140e_26.03.02.26_M_release_155771_signed.zip" to "PD15IMG.zip" (make sure its not PD15IMG.zip.zip) and put it in root of your SDCard. Go in to bootloader and follow the instructions. This will get you to stock rom/radio from there you can redo all your stuff.
Click to expand...
Click to collapse
C:\android-sdk-windows\tools>fastboot flash recovery recovery.img
sending 'recovery' (3426 KB)...
OKAY [ 1.159s]
writing 'recovery'...
FAILED (remote: not allowed)
finished. total time: 1.180s
The other file did not work either. It had "Fail-PU" for all the files it tried to flash
Did you try the PD15IMG.zip from bootloader? Download it make sure its not corrupted that is why I provided you with md5 hash to verify. Then put the file in root of your sdcard and then boot in to bootloader, it will scan it and follow the instruction to revert back to original.
BlackSHELF said:
Did you try the PD15IMG.zip from bootloader? Download it make sure its not corrupted that is why I provided you with md5 hash to verify. Then put the file in root of your sdcard and then boot in to bootloader, it will scan it and follow the instruction to revert back to original.
Click to expand...
Click to collapse
Yes I just verified it and it is not corrupt. Thats the way I did it and came up fail-pu
lilterro said:
Yes I just verified it and it is not corrupt. Thats the way I did it and came up fail-pu
Click to expand...
Click to collapse
Hmmm never seen or heard of that I am taking fail pu means failed partition update. What does your HBOOT ver say on the screen? I am not sure what happened but seems like it soft-brick ATM still not sure how you lost root. Hopefully someone who has little more knowledge can shed some light.
BlackSHELF said:
Hmmm never seen or heard of that I am taking fail pu means failed partition update. What does your HBOOT ver say on the screen? I am not sure what happened but seems like it soft-brick ATM still not sure how you lost root. Hopefully someone who has little more knowledge can shed some light.
Click to expand...
Click to collapse
Ok thanks anyway. I am normally able to wok my out of alot of these issues that come up with flashing but this one got me stumped to.
HBOOT-0.86.0000
perm-brick no fix
lilterro said:
Ok thanks anyway. I am normally able to wok my out of alot of these issues that come up with flashing but this one got me stumped to.
HBOOT-0.86.0000
Click to expand...
Click to collapse
I am having the very same problem i am very good at fixing my mistakes but this one is impossible i get that same fail-pu but only difference is mine is s-on and it was never rooted only temp-root i was trying to perm-root and that's when it crashed will not boot up any more and i can't boot into recovery because it never been rooted and i don't know how to do ( C:\android-sdk-windows\tools>fastboot flash recovery recovery.img ) looks like something for the pc and i tried factory reset it will just freeze with the 3 androids skating i go to fastboot and i see bootloader, reboot, reboot bootloader and power down but those did nothing i even offered $100 through paypal to the first person how fixes it but it's an impossible task so there is a full brick out there people say its not but i see different.
perm-brick no fix
Alright Ladies and Gentlemen.
Background: (skip if you don't think it's relevant)
I just bought a xt907 with the latest OTA.
I wanted root, however after looking into it, I read that the bootloader was forever locked from the new OTA.
But, me being as stubborn as I am, and always have had a rooted phone, I tried anyways, and with my surprise, somehow, I actually achieved root using motochopper after only clearing the dalvik cache and trying it for shiggles.
No backups.
Even though I couldn't flash a new recovery or a full rom without safestap, I just decided to mod the stock rom.
Installed pimp my rom, es file explorer, some app uninstallers for bloatware (no i didn't uninstall any COM files or important things), etc etc.
Then I Installed a font, didn't like it, went to try a few others.
NOW.
After installing a font and rebooting, I was stuck at the droid boot logo with the red eye and sparks flying about.
I booted into stock recovery, cleared the cache. Nothing. Reset to factory defaults. Nothing.
I was still stuck on the boot logo.
Now, the dumb part of my actions.
I downloaded matt's utility 1.20. I tried option 1, Which failed. So I tried option 2, flashing the recovery. Which was "successful".
Tried option 1 again, it keeps saying
Code:
sending 'system' (30720 KB)...
OKAY [ 2.318s]
writing 'system'...
OKAY [ 2.798s]
sending 'system' (30720 KB)...
OKAY [ 6.569s]
writing 'system'...
OKAY [ 1.358s]
Over and over again.
Now I can not boot the phone. AP Fastboot comes up.
Code:
AP Fastboot Flash Mode
(blah)
Device is LOCKED. Code 0.
No Valid PIV block in SP for system.
PIV validation failed (system)
Fastboot reason: Flash Failure
Same thing comes up when I try to go into recovery. Every time I turn on the phone, this comes up.
I tried RSD Lite, to flash the old rom back on, it keeps failing. I keep trying to flash VZW_XT907_4.1.2-9.8.1Q-66_1FF
With no avail.
So, Anyone who can help me, I would be forever grateful. Thanks.
cheno1115 said:
Alright Ladies and Gentlemen.
Background: (skip if you don't think it's relevant)
I just bought a xt907 with the latest OTA.
I wanted root, however after looking into it, I read that the bootloader was forever locked from the new OTA.
But, me being as stubborn as I am, and always have had a rooted phone, I tried anyways, and with my surprise, somehow, I actually achieved root using motochopper after only clearing the dalvik cache and trying it for shiggles.
No backups.
Even though I couldn't flash a new recovery or a full rom without safestap, I just decided to mod the stock rom.
Installed pimp my rom, es file explorer, some app uninstallers for bloatware (no i didn't uninstall any COM files or important things), etc etc.
Then I Installed a font, didn't like it, went to try a few others.
NOW.
After installing a font and rebooting, I was stuck at the droid boot logo with the red eye and sparks flying about.
I booted into stock recovery, cleared the cache. Nothing. Reset to factory defaults. Nothing.
I was still stuck on the boot logo.
Now, the dumb part of my actions.
I downloaded matt's utility 1.20. I tried option 1, Which failed. So I tried option 2, flashing the recovery. Which was "successful".
Tried option 1 again, it keeps saying
Code:
sending 'system' (30720 KB)...
OKAY [ 2.318s]
writing 'system'...
OKAY [ 2.798s]
sending 'system' (30720 KB)...
OKAY [ 6.569s]
writing 'system'...
OKAY [ 1.358s]
Over and over again.
Now I can not boot the phone. AP Fastboot comes up.
Code:
AP Fastboot Flash Mode
(blah)
Device is LOCKED. Code 0.
No Valid PIV block in SP for system.
PIV validation failed (system)
Fastboot reason: Flash Failure
Same thing comes up when I try to go into recovery. Every time I turn on the phone, this comes up.
I tried RSD Lite, to flash the old rom back on, it keeps failing. I keep trying to flash VZW_XT907_4.1.2-9.8.1Q-66_1FF
With no avail.
So, Anyone who can help me, I would be forever grateful. Thanks.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2379833
you have this as a sure thing.
I have wondered if my restore method would work on a locked BL phone. Scroll down to near the bottom and I comment on the possibility of getting custom recovery and then root? Impossible! But you are borked already..... My wife won't let me try it on her updated & locked M.
http://forum.xda-developers.com/showthread.php?t=2391641
aviwdoowks said:
http://forum.xda-developers.com/showthread.php?t=2379833
you have this as a sure thing.
I have wondered if my restore method would work on a locked BL phone. Scroll down to near the bottom and I comment on the possibility of getting custom recovery and then root? Impossible! But you are borked already..... My wife won't let me try it on her updated & locked M.
http://forum.xda-developers.com/showthread.php?t=2391641
Click to expand...
Click to collapse
I did try that and that is how I obtained root. Didn't have a problem up until now.
Anyways, I managed to fix my issue on my own.
Long story short, RSD Lite was flashing the VZW_XT907_4.1.2-9.8.1Q-66_1FF I downloaded from droid-developers.
My phone kept rejecting the tz.mbn saying it was invalid.
Sooooo, I searched for a 98.18.78 OTA pull and I found one.
This is the one for reference.
I swapped the tz.mbn files between the two folders and it flashed it without a problem. Phone booted up as if I just unboxed it.
So, I won't delete this just as a reference for anyone who has the same problems as me.
Sorry for taking anyone's time.
cheno1115 said:
....QUOTE]
I am curious, that link is the prev OTA.
Even then could you share how an ota useful in RSD?
"I swapped the tz.mbn files between the two folders and it flashed it without a problem. Phone booted up as if I just unboxed it."
You got the file from the old OTA?
Click to expand...
Click to collapse
aviwdoowks said:
cheno1115 said:
....QUOTE]
I am curious, that link is the prev OTA.
Even then could you share how an ota useful in RSD?
"I swapped the tz.mbn files between the two folders and it flashed it without a problem. Phone booted up as if I just unboxed it."
You got the file from the old OTA?
Click to expand...
Click to collapse
Yes, I just went in my phone settings and did realize this is a previous OTA. I checked for updates and my phone wants me to update to 98.18.78.
I am curious, that link is the prev OTA.
Even then could you share how an ota useful in RSD?
Click to expand...
Click to collapse
Well, Pretty much, my phone had no rom at the time. I ruined it by trying to flash stuff.
So I downloaded the bottom rom from
sbf.droid-developers.org/scorpion_mini_xt907/list.php
and was trying to flash it onto my phone. My phone kept rejecting the tz.mbn file, it said it was invalid. So I found that old OTA and swapped the two files, and to my surprise, my phone accepted that file. I don't know why it wouldn't take the original one.
Anyways, I'm updating my phone to OTA 98.18.78 right now, so all is good.
Click to expand...
Click to collapse
Samuri HL Downgrade Tool
cheno1115 said:
Alright Ladies and Gentlemen.
Background: (skip if you don't think it's relevant)
I just bought a xt907 with the latest OTA.
I wanted root, however after looking into it, I read that the bootloader was forever locked from the new OTA.
But, me being as stubborn as I am, and always have had a rooted phone, I tried anyways, and with my surprise, somehow, I actually achieved root using motochopper after only clearing the dalvik cache and trying it for shiggles.
No backups.
Even though I couldn't flash a new recovery or a full rom without safestap, I just decided to mod the stock rom.
Installed pimp my rom, es file explorer, some app uninstallers for bloatware (no i didn't uninstall any COM files or important things), etc etc.
Then I Installed a font, didn't like it, went to try a few others.
NOW.
After installing a font and rebooting, I was stuck at the droid boot logo with the red eye and sparks flying about.
I booted into stock recovery, cleared the cache. Nothing. Reset to factory defaults. Nothing.
I was still stuck on the boot logo.
Now, the dumb part of my actions.
I downloaded matt's utility 1.20. I tried option 1, Which failed. So I tried option 2, flashing the recovery. Which was "successful".
Tried option 1 again, it keeps saying
Code:
sending 'system' (30720 KB)...
OKAY [ 2.318s]
writing 'system'...
OKAY [ 2.798s]
sending 'system' (30720 KB)...
OKAY [ 6.569s]
writing 'system'...
OKAY [ 1.358s]
Over and over again.
Now I can not boot the phone. AP Fastboot comes up.
Code:
AP Fastboot Flash Mode
(blah)
Device is LOCKED. Code 0.
No Valid PIV block in SP for system.
PIV validation failed (system)
Fastboot reason: Flash Failure
Same thing comes up when I try to go into recovery. Every time I turn on the phone, this comes up.
I tried RSD Lite, to flash the old rom back on, it keeps failing. I keep trying to flash VZW_XT907_4.1.2-9.8.1Q-66_1FF
With no avail.
So, Anyone who can help me, I would be forever grateful. Thanks.
Click to expand...
Click to collapse
I lost root after the OTA update. Inused SamuriHL Downgrade tool to roll back to the stae my phone was in before update. then it gives instructions on how to retore and keep root. then yuo tkae the update again.
THANK YOU
I thought I was doomed to a bricked phone. This fix saved me.
Important to note for any other poor suckers who find themselves in the same spot - make sure you have an updated version of RSD Lite when you do this. My first (15) attempt(s) failed flashing system.img because I was running an old version of RSD Lite, but when I updated to 6.1.4 it worked fine.
cheno1115, THANK YOU!
I had the same issue with my xt907 after rooting with "DROID_RAZR_M_Utility_1.20" and after restoring my apps (including with framework mods.. stupid, I know) from xt890 via nandroid manager.
I thought oh my god, that is an expensive brick I have now.
I have just reflashed "VZW_XT907_4.1.2-9.8.1Q-66_1FF.xml.zip" via RSD (with "tz.mbn" file raplaced from "Blur_Version.98.16.1.XT907.Verizon.en.US.zip") and it did boot up, however it booted with all my "restored" apps. The problem is that I have tried to restore my home screen via nandroid backup manager and it failed, so I got only upper status bar, soft buttons and black screen... I'm lucky that Motorola placed a settings shortcut on upper drawer, so I was able to navigate to settings and do a factory reset. So this is how I got a fresh start again.
However if I launch "DROID_RAZR_M_Utility_1.20" with option 1 again, I get the same thing - many repeating "sending system.img", have to terminate it and then - a brick. So I had to repeat RSD reflash procedure once more. BTW flashing of "system.img" takes surprisingly long, like 5 minutes or so.
So that got me thinking... Isn't this repeating "sending system" and "writing system" just doing it in pieces and one should wait?
Anyway that has solved my problem. THANKS!
Does this mean you fully rooted your XT907 that had the latest OTA updates? Can you install other ROM's?
As far as I know, once you get the latest OTA update you're screwed and can't do anything.
I have a locked xt907
nifty101 said:
Does this mean you fully rooted your XT907 that had the latest OTA updates? Can you install other ROM's?
As far as I know, once you get the latest OTA update you're screwed and can't do anything.
I have a locked xt907
Click to expand...
Click to collapse
We have SafeRoot now. See the general section.
No custom roms though.
See my xt907 stuff
Can you send me a link to each the general section and your XT907 stuff? Not sure where or what you are referencing. Thanks so much.
nifty101 said:
Can you send me a link to each the general section and your XT907 stuff? Not sure where or what you are referencing. Thanks so much.
Click to expand...
Click to collapse
You are on tapatalk or xda app?
Go here & take your punishment. Lol.
http://forum.xda-developers.com/showthread.php?t=2610531
Links
http://forum.xda-developers.com/showpost.php?p=45548210&postcount=3
SamuriHL has fix for "cannot load system img"
http://www.droidrzr.com/index.php/topic/37658-green-robot-after-using-house-of-moto/#entry400767
No valid piv
Mr hello I have this problem with no valid PIV on my motorola RARZ M can you help me?
So i just saw the new Oxygen OS 3.1.0 is out in OTA form. Me being rooted i tried flashing it through twrp, which i had installed before. (i should also note that i had Xposed installed too, on Oxygen OS 3.0.2) now i think i might have gotten my zip file wrong and installed a previous version. The boot animation is the square, triangle and circle one. It just goes through my apps and tries to update them for eternity. When i try putting the device into recovery (power+vol down) it just freezes on the oneplus logo. I later discovered that i can use fastboot when in that mode. I tired flashing twrp but i couldnt boot into it. fastboot boot recovery.img didnt work either, giving me this:
downloading 'boot.img'...
OKAY [ 0.746s]
booting...
FAILED (remote: dtb not found)
finished. total time: 1.011s
Now i have no idea what to do. I'm sure I've made SOME kind of mistake along the way, but i cant find a way to fix this. I have a nandriod backup of just before flashing if that might help.
fastboot reboot-bootloader puts me in fastboot mode but it doesnt change anything.
also, ADB naturally wont detect the phone whatsoever.
Ill be very glad for any help! Thanks!
Are the drivers accurate? Does your PC recognize your device as it should in Device Manager? That's usually what I check first when I have fastboot errors. I think the only way to fix this is through fastboot... so I would focus on trying to get that to work first.
SynderBlack said:
So i just saw the new Oxygen OS 3.1.0 is out in OTA form. Me being rooted i tried flashing it through twrp, which i had installed before. (i should also note that i had Xposed installed too, on Oxygen OS 3.0.2) now i think i might have gotten my zip file wrong and installed a previous version. The boot animation is the square, triangle and circle one. It just goes through my apps and tries to update them for eternity. When i try putting the device into recovery (power+vol down) it just freezes on the oneplus logo. I later discovered that i can use fastboot when in that mode. I tired flashing twrp but i couldnt boot into it. fastboot boot recovery.img didnt work either, giving me this:
downloading 'boot.img'...
OKAY [ 0.746s]
booting...
FAILED (remote: dtb not found)
finished. total time: 1.011s
Now i have no idea what to do. I'm sure I've made SOME kind of mistake along the way, but i cant find a way to fix this. I have a nandriod backup of just before flashing if that might help.
fastboot reboot-bootloader puts me in fastboot mode but it doesnt change anything.
also, ADB naturally wont detect the phone whatsoever.
Ill be very glad for any help! Thanks!
Click to expand...
Click to collapse
**** man. I'm in the same boat as of a few hours ago. I was having a ProxyController wakelock and the few Google results I saw told me I should reflash the modem. I accidentally flashed the old modem (OOS2, I believe). I can't boot into my rom OR TWRP. BUT fastboot does work. I also get the "remote: dtb not found" error when trying to boot from the recovery image.
As long as we have fastboot, we can always go back to OOS 3 using the various unbrick methods. I'm trying to avoid having to go through that whole mess of re-rooting/unlock the bootloader etc etc. I'll post on here if I'm successful.
Update: I NEED a functional phone so I just went and erased everything. Sorry I couldn't be of much help to you man. What I did:
I went here and downloaded the fastboot version of OOS3 and converted the bat scripts into bash scripts (I only have Linux computers near me right now...; the commands in that bat script are exactly the same as they would be in bash, I just had to rename the ".bat" to ".sh" and make it executable). I'm back in OOS 3 now, unfortunately. There IS a way mentioned on the page below that talks about how you can prevent userdata from being formatted, but I didn't really care too much. Hope that helps.
http://forum.xda-developers.com/oneplus-2/general/rom-mirrors-official-oxygen-os-roms-ota-t3209863
I've gotten myself into a bit of a pickle. I just got my Nothing Phone yesterday, and I've already managed to get it stuck in a boot loop. I am still able to access fastboot and my computer still recognises it, so i hope it is still salvageable.
It all started when I stumbled upon this guide, which promised that unlocking and rooting it would be done in minutes. I know next to nothing about rooting phones, but the guide made it seem fairly straightforward. So I gave it a go. Big mistake.
Here's exactly what's happened:
I followed the guide step by step.
At step 2.2 I downloaded the full 1.1.7 (EEA) package from here. Then I extracted the boot image from the downloaded zip by following this guide (still following the main guide).
Flashing it went fine, no errors, but after trying to start it, it just shows the logo for a few seconds and then restarts.
A bunch of googling later, I stumbled upon an xda thread where someone had linked to a website with pre-built images. I tried flashing some of those too, no luck.
Last thing I tried was flashing the "v1.5.3 Fastboot ROM" from that site, but I didn't get far with that at all. It contains a .bat file, but i'm on mac, so tried running the commands one by one. First step was "fastboot set_active b" and that succeeded, but after that it fails with the flashing; "Flashing is not allowed for Critical Partitions". I'm afraid to continue at this point.
If possible I would still like to continue with rooting it, but if it is easier to go back to factory without root I am ok with that too at this point. Can someone please help?
Did you try this? https://forum.xda-developers.com/t/how-to-unbrick-nothing-phone-1-fastboot-bootloop.4501439/
@itsTarec oh god, i think that might just have worked! It does boot now, and i'm going through the setup process. BUT, a few things failed during the flash process:
Code:
(not in order)
Resizing 'system_a' FAILED (remote: 'Not enough space to resize partition')
Writing 'odm_b' FAILED (remote: 'No such file or directory')
Writing 'product_b' FAILED (remote: 'No such file or directory')
Writing 'system_b' FAILED (remote: 'No such file or directory')
Writing 'system_ext_b' FAILED (remote: 'No such file or directory')
Writing 'vendor_b' FAILED (remote: 'No such file or directory')
Should i be worried?
nike1 said:
@itsTarec oh god, i think that might just have worked! It does boot now, and i'm going through the setup process. BUT, a few things failed during the flash process:
Code:
(not in order)
Resizing 'system_a' FAILED (remote: 'Not enough space to resize partition')
Writing 'odm_b' FAILED (remote: 'No such file or directory')
Writing 'product_b' FAILED (remote: 'No such file or directory')
Writing 'system_b' FAILED (remote: 'No such file or directory')
Writing 'system_ext_b' FAILED (remote: 'No such file or directory')
Writing 'vendor_b' FAILED (remote: 'No such file or directory')
Should i be worried?
Click to expand...
Click to collapse
Sorry mate, I have no idea. Keep looking for a solution... I was thinking about rooting my NP1 either but after seeing your thread I'm reluctant
itsTarec said:
Sorry mate, I have no idea. Keep looking for a solution... I was thinking about rooting my NP1 either but after seeing your thread I'm reluctant
Click to expand...
Click to collapse
Yeah, can't recommend it unless you really know what you're doing. It seems to be alright now though, thankfully
nike1 said:
Yeah, can't recommend it unless you really know what you're doing. It seems to be alright now though, thankfully
Click to expand...
Click to collapse
Is your device rooted now? Or did you just fixed the issue?
nike1 said:
I've gotten myself into a bit of a pickle. I just got my Nothing Phone yesterday, and I've already managed to get it stuck in a boot loop. I am still able to access fastboot and my computer still recognises it, so i hope it is still salvageable.
It all started when I stumbled upon this guide, which promised that unlocking and rooting it would be done in minutes. I know next to nothing about rooting phones, but the guide made it seem fairly straightforward. So I gave it a go. Big mistake.
Here's exactly what's happened:
I followed the guide step by step.
At step 2.2 I downloaded the full 1.1.7 (EEA) package from here. Then I extracted the boot image from the downloaded zip by following this guide (still following the main guide).
Flashing it went fine, no errors, but after trying to start it, it just shows the logo for a few seconds and then restarts.
A bunch of googling later, I stumbled upon an xda thread where someone had linked to a website with pre-built images. I tried flashing some of those too, no luck.
Last thing I tried was flashing the "v1.5.3 Fastboot ROM" from that site, but I didn't get far with that at all. It contains a .bat file, but i'm on mac, so tried running the commands one by one. First step was "fastboot set_active b" and that succeeded, but after that it fails with the flashing; "Flashing is not allowed for Critical Partitions". I'm afraid to continue at this point.
If possible I would still like to continue with rooting it, but if it is easier to go back to factory without root I am ok with that too at this point. Can someone please help?
Click to expand...
Click to collapse
When you want to root it is fairly simple, but you need to patch the EXACT boot.img file that your current firmware has. For example, you cannot patch the 1.1.7 boot.img and flash it when you have installed the 1.5.3 firmware.
And for root you need to patch the boot.img with the Magisk app, not just flash it.
lucy1983 said:
When you want to root it is fairly simple, but you need to patch the EXACT boot.img file that your current firmware has. For example, you cannot patch the 1.1.7 boot.img and flash it when you have installed the 1.5.3 firmware.
And for root you need to patch the boot.img with the Magisk app, not just flash it.
Click to expand...
Click to collapse
Aha, I see. That wasn't clear to me. I thought i needed a full package and not just an incremental one, that's why I went for 1.1.7. I did patch it with Magisk though, just the wrong version i guess. But all is well now, the phone's fully working afaict. Thank you for clarifying what went wrong!