Database Info

[Completed] [Q] unlocking a proscan tablet with adb

I have a proscan tablet that is locked and the max password atempt is locked and the google account is locked there isnt a normal bootloader than i can wipe it from. I can get adb to work but cant find out how to flash a stock rom to it with adb. I have the img but dont know how to flash it. I have adb installed on my ubuntu pc just don't know the commands any help would be apppreciated.

doesn't look like there's a lot out here for your device. The only thing i could find that may be of some use is
Might be of some use.
Oh and generally you wipe your device in recovery not the bootloader. So maybe try that first
Good luck

Sorry I meant recovery not bootloader there isn't a recovery like on most devices

bump

I'm sorry man. I did not mean to leave you high and dry. I thought I had given you a link to look into. Try this link here. There's not a lot out here for your device so if that is not what you're looking for you can ask your question here

[Completed] [Q] HTC One X+ (AT&T) -TWRP issues/ ROM issues

First of all I did check other forums, etc. before coming here. I also spent countless hours researching the rooting process. Here is my problem:
I'm attempting to root an HTC One x+ (AT&T) that I purchased on amazon. I'm using a Windows 8.1 system, and The latest Windroid tool (v2.3). With the tool I was able to unlock bootloader. The next step (flash a recovery) is where I believe I made my mistake. For my phone there was 2 choices (global and AT&T). I hence learned that my phone is evitare-ul, so I should have used the AT&T version, but I flashed it with the Global TWRP. I also made some errors in that I somehow wiped out the stock ROM (still don't know how that happened). I posted a question in the HTC One x+ forum, and was answered by LLoir (Thank you). The response was:
"You need TWRP for the EVITAREUL and then use the sideload function to put a rom on, also you need to manually flash the boot.img in fastboot. There's no MTP for TWRP Evitareul hence the reason for sideload."
Being new to "rooting" I wasn't sure what Llior was saying, ergo all the research. OK, so I found the TWRP-evitare-ul, but it WON'T FLASH! (Via Windroid). Windroid says it worked, but there is no recovery installed. I am however able to flash and remove the "global TWRP". Lloir answer also referenced 'NO MTP for TWRP evitareul", so I assume it is indeed the global TRWP I had flashed (it does has MTP wish I can enable or disable). When "enabled" my windows computer sees my phone, when "disabled" it doesn't see anything connected. I Need Help in Finding a way to Flash the "TWRP - evitareul" onto my phone.
A related issue is that after each Flash attempt when I attempt to reboot The screen on my phone changes from the "bootloader" screen to the "htc" screen And nothing more. Windroid is waiting and waiting and waiting. I end up pressing the power and volume down button combo to get back to bootloader. With the "global TWRP" I can boot to recovery, but I am in limbo when I try to flash with the "TWRP evitareul". It never installs! I'm guessing I have a booting issue.
Based on various forum articles I believe I'm to get the "Boot.img" to flash when I exe the rom file? I really rather just have the "zip" version I can use with Windroid. I'll need guidance and help there.
As it stands right now I have unlocked bootloader and apparently have the wrong TWRP installed. I have issues with my phone being recognized by my computer, and at various times my computer states there is a problem with windroid (when phone connected via usb). Is using a windows 8.1 system an issue. I can go to my old XP
In summary I need:
1) Find a way to flash the correct TWRP into my HTC One x+
2)be able to flash a ROM (MagioRom).
3)Flash the boot/img.
Guidance and help is appreciated. At least point me in the right direction. This is why I posted here. Please excuse my ignorance. Thanks

