Related
Firstly, I am sorry for creating such a noob thread on the forum, but I could really use a hand.
I was flashing a 4.4 ROM (SlimKat), I had wiped /system, /boot, etc. everything but usb storage. I then went to flash the .zip and everything looked alright for about 30 seconds (formatting finished, mounting partitions, etc.) until the installation hit a bump and said there was an error in the ROM .zip, and then aborted.
I have a NANDroid backup on the USB storage, but for some reason CWM refuses to install it claiming there is an MD5 mismatch. USB storage won't mount to my PC (in CWM) for whatever reason, and fastboot won't work in either win7 or ubuntu. I've tried AdamOutler's unbrickable tool with no success, it can't recognise the device and says SBL Injection Failure.
Any ideas? Thanks very much for any help.
mrjimyjohn said:
Firstly, I am sorry for creating such a noob thread on the forum, but I could really use a hand.
I was flashing a 4.4 ROM (SlimKat), I had wiped /system, /boot, etc. everything but usb storage. I then went to flash the .zip and everything looked alright for about 30 seconds (formatting finished, mounting partitions, etc.) until the installation hit a bump and said there was an error in the ROM .zip, and then aborted..
Click to expand...
Click to collapse
What exactly was the error?
There wasn't a real error dialogue, if I remember right it just displayed "ERROR: there was an error in <ROM package.zip> installation aborted" The next line said something like "(code 7)".
Thanks man
Which CWM version were you using?
I was using 6.0.3.1. One of the first things I thought of was updating the recovery, but with no way to mount /sdcard I don't know how I could.
mrjimyjohn said:
I was using 6.0.3.1. One of the first things I thought of was updating the recovery, but with no way to mount /sdcard I don't know how I could.
Click to expand...
Click to collapse
You need at least CWM 6.0.4.3 to install any 4.4 rom. Flash the recovery.img via fastboot.
Download the latest CWM (.img, not .zip) and then also install this: http://forum.xda-developers.com/showthread.php?t=2317790, connect your device to pc, reboot to bootloader (vol up + power button) then enter this in command prompt provided by "minimal adb and fastboot": fastboot flash recovery <recovery img path and filename>.img
This should fix your problem if done correctly.
Thank you very much, I will try that.
I think the problem though, is that my pc cannot recognize the device in any form. Normally I would expect to at least see a "device not working properly" or similar message with the windows "beep", but I get nothing, in fastboot mode or with usb storage mounted in recovery. On a different ubuntu machine it's not recognized either, fastboot - devices and adb -devices both return nothing.
Try having your device drivers set-up through Nexus Root Toolkit. Just follow the "Full Driver Installation Guide" inside the app and delete all samsung drivers and then freshly install drivers needed for your device. This is worth the shot although the problem could be your usb cable, usb port, etc..
Thanks for your help. I actually tried Wug's tool with no luck, but I didn't ununstall the original drivers first so that may have been the problem. I'll also try using a different cords and PCs when I get back home.
Thanks again, and merry christmas!
So I bought a new usb cable and my pc could talk to the device as it was showing up in device manager. I installed the drivers again and got fastboot working, but I'm not really sure how to flash from here. I flashed the new CWM with
fastboot flash recovery <cwm*.zip>
It worked just fine, but how can I flash a rom now? regular .zip rom's can't be flashed through fastboot AFAIK, and looking through my NANDroid backups it looks like none of them have a system.img which seems really weird. Can I flash a system.ext4.tar.a as if it was a system.img?
I would have thought you could transfer files to /sdcard through fastboot but I guess not...
mrjimyjohn said:
So I bought a new usb cable and my pc could talk to the device as it was showing up in device manager. I installed the drivers again and got fastboot working, but I'm not really sure how to flash from here. I flashed the new CWM with
fastboot flash recovery <cwm*.zip>
It worked just fine, but how can I flash a rom now? regular .zip rom's can't be flashed through fastboot AFAIK, and looking through my NANDroid backups it looks like none of them have a system.img which seems really weird. Can I flash a system.ext4.tar.a as if it was a system.img?
I would have thought you could transfer files to /sdcard through fastboot but I guess not...
Click to expand...
Click to collapse
Oh I thought you already put your desired rom inside the sdcard. My workaround for this: flash TWRP via fastboot, mount sd card to pc, move rom.zip to sdcard, then re-flash latest CWM via fastboot. Flash rom through recovery.
I did have it on there originally but I foolishly did a full wipe through fastboot. I tried to mount SD card with cwm but my PC still wouldn't recognise it, does TWRP mount things differently or something? All is good now though, I didn't realise you could use adb while in recovery mode so I could push files that way with sideload. Thanks for your help man, its really, uh, helped.
Hello everyone,
FINAL Edit:
The device is stuck in bootloader, I can get it into recovery mode, and I have twrp installed. I noticed that I can use the abd sideloader option, as well as abd in my command prompt on my computer. Is there any way to push a rom onto the internal storage? I've tried using an SD Card, but the TWRP will not recognize the card, therefore I cannot flash from it. IF you know a solution to either of these issues, It will be very much appreciated.
Thanks,
Drewster1028
I have unlocked bootloader, rooted phone and installed TWRP recovery without any problems. I made one huge mistake - I wiped system and data, so Im left with no OS and no image to flash from memory. I can access TWRP wihout any problems, but i cannot use OTG mode (i cannot check box to mount it and in explorer usb is empty). When i connect my phone to PC i cannot flash using ADB, it cannot find the device. Fastboot can see it though. What do I do now, how to revive my phone?
fillion_f said:
I have unlocked bootloader, rooted phone and installed TWRP recovery without any problems. I made one huge mistake - I wiped system and data, so Im left with no OS and no image to flash from memory. I can access TWRP wihout any problems, but i cannot use OTG mode (i cannot check box to mount it and in explorer usb is empty). When i connect my phone to PC i cannot flash using ADB, it cannot find the device. Fastboot can see it though. What do I do now, how to revive my phone?
Click to expand...
Click to collapse
You need to use the mfastboot method. Check this tutorial: http://forum.xda-developers.com/showpost.php?p=47820707. Download the firmware (ideally 4.4.2 or 4.4.3) in *.xml.zip format, and do all the steps at the tutorial. Skip 3a) and go to 3b) - the one with mfastboot commands.
That's what helped me when I accidentally deleted my system - I also made a thread: http://forum.xda-developers.com/moto-g/help/bricked-moto-g-xt1032-converted-to-gpe-t3054655.
fillion_f said:
I have unlocked bootloader, rooted phone and installed TWRP recovery without any problems. I made one huge mistake - I wiped system and data, so Im left with no OS and no image to flash from memory. I can access TWRP wihout any problems, but i cannot use OTG mode (i cannot check box to mount it and in explorer usb is empty). When i connect my phone to PC i cannot flash using ADB, it cannot find the device. Fastboot can see it though. What do I do now, how to revive my phone?
Click to expand...
Click to collapse
Ya.. Using mfastboot and typing out those commands as given in tuitorial you can install stock firmware to your phone using the Adb.. Its not hard bricked. Don't worry. Had faced the same issue last month.
Sent from my Moto G using Tapatalk
I cannot flash sparsechunk 1,2 and 3 files, but it can be ROM's fault. I'll download another one to check if its working
EDIT: using another ROM worked for me, thanks for help
Debanka said:
Ya.. Using mfastboot and typing out those commands as given in tuitorial you can install stock firmware to your phone using the Adb.. Its not hard bricked. Don't worry. Had faced the same issue last month.
Sent from my Moto G using Tapatalk
Click to expand...
Click to collapse
Sorry for pushing this old thread.
My phone is also stucked, adb cannot find my device. How do I do it then? If my device is not listed, is it possible using fastboot to get back to the old stock Firmware?
Okay, so when trying to flash CM ROM, I stupidly ended up wiping EVERYTHING in the "wipe" option. Trying to recover it, I tried sideloading the file through ADB, but TWRP would disconnect off the PC and say failed (TWRP version 3.0.2-0). Pushing a ROM zip won't work, as the phone only connects to the PC as ADB Sideload mode ('error: closed' is what it would say), and nothing else would work except sideload. I no longer have a working OTG cable, as my last one broke on me a week ago. The PC will not connect to phone on the 'Mount USB' option from TWRP. Plz help! I'm running out of ideas. I did make a backup (using Online Nandroid Backup, no it wasn't a zip) on the SD card, but TWRP will not read the SD card on my device. Note that the only thing I have is TWRP; no bootloader, no Fastboot, no nothing. Just TWRP.
TRiP_E said:
Okay, so when trying to flash CM ROM, I stupidly ended up wiping EVERYTHING in the "wipe" option. Trying to recover it, I tried sideloading the file through ADB, but TWRP would disconnect off the PC and say failed (TWRP version 3.0.2-0). Pushing a ROM zip won't work, as the phone only connects to the PC as ADB Sideload mode ('error: closed' is what it would say), and nothing else would work except sideload. I no longer have a working OTG cable, as my last one broke on me a week ago. The PC will not connect to phone on the 'Mount USB' option from TWRP. Plz help! I'm running out of ideas. I did make a backup (using Online Nandroid Backup, no it wasn't a zip) on the SD card, but TWRP will not read the SD card on my device. Note that the only thing I have is TWRP; no bootloader, no Fastboot, no nothing. Just TWRP.
Click to expand...
Click to collapse
You can connect to ADB but the adb push command isn't working when you try to move the ROM.zip to the device?
Get a new OTG cable.
The nandroid backup you made should have been done in TWRP and stored on extsdcard instead of the online backup, online backup is crap because it only works in certain conditions, it's useless when the device can't connect to a network.
Sent from my SM-S903VL using Tapatalk
Yes. ADB commands other than sideload will say 'error:closed', and ADB Sideload will just end up making the phone disconnect. At this point, I may HAVE to end up getting a new OTG Cable.
Yes, I was trying to do the backup on TWRP, but as it couldn't read the SD Card, I used Online Nandroid Backup. Then I realized that everything I was doing was completely stupid while I wiped EVERYTHING....
TRiP_E said:
Yes. ADB commands other than sideload will say 'error:closed', and ADB Sideload will just end up making the phone disconnect. At this point, I may HAVE to end up getting a new OTG Cable.
Yes, I was trying to do the backup on TWRP, but as it couldn't read the SD Card, I used Online Nandroid Backup. Then I realized that everything I was doing was completely stupid while I wiped EVERYTHING....
Click to expand...
Click to collapse
Yeah, new cable seems to be your only option.
Sent from my SM-S903VL using Tapatalk
Alright then, I'm going to go see where I can buy one. Thanks for the confrirmation.
I cant even mount the ****ing usb flashdrive through OTG!!!!! On other devices, it works fine, but on this device it doesn't even show the frickin USB-OTG option.
TRiP_E said:
I cant even mount the ****ing usb flashdrive through OTG!!!!! On other devices, it works fine, but on this device it doesn't even show the frickin USB-OTG option.
Click to expand...
Click to collapse
Try rooting the device and then use the Stick Mount app, if your device has the hardware to support OTG, that should enable it, but if your device does not have the hardware to support OTG then it doesn't matter what you do softwarewise or what you modify, it has to have the hardware or it can't do it at all.
Things like this are why I'd never buy or own a ZTE device of any kind. Relatively soeakibg, they are all junk.
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
Only thing is, I dont HAVE any system to boot in order to check that. I guess I'm out of luck, no wonder why others said this phone was crap.
TRiP_E said:
Only thing is, I dont HAVE any system to boot in order to check that. I guess I'm out of luck, no wonder why others said this phone was crap.
Click to expand...
Click to collapse
If you can use adb shell or fastboot, you can try getting a copy of system.img from someone with your exact device and dd or fastboot flash the img.
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
Any ADB commands other than Sideload will just respond as error:closed, as the computer only reads the system when in ADB Sideload mode. However, when trying to sideload a ROM, the phone will disconnect and say failed, while the computer stays on xfer: 0.00. Maybe I could get some instructions to fix that? Maybe a bad TWRP version? If so, I'm ****ed...
After reading other pols forums, it seems that I didn't have to delete the internal storage........
TRiP_E said:
Any ADB commands other than Sideload will just respond as error:closed, as the computer only reads the system when in ADB Sideload mode. However, when trying to sideload a ROM, the phone will disconnect and say failed, while the computer stays on xfer: 0.00. Maybe I could get some instructions to fix that? Maybe a bad TWRP version? If so, I'm ****ed...
Click to expand...
Click to collapse
Sideloading a ROM won't work.
Try
adb reboot bootloader
If you can boot to bootloader or fastboot you can try finding the firmware for another device that has all of the exact same hardware components that your device has then try fastboot flashing it or extract the separate .imgs from the firmware and use the fastboot commands to flash the boot.img and system.img.
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
can't get into fastboot, ADB command says error: closed, while doing the command in terminal in the TWRP menu keeps me on ZTE screen (only reboot recovery works, not as ADB command but in terminal).
TRiP_E said:
Any ADB commands other than Sideload will just respond as error:closed, as the computer only reads the system when in ADB Sideload mode. However, when trying to sideload a ROM, the phone will disconnect and say failed, while the computer stays on xfer: 0.00. Maybe I could get some instructions to fix that? Maybe a bad TWRP version? If so, I'm ****ed...
Click to expand...
Click to collapse
I have most, if not all the. Img files for this I managed to successfully root, TWRP, and deKingoCrap my n817
I also have a nandroid of this phone, though mine is the qlink one
help.
equitube said:
I have most, if not all the. Img files for this I managed to successfully root, TWRP, and deKingoCrap my n817
I also have a nandroid of this phone, though mine is the qlink one
Click to expand...
Click to collapse
dude i need the twrp backup of the qlink variant. i formatted the system and got bootloop at zte screen
filldapipe said:
dude i need the twrp backup of the qlink variant. i formatted the system and got bootloop at zte screen
Click to expand...
Click to collapse
Did you ever get the TWRP for this? I have it in my dropbox pm me.
The issue were running into is that the TWRP on this model can't see the ext sd. The backup is 1.5 or 2gb which is usually too large to fit on the internal SD
Slacker is working hard at modding the Fstab file to make TWRP see that storage. Any ideas please let him or I know([email protected] or here )
I'm also working on an EquiMods custom ROM for this. Bare bones battery saver, switchable to performance when needed.
Anyone know if and how these can be overclocked?
I have a deodex rom done for this phone and also should have the working twrp recovery by morning. The cm11.0 ive been working on is almost done. I hope Everytime i flash it to phone i get white screen. Also im going to install xposed on it in the morning. I think i found the fix for that to work
Any news on this? I can't find anything that works with this phone. I have adb sideload working, but that's pretty useless from what I understand.
edsfunsite said:
Any news on this? I can't find anything that works with this phone. I have adb sideload working, but that's pretty useless from what I understand.
Click to expand...
Click to collapse
They obviously got something to work since there are members in this thread that have TWRP installed on their devices, that means they can at least root the device but I doubt there are any ROMs for this device.
Sent from my LGL84VL using Tapatalk
I've rooted my N817 but never made an Nandroid backup. I still have TWRP up and working but I've tried to flash the 2 roms I know of....they both "install" but when I try to boot It stays in the ZTE screen...Help!
So I was stupid enough to wipe all partitions (Data, system, internal storage etc) thinking that I'll do a super clean install of the new update.
Now I flash the new file (which I downloaded from the official website), it flashes just fine but gives me a bootloop.
I have (or had) root and can flash TWRP fine.
What else can I do to get back any running rom?
https://forum.xda-developers.com/oneplus-6/how-to/rom-stock-fastboot-roms-oneplus-6-t3796665
Hopefully this will help you like it did with me .
Try flashiing stock boot.img from adb or try to the unbrick tool
Absolutely nothing at all worked, not even in the slightest, everything gave me a boot loop. Except for one thing; I flashed the Open Beta DP3 zip file in twrp and that worked, then I use set it up and used the rollback-to-stable release file to revert to stable release.
I see absolutely no logic behind how and why this worked and not the other traditional methods though, anyone have any clarification on this please?
Thank you for your responses though guys, much appreciated!
If you can still access TWRP recovery, try sideloading a rom via fastboot on a Windows PC. Boot to TWRP > Advanced > Sideload. On your Windows machine - Open fastboot and type "adb sideload *rom name*.zip. See if that works. If sideloading fails for whatever reason but you can still access TWRP try pushing the rom to internal storage by using fastboot again. Boot to TWRP on your phone and do nothing else. On your Windows machine open fastboot and type "adb push *rom name*.zip /data/media/0" this will push the rom to your internal storage.
railpressureflip said:
Absolutely nothing at all worked, not even in the slightest, everything gave me a boot loop. Except for one thing; I flashed the Open Beta DP3 zip file in twrp and that worked, then I use set it up and used the rollback-to-stable release file to revert to stable release.
I see absolutely no logic behind how and why this worked and not the other traditional methods though, anyone have any clarification on this please?
Thank you for your responses though guys, much appreciated!
Click to expand...
Click to collapse
the most important thing you missed mentioning was which ROM were you ON when you wiped everything?
bcz if it was using an August security patch, and if you tried to go back to a july one without formatting data you were bound to get bootloops.
glad that it finally worked though.
but if you wanna try again, be sure to format data and your super clean install will go through.
wipe everything
format data
reboot fastboot
fastboot boot recovery
adb push stock stable ROM
flash via twrp
adb push twrp zip
flash twrp zip
reboot
now you will be fine.
speedyjay said:
If you can still access TWRP recovery, try sideloading a rom via fastboot on a Windows PC. Boot to TWRP > Advanced > Sideload. On your Windows machine - Open fastboot and type "adb sideload *rom name*.zip. See if that works. If sideloading fails for whatever reason but you can still access TWRP try pushing the rom to internal storage by using fastboot again. Boot to TWRP on your phone and do nothing else. On your Windows machine open fastboot and type "adb push *rom name*.zip /data/media/0" this will push the rom to your internal storage.
Click to expand...
Click to collapse
Thank you very much! Sideloading rom worked for me (OP6T).