Database Info

[q] depressed and need help

DESPERATE FOR HELP!
I bought a LG G2 D802 after deciding that ~ thats the phone i needed and after i bought it of course it had the 4.4.2 when i really wanted the 4.2.2
The reception was horrible too in low signal zones i had 90% of time no signal so after studying a little i decided i would Root it & install a new Rom possibly a Tmobile Version so i could fix my reception with Wifi-calling. Rooting was straight forward and no problems but Twrp was horrible i tried different ways and i couldnt install a recovery that worked or opened. Before i started playing with Twrp i made a Back up of the stock just in case.
AS it was BOUND to happen ~ flash errors occurred when i installed autorec.apk and rebooted. After that all i get is:
Fastboot mode started
udc_start()
and when im connected by USB
-reset-
-portcharge-
fastboot: proccessing commands
Pretty popular on the forum. So i tried to keep my cool and went through all same cases> I tried to get Recovery ( never installed right so ) tried to fix it by a method someone shared on the forum ~ didnt work Fastboot would flash the new recovery but once i went through the reboot and factory settings would go back to same black screen with fastboot mode started. To make things worse my download mode pops out and stays half a sec before it goes to same Awful screen. Tried to fix download with Laf file ~ fastboot erase and flash new one for my version as suggested by another member who unbriked his LG G2 didnt work ~ same issue.
ADB doesnt recognize the device. I have installed all device software in the beginning when i was rooting and trying to install Twrp. its an LG G2 with no SD slot and not a removable battery. Im losing all hope i dont know what to do anymore. If you guys can help me would be a life saver im close to smashing it to pieces and go back to my old Blackberry~...~
:crying::crying::crying::crying::crying::crying::crying: Please help !

DflMaster said:
DESPERATE FOR HELP!
I bought a LG G2 D802 after deciding that ~ thats the phone i needed and after i bought it of course it had the 4.4.2 when i really wanted the 4.2.2
The reception was horrible too in low signal zones i had 90% of time no signal so after studying a little i decided i would Root it & install a new Rom possibly a Tmobile Version so i could fix my reception with Wifi-calling. Rooting was straight forward and no problems but Twrp was horrible i tried different ways and i couldnt install a recovery that worked or opened. Before i started playing with Twrp i made a Back up of the stock just in case.
AS it was BOUND to happen ~ flash errors occurred when i installed autorec.apk and rebooted. After that all i get is:
Fastboot mode started
udc_start()
and when im connected by USB
-reset-
-portcharge-
fastboot: proccessing commands
Pretty popular on the forum. So i tried to keep my cool and went through all same cases> I tried to get Recovery ( never installed right so ) tried to fix it by a method someone shared on the forum ~ didnt work Fastboot would flash the new recovery but once i went through the reboot and factory settings would go back to same black screen with fastboot mode started. To make things worse my download mode pops out and stays half a sec before it goes to same Awful screen. Tried to fix download with Laf file ~ fastboot erase and flash new one for my version as suggested by another member who unbriked his LG G2 didnt work ~ same issue.
ADB doesnt recognize the device. I have installed all device software in the beginning when i was rooting and trying to install Twrp. its an LG G2 with no SD slot and not a removable battery. Im losing all hope i dont know what to do anymore. If you guys can help me would be a life saver im close to smashing it to pieces and go back to my old Blackberry~...~
:crying::crying::crying::crying::crying::crying::crying: Please help !
Click to expand...
Click to collapse
is your fastboot working?? do you have proper drivers... please search for x64 drivers if you have 64 bit os... sometimes that help.. i can be simple driver problem.. i tried to read you post twice but couldn't understand moreover i am not familiar with specifically LG but still i have some experience in flashing samsung s devices and nexus

pushkardua said:
is your fastboot working?? do you have proper drivers... please search for x64 drivers if you have 64 bit os... sometimes that help.. i can be simple driver problem.. i tried to read you post twice but couldn't understand moreover i am not familiar with specifically LG but still i have some experience in flashing samsung s devices and nexus
Click to expand...
Click to collapse
I dont know! I can Erase and Flash .img files into the phone ~ by using CMD and the SDK but i dont seem to be able to flash a system.img the one i have is 3gb and says error allocating memory. I dont see my device on adb ~ and fastboot shows ? Fastboot as device. I went and installed Ubuntu into a Virtual drive to try to push files into phone so i could access download mode or recovery. No luck there i couldnt find the phone under devices either.
When i use CMD on the PC and flash recovery recovery.img or any other image command the phone displays the work being done. So i think i am connected to Fastboot.

[Q] Moto G, wiped system through idiocy and can only access TWRP & fastboot

