Database Develop

[Kernel] Unsecured Boot Images

Samsung made these devices a bit more secure than normal (this is a good thing), by making adbd ignore ro.kernel.qemu/ro.secure/ro.debuggable.
However some people prefer an unsecured boot image that runs adbd as root, so here you go. These are stock with ro.secure=0 set, and with a standard AOSP adbd, please match them with your firmware (do not flash to other firmwares)
IML74K_P3113UEALCB
http://goo.im/devs/jcase/IML74K_P3113UEALCB_boot.zip
f16b0fdcba6988b9cfbdc1eb084b4a6b IML74K_P3113UEALCB_boot.zip
IML74K_P3113UEALD3
http://goo.im/devs/jcase/IML74K_P3113UEALD3_boot.zip
ba434a9112b293f93111d6266ca22c6d IML74K_P3113UEALD3_boot.zip
Flash from Clockwork recovery.
Again, only flash these to corresponding firmwares/devices.

hi jcase can u upload unsecured boot images for GT-P3100.. would be of great help
Badly in need for root

Seconded, I just update my P3100 via OTA to 4.0.4 and now I can't root the device.

@innov have u tried method from this post link? http://forum.xda-developers.com/showpost.php?p=27792825&postcount=11
posted by the guy above your post... previously i had the same problem but solved by following guide from the link... :good:

baliriot said:
@innov have u tried method from this post link? http://forum.xda-developers.com/showpost.php?p=27792825&postcount=11
posted by the guy above your post... previously i had the same problem but solved by following guide from the link... :good:
Click to expand...
Click to collapse
Will this method erases the old data / system? If yes then I will try this as last resort but in the meantime if there's safer (and smaller downloads, the full rom is about 700 mb in size) way I'll try that first.

What i did, just flash the recommended firmware over my existing 4.0.4 XXBLE3 & no data wiped after finished boot...

baliriot said:
@innov have u tried method from this post link? http://forum.xda-developers.com/showpost.php?p=27792825&postcount=11
posted by the guy above your post... previously i had the same problem but solved by following guide from the link... :good:
Click to expand...
Click to collapse
Thanks I managed to root my phones via the link you gave , glad I won't have to search for unsecured boot images or factory reset my P3100.

yeay, glad that method by incredible.razz helped

[ROM][CWM][Recovery][Pre-Rooted]Tablet Z Stock 10.1.C.0.370 -Reboot FIX Included

Just share the ROM using now, for those who want to keep BL locked.
Please note that this is a Japan version, for WiFi models.
STOCK 10.1.C.0.370 JP
Recovery Pre-installed
Pre-Rooted
Reboot issue Fixed (Credit goes to @Carceri, Modified a bit to make it work. Another solution by @[NUT] :[Locked Bootloader] The definitive root Remount-Reboot fix!)
Init.d support
Nothing more～
Download Here：
Part1 Part2
Installation:
1. Backup everything in case of any bad luck.
2a. Flash 370 FTF without system and data.
2b.1. Or update to 370 official with SONY Update Service for more insurance (This will WIPE EVERYTHING if 370 already installed/it failed to update, Confirm your Backup 65535 times before start).
2b.2. Unplug and Flash 344 FTF, system only.
3. Get root with Bin4ry's tool.
4. Install Recovery.
5. Flash the zip.

does bootloader need to be unlocked for this?

shaun.s said:
does bootloader need to be unlocked for this?
Click to expand...
Click to collapse
No，it's for locked BL so recovery and root/su are integrated, which can be provided by a custom kernel.

Fishmanzero said:
No，it's for locked BL so recovery and root/su are integrated, which can be provided by a custom kernel.
Click to expand...
Click to collapse
you rock!
thanks downloading now
---------- Post added at 06:20 PM ---------- Previous post was at 06:17 PM ----------
Fishmanzero said:
No，it's for locked BL so recovery and root/su are integrated, which can be provided by a custom kernel.
Click to expand...
Click to collapse
is this for 16GB version?
I have 32GB LTE

shaun.s said:
you rock!
thanks downloading now
---------- Post added at 06:20 PM ---------- Previous post was at 06:17 PM ----------
is this for 16GB version?
I have 32GB LTE
Click to expand...
Click to collapse
Internal storage size doesn't matter in this case I think, but 10.1.C.0.370 is for WiFi model and LTE model's firmwares use a different build, like 10.1.E.0.265.
It is not recommended to flash a different zip...
If you are already up to date and only want root, reboot fix or recovery, try @DooMLoRD's new root tool and the fix mentioned in the #1.

