Database Develop

[ROM]Stock JDQ39E flashable zip

Introduction:
This is an update zip containing stock JDQ39E, it is as close to stock as possible.
It also includes the M9615A-CEFWMAZM-2.0.1700.54 radio associated with JDQ39E
It should be close enough to be able to get OTAs when something beyond JDQ39E is released for the N4.
It is NOT rooted or modified in any way, this is as close to what you would expect from an actual google release as possible
It does not include /system/etc/install-recovery.sh as that is never included in preinstalled roms.
Click to expand...
Click to collapse
Requirements:
Fastboot unlocked
A custom recovery, it CANNOT be flashed with the stock recovery
Strongly recommended: Bootloader MAKOZ10o installed beforehand, this update zip does not include a bootloader
Click to expand...
Click to collapse
ROM Details
Build: JDQ39E
Build number: 610897
Build Date: Mar. 20, 2012
Tag: android-4.2.2_r1.2
Kernel:
Code:
[email protected] #1 Tue Mar 12 15:50:26 PDT 2013
Bootloader: MAKOZ10o
Radio: M9615A-CEFWMAZM-2.0.1700.54
Click to expand...
Click to collapse
Instructions:
Unlock device bootloader
STRONGLY RECOMMENDED: Flash MAKOZ10o
Download: update-N4-Stock-JDQ39E-1.zip
Flash or boot preferred custom recovery
Flash update zip with preferred method of flashing update zips
OPTIONAL: Root rom
OPTIONAL: Relock bootloader
Click to expand...
Click to collapse
Warnings:
It is NOT rooted
The stock JDQ39E recovery is included and automatically flashed alongside the rom
As with JDQ39, LTE is not expected to work without modifications
While it MAY be possible to OTA beyond JDQ39E, it is still STRONGLY RECOMMENDED to use an official google factory image when an update comes out
Click to expand...
Click to collapse
Changelog:
May 29, 2013: Initial Release
Click to expand...
Click to collapse
Credits:
Base rom: Google
Radio.img dump: eRajesh
System.img / bootloader.img dump: _Behemoth
Recovery.img dump: [xubz]
Click to expand...
Click to collapse
2char

Hasn't the JDQ39E code been pushed by Google.. awhile back?
http://www.androidpolice.com/2013/0...e-4-2-2_r1-2-here-is-the-developer-changelog/
Also, theres not really much new in JDQ39E, with 4.3 around the corner I don't really see the point for dumping 4.2.2_r1.2?
Unless I'm missing something...

Code yes, rom no.
We didnt get a good JOP40G dump until long after JDQ39 came out, and that was mainly due to the fact a tot exists.
Someone needs to dump it before an update comes out and it's lost to time, there's no guarantee that a tot will ever exist for JDQ39E

A dump of a newer OS version is always welcomed :thumbup:

