Develop Bugs

Blackscreen Recovery Visual Now!!

Hi Friends
Now You can see your Black Screen Recovery!!
NO More tension of flashing Rom's With Black Screen Recovery.
But again a bad News This is only visual with PC Not in phone .
Days are gone with BLACK SCREEN RECOVERY
Here how it works!!
You need some files.
1.Download Adb Files form here
2.Download This [email protected] Tool,Thanks To RiboComments
3.Extract Adb "c:\ " on your pc Creating Folder Adb.
4.Copy [email protected] From your Downloaded folder to desktop.
5.Double click on [email protected] ,and locate the adb.exe form c:\ when asked.
6.Connect you phone using "Charge only mode" with usb debug on.
7.Follow The UI of [email protected] and when will you get your phone screen appearing.
8.Now restart your phone in Recovery mode.
And enjoy The Pleasure Of CWM.
REMEMBER: PLEASE DISABLE ANY FIREWALL (If Getting connecting error) IN YOUR PC AND INSTALL THE LATEST JAVA SDK TO MAKE WORKING THIS SOFTWARE.
Sometime if not working in CWM .
Do the following Troubleshoot .
1. Disconnect your phone.
2. Close [email protected] And
3. Delete all Files In temp Directory Of your PC. (Type " %temp% " Under search box of Start Menu or Under Run Command window) to navigate to Tempdirectory Directly .
4. Now connect Your phone With CWM recovery screen and START [email protected]
5.Click on Restart ADB . (More than once if needed)
This Tool Is Not Mine.
Original Thanks Goes to creator of this Tool RiboComments For his Great Work.

Ugh. Get out spammers. We have no such problem.
Also, could someone report this. My tapatalk won't.
Sent from my Marvelc

BigChillin said:
Ugh. Get out spammers. We have no such problem.
Also, could someone report this. My tapatalk won't.
Sent from my Marvelc
Click to expand...
Click to collapse
Hello, you will not have that problem, but I have a Wildfire S with the black screen recovery problem, and I'm not the only.
And rajanand is the only one that provides a solution.
I'll try the solution of rajanand and I will post the results
Greetings.
Sorry for my bad English.

rajanand said:
Hi Friends
Now You can see your Black Screen Recovery!!
NO More tension of flashing Rom's With Black Screen Recovery.
But again a bad News This is only visual with PC Not in phone .
Click to expand...
Click to collapse
Works great ! Thanks again.

Works great ! You're the BOSS.:good::good:
Thanks a lot.

Aww yeah! Great job sir!

BigChillin said:
Ugh. Get out spammers. We have no such problem.
Also, could someone report this. My tapatalk won't.
Sent from my Marvelc
Click to expand...
Click to collapse
little knowledge it always dangerous to health, so tk care of ur health.
Thanks aunto for commenting on my useful post.

Whatever kid, I saw how many other forums you posted this in. Can we get a REAL member of the community to confirm we need this file, and that it's not brickware.
Sent from my Marvelc

Do not download! Maybe a VIRUS!
Never heard something about this iusses.
Why should I disable my FIREWALL?
Sounds like a virus.

matt5eo said:
Never heard something about this iusses.
Why should I disable my FIREWALL?
Sounds like a virus.
Click to expand...
Click to collapse
sometimes it disconnects itself due to continuous Data transfer in between adb and phone......so
To avoid interruption between ADB and Your phone.
i personally recommend it, rest is on your side.

BigChillin said:
Whatever kid, I saw how many other forums you posted this in. Can we get a REAL member of the community to confirm we need this file, and that it's not brickware.
Sent from my Marvelc
Click to expand...
Click to collapse
Go to market and purchase brand new Lot of WFS,you will surely find black screen problem in that.
Please Stop Arguing..further ,i am not here to entertain such comments.

rajanand: This works great!! thanks
To those who are saying this thread is fake shut up because you dont face our problems with black recovery and rajanand is the only one trying to help

Anto2 said:
Hello, you will not have that problem, but I have a Wildfire S with the black screen recovery problem, and I'm not the only.
Click to expand...
Click to collapse
You are not the one with this problem I have blank CWM Recovery too.
Rajanand helped me many times.

ngoralph said:
rajanand: This works great!! thanks
To those who are saying this thread is fake shut up because you dont face our problems with black recovery and rajanand is the only one trying to help
Click to expand...
Click to collapse
Thanks for your support.

marchelius said:
You are not the one with this problem I have blank CWM Recovery too.
Rajanand helped me many times.
Click to expand...
Click to collapse
Thanks dear for support , hope you all be with me always .

rajanand said:
Thanks dear for support , hope you all be with me always
Click to expand...
Click to collapse
Of course I will
But, I have now another problem to solve: please look : http://forum.xda-developers.com/showthread.php?t=1785689
I have blank screen with older versions of CM 7 !!!

