Database Info

Umi X2 bootloop

Hi all,
I'm trying for days to get my Umi X2 running again.
Momentarily I see the Umi screen, followed bij the start screen where it says android.
Then I see for a few seconds the menu where you can select the language and then reboots.
I tried using Shuame, SP Flash tool and MTK Droid Tools. Nothing seems to work.
Via ADB sideload I can push a package but this gets always aborted.
I used Shuame to push the CWM 6.0.3 recovery to the phone. It states that it worked, but when I reboot to Recovery I can only get to the Factory recovery. Here you can only update software instead of installaing complete zip images.
I read about a guy who had the somewaht same issue. He said that he fumbled around with Shuame and suddenly had a recovery menu of Shuame on his Device.
ADB shell works, but I can;t get to my SDCARD as it says no device found. When I run ADB Devices nothing returns.
I already tried adding my USB device to the ini-file of ADB, to no avail.
Can someone help me get my device running again.

Chucho72 said:
Hi all,
I'm trying for days to get my Umi X2 running again.
Momentarily I see the Umi screen, followed bij the start screen where it says android.
Then I see for a few seconds the menu where you can select the language and then reboots.
I tried using Shuame, SP Flash tool and MTK Droid Tools. Nothing seems to work.
Via ADB sideload I can push a package but this gets always aborted.
I used Shuame to push the CWM 6.0.3 recovery to the phone. It states that it worked, but when I reboot to Recovery I can only get to the Factory recovery. Here you can only update software instead of installaing complete zip images.
I read about a guy who had the somewaht same issue. He said that he fumbled around with Shuame and suddenly had a recovery menu of Shuame on his Device.
ADB shell works, but I can;t get to my SDCARD as it says no device found. When I run ADB Devices nothing returns.
I already tried adding my USB device to the ini-file of ADB, to no avail.
Can someone help me get my device running again.
Click to expand...
Click to collapse
Got it running.
If someone needs instructions, let me know.

err... did u reflash the partion part ?
Sent from my GT-S5360 using xda app-developers app

Ryanrioz said:
err... did u reflash the partion part ?
Sent from my GT-S5360 using xda app-developers app
Click to expand...
Click to collapse
Yeah, I used SP Flash Tool to reflash the recovery.img

More Details
I need more details on how did you use the flash tool to solve your problem? I have the same problem here. I need to know how to show (in sp flash tool) where is my downloaded .IMG file. Step by step
Chucho72 said:
Yeah, I used SP Flash Tool to reflash the recovery.img
Click to expand...
Click to collapse

Me Too
toninhocs said:
I need more details on how did you use the flash tool to solve your problem? I have the same problem here. I need to know how to show (in sp flash tool) where is my downloaded .IMG file. Step by step
Click to expand...
Click to collapse
Hi, I have the same problem (silly me), where did you get that recovery.img?
Any hints would be helpful
Thanks
TOM

[Q] Moto G has no OS installed!

hi everyone,
i accidentally deleted all of my data from my sd card when i got stuck in a bootloop and now my moto g has no OS installed. I've tried using adb to push the stock ROM onto it but because I cant access usb debugging through TWRP it doesn't even recognise my device is plugged in. any advice would be help full thanks.

NexusHaggis said:
hi everyone,
i accidentally deleted all of my data from my sd card when i got stuck in a bootloop and now my moto g has no OS installed. I've tried using adb to push the stock ROM onto it but because I cant access usb debugging through TWRP it doesn't even recognise my device is plugged in. any advice would be help full thanks.
Click to expand...
Click to collapse
Hmmm.. You basically have 2 options here.
1. Get ADB working (it's not hard, try the Koush's Universal ADB driver)
2. Restore back to stock ROM, but you will need Fastboot working.
The thing is, if you can get Fastboot working, ADB should work too.. so...
If you need help with ADB, just ask..

Maybe this will help you http://forum.xda-developers.com/showthread.php?t=2542219

guide me pls
same problem with me guide me step by step pls
i m fresher for all this stuff

neozen21 said:
Hmmm.. You basically have 2 options here.
1. Get ADB working (it's not hard, try the Koush's Universal ADB driver)
2. Restore back to stock ROM, but you will need Fastboot working.
The thing is, if you can get Fastboot working, ADB should work too.. so...
If you need help with ADB, just ask..
Click to expand...
Click to collapse
Ok so ive got the universal drivers, now what?