dpsrams said:
First of all I did check other forums, etc. before coming here. I also spent countless hours researching the rooting process. Here is my problem:
I'm attempting to root an HTC One x+ (AT&T) that I purchased on amazon. I'm using a Windows 8.1 system, and The latest Windroid tool (v2.3). With the tool I was able to unlock bootloader. The next step (flash a recovery) is where I believe I made my mistake. For my phone there was 2 choices (global and AT&T). I hence learned that my phone is evitare-ul, so I should have used the AT&T version, but I flashed it with the Global TWRP. I also made some errors in that I somehow wiped out the stock ROM (still don't know how that happened). I posted a question in the HTC One x+ forum, and was answered by LLoir (Thank you). The response was:
"You need TWRP for the EVITAREUL and then use the sideload function to put a rom on, also you need to manually flash the boot.img in fastboot. There's no MTP for TWRP Evitareul hence the reason for sideload."
Being new to "rooting" I wasn't sure what Llior was saying, ergo all the research. OK, so I found the TWRP-evitare-ul, but it WON'T FLASH! (Via Windroid). Windroid says it worked, but there is no recovery installed. I am however able to flash and remove the "global TWRP". Lloir answer also referenced 'NO MTP for TWRP evitareul", so I assume it is indeed the global TRWP I had flashed (it does has MTP wish I can enable or disable). When "enabled" my windows computer sees my phone, when "disabled" it doesn't see anything connected. I Need Help in Finding a way to Flash the "TWRP - evitareul" onto my phone.
A related issue is that after each Flash attempt when I attempt to reboot The screen on my phone changes from the "bootloader" screen to the "htc" screen And nothing more. Windroid is waiting and waiting and waiting. I end up pressing the power and volume down button combo to get back to bootloader. With the "global TWRP" I can boot to recovery, but I am in limbo when I try to flash with the "TWRP evitareul". It never installs! I'm guessing I have a booting issue.
Based on various forum articles I believe I'm to get the "Boot.img" to flash when I exe the rom file? I really rather just have the "zip" version I can use with Windroid. I'll need guidance and help there.
As it stands right now I have unlocked bootloader and apparently have the wrong TWRP installed. I have issues with my phone being recognized by my computer, and at various times my computer states there is a problem with windroid (when phone connected via usb). Is using a windows 8.1 system an issue. I can go to my old XP
In summary I need:
1) Find a way to flash the correct TWRP into my HTC One x+
2)be able to flash a ROM (MagioRom).
3)Flash the boot/img.
Guidance and help is appreciated. At least point me in the right direction. This is why I posted here. Please excuse my ignorance. Thanks
Click to expand...
Click to collapse
you should continue ask your question in http://forum.xda-developers.com/htc-one-x2/help/htc-one-x-stuck-twrp-v2-8-5-0-os-t3071068
also see HOX+ Tutorial for Unlocking, Rooting & installing a custom ROM [BEGINNERS FRIENDLY ]

No reply, thread will be closed.

[Completed] Xperia Z No Recovery

So got an interesting issue
My c6603 has no usb port (broke)
BUT does have full root running existance and can access adb via wifi
The problem i have is i haven't used recovery for a while and wanted to upgrade to lolipop (ExistanceY).
If i reboot i cant get into it and there is no pink light
Using shell to reboot to recovery, a shortcut or adb also does not work. just boots up as normal.
Any ideas
I have tried reimaging fotakernel with TWRP but nothing. the recovery installers dont work either they either come up that they cant find the partition or doesn't have an image for the device or comes back as successfull

Hi, thank you for using XDA Assist. Your best bet is to ask in your device specific forum, which I see you know where it is. But just in case, http://forum.xda-developers.com/xperia-z. They are the experts on your device. But you have another issue too. Since 5.x you have to be stock, no root, for the updates to work. Check you device specific forum for more information.

cheers, that page is actually open in my other tab, created a new post in the wrong one. my bad. again cheers

Thread closed.

[Completed] Soft Bricked UMI Iron Help

Hi,
I recently bought an Umi Iron and believe I have accidentally managed to soft brick it (based on what ive found on google and the forums here) I need a way to get it working again and have some ROMS (2 official ones) which are compatible for the device. The device will boot into recovery and allows restoration from an SD card, ABD Push or the cache. The cache is empty and although i have searched for how to do it from an SD card i have found no information (I've tried putting the .zip files onto the device and installing those but the device says "installation aborted"). I have a SDK which I am attempting t learn to use in order to fix the device. Any information about how to use the program/get the new ROM flashed via fastboot would be much appreciated as I have very little knowledge of what I am doing as I have never attempted to root or flash a phone. The phone comes pre rooted from the factory (I dont know if this info is relevant but I'm working on the assumption the more info i can give the better). The device entered this startup loop when i removed an app which i had accidentally installed as a system file while trying to use an app to move it to my SD card. Any information and help is much appreciated

