Hey all,
I have a question concerning 2 devices (both SGS2, I9100) only bought at different stores (both stores certified etc etc, so figured it'd be completely safe).
Device 1: Nothing wrong with it, bought it and it was in Dutch immediately... I bought it last summer. I recently rooted it, wrote down exactly how I did it etc (I always do that, just in case). It's now working with custom ROM and themes etc etc. (MIUI multilang ROM)
Device 2: Strange thing #1 was the fact that it was in Polish, straight out of the box. So I had to skip the whole set up and change the language in settings first to Dutch. I then rooted it, exactly the same way as my Dutch device, and problems started. It showed the startup screen with the yellow triangle&black exclamation mark for about an hour(!!!) Figuring it wouldn't do anything anymore, I turned it off and booted in recovery mode (CWM)
Immediately it said it couldn't find the logs (no such file or directory) I then tried to have a look in the sdcard folder... Which couldn't be found either. Same thing with "system", "emmc", "factoryfs", "cache" etc etc.
I tried to flash it to stock Dutch ROM (after rebooting in download mode) and the whole process got stuck at 24%, it then ended completely leaving me with a new terminal line (I did all this using linux, just like Device 1, so lots of terminal work...) I then figured, as it got stuck on 24%, I could try flashing CWM again. Then it said the device couldn't be found anymore, while it was still in download mode. I unplugged the micro usb, plugged it back in (device still in download mode) and tried flashing CWM again... Once again, no device found. Then, stupid me, thought "let's reboot the phone!" Turning it off went well.... Turning it back on... Never again....
Now after a little brainstorming... I have these questions:
Could it be, since it was in Polish straight out of the box, that the device simply couldn't be rooted this way?
Will a JIG work?
IF the JIG works, will I still have problems, cause maybe the device was somehow a little different, concerning hardware or whatever if it is some sort of Polish device?
Please help... And please, don't hold back on as much information as you have, any info (even if it seems useless) might be useful after all!!
Many thanks in advance.
Dephiax said:
Hey all,
I have a question concerning 2 devices (both SGS2, I9100) only bought at different stores (both stores certified etc etc, so figured it'd be completely safe).
Device 1: Nothing wrong with it, bought it and it was in Dutch immediately... I bought it last summer. I recently rooted it, wrote down exactly how I did it etc (I always do that, just in case). It's now working with custom ROM and themes etc etc. (MIUI multilang ROM)
Device 2: Strange thing #1 was the fact that it was in Polish, straight out of the box. So I had to skip the whole set up and change the language in settings first to Dutch. I then rooted it, exactly the same way as my Dutch device, and problems started. It showed the startup screen with the yellow triangle&black exclamation mark for about an hour(!!!) Figuring it wouldn't do anything anymore, I turned it off and booted in recovery mode (CWM)
Immediately it said it couldn't find the logs (no such file or directory) I then tried to have a look in the sdcard folder... Which couldn't be found either. Same thing with "system", "emmc", "factoryfs", "cache" etc etc.
I tried to flash it to stock Dutch ROM (after rebooting in download mode) and the whole process got stuck at 24%, it then ended completely leaving me with a new terminal line (I did all this using linux, just like Device 1, so lots of terminal work...) I then figured, as it got stuck on 24%, I could try flashing CWM again. Then it said the device couldn't be found anymore, while it was still in download mode. I unplugged the micro usb, plugged it back in (device still in download mode) and tried flashing CWM again... Once again, no device found. Then, stupid me, thought "let's reboot the phone!" Turning it off went well.... Turning it back on... Never again....
Now after a little brainstorming... I have these questions:
Could it be, since it was in Polish straight out of the box, that the device simply couldn't be rooted this way?
Will a JIG work?
IF the JIG works, will I still have problems, cause maybe the device was somehow a little different, concerning hardware or whatever if it is some sort of Polish device?
Please help... And please, don't hold back on as much information as you have, any info (even if it seems useless) might be useful after all!!
Many thanks in advance.
Click to expand...
Click to collapse
I cant see the fact that it is polish being the reason you cant root, as they should of both been the same hardware wise i.e. the international version. A jig will only get you into download mode but if you pc wont recognise it then its useless. Try using a different computer andflashing litening rom using odin on a windows machine. Thats what i did when i got into trouble and worked flawlessly
Ricey
I figured something went wrong when trying to flash to stock, which bricked it, so the computer wouldn't recognize it. Once it is in download mode, using a JIG, I'm 99% sure it'll be recognized by the computer again aswell (just a brainwave right now, download mode could've crashed or something) but I'll try your option, will definitely give litening a try as it is a very nice ROM aswell
But thanks for ruling some stuff out
Related
Hey, so I was trying to flash my friend's s3, and apparently, I did something wrong which got me stuck up at odin mode.
Initially, I could hold the vol up + home + power button to go to recovery, but now, even that won't work as it would just show me
Samsung's logo and a red exclamation mark on top left corner.
I've downloaded the firmware stock and tried to flash it using odin however it just won't work.
It says "NAND Write Start!!!" and it just stops there (stuck forever). It should (as I know it) show a progress bar on my android and
on it's interface to tell how much it has been done, but as soon as I start, the progress bar instantly fills up (on my android, the blue line)
and its just stuck there.
I've tried to take out the battery, clear cache/reset factory, take out sd and sim. But it simply won't work.
It's just stuck on "Downloading....do not turn of target!!!"
I cannot even get the flash counter to reset (I don't know how, since I can only open up odin mode)
counter: 4
binary: yes
Currently, I don't even know if it's suppose to be charging or the battery is just draining out.
Region for this phone is Turkey.
Yes I've also unrooted the phone using KingoRoot (previously, when it could go into recovery) but no luck.
Note: I have searched other threads on this forum but I cannot get anywhere around even close to fix my device.
It's soft-bricked (I assume, of course it is).
Any idea how to fix this?
Odin Screenshot (since it's my first post, it won't allow me to post outside links, sigh,):
http: // i.imgur .com/eBVZ3NN . png
^^ Just been stuck there....
Meanwhile on my android, it just shows a full-blue progress bar. And that downloading do not turn of target.
UPDATE:
THE PROBLEM HAS BEEN RESOLVED. I DOWNLOADED A CUSTOM FIRMWARE, (LUCKILY, CLOCKWORK MOD WORKED, JUST HAD TO WAIT AFTER GOING TO RECOVER)
FLASHED IT THROUGH THERE, WAITED FOR IT TO INSTALL, RESTART. BAM.
Did the 'something wrong' include flashing a firmware for another model?
What does the model number in download mode read?
You can try the rescue firmware, search general forum,.
Yeah, wrong firmware I suppose
boomboomer said:
Did the 'something wrong' include flashing a firmware for another model?
What does the model number in download mode read?
You can try the rescue firmware, search general forum,.
Click to expand...
Click to collapse
I was seeing this tutorial on how to install KitKat (4.4.4) on Galaxy S3. I must've made a mistake while trying to do so.
In other words, yes, flashing a firmware for another model.
You have a hard brick, sorry.
Yeah, no.
boomboomer said:
You have a hard brick, sorry.
Click to expand...
Click to collapse
No I don't lol. The problem has been solved anyway.
Im' glad to see you didn't give up on this, and came back to let us know what was wrong
I know this could be seen as off-topic, but the reality of devices becoming bricked isn't really possible luckily, it just takes longer to get around sometimes. If the item is worth fixing, then I always say keep at it, because I've never had an android device stay stuck so far. The only thing that really went nuts and refused to work, were 2 of the Iconia A500 tablets that lost access to their memory - but this is a common hardware fault as the RAM chips break away and need reflowing before you can even format the internal memory (it cant even see the SD cards either because the RAM comes and goes - same idea as plugging/unplugging a USB drive in Windows/Linux - it just doesn't know what to believe lol).
Great forum by the way, there's so much great information on here I get lost reading
Hello,
I wish I could explain my problem quickly and clearly, but I lost count on the amount of times I wiped, flashed and reset my Tablet so... I just hope someone comes up with a genius idea, because I'm desperate. I've tried everything.
Today I decided I wanted to try and find a better ROM I could install on my Ainol Tablet, and after doing some research I found out there was a 10.1 version of Cyanogenmod that was apparently quite popular.
I followed a tutorial I found on slatedroid.com (Flashed CM 10.1, Gapps and compatibility file) and only after I found out I just flashed a ROM built for the previous model of my tablet. When I reset it it came up as if it had done a Factory reset (same firmware but everything came up in chinese).
Then I went on and managed to find a tutorial for mine; repeated the process.
Right after doing that I re-read the tutorial (I would love to attach the link but I am a new user and am not allowed to...) and realised I was supposed to update my stock firmware to the latest version before flashing CM on it (apparently so they had the same kernel). Luckily, I had made a backup with TWRP so I went back to it and went looking on my PC for said firmware.
When I managed to find it, I realised the wifi on my tablet was gone. Whenever I switch it on, it goes back off after a few seconds. So no internet.
Then I thought I could just get that update file from my PC and copy it through USB. But that wasn't working either, my laptop will not recognise it whenever I plug it. The tablet won't even recognise a USB flashdrive.
Lastly, I realised there was a miniSD card port so I tried getting the file in through that as well. In this case, the tablet displayed a "preparing SD card" message but nothing happened afterwards...
I'm completely stuck. I have tried several times going back to Factory settings through TWRP, or reloading that backup I made, erasing Dalvik/Cache every single time, but the problems are still there. Everything else seems to be working though...
I did some research and it does look like I flashed a ROM with the wrong kernel so all the drivers are gone... (When the tablet is off and charging it displays a battery that used to stand vertically. Now it comes up horizontally...).
If that was the case, would anyone have any clue on anything I could do to fix it? Any files I could get rid of? Or maybe some secret menu on TWRP I haven't taken into account...?
Any ideas would be extremely appreciated. Please help! :'(
Thanks in advance.
Hello, XDA forumites!
I've been lurking and reading a lot of threads in here for years, using all your knowledge to fix various phones. Today though is the day I first post and it is for good reason. I'm a guy who loves challenges but this one is making me go insane. I've spend the last two days looking for ways to fix this phone but NOTHING works.
So, the deal is that this phone turns on fine. It boots, it gets to the lockscreen and... it restarts itself. Again and again and again until the battery is removed. To fix it, I've tried the following:
- recovering/updating it through the Huawei official "firmware" supplied by the site: you put the file they supply on an SD card, inside a folder named "dload" and then hold vol up and down along with the power button to make the phone install the contents of that file, named UPDATE.APP. Needless to say it doesn't work. A menu appears with the options reboot system now, apply update from sdcard, apply update from cache, wipe/data factory reset, wipe cache partition and calibrate touch screen. Trying to apply update from sdcard only lets me browse the SD looking for the file but doesn't actually see the file itself, it just shows the dload folder empty (I've tried with 4 different versions of the file compatible with phones from Central America which is where I am ATM). Also, the factory reset does nothing (although it shows it wipes data), everything's there when I start the phone up.
- flashing it with SD Flash Tool: apparently partially works with the last version 3 of the tool (although nothing changes) while version 5 of SDFT doesn't even see the phone (drivers are correctly installed, adb detects it, more on this later). A problem that arises is that I can't flash the SEC_RO package on it (don't know why) nor the PRELOADER (not that one is supposed to normally, but I feel like it would fix my problem in this case).
- cleaning it in safe mode: booting it in safe mode made me notice that it was an app pretending to be Whatsapp causing the restarts (or, perhaps, the one that loads immediately after? The phone has several malware apps). In safe mode those apps didn't load so the phone stayed on. So I cleaned everything, activated USB debugging (for later use in adb mode) and restarted only to find everything as it was before I did the cleanup. I tried rooting it in safemode, cleaning again, still reverts to full "normality" after the restart. Same results when using the phone's proprietary SW HiSuite.
- installing CWM's recovery img through adb+fastboot: I installed all the possible - necessary or unnecessary - drivers (Google's, phone's official ones, PDANet ones) and the phone is correctly detected by the PC (visible in Device Manager) and is visible through the adb devices command. But as soon as I adb reboot bootloader it to fastload the CWM image, the phone stops being seen correctly and doesn't show up in fastboot devices, only showing "NEW: SAFE OLD:RISK" on a black background on its screen.
So, to recap: the phone restarts because of a malware at startup, reverts any and all changes made to it in safemode, doesn't wipe from the recovery menu, apparently has a corrupted bootloader and is impervious to normal flashing SW... Anyone got any more ideas on how to deal with it? The only option left that comes to mind is to fix it directly by flashing the internal memory using JTAG/RIFF but I don't have the equipment (nor do I intend to buy it).
Bump, hoping for some help...
One more bump, still stuck
First, don't get happy: I have no answer to your problem. Sorry. But I have a similar one. I was running a very efficient, rooted, stock ROM G730-U251, until I decided to switch from 'Ninjamorph Free' to 'Pro'. I've been made a lot of changes with Free version for a long time without any issues at all. Then, one day, when making a small, useless change with 'Pro', something went wrong; phone just rebooted and refused to get past bootanimation. With no custom recovery on hand, only solution for this is to flash ROM. Though I had no problem finding the official, stock UPDATE.APP, which flashed smoothly from the SD card to be fair. Mess came when, once flashed, I decided to install OTA update available, which I overlooked since phone was new. Big, BIG mistake. It just came with more restrictions than ever, letting me root, yes, but this time with 'Kingroot' only (as stock, I had no problem rooting with Framaroot) but soon discovered I wasn't able to use 'Super-Sume', 'Adaway' and 'Link2SD', because some system parts now CAN'T be mounted rw, even using ES File Explorer. To avoid any complication, decided to reflash UPDATE.APP just as I did before. No way I can do it this time. Don't know exactly why, but assuming it's not possible to update with a previous version of the 'same' ROM. So now I'm looking for a flashable stock ROM in order to try SP flash tool. Phone is in working state right now (not as yours), but I just don't feel comfortable with it as it is right now, because those apps are always the main reason why I actually root every single of my devices and simply because I like to have my stuff as my own way as possible. You know, truth is there's not much of an advanced support for this phone, not even here at XDA and I think that's because this is a Latin America version. We owners of G730-U251 devices are pretty much on our own, to say the least. Whatever, if the whole deal gets more complicated than it is, there's a strong possibility for me to end up getting rid of this phone. Sad. Really. It's actually a good phone. Though it WAS better...
This problem has been driving me absolutely mental. About 2 months ago, I tried to root my Galaxy Tab 4 8.0 by T-Mobile (it was an old device anyways), I used the Odin method, and while it was installing, it said that the process was successful, and I saw it all come through. However, when my device restarted, it was stuck at "Starting apps..." for about an hour, so I tried restarting. Then it was stuck on the T-Mobile logo for 1.5 hours. I did a hard wipe/reset, and it was fine... for about a week.
The funny thing about it is, after I did the hard reset, certain bugs would happen, a different bug each time. (For example, Google Play apps would be stuck at "installing", screenshots wouldn't save, apps would crash repeatedly, etc) So if I tried to restart, it wouldn't fix it, but instead it would bootloop. I have to hard reset/wipe my whole system each time it happens, and it drives me up the friggin wall.
I saw online that you can try flashing your system by installing the default drivers onto your computer, and install it on your system through Odin. (or something like that, I'm not that professional at mobile technology) Awesome. Just one problem.. I have looked everywhere and I can't find the driver specifically for my system. I have looked for the driver ever since the problem got worse and I found out about this information, but I found nothing.
If anyone has any idea on how you can help, please respond as soon as you can. Thank you very much.
iamnekro said:
This problem has been driving me absolutely mental. About 2 months ago, I tried to root my Galaxy Tab 4 8.0 by T-Mobile (it was an old device anyways), I used the Odin method, and while it was installing, it said that the process was successful, and I saw it all come through. However, when my device restarted, it was stuck at "Starting apps..." for about an hour, so I tried restarting. Then it was stuck on the T-Mobile logo for 1.5 hours. I did a hard wipe/reset, and it was fine... for about a week.
The funny thing about it is, after I did the hard reset, certain bugs would happen, a different bug each time. (For example, Google Play apps would be stuck at "installing", screenshots wouldn't save, apps would crash repeatedly, etc) So if I tried to restart, it wouldn't fix it, but instead it would bootloop. I have to hard reset/wipe my whole system each time it happens, and it drives me up the friggin wall.
I saw online that you can try flashing your system by installing the default drivers onto your computer, and install it on your system through Odin. (or something like that, I'm not that professional at mobile technology) Awesome. Just one problem.. I have looked everywhere and I can't find the driver specifically for my system. I have looked for the driver ever since the problem got worse and I found out about this information, but I found nothing.
If anyone has any idea on how you can help, please respond as soon as you can. Thank you very much.
Click to expand...
Click to collapse
What you read in the internet means re-flashing your stock rom (system), that is the fix for your problem, the way to do it is to download and install Samsung USB drivers if you hadn't done that already, and Download stock rom from here or here search your model number in the search box and choose the stock rom based on your country, and flash with Odin, it's pretty much the same way you tried to root using CF-ROOT method:
1-you boot into download mode (volume down + home button + power button)
2-and then connect your phone to PC.
3-open Odin and uncheck everything except "auto reboot" and "F. Reset Time" (you should find it like that already), make sure your phone is recognized by Odin, you will see a blue box with a message saying "0:[COMX]" where X is a number.
4-press AP (or PDA in some versions) locate your stock rom which should be in .md5 format, and choose it, then 5-press start.
6-wait for the process to finish (takes a while) and then the phone should reboot itself and you will get a message in Odin saying "Reset!"
PS: you must register on the sites to download..bad thing i know but it's obligation.
Searched both of these websites for the drivers, found nothing.. I've been searching the internet for hours and not one driver was found. Extremely disappointed.
iamnekro said:
Searched both of these websites for the drivers, found nothing.. I've been searching the internet for hours and not one driver was found. Extremely disappointed.
Click to expand...
Click to collapse
Give me your model number.
Sorry found it in the thread title
@iamnekro
That is the link from the first site:
SM-T337T latest firmware android 5.1.1
That is the link from the second site:
SM-T337T latest firmware android 5.1.1
Obviously you didn't search at all...LOL
PS: It's called Stock Firmware or Stock ROM.... not Drivers
Register on any of the sites first to download.
And press the thanks button please
Regards Migo
I'll have to close the thread.. my computer isn't that advanced and is low on space anyways...
iamnekro said:
I'll have to close the thread.. my computer isn't that advanced and is low on space anyways...
Click to expand...
Click to collapse
It doesn't need any advanced computer and only the size of the stock rom and Odin, it's no big deal.
Hello Everyone!
So I just found My First Love, GT-I9300 laying in a drawer. Before moving to the current situation, let me put some light on the history.
I know this is a way too OLD device, But I want to try it for the last time kindly HELP me!!!!
I had this great phone years back, I installed several custom ROMs on it and used it for a while. The recovery I was using then was TWRP. ( Don't remember version ) But somehow it started behaving abnormal, like restarting on its own, etc. I thought it to be some button issue so I changed them but the problem persists. So I did a custom ROM (Don't exactly remember the name as my old HDD crashed which contained all the ROMs) but it doesn't go successful. So, I left it in a drawer.
Now in present
It doesn't boot in recovery mode, as no recovery is installed (Maybe I did something wrong last time)
The download mode shows this screen, see attached file (No model etc, strange huh)
When trying to install Firmware, it shows error no PIT found
When trying to install PIT write failed error shows up in ODIN
Samsung Kies doesn't recognise the device
So, My question here is
Can this device be fixed? If yes how can I do it? because I don't remember anything about ROM, Kernel, bootloader, firmware etc.
Or it is just bricked So I can stop wasting my time on it.
I don't have much knowledge, I was reading here and applying different tricks but none seems to work.
Any Help would be appreciated.
The screenshot shows no product id anymore, so I am afraid that your phone has a defect nand and is pricked.
rodman01 said:
The screenshot shows no product id anymore, so I am afraid that your phone has a defect nand and is pricked.
Click to expand...
Click to collapse
So it means it can't be fixed now?
no I don't think so.
Ahh okay. thank you for your response.