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!
Related
I got a Lenovo S850 from China and it came rooted from factory. I deleted apps I shouldnt and it booted up with constant security warning. I download what I thought was the correct rom and it did not install but phone would not come on. I found a rest of world rom to install that I thought was correct but after install imei's were missing and it had nvram warning in wifi. I have fixed that issue permanently but still with any sim card it says no service and a manual search fails.
Not sure if the first rom made a mess of the partitions etc but I have no idea why etc.
Just wondering if there was an expert that could connect to my pc via team viewer and take a look at it as I can connect it via adb but no idea what else to do. I think partitions are messed as in custom recovery it will not mount anything and had to adb sideload root.zip.
I will return it under warranty if I cant sort it though they may refuse to fix if they see it has a differnt rom on etc,
Anyone help?
Thanks
Simon.
Hi,
I can't find anything for your device on XDA, so you would need to ask here and hopefully someone can help. Otherwise I suggest you contact the manufacturer for original firmware and Flashing instructions...
> Android Development and Hacking > Android Q&A, Help & Troubleshooting
Good luck!
Thanks I will ask there.
I don't really know why my phone is stuck in a bootloop to begin with. I've tried EVERYTHING I could possibly think of!
Here's What I've tried :
WipeData/Factory Reset and I also wiped Cache.
I tried to use ODIN to flash the original stock ROM to the device but the bootloader is locked so its impossible to flash any ROM to the devices (Even if it's official).
I tried to apply the Lollipop 5.0 update in recovery using a external SD card.
I tried using ADB sideload.
(Bonus points if you can give me away to unlock the bootloader! because i'll know what to do if it's unlocked.)
So...If anyone has suggestions, I'll happily take any!
Also Please! Leave links so I have quick access!
Hi,
I can't find a relevant thread on your device and issue, but you can ask for help here,
http://forum.xda-developers.com/android/help
Good luck!
I will be as specific as I can in order to save time
So I was in need of a cheap phone and always liked the look of the S7 since release. It came today but there was very little internal memory so I decided to root the device via ''Kingo Root'' in order to install an app called FolderMount. The app was meant to merge my SD card memory with my Internal Memory allowing me to install apps without a problem. As far as I can tell the root stage went fine, it said successful, rebooted and SuperSU worked a treat.
When I installed FolderMount it claimed the patch it applied was successful and my phone just needed to reboot in order to apply. So I rebooted and then it was stuck on the boot logo :crying: I have tried every combination to boot it into recovery in order to do a hard reset but nothing seems to work. No matter what button combination I seem to use the device to reboots, I have searched the all over the web for a solution but because it is a clone phone and its origins are unclear finding a relevant solution has being a nightmare.
So I have decided to turn to you fine folks in a hope someone could point me in the right direction. I will post everything about the phone I know below and if anybody has some suggestions that would be great.
Thanks guys
The phone is an HDC S7 - I can't post a link due to my account limitations.
Danny1231732 said:
I will be as specific as I can in order to save time
So I was in need of a cheap phone and always liked the look of the S7 since release. It came today but there was very little internal memory so I decided to root the device via ''Kingo Root'' in order to install an app called FolderMount. The app was meant to merge my SD card memory with my Internal Memory allowing me to install apps without a problem. As far as I can tell the root stage went fine, it said successful, rebooted and SuperSU worked a treat.
When I installed FolderMount it claimed the patch it applied was successful and my phone just needed to reboot in order to apply. So I rebooted and then it was stuck on the boot logo :crying: I have tried every combination to boot it into recovery in order to do a hard reset but nothing seems to work. No matter what button combination I seem to use the device to reboots, I have searched the all over the web for a solution but because it is a clone phone and its origins are unclear finding a relevant solution has being a nightmare.
So I have decided to turn to you fine folks in a hope someone could point me in the right direction. I will post everything about the phone I know below and if anybody has some suggestions that would be great.
Thanks guys
The phone is an HDC S7 - I can't post a link due to my account limitations.
Click to expand...
Click to collapse
Greetings!
Thank you for using XDA Assist.
I recommend you post your question in this friendly help thread:
http://forum.xda-developers.com/showthread.php?t=2259645
There's not much support for cloned devices on XDA but someone may be able to help you there.
Good luck!
My question current is really about better understanding something in this whole Root and Linux learning adventure I think I am totally confused about.
Basically if no custom ROM exist or your device is not listed on the supported list of devices in any recovery program....
OR as in my case you want desperately to get the thing back running on it's true stock what do you do?
Your rooted, but stuck.
So my main question is:
What is the best way to bring a device back to stock if there is no stock ROMs available and factory reset will not work?
On any device in this situation. Mostly I am hoping to have it explained in a way I can really finalize this confusing hole in my logic.
Like can a recovery program find it if it is still on the device somewhere and if not, why not?
Thanks in advance.
Additional backstory if helpful.
I have a Wacom Cintiq Hybrid running Android 4.1 that is ( now ) rooted..
This is a very bad thing. The Real Stock ROM has palm rejection and all the drivers to make it work as a tool. So stock is the ideal but it is clearly not stock as my device supposedly came in the
box running 4.2 and with software and drivers to make it work properly with the pen. This has nothing. No software and the smallest amount of apps possible. Worse this is no custom ROM its on ( I think) as it would be the worst one ever and it was not rooted on arrival. I have no idea what happened before I got it. I may have made the mistake of rooting it really as I found out to my dismay there is no ROM support. So back to square one. I bought it ( very cheap for one of these ) "stuck and unable to go to the play store" and I did not realize until I got it, on a version of Android it was not meant for. Wacom is totally and woefully unhelpful in every way. They seem to want to quietly put this device behind them at the expense literally of their customers.
I have discussed this problem in another thread if more details on all this specific to this device are of interest.
Duende101 said:
My question current is really about better understanding something in this whole Root and Linux learning adventure I think I am totally confused about.
Basically if no custom ROM exist or your device is not listed on the supported list of devices in any recovery program....
OR as in my case you want desperately to get the thing back running on it's true stock what do you do?
Your rooted, but stuck.
So my main question is:
What is the best way to bring a device back to stock if there is no stock ROMs available and factory reset will not work?
On any device in this situation. Mostly I am hoping to have it explained in a way I can really finalize this confusing hole in my logic.
Like can a recovery program find it if it is still on the device somewhere and if not, why not?
Thanks in advance.
Additional backstory if helpful.
I have a Wacom Cintiq Hybrid running Android 4.1 that is ( now ) rooted..
This is a very bad thing. The Real Stock ROM has palm rejection and all the drivers to make it work as a tool. So stock is the ideal but it is clearly not stock as my device supposedly came in the
box running 4.2 and with software and drivers to make it work properly with the pen. This has nothing. No software and the smallest amount of apps possible. Worse this is no custom ROM its on ( I think) as it would be the worst one ever and it was not rooted on arrival. I have no idea what happened before I got it. I may have made the mistake of rooting it really as I found out to my dismay there is no ROM support. So back to square one. I bought it ( very cheap for one of these ) "stuck and unable to go to the play store" and I did not realize until I got it, on a version of Android it was not meant for. Wacom is totally and woefully unhelpful in every way. They seem to want to quietly put this device behind them at the expense literally of their customers.
I have discussed this problem in another thread if more details on all this specific to this device are of interest.
Click to expand...
Click to collapse
Hello & welcome to xda-assist,
If you rooted the device you changed the system /kernel in the process, if root is all you done you should be able to unroot by using the unroot option in your root management application, if you did further changes like deleting system apps and so on it gets more complex, the best and easiest way to get back to the original state would be a copy of the latest firmware.. If it doesn't exist you're somewhat out of luck, please refer to this link for further help & information..
http://forum.xda-developers.com/android/help
Sam Nakamura said:
Hello & welcome to xda-assist,
If you rooted the device you changed the system /kernel in the process, if root is all you done you should be able to unroot by using the unroot option in your root management application, if you did further changes like deleting system apps and so on it gets more complex, the best and easiest way to get back to the original state would be a copy of the latest firmware.. If it doesn't exist you're somewhat out of luck, please refer to this link for further help & information..
http://forum.xda-developers.com/android/help
Click to expand...
Click to collapse
Thanks for the reply. So no way to get the extract the original firmware? I don't wish to un-root. The device was set to a very sad state of affairs when I got it, unrooted, with something very unlike the stock firmware and factory date reset not helping at all. Persistently locked into a lower version of Android than it was not meant for and not running the drivers or software it would seem I need to make it function properly that came with the device.
Basically it lead to my curiosity of how one goes about extracting or mining the data that is stored somewhere on the device if all I did was root. Which is all I did.
It should still be there. Basically how do I get to it?
The link takes me back to the forums for help, however I found no help there after much searching before I asked here but thanks
Duende101 said:
Thanks for the reply. So no way to get the extract the original firmware? I don't wish to un-root. The device was set to a very sad state of affairs when I got it, unrooted, with something very unlike the stock firmware and factory date reset not helping at all. Persistently locked into a lower version of Android than it was not meant for and not running the drivers or software it would seem I need to make it function properly that came with the device.
Basically it lead to my curiosity of how one goes about extracting or mining the data that is stored somewhere on the device if all I did was root. Which is all I did.
It should still be there. Basically how do I get to it?
The link takes me back to the forums for help, however I found no help there after much searching before I asked here but thanks
Click to expand...
Click to collapse
The intended of xda-assist is to direct you to the most suitable board of xda, we do not solve issues for you or do technical support, please be patient, it often takes time for exotic devices / questions to be seen by someone who can give hints and answers..
Edit: but it's not that the original firmware is stored somewhere on the device by default where you can grab it and reinstall it..
Sent from my OnePlus 2 using XDA Labs
Sam Nakamura said:
The intended of xda-assist is to direct you to the most suitable board of xda, we do not solve issues for you or do technical support, please be patient, it often takes time for exotic devices / questions to be seen by someone who can give hints and answers..
Edit: but it's not that the original firmware is stored somewhere on the device by default where you can grab it and reinstall it..
Sent from my OnePlus 2 using XDA Labs
Click to expand...
Click to collapse
Totally cool. It's a tough question.
The OG firmware thing is the toughest part to understand. Just wanted to make sure I was clear in my explanation and question.
Hello everyone, I hope I'm writing in the right section.
I'll go straight to the issue: after finally deciding to install a custom rom on my device (HUAWEI GX8), i decided to opt for this one: https://forum.xda-developers.com/moto-g4-plus/development/rom-aospextended-rom-v3-0-t3537792
The first problem i had to face was the "ERROR:7" (so the rom seemed to be made for a different phone than mine) that occured while installing the rom in the twrp, but being that the rom was specifically made for my phone I followed this guide: https://www.youtube.com/watch?v=wed03948gcg and fixed the issue, resulting in a perfect installation... or so I thought.
After rebooting, the phone didn't start the os but was stuck in the twrp (I tried rebooting multiple times and in different ways of course).
Being that I had made a backup before installing the new rom, I decided to restore that backup from the twrp... but still the phone is stuck in the twrp and I don't know what to do :crying:
I hope somebody can help me because I'm starting to panicking.
Cheers in advance.
PS: I'm a complete newb so this was the first time I installed a custom rom, I tried searching for this problem online but couldn't find a solution that fitted me. I hope I won't ask too many stupid questions.
SlimeAndroid said:
Hello everyone, I hope I'm writing in the right section.
I'll go straight to the issue: after finally deciding to install a custom rom on my device (HUAWEI GX8), i decided to opt for this one: https://forum.xda-developers.com/moto-g4-plus/development/rom-aospextended-rom-v3-0-t3537792
The first problem i had to face was the "ERROR:7" (so the rom seemed to be made for a different phone than mine) that occured while installing the rom in the twrp, but being that the rom was specifically made for my phone I followed this guide: https://www.youtube.com/watch?v=wed03948gcg and fixed the issue, resulting in a perfect installation... or so I thought.
After rebooting, the phone didn't start the os but was stuck in the twrp (I tried rebooting multiple times and in different ways of course).
Being that I had made a backup before installing the new rom, I decided to restore that backup from the twrp... but still the phone is stuck in the twrp and I don't know what to do :crying:
I hope somebody can help me because I'm starting to panicking.
Cheers in advance.
PS: I'm a complete newb so this was the first time I installed a custom rom, I tried searching for this problem online but couldn't find a solution that fitted me. I hope I won't ask too many stupid questions.
Click to expand...
Click to collapse
The ROM that you flashed was NOT made specifically for your device, you have HUAWEI GX8, the ROM was made for Moto G4 Plus. You would have know this if you had looked at the forum it was posted in. It was posted in in the Moto G4 forum, not in a Huawei forum.
The "fix" that you used didn't help.it successfully flash, it only help you "force" the ROM to flash. You bypassed a safety measure that was designed to keep you from flashing the wrong thing, now you're dealing with the results of forcing it to flash on a device it wasn't meant for.
Learn to pay attention to what you are reading.
You need to flash your stock firmware to fix this.
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
Droidriven said:
The ROM that you flashed was NOT made specifically for your device, you have HUAWEI GX8, the ROM was made for Moto G4 Plus. You would have know this if you had looked at the forum it was posted in. It was posted in in the Moto G4 forum, not in a Huawei forum.
Learn to pay attention to what you are reading.
You need to flash your stock firmware to fix this.
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
Click to expand...
Click to collapse
I'm sorry I may have linked the wrong page, either way on the website of the rom I downloaded the right thing, I'm sure about it because I checked it multiple times (the error I made in writing the post may be cause by me panicking, sorry :crying: ).
While waiting for answers I installed a different twrp and it WORKS! I'm so happy I could cry. Thank you nonetheless for your help (Still dunno what the problem was though xD)
@SlimeAndroid as you installed ROM of different phone, it might not get installed as ROM zip contains script for Mobile verification.
I assume you had wiped /system and after installation of wrong ROM you rebooted your phone without reading if TWRP said you don't have any OS installed or what. (That means you have ran without any OS, that may be reason why you stuck with TWRP.)
But after Restoring Backup of Working ROM, it should boot your device, but it doesn't.
We (on G4 plus) have faced issue: when phone start, it always goes to TWRP/recovery instead of booting to system.
Are you facing similar ?
Solution for this problem was to clear bootloader data, by using fastboot commands (i assume you know how to do, otherwise ask for better explanation )
Run this two commands from Comand Prompt
-> fastboot oem fb_mode_set
-> fastboot oem fb_mode_clear
This worked for us. You can try, if doesn't work then flash Stock ROM.
____Mdd said:
@SlimeAndroid as you installed ROM of different phone, it might not get installed as ROM zip contains script for Mobile verification.
I assume you had wiped /system and after installation of wrong ROM you rebooted your phone without reading if TWRP said you don't have any OS installed or what. (That means you have ran without any OS, that may be reason why you stuck with TWRP.)
But after Restoring Backup of Working ROM, it should boot your device, but it doesn't.
We (on G4 plus) have faced issue: when phone start, it always goes to TWRP/recovery instead of booting to system.
Are you facing similar ?
Solution for this problem was to clear bootloader data, by using fastboot commands (i assume you know how to do, otherwise ask for better explanation )
Run this two commands from Comand Prompt
-> fastboot oem fb_mode_set
-> fastboot oem fb_mode_clear
This worked for us. You can try, if doesn't work then flash Stock ROM.
Click to expand...
Click to collapse
If you read the post above yours, you'll see they solved the issue.
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
You always have to make sure the download is for your model of phone(settings -about) and always make sure the download has properly downloaded and I use md5 checksum as this verifies the download is not courupt.
Sent from my iPhone using Tapatalk