Database Develop

[Q][GT-I9001] Ivendor CM10 plus CastagnaIT Kernel (from Softreboot to Hardbrick)

Hello everyone,
I just hardbricked my SGS+ and now I'm a bit curious how this could happen.
This is what I did:
I used to run CM9 RC5 from arco68 along with the Kernel for ICS from Christopher83 and CWM 6.0.1.2.
Because my phone always lost the wifi-connection and also had some freezes I decided to try out CM10 Beta 3 from ivendor.
I backuped my phone, downloaded the zips and even verified the MD5sums. Next I flashed CWM 6.0.1.9 as recommended in the thread from ivendor.
After exporting the nandroid backup and other stuff like photos to my computer I wiped everything as mentioned in the thread, flashed the two zips and rebooted. Everything went fine and I was almost ready with setting up my phone again when I got my first softreboot.
Suddenly it showed the CM-bootlogo and after maybe 10 seconds I was back on my homescreen. I got another two or three softreboots until I decided to flash the Kernel 3.x from CastagnaIT.
I rebooted into recovery, wiped cache and dalvik cache, flashed the zip and rebooted.
Now I wanted to reboot into recovery again to fix permissions but instead I got a softreboot and my phone stuck at the CM10 bootlogo.
I waited for around 5 minutes and then I just turned the phone off and booted into the recovery mode.
Because I wanted a clean install without any problems like softreboots I decided to wipe my phone again (data, cache, system) and just reflash the zip for CM10. And at this point everything went wrong.
I flashed CM10 but when I tried to flash gapps my phone just turned off. And no, the battery was not empty. In fact the battery was at around 50-60% and my phone was also connected to my computer.
I tried to turn on my phone but now it stuck at the Samsung bootlogo.
The next thing I did was probably a horrible mistake. I tried to un-brick my phone but I did not realize that I could boot into download mode without problems so I guess my phone wasn't softbricked at all.
Well, after that I still stuck at the Samsung bootlogo and couldn't enter recovery mode. I got into download mode somehow and maybe this was my second mistake. I tried to flash the "i9001Reset.zip" via Odin. Everything went fine but when Odin said "Close serial port and wait until rebooting" my phone was completely dead. I think it was while I tried to flash the reset-file when I got a message like "MBR: read failed". So somehow I managed to destroy my master boot record.
Now I can't turn on my phone or enter download nor recovery mode. I already removed the battery for about 45 minutes but this didn't work either.
My phone is dead but at least I saved the important data and maybe I'll get a new one through warranty. Or I just buy a Nexus 4.
My questions are:
What did I do wrong especially when I tried to save my phone?
How can I prevent such things from happening?
And at which point I should have got help here in the forum or elsewhere?
I would really appreciate some tips for the future because I already flashed and used a lot of different ROMs but this is the first time something really went wrong.
Thanks for reading and thanks for your help in advance.
(Please excuse my non-perfect englisch.)
Greetings,
Mangoniter

Problem restarting Galaxy Note

Hi guys
I have a problem with my Note. I have installed several roms over the last year without any problems. Recently though I had a problem. I had been using about a week or two the ROM SuperNexus but a few days ago the powerbutton started not to work. It would at some moments work and some other moments it wouldn't. Very frustrating. I reinstalled the ROM, still didn't help. Then I installed a different ROM. It worked but not for long. Now it also started to reboot itself every 5 minutes or so. No idea why. I decided then to flash a new kernel. Abyss didn't work like I wanted so I installed Speedmod kernel and then installed the stock JB rom. Now that worked all fine and well. No problems at all, but the weird thing is when it gets to about 20-30% on battery, it reboots and then gets stuck at the bootscreen.
Why would this be? I'm afraid there is something really wrong with the phone. Does anyone have an idea what this could be or how I may be able to fix it?
Thanks in advance
Daniel
Edit: Also should not when it gets stuck at boot, wiping data/reset factory helps. Also when it's stuck at the bootscreen, it does get warm I find.

I just did a test with the App eMMC BrickBug Test and it said that Yes. Insane chip.

