[SOLVED]borked my device with twrp - Galaxy S 4 Mini General

SOLUTION: see answer #2
hi,
i was trying to change CWM recovery with TWRP, but now im stuck in a screen that starts with 2 red lines reading:
could not do normal boot
ODIN MODE
in the background is the green fat android that looks lie R2D2 with arms.
below that it reads:
Downloading....
Do not turn off target !!!
now, its been 15 minutes and of course i turned it off. but it reboots into the same screen.
what i did to get here:
i was happily running cm 12.1, used adb shell to connect to the phone and did run:
Code:
dd if=/sdcard/twrp.img of=dev/block/platform/msm_sdcc.1/by-name/recovery
dd: /dev/block/platform/msm_sdcc.1/by-name/recovery: No space left on device
20481+0 records in
20480+0 records out
10485760 bytes transferred in 1.435 secs (7307149 bytes/sec)
i was uder the inpression that this:
https://twrp.me/devices/samsunggalaxys4mini64bit.html
was my device, but apparently it isnt.
now after that first dd failed, i panicked a bit and googled further and found this:
https://s.basketbuild.com/devs/F4k/twrp/serranoltexx
seranolltexx sounded familiar so i dd'ed that to the device, no errors this time.
but now im stuck in this state.
how can i make my device useable again?

Your device seems stuck in download mode. Try to flash the right recovery through Odin. There are several s4 mini models, so find out which one you have in order to choose the right recovery.
Also, this belongs in Galaxy S 4 Mini Q&A, Help & Troubleshooting

well, after a lot of bad advice from #cyanogenmod
i downloaded the original android firmware...what a annoying waste of time. 1gb with 50kbyte/s.
the poster before me is right.
start odin 3.0.9 on windows
press "AP" select the file: recovery-clockwork-6.0.5.1-seranoltexx.tar.md5
flash
turn device off
start device with: volume up, home, power
and voila, youre in cwm again
came into this trouble by flashing the wrong TWRP. is there a TWRP for the i19195?
download link for CWM(first post, attachements):
http://forum.xda-developers.com/showthread.php?t=2364980

