Database Develop

[Q] Micro usb door damaged,how to restore original firmware through micro sd

Hey all
As the title says my Xperia z micro usb door is damaged so i cant charge or plug the mobile through my pc to restore the original firmware and send it back for reparation.
Is there any way to restore the firmware by using the micro sd?
Actually im charging the mobile using the dock. But since i dont like the battery life of the mobile..im thinking to fix it and sell it and buy new mobile.
Thanks for help

wiimourad said:
Hey all
As the title says my Xperia z micro usb door is damaged so i cant charge or plug the mobile through my pc to restore the original firmware and send it back for reparation.
Is there any way to restore the firmware by using the micro sd?
Actually im charging the mobile using the dock. But since i dont like the battery life of the mobile..im thinking to fix it and sell it and buy new mobile.
Thanks for help
Click to expand...
Click to collapse
If your phone has recovery installed you might be able to flash a stock ROM zip to put it back to its original firmware, otherwise u would need to use flashtool and flash a firmware via usb for it to be restored

Mackay53 said:
If your phone has recovery installed you might be able to flash a stock ROM zip to put it back to its original firmware, otherwise u would need to use flashtool and flash a firmware via usb for it to be restored
Click to expand...
Click to collapse
i got a FTF file with 758mb
is it that one?

wiimourad said:
i got a FTF file with 758mb
is it that one?
Click to expand...
Click to collapse
You can only flash an FTF via flashtool via USB
Are you rooted and have a recovery installed?

Mackay53 said:
You can only flash an FTF via flashtool via USB
Are you rooted and have a recovery installed?
Click to expand...
Click to collapse
yes is rooted and i got cyanogenmod on it...so i guesse there is a recovery

wiimourad said:
yes is rooted and i got cyanogenmod on it...so i guesse there is a recovery
Click to expand...
Click to collapse
You should be able to put the zip file onto the SD card and flash it via recovery. I'm guessing u never backed up your original ROM when you first installed recovery?

If that doesnt work, you could also try moving it to your phone through google drive?
Sent from my Nexus 5 using xda app-developers app

Could he restore to completely stock using a backup of somebody else's XZ?
Or could that cause issues?

Mackay53 said:
You should be able to put the zip file onto the SD card and flash it via recovery. I'm guessing u never backed up your original ROM when you first installed recovery?
Click to expand...
Click to collapse
i didnt unfortunaly
So i just have to put the FTF into my Sd card and flash via recovery?
How exactly?! Can you please link the intire procedure
If that doesnt work, you could also try moving it to your phone through google drive?
Click to expand...
Click to collapse
The sd card work fine,but if you mean that i have to download the FTF to internal storage and restore it via recovery is not a problem.

You cannot flash FTF files in recovery. They are for use with Flashtool only.
{
"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"
}

kingvortex said:
You cannot flash FTF files in recovery. They are for use with Flashtool only.
Click to expand...
Click to collapse
Is there any other way to bring back the mobile to his original status?

Completely stock? I don't think so, unfortunately.
I don't think it should matter when returning the device for a hardware defect though. The rom you're running didn't break your USB port.

wiimourad said:
Is there any other way to bring back the mobile to his original status?
Click to expand...
Click to collapse
You can get close enough
Install NUT's pre-rooted (odex version) rom through recovery.
While in recovery do a wipe. /data/factory reset.
Then flash my XZDR removal tool http://d-h.st/wOc
Reboot and you will be back on pure stock with root.
Then just do a full unroot from within SuperSU app.
Done
Edit: Hopefully your bootloader is locked But as @kingvortex said - its got nothing to do with a broken port
Sent from my C6603 using xda app-developers app

