Database Info

Need a tester for anything?

For all you smart folks out there working hard to get this bootloader unlocked for the rest of us, I'd be happy to test anything out for you that you are unwilling or unable to test yourselves. My A2 is stuck in bootloop mode (yes, my own stupid fault) and I can only access via fastboot, no adb. Just let me know, give me some decent instructions for what you want, and I will post the results.

If you can access the stock recovery have you tried flashing the Chinese leak via RSD lite? Might be worth a try

rsd lite
JRW 28 said:
If you can access the stock recovery have you tried flashing the Chinese leak via RSD lite? Might be worth a try
Click to expand...
Click to collapse
what version of rsd do you use? ive found many differnet versions via google search and didnt know which one to grab. seached this forum and didnt find anything. any help would be great. thanks

JRW 28 said:
If you can access the stock recovery have you tried flashing the Chinese leak via RSD lite? Might be worth a try
Click to expand...
Click to collapse
I'm on a Mac and have been using sbf_flash, would it be possible like that? I already tried flashing the boot.img from the Chinese one.
I tried over the weekend to use RSD w/Wine but couldn't get it to work.

Im on my phone right but the newest one will be the best....can't remember of the top of my head....and I think I may have been wrong ...to use RSD lite I think you would use BP tools

You have to use RSD lite, and wine does not work. You need to find a way to run windows, there are free vm utils like virtualbox, and I am sure you know how to get copies of windows. I won't get into that here though. You also need version 5.5 or higher of rsd light.
Jim
Sent from my MB865 using xda premium

jimbridgman said:
You have to use RSD lite, and wine does not work. You need to find a way to run windows, there are free vm utils like virtualbox, and I am sure you know how to get copies of windows. I won't get into that here though. You also need version 5.5 or higher of rsd light.
Jim
Sent from my MB865 using xda premium
Click to expand...
Click to collapse
I already have VirtualBox installed, but it might take me a couple days to track down a copy of windows to install on it. If I can get that and RSD up and running, I'll let y'all know!

There are legal ways get windows for temporary usage... Win8 developer preview, & win7 has 30days before it needs a serial/activation...

Allright... Got Windows installed in VB and installed the SDK and RSD lite 5.6. The Chinese download is on my desktop. I think all I'm lacking is getting the VM to pick up the phone on the USB port, I can't seem to get it. If it ain't one thing...

The detection issue might set you back a bit for a while... I'm not sure anyone has found a surefire way to get A2s that aren't stuck in a bootloop to connect to the PC when they aren't.

If you can get into the boot options upon boot choose BP tools. I thinks this will let you be able to run RSD lite from there.

I'm about a half step closer, I suppose. VB can see the phone in fastboot mode when it's connected to my USB hub, but not directly to the computer. Still can't get it to where I can read it though.

Is RSD lite recognizing the phone?

JRW 28 said:
Is RSD lite recognizing the phone?
Click to expand...
Click to collapse
No, haven't been able to get there yet.

No joy
Finally broke down and used the wife's Windows machine, VB & USB devices seems to be a crap shoot all around.
RSD recognized the phone in fastboot mode. Didn't get very far w/the flashing though, received this error:
Failed flashing process. Failed flashing process. 2/15 flash cdt.bin "cdt.bin" -> Phone returned FAIL; phone connected
I'm still open to suggestions and willing to give something else a shot.

Major problem - tf101 bricked

I rooted my tablet and it worked fine. I then proceded to modify my build.prop file. My friend sent me his to work from but i mistakenly copied it over directly. Now the tablet will not boot. How can i restore to factory or whatever i need to do?
(please spare me from the "you shouldn't have done that" speech, trust me i know lol)

need more info
what model number do you have, what can you get into, what cant you get into etc

lowgoz said:
need more info
what model number do you have, what can you get into, what cant you get into etc
Click to expand...
Click to collapse
sorry, late night, not really with it lol
its model tf101 US version and it has the latest ICS firmware, stock recovery. i can get it to load the recovery screen with the wipe data option. sorry for my poor terminology im new to the whole android rooting stuff.

