Develop Bugs

Maybe Brick me N7100

Hello,
I have i problems with my N7100.
I can't boot the phone after flash Hybrid Kernel 9.0.3
https://forum.xda-developers.com/galaxy-note-2/development/kernel-t3732155
I have try to install N7100XXDLJ2_OXA_FACTORY to recover me phone but i have a red message in download mode.
I think is because i try to downgrade the bootloader.
I have try to flash N7100XXSFQA7_N7100OXAFOC2_N7100XXUFNG1_HOME.tar.md5
When odin finish, the phone reboot and the phone boot
I can see the samsung logo
When the phone ask for pin, the phone reboot.
And now the phone stick on N7100 logo
Can you help me ?
Thank you

Did you perform a factory reset from stock recovery after flashing the latest stock ROM?

Hello, i fix it, after many flash, stock, custom ....
I can't explain, but when i boot on me OEM battery the phone boot loot.
I install a new battery inside and my phone work very well.

evilpacer said:
Hello, i fix it, after many flash, stock, custom ....
I can't explain, but when i boot on me OEM battery the phone boot loot.
I install a new battery inside and my phone work very well.
Click to expand...
Click to collapse
I always hear about this alot that battery was the problem but i am always thinking why, Whats the connection between them.

Did factory reset rooted XT 1799-2, now phone only boots into recovery mode

Hi,
My previous post relates to this one. Due to that problem I got, I had to factory reset my device to get my camera working again. However, instead, my phone rebooted into TWRP and would not boot system normally. When I tried to go to factory mode via fastboot I ended up in endless bootloop. Back in TWRP I tried to restore my backed up ROM from before rooting, but nothing really changed. I am really desperate because I have not find any solutions for my model and I don't want to use other montana models stock ROMs as I suspect them not to be compatible. What shall I do?
Cheers
Six

sixtheninth said:
Hi,
My previous post relates to this one. Due to that problem I got, I had to factory reset my device to get my camera working again. However, instead, my phone rebooted into TWRP and would not boot system normally. When I tried to go to factory mode via fastboot I ended up in endless bootloop. Back in TWRP I tried to restore my backed up ROM from before rooting, but nothing really changed. I am really desperate because I have not find any solutions for my model and I don't want to use other montana models stock ROMs as I suspect them not to be compatible. What shall I do?
Cheers
Six
Click to expand...
Click to collapse
Flash montana_retcn stock rom via rsd lite or fastboot and your device will boot again but it will lose all your files

jvfigueredo said:
Flash montana_retcn stock rom via rsd lite or fastboot and your device will boot again but it will lose all your files
Click to expand...
Click to collapse
Thanks senor, but how do I flash it via fastboot? Can't I use TWRP instead?

jvfigueredo said:
Flash montana_retcn stock rom via rsd lite or fastboot and your device will boot again but it will lose all your files
Click to expand...
Click to collapse
Ok I was able the Stock rom, but it is Chinese, not the global one wihout Gapps and lots of bloatware. Do you know if there is also a GLOBAL stock ROM I can get? Conversely, is there perhaps a custom ROM like Lineage OS or others that is compatible with this device? Cheers

sixtheninth said:
Ok I was able the Stock rom, but it is Chinese, not the global one wihout Gapps and lots of bloatware. Do you know if there is also a GLOBAL stock ROM I can get? Conversely, is there perhaps a custom ROM like Lineage OS or others that is compatible with this device? Cheers
Click to expand...
Click to collapse
Sorry this is the stock rom of montana_retcn, to install the playstore by the store that comes in it, and it has the English language.
The rom that you were supposed to be a shop rom of the store that you bought, mine came with one of this but unfortunately I do not know where it has to download ...

jvfigueredo said:
Sorry this is the stock rom of montana_retcn, to install the playstore by the store that comes in it, and it has the English language.
The rom that you were supposed to be a shop rom of the store that you bought, mine came with one of this but unfortunately I do not know where it has to download ...
Click to expand...
Click to collapse
Ok I guess there is nothing more to be done here. Any custom ROMs are also probably not lying around too I guess :/

