Before going any further, i reverted back to stock yesterday via LGUP to fix some issues i had with the phone on custom roms that caused system crashes. Bootloader is unlocked, i get the prompt that bootloader is unlocked and it isn't safe when the device is booting and OEM unlock is enabled in developer settings.
I'm trying to re-flash TWRP since reverting to stock via. LGUP reverts recovery back to stock. I have issues sending commands via. Fastboot which is making me unable to flash the recovery rom.
Fastboot devices detects my H930, and a few commands works like fastboot reboot bootloader. It's only when it reaches the step to sending the image that the device either freezes for hours or gives an random error like failed command, or too many links.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I've tried multiple ports and usb cables on multiple operating systems "Windows 10 and Arch Linux" on multiple computers my old laptop and my desktop PC with the latest drivers.
I have the latest LG Mobile drivers, i have also tried Driver booster which worked for some but not me
I have the latest SDK platform tools from developer.android.com r31.0.2 (ADB/Fastboot), I've also tried 1.6_r1 and 1.43 with no success.
I'm on a Pre-July 2018 Android security patch on Oreo for LG V30 H930
And I'm using the latest TWRP Joan that i used before reverting to stock (TWRP-JOAN-3312_2020-02-23)
I've followed all troubleshoot options under section 7 at WTF V30 Root Guide other than buying a USB 2.0 hub which seems ridiculous
I have no more options, It's not like i haven't done this before so I'm sure that I'm doing it correctly
Sounds to me like a communication error, which is either a cable or USB issue. As you know, some computers simply don't work well with this process, and fail to unlock bootloaders and/or flash things. I know you feel like you've tried everything, but you may just need to try other cables and most likely computers. There's really no other solution to that problem beyond that.
Also, age of the computer doesn't make as much of a difference, from what I've seen. Just because it's "old" doesn't mean it should work, necessarily. Maybe it's not a chipset that works, and there's no way to fix that externally. Admittedly, older machines seem to work better, but maybe yours is just not "old enough" or something. Do you have the machine that you originally did the BL unlock with, successfully? That might be a good place to start...
Again, I hear you, and you seem experienced... but you just might need to keep trying.
Also, make sure your twrp.img is correct and not corrupted in some way. Can't hurt to check.
I wonder if you can do a fastboot boot twrp.img, and then use TWRP there to perform the flash to the recovery partition? Just thinking aloud...
schwinn8 said:
Sounds to me like a communication error, which is either a cable or USB issue. As you know, some computers simply don't work well with this process, and fail to unlock bootloaders and/or flash things. I know you feel like you've tried everything, but you may just need to try other cables and most likely computers. There's really no other solution to that problem beyond that.
Also, age of the computer doesn't make as much of a difference, from what I've seen. Just because it's "old" doesn't mean it should work, necessarily. Maybe it's not a chipset that works, and there's no way to fix that externally. Admittedly, older machines seem to work better, but maybe yours is just not "old enough" or something. Do you have the machine that you originally did the BL unlock with, successfully? That might be a good place to start...
Again, I hear you, and you seem experienced... but you just might need to keep trying.
Also, make sure your twrp.img is correct and not corrupted in some way. Can't hurt to check.
I wonder if you can do a fastboot boot twrp.img, and then use TWRP there to perform the flash to the recovery partition? Just thinking aloud...
Click to expand...
Click to collapse
My reasoning for why my old laptop might have worked is because of the older USB ports on it, since it's from the early 2010, but it didn't work.
I'm unable to send anything to my device via. fastboot which includes trying to boot into the TWRP image. I have tried multiple versions of the TWRP image and they worked prior to reverting to stock so i don't expect the image file to be the issue.
Do keep in mind that all of my issues are related to fastboot and not adb or the device itself since i've flashed multiple custom roms on it before, i just didn't expect that reverting to stock would make me unable to flash TWRP back on it.
I've tried the original cable, all of my VR charging cables which are also USB-C on multiple ports on both machines and in both operating systems. At least the phone is not unusable, but i miss Pixel Experience.
When I suggested checking the image files, I mean be sure you're getting a ZIPped image that you are extracting, or be sure that the hashes match. Zip does internal hashing to some extent, so it can prevent corruption, but outside of that it's a good idea to check the hash. But, I do agree, that's not likely the issue.
Again, you may just need to try different, older machines. You mention you have two - a new and old. That's fine, but not all "old" machines work either.
You may also try going into safemode or something - sometimes firewalls, virus scanners, etc get in the way. I haven't experienced that personally on this application, but I have seen such things happen recently with other software.
Beyond that, I don't have any other ideas to offer, sorry.
em.. if you can issue fastboot reboot bootloader, I don't think this is connection issue. are you able to get to the download mode? if so, try to refurbish your kdz again, and then restart over
Related
Installed cm via directions. No problems. Decided to try installing a new Android kernel. Flashed via recovery.
Moboot, but couldn't get into any os, not even recovery. Eventually got into Android. Was able after many attempts to get to webos. Decided to try and reinstall cm9 and such. Plugged into computer while in webos to move files over and got a need to format window. Hit yes (i know, I know).
Now can't even get moboot. Decide to Dr it. Gets to 12% and doesn't move. Google it and follow some novaterm/cmd directions.
Now Dr gets to 8% and says unable to reset device. Have a hard time getting into HP recovery (usb symbol). Mostly get an exclamation point in a triangle and the url for Dr.
What r my options, HP warranty? Thx
Sent from my PG86100 using XDA App
The cm team can help you on IRC here's info I copied from the cm thread go here and they should get you right http://webchat.freenode.net?channels=cyanogenmod-touchpad
The reason the doctor is failing is because Android messes with your partitions and at 12% the webOS doctor is verifying partitions. Have you attempted ACMEUninstaller? When at the webOS screen go ahead and run ACMEUinstaller. Then if uoi can boot into webOS do the complete wipe to wipe the entire SD section. Then doctor it and then reflash Android with ACMEinstaller2
Sent from T the Touchpad
Eat it iPhone said:
Installed cm via directions. No problems. Decided to try installing a new Android kernel. Flashed via recovery.
Moboot, but couldn't get into any os, not even recovery. Eventually got into Android. Was able after many attempts to get to webos. Decided to try and reinstall cm9 and such. Plugged into computer while in webos to move files over and got a need to format window. Hit yes (i know, I know).
Now can't even get moboot. Decide to Dr it. Gets to 12% and doesn't move. Google it and follow some novaterm/cmd directions.
Now Dr gets to 8% and says unable to reset device. Have a hard time getting into HP recovery (usb symbol). Mostly get an exclamation point in a triangle and the url for Dr.
What r my options, HP warranty? Thx
Sent from my PG86100 using XDA App
Click to expand...
Click to collapse
lucky for us, the TP can never be bricked unless you start to manually edit partition tables (and even then, its fixable with much hair pulling, ive personally troubleshooted this with a friend before )
maybe these threads can help you out:
http://forum.xda-developers.com/showthread.php?t=1236727&page=2.
http://forum.xda-developers.com/showthread.php?t=1379579
it really helps to have a grasp on how novaterm works, and ALWAYS ALWAYS re read your commmands to ensure you typed it correctly (upper/lower case espicially ;P)
Thx guys ill look into it, but I'ma be busy so ill have to chk this out tomorrow
Sent from my PG86100 using XDA App
http://forum.xda-developers.com/showthread.php?t=1426244
Try it. It may just work.
rr5678 said:
http://forum.xda-developers.com/showthread.php?t=1426244
Try it. It may just work.
Click to expand...
Click to collapse
oh god, that brings back terrible memories of "unbricking" my buddies TP from scratch using mine as a reference
and yes, Eat it iPhone, this is the best last alternative for repair, you will be restored to 100% BNIB (or LNIB as the case would be )
Solidus_n313 said:
oh god, that brings back terrible memories of "unbricking" my buddies TP from scratch using mine as a reference
and yes, Eat it iPhone, this is the best last alternative for repair, you will be restored to 100% BNIB (or LNIB as the case would be )
Click to expand...
Click to collapse
It may be horrible but in the end it's worth it
P.S.: I read that link in your signature (The TRUTH: XDA: Then and Now), and all I have to say is.....
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
im still wating for a complete recovery without bootie... which doesnt evn turn on the screen.heh
as said before more likely than not its a currupted partition that its stoping on...
darkassain said:
im still wating for a complete recovery without bootie... which doesnt evn turn on the screen.heh
as said before more likely than not its a currupted partition that its stoping on...
Click to expand...
Click to collapse
There is no recovery from a missing bootie (not that I know of). A missing bootie is like a missing hboot.
rr5678 said:
There is no recovery from a missing bootie (not that I know of). A missing bootie is like a missing hboot.
Click to expand...
Click to collapse
yep there is a way, you just havent heard of it (the pre has a way to boot from a corrupted bootie too)...
you can boot directly from the usb into the cpu bypasing bootie (instead of power + vol-up to enter bootie try it with vol-down while connected to a pc , and you will get what i mean..)
work has been done on this but a working product hasnt...
also is the hboot in nand or rom (im gueasing the nand /boot partiton just as with the few android devices i have worked on)
darkassain said:
yep there is a way, you just havent heard of it (the pre has a way to boot from a corrupted bootie too)...
you can boot directly from the usb into the cpu bypasing bootie (instead of power + vol-up to enter bootie try it with vol-down while connected to a pc , and you will get what i mean..)
work has been done on this but a working product hasnt...
also is the hboot in nand or rom (im gueasing the nand /boot partiton just as with the few android devices i have worked on)
Click to expand...
Click to collapse
No, the Pre is a completely different device. The Pre has an OMAP3430, while the TouchPad has your typical (non-USB bootable) Qualcomm processor.
And hboot is in the nand. (but still erasable)
rr5678 said:
No, the Pre is a completely different device. The Pre has an OMAP3430, while the TouchPad has your typical (non-USB bootable) Qualcomm processor.
And hboot is in the nand. (but still erasable)
Click to expand...
Click to collapse
doesnt matter boot with power+voldown and you enter qualcomm recovery which can boot from usb....
ps should have said that this only works on the TP
pps should mention that other qualcomm devices can boot from usb too...
darkassain said:
doesnt matter boot with power+voldown and you enter qualcomm recovery which can boot from usb....
ps should have said that this only works on the TP
pps should mention that other qualcomm devices can boot from usb too...
Click to expand...
Click to collapse
If you're talking about QHSUSB_DLOAD, there is no known way to use that. No image files, nothing.
rr5678 said:
If you're talking about QHSUSB_DLOAD, there is no known way to use that. No image files, nothing.
Click to expand...
Click to collapse
which is why i mentioned in two different posts that that its "not working" and why "im waiting" for something like this...
it works on some phones though which means it will communicate
darkassain said:
which is why i mentioned in two different posts that that its "not working" and why "im waiting" for something like this...
it works on some phones though which means it will communicate
Click to expand...
Click to collapse
I wish it was known what to do though. That's a super low level function.
Hello there experts,
The volume buttons of my S2 don't work at all. I bought it 2nd handed and the seller told me this beforehand. It seems they were broken in the process of replacing the screen, God knows who made such mistake.
I installed cyanogenmod with CM installer, as it does the job almost automatically without the need to go to the Download mode.
Once everything was installed and set up I thought, well let's try to remove that yellow triangle image...
After installing Triangle Away, it brought me to the download mode. I knew it was risky but I thought the phone would restart normally.
If I remove the battery, it'd always go back to download mode, and there is no way to start the phone normally.
as I'm unable to either press VOL up / down, i'm stuck in the download mode.
The only solution that comes to mind is disassembling the phonem, play with the volume buttons and see what's happening there, and try to fix it (if there's even a possible fix)
Does that look like it could be fixed? or it would need to replace and solder something else?
also, is there a way to get rid from the DL mode with some USB method on the PC? also flashing the phone as it is right now is impossible I guess.
this is what I found in the volume parts,
it's the first time I dare to disassemble a device like this. I have no clue about this kind of stuff;
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Try ADB Fastboot commands. Maybe it detects S2 in Download Mode. But not sure about that. First of all,
Download Samsung USB Drivers.
Download Minimal ADB & Fastboot
Connect USB Cable
Open that command line tool
Issue command 'adb devices' or 'fastboot devices'. If it detects your phone, your IMEI will be shown. Then try,
ADB Fastboot Reboot System
If all good, your S2 will be rebooted.(presuming that you're Rooted). If it doesn't you have to repair those keys or try to press them by some sort of sharp thing but easy you go, otherwise you will be damaging your phone. I recommend you ti get them repaired
syedbilal093 said:
Try ADB Fastboot commands. Maybe it detects S2 in Download Mode. But not sure about that. First of all,
Downliad Samsung USB Drivers.
Download Minimal ADB & Fastboot
Connect USB Cable
Open that command line tool
Issue command 'adb devices' or 'fastboot devices'. If it detects your phone, your IMEI will be shown. Then try,
ADB Fastboot Reboot System
If all good, your S2 will be rebooted.(presuming that you're Rooted). If it doesn't you have to repair those keys or try to press them by some sort of sharp thing but easy you go, otherwise you will be damaging your phone. I recommend you ti get them repaired
Click to expand...
Click to collapse
Thanks for your help.
Yes I was root, the solution you gave looks like it could have worked to get rid from the download mode.
Anyways, the flex that connects the buttons internally was broken, maybe this was a good thing that had to happen to get it repaired, as sooner or later I'd have to do that.
Finally I found a guy who is a beast at these things and he had lots of parts of S2's, so he repaired it in about 10 minutes.
Now I have a fully functional S2. It's still a good device in my opinion.
I bought it 2nd handed for a lower price that any chinese phone, good cam and speakers... makes me wonder if we should get ex-flagship devices instead of newer chinese cheap phones. I paid only 55euros for this phone, I know it's usually more expensive. After using a chinese android phone, my experience is much better with the S2.
So far I'm using cyanogenmod11 as my first rom. I know this question can be dumb and repetitive, but could you tell me what are the best roms/rom in your honest opinion? As usually, the smoothest running and more lasting battery are the most demanding needs.
Thanks again man!
Thats good to hear that. Yeah chinese phones are not good at all. Samsung S2 is a demanding phone still. I am also using S2.
As you asked about ROMs, personally i haven't rooted my S2. But in my opinion, i am listing three links about Top Custom ROMs. Visit them you'll find something for your S2.
http://www.cnet.com/how-to/best-custom-roms-for-the-samsung-galaxy-s2/
http://androidcure.com/best-kitkat-roms-samsung-galaxy-s-ii-i9100/
http://www.androidpit.com/best-5-custom-roms-for-the-galaxy-s2
Visit CNET first. In my honest opinion, stock Rom is the best ROM if we talk about stability,smoothness & performance. . Visit them you'll be able to find a ONE for your's.
syedbilal093 said:
Thats good to hear that. Yeah chinese phones are not good at all. Samsung S2 is a demanding phone still. I am also using S2.
As you asked about ROMs, personally i haven't rooted my S2. But in my opinion, i am listing three links about Top Custom ROMs. Visit them you'll find something for your S2.
http://www.cnet.com/how-to/best-custom-roms-for-the-samsung-galaxy-s2/
http://androidcure.com/best-kitkat-roms-samsung-galaxy-s-ii-i9100/
http://www.androidpit.com/best-5-custom-roms-for-the-galaxy-s2
Visit CNET first. In my honest opinion, stock Rom is the best ROM if we talk about stability,smoothness & performance. . Visit them you'll be able to find a ONE for your's.
Click to expand...
Click to collapse
I'm not sure about the s2 but in other devices, the stock updated roms+root access have always been the best configuration. Thing is I don't like TouchWhiz much.
Thanks for the info man. I'll check that out.
Enviado desde mi M9Pro mediante Tapatalk
Yeah check them out. No problem man. ! I also dont like TouchWiz. I like HTC Sense.:thumbup:
So tried downloading the 6.0 ota. after it installed it, it got stuck in a bootloop. tried doing factor reset and deleting cache and data.
nothing has worked so far.
heres the rub, i never unlocked my bootloader and i cant get into the OS to set the developer options. it seems my only solution is to RMA it. but im hoping maybe there is a hack of some sort.
heres to hoping.
My N9 wouldnt allow me to even attempt to flash anything when it was locked. One of the first things I had to do was a fastboot oem unlock (which also required me to boot into the OS to toggle that developer option). When you flashed 6.0 did you use the "flash-all" script?
WoodroweBones said:
My N9 wouldnt allow me to even attempt to flash anything when it was locked. One of the first things I had to do was a fastboot oem unlock (which also required me to boot into the OS to toggle that developer option). When you flashed 6.0 did you use the "flash-all" script?
Click to expand...
Click to collapse
No it was an OTA update. got the notification this morning and had it install the update. it obviously didnt take. i have not rooted my tablet or done anything like that. its actually the first device ive ever not rooted....
I had the exact same problem. I installed the OTA last night, and now it sits at the boot animation for hours. I tried to wipe cache, but I got an error saying it couldn't mount the partition. I tried to sideload it, and it failed, saying it couldn't mount it. I just (reluctantly) performed a wipe and hopefully that will work, but I'm not optimistic.
Update: no luck. So I permanently deleted a lot of stuff for no reason. =/
Yeah my problem is I can't sideload because my computer doesn't recognize it . I mean this whole unlocking the boot loader from within the OS thing is the stupidest design I've ever seen.....
since i can still get into hboot and fastboot can i side load the OTA? adb isnt seeing it in recovery but it sees it in fastboot.
I was not able to sideload anything. I could see the device, I could start the process, but it would fail every time. I talked to HTC last night and they are going to replace it.
Weirdly, when I was talking with them, they had me try to clear the cache and it actually worked, so I'm going to try and sideload it one more time tonight and if it doesn't work, just swap it out.
I'm caught in the boot loop as well after having downloaded the OTA... I must say, over the past couple weeks I was stuck in boot loops on several occasions, and only after a bunch of restarts would it load fully (and "update apps").
When this device works properly, I have no qualms. But it's incredibly irritating for a $600 tablet to be so shoddy...
stevesmithis said:
I was not able to sideload anything. I could see the device, I could start the process, but it would fail every time. I talked to HTC last night and they are going to replace it.
Weirdly, when I was talking with them, they had me try to clear the cache and it actually worked, so I'm going to try and sideload it one more time tonight and if it doesn't work, just swap it out.
Click to expand...
Click to collapse
Yeah I was able to clear the cache I was even able to format the user data the problem is is there is no OS loaded. At least with the fastboot says under os it says N/A.
HTC said they'll replace it I just have to send it in to them problem is I'm a truck driver so I'm never at home.
-Wes-
Sent from my SM-N910T using Tapatalk
wesmagyar said:
Yeah I was able to clear the cache I was even able to format the user data the problem is is there is no OS loaded. At least with the fastboot says under os it says N/A.
HTC said they'll replace it I just have to send it in to them problem is I'm a truck driver so I'm never at home.
-Wes-
Sent from my SM-N910T using Tapatalk
Click to expand...
Click to collapse
I had the same problem: even after wiping the cache and formatting the user data, the tablet wouldn't boot, and fastboot said "OS: N/A". However, I went into recovery and sideloaded the OTA file with adb. The update went fine and now my Nexus 9 works again. If you are using Windows and the computer doesn't recognize the tablet you should install the appropriate drivers, I guess (look up "Google USB Driver"). I use a Mac so drivers weren't a problem for me.
xworld21 said:
I had the same problem: even after wiping the cache and formatting the user data, the tablet wouldn't boot, and fastboot said "OS: N/A". However, I went into recovery and sideloaded the OTA file with adb. The update went fine and now my Nexus 9 works again. If you are using Windows and the computer doesn't recognize the tablet you should install the appropriate drivers, I guess (look up "Google USB Driver"). I use a Mac so drivers weren't a problem for me.
Click to expand...
Click to collapse
Will I'll be a mother effer I was able to get it to recognize my device by installing the Samsung ADB driver and from there I was able to sideload the OTA and it is now working.......
The very first thing I'm doing as soon as I actually get it start it is I am going to enable OEM unlock. Everybody who has one of these devices should do that immediately.
Thank you so much man you are awesome
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my SM-N910T using Tapatalk
I tried again and it failed. Sadness. Guess I'll just have to swap it out.
I can't figure out how have my device appear when entering "adb devices" ... when i'm in fastboot, i "fastboot devices" and it shows with the serial number. when i'm in recovery, though, "adb devices" shows nada. When I'm in TWRP after selecting "ADB Sideload", my device appears in my Device Manager under Nexus 9, but I can't update driver info to anything that seems to work.
I've got the most up to date drivers via SDK.
Any ideas how I can get my device to be recognized by my PC so that I can sideload the OS?
Thank you all.
thegeneralfamily said:
I can't figure out how have my device appear when entering "adb devices" ... when i'm in fastboot, i "fastboot devices" and it shows with the serial number. when i'm in recovery, though, "adb devices" shows nada. When I'm in TWRP after selecting "ADB Sideload", my device appears in my Device Manager under Nexus 9, but I can't update driver info to anything that seems to work.
I've got the most up to date drivers via SDK.
Any ideas how I can get my device to be recognized by my PC so that I can sideload the OS?
Thank you all.
Click to expand...
Click to collapse
I was having the same problem I installed the Samsung ADB driver, , and all of a sudden my computer recognized my Nexus 9 in a adb mode
Sent from my SM-N910T using Tapatalk
Mine wouldn't show up until I was in recovery and actually picked the "install from adb" or whatever from the menu.
yeah it doesn't actually go into adb mode until you select the sideload option. just as it doesn't go into fastboot untill you are in fastboot.
I was able to download the OTA from android authority. just made sure that the upgrade matched the one that i was upgrading from, i have a galaxy note so when i couldnt get windows to recognize the nexus 9 in adb mode i selected search my computer for the drivers and selected select from installed drivers and out of sheer desperation selected the Samsung ADB driver and sure enough the worked. from there i was able to adb sideload the update and install it and it rebooted into beatiful android 6.0 tablet has been working fine so far with no issues.
First thing i did however was allow unlocking of the bootloader in the developer options.
Edit: nvm
stevesmithis said:
Edit: nvm
Click to expand...
Click to collapse
Yeah I was going to say because I'm the op, I had no access to the operating system either but I was able to accomplish two steps I laid out above and it fixed my problem.
Sent from my SM-N910T using Tapatalk
Also also misread your post. I thought you were saying that unlocked the bootloader before you fixed it. Lol
I have two of the units mentioned in the thread title. One simply is stuck at the Alcatel logo after a reboot. I can get into the stock recovery, have done a factory reset (plus cache), but still just stuck at the logo. I've also popped it open and unplugged the battery (it's the attached kind), but still back at a logo after everything was back together.
I mentioned that I had two because the other one is working fine and available to use for a firmware dump. The issue I'm running into is that a cat /proc/mtd command returns no partitions (just blank) and there is no emmc on this unit. From what I've read, bad Chinese firmwares sometimes do not report out partition tables from mtd. So, all the guides I've found for using MTK Rom Studio, MTK Droid Tools, and SP Flash Tool don't work for me (at the moment) because I cannot produce a firmware.info or scatter file, due to mtd not populating the required info. Also, from what I gather, there is no firmware file available for this. I've tried using the Mobile Upgrade program from Alcatel, but it reports that the ROM is the most up-to-date and then quits. Yay.
Any help or insight would be greatly appreciated. I'm not desperate or anything; just hoping to get this one back working is all.
my_former_self said:
I have two of the units mentioned in the thread title. One simply is stuck at the Alcatel logo after a reboot. I can get into the stock recovery, have done a factory reset (plus cache), but still just stuck at the logo. I've also popped it open and unplugged the battery (it's the attached kind), but still back at a logo after everything was back together.
I mentioned that I had two because the other one is working fine and available to use for a firmware dump. The issue I'm running into is that a cat /proc/mtd command returns no partitions (just blank) and there is no emmc on this unit. From what I've read, bad Chinese firmwares sometimes do not report out partition tables from mtd. So, all the guides I've found for using MTK Rom Studio, MTK Droid Tools, and SP Flash Tool don't work for me (at the moment) because I cannot produce a firmware.info or scatter file, due to mtd not populating the required info. Also, from what I gather, there is no firmware file available for this. I've tried using the Mobile Upgrade program from Alcatel, but it reports that the ROM is the most up-to-date and then quits. Yay.
Any help or insight would be greatly appreciated. I'm not desperate or anything; just hoping to get this one back working is all.
Click to expand...
Click to collapse
I'm not sure how to fix your device without knowing more about it. Is it possible you could provide the firmware dump of the one that is working? I was interested in using such to get a working TWRP recovery going for this model. With a working recovery, might be able to do more for your bricked unit.
I can provide some of the images - a noted exception is for the System partition, as I have already mucked with that one while doing my experimentation with my own.
If you already have the working one rooted, I would suggest just using dd and looking under /dev/devices/by-name (I think that is what it is called) which should provide you access to the partitions you need and what they are called.
titanshadow said:
I'm not sure how to fix your device without knowing more about it. Is it possible you could provide the firmware dump of the one that is working? I was interested in using such to get a working TWRP recovery going for this model. With a working recovery, might be able to do more for your bricked unit.
I can provide some of the images - a noted exception is for the System partition, as I have already mucked with that one while doing my experimentation with my own.
If you already have the working one rooted, I would suggest just using dd and looking under /dev/devices/by-name (I think that is what it is called) which should provide you access to the partitions you need and what they are called.
Click to expand...
Click to collapse
Thanks for the reply. Let me see what I can do. This model is very odd, I have to admit. The fact that it does not use emmc, but instead mtd, yet a cat /proc/mtd produces nothing is baffling to me.
my_former_self said:
Thanks for the reply. Let me see what I can do. This model is very odd, I have to admit. The fact that it does not use emmc, but instead mtd, yet a cat /proc/mtd produces nothing is baffling to me.
Click to expand...
Click to collapse
What you're trying to do is for older MTK phones....as in like everything not just the cat /proc/mtd.
What you have to do it make a backup of your working tab and flash the brick tab with the back up.
Here's some links that can help you:
MTK Preloader drivers for Win 7- https://thebroodle.com/microsoft/win...rs-in-windows/
MTK Preloader drivers for Win 10- http://laurentiumihet.ro/windows-10-...tion-tutorial/
How to create a scatter file- https://androidmtk.com/create-scatte...or-mtk-devices
How to make a backup of your phone/ROM- https://forum.hovatek.com/thread-526.html
After making a backup, restore your ROM_0 backup using this method-----> http://forum.xda-developers.com/showpost.php?p=65784715&postcount=953
Check out this thread as it relates to all things Pixi----> http://forum.xda-developers.com/android/general/root-alcatel-one-touch-pixi-34-official-t3193624
Good luck
Can I get a copy kind that back up
kirito9 said:
What you're trying to do is for older MTK phones....as in like everything not just the cat /proc/mtd.
What you have to do it make a backup of your working tab and flash the brick tab with the back up.
Here's some links that can help you:
MTK Preloader drivers for Win 7- https://thebroodle.com/microsoft/win...rs-in-windows/
MTK Preloader drivers for Win 10- http://laurentiumihet.ro/windows-10-...tion-tutorial/
How to create a scatter file- https://androidmtk.com/create-scatte...or-mtk-devices
How to make a backup of your phone/ROM- https://forum.hovatek.com/thread-526.html
After making a backup, restore your ROM_0 backup using this method-----> http://forum.xda-developers.com/showpost.php?p=65784715&postcount=953
Check out this thread as it relates to all things Pixi----> http://forum.xda-developers.com/android/general/root-alcatel-one-touch-pixi-34-official-t3193624
Good luck
Click to expand...
Click to collapse
Thanks. Sorry for the ridiculous delay; life happened. Anyways, I cannot create a scatter file (from the working unit), just as before.; it gives me no partitions.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Alcutel pixi 3 (7) 4G 9007T tablet soft bricked
decided to play around with cleaning up the bloatware and Sprint installed junk on my Alcutel one touch pixi 3 (7) 4G 9007T tablet running originally android 5.1.1 , and ended up soft bricked stuck in a loop cycle of optimizing/staring apps, have scoured XDA and every other resource i have seen and for every device but this one there seems to be a fix, a stock rom, etc ,... one good thing is i am able to factory reset to at least enable debugging for adb access (though fastboot wont detect it) and hence cant get the device into a fastboot mode or unlock the loader.
Is there any compatible roms or recoveries out there for this particular device
Recovery <3e> Android L(not sure how to get a recovery log dump for providing more info)
I used nobloat app from google play had things pretty well cleaned up but thought to see how far i could go and i used the backup function in the app, but evidently i deleted something I shouldn't have and of course after trying a factorry rest the nobloat backup would be gone even if i could get botted back up)
after recovery I do get through the intitial setup, wifi, google account login etc,.. (using safemode) but if i use google backup files it gets to the loop fast, so i try to skip all that being restored, and am able to get to the settings to enable developer mode /debugging mode but once I exit that its a blank screen outside the clock showing then it reboots and keeps in the abov mentioned loop.
(as i mentioned adb detects the device but fastboot won't it just stuck on "waiting for any device"
I cannot seem to get this phone into the bootloader, download mode, or fastboot mode. I also can't get any rooting programs to work.
I have an LG Rebel 2 L57BL Tracfone that I've read is a variant of an LG K4 2017 LTE.
I have tried like every combination of buttons to get into fastboot but can only get into Recovery Mode. Using sudo adb reboot bootloader or sudo adb reboot-bootloader does not work, it just reboots the phone. I have managed to get the phone to boot into safe mode as well while messing with different buttons combinations and times.
I am just trying to get this phone rooted but I'm having a hell of a time. I am running Linux and Windows. Does anybody have any idea how to get into fastboot mode or how to root this device? It would be awesome, Thanks
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Knuxyl said:
I cannot seem to get this phone into the bootloader, download mode, or fastboot mode. I also can't get any rooting programs to work.
I have an LG Rebel 2 L57BL Tracfone that I've read is a variant of an LG K4 2017 LTE.
I have tried like every combination of buttons to get into fastboot but can only get into Recovery Mode. Using sudo adb reboot bootloader or sudo adb reboot-bootloader does not work, it just reboots the phone. I have managed to get the phone to boot into safe mode as well while messing with different buttons combinations and times.
I am just trying to get this phone rooted but I'm having a hell of a time. I am running Linux and Windows. Does anybody have any idea how to get into fastboot mode or how to root this device? It would be awesome, Thanks
Click to expand...
Click to collapse
Aaaaah.Unlock your bootloader First?
Sent from my Nexus 6P using Tapatalk
Knuxyl said:
I cannot seem to get this phone into the bootloader, download mode, or fastboot mode. I also can't get any rooting programs to work.
I have an LG Rebel 2 L57BL Tracfone that I've read is a variant of an LG K4 2017 LTE.
I have tried like every combination of buttons to get into fastboot but can only get into Recovery Mode. Using sudo adb reboot bootloader or sudo adb reboot-bootloader does not work, it just reboots the phone. I have managed to get the phone to boot into safe mode as well while messing with different buttons combinations and times.
I am just trying to get this phone rooted but I'm having a hell of a time. I am running Linux and Windows. Does anybody have any idea how to get into fastboot mode or how to root this device? It would be awesome, Thanks
Click to expand...
Click to collapse
Hey, try removing the battery, pressing the vol+ button & plugging it into PC, then you should see a little screen show up about having no battery to charge,
So while still holding the vol+ button on the device, with it still plugged into the PC, insert your battery back into the phone, don't take ur finger off the vol+ button until after you are in the Download Mode (at least my rebel 1 thru TracFone does it just fine)
Similar problem
What apps did you use to root? I have lg rebel 2. Also will I still have the same rom so the stock can be backed up or will rooting it alter the rom
OP, did you find anything new about rooting this phone as I have the same exact problem and I need a root
I have the 58vl (cdma variant) and from the research I've done tonight it looks like the only hope is porting twrp from a similar msm8909 device but using our kernel as well as modifying the partition layout. I've done this with similar low end devices with success, with that being said there has also been a few bricks in the wall as well. I suppose this phone qualifies as cheap enough to mess with, with little to lose. I can probably provide a recovery.img for the l58vl model, but gsm users should use at their own risk. I'll of course test the recovery.img on my device before releasing publicly. Really the only real reason I need this is for disabling anything lower than 4g because the tf Verizon network does not seem to allow roaming any at all unless it is 4g/lte.. I can have 3 bars on 3g and have no sms/voice/data, however in that exact same spot if I manage to skip the 3g network and hook onto lte with only one bar I've got service. With gsm variants the phone service menu / engineer mode probably works? But with cdma it doesn't and i need to provide a build.prop mod on order to disable the cellular radio on any technology older than 4g.. Otherwise I'd not really even need root myself with this device.
linuxsociety said:
I have the 58vl (cdma variant) and from the research I've done tonight it looks like the only hope is porting twrp from a similar msm8909 device but using our kernel as well as modifying the partition layout. I've done this with similar low end devices with success, with that being said there has also been a few bricks in the wall as well. I suppose this phone qualifies as cheap enough to mess with, with little to lose. I can probably provide a recovery.img for the l58vl model, but gsm users should use at their own risk. I'll of course test the recovery.img on my device before releasing publicly. Really the only real reason I need this is for disabling anything lower than 4g because the tf Verizon network does not seem to allow roaming any at all unless it is 4g/lte.. I can have 3 bars on 3g and have no sms/voice/data, however in that exact same spot if I manage to skip the 3g network and hook onto lte with only one bar I've got service. With gsm variants the phone service menu / engineer mode probably works? But with cdma it doesn't and i need to provide a build.prop mod on order to disable the cellular radio on any technology older than 4g.. Otherwise I'd not really even need root myself with this device.
Click to expand...
Click to collapse
hey did u managed to create an image of twrp?
I'm having trouble rooting my lgl57bl.can someone help me plz.
LilAnt530 said:
Hey, try removing the battery, pressing the vol+ button & plugging it into PC, then you should see a little screen show up about having no battery to charge,
So while still holding the vol+ button on the device, with it still plugged into the PC, insert your battery back into the phone, don't take ur finger off the vol+ button until after you are in the Download Mode (at least my rebel 1 thru TracFone does it just fine)
Click to expand...
Click to collapse
Can I see a video of this by chance ?
You're sure just holding some of the buttons from powered off isn't enough ?