You can download the latest firmware from Asus website.
Unzip it to get the zip file from inside and put it on your external sd card. Boot into recovery and let it flash the ROM again.
Plenty of thread to show step by step if needed.
You could also try to adb push the original file to your tf

baseballfanz said:
You can download the latest firmware from Asus website.
Unzip it to get the zip file from inside and put it on your external sd card. Boot into recovery and let it flash the ROM again.
Plenty of thread to show step by step if needed.
You could also try to adb push the original file to your tf
Click to expand...
Click to collapse
i've already tried this. it just gives me the dead android with a red exclamation point. also for some reason my windows pc says "the device cannot start" and im unable to use adb.

What is the serial number of your tf?
Hopefully it's one that's nvflash compatible

baseballfanz said:
What is the serial number of your tf?
Hopefully it's one that's nvflash compatible
Click to expand...
Click to collapse
dont think it is, starts with B90

i think the mods rudely removed my post in general forum where i was actually getting some help, but whatever. still need help here if anyone has any ideas.

I think you have several options-
1) use adb to fix your build.prop file. This can be done in the rom or recovery. There are adb guides coming out of the woodworks on here. If windows doesn't recognize your device, then get linux or a mac and kick windows to the curb. Nothing but grief.
2) install the correct build.prop via a flashable zip. You can extract the build.prop from the system dump I have in the dev section. Yeah, it's a slow download, but I'm working on something to move it to a faster server.
There's no easy fix... yet. adb will be the "easiest" fix.

gee one said:
I think you have several options-
1) use adb to fix your build.prop file. This can be done in the rom or recovery. There are adb guides coming out of the woodworks on here. If windows doesn't recognize your device, then get linux or a mac and kick windows to the curb. Nothing but grief.
2) install the correct build.prop via a flashable zip. You can extract the build.prop from the system dump I have in the dev section. Yeah, it's a slow download, but I'm working on something to move it to a faster server.
There's no easy fix... yet. adb will be the "easiest" fix.
Click to expand...
Click to collapse
ok well heres the issue. earlier way early this morning when this first started i was able to adb in, saw it was going in an infinite loop in logcat. now for some reason windows, and i've tried 3 installations of it, says the device cannot start. to me it sounds like something weird with the device. any ideas?

The exact same thing happened to me. I booted into recovery and restored from a nandroid backup. Maybe their is a way you can still install recovery and you someone can lend you their nandroid?

roflcopterofl said:
The exact same thing happened to me. I booted into recovery and restored from a nandroid backup. Maybe their is a way you can still install recovery and you someone can lend you their nandroid?
Click to expand...
Click to collapse
i think its too late for that now, adb wont work. im guessing now maybe the recovery isnt working because i had a newer version of the os than i can get a copy of right now. anyone have/know where i can get 9.2.1.17 fw?

If he is getting the dead android, it sounds like he has a stock recovery.
regarding adb, if windows won't start, then get a linux live cd. I think rebound128 has a minimal one in the dev section for nvflash rooting, but it will probably work. Or you can download a ubuntu live cd and boot from there.
one other option would be to wait until asus releases the 9.2.1.17 firmware on their site and download that. You should be able to flash it without the dead android. the 8.6.5.21 won't work because it won't let you install to a previous version. You can only install your current version or later. In your case, that would be 9.2.1.17.
At this point, I would say that windows is holding you back. I wish I had a $1 for every person that gets screwed over by windows- I would be as rich as Bill Gates used to be.