Same problem here...
Please help us

Check the link that Eduzerokm posted
Sent from my XT1032 using xda app-developers app

More info on your status quo please..
1) Got ADB up and running on your PC?
No: Use search option, there's plenty of guides in this forum..
Yes:
2) Make sure you flash the latest recovery image. Here's the link to the link:
http://forum.xda-developers.com/showthread.php?t=2608377
Place the recovery image in the same folder with your adb and fastboot
Connect your phone to your computer
Boot into bootloader by holding power + volume down
Open command prompt and type:
fastboot flash recovery PUTNAMEOFRECOVERYHERE.img <press enter>
3) From here just follow this link:
http://forum.xda-developers.com/showthread.php?t=1667929
(It's for HTC phone, but applies to moto g, too. Tested by myself)
4) Enjoy!

After flashing miui in moto g5s plus it is showing no os installed are u sure to reboot?
plz help me?

[Completed] Lg Volt Soft Bricked

I have messed up my lg volt it was on the stock rom zv5 and was running fine with root. I decided to flashify a deodexed version of my rom onto my phone, this of course went wrong as all my phone displays is the Lg boot animation with Fastboot in the top right corner i cant enter recovery mode as I have a bad recovery. I can open up the adb sideloader within Android System Recovery but have no idea how to get it to work as my command prompt does not recognize the command. I have tried a factory reset and rebooting. Help please I am getting desperate. FYI I am 14 and my knowledge on flashing is minimal.

XDA Visitor said:
I have messed up my lg volt it was on the stock rom zv5 and was running fine with root. I decided to flashify a deodexed version of my rom onto my phone, this of course went wrong as all my phone displays is the Lg boot animation with Fastboot in the top right corner i cant enter recovery mode as I have a bad recovery. I can open up the adb sideloader within Android System Recovery but have no idea how to get it to work as my command prompt does not recognize the command. I have tried a factory reset and rebooting. Help please I am getting desperate. FYI I am 14 and my knowledge on flashing is minimal.
Click to expand...
Click to collapse
Hello, and welcome to XDA! You could try to adb sideload a rom and flash it. Or fastboot flash a working recovery onto your device, and then sideload a rom and flash it. Or you may have to reflash stock firmware onto your device to get it to work. Here is a guide as to how to flash roms: http://forum.xda-developers.com/wiki/index.php?title=Flashing_Guide_-_Android. To sideload, the command is simply "adb sideload name of file" without the quotation marks. For further help regarding your problem, you can register and post your questions in the XDA help forum: http://forum.xda-developers.com/general/help.
Good luck!

Can I still install any recovery(CWM or TWRP) after I have forgotten my password?

My question is: Is there any way that i can install any custom recovery now, when I am locked out of my phone, so I can try Method 7 from this post . I have enabled USB debugging, but for some reason, my device is unauthorized from executing adb commands.
I have Xiaomi Redmi Note 3, and have forgotten its password. I have tried Method 2, 5 and 6 from this post, but to no avail.
I tried method 2 and 5 which requires ADB to be installed, but I was not able to access my phone. I have USB debugging enabled and my phone is not rooted. When I tried to run the following code:
Code:
adb devices
adb shell
it showed that my phone is unauthorized and error: device unauthorized This adb server's $ADB_VENDOR_KEYS is not set
Here's the screenshot:
When trying method 6, I had to change the path of ADB driver because the file I downloaded from the post, had its own ADB driver which clashed with my already installed ADB driver, but even after that, it again showed the above error. Here' the screenshot:
Finally I want to try method 7 from the above post, which requires custom recovery to be installed on the phone, is there any way now?
Though it seems now that the I have only one option left and that is to factory reset my phone, but if , there is any other way by which I can bypass my lock screen, please please please inform me.

Of course you can. Just boot your phone into fastboot and do "fastboot flash recovery <recovery image name>.IMG" and you'll flash it. And you can't access the adb because your screen is locked... This is how companies prevent phone hacking
So flash custom recovery, backup the /data , factory reset and after resetting restore the /data backup. And you're good to go. I suggest you using TWRP, because I use it and it never left me hanging Keep me updated.
Sent from Lenovo a6000 1GB version.