marchelius said:
Of course I will
But, I have now another problem to solve: please look : http://forum.xda-developers.com/showthread.php?t=1785689
I have blank screen with older versions of CM 7 !!!
Click to expand...
Click to collapse
try these steps and try to replace boot.img
(by copying boot.img file only inside the folder),from any other working roms
http://forum.xda-developers.com/showthread.php?t=1749212
older version of boot.img incompatible with black screen devices.

I've never had a recovery with a black screen [on any of my devices and I've tested my share of crappy recoveries]. The stock RUU recovery option sounds better OR flash a working recovery through fastboot. The whole point of a recovery is to have a tool by which you can reset/recover your device. If I have to drive in to a workstation and do an adb plug-in anytime I want to use recovery.. I'm sorry, but I'd seek a better solution. And that's without considering the security risks associated with dropping a firewall and adding a java dev kit. I would in fact, if I had experienced such, find out:
1. Why the blackscreen occurred
2. Fix it
3. Take preventative measures so that it would not occur again.
But that's just me. I wouldn't build a tool to propigate my device's bad behavior.
Rob
Sent from my HTC_A510c using Tapatalk 2

rajanand said:
try these steps and try to replace boot.img
(by copying boot.img file only inside the folder),from any other working roms
http://forum.xda-developers.com/showthread.php?t=1749212
older version of boot.img incompatible with black screen devices.
Click to expand...
Click to collapse
Not working, same sh*it

insink71 said:
I've never had a recovery with a black screen [on any of my devices and I've tested my share of crappy recoveries]. The stock RUU recovery option sounds better OR flash a working recovery through fastboot. The whole point of a recovery is to have a tool by which you can reset/recover your device. If I have to drive in to a workstation and do an adb plug-in anytime I want to use recovery.. I'm sorry, but I'd seek a better solution. And that's without considering the security risks associated with dropping a firewall and adding a java dev kit. I would in fact, if I had experienced such, find out:
1. Why the blackscreen occurred
2. Fix it
3. Take preventative measures so that it would not occur again.
But that's just me. I wouldn't build a tool to propigate my device's bad behavior.
Rob
Sent from my HTC_A510c using Tapatalk 2
Click to expand...
Click to collapse
its fully upon users ,weather they are using it on firewall on or off.(it will work on both the conditions if the "adb" have the access to the port)
its just a recommendation from my side. That's it
Its fully safe from my end and free from any type of virus.
as i have already said this tool is not mine.Please consult the owner of this tool linked on first page of this Thread For future reference.
i don't know why this "black screen recovery" Problem is there with all the newly manufactured WFS.
Why occurred?
1. I am rooting and reflashing CWM on old wfs without any problem.(even rooted for the first time)
2. the same above is not working with any newly manufactured devices.(all working well but With a black CWM recovery)
3. My doubts are pointing, its a fault of hardware,or any kind of display adapters Upgradation from HTC Side.(May be HTC is planning to give supports like ICS etc for future)
4.Also Some rooting errors can be the catch,(Again if HTC upgraded something)
4.CWM is fully working without any error.(Blindly)
5.only the four keys are lighting up,
6.This tool is The only option in that case to flash any custom ROMS.

[9/9/12][Recovery]Clockworkmod v6.0.1.3

This is just a recovery I compiled from the latest available code from the CM10 source. It does not offer any major upgrade in function from ACL's latest cwm recovery, but is slightly aesthetically different.
Installation:
Download from link below, flash with fastboot
Code:
fastboot flash recovery recovery.img
Bugs:
recovery.log may show these errors:
Code:
failed to open /sys/class/android_usb/android0/state: No such file or directory
but it does not affect usb or mass storage afaik.
Download:
recovery_cwr_6.0.1.3.img - 3.36 MB 9912
Credits: Everyone involved in Android development.
Feel free to report any bugs and enjoy.

works great, but one question: what is the thing you are asked first time you click reboot system now and what should i have answered yes or no, cause i clicked no?

Ranomez said:
works great, but one question: what is the thing you are asked first time you click reboot system now and what should i have answered yes or no, cause i clicked no?
Click to expand...
Click to collapse
I have not seen that prompt before.. what did it say? If you don't know what it does, answering "no" is probably a good idea

jianC said:
I have not seen that prompt before.. what did it say? If you don't know what it does, answering "no" is probably a good idea
Click to expand...
Click to collapse
something about after reboot rom may flash stock recovery, do you want to disable recovery flash, thats the question i get

Ranomez said:
something about after reboot rom may flash stock recovery, do you want to disable recovery flash, thats the question i get
Click to expand...
Click to collapse
In that case, just choose "no".