androidfan34 said:
well, after a lot of bad advice from #cyanogenmod
i downloaded the original android firmware...what a annoying waste of time. 1gb with 50kbyte/s.
the poster before me is right.
start odin 3.0.9 on windows
press "AP" select the file: recovery-clockwork-6.0.5.1-seranoltexx.tar.md5
flash
turn device off
start device with: volume up, home, power
and voila, youre in cwm again
came into this trouble by flashing the wrong TWRP. is there a TWRP for the i19195?
download link for CWM(first post, attachements):
http://forum.xda-developers.com/showthread.php?t=2364980
Click to expand...
Click to collapse
androidfan34 said:
well, after a lot of bad advice from #cyanogenmod
i downloaded the original android firmware...what a annoying waste of time. 1gb with 50kbyte/s.
the poster before me is right.
start odin 3.0.9 on windows
press "AP" select the file: recovery-clockwork-6.0.5.1-seranoltexx.tar.md5
flash
turn device off
start device with: volume up, home, power
and voila, youre in cwm again
came into this trouble by flashing the wrong TWRP. is there a TWRP for the i19195?
download link for CWM(first post, attachements):
http://forum.xda-developers.com/showthread.php?t=2364980
Click to expand...
Click to collapse
seranoltexx model number is i9195 (normally written in caps as I9195), but you must make 100% certain what phone you have. Some model numbers are very similar e.g. i9195l (see http://www.gsmarena.com/samsung_galaxy_s4_mini_i9195i-7468.php) but you cannot run software for i9195 on an i9195i as the last letter indicates a hardware difference. Also there are a lot of carrier specific phones so you can't run standard software with this (in most cases, I believe ...... I've never had a carrier version). You need to pop the battery out and find out exactly what your model number is if you can't do it via software.
There is a TWRP version for the i9195, if that is your phone
http://forum.xda-developers.com/showthread.php?t=2449107

IronRoo said:
seranoltexx model number is i9195 (normally written in caps as I9195), but you must make 100% certain what phone you have. Some model numbers are very similar e.g. i9195l (see http://www.gsmarena.com/samsung_galaxy_s4_mini_i9195i-7468.php) but you cannot run software for i9195 on an i9195i as the last letter indicates a hardware difference. Also there are a lot of carrier specific phones so you can't run standard software with this (in most cases, I believe ...... I've never had a carrier version). You need to pop the battery out and find out exactly what your model number is if you can't do it via software.
There is a TWRP version for the i9195, if that is your phone
http://forum.xda-developers.com/showthread.php?t=2449107
Click to expand...
Click to collapse
yes thats the one.
but its from 2013....isn that a bit old?

androidfan34 said:
yes thats the one.
but its from 2013....isn that a bit old?
Click to expand...
Click to collapse
mmmmm yes does look a bit old, I use CWM, so am not up to date on TWRP, I was just saying there is a version of TWRP for our phone, I guess you searched with the wrong phone model number which is why you didn't find anything.
A quick search shows there is a recent one
http://forum.xda-developers.com/showthread.php?t=2678420&page=88
but it's an unofficial version, you may find something else searching again or a TWRP user will point you in the right direction

Related

[How to][guide] UPDATE TO 4.4.2 BOOTLOADER AND ROOT TMO/CANADIAN VARIANTS

The point of this thread is to help people safely update their bootloader so that they may flash a touchwiz kitkat rom.
I have seen several threads where people are running into issues and even development threads get cluttered with questions. So I will give you the steps needed using my method.
Please note this is for windows 7. However it should work on other versions of windows too.
This method may wipe your internal storage completely so transfer anything you do not wish to lose to you pc.
This method will also trip yout knox counter which may void your warranty.
You also may not be able to downgrade to 4.3 so make sure this is what you want to do
I am not responsible for bricked devices. Proceed at own risk
You have been warned!!!
So what you need to do is download a few files.
I have created a zip file and uploaded it for easy access and simplicity reasons. If it becomes out dated I will update accordingly.
What is needed is your variants stock firmware. You need to get the one for your device off sammobile.com
On sammobile you must create an account in order to download (if you don't have an account already).
Once you are logged in click on the firmware tab. Then enter your device name.
Canadian variants enter: SM-N900W8
TMO variants enter: SM-N900T
You will then be able to pick the most recent firmware for your device and download it. So now that you have the correct firmware (please double check, and if unsure google it)!!!
So lets begin
You also need to download the zip file I have made and extract it. Inside it you will find the samsung drivers, 3 recovery options to pick from, the supersu.zip and also odin.zip. once you've extracted the file you've just downloaded you need to extract the odin.zip inside it as well.
So if you have not previously installed the samsung drivers you will need to do so. Simply run the samsung mobile driver.exe file and install it. Once successful in installing, reboot your pc.
when it boots up, connect yout device to you pc and transfer over the supersu.zip over to your phone. The root of your sd card is recommended for easy access.
Now what you need to do is ensure usb debugging is enabled. Do so by going to settings, general, developer options and ensure its checked. If you do not have developer options simply go to about phone, and tap om build number 7 times to enable developer options.
Once this is done you need to power off your device with it unplugged. Now we need to enter download mode. You can do this by holding the home button, volume down and pushing and hokding the power button. You will be presented with a warning screen. You push volume up to proceed or vokume down to cancel and restart device.
We want to push volume up. It will then show a big android saying warning do not turn off target.
Now connect your device to your pc and run odin as administrator.
In odin near the top left you shoukd see a box colored in saying:
Com and have a number. If you see this that means odin recognizes your device. If you do not that means eiter you dont have the drivers installed properly or perhaps you need to try a different usb port or cord.
You then will see a few check boxes checked off. Auto reboot and f.reset time. leave these checked only.
Theres an AP BUTTON. Click this button and then navigate to your stock firmware file you've downloaded and select it. It may take a few minutes to load it. Once it does load all you need to do is click the start button and let odin do the rest. Do not touch anything.
This will take a few minutes. You should see a green "pass" in the box at the top left. Your device will eventually reboot and you will now be stock, unrooted on the latest firmware.
*please note that if at this point your device hangs on the Samsung logo sayong "recovery booting" you need to pull the battery and reflash the firmware. This time also check the repartition box.
Now we need to root and flash a custom recovery.
Again you'll need to enable usb debugging on your phone so I recommend skipping the google setup stuff on your phone.
Once you have enabled it, power off your phone with it unplugged and again enter download mode the same way you did before.
Plug in your device and in odin press the reset button to clear the stock firmware file.
Now connect your device to your pc and again ensure that odin recognizes it.
Click the AP BUTTON again and this time navigate to the custom recovery of choice ( I reccomend twrp. I am also using the tmo version as I could not get the canadian version to boot)
Once selected again hit the start button. In a few seconds you should again receive a "PASS" message. That mrans you have successfully flashed a custom recovery.
Now power off your device and unplug it. Now we need to enter recovery.
Do so by pressing the home button, volume up, and push and hold the power button. Once you see recovery booting you can let go. You will also see in red font: recovery is not seandroid enforcing. That just means you have a custom recovery.
If your device hangs at this screen you will need to oower it off and try a different recovery.
Once in recovery I reccomend making a nandroid backup. (Optional)
Next we are going to root. All that you need to do is press install or install zip from sd card depending on which recovery you chose and navigate to the supersu.zip
Now install the zip by following the instructions of the recovery and then reboot.
Congratulations you are now rooted (you can confirm if you like by downloading the root checker app if you wish) and on the latest firmware and can flash custom 4.4.2 roms for your device. Please read and follow the directions of the op in the thread of the rom you wish to flash.
Download link: http://d-h.st/4xl
sent from my JEDI ELITE Note 3
for best xda results, click to enlarge ?
http://img268.imageshack.us/img268/9564/searchitnoob.gif
phone stuck on recoveryboot a
Theres an AP BUTTON. Click this button and then navigate to your stock firmware file you've downloaded and select it. It may take a few minutes to load it. Once it does load all you need to do is click the start button and let odin do the rest. Do not touch anything.
This will take a few minutes. You should see a green "pass" in the box at the top left. Your device will eventually reboot and you will now be stock, unrooted on the latest firmware.
= at this part of the instruction odin has said pass but my phone just has samsung logo and says on top recovery boot... and nothing else i dont know how to continue or move forward i hope someone can help me thank you and sorry for troubling you
nymomo789 said:
Theres an AP BUTTON. Click this button and then navigate to your stock firmware file you've downloaded and select it. It may take a few minutes to load it. Once it does load all you need to do is click the start button and let odin do the rest. Do not touch anything.
This will take a few minutes. You should see a green "pass" in the box at the top left. Your device will eventually reboot and you will now be stock, unrooted on the latest firmware.
= at this part of the instruction odin has said pass but my phone just has samsung logo and says on top recovery boot... and nothing else i dont know how to continue or move forward i hope someone can help me thank you and sorry for troubling you
Click to expand...
Click to collapse
I replied to your pm you sent me. Anyway just flash a different recovery if it's hanging after flashing recovery. If its hanging after flashing stock 4.4.2 firmware try it again by oulling battery and going back into dl lodem this time also check the repartition box
sent from my JEDI ELITE Note 3
for best xda results, click to enlarge ?
http://img268.imageshack.us/img268/9564/searchitnoob.gif
Where are the download links?
Arturofm2 said:
Where are the download links?
Click to expand...
Click to collapse
Well if you're having to ask this then that leads me to believe you did not read the op. I suggest you do so or you may have a bad experience. Once you read all of the op I will tell you where it is
Sent from my GT-I9205 using Tapatalk
markbencze said:
Well if you're having to ask this then that leads me to believe you did not read the op. I suggest you do so or you may have a bad experience. Once you read all of the op I will tell you where it is
Sent from my GT-I9205 using Tapatalk
Click to expand...
Click to collapse
Now I see the download link, but it wasn't there yet.
Thanks, by the way you said that it may be difficult to go back to a different version, does this include the backups too?
Arturofm2 said:
Now I see the download link, but it wasn't there yet.
Thanks, by the way you said that it may be difficult to go back to a different version, does this include the backups too?
Click to expand...
Click to collapse
Yes
Sent from my GT-I9205 using Tapatalk
My phone is not flashing
its working never mind lol. I just tried again and it worked
regarding the stuck on RECOVERY BOOTING, you have to reflash it, WITHOUT ticking the REPARTITION (as stated in the instructions. you just need to reflash again. and it should work the 2nd time around
Thanks very
How can i get it to work with mac
Sent from my SM-N900T using xda premium
westkhalifa13 said:
How can i get it to work with mac
Sent from my SM-N900T using xda premium
Click to expand...
Click to collapse
No idea man. I don't have a mac. Google it man
running DECEPTICON rom (coming soon)
for best xda results, click to enlarge ?
http://img268.imageshack.us/img268/9564/searchitnoob.gif

[CLOSED]Yoga Tab 2 (830, 1050, 1380) - get back to KitKat

@MikeChannon removed OP. please close
what? lol
Yeeha! You are the magic man....
workdowg said:
Yeeha! You are the magic man....
Click to expand...
Click to collapse
He truly IS the man. Helped me out BIG style.
ionioni said:
READ CAREFULLY AND BE WARNED BEFORE ANYTHING:
THIS CAN HARD-BRICK YOUR DEVICE AND I TAKE NO RESPONSIBILITY FOR THAT!
use it only if you must or not at all
you can read this for some details about what bricks are so you understand what you can get into
this is for all Yoga Tab 2 models 830, 1050, 1380 (regardless of the submodel F,L,LC)
it restores(downgrades) your bios firmware from whatever Lollipop version to the original/genuine one from the latest KitKat stock rom released by Lenovo (and all the latest KitKat stock rom's have 150422 in the rom filename, ie April 15, 2015 and nothing not even minor OTA's were released after this date for KitKat, next ones upgraded KitKat to Lollipop)
useful to:
1. those who want to return back to the KitKat stock rom from Lollipop (if you simply flash back the KitKat stock rom files and you are still on Lollipop bios firmware you will softbrick as the Lollipop bios is a x64 version while the KitKat loader/kernel are ia32 so you will get stuck at efi shells, bios screen etc)
2. those who took the Lollipop OTA, succeded, but had in time problems (bricked their device) and cannot flash a Lollipop stock rom as they don't have one (not being released by Lenovo/available yet and at least some 830 and 1380 models are in this situation), so they must flash back KitKat stock rom and after take the OTA to Lollipop (and the KitKat flashing part put's them in the same situation as those from p1.)
3. those who tried to take the Lollipop OTA and had problems and they tried to flash KitKat stock rom and yet they are failing (this could be due to problems in the updating while OTA was applied, yet could be that their bios firmware was updated to Lollipop version)
4. those who want to test stuff (going down/up between versions) ... you name it...
how to use it:
1. first download and extract the corresponding tool for your device (830 and 1050 models share the same bios firmware so they have a common tool), while at this you can watch the little attached recording i made with the tool restoring the bios for my 1380F tab so you know what to expect when you run it. USE THE TOOL THAT MATCHES/CORRESPONDS TO YOUR MODEL, you can hard-brick if for eg you use the 1380 one on a 1050 model (didn't even tried but nothing good can happen)
2. place your tab in the DnX mode: power off (by force if you have to), press and hold both VolUp and VolDown butons, keep them pressed, now press Pwr to start and release Pwr when it turns on/buzz (but keep holding pressed Vol buttons), in a few seconds your screen will display "Fastboot starting..." and it will hold on that, now you can release the Vols (you are in DnX mode). you must get that message, try again the whole sequence until you succed, don't move on until you have that "Fastboot starting..." on your screen.
3. run the tool (you must have the intel drivers installed, if you flashed to your tab at some point you should have them already), follow the messages i think it's quite easy and straightforward, in a few minutes you will be done and having a brand new kKitKat bios firmware on your tab
(3) if while running it hangs on the "Preparing to push files..." message, and your tab starts to the whatever error message you had before it means that you already have a KitKat bios (the tool works only with the Lollipop bios firmware) so you don't need to restore the bios, you can flash stock KitKat rom directly (in this scenario the tool doesn't modify anything on your tab)
4. when it finishes the tool will automatically reboot your tablet, leave it for a few seconds to start (it will most likely go ninto some efi shell, or bios screen whatever your old files were) afterwards turn it off (long press Pwr) and that's it
5. you can now start in DnX mode again and flash your stock KitKat rom (this step is quite known by now so i won't detail it, there's a lot of info on that in other threads), take OTA's, eat candies... whatever you like
i must warn you again, while i tested this tool (i think i moved from KitKat to Lollipop and back at least 20 times and never had any issue with it) you are the only responsible if something bad could happen, this is playing with bios (and any mistake will hard-brick your tab so you will have to send it to a service for fixing). make sure you have enough battery (while i used the tool even when i was with 5% on my battery i would not recommend, i say at least a 30-40%, the process runs only for 2-3 minutes so that should not be an issue). and of course once it started the flashing DO NOT EVEN THINK OF INTERRUPTING! (you could close other software on your PC that maybe can hang your computer while flashing.. you got the point)
Good Luck!
edit: i already have messages about successful bios restoring (as expected no? ) but failing on completing the OTA to Lollipop update after flashing anew the KitKat stock rom. to them and to all of you people who are going to Lollipop from your newly flashed stock KitKat: SET YOUR COUNTRY CODE!!! after you flash back stock kitkaton the first boot input ####6020# in your contacts and a dialog will pop from which you MUST choose a country (no matter which one, preferably yours or a close one), then after the tab reboots for updating the region and comes back to Android check that you have a country code set by entering #### 59930# and it should show the code you chosed. if you take the OTA without a country set you will FAIL! if you failed on your OTA to Lollipop flash anew the stock KitKat rom and set the country code
also do not take an OTA if your device is rooted, always UNROOT first then take the update, and you can root back after or just don't root until you finished the whole Android installing and OTA updates
Click to expand...
Click to collapse
thank you! i had the boot to bios problem after trying some not-smart things. after spending an hour on the phone with lenovo this morning getting a repair authorization, i printed out the label. i don't need to send in my 1380f now.
your app fixed that and i was able to flash to kitkat and then upgrade to lollipop.
Works perfect! Thanks!
daWyrd1 said:
thank you! i had the boot to bios problem after trying some not-smart things. after spending an hour on the phone with lenovo this morning getting a repair authorization, i printed out the label. i don't need to send in my 1380f now.
your app fixed that and i was able to flash to kitkat and then upgrade to lollipop.
Click to expand...
Click to collapse
yeah... the guys at Lenovo deserve a break, they have such a beautiful daadeedaadoo sound on the boot animation (that one cannot even disable it )
bisti2004 said:
Works perfect! Thanks!
Click to expand...
Click to collapse
Pentru putin
Mersi Dorin!
My 1050F cannot boot for long time, I posted the problem(http://forum.xda-developers.com/thinkpad-tablet/general/help-1050f-dead-t3188696) but no one answered me. Today I was very excited to find this post and read it carefully, then tried to do it. But just after the sending progress started (the "xx%" progress began)for about 10 seconds, the program "restore-kitkat-bios-830_1050" vanished(Maybe forced teminated by Windows? I ran the "restore-kitkat-bios-830_1050" after a new reboot of Windows). I waited for about 3 minutes, the "restore-kitkat-bios-830_1050" program still didn't appear, and the tab hanging on a normal picture ( I don't remember, probably a recovery stage picture? but I remember the last line is "the result is Okay"). So I had to disconnct the tab from the computer, and powered it off. Then I try to power it on, but sadly find it cannot boot to any screen. In a dark room, I find the backlight of the tab is on when I pressed the power button, but there is no text or picture on it, regardless of whether I press the power button independently, or press the power button together with any volume button(s).
Now the tablet seemingly has changed into a REAL brick (or hardware brick?). How can I rescue it? The only way is to send it to a service?
aerofisher said:
My 1050F cannot boot for long time, I posted the problem(http://forum.xda-developers.com/thinkpad-tablet/general/help-1050f-dead-t3188696) but no one answered me. Today I was very excited to find this post and read it carefully, then tried to do it. But just after the sending progress started (the "xx%" progress began)for about 10 seconds, the program "restore-kitkat-bios-830_1050" vanished(Maybe forced teminated by Windows? I ran the "restore-kitkat-bios-830_1050" after a new reboot of Windows). I waited for about 3 minutes, the "restore-kitkat-bios-830_1050" program still didn't appear, and the tab hanging on a normal picture ( I don't remember, probably a recovery stage picture? but I remember the last line is "the result is Okay"). So I had to disconnct the tab from the computer, and powered it off. Then I try to power it on, but sadly find it cannot boot to any screen. In a dark room, I find the backlight of the tab is on when I pressed the power button, but there is no text or picture on it, regardless of whether I press the power button independently, or press the power button together with any volume button(s).
Now the tablet seemingly has changed into a REAL brick (or hardware brick?). How can I rescue it? The only way is to send it to a service?
Click to expand...
Click to collapse
i've seen the post with the problem you had, now the thing is on a "normal" bricked tablet (meaning soft bricked one) your tab never hangs at the screen to which you're referring to (Powered by Android) it will always move on (to some error message, bios etc). the same tool was used by me and others (including for your 1050F model last one I recall is @Einwood) and never had issues (until now) so imo it's very unlikely that the problem was from the tool (it's task is quite simple and don;t see what could go wrong) something interrupted the flashing process. also you said you tried both lollipop and kiktkat rom flashing and failed and at least one of them should have worked (the roms are flashed using bios dnx as start) so the issues are with your tab hardware most likely.
but all that is irrelevant now... if it doesn't boot at all and you cannot get it to show ANY message at all (white Lenovo logo doesn't show up when you power on nor does it buzz when pwr on) then service is the only solution
@ The Others: please post your tab model too when posting
Thank you so much for such detailed analysis, but I cannot figure out why the hardware has problem. Yes, now it cannot show ANYTHING, white Lenovo logo doesn't show up nor does it buzz when pwr on. Anyway, I think I have no choice except the official repairment now.
I'm trying to find the LENOVO service sites in Canada, but their Canada official site has no such information, on the contrast, its website is full of sale/order/payment information. I think I should re-think about this company.
Thank you again for the reply.
ionioni said:
i've seen the post with the problem you had, now the thing is on a "normal" bricked tablet (meaning soft bricked one) your tab never hangs at the screen to which you're referring to (Powered by Android) it will always move on (to some error message, bios etc). the same tool was used by me and others (including for your 1050F model last one I recall is @Einwood) and never had issues (until now) so imo it's very unlikely that the problem was from the tool (it's task is quite simple and don;t see what could go wrong) something interrupted the flashing process. also you said you tried both lollipop and kiktkat rom flashing and failed and at least one of them should have worked (the roms are flashed using bios dnx as start) so the issues are with your tab hardware most likely.
but all that is irrelevant now... if it doesn't boot at all and you cannot get it to show ANY message at all (white Lenovo logo doesn't show up when you power on nor does it buzz when pwr on) then service is the only solution
@ The Others: please post your tab model too when posting
Click to expand...
Click to collapse
aerofisher said:
Thank you so much for such detailed analysis, but I cannot figure out why the hardware has problem. Yes, now it cannot show ANYTHING, white Lenovo logo doesn't show up nor does it buzz when pwr on. Anyway, I think I have no choice except the official repairment now.
I'm trying to find the LENOVO service sites in Canada, but their Canada official site has no such information, on the contrast, its website is full of sale/order/payment information. I think I should re-think about this company.
Thank you again for the reply.
Click to expand...
Click to collapse
sorry about your issue, yet repairing should not take long, maybe @workdowg can guide you more as it had a similar problem and was solved very fast (6 days if i recall) sending through fedex on lenovo's expenses.
aerofisher said:
Thank you so much for such detailed analysis, but I cannot figure out why the hardware has problem. Yes, now it cannot show ANYTHING, white Lenovo logo doesn't show up nor does it buzz when pwr on. Anyway, I think I have no choice except the official repairment now.
I'm trying to find the LENOVO service sites in Canada, but their Canada official site has no such information, on the contrast, its website is full of sale/order/payment information. I think I should re-think about this company.
Thank you again for the reply.
Click to expand...
Click to collapse
http://bfy.tw/2gNc (just having fun) it is the one that says phone support.
ionioni said:
sorry about your issue, yet repairing should not take long, maybe @workdowg can guide you more as it had a similar problem and was solved very fast (6 days if i recall) sending through fedex on lenovo's expenses.
Click to expand...
Click to collapse
Yes, once i talked to them (about 5 minutes) they emailed me all i needed and i just had to find a local fedex dropoff center. They boxed it and i got it back in 6 days.... this seems to be a common thing for them....
Sent from my YOGA Tablet 2-1050F using Tapatalk
Yoga Tab 2 (830, 1050, 1380) - get back to KitKat
You are my lifesaver and I just can not thank you enough @ionioni
how can you make a file like restore-kitkat-bios-1380.zip ??!! you are such a genius !! :good:
We will never be able to flash it back to KitKat Bios without this zip file !! :crying:
But why don't we need to flash it back to Kitkat Bios on my Samsung Note 3, S5, Note 10.1 (2014 version) and Nexus 9 ?!!
thank you very much for your hard work again and keep up the good work pls
this was on my inbox and it should continue publicly maybe others can benefit
KainXSS said:
I'm wondering what your flashing to the tablet with your tool, I have a Lenovo S8-50F and lollipop is pretty abysmal on it, so I'm wondering what your flashing to downgrade the bios so I can try it on the S8, since its very very similar to the 830.
Click to expand...
Click to collapse
you should NOT use the tool unless it is made exactly for your model, or you most likely will hard-brick. moreover Lenovo uses an in-cpu module for digitally checking the authenticity of the firmware you have on your board at pwr on time and even if you have a bios that would work on your model if it is signed with another key it will cause a hard-brick (the measured boot module will refuse to load the IBB in the new bios).
for eg if one writes the 1051 windows variant of bios on the 1050 android one (they are identical in hardware) it hard-bricks (tested).
send me a link to the latest KK stock rom for your device and i will check on it.
That is what happend to me. My loved 1380f is hard-bricked. Only the white lamp is blinking and it doesn't turn on anymore.
Is there a possibility to repair it or can i throw it in the garbage? Please give me an advice. Thank you very much.
bombolota1 said:
That is what happend to me. My loved 1380f is hard-bricked. Only the white lamp is blinking and it doesn't turn on anymore.
Is there a possibility to repair it or can i throw it in the garbage? Please give me an advice. Thank you very much.
Click to expand...
Click to collapse
not so much you can do, the hardware is fine, it just got the wrong firmware in it... somehow you must rewrite the bios but you cannot do that from the outside (ie by software means) without being able to boot at least in DnX mode. you can check quickly ... if after you PwrOn (well.. after you long press Pwr button as at this moment Powered On of Off are werid concepts ) you don't get NOTHING on your display (ye not even the Lenovo -> Powered by Android white/black logo) than that's it (try maybe to see if somehow DnX didn't got hooked by entering a fastboot devices and see if by some miraccle you don't see your device there)
your device must be opened by a repairing service tech (especially if he is on warranty), you could do it yourself (i did) but you need the appropiate tools and know/how otherwise from a hard-bricked yet recoverable (the hardware is ok) you will transform it into just a paper holder
updated kitkat bios restore tool to version 2 (foolproof version). read the main thread post at the beginning.
Good morning.
Please let me introduce my situation. I use Lenovo Yoga tablet 2 Pro. On 9-th of november I updated Android to 5.0.1. Unfortunately, one of my commercial aps now can not make a connection with external device (no appropriate information about USB connection is appeared).
I am affraid the problem lies on the Android 5.0.1 system. Before that everything had worked perfect.
That is way I decided to downgrade to the Androix 4.x.
I found above treads, but have some doubts.
Is above tool downgrade my system to Android 4.x or do I need to do some additional operations, to get back to the Android 4.x?
In the section - how to use it (point 5) we can read:
5. you can now start in DnX mode again and flash your stock KitKat rom (this step is quite known by now so i won't detail it, there's a lot of info on that in other threads), take OTA's, eat candies... whatever you like
Click to expand...
Click to collapse
Can you give me some more detalis (links about that?)
Kind regards from Poland
Pietia.
pawlikp100 said:
In the section - how to use it (point 5) we can read:
Can you give me some more detalis (links about that?)
Kind regards from Poland
Pietia.
Click to expand...
Click to collapse
you must:
1. Downgrade the bios using the restoring tool (you mention "Yoga Tab 2 Pro" so you must use the 1380 version), and you must do that so you can flash KitKat stock rom on your tablet (if you try to flash directly, without the bios downgrade it will fail and you will soft-brick your tablet)
2. After restoring the bios, download from here your stock KitKat rom and extract
3. Flash using Intel Phone Flash Tool (open with it the "flash.xml" from the target_bin directory of the extracted archive). the Intel Tool can be found in the tools directory of the same extracted archive.
4. After you finished sotck KitKat flashing, remember to set your contry code (####6020# in Contacts), also it's not necessary to make your settings wifi etc before you set your country code as they will anyway going to be deleted (a factory reset is performed on country code setting operation). if you don't set a country code you will fail when upgrading to Lollipop.
5. Update using the Lollipop OTA or stay on KitKat
Thank you for explanation.
I download system, installed Phone Flash Tool, open it and chose flash.xml, but after connecting my YT2Pro I can not see device specific with "Start to flash" button in the Device list area of the program.
see below screen. Is this screen looks as it should? (ups, unfortunately I can not post images, because I am new user).
One more thing, tablet should be turned off during flashing?
Right now my tablet is connected to the laptop by USB. It is not switched off and charging is in progress (laptop does not see my tablet as an additional disc/device).
Is above status correct?

Yotaphone 2 yd206 updating issues

Just bought this from Gearbest. It is unrooted. I don't have a "check for system updates" button in Settings,About phone.
1. Is there a way of enabling this or will OTA update happen automatically?
2. I have read about manually updating with the yotaphone flasher utility but some of the posts here are scaring me off. Has anyone successfully flashed the EU firmware onto this phone using the flasher?
Thanks
John
HI, I had the same with my phone from tinydeal.
You can update it manually, but prepare to lose all you data if you don't have it backed up in some way.
Also, you need to be sure that you are prepared to try again and mess around a little if it does not work. As far as i've read nobody has actually hardbricked the device by trying to flash it.
My advise would be to download the latest firware via the yotaflasher, whichever you like but rename the radio folder in the firmware folder in the yotaflasher folder so the radio part just stays the same, this worked for me.
then choose flash the firmware in the yotaflasher tool and when it asks to flash userdata, you better press yes, otherwise it will probably bootloop, but so this also means EVERYTHING on your device is deleted
Greets and good luck!
Jblessing said:
Just bought this from Gearbest. It is unrooted. I don't have a "check for system updates" button in Settings,About phone.
1. Is there a way of enabling this or will OTA update happen automatically?
2. I have read about manually updating with the yotaphone flasher utility but some of the posts here are scaring me off. Has anyone successfully flashed the EU firmware onto this phone using the flasher?
Thanks
John
Click to expand...
Click to collapse
tomgaga said:
HI, I had the same with my phone from tinydeal.
You can update it manually, but prepare to lose all you data if you don't have it backed up in some way.
Also, you need to be sure that you are prepared to try again and mess around a little if it does not work. As far as i've read nobody has actually hardbricked the device by trying to flash it.
My advise would be to download the latest firware via the yotaflasher, whichever you like but rename the radio folder in the firmware folder in the yotaflasher folder so the radio part just stays the same, this worked for me.
then choose flash the firmware in the yotaflasher tool and when it asks to flash userdata, you better press yes, otherwise it will probably bootloop, but so this also means EVERYTHING on your device is deleted
Greets and good luck!
Click to expand...
Click to collapse
Thanks. I took the plunge and ran yotaflasher, downloaded the latest EU firmware and flashed the phone. It all went well, though after reboot there was a worrying 5 minutes as it stayed on the Yotaphone logo. Rebooted fine into lollipop and "about phone" now shows it as YD201. I didn't bother renaming the radio part of the firmware and, so far, it seems no worse or better than before flashing.
The system update option became available and it immediately downloaded the latest OTA update. All looks good so far.
I had contacted yotaphone support before I flashed the new firmware and they told me that as it was the Chinese version, there was no international support. I wonder if now it is showing as model yd201 whether I would get support ?
Jblessing said:
Thanks. I took the plunge and ran yotaflasher, downloaded the latest EU firmware and flashed the phone. It all went well, though after reboot there was a worrying 5 minutes as it stayed on the Yotaphone logo. Rebooted fine into lollipop and "about phone" now shows it as YD201. I didn't bother renaming the radio part of the firmware and, so far, it seems no worse or better than before flashing.
The system update option became available and it immediately downloaded the latest OTA update. All looks good so far.
I had contacted yotaphone support before I flashed the new firmware and they told me that as it was the Chinese version, there was no international support. I wonder if now it is showing as model yd201 whether I would get support ?
Click to expand...
Click to collapse
Nice to hear, and well you can probably het some support but I bet it will be rather useless anyways
Hi I tried to do this but when I put the phone in android recovery there are four options...reboot,apply update from adb,wipe data factory reset,and wipe cache partition,I think the correct option would be 2,apply update,but
---------- Post added at 01:29 AM ---------- Previous post was at 01:25 AM ----------
Hi I tried to do this but when I put the phone in android recovery there are four options...reboot,apply update from adb,wipe data factory reset,and wipe cache partition,I think the correct option would be 2,apply update,but yotaflasher stills waiting device and the phone says cannot load volume/misc!
Now send the package to applyto the device with adb sideload(filename)
What must I have to do?????
pedropicapiedra1 said:
Hi I tried to do this but when I put the phone in android recovery there are four options...reboot,apply update from adb,wipe data factory reset,and wipe cache partition,I think the correct option would be 2,apply update,but
---------- Post added at 01:29 AM ---------- Previous post was at 01:25 AM ----------
Hi I tried to do this but when I put the phone in android recovery there are four options...reboot,apply update from adb,wipe data factory reset,and wipe cache partition,I think the correct option would be 2,apply update,but yotaflasher stills waiting device and the phone says cannot load volume/misc!
Now send the package to applyto the device with adb sideload(filename)
What must I have to do?????
Click to expand...
Click to collapse
You don't need to put your phone into Android recovery mode to flash. Just hold power and volume down until your phone displays Downloading... Now run YotaFlasher on your PC to flash your phone with the firmware you like.
stuck after tried flash
I ran into trouble when trying to flash my new Yotaphone2: After the flash-process (really quick) the yotaflash-software asked if I wanted to flash user-partition also (or sometihng to that extent). I answered "no". Now the phone seems stuck, only showing "powered by android". I read all the posts, but could find no solution. Fastboot does not find the phone. I can not power it off using any buttons, so I cannot put in in the flash-mode.
Any ideas what I can do?
klettervirus said:
I ran into trouble when trying to flash my new Yotaphone2: After the flash-process (really quick) the yotaflash-software asked if I wanted to flash user-partition also (or sometihng to that extent). I answered "no". Now the phone seems stuck, only showing "powered by android". I read all the posts, but could find no solution. Fastboot does not find the phone. I can not power it off using any buttons, so I cannot put in in the flash-mode.
Any ideas what I can do?
Click to expand...
Click to collapse
It's a common problem. Try this:
- Put your phone in download mode. Just keep holding power and volume down, it will get there eventually.
- Use the YotaFlash tool to flash the latest EU or RU firmware, whichever you like.
- After YotaFlash is finished your phone will reboot and still be in a bootloop
- Put your phone in download mode again. Just keep holding power and volume down.
- Now go into the command prompt on your computer and navigate to the YotaFlash folder (for me it is in C:\Program Files (x86)\yotaphone_flasher)
- Now type the following command with your phone still in download mode: fastboot flash -S 512M system firmware/system.img This will flash the failed system.img in multiple parts.
- After the flashing of the system partition is finished reboot your phone with the command: fastboot reboot
After this your phone will restart. It may take around 10 minutes to finish and if everything went right the Android unlock screen should appear.
Finally did work. Thanks a million! What helped was pushing power off and volume up, that brought up a menu where i could select to bring up "downloading" screen. You are the best, thank you!
What I learned today about being stuck in loops -
1. Bootloop - to exit a bootloop, press up volume and on button simultaneously to enter recovery mode. DO this until you arrive at the Android symbol, normal after 2 cycles, up to 2 minutes. You are then presented with a few options (select with on button), since you are flashing, normally you would go to bootloader mode "downloading" , then change the firmware (usually a zip) file.
This is method employed in the post just above.
2 The second is stuck at Yotaphone logo at beginning. Have you waited long enough ? Be patient, maybe it is still installing , allow 10 minutes before you try the following method . To break out of the stuck at Yotaphone logo, enter the bootloader mode , by pressing the on button and volume down button simultaneously. You cannot enter recovery mode as in point 1 above. This method will restart the phone. After the reboot starts, quickly hold down the volume up (only) button before the short "buzz" then you will enter recovery mode. You only have a few seconds to do this. In recovery mode you can delete the cache , user data or reboot but not enter bootloader mode.
still stuck in
VirtuaLeech said:
It's a common problem. Try this:
- Put your phone in download mode. Just keep holding power and volume down, it will get there eventually.
- Use the YotaFlash tool to flash the latest EU or RU firmware, whichever you like.
- After YotaFlash is finished your phone will reboot and still be in a bootloop
- Put your phone in download mode again. Just keep holding power and volume down.
- Now go into the command prompt on your computer and navigate to the YotaFlash folder (for me it is in C:\Program Files (x86)\yotaphone_flasher)
- Now type the following command with your phone still in download mode: fastboot flash -S 512M system firmware/system.img This will flash the failed system.img in multiple parts.
- After the flashing of the system partition is finished reboot your phone with the command: fastboot reboot
After this your phone will restart. It may take around 10 minutes to finish and if everything went right the Android unlock screen should appear.
Click to expand...
Click to collapse
still stuck in "waiting for device" and my phone is still in dowlaoding mood. please help.
To exit downloading mode , press the yotaphone ”on/off" button for about 30 seconds . It will restart in normal mode.
You have incorrect "adb composite" drivers and your phone is not communicating with your PC. Try to get rid of any bad adb drivers in device manager on your PC.
where to get ypflasher from?
Jblessing said:
Thanks. I took the plunge and ran yotaflasher, downloaded the latest EU firmware and flashed the phone. It all went well, though after reboot there was a worrying 5 minutes as it stayed on the Yotaphone logo. Rebooted fine into lollipop and "about phone" now shows it as YD201. I didn't bother renaming the radio part of the firmware and, so far, it seems no worse or better than before flashing.
The system update option became available and it immediately downloaded the latest OTA update. All looks good so far.
I had contacted yotaphone support before I flashed the new firmware and they told me that as it was the Chinese version, there was no international support. I wonder if now it is showing as model yd201 whether I would get support ?
Click to expand...
Click to collapse
where can i download the ypflasher/yotaflasher from? the yota official website no longer have it available for download! at least the downloaded zip file is empty?
thanks. in advance
Basem
basemaggad said:
where can i download the ypflasher/yotaflasher from? the yota official website no longer have it available for download! at least the downloaded zip file is empty?
thanks. in advance
Basem
Click to expand...
Click to collapse
ftp://fw.ydevices.com/YotaPhone2/YotaPhoneFlasher/
kophyo07 said:
still stuck in "waiting for device" and my phone is still in dowlaoding mood. please help.
Click to expand...
Click to collapse
go to yotaflasher folder (usually under programme files) and ensure that the individual files of the firmware you want to install are there and not zipped!
VirtuaLeech said:
- Now go into the command prompt on your computer and navigate to the YotaFlash folder (for me it is in C:\Program Files (x86)\yotaphone_flasher)
Click to expand...
Click to collapse
Hi well I have reached this point too but how to I ascertain the address to enter? Yes, yotaphone_flasher in in \Program Files but I'm told that C:\Program is not a valid command... Sorry I know this is basic PC computing 101 but after hours of trawling the net I am none the wiser. I am running XP. How can I see what the file path would be? Apparently there is a helpful utility to bring up the file path in the command prompt but of course it has been deleted because XP is no longer supported...
nutsoboy said:
I'm told that C:\Program is not a valid command... Sorry I know this is basic PC computing 101 but after hours of trawling the net I am none the wiser.
Click to expand...
Click to collapse
Did you try "cd Program Files"?
Make sure you are in the root directory C:\ (type "cd.." to go one level back through the hierarchy)
then type "cd Program Files\yotaphone_flasher" (if that is your folder path)
Jblessing said:
Thanks. I took the plunge and ran yotaflasher, downloaded the latest EU firmware and flashed the phone. It all went well, though after reboot there was a worrying 5 minutes as it stayed on the Yotaphone logo. Rebooted fine into lollipop and "about phone" now shows it as YD201. I didn't bother renaming the radio part of the firmware and, so far, it seems no worse or better than before flashing.
The system update option became available and it immediately downloaded the latest OTA update. All looks good so far.
I had contacted yotaphone support before I flashed the new firmware and they told me that as it was the Chinese version, there was no international support. I wonder if now it is showing as model yd201 whether I would get support ?
Click to expand...
Click to collapse
Hey,
Facing the exact issue of not being able to see the update option!
Planing to take the plunge my self but am a bit skeptical about the lollipop update. On facebook yotaphone page ppl have been complaining a lot about the lollipop update slowing down the phone and lot many other issues.
If I could get a little review from your side it would be very help full.
If there are any issues?
If so what are they?
Are they worth taking?
should I stick to kitkat?
ETC
tnautanki said:
Hey,
Facing the exact issue of not being able to see the update option!
Planing to take the plunge my self but am a bit skeptical about the lollipop update. On facebook yotaphone page ppl have been complaining a lot about the lollipop update slowing down the phone and lot many other issues.
If I could get a little review from your side it would be very help full.
If there are any issues?
If so what are they?
Are they worth taking?
should I stick to kitkat?
ETC
Click to expand...
Click to collapse
I have had no issues with lollipop, doesn't seem any slower or battery guzzling than kitkat
Jblessing said:
I have had no issues with lollipop, doesn't seem any slower or battery guzzling than kitkat
Click to expand...
Click to collapse
Same for me. Battery is good and I have no problem.

bricked after attempted flash: help

Hi
I have just attempted to flash my S5 G900F to Android 7 from 6.0.1, having followed a reasonably well detailed set of instructions.
because my phone won't respond to the 3 button recovery/download mode, I had to use ADB to access download mode and then connect to Odin to install TWRP.
Successfully using TWRP to wipe the directories and select the zip files of the new rom and apps.
when I selected Install, I got a screen full of red text all ending in failed and the phone froze. Being unresponsive to any buttons or gestures I had to remove the battery to turn it off.
Now for the Main problem, It won't boot, I get a message in yellow at the top of the flash screen "Set Warranty Bit : kernel" and it does nothing.
I tried to reboot with ADB but it shows "error : device ' (null)' not found".
I tried to do an emergency recovery with Smart-switch but it won't connect to the phone.
I tried to re-install TWRP with Odin but Odin doesn't connect.
and the 3 button recovery option still does not work.
HELP!!!!!!!!!!!!!!!!! anyone please or have I killed the phone.
Questions: What ROM did you flash on TWRP? Steps taken to flash (or link to the ROM that you used with the instructions you followed)? Which TWRP version?
I am unsure what else to try if you cannot boot into recovery or download mode, but this information will assist in a diagnosis and hopefully help from someone more experienced than me.
edit - saw that you flashed Lineage 14-1. and open-gapps-arm-6.0-micro.
Eggleston11 said:
Questions: What ROM did you flash on TWRP? Steps taken to flash (or link to the ROM that you used with the instructions you followed)? Which TWRP version?
I am unsure what else to try if you cannot boot into recovery or download mode, but this information will assist in a diagnosis and hopefully help from someone more experienced than me.
edit - saw that you flashed Lineage 14-1. and open-gapps-arm-6.0-micro.
Click to expand...
Click to collapse
Instructions found here: https://www.androidpit.com/samsung-galaxy-s5-android-manual-installation.
comuscomp said:
I tried to re-install TWRP with Odin but Odin doesn't connect.
and the 3 button recovery option still does not work.
HELP!!!!!!!!!!!!!!!!! anyone please or have I killed the phone.
Click to expand...
Click to collapse
Your phone definitely is not killed.
But you're in a logical trap because the problem is a hardware issue (buttons), not the firmware/odin/twrp.
So you need to repair the phone's buttons first, then flash it.
P.S. Was it possible to adjust the volume with the buttons when the phone was operational?
bbsc said:
Your phone definitely is not killed.
But you're in a logical trap because the problem is a hardware issue (buttons), not the firmware/odin/twrp.
So you need to repair the phone's buttons first, then flash it.
P.S. Was it possible to adjust the volume with the buttons when the phone was operational?
Click to expand...
Click to collapse
The volume buttons worked fine, the middle frame was replaced with a new one last week which came with Vol and Power buttons and the home button was replaced with a new one at the same time. along with the charging port.
comuscomp said:
The volume buttons worked fine, the middle frame was replaced with a new one last week which came with Vol and Power buttons and the home button was replaced with a new one at the same time. along with the charging port.
Click to expand...
Click to collapse
having taken the phone apart, I have tested the button functions on the middle frame with a multi meter, the Volume buttons work as they should as does the power button.
Shorting the relevant contacts on the main board produces the same results as before, ie, the Galaxy S5 Powered by Android screen, with the "Set Warranty Bit : kernel" in yellow at the top.
so unless there is a some way of forcing the phone to recognise the USB or getting into recovery, or a low level way of replacing the ROM I have a big problem.
comuscomp said:
the Volume buttons work as they should as does the power button.
Click to expand...
Click to collapse
And what about "home" button?
bbsc said:
And what about "home" button?
Click to expand...
Click to collapse
just tested with new Home button, same result.
comuscomp said:
just tested with new Home button, same result.
Click to expand...
Click to collapse
You definetily know, home button is really located on the USB (charging port) PCB, which you've just replaced, don't you?
bbsc said:
You definetily know, home button is really located on the USB (charging port) PCB, which you've just replaced, don't you?
Click to expand...
Click to collapse
Yes.
Then it looks like a mystery.
Maybe a jig resistor will help.
In theory, a 300 kOhm resistor between pins 4 and 5 of microUSB should make the phone boot to download mode.
bbsc said:
Then it looks like a mystery.
Maybe a jig resistor will help.
In theory, a 300 kOhm resistor between pins 4 and 5 of microUSB should make the phone boot to download mode.
Click to expand...
Click to collapse
Thanks for that, I don't have any resistors in my boxes, so I would need to order some but it was easier to order a ready made jig which should be here tomorrow so I'll let you know what happens.
If it works, do you know of a source of instructions in how to recover the system please?
If it works and if you're able to get into the download mode, I'd recommend to flash a factory service (4-files) firmware for your SM-G900F and your regional code.
It can be downloaded form Samsung servers with "samfirm" program.
bbsc said:
If it works and if you're able to get into the download mode, I'd recommend to flash a factory service (4-files) firmware for your SM-G900F and your regional code.
It can be downloaded form Samsung servers with "samfirm" program.
Click to expand...
Click to collapse
OK, I have downloaded the firmware file should I use odin, if so does it matter which version/release?
comuscomp said:
OK, I have downloaded the firmware file should I use odin, if so does it matter which version/release?
Click to expand...
Click to collapse
Yes, you should use Odin. I'm not sure which version is enough, I use 3.12, you can download it from my cloud.
If you've downloaded a service factory firmware file you can see 4 files inside zip.
Unpack the zip and "insert" these 4 files into Odin's slots:
BL - to BL
AP - to AP
CP - to CP
CSC - to CSC.
bbsc said:
Yes, you should use Odin. I'm not sure which version is enough, I use 3.12, you can download it from my cloud.
If you've downloaded a service factory firmware file you can see 4 files inside zip.
Unpack the zip and "insert" these 4 files into Odin's slots:
BL - to BL
AP - to AP
CP - to CP
CSC - to CSC.
Click to expand...
Click to collapse
used the Samfirm program but it downloaded 1 file: G900FXXS1CQD1_G900FOXA1CPJ6_G900FXXS1CQAV_HOME.tar.md5 not 4, there doesn't seem to be an option to download anything else.
https://forum.xda-developers.com/attachment.php?attachmentid=4320318&stc=1&d=1509554313
comuscomp said:
used the Samfirm program but it downloaded 1 file: G900FXXS1CQD1_G900FOXA1CPJ6_G900FXXS1CQAV_HOME.tar.md5 not 4, there doesn't seem to be an option to download anything else
Click to expand...
Click to collapse
Check "Auto" and "Binary Nature" and try again.
bbsc said:
Check "Auto" and "Binary Nature" and try again.
Click to expand...
Click to collapse
Thanks, it's now giving me a different file.
comuscomp said:
Thanks, it's now giving me a different file.
Click to expand...
Click to collapse
It's a "must have" file in your situation because this service firmware reformats and wipes the phone's memory without need to enter recovery.
If you could get into recovery then a common "HOME" firmware would be enough.
bbsc said:
It's a "must have" file in your situation because this service firmware reformats and wipes the phone's memory without need to enter recovery.
If you could get into recovery then a common "HOME" firmware would be enough.
Click to expand...
Click to collapse
Dongle arrived this morning, plugged in and recovery mode in 3 seconds, used Odin 3.12 with the 4 file download and the phone is back to Android 6.0.1.
Thank you very much for all your help, I have learnt a lot, never having used Android before. At least if I try to root again and things go wrong, I now have a bit more knowledge to rectify things.

Unbrick a SM-J510MN using a working SM-J510MN

How to unbrinck an SM-J510MN using another one that is working to get the files needed for odin.
Does having a working device help me?
When I try to use odin I get the message "Volume Size is Too big"
Thanks
Gianlucas94 said:
How to unbrinck an SM-J510MN using another one that is working to get the files needed for odin.
Does having a working device help me?
When I try to use odin I get the message "Volume Size is Too big"
Thanks
Click to expand...
Click to collapse
Wrong firmware.
I had my original SM-J510MN bricked last night because I tried to install a corrupt or incompatible TWRP image on it, so, in the way all through the hell I did the following:
1. There is no information on Google about this exact machine (MSM8960).
2. I messed up with SmartSwitch PC Software piece of junk by reinstalling the driver which never worked, provided by its own SmartSwitch option menu.
3. That driver installed before was never going to work because you have to boot Windows 7 in a way to avoid signed drivers checking (Pressing F8 at boot).
4. After research I found out that I had to downgrade the SmartSwitch version to a one with the enabled tab "Device initialization".
5. Finally, I had the driver and a correct SmartSwitch version just to realize I had to type the Model name of my device in UPPERCASE because those Samsung engineers didn't realize a normal user may be would type in lowercase ().
6. I typed the S/N (serial number) located on the backside of the phone and I got the message "Please check the model name and S/N, and enter them again". I triple checked the inserted values, to this point I was feeling I'm totally lost.
7. I downloaded at least 10 Gibibytes (Gigabytes but in the right terms) in stock ROMs which none of them worked for multiple and different reasons.
So this beautiful COVID-19 lockdown morning I woke up inspired thanks Jehovah God and I just tried the old way to inspect this whole site by using Google like this: "site:xda-developers.com j510mn" and I found a compatible fully working TWRP that I flashed using Odin v3.14.1 and then the phone booted normally.
While I was looking for a custom ROM then I didn't realize the WiFi stopped working so I am looking for a solution.
2020-06-06
To bring the Wi-Fi back to my device I had to flash LineageOS 14.1, and then you will be able to flash any custom ROM you may find.
I hope this helps, greetings from Colombia.
akira_yuki said:
I had my original SM-J510MN bricked last night because I tried to install an incompatible TWRP on it (wrong device with similar name), so, in the way all through the hell I did the following:
1. There is no information in Google about this exact machine (MSM8960).
2. I messed up with SmartSwitch PC Software piece of junk by reinstalling the driver which never worked, provided by its own SmartSwitch option menu.
3. That driver installed before was never going to work because you have to boot Windows 7 in a way to avoid signed drivers checking (Pressing F8 at boot).
4. After a research I found out that I had to downgrade the SmartSwitch version to a one with the enabled tab "Device initialization".
5. Finally I had the driver and a correct SmartSwitch version just to realize I had to type the Model name of my device in UPPERCASE because those Samsung engineers didn't realize a normal user may be would type in lowercase ().
6. I typed the S/N (serial number) located on the backside of the phone and I got the message "Please check the model name and S/N, and enter them again". I triple checked the inserted values, to this point I was feeling I'm totally lost.
7. I downloaded at least 10 Gibibytes (Gigabytes but in the right terms) in stock roms which none of them worked for multiple and different reasons.
So this beautiful COVID-19 lockdown morning I woke up inspired thanks Jehovah God and I just tried the old way to inspect this whole site by using Google like this: "site:xda-developers.com j510mn" and I found a compatible fully working TWRP that I flashed using Odin v3.14.1
I hope this helps, greetings from Colombia.
Click to expand...
Click to collapse
When you open your device hold power button + Down volume + home button and flash the stock ROM, its a soft brick, not hard brick. J510MN is fully compatible with every version of TWRP.
NecromancerViper said:
When you open your device hold power button + Down volume + home button and flash the stock ROM, its a soft brick, not hard brick. J510MN is fully compatible with every version of TWRP.
Click to expand...
Click to collapse
OK, sorry for not having been that explicit, but I'm going to be right now:
Last night I had a useless phone...
satisfied?
does your correction help in any way? does that help with the initial post at all? is there any difference between hard and soft bricked that could help on that?
akira_yuki said:
OK, sorry for not having been that explicit, but I'm going to be right now:
Last night I had a useless phone...
satisfied?
does your correction help in any way? does that help with the initial post at all? is there any difference between hard and soft bricked that could help on that?
Click to expand...
Click to collapse
I mean, 3.2 and 3.3 versions of TWRP support MN

Categories

Resources