Install TWRP or CWM with fastboot and then flash the Unlock me! zip that I've created and you won't lose your data.
Sent by my iPad using Tapatalk

joe2k01 said:
Install TWRP or CWM with fastboot and then flash the Unlock me! zip that I've created and you won't lose your data.
Sent by my iPad using Tapatalk
Click to expand...
Click to collapse
Didn't know that such package existed... I'd still do it my way if your phone was laggy/corrupted,... Else do the package flash. Keep me updated!
Sent from Lenovo a6000 1GB version.

Thanks! a lot, could you please guide me a little bit, how should I proceed?
MGlolenstine said:
Of course you can. Just boot your phone into fastboot and do "fastboot flash recovery <recovery image name>.IMG" and you'll flash it. And you can't access the adb because your screen is locked... This is how companies prevent phone hacking
So flash custom recovery, backup the /data , factory reset and after resetting restore the /data backup. And you're good to go. I suggest you using TWRP, because I use it and it never left me hanging Keep me updated.
Sent from Lenovo a6000 1GB version.
Click to expand...
Click to collapse
Thanks! a lot for reply, As I am still a newbie and trying to learn few things. Could you please guide me how should I proceed?
Like What files I need to download and from where? Also how should I use these files to install recovery?

dost25 said:
Thanks! a lot for reply, As I am still a newbie and trying to learn few things. Could you please guide me how should I proceed?
Like What files I need to download and from where? Also how should I use these files to install recovery?
Click to expand...
Click to collapse
OK... So first boot into fastboot. When you've done that, connect It to your pc with usb, download fastboot package from somewhere on xda(you'll find it).
Open command prompt "CD" to the directory where your fastboot is located in, put recovery image in the folder where fastboot.exe is and type "fastboot flash recovery <recovery file name>.IMG". I'm gonna update this answer in 2 days, when I get to my pc, so try to do it by these instructions, if something isn't working, comment and we'll resolve the problem. If something isn't clear, just ask. Keep me updated.
Sent from Lenovo a6000 1GB version.

Ok i will try
MGlolenstine said:
OK... So first boot into fastboot. When you've done that, connect It to your pc with usb, download fastboot package from somewhere on xda(you'll find it).
Open command prompt "CD" to the directory where your fastboot is located in, put recovery image in the folder where fastboot.exe is and type "fastboot flash recovery <recovery file name>.IMG". I'm gonna update this answer in 2 days, when I get to my pc, so try to do it by these instructions, if something isn't working, comment and we'll resolve the problem. If something isn't clear, just ask. Keep me updated.
Sent from Lenovo a6000 1GB version.
Click to expand...
Click to collapse
Can unlocking my bootloader somehow brick my phone?

Everything can brick your phone. Updating my lenovo phone with official update hardbricked mine... But yeah, it can.

How to (root BLU Advance 5.0 HD)

Hi all
I'm looking to learn how to root a BLU Advance 5.0 HD phone (Marshmallow Android 6.0)
I'm newbie...
I already found a a blutwrp.img on https://bluroms.info/ website but this is the only thing I'm sure I have to use it.
About ADB I found the genuine google package (platform-tools-latest-windows) and the SR4-SuperSU-v2.78-SR4-20161115184928 package too.
I don't know if all this part are good for my phone...
Thanks for help...

I'm also looking for a root. I tried a few suggestions like Kingoroot but nothing has worked.

marshmallow
there is no automatic root for Marshmallow this is why I posted this thread ...