sixtheninth said:
Hi,
My previous post relates to this one. Due to that problem I got, I had to factory reset my device to get my camera working again. However, instead, my phone rebooted into TWRP and would not boot system normally. When I tried to go to factory mode via fastboot I ended up in endless bootloop. Back in TWRP I tried to restore my backed up ROM from before rooting, but nothing really changed. I am really desperate because I have not find any solutions for my model and I don't want to use other montana models stock ROMs as I suspect them not to be compatible. What shall I do?
Cheers
Six
Click to expand...
Click to collapse
Turn off the device, boot into Fastboot Flash Mode using vol down + power, using volume keys scroll and select factory mode and device will turn on. the next time you boot up the device, it won't go into TWRP directly. I have faced this issue many times. Hope this helps.

rizwan.mahai said:
Turn off the device, boot into Fastboot Flash Mode using vol down + power, using volume keys scroll and select factory mode and device will turn on. the next time you boot up the device, it won't go into TWRP directly. I have faced this issue many times. Hope this helps.
Click to expand...
Click to collapse
Not in this case. What Factory Mode did was that it got stuck in loading loop playing the Moto logo endlessly for over 5 minutes. Anyway, the phone is now hard bricked so I am facing even larger issue )

sixtheninth said:
Not in this case. What Factory Mode did was that it got stuck in loading loop playing the Moto logo endlessly for over 5 minutes. Anyway, the phone is now hard bricked so I am facing even larger issue )
Click to expand...
Click to collapse

I'm having the same problem with my wifes g5s.
I have found that from twrp>restart>bootloader (phone then enters bootloader) I can the immediately choose "start" to boot the phone.
But that is a hassle I'd prefer my wife not having to go through...

SvenHee said:
I'm having the same problem with my wifes g5s.
I have found that from twrp>restart>bootloader (phone then enters bootloader) I can the immediately choose "start" to boot the phone.
But that is a hassle I'd prefer my wife not having to go through...
Click to expand...
Click to collapse
Flash stock ROM via fastboot problem will be solved..
As far as people who need play store can flash gapps via TWRP as a same method we use for custom ROMs.
P.S. i will not suggest to buy XT1799-2 because this SKU is purely made for Chinese Market, if you need any custom ROM go to Weibo.com/diyroms and post a request to build a custom ROM for this device.
And there are some custom ROMs available that you can search via baidu.com ( Chinese Search Engine).
I will try to find any ROM and post for you guys and also post. Request to build for XT1799-2.
CHEERS

so have you find any global custom rom for this device ?

aamszia said:
so have you find any global custom rom for this device ?
Click to expand...
Click to collapse
Yes you can flash Viper Pie for Xt1792
Already tested at Xt1799