Hi,
I can't find anything relevant on XDA for your device and issue, but perhaps the members in this thread can help..
http://forum.xda-developers.com/android/general/umi-iron-unibody-alloy-dual-led-t3127905
Good luck!

Hi Darth,
Many thanks for your reply, since i posted this thread I have done some further research and narrowed the problem down further. The device runs android 5.1 and there is a setting in the developer settings which locks the OEM bootlocker. This is the issue i am having. Because the device has this option checked, I cannot unlock the bootloader to install a custom rom to rectify the issue as i cannot turn the device on to access these settings. I have seen many people have had this problem with devices and android 5.1 including Nexus and HTC phones. I have been unable to find a fix for this issue though so if you know of any articles which may point me in the direction that would be most helpful
Thanks again

I would say the best place to ask about that is in the thread I linked above. But if that's not helpful, you could ask here,
http://forum.xda-developers.com/showthread.php?t=2257421
Every device is different as far as if or how the bootloader can be unlocked. So you really need an answer specific to your device.
Hope it works out for you!

Rooted and bricked without a custom recovery.

rooted bricked boost mobile moto G. 4.4.4. i messed up my phone while editing "build.prob" with es root file i believe and when i was done editing i clicked on the folder looking icon on the top right corner which i thought was enter/save but itwas something else that rearranged the letters after it booted i only got bootloader unlocked warning screen and a plain black screen after and thats it however i can also get to the the fastboot menu. so any way can i get my phone back with maybe just using adb and fastboot. i just rooted my phone like a week ago so never got to play around with it so i have alot to catch up with on terms and research dont worry i'll look up what you tell me to do rather than keep on asking how how and how. well guys hope you can help me thank you.