DanielG27 said:
Hi guys
I have a problem with my Note. I have installed several roms over the last year without any problems. Recently though I had a problem. I had been using about a week or two the ROM SuperNexus but a few days ago the powerbutton started not to work. It would at some moments work and some other moments it wouldn't. Very frustrating. I reinstalled the ROM, still didn't help. Then I installed a different ROM. It worked but not for long. Now it also started to reboot itself every 5 minutes or so. No idea why. I decided then to flash a new kernel. Abyss didn't work like I wanted so I installed Speedmod kernel and then installed the stock JB rom. Now that worked all fine and well. No problems at all, but the weird thing is when it gets to about 20-30% on battery, it reboots and then gets stuck at the bootscreen.
Why would this be? I'm afraid there is something really wrong with the phone. Does anyone have an idea what this could be or how I may be able to fix it?
Thanks in advance
Daniel
Edit: Also should not when it gets stuck at boot, wiping data/reset factory helps. Also when it's stuck at the bootscreen, it does get warm I find.
Click to expand...
Click to collapse
1. Boot your phone in recovery and flash the latest kernel from here
http://forum.xda-developers.com/showthread.php?t=1789397
2. Restart and allow some time to settle.
3. reboot and do wipe data /factory reset, wipe cache, wipe dalvik
4. Use pc Odin to flash stock ROM from sammobile.com
5. Check if it works and update...

[Q] i9305 newest cyanogenmod does not boot

Hi.
Since yesterday my galaxy s3 lte i9305 does not boot anymore, the blue cyanogenmod logo keeps turning for hours. I can however still go to the recovery (which was a few month old cwm). I completely wiped the phone (both caches, data, internal sd, boot, firmware etc ... all but the modem) and reinstalled the newest cwm and the newest nightly build three times now using heimdall and the external sd (connected my external micro sd to my computer sd card reader via adapter and put the zip on it). Just now I installed twrp-2.8.5.0-i9305 as a new recovery and installed everything again, but everytime - and also now - despite the seemingly successful installation, the phone is stuck at the cyanogen bootlogo.
Any ideas on how to get my phone running again?
Cheers

ScPo said:
Hi.
Since yesterday my galaxy s3 lte i9305 does not boot anymore, the blue cyanogenmod logo keeps turning for hours. I can however still go to the recovery (which was a few month old cwm). I completely wiped the phone (both caches, data, internal sd, boot, firmware etc ... all but the modem) and reinstalled the newest cwm and the newest nightly build three times now using heimdall and the external sd (connected my external micro sd to my computer sd card reader via adapter and put the zip on it). Just now I installed twrp-2.8.5.0-i9305 as a new recovery and installed everything again, but everytime - and also now - despite the seemingly successful installation, the phone is stuck at the cyanogen bootlogo.
Any ideas on how to get my phone running again?
Cheers
Click to expand...
Click to collapse
I would try a factory reset from recovery and see if that helps. You did check the md5 for your downloads right?
Otherwise I would install the stock rom, then try again, this time(making sure you have a compatible recovery) just wipe caches, data, and format system, and then install CM

noppy22 said:
I would try a factory reset from recovery and see if that helps. You did check the md5 for your downloads right?
Otherwise I would install the stock rom, then try again, this time(making sure you have a compatible recovery) just wipe caches, data, and format system, and then install CM
Click to expand...
Click to collapse
I did do the factory reset. I just wiped the areas separately as well. Anyway, I took your advice and installed the latest stock rom. Now I got the Samsung logo slightly flashing blue for hours instead of the cyanogenmod logo. Did not do anything else.
I suspect that its a battery issue in some way. The last weeks the phone lost its charge very quickly very often (not constantly though). Yesterday, the phone was in my pocket and then went off. It went into the constantly trying to restart despite the lack of batteries state until I removed the battery. Maybe that gives any clue?

ScPo said:
I did do the factory reset. I just wiped the areas separately as well. Anyway, I took your advice and installed the latest stock rom. Now I got the Samsung logo slightly flashing blue for hours instead of the cyanogenmod logo. Did not do anything else.
I suspect that its a battery issue in some way. The last weeks the phone lost its charge very quickly very often (not constantly though). Yesterday, the phone was in my pocket and then went off. It went into the constantly trying to restart despite the lack of batteries state until I removed the battery. Maybe that gives any clue?
Click to expand...
Click to collapse
Try booting into stock recovery, then factory reset from there. Last time I went back to stock I had a bootloop until I did this, then it booted properly. If that doesn't work, maybe try new battery.
Have you tried booting up whilst plugged in to a usb charger?