NERVOUS about flashing Lineage 18 :-(

HI,
I am not new to flashing phones and tablets, but I am a bit confused about the new partition format.
I have a nokia 6.1.
I want to flash the official lineage 18 ROM on it.
I downloaded the latest version , and also the latest lineage recovery.
I followed the install instructions on the website . I believe, exactly.
But after I have executed this command '' fastboot flash boot xxxxx.img"" to temporarily boot recovery, the phone stays in download mode and does nothing.
I then thought maybe I need to reboot?, and power down, because the next thing on the lineage install instructions is to start the phone having powered down.
Anyways, when it boots up, it hangs and stays on the android one screen.
Power/Volume up does nothing.
Whats worse is, it is no longer recognised in ADB.
I was really worried. I let the battery die overnight, and then tried to get some response, but no - still stuck.
Finally, after more fiddling, I got it into download mode, and was able to flash stock using OST.
I tried again - same thing, and once again luckily managed after an hour or so to get it into download mode.
So I have reflashed stock, and wondering if somebody a lot brighter than me can give some advice??
Currently on stock android 10, but would much prefer lineage 18 , as I have no need for google services.
Can only think something is going wrong with whichever partition I am temporarily booting to recovery?
Many Thanks ( with a relieved sigh for escaping a brick )
pootler

Something similar happened to me, it turns out that from android 10 stock you have to first:
fastboot flash recovery xxxx.img
you will get an error in the cmd, that's good, now
fasboot boot xxxx.img
.
this was mentioned a long time ago but was never mentioned more in other threads
if you get stuck you can use ost la. also remember the slot A B when you flash the rom

Tsuragi said:
Something similar happened to me, it turns out that from android 10 stock you have to first:
fastboot flash recovery xxxx.img
you will get an error in the cmd, that's good, now
fasboot boot xxxx.img
.
this was mentioned a long time ago but was never mentioned more in other threads
if you get stuck you can use ost la. also remember the slot A B when you flash the rom
Click to expand...
Click to collapse
Thanks Tsuragi,
Forgot about that - it was me who posted that solution some time ago duh!
Pootler

pootler said:
HI,
I am not new to flashing phones and tablets, but I am a bit confused about the new partition format.
I have a nokia 6.1.
I want to flash the official lineage 18 ROM on it.
I downloaded the latest version , and also the latest lineage recovery.
I followed the install instructions on the website . I believe, exactly.
But after I have executed this command '' fastboot flash boot xxxxx.img"" to temporarily boot recovery, the phone stays in download mode and does nothing.
I then thought maybe I need to reboot?, and power down, because the next thing on the lineage install instructions is to start the phone having powered down.
Anyways, when it boots up, it hangs and stays on the android one screen.
Power/Volume up does nothing.
Whats worse is, it is no longer recognised in ADB.
I was really worried. I let the battery die overnight, and then tried to get some response, but no - still stuck.
Finally, after more fiddling, I got it into download mode, and was able to flash stock using OST.
I tried again - same thing, and once again luckily managed after an hour or so to get it into download mode.
So I have reflashed stock, and wondering if somebody a lot brighter than me can give some advice??
Currently on stock android 10, but would much prefer lineage 18 , as I have no need for google services.
Can only think something is going wrong with whichever partition I am temporarily booting to recovery?
Many Thanks ( with a relieved sigh for escaping a brick )
pootler
Click to expand...
Click to collapse
Hey bro same experience, thats why im stock in android 10 with unlock bootloader. but i successfully flashed lineage with unofficial twrp but the problem is i cant flashed gapps thats why i cant install pre apps and cant use the default message and call. please help me

Cant get back to factory

i am on PE and been on Linage and then Derp but for 2 weeks now ive tried to go back to factory and for the life of me nothing works ive tried the All N One Tool and MSM Tool and nothing i constantly end up back where i started.
Ive downloaded the latest os firmware from oneplus All N One Tool Downloads the firmware extrasts it the pops up a error saying flash all .bat is missing so dead end there.
could someone lead me in the right direction or explain to me if im doing something wrong.... thanks

[CLOSED] T-Mobile 7T Conversion to International WITHOUT unlocked bootloader/SIM unlock!
Here is a patched MSM download tool for TMobile OP7T. It will bypass the need to sim unlock before unlocking the bootloader, and will also bypass the need of an unlock token file from OnePlus (hence skip the wait period of 1 week to get the...
forum.xda-developers.com

this will be my last onepluse thatr for sure going back to Pixel 4 XL didnt have no issues going back to stock this is crazy

I'm having the same issue, so I'm gonna piggyback this in hopes of a different direction.. Long story, short, I've spent hours trying to get back to OOS from crdroid 11. the link above got me back to booting up t-mobile and relocks the bootloader, but wifi radio doesnt work & restarting brings me to being stuck on the boot logo. none of the other MSMtools work, unlocked or TMO from the unbrick page.
what step am i missing after going through the tmo to int. guide? since that's the only thing that's working.. thanks in advance, i'm attempting round 2 in the meantime.

When u r stuck on pink TMobile screen, force reboot to bootloader by holding vol+, vol-, & power buttons for 10 sec. Once you see phone rebooting, let go of power button only to enter bootloader mode. Then type "fastboot reboot fastboot" on PC while USBC cable is plugged into phone. This will kick phone into fastbootD mode. Then fastboot flash all stock rom files.
When wifi and 4g not working, u did not enter fastbootD mode, so system did not flash right

SageChrono said:
I'm having the same issue, so I'm gonna piggyback this in hopes of a different direction.. Long story, short, I've spent hours trying to get back to OOS from crdroid 11. the link above got me back to booting up t-mobile and relocks the bootloader, but wifi radio doesnt work & restarting brings me to being stuck on the boot logo. none of the other MSMtools work, unlocked or TMO from the unbrick page.
what step am i missing after going through the tmo to int. guide? since that's the only thing that's working.. thanks in advance, i'm attempting round 2 in the meantime.
Click to expand...
Click to collapse
Above

HueyT said:
Above
Click to expand...
Click to collapse
i was just coming to edit my post. rookie mistake - i forgot to overwrite adb/fastboot tools everytime i moved the OS files to my adb folder lol... somehow i forgot a bunch of times
phone is booting up without that userspace error, so i may be back in good shape!
edit 2.0: all booted up with wifi/camera working again

well gonna try again for the 4th time this time im gonna use a different computer and see if that works..... UUUGGGG

well the 4th time fail to restore back to stock OOS.. its gotta be something im doing bc i even used a different computer. but gonna keep looking around for another route.

msmdownloaderTool says this (Device Not Match Image) the device seems to time out and disconnects from MSMDownloaderTool every time. any advice i have the global version 7T 1905

HueyT said:
[CLOSED] T-Mobile 7T Conversion to International WITHOUT unlocked bootloader/SIM unlock!
Here is a patched MSM download tool for TMobile OP7T. It will bypass the need to sim unlock before unlocking the bootloader, and will also bypass the need of an unlock token file from OnePlus (hence skip the wait period of 1 week to get the...
forum.xda-developers.com
Click to expand...
Click to collapse
this would not work for me im assuming bc i have the global HD1905 not the T Mobile branded. u can read above why it wouldn't work . but i seem to have made some progress using the All in One Tool i clicked on flash factory image tab and at first it keep error out saying no Flash-All.bat found after unzipping it. so i kelp looking around and finally foud a factory zip that had the Flash-All.bat file in it so tried again using the Allin One Tool clicked Flash Factory image and it unzipped it and flashed fine but now i cant boot to the OOS it just reboots to the " your bootloader is unlocked integrity screen and stays . but i can boot in fastboot mode and recovery which is now factory recovery. i noticed that it flashed the OOS zip on slot A so i think the reason its not booting up to OOS is bc i need it flased on both slots ??

scoot0073 said:
this would not work for me im assuming bc i have the global HD1905 not the T Mobile branded. u can read above why it wouldn't work . but i seem to have made some progress using the All in One Tool i clicked on flash factory image tab and at first it keep error out saying no Flash-All.bat found after unzipping it. so i kelp looking around and finally foud a factory zip that had the Flash-All.bat file in it so tried again using the Allin One Tool clicked Flash Factory image and it unzipped it and flashed fine but now i cant boot to the OOS it just reboots to the " your bootloader is unlocked integrity screen and stays . but i can boot in fastboot mode and recovery which is now factory recovery. i noticed that it flashed the OOS zip on slot A so i think the reason its not booting up to OOS is bc i need it flased on both slots ??
Click to expand...
Click to collapse
[OP7T][OOS 11.0.5.1 HD65AA/BA] Unbrick tool to restore your device to OxygenOS
Disclaimer: By attempting any of the processes listed in this thread you accept full responsibility for your actions. I will not be held responsible if your device stops working, catches fire, or turns into a hipster and claims to have been...
forum.xda-developers.com

using the " All in One Tool "
Flashing is not allowed for Critical Partitions
is this normal error when flashing back to stock OOS ? when the flashing starts it says this for the first 4 or 5 flashing parts then it stats flashing as described in OP. then it reboots out of fastboot and boots to stock recovery then it finishes the flashing . then at the end it says to press any key to continue and the phone reboots and hangs at the screen that lets me know the bootloader is unlock screen. i flashed both a \b partitions and still does the same thing. its like the boot image is not flashing or im missing something else in the OP to get back to stock OOS.
anyone can help me please ?

"Fastboot reboot fastboot" will enter fastbootD mode to allow flashing system parts

HueyT said:
"Fastboot reboot fastboot" will enter fastbootD mode to allow flashing system parts
Click to expand...
Click to collapse
ok that command worked it successfully Flashed all partitions and when it it it finished it said to press any key to continue .... i did and it rebooted into stock recovery and finished the flashing . then it reboots to the Your Bootloader is unlocked warning and stays there . so i went into recovery and factory reset everything and still hangs at the bootloder unlocked warningthat was all on Slot b so i was like maybe i need to flash both Slots so i switched to slot a active and repeated the whole process above and still nothing hangs again at the bootloader is unlocked warning... ggggrrrrr
what gives..... this is all done using the All in One Tool ... i know im getting close to getting it back to Stock OOS as i made progress with your help.
i then downloaded the factory image from OnePlus site but that was a no go as the zip had only something called Payload which wouldn't flash ..
anymore knowledge u might can share and thank you very much for your help

Go back to fastbootD and flash-all parts manually on A slot, then go to bootloader, type "fastboot set_active other" to go into B slot and repeat fastbootD flashing all parts again. Then go into stock recovery to format data and then reboot

HueyT said:
Go back to fastbootD and flash-all parts manually on A slot, then go to bootloader, type "fastboot set_active other" to go into B slot and repeat fastbootD flashing all parts again. Then go into stock recovery to format data and then reboot
Click to expand...
Click to collapse
that did it im back to all stock oos thank you so much buddy couldn't have doe it without your knowledge. crazy that none of the tools didn't work mine must have been a rare odd ball that i had to flash everything manually.
again thank you.

Question Poco f3 Error: Sending modem_ab

good evening
I have been trying to return to stock miui from Pixel Experience since yesterday but get this error every time I try to flash the Firmware and do not know what I can do about it. I would be happy if somebody knew what this error is from and what might fix it.

Same problem. Don't try more things because you will brick your phone like mine.

Thanks for your reply. What did you do that bricked your Phonem? This way I know what to avoid. Thanks you in advance

As you are sure your device is a eea one, try with this last official stable firmware : Version: V13.0.7.0.SKHEUXM
You can find it here https://new.c.mi.com/global/miuidownload/detail/device/1900394
Fastboot version here at bottom : https://xiaomifirmwareupdater.com/miui/alioth/stable/V13.0.7.0.SKHEUXM/
Or https://bigota.d.miui.com/V13.0.7.0...EUXM_20220627.0000.00_12.0_eea_e461331a7d.tgz

Thanks you so much I will try that

and i did not mention this but I started this whole project of returning to miui because my poco was and still is in a bootloop and is only accessible over fastboot, not recovery and even though it sometimes gets to the system it almost instantly crashes and reboots

Still the Same Error unfortunatelly

nockcx said:
and i did not mention this but I started this whole project of returning to miui because my poco was and still is in a bootloop and is only accessible over fastboot, not recovery and even though it sometimes gets to the system it almost instantly crashes and reboots
Click to expand...
Click to collapse
Ok,
Do you have any idea what you did that may have caused this bootloop ?
Have you used any Qualcomm Tools or any soft in EDL mode ?

No, I did not do anything that would mess with the system to my knowledge . which is why i really do not know what to do. Can This Error occur because of a USB 3.0 used to flash? The Phone even tries to reboot when it is detected as a Fastboot device, maybe This has Something to do with it. Maybe it loses the Connection and therefore the flashing process stops. Are there possible ways to fix This?

Try with the latest android platform tools.
Put the content of platform tools archive in the fastboot folder and launch flash_all.bat don't use flash_all_lock

Still the Same Error . Can This be because of a Driver or a hardware issue?

i had similar issues but with the super partition when trying to flash from cmd.
flashing with miflash instead solved it.

It doesnt seem to make any difference to the error whether i flash it via cmd or miflash

nockcx said:
Still the Same Error . Can This be because of a Driver or a hardware issue?
Click to expand...
Click to collapse
Maybe : So as you can try with other PC, USB cable, USB connector, reinstall USB drivers...

I already tried with two Notebooks, I will try again tomorrow with another PC and installing USB drivers again. Thank you

You could try redownloading the MIUI ROM... you got it from xiaomifirmwareupdater.com right?
And yes ^^, try other PCs/laptops and other USB-cables.
Just please make sure
Unfortunately, Fastboot-Flashing is a gamble. It's not a solid protocol. It has zero protection against sudden USB-connection loss.
And manufacturers like Xiaomi go out of their way and block Qualcomm's EDL Mode, which is the only way to recover your phone in case Fastboot Mode stops working, because that Mode itself can also get damaged.

Fixed - first flash a miui recovery rom from twrp make sure the rom version lower than the latest one, now flash and boot miui , now just update from miui updater once you updated to the latest version , now try to flash the fastboot rom that you trying to flash, it should work.

I cant access a bootloader like TWRP because the phone still keeps rebooting after a couple of seconds in the bootloader so i cant really do much. I only have access to fastboot

nockcx said:
just flash a custom vbmeta and then install a custom recovery in to the boot partition like fastboot flash boot ....flash both the slots boot_a and boot_b the run fastboot reboot recovery do all this with latest platform tools
Click to expand...
Click to collapse

okay Im as far as I have never been with a very weird method, maybe somebody can explain. Because my poco always wants to reboot I found out a way to keep in in Fastboot mode. I repeatedly press the power and volume down button, This way it stays on for a lot longer, but it still is not enough to succeed at flashing the rom. It also lets me believe that my problem is not a software but probably a hardware problem, otherwise and cannot explain this suuuper weird behavior. what do you guys think? is there a possible fix you know?