Hey. Tried flashing the new 2.1.A.0.435 via FlashTool, was rooted, had xrecovery and busybox installed (if it matters...)
now, flashtool got through the loader in a matter of about a minute, but the kernel-flashing has been stuck at this stage for close to 25 minutes! It's gotten in about half a centimeter if I had to guess.
What should I do? Can I just unplug my phone and try again or will I brick it?
oh god, sorry for being so stupid. the flashing has just now moved on. guess I'm too jumpy and jittery.
I was certain I had ****ed something up. Can I call "No question is a dumb question"? Sorry.
thread can be locked, deleted or whatever.
Related
I have one of those Legends that require a downgrade before you root, but I decided to chicken out and after I downgraded to 1.31 or whatever it was, I decided to debrand my Bell Legend and chicken out to get the worldwide Froyo OTA. Plus, it was getting late, I didn't want to accidentally screw up the rooting because I was tired.
Anyway, after I downgraded, I installed a system update that brought me to Eclair-update-1. I don't think that was a really good idea.
Because afterwards, when I tried installing the debranded RUU from the debrand thread, it resulted in an error and I have to keep what I have right now.
UNLESS YOU GUYS HELP.
What did I do wrong? I'm only still a kid. Hell, I thought I bricked my phone halfway through installing the first RUU because there was something wrong with the drivers, I ALMOST TEARED UP FFS.
Oh yeah, and wtf is up with this BS where you format the SD card to turn it into a Goldcard, and HTC Footprints just decides to move its crap into the SD card RIGHT AFTER I FORMAT IT. It's not important, but I was just wondering.
I might have been missing some details (it's late) so please post below and tell me what I'm missing.
Thanks in advance!
PS: Oh yeah, have I voided my warranty yet? Technically, I mean. I COULD still clean it up somehow, and make it seem like I didn't do anything to it, right?
PS2: OK, now I'm getting USB errors 171 and 170 when installing RUUs. I can't get out of the RUU I'm on. Oh crap.
PS3: I just got Error 140, BOOTLOADER Error. What did I do wrong here?
At least I'm at the phone's home screen now, no more unfamilar scary-ass HTC LOGO territory.
Basically the update to "2.1-update1" brought you back to where you were before the downgrade. Your phone is stock right now.
So first relax and get some sleep
Do the downgrade again. DO NOT UPDATE.
Continue the debranding/gold card procedure.
good luck
p.s. your warranty might technically be void when you install another ROM or debrand or root, mostly they don't care as long as you didnt drop it in water . There is always a way to bring it back to stock/unroot
Oh my goodness I love you. I just noticed (while I was tired, wow, that's strange) that the strange ROM number within the About Phone menu finally clicked with what I've been doing! NO UPDATE.
So I decided to call it a night after I try once more.
So I downgraded to w/e. It was fine.
And I tried the debranding RUU. Then I got a bootloader error. I guess I'll try to find out what that means when I wake up, I'm super sleepy. (Unless you guys can help me 'til then )
It was error 140 or something like that, but it booted me fine to my downgraded ROM, so I'm good for the time being.
Good night!
EPIC ACHIEVEMENT EDIT:
Alright, I rooted it. Sweat all over the place, but hey, don't blame me. The problem above is still experienced by many people all over the internet, unfortunately. Too bad I can't answer it.
Just a question before I flash my first ROM with ClockworkMod: What about fixes? How do I flash those? Super noobish, but yeah.
The moment I opened my phone I quickly unlocked the bootloader and rooted my device without realizing there is a newer build out.
I tried flashing in through recovery but every time I do it seems to corrupt my device and im forced to recover from my backup. Ive been out of the android modding for a little while so maybe im missing a step. Can someone point me in the right direction.
Avenue Blue said:
The moment I opened my phone I quickly unlocked the bootloader and rooted my device without realizing there is a newer build out.
I tried flashing in through recovery but every time I do it seems to corrupt my device and im forced to recover from my backup. Ive been out of the android modding for a little while so maybe im missing a step. Can someone point me in the right direction.
Click to expand...
Click to collapse
http://forum.xda-developers.com/nex...ol-skipsoft-android-toolkit-nexus-6p-t3234159 install this on pc press 06 then 11 then 4 let it do its thing and your good or just flash a rom
jaythenut said:
http://forum.xda-developers.com/nex...ol-skipsoft-android-toolkit-nexus-6p-t3234159 install this on pc press 06 then 11 then 4 let it do its thing and your good or just flash a rom
Click to expand...
Click to collapse
This brings me to the unroot menu but it seems that most of the options are disabled, option 6 which says it will unroot fails when booting into twrp
edit: spoke too soon, it worked the second time
now the ota is gone and it says my phone is update date. should I just proceed with flashing it anyways?
edit: when attempting to side load through stock recovery the toolkit stops detecting my phone is connected. This is annoying
edit: got it to side load but its failing now due to "E:footer is wrong" and "E:signature verification failed"
I was trying to root my phone today using kingoapp (one-touch root), and it froze not long after completion ("android is upgrading, Starting apps.."). i let ths sit for about 45mins just in case it was actually doing something but nothing happened.
I forced a reboot and the phone wouldn't start up again. I wasn't able to get into recovery mode either. After a bit of reading up, I flashed the chainfire autoroot file and the stock ROM - this now allowed me into recovery mode.
Problem is, I till can't get the phone to boot - it just sits at the samsung logo and goes no further. If I reflash the stock .md5 in odin, then i get to the "android is upgrading, Starting apps.." again but it goes no further. the md5 I'm using is N9005XXUBMI7_N9005O2UBMHD_N9005XXUBMI6_HOME.tar.md5
Am I missing something obvious?
Read this thead
guitarbloke said:
I was trying to root my phone today using kingoapp (one-touch root), and it froze not long after completion ("android is upgrading, Starting apps.."). i let ths sit for about 45mins just in case it was actually doing something but nothing happened.
I forced a reboot and the phone wouldn't start up again. I wasn't able to get into recovery mode either. After a bit of reading up, I flashed the chainfire autoroot file and the stock ROM - this now allowed me into recovery mode.
Problem is, I till can't get the phone to boot - it just sits at the samsung logo and goes no further. If I reflash the stock .md5 in odin, then i get to the "android is upgrading, Starting apps.." again but it goes no further. the md5 I'm using is N9005XXUBMI7_N9005O2UBMHD_N9005XXUBMI6_HOME.tar.md5
Am I missing something obvious?
Click to expand...
Click to collapse
Well mate in this thread you can find the solution. I am noob like you and one of ours problems is we don't want to read and search carefully.
Please read be carefully this thread it's may help you: http://forum.xda-developers.com/showthread.php?t=2625332
Hopefully help you.
if you can access recovery try to flash a Nandroid Backup
hey all,
Saturday morning a wake up to my alarm on my phone (SM-G950U T-Mobile Stock since new) and turn off the alarm and proceed to check email and scroll social medias. A few minuted later phone turns off and starts boot looping. Occasionally it would boot to home screen and i could unlock it but then maybe 30 seconds later it would start boot loping again. Now it either just boot loops or boots straight to recovery . I have tried flashing current firmware in case it was corrupted and i have tried accessing it through ADB. I know for a fact USB debugging is on because I just used abd to pull wifi passwords 2 weeks ago, but when I try to [ abd devices] if comes up as unauthorized and I cannot proceed. I know everyone will suggest a factory reset, but I am hoping someone has a trick for extracting files. I dont care about most on my phone, but I would like to save the pics from my GF and I trip this past august. Apparently I didnt have my photo library set to sync to cloud -_-
thanks
-chip
update: it appears there is a pattern. it boot loops or boots to recovery (after a blue failed system update screen) 99% of the time. the 1% it boot fully and then crashes is only when battery is 0% . it for some reason is only trickle charging and isnt getting enough juice when it does boot fully to stay on . But if i leave it charging a while it will then only boot loop or boot to recovery. Strange...any way I had enough time this past boot to reauthorize usb debug.....wish me luck with adb
....nevermind. still shows up as unauthorized
chip102 said:
hey all,
Saturday morning a wake up to my alarm on my phone (SM-G950U T-Mobile Stock since new) and turn off the alarm and proceed to check email and scroll social medias. A few minuted later phone turns off and starts boot looping. Occasionally it would boot to home screen and i could unlock it but then maybe 30 seconds later it would start boot loping again. Now it either just boot loops or boots straight to recovery . I have tried flashing current firmware in case it was corrupted and i have tried accessing it through ADB. I know for a fact USB debugging is on because I just used abd to pull wifi passwords 2 weeks ago, but when I try to [ abd devices] if comes up as unauthorized and I cannot proceed. I know everyone will suggest a factory reset, but I am hoping someone has a trick for extracting files. I dont care about most on my phone, but I would like to save the pics from my GF and I trip this past august. Apparently I didnt have my photo library set to sync to cloud -_-
thanks
-chip
update: it appears there is a pattern. it boot loops or boots to recovery (after a blue failed system update screen) 99% of the time. the 1% it boot fully and then crashes is only when battery is 0% . it for some reason is only trickle charging and isnt getting enough juice when it does boot fully to stay on . But if i leave it charging a while it will then only boot loop or boot to recovery. Strange...any way I had enough time this past boot to reauthorize usb debug.....wish me luck with adb
....nevermind. still shows up as unauthorized
Click to expand...
Click to collapse
Ive had similar cases happen with older models. May be time for a battery. They will do crazy **** when the battery crashes. When you flashed stock firmware you lost adb authorisation. Need to get the system back first for that.
TheMadScientist said:
Ive had similar cases happen with older models. May be time for a battery. They will do crazy **** when the battery crashes. When you flashed stock firmware you lost adb authorisation. Need to get the system back first for that.
Click to expand...
Click to collapse
thank you very much. my battery life was greatly suffering and the USB-c port was worn pretty bad. Ill grab a new battery and hope that works.
chip102 said:
thank you very much. my battery life was greatly suffering and the USB-c port was worn pretty bad. Ill grab a new battery and hope that works.
Click to expand...
Click to collapse
Cheapest fix in my opinion. I saw another thread a guy dropped his. Now detects 9008 how to fix. More than likely a phone wont just not boot. Or lose programming unless a hardware issue. So if it was just running and quit. Not modding stuff really. More likely than not its gonna be some form of software. But hardware.
TheMadScientist said:
Cheapest fix in my opinion. I saw another thread a guy dropped his. Now detects 9008 how to fix. More than likely a phone wont just not boot. Or lose programming unless a hardware issue. So if it was just running and quit. Not modding stuff really. More likely than not its gonna be some form of software. But hardware.
Click to expand...
Click to collapse
Replaced Daughter board and battery. No improvement :/ bummer
the only time i can get it back into recovery is after a "successful" flash with odin. by successful i mean that it says it worked but it just continues to boot loop or boots to recovery. attached is a picture of the info i get in recovery every time. hope someone can shed some light in the issue. im using my old phone so i dont feel pressured to call the data a loss and try a factory reset just yet....my old phone is a POS though
chip102 said:
the only time i can get it back into recovery is after a "successful" flash with odin. by successful i mean that it says it worked but it just continues to boot loop or boots to recovery. attached is a picture of the info i get in recovery every time. hope someone can shed some light in the issue. im using my old phone so i dont feel pressured to call the data a loss and try a factory reset just yet....my old phone is a POS though
Click to expand...
Click to collapse
Yea some one tried to root it using the edl safestrap thread. Only wsy to fix it is filled the steps and reflash jrkruses pie rom. One of my mother boards are in the same state. That's the only way dm verity fails. Is his rom method.
There's some easy to flash a cache wipe in Odin but I hadn't found it yet. I have 2 mother boards and one is identical. I flash this stock and lose download or recovery. but the errors you show are only from doing that edl safestrap
Ill be honest..i have no idea what you are talking about. Ive messed with the software with previous devices and never heard of safe strap. This one has been bone stock since I got it from Tmobile and i haven't attempt to flash anything until i had this issue. never tried to root it
TheMadScientist said:
Yea some one tried to root it using the edl safestrap thread. Only wsy to fix it is filled the steps and reflash jrkruses pie rom. One of my mother boards are in the same state. That's the only way dm verity fails. Is his rom method.
There's some easy to flash a cache wipe in Odin but I hadn't found it yet. I have 2 mother boards and one is identical. I flash this stock and lose download or recovery. but the errors you show are only from doing that edl safestrap
Click to expand...
Click to collapse
chip102 said:
Ill be honest..i have no idea what you are talking about. Ive messed with the software with previous devices and never heard of safe strap. This one has been bone stock since I got it from Tmobile and i haven't attempt to flash anything until i had this issue. never tried to root it
Click to expand...
Click to collapse
https://forum.xda-developers.com/galaxy-s8/development/root-t3904613. This thread can help you at least get pie back up and running. I wouldn't mess with no more. I haven't had much luck with mine. But I did get it booting again
Tl;dr: I(dumbass) bricked my phone to the point, where I only can get the bootloader. No fastboot mode, no recovery, no boot.
How: I rooted my phone to a pretty good working state of stock OS+Magisk, right after I got it (Android 10). Later after a couple systemupdates and the patch to A11 and even more updates I thought, it would be time to patch magisk again, or revert to unroot, so I tried patching magisk, but somehow my phone got a lot of bugs, like no sound and very long boot times.
Then I tried reverting back by adding a stock boot image and stuff and a lot of things went unlike any tutorial said and now I'm stuck on beforementioned phonestate.
My PC(Asus Notebook) with installed Qualcomm-Drivers and Oneplus-drivers only recognizes the phone when I try to connect it via EDL-mode (vol-up+down+connect USB) but only for like 10 sec. Then bootloader starts up annd connection is lost.
What would be the most logical approach? How do I start?
And yes, I read a lot of posts trying to fix it myself, but I can only find so much.
This will work. https://forum.xda-developers.com/t/...l-to-restore-your-device-to-oxygenos.4084953/
MRobbo80 said:
This will work. https://forum.xda-developers.com/t/...l-to-restore-your-device-to-oxygenos.4084953/
Click to expand...
Click to collapse
Are you using the correct cable?
Thread can be closed.
I followed the beforementioned link already but on my homepc I had some issues with the tool and/or drivers, I think.
Now on my notebook Ijust wasn't quick enough, so the phone restartet into bootloader after a couple seconds.
After a couple tries it worked.
Whew, glad that worked out. I bricked my Optimus M and this guy Asdullah took time out of his day to video chat with me and help me unbrick my phone. Some folks in this community are ****ing awesome!