I read over and over through the forums about bugs on 5.1.. As long as I've been "playing" with phones, that's the first thing you do.... So to everyone having problems first make sure you do a factory reset. I have less problems using factory recovery, then install twrp ..... Then if your having problems check your boot loader version..... If those don't work then ask for help. It really sucks for us to read through the same questions over and over... It's not hard to skim through the pages first also.. If you have the problem someone else probably had also... I hope I put this in the right part of the forum
Related
Hey guys its been a while since I've even tried to fix my phone cause everyone was saying its dead. But I've been reading stories of people coming back from the G1 logo. So i could really use your help.
Heres the problem, A while back I dropped my old G1 and had to get a new one. Upon looking for the video I used last time to root my phone, I couldn't find it. I searched high and low but to no avail. I figured any video would work as long as it rooted me. So I started up the video. however once i was "done" with it i noticed nothing had changed. So i figured the video was garbage and found another one and started it up. I know, STUPID. Well when i booted my phone after wiping and flashing. It stayed on the G1 logo. I knew the worst had happened. So now i don't know what to do. There have been one or two occasions that I've gotten it to boot loader. So i know i can get there. but what do i do when I get it?
Also, no, I never got to flashing raido's or anything like that. I thought I wasn't rooted so i didn't move on.
I know it was long but I'm getting all the info out there. Please help, I think its possible, and if it is I want my phone back!!!
What were you installing by the way?
EDIT: Made a mistake, thought you were able to boot into recovery.
He does not get to recovery, but into bootloader mode (cam + power on). This is good, as there is a good chance to recover from that.
Try the first section of this guide:
http://wiki.cyanogenmod.com/index.php/Full_Update_Guide_-_G1/Dream_Firmware_to_CyanogenMod
You have to flash the correct dreamimg.nbh via bootloader. You might need a Goldcard to do so, in certain countries, but lets just hope that is not the case (would be more work...)
€: Some more Info on Bricking your device with Radio/SPL updates, so take care: http://forum.xda-developers.com/showthread.php?t=655097
The guide on cyanogens wiki is considered dangerous at the optional update to HardSPL
hi everyone. i've been following the forum here for awhile and finally decided to root my brand new NC. i autorooted from 1.1. i saw some things weren't working so i quickly decided to unroot back to factory settings. i unrooted by unregistering the device and turning off the power 8 times. my NC boots up fine, but it gets stuck on the "Registering your Device" page and just remains there with the circle spinning. i think i left it there for more than 30 minutes and nothing happens. has anyone experienced this before? if so, how did you fix it? any help would be appreciated.
sorry if this topic has already been asked - i tried searching but didn't find anything on this specific issue. if there's already a thread, please feel free to share the link with me. thank you!
EDIT: really need some help here... i tried to fix it myself (i know i shouldn't have) and might have made it even worse. i tried to re-autoroot my NC but just completely failed. it was not loading anything anymore, so i tried to unroot again by powering off 8 times. when i restarted, everything looked normal, except the bootloader screen was not stock. it brought me back through the normal tutorial and same thing with it getting stuck on "registering your device". could someone please provide a thorough walkthrough on how to reset to factory settings? i'm seeing all these threads throwing around all these acronyms that i don't understand. seems like i need to try running some clockwork rom but not even sure how to do that. please help!!
Bump, i have just encountered this problem and i need help as well.
Update:
actually just figured it out and heres what fixed my problem, i wasn't doing the factory reset part only the 8 reboot interruptions.
hxxp://nookdevs.com/Flash_back_to_clean_stock_ROM
Thanks for your post, even though no one ever helped. I was having the same problem and doing a clear data/factory reset from Clockwork Recover booted from an SD card did the trick for me.
Hello Everybody!
So, the thing is that I bought a brand new DS7 from ebay recently, and it has Honeycomb in it, but about a week ago things went wrong -actually I'm not sure if it was good before. The tablet does not work on the proper way. First of all, I tried to install iGO on it, but it didn't let me to do it. So I can't install apps. And there are times when I can't connect it to the computer...and etc. I was wondering if it has a proper Honeycomb in it...so the point is that I decided to delete everything from it and reinstall the Honeycomb myself. I'm not very into these things, so it's a big effort for me to do this.
I have been searching for tutorials for 2 days. I think I found the right one somewhere here on this website. I've closed it unfortunately and it was opened yesterday and I cleared yesterday's history for some other reasons...so I can't open it again.
So the last time everything was ready, so was I, to do the installing. But, the comp. was searching for some APX files, probably drivers, but it didn't find it. So I couldn't continue the installation.
I've been looking for these drivers for hours, but haven't found anything. So I decided to register to this site, ask you, experts where to seek and what to do.
I lost so much time on this that I shouldn't have...
Thanks for your help in advance!
(Sorry for my English if it isn't understandable everywhere, I'm a non-native-speaker. Cheers! )
Now I'm about to restore the whole device following this (http://forum.xda-developers.com/showthread.php?t=1011654) tutorial. Hope it'll solve some of the problems.
raidon24 said:
Now I'm about to restore the whole device following this (http://forum.xda-developers.com/showthread.php?t=1011654) tutorial. Hope it'll solve some of the problems.
Click to expand...
Click to collapse
Dude, try not to dobblepost. Its quite better when you edit the first one.
(By the way im not a native english speaker to but i hope you understand what i mean)
Could you write down how far you come. At which step do you stop? And if the drivers are a problem, please post your Computer OS, like Windows or Linux or Mac.
I have solved the problem. Should I delete this thread somehow?
raidon24 said:
I have solved the problem. Should I delete this thread somehow?
Click to expand...
Click to collapse
No, you should post your solution in this thread. If someone has the same problem they may do a search and find this thread, and they can learn from you. Or if the solution was in another thread, post a link to that thread.
hah, okay The reason I didn't want to is because I think it's not a big deal. I have pushed the volume + and the Turn Off button then Factory Reset, and waited. Now everything's fine. The problem was, actually that I'd been doing...rather trying the reseting in a wrong way. I thought I should do it in the Settings/Privacy menu. But no. So It solved my problems. I didn't need to re-install Honeycomb as I'd thought the time I started this thread. I believed that the problem is in my HC, but fortunately no, so I'm going to sleep. Minden jót, srácok!
Hello everyone,
I have searched the forum and have not found any information on my problem which is why I'm creating this thread. If I have missed some earlier thread please do point it out and I'll delete this immediately.
It is the first time I attempt to flash a custom rom (I'm not even sure I'm using the correct words). I read the instructions on
http://forum.xda-developers.com/showthread.php?t=2555445 and followed them. I did read in the forum that the first boot will take a long time, 5 to 10 minutes. It's been about 40 minutes since I rebooted my Galaxy S Advance and got that sleek green android face. However my gt-i9070 just sits there, blinking at me ...
I don't really know what to do, is this expected? If anyone has experienced this please tell me what I'm supposed to do.
Thank you for your time,
Vassilis
Well, I rebooted did a factory reset, cleared the cache, and dalvik. Reinstalled the ROM and afterwards the phone booted to the new ROM. At first I didn't have WIFI but after a reboot everything went fine. Problem solved !
So i have a Moto g xt1072 wich i got second hand.. i got it into recovery mode and eventually got it working, but it was really unstable, so i wanted to reflash the stock rom, because it looked like the current one on the phone was corrupted (i was running android 6.0) (btw i have a xt1068 as my daily driver, but i want this to work again)
So i started flashing http://forum.xda-developers.com/moto-g-lte/general/stock-6-0-marshmallow-europe-reteu-t3338075 <-this
but i had errors and it was failing multiple times.. so i looked up some tutorials, and most of them were unlocking the bootloader at the beginning, so i was unlocking and locking the bootloader trying to get the commands to work,
then i found a tutorial wich coppyd all of the commands at once, so i tried that.. screen went black..
Wont boot into recovery, 3sec method or 120 sec method, and connects to my pc as QHSUSB_BULK
luckily i made a picture of the recovery when i tried to flash:
http://imgur.com/8avCk3T
I think i may need to blank flash, but im not certain..
I would also like to find the firmware for this phone that wont brick it..
Can anyone help?
Need more info?
Please just ask me, i will respond immediately
i dont care what i need to do.. even if i need to hardwire (because im really good at those finicky things)
Thanks for reading XD
Same issue here. I flashed a stock image and something must've gone wrong at some point
hamzahrmalik said:
Same issue here. I flashed a stock image and something must've gone wrong at some point
Click to expand...
Click to collapse
you probably also flashed the vootloader and the bootanimation, these are known to give problems, but ive foubd a test point on the pcb which brings the phone in a les hard bricked state, but ive yet to find a method to unbrick the phone..
ill keep you posted
ora69 said:
you probably also flashed the vootloader and the bootanimation, these are known to give problems, but ive foubd a test point on the pcb which brings the phone in a les hard bricked state, but ive yet to find a method to unbrick the phone..
ill keep you posted
Click to expand...
Click to collapse
Sorry could you please explain. How can a phone be less hard bricked. Thanks
Sent from my A0001 using Tapatalk
hamzahrmalik said:
Sorry could you please explain. How can a phone be less hard bricked. Thanks
Sent from my A0001 using Tapatalk
Click to expand...
Click to collapse
okay, so there are different types of hardbricks, all act the same, but one is harder to unbrick than the other, there is qh usb bulk and qhas bulk with numbers behind it, search for force unbrick lg g2,
now the problem is, it should be easy to unbrick the phone at thsi point, but im not an expert in that and have no idea what to do now xD so i posted it on xda, but no one answered me.. xD hopefully this clears it up some more
ora69 said:
okay, so there are different types of hardbricks, all act the same, but one is harder to unbrick than the other, there is qh usb bulk and qhas bulk with numbers behind it, search for force unbrick lg g2,
now the problem is, it should be easy to unbrick the phone at thsi point, but im not an expert in that and have no idea what to do now xD so i posted it on xda, but no one answered me.. xD hopefully this clears it up some more
Click to expand...
Click to collapse
Oh ok I get you. Mines USB bulk 9000 or something i can't remmeber now
Sent from my A0001 using Tapatalk
ora69 said:
So i have a Moto g xt1072 wich i got second hand.. i got it into recovery mode and eventually got it working, but it was really unstable, so i wanted to reflash the stock rom, because it looked like the current one on the phone was corrupted (i was running android 6.0) (btw i have a xt1068 as my daily driver, but i want this to work again)
So i started flashing http://forum.xda-developers.com/moto-g-lte/general/stock-6-0-marshmallow-europe-reteu-t3338075 <-this
but i had errors and it was failing multiple times.. so i looked up some tutorials, and most of them were unlocking the bootloader at the beginning, so i was unlocking and locking the bootloader trying to get the commands to work,
then i found a tutorial wich coppyd all of the commands at once, so i tried that.. screen went black..
Wont boot into recovery, 3sec method or 120 sec method, and connects to my pc as QHSUSB_BULK
luckily i made a picture of the recovery when i tried to flash:
http://imgur.com/8avCk3T
I think i may need to blank flash, but im not certain..
I would also like to find the firmware for this phone that wont brick it..
Can anyone help?
Need more info?
Please just ask me, i will respond immediately
i dont care what i need to do.. even if i need to hardwire (because im really good at those finicky things)
Thanks for reading XD
Click to expand...
Click to collapse
So that link to another thread in XDA forum, I think I had a similar experience. I too have the XT1072 as I live in the UK. now here on XDA you have to be careful and ask 3 4 maybe 5 times before someone listens properly. I know it is hard for the devs with so many dumb noobs asking so many dumb questions, I include myself as a noob so no worries. Anyway to get to the point that link is not referring to our phone the XT1072. You should ignore LTE in your search criteria, it will always point you towards the 2015 model and believe you me all roms in my experience area very device specific. You need to simply put Moto G 2nd gen 2014 in search criteria when it comes to searching for custom recoverys and/or stock ROMS. The Titan.IMG is always a safe bet if I remember correctly, dont take my word for it, I have been known to have a memory like a sieve now and again, the problem with getting older, cache gets smaller and smaller, lol! Best of luck!
hamzahrmalik said:
Sorry could you please explain. How can a phone be less hard bricked. Thanks
Sent from my A0001 using Tapatalk
Click to expand...
Click to collapse
Read the beginning on this article: http://rootmyandroid.org/how-to-unbrick-your-android-device-the-ultimate-guide.html/
the bricked term is a common misconception for phones that still turn on..