Related
Hi all.
I'll start by saying I have gotten in way over my head. I rooted my Evo with unrEVOked's one-click method, and then began to experience some problems with my 3g. Thinking I had somehow botched the rooting process, I tried to unroot using the two-step method I also found on xda (cannot post link.. further proof I am a noob ). More problems sprang up, one thing led to another, various fixes were tried (HUGE thanks to everyone in the IRC channel last night that tried to help my sorry ass..) but to no avail.
Here is where my phone is at now: booting using vol down+power shows me S-ON. Trying to flash mtd-eng.zip results in an error, so I am seemingly stuck with S-ON. Normally I would be happy about this (that's one step closer to unrooted, right?) but I notice I still have Superuser in my apps. My 3g is working again for whatever reason (no complaints here! maybe it was a Sprint-side problem in my area.. what timing!) but I'm confused as to whether my phone is rooted or not.
Ideally, I would like to go back to unrooted, since I have made it abundantly clear to myself that I am not yet prepared to embark in rooting. If anyone could guide me in the right direction, I would be very thankful.
You no longer have root access. Nothing you do at this point will allow you to run a .img on your own.
Your best bet would be to try and run one of the RUU programs to get it all back to stock.
I don't know if the Superuser application will be removed by this but you can try it:
Go to Settings>SD & Phone Storage>Factory Data Reset
Your phone should reboot and may have erased the Superuser app.
Jim M said:
You no longer have root access. Nothing you do at this point will allow you to run a .img on your own.
Your best bet would be to try and run one of the RUU programs to get it all back to stock.
I don't know if the Superuser application will be removed by this but you can try it:
Go to Settings>SD & Phone Storage>Factory Data Reset
Your phone should reboot and may have erased the Superuser app.
Click to expand...
Click to collapse
I did this, and my phone is now in RA-evo-v1.8.0 (it rebooted into recovery). Should I reboot the system now? I find it strange that it took me here in the first place.
The current PC36IMG that is flashed to the Evo is one with Amon Ra built into it.
The only RUU program that I am allowed to run (from the list that was given out in one of the unrooting evo threads) gives me the 170 error before anything happens.
You don't have root access, but your phone still has a custom recovery (Amon_RA) right now. No way to get rid of the custom recovery now except through an official update that replaces the recovery file.
Like I said you can try to run one of the RUU Official updates found in the Developer forum.
Don't know your location, but if you post it, someone close to you might try to help you out in person.
Jim M said:
You don't have root access, but your phone still has a custom recovery (Amon_RA) right now. No way to get rid of the custom recovery now except through an official update that replaces the recovery file.
Like I said you can try to run one of the RUU Official updates found in the Developer forum.
Don't know your location, but if you post it, someone close to you might try to help you out in person.
Click to expand...
Click to collapse
With a little digging and poking and reading, I found the proper RUU, ran it, and I believe I am now back to fully unrooted. Thank you very much for your help!
Sorry if it has been answered elsewhere, but I have a migraine and am going for now. I just wanted to post really fast. I rooted my phone recently and have CM 7.2 on my Dinc. Now it suddenly seems that programs seem to think it isn't. Programs such as Titanium Backup won't work saying there is no root. Same with BusyBox and so on. Anyone had any issues like this? Any ideas as to what is next? I am somewhat new to this and would appreciate the help.
Tried to just reroot, but can't seem to get DooMLord's thing to work. Can't get the ADB drivers since, for some reason the Android SDK thingy WILL NOT download the Google USB driver packages. Tried about 6 different times and it just will not download and install them. HELP?
BuffaloChips said:
Sorry if it has been answered elsewhere, but I have a migraine and am going for now. I just wanted to post really fast. I rooted my phone recently and have CM 7.2 on my Dinc. Now it suddenly seems that programs seem to think it isn't. Programs such as Titanium Backup won't work saying there is no root. Same with BusyBox and so on. Anyone had any issues like this? Any ideas as to what is next? I am somewhat new to this and would appreciate the help.
Tried to just reroot, but can't seem to get DooMLord's thing to work. Can't get the ADB drivers since, for some reason the Android SDK thingy WILL NOT download the Google USB driver packages. Tried about 6 different times and it just will not download and install them. HELP?
Click to expand...
Click to collapse
Open the superuser app and hit menu and select preferences. Scroll to the bottom and tap check for updates. If it says you have the latest update then hit the update anyways button. Also make sure you have the latest version of busybox installed. Then see if apps can get root. If not post back with your info.
S-off / s-on (can be found at the top of the hboot screen)
Android version (menu settings about phone software information)
Hboot version (found on hboot screen)
Radio (baseband) version. (also on hboot screen)
Also you can get the adb files and drivers here http://dinc.does-it.net/ADB
Tried that and it said d'ling manifest ... okay, parsing manifest ... okay, checking installed version = 3.0.3.2 . I clicked update anyway and got ,,, d'ling custom busybox ... okay, checking md5sum... FAIL! Tried the update fixer and it doesn't work either.Says no problems detected. In the little window it says checking signatures...ok! I click force and fix and get, extracting tiny busybox...fail! It says something about trying to download update.zip from somewhere but I cant see the rest.
My phone is s-off
Android version says 2.3.7
hboot 0.92.0000
radio 2.15.00.07.28
Now all I need are some good drugs so I can sleep. Migraines suck! It won't even let me do that.
BuffaloChips said:
Tried that and it said d'ling manifest ... okay, parsing manifest ... okay, checking installed version = 3.0.3.2 . I clicked update anyway and got ,,, d'ling custom busybox ... okay, checking md5sum... FAIL! Tried the update fixer and it doesn't work either.Says no problems detected. In the little window it says checking signatures...ok! I click force and fix and get, extracting tiny busybox...fail! It says something about trying to download update.zip from somewhere but I cant see the rest.
My phone is s-off
Android version says 2.3.7
hboot 0.92.0000
radio 2.15.00.07.28
Now all I need are some good drugs so I can sleep. Migraines suck! It won't even let me do that.
Click to expand...
Click to collapse
Try flashing these thru recovery.
http://dinc.does-it.net/SuperUser/SuperUser_3.0.7.zip, and http://dinc.does-it.net/BusyBox/Busybox_1.19.4_Flashable.zip, then boot and see if your apps can get root.
Flashed them but no good. Still says no root with programs requiring it.
Was going to go nuts and shoot for flashing Condemned CM7.2 to see if I brick my phone or not, but after d'ling the ROM, I'm not sure what I'm supposed to do next.
BuffaloChips said:
Flashed them but no good. Still says no root with programs requiring it.
Was going to go nuts and shoot for flashing Condemned CM7.2 to see if I brick my phone or not, but after d'ling the ROM, I'm not sure what I'm supposed to do next.
Click to expand...
Click to collapse
If you want to flash a new rom, download the roms zip to your sdcard. Go to recovery and go to advanced and wipe dalvik-cache. Go to mounts and storage and format everything in there except sdcard and emmc. Then go to install zip from sdcard, internal sdcard, and choose the rom zip you downloaded, and select yes to flash it.
Are you sure that you have superuser app set to allow, and not deny these root apps. Try opening superuser app ad removing the root apps from the list. Then try using the root apps and see if it propmpts for and allows root.
I have super user set to prompt me every time and I click on allow. And yes, I have deleted and retried them so many times I want to rip out what is left of my hair.
OK, after flashing Condemnedsoul's cm7.2 (post says v12 but in about phone I get v10, go figure) nothing had changed. I got the ROM manager updated and clicked fix permissions and it went through a bunch of stuff. Now, before it wouldn't do anything through the ROM manager and recovery would do nothing either. Guess I found the culprit here. This is the bad thing about not being able to remove and reinstall these little items. Makes you really crazy at times as you are not necessarily sure that it is really the issue and if it is.... it requires a bit of extra work to fix. Live and learn.
Thanks for trying hard to help me though. It is greatly appreciated.
Oh, thanks for reminding me I am an idiot for not realizing one CAN flash ROM's straight from a .zip through recovery. LMAO! (this is meant as self-deprecating and not as an insult to you)
BuffaloChips said:
I have super user set to prompt me every time and I click on allow. And yes, I have deleted and retried them so many times I want to rip out what is left of my hair.
OK, after flashing Condemnedsoul's cm7.2 (post says v12 but in about phone I get v10, go figure) nothing had changed. I got the ROM manager updated and clicked fix permissions and it went through a bunch of stuff. Now, before it wouldn't do anything through the ROM manager and recovery would do nothing either. Guess I found the culprit here. This is the bad thing about not being able to remove and reinstall these little items. Makes you really crazy at times as you are not necessarily sure that it is really the issue and if it is.... it requires a bit of extra work to fix. Live and learn.
Thanks for trying hard to help me though. It is greatly appreciated.
Oh, thanks for reminding me I am an idiot for not realizing one CAN flash ROM's straight from a .zip through recovery. LMAO! (this is meant as self-deprecating and not as an insult to you)
Click to expand...
Click to collapse
Yeah it is recomended not to use rom manager for flashing things, but to go straight to recovery to do it. The only thing i use rom manager for is so that i get notified about new versions of cwm recovery.
If flashing new roms dosent fix the issue there are always ruu's which will put your phone back to complete stock except for still having s-off, making it easy to root again.
Great! Wi-Fi doesn't want to work now! Crap! Gets as far as trying to obtain an IP address from my router and then says out of range while I am about ten feet from the router and the strength meter is showing full...! It just gets better and better some days.
BuffaloChips said:
Great! Wi-Fi doesn't want to work now! Crap! Gets as far as trying to obtain an IP address from my router and then says out of range while I am about ten feet from the router and the strength meter is showing full...! It just gets better and better some days.
Click to expand...
Click to collapse
Sounds like you need to just ruu and start over fresh. Seems something is seriously buggy with your setup. Are you using a custom kernel, or one that came with the rom?
Well, Wi-Fi was working with the original CM7.2. Just seems that it isn't with Condemned's. And I am using the kernel that came with the ROM.
To be honest, I haven't a clue about doing an RUU install.
BuffaloChips said:
Well, Wi-Fi was working with the original CM7.2. Just seems that it isn't with Condemned's. And I am using the kernel that came with the ROM.
To be honest, I haven't a clue about doing an RUU install.
Click to expand...
Click to collapse
Ruus are pretty simple. Make positive you are s-off before doing this, or rerooting will be a lot harder.
Download the ruu http://dinc.does-it.net/Stock_Images/4.06.605.3/PB31IMG.zip
Do not rename it just stick it on the root (in no folders) of your sdcard.
Boot into recovery (if entering recovery thru hboot select no when prompted to update) wipe dalvik-cache in the advanced menu, and format everything in mounts and storage except emmc and sdcard.
Power off the phone and boot to hboot. (hold vol down plus power till a white screen pops up) Hboot will find the ruu automaticly and prompt you to press vol up to update. Do so and let it do its thing, note it will reboot once durring the ruu, be patient and do not interupt it. When done press vol up to reboot. You are now stock.
Do the setup on the phone and then go to menu - settings - applications, and uncheck fastboot. Use a file explorer or pc to remove the PB31IMG.zip from your sdcard.
Power off the phone and boot to hboot again. From the hboot menu select factory reset. This will ensure all corrupt data is gone. After it finishes the phone should boot again. Once again do the setup and uncheck fastboot again.
Download these two files:
http://dinc.does-it.net/Recoveries/CWM_5.0.2.0/PB31IMG.zip
http://dinc.does-it.net/SuperUser/SuperUser_3.0.7.zip
Do not rename them and place them on the root of your sdcard.
Power off the phone and boot to hboot. It will find the PB31IMG.zip file (cwm recovery) and prompt to press vol up to update. Do so. When asked to reboot press vol down no.
Select recovery from the hboot menu. Once in recovery select install zip from sdcard - internal sdcard- and select the Superuser_3.0.7.zip. Select yes when prompted.
Reboot thr phone and go to the market and download the busybox app. Open busybox and install it. Go to your sdcard and delete or rename the clockwork PB31IMG.zip.
Thats it you should be stock rooted. From here you can stick with stock, or flash a rom of your choosing.
I have a PB31IMG.zip file that is 176,626kb with 8 "files" in it. It has andriod-info.txt, hboot_8x50_0.92.0000_100723nb0, radio.img, boot.img, recovery.img system.img splash1.nb0 and nv_MFG_VZW_1.70_0825_PRL58006.img in it. Any idea what the hell this is for? I thought about trying to use it, but I can't even remember what the hell it is. Sad, I know. I should have renamed it so I would know.
Live and learn ......
BuffaloChips said:
I have a PB31IMG.zip file that is 176,626kb with 8 "files" in it. It has andriod-info.txt, hboot_8x50_0.92.0000_100723nb0, radio.img, boot.img, recovery.img system.img splash1.nb0 and nv_MFG_VZW_1.70_0825_PRL58006.img in it. Any idea what the hell this is for? I thought about trying to use it, but I can't even remember what the hell it is. Sad, I know. I should have renamed it so I would know.
Live and learn ......
Click to expand...
Click to collapse
That is an ruu. Not sure which version, but definitley an ruu.
PB31IMG.zip files can be ruu's, radios, splash screens, recoveries, hboots, or a combination of them.
Verizon Toro cdma
I I think I know what is wrong, but can't figure out exactly how to get it fixed. I crushed my screen this weekend on my GN. So I found a decent one on Craigs. Guy had it rooted/unlocked/JB. I'm not sure what bootloader he had on it and I know for a face that it did not have the latest JB Radios.
I basically want to wipe this thing and get a stock JB back on it and then put my backed up JB rom that I have in clockwork. I can not get it to recover to this backup, but I can get it to restore back to my ICS backup. I have been trying to use wugtoolkit and have successfully got CWM touch put on, but as far as roms, I'm stuck.
I can't even flash back to stock rom in Wug??
Every time I do a factory wipe, etc in CWR it will not boot.
I went to factory images on google and didn't see a 4.1.1?? I thought they came out with it?
Any help would be appreciated.
1) stop using a toolkit.
2) there are no factory images from google for JB for the vzw nexus up yet.
3) follow this guide to the return to stock and then get the OTA to JB: http://forum.xda-developers.com/showthread.php?t=1626895
I will look into it.
Thank you
I tried that way, but commandline fails to find fastboot. I can flash the stock image through toolkit (yeah I know you said not to, but it is the only thing that works) yet it will never boot afterwards. Also the radios fail to install.
I just understand why my backup will not install. I keep getting error while restoreing /system
did you follow the steps exactly?
doesnt sound like you did.
Yep, opened up my command line, cd to the directory where the files were unzipped with 7-zip. Typed in fastboot and it says it doesn't understand that command. Using Win7.
I don't understand the toolkit, and I understand the other way you pointed to helps you learn. Still doesn't explain why it is stuck at boot (google) and why my restore/backup doesn't work.
you dont have the fastboot.exe downloaded in that same folder.
EDIT: fastboot allows you to delete the /system parition and reload it with the stock images.
Hmmm, didn't see that in the steps. Ok, so where do I get the fastboot .exe... NEVERMIND. I found it.
I also noticed in his instructions that after you unzip everything that you should have 6 files, yet I have? I downloaded the yakju.
Going through the steps, got fastboot in there now and up and running.
Click to expand...
Click to collapse
msucoleman said:
Hmmm, didn't see that in the steps. Ok, so where do I get the fastboot .exe... NEVERMIND. I found it.
I also noticed in his instructions that after you unzip everything that you should have 6 files, yet I have? I downloaded the yakju.
Going through the steps, got fastboot in there now and up and running.
Click to expand...
Click to collapse
uh you should not be using yakju. you need to be using mysid (thats the verizon version)
you could seriously screw up your phone if you use the GSM one (yakju)
got it and thanks again for pointing to that way. I see where my mistake was. I didn't download the toolkit with the other files.
Hmm, for some reason the radios did not work. Moving my .zip ones over now and will flash them. Hopefully will be back up and running full after a hour.
You might want to slow down a bit and do some reading first. 30 minutes of reading a few sticky'd posts can save you a lot of trouble. Read, understand, then flash (not the other way around). A good starting point is efrant's 101 & FAQ post.
Whoops. Flashing the correct one now.
You are correct on the slowing down part. I'm now back to where I need to be as far as starting out. I just missed that part on which file. I was thinking I could go straight to Jb, But i understand how to get there from here. That is the first time I have used fastboot and it was pretty easy.
I purchased my Pixel 2 XL from the Google store. I had just upgraded to the 8.1 OTA a few days before when i came across this video and used it to root my phone:
https://youtu.be/nFD9sa-WdUM
Here's the basic steps i took:
Unlock dev options and turn on OEM Unlocking
Boot to stock recovery
Go to his highonandroid site and download TWRP 3.1.1 beta2 (img and zip), an outdated fastboot.zip, magisk 14.5, and the USB drivers which i didnt download because my computer is already recognizing my device just fine.
Extract the fastboot files to a new folder and copy the twrp img file to the fastboot folder.
In CMD, unlock the bootloader with fastboot and reboot phone.
Connect phone as storage device, copy over twrp zip file and magisk 14.5 zip files to root folder on the phone, reboot into recovery
Use fastboot to boot the twrp image that we copied to fastboot folder to get into twrp
Unhook the USB cable, set TWRP to read only, install TWRP, hit home button, then install Magisk and reboot
Once booted up, get into Magisk, download proprietary software, run checks and done.
Once this was done, my fingerprint scanner and wifi no longer worked. I could turn wifi on but it would never find anything. I also received the error when rebooting the phone that says "There's an internal problem with your device. Contact your manufacturer for details." When this message is on the screen, if i dont touch the phone and the screen times out, it flickers really bad and never actually shuts off until i unlock it and hit the OK button.
So i decided to give it another go and ran into some big issues. I figured that i used 8.0 instructions on 8.1 and there was enough things different that it caused problems, so i used this link to reroot:
https://forum.xda-developers.com/pixel-2-xl/how-to/guide-unlock-flash-root-pixel-2-xl-t3702418
I went through the first 10-15 pages and the last 10-15 pages and did some searches on the thread and never found any of my issues, but found that a lot of people used different sets of steps and pretty much everything was successful as long as you didnt miss anything and used the most updated stuff. So i did, i went to googles website and downloaded the newest SDK with fastboot, adb, and all that good stuff, as well as the newest 8.1 image (there was a newer version but it had a carrier label on it so i didnt get that one), and the newest magisk and twrp.
I flashed 8.1 and the phone wouldnt boot, nor would it get into TWRP anymore, so i had to use fastboot to boot the twrp image and reinstall the recovery and magisk but it still wouldnt boot. I ran through several different steps and eventually got it to boot up with recovery working. Its the newest 8.1 image, the newest magisk, and the newest twrp, and since then magisk has updated a couple times.
Now on to my issues!
I still get the "Internal problem" popup when booting
I get a lot more random reboots
Sometimes random things just wont work, like streaming plex to my tv or loading an app or something on an app and i have to reboot and it works fine
I've seen numerous times that the "Internal problem" thing is just a mismatch between the system and vendor build.prop files. I dont know what exactly is mismatching between the two but i've tried reflashing them and all sorts of things and nothing ever fixes it.
Does anyone know if there's a fix to any of these three issues, or if maybe looking at my steps i clearly did something wrong? I'm willing to do the whole thing over again if there's a good suggestion, but once i flashed the 8.1 image and went that route, i rerooted successfully 4 times total before i quit doing it again just because of that internal problem popup, i kept figuring something went wrong or i did something wrong. I had no security or anything set before rooting or flashing or anything, and each time i reflashed the operating system, but when i flashed the OS, i had to extract the system file because i would constantly get an error that it was too big and it failed to truncate it, so i've always had to manually install it by first copying it to my phone and installing it through TWRP. Its been an adventure, but these problems suck!
PMad said:
...Its been an adventure, but these problems suck!
Click to expand...
Click to collapse
It's called training. For the error, you just need to fastboot flash the stock dtbo.img. This was fixed on the 15.1 version of Magisk so you shouldn't have that problem anymore. I can tell you that rooted, kernel and a few root apps and I have never had ANY random reboots, so one of your apps is causing it or you didn't start from a completely blank slate. Run your phone in Safe Mode for a while to see if you stop the reboots 100%. If so, one of your apps is the cause. If you still get reboots in Safe Mode, you're gonna need to re-install. I suggest using the instructions on the Google web page where you got the full image. (and try to distill your posts down a little, ffs)
v12xke said:
It's called training.
Click to expand...
Click to collapse
Every new phone is a new adventure, they are all the same but unique at the same time!
v12xke said:
For the error, you just need to fastboot flash the stock dtbo.img.
Click to expand...
Click to collapse
I'll give this a shot! Thank you!
v12xke said:
This was fixed on the 15.1 version of Magisk so you shouldn't have that problem anymore.
Click to expand...
Click to collapse
15.1 is the version i'm on now but nothing has changed. Which issue was this supposed to fix?
v12xke said:
I can tell you that rooted, kernel and a few root apps and I have never had ANY random reboots, so one of your apps is causing it or you didn't start from a completely blank slate.
Click to expand...
Click to collapse
My concern here is that my settings and apps are literally exactly the same as before root, except for magisk, its my only new app, which would lead me to believe that something Magisk is changing is causing the problem, or something else is happening that i'm not realizing yet.
v12xke said:
Run your phone in Safe Mode for a while to see if you stop the reboots 100%. If so, one of your apps is the cause. If you still get reboots in Safe Mode, you're gonna need to re-install. I suggest using the instructions on the Google web page where you got the full image.
Click to expand...
Click to collapse
The reboots are typically 1 reboot every 1 to 3 days, so its not a terrible issue but its happening and it shouldnt. For flashing the OS, after the first failure when trying to install it, those are the only instructions i've used, but i get that error when trying to install the OS that says something about how it failed to truncate the system.img file and so it wasnt installed, so my work around was to copy the file to the phones root folder, install the 8.1 image then immediately go and manually install the system.img file in twrp since its the only thing that fails, but i still have issues. What is this truncate issue?
v12xke said:
(and try to distill your posts down a little, ffs)
Click to expand...
Click to collapse
I agree! hahaha i just wanted to be clear and include all the details, otherwise everyone would have asked me question after question that i could have just included. It ends up being long, a lot happened!
I'll give that dtbo.img a shot and see what that clears up, then if there's issues with rebooting still i'll try safe mode for a few days and see what that does.
Thank you v12xke! (how do you pronounce that? haha)
PMad said:
...I'll give that dtbo.img a shot and see what that clears up, then if there's issues with rebooting still i'll try safe mode for a few days and see what that does.
Thank you v12xke! (how do you pronounce that? haha)
Click to expand...
Click to collapse
Your dtbo.img got patched by Magisk somewhere along the line and that is why the OS is throwing the error. Extract that img file from the full Google image and fastboot flash it, and the error will go away. There is a long thread around HERE on random reboots you should read. The v12xke is a car (Jaguar E-Type) I once owned.
v12xke said:
Your dtbo.img got patched by Magisk somewhere along the line and that is why the OS is throwing the error. Extract that img file from the full Google image and fastboot flash it, and the error will go away. There is a long thread around HERE on random reboots you should read. The v12xke is a car (Jaguar E-Type) I once owned.
Click to expand...
Click to collapse
So i just tried to do this and ran into one of the issues i had when originally trying to root it... I get into TWRP and it will not take any button presses, like the touch screen has become a screen (minus the touch). Is there a fix for this or do i just need to install TWRP before i use it each time it does this?
PMad said:
So i just tried to do this and ran into one of the issues i had when originally trying to root it... I get into TWRP and it will not take any button presses, like the touch screen has become a screen (minus the touch). Is there a fix for this or do i just need to install TWRP before i use it each time it does this?
Click to expand...
Click to collapse
1. You don't use TWRP to flash dtbo.img, you fastboot it while the phone is in bootloader mode.
2. TWRP works just fine if you install it and leave it installed. Make sure you are using 3.2.1-0 (img and zip).
v12xke said:
1. You don't use TWRP to flash dtbo.img, you fastboot it while the phone is in bootloader mode.
2. TWRP works just fine if you install it and leave it installed. Make sure you are using 3.2.1-0 (img and zip).
Click to expand...
Click to collapse
I was getting into TWRP to create a backup of everything and it popped up asking for my password, and i remembered reading that we have to get rid of all of our security before making a backup, so i tried to hit buttons to cancel it and nothing worked, i had to hold the power button. So i eliminated all of my security and went back thinking it was a 1 time issue but it happened again, it took me straight to the main menu but nothing would work. I'm using 3.2.1-0 like you mentioned and i cant press any buttons. I'd like to back everything up before flashing this or anything else.
PMad said:
I was getting into TWRP to create a backup of everything and it popped up asking for my password, and i remembered reading that we have to get rid of all of our security before making a backup, so i tried to hit buttons to cancel it and nothing worked, i had to hold the power button. So i eliminated all of my security and went back thinking it was a 1 time issue but it happened again, it took me straight to the main menu but nothing would work. I'm using 3.2.1-0 like you mentioned and i cant press any buttons. I'd like to back everything up before flashing this or anything else.
Click to expand...
Click to collapse
You don't need a backup before re-flashing the STOCK dtbo (or boot) partitions, haha. READ UP.
I was ALL good with my Pixel 6 pro, rooted and hours of tweaks in. My idiotic mistake here was I did not make a flashable backup before flashing the magisk-rooted despair kernel. Instead, because of laziness to find a nandroid backup method, I made a half-assed backup by dragging and dropping on my pc, and this has cost me.
Immediately after flashing via the 99 cent kernel flash app (can't remember the name) I was getting caught in the G loading screen bootloop.
Since then, I've tried everything. Every combination of every fastboot command I have found, on Windows and Ubuntu, multiple cables, etc. This has worked for me in every version of Android since 4.0 or earlier, as I've gone this whole time without really gaining understanding of any of the back end.
Now I cannot enter fastbootd. I get errors in fastboot that the "/system" partition does not exist. I have no stock recovery and can only enter Fastboot bootloader mode. GrapheneOS will not install due to an error at the final step indicating that fastboot is too old, despite the updates I keep reinstalling (Graphene web installer failing on download portion). Stock Recovery Flash Tool never works for me, always an error on the download. When manually flashing Stock, I am hit with the missing system partition error, the error that the image is too large for the partition, cannot determine image filename, etc.
Now, fastboot reboot bootloader doesn't even work until i unplug and replug the phone back in. And no flashing commands are attempted until the phone is unplugged/replugged. My bootloader is still unlocked as confirmed by the fastboot oem unlock command response.
Essentially I believe I am in need of a complete wipe, beyond anything I've done yet. I think I need to create new partitions before flashing? Someone please help me I'm dead in the water and on motel wifi to try and fix this stubborn beast.
When I first got my pixel 6 pro, I didn't let the update fully install and ended up using the web flasher to get it working again. Have you tried that? It'll be a full wipe but at least you would have your device.
bigdog1459 said:
When I first got my pixel 6 pro, I didn't let the update fully install and ended up using the web flasher to get it working again. Have you tried that? It'll be a full wipe but at least you would have your device.
Click to expand...
Click to collapse
Oh I've wiped it along the way already, since the "incident" of the kernel flash. Multiple ways. I would love to use the web flasher, but it just doesn't work for me. The download never completes, and I suspect even if it did that at this point it would get stuck right away and throw me an error message, likely deleting the whole download along with it.
nastyneighbor said:
Oh I've wiped it along the way already, since the "incident" of the kernel flash. Multiple ways. I would love to use the web flasher, but it just doesn't work for me. The download never completes, and I suspect even if it did that at this point it would get stuck right away and throw me an error message, likely deleting the whole download along with it.
Click to expand...
Click to collapse
Damn. I'm sure you have tried some of the manual flashing guides out there too?
nastyneighbor said:
I was ALL good with my Pixel 6 pro, rooted and hours of tweaks in. My idiotic mistake here was I did not make a flashable backup before flashing the magisk-rooted despair kernel. Instead, because of laziness to find a nandroid backup method, I made a half-assed backup by dragging and dropping on my pc, and this has cost me.
Immediately after flashing via the 99 cent kernel flash app (can't remember the name) I was getting caught in the G loading screen bootloop.
Since then, I've tried everything. Every combination of every fastboot command I have found, on Windows and Ubuntu, multiple cables, etc. This has worked for me in every version of Android since 4.0 or earlier, as I've gone this whole time without really gaining understanding of any of the back end.
Now I cannot enter fastbootd. I get errors in fastboot that the "/system" partition does not exist. I have no stock recovery and can only enter Fastboot bootloader mode. GrapheneOS will not install due to an error at the final step indicating that fastboot is too old, despite the updates I keep reinstalling (Graphene web installer failing on download portion). Stock Recovery Flash Tool never works for me, always an error on the download. When manually flashing Stock, I am hit with the missing system partition error, the error that the image is too large for the partition, cannot determine image filename, etc.
Now, fastboot reboot bootloader doesn't even work until i unplug and replug the phone back in. And no flashing commands are attempted until the phone is unplugged/replugged. My bootloader is still unlocked as confirmed by the fastboot oem unlock command response.
Essentially I believe I am in need of a complete wipe, beyond anything I've done yet. I think I need to create new partitions before flashing? Someone please help me I'm dead in the water and on motel wifi to try and fix this stubborn beast.
Click to expand...
Click to collapse
Not sure when you said you used "Stock Recovery Flash Tool" if you meant the "Android Flash Tool". But just in case you didn't, that can force flash partitions with it. Probably your best shot.
Android Flash Tool
flash.android.com
Android Flashing Tool online unbricked me the other day. You have to be patient with the tool as it took me several tries. It will totally wipe your phone, but at this point you just need to rescue your device. Keep us posted.
thanks for the tip. i'm trying the android flash tool again now. and will keep trying it until it at least passes the download stage. and yes i tried all the manual flashing guides out there...and hybrid combos of all as well. i mean i'm positive its my fault for missing SOMEthing somewhere but many hours have been spent with overall negative progress.
my track record is still zero hard bricked devices or soft ones I couldn't fix over all these years so i'm not too worried but i could use my phone back haha
will keep posted as requested. ty again.
I know this doesn't help your immediate situation, but when flashing anything like custom kernels, I would advise not to use some random app to flash it with, just follow the directions in the OP of the kernel's thread, and make sure you have up to date Platform Tools and driver. CleanSlate and many or all the custom kernels also require flashing more than just the boot.img.
Good luck, I hope you get it back working for you.
Hey guys, the Android Flashing Tool finally worked for me and I am up and running again. Thanks for your help and tips. Hacking phones is more important every year and thus I truly value your skills and advice. This community must survive the new world order. much love folks