noppy22 said:
Try booting into stock recovery, then factory reset from there. Last time I went back to stock I had a bootloop until I did this, then it booted properly. If that doesn't work, maybe try new battery.
Have you tried booting up whilst plugged in to a usb charger?
Click to expand...
Click to collapse
Thanks for your helpful input.
I did what you said, even tried it twice now. Phone is still booting after 20 minutes now. I also tried booting up while charging the phone, yes. That was my standard procedure actually, but nothing changes when I unplug it. I don't have a different battery and I am wary of buying one just for the sake of trying. Tried that when my galaxy s 1 broke down and that didn't save the phone. At this point I am contemplating if the phone (s3) is broken now or not. It still reliably boots to the recovery, but it doesn't do much else. How are the chances?
Or has anyone any idea on how to proceed?

ScPo said:
Thanks for your helpful input.
I did what you said, even tried it twice now. Phone is still booting after 20 minutes now. I also tried booting up while charging the phone, yes. That was my standard procedure actually, but nothing changes when I unplug it. I don't have a different battery and I am wary of buying one just for the sake of trying. Tried that when my galaxy s 1 broke down and that didn't save the phone. At this point I am contemplating if the phone (s3) is broken now or not. It still reliably boots to the recovery, but it doesn't do much else. How are the chances?
Or has anyone any idea on how to proceed?
Click to expand...
Click to collapse
Try to boot into recovery. Do a factory reset then boot straight into download mode and flash stock rom. You might have to redownload the firmware it could be corrupted.. If that doesn't work then you might have to send it in. It might cost about to fix. Or go to your local phone repair shop and see if they could fix it for cheaper
Sent from my GT-I9305 using XDA Forums

Phone's wifi connection causes modem to reset

Phone: Mi 5 64gb
This is crazy guys, after I flashed LOS, I wasn't able to connect to the wifi and whenever I do, the phone causes to reset and ruin the Internet for every temporarily. I thought it was just this phone so I went to shop and switched for a new one. And as soon as I flashed RR, guess what? Same thing happens. I'm so lost, what did I do wrong? These are the steps I took to flash custom ROMs. First, I unlocked bootloader and flash TWRP 3.0xx recovery. Next, I factory reset, wipe cache system data everything and flashed firmware, then ROM, finally the Gapps. I tried to flash back to official ROMs, the problem remained. I'm so screwed, don't know if the shop gonna let me switch to a new one, again.
P.S. on the bright side, I can mess with other's Wifi, make them unusable.
P.S. 2 during zip installing in TWRP, I saw two red lines like this "E:unknown command [log], detected filesystem ext4 for /dev/block/bootdevice/by-name/system, script succeeded: result was [1.000000]..." but it said done regardless

Question Xiaomi Note 11 stuck to rebooting into recovery mode 5.0 after unlocking the screen

Hi, sorry for the bad english. My Xiaomi Note 11 worked perfectly fine for months since I bought it, but last night I accidentally left it charging for the whole night and when I woke up, it suddenly rebooted to recovery mode. I rebooted it back to system, which reboots the phone as usual, then I unlocked the lockscreen, everything went perfectly normal, until it rebooted again to recovery mode. I tried rebooting again, but it rebooted again to recovery mode after I unlocked the lockscreen. I tried booting it to safemode, but it went the same way. However, when I leave the lockscreen unlocked, it doesn't reboot itself. I tried turning it off and rebooting it with the screen unlocked but it did nothing. Do you guys ever have the same problem? Is there any way to fix it without wiping the data? I have some banking apps and other data that would be difficult to recover if I were to wipe out the phone.

I have the same problem too, I think it might have to do with the new update Xiaomi pushed to European devices in the last few days. We'll have to wait and see if they push a fix/if we find a fix...

Exact same problem, started appearing today. This is so weird. I already wiped data and the problem persists; went thorough the setup with no issue, and as soon as I finished it and the phone goes to the main screen, after a few seconds it started appearing again.
MIUI Global
13.0.16.0(RGCMIXM)
Android ver: 11 RKQ1.211001.001

asabaraba said:
Exact same problem, started appearing today. This is so weird. I already wiped data and the problem persists; went thorough the setup with no issue, and as soon as I finished it and the phone goes to the main screen, after a few seconds it started appearing again.
MIUI Global
13.0.16.0(RGCMIXM)
Android ver: 11 RKQ1.211001.001
Click to expand...
Click to collapse
It's really weird that it happens to other people too!