Since I've already installed a custom kernel (faux123) and rooted. I can only contribute the stock recovery.
(Why oh why didn't I think of a Nandroid backup first. *bangs head on wall*)
Download link for recovery.img (from Stock Indian JDQ39E ROM): http://d-h.st/VHq (MD5Sum of recovery.img: 6300763a32d037cb5a3bdd307bcba4aa)

If you rooted, but know that you didnt do anything else to modify /system: it's likely still good.
I would still appreciate an additional dump of the recovery regardless, it would help to be sure we have a good dump.
Same with the radio, it couldnt hurt.
To dump radio/recovery:
Code:
dd if=/dev/block/platform/msm_sdcc.1/by-name/<image> of=/system/<image>.img
where <image> is any one of:
recovery
modem
The rest should be done with nandroid
--------------------------------------------------------------------------------------
Edit: I am fairly certian that the recovery provided is a good dump, but I still would welcome a repeat of both the rec and modem to be confirmed

I have made a nandroid of JDQ39E after rooting and installing TWRP. Will it work for your cause? As you know from another thread I do have a 7 day old black nexus 4 with JDQ39E.
I have attached a screenshot of my nandroid backup. What all files do you need? I'm guessing the 1st two and last two?

How did you root, did you just flash supersu/superuser/something.zip?
As long as you didnt end up modifying boot.img, it should be ok that it's rooted.
what i need is boot / system / recovery.
Could I ask if you could redump them with CWM and in tar mode (i think this is the default)
I'm guessing that wins will work, but I'm a lot more comfortable with tars.
Also I plan on making a "stock" update zip with these once i have them, we're almost there

TheManii said:
How did you root, did you just flash supersu/superuser/something.zip?
As long as you didnt end up modifying boot.img, it should be ok that it's rooted.
what i need is boot / system / recovery.
Could I ask if you could redump them with CWM and in tar mode (i think this is the default)
I'm guessing that wins will work, but I'm a lot more comfortable with tars.
Also I plan on making a "stock" update zip with these once i have them, we're almost there
Click to expand...
Click to collapse
I rooted and installed TWRP using WugFresh's NRT 1.6.3.

Yea the root method seems to be fine,
I'd prefer tars but wins are ok if you dont wish to re-backup them as tars.

Here is the boot image -
boot.emmc.win - http://d-h.st/qdR
boot.emmc.win.md5 - http://d-h.st/tAV
Uploading the system image now.

Here is the system image -
system.ext4.win - http://d-h.st/klw
system.ext4.win.md5 - http://d-h.st/vsQ

If anyone can get the stock dump with CWM (I prefer it to TWRP) I'd appreciate it - NOT rooted

@Behemoth.
Any info on how to flash this to the device. Even i had the JDQ39E image when i bought this phone last week in India. But flashed it with a different image so now on JDQ39.

this is getting intereting

rajesheber said:
@Behemoth.
Any info on how to flash this to the device. Even i had the JDQ39E image when i bought this phone last week in India. But flashed it with a different image so now on JDQ39.
Click to expand...
Click to collapse
Absolutely no idea man! The pro's could help better.

If we had the .img files instead of .win you can use the flash-all.bat tool to flash via fastboot

immunityx said:
If we had the .img files instead of .win you can use the flash-all.bat tool to flash via fastboot
Click to expand...
Click to collapse
Exactly this. Surely someone just needs to unlock the bootloader and pulls the files manually?
Sent from my Nexus 4 using xda premium

EddyOS said:
Exactly this. Surely someone just needs to unlock the bootloader and pulls the files manually?
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
Yup for example for the system img the following command would work
Code:
adb pull /system system.img
---------- Post added at 06:37 PM ---------- Previous post was at 06:35 PM ----------
Im currently at work can someone trying renaming the .win to .tar and exact the .tar file in winrar or some tool similar.. i believe the .img files are in there

{
"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"
}
I'm almost done building an update zip, still testing it
You can just nandroid it with TWRP, but i'd much prefer an update zip over that

Crashing Modem

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

Getting back stock recovery

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?

Help installing custom rom

Hey guys,
I am trying to intall a custom rom on my blu vivo xl. My worries are that i either soft-brick the phone or boot the new rom and having no signal due to no imei, or no 4G due to band change if it's even possible. I'll leave you with some reliable data:
-arch64 procesor
-5.1 stock android : BLU_V0030UU_V07_GENERIC 25-01-2016
- 3.10.65+ kernel
- Rooted with kingoroot
- Previously had xposed, but uninstalled due to random reboots.
I was looking to install aospextended rom:
https://forum.xda-developers.com/vivo-xl/development/rom-aospextended-rom-v4-1-t3592932
I'd really appreciate if you could orient me or refer me to a post with instructions, since i didn't find one. It's been some years since i don't do this back to the legendary HTC HD2 and i'm missing it btw
Thanks!
Nacho

https://forum.xda-developers.com/vivo-xl/how-to/fix-soft-brickedcannot-enter-recovery-t3594733
Unfortunately most custom ROMs in this forum were based off Gionee so likely you will get no SIM. Use your stock ROM /etc/firmware folder to replace that in ROM.

min1968 said:
https://forum.xda-developers.com/vivo-xl/how-to/fix-soft-brickedcannot-enter-recovery-t3594733
Unfortunately most custom ROMs in this forum were based off Gionee so likely you will get no SIM. Use your stock ROM /etc/firmware folder to replace that in ROM.
Click to expand...
Click to collapse
Thank you for your response.
I've already got twrp installed for 5.1
So i should just install this MM based ROM i said on the post and replace /etc/firmware folder?
Or i need to install stock MM from ota first?
Thing is, i cant OTA update, it says that the system is corrupted, i even tried from twrp but no luck

I've seen that i need stock mm to be able to install most of the custom rom's in xda
Thing is i can't install any OTA update. Should i flash 5.1 stock rom on top of the modified one i'm running?
By modified i am talking about the root and xposed, which is the cause i cant OTA

Nacholer said:
I've seen that i need stock mm to be able to install most of the custom rom's in xda
Thing is i can't install any OTA update. Should i flash 5.1 stock rom on top of the modified one i'm running?
By modified i am talking about the root and xposed, which is the cause i cant OTA
Click to expand...
Click to collapse
Follow my steps exactly then you can do OTA to MM.
The key is to use the 8 files backup to restore stock 5.1, not the backup only includes 4 files.

min1968 said:
Follow my steps exactly then you can do OTA to MM.
The key is to use the 8 files backup to restore stock 5.1, not the backup only includes 4 files.
Click to expand...
Click to collapse
Alright, ill do that. Tried with the 4 files backup last night, didn't work as you just told.
Do you have a link to the 5.1 stock recovery i should flash with sp flash tool? I can't find it anywhere. It wont work if i still have twrp installed, right?
Thanks! i really appreciate it, and great guide btw

min1968 said:
Follow my steps exactly then you can do OTA to MM.
The key is to use the 8 files backup to restore stock 5.1, not the backup only includes 4 files.
Click to expand...
Click to collapse
I installed the 11 files backup and i still can't get ota. I should install the stock recovery, right? got a link for that?
Thank you in advance!

In my case I have a fully working STOCK but ROOTED Marshmallow Blu Vivo XL with working IMEI, but as soon as I wipe and install say AEX rom, I lose both IMEI functions and also get the dreaded wifi NVRAM error (but working wifi).
I also restored the etc/firmware directory to AEX but it wont help regain IMEI functionality.
MTK Engineering mode does not work on AEX because it complains not being stock rom so it closes.
For the life of me, I can't make a connection to the PC through SP Flash Tool too.
Any pointers?
TIA!

Nacholer said:
I installed the 11 files backup and i still can't get ota. I should install the stock recovery, right? got a link for that?
Thank you in advance!
Click to expand...
Click to collapse
Yes need stock recovery to do OTA.
https://forum.xda-developers.com/vivo-xl/development/recovery-t3311601
---------- Post added at 03:00 PM ---------- Previous post was at 02:56 PM ----------
Rayan said:
In my case I have a fully working STOCK but ROOTED Marshmallow Blu Vivo XL with working IMEI, but as soon as I wipe and install say AEX rom, I lose both IMEI functions and also get the dreaded wifi NVRAM error (but working wifi).
I also restored the etc/firmware directory to AEX but it wont help regain IMEI functionality.
MTK Engineering mode does not work on AEX because it complains not being stock rom so it closes.
For the life of me, I can't make a connection to the PC through SP Flash Tool too.
Any pointers?
TIA!
Click to expand...
Click to collapse
Read above my #2 post on customer ROMs in this forum.
And my this post to rescue your Blu Vivo XL :
https://forum.xda-developers.com/vivo-xl/how-to/fix-soft-brickedcannot-enter-recovery-t3594733

min1968 said:
Yes need stock recovery to do OTA.
https://forum.xda-developers.com/vivo-xl/development/recovery-t3311601
Thank you!! i'll try that and report back.
Click to expand...
Click to collapse

min1968 said:
Yes need stock recovery to do OTA.
https://forum.xda-developers.com/vivo-xl/development/recovery-t3311601
---------- Post added at 03:00 PM ---------- Previous post was at 02:56 PM ----------
Read above my #2 post on customer ROMs in this forum.
And my this post to rescue your Blu Vivo XL :
https://forum.xda-developers.com/vivo-xl/how-to/fix-soft-brickedcannot-enter-recovery-t3594733
Click to expand...
Click to collapse
Thanks for the reply Min1968!
Yes, I know how to recover IMEI on the stock ROM and I'm currently running stock MM rooted with working IMEI.
The problem I have is that I can't run custom ROMs even if I try the etc/firmware trick you mentioned.
What is the stock TWRP partition that has the modem and IMEI? Maybe if I flash it back through TWRP once I get AEX rom up and running?
Thanks!

min1968 said:
Yes need stock recovery to do OTA.
https://forum.xda-developers.com/vivo-xl/development/recovery-t3311601
---------- Post added at 03:00 PM ---------- Previous post was at 02:56 PM ----------
Click to expand...
Click to collapse
Hey, i got into deep trouble. i Factory reseted the phone. Then did fastboot oem unlock, flashed by fastboot flash recovery, the stock recovery img. After that, the phone boot-loops. I installed back twrp and it sais : Unable to mount /data
Now i can't access my internal memory and i'm stuck. Please help me!
Thanks, i really appreciate this

Nacholer said:
Hey, i got into deep trouble. i Factory reseted the phone. Then did fastboot oem unlock, flashed by fastboot flash recovery, the stock recovery img. After that, the phone boot-loops. I installed back twrp and it sais : Unable to mount /data
Now i can't access my internal memory and i'm stuck. Please help me!
Thanks, i really appreciate this
Click to expand...
Click to collapse
Okay, i fixed it reformatting the data partition on twrp. Thing is, when i want to install the recovery that happens. Maybe if i dont oem unlock?

well, i did that and it booted with the stock recovery. But i still can't OTA, i really dont know why, i even could not when i bought the phone

Nacholer said:
Hey guys,
I am trying to intall a custom rom on my blu vivo xl. My worries are that i either soft-brick the phone or boot the new rom and having no signal due to no imei, or no 4G due to band change if it's even possible. I'll leave you with some reliable data:
-arch64 procesor
-5.1 stock android : BLU_V0030UU_V07_GENERIC 25-01-2016
- 3.10.65+ kernel
- Rooted with kingoroot
- Previously had xposed, but uninstalled due to random reboots.
I was looking to install aospextended rom:
https://forum.xda-developers.com/vivo-xl/development/rom-aospextended-rom-v4-1-t3592932
I'd really appreciate if you could orient me or refer me to a post with instructions, since i didn't find one. It's been some years since i don't do this back to the legendary HTC HD2 and i'm missing it btw
Thanks!
Nacho
Click to expand...
Click to collapse
to get imei working https://forum.xda-developers.com/vivo-xl/help/solution-to-sim-detected-flashing-t3620224

Question Is there a step by step guide for flashing stock payload.bin files.

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