Fishmanzero said:
Internal storage size doesn't matter in this case I think, but 10.1.C.0.370 is for WiFi model and LTE model's firmwares use a different build, like 10.1.E.0.265.
It is not recommended to flash a different zip...
If you are already up to date and only want root, reboot fix or recovery, try @DooMLoRD's new root tool and the fix mentioned in the #1.
Click to expand...
Click to collapse
Hi Fisherman, your links are down, could you please check it? or maybe create a mirror on another server?
By the way, is this a FTF file? or flasheable ZIP? i guess is a FTF because i read on DoomLord thread that in order to flash recovery you need to have the bootloader unlocked.
Thank you.

juanyunis said:
Hi Fisherman, your links are down, could you please check it? or maybe create a mirror on another server?
By the way, is this a FTF file? or flasheable ZIP? i guess is a FTF because i read on DoomLord thread that in order to flash recovery you need to have the bootloader unlocked.
Thank you.
Click to expand...
Click to collapse
d-h.st seems down now...
Cannot upload at the moment, if d-h.st does not recovers tomorrow I will upload to another mirror.
And this is a CWM flashable zip as stated in the title.
Also installing recovery does not necessarily require unlocked BL/Custom Kernel, it can be installed on a rooted rom. Find a version works in that way~
A working one attached:

Fishmanzero said:
d-h.st seems down now...
Cannot upload at the moment, if d-h.st does not recovers tomorrow I will upload to another mirror.
And this is a CWM flashable zip as stated in the title.
Also installing recovery does not necessarily require unlocked BL/Custom Kernel, it can be installed on a rooted rom. Find a version works in that way~
A working one attached:
Click to expand...
Click to collapse
Oh nice. I guess he stated that before because the system rw reboot issue, so the best way to achieve that was using fastboot. Thank you man!

I don't understand some points in the installation instructions.
1) Why must the 370 FTF / update be flashed first? When anyway after that 344 must be flashed???
2) When the bootloader is unlocked, I can install / run CWM directly and flash this ROM here directly, or can't I??

hasenbein1966 said:
I don't understand some points in the installation instructions.
1) Why must the 370 FTF / update be flashed first? When anyway after that 344 must be flashed???
2) When the bootloader is unlocked, I can install / run CWM directly and flash this ROM here directly, or can't I??
Click to expand...
Click to collapse
Well in the instructions he said:
1. the .370 without flashing system.sin and userdata.sin, that means, only stuff not related to the system partition and well, you can keep your data because userdata.sin is not selected.
2. the .344 only system.sin because this is the one with most opportunities to root using bin4ry tool.
3. then in the files he provides, you will have the 370 system with all the fixes but that one is a CWM flash file, so you will need to install the recovery and then flash this file. See the attachment he posted here.
If your bootloader is unlocked you can use fastboot to flash the recovery. Also you can skip flashing those FTF files, and just flash the CWM file. But i believe that someone confirmed that you won't need this because if your bootloader is unlocked you can install root and remount /system without any issues.
---------- Post added at 06:58 AM ---------- Previous post was at 06:52 AM ----------
Fishmanzero said:
d-h.st seems down now...
Cannot upload at the moment, if d-h.st does not recovers tomorrow I will upload to another mirror.
And this is a CWM flashable zip as stated in the title.
Also installing recovery does not necessarily require unlocked BL/Custom Kernel, it can be installed on a rooted rom. Find a version works in that way~
A working one attached:
Click to expand...
Click to collapse
I had to adapt the script because i'm running Mac OSX 10.8.4. but this worked perfect, i've CWM recovery with a locked bootloader, only problem is that it can mount my microsd card, maybe is missing the exfat module.
Thank you!

juanyunis said:
I had to adapt the script because i'm running Mac OSX 10.8.4. but this worked perfect, i've CWM recovery with a locked bootloader, only problem is that it can mount my microsd card, maybe is missing the exfat module.
Thank you!
Click to expand...
Click to collapse
Yes this CWMR does not have exFAT support, and this ROM includes the same one.

Fishmanzero said:
Yes this CWMR does not have exFAT support, and this ROM includes the same one.
Click to expand...
Click to collapse
So great yeah :laugh:
this means i can root+get recovery on .370 with locked bootloader if i get i right ?
i have a sgp 311 wifi on official 370 installed - wil this work then ??
Greetz
-----------------------
If anyone need a mirror let me know !!
-----------------------
How do i flash in flash tool it dosent reconigze image when put in firmwares?????

spoonymoon said:
So great yeah :laugh:
this means i can root+get recovery on .370 with locked bootloader if i get i right ?
i have a sgp 311 wifi on official 370 installed - wil this work then ??
Greetz
-----------------------
If anyone need a mirror let me know !!
-----------------------
Click to expand...
Click to collapse
Since you have already updated firmware, no need to install this if the new rootkits work, try them.
Find DooMLoRD's above.
Translated Japanese toolkit from 2ch in attachment.
If they don't apply to our Tablet Z, you will have to flash 344 FTF (system only) then do the rest.