AdonysGames said:
I have the same problem too, I think it might have to do with the new update Xiaomi pushed to European devices in the last few days. We'll have to wait and see if they push a fix/if we find a fix...
Click to expand...
Click to collapse
That might be it since it happens not only to me.

Same problem happening for me too from today. Anyone know a fix for it ?

hrishi654 said:
Same problem happening for me too from today. Anyone know a fix for it ?
Click to expand...
Click to collapse
Did a second data wipe and it worked this time, the phone's been running all night without any issue. I disabled xiaomi updates for the time being

Same issue here, please any solution, I've not been able to do anything since 48 hours

Is there a way to go through this without losing my data and files?

same problem i will try to wipe data again and see if it works

ReaperCat65 said:
Hi, sorry for the bad english. My Xiaomi Note 11 worked perfectly fine for months since I bought it, but last night I accidentally left it charging for the whole night and when I woke up, it suddenly rebooted to recovery mode. I rebooted it back to system, which reboots the phone as usual, then I unlocked the lockscreen, everything went perfectly normal, until it rebooted again to recovery mode. I tried rebooting again, but it rebooted again to recovery mode after I unlocked the lockscreen. I tried booting it to safemode, but it went the same way. However, when I leave the lockscreen unlocked, it doesn't reboot itself. I tried turning it off and rebooting it with the screen unlocked but it did nothing. Do you guys ever have the same problem? Is there any way to fix it without wiping the data? I have some banking apps and other data that would be difficult to recover if I were to wipe out the phone.
Click to expand...
Click to collapse
I didn't put mine to charge and this happened

mateuszzsa said:
same problem i will try to wipe data again and see if it works
Click to expand...
Click to collapse
Can you give us an update if it works? I also post the problem on Reddit and some people there were also able to fix it by wiping the data.

Will wiping the data fix the issue, if it does, please do let us know

Dr_toluwani said:
Will wiping the data fix the issue, if it does, please do let us know
Click to expand...
Click to collapse
47 minutes since i wiped the data by the second time and my phone its working, I don't know until when.

Does anyone know of way to save the data? Surely it must be accessibl.

ishouldbeworking said:
Does anyone know of way to save the data? Surely it must be accessibl.
Click to expand...
Click to collapse
I found a way to do so. The problem is that once the phone is unlocked you have a few minutes before it gets booted into recovery mode. So:
Step 1) Have the phone connected to a computer before booting it up, with file explorer in the "this pc" category (where the phone storage will appear)
Step 2) boot the phone and input the password (if any)
Step 3) QUICKLY pull down the notification bar and press the usb options notification
Step 4) QUICKLY press the second option for file transferring
Step 5) QUICKLY open phone storage from pc once it pops up (at this point the phone screen will probably be black with a white loading circle but the phone storage is still accessible!!! You now have a few minutes to transfer any data you want)
Step 6) QUICKLY search through phone storage for any important data and copy/paste it to your computer
Sooner or later the phone will be booted to recovery mode and the mi logo will appear and the phone storage will disappear from the computer so repeat above steps until all your data is backed up.
If a file transfer gets stopped while running, copy/paste the data again on the next "run" and choose to ignore files that are already copied. With this method I managed to backup all my photos and files before wiping the phone.

This problem might be due to a problematic firmware update. My phone was running MIUI version 13.0.12(RGKEUXM) (europe version). I wiped the data and updated my phone to version 13.0.13(RGKEUXM) after setting it up just in case. I will update this thread if the problem reappears.

I am running RGCMIXM (13.0.16.0) and have encountered the issue. Really annoying. Did the wipe all and had no success. I hope someone can help find a fix. No feedback on the issue i logged thru the feedback app to Xiaomi.

akallabeth said:
I am running RGCMIXM (13.0.16.0) and have encountered the issue. Really annoying. Did the wipe all and had no success. I hope someone can help find a fix. No feedback on the issue i logged thru the feedback app to Xiaomi.
Click to expand...
Click to collapse
did you try to perform 2 wipes? apparently my device is working properly after that.

mateuszzsa said:
did you try to perform 2 wipes? apparently my device is working properly after that.
Click to expand...
Click to collapse
Which wipe method did you do? Just a factory reset or a reflash?