Hi Guys
I've been at this for almost 10 hours now and i need a solution. Every time i try and root through the method below, everything works fine till about step 17 where an error at formatting system pops up every time i try to format the system. Is there a reason why? and i cant access my memory card too from that recovery method.
http://forum.xda-developers.com/showthread.php?t=2642081
han_si said:
Hi Guys
I've been at this for almost 10 hours now and i need a solution. Every time i try and root through the method below, everything works fine till about step 17 where an error at formatting system pops up every time i try to format the system. Is there a reason why? and i cant access my memory card too from that recovery method.
http://forum.xda-developers.com/showthread.php?t=2642081
Click to expand...
Click to collapse
Which recovery menu are you using? TWRP or Philz touch? Which dualrecovery did you use? (do not use version 2.7.97)
Hey really appreciate the reply.
So I get through everything correctly till step 13, i run the lockedualrecovery 2.7.92, i run the install.bat file, runs smoothly till it says waiting for device to reboot, where it hangs for a while. I end up unplugging phone, force the phone off, and turn it on again and plug the usb back in, and then it says installation successful...(I have read somewhere the kernel gets the phone to reboot once rooted, but i've waited over an hour and it doesnt reboot, this is why i plugged it off, force it off then on again for the installation successful to come up)
I get through step 14,15 and 16.
Once in step 17, in Philz touch recovery, when i try to format it says error in formatting and has all these errors again when i try to factory reset through Philz Touch recovery. I then try and access my external_sd but my memory card is not readable through it (checked its not in exFAT, it was in FAT32 which is the default windows format).
So i end up booting in TWRP recovery. Tried and installing the 3 files in order that way. Rebooted it in from TWRP and the phone is just dead, Doesn't turn on whatsoever. However i am able to repeat the processes again. Repeated processes almost 5 times now, no luck.
Is my Kernel dead? is there a kernel i can flash to fix so i can restore to factory settings? or is it totally different issue. I hope phone isnt bricked.
Please need your help. Thanks heaps.
Hanafi.
zxz0O0 said:
Which recovery menu are you using? TWRP or Philz touch? Which dualrecovery did you use? (do not use version 2.7.97)
Click to expand...
Click to collapse
Use the latest recovery installer 2.7.99
Sent from my D5503 using xda app-developers app
this is frustrating now, how do i just restore back to factory settings. i cant find the option through pc companion, is there a stock rom i can flash?? pls help, thanks
han_si said:
this is frustrating now, how do i just restore back to factory settings. i cant find the option through pc companion, is there a stock rom i can flash?? pls help, thanks
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2631291
han_si said:
this is frustrating now, how do i just restore back to factory settings. i cant find the option through pc companion, is there a stock rom i can flash?? pls help, thanks
Click to expand...
Click to collapse
Just start again from step 1 and use a newer dualrecovery (do not use version 2.7.97).
Related
So i was using slyking241 rom for a wile but then i decided to go back to stock rom i followed this:http://forum.xda-developers.com/showthread.php?t=1011527 tutorial step by step to reset my phone but when it starts updating it says unpacking and then updating gives na error i tried it multiple time but no luck then i though that i should go back to the 2.3.7 sly rom but it refused to boot up just get the cwm boot screen and endless reboots so i wiped data , cache,dalvik,battery stats but it still wont boot i reflashed the rom still doesnt boot tried 2.2 rom still doesn't boot..(cant past the sand clock icon) the recovery works fine i thought of istalling new recovery but i cant get into bootloader please help.
Thank You
bump
The U8120 hasn't a real bootloader.
You hould flash the phone again!
And I mean fullflash (root the phone,install AmonRA...)
Just like you want to root it.
In my Thread (just click U8120 in signature) you can download the stock rom!
P.S.on't change the recovery after rooting!
Eclair works only with AmonRA
!FORMAT YOUR SDCARD BEFORE TRYING THIS!
how should i reinstall it if it doesnt boot up?
Jorius said:
how should i reinstall it if it doesnt boot up?
Click to expand...
Click to collapse
You got a SD-Card Adapter?
If not go to CWM and use USB Massstorage.
For rooting google a bit :-D
Sent from my A10 using XDA
i mean how to i flash recovery if it doesnt work?
Lololololololololol said:
You got a SD-Card Adapter?
If not go to CWM and use USB Massstorage.
For rooting google a bit :-D
Sent from my A10 using XDA
Click to expand...
Click to collapse
mass storage doesn not work if it doesnts turn on + i didnt find anything to root a not working phone
Hello all,
Quick background - my wife's T-Mobile S4 went kaput on our honeymoon last night, but I was at least able to save some of her data. The problem now goes to installing a new ROM on her device.
I have wiped EVERYTHING and formatted the data, but when I install ANY ROM (I've tried multiple), I always get the E: Unable to mount '/data" error. Normally, I would just ODIN the stock tar, then install a custom recovery again and then the ROM, but I only have my work computer for the rest of my honeymoon and I don't have administrative access to run ODIN (you might not think it requires it, but if you're only a standard user then you cannot bypass UAC to run it).
Does anyone have any ideas on how to get this to mount? The phone will not boot past the "Samsung Galaxy S4" screen. I've tried going into TWRP and mounting Data but it will not work.
Any help is greatly appreciated! Please keep in mind that I don't have access to ODIN!
- Taxmaster
Taxmaster said:
Hello all,
Quick background - my wife's T-Mobile S4 went kaput on our honeymoon last night, but I was at least able to save some of her data. The problem now goes to installing a new ROM on her device.
I have wiped EVERYTHING and formatted the data, but when I install ANY ROM (I've tried multiple), I always get the E: Unable to mount '/data" error. Normally, I would just ODIN the stock tar, then install a custom recovery again and then the ROM, but I only have my work computer for the rest of my honeymoon and I don't have administrative access to run ODIN (you might not think it requires it, but if you're only a standard user then you cannot bypass UAC to run it).
Does anyone have any ideas on how to get this to mount? The phone will not boot past the "Samsung Galaxy S4" screen. I've tried going into TWRP and mounting Data but it will not work.
Any help is greatly appreciated! Please keep in mind that I don't have access to ODIN!
- Taxmaster
Click to expand...
Click to collapse
Sounds like a twrp issue. Try grabbing the cwm flash able zip and adb push to the sd card and then use twrp to install it. I've read so many issues about twrp. I recommend staying away from it. Philz touch recovery is really awesome too.
Sent from my SGH-M919 using Tapatalk 2
elesbb said:
Sounds like a twrp issue. Try grabbing the cwm flash able zip and adb push to the sd card and then use twrp to install it. I've read so many issues about twrp. I recommend staying away from it. Philz touch recovery is really awesome too.
Sent from my SGH-M919 using Tapatalk 2
Click to expand...
Click to collapse
Hello! I actually downloaded Philz touch recovery in both .zip and in .md5, so that is what I intend to go with. The issue is how I push it using adb, as I believe I need to install something in order to do so, but I don't have any administrative privileges! This is what's preventing me from running ODIN in the first place!
Can you confirm that I can push using adb without installing anything?
Thank you! - Taxmaster
I had this issue. Odin flashing and then booting into "STOCK RECOVERY" after flashing and then a factory reset in the stock recovery followed by a fresh re-flash from Odin worked to get my phone back up and running again.
I don't know how you are going to be able to fix it by just flashing a recovery. I tried for hours and could not get it to boot from just recovery alone.
Monkz said:
I had this issue. Odin flashing and then booting into "STOCK RECOVERY" after flashing and then a factory reset in the stock recovery followed by a fresh re-flash from Odin worked to get my phone back up and running again.
I don't know how you are going to be able to fix it by just flashing a recovery. I tried for hours and could not get it to boot from just recovery alone.
Click to expand...
Click to collapse
What you noted would be my plan if I had admin rights to my computer, but since I cannot get ODIN, I'm screwed at the moment. I'm hoping someone can assist with the "adb" proposal, however I'm not sure one can download/run adb without installation or prompt from UAC
Taxmaster said:
What you noted would be my plan if I had admin rights to my computer, but since I cannot get ODIN, I'm screwed at the moment. I'm hoping someone can assist with the "adb" proposal, however I'm not sure one can download/run adb without installation or prompt from UAC
Click to expand...
Click to collapse
I don't believe admin is required for adb... You could always try it... worst thing that could happen would be nothing.
lordcheeto03 said:
I don't believe admin is required for adb... You could always try it... worst thing that could happen would be nothing.
Click to expand...
Click to collapse
Using ADB does not require admin privelages, however, if your computer does not have the necessary drivers to detect the device in recovery, then you will have to install the drivers, which then yes UAC is required. HOWEVER, if you have another phone or device that supports MicroSD cards, you can just pop in the MicroSD into a working device and transfer the zip that way, then transfer back the sd card and flash
elesbb said:
Using ADB does not require admin privelages, however, if your computer does not have the necessary drivers to detect the device in recovery, then you will have to install the drivers, which then yes UAC is required. HOWEVER, if you have another phone or device that supports MicroSD cards, you can just pop in the MicroSD into a working device and transfer the zip that way, then transfer back the sd card and flash
Click to expand...
Click to collapse
I did exactly what's noted above --> took out the SDcard, put it in another phone, transferred over the .zip, put it back in her phone, went to TWRP, wiped everything on the device, installed the .zip, and rebooted into recovery from TWRP, and then the new recovery booted! I did another wipe/factory reset and then installed a ROM, but when I hit reboot, it didn't reboot past the Samsung Galaxy S4 splash screen , and to make matters worse, when I go to enter recovery pressing home+up+power, it says "Recovery Booting ...." in the top left corner but it won't boot into recovery!!!
Thoughts?
If someone could strip administrative privileges off of a version of ODIN v3 for me, that would be great! I don't see how else to get around this now!
-Taxmaster
Taxmaster said:
I did exactly what's noted above --> took out the SDcard, put it in another phone, transferred over the .zip, put it back in her phone, went to TWRP, wiped everything on the device, installed the .zip, and rebooted into recovery from TWRP, and then the new recovery booted! I did another wipe/factory reset and then installed a ROM, but when I hit reboot, it didn't reboot past the Samsung Galaxy S4 splash screen , and to make matters worse, when I go to enter recovery pressing home+up+power, it says "Recovery Booting ...." in the top left corner but it won't boot into recovery!!!
Thoughts?
If someone could strip administrative privileges off of a version of ODIN v3 for me, that would be great! I don't see how else to get around this now!
-Taxmaster
Click to expand...
Click to collapse
Out of curiosity, are you flashing a ROM for the T-Mobile S4? If no, are you using a T-Mobile kernel? I only ask because a kernel for a different device will normally cause you to not be able to pass the initial Galaxy S4 screen... Also, as far as TWRP goes, sometimes it doesn't go right into recovery. If it fails to enter recovery after a reasonable amount of time, just hold power to turn it off and try again. I've had to do it 2-3 times at least just to successfully enter TWRP.
lordcheeto03 said:
Out of curiosity, are you flashing a ROM for the T-Mobile S4? If no, are you using a T-Mobile kernel? I only ask because a kernel for a different device will normally cause you to not be able to pass the initial Galaxy S4 screen... Also, as far as TWRP goes, sometimes it doesn't go right into recovery. If it fails to enter recovery after a reasonable amount of time, just hold power to turn it off and try again. I've had to do it 2-3 times at least just to successfully enter TWRP.
Click to expand...
Click to collapse
I am installing a T-Mobile S4 ROM that uses a custom kernel. The ROM before was the same ROM just a lower revision, same kernel.
With respect to TWRP, I thought it was all gone now that I installed the CWM touch version. I've tried doing it a million times and cannot get back into either TWRP or CWM. At this point, the only thing I can do is turn on the device to see the "Samsung Galaxy S4" screen, attempt booting into recovery but never make it past the screen saying "Recovery Booting", or enter Download Mode but I cannot use it since I can't run ODIN on my work laptop .... stupid admin privileges!
Taxmaster said:
I am installing a T-Mobile S4 ROM that uses a custom kernel. The ROM before was the same ROM just a lower revision, same kernel.
With respect to TWRP, I thought it was all gone now that I installed the CWM touch version. I've tried doing it a million times and cannot get back into either TWRP or CWM. At this point, the only thing I can do is turn on the device to see the "Samsung Galaxy S4" screen, attempt booting into recovery but never make it past the screen saying "Recovery Booting", or enter Download Mode but I cannot use it since I can't run ODIN on my work laptop .... stupid admin privileges!
Click to expand...
Click to collapse
Not sure what happened there.. very strange. But seems as if you have no recovery xD lol Maybe heimdall will work. Never used it not sure if it needs UAC to work. But dont use TWRP anymore
As far as your situation goes, maybe if you have the time and fast enough internet, see if you can download a linux distro (i recommend fedora as it is small and light) then make a bootable USB from that distro (if you have a flash drive) then use Heimdall in linux to flash the tar image.
Or just wait to get home. not sure how long your honeymoon is xD
elesbb said:
Not sure what happened there.. very strange. But seems as if you have no recovery xD lol Maybe heimdall will work. Never used it not sure if it needs UAC to work. But dont use TWRP anymore
As far as your situation goes, maybe if you have the time and fast enough internet, see if you can download a linux distro (i recommend fedora as it is small and light) then make a bootable USB from that distro (if you have a flash drive) then use Heimdall in linux to flash the tar image.
Or just wait to get home. not sure how long your honeymoon is xD
Click to expand...
Click to collapse
I think I just need to accept that fact that I have been had and that the only thing I can do is wait until I'm home to use ODIN. Absolutely asinine in my opinion, however it seems the only logical conclusion at this point.
If anyone else cares to chime in with suggestions, please let me know!
-Taxmaster
I have had the same problem several times. The only way I have been able to boot up is to completely format data and either restore from backup or reflash a new ROM. If I wipe the dalvik cache after doing so however, it will not boot (hangs at the galaxy s4 screen like you said) and I will have to reflash or restore a 2nd time. (I'm using twrp too, but will switch to cwm if this happens again)
I m curious. Have you run into this problem again? Seems like every time my phone shuts off and tries to boot I have to restore from a backup that is days or weeks old. Super annoying. The first time this happened I restored to stock from Odin and did not use any backups in the hope that it would solve my problem and prevent it from happening again. No such luck.
coolastar said:
I have had the same problem several times. The only way I have been able to boot up is to completely format data and either restore from backup or reflash a new ROM. If I wipe the dalvik cache after doing so however, it will not boot (hangs at the galaxy s4 screen like you said) and I will have to reflash or restore a 2nd time. (I'm using twrp too, but will switch to cwm if this happens again)
I m curious. Have you run into this problem again? Seems like every time my phone shuts off and tries to boot I have to restore from a backup that is days or weeks old. Super annoying. The first time this happened I restored to stock from Odin and did not use any backups in the hope that it would solve my problem and prevent it from happening again. No such luck.
Click to expand...
Click to collapse
I ended up having to wait until I got home to use ODIN. I ODIN'd up the stock .tar and then installed Philz touch recovery (CWM-based), then I did a full wipe of everything and installed a ROM. Problem solved.
With that noted, I abandoned TWRP and am now only using CWM on my wife's phone.
Taxmaster said:
I ended up having to wait until I got home to use ODIN. I ODIN'd up the stock .tar and then installed Philz touch recovery (CWM-based), then I did a full wipe of everything and installed a ROM. Problem solved.
With that noted, I abandoned TWRP and am now only using CWM on my wife's phone.
Click to expand...
Click to collapse
Same, TWRP just has too many problems.
CWM is much more reliable.
Sent from my SGH-M919 using xda premium
Taxmaster said:
I ended up having to wait until I got home to use ODIN. I ODIN'd up the stock .tar and then installed Philz touch recovery (CWM-based), then I did a full wipe of everything and installed a ROM. Problem solved.
With that noted, I abandoned TWRP and am now only using CWM on my wife's phone.
Click to expand...
Click to collapse
If you were using TWRP 2.6.0, that could have been the problem. I reverted back to 2.5.0.2 and like many others, have had no issues. If you had a TWRP backup, that might have fixed it early on.
i accidently enabled some option under development tools (something about dual display, and i pressed in 1080p option) and when i did that the hole phone froze and i restarted and now it keeps getting stuck in boot.
But the hardest part is that i can't get in to CWM i keep trying but it just boots over and over again. I even tried to install another CWM with odin but no luck there still the same.. cause i have a backup but i can't reach it.
so if you guys don't know how to fix it could you tell me how to wipe all so i can re-install cm10.2 and then just restore from the backup i did before that's sitting on my ext.sdcard
:c
RaW D Coy said:
i accidently enabled some option under development tools (something about dual display, and i pressed in 1080p option) and when i did that the hole phone froze and i restarted and now it keeps getting stuck in boot.
But the hardest part is that i can't get in to CWM i keep trying but it just boots over and over again. I even tried to install another CWM with odin but no luck there still the same.. cause i have a backup but i can't reach it.
so if you guys don't know how to fix it could you tell me how to wipe all so i can re-install cm10.2 and then just restore from the backup i did before that's sitting on my ext.sdcard
Click to expand...
Click to collapse
Some suggestion
A) Try to download full wipe stock rom which you will get 5 files.
Or
B) flash twrp thru odin pc , boot into it and perform full wipe.
Or
C) Download bootloader and flash it thru pc odin and full wipe rom as well ( dangerous)
Just for your information, please use search function to find the related thread( mentioned above) and understand it before you proceed.
Sent from my GT-N7100 using xda premium
lee yun khong said:
Some suggestion
A) Try to download full wipe stock rom which you will get 5 files.
Or
B) flash twrp thru odin pc , boot into it and perform full wipe.
Or
C) Download bootloader and flash it thru pc odin and full wipe rom as well ( dangerous)
Just for your information, please use search function to find the related thread( mentioned above) and understand it before you proceed.
Sent from my GT-N7100 using xda premium
Click to expand...
Click to collapse
i flashed twrp, but i can't get in to recovery it keeps re-booting...
nvm manage to get it working
RaW D Coy said:
nvm manage to get it working
Click to expand...
Click to collapse
What did you do to get it work??
traumatic said:
What did you do to get it work??
Click to expand...
Click to collapse
i don't really know i keept flashing over and over again with the CWM and then i suddenly got in to it and i coul reset and install my rom again but now the problem is that my baseband is wrong and i can't find a Nordic Modem dl for it so my mobile network is offline...
Hey guys, I'm now trying to fix my problem for 2 days straight, but I think I'm just too noobie.
After using my phone regularly in the evening and putting it into standby afterwards, i woke up the next morning and saw my phone in a bootloop (just the pulsating Samsung logo).
My Note 2 was rooted. but I had the original firmware (4.3 I think).
All I can do now is booting into recovery (I had to reinstall CWM since it was gone) and boot into download modus.
Also, I get the error: E:failed to mount /efs (Invalid argument)
When I just let it sit for a few minutes, it sometimes plays the startup animation with sound, which is sometimes ending abruptly and after a few minutes more it just boots into recovery.
When I'm in CWM-Recovery, I can't use ADB (phone is not listed)
What I have tried:
Wipe data/factory reset
Install the stock-rom with Odin (one-part, I cant find a three-parted one)
Install a custom rom
I'm looking forward to see any helpful suggestions, also I have to apologize for my bad English, I'm not a native speaker :angel:
What third part?
ceomaverick said:
What third part?
Click to expand...
Click to collapse
PDA, phone and CSC, or is that unnecessary?
Re flash firmware....
Sent from my GT-N7100 using XDA Premium 4 mobile app
cruelscene said:
Re flash firmware....
Sent from my GT-N7100 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
If you mean flashing a firmware in CWM, I've already done that.
#push
Please guys, I really need help
Did odin show you some error messages? Anyway where did you download the firmware from? are you sure its the correct one?
Usually bootloop problems are solved by flashing the stock firmware. Please check the version of the firmware you have and make sure its the last relase and the correct one (there are a lot of note 2 models)
- Try flashing with a formatted sd or without the sd
- try to change usb port/cable/pc
- redownload the firmware from another site and try to reflash
- do you have a backup? can you revert to that?
- do you have a ESF backup?
When flashing via Odin please follow:
1. click on “PDA” button and choose the “.tar.md5” file from the folder where you’ve extracted the downloaded firmware file.
2.Ensure that only “Auto Reboot” and “F. Reset” are checked in Odin, do not make any other changes.
3.click on “Start” button to begin the flashing process.
4.As soon as the flashing process has completed, you will see a “PASS” message in Odin and your device will reboot automatically.
-after you flash the stock firmware try to wait at least 15 min for the first boot, then if it wont boot go on the original recovery and try wiping cache and factory reset then reboot and see if you are lucky.
- anyway keep us updated, more info = more chances to understand the problem = usually more chances to fix it
Well, I don't know why, but I tried flashing TWRP instead of CWR a few minutes ago and tried fixing the efs error with the help of this thread : http://forum.xda-developers.com/galaxy-s3/general/how-to-fix-efailed-to-mount-efs-invalid-t2858056 .
ADB commands did not work with CWR, but using TWRP I was able to use them, now my Note is turning on again.:good:
Obviously i was too dumb to make any backups of my efs folder, so now I just have got the developer IMEI and can't use mobile service.
Any suggestions?
SquatBaby said:
Well, I don't know why, but I tried flashing TWRP instead of CWR a few minutes ago and tried fixing the efs error with the help of this thread : http://forum.xda-developers.com/galaxy-s3/general/how-to-fix-efailed-to-mount-efs-invalid-t2858056 .
ADB commands did not work with CWR, but using TWRP I was able to use them, now my Note is turning on again.:good:
Obviously i was too dumb to make any backups of my efs folder, so now I just have got the developer IMEI and can't use mobile service.
Any suggestions?
Click to expand...
Click to collapse
please check this post by dr. ketan http://forum.xda-developers.com/showthread.php?t=2420881 got all the info you need
or try this https://www.youtube.com/watch?v=Pai4BH3AWq8 (never tried it)
giovait said:
please check this post by dr. ketan http://forum.xda-developers.com/showthread.php?t=2420881 got all the info you need
or try this https://www.youtube.com/watch?v=Pai4BH3AWq8 (never tried it)
Click to expand...
Click to collapse
none of the methods seem to work for me.
is there anything else I can do?
Anyone got some advice?
Hello,
A friend of mine tried to change from stock ROM to Eragon a few days ago.
He wiped all data and then tried to flash the ROM from Android system recovery but it wont install the ROM.
So now the phone just loads the boot screen when its started but nothing happens after that. I can still get access to Android system recovery.
From what I understand, he should have installed CWM before doing anything really but what's done is done.
Is there a way to save his phone?
Hi,
no worries, it's safe! Just reflash Stock ROM, afterwards CWM and install Eragon.
BlueFlame4 said:
Hi,
no worries, it's safe! Just reflash Stock ROM, afterwards CWM and install Eragon.
Click to expand...
Click to collapse
I have downloaded K05TS-A.A.vA0L.E1.150725.zip (Stock ROM Elephone P8000_20150909_Android)
put that on sd card, then I tried to "apply update from sdcard"
then I get "opening update package..." then "installation aborted"
is there something im doing wrong?
You need to use the sp flash tool, there is a guide somewhere so either try the BBS.elephone forum or Google it you will need to install mtk drivers on your PC/laptop...
charliepie said:
You need to use the sp flash tool, there is a guide somewhere so either try the BBS.elephone forum or Google it you will need to install mtk drivers on your PC/laptop...
Click to expand...
Click to collapse
Sp flash tool wont start to download.
Is there a certain setting that needs to be on phone, when you just connect it android preloader shows up in drivers quickly and then disappear. But if you hold down Vol - you get "CDC Serial"
But when in fastboot you get android "ADB Interface."
From what I have understood you want to stay in Preloader.
How do I do that?
Have read about sp flash tool, but there seems to be problems with the downloading proces and the mtk drivers.
Any idéas?
Click download first and then connect the phone while it's off. The guide on elephone's site is weirdly explained.
marwall said:
Hello,
A friend of mine tried to change from stock ROM to Eragon a few days ago.
He wiped all data and then tried to flash the ROM from Android system recovery but it wont install the ROM.
So now the phone just loads the boot screen when its started but nothing happens after that. I can still get access to Android system recovery.
From what I understand, he should have installed CWM before doing anything really but what's done is done.
Is there a way to save his phone?
Click to expand...
Click to collapse
1. Install drivers on your pc
2. download spflashtool
Turn off phone
3. format all + download K05TS-A.A.vA0L.E1.150725.zip
connect phone to pc while off
4. when its done start phone, takes around 5minutes to boot up.
5. download cwm recovery
6. use Spflashtool again and flash cwm.
7. put eragon 2.5 on your SDcard
8. Restart phone in recovery, turn off, powerbutton + vol up.
9. wipe data / factory and cash, and delvik cash.
10. install eragon 2.5
DONE
Thanks for all your suggestions on how to fix it.
I will try them as soon as possible.
To be clear:
You can only install STOCK ROM with SP Flash Tool
You can only install ERAGON ROM via Recovery
To install ERAGON you need to be ROOT'ed and have working CUSTOM Recovery...
Followed Peinnes list of what to do and it worked!
Thanks alot for the help!
Thx very much for this solution that work fine
Just i lose my imei duration and i fix it via the EngineerMode (*#*#3646633#*#*) connectivity - cds information - radio information - phone 1 - AT+ EGMR=1,7,"IMEI" and for phone 2 AT+ EGMR=1,10,"IMEI" (with the space between + and E and a restart at the evry time), you save me
Have a nice day