Hey folks,
I'm rather embarrassed that I have to ask for help here, but here we go:
I wanted to update my Moto G (1st gen) to Lollipop 5.1 (via this thread: http://forum.xda-developers.com/moto-g/development/rom-stock-motorola-lollipop-rom-t3017510) and after toying around with it for a few hours got frustrated and did some stupid things, which I'm also having a hard time to remember.
From what I recall, I managed to flash the "GPE 5.1 ROM (Optimized) v1.1" ROM via TWRP, but when booting the phone got stuck on the BOOTLOADER screen for about 1 1/2 hours, after which I decided to turn off the phone.
After that I frustratedly started fiddling around in TWRP and wiped system, cache and some more things (derp :silly: ) and well... ever since then I'm trying to get a new ROM on my SD card, but I can't push via adp because my device is not found.
Here's the facts
- When I try to regularly boot up my phone, the Warning Bootloader unlocked sign appears
- I can access the fastboot screen on my phone (AP Fastboot Flash Mode (S) 41.11), the one where it says normal powerup, recovery, factory, barcodes, bp tools and qcom. When I connect via USB it says USB connected.
- I can get access the recovery rom TWRP (v2.8.5.0)
- When I try to push a ROM to my sdcard command line tells me "error: device not found".
aaand that's it. I really hope I didn't brick my phone.
I'm on Windows 7 x64 and I would really appreciate the communities help. After that I'll show myself out and leave my phone working for a while hopefully.
edit: one more thing. my phone gets recognized as "Fastboot falcon S" in windows when I plug it in while in fastboot flash mode and as XT1032 when TWRP is booted. obviously it doesn't get recognized as a volume in Windows Explorer, or I would have already transfered another rom on the SD card by now.
edit 2: I also tried connecting the phone via another windows 7 x64 laptop now. installed motorola device manager & minimal adb and fastboot, but same thing there. :|
edit 3:ISSUE RESOLVED for now. I used this: http://forum.xda-developers.com/moto-g/general/gpe-lollipop-5-1-1click-installer-t3075522 and it worked like a charm. Thanks everyone.

@covecove until there is fastboot, there is hope.

Help with bricked? XT1039...

HI,
First time posting, but read a lot of great info on here in the past. just made a bit of a stupid mistake tho... I'd rooted my XT1039, and then flashed the custom recovery back as well as the stock 4.4.4 eu retail gb. I was getting the 5.1 OTA update, but the install was failing. In my eagerness, I downloaded the GPe Lollipop 5.1 update from here - http://forum.xda-developers.com/moto-g/general/gpe-lollipop-5-1-1click-installer-t3075522 - and tried to flash that, missing that it is for a different phone. Now I'm stuck at the bootloader menu, with the error "fall-through from normal boot mode." Any attempt to select normal powerup, recovery, etc results in a black screen with "Google" written on it and an unlocked padlock symbol.
I was going to try and flash the stock 4.4.4 image I had, but when connecting the phone to the PC via USB, fastboot isn't recognising it as attached, even though the phone detects that USB is connected...
Any help would be seriously and massively appreciated!!
Thanks in advance!

Hey man, I have a similar problem as you. Maybe I can give you a little hand, but its better if somebody who understan everything well give you the hand, becouse I'm a "starter" with this of Moto G.
Your device is charged? With my XT1040, the bootloader didnt connect with the PC via USB if the batery was low. Other thing, which version of bootloader do you have?

Thanks! Yes, the phone is charged! Not sure what version of the bootloader it is...

Start fastboot mode with "Pwr" + "VolDwn" and in the top of the screen says:
Code:
AP Fastboot Flash Mode (S)
41.xx [COLOR="Red"]<--- version of bootloader[/COLOR]

It's 41.19...

Try flashing the CWM Recovery again ClockWorkMod Recovery by Somcom3X with fastboot.
Then mount USB storage and upload an Lollipop's backup/system for your XT1039.
Finally, try to install the Lollipop's zip. If the instalation finish succesfull, wipe data and cache. Then try to start your device normaly (first option of CWM (restart))
Anyway, yesterday I made a thread explaining what happened to me with my XT1040 and how I solve it. Read it if you have time, maybe helps with your problem XT1040 - Reviving bad Lollipop flash/downgrade/bootloader 41.18
Note: I think that XT1039 and XT1040, both can work with the same Lollipop but I'm not sure, ask arround before try with a XT1040 backup.

Hi,
Thanks for that info. Unfortunately I can't do any of that, because fastboot doesn't see the phone any more. When I plug the phone in by USB, windows recognises it, and the phone says that USB is connected, but "ADB devices" in fastboot doesn't see it... So I don't know if it is completely bricked! Selecting any option in the bootloader menu gives me a screen with "Google" on it and a padlock sign...

It has enough battery? If not, Moto G dont allow you to use ADB comands for safety. If not that, really I have no idea. Hopefully someone who knows more than me pass by your thread

Yes, the battery is fully charged... ok, thanks for your help anyway!

Stuck at bootloop after update, can't access ADB.

Hi, I need your help here. I'm trying to fix my friends phone for her. What she told me is that it got stuck at the second boot screen after an update. She also said that it happened before and her father got it working. So my first thought was to clean flash stock firmware but I can't get ADB working. I've installed usb drivers and minimal ADB and fastboot but it doesn't recognize the phone in "adb devices" (I have no idea if USB debugging was on in dev options but I'm assuming it wasn't). I have no idea what to do now as I'm not that familiar with Xiaomi firmware.
Thanks in advance.
Edit: Xiaomiflash sees the device but not as COM.. but 72e728fb (?) and trying to flash it in this state ends with error:Flash xbl error

Blackview Tab 8 unlocked Bootloader, but how to magisk?

Hi,
so with this Tutorial i was able to unlock the bootloader of the Blackview tab 8.
but i just could not find any way to flash magisk.
- "fastboot boot patched_img.img" and "fastboot flash boot patched_img.img" gave me "fastboot: error: Couldn't parse partition size '0x'"
- "fastboot flash:raw boot boot.img" was able to flash the patched_boot.img (a twrp i tried to port as well), but then i was stuck at blackview logo (SOFTBRICK)
- SPD Research Tool R24.0.0003 was able to flash patched_boot.img, but same stuck at logo (SOFTBRICK)
The only way i was able to unbrick it, involved opening back cover and disconnecting the battery and reconnecting it again.
then put research tool to download mode and flash stock img
I'm hoping for some advices, what i could try to get magisk flashed
- Tab8 Firmware (DK_SC9863A_P30_5G_10.0_Tab8_EEA_20201022_V1.0)
- SPD Research Tool R24 (there are 2 other tools but afaik research tool is the only one, where i can choose which partitions to flash)
best regards
Oxo

Hi,
I've got a tab8 too (eu) and I have the boot_patched.img generated by magisk manager but I can't unlock the bootloader. I used the tuto you gave (your first link) too.
Could you explain what you did to successfully unlock your bootloader please?
Thanx
Bests regards

I was trying to backup the stock ROM of this same tablet, however i must have incorrectly installed SPD drivers or somehow had uninstalled them, Research Download said "failed user cancel", then boom when i tried to switch it on it was not turning on nor charging. I have been trying to charge it for about 4 days, no dice, it does not charge still, nor turning on.
I must have soft bricked it, because it gets detected by the PC as "SPRD U2S Diag (COM5)", but when i try to flash Stock ROM i downloaded it either says " failed user cancel" or gets stuck at "checking baudrate".
I don't know what to do, would opening it and test point it make a difference? Because some guy on Youtube was able to flash his SPD phone after test pointing it, as it was facing "failed user cancel"
Another question, which key combinations did you use when flashing your Tab 8? Vol - and Power or?

nr0000000 said:
Hi,
I've got a tab8 too (eu) and I have the boot_patched.img generated by magisk manager but I can't unlock the bootloader. I used the tuto you gave (your first link) too.
Could you explain what you did to successfully unlock your bootloader please?
Thanx
Bests regards
Click to expand...
Click to collapse
I did it like described in the tutorial i linked. did you use linux? maybe in a VM or so, to use the .sh script. AFAIK it doesnt work with windows
also dont forget to activate "OEM unlocking" in dev options
StormChaser1337 said:
I was trying to backup the stock ROM of this same tablet, however i must have incorrectly installed SPD drivers or somehow had uninstalled them, Research Download said "failed user cancel", then boom when i tried to switch it on it was not turning on nor charging. I have been trying to charge it for about 4 days, no dice, it does not charge still, nor turning on.
I must have soft bricked it, because it gets detected by the PC as "SPRD U2S Diag (COM5)", but when i try to flash Stock ROM i downloaded it either says " failed user cancel" or gets stuck at "checking baudrate".
I don't know what to do, would opening it and test point it make a difference? Because some guy on Youtube was able to flash his SPD phone after test pointing it, as it was facing "failed user cancel"
Another question, which key combinations did you use when flashing your Tab 8? Vol - and Power or?
Click to expand...
Click to collapse
i dont know about test point actually. you can open it pretty easily and just disconnect battery. then connect again, use sdp tool and start the flash process, then press vol- and hold it while pluging in usb cable. thats what i do, if im stuck and cant do anything else.
regarding button combination, i'm not sure. usually i use adb reboot bootloader.
Also for the Blackview Tab 8 you need to extract keys from your vbmeta.img and sign it differently, also every other .img you wanna flash, like patched magisk boot.img. i successfully rooted mine some time ago, but i flashed some magisk modules and something went wrong and i ended up bootlooping. now im trying to root again.
somehow i cant flash the vbmeta.img. i dont remember if i did anything different last time.
all the stuff i did to get it rooted, i have taken from that hovatek forum.
edit: uploaded Stock Rom Images and stuff like for example a magsik patched boot image, which got repacked with android image kitchen then signed and repacked again with avbtool here
PS: dont have time to invest to this atm, also i just read that there was a update sometime this year which i didnt get, so maybe that changed some stuff.

I was considering buying this Blackview tablet and before I ordered it I got in touch with the Blackview home people in Hong Kong. They were extremely UNHELPFUL AND EVEN RUDE (not unusual for the chinese). As far as I am concerned this mob does not deserve to be supported and having a product that is so difficult to do any tinkering with precludes it from my list for sure. It is so time for consumers to DEMAND that any product that does not give explicit instructions as to unlocking and flashing is not supported. Why is it not possible in this day and age for this to happen. OK I know why but you get my meaning.