Good day to y'all!
So... I did a thing. I pressed a button in TWRP without knowing what I was doing, and accidentally wiped my whole phone. And I mean, like, the entire thing.
I'm pretty sure I even managed to wipe TWRP after this, as I can no longer find a way to boot into it.
I've tried several things to fix this, namely the following:
-Flashing stock firmware using power+vol up+vol down. (says the update package isn't valid, I have a VNS-L31 and have tried every version of L31 firmware I could find.)
-Downloading a firmware update using eRecovery. (says getting package info failed.)
-Using fastboot to install TWRP.
Now, on this last one is where I'm stuck. My phone isn't being recognized by ADB anymore (it was before).
I've tried reinstalling my fastboot drivers, and my phone's USB drivers with no luck whatsoever.
If I could manage to get ADB to recognize my phone, I'm pretty sure I'd be able to flash TWRP and then a different ROM with that.
As aforementioned, I have a VNS-L31, Europe, Dual SIM w/ 3GB of RAM.
Very much lost on what to do, any help will be much appreciated!
Nantonix said:
Good day to y'all!
So... I did a thing. I pressed a button in TWRP without knowing what I was doing, and accidentally wiped my whole phone. And I mean, like, the entire thing.
I'm pretty sure I even managed to wipe TWRP after this, as I can no longer find a way to boot into it.
I've tried several things to fix this, namely the following:
-Flashing stock firmware using power+vol up+vol down. (says the update package isn't valid, I have a VNS-L31 and have tried every version of L31 firmware I could find.)
-Downloading a firmware update using eRecovery. (says getting package info failed.)
-Using fastboot to install TWRP.
Now, on this last one is where I'm stuck. My phone isn't being recognized by ADB anymore (it was before).
I've tried reinstalling my fastboot drivers, and my phone's USB drivers with no luck whatsoever.
If I could manage to get ADB to recognize my phone, I'm pretty sure I'd be able to flash TWRP and then a different ROM with that.
As aforementioned, I have a VNS-L31, Europe, Dual SIM w/ 3GB of RAM.
Very much lost on what to do, any help will be much appreciated!
Click to expand...
Click to collapse
adb only works if the phone is booted to android, if you can boot onto fastboot you should be able to flash twrp and then flash oeminfo for your phone, and then use the dload/update.app to flash the stock rom
mjz2cool said:
adb only works if the phone is booted to android, if you can boot onto fastboot you should be able to flash twrp and then flash oeminfo for your phone, and then use the dload/update.app to flash the stock rom
Click to expand...
Click to collapse
That's what I was trying to do. Thing is, I can't connect it to my PC at all. I can boot into fastboot (by holding the vol down button and then connecting it), but my PC doesn't detect anything.
Nantonix said:
That's what I was trying to do. Thing is, I can't connect it to my PC at all. I can boot into fastboot (by holding the vol down button and then connecting it), but my PC doesn't detect anything.
Click to expand...
Click to collapse
(if you use windows) have you tried looking in device manager? is the device recognized?
mjz2cool said:
(if you use windows) have you tried looking in device manager? is the device recognized?
Click to expand...
Click to collapse
It isn't, no. I have the USB drivers installed.
Nantonix said:
It isn't, no. I have the USB drivers installed.
Click to expand...
Click to collapse
i had a similar issue a while back, mine showed up in device manager with an error, and i uninstalled the driver from there, then completely uninstalled hisuite, and then reinstalled hisuite, after that, it did get recognized and i could use fastboot flash again. (however, i did have to oem unlock eventhough the phone said it was unlocked)
mjz2cool said:
i had a similar issue a while back, mine showed up in device manager with an error, and i uninstalled the driver from there, then completely uninstalled hisuite, and then reinstalled hisuite, after that, it did get recognized and i could use fastboot flash again. (however, i did have to oem unlock eventhough the phone said it was unlocked)
Click to expand...
Click to collapse
I'll try doing so later today! I'll report back once I have, to let you know if it worked or not.
mjz2cool said:
i had a similar issue a while back, mine showed up in device manager with an error, and i uninstalled the driver from there, then completely uninstalled hisuite, and then reinstalled hisuite, after that, it did get recognized and i could use fastboot flash again. (however, i did have to oem unlock eventhough the phone said it was unlocked)
Click to expand...
Click to collapse
Alright, so. Minor progress has been made.
I uninstalled HiSuite, and my fastboot drivers successfully. I then reinstalled HiSuite, and when I connect my phone in fastboot/rescue mode, HiSuite starts.
I, however, haven't been able to reinstall my fastboot drivers. The device is under the "unspecified" section, is called "Fastboot2.0", and windows reports there aren't any drivers installed.
Any idea where I can find the proper fastboot drivers?
Nantonix said:
Alright, so. Minor progress has been made.
I uninstalled HiSuite, and my fastboot drivers successfully. I then reinstalled HiSuite, and when I connect my phone in fastboot/rescue mode, HiSuite starts.
I, however, haven't been able to reinstall my fastboot drivers. The device is under the "unspecified" section, is called "Fastboot2.0", and windows reports there aren't any drivers installed.
Any idea where I can find the proper fastboot drivers?
Click to expand...
Click to collapse
hisuite should install the proper drivers, try updating the driver in device manager (right click - update). i will take a look on my own pc when i get home
mjz2cool said:
hisuite should install the proper drivers, try updating the driver in device manager (right click - update). i will take a look on my own pc when i get home
Click to expand...
Click to collapse
Okay, so.
I installed the latest version of HiSuite, and my drivers have now been installed. (or so it seems.)
The device is still listed as "unspecified", but in the properties tab it says "Name: Android Sooner Single ADB Interface - Type: Android Phone".
However, ADB still does not detect my device, and HiSuite says it isn't connected.
Nantonix said:
Okay, so.
I installed the latest version of HiSuite, and my drivers have now been installed. (or so it seems.)
The device is still listed as "unspecified", but in the properties tab it says "Name: Android Sooner Single ADB Interface - Type: Android Phone".
However, ADB still does not detect my device, and HiSuite says it isn't connected.
Click to expand...
Click to collapse
did you use adb devices? or fastboot devices? it is correct that both adb and hisuite don't detect your device as it isn't booted into android
mjz2cool said:
did you use adb devices? or fastboot devices? it is correct that both adb and hisuite don't detect your device as it isn't booted into android
Click to expand...
Click to collapse
OH!
I got confused there, bahaha. I was using adb devices.
After typing fastboot devices, it now detects my phone.
I'll try flashing TWRP, I have a recovery.img left over on my desktop. Report back once I've done so!
mjz2cool said:
did you use adb devices? or fastboot devices? it is correct that both adb and hisuite don't detect your device as it isn't booted into android
Click to expand...
Click to collapse
SUCCESS! TWRP has been flashed onto my phone.
Apparently though, the battery's drained >_>
I'll leave it to charge for a few minutes as I throw stock firmware onto my microSD, and then try to install it, as I have a southeast asia VNS-L31 firmware package saved.
Nantonix said:
SUCCESS! TWRP has been flashed onto my phone.
Apparently though, the battery's drained >_>
I'll leave it to charge for a few minutes as I throw stock firmware onto my microSD, and then try to install it, as I have a southeast asia VNS-L31 firmware package saved.
Click to expand...
Click to collapse
if you flash oeminfo for c432, you can use the europe version of the update.app, and put that in dload, it should be around here somewhere on this forum
mjz2cool said:
if you flash oeminfo for c432, you can use the europe version of the update.app, and put that in dload, it should be around here somewhere on this forum
Click to expand...
Click to collapse
I've been searching for the Europe update.app, couldn't find it anywhere.
Any idea where I can find southeast asia OEMinfo? I wouldn't mind using it that way. The only disadvantage would be I can only use one SIM, which I do anyway.
mjz2cool said:
if you flash oeminfo for c432, you can use the europe version of the update.app, and put that in dload, it should be around here somewhere on this forum
Click to expand...
Click to collapse
I found the C432 OEMinfo, and the Europe-bound UPDATE.APP.
However, I have absolutely no ****ing clue how to flash the OEMinfo onto my phone. Could you guide me through the process?
Well, Never mind.
I managed to install Meticulus' TWRP, and CyanogenMod.
Everything is working as intended again! ^^
Nantonix said:
Well, Never mind.
I managed to install Meticulus' TWRP, and CyanogenMod.
Everything is working as intended again! ^^
Click to expand...
Click to collapse
if you decide to flash stock, you can flash the oeminfo file with twrp, and then put the update.app in dload on your sdcard.
btw, how is cyanogenmod working for you? i've tried it before, but the batterylife seems to be quite less than i'm used to with emui.
also, when you turn on the screen, does it still show static for a fraction of a second?
mjz2cool said:
if you decide to flash stock, you can flash the oeminfo file with twrp, and then put the update.app in dload on your sdcard.
btw, how is cyanogenmod working for you? i've tried it before, but the batterylife seems to be quite less than i'm used to with emui.
also, when you turn on the screen, does it still show static for a fraction of a second?
Click to expand...
Click to collapse
Everything's working fine for me! Battery seemed bad at first, but after having charged a few times the drain slows down drastically below 50%. It takes about 6 hours to get from 50 to 0 with full use. It probably just isn't displaying correctly.
Apart from that, everything works! Running it with a custom theme/navbar and everything. No problems whatsoever
Nantonix said:
Everything's working fine for me! Battery seemed bad at first, but after having charged a few times the drain slows down drastically below 50%. It takes about 6 hours to get from 50 to 0 with full use. It probably just isn't displaying correctly.
Apart from that, everything works! Running it with a custom theme/navbar and everything. No problems whatsoever
Click to expand...
Click to collapse
okay thanks! will try a few days more this time ^^
Related
since i somehow managed to lose the ability to connect via fastboot..
is there another way for me to install zips?
phone rooted with 1 click..
also open to ideas as to why fast boot only says < waiting for device > now?
no conflicts in dev mgr, have uninstalled and reinstalled the sync and driver..
removed from dev mgr..
updated while in fastboot mode etc..
no dice..
318-us
official 2.2 rom
att unlocked.
Black
can i convert a zip to a pkg and rename it update.pkg?
right now all i have is the pkg option when i hold the vol buttons and power.
i recently flashed to the new update which had fixes and newer baseband etc..
that went fine but the the steve 1.5 came out and i want to switch back.
as stated above thats not possible now since fastboot refuses to see my device.
Can someone put it in a pkg format for me maybe?
I dont like this official release...
its slow..it has lame apps, etc..
lil help?
dont really want to formate my laptop to fix a usb driver issue..
especially when the mass storage and sync work just fine..
+1
cant use fastboot after update to 318
rooted by super one click
black
unlock 00
there is a way of flashing custom recovery via terminal emulator. DEVICE NEEDS TO BE ROOT'D
save .img on to SDcard and rename to recovery.img
then open terminal emulator and type
su (press enter)
flash_image recovery /sdcard/recovery.img (press enter)
reboot (press enter)
I had the waiting for device problem. I read a few tips saying to try...
Type "adb devices" to see if its recognised there.
Make sure streak is the only device plugged in usb.
If using a hub try a different slot or direct into pc.
Turn streak off and into fastboot while still connected to pc (after pc loads drivers)
Reboot pc.
I swapped usb soccets and that fixed it for me
Hope one of these tips works for you too.
Thank you. I actually tried all of those things...before i posted.
wondering if maybe the 318 isn't compatible..
it says its in fastboot mode..
everything else works..sync, sd card shows in explorer etc etc..
just no fastboot.
luckily the recovery still allows me to do .pkg but i need zips too
very annoying..
I ordered a M11XR2 and will try with that when it arrives..
tina333 said:
I had the waiting for device problem. I read a few tips saying to try...
Type "adb devices" to see if its recognised there.
Make sure streak is the only device plugged in usb.
If using a hub try a different slot or direct into pc.
Turn streak off and into fastboot while still connected to pc (after pc loads drivers)
Reboot pc.
I swapped usb soccets and that fixed it for me
Hope one of these tips works for you too.
Click to expand...
Click to collapse
I have 318 and fastboot works for me.
I only had to reconnect the adb bootloader interface driver again (just like I had to the very first time).
It is just fine now...
http://forum.pocketables.net/showthread.php?t=8285
I've not had any issues with fastbooting, after installing 318, I've managed to flash clockworkmod aswell as the new Streakmod recoveries with my Windows 7 64bit.
reconnect the adb bootloader???
what do you mean?
you mean you plugged the usb cable in and ran fastboot?
lol
yeah..thats helpful
Radimus said:
I only had to reconnect the adb bootloader interface driver again (just like I had to the very first time).
It is just fine now...
http://forum.pocketables.net/showthread.php?t=8285
Click to expand...
Click to collapse
bigfoots1 said:
reconnect the adb bootloader???
what do you mean?
you mean you plugged the usb cable in and ran fastboot?
lol
yeah..thats helpful
Click to expand...
Click to collapse
NO....
The streak wasn't recognized on the PC in fastboot mode, so I went back to device manager and found the unrecognized android device and set it to use the bootloader driver... The same proceedure as was done the first time the streak was connected to a PC to setup fastboot.
Took almost 30 seconds to fix
as i said though.. i have no conflicts...
I can even remove it from the device mgr...put eh phone in fastboot mode where it is waiting for usb coinnection..plug the phone in.. iot installs the drivers then the phone sees this and shows fast boot...
so you would expect it to work right? wrong... it says waiting for device...
I have tried everything I can think of..
i got a good deal on a new m11xr2 with win 7 so i will have a fresh slate and will see what results i can get.
in the mean time.. how can i convert this steve 1.5.zip to a .pkg?
or even install it with some other sokution or method?
i have it rooted via one click...
i have root explorer...
what now? lol
there has to be a better way..
Radimus said:
NO....
The streak wasn't recognized on the PC in fastboot mode, so I went back to device manager and found the unrecognized android device and set it to use the bootloader driver... The same proceedure as was done the first time the streak was connected to a PC to setup fastboot.
Took almost 30 seconds to fix
Click to expand...
Click to collapse
Its easy to miss bits when its all going wrong so do check the sticky look here first for streak, I had to refer to it a few times. You definitely need clockworkmod or streakmod to flash updates. I believe you can do it via a terminal app with su privileges. There's a thread from a few hrs ago saying. I will find for you if you can't
Can zip be extracted and converted to .pkg?
Hell I would be content with just a way to install the performance tweaks...thats the main issue really...
Sent from my Dell Streak using Tapatalk
bigfoots1 said:
Can zip be extracted and converted to .pkg?
Hell I would be content with just a way to install the performance tweaks...thats the main issue really...
Sent from my Dell Streak using Tapatalk
Click to expand...
Click to collapse
I know Steve mentions "if you haven't flashed official dell update" blah blah... so im guessing you don't loose performance unless you manually downgrade? Have you seen the thread I mentioned? The OP claims he changed the dell .pkg to .zip and successfully flashed via clockwork..
http://forum.xda-developers.com/showthread.php?t=869076
how does that help me?
when i power up holding the vol up and down buttons i only get the install Update.pkg option and when i choose it it takes me to the blue text screen when i choose to either update via pkg or reboot. its the Android system recovery utility GAUSB1A131800
there is no option or way to get an option to install zip.
I would like to be able to install the performance fix for 2.2 zip or steves 1.5zip
so do you understand now?
I cant get fastboot to work to install clockwork.
I only have the recovery utility...
tina333 said:
I know Steve mentions "if you haven't flashed official dell update" blah blah... so im guessing you don't loose performance unless you manually downgrade? Have you seen the thread I mentioned? The OP claims he changed the dell .pkg to .zip and successfully flashed via clockwork..
http://forum.xda-developers.com/showthread.php?t=869076
Click to expand...
Click to collapse
it seems like i remember a thread about converting zip to pkg..
I cant seem to find it though..
if you just rename it in root explorer you get a signing validation error when you try to install it..
so I'm still stuck on stock 2.2
The initial thread is irrelevant, Have you not flashed a clockworkmod or streakmod previously? I would guess its possible to store a recovery.img on sd then flash via terminal app, i cant see why not? You could also probably use adb (if you cant connect to that the theres apps to do it wirelessly)
yes, i have flashed many times...
I flashed to 309 recovery in order to install the latest dell Update.pkg which went just fine. then when i went back to flash clockwork i could no longer connect via fastboot.
and thats where im at now..
cannot get fastboot to flash clockwork so i can install zips..
hence im asking for a way to do it without clockwork/fastboot until i get that sorted..
tina333 said:
The initial thread is irrelevant, Have you not flashed a clockworkmod or streakmod previously? I would guess its possible to store a recovery.img on sd then flash via terminal app, i cant see why not? You could also probably use adb (if you cant connect to that the theres apps to do it wirelessly)
Click to expand...
Click to collapse
an I still believe the issue is that you do not have the correct bootloader driver installed on your PC as described here:
http://forum.xda-developers.com/attachment.php?attachmentid=397078&d=1283901727
The issue is your PC, not the Streak (most likely)
Hi,
I recently updated to the official 4.4.2 kitkat update.I then proceeded to root the phone, and then stupidly, installed CWM. I rebooted, and was greeted with an endless LG Splash screen. Now, I tried a HEAP of ways to restore to stock, all of them returning the same problem, my computer won't pick up my phone. In download mode, nothing happens, nothing in device manager, and same when I'm stuck on the LG splash screen. When I go into CWM, it then recogizes my phone, but the methods of restoring to stock won't work with CWM running in the background. CWM also won't let me mount the usb...
The methods return the same error: Phone not detected, please plug the USB cable and retry.
Ubuntu won't recognize the phone in all three modes, and another computer does the same thing. (Both Windows 8)
Methods of stock restoration tried:
-KDZ
-LGMobile support tool
-Ubuntu (This: http://forum.xda-developers.com/showthread.php?t=2582142)
Can anyone help?
MintLord said:
Hi,
I recently updated to the official 4.4.2 kitkat update.I then proceeded to root the phone, and then stupidly, installed CWM. I rebooted, and was greeted with an endless LG Splash screen. Now, I tried a HEAP of ways to restore to stock, all of them returning the same problem, my computer won't pick up my phone. In download mode, nothing happens, nothing in device manager, and same when I'm stuck on the LG splash screen. When I go into CWM, it then recogizes my phone, but the methods of restoring to stock won't work with CWM running in the background. CWM also won't let me mount the usb...
The methods return the same error: Phone not detected, please plug the USB cable and retry.
Ubuntu won't recognize the phone in all three modes, and another computer does the same thing. (Both Windows 8)
Methods of stock restoration tried:
-KDZ
-LGMobile support tool
-Ubuntu (This: http://forum.xda-developers.com/showthread.php?t=2582142)
Can anyone help?
Click to expand...
Click to collapse
Have you tried adb sideload
raahult said:
Have you tried adb sideload
Click to expand...
Click to collapse
I don't know how to do that, And no, I don't think I have. Could you give me a guide on doing that?
MintLord said:
I don't know how to do that, And no, I don't think I have. Could you give me a guide on doing that?
Click to expand...
Click to collapse
Install http://forum.xda-developers.com/showthread.php?t=2588979
then go to recovery and try adb devices on command prompt on your PC to check if your device is listed
if it shows your devices then just search any thread that tell how to push flashable rom to your device.
raahult said:
Install http://forum.xda-developers.com/showthread.php?t=2588979
then go to recovery and try adb devices on command prompt on your PC to check if your device is listed
if it shows your devices then just search any thread that tell how to push flashable rom to your device.
Click to expand...
Click to collapse
No luck...
raahult said:
Install http://forum.xda-developers.com/showthread.php?t=2588979
then go to recovery and try adb devices on command prompt on your PC to check if your device is listed
if it shows your devices then just search any thread that tell how to push flashable rom to your device.
Click to expand...
Click to collapse
Wait, I got it working!
MintLord said:
Wait, I got it working!
Click to expand...
Click to collapse
Was your phone able to connect to the PC afterwards? I have a D800 that I am unable to get any PC to recognize. I need to restore it to stock but no matter what I do it does not show up in device manager (and I have a working rom on it).
crawlgsx said:
Was your phone able to connect to the PC afterwards? I have a D800 that I am unable to get any PC to recognize. I need to restore it to stock but no matter what I do it does not show up in device manager (and I have a working rom on it).
Click to expand...
Click to collapse
Yes, it does work now. I was able to restore to stock by adb pushing phillz recovery, and then flashing that, then adb pushing the stock ROM. Everything works as it should, now.
MintLord said:
Yes, it does work now. I was able to restore to stock by adb pushing phillz recovery, and then flashing that, then adb pushing the stock ROM. Everything works as it should, now.
Click to expand...
Click to collapse
Ah nice. Unfortunately I can't get device manager to see mine at all so I can't even ADB .
crawlgsx said:
Ah nice. Unfortunately I can't get device manager to see mine at all so I can't even ADB .
Click to expand...
Click to collapse
Does it recognize your phone when it's in the custom recovery? That was the only way I could do it on my phone.
Good luck!
I tried ADB devices nothing came out.
I have the same problem as listed in this thread. Tried everything to SHort circuit the chip. Basically everything.
I think the last thing i haven't try is dump it into the bin.
MintLord said:
Does it recognize your phone when it's in the custom recovery? That was the only way I could do it on my phone.
Good luck!
Click to expand...
Click to collapse
On TWRP it's detect my phone as "LGE Android MTP device" and i can't copy anything from my PC to my phone,
I can't ADB push too, it was error Read-only system
Any ideas?
Hi, sorry to post in this 1 year old post buy mt G2 is totally dead, I can sometimes get LG Logo and the main problem is i cannot get it into QHS-USB mode or anything.
Is there any key combinaison to do that ?
Hello, I've a problem with my htc U Ultra (ocedugl). In fact, I upgraded supersu and when the phone was supposed to restart, I was stuck at the htc logo. I then had a backup of the boot and the system in reserve on my SD card, but when I wanted to restore them, I had the error 255. Only during the restoration of the system.
I do not know what to do, this phone is a real mystery to me. I have an internship tomorrow, not very practical suddenly. :/
The most problematic in all this is that twrp asks me for a password to decrypt the data at startup and I have the impression that I have only worsened the case. If anyone could help me quickly enough please.
PS: Me who I usually do alone, I must admit that I dry.
PS 2: I installed root switch for snapchat just before too, I do not know if that affects.
SofianeLasri said:
Hello, I've a problem with my htc U Ultra (ocedugl). In fact, I upgraded supersu and when the phone was supposed to restart, I was stuck at the htc logo. I then had a backup of the boot and the system in reserve on my SD card, but when I wanted to restore them, I had the error 255. Only during the restoration of the system.
I do not know what to do, this phone is a real mystery to me. I have an internship tomorrow, not very practical suddenly. :/
The most problematic in all this is that twrp asks me for a password to decrypt the data at startup and I have the impression that I have only worsened the case. If anyone could help me quickly enough please.
PS: Me who I usually do alone, I must admit that I dry.
PS 2: I installed root switch for snapchat just before too, I do not know if that affects.
Click to expand...
Click to collapse
Try TWRP 3.2.1-1
minhnewpro said:
Try TWRP 3.2.1-1
Click to expand...
Click to collapse
Ho to install without an accessible system?
SofianeLasri said:
Ho to install without an accessible system?
Click to expand...
Click to collapse
Turn off your phone. Press Power and volume down at the same time to boot in to download mode. connect to PC and flash TWRP
Install via ADB
Open the folder where your TWRP Recovery .img file is saved.
Then open a CMD window inside that folder. To do that, Shift + Right click on any empty white space inside the folder and then select Open command window here.
Connect your Android device to the PC. Type the following into the command window to boot your device into bootloader/fastboot mode:
Once your device boots into download mode, type this into the command line.
fastboot flash recovery twrp-3.2.1-1.img
Once TWRP is successfully flashed on your device, you can use TWRP now
minhnewpro said:
Turn off your phone. Press Power and volume down at the same time to boot in to download mode. connect to PC and flash TWRP
Install via ADB
Open the folder where your TWRP Recovery .img file is saved.
Then open a CMD window inside that folder. To do that, Shift + Right click on any empty white space inside the folder and then select Open command window here.
Connect your Android device to the PC. Type the following into the command window to boot your device into bootloader/fastboot mode:
Once your device boots into download mode, type this into the command line.
fastboot flash recovery twrp-3.2.1-1.img
Once TWRP is successfully flashed on your device, you can use TWRP now
Click to expand...
Click to collapse
thanks, i have now the twrp-3.2.1-1-oce but it still asks me for a password at startup and my restore still fails with error 255.
SofianeLasri said:
thanks, i have now the twrp-3.2.1-1-oce but it still asks me for a password at startup and my restore still fails with error 255.
Click to expand...
Click to collapse
Maybe you need flash a new rom. Viper, Ledroid,...
minhnewpro said:
Maybe you need flash a new rom. Viper, Ledroid,...
Click to expand...
Click to collapse
Okay, I was saying that too. I try your custom rom then.
PS : Ah, I just saw that the post requests the latest version of the system, except that I do not have access ...
unmout data in internal storage and retore
SofianeLasri said:
Okay, I was saying that too. I try your custom rom then.
PS : Ah, I just saw that the post requests the latest version of the system, except that I do not have access ...
Click to expand...
Click to collapse
You can try flash rom without have same firmware. I'm using Oreo on Nougat firmware
Oh no, I just understand! My SD card seems locked in read only. I really have a bad day me! Between my hard drive doing anything and my phone ... xD
SofianeLasri said:
Oh no, I just understand! My SD card seems locked in read only. I really have a bad day me! Between my hard drive doing anything and my phone ... xD
Click to expand...
Click to collapse
Oh it's good, it was really my card sd the problem.
SofianeLasri said:
Oh no, I just understand! My SD card seems locked in read only. I really have a bad day me! Between my hard drive doing anything and my phone ... xD
Click to expand...
Click to collapse
i don't know what extractly happened with your phone. You can access your storage by connect to PC when your phone in TWRP Recovery. Backup your personal data. Choose wipe => format data => type "yes" => copy Rom into your internal storage or SD Card and flash
minhnewpro said:
i don't know what extractly happened with your phone. You can access your storage by connect to PC when your phone in TWRP Recovery. Backup your personal data. Choose wipe => format data => type "yes" => copy Rom into your internal storage or SD Card and flash
Click to expand...
Click to collapse
No, in fact my sd card is dead. I can't write anymore on. I have save mys backup and restore my system. Thanks for the help!
HTC u ultra Oreo messed up my phone and now I need help.
My story:
Bought a HTC U Ultra European.
I was kind of satisfied with it. The device didn't really live up to my expectations. But when it was upgraded to Oreo the screen start to flash when opening apps and Bluetooth sound went bad. It looks like the app opens twice. After a while it went even worse with the flashing.
Anyways I unlocked the bootloader and flashed TWRP 3.2. That process went fine then I wanted to flash leedroid to test something else (yes I saved a recovery file).
The result is now my device is working but I'm unable to flash twrp again. Since Oreo still sucks to u ultra and I want to downgrade to nougat since it works.
My adb (Linux) detects my device but when I start my HTC in download mode I'm unable to flash to since my PC says:
<waiting for device>
When I try to start it in recovery mode it sticks in a reboot loop.
And BTW I can't restore factory settings.
So if anyone can give me any answers it would be great.
ibringthemadness said:
My story:
Bought a HTC U Ultra European.
I was kind of satisfied with it. The device didn't really live up to my expectations. But when it was upgraded to Oreo the screen start to flash when opening apps and Bluetooth sound went bad. It looks like the app opens twice. After a while it went even worse with the flashing.
Anyways I unlocked the bootloader and flashed TWRP 3.2. That process went fine then I wanted to flash leedroid to test something else (yes I saved a recovery file).
The result is now my device is working but I'm unable to flash twrp again. Since Oreo still sucks to u ultra and I want to downgrade to nougat since it works.
My adb (Linux) detects my device but when I start my HTC in download mode I'm unable to flash to since my PC says:
<waiting for device>
When I try to start it in recovery mode it sticks in a reboot loop.
And BTW I can't restore factory settings.
So if anyone can give me any answers it would be great.
Click to expand...
Click to collapse
Try reinstall driver, buy or borrow an other usb-c cable.
minhnewpro said:
Try reinstall driver, buy or borrow an other usb-c cable.
Click to expand...
Click to collapse
I already installed drivers and tried other cables. Did the procedure again bit with no results.
I think the big problem actually is that since the phone can't boot into recovery mode it get messed up.
I try to do a hard reset but every time I either get stuck in a bootloop or the phone boots into regular mode. So I literally can't do anything to fix this problem as far as I know.
Getting a little bit of frustrated over here.
Why you need reflash TWRP after used Leedroid's rom?
minhnewpro said:
Why you need reflash TWRP after used Leedroid's rom?
Click to expand...
Click to collapse
Because I can't boot to recovery mode. Either I get stuck in a boot loop or the device boots just like I rebooted it. So I can't get to twrp and I can't flash anything. I can't hard reset either. All I can do is reboot, enter bootloader and enter download mode.
So I guess I'm stuck with Oreo that's a mess on my device.
ibringthemadness said:
Because I can't boot to recovery mode. Either I get stuck in a boot loop or the device boots just like I rebooted it. So I can't get to twrp and I can't flash anything. I can't hard reset either. All I can do is reboot, enter bootloader and enter download mode.
So I guess I'm stuck with Oreo that's a mess on my device.
Click to expand...
Click to collapse
Try boot into Download mode and Flash new TWRP https://dl.twrp.me/oce/twrp-3.2.2-0-oce.img.html
If your PC can not recognize your phone, try another PC.
minhnewpro said:
Try boot into Download mode and Flash new TWRP https://dl.twrp.me/oce/twrp-3.2.2-0-oce.img.html
If your PC can not recognize your phone, try another PC.
Click to expand...
Click to collapse
Already tried to flash twrp-3.2.2...
Same result. None.
My PC finds my phone with no problem until I boot into download mode then it doesn't find it anymore.
Still another PC?
I flashed twrp installer and magisk but now everytime i reboot my phone, it reboots all the way but right as it finishes booting and shows the lockscreen it says powering off. Please help i hope i didnt mess up my phone.
I tried restoring and it had an error now it wont boot past fastboot mode omg help please!!
Use the MSM tool. I had to do that, too, and it saved me!
bigmikey307 said:
I tried restoring and it had an error now it wont boot past fastboot mode omg help please!!
Click to expand...
Click to collapse
link for help: https://forum.xda-developers.com/oneplus-6t/how-to/tool-6t-msmdownloadtool-v4-0-oos-9-0-5-t3867448
bigmikey307 said:
I flashed twrp installer and magisk but now everytime i reboot my phone, it reboots all the way but right as it finishes booting and shows the lockscreen it says powering off. Please help i hope i didnt mess up my phone.
Click to expand...
Click to collapse
Just out of curiosity, report back if that MSM tool worked for you. Never tried it myself because I've never bricked this phone, but curiosity.
No, I already tried that msm tool. It doesn't recognize my device. Probably because my device was on 9.0.10 or 9.0.6...im not really sure bc I tried restoring with a backup from 9.0.6 while I was on 9.0.10. But my computer did recognize it while it was in Qualcomm Download mode so maybe the toll just needs to be updated?
This happened to me when I upgraded from 9.0.7 to 9.0.10. When I booted into TWRP, all my internal storage was encrypted, so I couldn't flash the OS again from there. I tried to wipe just the data and dalvik/cache in a hope to fix it. Don't do this as my internal storage got wiped (most likely due to the encryption). I had to download and reflash the OS through OTG with a pendrive in the end. Possibly try to do that first if you have access to it instead of wiping the phone.
bigmikey307 said:
No, I already tried that msm tool. It doesn't recognize my device. Probably because my device was on 9.0.10 or 9.0.6...im not really sure bc I tried restoring with a backup from 9.0.6 while I was on 9.0.10. But my computer did recognize it while it was in Qualcomm Download mode so maybe the toll just needs to be updated?
Click to expand...
Click to collapse
Msm doesn't need update. It's meant to work with phone off just pressing volume up I think, whatever version/type of ROM there is in it. Phone is recognized as a Qualcomm modem by the computer. Read carefully how to use it. It will restore a full out of factory 9.0.5 then you'll update it as usual.
Striatum_bdr said:
Msm doesn't need update. It's meant to work with phone off just pressing volume up I think, whatever version/type of ROM there is in it. Read carefully how to use it. It will restore a full out of factory 9.0.5 then you'll update it as usual.
Click to expand...
Click to collapse
Ok, then if it should work, it isn't working with my device. It's not recognizing it. I tried both msm tools, the T-Mobile one and the regular one and my device just isn't showing up on the tool
bigmikey307 said:
Ok, then if it should work, it isn't working with my device. It's not recognizing it. I tried both msm tools, the T-Mobile one and the regular one and my device just isn't showing up on the tool
Click to expand...
Click to collapse
Power off device then hold volume up & volume down at same time then plug into PC it may take a second but it will recognize it
twinnfamous said:
Power off device then hold volume up & volume down at same time then plug into PC it may take a second but it will recognize it
Click to expand...
Click to collapse
Yes, I know how to read directions. I'm telling you it didn't recognize it. The drivers are installed and it's recognized in device manager but it's not showing up in the tool.
bigmikey307 said:
Yes, I know how to read directions. I'm telling you it didn't recognize it. The drivers are installed and it's recognized in device manager but it's not showing up in the tool.
Click to expand...
Click to collapse
I was on windows 10 and I had to unplug and plug in a few times and I could only use the USB 2.0 port. It wouldn't work in USB 3.0 port. That's about what I remember
twinnfamous said:
I was on windows 10 and I had to unplug and plug in a few times and I could only use the USB 2.0 port. It wouldn't work in USB 3.0 port. That's about what I remember
Click to expand...
Click to collapse
Ok thanks, I'll keep trying
H4X0R46 said:
Just out of curiosity, report back if that MSM tool worked for you. Never tried it myself because I've never bricked this phone, but curiosity.
Click to expand...
Click to collapse
It's working now! That msm tool wasn't working for me so I found an all in one tool and I I flashed a whole new rom and it didn't work at first but I tried again and it worked. I tried using adb to flash it but it would boot any imgs but that tool worked!
bigmikey307 said:
It's working now! That msm tool wasn't working for me so I found an all in one tool and I I flashed a whole new rom and it didn't work at first but I tried again and it worked. I tried using adb to flash it but it would boot any imgs but that tool worked!
Click to expand...
Click to collapse
Glad to hear u got it fixed
bigmikey307 said:
It's working now! That msm tool wasn't working for me so I found an all in one tool and I I flashed a whole new rom and it didn't work at first but I tried again and it worked. I tried using adb to flash it but it would boot any imgs but that tool worked!
Click to expand...
Click to collapse
Hi I flashed the installer by mistake once.
The solution is to flash the stock boot image in both slots.
Worked fine for me.
bigmikey307 said:
Yes, I know how to read directions. I'm telling you it didn't recognize it. The drivers are installed and it's recognized in device manager but it's not showing up in the tool.
Click to expand...
Click to collapse
Umm.. That's probably what you did, but make sure to get the driver automatically via internet. If that doesn't help, perhaps a different pc/port/cable will do the trick (different pc worked for me).
H4X0R46 said:
Just out of curiosity, report back if that MSM tool worked for you. Never tried it myself because I've never bricked this phone, but curiosity.
Click to expand...
Click to collapse
I've had to use that tool twice for doing stuff the phone didn't like, testing etc. Saved my bacon both times
Sent from my ONEPLUS A6013 using XDA-Developers Legacy app
Good evening! I hope you can help me.
I flashed LineageOS 14.1, but I wanted to go back to EMUI. I made all the wipes and tried to flash different stock firmwares through a forced update (volume buttons + power button), but it never worked. At that point, I read about a guy in this forum who suggested to create a flashable zip with Huawei Update Extractor: I followed the suggestion and tried to flash it with TWRP. No error was given, but when I tried to restart, TWRP told me I had no OS installed. I thought it was strange, so I tried to restart anyway. That's when I got in rescue mode. I can't get into the recovery and I can't use fastboot. What rescue mode shows me is:
RESCUE MODE
Attention!
Please update system again
Update User Guide:
*link*
*android avatar*
Error!
Func NO: 10 (boot image)
Error NO: 2 (load failed!)
Pressing the three buttons, I'm able to force an update. The problem is I can't find a firmware that doesn't get rejected. With Lollipop firmwares, it starts to install, but it fails at 12%. With Marshmallow ones, the installation process doesn't even start.
What can I do to make it work again? I'm very sad because this phone was gifted to me a couple of days ago and I already messed it up. I don't even know how to turn it off.
What can I do to get in fastboot mode? At that point, what should I do to flash the stock firmware? Or maybe do I need to find the first stock firmware ever installed into this phone to make the forced update work?
Please, I need help. Thank you in advance!
P.S. The phone's model is ALE-L21. I live in Italy, so I assume it's a European version.
Did you managed to fix this?
Jhon_Locke said:
Did you managed to fix this?
Click to expand...
Click to collapse
Not yet, but I'm working on it. I found out that the device is recognized by my PC if I follow these steps:
1. Connect the phone to the PC and wait for it to go in rescue mode;
2. Wait until the notification LED stops to blink;
3. Disconnect the USB cable;
4. Press volume - and power button;
5. Reconnect the cable.
At that point, the screen turns black and the phone is recognized as "㌲㔴㜶㤸". I installed the drivers and now it's recognized as "HUAWEI USB COM 1.0". I should be able to reflash the partitions and make my phone work again, but I'm still trying to understand how to do it correctly.
Any help is appreciated!
ErikChimello said:
Not yet, but I'm working on it. I found out that the device is recognized by my PC if I follow these steps:
1. Connect the phone to the PC and wait for it to go in rescue mode;
2. Wait until the notification LED stops to blink;
3. Disconnect the USB cable;
4. Press volume - and power button;
5. Reconnect the cable.
At that point, the screen turns black and the phone is recognized as "㌲㔴㜶㤸". I installed the drivers and now it's recognized as "HUAWEI USB COM 1.0". I should be able to reflash the partitions and make my phone work again, but I'm still trying to understand how to do it correctly.
Any help is appreciated!
Click to expand...
Click to collapse
fastboot detects your device when you plug it into your computer?
I mean, if you run "fastboot devices" it shows your phone?
I've had this same problem but with an P8 Lite 2017, after flashing some ROM that supposedly was the stock one and trying to flash recovery I ended up with my phone bootlooping into rescue mode, I was able to "bypass" this thing rebooting my phone like crazy, seriously like after 20 reboot it finally booted into the damn ROM and I never touched the phone again. Sometimes when the phone ran out of battery and tried to power it on the phone booted into rescue mode and again after some reboots it booted to Android but now I want to install a custom ROM or at the very least root this damn phone so that's why I'm asking you if you have solved this, if you do then probably if I follow the same steps I would be able to fix that screen, hopefully.
If you are able to flash something start with flashing all recoveries your update.app has, maybe that's the problem (at least in my phone it is).
Jhon_Locke said:
fastboot detects your device when you plug it into your computer?
I mean, if you run "fastboot devices" it shows your phone?
I've had this same problem but with an P8 Lite 2017, after flashing some ROM that supposedly was the stock one and trying to flash recovery I ended up with my phone bootlooping into rescue mode, I was able to "bypass" this thing rebooting my phone like crazy, seriously like after 20 reboot it finally booted into the damn ROM and I never touched the phone again. Sometimes when the phone ran out of battery and tried to power it on the phone booted into rescue mode and again after some reboots it booted to Android but now I want to install a custom ROM or at the very least root this damn phone so that's why I'm asking you if you have solved this, if you do then probably if I follow the same steps I would be able to fix that screen, hopefully.
If you are able to flash something start with flashing all recoveries your update.app has, maybe that's the problem (at least in my phone it is).
Click to expand...
Click to collapse
No, it doesn't show anything if I write that command...
I guess mine won't ever boot into the rom because it seems like there's no system installed. I made some researches and found out there are some softwares that let you reflash the partitions IF the phone is recognized as "HUAWEI USB COM 1.0". I'm still trying to figure out how to do it correctly though. I feel like if I do something wrong, then my phone won't probably turn on again.
In your case, you should be able to flash a custom rom without any issue. You just have to be very careful and inform you as much as you can: I don't want your phone to end up like mine?. Anyway, it seems pretty hard to go back to the stock rom, so think about it before you flash a custom rom. Also, make a Nandroid Backup is very important.