I'm officially unlocked, today my sims weren't working and the phone was stuck on activate phone. Since without internet it wouldn't work, I somehow cleared config files and used command fast boot -w and now I don't get to see recovery, tried to flash each one through fast boot. But when I go to recovery, it just shows our phone with data cable unplugged and plugged according to data cable.
Anyone have any idea to correct this thing? Messing up with my mind from morning itself.
Sent from my Redmi Note 3 using Tapatalk
Is your bootloader unlocked?
s-u-f-f-e-r said:
Is your bootloader unlocked?
Click to expand...
Click to collapse
Yes it is.
Is it possible for recovery to get locked somehow?
Some game showed up once while I went to recovery, like Tetris. After that this all happened
Sent from my Redmi Note 3 using Tapatalk
Never heard of it.
Try not to install the recovery. Just boot into it.
fatboot boot and the name of the image.
For example
fastboot boot twrp.img
And try with recovery from another source like twrp.me
Navi44 said:
I'm officially unlocked, today my sims weren't working and the phone was stuck on activate phone. Since without internet it wouldn't work, I somehow cleared config files and used command fast boot -w and now I don't get to see recovery, tried to flash each one through fast boot. But when I go to recovery, it just shows our phone with data cable unplugged and plugged according to data cable.
Anyone have any idea to correct this thing? Messing up with my mind from morning itself.
Sent from my Redmi Note 3 using Tapatalk
Click to expand...
Click to collapse
Ok , try . Boot into fastboot check weather your bootloader is unlocked or not .
If unlocked .
Download stable or dev rom for mi website .
Make sure you have all the drivers installed.
Flash it using Miflash tool via the edl mode . It should fix all your issues . *Recovery,kernel,etc* : *It will lock the bootloader , unlock it again *
ps: you can go to edl mode from fastboot also . *Google it* .
Manoj Rocker said:
Ok , try . Boot into fastboot check weather your bootloader is unlocked or not .
If unlocked .
Download stable or dev rom for mi website .
Make sure you have all the drivers installed.
Flash it using Miflash tool via the edl mode . It should fix all your issues . *Recovery,kernel,etc* : *It will lock the bootloader , unlock it again *
ps: you can go to edl mode from fastboot also . *Google it* .
Click to expand...
Click to collapse
Actually the problem was something else. I unlocked bootloader and flashed almost every mi rom through edl, nothing worked.
At last I locked bootloader with command and then unlocked it with miunlock, that did the trick.i got it working now.
Thanks bro.
Earlier it always showed bootloader unlocked. Somehow lp and mm bootloader are different that must have caused the issue.
Sent from my Redmi Note 3 using Tapatalk
Navi44 said:
Actually the problem was something else. I unlocked bootloader and flashed almost every mi rom through edl, nothing worked.
At last I locked bootloader with command and then unlocked it with miunlock, that did the trick.i got it working now.
Thanks bro.
Earlier it always showed bootloader unlocked. Somehow lp and mm bootloader are different that must have caused the issue.
Click to expand...
Click to collapse
Glad it worked for you
How you did unlock officially
Sent from my Redmi Note 3 using Tapatalk
Camlin3 said:
How you did unlock officially
Sent from my Redmi Note 3 using Tapatalk
Click to expand...
Click to collapse
Submitted request On miunlock website. Got confirmation after 3 days. And unlocked it
Sent from my Redmi Note 3 using Tapatalk
Hey all use alka twrp by cofface....it won't lock again and again....every thing stays as old methods....once you are on twrp(alka).
Sent from my Redmi Note 3 using XDA-Developers mobile app
---------- Post added at 09:24 AM ---------- Previous post was at 09:21 AM ----------
Navi44 said:
Submitted request On miunlock website. Got confirmation after 3 days. And unlocked it
Sent from my Redmi Note 3 using Tapatalk
Click to expand...
Click to collapse
I even got permission without applying....first time I got 50 percent error...no time and I left it....once after 3-5 I tried it worked....really don't know what happened.it unlocked in less than a minute.
Sent from my Redmi Note 3 using XDA-Developers mobile app
pranavateja99 said:
Hey all use alka twrp by cofface....it won't lock again and again....every thing stays as old methods....once you are on twrp(alka).
Sent from my Redmi Note 3 using XDA-Developers mobile app
---------- Post added at 09:24 AM ---------- Previous post was at 09:21 AM ----------
I even got permission without applying....first time I got 50 percent error...no time and I left it....once after 3-5 I tried it worked....really don't know what happened.it unlocked in less than a minute.
Sent from my Redmi Note 3 using XDA-Developers mobile app
Click to expand...
Click to collapse
Mi must have changed unlock policy. Now thy are making a tool in which u will get permission in 5 mins.
Actually my problems happened because i flashed a couple of fastboot ROMs back to back. Bootloader was messed up, lp mm and so on
Sent from my Redmi Note 3 using Tapatalk
Navi44 said:
Mi must have changed unlock policy. Now thy are making a tool in which u will get permission in 5 mins.
Actually my problems happened because i flashed a couple of fastboot ROMs back to back. Bootloader was messed up, lp mm and so on
Sent from my Redmi Note 3 using Tapatalk
Click to expand...
Click to collapse
How come bootloader get effected when it's locked...just reset your phone..may be multiple incompatible iterations of Same app from different builds causing error..
Sent from my Redmi Note 3 using XDA-Developers mobile app
pranavateja99 said:
How come bootloader get effected when it's locked...just reset your phone..may be multiple incompatible iterations of Same app from different builds causing error..
Sent from my Redmi Note 3 using XDA-Developers mobile app
Click to expand...
Click to collapse
I flashed through edl mode, how can multiple iteration of apps can be a problem. Anyways its solved for me, many guys got into this problem too.
Sent from my Redmi Note 3 using Tapatalk
Related
Recently just received a warranty replacement Note 2 and of course first thing I did was root and unlock it. After flashing a rom a indicator would pop up saying TWRP had lost root permissions and after selecting okay, fix permissions for it. I wrote it off not thinking much of it but after flashing a different rom the same pop up appeared again, still no problems. Finally my phone started locking up and today it eventually bricked up as I flashed a rom. No biggie, I flashed back to stock and am good to go but I just want to know if anyone else has come across this same issue as well?
Sent from my SCH-I605 using Tapatalk 4 Beta
endo689 said:
Recently just received a warranty replacement Note 2 and of course first thing I did was root and unlock it. After flashing a rom a indicator would pop up saying TWRP had lost root permissions and after selecting okay, fix permissions for it. I wrote it off not thinking much of it but after flashing a different rom the same pop up would appear again, still no problems. Finally my phone started locking up and today it eventually bricked up as I flashed a rom. No biggie, I flashed back to stock and am good to go but I just want to know if anyone else has come across this same issue as well?
Sent from my SCH-I605 using Tapatalk 4 Beta
Click to expand...
Click to collapse
Only time I've seen this it has been an issue with the rom I'm flashing.
Sent from my SAMSUNG-SGH-I957 using xda app-developers app
jd1639 said:
Only time I've seen this it has been an issue with the rom I'm flashing.
Sent from my SAMSUNG-SGH-I957 using xda app-developers app
Click to expand...
Click to collapse
For some reason it happened with every rom I would flash. Possibly mucked something up when I rooted and unlocked in the first place.
Sent from my SCH-I605 using Tapatalk 4 Beta
I is twrp that causes the issue, if I'm mistaken they have updated to fix that bug.
M.A.D.NoTe.||
Going through the exact same thing right now, same situation and all, did you get this worked out? I flashed back to stock just a couple minutes ago and am now in the process of flashing a custom rom again. Never experienced this before and been flashing on this phone the Note 2 since October. New phone, new problem. Used the Toolkit to do everything every time I get a new phone. This is my third.
StevetotheH said:
Going through the exact same thing right now, same situation and all, did you get this worked out? I flashed back to stock just a couple minutes ago and am now in the process of flashing a custom rom again. Never experienced this before and been flashing on this phone the Note 2 since October. New phone, new problem. Used the Toolkit to do everything every time I get a new phone. This is my third.
Click to expand...
Click to collapse
Sorry for such a long delay in responding. I found a fix for this issue. I ended up just flashing all the way back to the original stock rom when the Note 2 was released then went about using the unlocking/rooting methods and have not ran into a single problem.
Sent from my SCH-I605 using Tapatalk 4 Beta
endo689 said:
Sorry for such a long delay in responding. I found a fix for this issue. I ended up just flashing all the way back to the original stock rom when the Note 2 was released then went about using the unlocking/rooting methods and have not ran into a single problem.
Sent from my SCH-I605 using Tapatalk 4 Beta
Click to expand...
Click to collapse
I was having this issue a few days ago and formatting my internal SD with TWRP and reflashing my ROM fixed it.
Sent from my SCH-I605 using XDA Premium HD app
I wipe internal every time along with the normal wipes when I flash a rom. Gives you the best chance of everything being stable and having a great gps lock even on aosp or tablet roms
Sent from my SCH-I605 using Tapatalk 2
hopesrequiem said:
I wipe internal every time along with the normal wipes when I flash a rom. Gives you the best chance of everything being stable and having a great gps lock even on aosp or tablet roms
Sent from my SCH-I605 using Tapatalk 2
Click to expand...
Click to collapse
I do this as well but for some reason twrp still lost root permissions.
Oh well having no issues anymore so I am a happy camper.
Sent from my SCH-I605 using Tapatalk 4 Beta
USB connection problems
Now I keep running into USB driver issues as of late. Don't understand why this keeps happening. Uninstalled and reinstalled all drivers and Note 2 connects for awhile and then completely stops. I can browse/edit items on the phone but cannot copy files over to it. A pop up saying it has been disconnected and cannot copy files to said device. WTF?!
endo689 said:
Now I keep running into USB driver issues as of late. Don't understand why this keeps happening. Uninstalled and reinstalled all drivers and Note 2 connects for awhile and then completely stops. I can browse/edit items on the phone but cannot copy files over to it. A pop up saying it has been disconnected and cannot copy files to said device. WTF?!
Click to expand...
Click to collapse
What OS you on? Try a different cable and different usb port. Use the drivers from mskips all in one tool from the forum. Have you tried adb devices to see if it recognizes your device? If you haven't rebooted you rig lately do that and your device as well. I had this happen for a minute on Win8 I had to manually point the driver update to the file I wanted to use.
Rock, Flag and Eagle!
Way back when I got my Note 2.... the version of casual actually flashed a wrong TWRP , it was the one for the international Note 2.
The fix was to simply install the newest TWRP for our phone (SCH-i605)
Milimbar said:
Way back when I got my Note 2.... the version of casual actually flashed a wrong TWRP , it was the one for the international Note 2.
The fix was to simply install the newest TWRP for our phone (SCH-i605)
Click to expand...
Click to collapse
What?
Rock, Flag and Eagle!
StevetotheH said:
What OS you on? Try a different cable and different usb port. Use the drivers from mskips all in one tool from the forum. Have you tried adb devices to see if it recognizes your device? If you haven't rebooted you rig lately do that and your device as well. I had this happen for a minute on Win8 I had to manually point the driver update to the file I wanted to use.
Rock, Flag and Eagle!
Click to expand...
Click to collapse
I will definitely give this a shot when I have a chance.
Sent from my SCH-I605 using Tapatalk 4 Beta
Make sure youre using the latest TWRP version.
Hi all, I switched from Fastboot mode to bootloader mode and captured this image. Could someone please help me to understand why this is happening ?
leoaudio13 said:
Hi all, I switched from Fastboot mode to bootloader mode and captured this image. Could someone please help me to understand why this is happening ?
Click to expand...
Click to collapse
Completely normal. That's only used if you purposely put an ruu file on your sd card for hboot to run. Therefore, unless you plan to do just that, it should never find one of those.
Sent from my HTC6600LVW using Tapatalk
dottat said:
Completely normal. That's only used if you purposely put an ruu file on your sd card for hboot to run. Therefore, unless you plan to do just that, it should never find one of those.
Sent from my HTC6600LVW using Tapatalk
Click to expand...
Click to collapse
Thank you for your fast reply. 1 quick question : I tried to flash RUU zip via fastboot, during process of flashing, phone flashed fine and completed. But after checking logs on CMD screen, some of partitions were failed to flash ( radio, system and main partitions flashed fine ). Is it also normal ?
leoaudio13 said:
Thank you for your fast reply. 1 quick question : I tried to flash RUU zip via fastboot, during process of flashing, phone flashed fine and completed. But after checking logs on CMD screen, some of partitions were failed to flash ( radio, system and main partitions flashed fine ). Is it also normal ?
Click to expand...
Click to collapse
Whether flashing it from fastboot or flashing it from boot loader it needs to run twice.
Sent from my HTC6600LVW using Tapatalk
P605
Sent from my SM-P605 using XDA Premium 4 mobile app
afshari1974 said:
P605
Sent from my SM-P605 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
What do you mean Sir ?
I'm sorry dear, it was a mistake. Thank you.
rooted p605
I flashed my phone to a newer version of CM 12.1 that I found here:
http://android.cmphys.com/cyanogenmod-fireball/
it was an attempt to fix an issue with my data network. This build included a patch for the Fireball Radio. A few hours after the flash, I tried making a call. I have a signal but the phone says "Cellular network not available". I've restored a backup of the previous ROM, wiped cache and reseated the SIM. Still having the same problem. The phone is Straight Talk/Verizon using CDMA/LTE. Before I ditch the phone, is there anything else I can try? Would going back to stock ROM change anything? I've not touched baseband, etc unless they are port of the ROM I installed. I like the phone but I also need one that works.
Try returning to stock http://android.cmphys.com/stock-fireball/ or search for the ruu here to see if that helps. And make sure you have the most updated firmware 2.19.605.2.zip
Sent from my Nexus 7 WiFi using XDA Free mobile app
wmuflyer said:
Try returning to stock http://android.cmphys.com/stock-fireball/ or search for the ruu here to see if that helps. And make sure you have the most updated firmware 2.19.605.2.zip
Sent from my Nexus 7 WiFi using XDA Free mobile app
Click to expand...
Click to collapse
the phone is s-off boot loader unlocked and partition swapped. I know I have to reverse the partition swap. Do I need to relock bootloader, etc or will the stock ROM work after the partitions are swapped back?
Trying to update firmware, I am using these step
Reboot the device to HBOOT: adb reboot-bootloader
Enter the OEM update mode: fastboot oem rebootRUU
Flash the firmware package. cd to the directory containing fireball-firmware-2.19.605.2.zip and run:
fastboot flash zip fireball-firmware-2.19.605.2.zip
Wait for the process to finish
Reboot the phone: fastboot reboot
I get to step 2, and my laptop says it is waiting for device. am I supposed to do anything on the phone or just wait?
Just swapping partitions back should work.
Sent from my Nexus 7 WiFi using XDA Free mobile app
---------- Post added at 09:05 PM ---------- Previous post was at 09:04 PM ----------
Did you get stock recovery installed?
Sent from my Nexus 7 WiFi using XDA Free mobile app
wmuflyer said:
Just swapping partitions back should work.
Sent from my Nexus 7 WiFi using XDA Free mobile app
---------- Post added at 09:05 PM ---------- Previous post was at 09:04 PM ----------
Did you get stock recovery installed?
Sent from my Nexus 7 WiFi using XDA Free mobile app
Click to expand...
Click to collapse
Do I need stock recovery? I was hoping to just update the firmware and see if that fixes it. Do I need stock recovery to flash stock ROM and/or the firmware?
If I remember correctly the ruu command requires the stock recovery.
Sent from my Nexus 7 WiFi using XDA Free mobile app
wmuflyer said:
If I remember correctly the ruu command requires the stock recovery.
Sent from my Nexus 7 WiFi using XDA Free mobile app
Click to expand...
Click to collapse
ok thanks. I can;t hurt the phone any more than it already is.
I figured it out. I'm in Linux and had to su to root to get fastboot to flash anything. oddly, the reboot commands just fine when I'm not root.
So, were you successful getting your voice connection back?
Nexus 5 Chroma
No. And it doesn't appear I was successful at flashing firmware either. The phone still says I am version 1.5 I tried flashing stock recovery then repeating the firmware flash. I am going to be looking for a new phone today.
Gets another option to try http://forum.xda-developers.com/showthread.php?t=2759010
Sent from my Nexus 7 WiFi using XDA Free mobile app
I replaced the phone today. I am on call tonight and tomorrow and needed a working phone. I could use a land line but it would be painful. thanks for all the help. I spent some time on the phone last night with Verizon. I'm wondering if either they figured out the phone was unlocked or its just older so they flipped a bit somewhere to keep it from connecting. I could also try a GSM SIM and may keep the phone for if I ever travel international.
Yeah, Verizon is slightly fishy that way, on mine two days before my contract was up my LTE just stopped working. Good luck with the new phone.
Sent from my Nexus 7 WiFi
try
crokett said:
I flashed my phone to a newer version of CM 12.1 that I found here:
http://android.cmphys.com/cyanogenmod-fireball/
it was an attempt to fix an issue with my data network. This build included a patch for the Fireball Radio. A few hours after the flash, I tried making a call. I have a signal but the phone says "Cellular network not available". I've restored a backup of the previous ROM, wiped cache and reseated the SIM. Still having the same problem. The phone is Straight Talk/Verizon using CDMA/LTE. Before I ditch the phone, is there anything else I can try? Would going back to stock ROM change anything? I've not touched baseband, etc unless they are port of the ROM I installed. I like the phone but I also need one that works.
Click to expand...
Click to collapse
try this http://forum.xda-developers.com/showthread.php?t=2770176
just flashing
Hi,
i have to revert my note 3 pro to stock miui. I want to revert everything, including radio/Firmware and recovery.
In my understanding i have to:
- flash miui global dev via miflash in fastboot mode
- reunlock my bootloader (if i want)
Thats all? Does this work, even when i'm on Nougat cm firmware?
Thanks!
Sent from my Redmi Note 3 using XDA-Developers mobile app
you also can flash miui recovery rom from twrp, personally i am like miui.eu rom.
Thanks, but thats not an Option because my microphone does not work. It doesnt matter which Rom i try, even backups dont work. Thats why i want to revert everything.
I have read many threads and tutorials and i think i have to revert back to miui via fastboot edl mode. Maybe somebody could confirm this?
Sent from my Redmi Note 3 using XDA-Developers mobile app
desmoloch said:
Thanks, but thats not an Option because my microphone does not work. It doesnt matter which Rom i try, even backups dont work. Thats why i want to revert everything.
I have read many threads and tutorials and i think i have to revert back to miui via fastboot edl mode. Maybe somebody could confirm this?
Sent from my Redmi Note 3 using XDA-Developers mobile app
Click to expand...
Click to collapse
yes...i can confirmed it...you'll revert everything into stock including recovery, firmware & also relock your bootloader.
I recently purchased the me max 2 x829. I had twrp 3.1.1.0 installed and tried out MIUI just fine. I later restored my backup and went to install small eui. After doing so the stock recovery is what my phone would boot into when trying to boot into recovery. I've tried reinstalling twrp but when booting into recovery I just get a blue led and on the next attempt I get the stock recovery again. Any help? I'm currently running the 16s Indian stock rom
Sent from my Nexus 5X using Tapatalk
GenoAndroid said:
I recently purchased the me max 2 x829. I had twrp 3.1.1.0 installed and tried out MIUI just fine. I later restored my backup and went to install small eui. After doing so the stock recovery is what my phone would boot into when trying to boot into recovery. I've tried reinstalling twrp but when booting into recovery I just get a blue led and on the next attempt I get the stock recovery again. Any help? I'm currently running the 16s Indian stock rom
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
I haven't read anything about but I also had problems with this twrp version. My first attempt was just booting it and I got the same blue led with no response. Fastboot commands were not being recognized as well. So I tried the second most recent version, which worked smoothly.
The last one e quite smaller so I was afraid it could be corrupted. Not sure about it.
Sent from my Le X820 using Tapatalk
razmth said:
I haven't read anything about but I also had problems with this twrp version. My first attempt was just booting it and I got the same blue led with no response. Fastboot commands were not being recognized as well. So I tried the second most recent version, which worked smoothly.
The last one e quite smaller so I was afraid it could be corrupted. Not sure about it.
Sent from my Le X820 using Tapatalk
Click to expand...
Click to collapse
I'll test the previous recent version and report back.
Sent from my Le X821 using Tapatalk
razmth said:
I haven't read anything about but I also had problems with this twrp version. My first attempt was just booting it and I got the same blue led with no response. Fastboot commands were not being recognized as well. So I tried the second most recent version, which worked smoothly.
The last one e quite smaller so I was afraid it could be corrupted. Not sure about it.
Sent from my Le X820 using Tapatalk
Click to expand...
Click to collapse
So. I had the version numbers wrong. I was trying to install the most recent 3.1.1.1 to no avail. I pushed 3.1.1.0 to the phone via fastboot with no issues and currently running miui again. Thanks for your help [emoji2]
Sent from my Le X820 using Tapatalk