Fishmanzero said:
Since you have already updated firmware, no need to install this if the new rootkits work, try them.
Find DooMLoRD's above.
Translated Japanese toolkit from 2ch in attachment.
If they don't apply to our Tablet Z, you will have to flash 344 FTF (system only) then do the rest.
Click to expand...
Click to collapse
thanx
your attched files does say it installs root ok - but when checked after reboot - no root ?
but why not flash 370. pre rooted insted? and not least HOW do i flash it? its not a ftf file

spoonymoon said:
thanx
your attched files does say it installs root ok - but when checked after reboot - no root ?
but why not flash 370. pre rooted insted? and not least HOW do i flash it? its not a ftf file
Click to expand...
Click to collapse
You can not flash a CWM zip without recovery, and it need root to install one, and no root for 370 now
So it's necessary to download a 344 FTF, flash the system part only, and use the old working toolkit to root it.
It may be very likely to fail on different devices because the rootkit uses a kernel exploit, the address for which to run just usually varies from kernel to kernel.
Wait for our great devs to figure out the working address will be the most painless.
Or do the operations in the OP, and of course install a custom kernel after unlocking BL if you don't mind doing so, is way faster atm.
Here's an older rootkit also from 2ch. Try it if interested.

Fishmanzero said:
You can not flash a CWM zip without recovery, and it need root to install one, and no root for 370 now
So it's necessary to download a 344 FTF, flash the system part only, and use the old working toolkit to root it.
It may be very likely to fail on different devices because the rootkit uses a kernel exploit, the address for which to run just usually varies from kernel to kernel.
Wait for our great devs to figure out the working address will be the most painless.
Or do the operations in the OP, and of course install a custom kernel after unlocking BL if you don't mind doing so, is way faster atm.
Here's an older rootkit also from 2ch. Try it if interested.
Click to expand...
Click to collapse
Thanx a lot
tried and same result, says its rooted and its not - but you´re right better wait a bit for better solution , that dosent involve any risk !!
(wife and kid is going to ´kill´me if it f... up soo )

spoonymoon said:
Thanx a lot
tried and same result, says its rooted and its not - but you´re right better wait a bit for better solution , that dosent involve any risk !!
(wife and kid is going to ´kill´me if it f... up soo )
Click to expand...
Click to collapse
And yes, Japanese user got it work:laugh:
370

Fishmanzero said:
And yes, Japanese user got it work:laugh:
370
Click to expand...
Click to collapse
Woooow it f..... works i´ve got root .....wiiiiii :laugh::good::good::good::good::good::good::good::good:
i ow you big time
thanx thanx

is their a possibility for SGP321 with 10.1.1.A.1.307 too?

Fishmanzero said:
Reboot issue Fixed (Credit goes to @Carceri, Modified a bit to make it work. New solution also from him: [Locked Bootloader] The definitive root Remount-Reboot fix!)
Click to expand...
Click to collapse
Heh, you are pointing to a thread by me but refer to a fix done by Carceri ... who's are you using exactly?

[Q] Question about ROMs and warranty