gee one said:
If he is getting the dead android, it sounds like he has a stock recovery.
regarding adb, if windows won't start, then get a linux live cd. I think rebound128 has a minimal one in the dev section for nvflash rooting, but it will probably work. Or you can download a ubuntu live cd and boot from there.
one other option would be to wait until asus releases the 9.2.1.17 firmware on their site and download that. You should be able to flash it without the dead android. the 8.6.5.21 won't work because it won't let you install to a previous version. You can only install your current version or later. In your case, that would be 9.2.1.17.
At this point, I would say that windows is holding you back. I wish I had a $1 for every person that gets screwed over by windows- I would be as rich as Bill Gates used to be.
Click to expand...
Click to collapse
im hearing that from everyone i talk to but in this case i dont think its windows thats causing the problem. like i said, i've tried THREE different installations of windows, and none of them pick up the tablet properly, they see "ASUS Android MTP Device" for some reason, and then it says that device isnt working properly. im probably just gonna wait till asus releases the new firmware. that will definately work....right?

joshcrumley100 said:
im hearing that from everyone i talk to but in this case i dont think its windows thats causing the problem. like i said, i've tried THREE different installations of windows, and none of them pick up the tablet properly, they see "ASUS Android MTP Device" for some reason, and then it says that device isnt working properly. im probably just gonna wait till asus releases the new firmware. that will definately work....right?
Click to expand...
Click to collapse
just tried it on linux, adb wont detect the device, so no luck there. im just hoping the .17 firmware will work on it, if not idk what to do.

In linux, with the TF plugged into the USB, what do you get when you type "lsusb" ??

gee one said:
In linux, with the TF plugged into the USB, what do you get when you type "lsusb" ??
Click to expand...
Click to collapse
it had Asus Transformer or something like that, it had it listed, but thats all. couldnt interact with the device.

Perhaps adb/debugging is not activated in the rom?
I think you'll have to wait until Asus releases a new update, although the last update checked the md5 sum of the build.prop file, so if you made any changes it won't flash.

gee one said:
Perhaps adb/debugging is not activated in the rom?
I think you'll have to wait until Asus releases a new update, although the last update checked the md5 sum of the build.prop file, so if you made any changes it won't flash.
Click to expand...
Click to collapse
Wait so you're saying even after i get the new firmware it still may not work? What a load of BS...

Originally Posted by gee one
Perhaps adb/debugging is not activated in the rom?
I think you'll have to wait until Asus releases a new update, although the last update checked the md5 sum of the build.prop file, so if you made any changes it won't flash.
Click to expand...
Click to collapse
Wait so you're saying even after i get the new firmware it still may not work? What a load of BS...
Click to expand...
Click to collapse
Sorry for the confusion- I think the full 9.2.1.17 rom that asus posts on their website will work, as long as it checks the rom version in recovery default.prop. It's not clear to me how it checks the "rule" that prevents downgrading. It's a maybe, but there's still a chance.
sent from my cyanogen(mod) vision

[Q] Rooting with Toolkit Fails: "Unauthorized"