XDA Visitor said:
rooted bricked boost mobile moto G. 4.4.4. i messed up my phone while editing "build.prob" with es root file i believe and when i was done editing i clicked on the folder looking icon on the top right corner which i thought was enter/save but itwas something else that rearranged the letters after it booted i only got bootloader unlocked warning screen and a plain black screen after and thats it however i can also get to the the fastboot menu. so any way can i get my phone back with maybe just using adb and fastboot. i just rooted my phone like a week ago so never got to play around with it so i have alot to catch up with on terms and research dont worry i'll look up what you tell me to do rather than keep on asking how how and how. well guys hope you can help me thank you.
Click to expand...
Click to collapse
Hello, and thank you for using XDA Assist!
Quite possibly my easiest problem of the night.
Your bootloader is unlocked. So....flash custom recovery. One that can do adb as well (unless you Moto G also has an SD card slot, but if we are talking about the original 2013 model, then one won't be there).
Then, reboot into recovery. Make a backup. Pull the backup files to your PC (either by adb or MicroSD, if available). Extract the system backup file (is a tarball) in a Linux filesystem. Fix up your build.prop mistakes. Tar system back up, and bundle the backup as a second set to push back to your device. Restore that backup (need only be system partition). Profit.
Any further questions, can ask in the following thread (assuming you have the 2013/1st gen non-LTE version - otherwise reply here with variant details for further instructions):
> Moto G > Moto G Q&A, Help & Troubleshooting > [RC-FAQ] >> Frequently Asked Questions for Motorola Moto G [Updated : 2015/09/23]
Please note, you will need to register for an account in order to post there.
Hope this helps, and good luck!

joel.maxuel said:
Hello, and thank you for using XDA Assist!
Quite possibly my easiest problem of the night.
Your bootloader is unlocked. So....flash custom recovery. One that can do adb as well (unless you Moto G also has an SD card slot, but if we are talking about the original 2013 model, then one won't be there).
Then, reboot into recovery. Make a backup. Pull the backup files to your PC (either by adb or MicroSD, if available). Extract the system backup file (is a tarball) in a Linux filesystem. Fix up your build.prop mistakes. Tar system back up, and bundle the backup as a second set to push back to your device. Restore that backup (need only be system partition). Profit.
Any further questions, can ask in the following thread (assuming you have the 2013/1st gen non-LTE version - otherwise reply here with variant details for further instructions):
> Moto G > Moto G Q&A, Help & Troubleshooting > [RC-FAQ] >> Frequently Asked Questions for Motorola Moto G [Updated : 2015/09/23]
Please note, you will need to register for an account in order to post there.
Hope this helps, and good luck!
Click to expand...
Click to collapse
im sorry man i shouldve updated and listed that i have usb debugging off -_- i was trying a stock fastboot method but ended up putting 4.3 or 4.4 instead without realizing so now its in a bootlooop still access to stock recovery tho. and so i was going to fastboot the 4.4.4 download from file factory but its down due to maintenance. so on to motorolla website i go and what ya know "cant unarchive". any ideas man? its a 45 dollar phone couldve easily replace it but something about leaving it as paper weight that will bug me forever haha plus lets not forget the satisfaction of solving the problem haha. and i have yet to read up on custom recovery which i will do if you believe it'll work. thanks for your reply man

jasj0410 said:
im sorry man i shouldve updated and listed that i have usb debugging off -_- i was trying a stock fastboot method but ended up putting 4.3 or 4.4 instead without realizing so now its in a bootlooop still access to stock recovery tho. and so i was going to fastboot the 4.4.4 download from file factory but its down due to maintenance. so on to motorolla website i go and what ya know "cant unarchive". any ideas man? its a 45 dollar phone couldve easily replace it but something about leaving it as paper weight that will bug me forever haha plus lets not forget the satisfaction of solving the problem haha. and i have yet to read up on custom recovery which i will do if you believe it'll work. thanks for your reply man
Click to expand...
Click to collapse
No problem.
USB debugging being off is only a consequence if planning to ADB in from system. Recovery has it's own rules.
Not sure about the "cannot unarchive" message, but if you can get the stock ROM, that's a viable option as well.

joel.maxuel said:
No problem.
USB debugging being off is only a consequence if planning to ADB in from system. Recovery has it's own rules.
Not sure about the "cannot unarchive" message, but if you can get the stock ROM, that's a viable option as well.
Click to expand...
Click to collapse
no luck with installing Stock Rom thru Custom Recovery im using twrp. suddenly my terminal wont let me fastboot the zip file because of
"unknown partition 'Rom.zip'
error: cannont determine image filename for 'Rom.zip'
and if it helps i tried using stock recovery with this method (installed. 4.4):
androidforumsDOTcom/threads/cdma-boostmobile-only-guide-on-returning-to-stocDOT.826108/
and adb works when im on custom recovery if that helps out
and i never got to do the back up build.prop method because i had already done the first stock recovery method which i feel mightve messed things up. thanks for your replies man it really means alot

jasj0410 said:
no luck with installing Stock Rom thru Custom Recovery im using twrp. suddenly my terminal wont let me fastboot the zip file because of
"unknown partition 'Rom.zip'
error: cannont determine image filename for 'Rom.zip'
and if it helps i tried using stock recovery with this method (installed. 4.4):
androidforumsDOTcom/threads/cdma-boostmobile-only-guide-on-returning-to-stocDOT.826108/
and adb works when im on custom recovery if that helps out
and i never got to do the back up build.prop method because i had already done the first stock recovery method which i feel mightve messed things up. thanks for your replies man it really means alot
Click to expand...
Click to collapse
Hello,
Fastboot is unable to flash zips unfortunately. That's the recoveries job.
If you can find fastboot images of stock, you can flash back that way.
Especially at this point, I would urge you to take advantage of the help thread I mentioned earlier. They know more about your device (particularly what's available and what not) they I would.
Hope this helps!