Hello
Excuse me but I'm a newbie to all of this. I have found tons of posts here to help me with whatever I need but now I can't seem to find a way to update to 5.1
I tried the OTA but it didn't work since my device is already rooted although I am still running 5.0.1.
I tried sideloading it but it didn't work and I read a few posts that it won't work anymore since I rooted already.
So what's left to do? Flash image? If so, can someone point me in the right direction? Didn't any new posts regarding 5.1 image flashing and I really don't wanna risk doing anything stupid. Also, I read that there's a way through which I can bypass losing all my data?
Thanks in advance!
mounirkh said:
Hello
Excuse me but I'm a newbie to all of this. I have found tons of posts here to help me with whatever I need but now I can't seem to find a way to update to 5.1
I tried the OTA but it didn't work since my device is already rooted although I am still running 5.0.1.
I tried sideloading it but it didn't work and I read a few posts that it won't work anymore since I rooted already.
So what's left to do? Flash image? If so, can someone point me in the right direction? Didn't any new posts regarding 5.1 image flashing and I really don't wanna risk doing anything stupid. Also, I read that there's a way through which I can bypass losing all my data?
Thanks in advance!
Click to expand...
Click to collapse
you can just flash a 5.1 rooted rom, just like before 5.1. thats the easiest way around. you can flash the factory img as well, then reroot.
Download the Google factory image here: https://developers.google.com/android/nexus/images
Extract the system.img and boot.img then fastboot flash them. Read general > all in one guide > question 28 for fastboot.
Once flashed, boot straight into twrp recovery and flash SuperSU. Zip to root.
Edit.. Or if you want, you can download a pre-rooted ROM.zip and just flash that from twrp recovery
rootSU said:
Download the Google factory image here: https://developers.google.com/android/nexus/images
Extract the system.img and boot.img then fastboot flash them. Read general > all in one guide > question 28 for fastboot.
Once flashed, boot straight into twrp recovery and flash SuperSU. Zip to root.
Edit.. Or if you want, you can download a pre-rooted ROM.zip and just flash that from twrp recovery
Click to expand...
Click to collapse
simms22 said:
you can just flash a 5.1 rooted rom, just like before 5.1. thats the easiest way around. you can flash the factory img as well, then reroot.
Click to expand...
Click to collapse
Do you guys advise me to do this? http://forum.xda-developers.com/nexus-6/development/rom-3-13-stock-rooted-5-1-lmy47d-root-t3054253
Also all I need is to flash this ROM? Nothing else? If so, I intend to do it using ROM Manager.
mounirkh said:
Do you guys advise me to do this? http://forum.xda-developers.com/nexus-6/development/rom-3-13-stock-rooted-5-1-lmy47d-root-t3054253
Also all I need is to flash this ROM? Nothing else? If so, I intend to do it using ROM Manager.
Click to expand...
Click to collapse
no advice, flash whatever you like. but ill warn you ROM Manager is an ancient app that WILL cause you issues. what you should do iz boot into twrp recovery, flash whatever, then reboot. thats how you flash. remember my words, rom manager WILL cause you iasues.
Just flashing a rooted rom will not install the newest bootloader and modem/radio. So I wouldn't recommend that....
But either way works if all you want to do is get on 5.1 without updating the bootloader and modem/radio
idtheftvictim said:
Just flashing a rooted rom will not install the newest bootloader and modem/radio. So I wouldn't recommend that....
But either way works if all you want to do is get on 5.1 without updating the bootloader and modem/radio
Click to expand...
Click to collapse
I'm never updating my bootloader. At least not until I have to. The 5.1 bootloader is not a friend of anyone racking up their frequent flasher miles.
rootSU said:
I'm never updating my bootloader. At least not until I have to. The 5.1 bootloader is not a friend of anyone racking up their frequent flasher miles.
Click to expand...
Click to collapse
the last time i flashed a bootloader was on the nexus 7, and that was in 2012. i dont flash bootloaders ever, but that n7 original bootloader was broken. im not planning on flashing the n6 bootloader either.
simms22 said:
the last time i flashed a bootloader was on the nexus 7, and that was in 2012. i dont flash bootloaders ever, but that n7 original bootloader was broken. im not planning on flashing the n6 bootloader either.
Click to expand...
Click to collapse
I flashed one if the modified loaders on the n5. Just aesthetics really.
This ROM manager? Ah... Memories
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my Google N6 on VZ
DebianDog said:
This ROM manager? Ah... Memories
Sent from my Google N6 on VZ
Click to expand...
Click to collapse
Always hated that app tbh Caused problems instead of offering solutions. Just my opinion though..
gee2012 said:
Always hated that app tbh Caused problems instead of offering solutions. Just my opinion though..
Click to expand...
Click to collapse
Yep. I saw a lot of HTC desire users get into trouble with it.
rootSU said:
Yep. I saw a lot of HTC desire users get into trouble with it.
Click to expand...
Click to collapse
Helium is seemingly going the same way lately, fc`s while backing up apps and loaded cloud backups not restoring
gee2012 said:
Always hated that app tbh Caused problems instead of offering solutions. Just my opinion though..
Click to expand...
Click to collapse
No it was one of those things I bought to support the developer but I never used it. Because like you said[emoji6]
Sent from my Google N6 on VZ
DebianDog said:
No it was one of those things I bought to support the developer but I never used it. Because like you said[emoji6]
Sent from my Google N6 on VZ
Click to expand...
Click to collapse
Bought the app too, in that time we needed it as CM could only be downloaded through Rom Manager. Flashed it with CWM afterwards because RM didn`t work and messed up CWM recovery so i had to reflash it ugh.....
gee2012 said:
Bought the app too, in that time we needed it as CM could only be downloaded through Rom Manager. Flashed it with CWM afterwards because RM didn`t work and messed up CWM recovery so i had to reflash it ugh.....
Click to expand...
Click to collapse
Yes and the good news is those guys are sitting on like 500 million dollars right now so mission accomplished[emoji23]
Sent from my Google N6 on VZ
rootSU said:
I'm never updating my bootloader. At least not until I have to. The 5.1 bootloader is not a friend of anyone racking up their frequent flasher miles.
Click to expand...
Click to collapse
I could have used you guys over in the Wugfresh thread this evening...just endless crazy...
---------- Post added at 09:40 PM ---------- Previous post was at 09:39 PM ----------
simms22 said:
the last time i flashed a bootloader was on the nexus 7, and that was in 2012. i dont flash bootloaders ever, but that n7 original bootloader was broken. im not planning on flashing the n6 bootloader either.
Click to expand...
Click to collapse
Such sage advice...again, the Wugfresh thread needs you...
Related
Hi guys.
I've been having issues with my Atrix lately.
My phone ramdomly looses signal for like 10 seconds and it generates a folder named "bd-dumps" with 3 archives on it: ramdump_modem_fw.bin, ramdump_modem_sw.bin and ramdump_smem.bin.
I didn't changed anything on the phone when the problem started. I was running LiquidSmooth ROM (Very nice, BTW), and started noticing this issue. In fact, I noticed because my phone was lacking memory.
Now, I've been searching about this issue, but none of the solutions have worked for me. Some say is a bad SIM Card, others a bad network, but I am pretty sure that the issue is not about that.
Everytime that I turn on Data services, it happens. When data services are off, it doesn't. I can be using Wi-Fi just fine.
I have tried:
Flashing Stock with RSD Lite
Flashing Stock AT&T and Mexican ROMS
Flashing Stock manually
Flashing modem manually
Flashing several ROMS (CM and AOSP based)
Formatting partitions
Deleting the bd-dumps folder everytime it shows up
Formatting and fixing the modem partition
So far, nothing has worked. I'm attaching a log that I got exactly when this happens and when it gets signal again. Hope anybody can give me a hand.
Thanks, everybody.
Did you try flashing back to stock ATT 4.1.1, taking the OTA update, and testing again?
audit13 said:
Did you try flashing back to stock ATT 4.1.1, taking the OTA update, and testing again?
Click to expand...
Click to collapse
I flashed Stock AT&T 4.1.1 but didn't taked any OTA. Does that updates the modem or some module related? I will try it tonight, thanks for the advice!
mauchito said:
I flashed Stock AT&T 4.1.1 but didn't taked any OTA. Does that updates the modem or some module related? I will try it tonight, thanks for the advice!
Click to expand...
Click to collapse
Yes, there is a modem update included. What it does, I'm not sure. Before taking the update, my wi-fi would drop randomly. I've had solid wi-fi connections since the update. Reception also seems to have improved.
audit13 said:
Yes, there is a modem update included. What it does, I'm not sure. Before taking the update, my wi-fi would drop randomly. I've had solid wi-fi connections since the update. Reception also seems to have improved.
Click to expand...
Click to collapse
Great advice, I really appreciate it. Let me try it tonight and I will share the results. Thanks!
audit13 said:
Did you try flashing back to stock ATT 4.1.1, taking the OTA update, and testing again?
Click to expand...
Click to collapse
I just tried this but there is no OTA available for me. Any ideas? I'm flashing: ATT_MB886_4.1.1-9.8.0Q-97_MB886_FFW-28_CFC_1FF
mauchito said:
I just tried this but there is no OTA available for me. Any ideas? I'm flashing: ATT_MB886_4.1.1-9.8.0Q-97_MB886_FFW-28_CFC_1FF
Click to expand...
Click to collapse
I think that is the latest firmware. The baseband should be mb886_bp_100740.071.65.04p.
This person had a USB issue and got it to work by restoring individual partitions: http://forum.xda-developers.com/showthread.php?t=1813418&page=3
Not sure if that would help.
audit13 said:
I think that is the latest firmware. The baseband should be mb886_bp_100740.071.65.04p.
This person had a USB issue and got it to work by restoring individual partitions: http://forum.xda-developers.com/showthread.php?t=1813418&page=3
Not sure if that would help.
Click to expand...
Click to collapse
That sounds very interesting and useful. I will try it as soon as I get another backup. Thanks!
mauchito said:
That sounds very interesting and useful. I will try it as soon as I get another backup. Thanks!
Click to expand...
Click to collapse
Getting exactly same problem
I also have bp_dumps folder in internal ..
Any body got a fix?
Sent from my ATRIX HD using XDA Premium 4 mobile app
Taha Haq said:
Getting exactly same problem
I also have bp_dumps folder in internal ..
Any body got a fix?
Sent from my ATRIX HD using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Fortunately, yes. Check this post:
http://forum.xda-developers.com/showpost.php?p=54833165&postcount=23
And just flash the modem partition. Then I recommend to go back to Stock and then, if you want, custom ROM. Before I went to stock I had signal issues, but the bd-dumps issue was gone. After flashing Stock, everything worked fine.
Try it, it should work. Don't forget to thank Erick! If you have any issues, let me know.
I didn't understand from erick post may be too complicated for me
Can you please make a guide in the general section for flashing a modem and to do all this . when you have time . it will be helpful for many people.
Sent from my ATRIX HD using XDA Premium 4 mobile app
mauchito said:
Fortunately, yes. Check this post:
http://forum.xda-developers.com/showpost.php?p=54833165&postcount=23
And just flash the modem partition. Then I recommend to go back to Stock and then, if you want, custom ROM. Before I went to stock I had signal issues, but the bd-dumps issue was gone. After flashing Stock, everything worked fine.
Try it, it should work. Don't forget to thank Erick! If you have any issues, let me know.
Click to expand...
Click to collapse
Did you flash Mexican or ATT Stock after flashing the modem partition?
EDIT. I just saw your post on another thread. I flashed the modem partition and then flashed Mexican Stock. Then i installed CM11 but im still having bd-dumps problems. I will try again but with ATT Stock
Taha Haq said:
I didn't understand from erick post may be too complicated for me
Can you please make a guide in the general section for flashing a modem and to do all this . when you have time . it will be helpful for many people.
Sent from my ATRIX HD using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Of course, just don't forget to thank him because he gave the original solution.
Download this (Original link by ErickST18): https://www.dropbox.com/s/a5v8yakw5eshrmc/AHD_Blocks.rar
Use WinRAR to extract the files.
There are 1.img, 2.img, 3.img, etc etc archives. Focus on the 1.img.
Now, like when you flash the recovery on the command line (fastboot flash recovery recovery.img), you will flash this one this way:
fastboot flash modem 1.img
Remember to put the 1.img archive on the same folder that you have the fastboot archive.
And that's it. Reboot, and then flash RSD with Stock. Then with you favorite custom ROM.
Hope it works for you. Please let me know if you need further assistance.
plunplan said:
Did you flash Mexican or ATT Stock after flashing the modem partition?
EDIT. I just saw your post on another thread. I flashed the modem partition and then flashed Mexican Stock. Then i installed CM11 but im still having bd-dumps problems. I will try again but with ATT Stock
Click to expand...
Click to collapse
I just answered in the other thread, but I want to clarify that I used Mexican Stock because my phone is mexican (and I'm too ). If your phone is from AT&T, then I would recommend you to flash that one.
Already thanked him .
And thanks for your help too
Just one thing i need to know that is it neccessary to use rsd or i can use myth tools instead?
Taha Haq said:
Already thanked him .
And thanks for your help too
Just one thing i need to know that is it neccessary to use rsd or i can use myth tools instead?
Click to expand...
Click to collapse
I guess you can use it, I honestly have never tried it, but if you can flash back to Stock with that, go ahead. There shouldn't be any problem.
mauchito said:
I guess you can use it, I honestly have never tried it, but if you can flash back to Stock with that, go ahead. There shouldn't be any problem.
Click to expand...
Click to collapse
i tried your method but after flashing that modem 1.img i got stock in bootloader and this was showing up Fastboot Reason: Flash Failure
then i formatted some patitions and somehow managed to get out of bootloader then i tried flashing different ROM but every ROM gets stuck at bootanimation also the recovery is giving this error E: could not mount /data to setup /data/media path!
any help?
edit: i got my phone working once again by formatting data and data media
Fastboot Atrix HD failure
mauchito said:
Now, like when you flash the recovery on the command line (fastboot flash recovery recovery.img), you will flash this one this way:
fastboot flash modem 1.img
Remember to put the 1.img archive on the same folder that you have the fastboot archive.
And that's it. Reboot, and then flash RSD with Stock. Then with you favorite custom ROM.
Hope it works for you. Please let me know if you need further assistance.
Click to expand...
Click to collapse
Alright, people. I'm a noob here and I tried to do this to fix my Atrix HD modem using this. I hooked my cel in Fastboot mode, checked if it was recognized and all cool. I attempted to flash modem and I got a big fat failure.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Now I'm sutck in a bootloop. I'm not sure what is wrong (I'll say it again, I'm a NOOB)... Maybe I just need to flash something dumb, but I don't know what.
It won't let me flash cdrom from fastboot and I'm running out of battery. It also failed when trying to flash a STOCK ROM (4.1.1) with RSD lite (it got stuck in cdrom as well).
---------- Post added at 01:49 AM ---------- Previous post was at 01:34 AM ----------
Taha Haq said:
edit: i got my phone working once again by formatting data and data media
Click to expand...
Click to collapse
What exactly did you flash and how? I need some help bringing my Atrix back to life.
Double post. Oops.
QuantumCreator said:
Alright, people. I'm a noob here and I tried to do this to fix my Atrix HD modem using this. I hooked my cel in Fastboot mode, checked if it was recognized and all cool. I attempted to flash modem and I got a big fat failure.
Now I'm sutck in a bootloop. I'm not sure what is wrong (I'll say it again, I'm a NOOB)... Maybe I just need to flash something dumb, but I don't know what.
It won't let me flash cdrom from fastboot and I'm running out of battery. It also failed when trying to flash a STOCK ROM (4.1.1) with RSD lite (it got stuck in cdrom as well).
---------- Post added at 01:49 AM ---------- Previous post was at 01:34 AM ----------
What exactly did you flash and how? I need some help bringing my Atrix back to life.
Click to expand...
Click to collapse
Well, first of all, if you are running out of battery, first flash the custom recovery.
fastboot flash recovery recovery.img
I would recommend Philz touch. After this, reboot your phone and enter in recovery presing power + up. Here your phone will charge.
If it doesn't work, try with another fastboot. That could be the issue, too. After you have enough battery, try again to flash RSD Lite to Stock. If it works, then try to flash the partitions. If nothing works, please let me know, let's find a solution
Every time I try to update, my phone downloads it then installs and during the install process my phone stops and tells me it was interrupted.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
BiggaThanLife said:
Every time I try to update, my phone downloads it then installs and during the install process my phone stops and tells me it was interrupted.
Click to expand...
Click to collapse
Your going to have to Odin back to stock NE4, then ota up from their.
If you have/want root then follow this thread....
http://forum.xda-developers.com/showthread.php?t=3083841
I was under the impression I lost my root because I accidentally updated and my SU access would not work anymore.
Edit: the update before lollipop.
BiggaThanLife said:
I was under the impression I lost my root because I accidentally updated and my SU access would not work anymore.
Edit: the update before lollipop.
Click to expand...
Click to collapse
Not a good idea to take OTA updates if your rooted....usually breaks root. The reason it won't update now is due to the fact you were rooted...even if you loose/unroot it still detects traces and the update fails. The only way to OTA now will be to use odin to flash back to stock NE4.
I see from the photo your on NG3 so you can reroot and go from their.
http://forum.xda-developers.com/showthread.php?t=2799754
This and the thread I posted above should have all the info/files you need to get to rooted 5.0.
I appreciate it greatly. I will be taking on that endeavor later on today.
nutt_case said:
Not a good idea to take OTA updates if your rooted....usually breaks root. The reason it won't update now is due to the fact you were rooted...even if you loose/unroot it still detects traces and the update fails. The only way to OTA now will be to use odin to flash back to stock NE4.
I see from the photo your on NG3 so you can reroot and go from their.
http://forum.xda-developers.com/showthread.php?t=2799754
This and the thread I posted above should have all the info/files you need to get to rooted 5.0.
Click to expand...
Click to collapse
I am sorry for being ignorant, it has been a while since I have messed with anything. What do I do first since I have the s5 active variant?
BiggaThanLife said:
I am sorry for being ignorant, it has been a while since I have messed with anything. What do I do first since I have the s5 active variant?
Click to expand...
Click to collapse
Ignorance would be not reading or asking anything until after you brick the phone :sly:
Nothing wrong with asking legit questions, that's what it's all here for:thumbup:
Since your on NG3 now my advice would be to use odin and flash the ne4 stock kernel...then you can use towelroot again...reinstall supersu...then again in odin flash back to the NG3 stock kernel. This will put you on NG3 with root. From their you can follow that top thread and it will put you on stock rooted 5.0.
Edit: Here is another thread for you...OP has all the steps to walk you through rerooting. Just skip the first step about taking the ota and go from their.
http://forum.xda-developers.com/showthread.php?t=3025119
Good luck!
I really appreciate it, when I flash, will that wipe anything on my phone (data, apps, contacts, ect.) Or will it just be the firmware that is changed?
BiggaThanLife said:
I really appreciate it, when I flash, will that wipe anything on my phone (data, apps, contacts, ect.) Or will it just be the firmware that is changed?
Click to expand...
Click to collapse
Flashing the kernels to root shouldn't delete any data, but the jump to 5.0 will. I'd strongly recommend backing up first just to be safe.
nutt_case said:
Flashing the kernels to root shouldn't delete any data, but the jump to 5.0 will. I'd strongly recommend backing up first just to be safe.
Click to expand...
Click to collapse
I'm pretty sure it's already backed up to my Gmail, but I'll do a manual onto my computer. Now I am debating on just flashing to keep my root cause I don't want to go to 5 and I lose it again.
BiggaThanLife said:
I'm pretty sure it's already backed up to my Gmail, but I'll do a manual onto my computer. Now I am debating on just flashing to keep my root cause I don't want to go to 5 and I lose it again.
Click to expand...
Click to collapse
When your done, just make sure to freeze the Att software update app with titanium or similar, that will kill OTA so you don't have to worry about them sneaking an update in.
nutt_case said:
When your done, just make sure to freeze the Att software update app with titanium or similar, that will kill OTA so you don't have to worry about them sneaking an update in.
Click to expand...
Click to collapse
I need a refresher on the terminology again, like sideload and OT4 or what ever. Lol where do you suggest I glance through.
BiggaThanLife said:
I need a refresher on the terminology again, like sideload and OT4 or what ever. Lol where do you suggest I glance through.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2697270
This one is a general guide for the g900a...not quite the same as the active, but the terminology still applies.
Just Google "guide to android terminology" and you'll end up with more info than you ever wanted! :sly:
nutt_case said:
http://forum.xda-developers.com/showthread.php?t=2697270
This one is a general guide for the g900a...not quite the same as the active, but the terminology still applies.
Just Google "guide to android terminology" and you'll end up with more info than you ever wanted! :sly:
Click to expand...
Click to collapse
Is there a way to back up my phone 100% before I go ahead and try rerooting?
BiggaThanLife said:
Is there a way to back up my phone 100% before I go ahead and try rerooting?
Click to expand...
Click to collapse
Helium is pretty good.
Kies does everything except app data.
nutt_case said:
Helium is pretty good.
Kies does everything except app data.
Click to expand...
Click to collapse
So good news, I re-rooted after a couple hours of research and I am rooted on 4.4.2. Now all I have to do is flash up to 5.0?
BiggaThanLife said:
So good news, I re-rooted after a couple hours of research and I am rooted on 4.4.2. Now all I have to do is flash up to 5.0?
Click to expand...
Click to collapse
Yes, as long as you have root you can flash straight to rooted 5.0. :thumbup:
nutt_case said:
Yes, as long as you have root you can flash straight to rooted 5.0. :thumbup:
Click to expand...
Click to collapse
And flashing 5.0 is the SAME process? Lol if so I will be okay. Do you suggest any other root apps? I had flashify, but I was nervous and deleted it before I go stuck in a boot loop. Lmfao
BiggaThanLife said:
And flashing 5.0 is the SAME process? Lol if so I will be okay. Do you suggest any other root apps? I had flashify, but I was nervous and deleted it before I go stuck in a boot loop. Lmfao
Click to expand...
Click to collapse
It's not exactly the same, but not hard....
http://forum.xda-developers.com/showthread.php?t=3083841
Just follow the steps in the op and you'll be fine.
You'll need FlashFire, and I'd recommend TiBu...Good for freezing/removing bloat and backing up app data.
Hi, I hope I post this in the right place. Anyway, as the title suggests, I want to get back stock recovery on my Nexus 6 without getting back the entire system image. I currently have TWRP as a recovery and I want to be able to receive OTA updates but I would need to uninstall BusyBox, which TWRP uses. The only thing that is 'custom' right now is the recovery and that's all I want to replace because I've heard that if I flash the entire system image, I lose data. I haven't been successful in finding the exact guide or support I need so I am posting my own thread. Sorry if it's in the wrong place.
You would download the stock image, extract recovery.img from that, boot phone into the bootloader and using a computer with the Android SDK installed, use the command fastboot to flash the recovery, so: fastboot flash recovery recovery.img
There's guides here on how to do this.
RMarkwald said:
You would download the stock image, extract recovery.img from that, boot phone into the bootloader and using a computer with the Android SDK installed, use the command fastboot to flash the recovery, so: fastboot flash recovery recovery.img
There's guides here on how to do this.
Click to expand...
Click to collapse
I have Android SDK but I have no idea how to do it. I don't suppose you have a link? If not, it's alright. Thank you for the quick response.
I have found guides on how to do it, but I can't get them to work. Haven't seen one using Android SDK.
Are you rooted?
Sent from my Nexus 6 using Tapatalk
---------- Post added at 07:51 AM ---------- Previous post was at 07:47 AM ----------
Gotta be with busy box, twrp. Flashifly should do the job. Strangely I've go a update alert on stock rooted ROM with twrp.
Official Team Bliss Flo/Deb/v410 Maintainer
Sent from my Nexus 6 using Tapatalk
713brianp27 said:
Are you rooted?
Sent from my Nexus 6 using Tapatalk
---------- Post added at 07:51 AM ---------- Previous post was at 07:47 AM ----------
Gotta be with busy box, twrp. Flashifly should do the job. Strangely I've go a update alert on stock rooted ROM with twrp.
Official Team Bliss Flo/Deb/v410 Maintainer
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
Yes I am.
So, I flashed the stock recovery of Android 5.0.1 and when I try to boot into recovery, I get an Android laying down, chest open with a red caution sign. I think I may have downloaded the wrong version. I probably have Android 5.1 not 5.0.1
Flashifly app does fine job on boot&recovery. Don't see the need for fastboot. Hate wiring up to a computer just for an image. It'll flash it then boot you to it. Bam done
Sent from my Nexus 6 using Tapatalk
You'll not be able to flash teh update because youa re rooted. You will need to flash recovery.img and system.img and boot.img to get back to 100% stock. You will recieve OTA then, though you may aswell download latest version now so no need to update.
---------- Post added at 03:59 PM ---------- Previous post was at 03:58 PM ----------
713brianp27 said:
Flashifly app does fine job on boot&recovery. Don't see the need for fastboot. Hate wiring up to a computer just for an image. It'll flash it then boot you to it. Bam done
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
Flashify doesn't flash system.images. You need to do that to flash back to stock.
Flashifly most certainly does. Exactly where is your info coming from.
Sent from my Nexus 6 using Tapatalk
---------- Post added at 09:07 AM ---------- Previous post was at 09:07 AM ----------
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my Nexus 6 using Tapatalk
713brianp27 said:
Flashifly most certainly does. Exactly where is your info coming from.
Sent from my Nexus 6 using Tapatalk
---------- Post added at 09:07 AM ---------- Previous post was at 09:07 AM ----------
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
My info is coming from the fact I have flashify installed for many yars and now it is also coming from your screenshot, which also confirms it cannot flash system images.
Screen shows two images?! Your boot and recovery ARE images. What is the point of the app otherwise?
http://highonandroid.com/android-ap...n-rooted-android-with-flashify-app-root-apps/
Sent from my Nexus 6 using Tapatalk
713brianp27 said:
Screen shows two images?! Your boot and recovery ARE images. What is the point of the app otherwise?
http://highonandroid.com/android-ap...n-rooted-android-with-flashify-app-root-apps/
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
#
I think you're misreading my post. I didn't say it cannot flash images. I said it cannot flash System Images.
danarama said:
#
I think you're misreading my post. I didn't say it cannot flash images. I said it cannot flash System Images.
Click to expand...
Click to collapse
I never said it could flash the system.img
The thread is about recovery. Cut and dry. You bring in a fact I'm aware of. But no one is talking about the system.img . it would be system image, not system images which could confuse , using it plural implies reference to images in the system (partition). Anyway. You can flash your stock recovery.img with app. Thread question solved. And folks he's right, can't flash system image.
Sent from my Nexus 6 using Tapatalk
713brianp27 said:
I never said it could flash the system.img
The thread is about recovery. Cut and dry.
Click to expand...
Click to collapse
No it is not. Read between the lines. The thread is about being able to accept OTA updates. Flashing stock recovery is what the OP has guessed is required to do this (he is wrong)
713brianp27 said:
You bring in a fact I'm aware of.
Click to expand...
Click to collapse
Really? I said it cannot flash system images twice and you still said it could. Maybe you are aware of it, but your reading misses things. I'll give you the benefit of the doubt.
713brianp27 said:
But no one is talking about the system.img
Click to expand...
Click to collapse
I AM!!! Because that is the resolution to this thread.
713brianp27 said:
it would be system image, not system images which could confuse , using it plural implies reference to images in the system (partition).
Click to expand...
Click to collapse
What, you flash one image and then it explodes, so you can't flash any more? You can flash multiple recovery images. I use plural because the English language allows for it. And Yes, System images are the System partition. Not sure I'm grasping your point.
713brianp27 said:
Anyway. You can flash your stock recovery.img with app
Click to expand...
Click to collapse
Great! Though no help here.
713brianp27 said:
Thread question solved.
Click to expand...
Click to collapse
Yes, by using fastboot, which was why I posted about flashify not being able to flash system images. "Don't see a need for fastboot" - Well, there is a need.
Thread title"Getting back stock recovery". Easy. Answered. She want the ota. Not a system.img. Yhey get recovery. Should they get an alert. OTA.
Here is my point. 1) what's the title, answered.
2)you bring up "can't ..." When NOBODY EVER said flash system.img with any app, fastboot, or any other means. Intent is get it via carrier download---
3) How in the world of reality do you flash something that is coming through the carrier update push , as far as I know they don't leave a copy behind
4) Stick to topic. Title... Simple. I can flash stock recovery now, and reflash twrp. So why the "need". Why bring up system image(s). Which can be packaged and flashed in custom recovery. I've got an ota notice running stock root so the only thing I would of lacked was ... Yes correct recovery
I apologize for entertaining and debating. I am going to make an exit. Good day
Sent from my Nexus 6 using Tapatalk
713brianp27 said:
Thread title"Getting back stock recovery". Easy. Answered. She want the ota. Not a system.img. Yhey get recovery. Should they get an alert. OTA.
Here is my point. 1) what's the title, answered.
2)you bring up "can't ..." When NOBODY EVER said flash system.img with any app, fastboot, or any other means. Intent is get it via carrier download---
3) How in the world of reality do you flash something that is coming through the carrier update push , as far as I know they don't leave a copy behind
4) Stick to topic. Title... Simple. I can flash stock recovery now, and reflash twrp. So why the "need". Why bring up system image(s). Which can be packaged and flashed in custom recovery. I've got an ota notice running stock root so the only thing I would of lacked was ... Yes correct recovery
I apologize for entertaining and debating. I am going to make an exit. Good day
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
Look, all I wanted to do was help the OP get what they want and identify the need for using fastboot.
The fact that you either didn't read the thread properly or don't have the technical understanding of OTA to answer the question effectively is of no concern. You can argue what you want, but flashify won't help here. Reading the title of a thread is not enough, you should read the full opening post first. You can be forgiven for not having the technical understanding needed to resolve the issue. But you shouldn't keep going on when someone points out that your answer won't help.
In regards to your very last point. Getting notification is not the same as getting the ota. Yes you need stock recovery, but also you must have 100% stock android. No root. Must be never rooted.. I can tell you're a noob by not knowing this and again, that is fine. What is not fine though, is your attitude and refusing to believe you are wrong. It's not the first time you've been like this either. I've seen it before.. I don't really care what you think you know though to be honest.
@Prowler1000, the *ONLY* way you will successfully get an OTA officially in the future is by flashing the system.img first.
You cannot simply have a stock recovery or use any other unroot methods. You must have a clean, untouched rom and kernel, never rooted.. Any change, even if just one letter in a text file of the rom will be enough to make the official OTA flash fail, this i promise you. This is why you must flash a system.image.
Actually on a ROM I built in buildbox. And know my way around. But think what you want. Said bye once. Troll on. Your blocked so I hear no more
Sent from my Nexus 6 using Tapatalk
713brianp27 said:
Actually on a ROM I built in buildbox. And know my way around. But think what you want. Said bye once. Troll on. Your blocked so I hear no more
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
Haha. You're priceless. Luckily, anyone reading this thread will see your true qualities.
danarama said:
No it is not. Read between the lines. The thread is about being able to accept OTA updates. Flashing stock recovery is what the OP has guessed is required to do this (he is wrong)
Click to expand...
Click to collapse
No, I just needed to get rid of TWRP so I could get rid of BusyBox. That is all.
Edit: I was hoping by getting rid of BusyBox, I could update without having to flash a system.img so that I don't have to wipe my phone. But I guess that is out of the picture. I will just flash M, rather then waiting for the OTA.
Prowler1000 said:
No, I just needed to get rid of TWRP so I could get rid of BusyBox. That is all.
Edit: I was hoping by getting rid of BusyBox, I could update without having to flash a system.img so that I don't have to wipe my phone. But I guess that is out of the picture. I will just flash M, rather then waiting for the OTA.
Click to expand...
Click to collapse
What you are saying is you want to get rid of TWRP so you can get rid of busybox (TWRP does not need busybox by the way) and that getting rid of busy box will enable you to get an Update.
What I am saying is that is not enough. Root is preventing you getting the update. You *must* flash the system.img to clean your ROM to be able to accept future updates.
However, for info, flashing a system.img does NOT wipe your phone. system.img goes in the /system partition only. It is the ROM. all your data is in the data partition. If you just flash the system.img, recovery.img and boot.img, you will be stock enough to take updates in the future. If you flash the full factory image (which includes all the indivudual images I mentioned, plus cache.img, userdata.img, radio.img, bootloader.img) then that WILL wipe your phone, but you do not need to do that.
If your plan is to stay rooted in the future, the best thing is to keep TWRP and just flash the system.img and boot.img when you ware ready to update. OTA's are more hassle than benefit anyway, and you cant take them if you want to stay rooted. But once rooted on a stock rom, you can never unroot without flashign that system.img (at least not to the point where an OTA will flash successfully
danarama said:
What you are saying is you want to get rid of TWRP so you can get rid of busybox (TWRP does not need busybox by the way) and that getting rid of busy box will enable you to get an Update.
What I am saying is that is not enough. Root is preventing you getting the update. You *must* flash the system.img to clean your ROM to be able to accept future updates.
However, for info, flashing a system.img does NOT wipe your phone. system.img goes in the /system partition only. It is the ROM. all your data is in the data partition. If you just flash the system.img, recovery.img and boot.img, you will be stock enough to take updates in the future. If you flash the full factory image (which includes all the indivudual images I mentioned, plus cache.img, userdata.img, radio.img, bootloader.img) then that WILL wipe your phone, but you do not need to do that.
If your plan is to stay rooted in the future, the best thing is to keep TWRP and just flash the system.img and boot.img when you ware ready to update. OTA's are more hassle than benefit anyway, and you cant take them if you want to stay rooted. But once rooted on a stock rom, you can never unroot without flashign that system.img (at least not to the point where an OTA will flash successfully
Click to expand...
Click to collapse
But I can manually flash the new update, right?
Hi so I've spent a good deal of the morning attempting to finally fix this phone, a couple years ago I removed all OS from it and no backup but I still have TWRP.
The phone is tampered/unlocked.
Hboot is 1.54.0000
I tried loading one of the latest ROMS from here via side loading - http://forum.xda-developers.com/htc-one/general/lollipop-ruu-zip-small-collection-t3053944
I used this guide - http://htc-one.wonderhowto.com/how-to/fix-soft-bricked-htc-one-by-flashing-new-rom-via-adb-0154361/
Unfortunately once the sideload is complete I get an error E: Zio file is corrupt, I was wondering if anyone knows what I'm doing wrong? Can attempt to provide more information if required.
Purdy8TV said:
Hi so I've spent a good deal of the morning attempting to finally fix this phone, a couple years ago I removed all OS from it and no backup but I still have TWRP.
The phone is tampered/unlocked.
Hboot is 1.54.0000
I tried loading one of the latest ROMS from here via side loading - http://forum.xda-developers.com/htc-one/general/lollipop-ruu-zip-small-collection-t3053944
I used this guide - http://htc-one.wonderhowto.com/how-to/fix-soft-bricked-htc-one-by-flashing-new-rom-via-adb-0154361/
Unfortunately once the sideload is complete I get an error E: Zio file is corrupt, I was wondering if anyone knows what I'm doing wrong? Can attempt to provide more information if required.
Click to expand...
Click to collapse
What recovery version do you have? Try flashing newest TWRP and give it a go
donkeykong1 said:
What recovery version do you have? Try flashing newest TWRP and give it a go
Click to expand...
Click to collapse
Hey thanks for the reply
This is the ROM I downloaded https://www.androidfilehost.com/?fid=95916177934554130
My recovery version is v2.6.0.1 for TWRP, should I upgrade?
You can't flash that via recovery. That's a RUU, and your phone must be in RUU mode and you flash it via recovery. Also, you're on very old firmware, so you need to flash all firmwares before that one. My suggestikn is to flash the latest recovery, and then flash a custom ROM. You can find custom ROMs on M7 android development thread
donkeykong1 said:
You can't flash that via recovery. That's a RUU, and your phone must be in RUU mode and you flash it via recovery. Also, you're on very old firmware, so you need to flash all firmwares before that one. My suggestikn is to flash the latest recovery, and then flash a custom ROM. You can find custom ROMs on M7 android development thread
Click to expand...
Click to collapse
Ah that would explain it lol, sadly very inexperienced with this.
Would there be a stock rom or just choose the one close to stock? (As in HTC sense one)
Purdy8TV said:
Ah that would explain it lol, sadly very inexperienced with this.
Would there be a stock rom or just choose the one close to stock? (As in HTC sense one)
Click to expand...
Click to collapse
I think there should be a stock rooted ROM, but you can flash pretty much any ROM from there. Most of them are stockish looking
donkeykong1 said:
I think there should be a stock rooted ROM, but you can flash pretty much any ROM from there. Most of them are stockish looking
Click to expand...
Click to collapse
Hey thanks very much for your speedy replies
Would this be okay then - http://forum.xda-developers.com/htc-one/development/rom-google-play-edition-lollipop-v1-00-t2963927 ?
Also do I just sideload it as I attempted previously once TWRP is updated?
Purdy8TV said:
Hey thanks very much for your speedy replies
Would this be okay then - http://forum.xda-developers.com/htc-one/development/rom-google-play-edition-lollipop-v1-00-t2963927 ?
Also do I just sideload it as I attempted previously once TWRP is updated?
Click to expand...
Click to collapse
Of all sense TOMs out there, you picked a GPE [emoji4] that's not Sense, but it will work.
New recoveries have MTP option, so you don't need sideload. Just mount MTP, and move your zip to your phone
donkeykong1 said:
Of all sense TOMs out there, you picked a GPE [emoji4] that's not Sense, but it will work.
New recoveries have MTP option, so you don't need sideload. Just mount MTP, and move your zip to your phone
Click to expand...
Click to collapse
Haha yeah, I did decide I actually preferred closer to stock android after using my Z3
I don't really know how to do that, will side loading still be okay? (I assumed this was my only option as I literally have no OS on my phone and just get stuck at the HTC loading screen when I turn phone on normally)
Purdy8TV said:
Haha yeah, I did decide I actually preferred closer to stock android after using my Z3
I don't really know how to do that, will side loading still be okay? (I assumed this was my only option as I literally have no OS on my phone and just get stuck at the HTC loading screen when I turn phone on normally)
Click to expand...
Click to collapse
MTP is much easier than sideload, and newer TWRP have it. You go into recovery (updated) and you will see "mount MTP" option. Click that, and your phone will show up on your PC. After that it's just drag and drop, but sideload will work too I think
donkeykong1 said:
MTP is much easier than sideload, and newer TWRP have it. You go into recovery (updated) and you will see "mount MTP" option. Click that, and your phone will show up on your PC. After that it's just drag and drop, but sideload will work too I think
Click to expand...
Click to collapse
Hmm
I can just see 'Mount' on the main TWRP page, then I go into that and see Cache/Data/devlog/System/USB OTG as check boxes and then just disable MTP button at the bottom.
Nothing showing on my macbook (not sure if that makes a difference as my w10 pc could not recognise the phone at all)
Purdy8TV said:
Hmm
I can just see 'Mount' on the main TWRP page, then I go into that and see Cache/Data/devlog/System/USB OTG as check boxes and then just disable MTP button at the bottom.
Nothing showing on my macbook (not sure if that makes a difference as my w10 pc could not recognise the phone at all)
Click to expand...
Click to collapse
Disable MTP is the one. Click it twice, and you're good to go
donkeykong1 said:
Disable MTP is the one. Click it twice, and you're good to go
Click to expand...
Click to collapse
Not showing up as a removable storage
Purdy8TV said:
Not showing up as a removable storage
Click to expand...
Click to collapse
Weird... Then go with sideload
donkeykong1 said:
Weird... Then go with sideload
Click to expand...
Click to collapse
Okay so I tried side loading, downloaded the google plus ROM from the link I posted, zipped it up and ended up getting this error.
Purdy8TV said:
Okay so I tried side loading, downloaded the google plus ROM from the link I posted, zipped it up and ended up getting this error.
Click to expand...
Click to collapse
That error means your adb tool is not working properly. At least that was the case on my PC. Can you try it on your windows machine?
donkeykong1 said:
That error means your adb tool is not working properly. At least that was the case on my PC. Can you try it on your windows machine?
Click to expand...
Click to collapse
Yeah I'll go give it another go on it.
It wouldn't be anything to do with the fact my device is tampered? (S Off I think?) Do I need something extra other than just the one link in the ROM I said i chose?
Purdy8TV said:
Yeah I'll go give it another go on it.
It wouldn't be anything to do with the fact my device is tampered? (S Off I think?) Do I need something extra other than just the one link in the ROM I said i chose?
Click to expand...
Click to collapse
You're s-off??? Go to your bootlader and confirm that please
donkeykong1 said:
You're s-off??? Go to your bootlader and confirm that please
Click to expand...
Click to collapse
Talking out my arse I'm S-ON lol, thought tampered meant S OFF lol, apologies
donkeykong1 said:
You're s-off??? Go to your bootlader and confirm that please
Click to expand...
Click to collapse
Okay so windows can detect the device it seems!
I see this, do I just delete the sideload.zip and then drag and drop the ROM I downloaded ?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Hi everyone. Apparently I know just enough to get me in trouble. I received my new OnePlus 10 Pro 5G yesterday which I ordered thinking OnePlus phone were easy to root and mod. I was able to get the boot loader unlocked eventually, but then when I tried to root the phone I ended up in a boot loop. I can still get into to fastboot, lock and unlock my boot loader, but I can't get it to boot.
I found a rollback file for North America and was hoping to hopefully save my new phone by reflashing it.
Sorry for inexperience, I'm hoping there is a guide to doing this. I've been looking for hours
Thanks,
KB
For rooting our device we can use This guide, i don't know which model is you device but probably you can use the files provided there.
Now to solve your problem you need a stock boot.img file that match your current system version and flash it via fastboot
you are kind of sol. keep watching this thread and hopefully someone will post new login creds https://forum.xda-developers.com/t/edl-flash-tool-leak.4494211/
g96818 said:
you are kind of sol. keep watching this thread and hopefully someone will post new login creds https://forum.xda-developers.com/t/edl-flash-tool-leak.4494211/
Click to expand...
Click to collapse
That is what I was afraid of. I saw this thread before asking for help. There is just so much to sort through and hard to know
RokCruz said:
For rooting our device we can use This guide, i don't know which model is you device but probably you can use the files provided there.
Now to solve your problem you need a stock boot.img file that match your current system version and flash it via fastboot
Click to expand...
Click to collapse
My model is the NE2215. I found this rooting guide after following a bad rooting guide. I think the main difference is that the other one had me flash the patched boot.ini file and not boot from that file.
As far as stock boot image, I thought I found one in this thread https://community.oneplus.com/thread/1114712420498538501 for the Android 13 beta. It has a rollback package to revert to 12.
KB- said:
That is what I was afraid of. I saw this thread before asking for help. There is just so much to sort through and hard to know
My model is the NE2215. I found this rooting guide after following a bad rooting guide. I think the main difference is that the other one had me flash the patched boot.ini file and not boot from that file.
As far as stock boot image, I thought I found one in this thread https://community.oneplus.com/thread/1114712420498538501 for the Android 13 beta. It has a rollback package to revert to 12.
Click to expand...
Click to collapse
So you are on global ROM, do you remember which version? If it's the lastest version(NE2215_11_C.21) I can provide you with the stock boot.img
RokCruz said:
So you are on global ROM, do you remember which version? If it's the lastest version(NE2215_11_C.21) I can provide you with the stock boot
Click to expand...
Click to collapse
I had the August update I believe. It was the latest update.
KB- said:
That is what I was afraid of. I saw this thread before asking for help. There is just so much to sort through and hard to know
My model is the NE2215. I found this rooting guide after following a bad rooting guide. I think the main difference is that the other one had me flash the patched boot.ini file and not boot from that file.
As far as stock boot image, I thought I found one in this thread https://community.oneplus.com/thread/1114712420498538501 for the Android 13 beta. It has a rollback package to revert to 12.
Click to expand...
Click to collapse
Don’t know which version you’re on, but it’s best to follow the right guide for your model https://forum.xda-developers.com/t/oneplus-10-pro-ne2215-rooted.4431585/
All the stock boot files are there. Recommend you try booting each one until you find one that works, then validate your phone os version and flash the correct boot image.
May or may not work depending on your luck
KB- said:
I had the August update I believe. It was the latest update.
Click to expand...
Click to collapse
g96818 said:
Don’t know which version you’re on, but it’s best to follow the right guide for your model https://forum.xda-developers.com/t/oneplus-10-pro-ne2215-rooted.4431585/
All the stock boot files are there. Recommend you try booting each one until you find one that works, then validate your phone os version and flash the correct boot image.
May or may not work depending on your luck
Click to expand...
Click to collapse
As said here, download the stock boot from there and only boot it, it your device boots then flash that boot.img on fastboot or fastbootenhace
KB- said:
I had the August update I believe. It was the latest update.
Click to expand...
Click to collapse
I'm sorry, when you say version, I was assuming you meant which software update I had. Which version am I looking for?
RokCruz said:
As said here, download the stock boot from there and only boot it, it your device boots then flash that boot.img on fastboot or fastbootenhace
Click to expand...
Click to collapse
Sorry if these are dumb questions but I just want to make sure I'm doing it right.
I have downloaded both the global (6812ccee9a8a891032af1e053e3217731ac7ad92) and North American versions (2370_sign_NE2215_11_A_OTA_0130_all_bb1e47_10100001)
I have extracted them so I have the boot.img files as well. So you're saying I should run 'fastboot boot boot.img' and if it works, then I should do 'fastboot flash boot.img'?
KB- said:
Sorry if these are dumb questions but I just want to make sure I'm doing it right.
I have downloaded both the global (6812ccee9a8a891032af1e053e3217731ac7ad92) and North American versions (2370_sign_NE2215_11_A_OTA_0130_all_bb1e47_10100001)
I have extracted them so I have the boot.img files as well. So you're saying I should run 'fastboot boot boot.img' and if it works, then I should do 'fastboot flash boot.img'?
Click to expand...
Click to collapse
Yep that should be the procedure, the important thing is if that version match the current installed in your device, do you remember which android version you had? A13? A12?
RokCruz said:
Yep that should be the procedure, the important thing is if that version match the current installed in your device, do you remember which android version you had? A13? A12?
Click to expand...
Click to collapse
I don't know what version I had. I just tried to boot off both boot.img and both failed.
KB- said:
I don't know what version I had. I just tried to boot off both boot.img and both failed.
Click to expand...
Click to collapse
Quick settings look like this? How many updates did you installed?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
RokCruz said:
Quick settings look like this? How many updates did you installed?
View attachment 5767207
Click to expand...
Click to collapse
I can't get into my phone at all other than the fastboot screen.
KB- said:
I can't get into my phone at all other than the fastboot screen.
Click to expand...
Click to collapse
Yeah I know that but you almost see Q's once, anyway the only way that comes to my mind is flashing the full ROM via fastboot enhance for you device that should be NE2215_11_C21(Android 13)
For now i didn't used that tool, i upgraded my device via local update so I can't help with that
KB- said:
I can't get into my phone at all other than the fastboot screen.
Click to expand...
Click to collapse
RokCruz said:
Yeah I know that but you almost see Q's once, anyway the only way that comes to my mind is flashing the full ROM via fastboot enhance for you device that should be NE2215_11_C21(Android 13)
For now i didn't used that tool, i upgraded my device via local update so I can't help with that
Click to expand...
Click to collapse
Thank you for all your help. I think I've done about all I know how to do. I guess I'll just take it as an expensive lesson learned and hope that there is a way to do it in the future.
RokCruz said:
Yeah I know that but you almost see Q's once, anyway the only way that comes to my mind is flashing the full ROM via fastboot enhance for you device that should be NE2215_11_C21(Android 13)
For now i didn't used that tool, i upgraded my device via local update so I can't help with that
Click to expand...
Click to collapse
I've flashed a full firmware via Fastboot enhance after I installed a GSI..
I connected when in fastboot..
Deleted cow files, need to search then delete each one, then grabbed my most current full firmware payload.bin and flashed it.
Device booted fine, one part of it I need to be in Fastboot d, I think that was the cow files part. I could be remembering that part wrong though.
dladz said:
I've flashed a full firmware via Fastboot enhance after I installed a GSI..
I connected when in fastboot..
Deleted cow files, need to search then delete each one, then grabbed my most current full firmware payload.bin and flashed it.
Device booted fine, one part of it I need to be in Fastboot d, I think that was the cow files part. I could be remembering that part wrong though.
Click to expand...
Click to collapse
@KB- that should fix your issue.
@dladz I guess the patched boot.img needs to be flashed in fastbootd instead bootloader? to avoid bootloops anyway better to just boot it.
RokCruz said:
@KB- that should fix your issue.
@dladz I guess the patched boot.img needs to be flashed in fastbootd instead bootloader? to avoid bootloops anyway better to just boot it.
Click to expand...
Click to collapse
If it's within a payload then no it's integrity is intact.
If it's been extracted to be patched then yes booting is preferred, but there's no option in Fastboot enhance for that.
RokCruz said:
@KB- that should fix your issue.
@dladz I guess the patched boot.img needs to be flashed in fastbootd instead bootloader? to avoid bootloops anyway better to just boot it.
Click to expand...
Click to collapse
Thank you for the advice. Is there a tutorial on how to do all this? I feel like I'm just making it worse since I don't know enough