Hmm, good thinking, but does [NUT]'s flashable zip include the kernel? I was under the (perhaps mistaken) impression that the stripped FTF had to be flashed with Flashtool for the kernel and baseband. If I'm correct, then the rom will not boot with the CM kernel (correct me if I'm wrong). In that case, DooMLoRD's advanced stock kernel is a possibility, but that is still not fully stock and would require that the bootloader remain unlocked.
There's also the fact that the OP is on a CM rom, so therefore fastboot is needed to relock the bootloader even if a fully stock system is achieved.
It all depends on how closely the service centre looks at the software on the phone, I suppose.

Oh OK. So he is on CM11? - missed that. I was hoping he was on stock based.
Yeah your probably right about the stock kernel being in the stripped FTF. (Never tried it), however there is still a way. A little convoluted though, and I don't have time for a new tutorial.
Easiest way is, as you said, just take the damn thing to the repair centre and argue that customizing the phone has nothing to do with a faulty USB port
Sent from my Full Android on C6603 using xda app-developers app

Yeah, he didn't say he was on CM until post #5. I'm used to people not being forthcoming with all pertinent information here, so read through his other posts before replying.
I think it's possible to package a stock kernel up in a flashable zip. If it is, it may be possible to get back to stock. I'll look for the post where I saw it.
Edit - Found it.
http://forum.xda-developers.com/showthread.php?t=2470280
So, maybe -
1. Flash [NUT]'s rom.
2. Flash stock kernel packaged by the method above.
3. Wipe /data.
4. Flash your XZDR removal tool.
5. Reboot.
That may work. Trouble is, performing steps like this without the safety net of Flashtool or even fastboot in the event of something going wrong is quite risky, so nobody blame me if a brick happens!
Even if all is successful, the bootloader will still be unlocked, so hopefully the service centre will not check.

kingvortex said:
Completely stock? I don't think so, unfortunately.
I don't think it should matter when returning the device for a hardware defect though. The rom you're running didn't break your USB port.
Click to expand...
Click to collapse
they might say the usb door is broken coz you use it to perform software modification
Are you sure about this info?
i bought the mobile from Amazon.de

wiimourad said:
they might say the usb door is broken coz you use it to perform software modification
Are you sure about this info?
i bought the mobile from Amazon.de
Click to expand...
Click to collapse
Well, no I'm not sure as I haven't had to take mine to service, but how would changing the software on the phone physically break it?

kingvortex said:
Well, no I'm not sure as I haven't had to take mine to service, but how would changing the software on the phone physically break it?
Click to expand...
Click to collapse
an intense usage of the door would break it..or a high voltage caused by the software modification...you know how they think.

is it possible to have the link for
1:[NUT]'s rom
2:XZDR removal tool
thanks

[Q] CM Installer not recognizing my phone

Ok so I just got the One M7 and I hate Sense, like really hate it so I went on to install CM11 via CyanogenMod Installer (Like MKBHD did, that's why I thought I should) and I did everything it said, Opened up the app on my phone followed the instructions until it said "Continue installation on your computer" and I did, when I opened the CM Installer however, it never detects my phone! I don't have HTC Drivers nor HTC Sync manager, but I heard that it isn't needed, help

CesarRaimon said:
Ok so I just got the One M7 and I hate Sense, like really hate it so I went on to install CM11 via CyanogenMod Installer (Like MKBHD did, that's why I thought I should) and I did everything it said, Opened up the app on my phone followed the instructions until it said "Continue installation on your computer" and I did, when I opened the CM Installer however, it never detects my phone! I don't have HTC Drivers nor HTC Sync manager, but I heard that it isn't needed, help
Click to expand...
Click to collapse
if your phone must communicate with your pc at some point, you must have the drivers installed even if its not specified
Btw this is very simple to flash CM using a custom recovery if the installer doesn't work.
install the drivers using this guide:
originally from @nkk71: [GUIDE] [02-MAR-2014] nkk71's SuperGUIDE to returning 100% back to stock
2) Q: I'm using Windows 7 what should I worry about
A: when you issue the command "fastboot boot CWM.img" (now only in CWM/TWRP restore method) there's a high chance drivers won't correctly install
{
"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"
}
follow the below instructions to fix
Open "Device Manager" -> select the unknown "One" -> right-click -> "Update Driver Software ..." -> "Browse my computer" -> "Let me pick" -> "Android USB Devices" -> select "My HTC ..." -> install that
just in case, HTC Drivers can be found here: [Drivers] HTC Drivers for Windows - Several Versions (credits to @mdmower)
though you should already have them since you have been using your phone anyways​
for those who like a visual guide:
okay so I did a fastboot boot command, and as you can see it didnt install correct driver
Open "Device Manager"
there's the culprit
right click and Update Driver Software
select Browse my computer for driver software
select Let me pick from a list of device drivers on my computer
select Android USB Devices
select My HTC ... (if you have more than one version, choose the latest)
warning, select Yes
successful installation
now it looks better
and can confirm:
Code:
C:\ADB3>[B]adb devices[/B]
List of devices attached
HTxxxxxxxxxx recovery
-------------------------------------------------------------------------------------------------------------------------------------------
Click to expand...
Click to collapse

alray said:
if your phone must communicate with your pc at some point, you must have the drivers installed even if its not specified
Btw this is very simple to flash CM using a custom recovery if the installer doesn't work.
install the drivers using this guide:
Click to expand...
Click to collapse
woah thanks for the quick response, I'll try that and report shortly, thanks again

CesarRaimon said:
woah thanks for the quick response, I'll try that and report shortly, thanks again
Click to expand...
Click to collapse
The problem using the CM installer is that you don't have any option to revert back to stock which is possible when you flash the rom from recovery. (you can make a nandroid backup before flashing the rom)
So if you need to send your phone to repair under warranty, can you return to stock? Is there a ruu for your phone if you don't have a backup?

alray said:
The problem using the CM installer is that you don't have any option to revert back to stock which is possible when you flash the rom from recovery. (you can make a nandroid backup before flashing the rom)
So if you need to send your phone to repair under warranty, can you return to stock? Is there a ruu for your phone if you don't have a backup?
Click to expand...
Click to collapse
I'm really not willing to go back to stock, and the warranty is already expired so I got nothing to lose really, don't know what RUU is

CesarRaimon said:
I'm really not willing to go back to stock, and the warranty is already expired so I got nothing to lose really, don't know what RUU is
Click to expand...
Click to collapse
ok its up to you :angel:
btw I like this name.... Raymond

alray said:
ok its up to you :angel:
btw I like this name.... Raymond
Click to expand...
Click to collapse
Thanks! Like the name Alray!
And what's RUU btw, any links would be much appreciated

CesarRaimon said:
Thanks! Like the name Alray!
And what's RUU btw, any links would be much appreciated
Click to expand...
Click to collapse
RUU is for Rom Update Utility. Its the most common way to restore HTC devices back to stock from your computer. It can also be used to updated a phone if something is messed up and prevent the ota update to install. It flashes/update stock hboot, stock recovery, stock radio, stock software (rom).... stock everything.... But to use a ruu you must find one that is specifically for your phone model, software, CID and MID.
RUU for the htc one M7 can be found here http://www.htc1guru.com/

alray said:
RUU is for Rom Update Utility. Its the most common way to restore HTC devices back to stock from your computer. It can also be used to updated a phone if something is messed up and prevent the ota update to install. It flashes/update stock hboot, stock recovery, stock radio, stock software (rom).... stock everything.... But to use a ruu you must find one that is specifically for your phone model, software, CID and MID.
RUU for the htc one M7 can be found here http://www.htc1guru.com/
''ray'' in alray is for Raymond thats why I like it...
Click to expand...
Click to collapse
Aha so it's kinda like Odin for Samsung devices! and I see what you did there

[Q] need help broken usb prot

hi guys im having problems with my usb port on my s3 mini l1890T its been rooted and is currently running a custom ROM but i need to put it back to stock so i can use the warrenty to get it fixed however i cant find any backups of this phone prior to the custom rom as i think it was on my old pc when it kicked the bucket. so im after a stock rom that could be flashed via cwm if this is possible.
please help and leave a comment even if its to say sorry but your screwed. i really need to get this sorted tonight as i need to return it in the morning.

jezcullen09 said:
hi guys im having problems with my usb port on my s3 mini l1890T its been rooted and is currently running a custom ROM but i need to put it back to stock so i can use the warrenty to get it fixed however i cant find any backups of this phone prior to the custom rom as i think it was on my old pc when it kicked the bucket. so im after a stock rom that could be flashed via cwm if this is possible.
please help and leave a comment even if its to say sorry but your screwed. i really need to get this sorted tonight as i need to return it in the morning.
Click to expand...
Click to collapse
Stock ROM via cwm is possible but I don't know if anyone have made a zip for it.
What country/service provider?
Sent through time and space from my s3mini/CM11

im in new zealand and im on telecom.
my wife has the same phone i was wondering if i could root her phone then take a backup of that and install the backup on mine
would that work?

tys0n said:
Stock ROM via cwm is possible but I don't know if anyone have made a zip for it.
What country/service provider?
Sent through time and space from my s3mini/CM11
Click to expand...
Click to collapse
im in new zealand and im on telecom.
my wife has the same phone i was wondering if i could root her phone then take a backup of that and install the backup on mine
would that work?

jezcullen09 said:
im in new zealand and im on telecom.
my wife has the same phone i was wondering if i could root her phone then take a backup of that and install the backup on mine
would that work?
Click to expand...
Click to collapse
Could work, depending on how backups are stored. I can just tell that tarp looks for backups in a folder with your device-id.
{
"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"
}
What you need is system and boot, and a flashable zip with original recovery.
Sent through time and space from my s3mini/CM11

tys0n said:
Stock ROM via cwm is possible but I don't know if anyone have made a zip for it.
What country/service provider?
Sent through time and space from my s3mini/CM11
Click to expand...
Click to collapse
tys0n said:
Could work, depending on how backups are stored. I can just tell that tarp looks for backups in a folder with your device-id.
View attachment 2783531
What you need is system and boot, and a flashable zip with original recovery.
Sent through time and space from my s3mini/CM11
Click to expand...
Click to collapse
i dont suppose you know where i could find them do you?
what about the idea that i had with my wifes phone?

jezcullen09 said:
i dont suppose you know where i could find them do you?
what about the idea that i had with my wifes phone?
Click to expand...
Click to collapse
No i dont. Not as cwm flashable zip.
Backup from another phone probably works as long as the backup folder is named right so that recovery finds it.
Make a backup and folders will be created, use external storage.
Whole restore process would be:
Make sure binary count is zero with triangle away.
Boot download mode to make sure as well.
Copy backups of system and boot to backup folder.
Boot to recovery, factory reset, restore backups from other phone, factory reset again.
Boot system to see that all is OK.
Unroot from SuperSU settings if needed.
Back to recovery to flash flashable zip of stock recovery.
I guess you'll have to make one more factory reset from stock recovery to get everything official status.
I hope I didn't miss anything
(I can make that zip for you if you'll need it. Downloading firmware right now, just in case)
Sent through time and space from my s3mini/CM11

tys0n said:
No i dont. Not as cwm flashable zip.
Backup from another phone probably works as long as the backup folder is named right so that recovery finds it.
Make a backup and folders will be created, use external storage.
Whole restore process would be:
Make sure binary count is zero with triangle away.
Boot download mode to make sure as well.
Copy backups of system and boot to backup folder.
Boot to recovery, factory reset, restore backups from other phone, factory reset again.
Boot system to see that all is OK.
Unroot from SuperSU settings if needed.
Back to recovery to flash flashable zip of stock recovery.
I guess you'll have to make one more factory reset from stock recovery to get everything official status.
I hope I didn't miss anything
(I can make that zip for you if you'll need it. Downloading firmware right now, just in case)
Sent through time and space from my s3mini/CM11
Click to expand...
Click to collapse
that would be awsome if you could make that zip for me i would really appreciate it but if its to much of a hasel for you ill start the process of rooting my wifes phone.

jezcullen09 said:
that would be awsome if you could make that zip for me i would really appreciate it but if its to much of a hasel for you ill start the process of rooting my wifes phone.
Click to expand...
Click to collapse
No problem at all. I could have made whole firmware for you if it wasn't for my damn internet upload when I'm at home. (data plan from my phone at the moment)
Downloaded firmware while I was at a friend.
Sent through time and space from my s3mini/CM11

tys0n said:
I could have made whole firmware for you if it wasn't for my damn internet upload when I'm at home. (data plan from my phone at the moment)
Click to expand...
Click to collapse
i know that feeling we live out on a farm and the speeds are so slow

Damn. I just extracted firmware and recovery.img is not included there.
Sent through time and space from my s3mini/CM11
---------- Post added at 02:59 PM ---------- Previous post was at 02:14 PM ----------
Im pretty sure i8190 stock recovery will do anyway. We got the same partitions. Otherwise you would not been able to flash a custom recovery neither.
Sent through time and space from my s3mini/CM11

Any progress?

tys0n said:
Any progress?
Click to expand...
Click to collapse
No not yet I went root my wife's phone but she had next to no battery plus it was about 2 in the morning

jezcullen09 said:
No not yet I went root my wife's phone but she had next to no battery plus it was about 2 in the morning
Click to expand...
Click to collapse
Ah I see.
Is this the firmware you two have?
PDA: I8190TDCAMA3
CSC: I8190TTNZAMA2
MODEM: I8190TDCAMA3
If it is, then I got a flashable zip for you. Took me only ten minutes to make, and uploaded at another friend
No root no, busybox, no deodexed. Just stock.
I8190T-DCAMA3_I8190T-TNZAMA2_TNZ.zip

tys0n said:
Ah I see.
Is this the firmware you two have?
PDA: I8190TDCAMA3
CSC: I8190TTNZAMA2
MODEM: I8190Towe you oneDCAMA3
If it is, then I got a flashable zip for you. Took me only ten minutes to make, and uploaded at another friend
No root no, busybox, no deodexed. Just stock.
I8190T-DCAMA3_I8190T-TNZAMA2_TNZ.zip
Click to expand...
Click to collapse
Thanks mate she worked all that is left is the cwm but I'm going to risk sending it in for repair.
I owe you one if you ever find your self in nz come have a feed

jezcullen09 said:
Thanks mate she worked all that is left is the cwm but I'm going to risk sending it in for repair.
I owe you one if you ever find your self in nz come have a feed
Click to expand...
Click to collapse
Good to hear that it worked out fine. I even flashed it myself to make sure it would work.
Nothing owned.. A simple push on thanks button is enough
Hope you'll get it back fully functional again.
Sent through time and space from my s3mini/CM11

[Q] How can I update to Lollipop 5.1 if my device is already rooted?

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...

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