sorry to revive this old thread, but i just realised this recovery has a big problem and wanted to warn anyone who may want to try it: most blckups made by it have md5 mismatch, i meant i got that error at 14 out of 15 backups created.
EDIT1: i had a look at the backup folder and as far as i can see some .img files are not generated (i think cache and recovery) and also the nandroid.md5 is not generated, but that is easy to fix by generating it by urself throu adb.

Battery loading Led not working
The Led is not working with this recovery while charging.
I guess the Battery is not loading, too.
Edit - This is only, when phone is off. -
Hope this can be fixed.
regards

Sorry about the bugs/lack of support but I do not have a Touch Pro 2 anymore.
The most help I can offer is uploading the device tree that I used to compile recovery in CM10 (and potentially compile a booting version of CM10 but that has never been accomplished due to kernel issues).
https://github.com/jianC/android_device_htc_rhodium

jianC said:
Sorry about the bugs/lack of support but I do not have a Touch Pro 2 anymore.
The most help I can offer is uploading the device tree that I used to compile recovery in CM10 (and potentially compile a booting version of CM10 but that has never been accomplished due to kernel issues).
http://ge.tt/1gVK1FS/v/0?c
Click to expand...
Click to collapse
If you would like to play with the 3.4.17 kernel for S&Gs, you can find it in this thread at the bottom of the first post.
Maybe some of the kernel issues will be fixed there? I can probably get the git for it if you would want it.

wizardknight said:
If you would like to play with the 3.4.17 kernel for S&Gs, you can find it in this thread at the bottom of the first post.
Maybe some of the kernel issues will be fixed there? I can probably get the git for it if you would want it.
Click to expand...
Click to collapse
Thanks for the links, but I do not have a rhod for testing anymore.. maybe someone adventurous could take a stab at it .

CM on LOCKED Bootloader !! Now with test build !!(CM9)Come and help !! :)

