Related
Please bear with me. I tried posting questions about this in the Q/A forum and received no real help.
I recently went from FRF50 to FRF83 and started getting random reboots. I'm on the 4.06.00.12_07 radio with the stock kernel. I wiped everything before flashing.
Today I wiped again and reflashed FRF50 and everything seemed to be okay aside from maybe 1 reboot.
I just flashed the stock FRF85B and rooted it and I'm back to rebooting. It's even worse now. It reboots the instant everything loads.
I got the last_kmsg:
http://pastebin.org/365407
Please let me know what's wrong. I'm dying to know. Is it hardware? Is it the battery? Am I going to have to pay a buttload of cash for HTC to fix it?
Thanks for any help
1) This is the wrong forum and you know it.
2) Wipe everything, start over from stock rom.
GldRush98 said:
1) This is the wrong forum and you know it.
2) Wipe everything, start over from stock rom.
Click to expand...
Click to collapse
Is it the wrong forum? Do people at the Q/A or general forum know about kernels/deeper info and do the people who know about that stuff venture over to those forums?
I tried getting info there, and I got none. This is the last place to turn.
What would wiping and starting from stock achieve?
No excuse for posting in the wrong location. But wipe data, all caches and reflash stock rom + radio. Report in General Section.
S_Dot said:
No excuse for posting in the wrong location. But wipe data, all caches and reflash stock rom + radio. Report in General Section.
Click to expand...
Click to collapse
How will this help me? Okay if stock works, but what about the update?
Why not maybe looking at using one of the moded versions of the Rom. If those dont work then maybe you need to think of going back to the Stock 2.1 and waiting for OTA to hit your phone. Going back to 2.1 will fix the problem and getting the OTA should work. Other wise wiping and reflashing is all that someone can tell you to do since I know i am using FRF83 right now with no reboots.
Just wipe everything inc dalvik-cache
Stock kernel keeps rooting so I guess its a framework issue
Prod1702 said:
Why not maybe looking at using one of the moded versions of the Rom. If those dont work then maybe you need to think of going back to the Stock 2.1 and waiting for OTA to hit your phone. Going back to 2.1 will fix the problem and getting the OTA should work. Other wise wiping and reflashing is all that someone can tell you to do since I know i am using FRF83 right now with no reboots.
Click to expand...
Click to collapse
leonnib4 said:
Just wipe everything inc dalvik-cache
Stock kernel keeps rooting so I guess its a framework issue
Click to expand...
Click to collapse
I'm going to try to go back to stock and see if it works. If not I can only assume that it is a hardware problem and I'll have to bite the bullet and pay for repairs.
What kind of a hardware problem could it be???
Can someone help me get back to stock properly?
See sticky.
Mod move to q&aplease.
leonnib4 said:
See sticky.
Mod move to q&aplease.
Click to expand...
Click to collapse
Sticky is full of bad info. I have new radio (4.06.00.12_07).
I'm assuming that if I get stock radio and the ERD79 update.zip I should be fine?
GldRush98 said:
1) This is the wrong forum and you know it.
2) Wipe everything, start over from stock rom.
Click to expand...
Click to collapse
You sir, are a complete asshole.
Sent from my Nexus One using XDA App
Yes the new radio won't work on 2.1 so change Ur radio and flash that update.zip and cross Ur fingers that Ur problem is fixed good luck let us know
Sent from my Nexus One using XDA App
FML. Hardware issue. Just went through CM 5.0.8. flash from scratch including re-flashing new radio and new recovery and I got a reboot during sign-in to Google.
God ****ing dammit.
Any logcat?
if you have an ext partition.. wipe that as well..
might be a battery issue. my battery had been overheated during navigation and right after boot it would give out turn off and boot again. just replaced it and worked fine.
To check battery issue, I suppose running with charger inserted would be enough.
Jack_R1 said:
To check battery issue, I suppose running with charger inserted would be enough.
Click to expand...
Click to collapse
What do you mean by this?
I'm pretty sure it is the battery. Been keeping minimal use today without USB charging and haven't had a reboot.
Any other ways I can confirm a bad battery?
Sent from my Nexus One using XDA App
If you can successfully boot and use the phone heavily while connected to a charger (preferrably AC charger - it can provide twice the current of USB cable), and you see no reboots - I believe that would point to your battery with a very high probability.
noob here,,,where can I find a thread on flashing recoverys and how to get back to a working recovery if something goes bad....Thanks
[Solved]
i reloaded sdk,java bla bla bla like i said, any way still didnt recognize by just typing adb shell...
so just for kicks i decided to go ahead and do this
cd C:\android-sdk-windows\tools...got
cd C:\android-sdk-windows\tools>adb devices...got
(recognized phone)>>>>>
cd C:\android-sdk-windows\tools>adb shell
#flash_recovery image /sdcard/recovery-clockwork-4.0.0.2-heroc-20110611.img (enter)
mtd: successfully bla bla bla
#reboot....
worked like a charm,,, thanks again coffeehandle for all your help
drlzanej said:
noob here,,,where can I find a thread on flashing recoverys and how to get back to a working recovery if something goes bad....Thanks
Click to expand...
Click to collapse
Search here on Hero CDMA development
and when ever a a post is a recovery, at the begining of the title it will say [RECOVERY]
or you can use the search button anytime. "Clockworkmod Recovery" or what have you. Youre recovery really shouldn go bad unless you did something stupid.
and 1 way to get a new Recovery is through Rom Manger but id highly suggest to use ABD/SDK. its not TOO hard to set up heres a link showing step by step instructions.
This site will probably half your answers that you might have already
http://wiki.cyanogenmod.com/index.php?title=Howto:_Install_the_Android_SDK
edit: PM me if you need anything elso
What do you mean if something goes bad??? Care to give a little more details???
#Root/Hack-Mod_Always*
key word is "noob", lol,,,in case i screw something up, and yes i have been known to do that from time to time. sorry for the lack of detail. thanks
Well you still didn't state if your problem was still an issue. Or if the information that coffeehandle has been kind enough to provide you with resolved you issue.
#Root/Hack-Mod_Always*
stepped away for a moment
got called away for work, thats why i didnt respond with a speedy reply...yes his information was helpful, it did resolve my issue, and i did hit the thanks button.....a little more information and i probably would have given a generous donation as well...(gave 10 bucks to someone once for writing "wipe cashe, wipe data, wipe dalvik, flash away").....so i think all have completed their missions on this thread, dont you ?
Btw laie , if your not responding with helpful info,,,why are you responding??? just curious
Glad you got it worked out. Have a good one.
#Root/Hack-Mod_Always*
drlzanej said:
got called away for work, thats why i didnt respond with a speedy reply...yes his information was helpful, it did resolve my issue, and i did hit the thanks button.....a little more information and i probably would have given a generous donation as well...(gave 10 bucks to someone once for writing "wipe cashe, wipe data, wipe dalvik, flash away").....so i think all have completed their missions on this thread, dont you ?
Btw laie , if your not responding with helpful info,,,why are you responding??? just curious
Click to expand...
Click to collapse
Because its respectful to let the board know in general that you've figured it out. By telling us that, it lets others know maybe how to fix the same type of problem instead of leaving the thread in limbo. Simply edit your original post and put [solved] in the header also works and is very easy. Some xda users only use the app like myself and don't see the thanks. Plus it doesn't say that it worked for you. Just that you thanked him for a reply to your problem or whatever we could assume. And we all know what assume means. Makes an ASS out of U and ME.
®patience is a virtue©
Thanks Matt for the advice, dont get to visit here as often as id like, so im still learning the ropes man,,,thanks again
solved <edited>
solution <posted>
later......
Its all good man. Just things like this will help noobs and the easier it is for them to find info the less we senior members have to post that's all.
®patience is a virtue©
hi i have been trying to mount the phone to read/write in order to access the /system folder for copying files
however, i am unable to do this
i have tried the mount r/w applications online but not working as well
i have tried all the commends on adb as well, what i get is "remount fail: read-only file system
i have used the abd to run super user, but it shows im already a super user
i have tried to set adb to set as root and it also shows already running as root.
any ideas guys??
i have tried reflashing several kernels and also roms, same thing.
oh additional note, i have tried adb in recovery mode and also in normal mode, doesnt work.
and my usb debugging is already checked
Very interesting development. Download Link please... :silly:
Despite that this surely the wrong thread you could tell us whether you have this problem on a toaster or a tumble dryer...
And what are you trying?
adb push iOS5.apk /system/s**t or what?
hi there, thank you for the really useless reply there. unfortunately you are right, i had put this in the wrong place. anyway, thanks to the admin for helping me move it to the right place.
in case you have been in a cave or dont have google, many people have issues trying to mount read/write capabilities in their /system folders be it to be able to move some things in there or to push applications.
as most people who ask questions here dont get much answers because of people like you, i had to do my own searching and try everything on the web and sadly it didnt work.
so, for people who have come to this thread looking for answers, please try the following (only if you have tried everything)
SOLUTION
it would seem that after flashing many roms, the /system folder has issues.
please go to recovery (CWM) > mounts and storage> format /system
once you have done this, please reinstall your rom. this will fix your issues.
as for trahzef*ck: i'll give u a thanks since you being a d*ck helped me figure out my solution and you look like you need a hand in being nice
vyraz said:
hi there, thank you for the really useless reply there. unfortunately you are right, i had put this in the wrong place. anyway, thanks to the admin for helping me move it to the right place.
in case you have been in a cave or dont have google, many people have issues trying to mount read/write capabilities in their /system folders be it to be able to move some things in there or to push applications.
as most people who ask questions here dont get much answers because of people like you, i had to do my own searching and try everything on the web and sadly it didnt work.
so, for people who have come to this thread looking for answers, please try the following (only if you have tried everything)
SOLUTION
it would seem that after flashing many roms, the /system folder has issues.
please go to recovery (CWM) > mounts and storage> format /system
once you have done this, please reinstall your rom. this will fix your issues.
as for trahzef*ck: i'll give u a thanks since you being a d*ck helped me figure out my solution and you look like you need a hand in being nice
Click to expand...
Click to collapse
Congrats! Obviously you have learned something. Learning by own research will help more than to be spooned.
To be honest: Maybe my answer was harsh. But be aware for the following:
- Post in the right section
- Give people, who want to help the needed information. Rom, Version, Kernel etc. So that they can help.
- and don't try to be so smart ass cause you found a format command. There are already enough on XDA.
As your thank meter is Zero I give u one back. for your most intelligent word/spelling creations. It's your first one. maybe the last.
Halleluja! An new &%/()&%%$ on XDA. Thank god.
Maybe you have partial root. Try Busybox from playstore and update the binaries.
trahzebuck said:
Congrats! Obviously you have learned something. Learning by own research will help more than to be spooned.
To be honest: Maybe my answer was harsh. But be aware for the following:
- Post in the right section
- Give people, who want to help the needed information. Rom, Version, Kernel etc. So that they can help.
- and don't try to be so smart ass cause you found a format command. There are already enough on XDA.
As your thank meter is Zero I give u one back. for your most intelligent word/spelling creations. It's your first one. maybe the last.
Halleluja! An new &%/()&%%$ on XDA. Thank god.
Click to expand...
Click to collapse
haha well i dont care about hard answers, just answers, you on the other hand gave nothing. no wonder although your status shows "senior member" all you have is a measly 200 odd thanks. half of them must have been like mine, pity thanks for nothing.
i will however take your advice on the first two, but i dont have to be one because you apparently are one big enough to cover most of the members here.
thanks for the thanks but i think you may need one more then me.
and last but not least, yes i can spell, and its quite obvious much better then you can and if i am another *ssh0le on the forum, i must have learnt from the best, thanks a mil trasherf*ck! you're my hero
sahilarora2003 said:
Maybe you have partial root. Try Busybox from playstore and update the binaries.
Click to expand...
Click to collapse
erm nope, i checked with afew other guys, who root alot as well, apparently sometimes the /system file will get mucked up like that once in awhile. so this doesnt really apply to specific phones or tabs but to all who may have this issue.
but the issue has been resolved. thanks for the suggestion tho...
Thread closed
sahilarora2003 said:
Maybe you have partial root. Try Busybox from playstore and update the binaries.
Click to expand...
Click to collapse
Thank you, sahilarora2003, you are the only responsible poster in this thread.
If a post is placed in the wrong subforum, simply hit the report button and we'll move it. There is no need for the drippingly sarcastic responses I see here, provoked or not.
The rest of you need to smarten up.
Basically my phone is stuck on the GT-N7000 Samsung Logo screen.
Would love if somebody could make my day and tell me how I can restore my phone with it's pictures.
I know this is not as simple as it sounds but I have read a thread that explains something about non-wiping ROMs / upgrade ROMs? Is this true?
Notes:
I have a stock ROM (I bought the phone via Amazon Germany though).
Never tried to place another ROM onto phone.
I cannot go into recovery mode.
I am able to go into download mode.
I have heard of this ODIN but not familiar.
Heeelp!
This is a good thread to learn about odin
http://forum.xda-developers.com/showthread.php?t=1424997
Sent from my GT-I9500 using xda premium
nokiamodeln91 said:
This is a good thread to learn about odin
http://forum.xda-developers.com/showthread.php?t=1424997
Sent from my GT-I9500 using xda premium
Click to expand...
Click to collapse
501 pages to the thread don't suppose you know anything about upgrade ROM's?
Makkand said:
501 pages to the thread don't suppose you know anything about upgrade ROM's?
Click to expand...
Click to collapse
If you do not want to listen and do not want to read yourself (at least the first few posts with the tutorials) then why do you cry for help?
And answer in such an idiotic behavior?
Don't you think that it is this way of ignorance that is resulted in your "bricked" device?
ThaiDai said:
If you do not want to listen and do not want to read yourself (at least the first few posts with the tutorials) then why do you cry for help?
And answer in such an idiotic behavior?
Don't you think that it is this way of ignorance that is resulted in your "bricked" device?
Click to expand...
Click to collapse
Are you kidding me!? You're honestly a senior member? Calling my response idiotic is probably a little ironic. Let me explain why...
Firstly, I'm not going to waste too much of my time replying to you but my concern was that during the 501 pages of the thread something may changed from the start, I can't be sure how accurate the first posts are, which I feel is a valid point 1.
As for the bricked device, the phone became bricked itself due to no fault of my own, other people have experienced the same thing, I have avoided popping ROM's onto the phone to avoid voiding my warranty, I did not tamper with anything, this is valid point 2.
If you have nothing positive to contribute to this thread please refrain from adding any further comments, or take a chill pill and use a little empathy senior member.
I should also add that:
- I eeked at the 501 pages - I was not being condescending.
- I believe that there is a difference between ROM's that completely flash the whole memory and upgrade ROM's that will retain, hence why I asked the question, about 'upgrade' ROM's.
If you want to pull the pictures from the phone internal memory you can use a pc program called adb.exe, but you need to be in download mode.
Makkand said:
Are you kidding me!? You're honestly a senior member? Calling my response idiotic is probably a little ironic. Let me explain why...
Firstly, I'm not going to waste too much of my time replying to you but my concern was that during the 501 pages of the thread something may changed from the start, I can't be sure how accurate the first posts are, which I feel is a valid point 1.
As for the bricked device, the phone became bricked itself due to no fault of my own, other people have experienced the same thing, I have avoided popping ROM's onto the phone to avoid voiding my warranty, I did not tamper with anything, this is valid point 2.
If you have nothing positive to contribute to this thread please refrain from adding any further comments, or take a chill pill and use a little empathy senior member.
I should also add that:
- I eeked at the 501 pages - I was not being condescending.
- I believe that there is a difference between ROM's that completely flash the whole memory and upgrade ROM's that will retain, hence why I asked the question, about 'upgrade' ROM's.
Click to expand...
Click to collapse
Except he is right. This has been discussed. You're method is to read that thread. This is a website (or at least is supposed to be) for users that are willing to read the guides people have slaved to create
Everything you need to know is there.
And absent hardware failure, a phone doesn't brick itself.
Read dr.ketan thread on how to flash a stock ROM via PC Odin from download mode. The guide is current. This is the only answer you will receive here.
AndroidSlave said:
Except he is right. This has been discussed. You're method is to read that thread. This is a website (or at least is supposed to be) for users that are willing to read the guides people have slaved to create
Everything you need to know is there.
And absent hardware failure, a phone doesn't brick itself.
Read dr.ketan thread on how to flash a stock ROM via PC Odin from download mode. The guide is current. This is the only answer you will receive here.
Click to expand...
Click to collapse
Thai and AndroidSlave are right, if they are harsh they are being truthful and trying to help. Cherish their advice, the answer is there, lets not fight please.
Sent from my GT-N7000 using Tapatalk 2
rangercaptain said:
If you want to pull the pictures from the phone internal memory you can use a pc program called adb.exe, but you need to be in download mode.
Click to expand...
Click to collapse
Thanks Ranger Captain! Much appreciated. I'll look into this!
The expert on adb.exe is a user nemed studacris. I think it would be ok to PM him and get the specifics of the command.
Roughly, connect the phone to the pc in download mode, open a command window, navigate to your adb directory, type adb device to confirm the connection, then type adb pull \directory name\all files /directory on pc and the files will transfer from the internal phone memory to your pc.
AndroidSlave said:
Except he is right. This has been discussed. You're method is to read that thread. This is a website (or at least is supposed to be) for users that are willing to read the guides people have slaved to create
Everything you need to know is there.
And absent hardware failure, a phone doesn't brick itself.
Read dr.ketan thread on how to flash a stock ROM via PC Odin from download mode. The guide is current. This is the only answer you will receive here.
Click to expand...
Click to collapse
When you come across a 501 page thread and say the answer is there and current for people who are willing to read there is a bit of a problem here.
I was hoping a tech Guru on here who is familiar with my problem could help summarise key points relevant to my problem.
I am willing to concede after some of you have eluded to much of the information is in the first few pages. Thank you.
As for bricking - there has been corruption of what seems to be the firmware, which not is of the question, what point are you making? If you read a few other threads, others have experienced similar issues with attempting to update their ROM's.
baz77 said:
Thai and AndroidSlave are right, if they are harsh they are being truthful and trying to help. Cherish their advice, the answer is there, lets not fight please.
Sent from my GT-N7000 using Tapatalk 2
Click to expand...
Click to collapse
Sorry Tapatalk you have not taken my view into consideration at all. But I appreciate your intervention.
rangercaptain said:
The expert on adb.exe is a user nemed studacris. I think it would be ok to PM him and get the specifics of the command.
Roughly, connect the phone to the pc in download mode, open a command window, navigate to your adb directory, type adb device to confirm the connection, then type adb pull \directory name\all files /directory on pc and the files will transfer from the internal phone memory to your pc.
Click to expand...
Click to collapse
You are the man!! Thank you kindly!
Makkand said:
When you come across a 501 page thread and say the answer is there and current for people who are willing to read there is a bit of a problem here.
I was hoping a tech Guru on here who is familiar with my problem could help summarise key points relevant to my problem.
Click to expand...
Click to collapse
Hey man. All you need to do is read the first post of dr.ketan's thread. Good luck. If flashing a stock ROM via PC Odin doesn't work, per the isnstructions on that thread, I will personally be more than glad to help. But that IS your first step.
There is nothing to summarize. Follow the procedure in that thread OP. You don't have to read ANY of the thread except the guide. If it doesn't help you get up and running, feel free to PM me or post here. But when someone tells you to read a thread you must realize they are probably referring to the Original Post. If you are told to search (xda users rule #1), then that is a different story. For example, if you said 'how do I Use an OTG cable', I would say 'search this thread for the keyword otg'. Nevertheless, that is not the case here. There is a specific guide in the OP of that thread that describes what your first step to fix your device should be. Once that has been exhausted, please feel free to ask for further guidance.
Take care and good luck.
AndroidSlave said:
Hey man. All you need to do is read the first post of dr.ketan's thread. Good luck. If flashing a stock ROM via PC Odin doesn't work, per the isnstructions on that thread, I will personally be more than glad to help. But that IS your first step.
There is nothing to summarize. Follow the procedure in that thread OP. You don't have to read ANY of the thread except the guide. If it doesn't help you get up and running, feel free to PM me or post here. But when someone tells you to read a thread you must realize they are probably referring to the Original Post. If you are told to search (xda users rule #1), then that is a different story. For example, if you said 'how do I Use an OTG cable', I would say 'search this thread for the keyword otg'. Nevertheless, that is not the case here. There is a specific guide in the OP of that thread that describes what your first step to fix your device should be. Once that has been exhausted, please feel free to ask for further guidance.
Take care and good luck.
Click to expand...
Click to collapse
That was a meaningful considered response and appreciated, thank you.
Makkand said:
That was a meaningful considered response and appreciated, thank you.
Click to expand...
Click to collapse
did you solve your problem?
AndroidSlave said:
did you solve your problem?
Click to expand...
Click to collapse
I have seen that this is something that I need to sit down and concentrate on however I have not had a spare moment. I will have a crack at over the next few days and feedback in...most likely I will have more questions but watch this space!
AndroidSlave said:
did you solve your problem?
Click to expand...
Click to collapse
I was reading. There is something not quite clear. Although the thread tells you a lot about how to do something, it doesn't say what it does or what it's for.
I've downloaded the software but further threads highlight that data may still be deleted.
Would you mind advising of how the thread can ensure that my data will not be deleted?
Makkand said:
I was reading. There is something not quite clear. Although the thread tells you a lot about how to do something, it doesn't say what it does or what it's for.
I've downloaded the software but further threads highlight that data may still be deleted.
Would you mind advising of how the thread can ensure that my data will not be deleted?
Click to expand...
Click to collapse
Which data you refer to?
Question: is your data nor backed up via Google?
As for SD card data, like photos, is that what you're talking about?
What happened to the recovery partition?
Before posting your reply, just to be clear, I do not need a guide on rooting my device or flashing a recovery. This has already been done! So please don't spam links at me for things I can find with a 5 minute search on google because I have don't this already <3
lukemovement1 said:
Not long go the pixel 5 and its been a while since I've played with flashing device partitions. Can anyone give me some pointers on the below?
Is the recovery now the boot partition and the boot partition boot_a?
Is their a way of rooting lineage os without having to modify the boot.img? (idk about amazon)
Do I need to re-root with magisk after each update?
Click to expand...
Click to collapse
Unfortunately you might have asked this in the wrong forum, thus no replies. Look here in Guides https://forum.xda-developers.com/t/guide-root-pixel-5-android-11-r.4187609/
What on earth makes you think I need a guide to rooting my device?
Made the question a bit simpler to avoid confusion
lukemovement1 said:
What on earth makes you think I need a guide to rooting my device?
Made the question a bit simpler to avoid confusion
Click to expand...
Click to collapse
You did originally ask about rooting so I thought I'd help out a little. What I don't understand is your animosity towards an attempt at posting a possible helpful link. Maybe a simple.. let me clarify my request since it might not have been clear. Oh well good luck.
lukemovement1 said:
What happened to the recovery partition?
Before posting your reply, just to be clear, I do not need a guide on rooting my device or flashing a recovery. This has already been done! So please don't spam links at me for things I can find with a 5 minute search on google because I have don't this already <3
Click to expand...
Click to collapse
Hmmmm, your edit removed the actual question and I don't remember exactly what it was.
xunholyx said:
Hmmmm, your edit removed the actual question and I don't remember exactly what it was.
Click to expand...
Click to collapse
Fastboot says that the recovery doesn't exists?
lukemovement1 said:
Fastboot says that the recovery doesn't exists?
Click to expand...
Click to collapse
I'm not sure what you mean.
fastboot reboot recovery won't work. It never has afaik
fastboot boot *twrp.img name* should work if you are trying the test build of TWRP
adb reboot recovery always works
You can't boot to recovery from bootloader with fastboot commands, but you can boot to it with adb commands while booted to /system
lukemovement1 said:
What happened to the recovery partition?
Before posting your reply, just to be clear, I do not need a guide on rooting my device or flashing a recovery. This has already been done! So please don't spam links at me for things I can find with a 5 minute search on google because I have don't this already <3
Click to expand...
Click to collapse
I'm guessing, as there's really not enough information to know for sure, but is this possibly a google treble question?
prior to treble, yes->recovery partition
with treble->no recovery partition, but another 'slot' for recovery.
cheers
Recovery and boot have merged into one partition, (on a/b devices at least) and you ship your boot and reco partitions in a unified boot image now which you can flash with fastboot flash boot x.img.
lukemovement1 said:
What on earth makes you think I need a guide to rooting my device?
Made the question a bit simpler to avoid confusion
Click to expand...
Click to collapse
Ay, Ay, Ay,,,
To be fair, he was only trying to help, a simple this isn't helpful goes a long way. Being sour though, gets everyone absolutely nowhere.
And you did ask "Is their a way of rooting lineage os without having to modify the boot.img" -- I believe he was guiding you to that thread to possibly ask there as you may get a faster response. I think the question was just taken incorrectly is simply all. No harm, no foul.
bobby janow said:
You did originally ask about rooting so I thought I'd help out a little. What I don't understand is your animosity towards an attempt at posting a possible helpful link. Maybe a simple.. let me clarify my request since it might not have been clear. Oh well good luck.
Click to expand...
Click to collapse
You make more friends with lemonade, or something like that, you were trying to help, so good job in my eyes.
xunholyx said:
Hmmmm, your edit removed the actual question and I don't remember exactly what it was.
Click to expand...
Click to collapse
I'll help.
"Is their a way of rooting lineage os without having to modify the boot.img"
xunholyx said:
I'm not sure what you mean.
fastboot reboot recovery won't work. It never has afaik
fastboot boot *twrp.img name* should work if you are trying the test build of TWRP
adb reboot recovery always works
You can't boot to recovery from bootloader with fastboot commands, but you can boot to it with adb commands while booted to /system
Click to expand...
Click to collapse
I believe he was propbly doing a list of the partition table, and I haven't looked myself, but recovry is missing and instead of doing some research into this, he was simply asking for a simple answer, I feel this is the point of the Q & A forum, so good job to OP.. Personaly I feel this needed a simple answer, as someone coming from like a htc one m8 or htc 10 (like myself) what the hell happened to recovery.img -- a fair question in my eyes, everyone.
AsItLies said:
I'm guessing, as there's really not enough information to know for sure, but is this possibly a google treble question?
prior to treble, yes->recovery partition
with treble->no recovery partition, but another 'slot' for recovery.
cheers
Click to expand...
Click to collapse
Appreciate the info, thank you.
fadedave said:
Recovery and boot have merged into one partition, (on a/b devices at least) and you ship your boot and reco partitions in a unified boot image now which you can flash with fastboot flash boot x.img.
Click to expand...
Click to collapse
Thank you!
Guys, this is how it should work. This is the point of the Q&A thread, ask a question, get an answer, no need for anyone to get upset or to be sour. A question was asked, an answer was kindly given.
Kinda lost all faith in this forum tbh. Loads of incorrect and missing info, asking a question is a battle and half the ROMs and images don't work
lukemovement1 said:
asking a question is a battle
Click to expand...
Click to collapse
That's because you're making it a battle. As mentioned above, you were partly to blame for the initial misunderstanding. If people don't fully understand your question, instead of being upright rude, maybe rephrase or add more clarification as @andybones said.
lukemovement1 said:
half the ROMs and images don't work
Click to expand...
Click to collapse
There are 3 roms in this forum for Pixel 5. They all work and all are regularly updated. You are complaining about the time, sweat and money that developers put in to bring custom roms to us for free. If you don't like something about it, post a feedback or don't use it rather than be disrespectful.
lukemovement1 said:
Kinda lost all faith in this forum tbh. Loads of incorrect and missing info
Click to expand...
Click to collapse
Then leave, or contribute to providing the correct and missing info, rather than, again, complain about free info people bring together in their spare time. None of us here are paid to bring info and provide code. We all do it in our spare time and share our knowledge because we want to make a positive community.
Your total disrespect, negativity and entitlement is not welcome here.
Touché
If you post was removed, it's because I decided to do some house-cleaning -- no one did anything wrong.
And I fixed the title to the thread, so that it's easier on those seeing it and understand what the "simple question" actually is.
Not sure why people get all salty over a simple question...
There is no /recovery partition on Pixel devices. Recovery coresides with the kernel in /boot. Previously, with Android 10, it was possible to install a custom recovery alongside a rooted kernel (such as using Magisk) but Android 11 broke this.
The best and most foolproof option in my opinion is to only temporarily boot a custom recovery to perform modifications. This is what I do every time I get an update on my Pixel 5 - I download the OTA, boot TWRP, install the OTA, reboot to system, let the update finish, boot TWRP again, and flash Magisk.
lukemovement1 said:
What happened to the recovery partition?
Before posting your reply, just to be clear, I do not need a guide on rooting my device or flashing a recovery. This has already been done! So please don't spam links at me for things I can find with a 5 minute search on google because I have don't this already <3
Click to expand...
Click to collapse
agree , the people don't want to help,