mikele2016 said:
Hi all
I'm looking to learn how to root a BLU Advance 5.0 HD phone (Marshmallow Android 6.0)
I'm newbie...
I already found a a blutwrp.img on https://bluroms.info/ website but this is the only thing I'm sure I have to use it.
About ADB I found the genuine google package (platform-tools-latest-windows) and the SR4-SuperSU-v2.78-SR4-20161115184928 package too.
I don't know if all this part are good for my phone...
Thanks for help...
Click to expand...
Click to collapse
Yes you have to use the twrp recovery. Have you even flashed it? Using adb when the device is on, (make sure to enable usb debugging in settings and authorize your computer) run adb reboot bootloader and then make sure that fastboot recognizes your device and run fastboot oem unlock to unlock your bootloader. Unlocking your bootloader this way is the easiest and doesn't work all times. If it successfully unlocked your bootloader, just do fastboot flash recovery <recovery.img location> and then reboot into system and run adb reboot recovery, from there you can push the su zip or just adb sideload it. To push you do adb push <location to supersu.zip> /sdcard and then go to install and find the zip and flash it, to sideload it, go to advanced and hit sideload and type adb sideload <location to supersu zip>
If I helped, hit thanks Hope it works!

@RAZERZDAHACKER Thanks for help !
I would like to have more info about blutwrp.img and the SR4-SuperSU-v2.78-SR4-20161115184928 package too. I'm not sure this is the two files I have to use with my BLU Advance 5.0 HD...
Thanks

mikele2016 said:
@RAZERZDAHACKER Thanks for help !
I would like to have more info about blutwrp.img and the SR4-SuperSU-v2.78-SR4-20161115184928 package too. I'm not sure this is the two files I have to use with my BLU Advance 5.0 HD...
Thanks
Click to expand...
Click to collapse
What's the codename for that device? Open up an adb shell, and report whatever comes before the $ sign

Hi
Thanks for help
There is many info here
please look at the file attached

I am strongly doubting that came before the $ sign. The attached file says [email protected] in the shell, indicating the codename to be ducati

its not rooted device
what is the command line to see the codename ?

In build.prop I can see :
ro.build.version codename = REL
ro.product.device=BLU_ADVANCE_5.0_HD
when I open a terminal I see:
[email protected]_ADVANCE_5.0_HD:/$
this is what you want ? So the codename is BLU_ADVANCE_5.0_HD
thanks

You don't even need to do anything or have root access, just open a terminal window and see what text is there, don't you're anything

[email protected]_ADVANCE_5.0_HD:/
this is what I see when I open a terminal windows

mikele2016 said:
[email protected]_ADVANCE_5.0_HD:/
this is what I see when I open a terminal windows
Click to expand...
Click to collapse
Huh, no offense to the creators but that is a pretty dumb name, anyway, you have fastboot and adb access right? I will try and have a check at the twrp image and see if I can verify that it is for the correct device and if you don't know how to flash it, a guide on that as well
---------- Post added at 09:30 PM ---------- Previous post was at 09:26 PM ----------
Update: The website seems genuine. Using an mtk flashing tool you can flash this file (youtube guide) and then using the supersu zip you've downloaded, use the methods I mentioned in my first post.
Good luck!

Yes its the device name. Thanks for your help I appreciate. The root process is often described on many website but there seems to be a doubt about a possible boot loop problem depending on the command executed... so I will follow your guide for sure.

I do not really understand.. You say I have to use MTK Flashing Tool+ADB + TWRP + SuperSU ... ?? I need two more university years ...

mikele2016 said:
I do not really understand.. You say I have to use MTK Flashing Tool+ADB + TWRP + SuperSU ... ?? I need two more university years ...
Click to expand...
Click to collapse
Should work with just using the mtk flashing tool to flash twrp then flash SuperSU. If it says something about bootloader being locked, just boot I to fastboot via adb and do fastboot oem unloc.

RAZERZDAHACKER said:
Should work with just using the mtk flashing tool to flash twrp then flash SuperSU. If it says something about bootloader being locked, just boot I to fastboot via adb and do fastboot oem unloc.
Click to expand...
Click to collapse
hey thank you so much for help I appreciate ! I understand that if i use adb to unlock the bootloader this will erase all my data right ? but if I use mtk flashing tool I get a chance to do a clean root to save my data right ?

mikele2016 said:
hey thank you so much for help I appreciate ! I understand that if i use adb to unlock the bootloader this will erase all my data right ? but if I use mtk flashing tool I get a chance to do a clean root to save my data right ?
Click to expand...
Click to collapse
It's fastboot to unlock bootloader, and I believe you're correct. Though, always make backups.

I managed to flash the blutwrp.img file but it put me into a boot loop. It would boot into Twrp, scroll information about being unable to mount anything and just boot loop.

same for me