Hello developers and xda members!
Some months/weeks ago I asked about rooting and warranty.I got some answers that if I unroot it or use SEUS I will not loose warranty.
This time is about roms and locked bootloaders.
If I install a CWM Recovery then flash a ROM do I void warranty?If yes is there anyway that I can make it so it's like I never flashed anything so the warranty will still last?
If yes what is the best rom I can install for LOCKED bootloader(I don't want to unlock it)?
I want a rom with good battery life + camera (I don't care if it's not 100% perfect but at least better than the stock one!)
Any answer would be helpful!
Thanks

UltraWelfare said:
Hello developers and xda members!
Some months/weeks ago I asked about rooting and warranty.I got some answers that if I unroot it or use SEUS I will not loose warranty.
This time is about roms and locked bootloaders.
If I install a CWM Recovery then flash a ROM do I void warranty?If yes is there anyway that I can make it so it's like I never flashed anything so the warranty will still last?
If yes what is the best rom I can install for LOCKED bootloader(I don't want to unlock it)?
I want a rom with good battery life + camera (I don't care if it's not 100% perfect but at least better than the stock one!)
Any answer would be helpful!
Thanks
Click to expand...
Click to collapse
Search the forum. Many other topics just like yours.

Nanostray said:
Search the forum. Many other topics just like yours.
Click to expand...
Click to collapse
Already searched but I can't find exact answer.I really don't want to loose my warranty!
Also I care for the exact model (Xperia SP) and not for others

UltraWelfare said:
Already searched but I can't find exact answer.I really don't want to loose my warranty!
Also I care for the exact model (Xperia SP) and not for others
Click to expand...
Click to collapse
Even if you unlock your bootlader you wont loose your warranty (if that is the reason you are not doing it).Just make a backup of your DRM keys and the unlock code and keep it safe.

BlAckXpeRia said:
Even if you unlock your bootlader you wont loose your warranty (if that is the reason you are not doing it).Just make a backup of your DRM keys and the unlock code and keep it safe.
Click to expand...
Click to collapse
I don't generally want to unlock bootloader.
Even if I don't unlock it and just install a rom(e.x Existenz) would I need to backup DRM keys?
Also can you give me a SAFE tutorial about backing them up?
I also asked about a good rom that has a good battery life and camera than the stock one.
What's your opinion about roms?What is the best based on your opinion?

UltraWelfare said:
I don't generally want to unlock bootloader.
Even if I don't unlock it and just install a rom(e.x Existenz) would I need to backup DRM keys?
Also can you give me a SAFE tutorial about backing them up?
I also asked about a good rom that has a good battery life and camera than the stock one.
What's your opinion about roms?What is the best based on your opinion?
Click to expand...
Click to collapse
If you wont be unlocking the bootlooder, you dont need the backup.Here is the thread with anything needed to get started with your phone: http://forum.xda-developers.com/showthread.php?t=1701644
I've never used the stock or other based on it (I use 4.3+ ROMs ), but other forum members say that Existenz is the best one out there.Currently, I am using the leaked 4.3,but it is for unlocked bootloaders.

BlAckXpeRia said:
If you wont be unlocking the bootlooder, you dont need the backup.Here is the thread with anything needed to get started with your phone: http://forum.xda-developers.com/showthread.php?t=1701644
I've never used the stock or other based on it (I use 4.3+ ROMs ), but other forum members say that Existenz is the best one out there.Currently, I am using the leaked 4.3,but it is for unlocked bootloaders.
Click to expand...
Click to collapse
Why would I need the list of things to scan with a NFC enabled phone?
Anyway so I will not void my warranty if i flash a custom rom and then "format" it with SEUS?
That's my point

UltraWelfare said:
Why would I need the list of things to scan with a NFC enabled phone?
Anyway so I will not void my warranty if i flash a custom rom and then "format" it with SEUS?
That's my point
Click to expand...
Click to collapse
nope, SUS will just repair the phone, leaving no evidence of root or ROM

Nanostray said:
nope, SUS will just repair the phone, leaving no evidence of root or ROM
Click to expand...
Click to collapse
OK Thanks nanostray (again because you also gave me answers for rooting my phone).
I will proceed installing Xperia ExistenZ rom and I hope I will not brick my phone!:fingers-crossed:
Thanks for any answer

UltraWelfare said:
Why would I need the list of things to scan with a NFC enabled phone?
Anyway so I will not void my warranty if i flash a custom rom and then "format" it with SEUS?
That's my point
Click to expand...
Click to collapse
Oops..wrong link!Here s the right one : http://forum.xda-developers.com/showthread.php?t=2354704
P.S. Im not sure but I think you will still have your warranty.Back in the days, when i had my xperia x8 and it got hardbricked, I lied to my operator that it got fully discharged and it never turned on again.The trick worked and it went to Sony with a custom ROM inside of it .Anyways..today i had to revert to stock, because the tutorial for the leaked 4.3 said so, but i encountered a problem - SUS said that my phone has modified software and it didn't complete the operation.I had to flash an .ftf image file with flashtool.But after all, It was successfull.

Ehm I got a question.At the install instructions of Existenz it says
Flash the rom.
Flash NUT reboot fix: http://forum.xda-developers.com/show....php?t=2317432
Flash 12.0.A.2.254 kernel only with flashtool (see FAQ).
As I see NUT reboot fix is for Xperia Z...Do I need to install this?Do I also need to install .254 kernel only again?At the FAQ it says about How to flash 6.2.B.1.96 Kernel with flashtool <- but this kernel is for Z...What happens?
Should I flash the rom then reboot my phone and OK?
Should I flash the rom then reboot my phone and existenz rom opens and then flash the NUT reboot fix?
Should I flash the rom then instantly install the NUT reboot fix?
Should I also install the kernel (12.0.A.254)?
I am kinda confused :/

UltraWelfare said:
OK Thanks nanostray (again because you also gave me answers for rooting my phone).
I will proceed installing Xperia ExistenZ rom and I hope I will not brick my phone!:fingers-crossed:
Thanks for any answer
Click to expand...
Click to collapse
Always glad to help but remember, in case of unlocked BL, SUS will not work.
Aye, you got a thank button for that, mate
---------- Post added at 08:07 PM ---------- Previous post was at 08:04 PM ----------
UltraWelfare said:
Ehm I got a question.At the install instructions of Existenz it says
Flash the rom.
Flash NUT reboot fix: http://forum.xda-developers.com/show....php?t=2317432
Flash 12.0.A.2.254 kernel only with flashtool (see FAQ).
As I see NUT reboot fix is for Xperia Z...Do I need to install this?Do I also need to install .254 kernel only again?At the FAQ it says about How to flash 6.2.B.1.96 Kernel with flashtool <- but this kernel is for Z...What happens?
Should I flash the rom then reboot my phone and OK?
Should I flash the rom then reboot my phone and existenz rom opens and then flash the NUT reboot fix?
Should I flash the rom then instantly install the NUT reboot fix?
Should I also install the kernel (12.0.A.254)?
I am kinda confused :/
Click to expand...
Click to collapse
1. Flash ROM
1.b Reboot phone
2. Use .bat from NUT (I used it after OTArootkeeper failed and I couldn't mount /system r/w)
3. Flash the kernel with Flashtool
Step 1b and 2 depend on what you prefer, flashing the fix or rebooting and let the computer do the fix: http://forum.xda-developers.com/showthread.php?t=2317432
You can use NUT for the SP. About the kernel I'm not sure. I am on LB atm.
Hope this helps (except for the kernel of course)

Nanostray said:
Always glad to help but remember, in case of unlocked BL, SUS will not work.
Aye, you got a thank button for that, mate
---------- Post added at 08:07 PM ---------- Previous post was at 08:04 PM ----------
1. Flash ROM
1.b Reboot phone
2. Use .bat from NUT (I used it after OTArootkeeper failed and I couldn't mount /system r/w)
3. Flash the kernel with Flashtool
Step 1b and 2 depend on what you prefer, flashing the fix or rebooting and let the computer do the fix: http://forum.xda-developers.com/showthread.php?t=2317432
You can use NUT for the SP. About the kernel I'm not sure. I am on LB atm.
Hope this helps (except for the kernel of course)
Click to expand...
Click to collapse
Everything went fine without using NUT.If problems appear then I will use it!!
Thanks again

UltraWelfare said:
Everything went fine without using NUT.If problems appear then I will use it!!
Thanks again
Click to expand...
Click to collapse
haha not every problem can be solved with NUT

Nanostray said:
haha not every problem can be solved with NUT
Click to expand...
Click to collapse
Haha I know but there it might if it's related...You never know .
Thanks again the new rom made my phone smoother + faster and a lot better.
Now we wait for 4.3 .

UltraWelfare said:
Haha I know but there it might if it's related...You never know .
Thanks again the new rom made my phone smoother + faster and a lot better.
Now we wait for 4.3 .
Click to expand...
Click to collapse
Well, I've no idea how much longer.. Should have been here in December..

{ROM}[STOCK][TX][JB 4.3][9.2.A.1.205] Deodexed + Zipaligned + Philz Recovery

XPERIA TX - JB 4.3 - 9.2.A.1.205 OFFICIAL USA STOCK ROM - FLASHABLE ZIP​
Based on the latest .205 FTF, pure stock ROM, no custom themes, superuser mod, etc.
Downloads:
1.- LT29i_9.2.A.1.205_USA_antigaprime.zip
2.- SuperSU
Basic flashing instructions apply:
1.- Flash LT29i_9.2.A.1.205_USA_antigaprime.zip
2.- Flash UPDATE-SuperSU-v1.94.zip
If flashing doesn't work for you at first, wipe /system first with recovery.
I started making this basically for myself, but since I usually delete most crapware/bloatware, I decided to share it first before I perform those changes. DPI is set to 280, since that is how I like it. If you don't like it, you can always change it back to 320 in build.prop. (Note: having the DPI to 280 changes the dialer app a bit, so I use Xposed+App Settings to set the DPI for that specific app to 320).
Stock kernel is included and flashed with the ROM, which means it'll most likely work on locked bootloaders, but if it doesn't, I am not responsible for users having to reflash their stock FTF.
So far I've tested everything, but like I said before, I am not responsible if things do not work for you, especially if you didn't wipe /system and /data.
Thanks:
@DaRk-L0rD, for answering my questions, and for all his work on which many ROMs are based on.
@Leo, for uploading the .205 FTF

Well-done bro! Thanks for the credits!

Could you pleaase post some screenshots?
Sent from my Xperia T using xda app-developers app

zy4377340 said:
Could you pleaase post some screenshots?
Sent from my Xperia T using xda app-developers app
Click to expand...
Click to collapse
Sure, but it looks exactly the same as a regular JB 4.3, and I've already modded it a bit.

auto reboot cause copy/delete file directly again. just weird , maybe i have to unlock BL and start from beginning again.

devilmaycry2020 said:
auto reboot cause copy/delete file directly again. just weird , maybe i have to unlock BL and start from beginning again.
Click to expand...
Click to collapse
You mean the reboot issue when trying to mount /system as RW? If you are talking about that, it doesn't make sense because, according to the fix:
It is safe to use on any STOCK (Read: NOT CM Based) ROM version released for all Xperia phones with the ric binary incorporated in the ramdisk (/sbin/ric) up to now.
Click to expand...
Click to collapse
This ROM/kernel does not have the ric binary incorporated in the ramdisk, though it does have the ric binary in /system/bin/. Since, according to the fix posted in the link above, the author forbids the ric binary from every starting up by changing it's permissions, if your problem were happening to me, I'd reboot into recovery, connect my phone to my pc with ADB, and do the exact same thing, or even just rename the ric binary to ric.bak, or delete it alltogether, and see if that fixes that.
As a matter of fact, even the flashable zip from that post does that exactly:
$BUSYBOX chmod 644 /system/bin/ric
Click to expand...
Click to collapse
So maybe you'd want to try flashing that file, or what I suggested, before trying to unlock your bootloader. You might find a quicker fix for your problem.

Antiga Prime said:
You mean the reboot issue when trying to mount /system as RW? If you are talking about that, it doesn't make sense because, according to the fix:
Click to expand...
Click to collapse
thanks. no no, i'm talking about delete/copy file use ROM tool box or via PC. the fix from NUT didn't solve my problem.
here is my solution, i unlock BL , flash dual recovery kernel , flash PhilZ touch, flash stock kernel back, relock BL and problem gone

Error "No detect SIM" and Can't save build.drop after edited
How can I fix it?
---------- Post added at 02:55 PM ---------- Previous post was at 02:41 PM ----------
Can't turn on wifi
No Sim card cuold be recognized
DPI 280, It looks bad and I cann't change it to 320 (Can''t save build.drop by ES fil manager, and cann't open Root Explorer, It said Stopped)
This Room contains many errors

luvyoursmile said:
Error "No detect SIM" and Can't save build.drop after edited
How can I fix it?
---------- Post added at 02:55 PM ---------- Previous post was at 02:41 PM ----------
Can't turn on wifi
No Sim card cuold be recognized
DPI 280, It looks bad and I cann't change it to 320 (Can''t save build.drop by ES fil manager, and cann't open Root Explorer, It said Stopped)
This Room contains many errors
Click to expand...
Click to collapse
calm down mate. it's work great to me. take time to optimize them.

E: Can't make /tmp/update_binary when try flashing LT29i_9.2.A.1.205_USA_antigaprime.zip

luvyoursmile said:
Error "No detect SIM" and Can't save build.drop after edited
How can I fix it?
---------- Post added at 02:55 PM ---------- Previous post was at 02:41 PM ----------
Can't turn on wifi
No Sim card cuold be recognized
DPI 280, It looks bad and I cann't change it to 320 (Can''t save build.drop by ES fil manager, and cann't open Root Explorer, It said Stopped)
This Room contains many errors
Click to expand...
Click to collapse
I am not responsible if things do not work for you, especially if you didn't wipe /system and /data.
Click to expand...
Click to collapse
You most likely didn't wipe your /data partition.
neneaiancu said:
E: Can't make /tmp/update_binary when try flashing LT29i_9.2.A.1.205_USA_antigaprime.zip
Click to expand...
Click to collapse
That's a problem with your recovery/phone, not the zip file. Try wiping /data and/or /system first, or use a different recovery.

Antiga Prime said:
You most likely didn't wipe your /data partition.
That's a problem with your recovery/phone, not the zip file. Try wiping /data and/or /system first, or use a different recovery.
Click to expand...
Click to collapse
Thanks!
Now it works great ^^

Antiga Prime said:
You most likely didn't wipe your /data partition.
That's a problem with your recovery/phone, not the zip file. Try wiping /data and/or /system first, or use a different recovery.
Click to expand...
Click to collapse
tks, it was recovery problem. with cwm worked

help
can i flash this directly on my 4.3 .199 deodex rom? or do i need to downgrade first to 4.1.2 jelly bean before i can flash this? thanks!

Rken09 said:
can i flash this directly on my 4.3 .199 deodex rom? or do i need to downgrade first to 4.1.2 jelly bean before i can flash this? thanks!
Click to expand...
Click to collapse
You can flash directly on 4.3

Is it possible to wipe battery stats on this recovery? Because when i play clash of clans, Xperia T reboots itself everytime, and battery got hotter and hotter, so i think this is the problem. If not, can someone tell me what can be the problem?

isko95 said:
Is it possible to wipe battery stats on this recovery? Because when i play clash of clans, Xperia T reboots itself everytime, and battery got hotter and hotter, so i think this is the problem. If not, can someone tell me what can be the problem?
Click to expand...
Click to collapse
You can do it through ADB in recovery, but there isn't an option in recovery for that specifically. You can even wipe it through Android directly. In any event, I don't think that is your problem:
http://www.xda-developers.com/andro...-battery-stats-does-not-improve-battery-life/

question
how was the battery life on this rom? thanks!

Rken09 said:
how was the battery life on this rom? thanks!
Click to expand...
Click to collapse
Depends on your usage, but it's basically a stock ROM. Check the attachment. I've gotten about 2 days with this, and most any other Stock ROM (4.1.2 - 4.3).

Question here:
I'm on locked bootloader, if I were to start flashing this rom from 4.1.2, is the rooting guide from this or this applicable to your rom?

Help installing custom rom

Hey guys,
I am trying to intall a custom rom on my blu vivo xl. My worries are that i either soft-brick the phone or boot the new rom and having no signal due to no imei, or no 4G due to band change if it's even possible. I'll leave you with some reliable data:
-arch64 procesor
-5.1 stock android : BLU_V0030UU_V07_GENERIC 25-01-2016
- 3.10.65+ kernel
- Rooted with kingoroot
- Previously had xposed, but uninstalled due to random reboots.
I was looking to install aospextended rom:
https://forum.xda-developers.com/vivo-xl/development/rom-aospextended-rom-v4-1-t3592932
I'd really appreciate if you could orient me or refer me to a post with instructions, since i didn't find one. It's been some years since i don't do this back to the legendary HTC HD2 and i'm missing it btw
Thanks!
Nacho

https://forum.xda-developers.com/vivo-xl/how-to/fix-soft-brickedcannot-enter-recovery-t3594733
Unfortunately most custom ROMs in this forum were based off Gionee so likely you will get no SIM. Use your stock ROM /etc/firmware folder to replace that in ROM.

min1968 said:
https://forum.xda-developers.com/vivo-xl/how-to/fix-soft-brickedcannot-enter-recovery-t3594733
Unfortunately most custom ROMs in this forum were based off Gionee so likely you will get no SIM. Use your stock ROM /etc/firmware folder to replace that in ROM.
Click to expand...
Click to collapse
Thank you for your response.
I've already got twrp installed for 5.1
So i should just install this MM based ROM i said on the post and replace /etc/firmware folder?
Or i need to install stock MM from ota first?
Thing is, i cant OTA update, it says that the system is corrupted, i even tried from twrp but no luck

I've seen that i need stock mm to be able to install most of the custom rom's in xda
Thing is i can't install any OTA update. Should i flash 5.1 stock rom on top of the modified one i'm running?
By modified i am talking about the root and xposed, which is the cause i cant OTA

Nacholer said:
I've seen that i need stock mm to be able to install most of the custom rom's in xda
Thing is i can't install any OTA update. Should i flash 5.1 stock rom on top of the modified one i'm running?
By modified i am talking about the root and xposed, which is the cause i cant OTA
Click to expand...
Click to collapse
Follow my steps exactly then you can do OTA to MM.
The key is to use the 8 files backup to restore stock 5.1, not the backup only includes 4 files.

min1968 said:
Follow my steps exactly then you can do OTA to MM.
The key is to use the 8 files backup to restore stock 5.1, not the backup only includes 4 files.
Click to expand...
Click to collapse
Alright, ill do that. Tried with the 4 files backup last night, didn't work as you just told.
Do you have a link to the 5.1 stock recovery i should flash with sp flash tool? I can't find it anywhere. It wont work if i still have twrp installed, right?
Thanks! i really appreciate it, and great guide btw

min1968 said:
Follow my steps exactly then you can do OTA to MM.
The key is to use the 8 files backup to restore stock 5.1, not the backup only includes 4 files.
Click to expand...
Click to collapse
I installed the 11 files backup and i still can't get ota. I should install the stock recovery, right? got a link for that?
Thank you in advance!

In my case I have a fully working STOCK but ROOTED Marshmallow Blu Vivo XL with working IMEI, but as soon as I wipe and install say AEX rom, I lose both IMEI functions and also get the dreaded wifi NVRAM error (but working wifi).
I also restored the etc/firmware directory to AEX but it wont help regain IMEI functionality.
MTK Engineering mode does not work on AEX because it complains not being stock rom so it closes.
For the life of me, I can't make a connection to the PC through SP Flash Tool too.
Any pointers?
TIA!

Nacholer said:
I installed the 11 files backup and i still can't get ota. I should install the stock recovery, right? got a link for that?
Thank you in advance!
Click to expand...
Click to collapse
Yes need stock recovery to do OTA.
https://forum.xda-developers.com/vivo-xl/development/recovery-t3311601
---------- Post added at 03:00 PM ---------- Previous post was at 02:56 PM ----------
Rayan said:
In my case I have a fully working STOCK but ROOTED Marshmallow Blu Vivo XL with working IMEI, but as soon as I wipe and install say AEX rom, I lose both IMEI functions and also get the dreaded wifi NVRAM error (but working wifi).
I also restored the etc/firmware directory to AEX but it wont help regain IMEI functionality.
MTK Engineering mode does not work on AEX because it complains not being stock rom so it closes.
For the life of me, I can't make a connection to the PC through SP Flash Tool too.
Any pointers?
TIA!
Click to expand...
Click to collapse
Read above my #2 post on customer ROMs in this forum.
And my this post to rescue your Blu Vivo XL :
https://forum.xda-developers.com/vivo-xl/how-to/fix-soft-brickedcannot-enter-recovery-t3594733

min1968 said:
Yes need stock recovery to do OTA.
https://forum.xda-developers.com/vivo-xl/development/recovery-t3311601
Thank you!! i'll try that and report back.
Click to expand...
Click to collapse

min1968 said:
Yes need stock recovery to do OTA.
https://forum.xda-developers.com/vivo-xl/development/recovery-t3311601
---------- Post added at 03:00 PM ---------- Previous post was at 02:56 PM ----------
Read above my #2 post on customer ROMs in this forum.
And my this post to rescue your Blu Vivo XL :
https://forum.xda-developers.com/vivo-xl/how-to/fix-soft-brickedcannot-enter-recovery-t3594733
Click to expand...
Click to collapse
Thanks for the reply Min1968!
Yes, I know how to recover IMEI on the stock ROM and I'm currently running stock MM rooted with working IMEI.
The problem I have is that I can't run custom ROMs even if I try the etc/firmware trick you mentioned.
What is the stock TWRP partition that has the modem and IMEI? Maybe if I flash it back through TWRP once I get AEX rom up and running?
Thanks!

min1968 said:
Yes need stock recovery to do OTA.
https://forum.xda-developers.com/vivo-xl/development/recovery-t3311601
---------- Post added at 03:00 PM ---------- Previous post was at 02:56 PM ----------
Click to expand...
Click to collapse
Hey, i got into deep trouble. i Factory reseted the phone. Then did fastboot oem unlock, flashed by fastboot flash recovery, the stock recovery img. After that, the phone boot-loops. I installed back twrp and it sais : Unable to mount /data
Now i can't access my internal memory and i'm stuck. Please help me!
Thanks, i really appreciate this

Nacholer said:
Hey, i got into deep trouble. i Factory reseted the phone. Then did fastboot oem unlock, flashed by fastboot flash recovery, the stock recovery img. After that, the phone boot-loops. I installed back twrp and it sais : Unable to mount /data
Now i can't access my internal memory and i'm stuck. Please help me!
Thanks, i really appreciate this
Click to expand...
Click to collapse
Okay, i fixed it reformatting the data partition on twrp. Thing is, when i want to install the recovery that happens. Maybe if i dont oem unlock?

well, i did that and it booted with the stock recovery. But i still can't OTA, i really dont know why, i even could not when i bought the phone

Nacholer said:
Hey guys,
I am trying to intall a custom rom on my blu vivo xl. My worries are that i either soft-brick the phone or boot the new rom and having no signal due to no imei, or no 4G due to band change if it's even possible. I'll leave you with some reliable data:
-arch64 procesor
-5.1 stock android : BLU_V0030UU_V07_GENERIC 25-01-2016
- 3.10.65+ kernel
- Rooted with kingoroot
- Previously had xposed, but uninstalled due to random reboots.
I was looking to install aospextended rom:
https://forum.xda-developers.com/vivo-xl/development/rom-aospextended-rom-v4-1-t3592932
I'd really appreciate if you could orient me or refer me to a post with instructions, since i didn't find one. It's been some years since i don't do this back to the legendary HTC HD2 and i'm missing it btw
Thanks!
Nacho
Click to expand...
Click to collapse
to get imei working https://forum.xda-developers.com/vivo-xl/help/solution-to-sim-detected-flashing-t3620224