After a horrid couple of days staring at a "system software unauthorized by verizon" screen and being unable to get to DL mode I have un-softbricked my phone by pushing
HOME_I535VRALF2_I535VZWALF2_618049_REV09_user_low_ship.tar.md5. That works fine.
However, pushing the boot image fails (Samsung-Updates.com-SCH-I535-VZW-I535VRALF2_Kernel.zip)
Evidently the Boot.img is perhaps optional.
After the boot image failed I tried rooting by using Samsung Galaxy Toolkit. That's failed a few times on two different computers, each time returning me to the "System software unauthorized by Verizon" screen. The phone reboots a few times (twice?). Odin launches and pushes the first file. When the second Odin flash starts it FAILS and I get the "unauthorized" message on the phone.
I've also tried to root by using GS3_debugfs-root_r2.zip (well, the files within actually). The latter requires Android SDK which I think I have set up correctly. Also no luck.
Of perhaps some relevance is that my Win 7 machine keeps telling me that the device drivers aren't installed properly (although I've done it several times and both the installer and Device Manage seems to think they are there). Samsung Toolkit can't read the device ID. However an XP machine does see the phone so maybe it is something about the Win 7 machine.
The root fail happens on both machines at the same point in the process so I assume their is an issue on the phone side.
And suggestions?
(Of course when the phone does come alive Verizon keeps trying to push this new search-crippling update. One more problem I don't need today).
Do I need some other boot.img or some other method or what?

maplewood said:
After a horrid couple of days staring at a "system software unauthorized by verizon" screen and being unable to get to DL mode I have un-softbricked my phone by pushing
HOME_I535VRALF2_I535VZWALF2_618049_REV09_user_low_ship.tar.md5. That works fine.
However, pushing the boot image fails (Samsung-Updates.com-SCH-I535-VZW-I535VRALF2_Kernel.zip)
Evidently the Boot.img is perhaps optional.
After the boot image failed I tried rooting by using Samsung Galaxy Toolkit. That's failed a few times on two different computers, each time returning me to the "System software unauthorized by Verizon" screen. The phone reboots a few times (twice?). Odin launches and pushes the first file. When the second Odin flash starts it FAILS and I get the "unauthorized" message on the phone.
I've also tried to root by using GS3_debugfs-root_r2.zip (well, the files within actually). The latter requires Android SDK which I think I have set up correctly. Also no luck.
Of perhaps some relevance is that my Win 7 machine keeps telling me that the device drivers aren't installed properly (although I've done it several times and both the installer and Device Manage seems to think they are there). Samsung Toolkit can't read the device ID. However an XP machine does see the phone so maybe it is something about the Win 7 machine.
The root fail happens on both machines at the same point in the process so I assume their is an issue on the phone side.
And suggestions?
(Of course when the phone does come alive Verizon keeps trying to push this new search-crippling update. One more problem I don't need today).
Do I need some other boot.img or some other method or what?
Click to expand...
Click to collapse
When did he update the toolkit for verizon phones?

piiman said:
When did he update the toolkit for verizon phones?
Click to expand...
Click to collapse
Not sure who you mean by "he" when you ask when the toolkit was updated. I downloaded it pretty recently.

mapleood said:
Not sure who you mean by "he" when you ask when the toolkit was updated. I downloaded it pretty recently.
Click to expand...
Click to collapse
Where did you get it from? If its the toolkit im thinking of he didn't have a vzw version. Also if he does have new vzw version I want it if he doesn't then that's your problem.

piiman said:
Where did you get it from? If its the toolkit im thinking of he didn't have a vzw version. Also if he does have new vzw version I want it if he doesn't then that's your problem.
Click to expand...
Click to collapse
Can't say I recall where I got it from.
But if the Toolkit ain't the solution then I need a plan C.
But I suspect that I still need to successfully flash the boot.img. Which so far I can't. Independent of evidence my guess is that if I could flash that boot.img then the rooting might work. Just a guess.

http://forum.xda-developers.com/showthread.php?t=1762709
This guide is a sticky for a reason and will be your best friend.
Sent from my Galaxy Nexus using xda app-developers app

maplewood said:
Can't say I recall where I got it from.
But if the Toolkit ain't the solution then I need a plan C.
But I suspect that I still need to successfully flash the boot.img. Which so far I can't. Independent of evidence my guess is that if I could flash that boot.img then the rooting might work. Just a guess.
Click to expand...
Click to collapse
Hmmmm so you dont even know if you flashed a boot.img for our phone or where the tools came from? Not good
If your guess is correct and your pc recognized the phone and you can use adb you could use the dd command to push the boot.img. but if you dont have the correct drivers none of the above will work. Good luck
Or you could follow that link you just got
---------- Post added at 05:20 PM ---------- Previous post was at 04:33 PM ----------
http://forum.xda-developers.com/showthread.php?t=1762204
This may also help you out as its very detailed.

Unable to unlock bootloader

As the title says, i cant manage to unlock the bootloader. My device is GM1910, i am running 9.5.10 GM21AA. i went to OB2 but then rolled back and decided i wanted to unlock and root, but for some reason i cannot. followed all the proper guides, tried the adb method, but when i type fastboot oem unlock, it just says waiting for device. I also tried the all-in-one tool and same problem, the moment i check for bootloader status, the application hangs. has anyone faced this issue before? could use some help. Thanks
Using the OP cable and tried on both USB 3 and 2

linx1287 said:
As the title says, i cant manage to unlock the bootloader. My device is GM1910, i am running 9.5.10 GM21AA. i went to OB2 but then rolled back and decided i wanted to unlock and root, but for some reason i cannot. followed all the proper guides, tried the adb method, but when i type fastboot oem unlock, it just says waiting for device. I also tried the all-in-one tool and same problem, the moment i check for bootloader status, the application hangs. has anyone faced this issue before? could use some help. Thanks
Using the OP cable and tried on both USB 3 and 2
Click to expand...
Click to collapse
If your on sprint you cant unless you pay off the phone or have it active for 50days. Not sure about t-mobile. heres a helpful link tho.
https://forum.xda-developers.com/oneplus-7-pro/how-to/discussion-sprint-oneplus-7-pro-5g-t3963319

lonewolf2k2 said:
If your on sprint you cant unless you pay off the phone or have it active for 50days. Not sure about t-mobile. heres a helpful link tho.
https://forum.xda-developers.com/oneplus-7-pro/how-to/discussion-sprint-oneplus-7-pro-5g-t3963319
Click to expand...
Click to collapse
Sorry but mine isnt any carrier phone GM1910 is the chinese international running GM21AA

Sounds more like a USB connectivity issue, than a problem with the device. Try the command: fastboot devices
And if it just hangs, then you don't have USB fastboot connectivity.
To be clear, the phone is booted to bootloader-fastboot mode (which is required for fastboot commands)?

You need the latest windows 10 drivers, adb & fastboot. And off course Open Beta it's still young... meanning sh.. could happen.

redpoint73 said:
Sounds more like a USB connectivity issue, than a problem with the device. Try the command: fastboot devices
And if it just hangs, then you don't have USB fastboot connectivity.
To be clear, the phone is booted to bootloader-fastboot mode (which is required for fastboot commands)?
Click to expand...
Click to collapse
null0seven said:
You need the latest windows 10 drivers, adb & fastboot. And off course Open Beta it's still young... meanning sh.. could happen.
Click to expand...
Click to collapse
Yes adb devices does register and adb reboot bootloader command does take me to the bootloader, but when i tried the fastboot devices it didnt register, so i think you are on to something. I will check again once i get home today. Thanks
I was on open beta, i reverted to 9.5.10 Pie in order to unlock bootloader and root.
If its not too much trouble, could you link me to the drivers (i would ask adb too but seeing as it works when i do adb devices command, i think thats working fine)? Thanks

Platform tool 2.9.0.4 (adb-fastboot), latest
https://android.gadgethacks.com/how...stall-adb-fastboot-mac-linux-windows-0164225/

null0seven said:
Platform tool 2.9.0.4 (adb-fastboot), latest
https://android.gadgethacks.com/how...stall-adb-fastboot-mac-linux-windows-0164225/
Click to expand...
Click to collapse
Thanks. This was the version i was working with yesterday. Could you link me to the usb drivers i might need? Since response stops at fastboot i am assuming the drivers are to blame

One thing you can try, on Windows go to Device Manager, find the phone, and pick the option to update the drivers. Select the drivers manually (don't let Windows find the drivers automatically). Then the one called Generic Android Device (or something like that).
I sometimes have to do this, to get Windows to work with adb/fastboot.
This is all on my old Windows 7 machine. So if you have Win 10, it might be a bit different.

redpoint73 said:
One thing you can try, on Windows go to Device Manager, find the phone, and pick the option to update the drivers. Select the drivers manually (don't let Windows find the drivers automatically). Then the one called Generic Android Device (or something like that).
I sometimes have to do this, to get Windows to work with adb/fastboot.
This is all on my old Windows 7 machine. So if you have Win 10, it might be a bit different.
Click to expand...
Click to collapse
Thank you. You were right about the driver issue....going through the device manager yielded the driver situation. Had to enable debugging to finally let the driver install. I completely forgot about this. I had to do this same thing when i had to unlock bootloader and twrp for my HTC 10.
Now that i am done with this, a few final things i would like to clear out....doing the local update on root to restore stock system is still valid right? and if i want to go full stock from say custom roms like los and so on, a flash through MSM tool? Will doing that also relock the bootloader? Sorry for all the noob questions and thanks in advance.

Local upgrade works with/without root or twrp.
MSM tool revert youre phone like it's out of the factory. Bootloader locked, no root, no twrp.
If you come back to Oos from custom roms you need to Format Data (this will wipe ALL in youre phone. everything).

NEED HELP UNBRICKING ONEPLUS 8T WILL PAY FOR REPAIR AND OR WALKTHROUGH IN NYC arwa

Kb2005 international version just purchased. Rooted but lost wifi access tried to fix and bricked stuck in fastboot repeat and red boot loop

Hi,
You may try to boot to safe mode. Just a thought. If you choose to do it, I am not responsible if it would not work or if something else wrong happens.
Good luck!

Have you MSM'd back to stock? https://androidfilehost.com/?fid=2188818919693750637

craznazn said:
Have you MSM'd back to stock? https://androidfilehost.com/?fid=2188818919693750637
Click to expand...
Click to collapse
Mam isnt working this should work on a vm too right ive installed all usb drivers too

amplatfus said:
Hi,
You may try to boot to safe mode. Just a thought. If you choose to do it, I am not responsible if it would not work or if something else wrong happens.
Good luck!
Click to expand...
Click to collapse
Thanks for the reply thats fine im ok i just want to try and get it back its a brand new phone

Method 1. Download Full ROM, and Payload Dumper. Extract payload.bin and put it to payload_input folder and all *.img files will be in payload_output folder. Use fastboot flash boot boot.img command and reboot. Device should work after reboot. If you need root, either flash a patched boot.img or use flashboot to flash TWRP and then install Magisk from TWRP.
Method 2. Manually flash *.img files. Reference: [GUIDE] Unbrick or restore to OOS using only fastboot
Method 3. Use MSMtool to wipe and restore your phone.
Note: If you lost WiFi AFTER your device is rooted, and if you ever installed a custom kernel, it's probably the RAMDISK (can't remember where I saw it before) causing the issue. Easy solution, flash same custom kernel again. Or try different kernels.

So these unbricktools here don't work for you?
Index of /list/Unbrick_Tools/OnePlus_8T

Millyrocker said:
Mam isnt working this should work on a vm too right ive installed all usb drivers too
Click to expand...
Click to collapse
EDL mode will disconnect/reconnect several times and change connection protocol. Your virtual machine may lost device due to this process.
So better on Windows PC.

ULTRAJC said:
EDL mode will disconnect/reconnect several times and change connection protocol. Your virtual machine may lost device due to this process.
So better on Windows PC.
Click to expand...
Click to collapse
Im on linux right now im trying to find a way to install windows but even thats not working smh

Millyrocker said:
Im on linux right now im trying to find a way to install windows but even thats not working smh
Click to expand...
Click to collapse
I applaud your use of linux! Unfortunately, I've not found a good solution under linux to do what the windows MSM tool can do. I had to book in to a full Win install in order to use it on my phone as well.
On a positive note, it's nearly impossible to truely brick these phones. The negative is the MSM tool needs windows. Unless someone can point to a linux solution (which I'd love) you may need to find a friend with Windows and borrow their computer...
The fact you are in fastboot loop makes me think you should be able to just fastboot flash everything manually. MSM is the nuclear option. I'd try getting the stock full ROM and manually flashing everything in fastboot.
What fastboot are you using? I've found that the one in many linux distributions are old. Download the latest from Android https://dl.google.com/android/repository/platform-tools-latest-linux.zip and use this.

Millyrocker said:
Im on linux right now im trying to find a way to install windows but even thats not working smh
Click to expand...
Click to collapse
EDL mode will reboot itself if there was no command sent to the phone. So you need to run MSM tool first and once you see the phone is recognized, just execute.
A real Windows should make whole process a lot more easier. If you use a VM, as long as Windows can recognize Qualcomm Modem driver, it should work too.