Hey everybody !!! Did you red this ?? http://www.xda-developers.com/android/locked-bootloader-xperia-s-and-want-cm10-no-problem/
Is it possible on our devices too ?? It would be awensome if anybody from our community could do anything like this for our device .
I think at least CM7 or 9 would be possible i dont even think of getting cm10..
@djolivier
Hi,
it could be possible. I just made a test build for everyone who is willing to test (even users with UB). This is for anzu, don't know if it will work with Arc. Do NOT mirror it, share it or something else. I don't want to create a thread for this because I'm not sure wether it boots or not. The reason why I post it here is that I want to know if it boots. If it does, tell me how it is like. If it doesn't, try to boot to recovery (thanks to pvyParts for recovery.tar, I will remove it later, it's just for debugging purposes) and get me log by connecting the phone to a PC and issueing
Code:
adb shell cat /proc/last_kmsg > sdcard/last_kmsg.txt
.
Developers, feel free to correct mounting points or errors in ramdisk.
Please charge your battery up to 100% before flashing this because offline charging might be broken. I am not responsible for anything (not even for bricked devices) at all, I just wanted to share it for you as I actually made this for a friend of mine who can't test it ATM.
Thanks to FXP for making this all possible!
DOWNLOAD: http://goo.im/devs/djolivier/anzu/CyanogenMod for LB//cm-9-lb-anzu.zip
Click to expand...
Click to collapse

The support is dropped for both CM 7.2 and CM 9, so the chance, that someone will actually make it work, is very low.

Someguyfromhell said:
The support is dropped for both CM 7.2 and CM 9, so the chance, that someone will actually make it work, is very low.
Click to expand...
Click to collapse
It is a shame because i thnik i'm not the only one who can't open the BL so a CM for locked bl would be very awensome..

adamka13 said:
It is a shame because i thnik i'm not the only one who can't open the BL so a CM for locked bl would be very awensome..
Click to expand...
Click to collapse
I think it will be harder because Xperia 2011 devices and Xperia 2012 devices use different memory partitions.
僕のLT18iから送られてきた

Hi,
it could be possible. I just made a test build for everyone who is willing to test (even users with UB). This is for anzu, don't know if it will work with Arc. Do NOT mirror it, share it or something else. I don't want to create a thread for this because I'm not sure wether it boots or not. The reason why I post it here is that I want to know if it boots. If it does, tell me how it is like. If it doesn't, try to boot to recovery (thanks to pvyParts for recovery.tar, I will remove it later, it's just for debugging purposes) and get me log by connecting the phone to a PC and issueing
Code:
[B]adb shell cat /proc/last_kmsg > sdcard/last_kmsg.txt[/B]
.
Developers, feel free to correct mounting points or errors in ramdisk.
Please charge your battery up to 100% before flashing this because offline charging might be broken. I am not responsible for anything (not even for bricked devices) at all, I just wanted to share it for you as I actually made this for a friend of mine who can't test it ATM.
Thanks to FXP for making this all possible!
DOWNLOAD

djolivier said:
Hi,
it could be possible. I just made a test build for everyone who is willing to test (even users with UB). This is for anzu, don't know if it will work with Arc. Do NOT mirror it, share it or something else. I don't want to create a thread for this because I'm not sure wether it boots or not. The reason why I post it here is that I want to know if it boots. If it does, tell me how it is like. If it doesn't, try to boot to recovery (thanks to pvyParts for recovery.tar, I will remove it later, it's just for debugging purposes) and get me log by connecting the phone to a PC and issueing
Code:
[B]adb shell cat /proc/last_kmsg > sdcard/last_kmsg.txt[/B]
.
Developers, feel free to correct mounting points or errors in ramdisk.
Please charge your battery up to 100% before flashing this because offline charging might be broken. I am not responsible for anything (not even for bricked devices) at all, I just wanted to share it for you as I actually made this for a friend of mine who can't test it ATM.
Thanks to FXP for making this all possible!
DOWNLOAD
Click to expand...
Click to collapse
Wooooooooooooww!!! THANK YOU Very Much!!! I will test if i have some time! What do you need if boot successfully? Thanks again, this is unbelievable!!

Sorry, can i flash this from CWM? Delete cache,system,data,etc before flash?(which is must?)

Yes, just flash it using CWM and make a factory reset (data, cache, dalvik cache). System gets wiped automatically.

boot
djolivier said:
Yes, just flash it using CWM and make a factory reset (data, cache, dalvik cache). System gets wiped automatically.
Click to expand...
Click to collapse
Hi!
Flashed, wiped before. No boot, stuck at sony logo Cannot go to recovery, pressed voldown multiple times + tried to release the button but no recovery.

mman1982 said:
Hi!
Flashed, wiped before. No boot, stuck at sony logo Cannot go to recovery, pressed voldown multiple times + tried to release the button but no recovery.
Click to expand...
Click to collapse
Do you have ICS kernel ? I mean you came from an ICS rom ?

boot
adamka13 said:
Do you have ICS kernel ? I mean you came from an ICS rom ?
Click to expand...
Click to collapse
Yeah, i come from UHD. I used .13 ICS kernel.

mman1982 said:
Yeah, i come from UHD. I used .13 ICS kernel.
Click to expand...
Click to collapse
Hmm.. you should try with .587 's kernel maybe it could help. /Sorry but im on GB and i don't have time to test.. :/

Yes as far as I remember I used .587 kernel. Can I please have a log? I was aware of the fact that it wouldn't boot (and I hope you are too). This is for advanced users/dev only. I do not own the Xperia Arc S (therefore I don't want to create a thread for this) If another dev who owns this device wants to continue this project, he can do so.

boot
djolivier said:
Yes as far as I remember I used .587 kernel. Can I please have a log? I was aware of the fact that it won't boot (and I hope you are too).
Click to expand...
Click to collapse
Hi,
I tried adb shell with connected USB but device not found, so i cannot get log Recovery won't work with voldown..so no log there I will try with .587 but now i haven't got more time

I think we sholud post this in another section of this forume bec. this is only a Q/A section and maybe just some people can se it...

As I said, I'm not going to create a thread. If you want to overtake the responsabilty AND the project and you think you have the skills to get this working, you can create a thread. Else it's pointless.

Forum
adamka13 said:
I think we sholud post this in another section of this forume bec. this is only a Q/A section and maybe just some people can se it...
Click to expand...
Click to collapse
Yes, i think too..

djolivier said:
As I said, I'm not going to create a thread. If you want to overtake the responsabilty AND the project and you think you have the skills to get this working, you can create a thread. Else it's pointless.
Click to expand...
Click to collapse
I'm just asking for somebody because i don't have experience in this stuff..... :/ And Yes you are completly right !

boot
No problem, i flashed stock tft and restored from backup I feel myself an advanced user, but not a developer.

Well it's sad it didn't boot was hoping for it...
Sent from my LT18i using xda app-developers app

[TOOL] OneX Modder |Recovery|Roms|BL Unlocker|And Much More!|

The disclaimer is attached to the script file. When you open them, a disclaimer will show up with 2 choices: accept them or exit.
Hi guys
I'm here for give you a batch script (with repo) that works on all windows system without installing .net framework or other software!
The only thing that you need is WinRAR 5.30 or up! Otherwise you will aren't able to unpack all the folder.
I've made this because i see some people that wants to mod his One X, but they can't due to unknown errors with some tools.
This tool will do these functions:
*Bootloader Unlocker/Locker!
*Fastboot Recharger!
*Helps to root your device!
*Recovery Flasher! (New layout and Old layout, no need to download anything!)
*Guides to flash a custom rom!
*boot.img extractor and autoflasher!
*CID/MID Reader!
*Fastboot Emergency Recovery!
*Some accurates guides! (provided by @teemo)
*Integrated FAQ and How To!
*Fastboot&ADB status Connection Verifer!
*And much much more! Stay tuned!
Special contributors:
@teemo for providing all stuff needed like recoveries, guides and others.
Downloads and repo:
MEGA LINKS:
V1.0 Stable: https://mega.nz/#!NddVkTTb!aINZPwACwHgAYgpA4L8tR86dobJ9zGuGpY-5In3YE7E
Beta3: https://mega.nz/#!AFkEFJIL!jI3EJtJhbdiT_Q8I7tb3qnDINNj3os8CYNtB_htHGvA
Beta2: https://mega.nz/#!MUlSgZwI!SPaAKOkgt-xCHyzMwb6rJmzW0mQY66N8L87S5JbgZVs
Beta1: https://mega.nz/#!tRMDHDAZ!Cv09ijHB5WJrp5zNL4gzUyz3cv_1qy1X06Lx_e_t65k
Google Drive Links:
V1.0 Stable: https://drive.google.com/file/d/0BzLuAF-eWwH9VnIzNkxEbldsTjQ/view?usp=drivesdk
GitHub Repo: https://github.com/Giovix92/onex-modder.git
Tested OS:
*Windows 98 (Yeah, on VM )
*Windows XP (All SPs)
*Windows Vista (All SPs)
*Windows 7 (All SPs)
*Windows 8
*Windows 10
Download it and test if all works! If there is any bug, tell me! If anyone goes wrong, i'm happy to help you!
Please don't modify the batch code, or you can harm your device/pc.
Changelog:
V1.0 Stable: Added 5 more function. Check the new features pressing 11 on the menù!
V1.0b3: Added 7 more functions. Now there is 11 items + 2 hide on the menú. Check the new features pressing 11 on the menú!
V1.0b2: Added 2 new functions: Fastboot & Adb status connection verifer and Fastboot phone recharger
V1.0b1: Initial Release
Enjoy! )

How to use:
You don't need to setup anything.
You don't need .NET Framework. Simply install WinRAR 5.30 or up, download my rar package, decompress it and open the batch file. Make sure you have this tree:
|OneX_Modder (Folder)
|---OneX_Modder.bat
|---Resources
At first screen there is the disclaimer. After the disclaimer, there are some options:
If you want to unlock your bootloader, press 1. It will guides on how to. It includes an Unlock_code.bin auto flasher. )
If you want to flash a custom recovery, press 2. It will flash a custom recovery in the menú. Simply select a recovery, type Y (yes) and wait for the flashing. It's very easy. No more annoying manual-flashing
If you want to root your device, press 3. There is an explained how to.
If you want to flash a custom rom, press 4. There is an boot.img extractor and flasher and a guide provided by @teemo (thanks).
If you want to verify if the pc recognize the device, press 5, and the tool will show you the adb&fastboot status.
If you are desperatly in need to flash a rom but you haven't enough power, no more worries!! Reboot your phone in fastboot mode, connect to the pc, press 7 and your phone will be recharged!
If you want to read the about, press 9.
If you want to flash a new RUU, but you have the Bootloader unlocked and you need to flash a new RUU, press 8 and your bl will be relocked!
If you want to see the lasts changes, press 11.
If you want to flash a custom rom, but your hboot is older, press 0 and you will be guided. You need only to follow the first steps. The final process is automated!
FAQ:
Q: I have a problem with this tool! How can i do?
A: Don't worry! I will help you in any situation!
Q: Why some numbers aren't show?
A: They aren't shown because i'm working on their sections. I will add in new betas
Q: Really i need WinRAR? Why?
A: Yes, because the .rar archive is a RAR5 archive. Only WinRAR can open them.
Q: I really love it! How can i support you?
A: Simply press thanks button!
Q: How can i contact you if i have a problem with this tool?
A: Only this thread, because if a user has the same problem than you, he will find easily the solution without making a new post.

