I bricked my U.S. market ZL550 Zenfone 2. My bad, I spent the last two weeks desperately trying everything I could think of to get Link2SD to mount an Ext2 or 4 partition on my SDXC card, and I wasn't at all surprised when it hung on the Asus logo while booting on Saturday.
Anyway, I can't get it to boot normally again. Using fastboot, I flashed recovery, boot and droidboot from the latest Asus ROM, Z008-WW-2.18.40.7, but when I try to flash the system image zip, I get a bunch of errors and a "fail" message on the phone.
I tried sideloading the image with adb but adb won't connect to the phone in recovery mode. Also tried copying the image zip to the SD Card but that wouldn't load, it would only look for MOFD_SDUPDATE.ZIP.
I can return it, I'm not exactly thrilled with it anyway. Anyone have any ideas of what I might try before sending it back?
Thanks! Carl
ConnCarl said:
I bricked my U.S. market ZL551 Zenfone 2. My bad, I spent the last two weeks desperately trying everything I could think of to get Link2SD to mount an Ext2 or 4 partition on my SDXC card, and I wasn't at all surprised when it hung on the Asus logo while booting on Saturday.
Anyway, I can't get it to boot normally again. Using fastboot, I flashed recovery, boot and droidboot from the latest Asus ROM, Z008-WW-2.18.40.7, but when I try to flash the system image zip, I get a bunch of errors and a "fail" message on the phone.
I tried sideloading the image with adb but adb won't connect to the phone in recovery mode. Also tried copying the image zip to the SD Card but that wouldn't load, it would only look for MOFD_SDUPDATE.ZIP.
I can return it, I'm not exactly thrilled with it anyway. Anyone have any ideas of what I might try before sending it back?
Thanks! Carl
Click to expand...
Click to collapse
I'm surprised!! Why do you need link2sd??? with 32 GB Internal, I have 118 Apps installed along with movies and music. Still I have space( I have not used SD Card).
Anyways,
From what you mentioned, you seem to have a ZE551ML. And you Installed Z008-WW-2.18.40.7. It should be Z00A and not Z008. Please download the correct firmware and try out.:good:
Thumb-rule,
ZE550ML = Z008
ZE551ML = Z00A
I guess thats what you did Wrong
Thanks for pointing that out! It's actually a 16GB 550.
I'd go and connect it to pc on fastboot and wipe everything via command. Ex. Fastboot erase system, data, cache. Then flash a stock Rom from Asus via adb sideload
ConnCarl said:
Thanks for pointing that out! It's actually a 16GB 550.
Click to expand...
Click to collapse
for MOFD_SDUPDATE.zip to work, you need to place it on the external sd card and reboot into recovery. It will automatically start to install.
Placing it on the Internal card wont help.
---------- Post added at 08:58 AM ---------- Previous post was at 08:57 AM ----------
lordpipa said:
I'd go and connect it to pc on fastboot and wipe everything via command. Ex. Fastboot erase system, data, cache. Then flash a stock Rom from Asus via adb sideload
Click to expand...
Click to collapse
I wouldnt recommend that.
He is unable to use adb properly. And if he messes up something, he might even lose his warranty
lordpipa said:
I'd go and connect it to pc on fastboot and wipe everything via command. Ex. Fastboot erase system, data, cache. Then flash a stock Rom from Asus via adb sideload
Click to expand...
Click to collapse
Tried all that. Many times.
ConnCarl said:
Tried all that. Many times.
Click to expand...
Click to collapse
When i restored from stock via ADB, I was going from a preroot, bricked, because I updated and was getting the little error bot.. After i sideload the image, i still had to factory reset. I'm just guessing, but you did try and do the factory reset after fastboot/ADB.
godgib said:
When i restored from stock via ADB, I was going from a preroot, bricked, because I updated and was getting the little error bot.. After i sideload the image, i still had to factory reset. I'm just guessing, but you did try and do the factory reset after fastboot/ADB.
Click to expand...
Click to collapse
I can't sideload the image, because I can't connect with ADB.
ConnCarl said:
I can't sideload the image, because I can't connect with ADB.
Click to expand...
Click to collapse
but you can get into recovery, it's just when you click on "ADB update" your computer doesn't see the phone, that's my understanding...
Right, correct. I can get into recovery, and fastboot works, but not ADB.
ConnCarl said:
Right, correct. I can get into recovery, and fastboot works, but not ADB.
Click to expand...
Click to collapse
It sounds like you still in fastboot and not recovery. This is what recovery looks like and then you put in it "Apply update ADB sideload."
{
"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"
}
Yep, that is exactly what it looks like. But when I try to sideload, it times out. ADB won't see the phone.
ConnCarl said:
Yep, that is exactly what it looks like. But when I try to sideload, it times out. ADB won't see the phone.
Click to expand...
Click to collapse
I'm pretty sure if it timse out using ADB sideload then it should also timeout when you type ADB deviecs, but try it you should see your serial number sideload.... If you don't then
1. Make sure you have ADB 1.42 with intel drives 1.9
2. Use the stock cable.
3. In device manager make sure there's no unknown Android devices.
4. if ADB still doesn't work then try and flash via fast boot a new boot.img and recovery.img.
5. If you do get to the point where you can sideload...
6. Downloaded the ASUS firmware with WW not CN.
7. Also make sure the firmware package doesn't have ext .zip.zip, because of unknown file ext in windows.
Not sure if this works but you can give it a try.
Have you boot it with Temp CWM?
Delete all cache, including those of under advanced section
install zip file should work to install your full rom. since you stated you cant adb to detect.
Thanks everyone for all the suggestions!
I was just sort of reviewing godgib's screen grab when it slowly dawned on me that at least part of the solution had been staring me in the face all along.
It had never occurred to me that adb might not be able to connect even though fastboot could. Then when I read "you need adb 1.0.32 or newer to sideload to this device", it started to make sense. I upgraded adb and connected but still couldn't sideload. After reviewing godgib's methodical list, I realized it was a driver problem. Once I squared that away, sideload went without a hitch.
Interesting side note...I don't know what build I had originally, but it had to be at least a month old or so. I figured I might as well get the latest release, so I went with Z008_WW_2.18.40.7, and I updated boot/droidboot/recovery while I was at it. The funny thing was that when it booted, it was set for 250 dpi and everything was tiny.
Luckily, since adb was finally working (thanks again godgib) I was able to send "adb shell wm density 480" to put it back to normal.
Thanks again, everyone!
Carl
Glad you got it working...
Sent from my ASUS_Z00AD using XDA Free mobile app
godgib said:
Glad you got it working...
Sent from my ASUS_Z00AD using XDA Free mobile app
Click to expand...
Click to collapse
Appreciate that.
Of course now auto-rotate is borked. I'll have to either wait for a patch or downgrade.
Did you ever figure out the sdcard problem? I just got the same card and want to do the same thing. But the phone wont see the second partition at all.
i have similar problem too
Related
So heres the deal, I formated my SD card, so now, there is nothing on the ouya... I still have recovery, but I don't see the big exclamation point and the ouya lettering, wich I trully belive that my litle box is bricked.
My ouya doesn't appear in device manager, nor does it work with adb...
My question is, is there a way to install OTA and/or Custom Roms via OTG?
Thank you. and please help me!
New developments...
My device manager detects an unknown device, however, when I try to install the drivers it won't let me, says that the device could harm my PC.
Il_Padrino said:
So heres the deal, I formated my SD card, so now, there is nothing on the ouya... I still have recovery, but I don't see the big exclamation point and the ouya lettering, wich I trully belive that my litle box is bricked.
My ouya doesn't appear in device manager, nor does it work with adb...
My question is, is there a way to install OTA and/or Custom Roms via OTG?
Thank you. and please help me!
Click to expand...
Click to collapse
Hi,
In al my desperation i also formatted my SD. When the Ouya booted i had nothing more than a black screen.
I rebooted into recovery .. sideloaded the latest OTA and this worked for me (after that i installed the stock plus rom)
But my point of view is "when the device is still being detected by a computer, its possible to recover )
Greetz
I did the same, to be clear: i did wipe data and dalvik to flash a ROM and when y tried to flash i got an error. I dont know how but i missclicked on a keyboard test and dont know how to get out so i had to reboot. The result is a black screen and the device detected as MTP device...
Im trying to get on recovery with the keyboard but it dsnt works :/
tupie said:
I did the same, to be clear: i did wipe data and dalvik to flash a ROM and when y tried to flash i got an error. I dont know how but i missclicked on a keyboard test and dont know how to get out so i had to reboot. The result is a black screen and the device detected as MTP device...
Im trying to get on recovery with the keyboard but it dsnt works :/
Click to expand...
Click to collapse
lel, everytime ill visit a thread to help somebody, their problem seems to be directly releated to the one i had a few days ago.
try to list the device via adb, if it doesnt show up, click this link and scroll down to my second post, it seems recovery, fastboot, and normal operation have 3 different hardware id's.
OPTIONAL
ArdDarvis also pointed out that you can add the id instead of replacing it, just seperate them with a comma like this:
Code:
;OUYA Console
%SingleAdbInterface% = USB_Install, USB\VID_2836&PID_0010
%CompositeAdbInterface% = USB_Install, USB\VID_2836&PID_0010, USB\VID_18D1&PID_D001
report back and let us know if it worked.
iAmSmokey said:
lel, everytime ill visit a thread to help somebody, their problem seems to be directly releated to the one i had a few days ago.
try to list the device via adb, if it doesnt show up, click this link and scroll down to my second post, it seems recovery, fastboot, and normal operation have 3 different hardware id's.
OPTIONAL
ArdDarvis also pointed out that you can add the id instead of replacing it, just seperate them with a comma like this:
Code:
;OUYA Console
%SingleAdbInterface% = USB_Install, USB\VID_2836&PID_0010
%CompositeAdbInterface% = USB_Install, USB\VID_2836&PID_0010, USB\VID_18D1&PID_D001
report back and let us know if it worked.
Click to expand...
Click to collapse
Tnx for the help but my problem wasnt like your. I just wiped my data partition. I finally fixed it using the alt+i+imprscrn keys to get on CWM and restoring from backup.
Tnx a lot anyway dude
I went ahed and installed the drivers anyway, and I got a "google device" and not OUYA, my box isn't detected when I try to sideload OTA!
my device manager shows this...
{
"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 need help, please...
That may still work like that. My OUYA is detected by Windows 7 home premium 64bit very similarly and I was able to access it using the one click test version.
Go ahead and try to get on to recovery
Sent from my SCH-I535 using Tapatalk 4 Beta
Il_Padrino have you tried reinstalling the driver? also the image is a little small :S
iAmSmokey said:
Il_Padrino have you tried reinstalling the driver? also the image is a little small :S
Click to expand...
Click to collapse
I did. says it's a generic google device, doesn't recognizes being an ouya...
Il_Padrino said:
I did. says it's a generic google device, doesn't recognizes being an ouya...
Click to expand...
Click to collapse
It shouldn't matter. You just need to connect via adb, have you tried to list adb devices from the command prompt?
As I said, that is how my computer lists it and I was able to root it using the test version of the tool kit.
Sent from my SCH-I535 using Tapatalk 4 Beta
TadeoNYC said:
It shouldn't matter. You just need to connect via adb, have you tried to list adb devices from the command prompt?
As I said, that is how my computer lists it and I was able to root it using the test version of the tool kit.
Sent from my SCH-I535 using Tapatalk 4 Beta
Click to expand...
Click to collapse
my device is listed and connect, however, when I try to sideload the OTA it gives me it shows E:Error in /tmp/update.zip
(Status 7)
Installation aborted.
I tried installing CWM again, and even pushing the boot.img into ouya, but when I go and change the drivers from adb to bootloader the ouya restarts and the alt+prt sc+I method doesn't work...
Just came to realize that all the directories in my memory are gone I tought that it was like the phones, that if you formated the SD Card it would be rebuilt with the standard directories,
Is there any way to create directories trough adb?
Can anyone send me a backup of their system?
or
Do I have a brick?
Il_Padrino said:
my device is listed and connect, however, when I try to sideload the OTA it gives me it shows E:Error in /tmp/update.zip
(Status 7)
Installation aborted.
I tried installing CWM again, and even pushing the boot.img into ouya, but when I go and change the drivers from adb to bootloader the ouya restarts and the alt+prt sc+I method doesn't work...
Just came to realize that all the directories in my memory are gone I tought that it was like the phones, that if you formated the SD Card it would be rebuilt with the standard directories,
Is there any way to create directories trough adb?
Can anyone send me a backup of their system?
or
Do I have a brick?
Click to expand...
Click to collapse
nothing is bricked as long as you still have a recovery installed.
either CWM or Stock, download this: http://devs-ouya-tv-prod.s3.amazonaws.com/ota/RC-OUYA-1.0.356-r1_ota.zip
1.) Then bring your Ouya into recovery, turn it on and hold alt+prt sc+I several times until the Ouya Logo and a exclamation mark shows up, then press HOME.
2.) Do a factory reset
3.) navigate to apply update from ADB, plug your Ouya into USB and use "ADB sideload RC-OUYA-1.0.356-r1_ota.zip"
4.) after a reboot your Ouya should work again.
If you had CWM and applying the OTA update bricked your Ouya, repeat these steps with the Stock recovery, if it didn't flash the stock recovery, try looking for the stock recovery that you can flash with CWM.
This was the case for me, flashing the OTA update with CWM bricked it, but it was fine after I flashed with stock.
My drama is over...
I come to accept it. My OUYA is 100% bricked has I lost recovery from my litle box...
It was fun, but now is over.
:crying:
So I recently flashed a self made ROM for my watch and it totally bricked it, it cannot boot into a system (just bootloops), Cannot access recovery mode (just turns off and bootloops) and last but not least PC Companion will not detect it. All I have now is fastboot mode so if someone can please help me flash each partition via fastboot that would amazing. I do how ever all of the correct drivers so I am guessing that it will not detect is due to the fact my device has no build.prop.
I really DON'T want to call sony support unless I really have to, so any help would be beyond amazing.
Screenshot from PC Companion:
{
"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"
}
If you need ANYTHING, Video's Pictures, etc feel free to ask as I will try my best to help.
Grab the stock recovery (or the version of twrp) which is appropriate for your build.
Put the watch in fastboot and on your computer in a terminal window type
Code:
fastboot boot <recovery.img>
Then in recovery, install the Os you want.
You have two options. Use stock recovery and then factory reset. Or, use twrp and go all the way back to the 5.0.1 image. If nothing else works. The later will. Do not forget to factory reset after you roll back.
lekofraggle said:
Grab the stock recovery (or the version of twrp) which is appropriate for your build.
Put the watch in fastboot and on your computer in a terminal window type
Code:
fastboot boot <recovery.img>
Then in recovery, install the Os you want.
You have two options. Use stock recovery and then factory reset. Or, use twrp and go all the way back to the 5.0.1 image. If nothing else works. The later will. Do not forget to factory reset after you roll back.
Click to expand...
Click to collapse
Tried it, just reboots
Then you are using the wrong recovery. What did you build?
lekofraggle said:
Then you are using the wrong recovery. What did you build?
Click to expand...
Click to collapse
Well I think what happened is all of the partitions got messed up, does this watch use system.img? Because then I could flash that through FASTBOOT
UPDATE: I got twrp to boot but... It cannot mount any partitions
1619415 said:
Well I think what happened is all of the partitions got messed up, does this watch use system.img? Because then I could flash that through FASTBOOT
UPDATE: I got twrp to boot but... It cannot mount any partitions
Click to expand...
Click to collapse
The closest thing I have seen to a system.img is the roll back zip file of 5.0.1 in this thread
http://forum.xda-developers.com/smartwatch-3/general/guide-roll-watch-to-previous-software-t3176801
I also can't access my SDCard/Internal Storage
UPDATE: I just think I have no OS installed, nothing installed at all actually. So I think I just need to reinstall system and other important data
Okay so that is my guide. Use the 5.0.1 image. I think the issue is precisely that you have no system. A normal flash does not usually touch the boot loader or partition map. So, do not jump to that conclusion yet. If twrp does not work for you, try using the fast boot flash of the 5.0.1 Recovery image.
Which version of twrp worked for you?
lekofraggle said:
Okay so that is my guide. Use the 5.0.1 image. I think the issue is precisely that you have no system. A normal flash does not usually touch the boot loader or partition map. So, do not jump to that conclusion yet. If twrp does not work for you, try using the fast boot flash of the 5.0.1 Recovery image.
Which version of twrp worked for you?
Click to expand...
Click to collapse
The 5.0.1 twrp would not boot but, the 5.1.1 one does just does not mount anything and the stock recovery does not boot either. I did however try to adb sideload stuff but could not find a system.img.
So, what you should try to do is adb push the 5.01 file while booted in the 5.1.1 twrp.
Did you try the 5.1.1 stock recovery? I am not sure it will help even if you get it to boot.
lekofraggle said:
So, what you should try to do is adb push the 5.01 file while booted in the 5.1.1 twrp.
Did you try the 5.1.1 stock recovery? I am not sure it will help even if you get it to boot.
Click to expand...
Click to collapse
I already tried twrp, it can't mount any partitions
Did you try pushing from the computer?
Code:
adb push <originalsystem.zip> /sdcard
If so, what was the exact error you received?
lekofraggle said:
Did you try pushing from the computer?
Code:
adb push <originalsystem.zip> /sdcard
If so, what was the exact error you received?
Click to expand...
Click to collapse
Twrp can't mount anything at all, im guessing that it cannot create a folder on my internal storage. Adb sideload wont work either because it cannot mount
Again, what is the specific error you receive trying adb push (not sideload) after you boot to the somewhat working twrp?
lekofraggle said:
Again, what is the specific error you receive trying adb push (not sideload) after you boot to the somewhat working twrp?
Click to expand...
Click to collapse
error: device not found
Okay, so try adb devices and see if it shows up. If it does, you are correct and need to repartition. That is neither easy nor unrisky. It is easy to brick your device.
If it does not show up, you need to install the drivers. Twrp uses different adb drivers than the watch Os for some reason.
I think this is my main problem...
@lekofraggle
Potentially. What happened when you ran adb devices? You need to do that on your computer.
---------- Post added at 10:16 PM ---------- Previous post was at 10:15 PM ----------
Adb has different permissions than twrp.
Do a format of the system, recovery, userdata and then reinstall from a custom rom online
****************
* SENT FROM *
* A *
* MOD KING *
* DEVICE *
****************
lekofraggle said:
Potentially. What happened when you ran adb devices? You need to do that on your computer.
---------- Post added at 10:16 PM ---------- Previous post was at 10:15 PM ----------
Adb has different permissions than twrp.
Click to expand...
Click to collapse
Either it does not show up or... it just says "error: device not found"
Hi guys
Well I guess I ruined my phone , I rooted my honor 7x BND-L21 a couple weeks ago and it worked after I rooted it everything was fine and normal till I was stupid enough and went into the super su app and I saw the full uninstall super su so I was even more stupid to press it and thinking that I’m gonna be free from the root and I won’t have to be afraid that it getting wrecked which I did it with my own hands after I pressed the uninstall super su the phone went black and won’t reboot anymore so I linked the phone to my laptop and went into my internal storage I didn’t find anything but the TWRP file which means there are no more system or systems files what so ever that’s my sad story I hope that any one of you can help me and make a backup to there phone like mine and take the time to help me install it because I don’t know anything about these stuff and I’ll be great full for you guys for the rest of my life
Again My phone is a : honor 7x BND-L21
ayadmanhal said:
Hi guys
Well I guess I ruined my phone , I rooted my honor 7x BND-L21 a couple weeks ago and it worked after I rooted it everything was fine and normal till I was stupid enough and went into the super su app and I saw the full uninstall super su so I was even more stupid to press it and thinking that I’m gonna be free from the root and I won’t have to be afraid that it getting wrecked which I did it with my own hands after I pressed the uninstall super su the phone went black and won’t reboot anymore so I linked the phone to my laptop and went into my internal storage I didn’t find anything but the TWRP file which means there are no more system or systems files what so ever that’s my sad story I hope that any one of you can help me and make a backup to there phone like mine and take the time to help me install it because I don’t know anything about these stuff and I’ll be great full for you guys for the rest of my life
Again My phone is a : honor 7x BND-L21
Click to expand...
Click to collapse
There is , at this time, no suggestion for you to fix.
Because, you do not tell enough of what you were doing, or did.
I mean. First superSU does not work on updated device(Oreo) . So must be nougat, but you did not say.
Next , removeing superSU , from inside of it's settings, will not erase system.
Your description of connecting to PC with USB and not able to see any system files. Well you cannot see Android system files in this way anyhow. Add to that USB (mtp) does not wokif there is no system I place to run the adb/mtp service.
Well if you mean you uninstalled root/superSU , then tried to restart, and that made the black screen, well this is different completely to what you asked. And this makes sense.
If this is what you need. You just need boot.img, if you were in fact on nougat. Or ramdisk.img, and/or kernel.kmg if it was Oreo.
For l21, I do not have these.
mrmazak said:
There is , at this time, no suggestion for you to fix.
Because, you do not tell enough of what you were doing, or did.
I mean. First superSU does not work on updated device(Oreo) . So must be nougat, but you did not say.
Next , removeing superSU , from inside of it's settings, will not erase system.
Your description of connecting to PC with USB and not able to see any system files. Well you cannot see Android system files in this way anyhow. Add to that USB (mtp) does not wokif there is no system I place to run the adb/mtp service.
Well if you mean you uninstalled root/superSU , then tried to restart, and that made the black screen, well this is different completely to what you asked. And this makes sense.
If this is what you need. You just need boot.img, if you were in fact on nougat. Or ramdisk.img, and/or kernel.kmg if it was Oreo.
For l21, I do not have these.
Click to expand...
Click to collapse
bro .
i was playing a game in my phone and the game shot me out and i see the system apps deleted in the menu of apps
i trie restart phone when idid my phone stuck wont open the system but its redirect me to twrp recovery
when the twrp opened i connect my phone with usb to pc
and i see nothing in internal storage only the twrp files !
im find all backup files (IMGs) system.img and cus.img etc..
but idk how to install it
My android version is 7..0 nougat 5.1 emui
and sry for my bad english ..
{
"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"
}
ayadmanhal said:
bro .
i was playing a game in my phone and the game shot me out and i see the system apps deleted in the menu of apps
i trie restart phone when idid my phone stuck wont open the system but its redirect me to twrp recovery
when the twrp opened i connect my phone with usb to pc
and i see nothing in internal storage only the twrp files !
im find all backup files (IMGs) system.img and cus.img etc..
but idk how to install it
My android version is 7..0 nougat 5.1 emui
and sry for my bad english ..
Click to expand...
Click to collapse
If you have all the needed files, just do this:
1. Boot into TWRP
2. Flash vendor.img, recovery_ramdis.img (Or something similar to that), and system.img
3. Flash them ^^^^ to the required partitions (Partition names to flash to should be self explanatory)
4. Do a factory reset
5. Reboot
Report back please if this works!
I have the exact same problem as OP. When I go into TWRP and mount an img or zip, there is always an error message saying
"Unable to find partition for path '/system' ". /system also doesn't show up anywhere else. . .
I tried your suggestion too but to no avail.
I don't know what to do anymore.
Edit: Now I can’t even get into TWRP after trying these 5 steps. All it shows me is the bootloader screen but with error messages.
“Please update the system again”
And at the bottom of the screen something about the boot.img
dutyyaknow said:
I have the exact same problem as OP. When I go into TWRP and mount an img or zip, there is always an error message saying
"Unable to find partition for path '/system' ". /system also doesn't show up anywhere else. . .
I tried your suggestion too but to no avail.
I don't know what to do anymore.
Edit: Now I can’t even get into TWRP after trying these 5 steps. All it shows me is the bootloader screen but with error messages.
“Please update the system again”
And at the bottom of the screen something about the boot.img
Click to expand...
Click to collapse
If you're talking about my suggestion, then please quote me next time.
Also, are you sure you have the right twrp installed?
When in bootloader mode, connect your device to adb. Does you device get recognized when you type "fastboot devices" ???
crayonicle said:
If you're talking about my suggestion, then please quote me next time.
Also, are you sure you have the right twrp installed?
When in bootloader mode, connect your device to adb. Does you device get recognized when you type "fastboot devices" ???
Click to expand...
Click to collapse
Thank you for helping out.
Yes, I tried your suggestion and I used version 3.1.1.0 of TWRP.
Unfortunately it looks like my device is not getting recognized in adb anymore. All I get is either the screen where it says "booting your device now" forever or the white ERROR MODE screen with "Attention! Please update system again.
There are two error messages at the bottom of the screen :
Func NO : 10 (boot image)
Error NO : 2 (load failed)
Now, how do I save myself out of this? It looks like I can't do anything. . .
Edit: correction, it does get recognized in adb in fastboot mode. Can I just flash your suggested TWRP from there?
Edit2: tried to flash the complete_twrp_ramdisk.img in fastboot mode with fastboot flash recovery command. Then I rebooted but instead of TWRP it still shows ERROR MODE
crayonicle said:
If you have all the needed files, just do this:
1. Boot into TWRP
2. Flash vendor.img, recovery_ramdis.img (Or something similar to that), and system.img
3. Flash them ^^^^ to the required partitions (Partition names to flash to should be self explanatory)
4. Do a factory reset
5. Reboot
Report back please if this works!
Click to expand...
Click to collapse
i did everything but nothing changed
ihave installed all IMGs
nothing happened and my phone still empty !
i trying to flash [OpenKirin's RROS ] room
it says succes but when im reboot still rebooting into recovery mode {twrp} 3.1.1.0
and my storage still empty
idk what i have to do
im think we have nothing to do !?
dutyyaknow said:
I have the exact same problem as OP. When I go into TWRP and mount an img or zip, there is always an error message saying
"Unable to find partition for path '/system' ". /system also doesn't show up anywhere else. . .
I tried your suggestion too but to no avail.
I don't know what to do anymore.
Edit: Now I can’t even get into TWRP after trying these 5 steps. All it shows me is the bootloader screen but with error messages.
“Please update the system again”
And at the bottom of the screen something about the boot.img
Click to expand...
Click to collapse
i think we loose our devices <\3
crayonicle said:
If you're talking about my suggestion, then please quote me next time.
Also, are you sure you have the right twrp installed?
When in bootloader mode, connect your device to adb. Does you device get recognized when you type "fastboot devices" ???
Click to expand...
Click to collapse
ayadmanhal said:
i think we loose our devices <\3
Click to expand...
Click to collapse
There has to be a way to fix it from fastboot mode.
If everything fails, we can still try to send it to a Huawei Center to get fixed. Just don't tell them that you rooted or unlocked your device. I heard that they will then switch out the motherboard for a new one.
dutyyaknow said:
There has to be a way to fix it from fastboot mode.
If everything fails, we can still try to send it to a Huawei Center to get fixed. Just don't tell them that you rooted or unlocked your device. I heard that they will then switch out the motherboard for a new one.
Click to expand...
Click to collapse
we cant go to huawei center bcz the phone unlocked and rooted
so the phone has no Guarantee and they will see the boot when says the device is not trusted <\3
After reflashing my old TWRP from fastboot, I can now access TWRP again and /system partition is showing up too. The ERROR MODE screen still shows up when I boot the phone with VOL + and POWER but when I press VOL + - and POWER I load into TWRP
dutyyaknow said:
After reflashing my old TWRP from fastboot, I can now access TWRP again and /system partition is showing up too. The ERROR MODE screen still shows up when I boot the phone with VOL + and POWER but when I press VOL + - and POWER I load into TWRP
Click to expand...
Click to collapse
my device only auto booting for twrp nothing more
up
no help :\
ayadmanhal said:
no help :\
Click to expand...
Click to collapse
Do you have ADB support on TWRP mode?
If so just use dd command to flash stock boot.img.
Try it by fastboot if you can.
You need to flash stock boot.img because rooting patches boot image and you tried to unroot but were unable to reboot that would replace the patched boot with the stock one.
If i undetstood the issue correctly...
If not, please enlight me...
Enviado do meu Le 2 através do Tapatalk
RSGI said:
Do you have ADB support on TWRP mode?
If so just use dd command to flash stock boot.img.
Try it by fastboot if you can.
You need to flash stock boot.img because rooting patches boot image and you tried to unroot but were unable to reboot that would replace the patched boot with the stock one.
If i undetstood the issue correctly...
If not, please enlight me...
Enviado do meu Le 2 através do Tapatalk
Click to expand...
Click to collapse
i trie much of boot.img files but no change
i tried everything but the phone still wont read the system files
dutyyaknow said:
Thank you for helping out.
Yes, I tried your suggestion and I used version 3.1.1.0 of TWRP.
Unfortunately it looks like my device is not getting recognized in adb anymore. All I get is either the screen where it says "booting your device now" forever or the white ERROR MODE screen with "Attention! Please update system again.
There are two error messages at the bottom of the screen :
Func NO : 10 (boot image)
Error NO : 2 (load failed)
Now, how do I save myself out of this? It looks like I can't do anything. . .
Edit: correction, it does get recognized in adb in fastboot mode. Can I just flash your suggested TWRP from there?
Edit2: tried to flash the complete_twrp_ramdisk.img in fastboot mode with fastboot flash recovery command. Then I rebooted but instead of TWRP it still shows ERROR MODE
Click to expand...
Click to collapse
Have you re-flash with Huawei Multi Tool, but first you must have file update.zip and extract update.app from http://pro-teammt.ru/firmware-database/?firmware_model=BND&firmware_page=0
---------- Post added at 06:48 AM ---------- Previous post was at 06:41 AM ----------
ayadmanhal said:
i trie much of boot.img files but no change
i tried everything but the phone still wont read the system files
Click to expand...
Click to collapse
you on Nougat? have try to upgrade to Oreo from this thread,
https://forum.xda-developers.com/honor-7x/how-to/manual-update-to-oreo-beta-emui-8-bnd-t3767044
there's maybe can fix your system file
Firstly, when plugging my 7t in to my windows 10 PC, I am asked to choose which mode to go in within usb preferences, as I did previously in order to achieve and ADB driver connection I chose file transfer.......
this didn't work for some reason, only when in MIDI did I get a confirmation with adb devices.....even though there is still no sign of adb interface in device manager.....
any ideas? I can get adb connection with MIDI but is this good enough to flash recoveries/boot images etc....?
I tried to flash twrp and I could successfully boot into twrp directly via fastboot but twrp couldn't seen any of my storage, despite having all security methods turned off...
all i want to do is gain root access but I am having no joy....
ever since android 10 rooting anything for me has been a pain in the ass......truly fed up....it shouldn't be this hard......
I also flashed a patched boot image in an attempt to gain root access but it all did was break my wifi........which i fixed by copying over the latest image and installing locally......
please HELP....
Everything about this issues is already said in this forum.
Try looking at this topic here:
https://forum.xda-developers.com/oneplus-7t/development/recovery-unofficial-twrp-recovery-t3976961
ontwykende said:
Try looking at this topic here:
https://forum.xda-developers.com/oneplus-7t/development/recovery-unofficial-twrp-recovery-t3976961
Click to expand...
Click to collapse
sweet, ill check it out.....
ontwykende said:
Try looking at this topic here:
https://forum.xda-developers.com/oneplus-7t/development/recovery-unofficial-twrp-recovery-t3976961
Click to expand...
Click to collapse
It would seem that TWRP is a no go, for awhile at least.....
anyone managed to gain root access by flashing a patched boot.img?
mediaman123 said:
It would seem that TWRP is a no go, for awhile at least.....
anyone managed to gain root access by flashing a patched boot.img?
Click to expand...
Click to collapse
Lots of people have. Just boot your version and use magisk to direct install and reboot then you have root
Josh McGrath said:
Lots of people have. Just boot your version and use magisk to direct install and reboot then you have root
Click to expand...
Click to collapse
Normally I would be able to carry out such tasks but because I now feel so fed up with it all could I trouble you to tell my step by step how that is done.....?
many thanks..
mediaman123 said:
Normally I would be able to carry out such tasks but because I now feel so fed up with it all could I trouble you to tell my step by step how that is done.....?
many thanks..
Click to expand...
Click to collapse
I made a tool to install the latest ADB, Fastboot and USB drivers for windows, its very easy to use, just double click the file to start the installation process
you can see it here:
https://forum.xda-developers.com/android/general/tool-adb-fastboot-installer-tool-windows-t3999445
Screenshot:
{
"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"
}
fawazahmed0 said:
I made a tool to install the latest ADB, Fastboot and USB drivers for windows, its very easy to use, just double click the file to start the installation process
you can see it here:
https://forum.xda-developers.com/android/general/tool-adb-fastboot-installer-tool-windows-t3999445
Screenshot:
Click to expand...
Click to collapse
I can operate that fine, its just how to obtain boot.img files etc, patch them and so on..
mediaman123 said:
I can operate that fine, its just how to obtain boot.img files etc, patch them and so on..
Click to expand...
Click to collapse
Oh, I thought, you are have issues with adb, and for root, you just have to flash magisk using twrp
fawazahmed0 said:
Oh, I thought, you are have issues with adb, and for root, you just have to flash magisk using twrp
Click to expand...
Click to collapse
This isn't functional at the minute as TWRP, whether its flashed or booted from, cant get past the encryption.......it cant see/mount the internal storage....
mediaman123 said:
This isn't functional at the minute as TWRP, whether its flashed or booted from, cant get past the encryption.......it cant see/mount the internal storage....
Click to expand...
Click to collapse
You will have to wipe the data and then twrp can access internal storage.
This is how I did (in my phone, which is not Oneplus, but the process remain same for all phones), boot to fastboot mode and type this:
fastboot -w
Now, boot your phone to recovery mode:
(Now take complete twrp backup of your phone, and save it in your pc, before proceeding futher)
flash DM verity disabler: https://forum.xda-developers.com/android/software/universal-dm-verity-forceencrypt-t3817389
flash magisk: https://github.com/topjohnwu/magisk_files/raw/canary/magisk-release.zip
Now boot the phone back to OS and you will have root access
fawazahmed0 said:
You will have to wipe the data and then twrp can access internal storage.
This is how I did (in my phone, which is not Oneplus, but the process remain same for all phones), boot to fastboot mode and type this:
fastboot -w
Now, boot your phone to recovery mode:
(Now take complete twrp backup of your phone, and save it in your pc, before proceeding futher)
flash DM verity disabler: https://forum.xda-developers.com/android/software/universal-dm-verity-forceencrypt-t3817389
flash magisk: https://github.com/topjohnwu/magisk_files/raw/canary/magisk-release.zip
Now boot the phone back to OS and you will have root access
Click to expand...
Click to collapse
thanks for this......want to try and avoid wiping if possible but if I really want root I will do it.....
what does the command fastboot -w do?
mediaman123 said:
thanks for this......want to try and avoid wiping if possible but if I really want root I will do it.....
what does the command fastboot -w do?
Click to expand...
Click to collapse
it wipe's the data
mediaman123 said:
This isn't functional at the minute as TWRP, whether its flashed or booted from, cant get past the encryption.......it cant see/mount the internal storage....
Click to expand...
Click to collapse
fawazahmed0 said:
You will have to wipe the data and then twrp can access internal storage.
This is how I did (in my phone, which is not Oneplus, but the process remain same for all phones), boot to fastboot mode and type this:
fastboot -w
Now, boot your phone to recovery mode:
(Now take complete twrp backup of your phone, and save it in your pc, before proceeding futher)
flash DM verity disabler: https://forum.xda-developers.com/android/software/universal-dm-verity-forceencrypt-t3817389
flash magisk: https://github.com/topjohnwu/magisk_files/raw/canary/magisk-release.zip
Now boot the phone back to OS and you will have root access
Click to expand...
Click to collapse
TWRP is not functional at the moment, so stay away from it.
The only way to root right now is to use the patch boot image method.
Lossyx said:
No don't do this.... This is not about encryption at all. It's about the major partitioning changes that has happened in Android 10. Wiping the system will just make everything worse.
Avoid using TWRP at all.
Sent from my OnePlus7TPro using XDA Labs
Click to expand...
Click to collapse
Oh, I didn't know this phone was on Android 10, Thanks for letting me know.
TWRP doesn't support Android 10 yet.
You can see it here
https://twrp.me/site/update/2019/10/23/twrp-and-android-10.html
Actually there is a twrp compiled for this phone, but that doesn't work , you can see the messages in thread:
https://forum.xda-developers.com/oneplus-7t/development/recovery-unofficial-twrp-recovery-t3976961
The steps I told, was for Android 9 and earlier devices, I assumed, this is an old device.
@mediaman123, So please wait, until twrp starts supporting the Android 10.
And for rooting, I am not sure, whether magisk supports this new phone or not.
Maybe @Lossyx can help you on that.
https://forum.xda-developers.com/oneplus-7t/how-to/guide-how-to-root-oneplus-7t-twrp-t3979307
Sent from my OnePlus7TPro using XDA Labs
Lossyx said:
https://forum.xda-developers.com/oneplus-7t/how-to/guide-how-to-root-oneplus-7t-twrp-t3979307
Sent from my OnePlus7TPro using XDA Labs
Click to expand...
Click to collapse
Seen this, however my device, the European version, is running on 10.0.6.....
The only boot images available with that post is the 10.0.3...
wouldn't feel comfortable using them.....
I would like to know how to extract the stock boot image from either the firmware file or the phone itself...
mediaman123 said:
Seen this, however my device, the European version, is running on 10.0.6.....
The only boot images available with that post is the 10.0.3...
wouldn't feel comfortable using them.....
I would like to know how to extract the stock boot image from either the firmware file or the phone itself...
Click to expand...
Click to collapse
You can go ahead and just fastboot boot them. If it works then just proceed, if it doesn't, just hold volume up+down and power button. (To boot into fastboot or restart phone)
Nothing will change in the system because it only boots a temporary image.
If your want to extract your own boot image you can use this tool.
https://github.com/cyxx/extract_android_ota_payload
Sent from my OnePlus7TPro using XDA Labs
Lossyx said:
You can go ahead and just fastboot boot them. If it works then just proceed, if it doesn't, just hold volume up+down and power button. (To boot into fastboot or restart phone)
Nothing will change in the system because it only boots a temporary image.
If your want to extract your own boot image you can use this tool.
https://github.com/cyxx/extract_android_ota_payload
Sent from my OnePlus7TPro using XDA Labs
Click to expand...
Click to collapse
So if it boots an older image successfully I can move it over to the phone to patch to then flash it or use the already patched one and flash that...?..
{
"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"
}
Hello, dear owners of this beautiful device.
After an unsuccessful attempt to get root, such a warning appeared, plus the ability to lock the screen disappeared. As a result, I didn't get root either and problems arose)
Could you show the instructions how to fix everything step by step and get root? Thanks)
Hey, so I have the same problem as you. I was installing the patched boot.img file when I rebooted, but there was no magsik app. After I tried to flash the same file again, except I put in some vbmeta file because some website said so, now my phone's files are corrupted. I got into fastboot mode and put through recovery mode, and did a data wipe and one final reboot, but even that did work because it said my phone is corrupt. The last thing I will try is to install TWRP, remove the old data, and install the update to restore the previous ROM files. I'll let you know if anything works. Just try ur methods and let me know if they worked. Sure is an expensive paperweight if it doesn't work...
redmgicUSER8 said:
Hey, so I have the same problem as you. I was installing the patched boot.img file when I rebooted, but there was no magsik app. After I tried to flash the same file again, except I put in some vbmeta file because some website said so, now my phone's files are corrupted. I got into fastboot mode and put through recovery mode, and did a data wipe and one final reboot, but even that did work because it said my phone is corrupt. The last thing I will try is to install TWRP, remove the old data, and install the update to restore the previous ROM files. I'll let you know if anything works. Just try ur methods and let me know if they worked. Sure is an expensive paperweight if it doesn't work...
Click to expand...
Click to collapse
did anything happen?
Stusick said:
Did anything happen?
Click to expand...
Click to collapse
Nothing yet... I'm trying to contact the support team. They can only do so much remotely
i have this error also what should i do?
the phone not boot up
the red warning are stuck
yakir150 said:
i have this error also what should i do?
the phone not boot up
the red warning are stuck
Click to expand...
Click to collapse
Your boot loader must be unlock
Reboot to recovery, choose English when you see "Wipe data" type
adb reboot sideload
Once your phone boots into sideload mode (When you see the two error line at the bottom of the screen) type
adb sideload NX729J-update.zip
When the transfer is successful ( with a transfer of 2.0 display) you can wipe the data twice with the first and second options and reboot the phone. If you are lucky, the phone will boot
[email protected] said:
Your boot loader must be unlock
Reboot to recovery, choose English when you see "Wipe data" type
adb reboot sideload
Once your phone boots into sideload mode (When you see the two error line at the bottom of the screen) type
adb sideload NX729J-update.zip
When the transfer is successful ( with a transfer of 2.0 display) you can wipe the data twice with the first and second options and reboot the phone. If you are lucky, the phone will boot
Click to expand...
Click to collapse
okay i try it and still no luck the same problem
yakir150 said:
okay i try it and still no luck the same problem
Click to expand...
Click to collapse
Download global V3.19 rom from: https://rom.download.nubia.com/Europe&Asia/NX729J/V319/NX729J.zip
Download QPST and QFIL flash tool from: https://www.mediafire.com/file/220h5xaxi1gd55m/QPST_2.7.496.zip/file. Install the driver (provided in the download) and these two programs.
You could then flash this rom V3.19 using QFIL flash tool. If you can flash this rom successfully your phone will work.
[email protected] said:
Download global V3.19 rom from: https://rom.download.nubia.com/Europe&Asia/NX729J/V319/NX729J.zip
Download QPST and QFIL flash tool from: https://www.mediafire.com/file/220h5xaxi1gd55m/QPST_2.7.496.zip/file. Install the driver (provided in the download) and these two programs.
You could then flash this rom V3.19 using QFIL flash tool. If you can flash this rom successfully your phone will work.
Click to expand...
Click to collapse
my phone is eu and using 4.18
can i use 3.19?
it's ok?
yakir150 said:
okay i try it and still no luck the same problem
Click to expand...
Click to collapse
For QFIL, use Flat Build and in the configuration use ufs. Good luck!
yakir150 said:
my phone is eu and using 4.18
can i use 3.19?
it's ok?
Click to expand...
Click to collapse
Your version V4.18 will be replaced by V3.19. This V3.19 version can be flashed through edl mode. I could not find V4.18 in this format. The two roms are very similar. They are both global roms.
[email protected] said:
Your version V4.18 will be replaced by V3.19. This V3.19 version can be flashed through edl mode. I could not find V4.18 in this format. The two roms are very similar. They are both global roms.
Click to expand...
Click to collapse
okay i will try and let you know
thank you very much
yakir150 said:
okay i try it and still no luck the same problem
Click to expand...
Click to collapse
If QFIL does not work, you need to do side load the rom multiple times again then it might work!
turn off the red rm8 notification (Your device is broken. It is unreliable and may not work)
- enter command on PC: adb reboot "dm-verity enforcing"
- on phone for rooted device with termux: reboot "dm-verity enforcing"
izsdeaman said:
turn off the red rm8 notification (Your device is broken. It is unreliable and may not work)
- enter command on PC: adb reboot "dm-verity enforcing"
- on phone for rooted device with termux: reboot "dm-verity enforcing"
Click to expand...
Click to collapse
The command on PC shows "Too many arguments." The Termux one works. Thanks!
[email protected] said:
Your boot loader must be unlock
Reboot to recovery, choose English when you see "Wipe data" type
adb reboot sideload
Once your phone boots into sideload mode (When you see the two error line at the bottom of the screen) type
adb sideload NX729J-update.zip
When the transfer is successful ( with a transfer of 2.0 display) you can wipe the data twice with the first and second options and reboot the phone. If you are lucky, the phone will boot
Click to expand...
Click to collapse
Tahnk you very very very much.