softbrick woes - Nexus S Q&A, Help & Troubleshooting

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.

Related

adb and ruu problems

Hi!
First of i got a Htc one S from sweden and have been using utb rom for the last weeks with CWR Touch. After hearing that Cyanigenmod 10 was not as buggy as i thought i decided to use it.
This is what i did:
Downloaded the rom with rom manger - the phone restarted and viped everythig and started to install. It then aborted because of something wrong with the file.
Now i dont have a rom on my phone and i cant acces my SD card where i got other roms waiting for me to install.
When i try to use any ADB commands like "adb devices" nothing shows up under devices.
I tried "adb kill-server" and "adb devices" still nothing. When i use "fastboot devices" my device shows. I have tried both Hboot and Fastboot.
I tried to use one guide i found where someone used "all in one toolkit" to go back to stock recovery, delete space, re-enter recovery but that did not work for me.
I tried to adb push roms to my phone but still, no luck because my phone cant be found.
I tried to use the software "quick adb pusher" and with it i could se my device show and i could acces the storage, but there is a folder named "error device not found".
I tried to use "all in one toolkit" so i atleast could get CWR back on my phone, it flashes and finds my device, but when i try to rebot to recovery nothing happens anymore.
Do anyone have a fix for this? 7h later and im out of ideas.....what ever small ammount of knowledge i have about this ended hours ago and google cant help me anymore.
I even tried to download a ruu to try and install it but keeps telling me its the wrong version and then the installation aborts.
i have htc sync and htc usb drivers.
I also downloaded....well atleast 15 diffrent drivers and tried them still no adb device found.
I tried to download android atk but it complains about me not having java runtime but i installed it.
Im using windows 7 x64 bootcamp and osx
aasterix said:
Now i dont have a rom on my phone and i cant acces my SD card where i got other roms waiting for me to install.
Click to expand...
Click to collapse
In fastboot you can flash boot images and recoveries.
You can only use ADB when booted (which you can't) or when in recovery.
If you are unable to mount /sdcard in recovery, check the sticky on how to fix unmountable sdcard. It's here in Q&A.
Once you can mount /sdcard in recovery, you can adb push roms to it. You have to be in recovery for that, not in fastboot. First flash the boot image for your rom from fastboot, then boot into recovery and push and flash the rom. Wipe your data and cache.
You can do this either on windows or osx but on osx you dont need drivers so you can't have the wrong ones.
Good hunting,
-Jobo
The CWM version shipped with all-in-one doesn't work. CWM doesn't mount the sdcard anyway. I'd suggest TWRP because it can mount the sdcard and also has other features that CWM lacks.
Just boot into bootloader and in fastboot:
fastboot flash recovery twrpfilename.img
Then do as jobo said within the recovery.
Sent from my HTC One S
Pheroh said:
CWM doesn't mount the sdcard anyway.
Click to expand...
Click to collapse
What I meant, and what I think aasterix meant as well, is not mount the sdcard onto your computer over usb, but just mount the sdcard onto the root filesystem in recovery on the device.
If that doesn't work, you have to fix that first using '[HOW-TO] Fix soft brick & error mounting sdcard'. Once you can mount /sdcard in recovery (any custom recovery will do) you're good to push and flash your favorite rom.

[Q] Really Hard Brick.. I think..

HELP TO ALL THE COMMUNITY ASAP!!!
here is the deal, i had the HTC One S Rooted fine, it was working but i tried now to install a custom rom, baked black beans, but now i've downloaded the rom, set it in my HTC, accessed CMW, wiped data, installed from sd, rebooted, went to bootloader, run boot.img on cmd on computer, restarted and now i am getting the HTC Bootloader that states that "This build is for development purporses etc. etc.." now here is the deal guys... i was able to get to bootloader then to recovery, i check the sd files in clockwork recovery and nothing!! all i want now is just stock and try again.. guys.. help???
URGENT!!
therion0 said:
HELP TO ALL THE COMMUNITY ASAP!!!
here is the deal, i had the HTC One S Rooted fine, it was working but i tried now to install a custom rom, baked black beans, but now i've downloaded the rom, set it in my HTC, accessed CMW, wiped data, installed from sd, rebooted, went to bootloader, run boot.img on cmd on computer, restarted and now i am getting the HTC Bootloader that states that "This build is for development purporses etc. etc.." now here is the deal guys... i was able to get to bootloader then to recovery, i check the sd files in clockwork recovery and nothing!! all i want now is just stock and try again.. guys.. help???
URGENT!!
Click to expand...
Click to collapse
CWM cant mount SD you need TWRP for that and a RUU put you back to stock but the bootloader needs relocking. So did you even try booting the rom because the red writing is fine.
you didn't mention it, but you should wipe system and caches as well as data
Not hard brick. you can chose the correct Ruu file and flash it to your phone.... solved your case.
Darknites said:
CWM cant mount SD you need TWRP for that
Click to expand...
Click to collapse
CWM can not mount our sdcard onto your computer over USB.
But it absolutely can mount the sdcard partition onto the root filesystem.
Unless you have the 'unmountable sdcard' problem, for which there is a sticky in Q&A.
My feeling is that the OP didnt mount the sdcard partition. In that case it is normal to see the mount point as an empty folder.
Once it's mounted, you can adb push rom zips to it.
touch of jobo said:
CWM can not mount our sdcard onto your computer over USB.
But it absolutely can mount the sdcard partition onto the root filesystem.
Unless you have the 'unmountable sdcard' problem, for which there is a sticky in Q&A.
My feeling is that the OP didnt mount the sdcard partition. In that case it is normal to see the mount point as an empty folder.
Once it's mounted, you can adb push rom zips to it.
Click to expand...
Click to collapse
Oh right seems a lot work lol, I think I stick to TWRP.
Darknites said:
Oh right seems a lot work lol, I think I stick to TWRP.
Click to expand...
Click to collapse
+1, 2 & 3!
Really don't understand why anyone still uses CWM, I think its just habit with some people.
shadowch31 said:
+1, 2 & 3!
Really don't understand why anyone still uses CWM, I think its just habit with some people.
Click to expand...
Click to collapse
Habit and guides.
I thought I saw a post that mentioned cwm has not kept up to date--not sure
But, I was a slow convert too and very happy with twrp 2.2.2.0
rugmankc said:
I thought I saw a post that mentioned cwm has not kept up to date--not sure
But, I was a slow convert too and very happy with twrp 2.2.2.0
Click to expand...
Click to collapse
I not seen updates but then I not looked and I didn't move over in till it got the usb mount.
when i run the CMD Command prompt adb reboot bootloader I get error: device not found, i was able to flash the boot.img and i got the 2 OKs but i get that error now... what now?
Also, when i go to recovery mode, i don't see any files to install the .zip file of the rom i want to install
therion0 said:
Also, when i go to recovery mode, i don't see any files to install the .zip file of the rom i want to install
Click to expand...
Click to collapse
You lost SD then and best off running a RUU to recover it.
ok i'm lost.. how do i run an RUU to recover it?
therion0 said:
ok i'm lost.. how do i run an RUU to recover it?
Click to expand...
Click to collapse
Download the right RUU for your carrier and location by looking at http://forum.xda-developers.com/showthread.php?t=1543588 and you can get free download at http://www.4shared.com/folder/jKN2qjTl/HTC_Ville_RUU_Collection.html
Then plug in your phone and follow the instructions when you run the RUU .exe file.
AKToronto
but everytime i try to run it, it says it fails because the phone it is not connected to the computer but it is...
did you ever try to boot into the rom after you flashed it and boot image as in just tapping on reboot system
can you plug phone into pc and get indicator at top of screen that says you are connected. then pull down notification bar and select to mount drive
if so, does it show you your sdcard in the windows screen
you do have an S4 device and assume you are hboot .13 or higher
if you can get into os and see sdcard, you can get twrp and flash image gui and flash rom and boot image with it
i am sure you tried these things, just hard to know when reading posts
also, i don't know if you are running your commands correctly based on how i undestand your posts. you can't run adb commands from fastboot, which is what you were in to fastboot boot image. you would want to type fastboot reboot-bootloader
if you are very familiar with adb/fastboot--sorry. if not need to get up to speed on them
if i misread or misunderstood any of this, sorry for butting in--
rugmankc said:
did you ever try to boot into the rom after you flashed it and boot image as in just tapping on reboot system
can you plug phone into pc and get indicator at top of screen that says you are connected. then pull down notification bar and select to mount drive
if so, does it show you your sdcard in the windows screen
you do have an S4 device and assume you are hboot .13 or higher
if you can get into os and see sdcard, you can get twrp and flash image gui and flash rom and boot image with it
i am sure you tried these things, just hard to know when reading posts
also, i don't know if you are running your commands correctly based on how i undestand your posts. you can't run adb commands from fastboot, which is what you were in to fastboot boot image. you would want to type fastboot reboot-bootloader
if you are very familiar with adb/fastboot--sorry. if not need to get up to speed on them
if i misread or misunderstood any of this, sorry for butting in--
Click to expand...
Click to collapse
Ya he messed it up so needs RUU. He has PM me just waiting on a reply.

[Q] Bootloop with no Rom installed

Could any one help me please?
I unlocked my bootloader using the One Tool. Installed CWM recovery but I formatted the whole device with no Rom or back up. I then tried to run a RUU (RUU_Ville_U_JB_45_S_HTC_Europe_3.16.401.8_Radio_1.11.50.05.28_10.27.50.08L_release_301814_signed_2_4) to restore it all back to to stock. But it only send me to a black HTC screen. Nothing else.
When I try to install the stock recovery the One Tool can not find the the phone.
Can anyone help at all please?
Does anyone know how I can bring it at least to a working order?
Vivimagic said:
Installed CWM recovery but I formatted the whole device with no Rom or back up.
Does anyone know how I can bring it at least to a working order?
Click to expand...
Click to collapse
At this point you can adb push a custom rom zip to your sdcard (mount it in recovery first) and flash it. Then boot back into bootloader and fastboot flash the boot.img from the rom.
Alternatively, you can adb push a system.img extracted from a RUU to your sdcard and then dd it into /dev/block/mmcblk0p33
touch of jobo said:
At this point you can adb push a custom rom zip to your sdcard (mount it in recovery first) and flash it. Then boot back into bootloader and fastboot flash the boot.img from the rom.
Alternatively, you can adb push a system.img extracted from a RUU to your sdcard and then dd it into /dev/block/mmcblk0p33
Click to expand...
Click to collapse
Well that is the problem I can't mount the SD card via Recovery! Other. I have also tried to sideload a Rom as well.
Vivimagic said:
Well that is the problem I can't mount the SD card via Recovery! Other. I have also tried to sideload a Rom as well.
Click to expand...
Click to collapse
It is normal that you can't mount your sdcard onto your PC over USB in recovery, but you should be able to just mount it onto the root filesystem, so that you can adb push. Do you get an error message when trying to mount the sdcard in recovery? If you do, there is a sticky for that here in the Q&A forum. It comes down to flashing a stock recovery and then clearing storage or performing a factory reset in bootloader.
touch of jobo said:
It is normal that you can't mount your sdcard onto your PC over USB in recovery, but you should be able to just mount it onto the root filesystem, so that you can adb push. Do you get an error message when trying to mount the sdcard in recovery? If you do, there is a sticky for that here in the Q&A forum. It comes down to flashing a stock recovery and then clearing storage or performing a factory reset in bootloader.
Click to expand...
Click to collapse
Ah ok. I do get a problem with Windows install the HTC MTP drivers when I am in Recovery. Basically I can't turn on USB debugging because there is no Rom to tell it to be in that mode, and that is why it thinks it is an MTP device!
Yes the error on CWM is "E: Can't mount <location>
I think I need to sort out the driver before I can start flashing the stock recovery.
I have tried to return the recovery to stock but it just won't send it to my phone. I can however mount it a disk drive via CWM.
Vivimagic said:
Ah ok. I do get a problem with Windows install the HTC MTP drivers when I am in Recovery. Basically I can't turn on USB debugging because there is no Rom to tell it to be in that mode, and that is why it thinks it is an MTP device!
Yes the error on CWM is "E: Can't mount <location>
I think I need to sort out the driver before I can start flashing the stock recovery.
I have tried to return the recovery to stock but it just won't send it to my phone. I can however mount it a disk drive via CWM.
Click to expand...
Click to collapse
You don't need debugging to use adb in recovery, recovery already has adb. Have you tried "adb push rom.zip /sdcard/rom.zip" while in recovery?
I had the same problem and this post helped me immensly
http://www.htconeforum.com/forum/ht...unbrick-restore-htc-one-s-stock-relocked.html
Mine is a US RUU though so you might need to find a European RUU

[Q] Help - Rooting gone wrong

So I got the HTC One s and try to root it with the following instruction: http://forum.xda-developers.com/showthread.php?t=1583427&__utma=248941774.997411949.1390324490.1394471756.1396118873.6&__utmb=248941774.2.10.1396118873&__utmc=248941774&__utmx=-&__utmz=248941774.1394471756.5.2.utmcsr=feedburner|utmccn=Feed:%20xda-developers/ShsH%20(xda-developers)|utmcmd=feed&__utmv=-&__utmk=25799614
As I thought that Step 3 was only there to install the Superuser.apk i just skipped it (mistake no. 1) and wiped the whole thing (without making a backup --> mistake no. 2) and tried to install the Maximus HD Rom which as I am still S-On of course didnt work. So I wiped again but really careless and made mistake no. 3: wiping the whole thing instead of just a few partitions like system, cache,....
So now I have my device S-On, theres really nothing on it exept TWRP but there (and in other recoverys I tried) the USB mout doesnt work so I cant get a new rom on it So I tried to push it through fastboot but I cant find a fitting command.
Any advice what I can do to either get the USB work in the recoverys or push it through fastboot and which rom works without S-Off?
If you need further infos Id like to give those!
Akkordinator said:
So I got the HTC One s and try to root it with the following instruction: http://forum.xda-developers.com/showthread.php?t=1583427&__utma=248941774.997411949.1390324490.1394471756.1396118873.6&__utmb=248941774.2.10.1396118873&__utmc=248941774&__utmx=-&__utmz=248941774.1394471756.5.2.utmcsr=feedburner|utmccn=Feed:%20xda-developers/ShsH%20(xda-developers)|utmcmd=feed&__utmv=-&__utmk=25799614
As I thought that Step 3 was only there to install the Superuser.apk i just skipped it (mistake no. 1) and wiped the whole thing (without making a backup --> mistake no. 2) and tried to install the Maximus HD Rom which as I am still S-On of course didnt work. So I wiped again but really careless and made mistake no. 3: wiping the whole thing instead of just a few partitions like system, cache,....
So now I have my device S-On, theres really nothing on it exept TWRP but there (and in other recoverys I tried) the USB mout doesnt work so I cant get a new rom on it So I tried to push it through fastboot but I cant find a fitting command.
Any advice what I can do to either get the USB work in the recoverys or push it through fastboot and which rom works without S-Off?
If you need further infos Id like to give those!
Click to expand...
Click to collapse
TWRP has ADB Sideload feature. Means you can flash zips using adb. Of course you can flash a roms this but keep in mind you have to flash the kernel (boot.img) manually immediately after flashing the rom.zip. When flashed Rom.zip by using ADB sideload method make SURE that you direct go into fastboot mode and flash the kernel (fastboot flash boot boot.img) (you can extract the boot.img from your rom.zip)
May be a compatible rom this time? But you're lucky -> Infact you already deleted everything you won't have to perform a wipe before flashing lol
LS.xD said:
Of course you can flash a roms
Click to expand...
Click to collapse
Ok, but I dont know with which command (fastboot flash what? or adb?)
You can use adb sideload as followed:
Start TWRP -> advanced -> ADB sideload + swipe to activate it. Connect your phone to the computer. Open "CMD Commandline" and type "adb sideload ROMNAME.zip"
Of course "ROMNAME" has to match the zip you want to flash. Thats it
In twrp go to "REBOOT" -> "fastboot"
When fastboot usb is ready use CMD commandline again and type "fastboot flash boot boot.img"
Then you can boot android
I whished I could. As I start ADB sideload it keeps doing nothing at all until I abort it. What I think is important to know is that it is then:
"E:Unable to mout '/internal_sd'
E:Unable to mount storage.", which I think is the problem.
Flash Stock recovery And perform "factory Reset + clear storage" that will fix your storage. Then flash twrp Version 2.7 again and do what I suggested to flash the Rom
Sent from my beloved HTC One S using (most time buggy) Tapatalk
Did the exact thing which removes the mounting error, but this has no effect on the sideload (or usb mount). Still not working.
Akkordinator said:
Did the exact thing which removes the mounting error, but this has no effect on the sideload (or usb mount). Still not working.
Click to expand...
Click to collapse
Can you acces your sdcard by twrp? Lot of poeple here has sd card bug yet and it was fixed everytime.
You're facing sdcard bug.
This is how to solve:
1. Flash stock recovery
2. reboot to bootloader and perform "factory reset + clear storage" (While in bootloader NOT in recovery)
3. Flash custom recovery again
4. Reboot recovery - mount usb storage - copy ROM.zip to sdcard // adb sideload rom
7. NOW boot android (Not at any time before! Even there is no system installed)
Please just repeat it.
LS.xD said:
Can you acces your sdcard by twrp? Lot of poeple here has sd card bug yet and it was fixed everytime.
Click to expand...
Click to collapse
I can acces it in TWRP (of course only a TWRP folder in it). Tried the repeating progress over and over but nothing changes. And USB-OTG isnt able to mount.
Thanks for your patient help!
Akkordinator said:
I can acces it in TWRP (of course only a TWRP folder in it). Tried the repeating progress over and over but nothing changes. And USB-OTG isnt able to mount.
Thanks for your patient help!
Click to expand...
Click to collapse
In case you can acces the storage in twrp its related to windows or drivers. What windows version you are running?
LS.xD said:
In case you can acces the storage in twrp its related to windows or drivers. What windows version you are running?
Click to expand...
Click to collapse
It was windows! Tried it on the other computer with win7 instead of 8.1 and I finally got a connection!
Thanks so much!!!

Help! Deleted EVERYTHING on ZTE N817

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!

Categories

Resources