Added beta2! It has new functions: please check changelog (op post)

Thank you. Please place instructions of use/setup in op

nchc said:
Thank you. Please place instructions of use/setup in op
Click to expand...
Click to collapse
Yes, sure! There's no setup. I will add in 2nd post. Thanks for the tip.

Added an How to and FAQ. Enjoy! The beta3 is already ready for uploading! I will upload it the next week.

Guys, tell me your favourite colours for this little batch script and i will create 3 modded version with different colours! The beta3 will be published the next week due to much much work on it. It will has: HBOOT Upgrader, an how to and more more functions! The size is decreased of 30%. Sorry for this little problem

Some trouble.
Hello and thank you for your effort! I tried to flash twrp2853-endeavoru-NewLayout over the old one but while in recovery, the phone stays stuck at twrp hox welcome screen. Any idea of how can I pass this and access the twrp menu?

b12rtc said:
Hello and thank you for your effort! I tried to flash twrp2853-endeavoru-NewLayout over the old one but while in recovery, the phone stays stuck at twrp hox welcome screen. Any idea of how can I pass this and access the twrp menu?
Click to expand...
Click to collapse
Hmmm. Isn't passing at all TWRP welcome screen? The phone can boot up in fastboot? If yes, Try this: go on Resources-ADB_TOOLS. Right click on ADB_TOOLS and select command prompt. Then reboot your phone in bootloader mode and type: fastboot erase cache , press enter, type fastboot reboot bootloader or fastboot reboot-bootloader and try to access in recovery.
P.s. tomorrow i will publish beta3 with HBOOT Upgrader and much much more!

Giovix92 said:
Hmmm. Isn't passing at all TWRP welcome screen? The phone can boot up in fastboot? If yes, Try this: go on Resources-ADB_TOOLS. Right click on ADB_TOOLS and select command prompt. Then reboot your phone in bootloader mode and type: fastboot erase cache , press enter, type fastboot reboot bootloader or fastboot reboot-bootloader and try to access in recovery.
P.s. tomorrow i will publish beta3 with HBOOT Upgrader and much much more!
Click to expand...
Click to collapse
Thanks for reply! I've just tried what you suggested but in recovery I still can't pass the twrp ''hox teamwin big'' screen. If I put the old layout back everything is fine again but can't flash any newer rom.
I must tell you though, that I've tried to install it before using different ways but I had the same result There's no way to pass the twrp new layout's start scxreen. So I guess there's something wrong on my side... (I had cwmr before, it may be that?). If you have any other suggestion i'll be happy to try, If not I'll try to dig more.
Once again, thank you for your work and support.

b12rtc said:
Thanks for reply! I've just tried what you suggested but in recovery I still can't pass the twrp ''hox teamwin big'' screen. If I put the old layout back everything is fine again but can't flash any newer rom.
I must tell you though, that I've tried to install it before using different ways but I had the same result There's no way to pass the twrp new layout's start scxreen. So I guess there's something wrong on my side... (I had cwmr before, it may be that?). If you have any other suggestion i'll be happy to try, If not I'll try to dig more.
Once again, thank you for your work and support.
Click to expand...
Click to collapse
Hmmm... Probably the zip is damaged. The TWRP is flashed successfully or there are errors? No, the cwm doesn't make any problem. I will try to view if there is a problem on the code. Thanks for your test

Giovix92 said:
Hmmm... Probably the zip is damaged. The TWRP is flashed successfully or there are errors? No, the cwm doesn't make any problem. I will try to view if there is a problem on the code. Thanks for your test
Click to expand...
Click to collapse
I don't know for sure, but I rather think your zip file is ok. The flashing was ok, no errors. It's probably my phone. Of course, a double check on the code doesn't hurt, it just might be loosing time for nothing. Of course, if you will come back with something new tomorrow I will try my luck again

b12rtc said:
I don't know for sure, but I rather think your zip file is ok. The flashing was ok, no errors. It's probably my phone. Of course, a double check on the code doesn't hurt, it just might be loosing time for nothing. Of course, if you will come back with something new tomorrow I will try my luck again
Click to expand...
Click to collapse
I will check the code asap. In 10 minutes i will update you... No, if it's your phone other recoveries doesn't boot at all. Anyway, i will check. Retry and update me. Good luck!
Edit: I've checked all the code, of all recoveries.Now i will add stock HTC Recovery (if anyone wants the stock recovery). Anyway... I will add another TWRP with New Layout Support.
Edit2: Check the beta3!

Beta3 is out! Check the new version! It has 7 more functions. You can find them in OP post at Downloads section!

b12rtc said:
I don't know for sure, but I rather think your zip file is ok. The flashing was ok, no errors. It's probably my phone. Of course, a double check on the code doesn't hurt, it just might be loosing time for nothing. Of course, if you will come back with something new tomorrow I will try my luck again
Click to expand...
Click to collapse
Man, type fastboot getvar all into your cmd, and post here the result.

Guys, tell me any idea for the first stable. If you want any function on this script, tell me and i add them! (S-OFF is possible only on HTC One X+ and AT&T HTC One X)

Giovix92 said:
Guys, tell me any idea for the first stable. If you want any function on this script, tell me and i add them! (S-OFF is possible only on HTC One X+ and AT&T HTC One X)
Click to expand...
Click to collapse
Any chance of incorporating the ability to get Kali Nethunter on our One X(https://cyberkryption.wordpress.com/2014/10/13/the-quest-for-kali-nethunter-part1/)

pleomaxell said:
Any chance of incorporating the ability to get Kali Nethunter on our One X(https://cyberkryption.wordpress.com/2014/10/13/the-quest-for-kali-nethunter-part1/)
Click to expand...
Click to collapse
Hmmm... I've read all the steps... But i don't know kali nethunter. I know only Kali for pc. If you explain me because you want it i will add them in a separate batch that will be called by the main program. The main step is to build the cm... the 2nd is more difficult... The 3rd too... Please explain me. Thanks in advance.

Giovix92 said:
Hmmm... I've read all the steps... But i don't know kali nethunter. I know only Kali for pc. If you explain me because you want it i will add them in a separate batch that will be called by the main program. The main step is to build the cm... the 2nd is more difficult... The 3rd too... Please explain me. Thanks in advance.
Click to expand...
Click to collapse
I don't know how to explain it to you because I am not a programmer. I tried to follow that guide but got scared because it looked a bit complex.

pleomaxell said:
I don't know how to explain it to you because I am not a programmer. I tried to follow that guide but got scared because it looked a bit complex.
Click to expand...
Click to collapse
Okay, so... The process for me is a bit complicated because now i'm a win user, and not a linux user due to my bad pc (only 1gig of ram, single core 1.66GHz), but i can create an .sh script that can do this process automatically. Maybe if this work i will create some .sh script to build some custom rom . I need only to write the code that is in the guide (maybe with 2-3 sec of delay too and some echo) and optimizing them with some request. Anyway, stay tuned!

Samsung j2 Prime (sm-g532m) - how do I get LineageOS on this device?

I'm not completely brand new to flashing with custom roms, but I sometimes go 2-3 years running stock, so when I do come back I have forgotten everything and it feels like starting over.
So far I have achieved the following:
1 - backed up device
2 - reset device back to stock
3 - flashed stock image using Heimdall
Unfortunately after all that I am not sure if I have made any progress. It just took my phone back to factory settings.. My storage is full, my SDCard is empty and I can't push a file to the sdcard because I don't know how to reference the right path.
I tried flashing a TWRP recovery.img file to the recovery partition, and it indicated success. But when I boot into recovery it looks exactly like it did before. I get no TWRP gui interface. The TWRP app has no official build for this device, so is unusable. I also tried installing Magisk but got errors and just uninstalled it.
Frankly I don't know what to do yet. I'm not sure the device is officially 'rooted' or not. I'm not sure what to do next. Do I flash an Enigma Android 6 image? Do I have to do that before I can update to Android 9?

dixonge said:
I'm not completely brand new to flashing with custom roms,.........
Click to expand...
Click to collapse
I don't have this device but, your best bet is to take a look at the following TWRP thread that's specific to your device and variants. Don't be afraid to ask for some member guidance as well.
https://forum.xda-developers.com/showthread.php?t=3616589
Good Luck!
~~~~~~~~~~~~~~~
UNLESS asked to do so, PLEASE don't PM me regarding support. Sent using The ClaRetoX Forum App on my Commodore VIC-20.

Ibuprophen said:
I don't have this device but, your best bet is to take a look at the following TWRP thread that's specific to your device and variants. Don't be afraid to ask for some member guidance as well.
https://forum.xda-developers.com/showthread.php?t=3616589
Good Luck!
~~~~~~~~~~~~~~~
UNLESS asked to do so, PLEASE don't PM me regarding support. Sent using The ClaRetoX Forum App on my Commodore VIC-20.
Click to expand...
Click to collapse
Yes, that's where I got my twrp recovery.img file from. I'll go back through those steps and ask in the thread if I have further issues. Thanks.

Typically there is a reboot into system after flashing twrp. Some stock ROM replace twrp with stock recovery in that case.
Known workarounds:
Flash twrp to boot partition also
Remove battery after flashing twrp
Use windows Odin and unchecked reboot
Do some key tricks to force recovery during reboot.
Once twrp booted, it normally does tricks to not get overwritten.

Asgard holds your answer
dixonge said:
I'm not completely brand new to flashing with custom roms, but I sometimes go 2-3 years running stock, so when I do come back I have forgotten everything and it feels like starting over.
So far I have achieved the following:
1 - backed up device
2 - reset device back to stock
3 - flashed stock image using Heimdall
Unfortunately after all that I am not sure if I have made any progress. It just took my phone back to factory settings.. My storage is full, my SDCard is empty and I can't push a file to the sdcard because I don't know how to reference the right path.
I tried flashing a TWRP recovery.img file to the recovery partition, and it indicated success. But when I boot into recovery it looks exactly like it did before. I get no TWRP gui interface. The TWRP app has no official build for this device, so is unusable. I also tried installing Magisk but got errors and just uninstalled it.
Frankly I don't know what to do yet. I'm not sure the device is officially 'rooted' or not. I'm not sure what to do next. Do I flash an Enigma Android 6 image? Do I have to do that before I can update to Android 9?
Click to expand...
Click to collapse
OK, bad jokes about Nordic deities aside. Try using ODIN rather than Heimdall to flash TWRP. In ODIN, make sure the automatic reboot on exit feature is turned OFF. After exiting ODIN, MANUALLY reboot the thing into recovery mode using whatever multiple button combination is required, and you "should" find it starting up TWRP for you. ASSUMING that is so, then power off the device and re-start it. it "should" now be working correctly, meaning with whatever ROM you have in place and TWRP as the recovery. And if THAT worked, you can flash SU using TWRP if you are not already rooted and you are good to go. Good Luck.

I now have managed to finally get TWRP flashed. It worked this time. Could not begin to tell you what I did differently...
I managed to flash the custom ROM and am now dealing with two remaining issues - a password I am being asked for that I never set, and getting the right version of opengapps flashed.

nezlek said:
OK, bad jokes about Nordic deities aside. Try using ODIN rather than Heimdall to flash TWRP. In ODIN, make sure the automatic reboot on exit feature is turned OFF. After exiting ODIN, MANUALLY reboot the thing into recovery mode using whatever multiple button combination is required, and you "should" find it starting up TWRP for you. ASSUMING that is so, then power off the device and re-start it. it "should" now be working correctly, meaning with whatever ROM you have in place and TWRP as the recovery. And if THAT worked, you can flash SU using TWRP if you are not already rooted and you are good to go. Good Luck.
Click to expand...
Click to collapse
FYI - the only version of Odin I could find for Linux is a glitchy Java version. All the tutorials say to put things in the 'AP Slot' - and I can clearly see that in screenshots. But my version didn't have an AP slot. The graphics were misaligned and I finally gave up. I did manage to flash a ROM using ADB sideload. So there's that.

ODIN for Linux ....
dixonge said:
FYI - the only version of Odin I could find for Linux is a glitchy Java version. All the tutorials say to put things in the 'AP Slot' - and I can clearly see that in screenshots. But my version didn't have an AP slot. The graphics were misaligned and I finally gave up. I did manage to flash a ROM using ADB sideload. So there's that.
Click to expand...
Click to collapse
Yeah, Odin can be more than a little bit "glitchy" on Linux boxes. Surprised you found one that worked at all, to be totally candid. I suggest to folks that they just beg, borrow, or steal 15 minutes on a Windows box and do it the easy way. Yes, I know "windows" is a very long "four letter word" in many circles, but sometimes you just bite the bullet and take the path of least resistance. The IMPORTANT question is: is your problem solved ??

nezlek said:
Yeah, Odin can be more than a little bit "glitchy" on Linux boxes. Surprised you found one that worked at all, to be totally candid. I suggest to folks that they just beg, borrow, or steal 15 minutes on a Windows box and do it the easy way. Yes, I know "windows" is a very long "four letter word" in many circles, but sometimes you just bite the bullet and take the path of least resistance. The IMPORTANT question is: is your problem solved ??
Click to expand...
Click to collapse
Good question. Do I have LineageOS on my device? Yes.
Is it a usable version? Uh, no. My device is now reporting to be a Galaxy J7 and the WiFi is useless. This was from an Enigma ROM. So at least I have managed to figure out how to flash the device and TWRP recovery is working. Now to find a better ROM.
I guess the question I have now is this: *IS THERE* an actual, working Android 9 PIE ROM for the J2 Prime (Grand Prime+) model?

dixonge said:
Good question. Do I have LineageOS on my device? Yes.
Is it a usable version? Uh, no. My device is now reporting to be a Galaxy J7 and the WiFi is useless. This was from an Enigma ROM. So at least I have managed to figure out how to flash the device and TWRP recovery is working. Now to find a better ROM.
I guess the question I have now is this: *IS THERE* an actual, working Android 9 PIE ROM for the J2 Prime (Grand Prime+) model?
Click to expand...
Click to collapse
Hui. Quick search in XDA shows: there is probably no aosp based ROM for your device. So you flashed a ROM for a different device? You should learn a bit about model names and codenames. And be glad to not have bricked your phone.

kurtn said:
Hui. Quick search in XDA shows: there is probably no aosp based ROM for your device. So you flashed a ROM for a different device? You should learn a bit about model names and codenames. And be glad to not have bricked your phone.
Click to expand...
Click to collapse
Well, it's from here on XDA, and it was advertised as being ported for my model specifically. Just surprised to see the other model info in 'About' - I agree that Pie seems to be non-existent for this phone. What about Oreo? So far every single article I find on the 'net is just click-bait.

Sometimes it is better to stay on stock ROM. With twrp you can install magisk or xposed or nanodroid.